Table Of Contents

Managing PNNI Nodes and PNNI Routing

Managing PNNI Nodes

Creating Upper Level Peer Groups

Enabling and Disabling Routes Through a Node

Enabling and Disabling Point-to-Multipoint Routes

Adding an ATM Summary Address Prefix

Configuring SVCC RCC Variables

Configuring Routing Policies for Background Routing Tables

Configuring PNNI Timers

Managing PNNI Route and Link Selection

Configuring the Route Selection Method (First Fit or Best Fit)

Configuring the Best-Fit Route Selection Method

Configuring Preferred Routes

Maintaining the Network Node Table

Creating a Preferred Route

Modifying a Preferred Route

Deleting a Preferred Route

Deleting a Node from the Network Node Table

Configuring Link Selection for Parallel Links

Configuring the Maximum Bandwidth for a Link

Configuring the Administrative Weight

Configuring the Bandwidth Overbooking Factor

Improving and Managing Rerouting Performance

Pure PXM45/C Networks

Hybrid Networks with PXM45/C and PXM45/B

Pure PXM45/B Networks Running Version 3.0.10 or Later

Hybrid Networks with PXM45/C and PXM45/A

Displaying Node Configuration Information

Displaying the PNNI Node Table

Displaying the PNNI Summary Address

Displaying System Addresses

Displaying PNNI Interface Parameters

Displaying the PNNI Link Table

Displaying the PNNI Routing Policy

Displaying the SVCC RCC Timer

Displaying Routing Policy Parameters

Displaying the SVCC RCC Table

Managing CUGs

Assigning Address Prefixes and AESAs

Creating Closed User Groups

Displaying CUG Configuration Data

Setting a Default Address for CUG Validation

Deleting a Default CUG Address

Managing Access Between Users in the Same CUG

Managing Access Between a CUG Member and Non-Members or Members of other CUGS

Deleting a CUG Assignment

Blocking the CUG IE

Maintaining a Persistent Network Topology in CWM

Configuring a Gateway Node

Displaying the Network Topology Database

Displaying Link Information

Displaying Feeder Information

Disabling a Gateway Node

Deleting a Node from the Topology Database

Deleting a Link from the Topology Database

Managing PNNI Nodes and PNNI Routing

---

This chapter provides procedures that you can use to manage Private Network-to-Network Interface (PNNI) nodes and routes. This chapter includes the following sections:

•Managing PNNI Nodes

•Managing PNNI Route and Link Selection

•Displaying Node Configuration Information

•Managing CUGs

•Maintaining a Persistent Network Topology in CWM

---

Note The concepts behind the procedures in this chapter are introduced in the PNNI Network Planning Guide for MGX and SES Products.

---

Managing PNNI Nodes

The following sections describe how to configure upper level peer groups and how to manage the PNNI node.

Creating Upper Level Peer Groups

Upper level peer groups enable routing from one PNNI peer group to another. If you are managing a single peer group WAN, you do not need to create upper level peer groups.

---

Note The "Configuring PNNI Node Parameters" section in Chapter 3, "Configuring General Switch Features," describes how to configure the lowest level peer group parameters, which many upper level peer group parameters are based on. You should configure the basic PNNI node parameters before creating upper level peer groups.

---

After you configure the lowest level PNNI nodes, all nodes within the same peer group can communicate with each other. All you need to do to enable communications between two nodes in a peer group is to add a PNNI trunk between them as described in the "ATM Trunk Configuration Quickstart" section in Chapter 11, "Provisioning PXM1E Communication Links." To enable routing between different peer groups at the same level, you must create one or more upper level peer groups.

The actual procedure for creating an upper level peer group for your WAN depends on the structure of your WAN. This section shows how to create an upper level peer group for the WAN shown in Figure 12-1.

Figure 12-1 Example Hierarchical PNNI Network Topology Showing a Two-Level Hierarchy

In Figure 12-1, the five level-56 peer groups are isolated from each other until the upper level peer group is created. The members of the upper level peer group are the peer group leaders from the lower level peer groups. To create an upper level peer group, you need to configure the peer group leaders and add the upper level PNNI process to each peer group leader (PGL) node. It is also a good practice to configure secondary peer group leaders that can take over if a PGL fails.

To configure peer group leaders, use the following procedure.

---

Step 1 Establish a configuration session using a user name with SUPER_GP privileges or higher.

Add the upper level PNNI logical node that will participate in the higher level PNNI group using the addpnni-node <level> command.

Replace level with the PNNI level for the higher level peer group. The PNNI level value must be smaller than the level value for the lower level peer groups. The following example creates a logical PNNI node at PNNI level 48.

mgx8830a.1.PXM.a > addpnni-node 48

---

Note You need to complete this step for all nodes that will serve as PGLs or backup PGLs.

---

Step 2 Display the current PGL priority of the node that will become PGL or a back up PGL by entering the dsppnni-election command as shown in the following example:

mgx8830a.1.PXM.a >  dsppnni-election

node index: 1

   PGL state......     OperNotPgl     Init timeliest).......        15

   Priority.......              0     Override delay(sec)..        30

                                      Re-election time(sec)        15

   Pref PGL...............0:0:00.000000000000000000000000.000000000000.00

   PGL....................0:0:00.000000000000000000000000.000000000000.00

   Active parent node id..0:0:00.000000000000000000000000.000000000000.00

In the example above, the PGL state indicates the PGL status of each of two logical nodes, and the priority value is what is used to determine if the node will become PGL. Since a PGL represents the peer group at a higher level, logical node 1 (node index 1) is the only node that can become a PGL. In this example, both logical nodes are set to the default value 0, and this value prevents a node from becoming a peer group leader.

