All MIBs › CISCO-VISM-SESSION-MIB › vismSessionSetState
vismSessionSetState
Module: CISCO-VISM-SESSION-MIB
OID (symbolic): CISCO-VISM-SESSION-MIB::vismSessionSetState
OID (numeric): 1.3.6.1.4.1.351.110.5.5.11.1.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: When an entry in vismSessionSetTable is created and no group has been added to this set yet or group has been created in this set but no session has been added yet the set state is 'idle'.
After a group has been created in this set and one session has been added to the group the set state becomes 'oos',i.e, out of service.
After successfully open socket and the session has sent START message to MGC, the state of the set will be changed based on whether this set is fault tolerant(FT) or none fault tolerant(NFT) specify in vismSessionSetFaultTolerant.
In NFT case the set state becomes 'activeIs'.
In FT case, if one session from a group received an active message from MGC and no standby message received from a session in the other group, the state of the set will change to 'activeIs'.
On the other hand, if at least one session from a group received standby message from MGC and no other session from the other group received active message then the set state is transferred to 'standbyIs'.
The set becomes 'fullIs' when at least one session from one group receives active message and at least one session from the other group receives standby message.
'unknown' is a state other than the above states.
What is vismSessionSetState?
This read-only INTEGER reports the operational state of a session set, progressing from idle (no group or no session yet added) to oos (out of service, once a group exists with a session added) to activeIs, standbyIs, fullIs, or unknown depending on session activity. An admin cares because this state machine reflects exactly how far along a redundant call-agent session set has progressed toward being fully in service. For example, an operator troubleshooting why a fault-tolerant session set never reaches full service would check whether it is stuck at oos, indicating a session was added but never successfully opened a socket and sent a START message.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.11.1.1.3 snmpwalk -v2c -c public <target> CISCO-VISM-SESSION-MIB::vismSessionSetState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.11.1.1.3.1 snmpget -v2c -c public <target> CISCO-VISM-SESSION-MIB::vismSessionSetState.1
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-SESSION-MIB::vismSessionSetState 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 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 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.5.11 | vismSessionGrp | CISCO-VISM-SESSION-MIB |
| 1.3.6.1.4.1.351.110.5.5.11.1 | vismSessionSetTable | CISCO-VISM-SESSION-MIB |
| 1.3.6.1.4.1.351.110.5.5.11.1.1 | vismSessionSetEntry | CISCO-VISM-SESSION-MIB |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.3 | vismSessionSetState | CISCO-VISM-SESSION-MIB |