CISCO-WIRELESS-NOTIFICATION-MIB
The CISCO-WIRELESS-NOTIFICATION-MIB defines SNMP trap structures for Cisco Wireless LAN Controllers (WLC) and the Network Control System (NCS) to transmit event severity alerts and status changes regarding Access Points (APs), Mobile Nodes (MNs), and Virtual Domains to Northbound Operations Support Systems. This module facilitates the aggregation of critical wireless network faults and configuration events, utilizing extended string buffers to ensure complete transmission of diagnostic details across UDP or TCP transport layers.
Imported Objects
Objects
26 total| Object Name |
|---|
ciscoWirelessNotificationMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.712 |
ciscoWirelessNotificationMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.0 |
ciscoWirelessMOStatusNotificationThis Notification is generated by the NM in response to an
Alert or Event related to a network device managed by it. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.712.0.1 |
ciscoWirelessNotificationMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.1 |
cWNotificationData OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.1.1 |
cwNotificationHistoryTableMaxLengthThis 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.rw Unsigned32 .1.3.6.1.4.1.9.9.712.1.1.1 |
cwNotificationHistoryTableThis 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. SEQUENCE OF CwNotificationHistoryEntry .1.3.6.1.4.1.9.9.712.1.1.2 |
cwNotificationHistoryEntryEach entry represents a conceptual row in
cwNotificationHistoryTable and corresponds to the information
about a Notification sent by the NM to Northbound applications. CwNotificationHistoryEntry .1.3.6.1.4.1.9.9.712.1.1.2.1 |
cWNotificationIndexThis 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. Unsigned32 .1.3.6.1.4.1.9.9.712.1.1.2.1.1 |
cWNotificationTimestampThis object in the Notification represents the time when the
corresponding Alert/Event was raised by the NM for a particular
condition in the network.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.712.1.1.2.1.2 |
cWNotificationUpdatedTimestampThis 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.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.712.1.1.2.1.3 |
cWNotificationKeyThis object represents the entity string that describes the
network condition identified by cwNotificationType for which
this Notification is generated.ro SnmpAdminString .1.3.6.1.4.1.9.9.712.1.1.2.1.4 |
cWNotificationCategoryThis object represents the category of the network condition
represented by cwNotificationType for which this Notification
is generated.ro CWirelessNotificationCategory .1.3.6.1.4.1.9.9.712.1.1.2.1.5 |
cWNotificationSubCategoryThis 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.ro OCTET STRING .1.3.6.1.4.1.9.9.712.1.1.2.1.6 |
cWNotificationManagedObjectAddressTypeThis object represents the type of the Internet
network address made available through
cWNotificationManagedObjectAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.712.1.1.2.1.7 |
cWNotificationManagedObjectAddressThis object represents the network address of the Managed
Object. The type of the address stored in this object is
determined by the
cWNotificationManagedObjectAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.712.1.1.2.1.8 |
cWNotificationSourceDisplayNameThis object represents the display name for the source that
triggered the network condition represented by
cwNotificationType for which this Notification is generated.ro OCTET STRING .1.3.6.1.4.1.9.9.712.1.1.2.1.9 |
cWNotificationDescriptionThis 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''.ro OCTET STRING .1.3.6.1.4.1.9.9.712.1.1.2.1.10 |
cWNotificationSeverityThis object represents the severity of the network condition
represented by cwNotificationType for which this Notification is
generated.ro CiscoAlarmSeverity (CISCO-TC) .1.3.6.1.4.1.9.9.712.1.1.2.1.11 |
cWNotificationSpecialAttributesThis 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.ro OCTET STRING .1.3.6.1.4.1.9.9.712.1.1.2.1.12 |
cWNotificationTypeThis object represents the type of this Notification. This
basically indicates the trigger that has caused the NM to
generate this Notification.ro CWirelessNotificationType .1.3.6.1.4.1.9.9.712.1.1.2.1.13 |
cWNotificationVirtualDomainsThis 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.ro OCTET STRING .1.3.6.1.4.1.9.9.712.1.1.2.1.14 |
cwNotificationMOStatusEnableThis 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.712.1.1.3 |
ciscoWirelessNotificationMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.2 |
ciscoWirelessNotificationMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.2.1 |
ciscoWirelessNotificationMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.712.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.