I am having trouble booting SUP-32 on 7606-S Chassis. Tried two different IOS but getting below errors: rommon 4 >  boot disk0:c7600s3223-advipservicesk9-mz.122-33.SRE12.bin Initializing ATA monitor library... Self extracting the image... [OK] Self decompressing the image : ######################################################################################################## [OK]               Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013.            cisco Systems, Inc.            170 West Tasman Drive            San Jose, California 95134-1706 Cisco IOS Software, c7600s3223_sp Software (c7600s3223_sp-ADVIPSERVICESK9-M), Version 12.2(33)SRE12, RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Thu 12-Mar-15 00:26 by prod_rel_team MAC based EOBC installed *Jan  1 01:55:54.567: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 01:55:52.359: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor *Jan  1 01:55:54.567: %OIR-SP-6-CONSOLE: Changing console ownership to route processor System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 2004 by cisco Systems, Inc. Cat6k-MSFC2A platform with 524288 Kbytes of main memory rommon 1 > *Jan  1 01:58:55.595: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 01:55:54.835: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. Firmware compiled 08-Dec-11 13:19 by integ Build [100] *Jan  1 01:58:55.595: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor %Software-forced reload  01:58:55 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DDD0F0 0x40DE5728 0x40DE6A14 0x40DA2CEC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B17910, a1 : BE880000, a2 : 00004038, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 444A0000, s3 : 00000000 s4 : 00000000, s5 : 44490000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849DAB40, k1 : 05389200 gp : 424433F0, sp : 51033EB0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00000000, MDHI     : 00000009, BadVaddr : D37AFBDF DATA_START : 0x4214F2B0 Cause 00000024 (Code 0x9): Breakpoint exception  01:58:55 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DDD0F0 0x40DE5728 0x40DE6A14 0x40DA2CEC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B17910, a1 : BE880000, a2 : 00004038, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 444A0000, s3 : 00000000 s4 : 00000000, s5 : 44490000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849DAB40, k1 : 05389200 gp : 424433F0, sp : 51033EB0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00000000, MDHI     : 00000009, BadVaddr : D37AFBDF DATA_START : 0x4214F2B0 Cause 00000024 (Code 0x9): Breakpoint exception File bootdisk:crashinfo_20000101-015855-UTC Device Error :No such device  01:58:55 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DDD0F0 0x40DE5728 0x40DE6A14 0x40DA2CEC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B17910, a1 : BE880000, a2 : 00004038, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 444A0000, s3 : 00000000 s4 : 00000000, s5 : 44490000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849DAB40, k1 : 05389200 gp : 424433F0, sp : 51033EB0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00000000, MDHI     : 00000009, BadVaddr : D37AFBDF DATA_START : 0x4214F2B0 Cause 00000024 (Code 0x9): Breakpoint exception -Traceback= 0x4054EAC0 0x4054D9A4 0x40DDD0F0 0x40DE5728 0x40DE6A14 0x40DA2CEC ------------------ show chunk failures ------------------ ------------------ show redundancy states ------------------ File bootdisk:crashinfo_20000101-015856-UTC Device Error :No such device === Flushing messages (01:58:58 UTC Sat Jan 1 2000) === Buffered messages: Queued messages: *Jan  1 01:58:58.523: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 01:58:55.967: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jan  1 01:58:55.971: %PFREDUN-SP-4-AUTOBOOT: Disable autoboot for Supervisor in slot 6 *Jan  1 01:58:55.971: %PFREDUN-SP-6-ACTIVE: Sup in slot 6 is crashing due to RP failed to boot *Jan  1 01:58:55.999: SP: Failed to send heartbeat poison message *Jan  1 01:58:59.015: %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 01:58:59.015: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jan  1 01:58:59.015: %OIR-SP-6-CONSOLE: Changing console ownership to switch processor *** System received a Software forced crash *** signal= 0x17, code= 0x24, context= 0x43852654   PC = 0x4053efec, SP = 0x504f6da0, RA = 0x4054f308   Cause Reg = 0x00001020, Status Reg = 0x34008102 rommon 5 > monitor: command "" not found rommon 6 > rommon 6 > rommon 6 > dir disk0: Initializing ATA monitor library... Directory of disk0: 5080    103051324 -rw-     c7600s3223-advipservicesk9-mz.122-33.SRE12.bin 2      41594880  -rw-     c7600-fpd-pkg.122-33.SRE12.pkg 17660    106763004 -rw-     c7600s3223-advipservicesk9-mz.152-2.S.bin rommon 7 > boot disk0:c7600s3223-advipservicesk9-mz.122-33.SRE12.bin Initializing ATA monitor library... Self extracting the image... [OK] Self decompressing the image : ######################################################################################################## [OK]               Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013.            cisco Systems, Inc.            170 West Tasman Drive            San Jose, California 95134-1706 Cisco IOS Software, c7600s3223_sp Software (c7600s3223_sp-ADVIPSERVICESK9-M), Version 12.2(33)SRE12, RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Thu 12-Mar-15 00:26 by prod_rel_team MAC based EOBC installed Active crashed three times, disabling auto-boot and dropping to rommon %Software-forced reload  02:04:50 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DE2018 0x40DA2BFC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B8FE84, a1 : BE880000, a2 : 00004030, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 00000007, s3 : 00000000 s4 : 44490000, s5 : 43340000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849D8400, k1 : 05389200 gp : 42440CB0, sp : 511062E0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00007530, MDHI     : 00000000, BadVaddr : 00000000 DATA_START : 0x4214CB70 Cause 00000024 (Code 0x9): Breakpoint exception  02:04:50 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DE2018 0x40DA2BFC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B8FE84, a1 : BE880000, a2 : 00004030, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 00000007, s3 : 00000000 s4 : 44490000, s5 : 43340000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849D8400, k1 : 05389200 gp : 42440CB0, sp : 511062E0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00007530, MDHI     : 00000000, BadVaddr : 00000000 DATA_START : 0x4214CB70 Cause 00000024 (Code 0x9): Breakpoint exception File bootdisk:crashinfo_20000101-020450-UTC Device Error :No such device  02:04:50 UTC Sat Jan 1 2000: Breakpoint exception, CPU signal 23, PC = 0x4054EAC0 --------------------------------------------------------------------    Possible software fault. Upon recurrence, please collect    crashinfo, "show tech" and contact Cisco Technical Support. -------------------------------------------------------------------- -Traceback= 0x4054EAC0 0x4054D9A4 0x40DE2018 0x40DA2BFC $0 : 00000000, AT : 42440000, v0 : 00000000, v1 : 00000000 a0 : 50B8FE84, a1 : BE880000, a2 : 00004030, a3 : FFFFFFF7 t0 : 00000028, t1 : 3400FD01, t2 : 34008100, t3 : FFFF00FF t4 : 42440000, t5 : 00000000, t6 : 34008101, t7 : 34008100 s0 : 00000000, s1 : 421D0000, s2 : 00000007, s3 : 00000000 s4 : 44490000, s5 : 43340000, s6 : 00000000, s7 : 00000000 t8 : 00000000, t9 : 00000001, k0 : 849D8400, k1 : 05389200 gp : 42440CB0, sp : 511062E0, s8 : 00000000, ra : 4054D9A4 EPC  : 4054EAC0, ErrorEPC : 018BAEAE, SREG     : 3400FD03 MDLO : 00007530, MDHI     : 00000000, BadVaddr : 00000000 DATA_START : 0x4214CB70 Cause 00000024 (Code 0x9): Breakpoint exception -Traceback= 0x4054EAC0 0x4054D9A4 0x40DE2018 0x40DA2BFC ------------------ show chunk failures ------------------ ------------------ show redundancy states ------------------ File bootdisk:crashinfo_20000101-020450-UTC Device Error :No such device === Flushing messages (02:04:52 UTC Sat Jan 1 2000) === Buffered messages: Queued messages: *Jan  1 02:04:52.971: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 02:04:50.447: scp assert failure: queue != NULL: ../const/native/scp_const.c: 929 *Jan  1 02:04:50.447: -Traceback= 4077DE18 4077E4D0 *Jan  1 02:04:50.447: %SCHED-7-WATCH: Attempt to monitor uninitialized watched queue (address 0). -Process= "slcp process", ipl= 0, pid= 135 -Traceback= 405230F8 40CC2FFC 4055085C 40550A34 40527C1C *Jan  1 02:04:53.435: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jan  1 02:04:53.435: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jan  1 02:04:53.435: %OIR-6-CONSOLE: Changing console ownership to switch processor *** System received a Software forced crash *** signal= 0x17, code= 0x24, context= 0x4384ff14   PC = 0x4053efec, SP = 0x456fe0e0, RA = 0x4054f308   Cause Reg = 0x00001020, Status Reg = 0x34008102 rommon 8 > ... View more

