CPAM commissioning configuration

Overview

The main components of the control plane assurance management solution are:

route analyzer component, the 7701 CPAA
server component, the CPAM

The CPAM server component contains 7701 CPAA control frameworks, applications, and coordination functions for the distributed 7701 CPAAs. The CPAM server also provides the applications that are required to process the 7701 CPAA data.

CPAM commissioning configuration workflow

The following workflow describes the commissioning of the CPAM. See “CPAM commissioning configurations” in the NSP NFM-P Control Plane Assurance Manager User Guide for more information about CPAM commissioning.


1	Create the IGP administrative domains, or BGP autonomous systems (AS), or both, as required.
2	Assign role(s) to the 7701 CPAAs and associate every 7701 CPAA to an IGP administrative domain, or BGP AS, or both.
3	Enable the 7701 CPAA.

CPAM administrative domains

An administrative domain represents a logical routed network. Administrative domains are configured by the operator to reflect the logical structure of the network. The following types of administrative domains are supported:

IGP administrative domain

Represents an IGP routed network. In an IGP administrative domain, there can be both an OSPF and an IS-IS network.
BGP autonomous system

Represents either a standard BGP AS, a BGP Confederation AS, or a BGP Sub-AS (confederation member). BGP Sub-ASs are configured as members of a Confederation BGP AS.

See the NSP NFM-P Control Plane Assurance Manager User Guide for the rules governing the assignment of administrative domains.

Following are the minimum XML parameter tags required to develop an XML request to create an IGP administrative domain and a BGP AS.

The generic.GenericObject.configureChildInstance method is used to create an IGP administrative domain and a BGP AS. The request response returns the <objectFullName> attribute to identify the new IGP administrative domain and BGP AS, respectively.

IGP administrative domain creation parameters

method—generic.GenericObject.configureChildInstance
distinguishedName—tpgy-mgr. The FDN can be determined by looking at the Parent Hierarchy of the class to be created in the XML API Reference. In this case, it is the topology.TopologyManager class.
childConfigInfo—creates and configures the following parameters:
- IGP administrative domain object - topology.AutonomousSystem
- actionMask - specifies the create operation
- <asNumber> - (optional) assigns a numeric ID. If not specified, the ID will be zero. The asNumber and displayedName together need to be unique.
- <displayedName> - assigns a name. The asNumber and displayedName together need to be unique.
- <menuControl> - sets the bits for enabling the protocols for the administrative domain

Figure 21-1: IGP administrative domain creation request example

<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <distinguishedName>tpgy-mgr</distinguishedName>

   <childConfigInfo>

      <topology.AutonomousSystem>

         <actionMask>

            <bit>create</bit>

         </actionMask>

         <asNumber>10</asNumber>

         <displayedName>IGPadminDomain1</displayedName>

         <menuControl>

            <bit>ospf</bit>

            <bit>isis</bit>

            <bit>igp</bit>

         </menuControl>

      </topology.AutonomousSystem>

   </childConfigInfo>

</generic.GenericObject.configureChildInstance>

BGP autonomous system creation parameters

method—generic.GenericObject.configureChildInstance
distinguishedName—tpgy-mgr. The FDN can be determined by looking at the Parent Hierarchy of the class to be created in the XML API Reference. In this case, it is the topology.TopologyManager class.
childConfigInfo—creates and configures the following parameters:
- BGP AS object - topology.BgpAutonomousSystem
- actionMask - specifies the create operation
- <asNumber> - assigns a unique numeric ID.
- <asType> - sets the BGP AS type (as is standard type, confederation is confederation type)
- <displayedName> - assigns a unique name.
- <igpAdminDomain> - tpgy-mgr:name-${displayedName}-AS-${asNumber} - pointer to the IGP administrative domain. This parameter is not required for a BGP confederation AS.

Figure 21-2: Standard BGP AS creation request example

