cisco-vsi-controller-mib.mib object

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2025 can import MIB file cisco-vsi-controller-mib and use it to monitor vendor specific OID's.

cisco-vsi-controller-mib file content

Object view of cisco-vsi-controller-mib:

Scalar Object
cvcConfEntry	.1.3.6.1.4.1.9.9.141.1.1.1.1
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.
Tabular Object
cvcConfControllerID	.1.3.6.1.4.1.9.9.141.1.1.1.1.1
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.
cvcConfControllerType	.1.3.6.1.4.1.9.9.141.1.1.1.1.2
This object identifies the controller type. This object may not be modified if the associated cvcConfRowStatus is equal to 'active(1)'.
cvcConfControllerShelfLocation	.1.3.6.1.4.1.9.9.141.1.1.1.1.3
This identifies the location of the controller shelf. This Object can be set only during row creation.
cvcConfControllerLocation	.1.3.6.1.4.1.9.9.141.1.1.1.1.4
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)'.
cvcConfControllerName	.1.3.6.1.4.1.9.9.141.1.1.1.1.5
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)'.
cvcConfVpi	.1.3.6.1.4.1.9.9.141.1.1.1.1.6
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)'.
cvcConfVci	.1.3.6.1.4.1.9.9.141.1.1.1.1.7
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)'.
cvcConfRowStatus	.1.3.6.1.4.1.9.9.141.1.1.1.1.8
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)'.
Table
cvcConfTable	.1.3.6.1.4.1.9.9.141.1.1.1
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.
Object Identifier
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
cvcMIBConformance	.1.3.6.1.4.1.9.9.141.3
cvcMIBCompliances	.1.3.6.1.4.1.9.9.141.3.1
cvcMIBGroups	.1.3.6.1.4.1.9.9.141.3.2
Group
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.