Redundant Supervisors in a Dual-Core Catalyst 6500 network

Read the PDF doc called:
Designing a Campus Network for High Availability.
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns432/c649/cdccont_0900aecd801a8a2d.pdf
It essentially recommends that dual supervisors only be used in SPOF points - not in dual-distribution or dual-core switches.
The rationale is that a layer three routing protocol convergence (EIGRP for instance) only takes 60-200ms, but a supervisor failover using NSF and SSO takes up to 3 seconds.
In practice, I almost always see dual supervisors recommended in the core (and that's what I've recommended as well).
I can see keeping dual supervisors in the core because the customer may place a higher value on redundant hardware capability than an up to three second convergence, but I'd like to hear other rationales why dual supervisors should be used in a redundant core given the definite speed advantage of routing protco convergence over convergence following NSF/SSO failover.
Thanks,

In a completely clean textbook design where the cores are mirrors of each other and only provide transit between distribuition layers, NO, dual sups are not needed and will only slow convergence as the document indicates.
However, in some live environments this is not always the case, where the textbook does not reflect reality. One core switch can have a configuration or connection that the other core cannot backup. As much as people try to keep their cores clean and symetrical, a fast growing and underfunded network can quickly get messy with one-offs and bandaids that get forgotten about a few months later. In situations like these, having dual sups in the core provides the peace of mind and assurance that 3 seconds can buy (if you can afford it).
Please rate this post.
Thanks,
Brad

