SteelHead Interceptor Management Information Base (MIB)
  
SteelHead Interceptor Management Information Base (MIB)
This appendix provides a reference to the MIB and SNMP traps.
The MIB monitors device status, peers, and provides network statistics for seamless integration into network management systems such as Hewlett Packard OpenView Network Node Manager, PRTG, and other SNMP browser tools.
Note: For details about configuring and using these network monitoring tools, consult the vendor documentation.
This appendix includes the following sections:
•  Accessing MIB Files
•  SNMP Traps
Accessing MIB Files
The following guidelines describe how to download and access the MIB:
•  You can download the MIB file from the Help: Online Help page.
•  You can load the MIB file into any MIB browser utility.
•  Some utilities might expect a file type other than a text file. If this occurs, change the file type to the one expected.
•  Some utilities assume that the root is mib-2 by default. If the utility sees a new node, such as enterprises, it might look under mib-2.enterprises. If this occurs, use .iso.org.dod.internet.private.enterprises.rbt as the root.
•  Some command-line browsers might not load all MIB files by default. If this occurs, find the appropriate command option to load the RBT-mib.txt file. For example, for NET-SNMP browsers: snmwalk -m all.
SNMP Traps
The following table summarizes the SNMP traps sent to trap receivers for alarm event notification.
Trap and OID
Interceptor State
Text
Description
admissionConnError
(enterprises.17163.1.3.4.1.7)
Admission Control
Admission control connections alarm has been triggered.
The appliance has reached its rated capacity for optimized connections. During this event, the appliance continues to optimize existing connections, but new connections are then passed through without optimization.
admissionConnErrorClear
(enterprises.17163.1.3.4.1.1007)
 
Admission control connections alarm has been cleared, and the service is running normally.
The admission control connection alarms has been cleared and the service is running normally.
The alarm indicates that the condition has been corrected.
admissionMemError
(enterprises.17163.1.3.4.1.6)
Admission Control
Admission control memory alarm has been triggered.
The appliance has reached its rated capacity for optimized connections. During this event, the appliance continues to optimize existing connections, but new connections are then passed through without optimization.
admissionMemErrorClear
(enterprises.17163.1.3.4.1.1006)
 
Admission control memory alarm has been cleared, and the optimization service is running normally
The admission control connection alarms has been cleared and the service is running normally.
The alarm indicates that the condition has been corrected.
admissionServiceError
(enterprises.17163.1.3.4.1.28)
 
Admission control service alarm has been triggered
The admission control connection alarms has been triggered.
admissionServiceErrorClear
(enterprises.17163.1.3.4.1.1028)
 
Admission control service alarm has been cleared, and the optimization service is running normally.
The admission control connection alarms has been cleared and the service is running normally.
bypassMode
(enterprises.17163.1.3.4.1.5)
Critical
The appliance has entered bypass (failthru) mode.
The appliance has entered bypass mode and is now passing through all traffic unoptimized. This event can be the result of a system crash or a manual configuration change, such as a service restart or system reboot.
bypassModeClear
(enterprises.17163.1.3.4.1.1005)
 
Traffic is now being optimized.
The traffic is being optimized.
The alarm indicates that the condition has been corrected.
clusterAdmissionConnAlertClear
(enterprises.17163.1.3.4.3.1003)
 
Cluster SteelHeads are no longer under admission control.
Cluster SteelHeads are no longer under admission control.
The alarm indicates that the condition has been corrected.
clusterAdmissionConnAlertError
(enterprises.17163.1.3.4.3.3)
 
A cluster SteelHead has been reported to be in Admission Control.
A cluster SteelHead has been reported to be in Admission Control.
clusterCapacityAlertClear
(enterprises.17163.1.3.4.3.1004)
 
Cluster SteelHeads are no longer at capacity.
Cluster SteelHeads are no longer at capacity.
The alarm indicates that the condition has been corrected.
clusterCapacityAlertError
(enterprises.17163.1.3.4.3.4)
 
