CISCO-VISM-DSX1-MIB :: vismDsx1AdminStateControl

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VISM-DSX1-MIBvismDsx1AdminStateControl

vismDsx1AdminStateControl

Module: CISCO-VISM-DSX1-MIB

OID (symbolic): CISCO-VISM-DSX1-MIB::vismDsx1AdminStateControl

OID (numeric): 1.3.6.1.4.1.351.110.4.3.5.1.1.1.32

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This control object is used to change the service state of the line from 'is' to 'coos' or from 'coos' to 'is'. The resulting service state of the line is represented by vismDsx1State.

'inService': Transition vismDsx1State to 'is'(in service). In the course, the MG's MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy.

'forcefulOutOfService': Take the line out-of-service forcefully. This releases any resources at the line. In the course, the MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy.

'gracefulOutOfService': Take the line out-of-service gracefully. If there are no resources existing, vismDsx1State transitions to coos immediately. If resources exist, vismDsx1State transitions to poos thus initiating a graceful shutdown. In the course, the MG's MGCs may get notified of this transition, e.g. in the case of MGCP through emission of RSIPs to registered call agents according to policy. 'inactive': Indicates the vismDsx1State is in inactive state.

What is vismDsx1AdminStateControl?

This read-write INTEGER is a control object used to change the line's service state, transitioning it from in-service to command-out-of-service or back, with the resulting state reflected in vismDsx1State. The graceful option lets active calls complete before taking the line down, while forceful immediately removes it, giving an admin control over how disruptive a maintenance action will be. For example, an admin scheduling planned maintenance on a line would use gracefulOutOfService to let existing calls finish rather than dropping them abruptly with forcefulOutOfService.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.4.3.5.1.1.1.32
snmpwalk -v2c -c public <target> CISCO-VISM-DSX1-MIB::vismDsx1AdminStateControl

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.4.3.5.1.1.1.32.1
snmpget -v2c -c public <target> CISCO-VISM-DSX1-MIB::vismDsx1AdminStateControl.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.4.3.5.1.1.1.32.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-DSX1-MIB::vismDsx1AdminStateControl 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 (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.4basisLinesBASIS-MIB
1.3.6.1.4.1.351.110.4.3dsx1BASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.4.3.5dsx1VismCISCO-VISM-DSX1-MIB
1.3.6.1.4.1.351.110.4.3.5.1dsx1VismCnfGrpCISCO-VISM-DSX1-MIB
1.3.6.1.4.1.351.110.4.3.5.1.1dsx1VismCnfGrpTableCISCO-VISM-DSX1-MIB
1.3.6.1.4.1.351.110.4.3.5.1.1.1dsx1VismCnfGrpEntryCISCO-VISM-DSX1-MIB
1.3.6.1.4.1.351.110.4.3.5.1.1.1.32vismDsx1AdminStateControlCISCO-VISM-DSX1-MIB