|
|
This chapter introduces you to the CiscoView menus that can be used to manage the BPX SES PNNI node.
The PNNI Controller configuration window provides access to dialogs and tables used to configure a node. The title bar of the CiscoView Main window displays CiscoView Web as shown in Figure 2-1.
The PNNI Controller configuration dialogs and tables are described in Table 2-1.
This section describes the dialogs that support PNNI port configuration.
WAN ATM Port Configuration dialogs contain parameters that affect the operation of the controller interface. There is a single row for each interface that the system will manage. There are two separate dialogs due to size constraints, the WAN ATM Port Configuration dialog (see Figure 2-2) and the WAN ATM Port Creation dialog.
The WAN ATM Port Configuration dialog parameters are described in Table 2-2.
To create a port, select Create from the WAN ATM Port Creation dialog. The WAN ATM Port Creation dialog contains one attribute required for creation of a port as shown in Table 2-3.
| Parameter | Description | ||
|---|---|---|---|
Phys ID | Physical identification of the interface.
|
The More Port Configuration dialog (see Figure 2-3) enables comprehensive port configuration.
The More Port Configuration dialog parameters are described in Table 2-4. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
Port Type | ATM device, either public or private. The default value is private. |
Index | Instance ID to uniquely identify the interface on the local switching system. |
UNI Ver | Displays latest version of the ATM Forum UNI signaling specification on the ATM interface. |
NNI Ver | Displays latest version of the ATM Forum PNNI signaling specification on the ATM interface. |
Phys Id | Physical identification of the interface. This parameter is required when the port is provisioned for the first time through SNMP. |
Port Side | Type of ATM device, either user or network. The default value is network. |
Max P-to-P Calls | Maximum number of point-to-point calls---including VCs and VPs---allowed on the interface. The default value is 10,000. |
Max P-to-MP Calls | Maximum number of point-to-multipoint calls allowed on the interface. |
Max P-to-MP Leaves | Maximum number of leaf VCs (for point-to-multipoint) allowed on the interface, in the range 0 to 65535. The default value is 9,000. |
Min SVC VPI Configured | Minimum SVCC VPI configured on the interface, in the range |
Max SVC VPI Configured | Maximum SVCC VPI configured on the interface, in the range |
Min SVC VCI Configured | Minimum SVCC VCI configured on the interface, in the range |
Max SVC VCI Configured | Maximum SVCC VPI configured on the interface, in the range |
Min SVPC VPI Configured | Minimum SVPC CPI configured on the interface, in the range |
Max SVPC VPI Configured | Maximum SVPC VPI configured on the interface, in the range |
Enhanced ILMI status | Enhanced features for IISP are either enabled or disabled. The default value is disabled. |
The Port Call Incoming Statistics dialog (see Figure 2-4) provides information about calls received by an interface.
The Port Call Incoming Statistics dialog parameters are described in Table 2-5. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
Reset Counters | Value to reset counters. Acceptable values include:
|
Index | Instance ID to uniquely identify the interface on the local switching system. |
No of Incoming Calls | Number of incoming signaling messages (setup and add party) received by the switching node on this interface for call establishment. |
Incoming Calls Established | Number of incoming signaling messages (connect and add party ack) received by the switching node on this interface that indicate successful establishment of a call. |
Incoming Call Failures | Total number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts on this interface. |
Incoming NoFilter Failures | Total number of incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts which failed due to address filtering on this interface. |
Incoming NoRoute failures | Number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts due to address filtering on this interface. |
Incoming NoResource failures | Number of failed incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts on this interface due to insufficient resources, as requested in the call parameters. |
Incoming Timer Failures | Number of signaling timers timed out for incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC calls on this interface. |
Incoming Crankback IEs | Number of crankback IEs received on this interface for incoming point-to-point (p2p) and point-to-multipoint (p2mp) SVC/SPVC call attempts. |
The ATM Port Call Outgoing Statistics dialog (see Figure 2-5) provides information about outgoing signaling statistics on an interface.
The ATM Port Call Outgoing Statistics dialog parameters are described in Table 2-6. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
No of Outgoing Calls | Number of outgoing signaling messages (setup and add party) on this interface for call establishment. |
Port Index | Instance ID to uniquely identify the interface on the local switching system. |
Outgoing Calls Established | Number of outgoing signaling messages (connect and add party ack) that mark the call being established on this interface. |
Outgoing Call Failures | Number of failed outgoing signaling messages for point-to-point (p2p) and point-to-multipoint (p2mp) call establishment on this interface. |
Outgoing NoFilter Failures | Number of failed outgoing signaling messages for call establishment on this interface, due to address filtering. |
Outgoing NoRoute Failures | Number of failed outgoing signaling messages for call establishment on this interface, due to unavailable route. |
Outgoing NoResource Failures | Number of failed outgoing signaling messages for call establishment on this interface, due to unavailable resources. |
Outgoing timer Failures | Number of signaling timers timed-out on this interface for outgoing signaling messages. |
Outgoing Crankback IEs | Number of crankback IEs sent on this interface for outgoing signaling release messages. This is generated on the node that generates the crankback IEs. |
The ATM Port Signaling Statistics (Rcv) dialog (see Figure 2-6) provides statistics on types of messages transmitted from the interface.
The ATM Port Signaling Statistics (Rcv) dialog parameters are described in Table 2-7. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
No of Call Proceeds | Number of call proceeding messages received on this interface. |
Port Index | Instance ID to uniquely identify the interface on the local switching system. |
No of Connects | Number of connect messages received on this interface. |
No of Connect Acks | Number of connect ACK messages received on this interface. |
No of Setup Messages | Number of setup messages received on this interface. |
No of Release Messages | Number of release messages received on this interface. |
No of Release Complete Messages | Number of release complete messages received on this interface. |
No of Restart Messages | Number of restart messages received on this interface. |
No of Restart Act Messages | Number of restart ack messages received on this interface. |
No of Status Messages | Number of status messages received on this interface. |
No of Status Enquiries | Number of Status Enquiry messages received on this interface. |
No of Notify Messages | Number of notify messages received on this interface. |
No of Alerts | Number of alert messages received on this interface. |
No of Progress Messages | Number of progress messages received on this interface. |
No of Add Party Messages | Number of add party messages received on this interface. |
No of Add Party Acks | Number of add party reject messages received on this interface. |
No of Add Party Rejects | Number of add party reject messages received on this interface. |
No of Drop Party Messages | Number of drop party messages received on this interface. |
No of Incorrect Messages | Number of incorrect messages received on this interface. |
Reset Counters | Determines resetting of counters. Possible values include:
|
The Port Signaling Statistics (Xmt) dialog (see Figure 2-7) provides statistics on types of messages transmitted from the interface.
The ATM Port Signaling Statistics (Xmt) dialog parameters are described in Table 2-8. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
No of Call Proceeds | Number of call proceeding messages transmitted from this interface. |
SigPortIndex | Instance ID to uniquely identify the interface on the local switching system. |
No of Connects | Number of connect messages transmitted from this interface. |
No of Connect Acks | Number of Connect ACK messages transmitted from this interface. |
No of Setup Messages | Number of setup messages transmitted from this interface. |
No of Release Messages | Number of release messages transmitted from this interface. |
No of Release Complete Messages | Number of release complete messages transmitted from this interface. |
No of Restarts Messages | Number of restart messages transmitted from this interface. |
No of Restart Acks | Number of restart ack messages transmitted from this interface. |
No of Status Messages | Number of status messages transmitted from this interface. |
No of Status Enquiries | Number of Status Enquiry messages transmitted from this interface. |
No of Notifys | Number of notify messages transmitted from this interface. |
No of Alerts | Number of alert messages transmitted from this interface. |
No of Progress Messages | Number of progress messages transmitted from this interface. |
No of Add Party | Number of add party messages transmitted from this interface. |
No of Add Party Acks | Number of add party ack messages transmitted from this interface. |
No of Add Party Rejects | Number of add party reject messages transmitted from this interface. |
No of Drop Party | Number of drop party messages transmitted from this interface. |
Sscop Link Status | SSCOP link status on an NNI interface, object is meaningful along with ciscoWANSscopLinkChange trap. |
Reset counters | Determines resetting of counters. Possible values include:
|
The ATM Port Load Statistics dialog provides bandwidth statistics for a port. (See Figure 2-8.)
The ATM Port Load Statistics dialog parameters are describ ed in Table 2-9. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
If Bandwidth | Total bandwidth of the interface, in the range 0 to 2147483647. |
Index | Instance ID to uniquely identify the interface on the local switching system. |
Max CBR Bandwidth | Maximum bandwidth for CBR service, in the range |
Max RT VBR Bandwidth | Maximum bandwidth for real time VBR service, in the range |
Max NRT VBR Bandwidth | Maximum bandwidth for non-realtime VBR service, in the range |
Max ABR Bandwidth | Maximum bandwidth for non-realtime VBR service, in the range |
Max UBR BW | Maximum bandwidth for UBR service. |
Avail If BW | Total available bandwidth of the interface, in the range |
Avail CBR BW | Available bandwidth for CBR service, in the range |
Avail RT VBR BW | Available bandwidth for realtime VBR service, in the range |
Avail NRT VBR BW | Available bandwidth for non-realtime VBR service, in the range |
Avail ABR BW | The available bandwidth for ABR service. |
Avail UBR BW | Available bandwidth for ABR service, in the range |
Avail VCs | Available bandwidth for UBR service, in the range |
CBR used VCs | Total number of available VCs of the interface, in the range |
RT VBR used VCs | The number of VCs used by realtime VBR service. |
NRT VBR used VCs | Number of VCs used by non-realtime VBR service, in the range |
ABR used VCs | Number of VCs used by ABR service, in the range |
UBR used VCs | Number of VCs used by UBR service. |
The More Port Load Statistics dialog provides bandwidth statistics for a port. (See Figure 2-9.)
The More Port Load Statistics dialog parameters are described in Table 2-10. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
ABR Cell Transfer Delay | Cell transfer delay of ABR service, in the range 0 to 2147483647. |
UBR Cell Transfer Delay | Cell transfer delay of UBR service, in the range 0 to 2147483647. |
CBR Cell Delay Variation | Cell delay variation of CBR service. |
Index | Instance ID to uniquely identify the interface on the local switching system. |
RT VBR Cell Delay Variation | Cell delay variation of real time VBR service. |
NRT VBR Cell Delay Variation | Cell delay variation of non-realtime VBR service, in the range |
ABR Cell Delay Variation | Cell loss ratio -0 of ABR service. -1 implies N/A. |
UBR Cell Delay Variation | Cell loss ratio -0 of UBR service. -1 implies N/A. |
CBR Cell Loss Ratio-0 | Cell loss ratio -0 of CBR service. -1 implies N/A. |
RT VBR Cell Loss Ratio-0 | Cell loss ratio-1 of realtime VBR service. -1 implies N/A. |
NRT VBR Cell Loss Ratio-0 | Cell loss ratio-1 of non-realtime VBR service. -1 implies N/A. |
ABR Cell Loss Ratio-0 | Cell loss ratio -1 of ABR service. -1 implies N/A. |
UBR Cell Loss Ratio-0 | Cell loss ratio-1 of UBR service. -1 implies N/A. |
CBR Min Gntd Cell Rate | Minimum guaranteed cell rate capacity of CBR service, in the range 0 to 2147483647. |
RT VBR Min Gntd Cell Rate | Minimum guaranteed cell rate capacity of realtime VBR service, in the range 0 to 2147483647. |
NRT VBR Min Gntd Cell Rate | Minimum guaranteed cell rate capacity of non-realtime VBR service, in the range 0 to 2147483647. |
ABR Min Gntd Cell Rate | Minimum guaranteed cell rate capacity of ABR service, in the range 0 to 2147483647. |
UBR Min Gntd Cell Rate | Minimum guaranteed cell rate capacity of UBR service. |
Connection Admission Control (CAC) configuration dialogs provide read-write access to the ciscoWANportCacConfigTable object, which specifies CAC information for each interface. There are three CAC configuration dialogs.
The SVC CAC Configuration dialog provides service-specific bandwidth statistics. (See Figure 2-10.)
The parameters for this dialog are described in Table 2-11. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
CBR Booking | Booking factor for CBR services, in the range 0 to 100. The default value is 100. |
PortIndex | Instance ID to uniquely identify the interface on the local switching system. |
RT VBR Booking | Booking factor for realtime VBR service. |
Non-RT VBR Booking | Booking factor for real time VBR service, in the range 0 to 100. The default value is 100. |
ABR Booking | Booking factor for ABR service, in the range 0 to 100. The default value is 100. |
UBR Booking | Booking factor for UBR service, in the range 0 to 100. The default value is 100. |
Max CBR BW % | Maximum percentage bandwidth for CBR service, in the range |
Max RT VBR BW % | Maximum percentage bandwidth for real time VBR service, in the range 0 to 1000000. The default value is 1000000. |
Max Non-RT VBR BW % | Maximum percentage bandwidth for non-real time VBR service, in the range 0 to 1000000. The default value is 1000000. |
Max ABR BW % | Maximum percentage bandwidth for ABR service, in the range |
Max UBR BW % | Maximum percentage bandwidth for UBR service, in the range |
Min CBR BW % | Minimum percentage bandwidth for CBR, in the range 0 to 1000000. The default value is 0. |
Min RT VBR BW % | Minimum percentage bandwidth for VBR, in the range 0 to 1000000. The default value is 1000000. |
Min Non-RT VBR BW % | Minimum percentage bandwidth for non-real time VBR, in the range |
Min ABR BW % | Minimum percentage bandwidth for ABR, in the range 0 to 1000000. The default value is 1000000. |
Min UBR BW % | Minimum percentage bandwidth for UBR, in the range 0 to 1000000. The default value is 1000000. |
The SVC CAC Configuration VCs (Virtual Connections) dialog provides service-specific virtual connection statistics. (See Figure 2-11.)
The parameters for this dialog are described in Table 2-12. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
Max CBR VCs | Maximum number of VCs for CBR service percentage, in the range 0 to 1000000. The default value is 1000000. |
Index | Instance ID to uniquely identify the interface on the local switching system. |
Max RT VBR VCs | Maximum number of VCs for real time VBR service percentage, in the range 0 to 1000000. The default value is 1000000. |
Max Non-RT VBR VCs | Maximum number of VCs for non-real time VBR service percentage, in the range 0 to 1000000. The default value is 1000000. |
Max ABR VCs | Maximum number of VCs for ABR service percentage, in the range 0 to 1000000. The default value is 1000000. |
Max UBR VCs | Maximum number of VCs for ABR service percentage, in the range 0 to 1000000. The default value is 1000000. |
Min CBR VCs | Minimum number of VCs for CBR service percentage, in the range 0 to 1000000. The default value is 0. |
Min NRT VBR VCs | Minimum number of VCs for real time VBR service percentage, in the range 0 to 1000000. The default value is 0. |
Min Non-RT VBR VCs | Minimum number of VCs for non-real time VBR service percentage, in the range 0 to 1000000. The default value is 0. |
Min ABR VCs | Minimum number of VCs for ABR service percentage, in the range 0 to 1000000. The default value is 0. |
Max UBR VCs | Maximum bandwidth allowed for CBR service on a VC, in the range 0 to 1000000. The default value is 0. |
Max CBR VC BW % | Maximum bandwidth allowed for CBR service on a VC, in the range 0 to 1000000. The default value is 0. |
Max RT VBR VC BW % | Maximum bandwidth allowed for VBR service on a VC, in the range 0 to 1000000. The default value is 1000000. |
Max Non-RT VBR VC BW % | Maximum bandwidth allowed for non-real time VBR on a VC, in the range 0 to 1000000. The default value is 1000000. |
Max ABR VC BW % | Maximum bandwidth allowed for ABR service on a VC, in the range 0 to 1000000. The default value is 1000000. |
Max UBR VC BW % | Maximum bandwidth allowed for UBR service, in the range |
The SVC CAC Configuration Defaults dialog provides service-specific connection default statistics. (See Figure 2-12.)
The parameters for this dialog are described in Table 2-13. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
CBR CDVT | Default CDVT for CBR service. |
Index | Instance ID to uniquely identify the interface on the local switching system. |
RT VBR CDVT | Default CDVT realtime VBR service. |
Non-RT VBR CDVT | Default CDVT non-realtime VBR service. |
ABR CDVT | Default CDVT for ABR service. |
UBR CDVT | Default CDVT for UBR service. |
RT VBR MBS | Default MBS real time VBR service. |
Non-RT VBR MBS | Default MBS non-real time VBR service. |
The Interface ATM Port Addresses Configuration table (see Figure 2-13) contains the parameters necessary to determine what the PNNI entity believes is "reachable" in terms of ATM End System Addresses, and to determine which nodes are advertising this "reachability."
This table is also used to configure static routes to "reachable" addresses. Entries in this table can be created or deleted by setting the intfAddressRowStatus object to appropriate values. Existing entries in this table cannot be modified.
The parameters for this table are described in Table 2-14. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
Address (in Decimal) | ATM end-system address. |
ATM Port Index | Instance ID to uniquely identify the interface on the ATM. |
Length | Address length, in bits, to be applied to the ATM end-system address. |
Type | Type of reachability from the advertising node to the address, either internal or external. Refer to section 5.8.1 in the ATM Forum PNNI 1.0 3 document. |
Proto | Routing mechanism by which the connectivity from the advertising node to the reachable address is learned. Possible values are local or static. |
Plan | Address plan. The first byte of the address automatically implies one of the three NSAP address plans---NSAP E.164, NSAP DCC, or NSAP ICD. |
Scope | PNNI scope of advertisement (level of PNNI hierarchy) of the reachability from the advertising node to the address, in the range 0 to 104. |
Redistribute | Determines if the reachable address is advertised by the local node to its PNNI routing domain. Possible values are true or false. The default value is false. Route must be set to static to use this function. |
The ATM Port Address Creation dialog parameters allow users to create an ATM Address Port. (See Table 2-15.)
| Parameter | Description |
|---|---|
ifIndex | Instance ID to uniquely identify the interface on the local switching system. |
cwspAtmAddress | ATM end-system address. |
cwspAddrLen | Address length (in bits) applied to the ATM End System Address. |
The CWSP Interface Operation Configuration table (see Figure 2-14) contains the runtime negotiated values between platform, PNNI controller, and peer on an interface. An entry in the interface operation table contains negotiated values of an interface.
The parameters for this table are described in Table 2-16. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
Index | Index to the table. |
Operational State | The operational state of ILMI. |
Interface Type | The interface type of an interface. |
Interface Side | The IME type of the ATM device which is concluded from automatic interface type determination procedure. |
Max no of VPCS | The maximum number of switched and permanent VPCs supported on this ATM interface. |
Max no of VCCS | The maximum number of switched and permanent VCCs supported on this ATM interface. |
Max no of Active VPI | The maximum number of active VPI bits on this ATM interface. |
Type | The type of the ATM device, either public or private. |
Version | An indication of the latest version of the ATM Forum UNI Signaling Specification that is supported on this ATM Interface. If this value is not present, a version of the UNI earlier than 3.1 is supported. |
Device Type | It determines the type of the ATM device. ATM End System shall take the value of user(1), and an ATM network node shall take the value of node(2). |
ILMI Version | The latest version of the ATM Forum ILMI Specification that is supported on this ATM Interface. If this object is not present, a version of the ILMI earlier than 4.0 is supported. |
PNNI Routing Version | The latest version of the ATM Forum PNNI Signaling Specification that is supported on this ATM Interface. |
Max switched VPC VPI | Maximum switched VPC VPI. |
Min switched VPC VPI | Minimum switched VPC VPI. |
Max switched VCC VPI | Maximum switched VCC VPI. |
Min switched VCC VPI | Minimum switched VCC VPI. |
Max switched VCC VCI | Maximum switched VCC VCI. |
Min switched VCC VCI | Minimum switched VCC VCI. |
The PNNI Node Configuration table (see Figure 2-15) contains a row for each peer group of which the managed system is expected or eligible to become a member. Refer to the ATM Forum PNNI article, Version 1.0, Annex F.
There are two PNNI Node Configuration tables due to size constraints. These tables are used to configure/delete a PNNI node or modify related parameters for an existing node.
The parameters for the PNNI Node Table are described in Table 2-17. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
PNNI Node Index | A unique value assigned to a node in this switching system. |
PNNI Node Level | The level of PNNI hierarchy of the node. This attribute is used to determine the default node ID and the default peer group ID for the node. This object may only be written when the PNNI Node Admin Status has the value down. |
PNNI Node ID | The value the switching system is using to represent itself as this node. This object may only be written when pnniNodeAdminStatus has the value down. If pnniNodeLowest is true, then the default node ID takes the form defined for lowest level nodes, with the first octet equal to pnniNodeLevel, the second octet equal to 160, and the last 20 octets equal to pnniNodeAtmAddress. If pnniNodeLowest is false, then the default node ID takes the form defined for logical group nodes, with the first octet equal to pnniNodeLevel, the next fourteen octets equal to the value of pnniNodePeerGroupId for the child node whose election as PGL causes this LGN to be instantiated, the next six octets equal to the ESI of pnniNodeAtmAddress, and the last octet equal to zero. |
Lowest Node | Indicates whether this node acts as a lowest level node or whether this node is a logical group node that becomes active when one of the other nodes in this switching system becomes a peer group leader. The value false must not be used with nodes that are not PGL/LGN capable. This object may only be written when pnniNodeAdminStatus has the value down. |
Admin Status | Indicates whether the administrative status of the node is up (the node is allowed to become active) or down (the node is forced to be inactive). When pnniNodeAdminStatus is down, then pnniNodeOperStatus must also be down. |
Operating Status | Indicates whether the node is active or whether the node has yet to become operational. When the value is down, all state has been cleared from the node and the node is not communicating with any of its neighbor nodes. |
Routing Domain | Name of the PNNI routing domain in which this node participates. All lowest-level PNNI nodes with the same pnniNodeDomainName are presumed to be connected. |
End system Addr | This node's ATM End System Address. Remote systems wishing to exchange PNNI protocol packets with this node should direct packets or calls to this address. This attribute may only be written when pnniNodeAdminStatus has the value down. |
Peer Group id | Peer Group Identifier of the peer group that a specific node is to become a member of. The default value of this attribute has the first octet equal to pnniNodeLevel, the next pnniNodeLevel bits equal to the pnniNodeLevel bits starting from the third octet ofpnniNodeId, and the remainder padded with zeros. This object may only be written when pnniNodeAdminStatus has the value down. |
The PNNI Node Creation dialog specifies the parameters needed to create a PNNI node. The parameters for this dialog are described in Table 2-18.
| Parameter | Description |
|---|---|
Node Index | Unique value assigned to a node in this switching system. |
pnninode level | Level of PNNI hierarchy at which this node exists. This attribute is used to determine the default node ID and the default peer group ID for this node. This object may be written only when pnniNodeAdminStatus has the value down. |
The More PNNI Node Configuration dialog (see Figure 2-16) provides more parameters to create a PNNI node.
These parameters are described in Table 2-19.
| Parameter | Description |
|---|---|
PNNI Node Index | Unique value assigned to a node in this switching system. |
SVCs Restrict | Specifies whether the node is restricted to not allowing support of SVCs transiting this node. This attribute determines the setting of the restricted transit bit in the nodal information group originated by this node. |
Branches Restrict | Indicates whether the node is able to support additional point-to-multipoint branches. A value of false indicates that additional branches can be supported. A value of true indicates that additional branches cannot be supported. This attribute reflects the setting of the restricted branching bit in the nodal information group originated by this node. |
Complex Rep | Specifies whether this node uses the complex node representation. A value of true indicates that the complex node representation is used. A value of false indicates that the simple node representation is used. This attribute determines the setting of the nodal representation bit in the nodal information group originated by this node. |
DB Overload | Specifies whether the node is currently operating in topology database overload state. This attribute has the same value as the Non-transit for PGL Election bit in the nodal information group originated by this node. |
PTSES | Gauges the total number of PTSEs currently in this node's topology database(s). |
The PNNI PGL (Peer Group Leader) Configuration table (see Figure 2-17) provides access to Peer Group Leader election information for a PNNI node in this switching system. The pnniNodePglTable augments the pnniNodeTable. Refer to Section 5.10.1 of the ATM Forum PNNI document, Version 1.0.
The parameters for this table are described in Table 2-20. Some parameters are only visible by using the scroll bar.
| Parameter | Description |
|---|---|
PNNI Node Index | Value assigned to a node in this switching system that uniquely identifies it in the MIB. |
PGL Leadership Priority | The Leadership priority value this node should advertise in its nodal information group for the given peer group. Only the value zero can be used with nodes that are not PGL/LGN capable. If there is no configured parent node index or no corresponding entry in the pnniNodeTable, then the advertised leadership priority is zero regardless of this value. |
Parent Node Index | The local node index used to identify the node that represents this peer group at the next higher level hierarchy, if this node becomes peer group leader. Value 0 indicates that there is no parent node. |
Init Delay | The amount of time in seconds this node will delay advertising its choice of preferred PGL after having initialized operation and reached the full state with at least one neighbor in the peer group. |
Override Delay | The amount of time in seconds a node will wait for itself to be declared the preferred PGL by unanimous agreement among its peers. In the absence of unanimous agreement this will be the amount of time that will pass before the node considers a two thirds majority as sufficient agreement to declare itself peer group leader, abandoning the attempt to get unanimous agreement. |
Reelect Time | The amount of time in seconds after losing connectivity to the current peer group leader that this node will wait before re-starting the process of electing a new peer group leader. |
Election State | The state that this node is in with respect to the peer group leader election that takes place in the node's peer group. The values are enumerated in the peer group leader state machine. |
Preferred PGL | The Node ID of the node that the local node believes would be or becomes the peer group leader. This is also the value the local node is currently advertising in the "preferred peer Group Leader Node ID field of its nodal information group within the given peer group. If a Preferred PGL has not been chosen, this attribute's value is set to (all) zero(s). |
PGL | The Node Identifier of the node that is currently operating as peer group leader of the peer group this node belongs to. If a PGL has not been elected, this attribute's value is set to (all) zero(s). |
PGL Time Stamp | The time at which the current Peer Group Leader established itself. |
Parent Node ID | The Node Identifier value being used by the Peer Group Leader to represent this peer group at the next higher level of the hierarchy. If this node is at the highest level of the hierarchy or if no PGL has yet been elected the PNNI Protocol Entity sets the value of this attribute to (all) zero(s). |
The PNNI Address Summary table(see Figure 2-18) is used to specify a list of the summary address prefixes that may be advertised by the specified logical PNNI entity. The pnniSummaryRowStatus is used to create, delete, activate, and de-activate a summary.
The parameters for this dialog are described in Table 2-21.
| Parameter | Description |
|---|---|
Type | The type of summary (Internal or Exterior) described. |
PNNI Node Index | A unique value assigned to a node in the switching system. |
End System Addr Prefix | The ATM end system address prefix for the summary. |
Prefix Length | The prefix length for the summary. |
Suppression | Determines what is done with addresses that are being summarized by the instance. The default value will indicate that the summary should propagate into the peer group. Network management will be able to set the value of this attribute to suppress, which suppresses the summary and any reachable addresses it summarizes from being advertised into the peer group. |
State | Indicates whether the summary is currently being advertised by the node within the local switching system into its peer group. |
The PNNI Summary Address Prefix Creation dialog is used to create a PNNI summary address prefix. The parameters for this dialog are described in Table 2-22.
| Parameter | Description |
|---|---|
Index | A unique value assigned to a node in this switching system. |
Type | The type of summary (Internal or Exterior) described. |
End System Addr Prefix | The ATM end system address prefix for the summary. |
Prefix Length | The prefix length for the summary. |
The PNNI Base Group Configuration dialog (see Figure 2-19) defines the PNNI Base Group.
The parameters for this dialog are described in Table 2-23.
| Parameter | Description |
|---|---|
Highest Version | The highest version of the PNNI protocol that the software in this switching system is capable of executing. |
Lowest Version | The lowest version of the PNNI protocol that the software in this switching system is capable of executing. |
DTL Count Originator | The total number of DTL stacks that this switching system has originated as the DTL Originator and placed into signaling messages. This includes the initial DTL stacks computed by this system as well as any alternate route (second, third choice) DTL stacks computed by this switching system in response to crank backs. |
DTL Count Border | The number of partial DTL stacks that this switching system has added into signaling messages as an entry border node. This includes the initial partial DTL stacks computed by this system as well as any alternate route (second, third, choice, etc.) partial DTL stacks computed by this switching system in response to crank backs. |
Crankback Count Originator | The count of the total number of connection setup messages including DTL stacks originated by this switching system that have cranked back to this switching system at all levels of the hierarchy. |
Crankback Count Border | The count of the total number of connection setup messages including DTLs added by this switching system as an entry border node that have cranked back to this switching system at all levels of the hierarchy. This count does not include Crankbacks for which this switching system was not the crankback destination, only those crankbacks that were directed to this switching system are counted here. |
Alternate Route Count Originator | The count of the total number of connection setup messages including DTLs added by this switching system as an entry border node that have cranked back to this switching system at all levels of the hierarchy. This count does not include Crank backs for which this switching system was not the crank back destination, only those crank backs that were directed to this switching system are counted here. |
Alternate Route Count Border | Total number of alternate DTL stacks that this switching system has computed and placed into signaling messages as the DTL originator. |
Route Fail Count Originator | Total number of times where the switching system failed to compute a viable DTL stack as the DTL originator for some call. It indicates the number of times a call was cleared from this switching system due to originator routing failure. |
Route Fail Count Border | Total number of times where the switching system failed to compute a viable partial DTL stack as an entry border node for some call. It indicates the number of times a call was either cleared or cranked back from this switching system due to border routing failure. |
Route Fail Unreachable Originator | Total number of times where the switching system failed to compute a viable DTL stack as the DTLOriginator because the destination was unreachable. |
Route Fail Unreachable Border | The total times the switching system failed to compute a viable partial DTL stack as an entry border node because the target of the path calculation was unreachable. That is, those calls that are cleared or cranked back with either number 2, specified transit network unreachable, or cause number 3, destination unreachable, specified in the cause. |
Posted: Thu May 18 15:37:38 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.
