1OPSUBP-DEVICE-SIGNALING-MIB DEFINITIONS ::= BEGIN 2 3IMPORTS 4 Unsigned32, enterprises, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY 5 FROM SNMPv2-SMI 6 7 TEXTUAL-CONVENTION, DisplayString, TimeStamp 8 FROM SNMPv2-TC 9 10 nortel 11 FROM NORTEL-MIB 12 13 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 14 FROM SNMPv2-CONF; 15 16nnOPSNetIDGroup OBJECT-IDENTITY 17 STATUS current 18 DESCRIPTION 19 "The root naming arc for Nortel Networks." 20 ::= { nortel 42 } 21 22nnOPSMIBS OBJECT-IDENTITY 23 STATUS current 24 DESCRIPTION 25 "The root naming arc for Nortel Networks." 26 ::= { nnOPSNetIDGroup 5 } 27 28nnOPSQoSRootOID OBJECT-IDENTITY 29 STATUS current 30 DESCRIPTION 31 "The root naming arc for the ops ubp device signalling mib." 32 ::= { nnOPSMIBS 1 } 33 34nnOpsUbpDeviceSignalingMIB MODULE-IDENTITY 35 LAST-UPDATED "201304120000Z" 36 ORGANIZATION "Nortel Networks OPS group" 37 CONTACT-INFO 38 "Support ERC# 245 39 40 North America: (800) 4-NORTEL 41 (800) 466-7835 42 EMEA: (33)(4) 92-966-968 43 Asia Pacific: 61-2-9927-8800 44 China: (800) 810-5000 45 " 46 DESCRIPTION 47 "UBP notifications MIB" 48 49 REVISION "201304120000Z" -- 12 Apr 2013 50 DESCRIPTION "Version 02: Corrected module compliance" 51 52 ::= { nnOPSQoSRootOID 3 } 53 54nnOpsUbpDeviceSignalingMIBObjects OBJECT-IDENTITY 55 STATUS current 56 DESCRIPTION 57 "OPS UBP device signaling MIB objects are all defined in this 58branch." 59 ::= { nnOpsUbpDeviceSignalingMIB 1 } 60 61ubpNotifyObjects OBJECT-IDENTITY 62 STATUS current 63 DESCRIPTION 64 "Group of objects related to notification information." 65 ::= { nnOpsUbpDeviceSignalingMIBObjects 1 } 66 67 68-- ubpNotifyObjects: Objects which are used only in notifications 69 70ubpNotifyDeviceIdentifierType OBJECT-TYPE 71 SYNTAX INTEGER{ 72 devicemgmtadd(1), 73 snmpengineid(2) 74 } 75 MAX-ACCESS accessible-for-notify 76 STATUS current 77 DESCRIPTION 78 "This indicates the type of the device identifier that will be sent 79in the serverNotifyDeviceIdentifier attribute. This attribute is sent with 80the notification." 81 ::= { ubpNotifyObjects 1 } 82 83ubpNotifyDeviceIdentifier OBJECT-TYPE 84 SYNTAX DisplayString 85 MAX-ACCESS accessible-for-notify 86 STATUS current 87 DESCRIPTION 88 "A string that can be used to uniquely identify the device which is 89acting as an EAP access point. This attribute is sent with the 90notification." 91 ::= { ubpNotifyObjects 2 } 92 93ubpNotifyEAPAccessPortEntityIdentifier OBJECT-TYPE 94 SYNTAX DisplayString 95 MAX-ACCESS accessible-for-notify 96 STATUS current 97 DESCRIPTION 98 "A string that can be used to identify the interface on the EAP 99access point on which the EAP session was started/ended. The format for 100this attribute is device specific. For Passport 8600 devices, it will take 101the form of ?<slot>/<port>? e.g. ?3/16?. This attribute is sent with the 102notification." 103 ::= { ubpNotifyObjects 3 } 104 105 106ubpNotifyEAPUserIdentifier OBJECT-TYPE 107 SYNTAX DisplayString 108 MAX-ACCESS accessible-for-notify 109 STATUS current 110 DESCRIPTION 111 "The name of the user initiating the EAP session e.g. ?Joe?. This 112attribute is sent with the notification." 113 ::= { ubpNotifyObjects 4 } 114 115ubpNotifyEAPUserGroupIdentifier OBJECT-TYPE 116 SYNTAX DisplayString 117 MAX-ACCESS accessible-for-notify 118 STATUS current 119 DESCRIPTION 120 "The groups the user initiating the EAP session is associated with. 121The value for this attribute is made available through vendor specific 122attributes in the RADIUS authentication message received by the EAP access 123point. This attribute may contain multiple group names following the format 124?<groupname1>+<groupname2>? e.g. ?Engg+Admin?. This attribute is sent with 125the notification." 126 ::= { ubpNotifyObjects 5 } 127 128 129 130ubpNotifyEAPUserRoles OBJECT-TYPE 131 SYNTAX DisplayString 132 MAX-ACCESS accessible-for-notify 133 STATUS current 134 DESCRIPTION 135 "The name of the role combination. A role combination is a set of 136unordered roles; a role being an abstraction used to bind policies with 137actual interfaces on devices. Each role takes the form of a string. The 138value for this attribute is made available through vendor specific 139attributes in the RADIUS authentication message received by the EAP access 140point. This attribute may contain multiple roles, in the form 141?<role1>+<role2>? e.g. ?Student+TeachingAssistant?. The invalid characters 142for a role are : ?+?, ? ? (space), null, lf, cr, bell, bs, HT (tab), VT, FF 143(form feed). The maximum length for a role is 31 characters. This attribute 144is sent with the notification." 145 ::= { ubpNotifyObjects 6 } 146 147 148ubpNotifyEAPSignalSequenceNumber OBJECT-TYPE 149 SYNTAX Unsigned32 150 MAX-ACCESS accessible-for-notify 151 STATUS current 152 DESCRIPTION 153 "This is a unique sequence identifier for a EAP session start or 154end event. The EAP user session event signaling is done using SNMPv3 Inform 155messages. Each time the EAP access point does not get an acknowledgement 156for the Inform, it may retry sending the Inform message with the same EAP 157signal sequence number so that the Inform receiver can handle duplicate 158Informs. This attribute is sent with the notification." 159 ::= { ubpNotifyObjects 7 } 160 161ubpNotifyEAPSessionStartSignalSequenceNumber OBJECT-TYPE 162 SYNTAX Unsigned32 163 MAX-ACCESS accessible-for-notify 164 STATUS current 165 DESCRIPTION 166 "This is the sequence identifier that was associated with the SNMP 167Inform message sent for a EAP session started event. It can be used to 168correlate the EAP session end event with the notification for the EAP 169session start event. This attribute is sent with the notification." 170 ::= { ubpNotifyObjects 8 } 171 172 173ubpNotifyEAPSessionEndReason OBJECT-TYPE 174 SYNTAX INTEGER{ 175 eapsessionEndUserlogoff(1), 176 eapsessionEndOther(2) 177 } 178 MAX-ACCESS accessible-for-notify 179 STATUS current 180 DESCRIPTION 181 "The reason for the EAP user session end event. This is used for 182reporting purposes only. This attribute is sent with the notification." 183 ::= { ubpNotifyObjects 9 } 184 185ubpNotifyEAPAccessPortEntityOpenFlag OBJECT-TYPE 186 SYNTAX INTEGER{ 187 eapAccessPortFlagNotApplicable(1), 188 eapAccessPortOpenRequired(2), 189 eapAccessPortOpenNotRequired(3) 190 } 191 MAX-ACCESS accessible-for-notify 192 STATUS current 193 DESCRIPTION 194 "This is a flag indicating whether the receiver of the notification 195should perform an ?open? or ?activation? operation on the EAP access port 196entity after it has downloaded User based policies for the current EAP user 197session. This may be useful for reporting purposes. This attribute is sent 198with the notification." 199 ::= { ubpNotifyObjects 10 } 200 201-- Notifications 202 203ubpDeviceSignalingMIBNotifications OBJECT IDENTIFIER 204 ::= { nnOpsUbpDeviceSignalingMIB 2 } 205 206ubpEAPSessionStart NOTIFICATION-TYPE 207 OBJECTS { ubpNotifyDeviceIdentifierType, 208 ubpNotifyDeviceIdentifier, 209 ubpNotifyEAPAccessPortEntityIdentifier, 210 ubpNotifyEAPUserIdentifier, 211 ubpNotifyEAPUserGroupIdentifier, 212 ubpNotifyEAPUserRoles, 213 ubpNotifyEAPSignalSequenceNumber, 214 ubpNotifyEAPAccessPortEntityOpenFlag 215 } 216 STATUS current 217 DESCRIPTION 218 "This notification signifies that an EAP session was started on the 219host from which this notification has been sent." 220 ::= { ubpDeviceSignalingMIBNotifications 1 } 221 222ubpEAPSessionEnd NOTIFICATION-TYPE 223 OBJECTS { ubpNotifyDeviceIdentifierType, 224 ubpNotifyDeviceIdentifier, 225 ubpNotifyEAPAccessPortEntityIdentifier, 226 ubpNotifyEAPUserIdentifier, 227 ubpNotifyEAPSessionEndReason, 228 ubpNotifyEAPSignalSequenceNumber, 229 ubpNotifyEAPSessionStartSignalSequenceNumber 230 } 231 STATUS current 232 DESCRIPTION 233 "This notification signifies that an EAP session has ended on the 234host from which this notification has been sent." 235 ::= { ubpDeviceSignalingMIBNotifications 2 } 236 237 238 239-- Conformance 240 241nnOpsUbpDeviceSignalingMIBConformance OBJECT-IDENTITY 242 STATUS current 243 DESCRIPTION 244 "Policy Server MIB objects are all defined in this branch." 245 ::= { nnOpsUbpDeviceSignalingMIB 3 } 246 247nnOpsUbpDeviceSignalingMIBCompliances OBJECT IDENTIFIER 248 ::= { nnOpsUbpDeviceSignalingMIBConformance 1 } 249 250nnOpsUbpDeviceSignalingMIBGroups OBJECT IDENTIFIER 251 ::= { nnOpsUbpDeviceSignalingMIBConformance 2 } 252 253-- Compliance groups 254 255nnOpsUbpDeviceSignalingMIBCompliance MODULE-COMPLIANCE 256 STATUS current 257 DESCRIPTION 258 "Describes the requirements for conformance to the OPS Policy 259 Server MIB" 260 MODULE -- this module 261 MANDATORY-GROUPS { 262 ubpNotifyObjectsGroup, 263 serverNotificationsGroup 264 } 265 ::= { nnOpsUbpDeviceSignalingMIBCompliances 1 } 266 267 268ubpNotifyObjectsGroup OBJECT-GROUP 269 OBJECTS { 270 ubpNotifyDeviceIdentifierType, 271 ubpNotifyDeviceIdentifier, 272 ubpNotifyEAPAccessPortEntityIdentifier, 273 ubpNotifyEAPUserIdentifier, 274 ubpNotifyEAPUserGroupIdentifier, 275 ubpNotifyEAPUserRoles, 276 ubpNotifyEAPSignalSequenceNumber, 277 ubpNotifyEAPSessionStartSignalSequenceNumber, 278 ubpNotifyEAPSessionEndReason, 279 ubpNotifyEAPAccessPortEntityOpenFlag 280 } 281 STATUS current 282 DESCRIPTION 283 "Policy Server MIB objects used in notifications." 284 ::= { nnOpsUbpDeviceSignalingMIBGroups 1 } 285 286serverNotificationsGroup NOTIFICATION-GROUP 287 NOTIFICATIONS { 288 ubpEAPSessionStart, 289 ubpEAPSessionEnd 290 } 291 STATUS current 292 DESCRIPTION 293 "Notifications which are implemented by the agent on the EAP access 294point." 295 ::= { nnOpsUbpDeviceSignalingMIBGroups 2 } 296 297END 298