Step 3 Set the PNNI priority for the node with the cnfpnni-election command as follows:

mgx8830a.1.PXM.a > cnfpnni-election node-index -priority value

Replace node-index with the index that identifies the logical node you are modifying, and replace value with the new priority value. A zero value prevents the node from becoming a PGL. If only one node in a peer group has a non-zero priority, that node will become PGL. If multiple nodes have non-zero priority values, the node with the highest priority value becomes PGL. The following example shows what happens after you set the priority level and view the PGL status.

mgx8830a.1.PXM.a > cnfpnni-election 1 -priority 200

mgx8830a.1.PXM.a > dsppnni-election              

node index: 1

   PGL state...... AwaitUnanimity     Init time(sec).......        15

   Priority.......            200     Override delay(sec)..        30

                                      Re-election time(sec)        15

   Pref PGL...............56:160:47.00918100000100036b5e31b3.00036b5e31b3.01

   PGL....................0:0:00.000000000000000000000000.000000000000.00

   Active parent node id..0:0:00.000000000000000000000000.000000000000.00

node index: 2

   PGL state......       Starting     Init time(sec).......        15

   Priority.......              0     Override delay(sec)..        30

                                      Re-election time(sec)        15

   Pref PGL...............0:0:00.000000000000000000000000.000000000000.00

   PGL....................0:0:00.000000000000000000000000.000000000000.00

   Active parent node id..0:0:00.000000000000000000000000.000000000000.00

The first time the dsppnni-election command was entered, the PGL state was OperNotPgl, which means that the node is operating, but is not operating as a PGL. After the priority is changed, the PGL state changes to AwaitUnanimity, which means the node is communicating with the other nodes in its peer group to see if it has the highest priority and should be PGL. If you enter the dsppnni-election command again after about 15 seconds, the PGL state changes as shown in the following example:

mgx8830a.1.PXM.a > dsppnni-election

node index: 1

   PGL state......        OperPgl     Init time(sec).......        15

   Priority.......            250     Override delay(sec)..        30

                                      Re-election time(sec)        15

   Pref PGL...............56:160:47.00918100000100036b5e31b3.00036b5e31b3.01

   PGL....................56:160:47.00918100000100036b5e31b3.00036b5e31b3.01

   Active parent node id..48:56:47.009181000001000000000000.00036b5e31b3.00

node index: 2

   PGL state......     OperNotPgl     Init time(sec).......        15

   Priority.......              0     Override delay(sec)..        30

                                      Re-election time(sec)        15

   Pref PGL...............0:0:00.000000000000000000000000.000000000000.00

   PGL....................0:0:00.000000000000000000000000.000000000000.00

   Active parent node id..0:0:00.000000000000000000000000.000000000000.00

In the example above, the PGL state changes to show that logical node 1 is now the PGL. Notice that the priority value is 250. An earlier example in this procedure set the priority to 200. When a node is elected PGL, the node adds 50 to its priority value to prevent instability that might be caused by other peer group nodes with a marginally higher priority value.

Step 4 Repeat this procedure for backup peer group leaders and be sure to set their priority value to a lower value so that they operate as backup PGLs.

---

Enabling and Disabling Routes Through a Node

The restricted transit option allows you to allow or block call routes that pass through the node and terminate on other nodes. The default setting for this option enables calls to pass through.

To enable or disable PNNI routing through a node, enter the cnfpnni-node command as follows:

mgx8830a.1.PXM.a > cnfpnni-node <node-index > -transitRestricted on|off

Replace node-index with the index that identifies the logical node you are modifying, and enter either on or off for the -transitRestricted parameter. When this parameter is set to on, the node only accepts calls that terminate on this node. When the -transitRestricted parameter is set to off, the node accepts calls that pass through the node and terminate on other nodes.

To view the status of the -transitRestricted option, enter the dsppnni-node command as shown in the following example:

mgx8830a.1.PXM.a >  dsppnni-node

node index: 1                      node name: 8850_LA        

   Level...............        56     Lowest..............      true

   Restricted transit..        on     Complex node........       off

   Branching restricted        on

   Admin status........        up     Operational status..        up

   Non-transit for PGL election..       off

   Node id...............56:160:47.00918100000100001a531c2a.00001a531c2a.01

   ATM address...........47.00918100000100001a531c2a.00001a531c2a.01

   Peer group id.........56:47.00.9181.0000.0100.0000.0000.00

Enabling and Disabling Point-to-Multipoint Routes

The branching restricted option allows you to allow or block point-to-multipoint calls. The default setting for this option enables point-to-multipoint calls.

To enable or disable point-to-multipoint routes through a node, enter the cnfpnni-node command as follows:

mgx8830a.1.PXM.a > cnfpnni-node <node-index > -branchingRestricted on|off

Replace node-index with the index that identifies the logical node you are modifying, and enter either on or off for the -branchingRestricted parameter. When this parameter is set to on, the node does not accept point-to-multipoint calls. When the -branchingRestricted parameter is set to off, the node accepts point-to-multipoint calls.

To view the status of the -branchingRestricted option, enter the dsppnni-node command as shown in the following example:

mgx8830a.1.PXM.a >  dsppnni-node

