The Management Model of the Centralized Network Architecture

The Management Model of the Centralized Network Architecture draft-richard-opsawg-cna-mib-00 Richard IETF 75 th meeting, Stockholm

Preface For the Network Access Technologies such as PON, WLAN and so on, there is a Generic Management Model behind them. The presentation is to discuss the Model and give an example using SNMP MIB.

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

Typical Network Access Technologies (1/3) Passive Optical Network (PON) PON defines an architectures of fiber to the home. OLT POS ONU • OLT (Optical Line Termination) provides the interface between the PON and the service providers’ network • ONU (Optical Network Units) terminates the PON and offer interfaces such as x. DSL, Ethernet to users • OLT can manage and control the ONUs according to IEEE 802. 3 ah and IEEE 802. 1 ag

Typical Network Access Technologies (2/3) Centralized WLAN Architecture AC WTP station IETF CAPWAP WG defines RFCs for it. • AC (Access Controller) manages and controls multiple WTPs (Wireless Terminal Point) by the tunnel between WTP and AC. • WTP can forward the station’s data to AC by the tunnel. • WTP use certain wireless technologies such as 802. 11 radio interface to communicate with the station.

Typical Network Access Technologies (3/3) The PON and Centralized WLAN Architecture give some typical examples to the Network Access Technologies, the multiple access units (ONU, WTP) under control by a controller unit (OLT, AC) is a an emerging trend. There are generic models behinds • Network Topology • The Operation and Management Model

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

Centralized Network Architecture The Centralized network architecture (CNA) offers the access service to stations (user) by distributing functions among AC and multiple TPs. OLT AC manages multiple TPs through a Access Controller (AC) AC tunnel protocol. Tunnel offers a management channel to the AC ONU WTP Terminal Point (TP) 1 Ethernet, 802. 11, 3 G… 2 3 4 TP are under management by the AC Through the tunnel The interfaces on the TP are important Station entities which offers the access service to the station

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

Generic Management Model (1/2) To manage a CNA, the basic operation steps are: 1) The operator prepares the configurations for TPs to be managed before they connect to the AC and can change TPs' configuration after they connect to the AC. The configuration for a TP is identified by TP’s base MAC address. 2) The TP discovers AC and establishs the tunnel with AC. 3) TP downloads configuration by match its base MAC address with configuration’s Id. 4) TP MAY not run SNMP service, while AC SHOULD. TP reports Its status info to AC through the tunnel. AC provides the management Interfaces to the operators

Generic Management Model (2/2) The following management objects are important: 1. 1) AC 2. Such as the number Of TPs 3. connecting to AC. SNMP, Netconf AC 2) TP Such as status, software version, current configuration 3) Interfaces on the TP Such as if Name, status, configuration TP 1 1 2 3 TP 2 4 1 2 3 4 4) Tunnel Such as peer of the tunnel, the establishment time 5) Station Such as Id, the interface attached STA 1 STA 2 STA 3

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

MIB Operation Steps SNMP Agent on the AC Create TP profile to prepare Configuration It triggers the AC automatically creates Specify a TP profile used by which TPs To allow multiple TPs share a TP profile Use the MIBs such as the Network Access Technologies’ to configure parameters for TPs and their interfaces the “TP Profile Interface”. A access technology such as IEEE 802. 11 usually already defines the MIBs, We should reuse it. TP boots up and connects to AC through the tunnel Through the SNMP to query TP, station, It triggers the AC automatically creates the “TP Virtual Interface”.

TP Template Interface For any network access technology, the configuration and management of interface is very important, and a technology usually already defines the MIB modules on their own. For example, the MIB tables such as Dot 11 Operation. Table [IEEE. 802 -11. 2007] are able to support WLAN radio interface configuration, while the MIB tables such as adsl. Line. Table [RFC 2662] are able to support ADSL interface configuration. In such MIBs, the tables of the interface parameters usually use the if. Index as the Index. To prepare the configuration for the TP’s interfaces, it need the logic interfaces on the AC: TP Template Interfaces. Creation of the interface is triggered by TP profile.

