CISCO-VSI-MASTER-MIB

All MIBs › CISCO-VSI-MASTER-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2000-06-01

Category: Telephony and VoIP, Vendor: Cisco Devices

Description: Manages Cisco VSI master module coordinating VSI controller and slave relationships in ATM networks.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-VSI-MASTER-MIB?

CISCO-VSI-MASTER-MIB manages the master (controller) side of the Virtual Switch Interface (VSI) protocol, which Cisco ATM switches use to coordinate control between a VSI master (controller) and VSI slave switching elements. It exposes a controller table capturing controller identity, the number of cross-connects it manages, controller type, supported and in-use VSI protocol versions, and the control interface, physical or logical, used, along with notification and conformance groups. Monitoring this MIB is primarily about software/protocol-level status: confirming a VSI controller relationship is established with a compatible protocol version, how many cross-connects are active under a given controller, and which physical/logical interface is carrying VSI control traffic. It is inherently tied to the broader Cisco VSI protocol architecture and complements a corresponding VSI slave-side MIB. It is deployed in Cisco ATM switch fabrics using the VSI protocol for centralized control-plane switching, such as MGX/BPX-based ATM networks. Engineers can download the CISCO-VSI-MASTER-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-VSI-MASTER-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco ATM switch (VSI controller/master)
Cisco MGX/BPX ATM switching platform
Cisco MGX/BPX ATM switching platforms (VSI protocol master/controller)

Monitoring Examples

An administrator would poll vsiMasterControllerTable/vsiMasterControllerEntry keyed by vsiControllerIndex, checking vsiVersionInUse against vsiBaseVersionSupported/vsiTopVersionSupported to confirm protocol compatibility between master and slave. The vsiCrossConnects count reveals how many ATM cross-connects are currently managed by that controller, useful for capacity tracking. If vsiControlInterface or vsiLogicalControlInterface shows an unexpected or down interface, that would point to a broken VSI control channel between master and switch fabric.

What Can Be Monitored

VSI controller identity
cross-connect count
VSI protocol version in use vs supported
control interface used
controller type

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From IF-MIB

InterfaceIndex

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using vsiLogicalIfRxCells OID:

