OPSUBP-DEVICE-SIGNALING-MIB

All MIBs › OPSUBP-DEVICE-SIGNALING-MIB

Organization: Nortel Networks OPS group

Last Updated: 2013-04-12

Category: Optical Networking

Description: Manages device signaling protocol objects for Nortel Networks OPS optical networking equipment.

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 OPSUBP-DEVICE-SIGNALING-MIB?

OPSUBP-DEVICE-SIGNALING-MIB is a Nortel Networks SNMP module for the OPS optical networking equipment line, specifically defining notification objects related to UBP (User-Based Policy) device signaling and EAP (Extensible Authentication Protocol, i.e., 802.1X) access-port authentication events. Rather than exposing polled status tables, this MIB is built almost entirely around notification/trap objects that carry information about EAP authentication sessions on access ports. It functions purely as a software/protocol-status and security-event monitoring MIB: it reports when an 802.1X user session starts or ends and why, which user and role were involved, which access port and entity were affected, and whether the port ended up open or closed as a result, which is critical for tracking network access control events on the equipment. As part of Nortel's OPS optical platform MIB family, it likely depends on or complements other Nortel OPS device MIBs for baseline device and port identification. It would typically be deployed in enterprise or carrier networks using Nortel OPS equipment with 802.1X network access control enabled, where security/NAC administrators need visibility into authentication session events. Engineers can download the OPSUBP-DEVICE-SIGNALING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in OPSUBP-DEVICE-SIGNALING-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

Nortel Networks OPS optical networking equipment (802.1X-enabled access ports)

Monitoring Examples

A security administrator would trap on notifications carrying ubpNotifyEAPUserIdentifier and ubpNotifyEAPUserRoles to see which user authenticated on a given ubpNotifyEAPAccessPortEntityIdentifier, using ubpNotifyEAPAccessPortEntityOpenFlag to confirm whether the port was opened or remained blocked. The ubpNotifyEAPSessionEndReason object would explain why a session terminated, for example logoff versus authentication failure, while ubpNotifyEAPSignalSequenceNumber and the session start/end sequence numbers allow correlating the full lifecycle of a single authentication session. Repeated session-end events with a failure reason on the same access port would indicate a misconfigured supplicant or a potential unauthorized access attempt.

What Can Be Monitored

EAP user authentication session start/end
access port open/closed state
authenticated user identifier and roles
session termination reason
session signal sequence tracking

Imported Objects

From NORTEL-MIB

nortel

MODULE-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE
Unsigned32
enterprises

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TimeStamp

OIDs