A cluster SteelHead has been reported to be at capacity.
A cluster SteelHead has been reported to be at capacity.
clusterDisconnectedIBAlertClear
(enterprises.17163.1.3.4.3.1002)
 
All cluster Interceptors are currently connected.
All cluster SteelHead Interceptors are currently connected.
The alarm indicates that the condition has been corrected.
clusterDisconnectedIBAlertError
(enterprises.17163.1.3.4.3.2)
 
A cluster Interceptor has been reported as disconnected.
A cluster Interceptor has been reported as disconnected.
clusterDisconnectedSHAlertClear
(enterprises.17163.1.3.4.3.1001)
 
All cluster SteelHeads are currently connected.
All cluster SteelHeads are currently connected.
The alarm indicates that the condition has been corrected.
clusterDisconnectedSHAlertError
(enterprises.17163.1.3.4.3.1)
Degraded
A cluster SteelHead has been reported as disconnected.
A cluster SteelHead has been reported as disconnected.
clusterPermPenaltyAlertClear
(enterprises.17163.1.3.4.3.1005)
 
Cluster SteelHeads are no longer issued a permanent penalty.
Cluster SteelHeads are no longer issued a permanent penalty.
The alarm indicates that the condition has been corrected.
clusterPermPenaltyAlertError
(enterprises.17163.1.3.4.3.5)
 
A cluster SteelHead has been reported to have a permanent penalty.
A cluster SteelHead has been reported to have a permanent capacity reduction.
clusterVersionIncompatibleIcAlertClear
(enterprises.17163.1.3.4.3.1006)
 
A version incompatibility in Interceptors has been corrected.
A version incompatibility in SteelHead Interceptors has been corrected.
The alarm indicates that the condition has been corrected.
clusterVersionIncompatibleIcAlertError
(enterprises.17163.1.3.4.3.6)
 
A version incompatibility in Interceptors has been detected.
A version incompatibility in Interceptors has been detected.
clusterVersionIncompatibleShAlertClear
(enterprises.17163.1.3.4.3.1007)
 
A version incompatibility in SteelHeads has been corrected.
A version incompatibility in SteelHeads has been corrected.
The alarm indicates that the condition has been corrected.
clusterVersionIncompatibleShAlertError
(enterprises.17163.1.3.4.3.7)
 
A version incompatibility in SteelHeads has been detected.
A version incompatibility in SteelHeads has been detected.
configChange
(enterprises.17163.1.3.4.1.17)
Healthy
A change has been made to the system configuration.
A change has been made to the system configuration.
confModeEnter
(enterprises.17163.1.3.4.1.9)
Healthy
A user has entered configuration mode.
A system user has entered configuration mode from either the CLI or Management Console.
confModeExit
(enterprises.17163.1.3.4.1.10)
Healthy
A user has exited configuration mode.
A system user has exited configuration mode from either the CLI or Management Console.
cpuUtil
(enterprises.17163.1.3.4.1.3)
Degraded
The average CPU utilization in the past minute has gone above the acceptable threshold.
Average CPU utilization has exceeded an acceptable threshold.
If CPU utilization spikes are frequent, it might be because the system is undersized. Sustained CPU load might be symptomatic of more serious issues; for details, contact Riverbed Support.
cpuUtilClear
(enterprises.17163.1.3.4.1.1003)
 
The average CPU utilization has fallen back within the acceptable threshold.
Average CPU utilization has fallen back to an acceptable threshold.
The alarm indicates that the condition has been corrected.
fanError
(enterprises.17163.1.3.4.1.13)
Degraded
A fan has failed on this appliance (not supported on all models).
A fan error has occurred.
fanErrorClear
(enterprises.17163.1.3.4.1.1013)
 
 
All system fans are now functioning normally. Not supported on all models.
The system fans are functioning properly.
The alarm indicates that the condition has been corrected.
hardwareError
(enterprises.17163.1.3.4.1.20)
 
