SESSION-MIB

All MIBs › SESSION-MIB

Organization: SAGEM/DR Tolbiac Centre

Last Updated: 2002-06-11

Category: Microwave Radio - SAGEM

Description: Manages SAGEM/DR device session establishment, teardown, and active connection state.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SESSION-MIB?

SESSION-MIB is a SAGEM/DR network device module addressing coordination of access when multiple management interfaces, SNMP, HTTP, CLI, and vt100 terminal sessions, attempt to modify the same equipment configuration concurrently. It models session establishment, teardown, and the state of currently active management sessions across these different access methods, including session type and inactivity tracking. Its monitoring value is therefore about software/management-plane status: administrators can see which interfaces have open sessions, detect stuck or long-idle sessions via an inactivity timer object, and understand access-conflict situations before they cause configuration errors. The module notes that session-related trap functionality was superseded by a logTrap defined in a companion LOG-MIB, showing an explicit dependency on that module for event notification. It is deployed on SAGEM/DR equipment where multiple simultaneous management channels are supported and administrators need visibility into who currently holds configuration access. Engineers can download the SESSION-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SESSION-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management

Monitoring Examples

No object/table names were retained in this extract beyond historical change-log references (sessionTrap, sessionReason, tInactivity, sessionType), so a fully concrete polling walk cannot be built from confirmed current identifiers; based on the description, an administrator would poll active-session state to see which of SNMP/HTTP/CLI/vt100 currently holds a configuration session, check an inactivity/timeout value to spot a session left open unnecessarily, and rely on LOG-MIB's logTrap, which replaced the deprecated sessionTrap, for notification of session events.

What Can Be Monitored

active management session type (SNMP/HTTP/CLI/vt100)
session inactivity/timeout
session establishment/teardown events

Imported Objects

From EQUIPMENT-MIB

SagemBoolean

From SAGEM-DR-MIB

sagemDr

MODULE-IDENTITY

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tLock OID:

Select an SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management (concurrent management-session tracking) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tLock into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of minutes for which a write session is active on the equipment. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
SAG savePending	1.3.6.1.4.1.1038.201.20	SagemBoolean	read-only	Return TRUE if the write session is unlocked for more than 30 seconds
session	1.3.6.1.4.1.1038.201			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
IP sessionIp	1.3.6.1.4.1.1038.201.2	IpAddress	read-only	IP address of the application that holds the session
INT sessionType	1.3.6.1.4.1.1038.201.3	INTEGER	read-only	Type of the application protocol that holds the session
INT tInactivity	1.3.6.1.4.1.1038.201.6	INTEGER	read-write	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.
INT tLockEx	1.3.6.1.4.1.1038.201.1	INTEGER	read-write	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.
INT tLockDefault	1.3.6.1.4.1.1038.201.5	INTEGER	read-write	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

RFC description

Session management and access conflict handling for SAGEM network equipment configuration.

Start monitoring SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management (concurrent management-session tracking) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SESSION-MIB