| vismSessionSetNum |
.1.3.6.1.4.1.351.110.5.5.11.1.1.1 |
|
An arbitrary index that uniquely identifies a session set.
|
| vismSessionSetRowStatus |
.1.3.6.1.4.1.351.110.5.5.11.1.1.2 |
|
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.
|
| vismSessionSetState |
.1.3.6.1.4.1.351.110.5.5.11.1.1.3 |
|
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.
|
| vismSessionSetTotalGrps |
.1.3.6.1.4.1.351.110.5.5.11.1.1.4 |
|
The current number of session groups in the session set.
|
| vismSessionSetActiveGrp |
.1.3.6.1.4.1.351.110.5.5.11.1.1.5 |
|
This is the current group number in active state.
|
| vismSessionSetSwitchFails |
.1.3.6.1.4.1.351.110.5.5.11.1.1.6 |
|
The accumulated number of failed attempts to 'switch'
between session groups in this session set.
|
| vismSessionSetSwitchSuccesses |
.1.3.6.1.4.1.351.110.5.5.11.1.1.7 |
|
The accumulated number of successful attempts to
'switch' between session groups in this session set.
|
| vismSessionSetFaultTolerant |
.1.3.6.1.4.1.351.110.5.5.11.1.1.8 |
|
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.
|
| vismSessionGrpNum |
.1.3.6.1.4.1.351.110.5.5.11.2.1.1 |
|
An arbitrary index that uniquely identifies a session group.
|
| vismSessionGrpSetNum |
.1.3.6.1.4.1.351.110.5.5.11.2.1.2 |
|
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.
|
| vismSessionGrpRowStatus |
.1.3.6.1.4.1.351.110.5.5.11.2.1.3 |
|
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.
|
| vismSessionGrpState |
.1.3.6.1.4.1.351.110.5.5.11.2.1.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.
|
| vismSessionGrpCurrSession |
.1.3.6.1.4.1.351.110.5.5.11.2.1.5 |
|
This object indicates the current session that is open to
communication with MGC. There is only one active
session per session group.
|
| vismSessionGrpTotalSessions |
.1.3.6.1.4.1.351.110.5.5.11.2.1.6 |
|
The current number of sessions that are configured
in the session group.
|
| vismSessionGrpSwitchFails |
.1.3.6.1.4.1.351.110.5.5.11.2.1.7 |
|
The accumulated number of failed attempts to 'switch'
between sessions in this group.
|
| vismSessionGrpSwitchSuccesses |
.1.3.6.1.4.1.351.110.5.5.11.2.1.8 |
|
The accumulated number of successful attempts to
'switch' between sessions in this group.
|
| vismSessionGrpMgcName |
.1.3.6.1.4.1.351.110.5.5.11.2.1.9 |
|
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.
|
| vismRudpSessionNum |
.1.3.6.1.4.1.351.110.5.5.11.3.1.1 |
|
An arbitrary index that uniquely identifies a session.
|
| vismRudpSessionGrpNum |
.1.3.6.1.4.1.351.110.5.5.11.3.1.2 |
|
This indicates the session group that this session belongs to.
Once the entry is created, it cannot be modified.
|
| vismRudpSessionCnfRowStatus |
.1.3.6.1.4.1.351.110.5.5.11.3.1.3 |
|
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.
|
| vismRudpSessionPriority |
.1.3.6.1.4.1.351.110.5.5.11.3.1.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.
|
| vismRudpSessionState |
.1.3.6.1.4.1.351.110.5.5.11.3.1.5 |
|
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.
|
| vismRudpSessionCurrSession |
.1.3.6.1.4.1.351.110.5.5.11.3.1.6 |
|
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.
|
| vismRudpSessionLocalIp |
.1.3.6.1.4.1.351.110.5.5.11.3.1.7 |
|
The IP address of XGCP gateway.
|
| vismRudpSessionLocalPort |
.1.3.6.1.4.1.351.110.5.5.11.3.1.8 |
|
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).
|
| vismRudpSessionRmtIp |
.1.3.6.1.4.1.351.110.5.5.11.3.1.9 |
|
This is the IP address of the MGC. It is resolved by
using vismSessionGrpMgcName in vismSessionGrpTable.
|
| vismRudpSessionRmtPort |
.1.3.6.1.4.1.351.110.5.5.11.3.1.10 |
|
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.
|
| vismRudpSessionMaxWindow |
.1.3.6.1.4.1.351.110.5.5.11.3.1.11 |
|
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.
|
| vismRudpSessionSyncAttempts |
.1.3.6.1.4.1.351.110.5.5.11.3.1.12 |
|
Maximum number of attempts to synchronize with other side
(MGC). This object can be modified after a session is
created.
|
| vismRudpSessionMaxSegSize |
.1.3.6.1.4.1.351.110.5.5.11.3.1.13 |
|
The maximum number of octets that can be received by the peer
sending the SYN segment.
|
| vismRudpSessionMaxAutoReset |
.1.3.6.1.4.1.351.110.5.5.11.3.1.14 |
|
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.
|
| vismRudpSessionRetransTmout |
.1.3.6.1.4.1.351.110.5.5.11.3.1.15 |
|
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.
|
| vismRudpSessionMaxRetrans |
.1.3.6.1.4.1.351.110.5.5.11.3.1.16 |
|
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.
|
| vismRudpSessionMaxCumAck |
.1.3.6.1.4.1.351.110.5.5.11.3.1.17 |
|
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 .
|
| vismRudpSessionCumAckTmout |
.1.3.6.1.4.1.351.110.5.5.11.3.1.18 |
|
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.
|
| vismRudpSessionMaxOutOfSeq |
.1.3.6.1.4.1.351.110.5.5.11.3.1.19 |
|
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.
|
| vismRudpSessionNullSegTmout |
.1.3.6.1.4.1.351.110.5.5.11.3.1.20 |
|
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.
|
| vismRudpSessionTransStateTmout |
.1.3.6.1.4.1.351.110.5.5.11.3.1.21 |
|
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.
|
| vismRudpSessionType |
.1.3.6.1.4.1.351.110.5.5.11.3.1.22 |
|
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.
|
| vismRudpSessionRmtGwIp |
.1.3.6.1.4.1.351.110.5.5.11.3.1.23 |
|
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.
|
| vismRudpSessionStatNum |
.1.3.6.1.4.1.351.110.5.5.11.4.1.1 |
|
This is the index of vismRudpSessionStatEntry table.
It is the same as the index of vismRudpSessionCnfEntry
table.
|
| vismRudpSessionAutoResets |
.1.3.6.1.4.1.351.110.5.5.11.4.1.2 |
|
The accumulated number of soft reset for the session
initiated by the XGCP gateway.
|
| vismRudpSessionRcvdAutoResets |
.1.3.6.1.4.1.351.110.5.5.11.4.1.3 |
|
The accumulated number of auto resets initiated
by MGC and received by GW.
|
| vismRudpSessionRcvdInSeqs |
.1.3.6.1.4.1.351.110.5.5.11.4.1.4 |
|
The accumulated number of packets received in
sequence for the session.
|
| vismRudpSessionRcvdOutSeqs |
.1.3.6.1.4.1.351.110.5.5.11.4.1.5 |
|
The accumulated number of packets received
out of sequence.
|
| vismRudpSessionSentPackets |
.1.3.6.1.4.1.351.110.5.5.11.4.1.6 |
|
This is the number of packets sent by GW,
including SYN message.
|
| vismRudpSessionRcvdPackets |
.1.3.6.1.4.1.351.110.5.5.11.4.1.7 |
|
The accumulated number of packets received by GW
including active message.
|
| vismRudpSessionSentBytes |
.1.3.6.1.4.1.351.110.5.5.11.4.1.8 |
|
This object indicates the number of bytes sent to MGC.
|
| vismRudpSessionRcvdBytes |
.1.3.6.1.4.1.351.110.5.5.11.4.1.9 |
|
This object keeps track of the number of bytes received
from MGC.
|
| vismRudpSessionDataSentPkts |
.1.3.6.1.4.1.351.110.5.5.11.4.1.10 |
|
This object is the number of data packets sent to MGC.
|
| vismRudpSessionDataRcvdPkts |
.1.3.6.1.4.1.351.110.5.5.11.4.1.11 |
|
This object is the number of data packets received from MGC.
|
| vismRudpSessionDiscardPkts |
.1.3.6.1.4.1.351.110.5.5.11.4.1.12 |
|
This is the number of packets discarded by GW.
|
| vismRudpSessionRetransPkts |
.1.3.6.1.4.1.351.110.5.5.11.4.1.13 |
|
This is the number of packets retransmitted by GW.
|
