HWIF-QOS-ERR: Invalid QoS Port Type errors messages may be displayed after configuratio...
HWIF-QOS-ERR: Invalid QoS Port Type errors messages may be displayed after configurations are saved to a device (6500, 7600) with a cisco supervisor engine 720.
This would seem to be a cosmetic hardware interface descriptor block bug that is resolved in cisco ios 12.2(33)SXH and later.
To crash a router, issue the "router#test crash" hidden privilege EXEC command. Once th...
To crash a router, issue the "router#test crash" hidden privilege EXEC command. Once the command is issued, you will need to select "C" to reconfirm your intention and then you'll be asked to select a number corresponding to the type of crash you want executed.
For example:
Router#test crash
WARNING: Command selections marked with '(crash router)' will crash
router when issued. However a selection 'C' will need to
be issued IMMEDIATELY before these selections to enable them.
Type the number for the selected crash:
--------------------------------------
1 (crash router) Bus Error, due to invalid address access
2 (crash router) Bus Error, due to parity error in Main memory
3 (crash router) Bus Error, due to parity error in I/O memory
4 (crash router) Address Error, due to fetching code from odd address
5 (crash router) Jump to zero
6 (crash router) Software forced crash
7 (crash router) Illegal read of address zero
8 (crash router) Divide by zero
9 (crash router) Corrupt memory
C Enable crash router selection marked with (crash router)
U (crash router) User enter write bus error address
W (crash router) Software watchdog timeout (*** Watch Dog Timeout ***)
w (crash router) Process watchdog timeout (SYS-2-WATCHDOG)
d Disable crashinfo collection
e Enable crashinfo collection
i Display contents of current crashinfo flash file
n Change crashinfo flash file name
s Save crashinfo to current crashinfo flash file
q Exit crash menu
? C
!--- Enter C here and press return.
Type the number for the selected crash:
--------------------------------------
1 (crash router) Bus Error, due to invalid address access
2 (crash router) Bus Error, due to parity error in Main memory
3 (crash router) Bus Error, due to parity error in I/O memory
4 (crash router) Address Error, due to fetching code from odd address
5 (crash router) Jump to zero
6 (crash router) Software forced crash
7 (crash router) Illegal read of address zero
8 (crash router) Divide by zero
9 (crash router) Corrupt memory
C Enable crash router selection marked with (crash router)
U (crash router) User enter write bus error address
W (crash router) Software watchdog timeout (*** Watch Dog Timeout ***)
w (crash router) Process watchdog timeout (SYS-2-WATCHDOG)
d Disable crashinfo collection
e Enable crashinfo collection
i Display contents of current crashinfo flash file
n Change crashinfo flash file name
s Save crashinfo to current crashinfo flash file
q Exit crash menu
? 6
!--- Enter the number that corresponds to
!--- the crash type you want to test.
Unexpected exception, CPU signal 23, PC = 0x400E8DA8
-Traceback= 400E8DA8 40C6A4DC 404006E09C 400C477C 400C4768
To Connect To The Linecard Console use the interface console [Slot/Subslot] command as ...
To Connect To The Linecard Console
use the interface console [Slot/Subslot] command as shown below;
router#if-con [Slot/Subslot]
For example router#if-con 1/0
Depending on your IOS software, you may need to first enable service internal before the if-con command is enabled. Be sure to trun off service internal afterwards as it may impact performance and make available other normally hidden engineering debug commands that may impact the device negatively.
Tags: advertise-map bgp cisco cscin73487 ios non-exist-map software
Last Updated: 10 months ago - 137 Views
