CISCO-WAN-SVC-MIB: View SNMP OID List / Download MIB

The MIB modules describe an ATM network service on a BPX-SES or a MGX ATM switch. This MIB module provides configuring, provisioning, as well as status gathering for ATM services. Abbreviation used: ABR -- Available Bit Rate AINI -- ATM Inter-Network Interface ATM -- Asynchronous Transfer Mode BGN -- Begin BW -- Bandwidth CBR -- Constant Bit Rate ENNI -- Enhanced Network to Network Interface Note: The 'ENNI' term used here indicating 'enhanced' or 'friendly' NNI for linking two networks of CISCO AutoRoute or PNNI switches. The XPVCs and XPVPs are provisioned across them. Functionality includes changing segment OAM cell handling so that these cells flow over 'end-to-end OAM segment' loops for the provisioned length of the XPVC or XPVP, i.e. the 'segment' comprises the two or three segments between the user ports. Also implemented at ENNIs is an LMI functionality that enables auto-discovery of the ENNIs. ER -- Error Recovery GAT -- Generic Application Transport IE -- Information Element IISP -- Interim Inter-Switch Signaling Protocol ILMI -- Interim Local Management Interface MD -- Management Data PNNI -- Private Network-Network Interface RS -- Resynchronization REJ -- Rejection SD -- Sequence Data SDP -- Sequence Data with Poll SPVC -- Soft Permanent Virtual Circuit SSCOP -- Service Specific Connection Oriented Protocol SVC -- Switched Virtual Circuit UBR -- Unspecified Bit Rate UD -- Unit Data UNI -- User-Network Interface USTAT -- Unsolicited STAT VBR -- Variable Bit Rate

PNNI network controller software revision number.

The administrative status for the pnni active controller.

The administrative status for the standby controller.

The administrative status of the pnni controller. Note: this object is only used in the trap varbind, snmp get operation is meaningless. Enumeration: 'active': 1, 'stndby': 2, 'unavailable': 3.

The pnni controller physical location for MGX or BPX-SES. Note: this object is only used in the trap varbind, snmp get operation is meaningless.

The Interface configuration table collects attributes that affect the operation of the controller interface. There is a single row for each interface that the managed system is expected to be added or managed.

An entry in the interface configuration table containing information about an interface

The administrative status of the interface. inService (1) means that the interface is operational while outService (2) indicates that the interface is put out of service by the administrator. Enumeration: 'outService': 2, 'inService': 1.

The operational state of the interface. This status is derived from the physical state of the interface. failed (2) indicates that the interface has failed. ok (1) indicates that the interface is in operational status, while other (3) denotes that the interface is in an unknown state. Enumeration: 'failed': 2, 'other': 3, 'ok': 1.

Indicates whether Switches virtual connections are allowed through this interface.

Indicates whether soft permanent virtual connections are allowed through this interface.

Indicates whether ILMI address registration is enabled or disabled.

Indicates whether auto-configuration of the interface is turned on or off. If auto-configuration is enabled, then the interface comes up using the ILMI auto-configuration.

Indicates whether service registry is enabled or disabled on the interface.

Indicates the physical identification of the interface. Mandatory when the port is provisioned for the first time through SNMP.

Denotes the Signaling VPI used on the interface.

Indicates the signaling VCI used on the interface, acceptable value is 32-65535, and 5 being the default.

Indicates the VPI used for PNNI lowest level RCC.

Indicates the VCI used for the PNNI lowest level RCC, acceptable value is 32-65535, and 18 being the default.

The maximum number of active VPI bits on this ATM Interface. For virtual interfaces (i.e. Virtual Path Connections used by PNNI), this value has no meaning and is set to zero.

The maximum number of active VCI bits on this ATM Interface.

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. The value of 'self(9)' indicates this entry is a voice port. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. Enumeration: 'uni20': 1, 'frf4': 6, 'uni31': 3, 'ip': 8, 'self': 9, 'uni30': 2, 'unsupported': 7, 'ituDss2': 5, 'uni40': 4.

An indication of the latest version of the ATM Forum PNNI Signaling Specification that is supported on this ATM Interface. Note that the PNNI routing version is not determined through ILMI. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. Enumeration: 'iisp30': 1, 'enni': 4, 'unsupported': 7, 'aini': 5, 'pnni10': 3, 'iisp31': 2.

The type of the ATM device, either public or private. Enumeration: 'public': 1, 'private': 2.

This object determines the type of the ATM device. This object is used in automatic ATM Interface-Type determination procedure such that a correct operational ATM Interface-type can be determined. An ATM End System shall take the value of user(1), and an ATM network node shall take the value of node(2). Enumeration: 'user': 1, 'network': 2.

Indicates the maximum number of point to point calls (including VCs and VPs allowed on the interface.

Indicates the maximum number of root VCs (for point-to-multipoint) allowed on the interface.

Indicates the maximum number of leaf VCs (for point-to-multipoint) allowed on the interface.

Indicates the minimum SVCC VPI configured on the interface.

Indicates the maximum SVCC VPI configured on the interface.

Indicates the minimum SVCC VCI configured on the interface.

Indicates the maximum SVCC VCI configured on the interface.

Indicates the minimum SVPC VPI configured on the interface.

Indicates the maximum SVPC VPI configured on the interface.

Indicates whether the enhanced features for IISP are enabled or disabled.

Used to create and delete the Interface. However, only createAndGo, destroy, active and notInService are supported. NMS should only use createAndGo to create a row and destroy to delete a row. The managed device will either return active or notInService for a row status.

The ATM address plan supported on an interface. This can only be modified if interface is public UNI. For all other interfaces, the value is aesa. Enumeration: 'both': 1, 'e164': 3, 'aesa': 2.

Indicates whether ILMI Secure Link Protocol is enabled or disabled. When secure link protocol is enabled, loss in ILMI connectivity is treated as loss of attachment point which results in all SVCs/SVPs being released on the interface.

Indicates whether detection of loss of attachment procedures are enabled on this interface. When set to true, then standard ILMI procedures are employed to detect loss of attachment point. If set to false, then ILMI protocol on the interface does not detect the loss of attachment.

Indicates whether on modification of local attributes, procedures as recommended by ILMI 4.0 specification are followed or cisco proprietery procedures are followed. When set to true, the standard ILMI procedures are followed.

Indicates whether ILMI user connection status monitoring is enabled or disabled.

This object is the routing priority to be assigned to connections which enter the network from this ingress interface, but does not carry the routing priority signaling in the SETUP message. SETUP message. A default routing priority of 8 is used if this object is not configured. A routing priority 1 is the highest priority for a user connection. A connection tagged with a routing priority of 1 is derouted ahead of connections tagged with other priority values.

This object identifies the internal NSAP assigned to a port by the switch. a) The format is that of 13-byte node prefix and 7-byte port number. b) When the switch's node prefix is modified, the node prefix part of this variable is also changed accordingly. Note: the switch's node prefix cannot be changed if there are connections on the switch. c) The port number can be physical port identifier or the ifIndex of this port.