node index: 1                      node name: 8850_LA        

   Level...............        56     Lowest..............      true

   Restricted transit..       off     Complex node........       off

   Branching restricted        on

   Admin status........        up     Operational status..        up

   Non-transit for PGL election..       off

   Node id...............56:160:47.00918100000100001a531c2a.00001a531c2a.01

   ATM address...........47.00918100000100001a531c2a.00001a531c2a.01

   Peer group id.........56:47.00.9181.0000.0100.0000.0000.00

Adding an ATM Summary Address Prefix

Enter the addpnni-summary-addr command to add an ATM summary address prefix for a PNNI logical node on the switch.

mgx8830a.1.PXM.a > addpnni-summary-addr <node-index> <address-prefix> <prefix-length> [-type] 
[-suppress] [-state]

Table 12-1 lists the parameter descriptions for the addpnni-summary-addr command.

Table 12-1 Parameters for addpnni-summary-addr Command

Parameter	Description
node-index	The node index assigned to a PNNI logical node on a network. Range = 1 - 65535
address-prefix	The ATM address prefix assigned to the network.
prefix-length	The length of the summary address-prefix in number of bits, equal or less than 152 bits. Currently, the zero-length summary address is not supported.
-type	The type of the summary address.
-suppress	true = summary address is not advertised.
-state	The summary address is advertised | notadvertised | inactive.

Configuring SVCC RCC Variables

Configure SVCC-based RCC variables with the cnfpnni-svcc-rcc-timer command as follows:

mgx8830a.1.PXM.a > cnfpnni-svcc-rcc-timer <node-index> [-initTime] [-retryTime] 
[-callingIntegrityTime] [-calledIntegrityTime] 

This defines a node's initial PNNI SVCC-based variables, as shown in Table 12-2.

Table 12-2 Parameters for cnfpnni-svcc-rcc-timer Command

Parameter	Description
node-index	Node index.
-initTime	Time (in seconds) that the node delays establishment of an SVCC to a neighbor with a numerically lower ATM address, after determining that such an SVCC should be established.
-retryTime	Time (in seconds) that the node delays before attempting to re-establish an SVCC-based RCC after the RCC is unexpectedly torn down.
-callingIntegrityTime	Time (in seconds) that the node waits for a sent SVCC to become fully established before giving up and tearing it down.
-calledIntegrityTime	Time (in seconds) that the node waits for a received SVCC to become fully established before giving up and tearing it down.

Configuring Routing Policies for Background Routing Tables

Configure the routing policies used for background routing tables generation with the cnfpnni-routing-policy command as follows:

mgx8830a.1.PXM.a > cnfpnni-routing-policy [-sptEpsilon] [-sptHolddown] [-bnPathHolddown] 
[-loadBalance] [-onDemand] [-awBgTable] [-ctdBgTable] [-cdvBgTable]

Table 12-3 lists the parameter descriptions for the cnfpnni-routing-policy command.

Table 12-3 Parameters for cnfpnni-routing-policy Command 

Parameter	Description
-sptEpsilon	Indicates the node's policy in determining equal-cost path during routes calculation.
-sptHolddown	Defines the node's minimum time interval between two consecutive calculations for generating routing tables.
-bnPathHolddown	Defines the minimum time interval between two consecutive calculations for generating border node path in a peer group for a complex node representation at the next higher level. (Complex nodes are not supported by MGX 8850, Release 2.1 software image.)
-loadBalance	Defines the node's load balancing rule if alternative equal-lose routes exist for the call request.
-onDemand	Defines the node's on-demand routing rule, either to: firstfit = select the first route found bestfit = select the best route Default = firstfit
-awBgTable	Enable or disable administrative weight for the background routing table. Default = off
-ctdBgTable	Enable or disable CTD for the background routing table. Default = off
-cdvBgTable	Enable or disable CDV for the background routing table. Default = off

Configuring PNNI Timers

Configure the PNNI timers with the cnfpnni-timer command.

mgx8830a.1.PXM.a >  cnfpnni-timer <node-index> <options>

You can define the initial PNNI timer values and significant change thresholds of a PNNI logical node. Table 12-4 lists the parameter descriptions for the cnfpnni-timer command.

Table 12-4 Parameters for cnfpnni-timer Command

Parameter	Description
nodeindex	Logical node's node index.
-ptseholddown	The number is used as a multiplier of the Hello interval of the peer neighbor: the product is the maximum time that the neighbor is considered to be alive without the reception of its Hello packets. Range: (0.1 through 10) second Default = 1
-helloholddown	Value for the Hello hold down timer that limits the rate at which it sends Hellos.
-hellointerval	Initial value for the Hello timer.
-helloinactivityfactor	Inactivity time factor on a horizontal link between two logical nodes.
-ptserefreshinterval	Time allowed for the PTSE to re-originate.
-ptselifetimefactor	Value for the lifetime multiplier, expressed as a percentage. The product of this value and the ptserefreshinterval is sets the remaining lifetime of a self-originated PTSE.
-retransmitinterval	Period between retransmissions of unacknowledged DS, PTSE request, and PTSP.
-ptsedelayedackinterval	Minimum time allowed between transmissions of delayed PTSE acknowledgment packets.
-avcrpm	Proportional multiplier used in the algorithms that determines significant change for AvCR parameters.
-avcrmt	Minimum threshold used in the algorithms that determine significant change for AvCR parameters.
-cdvpm	Proportional multiplier used in the algorithms that determine significant change for CDV parameters.
-ctdpm	Proportional multiplier used in the algorithms that determine significant change for CTD parameters.

Managing PNNI Route and Link Selection

The following sections describe how to control route and link selection for the links on each PNNI node.

