CISCO-VSI-MASTER-MIB: View SNMP OID List / Download MIB

This MIB module contains objects related to the master side of the the Virtual Switch Interface protocol used for control of ATM switches.

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.

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.

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.

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.

This object contains a value equal to the number of cross-connects being controlled via VSI protocol via this controller.

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. Enumeration: 'pnni': 3, 'par': 4, 'other': 1, 'mpls': 2.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The identifier of the slave for this VSI master-slave session. This value is learned from the slave on the switch.

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. Enumeration: 'established': 8, 'configuring': 3, 'unknown': 2, 'resyncUnderway': 5, 'resyncStarting': 4, 'inactive': 1, 'shutdownStarting': 9, 'resyncEnding': 6, 'discovery': 7.

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.

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.

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.

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.

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.

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.

The VSI controller index of the controller through which this logical interface was learned.

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.

The physical descriptor of the logical interface, as reported by the VSI slave. It is distinct from ifName.

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. Enumeration: 'active': 2, 'failedExternal': 3, 'removed': 1, 'failedInternal': 4.

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. Enumeration: 'down': 1, 'up': 2, 'pendingDown': 3.

The number of cells received via this logical interface as reported to the VSI master by the VSI slave.

The number of cells transmitted via this logical interface as reported to the VSI master by the VSI slave.

The number of received cells discarded by this logical interface as reported to the VSI master by the VSI slave.

The number of transmitted cells discarded by this logical interface as reported to the VSI master by the VSI slave.

The number of cells received via this logical interface which had header errors, as reported to the VSI master by the VSI slave.

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.

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).

The number of ingress channels available for this logical interface, as reported to the VSI master by the VSI slave.

The number of egress channels available for this logical interface, as reported to the VSI master by the VSI slave.

The available ingress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.

The available egress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.

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.

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.

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.

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.

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.

The maximum egress cell rate in cells/second for the logical interface, as reported to the VSI master by the VSI slave.

Minimum allowed vpi value for this interface as reported by VSI slave switch.

Maximum allowed vpi value for this interface as reported by VSI slave switch.

Minimum allowed vci value for this interface as reported by VSI slave switch.

Maximum allowed vci value for this interface as reported by VSI slave switch.

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.

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.

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.

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.

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.

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.

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.

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).

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. Enumeration: 'deleted': 1, 'reservedFail': 4, 'reserved': 2, 'committed': 3.

The vpi of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfLow.

The vci of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfLow.

The vpi of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfHi.

The vci of that endpoint of the cross-connect which terminates on the logical interface whose index is given by vsiXCLogicalIfHi.

Objects that apply to all VSI Master implementations.

The basic implentation requirements for agents that support this VSI Master MIB.