A table specifying the CAC(Connection Admission Control) information for each interface.

An entry contains CAC information.

This is the booking factor for CBR service.

This is the booking factor for real time VBR service

This is the booking factor for non-real time VBR service

This is the booking factor for ABR service

This is the booking factor for UBR service.

This is the maximum bandwidth for CBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum bandwidth for real time VBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum bandwidth for non-real time VBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum bandwidth for ABR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum bandwidth for UBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum bandwidth for CBR service in percentage. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum bandwidth for real time VBR service in percentage. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum bandwidth for non-real time VBR service in percentage. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum bandwidth for ABR service in percentage. The total values of cwspMinBwCbr, cwspMinBwRtVbr, cwspMinBwNrtVbr, cwspMinBwAbr and cwspMinBwUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum bandwidth for UBR service in percentage. The value for this variable is always 0.

This is the maximum number of VCs for CBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum number of VCs for real time VBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum number of VCs for non-real time VBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum number of VCs for ABR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum number of VCs for UBR service in percentage. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum number of VCs for CBR service in percentage. The values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000, i.e. 100%. This variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum number of VCs for real time VBR service in percentage. The values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum number of VCs for non-real time VBR service in percentage. The values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr,cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum number of VCs for ABR service in percentage. The values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the minimum number of VCs for UBR service in percentage. The values of cwspMinVcCbr, cwspMinVcRtVbr, cwspMinVcNrtVbr, cwspMinVcAbr and cwspMinVcUbr can not exceed 1000000, i.e. 100%. The value of this variable is interpreted in the format of xxx.xxxx. For example a value of 750000 is interpreted as 75.0000%.

This is the maximum bandwidth allowed for a VC for real time CBR service. The value is in the unit of cells per second.

This is the maximum bandwidth allowed for a VC for real time VBR service. The value is in the unit of cells per second.

This is the maximum bandwidth allowed for a VC for non-real time VBR service. The value is in the unit of cells per second.

This is the maximum bandwidth allowed for a VC for ABR service. The value is in the unit of cells per second.

This is the maximum bandwidth allowed for UBR service. The value is in the unit of cells per second.

This is the default CDVT for CBR service.

This is the default CDVT real time VBR service.

This is the default CDVT non-real time VBR service.

This is the default CDVT for ABR service.

This is the default CDVT for UBR service.

This is the default MBS real time VBR service.

This is the default MBS non-real time VBR service.

This table specifies signaling configuration parameters.

An entry in the signaling configuration table. Each entry indexed by the ifIndex of a port.

Timer started when ALERT message received at Call Received State. Normally, timer is stopped when CONNECT message is received. Clear call at first expiry.

Timer started when SETUP message sent at Call Present State. Normally, timer is stopped when ALERT, CONNECT, RELEASE COMPLETE or CALL PROCEEDING message is received. Resend SETUP message and restart the timer at first expiry; Clear network connection and enter NULL state at second expiry.

Timer started when RELEASE message sent at Release Indication State. Normally, timer is stopped when RELEASE COMPLETE or RELEASE message is received. Resend RELEASE and restart the timer at first expiry; Release call reference and enter NULL state at second expiry.

Timer started when CALL PROCEEDING message received at Incoming Call Proceeding State. Normally, timer is stopped when ALERT, CONNECT or RELEASE message is received. Clear call at first expiry. Range from 10 to 20 seconds for UNI 3.0/3.1 with default of 10; 30 to 120 seconds for UNI 4.0 with default of 30, default number can be 10 or 30, 10 is used.

Timer started when RESTART message sent Restart Request State. Normally, timer is stopped when RESTART ACK message is received. RESTART may be sent multiple times in both first or second expiry.

Timer started when RESTART message received at Restart State. Normally, timer is stopped when Internal clearing of call references happen. Maintenance notification at first expiry. The value of this timer should be less than T316.

Timer started when STATUS ENQUIRY message sent at any call state. Normally, timer is stopped when STATUS RELEASE or RELEASE COMPLETE message is received. STATUS ENQUIREY message may be resent several times in both first or second expiry.

Timer started when ALERTING or PARTY ALERTING message received in point-to-multipoint call. Normally timer is stopped when ADD PARTY ACK message is received. Clear party at first expiry.

Timer is started when DROP PARTY message sent at Drop Party Initiated State. Normally, timer is stopped when DROP PARTY ACK or RELEASE message is received. Send DROP PARTY ACK or RELEASE at first expiry.

Timer is started when ADD PARTY message sent at Add Party Initiated State. Normally, timer is stopped when ADD PARTY ACK, ADD PARTY REJ or RELEASE message is received. Clear the party and enter NULL Party State at first expiry. Range from 14 to 28 seconds for UNI 3.0/3.1 with default of 14; 34 to 124 seconds for UNI 4.0 with default of 34, default can be 14 or 34, 14 is used.