OID symbolic	OID numeric	Type	Access	Description
nnOPSNetIDGroup	1.3.6.1.4.1.562.42			The root naming arc for Nortel Networks.
nnOPSMIBS	1.3.6.1.4.1.562.42.5			The root naming arc for Nortel Networks.
nnOPSQoSRootOID	1.3.6.1.4.1.562.42.5.1			The root naming arc for the ops ubp device signalling mib.
nnOpsUbpDeviceSignalingMIB	1.3.6.1.4.1.562.42.5.1.3			UBP notifications MIB
nnOpsUbpDeviceSignalingMIBObjects	1.3.6.1.4.1.562.42.5.1.3.1			OPS UBP device signaling MIB objects are all defined in this branch.
ubpNotifyObjects	1.3.6.1.4.1.562.42.5.1.3.1.1			Group of objects related to notification information.
INT ubpNotifyDeviceIdentifierType	1.3.6.1.4.1.562.42.5.1.3.1.1.1	INTEGER	accessible-for-notify	This indicates the type of the device identifier that will be sent in the serverNotifyDeviceIdentifier attribute. This attribute is sent with the notification.
STR ubpNotifyDeviceIdentifier	1.3.6.1.4.1.562.42.5.1.3.1.1.2	DisplayString	accessible-for-notify	A string that can be used to uniquely identify the device which is acting as an EAP access point. This attribute is sent with the notification.
STR ubpNotifyEAPAccessPortEntityIdentifier	1.3.6.1.4.1.562.42.5.1.3.1.1.3	DisplayString	accessible-for-notify	A string that can be used to identify the interface on the EAP access point on which the EAP session was started/ended. The format for this attribute is device specific. For Passport 8600 devices, it will take the form of ?/? e.g. ?3/16?. This attribute is sent with the notification.
STR ubpNotifyEAPUserIdentifier	1.3.6.1.4.1.562.42.5.1.3.1.1.4	DisplayString	accessible-for-notify	The name of the user initiating the EAP session e.g. ?Joe?. This attribute is sent with the notification.
STR ubpNotifyEAPUserGroupIdentifier	1.3.6.1.4.1.562.42.5.1.3.1.1.5	DisplayString	accessible-for-notify	The groups the user initiating the EAP session is associated with. The value for this attribute is made available through vendor specific attributes in the RADIUS authentication message received by the EAP access point. This attribute may contain multiple group names following the format ?+? e.g. ?Engg+Admin?. This attribute is sent with the notification.
STR ubpNotifyEAPUserRoles	1.3.6.1.4.1.562.42.5.1.3.1.1.6	DisplayString	accessible-for-notify	The name of the role combination. A role combination is a set of unordered roles; a role being an abstraction used to bind policies with actual interfaces on devices. Each role takes the form of a string. The value for this attribute is made available through vendor specific attributes in the RADIUS authentication message received by the EAP access point. This attribute may contain multiple roles, in the form ?+? e.g. ?Student+TeachingAssistant?. The invalid characters for a role are : ?+?, ? ? (space), null, lf, cr, bell, bs, HT (tab), VT, FF (form feed). The maximum length for a role is 31 characters. This attribute is sent with the notification.
U32 ubpNotifyEAPSignalSequenceNumber	1.3.6.1.4.1.562.42.5.1.3.1.1.7	Unsigned32	accessible-for-notify	This is a unique sequence identifier for a EAP session start or end event. The EAP user session event signaling is done using SNMPv3 Inform messages. Each time the EAP access point does not get an acknowledgement for the Inform, it may retry sending the Inform message with the same EAP signal sequence number so that the Inform receiver can handle duplicate Informs. This attribute is sent with the notification.
U32 ubpNotifyEAPSessionStartSignalSequenceNumber	1.3.6.1.4.1.562.42.5.1.3.1.1.8	Unsigned32	accessible-for-notify	This is the sequence identifier that was associated with the SNMP Inform message sent for a EAP session started event. It can be used to correlate the EAP session end event with the notification for the EAP session start event. This attribute is sent with the notification.
INT ubpNotifyEAPSessionEndReason	1.3.6.1.4.1.562.42.5.1.3.1.1.9	INTEGER	accessible-for-notify	The reason for the EAP user session end event. This is used for reporting purposes only. This attribute is sent with the notification.
INT ubpNotifyEAPAccessPortEntityOpenFlag	1.3.6.1.4.1.562.42.5.1.3.1.1.10	INTEGER	accessible-for-notify	This is a flag indicating whether the receiver of the notification should perform an ?open? or ?activation? operation on the EAP access port entity after it has downloaded User based policies for the current EAP user session. This may be useful for reporting purposes. This attribute is sent with the notification.
ubpDeviceSignalingMIBNotifications	1.3.6.1.4.1.562.42.5.1.3.2
NTF ubpEAPSessionStart	1.3.6.1.4.1.562.42.5.1.3.2.1			This notification signifies that an EAP session was started on the host from which this notification has been sent.
NTF ubpEAPSessionEnd	1.3.6.1.4.1.562.42.5.1.3.2.2			This notification signifies that an EAP session has ended on the host from which this notification has been sent.
nnOpsUbpDeviceSignalingMIBConformance	1.3.6.1.4.1.562.42.5.1.3.3			Policy Server MIB objects are all defined in this branch.
nnOpsUbpDeviceSignalingMIBCompliances	1.3.6.1.4.1.562.42.5.1.3.3.1
nnOpsUbpDeviceSignalingMIBCompliance	1.3.6.1.4.1.562.42.5.1.3.3.1.1			Describes the requirements for conformance to the OPS Policy Server MIB
nnOpsUbpDeviceSignalingMIBGroups	1.3.6.1.4.1.562.42.5.1.3.3.2
ubpNotifyObjectsGroup	1.3.6.1.4.1.562.42.5.1.3.3.2.1			Policy Server MIB objects used in notifications.
serverNotificationsGroup	1.3.6.1.4.1.562.42.5.1.3.3.2.2			Notifications which are implemented by the agent on the EAP access point.

RFC description

Manages signaling and device communication on optical/metro Ethernet platforms; vendor-specific for signaling protocol control.

Start monitoring Nortel Networks OPS optical networking equipment (802.1X-enabled access ports) 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 OPSUBP-DEVICE-SIGNALING-MIB

What Is OPSUBP-DEVICE-SIGNALING-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description