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.
Parsed from file CISCO-VISM-SESSION-MIB.mib
Module: CISCO-VISM-SESSION-MIB
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.
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.
Parsed from file CISCO-VISM-SESSION-MIB.my.txt
Company: None
Module: CISCO-VISM-SESSION-MIB
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.
vismSessionSetState OBJECT-TYPE SYNTAX INTEGER { idle (1), oos (2), activeIs (3), standbyIs (4), fullIs (5), unknown (6) } MAX-ACCESS read-only STATUS current 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. " ::= { vismSessionSetEntry 3 }
vismSessionSetState OBJECT-TYPE SYNTAX INTEGER { idle(1), oos(2), activeIs(3), standbyIs(4), fullIs(5), unknown(6) } ACCESS read-only STATUS mandatory 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. " ::= { vismSessionSetEntry 3 }
Vendor: Stratacom
Module: VISM-SESSION-MIB
[Automatically extracted from oidview.com]
vismSessionSetState OBJECT-TYPE SYNTAX INTEGER { idle (1), oos (2), activeIs (3), standbyIs (4), fullIs (5), unknown (6) } MAX-ACCESS read-only STATUS current 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. " ::= { vismSessionSetEntry 3 }
vismSessionSetState OBJECT-TYPE SYNTAX INTEGER { idle (1), oos (2), activeIs (3), standbyIs (4), fullIs (5), unknown (6) } MAX-ACCESS read-only STATUS current 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. " ::= { vismSessionSetEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.5.5.11.1.1.1 | vismSessionSetNum | 0 | 0 | An arbitrary index that uniquely identifies a session set. |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.2 | vismSessionSetRowStatus | 0 | 0 | This variable is used to allow add or delete a session set. 'active': This state indicates that the session set is available for … |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.4 | vismSessionSetTotalGrps | 0 | 0 | The current number of session groups in the session set. |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.5 | vismSessionSetActiveGrp | 0 | 0 | This is the current group number in active state. |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.6 | vismSessionSetSwitchFails | 0 | 0 | The accumulated number of failed attempts to 'switch' between session groups in this session set. |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.7 | vismSessionSetSwitchSuccesses | 0 | 0 | The accumulated number of successful attempts to 'switch' between session groups in this session set. |
| 1.3.6.1.4.1.351.110.5.5.11.1.1.8 | vismSessionSetFaultTolerant | 0 | 0 | This object indicates whether the set configuration is fault tolerant, 'true(1)' indicate fault tolerant and 'false(2)' non fault… |