Cisco Cisco IOS Software Releases 12.2 MC
12
Release Notes for Cisco MWR 1941-DC Mobile Wireless Edge Router for Cisco IOS Release 12.2(15)MC1
OL-13984-06
Troubleshooting
•
CSCin16619
Upon deleting a channel group, tracebacks might occur at “process_ok_to_reschedule” and traffic
might not pass through even though the interface is up and the routes exist.
might not pass through even though the interface is up and the routes exist.
•
CSCin31634
SNMP query of ciscoFlashDeviceSize returns 0.
•
CSCin32105
The cardSerial and cardSlots MIB variables display the wrong values.
Troubleshooting
Collecting Data for Router Issues
To collect data for reporting router issues, issue the following command:
•
show tech-support—Displays general information about the router when it reports a problem.
Collecting Data for Redundancy Issues
To collect data for redundancy-related issues, issue the following commands while in EXEC mode:
•
show cdp neighbors—Displays detailed information about neighboring devices discovered using
Cisco Discovery Protocol (CDP).
Cisco Discovery Protocol (CDP).
•
show controllers—Displays information that is specific to the hardware.
•
show ip interface—Displays the usability status of interfaces configured for IP.
•
show redundancy—Displays current or historical status and related information on redundant Dial
Shelf Controllers (DSCs).
Shelf Controllers (DSCs).
•
show standby—Displays Hot Standby Router Protocol (HSRP) information.
•
show standby brief—Displays Hot Standby Router Protocol (HSRP) information; specifically, with
the brief keyword specified, a single line of output summarizing each standby group.
the brief keyword specified, a single line of output summarizing each standby group.
Collecting Data for ROMmon Issues
To collect data for ROMmon issues, issue the following command while in EXEC mode:
•
showmon— Displays currently selected ROM monitor.
Collecting Data for Router Rebooting to ROMmon
If a router reboot to ROMmon occurs, issue the dir device ID command where device ID is slot0:, and
look for the router processor or network processor exception file (crashinfo* or pxf_crashinfo*
respectively). Once you have located one of these files, you can email the file along with a description
of the problem to your Cisco representative.
look for the router processor or network processor exception file (crashinfo* or pxf_crashinfo*
respectively). Once you have located one of these files, you can email the file along with a description
of the problem to your Cisco representative.