Cisco Cisco IOS Software Release 12.0 S
155
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
New and Changed Information
New Software Features in Cisco IOS Release 12.0(24)S
For more information about how to configure and use Sampled NetFlow, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/12soutfl.htm
Periodic MIB Data Collection and Transfer Mechanism
Platform: Cisco 12000 series
The Periodic MIB Data Collection and Transfer Mechanism feature provides the ability to periodically
transfer selected MIB data from Cisco IOS based devices to specified Network Management Stations
(NMSs). Using the command line interface (CLI), data from multiple MIBs can be grouped into lists,
and a polling interval (frequency of data collection) can be configured. All the MIB objects in a list are
periodically polled using this specified interval. The collected data from the lists can then be transferred
to a specified NMS at a user-specified transfer interval (frequency of data transfer) using TFTP, RCP, or
FTP.
transfer selected MIB data from Cisco IOS based devices to specified Network Management Stations
(NMSs). Using the command line interface (CLI), data from multiple MIBs can be grouped into lists,
and a polling interval (frequency of data collection) can be configured. All the MIB objects in a list are
periodically polled using this specified interval. The collected data from the lists can then be transferred
to a specified NMS at a user-specified transfer interval (frequency of data transfer) using TFTP, RCP, or
FTP.
QA Error Recovery for the Cisco 7500
Platform: Cisco 7500 series
The QA Error Recovery for the Cisco 7500 feature helps the networking device to recover quickly from
problems known as QAERRORs. These QAERRORs can be caused by hardware or software issues.
When a QAERROR occurs, the device can hang while it tries to recover from the problem. On fully
loaded devices, hang times following QAERRORs can be up to five minutes (300 seconds). With the
QAERROR recovery enabled, the hang time can be a little as one second.
problems known as QAERRORs. These QAERRORs can be caused by hardware or software issues.
When a QAERROR occurs, the device can hang while it tries to recover from the problem. On fully
loaded devices, hang times following QAERRORs can be up to five minutes (300 seconds). With the
QAERROR recovery enabled, the hang time can be a little as one second.
In Cisco IOS Release 12.0(24)S1, Release 12.0(24)S2, and Release 12.0(24)S3, you must enable QA
Error Recovery for the Cisco 7500 feature by entering the following global configuration command:
Error Recovery for the Cisco 7500 feature by entering the following global configuration command:
hw-module main-cpu qaerror-recovery-enable
Note
In releases following Cisco IOS Release 12.0(24)S3—that is, from Cisco IOS Release 12.0(25)S
on—the QA Error Recovery for the Cisco 7500 feature is enabled by default.
on—the QA Error Recovery for the Cisco 7500 feature is enabled by default.
You can tell that recovery from an error was successful because a message reporting a successful
recovery will appear on the console screen. Additionally, the number of QAERROR recoveries is
displayed in the output of the show controllers cbus command.
recovery will appear on the console screen. Additionally, the number of QAERROR recoveries is
displayed in the output of the show controllers cbus command.
The following example shows the output of the console or show logs when QAERROR happened.
Although the example indicates both the point at which the feature begins trying to recover from the
QAERROR and the point at which the device recovers from the error, the networking device may display
many additional messages that can help service technicians diagnose the actual cause of the problem.
Although the example indicates both the point at which the feature begins trying to recover from the
QAERROR and the point at which the device recovers from the error, the networking device may display
many additional messages that can help service technicians diagnose the actual cause of the problem.
%QA-3-DIAG:Trying to recover from QA ERROR.
%QA-3-DIAG:Removing buffer header 0xE360 from all queues
%QA-3-DIAG:Buffer 0xE360 is element 155 on queue 0x2E
%QA-3-DIAG:Queue 0x2E (48000170) has 154 elements
%QA-3-DIAG:Buffer 0xE360 is element 1 on queue 0x340
%QA-3-DIAG:Queue 0x340 (48001A00) has 0 elements
%QA-3-DIAG:At least one QA queue is broken
%QA-3-DIAG:Recovered from QA ERROR