EZ5 MIB Catalog

CISCO-WIRELESS-NOTIFICATION-MIB

2011-06-06

This MIB is intended to be implemented on those Network Management applications that manage a network of wireless devices through the Controller and send relevant management information to Northbound Operation Support Systems. The Northbound OSS, with the information received shall present a consolidated view of the whole network of wireless devices. The NM learns the status of the managed devices from the Controller through interfaces like the SNMP, and raises events. Depending upon the event severity, alerts are raised for the events. The alert/event information is sent to the Northbound OSS in the form of SNMP Notifications. This MIB defines these Notifications. The MIB objects cWNotificationDescription, cWNotificationSpecialAttributes and cWNotificationVirtualDomains have been defined to have a maximum size of 1024. The bigger size is required for the following reasons. 1. If the size is reduced, the information intended to be sent to the Northbound applications will be truncated / lost. 2. Networks using UDP are better in handling fragmentation than before. 3. In case if the implementation is used in those networks that can't handle Notifications of a larger size, the intent is to suggest the use of the TCP as the transport protocol for SNMP as against the UDP. 4. The respective objects may not have the maximum defined range at all the times. The higher range is just to accommodate those cases where the size can hit the maximum value. The relationships between NCS, CC, AP, MN and Mgmt-Appl can be depicted as follows : +................+ +................+ + + + + + NB OSS 1 + .. + NB OSS n + + + + + +................+ +................+ ^ ^ . . . . Notifications . . . +..........+ + + + NCS + + + +..........+ ^ ^ ^ . . . SNMP . . . . . . . . . +......+ +......+ +......+ + + + + + + + CC + + CC + + CC + + + + + + + +......+ +......+ +......+ .. . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + AP + + AP + + AP + + AP + + + + + + + + + +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + MN + + MN + + MN + + MN + + + + + + + + + +......+ +......+ +......+ +......+ GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control (MAC) and physical layer (PHY) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends it to the Controller to which it is logically connected to. Alert An alert is an NM response to one or more related Events from Managed Object. If the Event learnt is severe enough to let the user know about, the NM raises an alert i.e if event has one of the following severity critical, major, minor or warning. One or more Events can result in a single alert being raised. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity is also referred to as 'Controller'. Event An Event is an occurrence or detection of some condition in and around the network. Event can be generated by the NM corresponding to traps received or through polling the managed object. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Controllers. Managed Object Managed Objects are used to represent those entities being managed by the NM. It could be an AP, WLAN, Controller or an MN. Mobile Node ( MN ) Mobile Nodes are roaming 802.11 wireless devices that would associate to an AP to get their uplink to the wired network. Mobile Nodes are also known as clients. Network Management Application ( NM ) Application which manages network of managed objects using SNMP. It provides network management functions of FCAPS - Fault, Configuration, Accounting, Performance and Security to manage the network. Notification NM application like NCS sends Notifications defined through this MIB, corresponding to their Alerts and Events to a Northbound OSS to provide a consolidated view. Operations Support Systems ( OSS ) Management applications in the network that receive Notifications from NM (like NCS) and provide consolidated view of the whole network of wireless devices. Received Signal Strength Indicator ( RSSI ) A measure of the strength of the signal as observed by the entity that received it, expressed in 'dbm'. Signal-Noise Ratio ( SNR ) A measure of the quality of the signal relative to the strength of noise expressed in 'dB'. Virtual Domain A NM's Virtual Domain is a logical grouping that consists of a set of managed objects like Controllers, APs, WLANs, maps etc. It restricts a user's view to information relevant to these managed objects. Through a virtual domain, an administrator can ensure that users are only able to view the managed objects and maps for which they are responsible. A managed object can belong to more than one virtual domain. Network Control System ( NCS ) Network Control System (NCS) is a converged platform for wired, wireless, and security policy management in a single solution for faster troubleshooting and more efficient network operations. Wireless LAN ( WLAN ) A WLAN refers to the network of IEEE 802.11 complaint wireless devices within mutual communication range of each other via the wireless medium. REFERENCE [1] Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. [2] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 2.4 GHz RF and IR standard.

Download CISCO-WIRELESS-NOTIFICATION-MIB.txt Open CISCO-WIRELESS-NOTIFICATION-MIB.txt in a new tab

SCALARS (2) · TABLES (1) · TRAPS (1)

Scalars (2)

NameOID
cwNotificationHistoryTableMaxLength1.3.6.1.4.1.9.9.712.1.1.1
cwNotificationMOStatusEnable1.3.6.1.4.1.9.9.712.1.1.3

