Table Of Contents
cnfpnctlvc
Configure PNNI Port Control Virtual Channel—PXM45, PXM1E
The cnfpnctlvc command lets you configure bandwidth parameters for two types of control channels on a per-port basis. The types of control channels are service-specific connection-oriented protocol (SSCOP) and PNNI routing control channel (PNNI-RCC). The bandwidth parameters are as follows:
•
Peak cell rate
•
•
Note
If the bandwidth is reduced too much, the call rate on the port or the PNNI link may significantly drop, or signaling maybe hindered.
If the bandwidth is increased too much, other connections on the port may receive less bandwidth.Before using cnfpnctlvc, note the following:
•
•
•
•
The controller protect the flow of control data from bursts in user data by guaranteeing bandwidth for the control VCs. The reserved bandwidth is proportional to the line rate (T3/E3, OC3, OC12, and so on). Also, the excess priority for this category is equal to CBR and is higher than any other category.
The VC for ILMI (when enabled) is also a control channel, but its bandwidth parameters are fixed, as follows: PCR=1000 cps; SCR=50 cps; and MBS=1024 cells. The pertinent ILMI is configured on the AXSM, the PXM1E for its UNI/NNI back card, or the narrowband service modules.
Syntax
cnfpnctlvc <portid> <vc-type> [<-pcr> {peak cell rate}] [<-scr> {sustained cell rate}]
[<-mbs> {Maximum burst size}]Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vc-type
The type of control VC. The VC types are pnnircc and sscop.
-pcr
The PCR for the control VC has a range and default that depend on the VC type.
•
•
Defaults:
•
•
-scr
The SCR of the control VC.
Range: 1-5000 cps
The default depends first on the VC type and, for SSCOP, the line rate, as follows:
•
•
If the line rate is less than 47170 cps, the default is 126 cps
If the line rate is 47170-70754 cps, the default is 334 cps
If the line rate is 70755-117924 cps, the default is 500 cps
If the line rate is 117925-235848 cps, the default is 667 cps
If the line rate is 235849-707548 cps, the default is 2000 cps
-mbs
The maximum burst size of the control VC.
Range: 1-1000 cells
Defaults:
•
•
Related Commands
dsppnctlvc (on the active control card), dspload (on a service module or the PXM1E)
Attributes
Example
Change the MBS of the PNN-RCC VC on port 3:1.1:1 to 100 cells. The system returns the error message that the port is still in service. After downing the port with the dnpnport command, complete the task. (If connections were on the port, they would go into alarm.) Check the control VCs with dsppnctlvc.
One section of the display (labeled "provisioned") shows configured parameters, and one section shows operational VC parameters. In this example, the "provisioned" section reflects that you did not configure bandwidth parameters other than MBS, and the "operational" section shows actual bandwidth parameters—including the MBS you configured. Remember to re-activate the port by using uppnport.
8850_NY.8.PXM.a > cnfpnctlvc 3:1.1:1 sscop -mbs 100ERROR: Port is not out-of-service8850_NY.8.PXM.a > dnpnport 3:1.1:18850_NY.8.PXM.a > cnfpnctlvc 3:1.1:1 sscop -mbs 100cnfpnctlvc Successful8850_NY.7.PXM.a > dsppnctlvc 3:1.1:1vc type = sscop Parameter = Provisionedservice category : sig PCR: Not ProvisionedSCR : Not Provisioned MBS : 100vc type = sscop Parameter = Operationalservice category : sig PCR : 308000SCR : 2000 MBS : 1008850_NY.8.PXM.a > uppnport 3:1.1:1cnfpnni-election
Configure PNNI Election—PXM45, PXM1E
The cnfpnni-election command lets you specify the priority of a node for the purpose of electing a peer group leader (PGL). By using this ranking, you can promote or prevent certain nodes for consideration for election as PGL.
In a multi-peer group environment, each peer group can elect one PGL. Such an election takes place for every level of the hierarchy. (For example, if three levels exist, three PGL elections occur.) To ensure that a node cannot win the PGL election, you can assign 0 for the priority.
Every node in a peer group runs the election algorithm—with one exception: a node with the Non-Transit for PGL E;ection Flag set.
In addition to the priority, cnfpnni-election lets you specify the following:
•
•
•
Syntax
cnfpnni-election <node-index> [-priority priority] [-initTime init-time] [-overrideDelay override-delay] [-reelectionTime reelection-time]
Syntax Description
Related Commands
dsppnni-election
Attributes
Example
Specify the following PGL election parameters, then use dsppnni-election to check these parameters.
•
•
•
•
•
p2spvc4.7.PXM.a > cnfpnni-election 1 -priority 15 -initTime 10 -overrideDelay 20 -reelectionTime 10p2spvc4.7.PXM.a > dsppnni-electionnode index: 1PGL state...... OperPgl Init time(sec)....... 10Priority....... 15 Override delay(sec).. 20Re-election time(sec) 10Pref PGL...............56:160:47.019181004030211100000000.00107be92f13.01PGL....................56:160:47.019181004030211100000000.00107be92f13.01Active parent node id..36:56:47.019181004030211100000000.000142265c0d.00node index: 2PGL state...... OperPgl Init time(sec)....... 15Priority....... 15 Override delay(sec).. 30Re-election time(sec) 15Pref PGL...............36:56:47.019181004030211100000000.000142265c0d.00PGL....................36:56:47.019181004030211100000000.000142265c0d.00Active parent node id..0:0:00.000000000000000000000000.000000000000.00p2spvc4.7.PXM.a >cnfpnni-intf
Configure PNNI Interface—PXM45, PXM1E
The cnfpnni-intf command lets you specify two distinct PNNI parameters. The aggregation token applies to a logical node, and the administrative weight (AW) applies to a port.
Aggregation Tokens
An aggregation token is a marker that indicates which up-links (links going out of the peer group) can be bundled or aggregated at the next logical level. For example, if four links a, b, c, and d connect to peer groups X and Y, no aggregation exists for the links by default. The LGNs of these peer groups could have hypothetical names x02 and y02. They would be connected by a single logical link. You could use the cnfpnni-intf command to configure aggregation tokens.
If you configure the aggregation token of link c as 1, then x02 and y02 would have two logical links. One link would correspond to aggregation token 0, and the other link would correspond to aggregation token 1. In summary:
An aggregation token is the number of links between a peer group leader and the lowest level of a PNNI hierarchy. The range for tokens is 1-32.
Administrative Weight
The administrative weight (AW) is a number that serves as a cost-based determinant of a route. Each port in a PNNI network has a default AW for the egress direction. Whether it uses the default AW or an AW you specify, PNNI adds all the AWs in a prospective route then determines whether the route is too expensive. For an SPVC, you can specify the maximum cost with the addcon or cnfcon command.
You can specify that all classes of service on the port have the same AW, or you can specify an AW for each service class on the port. If you specify the same AW for all, it overrides the default AW or the AW you might specify for individual services types.
The AW for a path is the sum, in both directions, of the individual weight of each link on the path. See Usage Guidelines for details about AW.
Syntax
cnfpnni-intf <portid>
[-aggregationToken token]
[-awcbr aw]
[-awrtvbr aw]
[-awnrtvbr aw]
[-awabr aw]
[-awubr aw]
[-awall aw]Syntax Description
If you enter -awall to specify an AW, it overrides the AW for all individual service types.
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-aggregationToken
Specify a 32-bit number for logical link aggregation between a peer group leader and the lowest level.
Range: 0-2147483648
Default: 0-awcbr
Specify the administrative weight for constant bit rate (CBR) on this interface.
Range: 0-4,194,304
Default: 5040-awrtvbr
Specify the administrative weight for real-time variable bit rate (rt-VBR) on this interface.
Range: 0-4,194,304
Default: 5040-awnrtvbr
Specify the administrative weight for non-real-time variable bit rate (nrt-VBR) on this interface.
Range: 0-4,194,304
Default: 5040-awabr
Specify the administrative weight for available bit rate (ABR) on this interface.
Range: 0-4,194,304
Default: 5040-awubr
Specify the administrative weight for unspecified bit rate (UBR) on this interface. UBR connections can include SVC ping connections.
Range: 0-4,194,304
Default: 5040-awall
Specify the administrative weight for all service types on this interface. If you use -awall, this aw becomes the AW for every service type on this port.
Range: 0-4,194,304
Default: 5040
Usage Guidelines
PNNI includes a protocol for routing the topology state. This protocol advertises details about the peer group links and nodes. Links and nodes are assigned attributes that can be used to diagnose and tune network behavior.
The administrative weight (AW) for a port is an integer that has no units of measure. The switch compares the sum of all AWs along a path with the sum of all AWs along another path to determine which path is more cost-effective. You can specify one AW for all classes of service, or you can specify an AW for each class of service. The AW for all (-awall) overrides the AW for an individual class.
The AW parameter influences how PNNI selects a path within a peer group and therefore how it distributes SVCs and SPVCs. PNNI route selection can also use AW to exclude certain links from routing. For example, it can define a backup link for use only when insufficient bandwidth is available on the primary link.
Related Commands
dsppnni-intf
Attributes
Example
Specify the following AWs on port 4:1.1:11.
•
•
•
Use the dsppnni-intf command to display the configuration.
SanJose.7.PXM.a > cnfpnni-intf 4:1.1:11 -awrtvbr 11040 -awnrtvbr 20040 -awubr 1040SanJose.7.PXM.a > dsppnni-intf 4:1.1:11Physical port id: 4: 1.1:11 Logical port id: 17045515Aggr token.......... 0 AW-NRTVBR........... 20040AW-CBR.............. 5040 AW-ABR.............. 5040AW-RTVBR............ 11040 AW-UBR.............. 1040SanJose.7.PXM.a >cnfpnni-link-selection
Configure PNNI Link Selection—PXM45, PXM1E
The cnfpnni-link-selection command specifies which routing policies are used to select one of the parallel links that connect a neighboring PNNI node. "Neighboring node" in this case means a directly connected node. The cnfpnni-link-selection command applies only if parallel links exist between the specified port and neighboring nodes.
Syntax
cnfpnni-link-selection <portid> {minaw | maxavcr | maxcr | loadbalance}
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
minaw
The routing protocol selects the link with the least administrative weight (AW). The AW is a numeric value that every logical port ingress has. The total cost of a route is the sum of all ingress port AWs in both directions of the route.
The minaw policy is the default.
maxavcr
The routing protocol selects the link with the largest available cell rate (AvCR). The AvCR is the remaining bandwidth after the total utilized bandwidth is subtracted from the maximum cell rate (MaxCR).
The maxavcr policy works well for traffic that consistently requires a large amount of bandwidth.
maxcr
The routing protocol selects the link with the largest maximum cell rate (MaxCR). Typically, the MaxCR is the maximum speed of the line (or trunk). Therefore, if one link traverses an OC3 line and another link traverses a T3 line, the MaxCR policy dictates that PNNI select the OC3 line. Only when sufficient bandwidth does not exist on a line does the routing protocol switch to AvCR.
The maxcr policy works well for bursty traffic.
loadbalance
The routing protocol alternates the link it selects for routing new calls and so evenly distributes the number of calls across the parallel links. The load balance policy works well with links that have identical or very similar AW or bandwidth characteristics.
Related Commands
dsppnni-link-selection
Attributes
Example
Specify maximum available cell rate as the routing policy for the link with port ID 4:1.1:11. Use dsppnni-link-selection to see the link selection policy on this port. Note that dsppnni-link-selection shows the logical port number for the physical port ID.
SanJose.7.PXM.a > cnfpnni-link-selection 4:1.1:11 maxavcrSanJose.7.PXM.a > dsppnni-link-selection 4:1.1:11physical port id: 4:1.1:11 link selection: maxavcrlogical port id: 17045515SanJose.7.PXM.a >cnfpnni-mtu
Configure PNNI Maximum Transfer Unit—PXM45, PXM1E
The cnfpnni-mtu command specifies the maximum data packet size in number of bytes. This command is useful for internetworking compatibility, for which you must match the maximum packet size of your peer group to a size that another peer group can handle. This command is primarily for configuring internetwork compatibility, but you can use it in lab trials to test the affect of various packet sizes on the performance of the peer group.
Use dsppnni-mtu to display the PNNI packet size configuration.
Syntax
cnfpnni-mtu <mtu>
Syntax Description
Related Commands
dsppnni-mtu
Attributes
Example
This example shows the cnfpnni-mtu command line that specifies the maximum PNNI packet size to 3002 bytes. Use dsppnni-mtu to display the specified information.
SanJose.7.PXM.a > cnfpnni-mtu 3002SanJose.7.PXM.a > dsppnni-mtumax packet size: 3002SanJose.7.PXM.a >cnfpnni-node
Configure PNNI Node—PXM45, PXM1E
The node-level cnfpnni-node command lets you:
•
•
–
–
The node configuration and state parameters you can modify are as follows:
•
•
•
•
•
•
•
•
•
The preceding parameters appear as optional parameters in the syntax. The only required parameter for this command is the local node index. The local node index is a number in the range 1-10 that indicates the level of the logical node within a multi-peer hierarchy on the switch. If you do not know the value of this system-generated item, use dsppnni-node.
Note
Disabling the Node for Parameters That Require It
For some of parameters, you must first disable the node. Applicable parameters are the:
•
•
•
•
For these parameters, three executions of cnfpnni-node are necessary:
1.
2.
3.
Be sure to synchronize applicable changes (such a change in level) throughout the network and follow up with dsppnni-node or other applicable display commands.
Syntax
cnfpnni-node <node-index> [-atmAddr atm-address] [-level level] [-nodeId node-id] [-pgId pg-id] [-lowest {true | false}] [-enable {true | false}] [-transitRestricted {on | off}] [-complexNode{on | off}] [-branchingRestricted {on | off}]
Syntax Description
node-index
The node index specifies the relative position of a logical node within the hierarchy of a multi-peer group. The lowest level is 1. Each new logical node added to the hierarchy automatically gets the next higher index number, so you cannot configure the node index.
Range: 1-10
Default: 1-atmAddr
Specify the ATM address for this logical node. For you to change the ATM address, the node must be disabled. For details, see the section, "Disabling the Node for Parameters That Require It." Note that only the lowest node in the hierarchy requires an ATM address.
Default: Figure 2-7 shows the factory-set default.
-level
This parameter specifies the level of the node within the PNNI hierarchy. The level of the node is the number of bits in the node ID (-nodeId parameter) or peer group ID (-pg-id parameter). For example, the default level of 56 means that the node ID is 56 bits long. If you specify a level of 48, the node ID has a length of 48 bits.
The maximum number of levels you can configure on a switch 10. This limit is meaningful in a multi-peer group only. Although the level can be any value within the 1-104 range, selecting an 8-bit boundary makes network planning and address management easier. Four example, using 56 for a level is more expedient than using a level of 59.
Range: 1-104 bits
Default: 56 bits-nodeId
Specify the PNNI node identifier assigned to a PNNI node. The node ID consists of the PNNI hierarchy level (-level), followed by the length of the ATM address (addaddr length), followed by the ATM address (-atmAddr). As shown in Figure 2-7, node-id is a 22-byte, formatted hexadecimal string.
Note
Default: Figure 2-7 shows the factory-set default.
-pgId
All members of a peer group have the same peer group identifier (pgID) and exist on the same level. (The level is either the existing number of bits or whatever you specify with -level).
The default value of level is 56 (7 bytes), which specifies the length of -pgId to 7 bytes. However, the maximum length of -pgId is 14 bytes, so display commands always show -pgId as 14 bytes with trailing zeros filling the undefined fields. If you increase the value of level, you change the length, and therefore the value, of -pgId, but it will always be displayed as 14 bytes.
Before you change the value of pg-id, disable the node by entering cnfpnni-node -enable false.
This is a 14-byte, formatted hexadecimal string.
Default: Figure 2-7 shows the factory-set default.-enable
Specify the administrative status of the PNNI node. Before you change a node ATM address, node ID, peer group ID, or hierarchical level, the node must be disabled.
true: Enable the node.
false: Disable the node.Default: true
-transitRestricted
Specify whether connections can transit this node. You can disallow via connections for security reasons, to minimize traffic supported by either a low bandwidth node or a highly critical node, and so on.
on: This node allows via connections.
off: Via connections cannot transit this node.Default: off
-complexNode
Specify whether this node is a complex node. The lowest-level node cannot be a complex node.
on: This node is a complex node.
off: This node is not a complex node.Default: off
-branchingRestricted
Specify whether the PNNI node allows point-to-multipoint branches.
on: This node does not allow point-to-multipoint branches.
off: This node allows point-to-multipoint branches.Default: off
Caution
Figure 2-7 Cisco Factory-shipped Defaults for PNNI Peer Group Identifier, PNNI Summary Address, ATM Address, and PNNI Node Identifier
Usage Guidelines
All cards ship with default addresses. These defaults are provided for evaluation of the switch. Before or while you deploy a switch, you should change the default addresses by executing either cnfpnni-node or addpnni-node. The Cisco MGX 8850 and MGX 8950 Switch Software Configuration Guide explains node addressing in the section, "Guidelines for Creating an Address Plan."
The ATM address, address prefixes, and peer group ID share some default field values, as shown in Figure 2-7.
Related Commands
addpnni-node, delpnni-node, dsppnni-node, addaddr
Attributes
Example
This example shows the cnfpnni-node command line that specifies the PNNI configuration values for a node that already exists on the network. The command line configures the PNNI node as follows:
•
•
•
•
•
•
•
•
•
Use dsppnni-node to display the PNNI configuration values.
SanJose.7.PXM.a > cnfpnni-node 1 -level 56 -nodeId 56:160:47.0091 81000000 00309409f1f1.00309409f1f1.01 -atmAddr 47.0091 81000000 00309409f1f1.00309409f1f1.01 -pgId 56:47.00.9181.0000.0000.0000.0000.00 -lowest true -enable true -transitRestricted on -complexNode off -branchingRestricted offSanJose.7.PXM.a > dsppnni-nodenode index: 1 node name: SanJoseLevel............... 56 Lowest.............. trueRestricted transit.. on Complex node........ offBranching restricted offAdmin status........ up Operational status.. upNon-transit for PGL election.. offNode id...............56:160:47.00918100000000309409f1f1.00309409f1f1.01ATM address...........47.00918100000000309409f1f1.00309409f1f1.01Peer group id.........56:47.00.9181.0000.0000.0000.0000.00SanJose.7.PXM.a >cnfpnni-pkttrace
Configure PNNI Packet Trace—PXM45, PXM1E
This command applies to debugging. It causes the switch to check the PNNI packets transmitted and received at each peer. For example, if an interface is not receiving user-traffic, you can execute dsppnni-pkttrace to display packet information that can help you find the level and type of blockage.
The cnfpnni-pkttrace command specifies the trace command examines the contents of PNNI packets exchanged between two neighboring nodes. A PNNI packet consists of a Hello packet and the topology information packets.
Note
If you plan to use the optional -portId parameter but do not have the logical format of the port ID, use dsppnport. For details, refer to the Syntax Description of cnfpnni-pkttrace.
Syntax
cnfpnni-pkttrace {tx {on | off} | rx {on | off} } [node-index [-portId port-id | -svcIndex svc-index]]
Syntax Description
Usage Guidelines
PNNI trace commands have characteristics that standard debug commands lack, namely:
•
•
•
Related Commands
dsppnni-pkttrace, dsppnport, dsppnports
Attributes
Example
Configure then display a trace that examines the contents of PNNI Hello packets, as follows:
•
•
•
Geneva.7.PXM.a > cnfpnni-pkttrace tx 17504PNNI/tx_packet on port 17504 at level 56> 01:00010064 01010100 000038a0 47009181 00000000 309409f3 b8003094> 02:09f3b801 47009181 00000000 309409f3 b8003094 09f3b801 38470091> 03:81000000 00000000 000038a0 47009181 00000000 001a531c 2a00001aGeneva.7.PXM.a > dsppnni-pkttrace tx -portId 17504Node Index :1 Port id: 17504 Tx Pkt Trace onGeneva.7.PXM.a >cnfpnni-routing-policy
Configure PNNI Routing Policy—PXM45. PXM1E
The cnfpnni-routing-policy command specifies which routing policy values are used during UNI call setup. Routing policies control PNNI routing for your network.
The cnfpnni-routing-policy command specifies which routing policies are used for:
•
•
•
The two dynamic routing protocols are shortest path and on-demand routing.
Background Routing Tables
The background routing tables contain all routes within the peer group. The routes are calculated from information in the internal data base (IDB). When a topology change affects usable routes within the peer group, a PNNI topology state packet carries the formation to each node so it can update its IDB. The background routing tables are updated to reflect the change in routing parameters.
Routing tables are generated (or pre-computed) to support routing based on the shortest path.
•
•
•
On-demand routing is used if any of the following occur:
•
•
•
Caution
Syntax
cnfpnni-routing-policy [-sptEpsilon epsilon] [-sptHolddown holddown]
[-bnPathHolddown bn-path-holddown] [-loadBalance {random | maxbw}]
[-onDemand {firstfit | bestfit}] [-awBgTable {on|off}] [-ctdBgTable {on|off}]
[-cdvBgTable {on|off}]Syntax Description
Related Commands
dsppnni-routing-policy
Attributes
Example
Specify the following routing policy:
•
•
•
•
•
•
•
You can confirm your settings with the related command dsppnni-routing-policy.
Geneva.7.PXM.a > cnfpnni-routing-policy -sptEpsilon 0 -sptHolddown 1 -loadBalance random -onDemand bestfit -awBgTable on -ctdBgTable on -cdvBgTable onGeneva.7.PXM.a > dsppnni-routing-policySPT epsilon......... 0 Load balance........ randomSPT holddown time... 1 On demand routing... best fitSPT path holddown time 2 AW Background Table onCTD Background Table on CDV Background Table onGeneva.7.PXM.a >cnfpnni-scope-map
Configure PNNI Scope Map—PXM45, PXM1E
The cnfpnni-scope-map command specifies how UNI 4.0 address scope values are mapped to PNNI hierarchal levels. The purpose of scope values is to support granularity between the organizational hierarchy and to support growth. The organizational scope consists of 15 levels. These parameters are stored in the scope map table.
Application of Scope Levels
This section describes the applications of the organizational scopes as defined in Section A5.2 of UNI Signalling 4.0. If you already know the application, you can directly refer to the Syntax Description.
Level 1—Local Network
The level 1 scope maps to the concept of a physical network. Using Ethernet as an example, a single Ethernet segment and multiple Ethernet segments extended by repeaters or bridges can be treated as a local network. Therefore, the network operator configures the mapping of membership scope "local network" to map to the routing levels that fit the needs of the local scope concept. For example, the mapping can be to a bottom-level peer group or a peer group of higher level in a PNNI routing hierarchy to simulate extended physical networks.
Levels 2, 3, and 4—LocalNetworkPlusOne, LocalNetworkPlusTwo, SiteMinusOne
Scope levels 2-4 can be mapped to ATM sub-networks that do not use inter-building or wide-area links.
Level 5—IntraSite
Scope level 5 identifies the inclusive routing hierarchies that are not geographically separated. The intra-site scope allows the network operator to confine the traffic within a local location and therefore avoid using wide-area links or inter-building links.
Levels 6 and 7—SitePlusOne and OrganizationMinusOne
Scope levels 6 and 7 can identify ATM networks that may use inter-building links or wide-area links.
Level 8—IntraOrganization
The Intra-Organization scope identifies ATM networks that represent the inclusive routing hierarchy of an autonomous organization. An autonomous organization is an organization that has administrative authority over the network. The ATM networks identified by this membership scope therefore may use inter-building and wide-area links.
Levels 9 and 10—OrganizationPlusOne and CommunityMinusOne
The values 9-10 can be used to identify union of more than one organizations.
Levels 11, 12, 13, and 14—IntraCommunity, CommunityPlusOne, Regional, and InterRegional
Scope levels 11-14 can be used to identify ATM networks that represent a collection of autonomous organizations. These networks are organized by a provider or organizational partnership.
Level 15—Global
Scope level 15 represents all autonomous organizations that form a connected, private ATM network.
Syntax
cnfpnni-scope-map <scope> <level>
Syntax Description
Related Commands
dsppnni-scope-map
Attributes
Example
Configure the scope map table for the following:
•
•
These values map the UNI 4.0 scope `1' to the PNNI hierarchical level `56'.
Geneva.7.PXM.a > cnfpnni-scope-map 1 56Geneva.7.PXM.a > dsppnni-scope-mapUNI Scope Pnni Routing Level---------------------- ------------------LocalNetwork(1) 56LocalNetworkPlusOne(2) 56LocalNetworkPlusTwo(3) 56SiteMinusOne(4) 40IntraSite(5) 40SitePlusOne(6) 32OrganizationMinusOne(7) 32IntraOrganization(8) 24OrganizationPlusOne(9) 24CommunityMinusOne(10) 24IntraCommunity(11) 8CommunityPlusOne(12) 8Regional(13) 0InterRegional(14) 0Global(15) 0Geneva.7.PXM.a >cnfpnni-svcc-rcc-timer
Configure PNNI Switched Virtual Connection Routing Control Channel (SVCC-RCC) Timer—PXM45, PXM1E
The cnfpnni-svcc-rcc-timer command lets you specify the initial PNNI SVCC-based variables for a network node. Logical group nodes (LGNs) use SVCC-RCCs to exchange routing information.
Syntax
cnfpnni-svcc-rcc-timer <node-index> [-initTime init-time] [-retryTime retry-time] [-callingIntegrityTime calling-integrity-time] [-calledIntegrityTime called-integrity-time]
Syntax Description
Related Commands
dsppnni-svcc-rcc-timer
Attributes
cnfpnni-timer
Configure PNNI Timers—PXM45, PXM1E
The cnfpnni-timer command specifies the initial PNNI timer values and significant change thresholds of a network node. You must carefully plan the use of this command because modifying a timer can significantly change network efficiency.
Syntax
cnfpnni-timer <node-index> [-ptseHolddown ptse-holddown] [-helloHolddown hello-holddown] [-helloInterval hello-interval] [-helloInactivity-factor hello-inactivity-factor] [-horizontalLinkInactivityTime horizontal-link-inactivity-time] [-ptseRefreshInterval ptse-refresh-interval] [-ptseLifetimeFactor ptse-lifetime-factor] [-retransmitInterval retransmit-interval] [-ptseDelayedAckInterval ptse-delayed-ack-interval] [-avcrPm avcr-pm] [-avcrMt avcr-mt] [-cdvPm cdv-pm] [-ctdPm ctd-pm]
Syntax Description
Usage Guidelines
PTSE packets update the peer group when network changes occur. Your network should run fine with the defaults PTSE timing parameters. Networks that have properties significantly different from the norm may perform better if you optimize some of the PTSE parameters, but you should change these parameters carefully, and test the network before introducing live traffic.
For example, if no one is permitted to change a network topology (perhaps for test purposes), you may decide that the default -ptseHolddown value (1 sec) is too small, causing sequential broadcasts of identical PTSE packets. Further reason for making such a change would be given if the network was a small and it's connections were short. Inversely, it may warrant a smaller -ptseHolddown value if many changes are being made to a network, or if it was large, or if it had many long connections. These are only examples—these changes should only be made be network experts.
Related Commands
dsppnni-timer
Attributes
Example
This example shows the cnfpnni-timer command line that is set with the following parameter values:
•
•
•
•
•
•
•
•
•
•
•
•
You can confirm your settings with the related command dsppnni-timer.
SanJose.7.PXM.a > cnfpnni-timer 1 -ptseHolddown 120 -helloHolddown 120 -helloInterval 15 -helloInactivity-factor 5 -horizontalLinkInactivityTime 10 -ptseRefreshInterval 1800 -ptseLifetimeFactor 200 -retransmitInterval 50 -ptseDelayedAckInterval 10 -avcrPm 3 -avcrMt 50 -cdvPm 25 -ctdPm 50SanJose.7.PXM.a > dsppnni-timer 1node index: 1Hello holddown(100ms)... 12 PTSE holddown(100ms)... 12Hello int(sec).......... 15 PTSE refresh int(sec).. 1800Hello inactivity factor. 5 PTSE lifetime factor... 200Retransmit int(sec)..... 5AvCR proportional PM.... 3 CDV PM multiplier...... 25AvCR minimum threshold.. 50 CTD PM multiplier...... 50Peer delayed ack int(100ms)................... 10Logical horizontal link inactivity time(sec).. 10Geneva.7.PXM.a >cnfpnportacc
Configure Port Access—PXM45, PXM1E
The cnfpnportacc command lets you associate an ATM filter set with a port (after you create the filter set with addfltset). You must specify at least one filter set if you use this command.
Syntax
cnfpnportacc <portid> [-in in-filter-name] [-out out-filter-name]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-in
in-filter-name: the name of the filter set that applies to SETUP messages that arrive at the port.
-out
out-filter-name: the name of the filter set that applies to SETUP messages that leave the port.
Related Commands
delpnportacc, addfltset
Attributes
cnfpnportcac
Configure Port Connection Admission Control—PXM45, PXM1E
The cnfpnportcac command lets you reserve a percent of the bandwidth for an individual service type. The new configuration applies to new and existing calls. You can run this command whether the port is active or in the provisioning state.
The bookfactor is the percent of utilization. It applies to connection admission control (CAC). When the default for maxbw and minbw is used for all service types, the common AvCR is advertised for all the service types.
You must specify at least one of the optional keywords.
Syntax
cnfpnportcac <portid> <service_category> [-bookfactor utilization-factor] [-maxbw max-bw-percent] [-minbw min-bw-percent] [-maxvc max-vc-percent] [-minvc min-vc-percent] [-maxvcbw max-vc-bw]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
service_category
Service category (service type). Choices are: cbr, rtvbr, nrtvbr, ubr, or abr.
-bookfactor
The service category utilization factor (SCUF) for a service type.
Range: 1-200
Default: 100-maxbw
The max-bw-percent is the maximum percentage of bandwidth for a service category on this port.
Range: 0-100.0000
Default: 100-minbw
The min-bw-percent is the minimum percentage bandwidth for a service category on this port.
Range: 0-100.0000
Default: 0-maxvc
The max-vc-percent is maximum percent of VCs for a service category on this port.
Range: 0-100
Default: 100-minvc
The min-vc-percent: is the minimum percent of VCs for a service category on this port.
Range: 0-100
Default: 0-maxvcbw
The max-vc-bw: maximum bandwidth, in cells per second, as specified by the PCR allowed for a VC in a service category on this port.
Range: 0 through the maximum possible line rate
Default: 0 (disabled)
Related Commands
dsppnportcac
Attributes
Usage Guidelines
This section uses three examples to describe the booking factor.
1.
•
•
2.
Suppose that, for the same 100-Mbit link, the booking factor is 10.
•
•
3.
For the same 100-Mbit link, the booking factor is 200.
•
•
•
cnfpnportcc
Configure Port Call Control—PXM45, PXM1E
The cnfpnportcc command lets you set certain call control parameters for a specific port, as follows:
•
•
–
–
–
•
Choosing the enable for the subscription option depends on the intelligence of the CPE. If the CPE can process an ADDPARTY message, leave the subscription option disabled. (If this option is disabled, the port sends an ADDPARTY upon receipt of an ADDPARTY that terminates on an existing leaf.) If you enable the subscription option, the port sends a SETUP message instead of ADDPARTY and therefore forces the creation of a new branch or leaf on the switch. This option is available to either a private UNI or public UNI only.
Note
Changes apply to new incoming calls, not existing calls. For example, if the port has non-persistent endpoints when you block this type of endpoint, the existing endpoints remain.
Syntax
cnfpnportcc <portid> < [-maxp2mproot max-p2mp-root] [-maxp2mpleaf max-p2mp-leaf] [-svcblock {yes | no}] [-spvcblock {yes | no}] [-nonpersblock {yes | no}] [-subscribe {yes | no}] >
Syntax Description
You must specify at least one optional keyword.
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-maxp2mproot
The max-p2mp-root: maximum number of root VCs on this port. In the current release, this parameter is meaningless.
Default: 1000
-maxp2mpleaf
The max-p2mp-leaf: maximum number of leaf VCs on this port. In the current release, this parameter is meaningless.
Default: 4095
-svcblock
Enables or disables SVC blocking on the port.
•
•
Default: no.
-spvcblock
Enables or disables SPVC blocking on the port. Type "yes" or "no."
•
•
Default: no
-nonpersblock
Enables or disables blocking of calls with non-persistent slave endpoints on the port. Type "yes" or "no."
•
•
Default: no
-subscribe
The subscription option applies to a port that supports P2MP connections. Type yes to cause the port to send SETUP rather than ADDPARTY messages to the CPE.
Related Commands
dsppnportcc
Attributes
cnfpnportie
Configure PNNI Port Information Element—PXM45, PXM1E
The cnfpnportie command configures a port to take one of three actions on a priority services information element (PS IE) or a closed user group information (CUG IE).
Note
The choices with this command are to allow the IE, disallow the IE, or let the port automatically determine whether to send the IE. The effects of allowing and disallowing an IE are as follows:
•
•
•
–
–
Additionally, some behaviors depend on the type of IE and the interface, as follows:
•
•
Note
The CUG index IE is supported on both public and private UNI interfaces that have at least Q.2931 capability. The IE signalling also depends on the CUG provisioning at the interface address, as follows:
•
•
•
On non-UNI egress interfaces, the CUG IC IE is supported as follows:
•
•
Additionally, the PS IE can be passed along to other non-UNI interfaces if the passalong request bit is set in the IE and if those interfaces possess the passalong capability.
Syntax
cnfpnportie <portid> [-psie {auto | allowed | disallowed}] [-cugie {auto | allowed | disallowed}]
Syntax Description
Related Commands
dsppnportie
Attributes
Example
For port 12:12.1:1, specify the PS IE to be auto, and disallow the CUG IE,
pop3-1.7.PXM.a > cnfpnportie 12:12.1:1 -cugie disallowcnfpnportloscallrel
Configure PNNI Port Loss of Signal Call Release—PXM45, PXM1E
The cnfpnportloscallrel command lets you apply one of the following controls to connection de-routing on a port due to a loss of signal (LOS):
•
•
With standard operation, PNNI waits for the SSCOP "no-response" and T309 timers to expire before it releases calls on a broken link. The default values for these timers are 30 seconds and 10 seconds, respectively. The system-level default (and therefore the default for cnfpnportloscallrel) is to retain all the calls in case of a transitory loss of connectivity for the duration of these timers. However, this pause may unnecessarily delay the re-routing of connections. Therefore, the cnfpnportloscallrel feature gives you the option of controlling the call release as needed for a particular port.
Before you configure the de-route delay part of this feature, note the following characteristics:
•
•
–
–
•
•
•
•
•
•
•
•
•
Syntax
cnfpnportloscallrel <portid> <yes | no> [-delay <deroute-delay-val>]
Syntax Description
Related Commands
dsppnportloscallrel, cnfsscop, dspsscop
Attributes
Example
Enable call release upon LOS for port 3:1.1:1, then confirm its status.
8850_NY.8.PXM.a > cnfpnportloscallrel 3:1.1:1 yes8850_NY.8.PXM.a > dsppnportloscallrel 3:1.1:1Deroute Delay: 0 secondsCall release on Los:enabledEnable a call release upon LOS and a deroute delay of 10 seconds for port 1:1.2:2.
8850_NY.8.PXM.a > cnfpnportloscallrel 1:1.2:2 yes -delay 108850_NY.8.PXM.a > dsppnportloscallrel 1:1.2:2Deroute Delay: 10 secondsCall release on Los:enabledcnfpnportncci
Configure Network Call Correlation Identifier—PXM45, PXM1E
The cnfpnportncci command lets you determine the action that PNNI takes on a call correlation identifier. The possible responses to this identifier are:
•
•
•
Note
Syntax
cnfpnportncci <portid> [-action {forward | discard | assign}]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-action
The action that the controller takes on the network call correlation identifier: the choices are "forward," "discard," and "assign." The default is forward.
Related Commands
dsppnportncci
Attributes
cnfpnportrange
Configure Port Range—PXM45, PXM1E
The cnfpnportrange command lets you specify a range of VPIs and VCIs on a port for SVCCs or SVPCs for the purpose of screening calls from another switch. If the VPI or VCI for one of these control channels from another switch does not fall within the range for the called port, the called switch rejects the call.
To use this command, the port must be down (see dnpnport). The maxsvccvpi default of 4095 provides the maximum advantage for negotiation during ILMI auto-configuration. Note that the maxsvccvpi parameter is limited by the highest VPI that the switch assigns (whether the port is a UNI or an NNI).
In addition to the port ID, you must specify at least one keyword for cnfpnportrange.
Syntax
cnfpnportrange <portid> [-minsvccvpi min-svcc-vpi ] [-maxsvccvpi max-svcc-vpi ] [-minsvccvci min-svcc-vci ] [-maxsvccvci max-svcc-vci ] [-minsvpcvpi min-svpc-vpi ] [-maxsvpcvpi max-svpc-vpi ]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-minsvccvpi
The min-svcc-vp: minimum VPI for SVCC.
Range: 0-4095
Default: 0-maxsvccvpi
The max-svcc-vp: maximum VPI for SVCC.
Range: 0-4095
Default: 4095-minsvccvci
The min-svcc-vci: minimum VCI for SVCC.
Range: 0-65535
Default: 35-maxsvccvci
The max-svcc-vci: maximum VCI for SVCC.
Range: 32-65535
Default: 65535-minsvpcvpi
The min-svpc-vp: minimum VPI for SVPC.
Range: 1-4095
Default: 1-maxsvpcvpi
The max-svpc-vp: maximum VPI for SVPC.
Range: 1-4095
Default: 4095
Related Commands
dsppnportrange
Attributes
cnfpnportsig
Configure Port Signaling—PXM45, PXM1E
The cnfpnportsig command lets you specify ATM signaling parameters for a UNI, EVUNI, NNI, or EVNNI port. The port must be down for you to use this command. When a port is first created, its administrative state is down, in which case you do not need to down it. If the port is up, do the following:
1.
2.
3.
The type of interface you specify on the controller must match the interface type that you configure on the slave (either a service module of the PXM1E UNI/NNI back card). On the slave side, specify UNI, NNI, or VNNI. On the controller card, the cnfpnportsig command also has options for specifying the version of an interface type and other parameters that apply to signaling. See the Syntax Description.
A port can be non-signaling or capable of signaling. Only a UNI can be a non-signaling port and terminate SPVCs or SPVPs. A UNI does not necessarily require you to use the cnfpnportsig command. However, if you need to specify a UNI version, use the cnfpnportsig command for this purpose.
The non-signaling ports tend to be at the network edge. As the usage of a node gets closer to the core, more via nodes and NNI ports are configured, and more signaling ports are used. SVCs also require signaling ports. These variations affect the allotment of ports.
In the current release, the controller cards have different resources for maximum ports, as follows:
•
•
•
Syntax
cnfpnportsig <portid> [-univer {uni30 | uni31 | uni40 | q2931 | none | self}] [-nniver {iisp30 | iisp31 | pnni10 | enni | aini}] [-unitype {public | private}] [-addrplan {both | aesa | e164}] [-side {user | network}] [-vpi <vpi>] [-sigvci signalling-vci] [-rccvci routing-vci] [-cntlvc {ip}] [-passalongcap {enable | disable}] [-hopcntgen {enable | disable}] [-vpivcialloc {enable | disable}] [-svcroutingpri <priority> ]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-univer
UNI is the default for a new PNNI port, but no default version exists for UNI. The UNI version can be uni30, uni31, uni40, q2931, none, or self. Note that to change a UNI version, the port must be down. After configuration, up the port by using the uppnport command.
The none choice applies to any port that does not need to run SSCOP protocol (for example, SPVC endpoints).
The self choice applies to voice SVCs.
Note that univer and nniver are mutually exclusive—so the interface at each end of the connection must have the same interface type. Also, the port type on the PNNI controller side must be the same as the slave (through addport ifType, for example).
Default: no default
-nniver
The NNI version: iisp30, iisp31, pnni10, aini, or enni. Note that univer and nniver are mutually exclusive—so the interface at each end of the connection must have the same interface type. Also, the port type on the PNNI controller must be the same as on the slave (through addport ifType on the AXSM, for example).
The default for this parameter is PNNI 1.0. If this version is sufficient, you can forego this parameter. However, to change an NNI version, the port must be down. Remember to up the port by using the uppnport command after completing the cnfpnportsig command.
Default: no default
-unitype
The type of UNI is either private or public. This parameter is relevant only if you specified a UNI interface through the -univer parameter.
Default: no default
-addrplan
The address plan of the calling party that the interface accepts. The choices are both, e164, and aesa. The default is both.
Only a public UNI can use this parameter. For all other interface types, the port automatically accepts either AESA or E.164 address plans.
-side
For the side of the port, type user or network. When you set up PNNI signalling for IISP, one end must be network and one end must be user. If both sides are the same, a configuration error has occurred. This parameter applies to IISP only and public UNI. The network side is the side that assigns the VPI and VCI. (An NNI automatically is the network side.)
See also the cnfenhiisp description for details about enhanced IISP.
Note
Default: network
-vpi
The VPI of the signaling and routing control channel (RCC) on the port.
Range: 0-4095
Default: 0-sigvci
The signaling VCI for the port. If you do not use the default of 5, this VCI must be in the range 32-65535.
Range: 5 or 32-65535
Default: 5-rccvci
The routing control channel-vci: the VCI for PNNI RCC. If you do not use the default of 18, this VCI must be in the range 32-65535.
Range: 18 or 32-65535
Default: 18
-cntlvc
Enable for an IP-based signaling channel. This option applies only to a feeder connected to the switch. An IP-based control channel is mutually exclusive of either UNI or NNI. The only choice for -cntlvc is "ip."
Default: "ip" (for Internet Protocol)
-passalongcap
Pass-along capability: type "enable" or "disable." With this capability, the port has the ability to pass along unrecognized information elements (IEs) or messages. Enabling or disabling the pass-along capability applies to AINI, IISP, and public UNI. For all other types, the port behaves as if pass-along is enabled—you cannot disable pass-along on the other port types.
Default: enable
-hopcntgen
This parameter applies to AINI only. Type the entire word, "enable" or "disable." If you enable hop counting for AINI, the controller generates the hop counter information IE for all setup messages that pass through the interface if this IE does not already exist in the setup message. You must also enable AINI hop count IE for the switch by using the cnfainihopcount command.
Default: enable
-vpivcialloc
This parameter applies to AINI: type "enable" or "disable." If you enable it, the interface becomes responsible for assigning the VPI and VCI for all connections.
Note that if you enable VPI/VCI allocation on one side of the AINI link, allocation must be disabled on the other side of the link,
Default: enable
-svcroutingpri
The -svcroutingpri option lets you specify a default routing priority for a port. This parameter becomes relevant when a setup message for an SVC or SPVC arrives with no PSIE at a node that supports priority routing. For example, the PSIE may have been dropped at a via node that does not support priority routing. In such a situation, the value for svcroutingpri becomes the routing priority for the connection. See the cnfpri-routing description for details on priority routing.
The routing priority is used during de-routing. SVCs and SPVCs are released according to the routing priority. This release prioritization promotes faster re-routing of higher priority connections.
Range: 1-15
Default: 8
Related Commands
dsppnportsig
Attributes
Examples
Specify an RCC VCI of 10000 for port 1:2.1:1. Be sure the interface type is compatible with the parameter you want to change. Do the following:
1.
2.
3.
4.
5.
M8850_NY.7.PXM.a > dsppnport 1:2.1:1Port: 1:2.1:1 Logical ID: 16848897IF status: up Admin Status: upUCSM: enableAuto-config: enable Addrs-reg: enableIF-side: network IF-type: nniUniType: private Version: pnni10PassAlongCapab: n/aInput filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 200minSvccVci: 35 maxSvccVci: 255minSvpcVpi: 1 maxSvpcVpi: 200#SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive:p2p : 0 0 0 0p2mp: 0 0 0 0#Svcc: #Svpc: Total:p2p : 0 0 0p2mp: 0 0 0Total: 0M8850_NY.7.PXM.a > dnpnport 1:2.1:1M8850_NY.7.PXM.a > cnfpnportsig 1:2.1:1 -rccvci 10000M8850_NY.7.PXM.a > dsppnportsig 1:2.1:1provisioned IF-type: nni version: pnni10sigType: private side: networkaddrPlan: aesaVpiVciAllocator: n/a HopCounterGen: n/aPassAlongCapab: n/asigVpi: 0 sigVci: 5rccVpi: 0 rccVci: 10000M8850_NY.7.PXM.a > uppnport 1:2.1:1Take the following steps on a PXM1E for an initial configuration (assume the line has been upped):
1.
2.
3.
4.
5.
6.
7.
8.
PXM1E_SJ.7.PXM.a > addport 2 2.2 10000 10000 0 2PXM1E_SJ.7.PXM.a > addpart 2 2 5 10000 10000 10000 10000 110 220 2000 4000 100 100PXM1E_SJ.7.PXM.a > addpnport 7:2.2:2PXM1E_SJ.7.PXM.a > dsppnport 7:2.2:2Port: 7:2.2:2 Logical ID: n/aIF status: provisioning Admin Status: downVSVD Internal Loop: unspecifiedVSVD External Loop: unspecifiedPXM1E_SJ.7.PXM.a > dsppnportsig 7:2.2:2provisioned IF-type: uni version: nonesigType: private side: networkaddrPlan: aesaVpiVciAllocator: n/a HopCounterGen: n/aPassAlongCapab: n/asigVpi: 0 sigVci: 5rccVpi: n/a rccVci: n/asvc routing priority: 8PXM1E_SJ.7.PXM.a > cnfpnportsig 7:2.2:2 -nniver pnni10PXM1E_SJ.7.PXM.a > dsppnportsig 7:2.2:2provisioned IF-type: nni version: pnni10sigType: private side: networkaddrPlan: aesaVpiVciAllocator: n/a HopCounterGen: n/aPassAlongCapab: n/asigVpi: 0 sigVci: 5rccVpi: 0 rccVci: 18svc routing priority: 8PXM1E_SJ.7.PXM.a > uppnport 7:2.2:2PXM1E_SJ.7.PXM.a > dsppnport 7:2.2:2Port: 7:2.2:2 Logical ID: n/aIF status: provisioning Admin Status: upcnfpnstat
Configure PNNI Statistics—PXM45, PXM1E
Syntax
cnfpnstat {[[-feat {enable | disable}] [-ndlstats {enable | disable}]
[-allintfstats {enable | disable | as-per-each-intf-cfg}]] |
[-intfstats {enable | disable} -port <portid>]}Syntax Description
You must specify at least one parameter.
-feat
This parameter enables or disables PNNI bulk statistics availability for CWM. If this parameter is disabled, no PNNI statistics are not written to the bulk statistics file that CWM reads. For the remaining parameters to have any meaning, this parameter bust be enabled. Type the word "enable" or "disable."
Default: disabled
-ndlstats
This option enables or disables the node-based statistics collection. (See Table 2-12 for the node-based statistics.) For node-level stats to be available to the bulk stats file, -feat must be enabled.
Default: disable
-allintfstats
This option provides an easy way to enable or disable interface-based statistics collection on all ports. (See Table 2-12 for the interface-based statistics.) If this parameter remains disabled, none of the interface-based statistics become available to CWM. Note that if the -allintfstats value is "enable," this enable overrides the per interface enable of the -intfstats parameter. The keyword value "as-per-each-intf-cfg" means that the interface-based statistics are made available based on the configuration for each interface.
The -feat parameter must be enabled for this parameter to have any effect.
Possible entries: enable, disable, as-per-each-intf-cnf
Default: as-per-each-intf-cnf
-intfstats
This option enables or disables the collection of statistics per port. If you enable it, you should also provide a PNNI physical port ID. (See Table 2-12 for the interface-based statistics.) Note that -feat must be enabled for this parameter to have any effect.
Possible entries: disable, enable, and a port ID
Default: disable
Related Commands
dsppnstat
Attributes
Examples
Enable PNNI statistics.
PXM1E_SJ.7.PXM.a > cnfpnstat -feat enableEnable nodel-based PNNI statistics.
PXM1E_SJ.7.PXM.a > cnfpnstat -ndlstats enableDisable interface-based PNNI statistics on port 1:1.2:2.
PXM1E_SJ.7.PXM.a > cnfpnstat -intfstats disable -portid 1:1.2:2Enable interface-based statistics collection based on the per-interface configuration.
PXM1E_SJ.7.PXM.a > cnfpnstat -allintfstats as-per-intf-cfg
