Cisco 6500 with sup720 booting to rommon

Please how can I solve this problem. This cisco 6500 boots to rommon mode, I can't see any error showing why its booting to rommon.

Here is the boot process:
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower memory for cache initialization
Clearing bss
Clearing autoboot state machine
melody_present_reg: 1st read w/ 0x5555
melody_present_reg: 2nd read w/ 0xaaaa, reversed: 0x5555
Bootdisk adapter is detected, enabling bootdisk access...
Reprogramming CS1 w/ Melody value...
Reading monitor variables from NVRAM
Reset reason for CPU board 0xffff , BaseBoard 0x281ffff, display 0x20000System Reset by Software.
Enabling interrupts
Initializing TLB
Initializing cache
Initializing required TLB entries
MOBILE dimm - rev 0.15
Initializing main memory
Sizing NVRAM
Initializing PCMCIA controller
Initializing USB2.0 controller
Exiting init
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
Autoboot: failed, BOOT string is empty
Autoboot executing command: "boot "
Initializing ATA monitor library...
string is bootdisk:s72033-ipbasek9-mz.122-33.SXJ2.bin
Loading image, please wait ...
Initializing ATA monitor library...
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80108580
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x05090C00
comp_size           : 0x05090C00
comp_checksum       : 0x98ECBE18
uncomp_checksum     : 0x98ECBE18
CZIP_MEM_BASE       : 0x80000000
_end       : 0x8010BA00
Self extracting the image...
IOS compressed src copy is     : 0x80108594
czip + IOS tar size is :0x00E01FA8
czip + IOS Tar image is now :0x80108794
cptr is now :0x8010BB00
IOS compressed dest copy is     : 0x8010BB00
[OK]
image_entry :0x80100000
image_entry :0x80100000
__start : 0x80100000
tar_avail_size is now :0x0428EA00
Tar image address is             : 0x80F0DB00
tar_size is           : 0x0428E600
cpu type                   : 0x00000019
uncomp_size                : 0x05090C00
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x80F0DB00
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8010BC1C
    dest      = 0x80100000
    bytes     = 0x00010000
Section Index = 0x00000001
    source    = 0x8011BC1C
    dest      = 0x80110000
    bytes     = 0x00000720
Section Index = 0x00000002
    source    = 0x8011C33C
    dest      = 0x80110720
    bytes     = 0x00000020
Section Index = 0x00000003
    source    = 0x8011C35C
    dest      = 0x80110740
    bytes     = 0x00DF1730
Section Index = 0x00000004
    source    = 0x80F0DA8C
    dest      = 0x80F01E70
    bytes     = 0x00000000
reg_v0: 0x00000000
reg_k0: 0x80F0DB00
reg_k1: 0x0428E600
tar_start: 0x00000000
tar_size: 0x00000000
Tar image address is             : 0x80F0DB00
tar size is :0x00B6130E
Tar magic : ustar Tar filename : C2LC memsize             : 0x10000000
Tar gid         : 035231Tar uncomp_size         : 0x00B6130E
Tar mtime         : 11672344432 Tar username          : ccaiTar comp_checksum       : 0x0000125F
Tar group name    : buildTar prefix    : tar_size  in czip         : 0x0428E600
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80110740
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x02B3E7F0
comp_size           : 0x00DF171C
comp_checksum       : 0xE917F280
uncomp_checksum     : 0xD094D890
Compressed IOS src copy is     : 0x80110754
tar_dest is :0x8BD69200
tar_size is :0x0428E600
Compressed IOS dest copy is     : 0x8AF77AE4
Tar src before IOS decompression is     : 0x80F0DB00
Tar dest before IOS decompression is     : 0x8BD69200
compressed IOS  src is     : 0x8AF77AE4
IOS uncompressed dest copy is     : 0x8013C160
Self decompressing the image : ############################################################################################################################################################################################################################## [OK]
e_shoff :
0x02B3E660
e_flags : 0x10001001
e_phnum :
0x00000001
Source elf_hdr->e_shnum = 0x0000000A
Setting up to copy ELF section 0x00000001
to image_info section 0x00000000
sh_name = 0x0000000B
sh_type = 0x00000001
sh_flags = 0x00000007
sh_addr = 0x80100000
sh_offset = 0x00000060
sh_size = 0x02640000
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000020
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000002
to image_info section 0x00000001
sh_name = 0x00000011
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82740000
sh_offset = 0x02640060
sh_size = 0x00373440
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000008
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000003
to image_info section 0x00000002
sh_name = 0x00000017
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82AB3440
sh_offset = 0x029B34A0
sh_size = 0x0003EEE4
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000004
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000004
to image_info section 0x00000003
sh_name = 0x00000024
sh_type = 0x00000001
sh_flags = 0x10000003
sh_addr = 0x82AF2324
sh_offset = 0x029F2384
sh_size = 0x0000423C
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000010
sh_entsize = 0x00000000
sh_type = 0x00000008
sh_flags = 0x10000003
sh_addr = 0x82AF6560
sh_offset = 0x029F65C0
sh_size = 0x00000940
sh_type = 0x00000008
sh_flags = 0x00000003
sh_addr = 0x82AF6EA0
sh_offset = 0x029F65C0
sh_size = 0x021FE100
tar file start = 0x84D02F50
cpu type                   : 0x00000019
uncomp_size                : 0x02B3E7F0
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x84D02F50
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8013C1C0
    dest      = 0x80100000
    bytes     = 0x02640000