Configuring the Route Selection Method (First Fit or Best Fit)

When the PNNI controller searches for routes, it can choose the first route that meets the call requirements, or it can choose the route that provides the best performance. The first fit method chooses the first available route and reduces call processing time. The best fit method chooses the optimum route, but it takes longer to select the route. The default setting is first fit.

---

Note The route selection process is described in the PNNI Network Planning Guide for MGX and SES Products.

---

To configure the route selection method, enter the cnfpnni-routing-policy command as follows:

mgx8830a.1.PXM.a > cnfpnni-routing-policy -onDemand firstfit|bestfit

Enter firstfit to select the first route discovered, or enter bestfit to select the optimum route.

To display the route selection method, enter the dsppnni-routing-policy command as follows:

mgx8830a.1.PXM.a > dsppnni-routing-policy

   SPT epsilon.........         0     Load balance........    random

   SPT holddown time...         1     On demand routing... first fit

   SPT path holddown time       2     AW Background Table         on

   CTD Background Table        on     CDV Background Table        on 

The parameter labeled On demand routing shows which route selection method is configured.

Configuring the Best-Fit Route Selection Method

When the PNNI controller is configured to choose the best route and it discovers multiple eligible routes, the load balancing option determines which route to select. The option settings are random and maxbw, which selects the route with the greatest available bandwidth. Random selection is used to balance the load.

---

Note The route selection process is described in the PNNI Network Planning Guide for MGX and SES Products.

---

To configure the best-fit route selection method, use the cnfpnni-routing-policy command as follows:

mgx8830a.1.PXM.a > cnfpnni-routing-policy -loadBalance random|maxbw

Enter random to balance route selection, or enter maxbw to select the route with the greatest available bandwidth.

To display the route selection method, enter the dsppnni-routing-policy command as follows:

mgx8830a.1.PXM.a > dsppnni-routing-policy

   SPT epsilon.........         0     Load balance........    random

   SPT holddown time...         1     On demand routing... first fit

   SPT path holddown time       2     AW Background Table         on

   CTD Background Table        on     CDV Background Table        on 

The parameter labeled Load balance shows which best-fit route selection method is configured.

Configuring Preferred Routes

You can manually create a route that is preferred for specific SPVC and SPVP connections. Once a preferred route is created, the associated SPVC or SPVP connections will attempt to route via the preferred route before attempting other routes.

---

Note A preferred route can be assigned to multiple SPVCs or SPVPs.

---

Preferred routes can be configured to be directed or non-directed. A directed route only attempts a connection on the preferred route. If the connection cannot route over the preferred route, that connection will go into a failed state. A non-directed route first attempts to route over the preferred route. If the preferred route is not available, the connection will be attempted over other routes.

Keep the following in mind when planning preferred routes:

•All nodes in the preferred route must exist in the network node table.

•A preferred route can be confined to the same peer group as the source node, or it can go outside the local peer group.

•A preferred route can include non-Cisco nodes.

•A node can appear only once in a preferred route.

•Any preferred routes you defined using Release 3 software will be lost during an upgrade to Release 4. Once you have upgraded to Release 4, you must be manually re-enter your preferred routes. Prior to an upgrade, use the dspprefs command view all the configured preferred routes. Write down any preferred routes you want to re-enter once you have upgraded to Release 4.

•The preferred route feature is not compatible with point-to-multipoint SPVC configuration.

•Connections mastered on an RPM or VISM cannot be associated with a preferred route.

---

Note In Release 4, Cisco MGX switches with PXM45/A, PXM45/B, or PXM1E controllers support up to 5000 preferred routes per switch. Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switches with PXM45/C controllers support up to 10000 preferred routes.

---

A preferred route consists of a sequential list of up to 20 nodes, including the local node that hosts the starting point of the preferred route. The destination node can be up to 19 network elements (NEs), or 19 NNI links, away from the local node.

---

Note VISM-PR cards do not support preferred routes in Release 4. Any VISM-PR preferred routes that were configured in a previous release will be lost when the switch is upgraded to Release 4.

---

Maintaining the Network Node Table

The network administrator manually creates a node table that contains information about all the nodes in the network. All the nodes that will be in a preferred route must appear in the network node table, and each node in a preferred route must have it's own network table.

Cisco recommends that you keep the same network node table on every node in your network for the purpose of convenience when configuring preferred routes. Once you create the node table on one node, you can to FTP that table to all the other nodes in the network. If you change any information in one of the node tables, you need to update all of the node tables in the network to ensure synchronicity.

Before you can create a preferred route, all the nodes that will be in the preferred route must be in the network node table. Enter the dspnwnodes command to ensure that all the nodes in your planned preferred route are in the network node table, as shown in the following example:

U1.8.PXM.a > dspnwnodes

Node Identifier PXM Pref rte Node name 

     -------------------------------------------------- ----- -------- --------- 

     56:160:47.009181000000003071f80406.003071f80406.01 pxm1 No Fargo 

     56:160:47.009181000000003071f80422.003071f80422.01 pxm45 No Denver 

     56:160:47.339181000000003071f80433.003071f80433.01 pxm1E Yes Chicago 

If one or more nodes in your preferred route does not appear in the network node table, use the following procedure to add the missing nodes to the table.

---

Step 1 Establish a configuration session using a user name with GROUP1 privileges or higher.

Step 2 Enter the addnwnode command as follows to add the a node to the network node table:

U1.8.PXM.a > addnwnode <nodeId> <pxmType> [-name <nodeName>]

Table 12-5 describes the parameters you can configure through the addnwnode command.