Similar Messages

  • Replacement catalyst 6500 switches under redundancy environment

    Hi everyone,
    I plan to replace old core catalyst 6500 switches with new ones for the purpose of reinforcement.
    Now two core catalyst 6500 switches are working under redundancy environment.
    There are many catalyst 6500 switches as distribution switch connect to each core catalyst
    6500 switches as attached.
    I think there are two ways to replace core catalyst 6500 switches.
    [One]
    Replacing one core catalyst 6500 switches first, then one week later, replacing another core
    catalyst 6500 switch. And all traffic will be handled another core catalyst 6500 switch automatically
    by EIGRP routing during replacement.
    Advantage:
    One another core catalyst 6500 switch continues operating even if the replacement fail.
    Disadvantage:
    Two core catalyst 6500 switches will operate in a different version (CatOS, MSFC IOS) for one week.
    Any problem might be happened due to this issue.
    [Two]
    Replacing both core catalyst 6500 switches at the same time.
    Advantage:
    Replacement will be finished at one time
    Disadvantage:
    If the replacement fail, whole network goes to down and it cause critical situation.
    I have to replace successfully so I would like know good information about this, such as
    best practice, case study and so on.
    Your information would be greatly appreciated.
    Best regards,

    Hi,
    If I were you, I will go for option 1.
    This option will give us the time to observe the traffic pattern, time to get the network and EIGRP to stabilize and even to check for any issues on the IOS part.
    This will give you time frame to work out for any issue if it happens in between the weeks time.This will gibe you tha time to see for any imcompatibilty issues as such.
    HTH, Please rate if it does.
    -amit singh

  • Monitoring dual core (Supervisor Engine 7-E) through EEM Script.

    Hi,
    I have a Cisco Catalyst 4500E Supervisor Engine 7-E and configured an EEM Script to monitor the dual core CPU Utilization through PRTG Network Monitor.
    event manager applet dualcore authorization bypass
    event timer cron cron-entry "* * * * 0-6"
    action 100 cli command "en"
    action 120 cli command "show process cpu | include five"
    action 220 regexp "Core 0: CPU utilization for five seconds: ([^%]+)%; one minute: ([^%]+)%; five minutes: ([^%]+)%.*" $_cli_result result c0cpu5sec c0cpu1min c0cpu5min
    action 240 if $_regexp_result eq 1
    action 260 end
    action 320 regexp "Core 1: CPU utilization for five seconds: ([^%]+)%; one minute: ([^%]+)%; five minutes: ([^%]+)%.*" $_cli_result result c1cpu5sec c1cpu1min c1cpu5min
    action 340 if $_regexp_result eq 1
    action 360 end
    action 440 cli command "config t"
    action 441 cli command "snmp mib expression owner cisco name c0cpu5sec"
    action 442 cli command "expression $c0cpu5sec"
    action 443 cli command "snmp mib expression owner cisco name c0cpu1min"
    action 444 cli command "expression $c0cpu1min"
    action 445 cli command "snmp mib expression owner cisco name c0cpu5min"
    action 446 cli command "expression $c0cpu5min"
    action 550 cli command "config t"
    action 551 cli command "snmp mib expression owner cisco name c1cpu5sec"
    action 552 cli command "expression $c1cpu5sec"
    action 553 cli command "snmp mib expression owner cisco name c1cpu1min"
    action 554 cli command "expression $c1cpu1min"
    action 555 cli command "snmp mib expression owner cisco name c1cpu5min"
    action 556 cli command "expression $c1cpu5min"
    action 600 cli command "end"
    end
    It works fine but on the logging buffer there are a lot of %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:moncores) messages   -one per minute-   here an example:
    Oct 29 17:54:01: %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:dualcore)
    Oct 29 17:55:01: %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:dualcore)
    Oct 29 17:56:01: %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:dualcore)
    Oct 29 17:57:01: %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:dualcore)
    I considered to use the logging suppress duplicates command to prevent the consecutive logging of more than one copy of the same system logging (syslog) message but it is only available to the Cisco IOS XR.
    Someone could help me to determine if it is possible to avoid this messages through Embedded Syslog Manager, I tried to do that but
    I was not successful.
    Regards,
    ~Sergio

    Hi,
    I did transitioned CLI actions to the EXPRESSION-MIB SNMP but I could not receive anything information about the dualcore utilization on the PRTG Network Monitor and received a lot of  %HA_EM-7-FMFD_SNMP_ERRCODE: fh_fd_snmp_errcode: Error status: 6 NO_ACCESS_ERROR: 1. messages on the WS-C4507.
    Considering the initial EEM script, could ypu help me to avoid the  %SYS-5-CONFIG_I: Configured from console by  on vty0 (EEM:moncores)
    messages using Embedded Syslog Manager.
    Here some snmpwalk to validate that I could not get the OIDs to monitor both cores.
    STEP 1     Only one value is given because there is only one physical cpu.
    cpmCPUTotalPhysicalIndex
    1.3.6.1.4.1.9.9.109.1.1.1.1.2
    C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.4.1.9.9.109.1.1.1.1.2
    SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.4000 = INTEGER: 4000
    STEP 2
    entPhysicalName
    1.3.6.1.2.1.47.1.1.1.1.7
    C:\usr>
    C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.47.1.1.1.1.7.4000
    SNMPv2-SMI::mib-2.47.1.1.1.1.7.4000 = STRING: "Linecard(slot 4)"
    #sh mod
    Chassis Type : WS-C4507R+E
    Power consumed by backplane : 40 Watts
    Mod Ports Card Type                              Model              Serial No.
    ---+-----+--------------------------------------+------------------+-----------
    1    18  10GE (X2), 1000BaseX (SFP)             WS-X4606-X2-E      JAE151904JC
    2    24  1000BaseX (SFP)                        WS-X4624-SFP-E     JAE152001AE
    4     4  Sup 7-E 10GE (SFP+), 1000BaseX (SFP)   WS-X45-SUP7-E      CAT1522L0G1
    5    48  10/100/1000BaseT (RJ45)V, Cisco/IEEE   WS-X4548-GB-RJ45V  JAE12067N8K
    M MAC addresses                    Hw  Fw           Sw               Status
    --+--------------------------------+---+------------+----------------+---------
    1 e8b7.4880.e5db to e8b7.4880.e5ec 1.2                               Ok      
    2 e8b7.48cc.6167 to e8b7.48cc.617e 1.2                               Ok      
    4 4055.39d7.76c4 to 4055.39d7.76c7 1.0 15.0(1r)SG2  03.01.01.SG      Ok      
    5 001e.f7da.d290 to 001e.f7da.d2bf 4.1                               Ok      
    Mod  Redundancy role     Operating mode      Redundancy status
    ----+-------------------+-------------------+----------------------------------
    4   Active Supervisor   SSO                 Active                           
    STEP 3
    cpmCPUTotal1minRev
    1.3.6.1.4.1.9.9.109.1.1.1.1.7
    C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.4.1.9.9.109.1.1.1.1.7
    SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.7.4000 = Gauge32: 9
    C:\usr>
    ADDITIONAL INFORMATION
    C:\usr>
    C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.90
    SNMPv2-SMI::mib-2.90.1.1.1.0 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.1.2.0 = Gauge32: 0
    SNMPv2-SMI::mib-2.90.1.1.3.0 = Gauge32: 0
    SNMPv2-SMI::mib-2.90.1.1.4.0 = Gauge32: 0
    SNMPv2-SMI::mib-2.90.1.1.5.0 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = STRING: "9"
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = STRING: "11"
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = STRING: "8"
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = STRING: "13"
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = STRING: "13"
    SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = STRING: "11"
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 1
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = ""
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = OID: SNMPv2-SMI::zeroDotZero
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = Counter32: 0
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 2
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 2
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 2
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 2
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 2
    SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 2
    C:\usr>
    C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.47.1.1.1.1.2
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1 = STRING: "Cisco Systems, Inc. WS-C4507R+E 7 sl
    ot switch "
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.3 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.6 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.7 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.8 = STRING: "WS-C4507R+E 7 slot switch chassis sl
    ot"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.9 = STRING: " WS-C4507R+E 7 slot switch backplane
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.10 = STRING: "Container of Fan Tray"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.11 = STRING: "FanTray"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.12 = STRING: "Container of Container of Power Sup
    ply"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.13 = STRING: "Container of Power Supply"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.14 = STRING: "Power Supply ( AC 2800W )"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.15 = STRING: "Power Supply Fan Sensor"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.16 = STRING: "Container of Power Supply"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.19 = STRING: "Clock Module"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.20 = STRING: "Mux Buffers for Redundancy Logic"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.21 = STRING: "Mux Buffers for Redundancy Logic"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.22 = STRING: "Mux Buffers for Redundancy Logic"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.23 = STRING: "Mux Buffers for Redundancy Logic"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.24 = STRING: "Mux Buffers for Redundancy Logic"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1000 = STRING: "10GE (X2), 1000BaseX (SFP) with 6
    10GE X2 ports"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1001 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1002 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1003 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1004 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1005 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.1006 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2000 = STRING: "1000BaseX (SFP) with 24 SFP Ports
    Jumbo Frame Support"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2001 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2002 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2003 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2004 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2005 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2006 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2007 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2008 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2009 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2010 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2011 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2012 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2013 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2014 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2015 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2016 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2017 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2018 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2019 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2020 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2021 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2022 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2023 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2024 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2047 = STRING: "1000BaseSX"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.2048 = STRING: "1000BaseSX"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4000 = STRING: "Sup 7-E 10GE (SFP+), 1000BaseX (S
    FP) with 4 SFP+ Ports"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4001 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4002 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4003 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.4004 = STRING: "Port Container"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5000 = STRING: "10/100/1000BaseT (RJ45)V with 48
    10/100/1000 baseT voice power ports (Cisco/IEEE)"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5001 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5002 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5003 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5004 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5005 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5006 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5007 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5008 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5009 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5010 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5011 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5012 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5013 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5014 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5015 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5016 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5017 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5018 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5019 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5020 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5021 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5022 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5023 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5024 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5025 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5026 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5027 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5028 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5029 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5030 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5031 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5032 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5033 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5034 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5035 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5036 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5037 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5038 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5039 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5040 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5041 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5042 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5043 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5044 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5045 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5046 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5047 = STRING: "Gigabit Ethernet Port"
    SNMPv2-SMI::mib-2.47.1.1.1.1.2.5048 = STRING: "Gigabit Ethernet Port"
    C:\usr>

  • Cisco Catalyst 6500 Supervisor Engine 2T Baseboard

    Morning Guys
    i have just bought a Cisco 6506-E Chassis, it came out with only the SUP2T Engine on slot 5, i have already stacked 3 switches (3750-X) as my core, i want to replace them with the chassis the problem now is my company doesn't have money to buy the 48 port switch and the fibre switch for the chassis, help me link the SUP2T Engine with the stack and improve my network. i also have the 12 port netgear fibre switch. help with the configuration.

    You obviously need to configure the ports etc. but the switch should recognise the module as long as you have an IOS that supports it.
    There is nothing extra to do, you just slot the module in.
    If you are connecting all your distribution switches to the 6500 then if you don't need a vlan/IP subnet in multiple buildings then you should use L3 connections to the 6500.
    Note also that you may want to consider at some time in the future a second supervisor or another chassis as this 6500 with one supervisor is a single point of failure ie. if it goes then there is no communication between buildings.
    Jon

  • Catalyst 6500 - supervisor ports availability

    We have a Catalyst 6509 with redundant supervisor 32 with 8 portGbic SFP.
    The version of CatOs is 8.4.5 and MSFC IOS 12.2.17d-SXB11.
    The problem is that when the active supervisor reset and the standby supervisor becomes active, the 8Gbit links on the previous active supervisor go down till the resetting supervisor finish the reboot.

    I don't connect anything particular on these ports.
    The only thing that annoy me is that the devices attached on these ports aren't available in case of supervisor switch-over, till the "rebooting" sup32 booting sequence is ended, which is about 2 minutes.
    Which means that if I don't want any interrupted service on the sup32 ports, I have to double the links, one on each supervisor.
    regards

  • After upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T to the latest release the ASA-SM module is not recognized

    after upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T to the latest release the ASA-SM module is not recognized it is disabled. the FPD
    is not recognized any more. reverted back to previous ios with no luck

    Duplicate post.
    Being discussed actively in this thread.

  • After upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T ASA-SM is disabled

    after upgrading ios Cisco Catalyst 6500 Series Supervisor Engine 2T to the latest release the ASA-SM module is not recognized it is disabled. the FPD
    is not recognized any more.  reverted back to previous ios with no luck

    What IOS are you running on your Supervisor 2T? As long as it's 15.0(1)SY1 or later you should be OK. (Reference).
    If it's not working with that I'd try reload of the ASA SM module (from IOS cli - e.g. "hw-module <module#> reset" and, failing that, "no power-enable module <module#>" followed by "power-enable module <module#>) while the new Supervisor is installed. Watch the log for relevant messages during that process.

  • 15.1(2)SY1 on Catalyst 6500

    Hi,
    We are planning to upgrade two of our Catalyst 6500 switches to version 15.1(2)SY1 Advanced IP Services.
    The switches have dual supervisors and are currently running version 12.2(33)SXI11, but we have faced some issues and also would also like to enable some new features (e.g. BFD). The switches are running a fairly simple configuration with OSPF, MPLS and MP-BGP with about 30 VRFs.
    Are you aware of any major issues with 15.1(2)SY1 and would discourage the planned upgrade? I am aware that the version was only released in December, but since there are many bug fixes I thought this version might be better than e.g. 15.1(2)SY.
    Thanks in advance for your help!
    Best regards,
    Harry

    We replaced all (~ x20) our Sup720 (SXI4a) with Sup2T during late 2012 & running with Advance Enterprise 15.0(1)SY image. We did not have any issues with that code & still many of our distribution switches running on that code.
    Then we upgraded two core switches with 15.1(1)SY mid last year another two core switches to 15.1(2)SY late last year to accomodate WS-X6904-40G. With both of these new code we had couple of bugs still not proper fix
    CSCue58955: sup2t: LC file systems are not destroyed in Active upon reset"%SNMP-3-INPUT_QFULL_ERR: Packet dropped
    There is workaround for this, but that will impact netflow data if you are using that.
    For me 15.0(1)SY, is much better for Enterprise environment (based on my experience) compare to the two latest. But due to certain limitation we have to go for this newer codes whether you like it or not.
    These bugs may be not related to you if you are not runing Sup2T, anyway just thought to share this experience
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • How to remove the WiSM2 from the Catalyst 6500 series switch?

    Hello, can you explain to me how to safely remove the WiSM2 from the Catalyst 6500 series switch?
    According to the documentation "Catalyst 6500 Series Wireless Services Module 2 Installation and Verification Note":
    To remove the WiSM2, perform these steps:
    Step1     Shut down the module by one of these methods:
    In privileged mode from the router prompt, enter the hw-mod module mod shutdown command. NoteIf you enter this command to shut down the module, you must enter the following commands in global configuration mode to restart (power down, and then power up) the module:
    Router# no power enable module modRouter# power enable module mod
    If the module does not respond to any commands, press the SHUTDOWN button located on the front panel of the module.
    Step2     Verify that the WiSM2 shuts down. Do not remove the module from the switch until the POWER LEDis off.
    But, in the case of Step1 (1st methods) I do not see a option "shutdown"  in the command "hw-mod module 3"...
    All I prompted to enter is:
    c6500#hw-module module 3 ?
    boot           Specify boot options for the module through Power Management Bus control register
    reset          Reset specified component
    simulate  Simulate options for the module
    Is it hidden options? IOS version of c6500 is 12.2(33)SXJ1
    In the case of Step2 (2nd methods) there is not any button on the front panel of the module?
    And yet, it is better to remove the module configuration manually or use the command module clear-config prior to removing the module?

    Good catch.
    Which one is true, will get back to you on this if i've something soon.
    http://www.cisco.com/en/US/docs/wireless/module/wism2/installation/note/WiSM_2.html#wp34727
    The above link is procedure to remove wism2. This procedure doesn’t look like wism2 is hot swapable.
    http://www.cisco.com/en/US/docs/wireless/module/wism2/installation/note/WiSM_2.html#wp34621
    All modules, including the supervisor engine (if you have redundant supervisor engines), support hot swapping. You can add, replace, or remove modules without interrupting the system power or causing other software or interfaces to shut down. For more information about hot-swapping modules, see the Catalyst 6500 Series Switch Module Installation Guide.

  • Connecting routers to dual "core" switches

    At the core of my network I have pair of Catalyst 6509s with Sup720s. These are configured with a number of VLANs spread across both switches, using VRRP for fail-over. Servers with dual NICs are connected to both switches, providing a reasonable degree of redundancy. Likewise, my "edge" switches have dual dot1q trunk uplinks to both switches. PVST is configured. The idea is that the loss of one switch won't bring the whole network down. So far, so good.
    What I now want to do is connect some new 3845 routers in a similarly redundant way. I want to connect Gi0/0 to a port on Switch1, and Gi0/1 to Switch2, so that both switches have a direct connection to the router (which then handles a T3 link to another office, for example).
    Initially I thought I could just configure a port on the 6509 with an IP address and make point to point links to the 3845, and let OSPF worry about the routing - but the Sup720 doesn't let me do that with a switch port. I considered making the links dot1q trunks, but then where would I set IP addresses on the router? At the subinterface level? When I try that, it complains about overlapping networks on different interfaces.
    I'm looking for some sample configs or "best practice" advice, or specific pointers to documents on cisco.com that might explain how I should go about this. Unfortunately searches (on cisco.com or google) return just Too Much Information - it's like trying to drink from a fire hose. Any pointers would be appreciated!

    Hi Mcreilly,
    You should be able to assign an ip address on cat6k sup720 if you are running native ios on sup 720.
    If you are running catos then you will not be able to do that and you can have it configured as trunk and connect to the router.Also I do not think that you need subinterfaces on router and trunk on switch because your cat6k with sup720 must be doing intervlan routing between vlans.
    You can just connect it on some port on any vlan and same subnet ip address which you have it on msfc for that vlan you can assign on the router interface and anybody want to go out via t3 link will get routes on sup720 and move out via router vlan.
    For suppose you do not want the router to be part of existing vlan you can create one vlan on cat6k sup720 and assign one port to that new vlan and connect the royter to that new vlan port and then create logical interface on msfc for that new vlan and assign an ip address range on that logical vlan and same subnet ip address range you can assign on router physical interface.
    Any one from other vclan get routed on sup 720 msfc and will move out via the vlan on which you have connected the router.
    because you have only one router you will not be able to maintain box level redundancy by which i mean if the router goes down t3 will be unreachable.
    HTH
    Ankur

  • QoS on Catalyst 6500

    We have the following QoS config running on Edge, Distributions and Cores and got the following error.
    “priority command is not supported in output direction for this interface
    Configuration failed on: Port-channel”
    We had opened a TAC case and they said ” PFC QoS does not support these policy map class commands:
    bandwidth
    priority
    queue-limit
    random-detect
    set qos-group
    service-policy
    How can we prioritize voip traffic. On our monitoring application, it says queues empty. Even if the priority command is not working there should be traffic in the queue.Different version of supervisors in Distribution (sup720) and COREs (Sup2).
    Any suggestions? Attached document gives Config details.

    Are your Access Layer switches also 6500s? What Supervisor(s) are running in your 6500s & what CatOS or CatIOS are you running?
    It sounds like you are redefining your trust boundary at every layer (Access, Distribution, Core). Did you get a chance to look over this SRND document?
    http://www.cisco.com/application/pdf/en/us/guest/netsol/ns432/c649/ccmigration_09186a008049b062.pdf
    Here's an example of our L2 6513 with a WS-X6724 which has 1p3q8t for QoS Scheduling:
    interface GigabitEthernet1/2
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    no ip address
    logging event link-status
    logging event bundle-status
    logging event trunk-status
    wrr-queue bandwidth 5 25 70
    wrr-queue queue-limit 5 25 40
    wrr-queue random-detect min-threshold 1 80 100 100 100 100 100 100 100
    wrr-queue random-detect min-threshold 2 80 100 100 100 100 100 100 100
    wrr-queue random-detect min-threshold 3 50 60 70 80 90 100 100 100
    wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100
    wrr-queue random-detect max-threshold 2 100 100 100 100 100 100 100 100
    wrr-queue random-detect max-threshold 3 60 70 80 90 100 100 100 100
    wrr-queue cos-map 1 1 1
    wrr-queue cos-map 2 1 0
    wrr-queue cos-map 3 1 4
    wrr-queue cos-map 3 2 2
    wrr-queue cos-map 3 3 3
    wrr-queue cos-map 3 4 6
    wrr-queue cos-map 3 5 7
    priority-queue cos-map 1 5
    udld port
    mls qos trust dscp
    rmon collection stats 6001 owner monitor
    channel-group 2 mode desirable non-silent
    interface Port-channel2
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    no ip address
    mls qos trust dscp
    We also use NetMRI and you're correct, because the Cat 6500 PFC performs classification, marking, mapping, and policing functions, but the queuing and dropping policies are administered by the line cards, there are no MIBs for NetMRI to poll.
    HTH
    Steve

  • Dual Core, but just one recognized [SOLVED]

    In the last days I had problems with my computer just going off randomly after some time... As I found out the CPU fan was too loose... Now I somehow fastened it so it seems to work normally now.
    Today I noticed (I'm not sure whether it's now the first time or I just didn't see it) that on booting I see just one Arch logo, although I have a Dual Core processor and normally there are 2 logos... I checked whether GRUB has the option nosmp set which was not the case. cat /proc/cpuinfo gave me just one core.. Then I tried to boot the arch live cd (the 2008.06) and cpuinfo had both there!
    The BIOS says that there are still 2 as well... so my first idea, that one core is broken because of overheating seems to be wrong, it's impossible that just one core breaks, doesn't it?
    So my question is - how do I get my core to be recognized again? I have the new 2.6.29 kernel.. could this be the problem?
    My second question is - the information about launching daemons on booting appears AFTER showing the login prompt (I login via tty) [EDIT: This had to do with the OpenNTPD daemon...]
    Last edited by icetonic (2009-04-16 15:46:27)

    Linux version 2.6.29-ARCH (root@T-POWA-LX) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Wed Apr 8 12:47:56 UTC 2009
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007ffc0000 (usable)
    BIOS-e820: 000000007ffc0000 - 000000007ffce000 (ACPI data)
    BIOS-e820: 000000007ffce000 - 000000007fff0000 (ACPI NVS)
    BIOS-e820: 000000007fff0000 - 0000000080000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
    BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
    DMI present.
    AMI BIOS detected: BIOS may corrupt low RAM, working around it.
    last_pfn = 0x7ffc0 max_arch_pfn = 0x100000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009fc00 (usable)
    modified: 000000000009fc00 - 00000000000a0000 (reserved)
    modified: 00000000000e4000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000007ffc0000 (usable)
    modified: 000000007ffc0000 - 000000007ffce000 (ACPI data)
    modified: 000000007ffce000 - 000000007fff0000 (ACPI NVS)
    modified: 000000007fff0000 - 0000000080000000 (reserved)
    modified: 00000000fec00000 - 00000000fec01000 (reserved)
    modified: 00000000fee00000 - 00000000fef00000 (reserved)
    modified: 00000000ffb80000 - 0000000100000000 (reserved)
    kernel direct mapping tables up to 377fe000 @ 10000-15000
    RAMDISK: 7ff24000 - 7ffafb9e
    Allocated new RAMDISK: 00011000 - 0009cb9e
    Move RAMDISK from 000000007ff24000 - 000000007ffafb9d to 00011000 - 0009cb9d
    ACPI: RSDP 000FB800, 0024 (r2 ACPIAM)
    ACPI: XSDT 7FFC0100, 0054 (r1 HYRSLP HYRSLPTB 9000706 MSFT 97)
    ACPI: FACP 7FFC0290, 00F4 (r3 A_M_I_ OEMFACP 9000706 MSFT 97)
    FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
    ACPI: DSDT 7FFC05C0, 659A (r1 A0904 A0904000 0 INTL 20051117)
    ACPI: FACS 7FFCE000, 0040
    ACPI: MCFG 7FFC0400, 003C (r1 A_M_I_ OEMMCFG 9000706 MSFT 97)
    ACPI: SLIC 7FFC0440, 0176 (r1 HYRSLP HYRSLPTB 9000706 MSFT 97)
    ACPI: OEMB 7FFCE040, 0060 (r1 A_M_I_ AMI_OEM 9000706 MSFT 97)
    ACPI: HPET 7FFC6B60, 0038 (r1 A_M_I_ OEMHPET0 9000706 MSFT 97)
    ACPI: SSDT 7FFC6BA0, 0206 (r1 A_M_I_ POWERNOW 1 AMD 1)
    1159MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 00000000 - 377fe000
    bootmap 005ac000 - 005b2f00
    (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0000100000 - 00005a8584] TEXT DATA BSS ==> [0000100000 - 00005a8584]
    #4 [00005a9000 - 00005ac000] INIT_PG_TABLE ==> [00005a9000 - 00005ac000]
    #5 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
    #6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
    #7 [0000011000 - 000009cb9e] NEW RAMDISK ==> [0000011000 - 000009cb9e]
    #8 [00005ac000 - 00005b3000] BOOTMAP ==> [00005ac000 - 00005b3000]
    found SMP MP-table at [c00ff780] 000ff780
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x0007ffc0
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007ffc0
    On node 0 totalpages: 524111
    free_area_init_node: node 0, pgdat c0431600, node_mem_map c1000200
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3951 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 2320 pages used for memmap
    HighMem zone: 294578 pages, LIFO batch:31
    Detected use of extended apic ids on hypertransport bus
    ACPI: PM-Timer IO Port: 0x508
    ACPI: No APIC-table, disabling MPS
    ACPI: HPET id: 0x10de8201 base: 0xfed00000
    SMP: Allowing 1 CPUs, 0 hotplug CPUs
    Found and enabled local APIC!
    nr_irqs_gsi: 16
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
    PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
    Allocating PCI resources starting at 88000000 (gap: 80000000:7ec00000)
    NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:1 nr_node_ids:1
    PERCPU: Allocating 36864 bytes of per cpu data
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520015
    Kernel command line: root=/dev/disk/by-uuid/206cc51d-0ece-4693-a6cc-156428ba637f resume=/dev/sda5 ro vga=792 noapic
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 16384 bytes)
    Extended CMOS year: 2000
    Fast TSC calibration using PIT
    Detected 2109.362 MHz processor.
    spurious 8259A interrupt: IRQ7.
    Console: colour dummy device 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Memory: 2073012k/2096896k available (2369k kernel code, 22620k reserved, 1056k data, 356k init, 1187592k highmem)
    virtual kernel memory layout:
    fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc045f000 - 0xc04b8000 ( 356 kB)
    .data : 0xc03507cf - 0xc0458a88 (1056 kB)
    .text : 0xc0100000 - 0xc03507cf (2369 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    hpet clockevent registered
    HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Calibrating delay loop (skipped), value calculated using timer frequency.. 4220.50 BogoMIPS (lpj=7031206)
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    using C1E aware idle routine
    Checking 'hlt' instruction... OK.
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 10k freed
    ACPI: Core revision 20081204
    ACPI: Checking initramfs for custom DSDT
    ACPI Error (dswload-0239): Invalid type (Alias) for target of Scope operator [\._P] (Cannot override) [20081204]
    ACPI Exception (psloop-0227): AE_AML_OPERAND_TYPE, During name lookup/catalog [20081204]
    ACPI: setting ELCR to 0200 (from 8c00)
    weird, boot CPU (#0) not listed by the BIOS.
    SMP motherboard not detected.
    SMP disabled
    Brought up 1 CPUs
    Total of 1 processors activated (4220.50 BogoMIPS).
    net_namespace: 1016 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: Not using MMCONFIG.
    PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=4
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using PIC for interrupt routing
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
    PCI: Using MMCONFIG for extended config space
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:01.0: reg 10 io port: [0x900-0x9ff]
    pci 0000:00:01.1: reg 10 io port: [0xdc00-0xdc3f]
    pci 0000:00:01.1: reg 20 io port: [0x600-0x63f]
    pci 0000:00:01.1: reg 24 io port: [0x700-0x73f]
    pci 0000:00:01.1: PME# supported from D3hot D3cold
    pci 0000:00:01.1: PME# disabled
    pci 0000:00:02.0: reg 10 32bit mmio: [0xdbfff000-0xdbffffff]
    pci 0000:00:02.0: supports D1 D2
    pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:02.1: reg 10 32bit mmio: [0xdbffec00-0xdbffecff]
    pci 0000:00:02.1: supports D1 D2
    pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:02.1: PME# disabled
    pci 0000:00:05.0: reg 10 32bit mmio: [0xdbff8000-0xdbffbfff]
    pci 0000:00:05.0: PME# supported from D3hot D3cold
    pci 0000:00:05.0: PME# disabled
    pci 0000:00:06.0: reg 20 io port: [0xffa0-0xffaf]
    pci 0000:00:07.0: reg 10 32bit mmio: [0xdbffd000-0xdbffdfff]
    pci 0000:00:07.0: reg 14 io port: [0xd480-0xd487]
    pci 0000:00:07.0: supports D1 D2
    pci 0000:00:07.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:07.0: PME# disabled
    pci 0000:00:08.0: reg 10 io port: [0xd400-0xd407]
    pci 0000:00:08.0: reg 14 io port: [0xd080-0xd083]
    pci 0000:00:08.0: reg 18 io port: [0xd000-0xd007]
    pci 0000:00:08.0: reg 1c io port: [0xcc00-0xcc03]
    pci 0000:00:08.0: reg 20 io port: [0xc880-0xc88f]
    pci 0000:00:08.0: reg 24 32bit mmio: [0xdbffc000-0xdbffcfff]
    pci 0000:00:09.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:09.0: PME# disabled
    pci 0000:00:0b.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:0b.0: PME# disabled
    pci 0000:00:0c.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:0c.0: PME# disabled
    pci 0000:00:04.0: transparent bridge
    pci 0000:02:00.0: reg 10 32bit mmio: [0xdf000000-0xdfffffff]
    pci 0000:02:00.0: reg 14 64bit mmio: [0xc0000000-0xcfffffff]
    pci 0000:02:00.0: reg 1c 64bit mmio: [0xdc000000-0xddffffff]
    pci 0000:02:00.0: reg 24 io port: [0xec00-0xec7f]
    pci 0000:02:00.0: reg 30 32bit mmio: [0xdefe0000-0xdeffffff]
    pci 0000:00:09.0: bridge io port: [0xe000-0xefff]
    pci 0000:00:09.0: bridge 32bit mmio: [0xdc000000-0xdfffffff]
    pci 0000:00:09.0: bridge 64bit mmio pref: [0xc0000000-0xcfffffff]
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR11._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR12._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNEA] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNEB] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNEC] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LNED] (IRQs 7 10 *11 14)
    ACPI: PCI Interrupt Link [LUB0] (IRQs 7 10 *11 14)
    ACPI: PCI Interrupt Link [LUB2] (IRQs 7 *10 11 14)
    ACPI: PCI Interrupt Link [LMAC] (IRQs 7 10 *11 14)
    ACPI: PCI Interrupt Link [LAZA] (IRQs 7 10 *11 14)
    ACPI: PCI Interrupt Link [LACI] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LMC9] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LSMB] (IRQs 7 *10 11 14)
    ACPI: PCI Interrupt Link [LPMU] (IRQs 7 10 11 14) *0, disabled.
    ACPI: PCI Interrupt Link [LSA0] (IRQs *15)
    ACPI: PCI Interrupt Link [LSA1] (IRQs 5) *0, disabled.
    ACPI: PCI Interrupt Link [LATA] (IRQs 7 10 11 14) *0, disabled.
    ACPI Warning (tbutils-0242): Incorrect checksum in table [OEMB] - 08, should be 03 [20081204]
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:06: io resource (0x900-0x97f) overlaps 0000:00:01.0 BAR 0 (0x900-0x9ff), disabling
    pnp 00:06: io resource (0x980-0x9ff) overlaps 0000:00:01.0 BAR 0 (0x900-0x9ff), disabling
    pnp: PnP ACPI: found 15 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:06: ioport range 0xa30-0xa37 has been reserved
    system 00:06: ioport range 0x4d0-0x4d1 has been reserved
    system 00:06: ioport range 0x800-0x80f has been reserved
    system 00:06: ioport range 0x500-0x57f has been reserved
    system 00:06: ioport range 0x580-0x5ff has been reserved
    system 00:06: ioport range 0x800-0x87f could not be reserved
    system 00:06: ioport range 0x880-0x8ff has been reserved
    system 00:06: ioport range 0xd00-0xd7f has been reserved
    system 00:06: ioport range 0xd80-0xdff has been reserved
    system 00:06: ioport range 0x2000-0x207f has been reserved
    system 00:06: ioport range 0x2080-0x20ff has been reserved
    system 00:06: iomem range 0xfefe0000-0xfefe01ff has been reserved
    system 00:06: iomem range 0xfefe1000-0xfefe1fff has been reserved
    system 00:06: iomem range 0xfee01000-0xfeefffff has been reserved
    system 00:06: iomem range 0xffb80000-0xffffffff has been reserved
    system 00:06: iomem range 0xff300000-0xff3fffff has been reserved
    system 00:08: iomem range 0xfec00000-0xfec00fff has been reserved
    system 00:08: iomem range 0xfee00000-0xfee00fff has been reserved
    system 00:0b: ioport range 0x230-0x23f has been reserved
    system 00:0b: ioport range 0x290-0x29f has been reserved
    system 00:0b: ioport range 0xa00-0xa0f has been reserved
    system 00:0b: ioport range 0xa10-0xa1f has been reserved
    system 00:0d: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:0e: iomem range 0x0-0x9ffff could not be reserved
    system 00:0e: iomem range 0xc0000-0xcffff could not be reserved
    system 00:0e: iomem range 0xe0000-0xfffff could not be reserved
    system 00:0e: iomem range 0x100000-0x7fffffff could not be reserved
    system 00:0e: iomem range 0xff780000-0xffffffff could not be reserved
    pci 0000:00:04.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:04.0: IO window: disabled
    pci 0000:00:04.0: MEM window: disabled
    pci 0000:00:04.0: PREFETCH window: disabled
    pci 0000:00:09.0: PCI bridge, secondary bus 0000:02
    pci 0000:00:09.0: IO window: 0xe000-0xefff
    pci 0000:00:09.0: MEM window: 0xdc000000-0xdfffffff
    pci 0000:00:09.0: PREFETCH window: 0x000000c0000000-0x000000cfffffff
    pci 0000:00:0b.0: PCI bridge, secondary bus 0000:03
    pci 0000:00:0b.0: IO window: disabled
    pci 0000:00:0b.0: MEM window: disabled
    pci 0000:00:0b.0: PREFETCH window: disabled
    pci 0000:00:0c.0: PCI bridge, secondary bus 0000:04
    pci 0000:00:0c.0: IO window: disabled
    pci 0000:00:0c.0: MEM window: disabled
    pci 0000:00:0c.0: PREFETCH window: disabled
    pci 0000:00:04.0: setting latency timer to 64
    pci 0000:00:09.0: setting latency timer to 64
    pci 0000:00:0b.0: setting latency timer to 64
    pci 0000:00:0c.0: setting latency timer to 64
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
    pci_bus 0000:01: resource 0 mem: [0x0-0x0]
    pci_bus 0000:01: resource 1 mem: [0x0-0x0]
    pci_bus 0000:01: resource 2 mem: [0x0-0x0]
    pci_bus 0000:01: resource 3 io: [0x00-0xffff]
    pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
    pci_bus 0000:02: resource 0 io: [0xe000-0xefff]
    pci_bus 0000:02: resource 1 mem: [0xdc000000-0xdfffffff]
    pci_bus 0000:02: resource 2 mem: [0xc0000000-0xcfffffff]
    pci_bus 0000:02: resource 3 mem: [0x0-0x0]
    pci_bus 0000:03: resource 0 mem: [0x0-0x0]
    pci_bus 0000:03: resource 1 mem: [0x0-0x0]
    pci_bus 0000:03: resource 2 mem: [0x0-0x0]
    pci_bus 0000:03: resource 3 mem: [0x0-0x0]
    pci_bus 0000:04: resource 0 mem: [0x0-0x0]
    pci_bus 0000:04: resource 1 mem: [0x0-0x0]
    pci_bus 0000:04: resource 2 mem: [0x0-0x0]
    pci_bus 0000:04: resource 3 mem: [0x0-0x0]
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 558k freed
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: overridden by ACPI.
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1239902785.206:1): initialized
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1732
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:00:00.0: Found enabled HT MSI Mapping
    pci 0000:02:00.0: Boot video device
    pcieport-driver 0000:00:09.0: setting latency timer to 64
    pcieport-driver 0000:00:09.0: irq 16 for MSI/MSI-X
    pcieport-driver 0000:00:0b.0: setting latency timer to 64
    pcieport-driver 0000:00:0b.0: irq 17 for MSI/MSI-X
    pcieport-driver 0000:00:0c.0: setting latency timer to 64
    pcieport-driver 0000:00:0c.0: irq 18 for MSI/MSI-X
    vesafb: framebuffer at 0xdd000000, mapped to 0xf8080000, using 6144k, total 14336k
    vesafb: mode is 1024x768x32, linelength=4096, pages=1
    vesafb: protected mode interface info at c000:b470
    vesafb: pmi: set display start = c00cb4d3, set palette = c00cb52e
    vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
    vesafb: scrolling: redraw
    vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Console: switching to colour frame buffer device 128x48
    fb0: VESA VGA frame buffer device
    isapnp: Scanning for PnP cards...
    Switched to high resolution mode on CPU 0
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    IO APIC resources could be not be allocated.
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 356k freed
    SCSI subsystem initialized
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    libata version 3.00 loaded.
    pata_acpi 0000:00:06.0: setting latency timer to 64
    ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 15
    PCI: setting IRQ 15 as level-triggered
    pata_acpi 0000:00:08.0: PCI INT A -> Link[LSA0] -> GSI 15 (level, low) -> IRQ 15
    pata_acpi 0000:00:08.0: setting latency timer to 64
    pata_acpi 0000:00:08.0: PCI INT A disabled
    pata_amd 0000:00:06.0: version 0.4.1
    pata_amd 0000:00:06.0: setting latency timer to 64
    scsi0 : pata_amd
    scsi1 : pata_amd
    ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
    ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
    ata1.00: ATAPI: PHILIPS SPD6005T, P1.0, max UDMA/66
    ata1: nv_mode_filter: 0x1f39f&0x1f01f->0x1f01f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:900:0x11)
    ata1.00: limited to UDMA/33 due to 40-wire cable
    ata1.00: configured for UDMA/33
    scsi 0:0:0:0: CD-ROM PHILIPS SPD6005T P1.0 PQ: 0 ANSI: 5
    ata2: port disabled. ignoring.
    sata_nv 0000:00:08.0: version 3.5
    sata_nv 0000:00:08.0: PCI INT A -> Link[LSA0] -> GSI 15 (level, low) -> IRQ 15
    sata_nv 0000:00:08.0: setting latency timer to 64
    scsi2 : sata_nv
    scsi3 : sata_nv
    ata3: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 15
    ata4: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 15
    ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.00: ATA-8: WDC WD3200AAJS-00VWA0, 12.01B02, max UDMA/133
    ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata3.00: configured for UDMA/133
    scsi 2:0:0:0: Direct-Access ATA WDC WD3200AAJS-0 12.0 PQ: 0 ANSI: 5
    Driver 'sd' needs updating - please use bus_type methods
    sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda4 < sda5 sda6 sda7 >
    sd 2:0:0:0: [sda] Attached SCSI disk
    PM: Starting manual resume from disk
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    rtc_cmos 00:02: RTC can wake from S4
    rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
    udev: starting version 141
    loop: module loaded
    cfg80211: Using static regulatory domain info
    cfg80211: Regulatory domain: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
    (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
    cfg80211: Calling CRDA for country: US
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    usbcore: registered new interface driver rt73usb
    fuse init (API version 7.11)
    vboxdrv: Trying to deactivate the NMI watchdog permanently...
    vboxdrv: Successfully done.
    vboxdrv: Found 1 processor cores.
    vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    vboxdrv: Successfully loaded version 2.2.0 (interface 0x000a0009).
    input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
    ACPI: Power Button (CM) [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    IT8712 SuperIO detected.
    parport_pc 00:05: reported by Plug and Play ACPI
    parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 10
    PCI: setting IRQ 10 as level-triggered
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUB2] -> GSI 10 (level, low) -> IRQ 10
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:02.1: irq 10, io mem 0xdbffec00
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 8 ports detected
    i2c-adapter i2c-0: nForce2 SMBus adapter at 0x600
    i2c-adapter i2c-1: nForce2 SMBus adapter at 0x700
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 11
    PCI: setting IRQ 11 as level-triggered
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUB0] -> GSI 11 (level, low) -> IRQ 11
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 11, io mem 0xdbfff000
    Driver 'sr' needs updating - please use bus_type methods
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 8 ports detected
    forcedeth: Reverse Engineered nForce ethernet driver. Version 0.62.
    ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 11
    forcedeth 0000:00:07.0: PCI INT A -> Link[LMAC] -> GSI 11 (level, low) -> IRQ 11
    forcedeth 0000:00:07.0: setting latency timer to 64
    sr0: scsi3-mmc drive: 16x/16x writer dvd-ram cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 0:0:0:0: Attached scsi CD-ROM sr0
    sr 0:0:0:0: Attached scsi generic sg0 type 5
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    Linux agpgart interface v0.103
    usb 1-4: new high speed USB device using ehci_hcd and address 2
    input: PC Speaker as /devices/platform/pcspkr/input/input4
    lp0: using parport0 (interrupt-driven).
    usb 1-4: configuration #1 chosen from 1 choice
    hub 1-4:1.0: USB hub found
    hub 1-4:1.0: 4 ports detected
    usb 1-5: new high speed USB device using ehci_hcd and address 3
    forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x1374 @ 1, addr 00:1b:fc:fc:c3:29
    forcedeth 0000:00:07.0: highdma pwrctl mgmt timirq gbit lnktim msi desc-v3
    k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
    usb 1-5: configuration #1 chosen from 1 choice
    usb 1-4.1: new high speed USB device using ehci_hcd and address 4
    usb 1-4.1: configuration #1 chosen from 1 choice
    nvidia: module license 'NVIDIA' taints kernel.
    ppdev: user-space parallel port driver
    Initializing USB Mass Storage driver...
    scsi4 : SCSI emulation for USB Mass Storage devices
    Error: Driver 'pcspkr' is already registered, aborting...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 3
    usb-storage: waiting for device to settle before scanning
    wmaster0 (rt73usb): not using net_device_ops yet
    phy0: Selected rate control algorithm 'minstrel'
    ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 11
    HDA Intel 0000:00:05.0: PCI INT B -> Link[LAZA] -> GSI 11 (level, low) -> IRQ 11
    HDA Intel 0000:00:05.0: setting latency timer to 64
    psmouse serio1: ID: 10 00 64<6>wlan0 (rt73usb): not using net_device_ops yet
    Registered led device: rt73usb-phy0:radio
    Registered led device: rt73usb-phy0:assoc
    Registered led device: rt73usb-phy0:quality
    usb 1-4.3: new high speed USB device using ehci_hcd and address 5
    ACPI: PCI Interrupt Link [LNED] enabled at IRQ 11
    nvidia 0000:02:00.0: PCI INT A -> Link[LNED] -> GSI 11 (level, low) -> IRQ 11
    nvidia 0000:02:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86 Kernel Module 180.44 Mon Mar 23 14:59:10 PST 2009
    usb 1-4.3: configuration #1 chosen from 1 choice
    Linux video capture interface: v2.00
    usbcore: registered new interface driver snd-usb-audio
    uvcvideo: Found UVC 1.00 device USB Video Camera (0471:0334)
    input: USB Video Camera as /devices/pci0000:00/0000:00:02.1/usb1/1-4/1-4.3/1-4.3:1.0/input/input5
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v0.1.0)
    input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input6
    EXT3 FS on sda7, internal journal
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sda6, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sda1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    Adding 3919820k swap on /dev/sda5. Priority:-1 extents:1 across:3919820k
    scsi 4:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
    sd 4:0:0:0: [sdb] Attached SCSI removable disk
    sd 4:0:0:0: Attached scsi generic sg2 type 0
    scsi 4:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
    sd 4:0:0:1: [sdc] Attached SCSI removable disk
    sd 4:0:0:1: Attached scsi generic sg3 type 0
    scsi 4:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
    sd 4:0:0:2: [sdd] Attached SCSI removable disk
    sd 4:0:0:2: Attached scsi generic sg4 type 0
    scsi 4:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
    sd 4:0:0:3: [sde] Attached SCSI removable disk
    sd 4:0:0:3: Attached scsi generic sg5 type 0
    usb-storage: device scan complete
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    rt73usb 1-4.1:1.0: firmware: requesting rt73.bin
    ADDRCONF(NETDEV_UP): wlan0: link is not ready
    ADDRCONF(NETDEV_UP): wlan0: link is not ready
    wlan0: authenticate with AP 00:14:7f:83:b1:bb
    wlan0: authenticated
    wlan0: associate with AP 00:14:7f:83:b1:bb
    wlan0: RX AssocResp from 00:14:7f:83:b1:bb (capab=0x411 status=0 aid=1)
    wlan0: associated
    ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    wlan0: no IPv6 routers present
    IRQ 11/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs

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

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

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

  • Two Nexus 5020 vPC etherchannel with Two Catalyst 6500 VSS

    Hi,
    we are fighting with an 40 Gbps etherchannel between 2 Nx 5000 and 2 Catalyst 6500 but the etherchannel never comes up. Here is the config:
    NK5-1
    interface port-channel30
      description Trunk hacia VSS 6500
      switchport mode trunk
      vpc 30
      switchport trunk allowed vlan 50-54
      speed 10000
    interface Ethernet1/3
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      beacon
      channel-group 30
    interface Ethernet1/4
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      channel-group 30
    NK5-2
    interface port-channel30
      description Trunk hacia VSS 6500
      switchport mode trunk
      vpc 30
      switchport trunk allowed vlan 50-54
      speed 10000
    interface Ethernet1/3
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      beacon
      channel-group 30
    interface Ethernet1/4
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      beacon
      channel-group 30
    Catalyst 6500 VSS
    interface Port-channel30
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    interface TenGigabitEthernet2/1/2
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    channel-protocol lacp
    channel-group 30 mode passive
    interface TenGigabitEthernet2/1/3
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    channel-protocol lacp
    channel-group 30 mode passive
    interface TenGigabitEthernet1/1/2
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    channel-protocol lacp
    channel-group 30 mode passive
    interface TenGigabitEthernet1/1/3
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    channel-protocol lacp
    channel-group 30 mode passive
    The "Show vpc 30" is as follows
    N5K-2# sh vpc 30
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    30     Po30        down*  success     success                    -         
    But the "Show vpc Consistency-parameters vpc 30" is
    N5K-2# sh vpc consistency-parameters vpc 30
        Legend:
            Type 1 : vPC will be suspended in case of mismatch
    Name                             Type  Local Value            Peer Value            
    Shut Lan                              1     No                     No                   
    STP Port Type                    1     Default                Default              
    STP Port Guard                  1     None                   None                 
    STP MST Simulate PVST 1     Default                Default              
    mode                                    1     on                     -                    
    Speed                                  1     10 Gb/s                -                    
    Duplex                                   1     full                   -                    
    Port Mode                            1     trunk                  -                    
    Native Vlan                           1     1                      -                    
    MTU                                       1     1500                   -                    
    Allowed VLANs                    -     50-54                  50-54                
    Local suspended VLANs    -     -                      -         
    We will apreciate any advice,
    Thank you very much for your time...
    Jose

    Hi Lucien,
    here is the "show vpc brief"
    N5K-2# sh vpc brief
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 5  
    Peer status                     : peer adjacency formed ok     
    vPC keep-alive status           : peer is alive                
    Configuration consistency status: success
    Per-vlan consistency status     : success                      
    Type-2 consistency status       : success
    vPC role                        : secondary                    
    Number of vPCs configured       : 2  
    Peer Gateway                    : Disabled
    Dual-active excluded VLANs      : -
    Graceful Consistency Check      : Enabled
    vPC Peer-link status
    id   Port   Status Active vlans   
    1    Po5    up     50-54                                                   
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    30     Po30        down*  success     success                    -         
    31     Po31        down*  failed      Consistency Check Not      -         
                                          Performed                            
    *************************************************************************+
    *************************************************************************+
    N5K-1# sh vpc brief
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 5  
    Peer status                     : peer adjacency formed ok     
    vPC keep-alive status           : peer is alive                
    Configuration consistency status: success
    Per-vlan consistency status     : success                      
    Type-2 consistency status       : success
    vPC role                        : primary                      
    Number of vPCs configured       : 2  
    Peer Gateway                    : Disabled
    Dual-active excluded VLANs      : -
    Graceful Consistency Check      : Enabled
    vPC Peer-link status
    id   Port   Status Active vlans   
    1    Po5    up     50-54                                                   
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    30     Po30        down*  failed      Consistency Check Not      -         
                                          Performed                            
    31     Po31        down*  failed      Consistency Check Not      -         
                                          Performed             
    I have changed the lacp on both devices to active:
    On Nexus N5K-1/-2
    interface Ethernet1/3
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      channel-group 30 mode active
    interface Ethernet1/4
      switchport mode trunk
      switchport trunk allowed vlan 50-54
      channel-group 30 mode active    
    On Catalyst 6500
    interface TenGigabitEthernet2/1/2-3
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    switchport mode trunk
    channel-protocol lacp
    channel-group 30 mode active
    interface TenGigabitEthernet1/1/2-3
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 50-54
    switchport mode trunk
    channel-protocol lacp
    channel-group 30 mode active
    Thanks for your time.
    Jose

  • Catalyst 6500 - Nexus 7000 migration

    Hello,
    I'm planning a platform migration from Catalyst 6500 til Nexus 7000. The old network consists of two pairs of 6500's as serverdistribution, configured with HSRPv1 as FHRP, rapid-pvst and ospf as IGP. Futhermore, the Cat6500 utilize mpls/l3vpn with BGP for 2/3 of the vlans. Otherwise, the topology is quite standard, with a number of 6500 and CBS3020/3120 as serveraccess.
    In preparing for the migration, VTP will be discontinued and vlans have been manually "copied" from the 6500 to the N7K's. Bridge assurance is enabled downstream toward the new N55K access-switches, but toward the 6500, the upcoming etherchannels will run in "normal" mode, trying to avoid any problems with BA this way. For now, only L2 will be utilized on the N7K, as we're avaiting the 5.2 release, which includes mpls/l3vpn. But all servers/blade switches will be migrated prior to that.
    The questions arise, when migrating Layer3 functionality, incl. hsrp. As per my understanding, hsrp in nxos has been modified slightly to better align with the vPC feature and to avoid sub-optimal forwarding across the vPC peerlink. But that aside, is there anything that would complicate a "sliding" FHRP migration? I'm thinking of configuring SVI's on the N7K's, configuring them with unused ip's and assign the same virtual ip, only decrementing the prio to a value below the current standby-router. Also spanning-tree prio will, if necessary, be modified to better align with hsrp.
    From a routing perspective, I'm thinking of configuring ospf/bgp etc. similar to that of the 6500's, only tweaking the metrics (cost, localpref etc) to constrain forwarding on the 6500's and subsequently migrate both routing and FHRP at the same time. Maybe not in a big bang style, but stepwise. Is there anything in particular one should be aware of when doing this? At present, for me this seems like a valid approach, but maybe someone has experience with this (good/bad), so I'm hoping someone has some insight they would like to share.
    Topology drawing is attached.
    Thanks
    /Ulrich

    In a normal scenario, yes. But not in vPC. HSRP is a bit different in the vPC environment. Even though the SVI is not the HSRP primary, it will still forward traffic. Please see the below white paper.
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-516396.html
    I will suggest you to set up the SVIs on the N7K but leave them in the down state. Until you are ready to use the N7K as the gateway for the SVIs, shut down the SVIs on the C6K one at a time and turn up the N7K SVIs. When I said "you are ready", it means the spanning-tree root is at the N7K along with all the L3 northbound links (toward the core).
    I had a customer who did the same thing that you are trying to do - to avoid down time. However, out of the 50+ SVIs, we've had 1 SVI that HSRP would not establish between C6K and N7K, we ended up moving everything to the N7K on a fly during of the migration. Yes, they were down for about 30 sec - 1 min for each SVI but it is less painful and waste less time because we don't need to figure out what is wrong or any NXOS bugs.
    HTH,
    jerry

Maybe you are looking for

  • Reading temporary data from workstations

    Good morning, First I'm not a programmer, I write some code but looping gets me one loop is easy two loops gets me.  I will first explain what I'm trying to do and then show you my code. I'm trying to write a script to clean temporary files on workst

  • Datasocket, read when data changed in buffer

    Hai I am using datasocket to communicate between a remote VI on the PXI and a server application. Normally i would just write in to the datasocket server from the PXI, but if there is any data in the input buffer i need to read it and process it. Is

  • "Associated Certifications" incorrect on OE page for 1Z0-144

    Brandye: The associated certification currently displayed for 1Z0-144 is "Oracle Forms Developer Certified Professional" rather than "Oracle PL/SQL Developer Certified Associate". http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page

  • Dreamweaver - links not working

    On my page: http://wbindev.ws/test.html You can see that the box links work fine but the menu links aren't working. I've been trying to solve this problem for hours but I'm stuck! Can anyone help please? Thanks Hannah

  • E-TEST Suite

    Does anyone have any practical experience in using the e-TEST suite - I'm especially interrested in the e-Load component and would like to understand it's scope of features and ease of use. For context we currently use an ancient version of LoadRunne