https://sasipra.wordpress.com/2013/05/06/rep-resilience-ethernet-protocols-asymmetric-routing-and-hsrp/ ... View more

I need your help on very basic concept…. Could please help me to understand paragraph form “http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094afd.shtml#t8”                          Consequences of Asymmetric Routing Consider the case of the continuous ping of host B by host A. Remember that host A sends the echo packet to MSFC1, and host B sends the echo reply to MSFC2, which is in an asymmetric routing state. The only time that Switch 1 learns the source MAC of host B is when host B replies to an ARP request from MSFC1. This is because host B uses MSFC2 as its default gateway and does not send packets to MSFC1 and, consequently, Switch 1. Since the ARP timeout is four hours by default, Switch 1 ages the MAC address of host B after five minutes by default. Switch 2 ages host A after five minutes. As a result, Switch 1 must treat any packet with a destination MAC of host B as an unknown unicast. The switch floods the packet that comes from host A and is destined for host B out all ports. In addition, because there is no MAC address entry host B in Switch 1, there is no MLS entry as well. ” How could MAC Address can timeout if continuous ping of host B by host A is there? ... View more

     I have following Setup..... (FWSM in Cisco 7609 )      both FWSM interfaces are in security level 0 ....      following command is there too      "same-security-traffic permit inter-interface"       "route if_outside 0.0.0.0 0.0.0.0 10.1.90.5"      i am unable to understand which Firewall rule producing following Result:     From MSFC: ping 10.1.90.4 ---> OK ping 10.1.90.12 ----> OK ping 10.1.90.4 source loopback 0  ---> OK ping 10.1.90.12 source loopback 0  ---> NO Reply (Why?)  and message ASDM "No route to 202.92.25.254 from 10.1.90.12" then i add route:      "route if_inside 202.92.25.254 255.255.255.255 10.1.90.14"   So, ping 10.1.90.12 source loopback 0  ---> OK could any help to understand why default Route was not used.... ... View more