Select a Cisco MGX/BPX ATM switching platform as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type vsiLogicalIfRxCells into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of cells received via this logical interface as reported to the VSI master by the VSI slave. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoVsiMasterCompliances	1.3.6.1.4.1.9.9.162.3.2
ciscoVsiMasterConformance	1.3.6.1.4.1.9.9.162.3
ciscoVsiMasterGeneralGroup	1.3.6.1.4.1.9.9.162.3.1.1			Objects that apply to all VSI Master implementations.
ciscoVsiMasterGroups	1.3.6.1.4.1.9.9.162.3.1
ciscoVsiMasterMIB	1.3.6.1.4.1.9.9.162			This MIB module contains objects related to the master side of the the Virtual Switch Interface protocol used for control of ATM switches.
ciscoVsiMasterModuleCompliance	1.3.6.1.4.1.9.9.162.3.2.1			The basic implentation requirements for agents that support this VSI Master MIB.
ciscoVsiMasterNotifications	1.3.6.1.4.1.9.9.162.2
ciscoVsiMasterObjects	1.3.6.1.4.1.9.9.162.1
I32 vsiBaseVersionSupported	1.3.6.1.4.1.9.9.162.1.1.1.5	Integer32	read-only	A VSI Master protocol instance defines internally a set of versions of the protocol that it will support. These versions are numbered, by default, starting from 1. This object makes available the lowest numbered version that the VSI Master protocol supports. This object is related to the other vsiMasterControllerEntry objects, vsiTopVersionSupported and vsiVersionInUse.
NUM vsiControlInterface	1.3.6.1.4.1.9.9.162.1.1.1.9	InterfaceIndex	read-only	A VSI controller communicates with a set of VSI Slaves across a control interface. The controller is connected to the ATM switch via an ATM link called the Slave Control Link. The interface at the Master end of the link is the Master Control Port, and is described by this object; it is the ifIndex of this Master Control Port.
I32 vsiControllerId	1.3.6.1.4.1.9.9.162.1.1.1.2	Integer32	read-only	The controller identifier for the VSI controller. Values are arbitrarily assigned by the VSI protocol implementation being managed via this MIB, with local significance only. These values appear in the header of all VSI protocol messages.
VSI vsiControllerIndex	1.3.6.1.4.1.9.9.162.1.1.1.1	VsiControllerIndex	not-accessible	A unique value per VSI controller, greater than 0. This object gets its value from the vsiControllerId, and is used for row selection within the vsiMasterControllerTable.
INT vsiControllerType	1.3.6.1.4.1.9.9.162.1.1.1.4	INTEGER	read-only	A VSI controller represents an instance of a service layer accessible to a network control application. This object serves to identify the type of the network control application currently being supported by this controller. other(1): the type is unspecified. mpls(2): indicates that the client is a Label Switch Controller performing Multi Protocol Label Switching. pnni(3): indicates that the client is an instance of the ATM Private Network to Network Interface. par(4): indicates that the client is an instance of ATM Portable Autoroute.
I32 vsiCrossConnects	1.3.6.1.4.1.9.9.162.1.1.1.3	Integer32	read-only	This object contains a value equal to the number of cross-connects being controlled via VSI protocol via this controller.
NUM vsiLogicalControlIfIndex	1.3.6.1.4.1.9.9.162.1.3.1.27	InterfaceIndex	read-only	The interface index for the interface which controls this logical interface. This is the ifIndex of the controlling xtagatm interface, and is a direct manifestation of the mapping between a logical interface and the real ifIndex.
VSI vsiLogicalControlInterface	1.3.6.1.4.1.9.9.162.1.1.1.10	VsiLogicalIfIndex	read-only	This object describes the instance of a logical interface index bound to the slave end of the Slave Control Link, which is referred to in the description of vsiControlInterface.
INT vsiLogicalIfAdminState	1.3.6.1.4.1.9.9.162.1.3.1.5	INTEGER	read-only	The current administrative (configured) state of the interface, as reported to the VSI master by the VSI slave. down(1): the interface is not a valid interface for the controller. up(2): the interface is configured for use by the controller. pendingDown(3): the interface is being removed from service, and the controller is requested to remove all connections.
G32 vsiLogicalIfAvailEgressCellRate	1.3.6.1.4.1.9.9.162.1.3.1.16	Gauge32	read-only	The available egress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.
G32 vsiLogicalIfAvailEgressChnls	1.3.6.1.4.1.9.9.162.1.3.1.14	Gauge32	read-only	The number of egress channels available for this logical interface, as reported to the VSI master by the VSI slave.
G32 vsiLogicalIfAvailIngressCellRate	1.3.6.1.4.1.9.9.162.1.3.1.15	Gauge32	read-only	The available ingress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.
G32 vsiLogicalIfAvailIngressChnls	1.3.6.1.4.1.9.9.162.1.3.1.13	Gauge32	read-only	The number of ingress channels available for this logical interface, as reported to the VSI master by the VSI slave.
VSI vsiLogicalIfControllerIndex	1.3.6.1.4.1.9.9.162.1.3.1.1	VsiControllerIndex	not-accessible	The VSI controller index of the controller through which this logical interface was learned.
G32 vsiLogicalIfEndPointsInUse	1.3.6.1.4.1.9.9.162.1.3.1.12	Gauge32	read-only	The number of end points in use on this logical interface, as reported to the VSI master by the VSI slave. If this logical interface has not been removed, but does not currently support any cross connects, this object will be reported as zero (0).
vsiLogicalIfEntry	1.3.6.1.4.1.9.9.162.1.3.1		not-accessible	An entry containing information about a single VSI logical interface. Entries are instantiated and removed as signalled by the slave which controls the external interface. Each entry contains information about the capacity of cross-connects the interface can bear, cell rate, merge capability, vpi/vci ranges, and statistics. Pairs of logical interfaces support potential cross-connects that, when actualized, are represented by the vsiXCEntrys in the vsiXCTable. Logical interfaces are controlled by a designated slave, as determined by the switch. The slave is in the domain of the controller whose identity is given by vsiLogicalIfControllerIndex. This object is an opaque identifier, provided by the slave, and used as a key to identify the entry.
VSI vsiLogicalIfIndex	1.3.6.1.4.1.9.9.162.1.3.1.2	VsiLogicalIfIndex	not-accessible	A unique value, greater than zero, for each VSI logical interface. Logical interface numbers are selected by the switch to be unique and persistent. The same number is preserved through power failures. This index is not the same as an ifIndex. It is an abstract number provided by the slave, representing a virtual interface, which is an identifier to be used when communicating with the slave about an interface.
I32 vsiLogicalIfMaxEgressCellRate	1.3.6.1.4.1.9.9.162.1.3.1.22	Integer32	read-only	The maximum egress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.
I32 vsiLogicalIfMaxIngressCellRate	1.3.6.1.4.1.9.9.162.1.3.1.21	Integer32	read-only	The maximum ingress cell rate in cells/second for the logical interface, as reported to the VSI. This value is the limiting value for vsiLogicalIfAvailIngressCellRate.
INT vsiLogicalIfMaxVci	1.3.6.1.4.1.9.9.162.1.3.1.26	INTEGER	read-only	Maximum allowed vci value for this interface as reported by VSI slave switch.
INT vsiLogicalIfMaxVpi	1.3.6.1.4.1.9.9.162.1.3.1.24	INTEGER	read-only	Maximum allowed vpi value for this interface as reported by VSI slave switch.
INT vsiLogicalIfMinVci	1.3.6.1.4.1.9.9.162.1.3.1.25	INTEGER	read-only	Minimum allowed vci value for this interface as reported by VSI slave switch.
INT vsiLogicalIfMinVpi	1.3.6.1.4.1.9.9.162.1.3.1.23	INTEGER	read-only	Minimum allowed vpi value for this interface as reported by VSI slave switch.
T/F vsiLogicalIfMulticastSupported	1.3.6.1.4.1.9.9.162.1.3.1.18	TruthValue	read-only	If this object has the value true(1) then multicast capability is supported for this logical interface. Otherwise multicast capability is not supported on this logical interface.
STR vsiLogicalIfName	1.3.6.1.4.1.9.9.162.1.3.1.3	SnmpAdminString	read-only	The physical descriptor of the logical interface, as reported by the VSI slave. It is distinct from ifName.
INT vsiLogicalIfOperState	1.3.6.1.4.1.9.9.162.1.3.1.4	INTEGER	read-only	The VSI operational state of the logical interface as reported to the VSI master by the VSI slave. removed(1): the interface is not a valid interface for this controller. active(2): the interface is active and ready for use. failedExternal(3): external failure, such as a line alarm, detected. failedInternal(4): local hardware has detected a failure, making the interface unusable.
C32 vsiLogicalIfRxCellsEx	1.3.6.1.4.1.9.9.162.1.3.1.6	Counter32	read-only	The number of cells received via this logical interface as reported to the VSI master by the VSI slave.
C32 vsiLogicalIfRxCellsDiscarded	1.3.6.1.4.1.9.9.162.1.3.1.8	Counter32	read-only	The number of received cells discarded by this logical interface as reported to the VSI master by the VSI slave.
C32 vsiLogicalIfRxHeaderErrors	1.3.6.1.4.1.9.9.162.1.3.1.10	Counter32	read-only	The number of cells received via this logical interface which had header errors, as reported to the VSI master by the VSI slave.
C32 vsiLogicalIfRxInvalidAddrs	1.3.6.1.4.1.9.9.162.1.3.1.11	Counter32	read-only	The number of cells received by this logical interface which had invalid addresses, as reported to the VSI master by the VSI slave. An unknown vpi/vci value set is an example of of an invalid address.
VSI vsiLogicalIfSessionIndex	1.3.6.1.4.1.9.9.162.1.3.1.28	VsiSessionIndex	read-only	All logical interfaces are in the domain of a VSI slave, which communicates with the VSI master through a Session. This object is a selector for an entry in the table vsiSessionTable. It is the VSI session index for the VSI session which controls this logical interface.
T/F vsiLogicalIfStrictSigRange	1.3.6.1.4.1.9.9.162.1.3.1.20	TruthValue	read-only	If this object has the value true(1) then signalling addresses must be in the strict advertised range for the high-address (vpi). Otherwise, signalling addresses are not so constrained.
vsiLogicalIfTable	1.3.6.1.4.1.9.9.162.1.3		not-accessible	A table containing information about logical interfaces on the slave switch controlled via VSI. Logical interfaces are an abstraction of exposed, external ATM interfaces that are available for connections. When two external interfaces, represented by two logical interfaces, are paired, they provide physical paths through the switch. These physical pathways support cross-connects.
C32 vsiLogicalIfTxCells	1.3.6.1.4.1.9.9.162.1.3.1.7	Counter32	read-only	The number of cells transmitted via this logical interface as reported to the VSI master by the VSI slave.
C32 vsiLogicalIfTxCellsDiscarded	1.3.6.1.4.1.9.9.162.1.3.1.9	Counter32	read-only	The number of transmitted cells discarded by this logical interface as reported to the VSI master by the VSI slave.
T/F vsiLogicalIfVcMergeSupported	1.3.6.1.4.1.9.9.162.1.3.1.17	TruthValue	read-only	If this object has the value true(1) then VC merge capability is supported for this logical interface. Otherwise VC merge capability is not supported on this logical interface.
T/F vsiLogicalIfVpiTranslated	1.3.6.1.4.1.9.9.162.1.3.1.19	TruthValue	read-only	If this object has the value true(1) then vpi values entering on this logical interface are translated at the other end of the link. This translation may be an indication that the link is supporting a tunnel. Otherwise, vpi values are not translated for traversal of the link.
vsiMasterControllerEntry	1.3.6.1.4.1.9.9.162.1.1.1		not-accessible	An entry containing management information applicable to a controller which uses the VSI protocol. Controller entries represent internally generated control structures. Therefore each row is created by the agent in response to the learning of a controller's instantiation. Instantiation of a controller is performed by the VSI Master protocol implementation under management via this MIB. These structures, once instantiated, are never deleted. Each controller manages a set of VSI slaves, via a protocol instance called a Session.
vsiMasterControllerTable	1.3.6.1.4.1.9.9.162.1.1		not-accessible	A table containing a set of VSI controllers. Each controller represents an instance of the VSI Master control protocol. A controller communicates with a set of VSI Slaves across a control interface. Running the VSI protocol, the controller supports a network control application. Through VSI, such an application can control the Virtual Circuit cross-connect table inside the ATM switch, perform monitoring and statistics collection of interfaces and virtual circuits on the switch, and discover configuration information from within the switch.
I32 vsiSessionActiveId	1.3.6.1.4.1.9.9.162.1.2.1.11	Integer32	read-only	ID supplied by the slave to identify the session. This value is interpreted by the master, when a change occurs, to indicate that a resync should be inititated.
G32 vsiSessionCmdsPending	1.3.6.1.4.1.9.9.162.1.2.1.10	Gauge32	read-only	The number of unacknowledged command messages. The VSI master sends commands to the slave, without receiving acknowledgement, until the window size threshold has been reached. This object is a count of the number of commands that have been sent and that are awaiting acknowledgment.
VSI vsiSessionControllerIndex	1.3.6.1.4.1.9.9.162.1.2.1.1	VsiControllerIndex	not-accessible	The ID of the controller which controls this master-slave session. This identifies which vsiMasterControllerEntry represents the controller communicating with a slave through this Session.
vsiSessionEntry	1.3.6.1.4.1.9.9.162.1.2.1		not-accessible	A vsiSessionEntry is a set of objects that together represent the status of each instance of VSI protocol and the slave in an ATM switch to which that instance corresponds. There is one vsiSession for each slave. The number of slaves is discovered via the VSI protocol. Each slave is responsible for a subset of the total number of external interfaces on the ATM switch. Session entries refer back to their respective controllers via vsiSessionControllerIndex, and are in turn referred to by vsiLogicalIfSessionIndex in the VsiLogicalIfEntry. These entries are never deleted.
VSI vsiSessionIndex	1.3.6.1.4.1.9.9.162.1.2.1.2	VsiSessionIndex	not-accessible	A VSI controller discovers a set of slaves through VSI protocol. Each of the discovered slaves is bound to a protocol Session and each of these Sessions occupies a row in the vsiSessionTable. This object is the row selector. The value should remain constant after a VSI session is reinitialized.
I32 vsiSessionPowerupId	1.3.6.1.4.1.9.9.162.1.2.1.12	Integer32	read-only	ID supplied by the slave to identify the session at powerup. This is the initial value for vsiSessionActiveId, and its default is zero. Changes in vsiSessionActiveId signal a resync.
I32 vsiSessionSlaveId	1.3.6.1.4.1.9.9.162.1.2.1.7	Integer32	read-only	The identifier of the slave for this VSI master-slave session. This value is learned from the slave on the switch.
INT vsiSessionState	1.3.6.1.4.1.9.9.162.1.2.1.8	INTEGER	read-only	The state of the VSI session. inactive(1): communications data structures for communicating with the slave have been created, but the VSI protocol has not been started. unknown(2): slave has been queried, but its configuration data has not yet been recieved. configuring(3): configuration data has been sent to the slave, but a response has not yet been received. resyncStarting(4): a re-sync command has been sent to the slave, but a response has not yet been recieved. resyncUnderway(5): a re-sync command response has been received from the slave, but the network applications have not yet completed reasserting connections. resyncEnding(6): a command has been sent to end re-sync, but a response has not yet been received. discovery(7): a query has been sent to the slave for interface information, but a response has not yet been received. established(8): discovery has completed. shutdownStarting(9): the master has started an orderly shutdown of the slave.
I32 vsiSessionSwitchId	1.3.6.1.4.1.9.9.162.1.2.1.5	Integer32	read-only	The identifier of the switch which participates in this VSI master-slave session. The switch terminates the virtual circuit identified by the vpi/vci pair referred to by vsiSessionVpi and vsiSessionVci.
STR vsiSessionSwitchName	1.3.6.1.4.1.9.9.162.1.2.1.6	SnmpAdminString	read-only	The IP hostname for the slave switch which is controlled by this session. This is an ascii string of maximum length 64 characters, learned from the ATM switch.
vsiSessionTable	1.3.6.1.4.1.9.9.162.1.2		not-accessible	A table containing VSI master-slave session status information. Each VSI controller manages a set of VSI slaves, via a protocol instance called a Session. VSI slaves are entities that reside on the controlled ATM switch. Their number and characteristics are discovered by the VSI controller via the VSI protocol. This table has an entry for each slave so discovered.
I32 vsiSessionVci	1.3.6.1.4.1.9.9.162.1.2.1.4	Integer32	read-only	The virtual channel identifier for this VSI master-slave session. The Slave Control Link, referred to in the description of vsiLogicalControlInterface, supports an ATM control VC. This is the vci for that link.
I32 vsiSessionVpi	1.3.6.1.4.1.9.9.162.1.2.1.3	Integer32	read-only	The virtual path identifier for this VSI master-slave session. The Slave Control Link, referred to in the description of vsiLogicalControlInterface, supports an ATM control VC. This is the vpi for that link.
I32 vsiSessionWindowSize	1.3.6.1.4.1.9.9.162.1.2.1.9	Integer32	read-only	The maximum number of command messages the VSI master will send before requiring a response from slave. If the value is 0, then flow control is not enabled.
I32 vsiSpecifiedVersion	1.3.6.1.4.1.9.9.162.1.1.1.8	Integer32	read-write	When this object is written with a non-zero value, re-synchronization procedures will be initiated, if necessary, in order to constrain the master and slaves to use the indicated protocol version. When written with zero (0), the master and slaves should use the version dictated by the usual protocol version selection procedures; resynchronization procedures will be invoked, if necessary, to achieve this result.
I32 vsiTopVersionSupported	1.3.6.1.4.1.9.9.162.1.1.1.6	Integer32	read-only	A VSI Master protocol instance defines internally a set of versions of the protocol that it will support. These versions are numbered, by default, starting from 1. This object makes available the highest numbered version that the VSI Master protocol supports. This object is related to the other vsiMasterControllerEntry objects, vsiBaseVersionSupported and vsiVersionInUse.
I32 vsiVersionInUse	1.3.6.1.4.1.9.9.162.1.1.1.7	Integer32	read-only	The number of the VSI version currently being used by this controller. Protocol selection procedures dictate that this should be the highest value of protocol version, between vsiBaseVersionSupported and vsiTopVersionSupported, that is supported by all slaves. An exception to this rule will occur when the version is constrained to a specific value indicated by the vsiSpecifiedVersion object.
VSI vsiXCControllerIndex	1.3.6.1.4.1.9.9.162.1.4.1.1	VsiControllerIndex	not-accessible	The index of the VSI controller through which this crossconnect was instantiated. This object is the index for a vsiControllerTable entry; the controller indexed is the VSI protocol partner to the slave that is controlling the logical interfaces on which this cross connect is supported.
vsiXCEntry	1.3.6.1.4.1.9.9.162.1.4.1		not-accessible	An entry containing information about one unidirectional or bidirectional crossconnect on the slave switch controlled via VSI. A VSI controller represents an instance of a service layer accessible to a network control application. The application creates virtual links via service requests to the controller, which in turn sends commands to the VSI slave, indicating the participating logical interfaces. Conversely, links are taken down by a reverse process. Virtual link creation and deletion come about as a result of routing decisions.
VSI vsiXCIndex	1.3.6.1.4.1.9.9.162.1.4.1.4	VsiXCIndex	not-accessible	A unique value greater than zero, for each crossconnect within the set of VsiXCTable entries indexed by vsiXCLogicalIfLow and vsiXCLogicalIfHi. The value should remain constant after a crossconnect is initialized. These values are assigned in sequence by the management agent, starting from one (1).
VSI vsiXCLogicalIfHi	1.3.6.1.4.1.9.9.162.1.4.1.3	VsiLogicalIfIndex	not-accessible	The VSI logical interface index for the second endpoint of the cross-connect. This object is the selector index for one of the two vsiLogicalIfTable entries that support this cross connect. Further, this index value is constrained to be 'numerically higher than' the index value of the other vsiLogicalIfTable entry, indexed by vsiXCLogicalIfLow, supporting this cross connect.
VSI vsiXCLogicalIfLow	1.3.6.1.4.1.9.9.162.1.4.1.2	VsiLogicalIfIndex	not-accessible	The VSI logical interface index for the first endpoint of the cross-connect. This object is the selector index for one of the two vsiLogicalIfTable entries that support this cross connect. Further, this index value is constrained to be 'numerically lower than' the index value of the other vsiLogicalIfTable entry, indexed by vsiXCLogicalIfHi, supporting this cross connect.
INT vsiXCState	1.3.6.1.4.1.9.9.162.1.4.1.5	INTEGER	read-only	The operational state of the cross connect, as reported to the VSI master by the VSI slave. deleted(1): the connection does not exist. reserved(2): connection is in the reserved state. committed(3): connection is in the committed state. reservedFail(4): connection is reserved but has an internal failure.
vsiXCTable	1.3.6.1.4.1.9.9.162.1.4		not-accessible	A table containing information about crossconnects on the slave switch controlled via VSI. Cross connects represent virtual links across two interfaces. The participating interfaces that support these links are represented in this MIB by the vsiLogicalIfTable entries.
I32 vsiXCVciHi	1.3.6.1.4.1.9.9.162.1.4.1.9	Integer32	read-only	The vci of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfHi.
I32 vsiXCVciLow	1.3.6.1.4.1.9.9.162.1.4.1.7	Integer32	read-only	The vci of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfLow.
I32 vsiXCVpiHi	1.3.6.1.4.1.9.9.162.1.4.1.8	Integer32	read-only	The vpi of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfHi.
I32 vsiXCVpiLow	1.3.6.1.4.1.9.9.162.1.4.1.6	Integer32	read-only	The vpi of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfLow.

RFC description

Virtual Switch Interface (VSI) master control MIB for Cisco ATM switches, managing VSI protocol and session information.

Start monitoring Cisco MGX/BPX ATM switching platforms with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-VSI-MASTER-MIB