Either Critical or Degraded, depending on the state
Hardware error detected.
 
A hardware error has been detected.
hardwareErrorClear
(enterprises.17163.1.3.4.1.1020)
 
Hardware error has been cleared.
The hardware error has been cleared.
The alarm indicates that the condition has been corrected.
instanceHealthAlertClear
(enterprises.17163.1.3.4.4.1001)
 
An instance error has been corrected.
An instance error has been corrected.
The alarm indicates that the condition has been corrected.
InstanceHealthAlertError
(enterprises.17163.1.3.4.1.1)
 
An instance error has been detected.
An instance error has been detected.
ipmi
(enterprises.17163.1.3.4.1.15)
Degraded
An IPMI event has been detected on the appliance. Please check the details in the alarm report on the web UI (not supported on all models).
One of the following Intelligent Platform Management Interface (IPMI) events has been triggered:
•  Chassis intrusion (physical opening and closing of the appliance case)
•  Memory errors (correctable or uncorrectable ECC memory errors)
•  Hard drive faults and predictive failures
•  Power supply status and predictive failure
The alarms can be cleared by using the CLI command clear hardware error-log.
You can view the complete contents of the IPMI event log with the CLI command show hardware error-log all.
(ipmiClear indicates that the condition has been corrected.)
ipmiClear
(enterprises.17163.1.3.4.1.1015)
 
An IPMI event has been rectified on the appliance. Not supported on all models.
The Intelligent Platform Management Interface (IPMI) has been rectified.
The alarm indicates that the condition has been corrected.
licenseError
(enterprises.17163.1.3.4.1.25)
Needs Attention
The main appliance license has expired, been removed, or become invalid.
A license on the SteelHead has been removed, has expired, or is invalid.
The alarm clears when a valid license is added or updated.
licenseExpiring
(enterprises.17163.1.3.4.1.26)
Needs Attention
One or more licensed features will expire within the next two weeks.
Choose Configure > Maintenance > Licenses and look at the Status column to see which licenses are about to expire. One or more feature licenses are scheduled to expire within two weeks.
This alarm is triggered per feature. Suppose you installed two license keys for a feature, LK1-FOO-xxx, which is going to expire in two weeks, and LK1- FOO-yyy, which is not expired. Because one license for the feature is valid, the alarm does not trigger.
licenseExpired
(enterprises.17163.1.3.4.1.27)
Needs Attention
One or more licensed features have expired.
Choose Configure > Maintenance > Licenses and look at the Status column to see which licenses have expired. One or more feature licenses have expired.
This alarm is triggered per feature. Suppose you installed two license keys for a feature, LK1-FOO-xxx (expired), and LK1-FOO-yyy (not expired). Because one license for the feature is valid, the alarm does not trigger.
linkDuplex
(enterprises.17163.1.3.4.1.70)
Degraded
An interface on the appliance is in half-duplex.
Indicates that an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode. Half-duplex significantly limit the optimization service results.
linkDuplexClear
(enterprises.17163.1.3.4.1.1070)
 
An interface on the appliance has cleared the half-duplex error.
Indicates that an interface on the appliance has been cleared.
linkError
(enterprises.17163.1.3.4.1.11)
Degraded
An interface on the appliance has lost its link.
An interface has lost a link.
linkErrorClear
(enterprises.17163.1.3.4.1.1011)
 
An interface on the appliance has regained its link.
An interface has regained a link.
The alarm indicates that the condition has been corrected.
linkIoErrors
(enterprises.17163.1.3.4.1.71)
Degraded
An interface on the appliance is suffering I/O errors.
Indicates that the error rate on an interface has exceeded 0.1 percent while either sending or receiving packets. This threshold is based on the observation that even a small link error rate reduces TCP throughput significantly. A properly configured LAN connection should experience very few errors. The alarm clears when the error rate drops below 0.05 percent.
To troubleshoot, try a new cable and a different switch port. Another possible cause is electromagnetic noise nearby.
linkIoErrorsClear
(enterprises.17163.1.3.4.1.1071)
 