Tables (1)

NameOID
cwNotificationHistoryTable1.3.6.1.4.1.9.9.712.1.1.2

Traps (1)

NameOID
ciscoWirelessMOStatusNotification1.3.6.1.4.1.9.9.712.0.1

END OF TOC

Scalar details

cwNotificationHistoryTableMaxLength

1.3.6.1.4.1.9.9.712.1.1.1

Unsigned32 (1..4294967295)

This object represents the maximum number of entries permissible in cwNotificationHistoryTable. When user sets this to a lower value, for example from 100 to 50, entries corresponding to older Notifications will be deleted to adjust to the new setting.

cwNotificationMOStatusEnable

1.3.6.1.4.1.9.9.712.1.1.3

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is to control the generation of ciscoWirelessMOStatusNotification. A value of 'true' indicates that the NM generates ciscoWirelessMOStatusNotification Notification. A value of 'false' indicates that the NM does not generate ciscoWirelessMOStatusNotification Notification.

Table details

cwNotificationHistoryTable

1.3.6.1.4.1.9.9.712.1.1.2

Index: cWNotificationIndex

This table represents the information about the Notifications sent by the NM to Northbound applications. The Notification fields are populated from the corresponding Alert/Event.Whenever the NM sends a Notification to one of the Northbound applications, a row will be added to this table. When the number of maximum allowed of entries is decreased through cwNotificationHistoryTableMaxLength, the least recent entries will be deleted.

cWNotificationIndex

1.3.6.1.4.1.9.9.712.1.1.2.1.1

Unsigned32 (1..4294967295)

This object represents a monotonically increasing integer that uniquely identifies the information about the Notification. When the maximum value defined by cwNotificationHistoryTableMaxLength is reached, the value wraps back to 1.

cWNotificationTimestamp

1.3.6.1.4.1.9.9.712.1.1.2.1.2

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object in the Notification represents the time when the corresponding Alert/Event was raised by the NM for a particular condition in the network.

cWNotificationUpdatedTimestamp

1.3.6.1.4.1.9.9.712.1.1.2.1.3

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object in the Notification represents the time when Alert was last updated. Alerts persist over time and it is possible that their field(s) get changed. For example, when severity changes from a higher level (ex critical to major or major to minor or minor to clear), then the severity field gets updated. This object represents the time when it happened. This object will not be populated for Events.

cWNotificationKey

1.3.6.1.4.1.9.9.712.1.1.2.1.4

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..255) · OCTET STRING · hint 255t

This object represents the entity string that describes the network condition identified by cwNotificationType for which this Notification is generated.

cWNotificationCategory

1.3.6.1.4.1.9.9.712.1.1.2.1.5

CWirelessNotificationCategory1 = unknown2 = accessPoints3 = adhocRogue4 = clients5 = controllers6 = coverageHole7 = interference8 = contextAwareNotifications9 = meshLinks10 = mobilityService11 = performance12 = rogueAP13 = rrm14 = security15 = wcs16 = switch17 = ncsThis textual convention defines the different Notification categories. The semantics are as follows. 'unknown' This indicates an unknown category. 'accessPoints' The Notification is associated with APs. 'adhocRogue' The Notification is associated with adhoc rogue APs. 'clients' The Notification is associated with client/mobile nodes. 'controllers' The Notification is associated with Controllers. 'coverageHole' The Notification is associated with holes in radio coverage. 'contextAwareNotifications' The Notification is associated with Alerts generated by location service for Event definitions configured on the MSE like containment,chokepoint etc. 'interference' The Notification is associated with interference in radio coverage by APs. 'meshLinks' The Notification is associated with mesh wireless networks. 'mobilityService' The Notification is associated with MSE status. 'performance' The Notification is associated with wireless network performance. 'rogueAP' The Notification is associated with rogue APs detected in the network. 'rrm' The Notification is associated to radio resource management. 'security' The Notification is associated with security of wireless networks. 'wcs' The Notification is associated with WCS. 'switch' The Notification is associated with Ethernet switch. 'ncs' The Notification is associated with NCS. · Integer32

This object represents the category of the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationSubCategory

1.3.6.1.4.1.9.9.712.1.1.2.1.6

OCTET STRING SIZE (1..256)

This object represents the sub category of the network condition identified by cwNotificationType for which this Notification is generated. This object can be used to further filter down Alert/Event under a particular category.

cWNotificationManagedObjectAddressType

1.3.6.1.4.1.9.9.712.1.1.2.1.7

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object represents the type of the Internet network address made available through cWNotificationManagedObjectAddress.

