6509 vs 6513

Hello,
is there a difference between a 6509 and 6513, besides of course the no. of slots in each chassis?

Catalyst 6509 chasis supports both WS-C6500-SFM and WS-C6500-SFM2. Both the SFM's are inserted in either
slot 5 or slot 6 on a 6509 Chasis.
Catalyst 6513 supports only WS-C6500-SFM2 but not WS-C6500-SFM. WS-C6500-SFM2 is inserted into slot 7 or slot 8 on a 6513 Chasis.
Note: WS-X6500-SFM2 and WS-C6500-SFM in combination with the Supervisor Engine 2 deliver an increase in available system bandwidth from the existing 32 Gbps to 256 Gbps. They enable an architecture that allows 30 Mpps of Cisco Express Forwarding-based central forwarding performance on Supervisor Engine 2 and up to 210 Mpps of distributed forwarding performance.
Difference between the WS-C6500-SFM and WS-C6500-SFM2:
The WS-C6500-SFM can only support up to eight fabric-enabled modules. For this reason, it can only function in a 6-slot or 9-slot 6500 Chassis.
The WS-C6500-SFM2 can support 11 fabric modules and functions in the 6-slot, 9-slot and 13-slot chassis.
Note: All line card slots in a 6-slot or 9-slot chassis have dual fabric channels. A 13-slot chassis, on the other hand, only has dual fabric channels in slots 9 through