This table specifies SSCOP (Layer 2) configuration parameters.

An entry in the SSCOP configuration table. Each entry indexed by the ifIndex of a port.

This object contains the value for Connection control timer.

This object contains the value for keep alive timer

This object contains the value for no response timer.

This object contains the value for poll timer.

This object contains the value for idle timer.

This object contains the upper limit for the number of transmissions of a BGN, END, ER or RS PDU.

This object contains an upper limit for a counter which counts the number of SD PDUs transmitted between transmissions of POLL PDUs or the number of SD PDUs transmitted before the transmission of the first POLL PDU after POLL timer became active.

This object contains an upper limit for the number of list elements placed in a STAT PDU.

This Table contains objects showing the Statistics for SVC/SPVC calls on a given interface.

An entry contains SVC/SPVC call statistics

Writing a 2 to this object resets all counters. Enumeration: 'reset': 2, 'noop': 1.

This object shows the number of incoming Signaling messages (Setup and Add Party) received by the switching node on this interface for Call establishment.

This object shows the number of incoming Signaling Messages (Connect and Add Party Ack) received by the switching node on this interface which marks that a call has been successfully established.

This object shows the total number of incoming Point-to-Point (p2p) and Point-to-MultiPoint(p2mp) SVC/SPVC call attempts failed on this interface.

This object shows the 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.

This object shows the number of incoming Point-to-Point(p2p) and Point-to-MulitPoint(p2mp) SVC/SPVC call attempts on this interface which failed because there was no route to the destination available.

This object shows the number of incoming Point-to-Point(p2p) and Point-to-MulitPoint(p2mp) SVC/SPVC call attempts on this interface which failed because there were not enough resources as requested in the parameters of the call.

This object shows the number of signaling timers timed out for incoming Point-to-Point(p2p) and Point-to-MultiPoint(p2mp) SVC/SPVC calls on this interface.

This object shows the number of Crankback IEs received on this interface for incoming Point-to-Point(p2p) and Point-to-MultiPoint (p2mp) SVC/SPVC call attempts.

This object shows the number of outgoing Signaling messages (Setup and Add Party) on this interface for Call establishment.

This object shows the number of outgoing Signaling messages (Connect and Add Party Ack) which mark the call being established on this interface

This object shows the total number of outgoing Signaling messages for Point-to-Point and Point-to-MultiPoint call establishment on this interface which failed.

This object shows the number of outgoing Signaling messages for call establishment on this interface which failed the address filtering.

This object shows the number of outgoing Signaling messages for call establishment on this interface which failed because the route was not available.

This object shows the number of outgoing Signaling messages for call establishment on this interface which failed because the resource requested was not available.

This object shows the number of Signaling timers timed-out on this interface for outgoing signaling messages.

This object shows the number of Crankback IEs being sent on this interface for outgoing signaling Release messages. This is generated on the node which generates the Crankback IEs.

This table contains signaling statistics counters

An entry contains signaling statistics.

Writing a 2 to this object resets the all Sig counters. Enumeration: 'reset': 2, 'noop': 1.

Number of CALL PROCEEDING messages received on this interface.

Number of CONNECT messages received on this interface.

Number of CONNECT ACK messages received on this interface.

Number of SETUP messages received on this interface.

Number of RELEASE messages received on this interface.

Number of RELEASE COMPLETE messages received on this interface.

Number of RESTART messages received on this interface.

Number of RESTART ACK messages received on this interface.

Number of STATUS messages received on this interface.

Number of STATUS ENQUIRY messages received on this interface.

Number of NOTIFY messages received on this interface.

Number of ALERT messages received on this interface.

Number of PROGRESS messages received on this interface.

Number of ADD PARTY messages received on this interface.

Number of ADD PARTY ACK messages received on this interface.

Number of ADD PARTY REJECT messages received on this interface.

Number of DROP PARTY messages received on this interface.

Number of Incorrect messages received on this interface.

Number of timeouts occurred on this interface.

to indicate the last cause of release or cranckback.

to indicate the last diagnostic of release or cranckback.

Number of CALL PROCEEDING messages transmitted from this interface.

Number of CONNECT messages transmitted from this interface.

Number of CONNECT ACK messages transmitted from this interface.

Number of SETUP messages transmitted from this interface.

Number of RELEASE messages transmitted from this interface.

Number of RELEASE COMPLETE messages transmitted from this interface.

Number of RESTART messages transmitted from this interface.

Number of RESTART ACK messages transmitted from this interface.

Number of STATUS messages transmitted from this interface.

Number of STATUS ENQUIRY messages transmitted from this interface.

Number of NOTIFY messages transmitted from this interface.

Number of ALERT messages transmitted from this interface.

Number of PROGRESS messages transmitted from this interface.

Number of ADD PARTY messages transmitted from this interface.

Number of ADD PARTY ACK messages transmitted from this interface.

Number of ADD PARTY REJECT messages transmitted from this interface.

Number of DROP PARTY messages transmitted from this interface.

Sscop link status on an NNI interface, object is meaningful along with ciscoWANSscopLinkChange trap. Enumeration: 'down': 2, 'up': 1.

This table contains SSCOP (Layer 2) statistics counters.

An entry contains SSCOP (Layer 2) statistics.

This object specifies whether the SSCOP statistics collected for this interface needs to be reset. Enumeration: 'reset': 2, 'noop': 1.

This object stores the number of SSCOP PDUs that are received but ignored due to incorrect size, invalid PDU, unknown PDU type.

This object stores the number of SSCOP BGN PDUs received at this interface.

This object stores the number of SSCOP BGN ACK PDUs received at this interface.

This object stores the number of SSCOP END PDUs received at this interface.

This object stores the number of SSCOP END ACK PDUs received at this interface.

This object stores the number of SSCOP RS(Resync) PDUs received at this interface.