cWNotificationManagedObjectAddress

1.3.6.1.4.1.9.9.712.1.1.2.1.8

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object represents the network address of the Managed Object. The type of the address stored in this object is determined by the cWNotificationManagedObjectAddressType object.

cWNotificationSourceDisplayName

1.3.6.1.4.1.9.9.712.1.1.2.1.9

OCTET STRING SIZE (1..256)

This object represents the display name for the source that triggered the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationDescription

1.3.6.1.4.1.9.9.712.1.1.2.1.10

OCTET STRING SIZE (1..1024)

This object represents a detailed description of the network condition represented by cwNotificationType for which this Notification is generated. For example, rogueAp Alert is described as follows, 'Rogue AP '00:1b:2b:35:6a:f3' is removed; it was detected as Rogue AP by AP 'test_1' Radio Type '802.11b''.

cWNotificationSeverity

1.3.6.1.4.1.9.9.712.1.1.2.1.11

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object represents the severity of the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationSpecialAttributes

1.3.6.1.4.1.9.9.712.1.1.2.1.12

OCTET STRING SIZE (1..1024)

This object represents the specialized attributes required to describe the network condition identified by cWNotificationType. These include SNR, RSSI, channel information etc. This value is formatted as 'name=value' pairs in CSV format. For example, rogueAP Alert's special attributes are sent as 'detectingAPRadioType=a0,YCoordinate=0, state=11, rogueApType=0, spt Status=0, ssId=wpspsk, on80211A=0, numOfDetectingAps=0, on80211B=1, XCoordinate=0, classificationType=3, channelNumber=6, containmentLevel=0, rssi=-51, rogueApMacAddr=00:1b:2b:35:6a:f3, onNetwork=0, total RogueClients=0'. This string can be parsed to get different name-value pairs.

cWNotificationType

1.3.6.1.4.1.9.9.712.1.1.2.1.13

CWirelessNotificationType1 = unknown2 = alert3 = eventThis textual convention defines the different Notification types. Unknown : This indicates an unknown Notification type. Alert : This indicates that the Notification is generated due to an Alert generated by a set of Events. Event : This indicates that the Notification is generated due to an Event related to a Managed Object. The Event can be raised through polling the Managed Object, receiving SNMP Notifications from the Managed Object etc. · Integer32

This object represents the type of this Notification. This basically indicates the trigger that has caused the NM to generate this Notification.

cWNotificationVirtualDomains

1.3.6.1.4.1.9.9.712.1.1.2.1.14

OCTET STRING SIZE (1..1024)

This object represents the name of one or multiple virtual domains(comma separated) the source of the network condition represented by cWNotificationType is logically assigned to. For example, 'root, California, San Jose' indicates that the source of the network condition is logically assigned to these multiple virtual domains.

Trap details

ciscoWirelessMOStatusNotification

1.3.6.1.4.1.9.9.712.0.1

This Notification is generated by the NM in response to an Alert or Event related to a network device managed by it.

cWNotificationTimestamp

1.3.6.1.4.1.9.9.712.1.1.2.1.2

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object in the Notification represents the time when the corresponding Alert/Event was raised by the NM for a particular condition in the network.

cWNotificationUpdatedTimestamp

1.3.6.1.4.1.9.9.712.1.1.2.1.3

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object in the Notification represents the time when Alert was last updated. Alerts persist over time and it is possible that their field(s) get changed. For example, when severity changes from a higher level (ex critical to major or major to minor or minor to clear), then the severity field gets updated. This object represents the time when it happened. This object will not be populated for Events.

cWNotificationKey

1.3.6.1.4.1.9.9.712.1.1.2.1.4

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..255) · OCTET STRING · hint 255t

This object represents the entity string that describes the network condition identified by cwNotificationType for which this Notification is generated.

cWNotificationCategory

1.3.6.1.4.1.9.9.712.1.1.2.1.5

