Introduction
This document describes the steps to read the information about Object Identifiers (OIDs) within the Secure Web Appliance (SWA).
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- SWA administration
- Fundamental of Simple Network Management Protocol (SNMP)
- Fundamental networking principles
Cisco recommends that you have:
- Physical or Virtual SWA Installed.
- Administrative Access to the SWA Command Line Interface (CLI).
Components Used
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Problem
For network administrators and IT professionals working with Cisco Secure Web Appliance (SWA) and Security Management Appliance (SMA), the snmpwalk command is a crucial tool for retrieving OID values necessary for effective monitoring and management.
While snmpwalk is readily available on macOS, additional setup is required on Windows and Linux systems, which can be a barrier for some users.
To overcome this challenge, we have conducted snmpwalk commands in our lab and are providing the outputs for reference. This resource is intended to support users who face setup restrictions by offering these reference outputs, aiding in the management of their SWA and SMA environments.
OIDs play a vital role in network management, allowing for the identification and interaction with various network elements. By leveraging snmpwalk, users can efficiently obtain and interpret values associated with important OIDs, enhancing the monitoring and management of SWA and SMA systems. This guide walks you through using snmpwalk to access these key OID values, boosting your network management capabilities.
Solution
Here you can find sequence of OID name, snmpwalk command syntax and sample output.
SWA Sample Ouptut
Percent CPU Utilization
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.2.0
ASYNCOS-MAIL-MIB::perCentCPUUtilization.0 = INTEGER: 16
Percent Memory Utilization
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.1.0
ASYNCOS-MAIL-MIB::perCentMemoryUtilization.0 = INTEGER: 11
Disk Utilization
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.27.0
ASYNCOS-MAIL-MIB::diskUtilization.0 = STRING: Total_disk_space: 198.391 GB, Available_disk_space: 107.845 GB, Used_disk_space: 90.545 GB, Used_disk_space in % : 45.64
CPU Temperature
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.9.1.2
Fan Table
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.10
Power Supply Unit (PSU) Status
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.9.9.117.1.3.1
Note: The output of this command "1" means PSU not installed, "2" means PSU is healthy, "3" means no AC power, and "4" means PSU faulty.
Interface Link Status
snmpwalk -O a -v 2c -c <Community Name> -M <path to MIB files> -m "ALL" <SWA IP Address> .1.3.6.1.4.1.15497.1.2.5.1
Note: In the out put of this command, "1" means the Interface is up and "2" menas the Interface is down.
SMA Sample Ouptut
Power Supply Unit (PSU) Status
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.8
iso.3.6.1.4.1.15497.1.1.1.8.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.15497.1.1.1.8.1.2.1 = INTEGER: 2
iso.3.6.1.4.1.15497.1.1.1.8.1.3.1 = INTEGER: 1
iso.3.6.1.4.1.15497.1.1.1.8.1.4.1 = STRING: "PS 1"
Note: The output of this command "1" means PSU not installed, "2" means PSU is healthy, "3" means no AC power, and "4" means PSU faulty.
Fan Table
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.10
iso.3.6.1.4.1.15497.1.1.1.10.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.15497.1.1.1.10.1.1.2 = INTEGER: 2
iso.3.6.1.4.1.15497.1.1.1.10.1.1.3 = INTEGER: 3
iso.3.6.1.4.1.15497.1.1.1.10.1.1.4 = INTEGER: 4
iso.3.6.1.4.1.15497.1.1.1.10.1.1.5 = INTEGER: 5
iso.3.6.1.4.1.15497.1.1.1.10.1.1.6 = INTEGER: 6
iso.3.6.1.4.1.15497.1.1.1.10.1.1.7 = INTEGER: 7
iso.3.6.1.4.1.15497.1.1.1.10.1.1.8 = INTEGER: 8
iso.3.6.1.4.1.15497.1.1.1.10.1.1.9 = INTEGER: 9
iso.3.6.1.4.1.15497.1.1.1.10.1.1.10 = INTEGER: 10
iso.3.6.1.4.1.15497.1.1.1.10.1.1.11 = INTEGER: 11
iso.3.6.1.4.1.15497.1.1.1.10.1.1.12 = INTEGER: 12
iso.3.6.1.4.1.15497.1.1.1.10.1.1.13 = INTEGER: 13
iso.3.6.1.4.1.15497.1.1.1.10.1.1.14 = INTEGER: 14
iso.3.6.1.4.1.15497.1.1.1.10.1.2.1 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.2 = Gauge32: 10712
iso.3.6.1.4.1.15497.1.1.1.10.1.2.3 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.4 = Gauge32: 11227
iso.3.6.1.4.1.15497.1.1.1.10.1.2.5 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.6 = Gauge32: 11227
iso.3.6.1.4.1.15497.1.1.1.10.1.2.7 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.8 = Gauge32: 11227
iso.3.6.1.4.1.15497.1.1.1.10.1.2.9 = Gauge32: 10080
iso.3.6.1.4.1.15497.1.1.1.10.1.2.10 = Gauge32: 10712
iso.3.6.1.4.1.15497.1.1.1.10.1.2.11 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.12 = Gauge32: 11227
iso.3.6.1.4.1.15497.1.1.1.10.1.2.13 = Gauge32: 10500
iso.3.6.1.4.1.15497.1.1.1.10.1.2.14 = Gauge32: 10712
iso.3.6.1.4.1.15497.1.1.1.10.1.3.1 = STRING: "FAN 1"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.2 = STRING: "FAN 2"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.3 = STRING: "FAN 3"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.4 = STRING: "FAN 4"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.5 = STRING: "FAN 5"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.6 = STRING: "FAN 6"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.7 = STRING: "FAN 7"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.8 = STRING: "FAN 8"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.9 = STRING: "FAN 9"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.10 = STRING: "FAN 10"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.11 = STRING: "FAN 11"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.12 = STRING: "FAN 12"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.13 = STRING: "FAN 13"
iso.3.6.1.4.1.15497.1.1.1.10.1.3.14 = STRING: "FAN 14"
Percent CPU Utilization
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.2.0
iso.3.6.1.4.1.15497.1.1.1.2.0 = INTEGER: 0
Percent Memory Utilization
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.1.0
iso.3.6.1.4.1.15497.1.1.1.1.0 = INTEGER: 0
Disk Utilization
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.27.0
iso.3.6.1.4.1.15497.1.1.1.27.0 = STRING: "Total_disk_space: 556.391 GB, Available_disk_space: 526.995 GB, Used_disk_space: 29.396 GB, Used_disk_space in % : 5.28"
CPU Temperature
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.4.1.15497.1.1.1.9.1.2
iso.3.6.1.4.1.15497.1.1.1.9.1.2.1 = INTEGER: 35
Interface Link Status
snmpwalk -O a -v 2c -c <Community Name> -m <path to MIB files> <SWA IP Address> .1.3.6.1.2.1.2.2.1.8
iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
Note: In the out put of this command, "1" means the Interface is up and "2" means the Interface is down.
View OIDs
Cisco does not provide OID list for the content security appliances. You can convert the MIB file to view OID using a third-party MIB Browser Application such as Paessler MIB Imported. You can download this third-party application from this link.
Here are the steps to read the OIDs:
Step 1. Download the MIB Browser software
Step 2. Download the MIB files of the Content security Appliance (The latest MIB files can be downloaded here.)
Image: Download MIB Files
Step 3. Import The MIB File to your application.
Note: You need to download and Import the SMI MIB and the Web MIB.
Step 4. You can view all the OIDs defined in the MIB files.
Note: Please be aware that certain OIDs, such as those related to the Fan Table and Power Supply might not return any output in a virtual lab environment. This is because these components are not present in virtual appliances.
Related Information