All MIBs › CISCO-VISM-CONN-MIB › vismConnServiceType
vismConnServiceType
Module: CISCO-VISM-CONN-MIB
OID (symbolic): CISCO-VISM-CONN-MIB::vismConnServiceType
OID (numeric): 1.3.6.1.4.1.351.110.5.5.3.1.1.1.18
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This specifies the class of service or service type 'cbr (1)' : Constant Bit Rate.
'vbr-rt (2)' : Variable Bit Rate 1 (Real Time) although, VISM does not do any kind of traffic shaping, the PVC has to be specified as vbr-rt for PXM to treat the connection as a VBR1 connection. Variable Bit Rate is not currently supported.
'vbr-nrt (3)' : Variable Bit Rate 1 (non real time) the service type of the connection cannot be modified once the PVC is added.
'vbr3-rt (4)' : Variable Bit Rate 3 (Real Time) although, VISM does not do any kind of traffic shaping, the PVC has to be specified as vbr3-rt for PXM to treat the connection as a VBR3 connection. Variable Bit Rate is not currently supported.
'vbr2-rt (5)' : Variable Bit Rate 2 (Real Time) although, VISM does not do any kind of traffic shaping, the PVC has to be specified as 'vbr2-rt' for PXM to treat the connection as a VBR2 connection. Variable Bit Rate is not currently supported.
'vbr2-nrt (6)' : Variable Bit Rate 2 (non real time) the service type of the connection cannot be modified once the PVC is added.
'vbr3-nrt (7)' : Variable Bit Rate 3 (non real time) the service type of the connection cannot be modified once the PVC is added.
What is vismConnServiceType?
This read-write INTEGER object specifies the ATM class of service for a connection, including cbr (Constant Bit Rate) and several vbr (Variable Bit Rate) variants, noting that VBR is specified for PXM's routing purposes even though VISM itself performs no traffic shaping and VBR is not currently supported. This setting tells the PXM switching layer how to treat and route the connection even though the actual shaping behavior on VISM itself doesn't vary by this setting. An engineer setting up a connection expected to be treated as VBR for routing purposes would still need to configure this object as vbr-rt even knowing VISM won't perform true VBR shaping.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.18 snmpwalk -v2c -c public <target> CISCO-VISM-CONN-MIB::vismConnServiceType
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.18.1 snmpget -v2c -c public <target> CISCO-VISM-CONN-MIB::vismConnServiceType.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.18.1 i <value>
Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VISM-CONN-MIB::vismConnServiceType OID value, configure state conditions and alerts, and monitor any Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) from a single console.
OID Breakdown
Upper-level ancestors (12 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.351 | stratacom | CISCOWAN-SMI |
| 1.3.6.1.4.1.351.110 | basis | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5 | basisServices | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.5 | voice | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.5.3 | vismChanGrp | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.5.3.1 | vismChanCnfGrp | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.5.3.1.1 | vismChanCnfGrpTable | CISCO-VISM-CONN-MIB |
| 1.3.6.1.4.1.351.110.5.5.3.1.1.1 | vismChanCnfGrpEntry | CISCO-VISM-CONN-MIB |
| 1.3.6.1.4.1.351.110.5.5.3.1.1.1.18 | vismConnServiceType | CISCO-VISM-CONN-MIB |