SESSION-MIB
SAGEMCOM SASModification: Date: 20 12 1999 Description: modification of comments Name: sessionTrap Description: sessionTrap and sessionReason are no more used in SESSION-MIB. They have been replaced by a logTrap (see LOG-MIB) New Object: Date: 19 11 1999 Name: tInactivity Description: Name: sessionType Description: Add of tpiEmulated Creation: Description: This MIB module gives information about a way to handle access conflicts between several applications (SNMP, HTTP, CLI, vt100) that could try to modify the equipment configuration at the same time
snmptranslate -m SESSION-MIB -Tpsnmpwalk -v2c -c <community> -m SESSION-MIB <host> 1.3.6.1.4.1.1038.201Imports
| EQUIPMENT-MIB | SagemBoolean |
|---|---|
| SAGEM-DR-MIB | sagemDr |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Bits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DisplayString, PhysAddress, TEXTUAL-CONVENTION |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| Isession | 1.3.6.1.4.1.1038.201 | |||
identity Modification: Date: 20 12 1999 Description: modification of comments Name: sessionTrap Description: sessionTrap and sessionReason are no more used in SESSION-MIB. They have been replaced by a logTrap (see LOG-MIB) New Object: Date: 19 11 1999 Name: tInactivity Description: Name: sessionType Description: Add of tpiEmulated Creation: Description: This MIB module gives information about a way to handle access conflicts between several applications (SNMP, HTTP, CLI, vt100) that could try to modify the equipment configuration at the same time | ||||
| StLock | 1.3.6.1.4.1.1038.201.1 | INTEGER (0..30) | RW | |
scalar · INTEGER (0..30) · read-write · current Number of minutes for which a write session is active on the equipment. When the value of this variable is 0, the equipment is not locked. When a SNMP manager (iONOSANMSupervisor and Operator) start a write session, tLock can be set to a value by the manager (up to 30 minutes, so it has time to configure the equipment). Each time an action is done under the equipment tLock is set again to its value. tLock is a decremental counter; when the value of tLock return to 0, the write session is ended and the equipment is unlocked. The SNMP manager can choose to unlock the equipment by setting the value of tLock to 0 before it reach this value itself. | ||||
| SsessionIp | 1.3.6.1.4.1.1038.201.2 | IpAddress | RO | |
scalar · IpAddress · read-only · current IP address of the application that holds the session | ||||
| SsessionType | 1.3.6.1.4.1.1038.201.3 | INTEGER | RO | |
scalar · INTEGER · read-only · current Type of the application protocol that holds the session
| ||||
| StLockDefault | 1.3.6.1.4.1.1038.201.5 | INTEGER (0..20) | RW | |
scalar · INTEGER (0..20) · read-write · current tLockDefault is used to define initial value of tLock.
tLockDefault can be changed only by iONOSANMSupervisor or
by dIRECTACCESSsupervisor.
The normal value is 10 minutes | ||||
| StInactivity | 1.3.6.1.4.1.1038.201.6 | INTEGER (0..60) | RW | |
scalar · INTEGER (0..60) · read-write · current The normal configuration is tInactivity > tLock; tInactivityDefault is about 30 min. The session with a manager is closed by the equipment if there is no activity during tInactivity min. It is not used with SNMP. This is used to protect the acces to the manager when the operator is not there during a long time. | ||||
| SsavePending | 1.3.6.1.4.1.1038.201.20 | SagemBoolean | RO | |
scalar · SagemBoolean · read-only · current Return TRUE if the write session is unlocked for more than 30 seconds | ||||