Table 12-5 addnwnode Command Parameters

nodeId	This 22-octet uniquely identifies a PNNI node.
pxmType	Type of controller card in the switch. The controller type determines how the software converts between the physical and logical port identifiers. Type one of the following case-sensitive strings: •PXM45 •PXM1 •PXM1E •Others (for non-Cisco nodes) Note If you enter Others as the pxmType, you can not use the portId to build a preferred route. (See the neSyntax parameter in Table 12-6.)
-name	A string of up to 32 case-sensitive IA5 characters (except when empty) describing a PNNI node. If you plan to build a preferred route by using node names, you must include the -name option for entries in the network node table. Default: an empty string

In the following example, the user adds a PXM1E node named LA to the network.

MGX8850.7.PXM1E.a > addnwnode 56:100:47.009181000000003071f80406.003071f80406.01 PXM1E 
-name LA

Step 3 Enter the dspnwnode -id <nodeId> or the dspnwnode -name <nodeName> command to ensure that the node you added in Step 2 appears in the network node table. If you use the dspnwnode -id <nodeId> command, replace <nodeId> with the 22-octet node identifier. If you use the dspnwnode -name <nodeName> command, replace <nodeName> with the name you assigned to the node in Step 2.

---

Enter the cnfndidrtes command to replace a node ID with a different ID for all configured preferred routes. For example, if you remove a node that is a network element (NE) in one or more preferred routes, you can use the cnfndidrtes to enter a different node's name. Providing that the new node's name appears in the network node table, the new node replaces the old node in the preferred route. Enter the cnfndidrtes command as shown in the following example:

cnfndidrtes <oldNodeId> <newNodeId>

Replace <oldNodeId> with the 22-octet identifier for the node you want to replace. Replace <newNodeId> with the 22-octet identifier of the new node that replaces the old node.

Creating a Preferred Route

Use the following procedure to create a preferred route.

---

Step 1 Enter the dspnwnodes command to see the nodes in this database. These are the nodes you can use to set up your preferred route.

U1.8.PXM.a > dspnwnodes

Total Number of Network Nodes : 14 

     Node Identifier PXM Node name 

     --------------- --- --------- 

     56:160:47.0091810000000004c113ba39.0004c113ba39.01 PXM45 p2spvc7 

     56:160:47.00918100000000001a531c41.00001a531c41.01 PXM45 p2spvc14 

     56:160:47.009181000000000142266086.000142266086.01 PXM45 p2spvc15 

     56:160:47.00918100000000001a531c01.00001a531c01.01 PXM45 p2spvc20 

     56:160:47.00918100000000001a531c43.00001a531c43.01 PXM45 pswpop2-1 

     56:160:47.009181000000000164444ae0.000164444ae0.01 PXM45 pswpop2-2 

     56:160:47.00918100000000107be92fde.00107be92fde.01 PXM45 pswpop10 

     56:160:47.00918100000000c043002ddf.00c043002ddf.01 PXM1 pswpop9 

     56:160:47.009181000000003071f81323.003071f81323.01 PXM1 pnnises3 

     56:160:47.009181000000003071f8139d.003071f8139d.01 PXM1 pnnises4 

     56:160:47.00918100000000d058ac28e9.00d058ac28e9.01 PXM1 svcswp13 

     56:160:47.00918100000000c043002dcc.00c043002dcc.01 PXM1 svcswp15 

     56:160:47.0391810000000050e2003e16.0050e03e1600.00 Others svcslt5 

     56:160:47.0391810000000050e2001600.50e000000000.00 Others svcslt6 

Step 2 Enter the addpref command to set up your preferred route as follows:

8850_LA.7.PXM.a > addpref <routeid> <neSyntax> [-dstNEpos <NE>] [-ne1 {<node>/<port>}] 
[-ne2 {<node>/<port>}] ... [-ne20 {<node>/<port>}]

Table 12-6 describes the parameters you can configure for the addpref command.

Table 12-6 addpref Command Parameters

routeid	The preferred route identifier has a range of 1-65535. If a particular ID is in use, the node rejects the command. Check the dspprefs output for available route IDs as needed.
neSyntax	Four ways of identifying the NEs exist. Use the selected form for all NEs in the route Type one of the following keywords: •nodeidPnportid means the node is specified by the 22-octet node ID and the port by the PNNI logical integer pnPortId. •nodenamePortid means the node is specified by the node name and the port by the physical port ID. You can use node names only if the node names were added to the network node table (in addition to the mandatory node IDs). You can not use the physical port ID syntax if the pxmType is provisioned as Others. (See Table 12-5.) •nodeidPortid means the node is specified by the 22-octet node ID and the port by the physical port ID. You can not use the physical port ID syntax if the pxmType is provisioned as Others. (See Table 12-5.) •nodenamePnportid means the node is specified by the node name and the PNNI logical port by the integer pnPortId. You can use node names only if the node names were added to the network node table (in addition to the mandatory node IDs). The nodeID is the 22-octet PNNI node ID. The Portid is the PNNI physical port ID. On a PXM1E, the format is slot.port. On a PXM45, the format is slot:subslot.port:subport. The PnportID is the PNNI logical port identifier. This form of port identifier is an integer in the range 0-4294967295. Default: none
-dstNEpos	This integer identifies the position of the destination node in the NE sequence. For instance, an NE of 4 indicates that the fourth NE represents the destination node. Range: 1-20 Default: none
-ne1 through -ne20	Including the local node, you can specify up to 20 NEs in the preferred route. Each NE is defined by a pairing of a node and a port. The format of these paired elements must conform to the entry for neSyntax. Separate the values in the pairing by a slash and no spaces, but put a space between the keyword and NE, as follows: -ne(n) node/port The NE you specify as the destination node must be the highest numbered keyword, otherwise the switch rejects the command.The port identifier at the destination node must be set to 0. Note that the value 0 actually determines the last NE in the route. This 0 appears in the outputs of the display commands for preferred routes. For example, if a route has 9 NEs, the format would be: -ne9 node/0