Section Index = 0x00000001
    source    = 0x8277C1C0
    dest      = 0x8274CFB0
    bytes     = 0x00373440
Section Index = 0x00000002
    source    = 0x82AEF600
    dest      = 0x82AC03F0
    bytes     = 0x0003EEE4
Section Index = 0x00000003
    source    = 0x82B2E4E4
    dest      = 0x82AFF2D4
    bytes     = 0x0000423C
Section Index = 0x00000004
    source    = 0x8BD69200
    dest      = 0x84D02F50
    bytes     = 0x0428E600
data_size  in czip         : 0x00001000
bss end of IOS is         : 0x84D01F50
              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, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXJ2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 15-Dec-11 01:29 by prod_rel_team
Image text-base: 0x4010132C, data-base: 0x4274CFB0
Active crashed three times, disabling auto-boot and dropping to rommon
Firmware compiled 15-Nov-11 14:23 by integ Build [100]
*Jan  1 02:27:12.643: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
*Jan  1 02:27:13.459: %PFREDUN-4-SUP_FORCE_TO_ROMMON: Supervisor forced to rommon with reason: Active crashed three times in a row
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
rommon 1 >

Similar Messages

  • QoS Packets not matching on 6500 with SUP720-10GE and SU2T

    Hi,
    I do not see packets matching in policy. 
    output below:
    Switch#sh policy-map interface vlan 2232
     Vlan2232 
      Service-policy input: HARDPHONE-VVLAN
        Class-map: VOICETRAFFIC (match-all)
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: access-group name VOICETRAFFIC
        Class-map: VOICESIGNALING (match-all)
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: access-group name VOICESIGNALING
        Class-map: class-default (match-any)
          0 packets, 0 bytes
          5 minute offered rate 0000 bps, drop rate 0000 bps
          Match: any 
            0 packets, 0 bytes
            5 minute rate 0 bps
    I also not find packets matching ACL:
    switch#sh access-lists
    Extended IP access list VIDEOTRAFFIC
        10 permit udp any any range 16384 32767
    Extended IP access list VOICESIGNALING
        10 permit tcp any 10.128.0.0 0.3.255.255 range 2000 2002
        20 permit tcp any 10.128.0.0 0.3.255.255 eq 5060
        30 permit udp any 10.128.0.0 0.3.255.255 eq 5060
        40 permit tcp any 172.20.10.0 0.0.1.255 range 2000 2002
        50 permit tcp any 172.20.10.0 0.0.1.255 eq 5060
        60 permit udp any 172.20.10.0 0.0.1.255 eq 5060
    Extended IP access list VOICETRAFFIC
        10 permit udp 10.128.0.0 0.63.255.255 10.128.0.0 0.63.255.255 range 16384 32767
    I checked policies, they looks applied correctly.
    On SUP-720-10GE, I modified ACL to 'permit udp any any' but not found any matching packets. There are plenty of IP phones connected directly to this switch belongs to voice VLAN. I applied VLAN based QoS under voice VLAN and other VLANs too. 
    I observed different thing on SUP 2T. I saw packets matching ACL statement 'permit udp any any' but when I took off this line, ACL was not showing packets matching. 
    OUTPUT of IP phones connected to switch:
    switch#sh cdp neighbors | in SEP
    SEP0008308A5D7B  Gig 13/38         143             H P M  IP Phone  Port 1
    SEP0008308A5DE0  Gig 10/1          121             H P M  IP Phone  Port 1
    SEP0023049C6348  Gig 3/42          152             H P M  IP Phone  Port 1
    SEP0021A02D64D4  Gig 9/28          120             H P M  IP Phone  Port 1
    SEP1C6A7AE0588E  Gig 3/9           127             H P M  IP Phone  Port 1
    SEP00229059969E  Gig 12/48         166             H P M  IP Phone  Port 1
    SEP0008308AF26F  Gig 2/7           161             H P M  IP Phone  Port 1
    SEP00235EB7BE0E  Gig 4/2           154             H P M  IP Phone  Port 1
    SEP00229059BE5A  Gig 6/37          158             H P M  IP Phone  Port 1
    SEP1CAA07115CF3  Gig 12/29         148             H P M  IP Phone  Port 1
    SEP00235EB7884F  Gig 9/3           156             H P M  IP Phone  Port 1
    SEP0008308B03FB  Gig 2/30          178             H P M  IP Phone  Port 1
    SEP006440B42CD3  Gig 3/45          132             H P M  IP Phone  Port 1
    SEP0022905991C9  Gig 11/4          145             H P M  IP Phone  Port 1
    SEP0008308A5E6C  Gig 6/36          124             H P M  IP Phone  Port 1
    SEP006440B427CA  Gig 13/31         170             H P M  IP Phone  Port 1
    SEP006440B425FF  Gig 3/19          168             H P M  IP Phone  Port 1
    SEP0008308A7AD7  Gig 2/3           159             H P M  IP Phone  Port 1
    SEP0008308A3EB2  Gig 10/4          132             H P M  IP Phone  Port 1
    SEP002414B45A0E  Gig 10/28         170             H P M  IP Phone  Port 1
    SEP04C5A4B19C8B  Gig 2/15          162             H P M  IP Phone  Port 1
    SEP006440B43DE6  Gig 9/48          162             H P M  IP Phone  Port 1
    SEP006440B42B0D  Gig 9/23          179             H P M  IP Phone  Port 1
    Could anyone please help, how to make sure that packets are hitting correct ACL and policy on 6500 with SUP720-10GE and SUP2T.
    Thanks,
    Pruthvi

    Please note that 6500 is used as L2 switch only and SVI are used for applying policies only. 
    Configuration below:
    class-map match-all VOICESIGNALING
      match access-group name VOICESIGNALING
    class-map match-all VOICETRAFFIC
      match access-group name VOICETRAFFIC
    class-map match-all VIDEOTRAFFIC
      match access-group name VIDEOTRAFFIC
    policy-map HARDPHONE-VVLAN
      class VOICETRAFFIC
         police flow mask src-only 128000 8000 conform-action set-dscp-transmit ef exceed-action drop
      class VOICESIGNALING
         police flow mask src-only 32000 8000 conform-action set-dscp-transmit cs3 exceed-action policed-dscp-transmit
      class class-default
         police flow mask src-only 32000 8000 conform-action set-dscp-transmit default exceed-action policed-dscp-transmit
    policy-map STUDENT-DVLAN
      class class-default
         police flow mask src-only 25000000 1562500 conform-action set-dscp-transmit default exceed-action policed-dscp-transmit
    policy-map STAFF-DVLAN
      class VOICESIGNALING
         police flow mask src-only 32000 8000 conform-action set-dscp-transmit cs3 exceed-action policed-dscp-transmit
      class VOICETRAFFIC
         police flow mask src-only 128000 8000 conform-action set-dscp-transmit ef exceed-action drop
      class VIDEOTRAFFIC
         police flow mask src-only 2000000 150000 conform-action set-dscp-transmit ef exceed-action drop
      class class-default
         police flow mask src-only 50000000 1000000 conform-action set-dscp-transmit ef exceed-action drop
    ip access-list extended VOICESIGNALING
     remark Skinny and SIP protocols From Phones to Voice Core Infrastructure
     permit tcp any 10.128.0.0 0.3.255.255 range 2000 2002
     permit tcp any 10.128.0.0 0.3.255.255 eq 5060
     permit udp any 10.128.0.0 0.3.255.255 eq 5060
     permit tcp any 172.20.10.0 0.0.1.255 range 2000 2002
     permit tcp any 172.20.10.0 0.0.1.255 eq 5060
     permit udp any 172.20.10.0 0.0.1.255 eq 5060
    ip access-list extended VOICETRAFFIC
     permit udp any any dscp ef
     permit udp 10.128.0.0 0.63.255.255 10.128.0.0 0.63.255.255
     permit udp any any range 16384 32767 dscp ef
    ip access-list extended VOICESIGNALING
     remark Skinny and SIP protocols From Phones to Voice Core Infrastructure 
     permit tcp any 10.128.0.0 0.3.255.255 range 2000 2002
     permit tcp any 10.128.0.0 0.3.255.255 eq 5060
     permit udp any 10.128.0.0 0.3.255.255 eq 5060
     permit tcp any 172.20.10.0 0.0.1.255 range 2000 2002
     permit tcp any 172.20.10.0 0.0.1.255 eq 5060
     permit udp any 172.20.10.0 0.0.1.255 eq 5060
    ip access-list extended VIDEOTRAFFIC
     permit udp any any range 16384 32767 dscp ef
    interface Vlan104
     description PolicyOnlyInt
     no ip address
     service-policy input STAFF-DVLAN
    interface Vlan105
     description PolicyOnlyInt
     no ip address
     service-policy input STAFF-DVLAN
    interface Vlan573
     description PolicyOnlyInt
     no ip address
     service-policy input PUBLIC-DVLAN
    interface Vlan604
     description PolicyOnlyInt
     no ip address
     service-policy input PUBLIC-DVLAN
    interface Vlan654
     description PolicyOnlyInt
     no ip address
     service-policy input STUDENT-DVLAN
    interface Vlan674
     description PolicyOnlyInt
     no ip address
     service-policy input PUBLIC-DVLAN
    interface Vlan807
     ip address 172.18.128.5 255.255.255.0
    interface Vlan860
     description PolicyOnlyInt
     no ip address
     service-policy input PUBLIC-DVLAN
    interface Vlan2016
     description PolicyOnlyInt
     no ip address
     service-policy input HARDPHONE-VVLAN
    interface Vlan3124
     description PolicyOnlyInt
     no ip address
     shutdown
     service-policy input HARDPHONE-VVLAN
    switch#sh access-lists
    Extended IP access list VOICESIGNALING
        10 permit tcp any 10.128.0.0 0.3.255.255 range 2000 2002
        20 permit tcp any 10.128.0.0 0.3.255.255 eq 5060
        30 permit udp any 10.128.0.0 0.3.255.255 eq 5060
        40 permit tcp any 172.20.10.0 0.0.1.255 range 2000 2002
        50 permit tcp any 172.20.10.0 0.0.1.255 eq 5060
        60 permit udp any 172.20.10.0 0.0.1.255 eq 5060
    Extended IP access list VOICETRAFFIC
        10 permit udp any any dscp ef <----- not showing any match
        11 permit udp 10.128.0.0 0.63.255.255 10.128.0.0 0.63.255.255 <----not shwoing any match
        12 permit udp any any range 16384 32767 dscp ef<----not shwoing any match
    If I user "permit udp any any ", acl is showing match.
    switch#sh access-lists
    Extended IP access list VOICETRAFFIC
        10 permit udp any any dscp ef
        11 permit udp 10.128.0.0 0.63.255.255 10.128.0.0 0.63.255.255
        12 permit udp any any range 16384 32767 dscp ef
        13 permit udp any any (527055 matches)

  • Cisco 6500 with SUP 720 - Invalid boot Image

    Diagnostic sanity check on the 6500 reports Invalid boot image "bootdisk:<output omitted>
    The boot statement on the 6500 is :-
    boot system bootdisk:<filename.bin> and the 6500 boots fine.
    Please advise.
    Thank You.

    Hi ,
    I have found bug which is internally found by cisco.The bug is CSCsc98471 and following are details of bug .
    The command "show diagnostic sanity" checks amongst other things, if the current bootstring is matching pointing to an existing file.
    Since ION bootstring format has been extended (assuming an installed image) this check fails although the bootstring is correct.
    Can be easily reproduced by entering the "show diagnostic sanity" command.
    6500-6#show diagnostic sanity
    Pinging default gateway 172.26.197.33
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 172.26.197.33, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
    Could not verify boot image "sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm," specified in the boot string.
    6500-6#show bootvar
    BOOT variable = sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm,12;
    6500-6#dir sup-bootflash:/newsys/s72033/base/
    Directory of sup-bootdisk:/newsys/s72033/base/
    84 -rwx 1375696 Jan 5 2006 20:51:24 -08:00 imf.tar
    85 -rwx 12873200 Jan 5 2006 20:51:22 -08:00 s72033-adventerprisek9_wan_dbg-vm
    It is found in 12.2(18.09.20)SX3.39.
    *** open a TAC case so that the same bug is fixed in 12.2(18)SXF4.
    Hope it helps you.Plz rate it.
    Thanks,
    satish

  • When Booting Cisco 6500 its directly going to Rommon

    Hi All, When we reboot or Hrad boot the Cisco 6509 its directly going to rommon again to make the switch boot in IOS each and everytime we need to give the command boot, we have checked and found that flash is working fine and even the boot sequence is configured properly.
    what could cause this problem ?

    Check your boot statement , if this is a native box it should be "boot system flash sup-bootflash: or "boot system flash disk0: . Anything else will cause it to go to rommon if the config register is correct. It has to be pointed at the supervisor bootflash or disk0 and that is where the image should be located because that is where the initial boot starts , it boots the supervisor then hands it over to the mscf to be loaded.

  • Sup720 booting into rommon mode

    new sup720 drops into rommon mode. config reg is 2102 and boot system command points to right image located in sup-bootflash:

    You might need to upgrade your ROMMON. We did with our brand new Sup720's. Below is the procedure we use. Please pardon the formatting. If you see "invalid ..." after the "show rom slot n sp" you need to load ROMMON code (available from Cisco's downloads). Good luck.
    ROM Upgrade (650x)
    1 sh rom slot 5 sp Display current ROM settings
    2 copy tftp:c6ksup3-rm2.srec.8.4.2 sup-bootflash:c6ksup3-rm2.srec.8.4.2 TFTP the file to the 650x
    3 upgrade rom slot 5 sp pref region[1 | 2] Command to switch regions to boot ROMMON from. Upgrade that too or leave at old version.
    4 upgr rom slot 5 sp file sup-bootflash:c6ksup3-rm2.srec.8.4.2 Upgrades current preferred ROMMON region
    5 repeat step 3 for other region After successfully upgrading to the new version do the other one too.
    6 reload Reload (once for each ROMMON region) to test
    rommon invalidate F1 Command to invalidate a ROMMON region

  • Cisco 6509E with Sup720 Loadsharing

    Cisco 6509-E with two SUP720 in my environment I would like to achieve
    Active / Active with load sharing between the two SUP720, can this be implemented, please advice on configuration.

    Hi
    AFAIK, When you are using 2 MSFCs only one of them would be active and the other would compulsorily in standby mode. So I dont think you would be able to configure active/active configuration.
    Refer the following link for detailed instructions on configuring Redundancy using Dual MSFCs:
    http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a008019f02f.html
    Hope this helps.
    Regards,
    AbhisheK
    Please rate all posts!!!

  • 6500 with SUP720: Output Policing

    Can anybody tell me which Bytes from the L2 Header are included in the policing calculation if i police the rate of a ethernet interface (with a policy-map)? i.e. Preamble, dot1q, mac......
    Thanks for any feedback!

    Hi there,
    funny enough the info is found where one wouldn´t really expect it:
    What Bytes Are Counted by IP to ATM CoS Queueing?
    http://www.cisco.com/en/US/tech/tk39/tk824/technologies_tech_note09186a00800942f5.shtml
    So the answer would be: no preamble and no CRC is counted. It is the same byte counter implemented as with show interface.
    Hope this helps
    Martin

  • Cisco 6500 power supply and module (hot-swappable?)

    Hi everyone!
    We have currently a Cisco 6500 with 2 power supply of 3000w. We want to replace these PS for 2 new ones, which have higher wattage: 6000w. 
    Can we replace them without needing to turn the 6500 off?. I mean, What happens if we insert a 6000w PS and the switch is working with one 3000w PS?
    Is it possible to do this replacement "on hot"?
    And second, we also have a ws-x6708-10g-3c module. Can we insert this module "on hot"? Without needing to turn the Catalyst 6500 off? 
    Thanks a lot! and looking forward to an answer.

    Depends on your setup the table should be able to help:
    http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/pwr_envr.html#wp1020384
    Configuration Change
    Effect
    Redundant to nonredundant
    •System log and syslog messages are generated.
    •System power is increased to the combined power capability of both power supplies.
    •Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
    Nonredundant to redundant (both power supplies must be of equal wattage)
    •System log and syslog messages are generated.
    •System power is decreased to the power capability of one supply.
    •If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in theshow power oper state field.
    Equal wattage power supply is inserted with redundancy enabled
    •System log and syslog messages are generated.
    •System power equals the power capability of one supply.
    •No change in module status because the power capability is unchanged.
    Equal wattage power supply is inserted with redundancy disabled
    •System log and syslog messages are generated.
    •System power is increased to the combined power capability of both power supplies.
    •Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
    Higher or lower wattage power supply is inserted with redundancy enabled
    •System log and syslog messages are generated.
    •The system does not allow you to operate a power supply of different wattage even if the wattage is higher than the installed supply. The inserted supply shuts down.
    Higher or lower wattage power supply is inserted with redundancy disabled
    •System log and syslog messages are generated.
    •System power is increased to the combined power capability of both power supplies.
    •Modules marked power-deny in the show power oper state field are brought up if there is sufficient power.
    Power supply is removed with redundancy enabled
    •System log and syslog messages are generated.
    •No change in module status because the power capability is unchanged.
    Power supply is removed with redundancy disabled
    •System log and syslog messages are generated.
    •System power is decreased to the power capability of one supply.
    •If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in theshow power oper state field.
    System is booted with power supplies of different wattage installed and redundancy enabled
    •System log and syslog messages are generated.
    •The system does not allow you to have power supplies of different wattage installed in a redundant configuration. The lower wattage supply shuts down.
    System is booted with power supplies of equal or different wattage installed and redundancy disabled
    •System log and syslog messages are generated.
    •System power equals the combined power capability of both power supplies.
    •The system powers up as many modules as the combined capacity allows.

  • Hi, I have a Catalyst 6500 with X6K-SUP2-2ge, the IOS and bootlader image been wiped out, it starts in ROMmon SP mod end can't switch to RP to start download the IOS using Xmodem, though it shouldn't work in ROMmon SP omde but the xmodem is not gving the

    Hi, I have a Catalyst 6500 with X6K-SUP2-2ge, the IOS and bootlader image been wiped out, it starts in ROMmon SP modw and I can't switch to RP to start download the IOS using Xmodem, though Xmodem shouldn't work in ROMmon SP mode but the it's not gving the
    not executable message, the slot0: and disk0: are not accessable can't see the files inside, when I try the dir slot0: or dir disk0: it says it can't be opened and when I try to boot from them there's noting as well, what can I do to load an IOS image to the booflash: or slot0: ,each time I load the image using Xmodem at the end it gives me *** System received a Software forced crash ***
    signal=0x17, code=0x5, context=0x0
    When I run the command:
    rommom1> boot bootflash:
    boot: cannot determine first file name on deice "bootflash:"
    rommon2> boot slot0:
    boot: cannot open "slot0:"
    boot: cannot dtermine first file name on device "slot0:"
    BTW  System Bootstrap, version 7.1
    I''m looking to format the PCMCIA using a PC and format it to FAT16 and copy the boot image into it and then try to load from the PCMCIA afterward if it works I'll format it using the Supervisor engine 2.
    Any one have another new idea I can use, thanks in advance

    This is a potentially complex issue.
    Is this SUP configured to run as IOS native or CatOS Hybrid?
    While in ROMMON can you do the 'dev' command and see whad drives are recognized. Then 'dir' the drives that the SUP recognizes.
    Can you provide the screen captures as it boots?
    You would be bette served by hacing a TAC case.

  • Cisco 6500 Sup2 IOS with SLB support

    Hello
    A have two questions about SLB funcionality on Cisco 6500 SUP2/MSFC2
    1) Is IP LAN ONLY ios support SLB ? If yes, does it have any restrictions ?
    2) How heavy IOS SLB for processor ? (i mean in dispatched mode).

    Are sup-bootflash: and sup-bootdisk: the same thing ?
    No, they are not.   sup-bootflash: is located inside but the sup-bootdisk: is located OUTSIDE and is physically accessible.  If you look at the line card, you'll see a CF slot marked "Disk0:" or "Slot0".  This is the sup-bootdisk:.  It is also known as "disk0:".  Confusing, I know. 
    Can I make use of the disk0 of both chassis to perform ios upgrade ?
    Of course you can.  I perform VSS upgrade just using one of the disk0: and push the IOS from the disk0: to the two supervisor cards.  
    By setting the boot path to disk0
    You can too.  The sup-bootflash: and the sup-bootdisk:/disk0: are the same physical format.  
    A word of caution:  I cannot stop reiterating the importance of checking the MD5 hash value of the IOS file in the sup-bootdisk: or sup-bootflash: BEFORE rebooting the chassis for an IOS upgrade.  Make sure the MD5 hash value match exactly to the MD5 hash value found in the Cisco website.  Once they are match, check the boot variable string, the config-registry and you're off to the next step.

  • VRF-Lite with 6500 w/ Sup720

    I am working with a customer who would like to utilize path isolation in their network using VRF-Lite. I am currently debating between the use of GRE tunnels vs. VLANs between 3 core switches they currently have in place today. This is going to be overlay network on top of what they currently have. The core is all L2 today with 802.1q trunks between each of 3 cores in a ring topology. Closets are single homed into the core throughout.
    My question is regarding GRE vs. VLANs. Currently, we are looking at having to deploy 12 VRFs to support 12 seperate network types they would like to isolate. The Access layer switches will trunk to the cores where the core will apply VRFs to specific VLANs based on their role.
    Which is going to be a more scalable solution from a performance and adminstration standpoint. GRE, VLANs, or MPLS?
    Currently the GRE implementation is going to require that we configure many loopbacks and tunnels on each core in order to get the VRFs talking to each other in each core. The VLAN approach will require 24 VLANs per core (assuming we would go with PTP vs Multipoint for routing inside the VRF).
    Any thoughts on which way to proceed? From what i have read GRE is more appropriate when you have multiple hops between VRF tables, which in this case we do not. I am just concerned with loopbacks,tunnels, and then routing on top of that the GRE solution will lack scalability as they add more VRFs. A PTP VLAN will pose a similar problem without the need for loopbacks which should simplify the solution.
    Can we use MPLS here and just do PE to PE MPLS and still get the VRF segmentation we need between cores?
    I would like eventually migrate the entire core to L3 completely but today we are stuck with having to support legacy networks (DEC/LAT/SNA) and have to keep some L2 in place.
    Whats the best approach here?

    Shine,
    I actually ended up with basically the same design you are talking about here except that I ended up adding a couple 6500 +FWSM and NAC L3/L2 CAM/CAS into the mix.
    Here is the high level overview
    1. Every Closet had a minimum of 6 VLANs - unique to the stack or closet switch - Subnets were created for each VLAN as well - no spanning of L2 VLANs across switch stacks.
    2. VLANs were assigned for - Voice, Data, LWAPP VLAN, Guest/Unauthorized, Switch/Device Management, and at least 1 special purpose VLAN - (Lab, Building Controls, Security, etc).
    3. Then we trunked all the VLANs back to 1 of 3 cores - 6509s with Sup-720s
    4. Each Core 6509 was configured for each L2 VLAN with a L3 SVI (The VLANs configured here were not configured on any other cores - we didn't have available fiber runs to do any type of redundant pathing across multiple cores so it wasn't valid in this design to configure VLAN SVIs on more than one core).
    5. Each L3 SVI was assigned to the appropriate VRF based on use - Voice, Data, LWAPP, etc
    6. Spanning-Tree Roots for all VLANs trunked to a core were specific to that core - they did not trunk between Cores - no loops
    7. Each Core was connected via a L2 Trunk that carried Point to Point VLANs for VRFs traffic - We had an EIGRP AS assigned to each VRF on the link - so we had 6 VRFs and 6 EIGRP AS per trunk.
    8. This design occurred on each core x2 as it connected to the other cores in a triangle core fashion.
    9. Each of the Cores had a trunk to to 6500 with a FWSM configured - VRF/L3 PTP VLAN design continued here as well
    10. The 6500+FWSM was configured with multiple SVIs and VRFs - we had to issue mult-vlan mode on the FWSM to get it to work.
    11. Layer 2 NAC was configured with VLAN translation coming into the Core 6500/FWSM for Wireless in L2 InBand Mode - the L3 SVIs were configured on the clean side of the NAC CAM so traffic was pulled through the CAM from from the dirty side - where the controller mapped host SSIDs to appropriate VLANs. We only had to configure a couple host VLANs here - Guest and Private so this was not much of an issue - Private was NAC enabled, Guest VLAN/SVI was mapped to a DMZ on the firewall
    12. For Layer 3 NAC we justed used an out of band CAM configurations with ACLs on the Unauthorized VLAN
    It worked like a charm.
    If I had to do it all over again I would go with MPLS/BGP for more scalability. Configuring trunks between the cores and then having the mulitple EIGRP AS/PTP VLANs works well in networks this small but it doesn't scale indefinately. It sounds like your network is quite large. I would look into MPLS between a set of at least 3-4 Core PE/CE devices. Do you plan on building a pure MPLS core for tagged switched traffic only? Is your campus and link make up significant enough to benefit from such a flexible design?

  • How to count/determine downtime of Cisco 6500 switch?

    Hello,
    I work with cisco 6500 switches. now we need to evaluate the down time of all switces. now we using cacti to query system information to switches using SNMP, but some times cacti didnt get the data because of high cpu in switch so the switch stop di SNMP service. because of that, the data in Cacti not valid to determine our switch Downtime.
    Is there any tools or ather way to monitor Cisco switch downtime??
    Thanks a lot. 

    just like a reminding system. it can be send an email or some message.
    EEM can be configured to send someone an email when some kind of "event" is triggered, such as an uplink goes DOWN/UP.  
    However, the chassis can't send an email if it's down but can be configured to send out an email when the supervisor card boots up.  

  • AIR-LAP1142 Booting to Rommon

    I have a customer that has an air-lap1142.  He says that it boot to Rommon, and he has to issue the boot command to get it to boot.  What is the rommon command to have the ap boot to the image automatically?

    Here is a support document with instructions that will help you recover the AP:
    https://supportforums.cisco.com/docs/DOC-14636
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • Cisco catalyst 4506-e boot error

    Rommon signature verification PASSED for golden image
    Rommon signature verification PASSED for primary image
    FPGA signature verification PASSED for primary image
     * Welcome to Rom Monitor for   WS-X45-SUP7-E System.       *
     * Copyright (c) 2008-2011 by Cisco Systems, Inc.           *
     * All rights reserved.                                     *
     Primary Rom Monitor Version 15.0(1r)SG5
     CPU Rev: 2.2, Board Rev: 10, Board Type: 101, CPLD Moka Rev: 7.0x3718.0xb565
     Chassis: WS-C4506-E
    Got Mac Address: c0:67:af:40:24:c2
     MAC Address  : c0-67-af-40-24-c2
     IP Address   : 14.18.2.234
     Netmask      : 255.255.255.0
     Gateway      : 14.18.2.21
     TftpServer   : Not set.
     Peer supervisor not detected or is not running IOS
     Supervisor uplinks and all linecards have been reset
     ***** The system will autoboot in 5 seconds *****
     Type control-C to prevent autobooting.
     ******** The system will autoboot now ********
     config-register = 0x2101
     Autobooting using the first file from bootflash.....
    loading image
    Checking digital signature
    bootflash:/cat4500e-universal.SPA.03.05.02.E.152-1.E2.bin: Digitally Signed Release Software with key version A
    Rommon reg: 0x00004F80
    Reset2Reg: 0x00000F00
    Image load status: 0x00000000
    Snowtrooper 155 controller 0x044DDBD2..0x04688FA7 Size:0x0041DCD4 Program Done!
    [   57.324367] pci 0000:00:00.0: ignoring class b20 (doesn't match header type 01)
    Starting System Services
    Calculating module dependencies ...
    Loading rtc-ds1307
    RTNETLINK answers: Invalid argument
    No Mountpoints DefinedNov 13 09:35:24 %IOSXE-3-PLATFORM: process sshd[4211]: error: Bind to port 22 on :: failed: Address already in use.
    diagsk10-post version 5.1.4.0
    prod: WS-X45-SUP7-E part: 73-14393-02 serial: CAT1837L75P
    Power-on-self-test for Module 1: WS-X45-SUP7-E
    CPU Subsystem Tests ...
     seeprom: Pass
    Traffic: L3 Loopback ...
     Test Results: Pass
    Traffic: L2 Loopback ...
    post timeout
    A Critical job [post] exited abnormally! Reloading the supervisor
    Killed by signal [TERM]
    Loading virtuclock as vuclock
    Loading gsbu64atomic as gdb64atomic
    Loading isp1362_hcd_k10
    /dev/fd/13: line 273: /sys/devices/system/edac/mc/edac_mc_log_ce: No such file or directory
    Starting IOS Services
    AIPC Module Loaded...
    cat4k-watchdog[6250]: Watchdog daemon initialized on 2 CPU(s)
    cat4k-watchdog[6250]: Watchdog daemon started.
    Dumping all the logs to /root/reload.20141113..Please be patient
    All logs dumped
    sysmgr: <<%SYSMGR-2-SERVICE_CRASHED>> Service "System Manager (parser)" (PID 6820) hasn't caught signal 15 (no core).
    /bin/kill: 8178: No such process
    /bin/kill: 8179: No such process
    /bin/kill: 8197: No such process
    /bin/kill: 8198: No such process
    /etc/rc6.d/S01reboot: line 198: umount_cisco_filesystems: command not found
    Please stand by while rebooting the system...
    [  266.041680] Restarting system.
    Rommon signature verification PASSED for golden image
    Rommon signature verification PASSED for primary image
    FPGA signature verification PASSED for primary image
     * Welcome to Rom Monitor for   WS-X45-SUP7-E System.       *
     * Copyright (c) 2008-2011 by Cisco Systems, Inc.           *
     * All rights reserved.                                     *
     Primary Rom Monitor Version 15.0(1r)SG5
     CPU Rev: 2.2, Board Rev: 10, Board Type: 101, CPLD Moka Rev: 7.0x3718.0xb565
     Chassis: WS-C4506-E
    Got Mac Address: c0:67:af:40:24:c2
     MAC Address  : c0-67-af-40-24-c2
     IP Address   : 14.18.2.234
     Netmask      : 255.255.255.0
     Gateway      : 14.18.2.21
     TftpServer   : Not set.
     Peer supervisor not detected or is not running IOS
     Supervisor uplinks and all linecards have been reset
     ***** The system will autoboot in 5 seconds *****
     Type control-C to prevent autobooting.
     ******** The system will autoboot now ********
     config-register = 0x2101
     Autobooting using the first file from bootflash.....
    loading image
    Version: cat4500e-universal.SPA.03.05.02.E.152-1.E2.bin
    Any help PLZ

    config-register = 0x2101
    Autobooting using the first file from bootflash.....
    You need to provide more information.  What are you trying to do?  How many IOS file(s) do you have in the bootflash? 
    sysmgr: <<%SYSMGR-2-SERVICE_CRASHED>> Service "System Manager (parser)" (PID 6820) hasn't caught signal 15 (no core).
    Break into the auto-boot process and post the output to the command "dir bootflash:".

  • IP TCP intercept cisco 6500

    Hi,
    does anyone has experience with ip tcp intercept configuration on cisco 6500 for protecting network against TCP SYN flooding.
    Which mode is recommended to configure (intercept or watch) and how can affect CPU on cisco 6500?
    Any infos regarding that would be much appreciated.
    Thank you
    Salja

    Hey Salja,
    In Sup720 for TCP Intercept the support is as follows:
    Watch mode: Initial TCP packets (SYN, SYN-ACK and ACK of SYN-ACK) and terminating TCP packets (FIN, RST) of a TCP flow is sent to RP for processing in SW. All other TCP packets of the flow are handled in HW using netflow (if TCP packets come in before the netflow entry is created it will get punted to SW). Note that the rate of netflow entry creation is limited and if new TCP connections come in at a rate faster than the rate at which netflow entries can be created in HW there will be large number of packets hitting the CPU.
    Intercept Mode: For Intercept mode without timeout the behavior is similar to Watch mode mentioned above. Intercept mode with timeout all packets of a TCP flow is handled in SW by the RP.
    So its not advised to use TCP intercept on 6500 as it may degrade box performance. I would suggest using firewall for this feature.
    HTH.
    Regards,
    RS.

Maybe you are looking for