Table Of Contents
Monitoring WAAS Using SNMP
Information About Supported MIBs
Downloading Supported MIBs
Working with SNMP Traps
Enabling SNMP Traps
Viewing SNMP Trigger Lists
Defining New Traps
Information About Common SNMP MIB OIDS
cceAlarmCriticalRaised OID
coldStart OID
cceAlarmCriticalCleared OID
cceFailedDiskName OID
ciscoContentEngineDiskFailed OID
Monitoring WAAS Using SNMP
This chapter describes how to use the Simple Network Management Protocol (SNMP) to monitor your WAAS devices. SNMP is an interoperable standards-based protocol that allows for external monitoring of WAAS devices through an SNMP agent.
For more information about using and configuring SNMP, see the "Configuring SNMP Monitoring" chapter in the Cisco Wide Area Application Services Configuration Guide.
This chapter contains the following sections:
•
Information About Supported MIBs
•Downloading Supported MIBs
•Working with SNMP Traps
•Information About Common SNMP MIB OIDS
Information About Supported MIBs
This section describes the Cisco-specific MIBs that are supported by WAAS as shown in Table 3-1.
Table 3-1 MIBs Supported by WAAS
MIB
|
Description
|
CISCO-APPNAV-MIB
|
Provides information about AppNav objects, including WAAS nodes, WAAS node groups, AppNav controllers, and AppNav controller groups.
|
CISCO-CONTENT-ENGINE-MIB
|
The MIB module for the Cisco WAAS device from Cisco Systems. The following objects from this MIB are supported:
•cceAlarmCriticalCount
•cceAlarmMajorCount
•cceAlarmMinorCount
•cceAlarmHistTableSize
|
CISCO-ENTITY-ASSET-MIB
|
Monitors the asset information of items in the ENTITY-MIB (RFC 2037) entPhysicalTable. This MIB lists the orderable part number, serial number, hardware revision, manufacturing assembly number and revision, firmware ID and revision (if any) and software ID and revision (if any) of relevant entities listed in ENTITY-MIB entPhysicalTable.
|
CISCO-SMI
|
The MIB module for Cisco Enterprise Structure of Management Information. There is nothing to query in this MIB; it describes the structure of Cisco MIBs.
|
CISCO-WAN-OPTIMIZATION-MIB
|
Provides the following information:
•application optimizer status and statistics
•TFO statistics
•application, policy map, and class map statistics
|
ENTITY-MIB
|
Represents multiple logical entities supported by a single SNMP agent.
The entConfigChange notification is supported. This MIB is documented in RFC 2737.
|
EVENT-MIB
|
Defines event triggers and actions for network management purposes. The MIB is published as RFC 2981.
|
HOST-RESOURCES-MIB
|
Manages host systems. The term "host" implies any computer that communicates with other similar computers connected to the Internet. The HOST-RESOURCES-MIB does not necessarily apply to devices whose primary function is communications services (terminal servers, routers, bridges, monitoring equipment). This MIB provides attributes that are common to all Internet hosts, for example, personal computers and systems that run variants of UNIX.
|
IF-MIB
|
Supports querying for interface-related statistics including 64-bit interface counters. These counters include received and sent octets, unicast, multicast, and broadcast packets on the device interfaces. All the objects from ifXEntry are supported except for ifCounterDiscontinuityTime. This MIB is documented in RFC 2233.
|
MIB-II
|
The Internet Standard MIB that is documented in RFC 1213 and for use with network management protocols in TCP/IP-based Internets. This MIB is found in the RFC1213-MIB file in the v1 directory on the download site (other MIBs are in the v2 directory).
|
SNMP-COMMUNITY-MIB
|
Documented in RFC 2576.
|
SNMP-FRAMEWORK-MIB
|
Documented in RFC 2571.
|
SNMP-NOTIFICATION-MIB
|
Documented in RFC 3413.
|
SNMP-TARGET-MIB
|
Documented in RFC 3413.
|
SNMP-USM-MIB
|
Documented in RFC 2574.
|
SNMPv2-MIB
|
Documented in RFC 1907. This MIB supports the following notifications:
•coldStart
•linkUp
•linkDown
•authenticationFailure
|
SNMP-VACM-MIB
|
Documented in RFC 2575.
|
Downloading Supported MIBs
All supported MIB files can be downloaded from the following Cisco FTP locations:
•ftp://ftp.cisco.com/pub/mibs/v2
•ftp://ftp.cisco.com/pub/mibs/v1
The MIB objects that are defined in each MIB are described in the MIB files and are self-explanatory.
Working with SNMP Traps
This section contains the following topics:
•Enabling SNMP Traps
•Viewing SNMP Trigger Lists
•Defining New Traps
Enabling SNMP Traps
To send SNMP traps, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Monitoring > SNMP > General Settings. The SNMP General Settings window appears. See Figure 3-1. The settings window display which traps are enabled for the device or group.
Step 3 Configure the trap settings as desired. For more information, see the "Configuring SNMP Monitoring" chapter in the Cisco Wide Area Application Services Configuration Guide.
Figure 3-1 SNMP General Settings Window
Viewing SNMP Trigger Lists
To view the list of SNMP trap triggers defined for a device or group, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Monitoring > SNMP > Trigger. The SNMP Trigger List window appears. See Figure 3-2.
Figure 3-2 SNMP Trigger List Window
For more information about SNMP Triggers, see the "Configuring SNMP Monitoring" chapter in the Cisco Wide Area Application Services Configuration Guide.
Defining New Traps
To add a new SNMP trap on a WAAS device or device group, follow these steps:
Step 1 From the WAAS Central Manager menu, choose Devices > device-name (or Device Groups > device-group-name).
Step 2 Choose Configure > Monitoring > SNMP > Trigger. The SNMP Trigger List window appears. See Figure 3-2.
Step 3 In the Trigger list window, click Create. The SNMP Trigger window appears. See Figure 3-3.
Figure 3-3 SNMP Trigger Window
Step 4 Define the trigger settings.
Step 5 Click Submit.
Information About Common SNMP MIB OIDS
This section describes some of the common SNMP trap Object Identifiers (OIDs) that you might see:
•cceAlarmCriticalRaised OID
•coldStart OID
•cceAlarmCriticalCleared OID
•cceFailedDiskName OID
•ciscoContentEngineDiskFailed OID
cceAlarmCriticalRaised OID
The cceAlarmCriticalRaisedOID trap signifies that a module raised a Critical alarm.
Object
|
cceAlarmCriticalRaised
|
OID
|
1.3.6.1.4.1.9.9.178.2.0.7
|
Status
|
current
|
MIB
|
CISCO-CONTENT-ENGINE-MIB; View Supporting Images
|
Trap Components
|
cceAlarmHistId
cceAlarmHistModuleId
cceAlarmHistCategory
cceAlarmHistInfo
cceAlarmHistTimeStamp
|
coldStart OID
The coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
Object
|
coldStart
|
OID
|
1.3.6.1.6.3.1.1.5.1
|
Status
|
current
|
MIB
|
SNMPv2-MIB; View Supporting Images
|
cceAlarmCriticalCleared OID
The cceAlarmCriticalRaisedOID trap signifies that a module cleared a Critical alarm.
Object
|
cceAlarmCriticalCleared
|
OID
|
1.3.6.1.4.1.9.9.178.2.0.8
|
Status
|
current
|
MIB
|
CISCO-CONTENT-ENGINE-MIB; View Supporting Images
|
Trap Components
|
cceAlarmHistId
cceAlarmHistModuleId
cceAlarmHistCategory
cceAlarmHistInfo
cceAlarmHistTimeStamp
|
cceFailedDiskName OID
The cceFailedDiskNameOID trap signifies that a disk failure event occurred and includes the name of that disk.
Object
|
cceFailedDiskName
|
OID
|
1.3.6.1.4.1.9.9.178.1.5.1
|
Type
|
OCTET STRING
|
Permission
|
accessible-for-notify
|
Status
|
current
|
MIB
|
CISCO-CONTENT-ENGINE-MIB; View Supporting Images
|
ciscoContentEngineDiskFailed OID
The ciscoContentEngineDiskFailed trap signifies that a Content Engine data drive failed. This object supersedes ciscoContentEngineDataDiskFailed. Additional information about the error is logged to syslog.
Object
|
ciscoContentEngineDiskFailed
|
OID
|
1.3.6.1.4.1.9.9.178.2.0.6
|
Status
|
current
|
MIB
|
CISCO-CONTENT-ENGINE-MIB; View Supporting Images
|
Trap Components
|
cceFailedDiskName
|
Feedback