CWirelessNotificationCategory1 = unknown2 = accessPoints3 = adhocRogue4 = clients5 = controllers6 = coverageHole7 = interference8 = contextAwareNotifications9 = meshLinks10 = mobilityService11 = performance12 = rogueAP13 = rrm14 = security15 = wcs16 = switch17 = ncsThis textual convention defines the different Notification categories. The semantics are as follows. 'unknown' This indicates an unknown category. 'accessPoints' The Notification is associated with APs. 'adhocRogue' The Notification is associated with adhoc rogue APs. 'clients' The Notification is associated with client/mobile nodes. 'controllers' The Notification is associated with Controllers. 'coverageHole' The Notification is associated with holes in radio coverage. 'contextAwareNotifications' The Notification is associated with Alerts generated by location service for Event definitions configured on the MSE like containment,chokepoint etc. 'interference' The Notification is associated with interference in radio coverage by APs. 'meshLinks' The Notification is associated with mesh wireless networks. 'mobilityService' The Notification is associated with MSE status. 'performance' The Notification is associated with wireless network performance. 'rogueAP' The Notification is associated with rogue APs detected in the network. 'rrm' The Notification is associated to radio resource management. 'security' The Notification is associated with security of wireless networks. 'wcs' The Notification is associated with WCS. 'switch' The Notification is associated with Ethernet switch. 'ncs' The Notification is associated with NCS. · Integer32

This object represents the category of the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationSubCategory

1.3.6.1.4.1.9.9.712.1.1.2.1.6

OCTET STRING SIZE (1..256)

This object represents the sub category of the network condition identified by cwNotificationType for which this Notification is generated. This object can be used to further filter down Alert/Event under a particular category.

cWNotificationManagedObjectAddressType

1.3.6.1.4.1.9.9.712.1.1.2.1.7

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object represents the type of the Internet network address made available through cWNotificationManagedObjectAddress.

cWNotificationManagedObjectAddress

1.3.6.1.4.1.9.9.712.1.1.2.1.8

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object represents the network address of the Managed Object. The type of the address stored in this object is determined by the cWNotificationManagedObjectAddressType object.

cWNotificationSourceDisplayName

1.3.6.1.4.1.9.9.712.1.1.2.1.9

OCTET STRING SIZE (1..256)

This object represents the display name for the source that triggered the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationDescription

1.3.6.1.4.1.9.9.712.1.1.2.1.10

OCTET STRING SIZE (1..1024)

This object represents a detailed description of the network condition represented by cwNotificationType for which this Notification is generated. For example, rogueAp Alert is described as follows, 'Rogue AP '00:1b:2b:35:6a:f3' is removed; it was detected as Rogue AP by AP 'test_1' Radio Type '802.11b''.

cWNotificationSeverity

1.3.6.1.4.1.9.9.712.1.1.2.1.11

CiscoAlarmSeverity1 = cleared2 = indeterminate3 = critical4 = major5 = minor6 = warning7 = infoRepresents the perceived alarm severity associated with a service or safety affecting condition and/or event. These are based on ITU severities, except that info(7) is added. cleared(1) - Indicates a previous alarm condition has been cleared. It is not required (unless specifically stated elsewhere on a case by case basis) that an alarm condition that has been cleared will produce a notification or other event containing an alarm severity with this value. indeterminate(2) - Indicates that the severity level cannot be determined. critical(3) - Indicates that a service or safety affecting condition has occurred and an immediate corrective action is required. major(4) - Indicates that a service affecting condition has occurred and an urgent corrective action is required. minor(5) - Indicates the existence of a non-service affecting condition and that corrective action should be taken in order to prevent a more serious (for example, service or safety affecting) condition. warning(6) - Indicates the detection of a potential or impending service or safety affecting condition, before any significant effects have been felt. info(7) - Indicates an alarm condition that does not meet any other severity definition. This can include important, but non-urgent, notices or informational events.Reference: ITU-X.733 · Integer32

This object represents the severity of the network condition represented by cwNotificationType for which this Notification is generated.

cWNotificationSpecialAttributes

1.3.6.1.4.1.9.9.712.1.1.2.1.12

OCTET STRING SIZE (1..1024)

This object represents the specialized attributes required to describe the network condition identified by cWNotificationType. These include SNR, RSSI, channel information etc. This value is formatted as 'name=value' pairs in CSV format. For example, rogueAP Alert's special attributes are sent as 'detectingAPRadioType=a0,YCoordinate=0, state=11, rogueApType=0, spt Status=0, ssId=wpspsk, on80211A=0, numOfDetectingAps=0, on80211B=1, XCoordinate=0, classificationType=3, channelNumber=6, containmentLevel=0, rssi=-51, rogueApMacAddr=00:1b:2b:35:6a:f3, onNetwork=0, total RogueClients=0'. This string can be parsed to get different name-value pairs.

cWNotificationVirtualDomains

1.3.6.1.4.1.9.9.712.1.1.2.1.14

OCTET STRING SIZE (1..1024)

This object represents the name of one or multiple virtual domains(comma separated) the source of the network condition represented by cWNotificationType is logically assigned to. For example, 'root, California, San Jose' indicates that the source of the network condition is logically assigned to these multiple virtual domains.

↑ To TOC