An interface on the appliance has cleared the I/O error state.
Indicates that the error rate on an interface has been cleared.
linkPropagationStateAllError
(enterprises.17163.1.3.4.1.23)
 
Link state propagation is detected on all enabled in-path interfaces.
Link state propagation is detected on all enabled in-path interfaces.
linkPropagationStateAllErrorClear
(enterprises.17163.1.3.4.1.1023)
 
Some link propagation state error on the appliance has been rectified.
A link state propagation error has been rectified.
The alarm indicates that the condition has been corrected.
linkPropagationStateError
(enterprises.17163.1.3.4.1.16)
 
An interface has link propagation state error on the appliance.
An interface has detected a link propagation state error.
linkPropagationStateErrorClear
(enterprises.17163.1.3.4.1.1016)
 
A link propagation state error on an interface on the appliance has been rectified.
An interface error has been rectified.
The alarm indicates that the condition has been corrected.
loadBalanceServiceAlertClear
(enterprises.17163.1.3.4.2.1004)
 
The Interceptor service is back up and running.
The Interceptor service is back up and running.
The alarm indicates that the condition has been corrected.
loadBalanceServiceAlertError
(enterprises.17163.1.3.4.2.4)
 
The Interceptor service is not running.
 
The Interceptor service is not running.
loadOversubscriptionAlertClear
(enterprises.17163.1.3.4.2.1001)
 
Load SteelHeads are no longer oversubscribed.
The SteelHeads are not over subscribed.
The alarm indicates that the condition has been corrected.
loadOversubscriptionAlertError
(enterprises.17163.1.3.4.2.1)
 
A local SteelHead has been reported as oversubscribed.
A local SteelHead has been reported as oversubscribed.
loadRemoteAlertClear
(enterprises.17163.1.3.4.2.1003)
 
Remote SteelHeads are no longer timed out.
The remote SteelHeads are no longer timed out.
The alarm indicates that the condition has been corrected.
loadRemoteAlertError
(enterprises.17163.1.3.4.2.3)
 
A remote SteelHead has timed out.
A remote SteelHead has timed out.
loadUnpairedAlertClear
(enterprises.17163.1.3.4.2.1002)
 
Load SteelHeads are no longer unpaired.
The load SteelHeads are no longer unpaired.
The alarm indicates that the condition has been corrected.
loadUnpairedAlertError
(enterprises.17163.1.3.4.2.2)
 
A local SteelHead has been reported as unpaired.
A local SteelHead has been reported as unpaired.
memoryError
(enterprises.17163.1.3.4.1.14)
Degraded
A memory error has been detected on the appliance.
A memory error has occurred.
memoryErrorClear
(enterprises.17163.1.3.4.1.1014)
 
A memory error has been rectified on the appliance. Not supported on all models.
The memory error has been rectified.
The alarm indicates that the condition has been corrected.
pagingActivity
(enterprises.17163.1.3.4.1.4)
Degraded
The system has been paging excessively (thrashing).
The system is running low on memory and has begun swapping memory pages to disk.
This event can be triggered during a software upgrade and is normal. If this event be triggered at any other time, contact Riverbed Support.
pagingActivityClear
(enterprises.17163.1.3.4.1.1004)
 
The system has stopped paging excessively (thrashing).
The system has stopped paging excessively.
The alarm indicates that the condition has been corrected.
powerSupplyError
(enterprises.17163.1.3.4.1.12)
Degraded
A power supply on the appliance has failed (not supported on all models).
A power supply has gone down.
powerSupplyErrorClear
(enterprises.17163.1.3.4.1.1012)
 