This object stores the number of SSCOP RS(Resync) ACK PDUs received at this interface.

This object stores the number of SSCOP BGN REJ PDUs received at this interface.

This object stores the number of SSCOP SD (Sequenced Data) PDUs received at this interface.

This object stores the number of SSCOP SDP (Sequenced Data with Poll) PDUs received at this interface.

This object stores the number of SSCOP POLL PDUs received at this interface.

This object stores the number of SSCOP STAT PDUs received at this interface.

This object stores the number of SSCOP USTAT (Unsolicited STAT) PDUs received at this interface.

This object stores the number of SSCOP UD (Unit data) PDUs received at this interface.

This object stores the number of SSCOP MD (Management data) PDUs received at this interface.

This object stores the number of SSCOP ER ACK (error recovery ack) PDUs received at this interface.

This object stores the number of SSCOP BGN PDUs transmitted over this interface.

This object stores the number of SSCOP BGN ACK PDUs transmitted on this interface.

This object stores the number of SSCOP END PDUs transmitted on this interface.

This object stores the number of SSCOP END ACK PDUs transmitted on this interface.

This object stores the number of SSCOP RS (Resync) PDUs transmitted over this interface.

This object stores the number of SSCOP RS (Resync) ACK PDUs transmitted over this interface.

This object stores the number of SSCOP BGN REJ PDUs transmitted over this interface.

This object stores the number of SSCOP SD transmitted over this interface.

This object stores the number of SSCOP SDP PDUs transmitted over this interface.

This object stores the number of SSCOP POLL PDUs transmitted over this interface.

This object stores the number of SSCOP STAT PDUs transmitted over this interface.

This object stores the number of SSCOP USTAT PDUs transmitted over this interface.

This object stores the number of SSCOP UD PDUs transmitted over this interface.

This object stores the number of SSCOP MD PDUs transmitted over this interface.

This object stores the number of SSCOP ER(error recovery) ACK PDUs transmitted over this interface.

This Table contains the objects which show parameters associated with a Point-to-Point(p2p) or Point-to-MultiPoint (p2mp) SVC/SPVC call.

This object shows the multiple key index to get the Call record information. The key comprise of Interface Index, VPI/VCI value and Call Reference Value for the call.

This object shows the VPI value of the call on this interface.

This object shows The VCI value of the call on this interface. The value should be in the range of 32-65535 (0=SPVP).

This object shows the value of the Leaf Reference (EndPointReference) of the Call on this interface.

This object shows the Call Reference value of the call on this interface.

This object shows the Calling Party Address of the call.

This object shows the Called Party Address of the call.

This object shows the Calling Party Subaddress of the call.

This object shows the Called Party Subaddress of the call.

This object shows the Other Interface of the call. Generally, this would be the outgoing/egress interface for the call.

This object shows the VPI of the call on the partner interface.

This object shows The VCI of the call on the partner o interface. The value should be in the range of 32-65535 (0=SPVP).

This object shows the Call Reference of the call on the partner interface.

This object shows the Call Type for the call on this interface. The call type could be SVC or SPVC. Enumeration: 'spvc': 2, 'svc': 1.

This object shows the start time of the call. This is the timestamp when the Setup Message (or Add Party Message) was first received on this interface.

This object shows the Bearer Class of the Call. It could be BcobA, BcobC, BcobX or VP Service Enumeration: 'bcobC': 2, 'vp': 4, 'bcobA': 1, 'bcobX': 3.

This object shows the service category of the call, which can be CBR, rtVBR, nrtVBR, ABR or UBR Enumeration: 'cbr': 1, 'rtVbr': 2, 'abr': 4, 'ubr': 5, 'nrtVbr': 3.

This object shows the Cast Type of the call, which can be a Point-to-Point (p2p), Point-to-MultiPoint (p2mp) or MultiPoint-to-Point (mp2p) call. Enumeration: 'mp2p': 3, 'p2p': 1, 'p2mp': 2.

This object shows Susceptibility to Clipping. It can be susceptible or not susceptible. Enumeration: 'yes': 1, 'no': 2.

This object shows the conformance of the call to the traffic sets in the forward direction. It can be CBR.1, CBR.2, CBR.3, VBR.1 VBR.2, VBR.3, ABR, UBR.1 or UBR.2. This is as defined in ATMF Traffic Management 4.0 specification. Enumeration: 'vbr2': 5, 'vbr3': 6, 'vbr1': 4, 'cbr1': 1, 'cbr3': 3, 'cbr2': 2, 'abr': 7, 'ubr2': 9, 'ubr1': 8.

This object shows the Peak Cell Rate(pcr) in the forward direction of the call.

This object shows the Sustainable Cell Rate(scr) in the forward direction of the call.

This object shows the Maximum Burst Size(mbs) of the call in the forward direction.

This object shows the Cell Delay Variation Tolerance(cdvt) in the forward direction for the call, for PCR and SCR.

This object shows if the Frame Discard is enabled or disabled in the forward direction for the call Enumeration: 'yes': 1, 'no': 2.

This object shows the conformance of the call to the traffic sets in the backward direction. It can be CBR.1, CBR.2, CBR.3, VBR.1 VBR.2, VBR.3, ABR, UBR.1 or UBR.2. This is as defined in ATMF Traffic Management 4.0 specification. Enumeration: 'vbr2': 5, 'vbr3': 6, 'vbr1': 4, 'cbr1': 1, 'cbr3': 3, 'cbr2': 2, 'abr': 7, 'ubr2': 9, 'ubr1': 8.

This object shows the Peak Cell Rate in the backward direction of the call.

This object shows the Sustainable Cell Rate in the backward direction of the call.

This object shows the Maximum Burst Size of the call in the backward direction.

This object shows the Cell Delay Variation Tolerance in the backward direction for the call, for PCR and SCR.

This object shows if the Frame Discard is enabled or disabled in the backward direction for the call. Enumeration: 'yes': 1, 'no': 2.