<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <distinguishedName>tpgy-mgr</distinguishedName>

   <childConfigInfo>

      <topology.BgpAutonomousSystem>

         <actionMask>

            <bit>create</bit>

         </actionMask>

         <asNumber>35</asNumber>

         <asType>as</asType>

         <displayedName>BGPAS1</displayedName>

         <igpAdminDomain>tpgy-mgr:name-IGPadminDomain1-AS-10</igpAdminDomain>

      </topology.BgpAutonomousSystem>

   </childConfigInfo>

</generic.GenericObject.configureChildInstance>

Figure 21-3: BGP confederation AS creation request example

<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <distinguishedName>tpgy-mgr</distinguishedName>

   <childConfigInfo>

      <topology.BgpAutonomousSystem>

         <actionMask>

            <bit>create</bit>

         </actionMask>

         <asNumber>50</asNumber>

         <asType>confederation</asType>

         <displayedName>BGPAS2</displayedName>

      </topology.BgpAutonomousSystem>

   </childConfigInfo>

</generic.GenericObject.configureChildInstance>

7701 CPAA configuration

You can specify the role of a 7701 CPAA to be IGP, BGP, or both. The role of the 7701 CPAA indicates to the CPAM whether information from a protocol is interpreted. An IGP administrative domain must be assigned to a 7701 CPAA with an IGP role. A BGP AS must be assigned to a 7701 CPAA with a BGP role.

7701 CPAA set role parameters

method—generic.GenericObject.configureChildInstance
distinguishedName—network:${systemAddress}:cpaa. The FDN can be determined by looking at the Parent Hierarchy of the class to be created in the XML API Reference. In this case, it is the topology.Cpaa class.
configInfo—creates and configures the following parameters:
- 7701 CPAA object - topology.Cpaa
- actionMask - specifies the modify operation
- <role> - sets the role of the 7701 CPAA
- <asPointer> - tpgy-mgr:name-${displayedName}-AS${asNumber} - pointer to the administrative domain

Figure 21-4: 7701 CPAA IGP role-setting request example

<generic.GenericObject.configureInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <distinguishedName>network:198.51.100.70:cpaa</distinguishedName>

   <configInfo>

      <topology.Cpaa>

         <actionMask>

            <bit>modify</bit>

         </actionMask>

         <role>

            <bit>igp</bit>

         </role>

         <asPointer>tpgy-mgr:name-IGPadminDomain1-AS-10</asPointer>

      </topology.Cpaa>

   </configInfo>

</generic.GenericObject.configureInstance>

Set event types, keep event history, and enable 7701 CPAA parameters

method—generic.GenericObject.configureInstance
distinguishedName—network:${systemAddress}:cpaa. The FDN can be determined by looking at the Parent Hierarchy of the class to be created in the XML API Reference. In this case, it is the topology.Cpaa class.
configInfo—creates and configures the following parameters:
- 7701 CPAA object - topology.Cpaa
- actionMask - specifies the modify operation
- <protocolEventTypes> - sets the events that the 7701 CPAA will notify the CPAM
- <protocolRecord> - sets the protocol events to be recorded
- <administrativeState> - enables or disables the communication channels from the CPAM to the 7701 CPAA

The following figure shows an example of a request to set event types, keep an event history, and enable the 7701 CPAA.

Figure 21-5: 7701 CPAA configuration request example

<generic.GenericObject.configureInstance xmlns="xmlapi_1.0">

   <deployer>immediate</deployer>

   <distinguishedName>network:198.51.100.70:cpaa</distinguishedName>

   <configInfo>

      <topology.Cpaa>

         <actionMask>

            <bit>modify</bit>

         </actionMask>

         <protocolEventTypes>

            <bit>ospf</bit>

            <bit>isis</bit>

         </protocolEventTypes>

         <protocolRecord>

            <bit>ospf</bit>

            <bit>isis</bit>

            <bit>ospfTe</bit>

         </protocolRecord>

         <administrativeState>up</administrativeState>

      </topology.Cpaa>

   </configInfo>

</generic.GenericObject.configureInstance>