All power supplies are now functioning normally. Not supported on all models.
The power supply is back on.
The alarm indicates that the condition has been corrected.
procCrash
(enterprises.17163.1.3.4.1.1)
Healthy
A procCrash trap signifies that a process managed by PM has crashed and left a core file. The variable sent with the notification indicates which process crashed.
A process has crashed and subsequently been restarted by the system. The system has created a snapshot associated with this crash. You can access the snapshot using the CLI or Management Console. Riverbed Support might need this information to determine the cause of the crash.
procExit
(enterprises.17163.1.3.4.1.2)
Healthy
A procExit trap signifies that a process managed by PM has exited unexpectedly, but not left a core file. The variable sent with the notification indicates which process exited.
A process has unexpectedly exited and been restarted by the system. The process might have exited on its own or due to other process failures. Contact Riverbed Support to determine the cause of this event.
raidError
(enterprises.17163.1.3.4.1.22)
Degraded
An error has been generated by the RAID array.
An error has been generated by the RAID array.
A drive has failed in a RAID array. Consult the CLI or Management Console to determine the location of the failed drive. Contact Riverbed Support for assistance with installing a new drive, a RAID rebuild, or drive reseating. The appliance continues to optimize during this event. After the error is corrected, the alarm clears automatically.
raidErrorClear
(enterprises.17163.1.3.4.1.1022)
 
A RAID error has been cleared.
A RAID error has been cleared.
The alarm indicates that the condition has been corrected.
scheduledJobError
(enterprises.17163.1.3.4.1.8)
Healthy
A scheduled job has failed during execution.
A scheduled job on the system (for example, a software upgrade) has failed.
suspectedScannerAlertError
(enterprise.17163.1.3.4.5.1)
Needs Attention
There is suspected scanner traffic on the network.
The SteelHead Interceptor is attempting to optimize traffic which is scanner in nature.
suspectedScannerAlertClear
(enterprise. 17163.1.3.4.5.1001)
 
Suspected scanner traffic is no longer running on the network.
The SteelHead Interceptor is no longer attempting to optimize traffic which is scanner in nature.
The alarm indicates that the condition has been corrected.
systemDiskFullError
(enterprises.17163.1.3.4.1.21)
Degraded
One or more system partitions is full or almost full.
One or more system partitions are full or almost full. The alarm clears when the system partitions fall below usage thresholds.
systemDiskFullErrorClear
(enterprises.17163.1.3.4.1.1021)
 
The system partitions are below usage thresholds.
The system partitions are below usage thresholds.
The alarm indicates that the condition has been corrected.
temperatureCritical
(enterprises.17163.1.3.4.1.19)
Critical
The system temperature has reached a critical stage.
The system temperature has reached a critical stage.
This trap/alarm triggers a critical state on the appliance. This alarm occurs when the appliance temperature reaches 90 degrees C. The temperature value is not user-configurable. Reduce the appliance temperature.
temperatureNonCritical
(enterprises.17163.1.3.4.1.1019)
Healthy
The system temperature is no longer in a critical stage.
The system temperature is no longer in a critical stage.
temperatureNormal
(enterprises.17163.1.3.4.1.1018)
 
The system temperature is back within the threshold.
The system temperature is back within the threshold.
temperatureWarning
(enterprises.17163.1.3.4.1.18)
 
The system temperature has exceeded the threshold.
The system temperature has exceeded the threshold.
The appliance temperature is a configurable notification. By default, this notification is set to trigger when the appliance reached 70 degrees C. Raise the alarm trigger temperature if it is normal for the SteelHead to get that hot, or reduce the temperature of the SteelHead.
xbridgeError
(enterprises.17163.1.3.4.1.24
 
Xbridge is enabled but not running.
Xbridge is enabled but not running.
xbridgeErrorClear
(enterprises.17163.1.3.4.1.1024
 
An Xbridge error has been cleared.
An Xbridge error has been cleared.
The alarm indicates that the condition has been corrected.
For details on setting SNMP trap contacts and SNMP trap receivers, see Configuring SNMP Basic Settings.