This object shows the Maximum Cell Transfer Delay for the call on this interface.

This object shows the Maximum Cell Delay Variation in the forward direction for this call on this interface.

This object shows the Maximum Cell Loss Ratio in the forward direction for this call on this interface.

This object shows the Maximum Cell Delay Variation in the backward direction for this call on this interface.

This object shows the Maximum Cell Loss Ratio in the backward direction for this call on this interface.

This table contains information for ABR calls on an interface.

An entry in the table, containing information about an ABR call.

The VPI value of the ABR call on this interface.

The VCI value of the ABR call on this interface. The value should be in the range of 32-65535 (0=SPVP).

The Call Reference value of the ABR call on this interface.

The Calling Party Address of the ABR call.

The Called Party Address of the ABR call.

The Calling Party Subaddress of the ABR call.

The Called Party Subaddress of the ABR call.

The Other Interface ID of the ABR call. Generally this would be the outgoing/egress interface for the call.

The VPI value of the ABR call on the partner interface.

The VCI value of the ABR call on the partner interface. The value should be in the range of 32-65535 (0=SPVP).

The Call Reference of the ABR call on the partner interface.

The Call Type for the ABR call on this interface. The call type could be SVC or SPVC. Enumeration: 'spvc': 2, 'svc': 1.

The start time of the ABR call. This is the timestamp when the Setup Message (or Add Party Message) was first received on this interface.

The Bearer Class of the ABR call. It could be BCOB-A, BCOB-C, BCOB-X or VP Service. Enumeration: 'bcobC': 2, 'vp': 4, 'bcobA': 1, 'bcobX': 3.

The Service Category of the ABR call, which is ABR. Enumeration: 'abr': 4.

The Cast Type of the ABR call, which can only be Point-to-Point(p2p) call. Enumeration: 'p2p': 1.

Susceptibility to Clipping. It can be susceptible or not susceptible. Enumeration: 'yes': 1, 'no': 2.

The Conformance of the ABR call to the traffic sets in the forward direction. It can only be ABR as defined in ATMF Traffic Management 4.0 specification. Enumeration: 'abr': 7.

The Peak Cell Rate for the ABR call in the forward direction.

The Minimum Cell Rate for the ABR call in the forward direction.

The Initial Cell Rate for the ABR call in the forward direction. This is the rate at which the source starts, both initially and after an idle period. The value must not be larger than PCR, and is usually lower.

The Rate Increase Factor for the ABR call in the forward direction. This controls the rate at which the rate increases, when a backward RM-cell is received with CI=0 and NI=0. Larger values lead to faster rate increase. The default value is rifOneOver16(12). Enumeration: 'rifOneOver512': 7, 'rifOneOver32': 11, 'rifOneOver16384': 2, 'rifOneOver2048': 5, 'rifOneOver1024': 6, 'rifOneOver4': 14, 'rifOneOver256': 8, 'rifOneOver2': 15, 'rifOneOver8': 13, 'rifOneOver128': 9, 'rifOneOver4096': 4, 'rifOneOver16': 12, 'rifOneOver8192': 3, 'rifOneOver64': 10, 'rifOneOver32768': 1, 'rifOne': 16.

The Rate Decrease Factor for the ABR call in the forward direction. This controls the rate decrease which occurs when backward RM-cells with CI=1, are received. Larger values lead to faster rate decrease. The default value is rdfOneOver16(12). Enumeration: 'rdfOneOver256': 8, 'rdfOneOver32': 11, 'rdfOneOver32768': 1, 'rdfOneOver2048': 5, 'rdfOneOver512': 7, 'rdfOneOver64': 10, 'rdfOneOver16384': 2, 'rdfOneOver128': 9, 'rdfOneOver8192': 3, 'rdfOneOver8': 13, 'rdfOneOver4': 14, 'rdfOneOver4096': 4, 'rdfOne': 16, 'rdfOneOver2': 15, 'rdfOneOver1024': 6, 'rdfOneOver16': 12.

The Transient Buffer Exposure for the ABR call in the forward direction. This is the negotiated number of cells that the network would like to limit the source to sending during setup periods, before the first RM-cell returns.

The Maximum Number of Cells a source may send for each forward RM-cell in the forward direction for the ABR call. The default value is nrm32(5). Enumeration: 'nrm32': 5, 'nrm128': 7, 'nrm16': 4, 'nrm8': 3, 'nrm256': 8, 'nrm2': 1, 'nrm64': 6, 'nrm4': 2.

The Upper Bound on the time between forward RM-cells in the forward direction for the ABR call. Enumeration: 'trm0point78125': 1, 'trm12point5': 5, 'trm25': 6, 'trm1point5625': 2, 'trm100': 8, 'trm3point125': 3, 'trm50': 7, 'trm6point25': 4.

The Allowed Cell Rate (ACR) Decrease Time Factor for the ABR call in the forward direction. This is the time permitted between sending RM-cells before the rate is decreased to ICR. Range is 10 ms to 10.23 seconds. The unit is 10 msecs. For example, the default value of 50 corresponds to a time factor of 500 ms. Larger values allow a source to retain its current rate longer, during periods of relative inactivity. The default is 50 (0.5 seconds).

The Cutoff Decrease Factor for the ABR call in the forward direction. This controls the decrease in Allowed Cell Rate (ACR) associated with missing RM-cell count (CRM). Larger values result in faster rate decrease. The default value is cdfOneOver16(4). Enumeration: 'cdfOneOver8': 5, 'cdfOneOver2': 7, 'cdf0': 1, 'cdfOneOver4': 6, 'cdfOneOver64': 2, 'cdfOneOver16': 4, 'cdfOne': 8, 'cdfOneOver32': 3.

Whether Frame Discard is enabled or disabled in the forward direction for the ABR call. Enumeration: 'yes': 1, 'no': 2.

