CISCO-VISM-SESSION-MIB: View SNMP OID List / Download MIB

The vismSessionSetTable has entries for a collection of session group. Each entry provides connectivity to a different MGC.

An entry for vismSessionSetTable.

An arbitrary index that uniquely identifies a session set.

This variable is used to allow add or delete a session set. 'active': This state indicates that the session set is available for use by the managed device; 'createAndGo': Use this to add an entry in this table. `destroy': the status supplied by a management station wishing to delete all of the instances associated with this session group. Deletion of a set is not allowed if there is still group in this set. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

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. Enumeration: 'fullIs': 5, 'activeIs': 3, 'oos': 2, 'unknown': 6, 'idle': 1, 'standbyIs': 4.

The current number of session groups in the session set.

This is the current group number in active state.

The accumulated number of failed attempts to 'switch' between session groups in this session set.

The accumulated number of successful attempts to 'switch' between session groups in this session set.

This object indicates whether the set configuration is fault tolerant, 'true(1)' indicate fault tolerant and 'false(2)' non fault tolerant. If the set is fault tolerant then there can be two groups in this set. If the set is non fault tolerant then only one group can be added in this set. Once the entry is created this object cannot be modified.

This table has entries for a collection of sessions.

An entry for vismSessionGrpTable.

An arbitrary index that uniquely identifies a session group.

This object identify session set number to which this session Group belongs. Once the entry is created this object cannot be modified. The same session set can only be assigned to two different session groups.

This variable allows to add or delete an entry in this table. 'createAndGo': Use this to add an entry in this table. vismSessionGrpSetNum and vismSessionGrpMgcName are required to add an entry. Before adding the session group, The session set should already be created. 'active': This state indicates that the session group is available for use by the managed device; `destroy': the status supplied by a management station wishing to delete all of the instances associated with this session group. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

This object indicates the operational state of the session group. The possible operational states are as follows: 'idle': This is the initial state. 'oos' : Out of service state. when a session group has been created the state of the session group becomes 'oos' or when all sessions belonging to this group are deleted, session group state becomes 'oos' 'is': In service state. After at least one session has been added to the group, socket has been successfully set up and the session has sent a START message to MGC the group state changes to 'is'. 'unknown': This is the state other than the above states. Enumeration: 'unknown': 4, 'idle': 1, 'is': 3, 'oos': 2.

This object indicates the current session that is open to communication with MGC. There is only one active session per session group.

The current number of sessions that are configured in the session group.

The accumulated number of failed attempts to 'switch' between sessions in this group.

The accumulated number of successful attempts to 'switch' between sessions in this group.

This denotes the name of the MGC. This corresponds to a domain name under which the MGC could also be registered in a DNS(Domain Named System). Once this entry becomes active, this value may not be modified.

This table has entries of sessions, which are the connection between MGC and a gateway. A session is identified by a local IP address, port, remote IP address and remote port. The combination of these four numbers has to be unique to identify one session. This table also maintains the configuration for every session.

An entry for vismSessionCnfEntry.

An arbitrary index that uniquely identifies a session.

This indicates the session group that this session belongs to. Once the entry is created, it cannot be modified.

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. Enumeration: 'active': 1, 'destroy': 6, 'createAndGo': 4.

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.

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. Enumeration: 'unknown': 3, 'is': 2, 'oos': 1.

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.

The IP address of XGCP gateway.

The port number of XGCP gateway for this session. It can be modified after creation. This port number should be unique across other sessions and XGCP/SRCP(Simple Resource Coordination Protocol).

This is the IP address of the MGC. It is resolved by using vismSessionGrpMgcName in vismSessionGrpTable.

The port number of MGC for this session. It can be modified after creation. This port number should be unique across other sessions and XGCP/SRCP.

This object is the maximum number of segments that should be sent without getting an acknowledgment, i.e. the maximum size of the receive window in segments. This is used for flow control.

Maximum number of attempts to synchronize with other side (MGC). This object can be modified after a session is created.

The maximum number of octets that can be received by the peer sending the SYN segment.

The maximum number of consecutive auto reset that will be performed before a connection is reset. A value 0 indicates that an auto reset will not be attempted, the connection will be reset immediately if an auto reset condition occurs.

The timeout value for retransmission of unacknowledged packets. This is a negotiable parameter, MGC and GW must agree on the same value for this parameter.

The maximum number of times consecutive retransmission will be attempted before the connection is considered broken. A value 0 indicates retransmission should be attempted forever. This is a negotiable parameter, both MGC and GW must agree on the value for this parameter.

This object indicates the maximum number of acknowledgments that will be accumulated before sending an acknowledgment. A value of 0 indicates an acknowledgment segment will be sent immediately when a data, null, or reset segment is received. This is a negotiable parameter between MGC GW and .

This object is the timeout value for sending an acknowledgment segment. This value is specified in milliseconds. This parameter should be smaller than vismRudpSessionRetransTmout. This is a negotiable parameter betwen MGC and GW.

This object is the maximum number of out of sequence packets that will be accumulated before an EACK(Extended acknowledgement) segment is sent. The EACK segment is used to acknowledge segments received out of sequence. A value of 0 indicates a EACK will be sent immediately if an out of order segment is received. This is a negotiable parameter between MGC and GW.

This object specifies the session idle timeout. When the session idle time reaches this idle timeout value, a null segment will be sent to MGC from this GW. segments. This is a negotiable parameter between MGC and GW.

This object indicates the number of milliseconds to wait for transfer state before an auto reset occurs.The value 0 indicates the connection will be auto-reset immediately and would not be used with redundant links.

This object indicates if the session is configured for Trunking or PRI Backhaul. By default the object is set to 'backhaul' and it needs to set to 'lapdTrunking' if LAPD Trunking needs to be done. Enumeration: 'lapdTrunking': 2, 'backhaul': 1.

This is the IP address of the remote GW. This will be used only for 'lapdTrunking' applications and the vismRudpSessionType must be set to LAPD Trunking.

This table keeps track of state and session-specific counts. It is per session based.

An entry for vismSessionStatEntry.

This is the index of vismRudpSessionStatEntry table. It is the same as the index of vismRudpSessionCnfEntry table.

The accumulated number of soft reset for the session initiated by the XGCP gateway.

The accumulated number of auto resets initiated by MGC and received by GW.

The accumulated number of packets received in sequence for the session.

The accumulated number of packets received out of sequence.

This is the number of packets sent by GW, including SYN message.

The accumulated number of packets received by GW including active message.

This object indicates the number of bytes sent to MGC.

This object keeps track of the number of bytes received from MGC.

This object is the number of data packets sent to MGC.

This object is the number of data packets received from MGC.

This is the number of packets discarded by GW.

This is the number of packets retransmitted by GW.

The MIB module contain the RUDP session parameter. The relationship between session set, session group and RUDP session is that: For fault tolerant case each session set contains two groups. Each group connects to one MGC(Media Gateway Controller), One active, one standby. If one MGC fails, the other MGC will inform the session mamager to switch over. If the set configuration is non-fault tolerant, each set contains one group. Each session group contains upto four RUDP sessions. Session set is explicitly created first, then session group can be created in this set. After session group is created, session can be created in the group. For deletion, session has to be deleted first. However, the last session can not be deleted if there is still LAPD(Link Access Procedure on the D-channel) entry. A group can only be deleted if there is no more session in it. Session set will be deleted when the last group in the set has been deleted.

A collection of objects providing session set configuration.

A collection of objects providing session group configuration.

A collection of objects providing session configuration.

A collection of objects providing session relayed statistics information.

The compliance statement for objects related to CISCO-VISM-SESSION-MIB.