Cisco 6500 ACE ARP / mac-stick enable

Hi,
We recently found two entries on our ACE logs constantly complaining about ip/arp collisions(%ACE-4-405001), and on further investigation we saw that these IP's related to the mac addresses no longer existed anywhere in our network.
1              5              2014-06-07 06:00:03         2014-06-08 02:00:04         WARNING            LOCAL4 ACE-CORE1:         %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy on interface vlan5
2              4              2014-06-07 10:59:48         2014-06-08 02:59:49         WARNING            LOCAL4 ACE-CORE1:         %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy  on interface vlan5
3              2              2014-06-07 06:59:48         2014-06-07 22:59:48         WARNING            LOCAL4 ACE-CORE1:         %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy  on interface vlan5
4              1              2014-06-07 10:00:04         2014-06-07 10:00:04         WARNING            LOCAL4 ACE-CORE1:         %ACE-4-405001: Received ARP RESPONSE collision from x.x.x.x yy.yy.yy.yy.yy.yy  on interface vlan5
I exhausted the search for these two "ghost" ip's in our network, and finally remembered that our ACE configuration had a context we removed a few months back.
From this context we had the following configured on the interface:
interface vlan 18
  description CHAT-DMZ-FW
  bridge-group 1
  mac-sticky enable
  no shutdown
I want to confirm with you guys if anyone has seen something similar, or knows of this, but I believe the IP's learned mac addresses got "sticky" on the ACE admin context due to the mac-sticky enable command, even after we removed the context these entries persisted?
I finally used this command to remove the "ghost" IP's related to the mac addresses:
clear arp x.x.x.x no-refresh

Dear Friend,
Also confirm if the IP addresses were reachable though  and as far as the Ghost synonym is referred, I can say there can be virtual mac-addresses, Ip addresses therein the network.
Thats it !
Parvesh

