OPSUBP-DEVICE-SIGNALING-MIB: View SNMP OID List / Download MIB

VENDOR: NORTHERN TELECOM


 Home MIB: OPSUBP-DEVICE-SIGNALING-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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.
                           ubpNotifyDeviceIdentifierType 1.3.6.1.4.1.562.42.5.1.3.1.1.1 integer no-access
This indicates the type of the device identifier that will be sent in the serverNotifyDeviceIdentifier attribute. This attribute is sent with the notification. Enumeration: 'snmpengineid': 2, 'devicemgmtadd': 1.
                           ubpNotifyDeviceIdentifier 1.3.6.1.4.1.562.42.5.1.3.1.1.2 displaystring no-access
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.
                           ubpNotifyEAPAccessPortEntityIdentifier 1.3.6.1.4.1.562.42.5.1.3.1.1.3 displaystring no-access
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.
                           ubpNotifyEAPUserIdentifier 1.3.6.1.4.1.562.42.5.1.3.1.1.4 displaystring no-access
The name of the user initiating the EAP session e.g. ?Joe?. This attribute is sent with the notification.
                           ubpNotifyEAPUserGroupIdentifier 1.3.6.1.4.1.562.42.5.1.3.1.1.5 displaystring no-access
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.
                           ubpNotifyEAPUserRoles 1.3.6.1.4.1.562.42.5.1.3.1.1.6 displaystring no-access
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.
                           ubpNotifyEAPSignalSequenceNumber 1.3.6.1.4.1.562.42.5.1.3.1.1.7 unsigned32 no-access
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.
                           ubpNotifyEAPSessionStartSignalSequenceNumber 1.3.6.1.4.1.562.42.5.1.3.1.1.8 unsigned32 no-access
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.
                           ubpNotifyEAPSessionEndReason 1.3.6.1.4.1.562.42.5.1.3.1.1.9 integer no-access
The reason for the EAP user session end event. This is used for reporting purposes only. This attribute is sent with the notification. Enumeration: 'eapsessionEndOther': 2, 'eapsessionEndUserlogoff': 1.
                           ubpNotifyEAPAccessPortEntityOpenFlag 1.3.6.1.4.1.562.42.5.1.3.1.1.10 integer no-access
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. Enumeration: 'eapAccessPortFlagNotApplicable': 1, 'eapAccessPortOpenNotRequired': 3, 'eapAccessPortOpenRequired': 2.
                   ubpDeviceSignalingMIBNotifications 1.3.6.1.4.1.562.42.5.1.3.2
                       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.
                       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.