TP Virtual Interface For each PHY interface on the TP, it can have a TP Virtual Interface Corresponding to it on the AC. It looks like that PHY interfaces are located on the AC, and PHY location of the TP (interface) is hidden to the operator. If. Index is used as a common handler for a corresponding interfaces in the draft and the specific network access technologies' MIB modules PHY Interface identified by Id AC TP 1 1 MAPPING TP Virtual Interface identified by if. Index AC TP 2 11 12 13

Differences between the logic Interfaces TP Template Interface Function To help the operator to do Event to Create TP Virtual Interface configuration, and it is related to the TP profile Look like an interface corresponding to the “real” PHY interface on the TP, and operator could use it (by if. Index) to query the PHY interface’s info. Once the operator creates a TP profile Once TP connects to the AC, and gets Configuration Interface Keep the up status to allow status configuration Status is same as PHY interface on the TP (as TP could report its info to the AC through the management tunnel )

TP Profile A TP profile is used to make configurations such as the name of a TP before and after it connects to the AC. The profile could be shared by multiple TPs (TP is identified by base MAC). The tunnel protocol message received from the TP MUST contains its base MAC address. The AC uses the base MAC address to find the corresponding TP profile for a specific TP. Cna. Tp. Profile. Entry : : = SEQUENCE { cna. Tp. Profile. Id Cna. Tp. Profile. Id. TC, cna. Tp. Profile. Name Snmp. Admin. String, cna. Tp. Profile. Tp. Model. Number cna. Tp. Profile. Tp. Name Snmp. Admin. String, OCTET STRING, cna. Tp. Profile. Tp. Location OCTET STRING, cna. Tp. Profile. Row. Status }

Create the TP Template Interfaces (3/4) Another important function of TP profile is to trigger the creation of TP Template Interfaces on the AC. To implement this function, a TP profile MUST include the TP's model name [RFC 4133], which reflects the number of PHY interfaces on the TP. In this way, the creation of a TP profile triggers the AC to automatically create the same number of TP Template Interfaces corresponding to the TP's PHY interfaces without manual intervention. Cna. Template. If. Mapping. Entry : : = SEQUENCE { cna. Template. If. Mapping. If. Id Cna. Interface. Id. TC, cna. Template. If. Mapping. Template. If. Index Interface. Index, cna. Template. If. Mapping. Phy. If. Type IANAif. Type } Cna. Template. If. Mapping. Entry keeps the mapping between Interface Id And the if. Index of TP Template Interface.

Reusing of the Entity MIB To model a TP, besides its status, the properties such Each TP as the model name are well defined by the Entity MIB Identified by Physical Index [RFC 4133]. It should reuse such existing standards. From the ENTITY-MIB module's perspective, AC the overall physical entity (AC) is a 'compound' of multiple physical entities (that is, the TPs connected to AC), TP 1 1 2 3 4 TP 2 1 2 3 4 and all entities are each identified by a Physical index. STA 1 STA 2 STA 3 When the draft models a TP object, it also keeps the mapping value to the Physical index. Through it, the operator could query the model name, hardware version through the ENTITY-MIB.

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

Next Steps Current draft-richard-opsawg-cna-mib-00. txt post in the web site is a MIB draft. David Harrington suggests describing the management Model as an the Information Model, as described in RFC 3444, and make it apply to SNMP and Netconf. We would follow it and intend to publish one draft for Information Model , another one is for SNMP. Later, we can have a Netconf one.

Agenda § § § Typical Network Access Technologies Centralized Network Architecture A Generic Management Model MIB Objects for the Model Next Steps Need Your Guidance

Need Your Guidance You are welcomed if you have an interest to be co-editor.

Thank You Any Question?