-
ATM Switch Router Software Configuration Guide, 12.1(7a)EY
-
Preface
-
Product Overview
-
Understanding the User Interface
-
Initially Configuring the ATM Switch Router
-
Configuring System Management Functions
-
Configuring ATM Network Interfaces
-
Configuring Virtual Connections
-
Configuring Operation, Administration, and Maintenance
-
Configuring Resource Management
-
Configuring ILMI
-
Configuring ATM Routing and PNNI
-
Using Access Control
-
Configuring IP over ATM
-
Configuring LAN Emulation
-
Configuring ATM Accounting and ATM RMON
-
Configuring Tag Switching
-
Configuring Signalling Features
-
Configuring Interfaces
-
Configuring Circuit Emulation Services
-
Configuring Frame Relay to ATM Interworking Port Adapter Interfaces
-
Configuring IMA Port Adapter Interfaces
-
Configuring IP QoS
-
Configuring the ATM Traffic Shaping Carrier Module
-
Configuring Rate Limiting and Traffic Shaping
-
Configuring ATM Router Module Interfaces
-
Managing Configuration Files, System Images, and Functional Images
-
PNNI Migration Examples
-
Acronyms
-
Index
-
Table Of Contents
Configuring ATM Routing and PNNI
Configuring ATM Address Groups
Configuring PNNI without Hierarchy
Configuring the Lowest Level of the PNNI Hierarchy
Configuring Higher Levels of the PNNI Hierarchy
Configuring ATM PNNI Statistics Collection
Connecting Mobile PNNI Networks to Fixed PNNI Networks
Configuring ATM Routing and PNNI
This chapter describes the Interim Interswitch Signaling Protocol (IISP) and Private Network-Network Interface (PNNI) ATM routing protocol implementations on the ATM switch router.
Note
This chapter provides advanced configuration instructions for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. For conceptual and background information, refer to the Guide to ATM Technology. For complete descriptions of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference publication.
This chapter includes the following sections:
•
Overview
To place calls between ATM end systems, signalling consults either IISP, a static routing protocol, or PNNI, a dynamic routing protocol. PNNI provides quality of service (QoS) routes to signalling based on the QoS requirements specified in the call setup request.
For detailed discussions of the following topics, refer to the Guide to ATM Technology:
•
•
•
ATM Addresses
The autoconfigured ATM address of the ATM switch router suffices when implementing single-level PNNI. Hierarchical PNNI requires an addressing scheme to ensure global uniqueness of the ATM address and to plan for future network expansion.
For detailed discussions of the following related topics, refer to the Guide to ATM Technology:
•
•
•
•
IISP Configuration
This section describes the procedures necessary for Interim Interswitch Signaling Protocol (IISP) configuration, and includes the following subsections:
•
Configuring the Routing Mode
The ATM routing software can be restricted to operate in static mode. In this mode, the call routing is restricted to only the static configuration of ATM routes, disabling operation of any dynamic ATM routing protocols, such as PNNI.
The atm routing-mode command is different from deleting all PNNI nodes using the node command and affects Integrated Local Management Interface (ILMI) autoconfiguration. If the switch is configured using static routing mode on each interface, the switch ILMI variable atmfAtmLayerNniSigVersion is set to IISP. This causes either of the following to happen:
•
•
Note
To configure the routing mode, perform these steps, beginning in global configuration mode:
Example
The following example shows how to use the atm routing-mode static command to restrict the switch operation to static routing mode:
Switch(config)# atm routing-mode staticThis Configuration Will Not Take Effect Until Next Reload.Switch(config)# endSwitch# copy system:running-config nvram:startup-configBuilding configuration...[OK]Switch# reloadThe following example shows how to reset the switch operation back to PNNI if the switch is operating in static mode:
Switch(config)# no atm routing-mode staticThis Configuration Will Not Take Effect Until Next Reload.Switch(config)# endSwitch# copy system:running-config nvram:startup-configBuilding configuration...[OK]Switch# reloadDisplaying the ATM Routing Mode Configuration
To display the ATM routing mode configuration, use the following privileged EXEC command:
Example
The following example shows the ATM routing mode configuration using the more system:running-config privileged EXEC command:
Switch# more system:running-configBuilding configuration...Current configuration:!version 11.2<information deleted>!hostname Switch!username dtateip rcmd remote-username dplatz!atm e164 translation-tablee164 address 1111111 nsap-address 11.111111111111111111111111.112233445566.11e164 address 2222222 nsap-address 22.222222222222222222222222.112233445566.22e164 address 3333333 nsap-address 33.333333333333333333333333.112233445566.33!atm routing-mode static
atm address 47.0091.8100.0000.0040.0b0a.2b81.0040.0b0a.2b81.00!<information deleted>Configuring the ATM Address
If you are planning to implement only a flat topology network (and have no future plans to migrate to PNNI hierarchy), you can skip this section and use the preconfigured ATM address assigned by Cisco Systems.
Note
To change the active ATM address, create a new address, verify that it exists, and then delete the current active address. Follow these steps, beginning in global configuration mode:
Example
The following example shows how to add the ATM address prefix 47.0091.8100.5670.000.0ca7.ce01. Using the ellipses (...) adds the default Media Access Control (MAC) address as the last six bytes.
Switch(config)# atm address 47.0091.8100.5670.0000.0ca7.ce01...Switch(config)# no atm address 47.0091.8100.0000.0041.0b0a.1081...Displaying the ATM Address Configuration
To display the ATM address configuration, use the following EXEC command:
Example
The following example shows the ATM address configuration using the show atm addresses EXEC command:
Switch# show atm addressesSwitch Address(es):47.00918100567000000CA7CE01.00410B0A1081.00Soft VC Address(es):47.0091.8100.0000.0041.0b0a.1081.4000.0c80.0000.00 ATM0/0/047.0091.8100.0000.0041.0b0a.1081.4000.0c80.0000.63 ATM0/0/0.9947.0091.8100.0000.0041.0b0a.1081.4000.0c80.0010.00 ATM0/0/147.0091.8100.0000.0041.0b0a.1081.4000.0c80.0020.00 ATM0/0/247.0091.8100.0000.0041.0b0a.1081.4000.0c80.0030.00 ATM0/0/347.0091.8100.0000.0041.0b0a.1081.4000.0c80.1000.00 ATM0/1/047.0091.8100.0000.0041.0b0a.1081.4000.0c80.1010.00 ATM0/1/147.0091.8100.0000.0041.0b0a.1081.4000.0c80.1020.00 ATM0/1/247.0091.8100.0000.0041.0b0a.1081.4000.0c80.1030.00 ATM0/1/347.0091.8100.0000.0041.0b0a.1081.4000.0c80.8000.00 ATM1/0/047.0091.8100.0000.0041.0b0a.1081.4000.0c80.8010.00 ATM1/0/147.0091.8100.0000.0041.0b0a.1081.4000.0c80.8020.00 ATM1/0/247.0091.8100.0000.0041.0b0a.1081.4000.0c80.8030.00 ATM1/0/347.0091.8100.0000.0041.0b0a.1081.4000.0c80.9000.00 ATM1/1/047.0091.8100.0000.0041.0b0a.1081.4000.0c80.9010.00 ATM1/1/147.0091.8100.0000.0041.0b0a.1081.4000.0c80.9020.00 ATM1/1/247.0091.8100.0000.0041.0b0a.1081.4000.0c80.9030.00 ATM1/1/3ILMI Switch Prefix(es):47.0091.8100.0000.0041.0b0a.108147.0091.8100.0000.0060.3e5a.db01ILMI Configured Interface Prefix(es):LECS Address(es):Configuring Static Routes
Use the atm route command to configure a static route. A static route attached to an interface allows all ATM addresses matching the configured address prefix to be reached through that interface.
Note
To configure a static route, use the following global configuration command:
Examples
The following example uses the atm route command to configure a static route to the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0:
Switch(config)# atm route 47.0091.8100.0000.0041.0B0A.1081 atm 0/0/0The following example uses the atm route command to configure a static route to the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0 configured with a scope 1 associated:
Switch(config)# atm route 47.0091.8100.0000.0041.0B0A.1081 atm 0/0/0 scope 1Displaying the Static Route Configuration
To display the ATM static route configuration, use the following EXEC command:
Examples
The following example shows the ATM static route configuration using the show atm route privileged EXEC command:
Switch# show atm routeCodes: P - installing Protocol (S - Static, P - PNNI, R - Routing control),T - Type (I - Internal prefix, E - Exterior prefix, SE -Summary Exterior prefix, SI - Summary Internal prefix,ZE - Suppress Summary Exterior, ZI - Suppress Summary Internal)P T Node/Port St Lev Prefix~ ~~ ~~~~~~~~~~~~~~~~ ~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~S E 1 ATM0/0/0 DN 56 47.0091.8100.0000/56S E 1 ATM0/0/0 DN 0 47.0091.8100.0000.00/64(E164 Address 1234567)R SI 1 0 UP 0 47.0091.8100.0000.0041.0b0a.1081/104R I 1 ATM0 UP 0 47.0091.8100.0000.0041.0b0a.1081.0041.0b0a.1081/152R I 1 ATM0 UP 0 47.0091.8100.0000.0041.0b0a.1081.4000.0c/128R SI 1 0 UP 0 47.0091.8100.5670.0000.0000.0000/104R I 1 ATM0 UP 0 47.0091.8100.5670.0000.0000.0000.0040.0b0a.1081/152R I 1 ATM0 UP 0 47.0091.8100.5670.0000.0000.0000.4000.0c/128Configuring ATM Address Groups
ATM address groups allow more than one interface to have the same internal address prefix for the same static route. These multiple static routes provide load balancing for traffic from an end station.
Configure the interfaces in a group by performing the following tasks, beginning in global configuration mode:
Example
The following example shows how to configure ATM interface 1/1/0 and ATM interface 3/0/1 in ATM address group 5:
Switch(config)# interface atm 1/1/0Switch(config-if)# atm interface-group 5Switch(config-if)# exitSwitch(config)# interface atm 3/0/1Switch(config-if)# atm interface-group 5Displaying ATM Address Group Configuration
To determine if an interface is a member of an ATM address group, use the following privileged EXEC command:
show running-config interface atm card/subcard/port
Shows the ILMI configuration on a per-port basis.
Example
The following example shows the ATM address group configuration for ATM interface 1/1/0 and ATM interface 3/0/1:
Switch# show running-config interface atm 1/1/0Building configuration...Current configuration:!no ip addressno ip directed-broadcastno atm ilmi-keepaliveatm prefix 47.0091.8100.5670.0000.0000.1122...clock source free-runningendSwitch# show running-config interface atm 3/0/1Building configuration...Current configuration:!no ip addressno ip directed-broadcastno atm ilmi-keepaliveatm prefix 47.0091.8100.5670.0000.0000.1122...clock source free-runningendBasic PNNI Configuration
This section describes all the procedures necessary for a basic PNNI configuration and includes the following subsections:
•
•
•
Configuring PNNI without Hierarchy
The ATM switch router defaults to a working PNNI configuration suitable for operation in isolated flat topology ATM networks. The switch comes with a globally unique preconfigured ATM address. Manual configuration is not required if you:
•
•
•
If you plan to migrate your flat network topology to a PNNI hierarchical topology, proceed to the next section "Configuring the Lowest Level of the PNNI Hierarchy."
Configuring the Lowest Level of the PNNI Hierarchy
This section describes how to configure the lowest level of the PNNI hierarchy. The lowest-level nodes comprise the lowest level of the PNNI hierarchy. When only the lowest-level nodes are configured, there is no hierarchical structure. If your network is relatively small and you want the benefits of PNNI, but do not need the benefits of a hierarchical structure, follow the procedures in this section to configure the lowest level of the PNNI hierarchy.
To implement multiple levels of PNNI hierarchy, first complete the procedures in this section and then proceed to Configuring Higher Levels of the PNNI Hierarchy.
Configuring an ATM Address and PNNI Node Level
The ATM switch router is preconfigured as a single lowest-level PNNI node (locally identified as node 1) with a level of 56. The node ID and peer group ID are calculated based on the current active ATM address.
Note
To configure a node in a higher level of the PNNI hierarchy, the value of the node level must be a smaller number. For example, a three-level hierarchical network could progress from level 72 to level 64 to level 56. Notice that the level numbers graduate from largest at the lowest level (72) to smallest at the highest level (56).
To change the active ATM address you must create a new address, verify that it exists, and then delete the current active address. After you have entered the new ATM address, disable node 1 and then reenable it. At the same time, you can change the node level if required for your configuration. The identifiers for all higher level nodes are recalculated based on the new ATM address.
Caution
To change the active ATM address, perform these steps, beginning in global configuration mode:
Example
The following example changes the ATM address of the switch from the autoconfigured address 47.0091.8100.0000.0041.0b0a.1081.0041.0b0a.1081.00 to the new address prefix 47.0091.8100.5670.0000.0000.1122.0041.0b0a.1081.00, and causes the node identifier and peer group identifier to be recalculated:
Switch(config)# atm address 47.0091.8100.5670.0000.0000.1122...Switch(config)# no atm address 47.0091.8100.0000.0041.0b0a.1081...Switch(config)# atm router pnniSwitch(config-atm-router)# node 1 disableSwitch(config-pnni-node)# node 1 enableDisplaying the PNNI Node Configuration
To display the ATM PNNI node configuration, use the following privileged EXEC command:
Example
The following example shows the PNNI node configuration using the show atm pnni local-node privileged EXEC command:
Switch# show atm pnni local-nodePNNI node 1 is enabled and runningNode name: eng_1System address 47.0091810000000002EB1FFE00.0002EB1FFE00.01Node ID 56:160:47.0091810000000002EB1FFE00.0002EB1FFE00.00Peer group ID 56:160:47.0000.0000.0000.0000.0000Level 56, Priority 0 0, No. of interfaces 1, No. of neighbors 0Parent Node Index: 2Node Allows Transit CallsNode Representation: simpleHello interval 15 sec, inactivity factor 5,Hello hold-down 10 tenths of secAck-delay 10 tenths of sec, retransmit interval 5 sec,Resource poll interval 5 secSVCC integrity times: calling 35 sec, called 50 sec,Horizontal Link inactivity time 120 sec,PTSE refresh interval 1800 sec, lifetime factor 200 percent,Min PTSE interval 10 tenths of secAuto summarization: on, Supported PNNI versions: newest 1, oldest 1Default administrative weight mode: uniformMax admin weight percentage: -1Next resource poll in 3 secondsMax PTSEs requested per PTSE request packet: 32Redistributing static routes: YesConfiguring Static Routes
Because PNNI is a dynamic routing protocol, static routes are not necessary between nodes that support PNNI. However, you can extend the routing capability of PNNI beyond nodes that support PNNI to:
•
•
Use the atm route command to configure a static route. A static route attached to an interface allows all ATM addresses matching the configured address prefix to be reached through that interface.
Note
To configure a static route connection, use the following global configuration command:
atm route addr-prefix atm card/subcard/port [e164-address address-string [number-type numtype]] [internal] [scope org-scope]
Specifies a static route to a reachable address prefix.
Examples
The following example uses the atm route command to configure a static route to the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0:
Switch(config)# atm route 47.0091.8100.0000.0041.0B0A.1081 atm 0/0/0The following example uses the atm route command to configure a static route to the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0 configured with a scope 1 associated:
Switch(config)# atm route 47.0091.8100.0000.0041.0B0A.1081 atm 0/0/0 scope 1Displaying the Static Route Configuration
To display the ATM static route configuration, use the following EXEC command:
Example
The following example shows the ATM static route configuration using the show atm route EXEC command:
Switch# show atm routeCodes: P - installing Protocol (S - Static, P - PNNI, R - Routing control),T - Type (I - Internal prefix, E - Exterior prefix, SE -Summary Exterior prefix, SI - Summary Internal prefix,ZE - Suppress Summary Exterior, ZI - Suppress Summary Internal)P T Node/Port St Lev Prefix~ ~~ ~~~~~~~~~~~~~~~~ ~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~S E 1 ATM0/0/0 DN 56 47.0091.8100.0000/56S E 1 ATM0/0/0 DN 0 47.0091.8100.0000.00/64(E164 Address 1234567)R SI 1 0 UP 0 47.0091.8100.0000.0041.0b0a.1081/104R I 1 ATM0 UP 0 47.0091.8100.0000.0041.0b0a.1081.0041.0b0a.1081/152R I 1 ATM0 UP 0 47.0091.8100.0000.0041.0b0a.1081.4000.0c/128R SI 1 0 UP 0 47.0091.8100.5670.0000.0000.0000/104R I 1 ATM0 UP 0 47.0091.8100.5670.0000.0000.0000.0040.0b0a.1081/152R I 1 ATM0 UP 0 47.0091.8100.5670.0000.0000.0000.4000.0c/128Configuring a Summary Address
You can configure summary addresses to reduce the amount of information advertised by a PNNI node and contribute to scalability in large networks. Each summary address consists of a single reachable address prefix that represents a collection of end system or node addresses. We recommend that you use summary addresses when all end system addresses that match the summary address are directly reachable from the node. However, this is not always required because routes are always selected by nodes advertising the longest matching prefix to a destination address.
By default, each lowest-level node has a summary address equal to the 13-byte address prefix of the ATM address of the switch. This address prefix is advertised into its peer group.
You can configure multiple addresses for a single switch which are used during ATM address migration. ILMI registers end systems with multiple prefixes during this period until an old address is removed. PNNI automatically creates 13-byte summary address prefixes from all of its ATM addresses.
You must configure summary addresses (other than the defaults) on each node. Each node can have multiple summary address prefixes. Use the summary-address command to manually configure summary address prefixes.
Note
To configure a summary address, perform these steps, beginning in global configuration mode:
Example
The following example shows how to remove the default summary address(es) and add summary address 47.009181005670:
Switch(config)# atm router pnniSwitch(config-atm-router)# node 1Switch(config-pnni-node)# no auto-summarySwitch(config-pnni-node)# summary-address 47.009181005670Displaying the Summary Address Configuration
To display the ATM PNNI summary address configuration, use the following privileged EXEC command:
Example
The following example shows the ATM PNNI summary address configuration using the show atm pnni summary privileged EXEC command:
Switch# show atm pnni summaryCodes: Node - Node index advertising this summaryType - Summary type (INT - internal, EXT - exterior)Sup - Suppressed flag (Y - Yes, N - No)Auto - Auto Summary flag (Y - Yes, N - No)Adv - Advertised flag (Y - Yes, N - No)Node Type Sup Auto Adv Summary Prefix~~~~ ~~~~ ~~~ ~~~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 Int N Y Y 47.0091.8100.0000.0040.0b0a.2a81/1042 Int N Y N 47.01b1.0000.0000.0000.00/80Configuring Scope Mapping
The PNNI address scope allows you to restrict advertised reachability information within configurable boundaries.
Note
In PNNI networks, the scope is specified in terms of PNNI levels. The mapping from organizational scope values used at UNI and IISP interfaces to PNNI levels is configured on the lowest-level node. The mapping can be determined automatically (which is the default setting) or manually, depending on the configuration of the scope mode command.
In manual mode, whenever the level of node 1 is modified, the scope map should be reconfigured to avoid unintended suppression of reachability advertisements. Misconfiguration of the scope map might cause addresses to remain unadvertised.
In automatic mode, the UNI to PNNI level mapping is automatically reconfigured whenever the level of the node 1 is modified. The automatic reconfiguration avoids misconfigurations caused by node level modifications. Automatic adjustment of scope mapping uses the values shown in Table 10-1.
Entering the scope mode automatic command ensures that all organizational scope values cover an area at least as wide as the current node's peer group. Configuring the scope mode to manual disables this feature and no changes can be made without explicit configuration.
To configure the PNNI scope mapping, perform these steps, beginning in global configuration mode:
Step 1
Switch(config)# atm router pnni
Switch(config-atm-router)#
Enters ATM router PNNI mode.
Step 2
Switch(config-atm-router)# node node-index
Switch(config-pnni-node)#
Enters node configuration mode.
Step 3
Switch(config-pnni-node)# scope mode manual
Configures scope mode as manual.1
Step 4
Switch(config-pnni-node)# scope map low-org-scope [high-org-scope] level number
Configures node scope mapping.
1 You must enter the scope mode manual command to allow scope mapping configuration.
Example
The following example shows how to configure PNNI scope mapping manually so that organizational scope values 1 through 8 map to PNNI level 72:
Switch(config)# atm router pnniSwitch(config-atm-router)# node 1Switch(config-pnni-node)# scope mode manualSwitch(config-pnni-node)# scope map 1 8 level 72Displaying the Scope Mapping Configuration
To display the PNNI scope mapping configuration, use the following privileged EXEC command:
Example
The following example shows the ATM PNNI scope mapping configuration using the show atm pnni scope privileged EXEC command:
Switch# show atm pnni scopeUNI scope PNNI Level~~~~~~~~~ ~~~~~~~~~~(1 - 10) 56(11 - 12) 48(13 - 14) 32(15 - 15) 0Scope mode: manualConfiguring Higher Levels of the PNNI Hierarchy
Once you have configured the lowest level of the PNNI hierarchy, you can configure the higher levels. To do so, you must configure peer group leaders (PGLs) and logical group nodes (LGNs).
For an explanation of PGLs and LGNs, as well as guidelines for creating a PNNI hierarchy, refer to the Guide to ATM Technology.
Configuring a Logical Group Node and Peer Group Identifier
The LGN is created only when the child node in the same switch (that is, the node whose parent configuration points to this node) is elected PGL of the child peer group.
The peer group identifier defaults to a value created from the first part of the child peer group identifier, and does not need to be specified. If you want a nondefault peer group identifier, you must configure all logical nodes within a peer group with the same peer group identifier.
Higher level nodes are only active if:
•
•
To configure a LGN and peer group identifier, perform these steps, beginning in global configuration mode:
Examples
The following example shows how to create a new node 2 with a level of 56 and a peer group identifier of 56:47009111223344:
Switch(config)# atm router pnniSwitch(config-atm-router)# node 2 level 56 peer-group-identifier 56:47009111223344 enableSwitch(config-pnni-node)# endNotice that the PNNI level and the first two digits of the peer group identifier are the same.
Displaying the Logical Group Node Configuration
To display the LGN configuration, use the following privileged EXEC command:
Example
The following example shows the PNNI node information using the show atm pnni local-node privileged EXEC command:
Switch# show atm pnni local-node 2PNNI node 2 is enabled and not runningNode name: Switch.2.56System address 47.009181000000000000000001.000000000001.02Node ID 56:0:00.000000000000000000000000.000000000001.00Peer group ID 56:47.0091.1122.3344.0000.0000.0000Level 56, Priority 0 0, No. of interfaces 0, No. of neighbors 0Parent Node Index: NONENode Allows Transit CallsNode Representation: simpleHello interval 15 sec, inactivity factor 5,Hello hold-down 10 tenths of secAck-delay 10 tenths of sec, retransmit interval 5 sec,Resource poll interval 5 secSVCC integrity times: calling 35 sec, called 50 sec,Horizontal Link inactivity time 120 sec,PTSE refresh interval 1800 sec, lifetime factor 200 percent,Min PTSE interval 10 tenths of secAuto summarization: on, Supported PNNI versions: newest 1, oldest 1Default administrative weight mode: uniformMax admin weight percentage: -1Max PTSEs requested per PTSE request packet: 32Redistributing static routes: NoConfiguring the Node Name
PNNI node names default to names based on the host name. However, you can change the default node name to more accurately reflect the peer group. We recommend you chose a node name of 12 characters or less so that your screen displays remain nicely formatted and easy to read.
After a node name has been configured, it is distributed to all other nodes by PNNI flooding. This allows the node to be identified by its node name in PNNI show commands.
Note
To configure the PNNI node name, perform these steps, beginning in global configuration mode:
Example
Configure the name of the node as eng_1 using the name command, as in the following example:
Switch(config)# atm router pnniSwitch(config-atm-router)# node 1Switch(config-pnni-node)# name eng_1Displaying the Node Name Configuration
To display the ATM PNNI node name configuration, use the following privileged EXEC command:
Example
This example shows how to display the ATM node name configuration using the show atm pnni local-node command from user EXEC mode:
Switch# show atm pnni local-nodePNNI node 1 is enabled and runningSystem address 47.0091810000000002EB1FFE00.0002EB1FFE00.01Node ID 56:160:47.0091810000000002EB1FFE00.0002EB1FFE00.00Peer group ID 56:16.0347.0000.0000.0000.0000.0000Level 56, Priority 0 0, No. of interfaces 1, No. of neighbors 0Parent Node Index: 2Node Allows Transit CallsNode Representation: simpleHello interval 15 sec, inactivity factor 5,Hello hold-down 10 tenths of secAck-delay 10 tenths of sec, retransmit interval 5 sec,Resource poll interval 5 secSVCC integrity times: calling 35 sec, called 50 sec,Horizontal Link inactivity time 120 sec,PTSE refresh interval 1800 sec, lifetime factor 200 percent,Min PTSE interval 10 tenths of secAuto summarization: on, Supported PNNI versions: newest 1, oldest 1Default administrative weight mode: uniformMax admin weight percentage: -1Next resource poll in 3 secondsMax PTSEs requested per PTSE request packet: 32Redistributing static routes: YesConfiguring a Parent Node
For a node to be eligible to become a PGL within its own peer group, you must configure a parent node and a nonzero election leadership level (described in the following section, " Configuring the Node Election Leadership Priority"). If the node is elected a PGL, the node specified by the parent command becomes the parent node and represents the peer group at the next hierarchical level.
To configure a parent node, perform these steps, beginning in global configuration mode:
Example
The following example shows how to create a parent node for node 1:
Switch(config)# atm router pnniSwitch(config-pnni-node)# node 1Switch(config-pnni-node)# parent 2Displaying the Parent Node Configuration
To display the parent node configuration, use the following privileged EXEC command:
Example
The following example shows the ATM parent node information using the show atm pnni hierarchy privileged EXEC command:
Switch# show atm pnni hierarchyLocally configured parent nodes:Node ParentIndex Level Index Local-node Status Node Name~~~~~ ~~~~~ ~~~~~~ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~1 80 2 Enabled/ Running Switch2 72 N/A Enabled/ Running Switch.2.72Configuring the Node Election Leadership Priority
Normally the node with the highest election leadership priority is elected PGL. If two nodes share the same election priority, the node with the highest node identifier becomes the PGL. To be eligible for election the configured priority must be greater than zero. You can configure multiple nodes in a peer group with nonzero leadership priority so that if one PGL becomes unreachable, the node configured with the next highest election leadership priority becomes the new PGL.
Note
The control for election is done through the assignment of leadership priorities. We recommend that the leadership priority space be divided into three tiers:
•
•
•
This subdivision is used because when a node becomes PGL, it increases the advertised leadership priority by a value of 50. This avoids instabilities after election.
The following guidelines apply when configuring the node election leadership priority:
•
•
•
•
Note
To configure the election leadership priority, perform these steps, beginning in global configuration mode:
Example
The following example shows how to change the election leadership priority for node 1 to 100:
Switch(config)# atm router pnniSwitch(config-pnni-node)# node 1Switch(config-pnni-node)# election leadership-priority 100Displaying Node Election Leadership Priority
To display the node election leadership priority, use one of the following privileged EXEC commands:
show atm pnni election
Displays the node election leadership priority.
show atm pnni election peers
Displays all nodes in the peer group.
Examples
The following example shows the election leadership priority using the show atm pnni election privileged EXEC command:
Switch# show atm pnni electionPGL Status.............: PGLPreferred PGL..........: (1) SwitchPreferred PGL Priority.: 255Active PGL.............: (1) SwitchActive PGL Priority....: 255Active PGL For.........: 00:01:07Current FSM State......: PGLE Operating: PGLLast FSM State.........: PGLE Awaiting UnanimityLast FSM Event.........: Unanimous VoteConfigured Priority....: 205Advertised Priority....: 255Conf. Parent Node Index: 2PGL Init Interval......: 15 secsSearch Peer Interval...: 75 secsRe-election Interval...: 15 secsOverride Delay.........: 30 secsThe following example shows all nodes in the peer group using the show atm pnni election peers command:
Switch# show atm pnni election peersNode No. Priority Connected Preferred PGL~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~1 255 Yes Switch9 0 Yes Switch10 0 Yes Switch11 0 Yes Switch12 0 Yes SwitchConfiguring a Summary Address
Summary addresses can be used to decrease the amount of information advertised by a PNNI node. Summary addresses should only be used when all end system addresses that match the summary address are directly reachable from this node. However, this is not always required because routes are always selec