The Peak Cell Rate for the ABR call in the backward direction.

The Minimum Cell Rate for the ABR call in the backward direction.

The Initial Cell Rate for the ABR call in the backward direction. This is the rate at which the source starts, both initially and after an idle period. The value must not be larger than PCR, and is usually lower.

The Rate Increase Factor for the ABR call in the backward direction. This controls the rate at which the rate increases, when a forward RM-cell is received with CI=0 and NI=0. Larger values lead to faster rate increase. The default value is rifOneOver16(12). Enumeration: 'rifOneOver512': 7, 'rifOneOver32': 11, 'rifOneOver16384': 2, 'rifOneOver2048': 5, 'rifOneOver1024': 6, 'rifOneOver4': 14, 'rifOneOver256': 8, 'rifOneOver2': 15, 'rifOneOver8': 13, 'rifOneOver128': 9, 'rifOneOver4096': 4, 'rifOneOver16': 12, 'rifOneOver8192': 3, 'rifOneOver64': 10, 'rifOneOver32768': 1, 'rifOne': 16.

The Rate Decrease Factor for the ABR call in the backward direction. This controls the rate decrease which occurs when forward RM-cells with CI=1, are received. Larger values lead to faster rate decrease. The default value is rdfOneOver16(12). Enumeration: 'rdfOneOver256': 8, 'rdfOneOver32': 11, 'rdfOneOver32768': 1, 'rdfOneOver2048': 5, 'rdfOneOver512': 7, 'rdfOneOver64': 10, 'rdfOneOver16384': 2, 'rdfOneOver128': 9, 'rdfOneOver8192': 3, 'rdfOneOver8': 13, 'rdfOneOver4': 14, 'rdfOneOver4096': 4, 'rdfOne': 16, 'rdfOneOver2': 15, 'rdfOneOver1024': 6, 'rdfOneOver16': 12.

The Transient Buffer Exposure for the ABR call in the backward direction. This is the negotiated number of cells that the network would like to limit the source to sending during setup periods, before the first RM-cell returns.

The Maximum Number of Cells a source may send for each forward RM-cell in the backward direction for the ABR call. The default value is nrm32(5). Enumeration: 'nrm32': 5, 'nrm128': 7, 'nrm16': 4, 'nrm8': 3, 'nrm256': 8, 'nrm2': 1, 'nrm64': 6, 'nrm4': 2.

The Upper Bound on the time between forward RM-cells in the backward direction for the ABR call. Enumeration: 'trm0point78125': 1, 'trm12point5': 5, 'trm25': 6, 'trm1point5625': 2, 'trm100': 8, 'trm3point125': 3, 'trm50': 7, 'trm6point25': 4.

The Allowed Cell Rate (ACR) Decrease Time Factor for the ABR call in the backward direction. This is the time permitted between sending RM-cells before the rate is decreased to ICR. Range is 10 ms to 10.23 seconds. The unit is 10 msecs. For example, the default value of 50 corresponds to a time factor of 500 ms. Larger values allow a source to retain its current rate longer, during periods of relative inactivity. The default is 50 (0.5 seconds).

The Cutoff Decrease Factor for the ABR call in the backward direction. This controls the decrease in Allowed Cell Rate (ACR) associated with missing RM-cell count (CRM). Larger values result in faster rate decrease. The default value is cdfOneOver16(4). Enumeration: 'cdfOneOver8': 5, 'cdfOneOver2': 7, 'cdf0': 1, 'cdfOneOver4': 6, 'cdfOneOver64': 2, 'cdfOneOver16': 4, 'cdfOne': 8, 'cdfOneOver32': 3.

Whether Frame Discard is enabled or disabled in the backward direction for the ABR call. Enumeration: 'yes': 1, 'no': 2.

The Fixed Round-Trip Time for the ABR call. This is the sum of the fixed and propagation delays from the source to the furthest destination and back.

The Maximum Cell Transfer Delay for the ABR call on this interface.

The Maximum Cell Delay Variation in the forward direction for the ABR call on this interface.

The Maximum Cell Loss Ratio in the forward direction for the ABR call on this interface.

The Maximum Cell Delay Variation in the backward direction for the ABR call on this interface.

The Maximum Cell Loss Ratio in the backward direction for the ABR call on this interface.

A table specifying the network prefix(es) used for ILMI address registration.

Information about a single network prefix contained in the prefix table.

The network prefix specified for use in ILMI address registration.

Used to create, delete, activate and de-activate network prefixes used in ILMI address registration.

The Interface ATM Address Table. This table contains all the attributes 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/deleted by setting the intfAddressRowStatus object to appropriate values. Existing entries in this table cannot be modified. Entries in this table can also be created/deleted through the command provided by the CLI.

An entry in the table, containing information about a reachable address.

The value of the ATM End System Address.

The address length in bits to be applied to the ATM End System Address.

The type of reachability from the advertising node to the address. This variable indicates either this ATM address ('internal') is a reachable ATM destination that is directly attached to the logical node advertising this address or an ATM address('exterior') that can be reached through a PNNI routing domain but which is not located in that routing domain. Enumeration: 'internal': 1, 'exterior': 2.

The routing mechanism via which the connectivity from the advertising node to the reachable address was learned. A 'local' address indicates this address is automatically advertised. A 'static' address is not automatically advertised. By setting 'cwspAddrRedistribute' variable (see below) to 'true' will force a 'static' address to be advertised. Enumeration: 'static': 2, 'local': 1.

The address plan. For NSAP address, the first byte of the address automatically implies one of the three NSAP address plans: NSAP E.164, NSAP DCC or NSAP ICD. Enumeration: 'nsap': 2, 'e164': 1.

The PNNI scope of advertisement (i.e. level of PNNI hierarchy) of the reachability from the advertising node to the address.

Whether or not the reachable address specified by this entry is to be advertised by the local node into its PNNI routing domain. This object is only meaningful if the routing mechanism (cwspAddrProto) is static.

