vismRudpSessionNum - vism Rudp Session Num - CISCO-VISM-SESSION-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

vismRudpSessionNum

vism Rudp Session Num
1.3.6.1.4.1.351.110.5.5.11.3.1.1

An arbitrary index that uniquely identifies a session. ::= { vismRudpSessionCnfEntry 1 } SYNTAX Integer32 (1..65535) MAX-ACCESS read-write STATUS current DESCRIPTION This indicates the session group that this session belongs to. Once the entry is created, it cannot be modified. ::= { vismRudpSessionCnfEntry 2 } SYNTAX INTEGER { active (1), createAndGo (4), destroy (6) } MAX-ACCESS read-write STATUS current DESCRIPTION This variable allows the user to add or delete the entry for this table. 'createAndGo': Use this to add a RUDP session in this table. RUDP vismRudpSessionNum, vismRudpSessionGrpNum, vismRudpSessionPriority, vismRudpSessionLocalPort and vismRudpSessionRmtPort are required while creating an entry for PRI(Primary Rate Interface) Backhaul. On the other hand RUDP vismRudpSessionNum, vismRudpSessionLocalPort, vismRudpSessionRmtPort, remote IP and RUDP session type are required for LAPD Trunking. 'active': This state indicates that the session is available for use by the managed device; 'destroy': Use this to delete an RUDP session from this table. Only RUDP session number is needed for deleting. The last session shall not be deleted if there are still active LAPD entries. ::= { vismRudpSessionCnfEntry 3 } SYNTAX Integer32 (1..65535) MAX-ACCESS read-write STATUS current DESCRIPTION This object specifies the RUDP session priority for this session. Once a session has been added it can not be modified. When a session fails it indicates which session the session manager should try to bring active. A lower number means higher priority. ::= { vismRudpSessionCnfEntry 4 } SYNTAX INTEGER { oos (1), is (2), unknown (3) } MAX-ACCESS read-only STATUS current DESCRIPTION This object indicates the current session operational state. The possible operational states are as follows: 'oos': Out of service state. This is the initial state when a RUDP session is created. 'is' : In service state. When a channel has been created between gateway and MGC and gateway has sent Start message the state of the session changes to 'is'. If the communication is lost between GW (gateway) and the MGC, the state of this session becomes 'oos'. 'unknown': This is the state other than the above states. ::= { vismRudpSessionCnfEntry 5 } SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION This object indicates which session has got active message from MGC. The session manager will always try to bring the first added session to active. If the current active session fails the state of this session is changed to 'oos' through vismRudpSessionState and the session manager will try to bring the 'primary-is' session with highest priority identify by the object vismRudpSessionPriority among the rest of sessions in this group to active. ::= { vismRudpSessionCnfEntry 6 } SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION The IP address of XGCP gateway.

Back to CISCO-VISM-SESSION-MIB MIB page.

IPHost Network monitor allows you to monitor vismRudpSessionNum on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco mobile switches right now.

Easy monitoring of vismRudpSessionNum with IPHost tools

MIBs list