CISCO-VSI-CONTROLLER-MIB

All MIBs › CISCO-VSI-CONTROLLER-MIB

Organization: Cisco Systems, Inc.

Last Updated: 1999-06-08

Category: Telephony and VoIP, Vendor: Cisco Devices

Description: Manages Cisco VSI controller connections between ATM switches and external call agents.

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-CONTROLLER-MIB?

CISCO-VSI-CONTROLLER-MIB is a Cisco-specific MIB in the ATM switching technology area, used to configure and monitor the Virtual Switch Interface (VSI), a hardware-independent protocol that lets an ATM switch fabric be controlled by one or more external control planes such as PNNI or a Label Switch Controller (LSC). It exposes configuration data identifying each VSI controller attached to the switch, including controller ID, type, physical shelf/slot location, name, and the VPI/VCI used for the control channel between switch and controller. Its monitoring value is primarily around control-plane connectivity and configuration integrity: confirming which controllers are configured against a switch, their identifying VPI/VCI signaling channel, and row status (active/notInService) of each controller entry, which reveals whether a controller has been properly provisioned or has become disassociated from the switch. It is specific to Cisco ATM switch platforms and their VSI master/slave control architecture, layered on top of standard ATM MIB concepts for VPI/VCI addressing. It is deployed in carrier or enterprise ATM networks where Cisco ATM-capable switches are controlled by external PNNI or call-agent software via VSI. Engineers can download the CISCO-VSI-CONTROLLER-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-VSI-CONTROLLER-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-capable)

Monitoring Examples

An operator would poll cvcConfTable/cvcConfEntry to see each configured controller's cvcConfControllerID, cvcConfControllerType, and cvcConfControllerShelfLocation, confirming that the expected PNNI or LSC controller is associated with the correct switch shelf. Checking cvcConfVpi and cvcConfVci reveals which VPI/VCI pair carries VSI control traffic, and an unexpected value here could explain a loss of control-plane communication. The cvcConfRowStatus column shows whether a given controller entry is active, letting an admin detect a controller entry left in a notReady or notInService state after a configuration change.

What Can Be Monitored

configured VSI controller identity
controller type (PNNI/LSC)
controller shelf/slot location
control-channel VPI/VCI
controller row/provisioning status

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoVSIControllerMIB	1.3.6.1.4.1.9.9.141			This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information. Terminolgies used: VSI - Virtual Switch Interface, a hardware-independent switch control protocol. This allows a Switch(node) to be controlled by a multiple controllers such as PNNI,LSC. These control planes can be internal or external to the switch.The VSI interface defines the messages and associated functions which allow communication between the controller and the switch.This interface is expected to support all types of connections (voice,data,frame relay,ATM) for PVCs, SPVCs and SVCs. VSI Master - software component which requests connections and receives switch generic information. This controls one or more VSI Slaves. This may run on the switch or a dedicated controller platform. This is the master module.It performs the interface to the higher layer networking software and handles all VSI related functions. VSI Slave - software component which converts generic connection requests into hardware specific requests and hardware specific information into generic information. This runs on the switch.a A centralized slave has a single point of control for making connections and controlling interfaces, while a distributed slave allows for multiple slaves to coexist on the same switch. Controller - Software ( and possibly hardware) which manages topology and network resources and performs VSI Master fucntion. This performs source routing for ent-to-end SVCs, including general call acceptance GCAC,setup calls with other controllers. PNNI and MPLS are examples for the Controller. Controller Shelf - A controller shelf is a switch containing atleast one VSI Controller which is controlling a different switch.It will also, typically, contain 'local' controllers for itself.
cvcMIBObjects	1.3.6.1.4.1.9.9.141.1
cvcConfController	1.3.6.1.4.1.9.9.141.1.1
cvcConfTable	1.3.6.1.4.1.9.9.141.1.1.1		not-accessible	This table contains the entries for VSI Controllers. This table is used for informing the VSI Slaves about the existence of VSI Controllers and how the VSI slaves can reach the controller. The information in these entries are advertised to all the VSI Slaves using a system dependent implementation when an entry is created/activated.
cvcConfEntry	1.3.6.1.4.1.9.9.141.1.1.1.1		not-accessible	An entry for a VSI Controller. The entries in this table are created by setting the cvcConfRowStatus object to 'createAndGo(4)'. The entries in this table are deleted by setting the cvcConfRowStatus object to 'destroy(6)'. The entries are can be created/modified/deleted through the Command Line Interface(CLI) also.
I32 cvcConfControllerID	1.3.6.1.4.1.9.9.141.1.1.1.1.1	Integer32	not-accessible	This is the unique value for VSI Controller(VSI Master). The VSI Slave uses this value in the message to identify the VSI Master controller.
CVC cvcConfControllerType	1.3.6.1.4.1.9.9.141.1.1.1.1.2	CvcControllerType	read-create	This object identifies the controller type. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
CVC cvcConfControllerShelfLocation	1.3.6.1.4.1.9.9.141.1.1.1.1.3	CvcControllerShelfLocation	read-create	This identifies the location of the controller shelf. This Object can be set only during row creation.
I32 cvcConfControllerLocation	1.3.6.1.4.1.9.9.141.1.1.1.1.4	Integer32	read-create	This identifies the location of the controller. This object might contain the logical slot number of the Module where the controller is running on the same shelf as the switch. This object might contain the value of the interface on the module where the controller is running on an external shelf connected to the switch. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
STR cvcConfControllerName	1.3.6.1.4.1.9.9.141.1.1.1.1.5	DisplayString	read-create	This is the name choosen by the user for the VSI Controller. This object contains Octet string of length zero, if the user does not set the value for this object. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
I32 cvcConfVpi	1.3.6.1.4.1.9.9.141.1.1.1.1.6	Integer32	read-create	This is the Virtual Path Identifier(VPI) used for connecting to the controller which is external to the switch. This object has significance only if cvcConfControllerShelfLocation is 'external(2)'. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
I32 cvcConfVci	1.3.6.1.4.1.9.9.141.1.1.1.1.7	Integer32	read-create	This is the start value of Virtual Channel Identifier(VCI) used for connecting to the controller which is external to the switch. This object has significance only if cvcConfControllerShelfLocation is 'external(2)'. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
ROW cvcConfRowStatus	1.3.6.1.4.1.9.9.141.1.1.1.1.8	RowStatus	read-create	This object is used for adding,deleting and modifying the controller configuration. The row can be created by setting this object to 'createAndGo(4)'. The row can be deleted by setting this object to 'destroy(6)'. The objects in the row can not be modified when this object contains value 'active(1)'.
cvcMIBConformance	1.3.6.1.4.1.9.9.141.3
cvcMIBCompliances	1.3.6.1.4.1.9.9.141.3.1
cvcMIBCompliance	1.3.6.1.4.1.9.9.141.3.1.1			The Compliance statement for cisco VSI Controller group.
cvcMIBGroups	1.3.6.1.4.1.9.9.141.3.2
cvcConfGroup	1.3.6.1.4.1.9.9.141.3.2.1			The objects related to configuring VSI controllers running on the same shelf as the switch.
cvcConfGroupExternal	1.3.6.1.4.1.9.9.141.3.2.2			The objects related to configuring VSI controllers running on the shelf external to the switch.

RFC description

Configures ATM switches to be aware of VSI (Virtual Switch Interface) controller information.

Start monitoring Cisco ATM switch (VSI-capable, legacy) 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-CONTROLLER-MIB

What Is CISCO-VSI-CONTROLLER-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description