Step 3 Enter the dsppref <routeId> command to verify the preferred route was configured correctly. Replace <routeId> with the preferred routes identifier.

Step 4 Associate the appropriate SPVC.SPVP to the preferred route you created in Step 2.

a. If you are associating a new SPVC/SPVP with the preferred route, enter the addcon command as follows:

addcon <ifNum> <vpi> <vci> <serviceType> <mastership> -rtngprio <routingPriority> -prefrte <preferredRouteId> [-directrte <directRoute>]

---

Note You only need to set the -directrte option if you want the SPVP/SPVC to only follows the directed route. If you set the -directrte parameter to 1, the SPVC/SPVP will fail if the preferred route is not available.

---

Table 12-7 describes the parameters you can configure for the addcon command.

b. If you are associating a previously created SPVC/SPVP with the preferred route, enter the cnfcon command, as follows:

cnfcon <ifNum> <vpi> <vci> <serviceType> <mastership> -rtngprio <routingPriority> -prefrte <preferredRouteId> [-directrte <directRoute>]

---

Note The cnfcon command parameters are the same parameters you set with the addcon command.

---

---

Note There are several optional parameters you can set using the addcon and cnfcon commands, but they do not appear in Table 12-7 because you do not need to set them when you are associating an SPVC/SPVP with a preferred route. To see a complete description of all the options you can configure through the addcon command, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference.

---

Table 12-7 addcon/cnfcon Command Parameters 

Parameter	Description
ifNum	Logical interface (or port) number. This ifNum corresponds to the ifNum added through the addport command. The range is 1-31.
vpi	Virtual path identifier value in the range 0-255 (UNI) or 0-4095 (NNI or VNNI). For VNNI, specify one VPI per port.
vci	Virtual connection identifier (VCI): For a VCC on a UNI, the range is 1-4095. On an NNI or VNNI, the VCI range is 1-65535. For MPLS, the recommended minimum VCI is 35. For a VPC, the vci is 0.
mastership	Value to specify the endpoint as master or slave: •1 or `m' specifies the master end. •2 or `s' specifies the slave end.
routingPriority	Priority of this connection. The range is 1-15. Default: 8
-prefrte	Associates a preferred route (preferredRouteId) to the connection. Use this optional parameter at the master endpoint only. Range: 0-65535 Default: 0
-directrte	Specifies that the connection can take only the preferred route associated through the -prefrte parameter. Use this optional parameter at the master endpoint only. To remove this requirement from the connection, use the cnfcon command and specify a 0 for the parameter. The possible values are as follows: 1: yes (make the preferred route required) 0: no (do not require the connection to take the preferred route) Default: no (0)

Step 5 Enter the dspcon <portid> <vpi> <vci> command to ensure that the SPVC/SPVP has been configured properly and is associated with the preferred route you set up in Step 1. Replace <portid> with the port identifier in the format slot:bay.line:ifnum. Replace <vpi> with the virtual path identifier for the connection. Replace <vpi> with the virtual circuit identifier for the connection.

---

Modifying a Preferred Route

Use the cnfpref command to modify a preferred route. The cnfpref command lets you re-specify existing NEs in a route, or add one or more NEs to an existing route. You can also change an NE to indicate that it is the destination node. A new destination node must have the highest NE number in the route. (See the detailed usage guidelines for the addpref command for details.)

Enter the cnfpref command as follows:

8850_LA.7.PXM.a > cnfpref <rteId> <neSyntax> [-dstNePos <Ne>] [-ne1 {<node>/<port>}] [-ne2 
{<node>/<port>}] ... [-ne20 {<node>/<port>}]

Table 12-8 describes the cnfpref command parameters.

Table 12-8 Parameters for cnfpref Command 

Parameter	Description
routeid	The preferred route identifier has a range of 1-65535. If a particular ID is in use, the node rejects the command. Check the dspprefs output for available route IDs as needed.
neSyntax	Four ways of identifying the NEs exist. Use the selected form for all NEs in the route Type one of the following keywords: •nodeidPnportid means the node is specified by the 22-octet node ID and the port by the PNNI logical integer pnPortId. •nodenamePortid means the node is specified by the node name and the port by the physical port ID. You can use node names only if the node names were added to the network node table (in addition to the mandatory node IDs). You can not use the physical port ID syntax if the pxmType is provisioned as Others. (See Table 12-5.) •nodeidPortid means the node is specified by the 22-octet node ID and the port by the physical port ID. You can not use the physical port ID syntax if the pxmType is provisioned as Others. (See Table 12-5.) •nodenamePnportid means the node is specified by the node name and the PNNI logical port by the integer pnPortId. You can use node names only if the node names were added to the network node table (in addition to the mandatory node IDs). The nodeID is the 22-octet PNNI node ID. The Portid is the PNNI physical port ID. On a PXM1E, the format is slot.port. On a PXM45, the format is slot:subslot.port:subport. The PnportID is the PNNI logical port identifier. This form of port identifier is an integer in the range 0-4294967295. Default: none
-dstNEpos	This integer identifies the position of the destination node in the NE sequence. For instance, an NE of 4 indicates that the fourth NE represents the destination node. Range: 1-20 Default: none
-ne1 through -ne20	Including the local node, you can specify up to 20 NEs in the preferred route. Each NE is defined by a pairing of a node and a port. The format of these paired elements must conform to the entry for neSyntax. Separate the values in the pairing by a slash and no spaces, but put a space between the keyword and NE, as follows: -ne(n) node/port The NE you specify as the destination node must be the highest numbered keyword, otherwise the switch rejects the command.The port identifier at the destination node must be set to 0. Note that the value 0 actually determines the last NE in the route. This 0 appears in the outputs of the display commands for preferred routes.For example, if a route has 9 NEs, the format would be: -ne9 node/0