Similar Messages

  • Moved CSM's from 6509 to 6513

    I just upgraded to a 6513 with sup720's. I moved both csm's and config info to the new config. Everything is working but before the move I could see both csm probe details and they were both operable. Now after the move only the active say's operable and the standby says failed. How do I get this back so that both are operable?

    you will have to do some troubleshooting.
    Get on the standby.
    See if it can ping the server.
    'ping mod csm X x.x.x.x'
    Check csm arp table.
    Check L2 mac-address table between CSM and server.
    finally, sniff on the server to see if it gets the probe and if it does send a response.
    Once you know exactly why it fails, you'll know how to fix it.
    Gilles.

  • WiSM compatibility for a "regular" 6509 chassis (not 6509-E)

    Does anyone know if the regular 6509 (ios, SUP720) chassis can support WiSM modules? And if so, how many modules? The docs on the website aren't consistent, some pages state 6509E's and others say 6509's.

    Hi Steven,
    We are just getting ready to add some new WISM's to our existing WLC infrastructure, so we just went through these same "due diligence" type questions. The answers from this good Q&A doc are all very accurate :)
    Q. What products support the Cisco WiSM?
    A. A single Cisco WiSM occupies one slot in a Catalyst 6500 Series Switch or a Cisco 7600 Series Router. The WiSM is supported with the Cisco Supervisor Engine 720.
    Cisco Catalyst 6500 Series Switch
    Q. What hardware must be deployed in conjunction with the Cisco WiSM?
    A. The Cisco WiSM must be deployed with a Cisco Catalyst 6500 Series Switch and a Cisco Catalyst 6500 Series Supervisor Engine 720 (all Supervisor Engine 720 versions are supported, including the Sup720-10G-VSS).
    Q. Which Cisco Catalyst 6500 Series Switch chassis are supported with Cisco WiSM?
    A. The Cisco WiSM supports Cisco Catalyst 6503, 6504, 6506, 6509, and 6513 switches (**enhanced and nonenhanced versions).
    Check out Table 1. Number of WiSMs and Access Points Supported
    http://www.cisco.com/en/US/prod/collateral/modules/ps2706/ps6526/prod_qas0900aecd8036434e.html
    Hope this helps! Good luck,
    Rob

  • Chassis View error

    We have the "typical" error (LMS 3.0.1+CV 6.1.7):
    Cannot find applicable device package for x.x.x.x:
    This error could be due to one of the following:
    - The device package for this device type is not installed.
    - Device support for this device type is not available.
    - You are trying to open a component inside a device.
    To correct the problem, either install a device package for the device type, or open the
    parent device to manage the component."
    Looking through support, we have found:
    Shutdown Daemon Manager, then copy all of the .zip files from NMSROOT/www/classpath/com/cisco/nm/xms/psu/pkgs/cvw to NMSROOT/MDC/tomcat/webapps/CVng/WEB-INF/classes/com/cisco/nm/cvw/devpkgs.  then restart Daemon Manager
    We have problem with a SW6503, 6509 and 6513, but files are quite strange, i think

    They are:
    .1.3.6.1.4.1.9.1.282
    .1.3.6.1.4.1.9.1.283
    .1.3.6.1.4.1.9.1.400
    They say it has been working till they deleted and added nodes again.
    I have tried to delete package, and intall it again, and always the same error :-(
    For Product(s) : CiscoView
    Install Invoked by user : admin
    The Package(s) Selected for Install :
    Cat6000, Cat6000IOS
    Successfully installed packages (2):
    Cat6000(9.1) ,Cat6000IOS(30.0)
    Installation Completed for : CiscoView
    After deinstall/install packages, in www folder, only appear:
    Cat6000.cv50.v9-1.zip
    Cat6000IOS.cv50.v30-0.zip
    So, i have to copy Cat6000.zip and Cat6000IOS.zip from MDC folder again!!!
    Thanks in advance

  • 6513 - 6509 Chassis

    I currently have a 6513 chassis that have the following modules, (WS-6416-GBIC, WS-6316-GE-TX, & WS-6348-RJ45). I'm replacing the 6513 switch with a WS-C6509-E chassis, I need to know if my current modules that are listed above will work in the new C-6509-E chassis? Also what type of module goes into slot-13 of the 6513?
    Thanks,

    The cards you cite are not constrained in the 6509E
    Slot 13 in the 6513 is a regular module slot. Some modules only work in slot 9-13, and SFM(s) must be in slots 7 or 8.
    Reference chassis installation guide, pages 1-32, -33, and -48: http://www.cisco.com/application/pdf/en/us/guest/products/ps708/c2001/ccmigration_09186a0080231ba4.pdf)
    Hope this helps, Please rate helpful posts.

  • Rack / Cabinet for Cisco 6513/6509 switches

    Hi
    I'm currently engaged in a IT definition project and I have to define 4 racks or cabinets (42U) for 2 core switches (6509E) and 2 datacenter switches (6513). Another network equipments will be deployed in these racks (firewalls, VPN concentrators, stackable switches, etc). The racks will be located on the enterprise datacenter and the chassis switches have all slots filled. The datacenter cooling is under the racks.
    In this scenario, which kind of rack or cabinet is recommended? What is accepted? (open racks, closed cabinets, forced ventilation, etc). Who are the main manufacturers?
    Thanks in advance
    Wesley

    Hi,
    The most important thing in general the rack or cabinet width, i think you have to choose either 75 or 80 cm width, this is very important for the cable management for the patch cord cables from the network modules "RJ45".
    Another important issue, is the cooling for the 6500 switches, since these Cisco switches have a special case, the fresh air enter the chassis from the right and the bad air exit the chassis from the left. So, take care for this case.
    We are using APC brand for the racks and also we choosed special cooling device from APC for the 6500 cooling.
    http://www.apcc.com/
    And also i think the great lakes cabinets are good.
    Please rate helpful posts!
    Thanks
    Abd Alqader

  • How to extend VLAN in 3rd and 4th 6513 switch with HSRP

    Hi presently in One Data centre 02 Nos. of 6513 is configured in HSRP. Due to space constraint some servers need to be installed in other room and there 02 Nos of 6509 switches need to be configured in HSRP again. 
    One Data Vlan needs to be extended in expanded room. What should be the best practice for configuration in 6509 switches in HSRP. Please suggest.

    Just as #1 and #2 are connected with (I would assume) trunking ports, similarly add connections to #3 and #4 Catalyst 6k. Define the layer 2 VLANs in the 6509 and assign access ports to those VLANs as required.
    Personally I don't see much value to adding L3 interfaces (SVIs) for the VLANs (and adding them to the HSRP groups) on the 6509s. It depends in part on how your other connectivity into them is setup. If everything leaving the server VLAN goes to users, WAN, Internet etc. via the original pair of 6513s then keep the 6509s simple with only layer 2 VLANs.

  • 6506 and 6509

    Hello Experts,
    I have a quick question.
    Cisco Reommends to place the sup-1 and 2 in slot 1 and 2 of the chassis, and sup-720 to be places in slot 5 and 6 only.
    my question is that why i should place sup-720 in slot 5 and 6 only and not in slot 1 and 2.
    will appreciate your quick response.
    Many Thanks.

    Hello Experts,I have a quick question.Cisco Reommends to place the sup-1 and 2 in slot 1 and 2 of the chassis, and sup-720 to be places in slot 5 and 6 only.my question is that why i should place sup-720 in slot 5 and 6 only and not in slot 1 and 2.will appreciate your quick response.Many Thanks.
    Hi Kaushik,
    The Supervisor 720 incorporates a new version of the Policy Feature Card (PFC3A or PFC3B or PFC3BXL) as well as a new Multilayer Switch Feature Card (MSFC3) as well as an integrated 720 Gbps switch fabric. This level of integration increases slot efficiency of high performance and high availability configurations.Because the switch fabric is integrated with the supervisor, the Supervisor Engine 720 must be installed in particular slots.
    Chasis                                                                                        Slots for Supervisor Engine 720
    6503/6503-E/7603                                                                            1 or 2
    6506/6506-E/7606                                                                             5 or 6
    6509/6509-E                                                                                       5 or 6
    6509-NEBS/6509-NEBS-A/OSR-7609                                          5 or 6
    Cisco 7609                                                                                         5 or 6
    6513/7613                                                                                          7 or 8
    Hope to help !!
    If helpful do rate
    Ganesh.H

  • 6513 ACL List ION Routing Process

    Hello everyone I have a question about ION Routing Process that seems to show up on the 6513 cisco switch.
    Ok question, when I do a show access-list Test-ACL
    It will show me Test-ACL list then right after that with ION Routing Process the next line starts with all of the ACL lists that are on the device.
    We have two 6513 and they both do this but when i check out two 6509 they dont do this.
    Also check on 3750e too dont do this
    Can anyone explain this to me ?

    Craig
    What you are asking for can be done but it will be a bit tedious. You describe having 20 entries in the topology table and you want to control which one gets placed into the routing table. To do that you can either make the composite metric of the one entry more attractive or you can make the composite metric of the other 19 less attractive.
    When you use an offset list you add to the metric of an entry. It will not make any entry be more attractive but it can make other entries less attractive. So you could configure an offset list identifying the route in question and apply some offset (100 should work for example). Then you would need to apply this offset to the 19 neighbors who are advertising the route.
    HTH
    Rick

  • 6513-E chassis issue

    I have 6513-E chassis in which i have installed 2 "WS-SUP32-10GE-3B" supervisor modules. But when i power on the switch the sup engine crashes.
    Same sup engine is working on 6509-E chassis.
    I have checked on Cisco site this sup engine is supported on 6513-E switch.
    IOS installed in the sup engine is "sup-bootdisk:s3223-advipservicesk9_wan-mz.122-33.SXI.bin".
    Can anyone tell me what will be the issue?
    Is it IOS issue?
    When we will connect 2 chassis in VSS if the IOS available on both the sup engine is different can this create any problem?
    Regards,
    Mukesh Kumar
    Network Engineer
    Spooster IT Services

    Try loading a different IOS version.  If that does not help try moving the sup to a different slot and if that does not help the problem is the Sup.
    HTH

  • LAN network design - Core/access with Cisco 6513

    Hi,
    I have been tasked with setting up a new branch office, with 100+ users, a stack of servers (1Gb-based) and some wireless access points, WAN block (ASA 5520 and a couple of routers.)
    At the moment, port requirement is around 400. 
    As there's not enough space and it's only a single floor office, I'm thinking to go ahead with one of Cisco 6500 models, specifically Catalyst 6513-E, as a core and access switch. This way, there won't be any need to try to install 48-port switches around the small office area.
    I'm not too sure about the pricing at the moment. It may be a better/cheaper option to go with a couple of 3750s as core/aggregation and 2960s for access switch installed all in the same rack. If I go with small switches, it would be roughly x7 48-port access switches and one stack of two 3750s, which gives about 450-60. 
    I believe I won't utilise half of the capacity if I go ahead with 6513, however my manager wants to minimise the overhead managing this branch office hence this all-in-all one switch option has resurfaced.
    Is there anyone using this kind of similar setup in the environment? If so, can you please share your opinions?
    Also, would there be a huge difference in terms of pricing?
    Catalyst 6503-E
    Catalyst 6504-E
    Catalyst 6506-E
    Catalyst 6509-E
    Catalyst 6513-E
    Catalyst 6509-V-E
    Slots
    3
    4
    6
    9
    13
    9 vertical
    Max 10/100/1000 ports
    97
    145
    241
    385
    529
    385
    Max 1 GE ports1
    99
    147
    243
    387
    534
    387
    Max 10 GE ports2
    34
    50
    82
    130
    180
    130
    Max 40 GE ports
    8
    12
    20
    32
    44
    32
    Maximum forwarding performance (IPv4)
    150 Mpps
    210 Mpps
    330 Mpps
    510 Mpps
    720 Mpps
    510 Mpps
    Height (RU)
    4
    5
    11
    14
    19
    21
    Weight (chassis)
    33 lbs
    (15 kg)
    40 lbs
    (17.8 kg)
    50 lbs
    (22.7 kg)
    60 lbs
    (27.3 kg)
    79.1 lbs
    (35.9 kg)
    121 lbs
    (54.9 kg )
    Thanks

    Thanks a lot for your input, Joseph.
    I was just going over 4510R+E for a potential winner; It seems to have 10 slots, which gives me about 390 Gig ports, with two dual sups. Given that a single sup 8E can provide throughput as below table, I should think about going forward with a single sup.
    Given that most users will be on 100Mbps at peak time and all other miscellaneous traffic, it would come down to around 20Gbps.
    Model
    Supervisor 8E
    Supervisor 7E
    Supervisor 7LE
    Supervisor 6E
    Supervisor 6LE
    Supervisor V 10 GE
    Documentation
    Data Sheet
    Data Sheet
    Data Sheet
    Data Sheet
    Data Sheet
    Data Sheet
    Performance
    Supervisor 8E
    Supervisor 7E
    Supervisor 7LE
    Supervisor 6E
    Supervisor 6LE
    Supervisor V 10 GE
    Switching Capacity
    928 Gbps
    848 Gbps
    520 Gbps
    320 Gbps
    280 Gbps
    136 Gbps
    IPv4 Throughput
    250 Mpps
    250 Mpps
    225 Mpps
    250 Mpps
    225 Mpps
    102 Mpps
    IPv6 Throughput
    125 Mpps
    125 Mpps
    110 Mpps
    125 Mpps
    110 Mpps
    Software Switched
    Bandwidth/Slot
    48 Gbps
    48 Gbps
    48 Gbps
    24 Gbps
    24 Gbps
    6 Gbps
    Scalability
    Supervisor 8E
    Supervisor 7E
    Supervisor 7LE
    Supervisor 6E
    Supervisor 6LE
    Supervisor V 10 GE
    Number of Routes
    256K for IPv4
    128K for IPv6
    256K for IPv4
    128K for IPv6
    64K for IPv4
    32K for IPv6
    256K for IPv4
    128K for IPv6
    64K for IPv4
    32K for IPv6
    128K for IPv4
    1K for IPv6
    Number of Packet Buffers
    128K
    128K
    128K
    64K
    64K
    32K
    NetFlow Entries
    128K
    128K
    128K
    85K
    MAC Learning Rate per Second
    20K
    20K
    14K
    13K
    8K
    8K
    Dynamic Host Control Protocol (DHCP) Snoop Entries
    12K
    12K
    12K
    12K
    3K
    6K
    Number of 10/100/1000 Ports
    Up to 384 access
    Up to 384 access
    Up to 240 access
    Up to 384 access
    Up to 240 access
    Up to 384 access
    10 GE and 1 GE Uplinks
    8 10 GE / 1 GE
    4 10 GE / 1 GE
    2 10 GE / 4 1 GE
    2 10 GE / 4 1 GE (TwinGig)
    2 10 GE / 4 1 GE (TwinGig)
    2 10 GE + 4 1 GE
    1 GE Non-Blocking Fiber Ports
    192
    192
    120
    138
    120
    48
    10 GE Fiber Ports
    96
    96
    60
    30
    30

  • NAT IN CATALYST 6509-HOW TO DO IT?

    Hello friends,
    The LAN CAMPUS is conformed by more than 20 VLANS and all the PCs can go to Internet.
    Now I have a new network cloud and I have to attach that network into my campus.
    To do that, I have a Public IP Pool to do translation.
    But I just need that some IPs (from diferent Vlans)could go to the new Network while keep having connecivity to Internet.
    So my Question is:
    I am not interested in perform Static NAT.
    I wonder if I can NAT a group of IPs (in different subnets) with the Public POOL. i.e: group to group.
    I have a PIX 525. I could do it in that PIX but I think It could be better to do it in the Catalyst 6509. (Because the Pix CPU percentage is High-and sometimes I have problems)
    How can I do NAT in C 6509?
    I am attaching a referecial picture.

    Hi bosalaza:
    yes, I think ACL will help so much...
    Look I need to translate only this IPs:
    172.16.8.56
    172.16.24.85
    172.16.33.95
    172.16.86.56
    172.16.125.81
    172.16.157.89
    To this Public IPs:
    200.xx.45.170
    200.xx.45.171
    200.xx.45.172
    200.xx.45.173
    200.xx.45.174
    200.xx.45.175
    But whitout Static NAT.
    And do it but in the C6509.
    I have no enough experience to perform NAt in C6509.
    Thanks in advance.

  • A Problem with VSS in the 6509

    Hello,
    I have a problem with VSS in the 6500, when the switch 1 is active,probably a few months will switchover to switch 2 and switch 1 reload.
    config:
    switch virtual domain 1
     switch mode virtual
     switch 1 priority 110
     switch 2 priority 110
    interface Port-channel1
     description To 6509-B-VSS
     no switchport
     no ip address
     switch virtual link 1
     mls qos trust cos
     no mls qos channel-consistency
    interface Port-channel2
     description 6509-A-VSS
     no switchport
     no ip address
     switch virtual link 2
     mls qos trust cos
     no mls qos channel-consistency
    interface GigabitEthernet1/4/20
     no switchport
     no ip address
     dual-active fast-hello
    interface TenGigabitEthernet1/5/4
     description To 6509-B-VSS
     no switchport
     no ip address
     mls qos trust cos
     channel-group 1 mode on
    interface TenGigabitEthernet1/5/5
     description To 6509-B-VSS
     no switchport
     no ip address
     mls qos trust cos
     channel-group 1 mode on
    interface GigabitEthernet2/4/20
     no switchport
     no ip address
     dual-active fast-hello
    interface TenGigabitEthernet2/5/4
     description To 6509-A-VSS
     no switchport
     no ip address
     mls qos trust cos
     channel-group 2 mode on
    interface TenGigabitEthernet2/5/5
     description To 6509-A-VSS
     no switchport
     no ip address
     mls qos trust cos
     channel-group 2 mode on
    show switch virtual redundancy
                      My Switch Id = 2
                    Peer Switch Id = 1
            Last switchover reason = active unit removed
        Configured Redundancy Mode = sso
         Operating Redundancy Mode = sso
    Switch 2 Slot 5 Processor Information :
            Current Software state = ACTIVE
           Uptime in current state = 5 hours, 24 minutes
                     Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-M), Version 12.2(33)SXJ5, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Thu 31-Jan-13 14:30 by prod_rel_team
                              BOOT = sup-bootdisk:/s72033-ipbasek9-mz.122-33.SXJ5.bin,12;
            Configuration register = 0x2102
                      Fabric State = ACTIVE
               Control Plane State = ACTIVE
    Switch 1 Slot 5 Processor Information :
            Current Software state = STANDBY HOT (switchover target)
           Uptime in current state = 5 hours, 18 minutes
                     Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-M), Version 12.2(33)SXJ5, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Thu 31-Jan-13 14:30 by prod_rel_team
                              BOOT = sup-bootdisk:/s72033-ipbasek9-mz.122-33.SXJ5.bin,12;
            Configuration register = 0x2102
                      Fabric State = ACTIVE
               Control Plane State = STANDBY
    show log
    Jun 21 11:20:52.742: %VSL-SW2_SPSTBY-5-VSL_CNTRL_LINK:  New VSL Control Link Te2/5/4
    Jun 21 11:20:52.786: %VSLP-SW2_SPSTBY-3-VSLP_LMP_FAIL_REASON: Te2/5/4: Link down
    Jun 21 11:20:52.786: %VSLP-SW2_SPSTBY-2-VSL_DOWN:   Last VSL interface Te2/5/4 went down
    Jun 21 11:20:52.790: %VSLP-SW2_SPSTBY-2-VSL_DOWN:   All VSL links went down while switch is in Standby role
    Jun 21 11:20:52.790: %DUAL_ACTIVE-SW2_SPSTBY-1-VSL_DOWN: VSL is down - switchover, or possible dual-active situation has occurred
    Jun 21 11:20:53.622: %SYS-SW2_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
    Jun 21 11:20:54.678: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
    Jun 21 11:20:54.682: %C6KPWR-SP-4-PSOK: power supply 2 turned on.
    Jun 21 11:20:54.738: %SATVS_IBC-SW2_SP-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:0x4/0x4, SSAP/DSAP:0x19/0x0, OP/SEQ:0x320/0x8FD9, SIG/INFO:0x1/0x502, eSA:0000.0500.0000)
    Jun 21 11:20:56.490: %SATVS_IBC-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:0x14/0x4, SSAP/DSAP:0x18/0x0, OP/SEQ:0x19/0x98, SIG/INFO:0x1/0x502, eSA:0000.1500.0000)
    Jun 21 11:21:02.125: %VSDA-SW2_SP-3-LINK_DOWN: Interface Gi2/4/20 is no longer dual-active detection capable
    Jun 21 11:23:27.719: %VSLP-SW2_SP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
    Jun 21 11:23:27.719: %VSL-SW2_SP-5-VSL_CNTRL_LINK:  New VSL Control Link Te2/5/4
    Jun 21 11:23:27.799: %VSLP-SW2_SP-5-VSL_UP:  Ready for control traffic
    Jun 21 11:24:43.346: %PFINIT-SW2_SP-5-CONFIG_SYNC: Sync'ing the startup configuration to the standby Router.
    Jun 21 11:25:35.304: %VSLP-SW2_SP-5-VSL_UP:  Ready for data traffic
    Jun 21 11:25:14.946: %C6KPWR-SW1_SPSTBY-4-PSOK: power supply 1 turned on.
    Jun 21 11:25:14.950: %C6KPWR-SW1_SPSTBY-4-PSOK: power supply 2 turned on.
    Jun 21 11:25:16.975: %FABRIC-SW1_SPSTBY-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 5.
    Jun 21 11:25:16.975: %FABRIC-SW1_SPSTBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    Jun 21 11:26:13.738: %SYS-SW1_SPSTBY-5-RESTART: System restarted --
    Jun 21 11:26:20.446: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:01:47 to ensure console debugging output.
    Jun 21 11:26:32.056: %RF-SW2_SP-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
    Jun 21 11:27:56.962: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:01:24 to ensure console debugging output.
    Jun 21 11:27:53.970: %SYS-DFC4-5-RESTART: System restarted --
    Jun 21 11:28:34.222: %VSDA-SW1_SPSTBY-5-LINK_UP: Interface Gi1/4/20 is now dual-active detection capable
    Jun 21 11:28:36.236: %VSDA-SW2_SP-5-LINK_UP: Interface Gi2/4/20 is now dual-active detection capable
    Best Regard

    hi,
    Information of Last System Crash - SP
    Writing crashinfo to bootflash:crashinfo_SP_20140621-192052-TW 00 07 00 00 00 00 00 00 00 0F 00 00 00 00 00 00 10 D6 0A 06 FD 37 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
    Jun 21 11:19:43.723: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.723: SW1_SP: IPC: Message 504CA554 timed out waiting for Ack
    Jun 21 11:19:43.723: SW1_SP: IPC:  MSG: ptr: 0x504CA554, flags: 0x24100, retries: 8, seq: 0x315E1ED, refcount: 1, rpc_result = 0x0, data_buffer = 0x504104BC, header = 0x8A453C8, data = 0x8A453E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57837, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF38, lo: 0x8A453E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 5E 0A 06 01 01 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
    Jun 21 11:19:43.723: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504CA554, flags: 0x24100, retries: 8, seq: 0x315E1ED, refcount: 1, rpc_result = 0x0, data_buffer = 0x504104BC, header = 0x8A453C8, data = 0x8A453E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57837, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF38, lo: 0x8A453E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 5E 0A 06 01 01 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
    Jun 21 11:19:43.727: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.727: SW1_SP: IPC: Message 4528FE20 timed out waiting for Ack
    Jun 21 11:19:43.727: SW1_SP: IPC:  MSG: ptr: 0x4528FE20, flags: 0x24100, retries: 8, seq: 0x315E1EE, refcount: 1, rpc_result = 0x0, data_buffer = 0x4520B23C, header = 0x8C884C8, data = 0x8C884E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57838, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF39, lo: 0x8C884E8  || DATA: 2C D5 00 01 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 40 0A 06 0A 15 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
    Jun 21 11:19:43.727: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4528FE20, flags: 0x24100, retries: 8, seq: 0x315E1EE, refcount: 1, rpc_result = 0x0, data_buffer = 0x4520B23C, header = 0x8C884C8, data = 0x8C884E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57838, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF39, lo: 0x8C884E8  || DATA: 2C D5 00 01 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 40 0A 06 0A 15 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
    Jun 21 11:19:43.727: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.727: SW1_SP: IPC: Message 4529E380 timed out waiting for Ack
    Jun 21 11:19:43.727: SW1_SP: IPC:  MSG: ptr: 0x4529E380, flags: 0x24100, retries: 8, seq: 0x315E1EF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50418920, header = 0x8A93DC8, data = 0x8A93DE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57839, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3A, lo: 0x8A93DE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 12 00 00 00 00 00 00 08 9E 0A 06 9A 0B 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 16 00 00
    Jun 21 11:19:43.727: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4529E380, flags: 0x24100, retries: 8, seq: 0x315E1EF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50418920, header = 0x8A93DC8, data = 0x8A93DE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57839, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3A, lo: 0x8A93DE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 12 00 00 00 00 00 00 08 9E 0A 06 9A 0B 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 16 00 00
    Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.731: SW1_SP: IPC: Message 45238524 timed out waiting for Ack
    Jun 21 11:19:43.731: SW1_SP: IPC:  MSG: ptr: 0x45238524, flags: 0x24100, retries: 8, seq: 0x315E1F0, refcount: 1, rpc_result = 0x0, data_buffer = 0x50372694, header = 0x8468FC8, data = 0x8468FE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57840, sz: 1332, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3B, lo: 0x8468FE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 03 74 0A 06 FD 4C 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45238524, flags: 0x24100, retries: 8, seq: 0x315E1F0, refcount: 1, rpc_result = 0x0, data_buffer = 0x50372694, header = 0x8468FC8, data = 0x8468FE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57840, sz: 1332, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3B, lo: 0x8468FE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 03 74 0A 06 FD 4C 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.731: SW1_SP: IPC: Message 4524C89C timed out waiting for Ack
    Jun 21 11:19:43.731: SW1_SP: IPC:  MSG: ptr: 0x4524C89C, flags: 0x24100, retries: 6, seq: 0x315E1F1, refcount: 1, rpc_result = 0x0, data_buffer = 0x451B45EC, header = 0x894FCC8, data = 0x894FCE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57841, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFE9, lo: 0x894FCE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
    Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4524C89C, flags: 0x24100, retries: 6, seq: 0x315E1F1, refcount: 1, rpc_result = 0x0, data_buffer = 0x451B45EC, header = 0x894FCC8, data = 0x894FCE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57841, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFE9, lo: 0x894FCE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
    Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.731: SW1_SP: IPC: Message 45268348 timed out waiting for Ack
    Jun 21 11:19:43.731: SW1_SP: IPC:  MSG: ptr: 0x45268348, flags: 0x24100, retries: 6, seq: 0x315E1F2, refcount: 1, rpc_result = 0x0, data_buffer = 0x50462254, header = 0x8D4EFC8, data = 0x8D4EFE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57842, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEA, lo: 0x8D4EFE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 38 00 00 00 00 00 00 26 AB 0A 06 05 41 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 19 00 00
    Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45268348, flags: 0x24100, retries: 6, seq: 0x315E1F2, refcount: 1, rpc_result = 0x0, data_buffer = 0x50462254, header = 0x8D4EFC8, data = 0x8D4EFE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57842, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEA, lo: 0x8D4EFE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 38 00 00 00 00 00 00 26 AB 0A 06 05 41 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 19 00 00
    Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.735: SW1_SP: IPC: Message 45281D58 timed out waiting for Ack
    Jun 21 11:19:43.735: SW1_SP: IPC:  MSG: ptr: 0x45281D58, flags: 0x24100, retries: 6, seq: 0x315E1F3, refcount: 1, rpc_result = 0x0, data_buffer = 0x45201860, header = 0x8C2CEC8, data = 0x8C2CEE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57843, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEB, lo: 0x8C2CEE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 B9 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 97 0D 01 04 00 00 00 BB 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.735: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45281D58, flags: 0x24100, retries: 6, seq: 0x315E1F3, refcount: 1, rpc_result = 0x0, data_buffer = 0x45201860, header = 0x8C2CEC8, data = 0x8C2CEE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57843, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEB, lo: 0x8C2CEE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 B9 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 97 0D 01 04 00 00 00 BB 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.735: SW1_SP: IPC: Message 504A2D18 timed out waiting for Ack
    Jun 21 11:19:43.735: SW1_SP: IPC:  MSG: ptr: 0x504A2D18, flags: 0x24100, retries: 6, seq: 0x315E1F4, refcount: 1, rpc_result = 0x0, data_buffer = 0x451F3A88, header = 0x8BA92C8, data = 0x8BA92E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57844, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEC, lo: 0x8BA92E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 01 48 0A 06 FD 2F 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00
    Jun 21 11:19:43.735: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504A2D18, flags: 0x24100, retries: 6, seq: 0x315E1F4, refcount: 1, rpc_result = 0x0, data_buffer = 0x451F3A88, header = 0x8BA92C8, data = 0x8BA92E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57844, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEC, lo: 0x8BA92E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 01 48 0A 06 FD 2F 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00
    Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.735: SW1_SP: IPC: Message 504AA128 timed out waiting for Ack
    Jun 21 11:19:43.735: SW1_SP: IPC:  MSG: ptr: 0x504AA128, flags: 0x24100, retries: 6, seq: 0x315E1F5, refcount: 1, rpc_result = 0x0, data_buffer = 0x45228364, header = 0x8D9C8C8, data = 0x8D9C8E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57845, sz: 568, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFED, lo: 0x8D9C8E8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 26 00 0D 00 10 02 20 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00 00 00 00 00 02 3D 0A 06 FE 6C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 2D 00 00
    Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504AA128, flags: 0x24100, retries: 6, seq: 0x315E1F5, refcount: 1, rpc_result = 0x0, data_buffer = 0x45228364, header = 0x8D9C8C8, data = 0x8D9C8E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57845, sz: 568, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFED, lo: 0x8D9C8E8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 26 00 0D 00 10 02 20 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00 00 00 00 00 02 3D 0A 06 FE 6C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 2D 00 00
    Jun 21 11:19:43.739: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.739: SW1_SP: IPC: Message 504C15B4 timed out waiting for Ack
    Jun 21 11:19:43.739: SW1_SP: IPC:  MSG: ptr: 0x504C15B4, flags: 0x24100, retries: 4, seq: 0x315E1F6, refcount: 1, rpc_result = 0x0, data_buffer = 0x503C193C, header = 0x87593C8, data = 0x87593E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57846, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08B, lo: 0x87593E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 3B 00 00 00 00 00 00 10 A7 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 3B 00 00
    Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504C15B4, flags: 0x24100, retries: 4, seq: 0x315E1F6, refcount: 1, rpc_result = 0x0, data_buffer = 0x503C193C, header = 0x87593C8, data = 0x87593E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57846, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08B, lo: 0x87593E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 3B 00 00 00 00 00 00 10 A7 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 3B 00 00
    Jun 21 11:19:43.739: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.739: SW1_SP: IPC: Message 45273050 timed out waiting for Ack
    Jun 21 11:19:43.739: SW1_SP: IPC:  MSG: ptr: 0x45273050, flags: 0x24100, retries: 4, seq: 0x315E1F7, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044348C, header = 0x8C29BC8, data = 0x8C29BE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57847, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08C, lo: 0x8C29BE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00 00 00 00 00 02 24 0A 06 0C 18 01 04 00 00 00 98 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45273050, flags: 0x24100, retries: 4, seq: 0x315E1F7, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044348C, header = 0x8C29BC8, data = 0x8C29BE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57847, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08C, lo: 0x8C29BE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00 00 00 00 00 02 24 0A 06 0C 18 01 04 00 00 00 98 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.743: SW1_SP: IPC: Message 452A33E4 timed out waiting for Ack
    Jun 21 11:19:43.743: SW1_SP: IPC:  MSG: ptr: 0x452A33E4, flags: 0x24100, retries: 4, seq: 0x315E1F8, refcount: 1, rpc_result = 0x0, data_buffer = 0x50432830, header = 0x8B8A5C8, data = 0x8B8A5E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57848, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08D, lo: 0x8B8A5E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C4 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 A2 0B 01 04 00 00 00 C5 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.743: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452A33E4, flags: 0x24100, retries: 4, seq: 0x315E1F8, refcount: 1, rpc_result = 0x0, data_buffer = 0x50432830, header = 0x8B8A5C8, data = 0x8B8A5E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57848, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08D, lo: 0x8B8A5E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C4 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 A2 0B 01 04 00 00 00 C5 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
    Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.743: SW1_SP: IPC: Message 4523FFA4 timed out waiting for Ack
    Jun 21 11:19:43.743: SW1_SP: IPC:  MSG: ptr: 0x4523FFA4, flags: 0x24100, retries: 4, seq: 0x315E1F9, refcount: 1, rpc_result = 0x0, data_buffer = 0x5036F47C, header = 0x844B3C8, data = 0x844B3E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57849, sz: 772, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08E, lo: 0x844B3E8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 F2 00 0D 00 16 02 EC 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 01 46 0A 06 FE 5A 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
    Jun 21 11:19:43.743: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4523FFA4, flags: 0x24100, retries: 4, seq: 0x315E1F9, refcount: 1, rpc_result = 0x0, data_buffer = 0x5036F47C, header = 0x844B3C8, data = 0x844B3E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57849, sz: 772, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08E, lo: 0x844B3E8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 F2 00 0D 00 16 02 EC 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 01 46 0A 06 FE 5A 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
    Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.743: SW1_SP: IPC: Message 45279200 timed out waiting for Ack
    Jun 21 11:19:43.743: SW1_SP: IPC:  MSG: ptr: 0x45279200, flags: 0x24100, retries: 2, seq: 0x315E1FA, refcount: 1, rpc_result = 0x0, data_buffer = 0x5039C3B0, header = 0x85F65C8, data = 0x85F65E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57850, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B123, lo: 0x85F65E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
    Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45279200, flags: 0x24100, retries: 2, seq: 0x315E1FA, refcount: 1, rpc_result = 0x0, data_buffer = 0x5039C3B0, header = 0x85F65C8, data = 0x85F65E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57850, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B123, lo: 0x85F65E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
    Jun 21 11:19:43.747: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.747: SW1_SP: IPC: Message 504D3544 timed out waiting for Ack
    Jun 21 11:19:43.747: SW1_SP: IPC:  MSG: ptr: 0x504D3544, flags: 0x24100, retries: 2, seq: 0x315E1FB, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044AE34, header = 0x8C71FC8, data = 0x8C71FE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57851, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B124, lo: 0x8C71FE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 04 48 0A 06 0B 24 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
    Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504D3544, flags: 0x24100, retries: 2, seq: 0x315E1FB, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044AE34, header = 0x8C71FC8, data = 0x8C71FE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57851, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B124, lo: 0x8C71FE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 04 48 0A 06 0B 24 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
    Jun 21 11:19:43.747: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.747: SW1_SP: IPC: Message 504D5940 timed out waiting for Ack
    Jun 21 11:19:43.747: SW1_SP: IPC:  MSG: ptr: 0x504D5940, flags: 0x24100, retries: 2, seq: 0x315E1FC, refcount: 1, rpc_result = 0x0, data_buffer = 0x4521415C, header = 0x8CDD4C8, data = 0x8CDD4E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57852, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B125, lo: 0x8CDD4E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 0E 6D 0A 06 9C 5C 01 04 00 00 00 BF 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
    Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504D5940, flags: 0x24100, retries: 2, seq: 0x315E1FC, refcount: 1, rpc_result = 0x0, data_buffer = 0x4521415C, header = 0x8CDD4C8, data = 0x8CDD4E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57852, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B125, lo: 0x8CDD4E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 0E 6D 0A 06 9C 5C 01 04 00 00 00 BF 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
    Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.751: SW1_SP: IPC: Message 452989EC timed out waiting for Ack
    Jun 21 11:19:43.751: SW1_SP: IPC:  MSG: ptr: 0x452989EC, flags: 0x24100, retries: 2, seq: 0x315E1FD, refcount: 1, rpc_result = 0x0, data_buffer = 0x45172660, header = 0x86DCEC8, data = 0x86DCEE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57853, sz: 1060, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B126, lo: 0x86DCEE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 3E 0A 06 FE 1D 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 BF 00 00
    Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452989EC, flags: 0x24100, retries: 2, seq: 0x315E1FD, refcount: 1, rpc_result = 0x0, data_buffer = 0x45172660, header = 0x86DCEC8, data = 0x86DCEE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57853, sz: 1060, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B126, lo: 0x86DCEE8  || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 3E 0A 06 FE 1D 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 BF 00 00
    Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.751: SW1_SP: IPC: Message 504C9DAC timed out waiting for Ack
    Jun 21 11:19:43.751: SW1_SP: IPC:  MSG: ptr: 0x504C9DAC, flags: 0x24108, retries: 0, seq: 0x315E1FE, refcount: 1, rpc_result = 0x0, data_buffer = 0x451D3748, header = 0x8A772C8, data = 0x8A772E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57854, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D4, lo: 0x8A772E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 97 00 00
    Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504C9DAC, flags: 0x24108, retries: 0, seq: 0x315E1FE, refcount: 1, rpc_result = 0x0, data_buffer = 0x451D3748, header = 0x8A772C8, data = 0x8A772E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57854, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D4, lo: 0x8A772E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 97 00 00
    Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.751: SW1_SP: IPC: Message 4525926C timed out waiting for Ack
    Jun 21 11:19:43.751: SW1_SP: IPC:  MSG: ptr: 0x4525926C, flags: 0x24108, retries: 0, seq: 0x315E1FF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50405568, header = 0x89DD1C8, data = 0x89DD1E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57855, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D5, lo: 0x89DD1E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 80 0A 06 0B 24 01 04 00 00 00 8A 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
    Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4525926C, flags: 0x24108, retries: 0, seq: 0x315E1FF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50405568, header = 0x89DD1C8, data = 0x89DD1E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57855, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D5, lo: 0x89DD1E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 80 0A 06 0B 24 01 04 00 00 00 8A 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
    Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.755: SW1_SP: IPC: Message 452512E0 timed out waiting for Ack
    Jun 21 11:19:43.755: SW1_SP: IPC:  MSG: ptr: 0x452512E0, flags: 0x24108, retries: 0, seq: 0x315E200, refcount: 1, rpc_result = 0x0, data_buffer = 0x451AF00C, header = 0x891CCC8, data = 0x891CCE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57856, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D6, lo: 0x891CCE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C0 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0B 00 00 00 00 00 00 04 B2 0A 06 9E 0B 01 04 00 00 00 C3 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 17 00 00
    Jun 21 11:19:43.755: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452512E0, flags: 0x24108, retries: 0, seq: 0x315E200, refcount: 1, rpc_result = 0x0, data_buffer = 0x451AF00C, header = 0x891CCC8, data = 0x891CCE8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57856, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D6, lo: 0x891CCE8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C0 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0B 00 00 00 00 00 00 04 B2 0A 06 9E 0B 01 04 00 00 00 C3 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 17 00 00
    Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:43.755: SW1_SP: IPC: Message 504A9C90 timed out waiting for Ack
    Jun 21 11:19:43.755: SW1_SP: IPC:  MSG: ptr: 0x504A9C90, flags: 0x24108, retries: 0, seq: 0x315E201, refcount: 1, rpc_result = 0x0, data_buffer = 0x45158028, header = 0x85E22C8, data = 0x85E22E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57857, sz: 736, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D7, lo: 0x85E22E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 02 D0 00 0D 00 15 02 CA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 03 4E 0A 06 FE 4C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 C2 00 00
    Jun 21 11:19:43.755: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504A9C90, flags: 0x24108, retries: 0, seq: 0x315E201, refcount: 1, rpc_result = 0x0, data_buffer = 0x45158028, header = 0x85E22C8, data = 0x85E22E8  || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57857, sz: 736, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D7, lo: 0x85E22E8  || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 02 D0 00 0D 00 15 02 CA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 03 4E 0A 06 FE 4C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 C2 00 00
    Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:19:52.687: %CPU_MONITOR-SW1_SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 120 seconds [21/1]
    Jun 21 11:20:22.687: %CPU_MONITOR-SW1_SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 150 seconds [21/1]
    Jun 21 11:20:33.175: SW1_SP: IPC: Message 504F68E8 timed out waiting for Ack
    Jun 21 11:20:33.175: SW1_SP: IPC:  MSG: ptr: 0x504F68E8, flags: 0x34101, retries: 21, seq: 0x315AABD, refcount: 2, rpc_result = 0x0, data_buffer = 0x4517147C, header = 0x86D24C8, data = 0x86D24E8  || HDR: src: 0x10000, dst: 0x315000E, index: 1, seq: 43709, sz: 80, type: 1, flags: 0x1404, ext_flags: 0x0, hi: 0xA56AE85, lo: 0x86D24E8  || DATA: 00 00 00 15 00 00 00 00 00 00 07 D1 00 00 00 0A 00 00 00 0C 00 00 00 0F 00 00 00 05 00 00 00 0A 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    Jun 21 11:20:33.175: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504F68E8, flags: 0x34101, retries: 21, seq: 0x315AABD, refcount: 2, rpc_result = 0x0, data_buffer = 0x4517147C, header = 0x86D24C8, data = 0x86D24E8  || HDR: src: 0x10000, dst: 0x315000E, index: 1, seq: 43709, sz: 80, type: 1, flags: 0x1404, ext_flags: 0x0, hi: 0xA56AE85, lo: 0x86D24E8  || DATA: 00 00 00 15 00 00 00 00 00 00 07 D1 00 00 00 0A 00 00 00 0C 00 00 00 0F 00 00 00 05 00 00 00 0A 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    Jun 21 11:20:33.175: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
    Jun 21 11:20:33.179: %C6K_PROCMIB-SW1_SP-3-IPC_TRANSMIT_FAIL: Failed to send process statistics update : error code = timeout
    -Traceback= 40BF9E18 40BF9E68 40BFA070 40BFA2D4 408AAFE8 408AAFD4
    Jun 21 11:20:52.687: %CPU_MONITOR-SW1_SP-3-TIMED_OUT: CPU_MONITOR messages have failed, resetting system [21/1]

  • Why do I get %PIM-5-NBRCHG in the logs - 6509-E?

    Hello, I just had a look at the logs on a pair of 6509's with SUP-720-3B. They have a etherchannel between them (just standard basic campus config - with OSPF) and I get these so so frequently, fairly new to multicast arena so I have no idea why this is happening, could someone perhaps explain what is happening. Why would this just drop for 0.0.0.0 (itself, right?):
    6509-1
    May  2 21:23:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:23:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:24:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:24:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:24:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:24:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:25:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:25:16.705 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:25:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:25:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:26:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:26:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:26:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:26:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:27:16.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:27:16.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:27:46.697 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:27:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    6509-2
    May  2 21:34:16.700 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:34:16.704 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:34:46.701 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:34:46.705 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:35:16.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:35:16.717 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:35:46.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:35:46.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:36:16.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:36:16.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    May  2 21:36:46.709 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 UP on interface Vlan24
    May  2 21:36:46.713 BST: %PIM-5-NBRCHG: neighbor 0.0.0.0 DOWN on interface Vlan24 non DR
    It seems exactly every 30 seconds this happens. This is the config for vlan 24
    6509-1#show run int vlan 24
    Building configuration...
    Current configuration : 312 bytes
    interface Vlan24
    description *** Server VLAN***
    ip address 172.25.24.2 255.255.252.0
    ip helper-address 172.25.24.137
    ip helper-address 172.25.24.138
    ip directed-broadcast 110
    ip flow ingress
    ip flow egress
    ip pim sparse-mode
    standby 24 ip 172.25.24.1
    standby 24 priority 110
    standby 24 preempt
    end
    6509-2#show run int vlan 24
    Building configuration...
    Current configuration : 311 bytes
    interface Vlan24
    description *** Server VLAN***
    ip address 172.25.24.3 255.255.252.0
    ip helper-address 172.25.24.137
    ip helper-address 172.25.24.138
    ip directed-broadcast 110
    ip flow ingress
    ip flow egress
    ip pim sparse-mode
    standby 24 ip 172.25.24.1
    standby 24 priority 90
    standby 24 preempt
    end
    6509-1#show ip pim neighbor
    PIM Neighbor Table
    Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
          P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
    Neighbor          Interface                Uptime/Expires    Ver   DR
    Address                                                            Prio/Mode
    172.25.18.3       Vlan18                   29w4d/00:01:36    v2    1 / DR S P G
    172.25.24.3       Vlan24                   29w4d/00:01:32    v2    1 / DR S P G
    172.25.28.3       Vlan28                   29w4d/00:01:26    v2    1 / DR S P G
    172.25.32.3       Vlan32                   29w4d/00:01:40    v2    1 / DR S P G
    172.25.36.3       Vlan36                   29w4d/00:01:23    v2    1 / DR S P G
    172.25.40.3       Vlan40                   29w4d/00:01:43    v2    1 / DR S P G
    172.25.44.3       Vlan44                   29w4d/00:01:38    v2    1 / DR S P G
    172.25.48.3       Vlan48                   29w4d/00:01:41    v2    1 / DR S P G
    172.25.52.3       Vlan52                   29w4d/00:01:27    v2    1 / DR S P G
    172.25.56.3       Vlan56                   29w4d/00:01:22    v2    1 / DR S P G
    172.25.60.3       Vlan60                   29w4d/00:01:30    v2    1 / DR S P G
    172.25.64.3       Vlan64                   29w4d/00:01:21    v2    1 / DR S P G
    172.25.68.3       Vlan68                   29w4d/00:01:28    v2    1 / DR S P G
    172.25.72.3       Vlan72                   29w4d/00:01:28    v2    1 / DR S P G
    172.25.76.3       Vlan76                   29w4d/00:01:16    v2    1 / DR S P G
    172.25.84.3       Vlan84                   29w4d/00:01:30    v2    1 / DR S P G
    192.168.250.3     Vlan590                  10w1d/00:01:33    v2    1 / S P G
    192.168.250.6     Vlan590                  10w1d/00:01:35    v2    1 / DR S P G
    192.168.250.5     Vlan590                  10w1d/00:01:21    v2    1 / S P G
    192.168.240.6     Vlan592                  10w1d/00:01:21    v2    1 / DR S P G
    192.168.240.5     Vlan592                  15w5d/00:01:34    v2    1 / S P G
    192.168.240.3     Vlan592                  10w1d/00:01:16    v2    1 / S P G
    Thank you
    B
    Please rate useful posts and remember to mark any solved questions as answered. Thank you.       

    Hello Paul. Thanks for your reply.
    I may disagree that the neighbourship is dropping. I have assigned the RP statically and it is not one of the 6509s.
    All the other SVIs have the same thing as you can see from the neighbourship the PIM neighbours I.e. 6509-2 have been up for weeks including VLAN 24.
    Why is it only this VLAN 24 that I am getting these logs for?
    When there's a neighbourship change with another router, normally we see the address of the attached interface rather than 0.0.0.0. (This is what I have observed anyway)
    When we enable PIM sparse mode on an interface, we get the 0.0.0.0 if nothing is connected to the other side?
    I also don't understand why there would be consistency. Every 30 seconds or so?
    Thank you
    Sent from Cisco Technical Support iPhone App

  • What is the best way to trust DSCP values on 6509 interfaces?

    I have 6509's with 2 Ten-gig interfaces configured into a Port Channel (routed with IP addressing) - the IOS is 12.2(18)SXE3. I want to trust the DSCP values of packets traveling through the interfaces and have applied 'mls qos trust dscp' on both the physical Ten-gig interfaces as well as the L3 Port Channel interface.
    1.Is it necessary to have the statement on all the interfaces, or is just having it on the Port channel enough?
    Here is the config right now:
    interface Port-channel4
    description to 6509-Core-A P4 (T1/3, T2/3)
    ip address 164.xxx.xx.xx 255.255.255.252
    ip pim sparse-mode
    ip route-cache flow
    mls qos trust dscp
    interface TenGigabitEthernet1/1
    description to 6509-Core-A T1/3 (P4)
    no ip address
    ip route-cache flow
    mls qos trust dscp
    channel-group 4 mode desirable
    interface TenGigabitEthernet1/2
    description to 6509-Core-A T2/3 (P4)
    no ip address
    ip route-cache flow
    mls qos trust dscp
    channel-group 4 mode desirable
    Also, what command can I use to see the dscp counters? In the 3560/3750 catalyst line you can enter: 'sh mls qos int f0/1 statistics' and get a display of all the dscp/cos input/output packet counts, but I can't find a comparable command in the 6509.
    2. Is there one?

    I think you do this on the individual port interfaces, not the port-channel interface, becasue the queueing mechanisims associated with DSCP values are port based.
    By doing this, if you have policy maps you want to use, you attach them to the ports not the port-channel.
    For the command on 6509, you can use:
    sh mls qos ip gigabitEthernet 1/1
    Hope this helps and let me know how that works out.
    Gary

Maybe you are looking for

  • SQL Server Express hosting and EULA

    Hi, I have a (possibly stupid) question. I want to use SQL Server Express for hosting. It is for a small project and on a dedicated server, so I don't think there would be any problems with the limitation of express edition. However, I have run into

  • Automatic Down Payment clearing

    Dear All, We have activated the "Configure Automatic clearing of Down Payments". The down payment clearing document is posting at the time of Goods receipt and is consuming budget as an actual expenditure. At the time posting invoice, system is consu

  • Payment amount is greater than invoice amount error when doing AR CN

    Dear Experts, I am trying to post an AR CN on an AR Downpayment Invoice. This AR Downpayment Invoice has not been applied to its invoice yet, status is hence OPEN. I now go to AR CN and use Copy From function to browse for this AR Downpayment Invoice

  • Js, zero point in facing pages indd

    Hi, When I create my facing pages indd file, it only gives me one zero point for 2-page block. How can I change it to have two zero points - one for each page. I already have this, but it's not helping: myDoc.zeroPoint = [0,0]; Thank you.

  • Send string between JSP pages

    HI, how do I can use a variable String from one JSP to another JSP: example first.jsp (String mail_string="name@domain") second.jsp (I need the mail_string value)