VISM-SESSION-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
63
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
63 total| Object Name |
|---|
vismSessionGrp OBJECT IDENTIFIER .1.3.6.1.4.1.173.7.12.11 |
RFC1155-SMI Unknown .1.3.6.1.4.1.173.7.12.11 |
vismSessionSetTableThis table has entries for a collection of sessGrp(s) each
providing connectivity to a different Media gateway Controller
(MGC). SEQUENCE OF VismSessionSetEntry .1.3.6.1.4.1.173.7.12.11.1 |
vismSessionSetEntryAn entry for vismSessionSetTable. VismSessionSetEntry .1.3.6.1.4.1.173.7.12.11.1.1 |
vismSessionSetNumThis is the logical index of this table.
Currently only set 1 is used and all the signaling channels are
implicitly mapped to set 1.ro INTEGER .1.3.6.1.4.1.173.7.12.11.1.1.1 |
vismSessionSetRowStatusThis variable is used to allow add or delete a session set.
createAndGo: Use this to add an entry in set table.
vismSessionSetNum and vismSessionSetFaultTolerant are the
mandatory parameters while adding a set. Currently only
one set (set #1) can be created.
The entry will become 'active' after creation.
A set entry may be deleted by setting this object to 'destory'.
Deletion of a set is not allowed if there is still group in
this set.rw Enumeration .1.3.6.1.4.1.173.7.12.11.1.1.2 |
vismSessionSetStateWhen an entry in sessionSet table 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).
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.ro Enumeration .1.3.6.1.4.1.173.7.12.11.1.1.3 |
vismSessionSetTotalGrpsThis counter keeps track the number of session groups that has
been added to a session set.ro INTEGER .1.3.6.1.4.1.173.7.12.11.1.1.4 |
vismSessionSetActiveGrpThis is the current active group number.ro INTEGER .1.3.6.1.4.1.173.7.12.11.1.1.5 |
vismSessionSetSwitchFailsThis counter keeps track of failed attempts to switch between
session groups in this set.ro Counter .1.3.6.1.4.1.173.7.12.11.1.1.6 |
vismSessionSetSwitchSuccessesThis counter keeps track of successful attempts to switch
between session groups in this set.ro Counter .1.3.6.1.4.1.173.7.12.11.1.1.7 |
vismSessionSetFaultTolerantThis object indicates whether the set configuration is fault
tolerant or not.
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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.173.7.12.11.1.1.8 |
vismSessionGrpTableThis table has entries for a collection of sessions SEQUENCE OF VismSessionGrpEntry .1.3.6.1.4.1.173.7.12.11.2 |
vismSessionGrpEntryAn entry for vismSessionGrpTable. VismSessionGrpEntry .1.3.6.1.4.1.173.7.12.11.2.1 |
vismSessionGrpNumIndex for vismSessionGrpEntry table.
Currently the range of 1 to 16 is used.
One set can have upto two groups.ro INTEGER .1.3.6.1.4.1.173.7.12.11.2.1.1 |
vismSessionGrpSetNumThis is the session set number to which this session Group
belongs.
Once the entry is created this object cannot be modified.rw INTEGER .1.3.6.1.4.1.173.7.12.11.2.1.2 |
vismSessionGrpRowStatusThis variable allows to add or delete an entry in this table.
createAndGo: Use this to add an entry in this table.
vismSessionGrpNum, vismSessionGrpSetNum and vismSessionGrpMgcName
are required to add an entry. Before adding the session group,
the session set should already be created.
active: This value is returned once the session group is
created
destroy: Use this to delete a session group. Session group
number is the only mandatory parameter to delete an entry.rw Enumeration .1.3.6.1.4.1.173.7.12.11.2.1.3 |
vismSessionGrpState'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.ro Enumeration .1.3.6.1.4.1.173.7.12.11.2.1.4 |
vismSessionGrpCurrSessionThis object indicates the current session that is open to
communication with MGC.
There is only one active session per session group.ro INTEGER .1.3.6.1.4.1.173.7.12.11.2.1.5 |
vismSessionGrpTotalSessionsThis object keeps track the total number of sessions that
have been added to this group.ro INTEGER .1.3.6.1.4.1.173.7.12.11.2.1.6 |
vismSessionGrpSwitchFailsThis counter keeps track of failed attempts to switch between
sessions in this group.ro Counter .1.3.6.1.4.1.173.7.12.11.2.1.7 |
vismSessionGrpSwitchSuccessesThis counter keeps track of successful attempts to switch
between sessions in this group.ro Counter .1.3.6.1.4.1.173.7.12.11.2.1.8 |
vismSessionGrpMgcNameThis denotes the name of the media gateway controller.
This corresponds to a domain name under which the MGC
could also be registered in a DNS.
Once this entry becomes active, this value may not be modified.rw DisplayString .1.3.6.1.4.1.173.7.12.11.2.1.9 |
vismRudpSessionCnfTableThis table has entries of sessions, which are the connection
between MGC and a gateway (VISM). 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. SEQUENCE OF VismRudpSessionCnfEntry .1.3.6.1.4.1.173.7.12.11.3 |
vismRudpSessionCnfEntryAn entry for vismSessionCnfEntry. VismRudpSessionCnfEntry .1.3.6.1.4.1.173.7.12.11.3.1 |
vismRudpSessionNumThis is the index of vismRudpSessionCnfEntry table.
Currently the range of 1 to 64 is used.
One group can have maximum four sessions.ro INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.1 |
vismRudpSessionGrpNumThis indicates the session group that this session belongs to.
Currently the range of 1 to 16 is used.
Once the entry is created, it cannot be modified.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.2 |
vismRudpSessionCnfRowStatusThis 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 session number, session group number, priority, local
port and remote port are required while creating an entry for
PRI Backhaul. On the other hand Rudp session number, local
port, remote port, remote VISM IP and rudp session type are
required for Lapd trunking.
active: This value is returned, once the row is created.
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.rw Enumeration .1.3.6.1.4.1.173.7.12.11.3.1.3 |
vismRudpSessionPriorityThis object is used when creating a Rudp 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.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.4 |
vismRudpSessionState'oos': Out of service state. This is the initial state when
create a RUDP session.
'is': In service state. When a channel has been created between
gateway (VISM) and MGC and VISM has sent Start message the
state of the session changes to 'is'.
If the communication is lost between VISM and the MGC, the state
of this session becomes 'oos'.
'unknown': This is the state other than the above states.ro Enumeration .1.3.6.1.4.1.173.7.12.11.3.1.5 |
vismRudpSessionCurrSessionThis 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' and the session manager will try to bring the
'primary-is' session with highest priority among the rest of
sessions in this group to active.ro INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.6 |
vismRudpSessionLocalIpThe IP address of gateway (VISM).ro IpAddress .1.3.6.1.4.1.173.7.12.11.3.1.7 |
vismRudpSessionLocalPortThe port number of gateway (VISM) for this session.
It can be modified after creation. This port number should
be unique across other sessions and XGCP/SRCP.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.8 |
vismRudpSessionRmtIpThis is the IP address of the media gateway controller.
It is resolved by using vismSessionGrpMgcName in
vismSessionGrpTable.ro IpAddress .1.3.6.1.4.1.173.7.12.11.3.1.9 |
vismRudpSessionRmtPortThe 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.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.10 |
vismRudpSessionMaxWindowThis object is the maximum number of segments that should be
sent without getting an acknowledgment, i.e. the max size of
the receive window in segments. This is used for flow control.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.11 |
vismRudpSessionSyncAttemptsMaximum number of attempts to synchronize with other side (MGC).
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.12 |
vismRudpSessionMaxSegSizeThe maximum number of octets that can be received by the peer
sending the SYN segment.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.13 |
vismRudpSessionMaxAutoResetThe 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.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.14 |
vismRudpSessionRetransTmoutThe timeout value for retransmission of unacknowledged
packets in milliseconds. This is a negotiable parameter,
MGC and VISM must agree on the same value for this parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.15 |
vismRudpSessionMaxRetransThe 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 VISM must agree on the value for this parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.16 |
vismRudpSessionMaxCumAckThis object indicates the maximum number of acknowledgments
that will be accumulated before sending an acknowledgment
if another segment is not sent. A value of 0 indicates an
acknowledgment segment will be sent immediately when a data,
null, or reset segment is received. Negotiable parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.17 |
vismRudpSessionCumAckTmoutThis object is the timeout value for sending an acknowledgment
segment if another segment is not sent. This value is
specified in milliseconds. This parameter should be smaller
than rudpRetransTmout. Negotiable parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.18 |
vismRudpSessionMaxOutOfSeqThis object is the maximum number of out of sequence packets
that will be accumulated before an EACK 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. Negotiable parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.19 |
vismRudpSessionNullSegTmoutThis object is the number of milliseconds of idle time
before sending a null segment. A value of 0 disables null
segments. Negotiable parameter.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.20 |
vismRudpSessionTransStateTmoutThis object indicates the number of milliseconds to wait
for transfer state before an auto reset occurs. 0
indicates the connection will be auto-reset immediately
and would not be used with redundant links.
This object can be modified after a session is created.rw INTEGER .1.3.6.1.4.1.173.7.12.11.3.1.21 |
vismRudpSessionTypeThis 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.rw Enumeration .1.3.6.1.4.1.173.7.12.11.3.1.22 |
vismRudpSessionRmtGwIpThis is the IP address of the remote VISM. This will be used only
for Lapd Trunking applications and the vismRudpSessionType must be
set to Lapd trunking.rw IpAddress .1.3.6.1.4.1.173.7.12.11.3.1.23 |
vismRudpSessionStatTableThis table keeps track of state and connection-specific
counts. It is per connection based. SEQUENCE OF VismRudpSessionStatEntry .1.3.6.1.4.1.173.7.12.11.4 |
vismRudpSessionStatEntryAn entry for vismSessionStatEntry. VismRudpSessionStatEntry .1.3.6.1.4.1.173.7.12.11.4.1 |
vismRudpSessionStatNumThis is the index of vismRudpSessionStatEntry table.
Currently the range of 1 to 64 is used.
It is the same as the index of vismRudpSessionCnfEntry
table.ro INTEGER .1.3.6.1.4.1.173.7.12.11.4.1.1 |
vismRudpSessionAutoResetsAuto reset is also known as soft reset. VISM (gateway)
initiates an auto reset when it detects that a connection
has failed.
This keeps track of the number of auto resets initiated
by VISM.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.2 |
vismRudpSessionRcvdAutoResetsThis is the counter for the number of auto resets initiated
by MGC and received by VISM.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.3 |
vismRudpSessionRcvdInSeqsThis object indicates number of packets received in sequence.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.4 |
vismRudpSessionRcvdOutSeqsNumber of packets received out of sequence.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.5 |
vismRudpSessionSentPacketsThis is the number of packets sent by VISM.
Including SYN message.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.6 |
vismRudpSessionRcvdPacketsThis is the number of packets received by VISM.
Including active message.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.7 |
vismRudpSessionSentBytesThis object indicates the number of bytes sent to MGC.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.8 |
vismRudpSessionRcvdBytesThis object keeps track of the number of bytes received
from MGC.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.9 |
vismRudpSessionDataSentPktsThis object is the number of data packets sent to MGC.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.10 |
vismRudpSessionDataRcvdPktsThis object is the number of data packets received from MGC.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.11 |
vismRudpSessionDiscardPktsThis is the number of packets discarded.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.12 |
vismRudpSessionRetransPktsThis is the number of packets retransmitted.ro Counter .1.3.6.1.4.1.173.7.12.11.4.1.13 |