To see a list of all preferred routes and obtain the required route index for the cnfpref command, enter the dspprefs command. To see details about individual preferred route, use the dsppref <routeId> command, and replace <routeId> with the preferred route identifier.

---

Note Preferred routes that were configured on switches running Release 3 will be lost when you upgrade the switch to Release 4. Once you have upgraded the switch to Release 4, you need to re-configure your preferred routes.

---

Deleting a Preferred Route

Enter the delpref <routeId> command to delete a preferred route description.Before you delete a preferred route, you must ensure that no SPVCs/SPVPs have that preferred route currently associated with them. Enter the dspcons -rteid <routeId> command to verify that there are no SPVCs/SPVPs associated with the preferred route you want to delete. Replace <routeId> with the route identifier for the preferred route you want to display.

To disassociated any SPVCs/SPVPs from the preferred route, enter the cnfcon command as follows:

8850_LA.7.PXM.a > cnfcon <ifNum> <vpi> <vci> <serviceType> <mastership> -rtngprio 
<routingPriority> -prefrte 0 

Table 12-7 describes the parameters you need to configure with the addcon command. Note that you must set the -prefrte parameter to 0 to disassociate a connection with a preferred route.

Deleting a Node from the Network Node Table

Before you can delete a node from the network node table, enter the dspnwnode <nodeId> command to ensure that the node is not part of a preferred route.

---

Note You can not delete a node from the network node table if it is currently being used by a preferred route.

---

If the node you want to delete is not being used by a preferred route, enter the delnwnode <nodeId> command to delete the node from the network node table. Replace <nodeId> with the 22-octet node identifier that you set with the addnwnode command, as described in the "Maintaining the Network Node Table" section earlier in this chapter.

Configuring Link Selection for Parallel Links

When parallel links exist between two nodes on a route, the node closest to the originating node selects a link based on one of the following factors:

•lowest administrative weight (minaw)

•maximum available cell rate (maxavcr)

•maximum cell rate configured for the link (maxcr)

•random link selection (loadbalance)

---

Note The route selection process is described in the PNNI Network Planning Guide for MGX and SES Products.

---

To configure the link selection method, enter the cnfpnni-link-selection command as follows:

mgx8830a.1.PXM.a >  cnfpnni-link-selection pnportid minaw|maxavcr|maxcr|loadbalance

Replace pnportid with the port ID in the format slot[:subslot].port[:subport]. (This is the same format that appears when you display ports with the dsppnport command.) Enter one link selection method after the port ID.

To display the link selection method, enter the dsppnni-link-selection command as follows:

mgx8830a.1.PXM.a > dsppnni-link-selection 1:2.1:1

physical port id:         1:2.1:1     link selection: minaw

 logical port id:        16848897

Configuring the Maximum Bandwidth for a Link

The maximum bandwidth for a link is defined when a PNNI partition is configured for a port. For more information, see Chapter 11, "Provisioning PXM1E Communication Links."

Configuring the Administrative Weight

The link administrative weight (AW) is used to calculate the total cost of a route and can be used by the PNNI controller when it has to choose between multiple parallel links. You can assign different AW values for each ATM class of service.

---

Note The role of AW in route and link selection is described in more detail in the PNNI Network Planning Guide for MGX and SES Products.

---

To configure the AW for a link, enter the cnfpnni-intf command as follows:

mgx8830a.1.PXM.a > cnfpnni-intf <pnportid> [-awcbr] [-awrtvbr] [-awnrtvbr] [-awabr] 
[-awubr] [-awal]

Replace pnportid with the port ID in the format slot[:subslot].port[:subport]. (This is the same format that appears when you display ports with the dsppnport command.) For each class of service for which you want to change the AW value, enter the appropriate option followed by the new value. For example, the following command sets the AW for CBR calls over the link:

mgx8830a.1.PXM.a > cnfpnni-intf 1:2.1:1 -awcbr 2000

To display the AWs assigned to a PNNI port, enter the dsppnni-intf command as follows:

mgx8830a.1.PXM.a >  dsppnni-intf 1:2.1:1

Physical port id: 1:2.1:1          Logical port id:   16848897

   Aggr token..........         0     AW-NRTVBR...........      5040

   AW-CBR..............      2000     AW-ABR..............      5040

   AW-RTVBR............      5040     AW-UBR..............      5040

Configuring the Bandwidth Overbooking Factor

The bandwidth overbooking factor represents the percentage of the actual available bandwidth that is advertised for links as the Available Cell Rate (AvCR). The default overbooking factor is 100, and this specifies that 100% of the actual available bandwidth should be advertised as the AvCR. When the overbooking factor is set below 100, a link is oversubscribed because the bandwidth booked for each connection exceeds the configured bandwidth for the connection. When the overbooking factor is set above 100, the link is under subscribed because the bandwidth booked for a connection exceeds the connection's configured bandwidth.