To create or delete a reachable address. Note that NMS should use CreateAndGo to create a row and Destroy to delete a row. The managed device will return active or notInService as row status.

This table contains a list of ATM addresses that can be used for calls to and from a given interface by a switch or service. The ATM addresses are registered by the endsystem via ILMI. ILMI registered addresses cannot be deleted using this table. This table only applies to switches and network services.

An entry in the ATM Interface Registered Address table.

An address registered for a given switch or service interface.

This object indicates the organizational scope for the referenced address. The information of the referenced address shall not be distributed outside the indicated scope. The default values for organizational scope are localNetwork(1) for ATM group addresses, and global(15) for individual addresses. Enumeration: 'global': 15, 'localNetwork': 1.

A table specifying the load information for each interface.

An entry contains the load information.

The total bandwidth of the interface.

The Maximum bandwith for CBR service.

The maximum bandwith for real time VBR service.

The maximum bandwith for non-real time VBR service.

The maximum bandwith for ABR service.

The maximum bandwith for UBR service.

The total available bandwidth of the interface.

The available bandwith for CBR service.

The available bandwith for real time VBR service.

The available bandwith for non-real time VBR service.

The available bandwith for ABR service.

The available bandwith for UBR service.

The total number of available VCs of the interface.

The number of VCs used by CBR service.

The number of VCs used by real time VBR service.

The number of VCs used by non-real time VBR service.

The number of VCs used by ABR service.

The number of VCs used by UBR service.

The cell transfer delay of CBR service.

The cell transfer delay of real time VBR service.

The cell transfer delay of non-real time VBR service.

The cell transfer delay of ABR service.

The cell transfer delay of UBR service.

The cell delay variation of CBR service.

The cell delay variation of real time VBR service.

The cell delay variation of non-real time VBR service.

The cell delay variation of ABR service.

The cell delay variation of UBR service.

The cell loss ratio-0 of CBR service, -1 implies N/A.

The cell loss ratio-0 of real time VBR service, -1 implies N/A.

The cell loss ratio-0 of non-real time VBR service, -1 implies N/A.

The cell loss ratio-0 of ABR service, -1 implies N/A.

The cell loss ratio-0 of UBR service, -1 implies N/A.

The cell loss ratio-1 of CBR service, -1 implies N/A.

The cell loss ratio-1 of real time VBR service, -1 implies N/A.

The cell loss ratio-1 of non-real time VBR service, -1 implies N/A.

The cell loss ratio-1 of ABR service, -1 implies N/A.

The cell loss ratio-1 of UBR service, -1 implies N/A.

The minimum guaranteed cell rate capacity of CBR service.

The minimum guaranteed cell rate capacity of real time VBR service.

The minimum guaranteed cell rate capacity of non-real time VBR service.

The minimum guaranteed cell rate capacity of ABR service.

The minimum guaranteed cell rate capacity of UBR service.

This object tells the number of calls can be traced concurrently. Depending on the system resource, this object may vary sometime to time. NMS should query this object to ensure there is system resource available before creating a row in the cwspConnTraceCntlTable.

When creating a row in the cwspConnTraceCntlTable, NMS should query this object to obtain the index value to be used for row creation.

This Table contains the objects which control the creation of connection trace for the existing SVC call.

This object controls the connection trace creation. NMS needs to acquire the next index available to create a row. In addition, NMS needs to provide all read-create objects in the same pdu with RowStatus to be CreateAndGo.

Index to a row of connection trace.

The 'ifIndex' indicates the port to a trace connection.

This object shows the VPI value of the starting point on this interface.

This object shows The VCI value of the starting point on this interface. The value should be in the range of 32-65535 (0=SPVP).

Setting this object to either p2p or p2mp to specify tracing a p2p or p2mp connection. Enumeration: 'p2p': 1, 'p2mp': 2.

This object shows the Call Reference value of the call on this interface.

This object shows the value of the Leaf Reference (EndPointReference) of the Call on this interface, this value is used to support p2mp call trace. For p2p call, this value should be set as 0 by NMS.

This object shows the endpoint VPI value of the call on this interface.

This object shows the endpoint VCI value of the call on this interface.

This object shows the endpoint call reference on this interface.

This object shows the result of tracing the call. NMS should get positive result (i.e. traceCompleted) for this attribute before query the cwspConnTraceTable. Enumeration: 'traceIncompleted': 3, 'traceCompleted': 2, 'traceLackResource': 6, 'traceInProgress': 1, 'traceContRefused': 5, 'traceExceededLength': 4.

This object used to manage rows in this table. However, only CreateAndGo, NotInService, Active, and Destroy are start up the trace. To remove a row, NMS set this value to Destroy. The managed device will either return Active or NotInService.

This table contains the objects which show the traversed node information in the existing SVC call.

A conceptual row of the cwspConnTraceTable used to return information about all the nodes belongs to the connection which search criteria is corresponding to instance of the cwspConnTraceCntlTable.

Along with cwspConnTraceIndex, this object specified an unique entry in the cwspConnTraceTable.

This octet string represents 22 bytes nodeId in the traced connection.

This object represents 4 bytes logical port ID of the traversed node. When 0 is specified, the destination node for the trace is reached.

This object shows the Egress port's VPI value for the traced connection.

This object shows the Egress port's VCI value for the traced connection

This object shows the Egress port's call reference.

This object shows the Egress port's physical port Identifier for the traversed node; if this object is 0 meaning that the destination node for the traced connection has been reached. the meaning for the bytes are: first byte -- flag (used by CLI to decode the rest of bytes ) 2nd byte -- shelf 3rd & 4th bytes -- slot 5th byte -- subslot 6th & 7th bytes -- port 8th byte -- subport

This value indicates if this entry contains the information about the last node where this trace ends. If it is the last node, this value is 'true(1)' or it is 'false(2)'.

The Interface operation table contains the runtime negotiated values between platform, PNNI controller and peer on an interface