Similar Messages

  • Cisco wireless and Apple Mac woes

    Hello all,
    I've been working with Cisco wireless and WLC's for a couple of years now but the recent onslaught of Apple Mac's is giving me heart burn.  I've seen this at numerous sites now and need to throw it to eht community for guidance.
    Basically we have had a number of instances where the Macs just fall off the wifi.  Sometimes it's when they wake from sleep and other times when roaming between AP's (1131s with same SSID's).  Our standard install is WPA2 and per ap local authentication.  PC's work fine and never an issue.
    We have completed a survey with a spectrum analyser and no RF interefence is present nor errors on the radio interface.
    Questions:
    - Is there a preferred Cisco config/setup for Mac's to work reliably?  I've heard loads of rumors but nothing concrete and nor can I find anything specific.
    - Should I be setting up WDS in case there is an authenticating issue.
    - For those who are Mac gurus and happen to be reading. What Mac options we should look at?
    This has all come to a head because the clients IT company who recommended the Macs (different from us doing the network infrastructure) are insisting that the problem is Cisco incompatibility and that we should rip out the Cisco kit and install airports (what tha!!!).
    Thanks in advance for any pointers.
    For those who like a config here it is .... Vanilla stuff really
    Building configuration...
    Current configuration : 2236 bytes
    version 12.4
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname AP4
    no logging console
    enable secret xxxxxxxxxxxxxxxxx
    no aaa new-model
    dot11 syslog
    dot11 ssid Home
       vlan 1
       authentication open
       authentication key-management wpa
       guest-mode
       mbssid guest-mode
       wpa-psk ascii xxxxxxxxxxxx
    dot11 ssid avnet
       vlan 2
       authentication open
       authentication key-management wpa
       mbssid guest-mode
       wpa-psk ascii xxxxxxxxxxxxxxxx
    username abcd password 1234
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    encryption vlan 1 mode ciphers tkip
    encryption vlan 2 mode ciphers tkip
    ssid Home
    mbssid
    speed  basic-1.0 basic-2.0 5.5 11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
    channel 2412
    station-role root
    interface Dot11Radio0.1
    encapsulation dot1Q 1 native
    no ip route-cache
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface Dot11Radio0.2
    encapsulation dot1Q 2
    no ip route-cache
    bridge-group 2
    bridge-group 2 subscriber-loop-control
    bridge-group 2 block-unknown-source
    no bridge-group 2 source-learning
    no bridge-group 2 unicast-flooding
    bridge-group 2 spanning-disabled
    interface FastEthernet0
    no ip address
    no ip route-cache
    duplex auto
    speed auto
    hold-queue 80 in
    interface FastEthernet0.1
    encapsulation dot1Q 1 native
    no ip route-cache
    bridge-group 1
    no bridge-group 1 source-learning
    bridge-group 1 spanning-disabled
    interface FastEthernet0.2
    encapsulation dot1Q 2
    no ip route-cache
    bridge-group 2
    no bridge-group 2 source-learning
    bridge-group 2 spanning-disabled
    interface BVI1
    ip address 192.168.10.54 255.255.255.0
    no ip route-cache
    ip default-gateway 192.168.10.1
    no ip http server
    no ip http secure-server
    bridge 1 route ip
    line con 0
    line vty 0 4
    login local
    end

    Yeah!! even i have come across multiple issue with MAC and Cisco.. these are the below settings which i normally do on the cisco gears and most of the times this solved the issue..
    on the IOS AP disable Aironet Extentions and set the poer local and ofdm to max
    no dot11 extension aironet
    power local cck max
    power local ofdm max
    end
    On the WLC, disable Aironet IE..
    lemme know if this answered your question..
    Regards
    Surendra
    ====
    Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

  • Cisco ACS 4.2 authenticating Cisco 4710 ACE appliance failed

    Hi,
    I've got a problem with Cisco ACS 4.2 authenticating Cisco 4710 ACE appliance.
    ACS4.2 has been configured to use both internal and external database. It's been working fine for a couple or years.
    Recently we bought a Cisco 4710 ACE appliance. When I use ACS4.2 internal username and password to login the Cisco 4710 ACE appliance, I have no problem. I can also see the passed authentication log on ACS4.2. However, if I use AD username and password, I couldn't login in. The message is "Login incorrect". I checked the failed attempts log on the ACS4.2, there was no log regarding the failed attempt. My AD username and password works fine on all other cisco routers and switches.
    I've posted my AAA configuration of the 4710 ACE below. ACE is running on the latest version A4(1.1). Please help.
    tacacs-server key 7 "xxxxxxxxxxxxx"
    aaa group server tacacs+ tac_admin
      server xx.xx.xx.xx
    aaa authentication login default group tac_admin local
    aaa authentication login console group tac_admin local
    aaa accounting default group tac_admin

    Hi,
    Since the ACS is receiving the request.
    Could you please ensure that In ACE on every context (including Admin and other) you have  following strings:
    tacacs-server host x.x.x.x key 7 "xxx"
    aaa group server tacacs+  tac_admin
       server x.x.x.x
    aaa authentication login default group  tac_admin local
    aaa authentication login console group  tac_admin local 
    aaa accounting default group x.x.x.x
    On ACS side for group named "Network  Administrators" you should configure in TACACS settting:
    1. Shell  (exec) enable
    2. Privilege level 15
    3. Custom attributes:
               shell:Admin*Admin default-domain
        if you have additional  context add next line
              shell:mycontext*Admin  default-domain
    After  loging to ACE and issuing sh users command you should see following
    User             Context                                                                  Line     Login Time   (Location)        Role   Domain(s)   
    *adm-x        Admin                                                                    pts/0   Sep 21 12:24  (x.x.x.x)    Admin   default-domain
    Hope this helps.
    Regards,
    Anisha
    P.S.: please mark this thread as answered if you fee your query is resolved. Do rate helpful posts.

  • Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: Can Ping a device in another VLAN, that device cannot ping back

    Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: From the Switch I can Ping a device in another VLAN, that device cannot ping back. Some devices can ping devices in other VLANs and the device in the other VLAN can successfully return the Ping. Have a look at the attached diagram.
    Router Config:
    show run
    Building configuration...
    Current configuration : 7224 bytes
    ! Last configuration change at 09:05:48 EDT Wed Aug 6 2014
    version 15.2
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname ROUTER
    boot-start-marker
    boot-end-marker
    no aaa new-model
    clock timezone EDT -8 0
    ip cef
    ip name-server 8.8.8.8
    no ipv6 cef
    multilink bundle-name authenticated
    license udi pid CISCO1941/K9
    object-group network Net_Obj_Group1 
     description This network group allows all 10.0.0.0 and Email Forwarder server through to the Plt PCs
     205.191.0.0 255.255.0.0
     10.0.0.0 255.0.0.0
    object-group network Net_Obj_Group2 
     description This Network Group includes the Host IPs allowed through the Plant Router
     host 10.194.28.23
     host 10.194.28.25
     host 10.194.28.26
     host 10.194.28.27
     host 10.194.28.28
     host 10.194.28.29
     host 10.194.28.37
     host 10.194.28.39
     host 10.194.28.40
     host 10.194.28.70
     host 10.194.28.130
     host 10.194.28.131
     host 10.194.28.132
     host 10.194.28.133
     host 10.194.28.134
     host 10.194.28.135
     host 10.194.28.136
     host 10.194.28.137
     host 10.194.28.138
     host 10.194.28.139
     host 10.194.28.140
     host 10.194.28.141
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description Port Ge0/0 to IT Enterprise network Switch GE1/0/38
     ip address 10.194.28.111 255.255.255.0
     ip access-group 105 in
     ip access-group 106 out
     ip nat outside
     ip virtual-reassembly in
     shutdown
     duplex full
     speed auto
     no mop enabled
    interface GigabitEthernet0/1
     description Port to Plant PCN-K/L24 Sw1 Port 0/24
     no ip address
     duplex auto
     speed auto
     no mop enabled
    interface GigabitEthernet0/1.102
     description Port to VLAN 102
     encapsulation dot1Q 102
     ip address 192.168.102.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.104
     description Port to VLAN 104
     encapsulation dot1Q 104
     ip address 192.168.104.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.105
     description Port to VLAN 105
     encapsulation dot1Q 105
     ip address 192.168.105.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.106
     description Port to VLAN 106
     encapsulation dot1Q 106
     ip address 192.168.106.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.107
     description Port to VLAN 107
     encapsulation dot1Q 107
     ip address 192.168.107.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.111
     description Port to VLAN 111
     encapsulation dot1Q 111
     ip address 192.168.111.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.117
     description Port to VLAN 117
     encapsulation dot1Q 117
     ip address 192.168.117.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.121
     description Port to VLAN 121
     encapsulation dot1Q 121
     ip address 192.168.121.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.125
     description Port to VLAN 125
     encapsulation dot1Q 125
     ip address 192.168.125.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.150
     description Port to to VLAN 150
     encapsulation dot1Q 150
     ip address 192.168.150.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    interface GigabitEthernet0/1.999
     description Port to VLAN 999
     encapsulation dot1Q 999
     ip address 192.168.0.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    ip forward-protocol nd
    ip http server
    no ip http secure-server
    ip nat inside source static 192.168.102.201 10.194.28.23
    ip nat inside source static 192.168.121.201 10.194.28.25
    ip nat inside source static 192.168.106.251 10.194.28.26
    ip nat inside source static 192.168.107.245 10.194.28.27
    ip nat inside source static 192.168.102.251 10.194.28.28
    ip nat inside source static 192.168.150.201 10.194.28.29
    ip nat inside source static 192.168.107.179 10.194.28.37
    ip nat inside source static 192.168.111.201 10.194.28.39
    ip nat inside source static 192.168.105.201 10.194.28.40
    ip nat inside source static 192.168.106.21 10.194.28.70
    ip nat inside source static 192.168.107.146 10.194.28.130
    ip nat inside source static 192.168.107.156 10.194.28.131
    ip nat inside source static 192.168.107.161 10.194.28.132
    ip nat inside source static 192.168.107.181 10.194.28.133
    ip nat inside source static 192.168.107.191 10.194.28.134
    ip nat inside source static 192.168.106.202 10.194.28.135
    ip nat inside source static 192.168.106.212 10.194.28.136
    ip nat inside source static 192.168.117.190 10.194.28.137
    ip nat inside source static 192.168.117.100 10.194.28.138
    ip nat inside source static 192.168.106.242 10.194.28.139
    ip nat inside source static 192.168.125.100 10.194.28.140
    ip nat inside source static 192.168.125.99 10.194.28.141
    ip nat outside source static 10.194.28.23 10.194.28.23
    ip nat outside source static 10.194.28.25 10.194.28.25
    ip nat outside source static 10.194.28.26 10.194.28.26
    ip nat outside source static 10.194.28.27 10.194.28.27
    ip nat outside source static 10.194.28.28 10.194.28.28
    ip nat outside source static 10.194.28.29 10.194.28.29
    ip nat outside source static 10.194.28.37 10.194.28.37
    ip nat outside source static 10.194.28.39 10.194.28.39
    ip nat outside source static 10.194.28.40 10.194.28.40
    ip nat outside source static 10.194.28.70 10.194.28.70
    ip nat outside source static 10.194.28.130 10.194.28.130
    ip nat outside source static 10.194.28.131 10.194.28.131
    ip nat outside source static 10.194.28.132 10.194.28.132
    ip nat outside source static 10.194.28.133 10.194.28.133
    ip nat outside source static 10.194.28.134 10.194.28.134
    ip nat outside source static 10.194.28.135 10.194.28.135
    ip nat outside source static 10.194.28.136 10.194.28.136
    ip nat outside source static 10.194.28.137 10.194.28.137
    ip nat outside source static 10.194.28.138 10.194.28.138
    ip nat outside source static 10.194.28.139 10.194.28.139
    ip nat outside source static 10.194.28.140 10.194.28.140
    ip nat outside source static 10.194.28.141 10.194.28.141
    ip route 0.0.0.0 0.0.0.0 10.194.28.1
    access-list 105 permit ip object-group Net_Obj_Group1 object-group Net_Obj_Group2
    access-list 106 permit ip object-group Net_Obj_Group2 object-group Net_Obj_Group1
    dialer-list 1 protocol ip permit
    control-plane
    banner login ^CC
    Login banner for Plant Router #01^C
    banner motd ^CC
    MOTD Banner for Plant Router^C
    line con 0
     password XXXXXXXXX
     logging synchronous
     login
    line aux 0
    line 2
     no activation-character
     no exec
     transport preferred none
     transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
     stopbits 1
    line vty 0 4
     password XXXXXXXXX
     logging synchronous
     login
     transport input all
    scheduler allocate 20000 1000
    ntp server 10.199.100.92
    end
    Switch Config:
    sh ru
    Building configuration...
    Current configuration : 6513 bytes
    version 12.2
    no service pad
    service timestamps debug uptime
    service timestamps log datetime localtime show-timezone
    service password-encryption
    hostname K24Sw01
    boot-start-marker
    boot-end-marker
    no aaa new-model
    clock timezone EDT -5
    clock summer-time EDT recurring
    udld aggressive
    crypto pki trustpoint TP-self-signed-593746944
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-593746944
     revocation-check none
     rsakeypair TP-self-signed-593746944
      4B58BCE9 44
      quit
    spanning-tree mode pvst
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    interface FastEthernet0
     no ip address
    interface GigabitEthernet0/1
     description Trunk port for vlans 105, 111, 125 and 999 from K24Sw01 port Ge0/1 to P22Sw01 port Ge0/24
     switchport trunk allowed vlan 105,111,125,999
     switchport mode trunk
    interface GigabitEthernet0/2
     description Trunk port for vlans 150 and 999 from K24Sw01 port Ge0/2 to N25Sw01 port Ge0/26
     switchport trunk allowed vlan 150,999
     switchport mode trunk
    interface GigabitEthernet0/3
     description Trunk port for vlans 102, 104, 106, 107, 117 and 999 from K24Sw01 port Ge0/3 to K28Sw01 port Ge0/26
     switchport trunk allowed vlan 102,104,106,107,117,999
     switchport mode trunk
    interface GigabitEthernet0/4
     description Trunk port for vlans 102, 106, 107 and 999 from K24Sw01 port Ge0/4 to H23Sw01 port Ge0/26
     switchport trunk allowed vlan 102,106,107,999
     switchport mode trunk
    interface GigabitEthernet0/5
     description Trunk port for vlans 121, 125 and 999 from K24Sw01 port Ge0/5 to M21Sw01 port Ge0/24
     switchport trunk allowed vlan 121,125,999
     switchport mode trunk
    interface GigabitEthernet0/6
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/7
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/8
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/9
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/10
     description VLan 102 access port
     switchport access vlan 102
     spanning-tree portfast
    interface GigabitEthernet0/11
     description - VLan 104 access port
     switchport access vlan 104
     spanning-tree portfast
    interface GigabitEthernet0/12
     description - VLan 105 access port
     switchport access vlan 105
     spanning-tree portfast
    interface GigabitEthernet0/13
     description - VLan 106 access port
     switchport access vlan 106
     spanning-tree portfast
    interface GigabitEthernet0/14
     description - VLan 107 access port
     switchport access vlan 107
     spanning-tree portfast
    interface GigabitEthernet0/15
     description - VLan 111 access port
     switchport access vlan 111
     spanning-tree portfast
    interface GigabitEthernet0/16
     description - VLan 117 access port
     switchport access vlan 117
     spanning-tree portfast
    interface GigabitEthernet0/17
     description - VLan 121 access port
     switchport access vlan 121
     spanning-tree portfast
    interface GigabitEthernet0/18
     description - VLan 125 access port
     switchport access vlan 125
     spanning-tree portfast
    interface GigabitEthernet0/19
     description - VLan 150 access port
     switchport access vlan 150
     spanning-tree portfast
    interface GigabitEthernet0/20
     description - VLan 999 access port
     switchport access vlan 999
     spanning-tree portfast
    interface GigabitEthernet0/21
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/22
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/23
     description OPEN
     spanning-tree portfast
    interface GigabitEthernet0/24
     description From ROUTER Gw ge0/1
     switchport trunk allowed vlan 102,104-107,111,117,121,125,150,999
     switchport mode trunk
    interface GigabitEthernet0/25
    interface GigabitEthernet0/26
    interface Vlan1
     no ip address
     no ip route-cache
     shutdown
    interface Vlan102
     ip address 192.168.102.253 255.255.255.0
    interface Vlan104
     no ip address
     no ip route-cache
    interface Vlan105
     no ip address
     no ip route-cache
    interface Vlan106
     no ip address
     no ip route-cache
    interface Vlan107
     no ip address
     no ip route-cache
    interface Vlan111
     no ip address
     no ip route-cache
    interface Vlan117
     no ip address
     no ip route-cache
    interface Vlan121
     no ip address
     no ip route-cache
    interface Vlan125
     no ip address
     no ip route-cache
    interface Vlan150
     no ip address
     no ip route-cache
    interface Vlan999
     no ip address
     no ip route-cache
    ip default-gateway 192.168.102.1
    ip http server
    ip http secure-server
    snmp-server engineID local 00000009020000019634C2C0
    snmp-server community public RO
    snmp-server location 
    snmp-server contact 
    banner motd ^CCC ADMIN USE ONLY! ^C
    line con 0
     session-timeout 10 
     password xxxxxx
     logging synchronous
     login
     stopbits 1
    line vty 0 4
     session-timeout 10 
     password xxxxxxx
     login
    line vty 5 15
     session-timeout 10 
     password xxxxxxxx
     login
    ntp server 10.199.100.92
    end
    K24Sw01#

    HI Mark,
    Here is the my config:
    Create sub-interfaces, set 802.1Q trunking protocol and ip address on each sub-interface
    Router(config)#interface f0/0
    Router(config-if)#no shutdown
    (Note: The main interface f0/0 doesn’t need an IP address but it must be turned on)
    Router(config)#interface f0/0.10
    Router(config-subif)#encapsulation dot1q 10
    Router(config-subif)#ip address 192.168.10.1 255.255.255.0
    Router(config-subif)#interface f0/0.20
    Router(config-subif)#encapsulation dot11 20
    Router(config-subif)#ip address 192.168.20.1 255.255.255.0
    (Note: In the “encapsulation dot1q 10″ command, 10 is the VLAN ID this interface operates in)
    Configure VLAN
    Switch(config)#vlan 10
    Switch(config-vlan)#name SALES
    Switch(config-vlan)#vlan 20
    Switch(config-vlan)#name TECH
    Set ports to access mode & assign ports to VLAN
    Switch(config)#interface range fa0/1
    Switch(config-if)#no shutdown
    Switch(config-if)# switchport mode access
    Switch(config-if)# switchport access vlan 15
    Switch(config-if)#interface range fa0/3
    Switch(config-if)#no shutdown
    Switch(config-if)#switchport mode access
    Switch(config-if)# switchport access vlan 20
    Switch(config-if)#interface range fa0/5
    Switch(config-if)#no shutdown
    Switch(config-if)#switchport mode trunk
    1. Please check all your port are up.
    2. Check the config once again.
    3. Make sure the swicth and router connection port configured as trunk and it should be up.
    This config is working for me,
    Regards
    Dont forget to rate helpful posts.

  • 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 >

  • Cisco 6500 shows less traffic for NetFlow export

    I am using a Thrid party NetFlow tool, Enabled NetFlow on the Cisco 6500 as per recommendations and getting only half amout of traffic passing thorugh the interfaces. I have verified with 3 different NetFlow based tools, everything showing the same value. Is there any bug in my Cisco 6500. Any one faced this issue. Attached the output of (show run, show version)
    Cheers

    Hi Jake,
    I have already investigated this, the exporting interval and aging time for flows are set to lower active timeout. Is there any way to see all the flows are beeing captured and exported both on MSFC and PFC.
    Cheers

  • 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.

  • Is DOM supported using SNMP on Cisco 6500;s?

    Is DOM supported using SNMP on Cisco 6500's? I've configured DOM on 6509 using transceiver type all -> monitoring. Is DOM enable for SNMP mibs? Here's the MIB I got from a vendor. .1.3.6.1.4.1.3607. And I'm unable to walk it on any of my Cisco devices including Nexus 5672 and 4900.

    That oid looks like the sysoid for the ONS series of products. I don't think that will work in this case. Unfortunately, I can't offer any other advice, I've not looked into snmp support for DOM.
    chris

  • Contacts search for cisco Jabber for Windows & MAC

    Hello,
    Please assist on given below query !!
    System Deatails of CUCM & IM Presence Server
    CUCM:
    1>  System version: 9.1.1.20000-5
    2>  VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU X5650 @  2.67GHz, disk 1: 80Gbytes, 4096Mbytes RAM
    3> Physical Server UCS210 M2
    4>  Already Integrated with IM & Presence
    IM & Presence:
    1>  System version: 9.1.1.20000-5
    2>  VMware Installation: 1 vCPU Intel(R) Xeon(R) CPU X5650 @  2.67GHz, disk 1: 80Gbytes, 2048Mbytes RAM
    3> Physical Server UCS210 M2
    4>  Already Integrated with CUCM
    Requirement:
    1>  User Search base for Cisco Jabber for Windows & MAC Client
    2>  Will we able to get contacts list(Jabber For windows & MAC) as like "Lotus Sametimes" for all users?
    Every reply would highly Appreciated!!

    Hi Karthik,
    Thanks for your reply!
    I have gone through the link but query is different actually, please assist on below query and provide any document links if possible.
    1>  The contacts does not appear when I perform a search
    2>  Do I required to integrate LDAP for same? If Yes Then Do I need to perform integration with CUCM Or IM & Presence? Or Only CUCM? Or only IM & Presence? (Please post a link to perform same)
    3>  Please also provide If any specific system requirement for LDAP server.
    4>  Is it possible without LDAP integration?
    It is really urgent and every post would highly appreciate..........

  • My Mac sticks at the power down

    Hi!
    Since 1 week my Mac sticks at the power down. It says "unmount of /net failed (45)" and doesn't go to "done...", "CPU halted" and "AirPort en1 down". It just stays there. I can make some new lines and type in something, so it's still running, but doesn't go forward. This happens only if I use my Mac for more than 1-2 hours. If I boot and shut it off after 30 minutes or so it works.
    I read many things about such problems. I repaired the permissions and reintalled Mac OS 10.6.6, but this doesn't help. I don't use MobileMe and the iDisk, so this can't be the problem.
    Here are 2 logs. Maybe someone can find out why. I uploaded it to pastie.org, because it would be too long.
    http://pastie.org/private/4fkcvd7msdqeuidkmymaca
    http://pastie.org/private/goprcnq4zav3kz0kdtvwg

    Sorry for the push, but I found something out: If I sticks at the power down it says
    04.03.11 23:32:21 kernel Kext loading now disabled.
    04.03.11 23:32:21 kernel Kext unloading now disabled.
    04.03.11 23:32:21 kernel Kext autounloading now disabled.
    04.03.11 23:32:21 kernel Kernel requests now disabled.
    and doesn't do anything (I waited 15 minutes until I pressed the power button for 6 seconds). If I turn it off after 10 minutes or something like that it just says "systemShutdown true" and then it is off. This Kext messages appear after the "systemShutdown true" if I use my Mac for more than 2-3 hours or something like that. Does anyone know what this means?

  • Cisco connect software for MAC OSX 10.8.2

    Cicso,
    Please hurry up with releasing Cisco Connest software for MAC OSX 10.8.2
    Mine doesn't work anymore with the wireless Linksys router E3000

    I think we just need to wait until they update the software that will be compatible with this router. Who knows Cisco will be able to read this thread.

  • How to install cisco packet tracer on mac os x?

    I do not know to start for installing the cisco packet tracer on mac os x. please teach me. I need to use packet tracer for my styding in the class room

    Hi
    download " PlayOnMac " Application ==> http://www.playonmac.com/en  and  then install "Cisco Packet Tracer"
    Kind Regards

  • 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.  

  • Cisco 6500 --ACL entries showing incorrect order.

    Hi guys,
    I need your suggestion on my following issue:
    I have configure the ACL entries on my cisco 6500 series box but I see the ACL entries showing incorrect order when I check for the same.
    Eg:
    Europebox#show access-list 50
    10 permit 192.50.20.2 (10 matches)
     15 permit 192.52.0.134 (98 matches)
     75 permit 198.29.232.23 (38 matches)
     80 permit 10.96.127.14
     90 permit 192.22.2.10
     40 permit 192.22.0.76
    anyhelp would be appriciated
    regards
    neha

    Hi neha,
    This is the expected behaviour that you see for the standard access-lists.
    Regards
    Inayath

  • 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.

Maybe you are looking for