---

Note For more information on the bandwidth overbooking factor, refer to the PNNI Network Planning Guide for MGX and SES Products.

---

To configure the bandwidth overbooking factor for a PNNI port, enter the cnfpnportcac command as follows:

mgx8830a.1.PXM.a > cnfpnportcac <pnportid> <service_catogory> 
[-bookfactor <utilization-factor>] 

Replace pnportid with the port ID in the format slot[:subslot].port[:subport]. (This is the same format that appears when you display ports with the dsppnport command.) Replace service_catogory with the ATM class of service for which you are defining the overbooking factor, and replace utilization-factor with the new overbooking factor. For example:

mgx8830a.1.PXM.a >  cnfpnportcac 1:2.1:1 cbr -bookfactor 120

WARNING: New CAC parameters apply to existing connections also

To display the bandwidth overbooking factor for all classes of service, enter the dsppnportcac command as shown in the following example:

mgx8830a.1.PXM.a >  dsppnportcac 1:2.1:1                    

                  cbr:       rt-vbr:       nrt-vbr:          ubr:         abr:          
sig:

bookFactor:       120%          100%           100%          100%         100%          
100%

maxBw:       100.0000%     100.0000%      100.0000%     100.0000%    100.0000%     
100.0000%

minBw:         0.0000%       0.0000%        0.0000%       0.0000%      0.0000%       
0.3473%

maxVc:            100%          100%           100%          100%         100%          
100%

minVc:              0%            0%             0%            0%           0%            
1%

maxVcBw:            0             0              0             0            0             
0

Improving and Managing Rerouting Performance

The following sections provide some guidelines for improving and managing rerouting performance for the following network configurations:

•Pure PXM45/C Networks

•Hybrid Networks with PXM45/C and PXM45/B

•Pure PXM45/B Networks Running Version 3.0.10 or Later

•Hybrid Networks with PXM45/C and PXM45/A

Pure PXM45/C Networks

To improve rerouting performance in a pure PXM45/C based network, Cisco recommends entering the following commands on the active PXM45/C in each switch:

•cnfnodalcongth -setuphi 1200

•cnfnodalcongth -connpendhi 2400 -connpendlo 2000

•cnfnodalcongth -incompjour 30

To improve rerouting over specific NNI links, enter the following PXM45 commands at both ends of each link:

•cnfintfcongth <physical port> -setuphi 500

•cnfpnctlvc <physical port> sscop -scr 3000

---

Note These parameters are recommended only for the PXM45/C cards and not for the PXM45, PXM45/B or PXM1E cards.

---

Hybrid Networks with PXM45/C and PXM45/B

If the recommended settings for a pure PXM45/C network are used in a network that contains PXM45/B cards, the PXM45/B nodes can experience CLI lockout as a result of the volume of connections set up by the PXM45/C cards. CLI lockout is a condition where switch response to CLI commands is very slow because the switch is overloaded with other tasks.

For hybrid networks with PXM45/C and PXM45/B nodes, consider upgrading the PXM45/B nodes or limit the performance of the PXM45/C nodes to that of the PXM45/B nodes.

Pure PXM45/B Networks Running Version 3.0.10 or Later

To improve rerouting performance in a pure PXM45/B based network (Version 3.0.10 or later), Cisco recommends entering the following commands on the active PXM45/B in each switch:

For better call performance on PXM45/B cards, the following commands need to be issued after the upgrading to Release 3.0.10:

•cnfnodalcongth -connpendlo 750 -connpendhi 1000

•cnfnodalcongth -setuphi 1000

To improve rerouting over specific NNI links, enter the following PXM45 commands at both ends of each link:

•cnfintfcongth <physical port> -setuphi 500

•cnfpnctlvc <physical port> sscop -scr 3000

---

Note These parameters are recommended only for the PXM45/B cards and not for the PXM45, PXM45/C, or PXM1E cards.

---

Hybrid Networks with PXM45/C and PXM45/A

If the recommended settings for a pure PXM45/C network are used in a network that contains PXM45/A cards, the PXM45/A nodes can experience CLI lockout as a result of the volume of connections set up by the PXM45/C cards. CLI lockout is a condition where switch response to CLI commands is very slow because the switch is overloaded with other tasks. A normal deroute followed by a reroute will result in a CLI lockout on the PXM45A node.

The CLI lockout is extensive when a PXM45/A node is a via node between PXM45C based end nodes and there are permanently failed connections originating on the PXM45C end nodes. To prevent an extensive lockout, configure the PXM45C nodes that are adjacent to the PXM45A node using the following PXM command:

cnfnodalcongth -connpendhi 950 -connpendlo 750

---

Note This is same as the recommended threshold for PXM45/B nodes. This will configure the PXM45/C nodes to limit the number of connection setups forwarded to the PXM45A node.

---

Displaying Node Configuration Information

The following sections describe commands that display PNNI configuration information.

Displaying the PNNI Node Table

Once a PNNI node is configured, enter the dsppnni-node command to show the WAN nodal table. The node list is displayed in ascending order of each node index, all with one setting the node to the lowest PNNI hierarchy.

The significant information that will display is as follows:

•Node index

•Node name

•Node level (56 for all nodes until multiple peer groups are supported)

•Restricted transit—a flag that can prevent PNNI routing from transmitting this node

•Branching restricted—a flag that can prevent cpu-intensive branching at this node

•Admin status—up/down

•