An entry in the interface operation table containing negotiated values of an interface

The operational state of ILMI.

The interface type of an interface publicUni -- Public User-Network Interface privateUni -- Private User-Network Interface iisp -- Interim Inter-Switch Signaling Protocol pnni -- Private Network-Network Interface aini -- ATM Inter-Network Interface enni -- Enhanced Network-Network Interface, a cisco proprietary interfac type. Enumeration: 'publicUni': 1, 'enni': 6, 'privateUni': 2, 'pnni': 4, 'iisp': 3, 'aini': 5.

The IME type of the ATM device which is concluded from automatic interface type determination procedure. Enumeration: 'userSide': 1, 'symmetric': 3, 'networkSide': 2.

The maximum number of switched and permanent VPCs supported on this ATM interface

The maximum number of switched and permanent VCCs supported on this ATM interface

The maximum number of active VPI bits on this ATM interface.

The maximum number of active VCI bits on this ATM interface.

The type of the ATM device, either public or private. Enumeration: 'public': 1, 'private': 2.

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. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. Enumeration: 'unsupported': 5, 'version2point0': 1, 'version4poing0': 4, 'version3poing0': 2, 'version3poing1': 3.

This object determines the type of the ATM device. This object is used in automatic ATM Interface-Type determination procedure such that a correct operational ATM Interface-type can be determined. An ATM End System shall take the value of user(1), and an ATM network node shall take the value of node(2). Enumeration: 'node': 2, 'user': 1.

An indication of the latest version of the ATM Forum ILMI Specification that is supported on this ATM Interface. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. If this object is not present, a version of the ILMI earlier than 4.0 is supported. Enumeration: 'version4point0': 2, 'unsupported': 1.

An indication of the latest version of the ATM Forum PNNI Signaling Specification that is supported on this ATM Interface. Note that the PNNI routing version is not determined through ILMI. If the peer IME's value of this object is the same as, or later than the local IME's value, then the version corresponding to the local IME's value should be attempted. Otherwise, if the peer IME's value of this object is earlier, and supported locally, then the local IME should attempt the version corresponding to the peer IME's value. Otherwise, compatibility of the two IMEs cannot be assumed. Note that 'enni' is not a signaling protocol. Enumeration: 'enni': 4, 'iisp': 2, 'pnniVersion1point0': 3, 'aini': 5, 'unsupported': 1.

The maximum switched VPC VPI.

The minimum switched VPC VPI.

The maximum switched VCC VPI.

The minimum switched VCC VPI.

The maximum switched VCC VCI.

The minimum switched VCC VCI.

The ATM address plan supported on a public UNI. For all other interfaces, the value is aesa. Enumeration: 'both': 1, 'e164': 3, 'aesa': 2.

Defined SVC port failures. Note: this object is used as trap varbind only. The NMS applications should not issue SNMP get, get-next for this object. Enumeration: 'vsiAdminDown': 7, 'vccfailure': 4, 'vsiOperDown': 3, 'vsiRemove': 6, 'neighIpChanged': 5, 'ilmiDown': 1, 'portDown': 2.

Indicates the status of a link has changed: 1 - the link entered the 2-Way Inside state, 2 - the link exit the 2-Way Inside state, 3 - the link entered the 2-Way Outside state, 4 - the link exit the 2-Way Outside state. 5 - the link entered the Common Outside state, or 6 - the link exit the Common Outside state and entered the 1-Way Outside state. Enumeration: 'out2wout': 4, 'in2wout': 3, 'outCout': 6, 'in2win': 1, 'out2win': 2, 'inCout': 5.

Indicates the status of PGL process has changed: 1 - the PGL exit the hung-election state, or 2 - the PGL entered the hung-election state. Enumeration: 'hung': 2, 'ok': 1.

This object is used in conjunction with ciscoWANPnniRemoteNodeId to indicate the reachability of the RemoteNode has changed: 1 - RemoteNode became reachable, or 2 - RemoteNode became unreachable. Enumeration: 'fail': 2, 'ok': 1.

Indicates the node identifier of a remote node. If the remote node ID is unknown, this attribute is set to all zeros.

The port identifier of the port.

Defines SPVC manager failures. Refer description in the textual convention. Note: this object is for Supporting Varbinds used only in trap definitions. The NMS applications should not depend on the implementation of this object. The SNMP Requests(GET,GET-NEXT) is not valid for this object.

Spvc node prefix for the pnni controller. This node prefix identifies an SPVC node in the network.

The compliance statement for entities that support the Cisco SVC MIB.

The compliance statement for entities that support the Cisco SVC MIB.

The compliance statement for entities that support the Cisco SVC MIB.

A collection of objects providing device level information.

A collection of objects providing information about the controller interface operation and associated parameters.

A collection of objects providing information about CAC information of a interface.

A collection of objects providing information about call statistics of a interface.

A collection of objects providing information about signaling statistics.

A collection of objects providing information about the p2p or p2mp SVC/SPVC calls and associated parameters.

A collection of objects providing information about ABR calls and associated parameters of a interface.

A table specifying the network prefix(es) used for ILMI address registration.

A collection of objects providing information about load information and associated parameters of a interface.

A collection of objects providing information about ATM End System Addresses.

A collection of objects providing information about signaling configuration and associated parameters.

A collection of objects providing information about SSCOP configuration and associated parameters.

A collection of objects providing information about SSCOP statistics.

A collection of objects providing information about registed ATM address.

A collection of objects providing information about PNNI topology.

A collection of objects providing trace information about SVC/PNNI connnection.

A collection of objects providing information about runtime negotiated values between platform, PNNI controller and peer on an interface.

A collection of objects providing spvc related information in pnni controller.

A collection of objects providing trace information about SVC/PNNI connnection.

A collection of objects providing information about the controller interface operation and associated parameters.

A collection of objects providing information about the controller interface operation and associated parameters.