HELP - Licence Error on 4500x VSS

HI there,
have 2 4500x in vss mode. both are running 3.4.2 ipbase and are running on the correct licences etc.
after putting them in VSS mode the following error shows in the logs.
%SW_LEVEL-6-RESULT: Operational redundancy mode is UNKNOWN, due to software license-level mismatch at ACTIVE and STANDBY. Software Level on Active: ipbase; on Standby: ipbase
Any suggestions would be appreciated.
I thought it maybe related to bug CSCui54147 but cant see any details of it and it only seems to relate to 3.5.x
Thanks in advance.
Ross

Hi Apologies for not getting back.
To fix this I had to manually accept the EULA for ipbase licence on the 4500x.
After the reload everything worked correctly and I stopped getting this error.

Similar Messages

  • Cisco 4500X VSS & MEC Cisco 2960X

    Hi
    I have Cisco 4500x VSS  connect to  MEC Cisco 2960X using LACP.
    I encountered a problem about C2960X
    Integration reason
    1.C2960X Ten 1/0/2 link flapping interface error-disable .  I am  disable interface then  enable interface , switch show SFP not Present .
       Te1/0/2                      notconnect   1            full    10G Not Present. (SPF plug-in  Correct)
    2.use CLI reload C2960X , Ten 1/0/1 ,Ten 1/0/2   notconnect  SPF Not Present.  (SPF plug-in  Correct)
      error message :
    Dec 18 12:40:25.250: %SYS-5-CONFIG_I: Configured from console by console
    Dec 18 12:41:48.888: % ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured by Cisco or with Cisco's authorization.  This product may contain software that was copied in violation of Cisco's license terms.  If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet.  Please contact Cisco's Technical Assistance Center for more information.
    26F_guest_switch#show license
    Index 1 Feature: lanlite       
            Period left: 0  minute  0  second 
    Index 2 Feature: lanbase       
            Period left: Life time
            License Type: Permanent
            License State: Active, In Use
            License Priority: Medium
            License Count: Non-Counted
    3.C2960X power Cycle ,C2960X  operation normal, ,but recurring problems  every day.
    I do not know where the problem , I have  upgrade C2960X IOS but it had same problem.
    Cisco 2960X IOS version:  15.2(3)E    C2960X-UNIVERSALK9-M 
    Cisco 4500X IOS version: cat4500e-universalk9.SPA.03.05.00.E.152-1.E.bin
    Thanks for your help,

    Hi Reza,
    Thanks for your help
    I can not confirm that because I have a few switch have the same problem.
    C2960X 10G port 1 is connected to C4500X slot 1, Port 2 is connected to C4500X Slot2.
     link flapping, On the switch  port 2.
    I need to do a more precise test to confirm the problem is C2960X or 4500VSS

  • SBO Client and Windows Vista in workgroup Licence error

    Hi!
    My customer runs B1 2004C. Network structure is workgroup. Client and server are in the same workgroup. XP users connect successfully, but new Vista user gets the licence error: "-2147024891 Access denied". DCOM and other customizations on the licence server are done like in SAP Notes. It doesn't help.
    I know Vista is not officially supported by 2004C B1, but i have several Vista users running SBO fine in domain structure. I think the trouble is in the workgroup.
    Thanks a lot!
    David.

    Hi David,
    some of the SAP Notes addressing DCOM access denied problem of 2004 releases.
    <b>Note 833798 - After Upgrade W2003 to SP1: Access denied -2147024891</b>
    Symptom
    After upgrading Windows 2003 server to SP1 you get the access denied error -2147024891
    Other terms
    license server, error -2147024891
    Reason and Prerequisites
    Upgrade to Windows 2003 server changes security settings
    Solution
    The problem is caused by SP1 for W2003 Server. You have to change the
    default configuration of the DCOM to enable clients to access license
    server again:
    1. go to "Start/run", type in "Dcomcnfg" and the Dcom configuration will open
    2. expand "Component Services"
    3. right click on "my computer", open "Properties"
    4. go to tab "Com Security"
    5. in "launch and activation permission" go to "edit limits" this
    button is new since SP1
    6. tick the boxes "remote launch" and "remote activation" for user
    "everyone"
    After that the clients can access the license server again, if all nescessary rights are give in the DCOM as well. When the changes described above did not take effect, please check this additionally:
    1. go to "Start/run", type in "Dcomcnfg" and the Dcom configuration will open
    2. expand "Component Services"
    3. Go to "SBOLicense", open "Properties" by right-clicking the mouse
    4. On register tab "Security" customize all permissions. Add all nescessary User accounts there. If you add i.e. User Group "Everyone" there, you will not have access right problems any longer, as every user belongs by default to this group.
    If that change does not take effect immediately, reboot the server.
    This note is permanently updated. If you have any comments or proposals tho improve it, please contact the SAP Business One Hotline and let us know.
    <b>Note 824976 - error -2147024891, access denied to license server</b>
    Symptom
    error -2147024891 when trying to connect with B1 client to license server on another computer The License mechanism needs a properly set up license server which is available over the network via DCOM interface to client computers. The necessary windows user rights must be assigned to client and server.
    Other terms
    Access denied, SAP Business One, License server
    Reason and Prerequisites
    Functionality description
    Solution
    1. Is the license server up and running?
    The B1 client on the license server computer should be started and logged into to ensure that there are no problems withs the license server itself. The B1 Server tools should be opened and the settings of the License Manager should be checked so that it is possible to connect by pressing the Connect button.
    2. Is the network connection between client and license server working?
    The server should be pinged via its IP-address for a response. Any firewalls should be disabled between client and license server for troubleshooting reasons as they can effectively block data packets which are needed for license mechanism. If a VPN is used between client and license server all ports should be available.
    3. Are necessary windows user rights in the domain given?
    We highly recommend to use B1 in a windows domain, as this is the only way to manage user accounts effectively. Domain user accounts have to be configured on the domain controller computer only. For troubleshooting reasons log in at the client with the windows domain administrator account, that should prevent the user from being blocked due to a lack windows user rights. According to our recommendations the users should be Power Users on the local computer.
    4. Are necessary windows user rights in a workgroup given?
    If the user is in a windows workgroup, the same user account should be configured with the same password on the license server and on each client computer as well. For troubleshooting reasons a local admin account should be configured on each of these computers. As account information is stored locally on each computer, username and password must be exactly the same on each of the machines. Login with this local administrator account. According to our recommendations the users should be Power Users on the local computer.
    5. Is DCOM installed and configured correctly?
    On the license server DCOM interface should to be installed and configured correctly. It is located under Control panel\administrative tools\ component service. Expand and in My Computer you will find DCOM Config\SBO License. Open its Properties and check configurations in Security tab. Add user accounts there, if needed.
    DCOM should be enabled on the Client machines and on the server(s). In the Component Services expand to My Computer and right click to open the Properties for My Computer. Go to the Default Properties tab and make sure that 'Enable Distributed COM on this computer' is ticked. If these settings are modifed a restart of the computer is needed for the changes to take effect.
    Br,
    Chris

  • Licence error : verification of members outside domain

    Hi everybody,
    We have an error on our server Windows Server 2012 R2 Essential.
    Title : Licence error : verification of members outside domain.
    Description : Thefield outsidemembers of the auditstrategyin
    your environmenthas detecteda condition thatdoes not complylicensestrategy.This
    servercan only bein aworkgroup ora domain controller.
    Resolution :
    Make sure the server is in a
    workgroup or a domain
    is Controller.
    Our client has finally insert the server in a domain but the problem is not solved.
    Do you know if this requires a
    purchase of a license extension ?
    The other question is that their
    server (this server runs a company of 100
    people!) stopped the last weekend,
    and it seems that it is due to this ...
    Do you know if this can happen?
    Thanks a lot for your help!

    To tell you the truth, I am not sure of the answer if you have Server 2012R2 Essentials.  The software that costs around $400 US.  Though I think that must be what you have.
    The error you show above is saying you have not run the essentials configuration wizard which I said should have been run on day 1.  It must be a Domain Controller or join a Domain.  So you could rebuild the box as a DC and have two DC's on
    your network which would be no help at all.
    What I don't know for sure is if you join it to your domain and then run the Post Deployment wizard if it will complain you have more than 25 users.  I will try sometime over the weekend and see.  But I am pretty sure it will list your Domain Users
    as users because it is joined to the Domain and you have too many users.
    If you had Server 2012R2 Standard and enabled the Essentials role you would not have a limit on the number of users.
    Why did you build this box?  What are you trying to accomplish?
    Grey

  • Prime 2.1 and 4500X-VSS support?

    Anyone with a Prime 2.1.2 that successfully archives configurations from a WS-C4500X-16 running VSS?
    Error message after Configuration Archive:
    No device package found for the specified device.
    The software on the 4500X is 03.04.03SG.
    Support for 4500X in PI 2.1.2:
    Device Type
    SYSOIDS
    S/W Version
    Software
    Cisco Catalyst 4500X-16 SFP+ Switch
    OID:1.3.6.1.4.1.9.1.1605
    IOS
    Cisco Catalyst 4500X-32 SFP+ Switch
    OID:1.3.6.1.4.1.9.1.1606
    IOS
    Tanks

    Yes, all device packages are installed (including 7.0) and the Pi 2.1.2 patch.
    Info from "ifm_config_archive.log" when trying Archive the Configuration:
    [2014-12-09 19:58:11,300] [pool-37-thread-5] [service] [ERROR] - Thread Id : [9,460] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching VLAN file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]'
    Maybe the Prime don't know where to find the vlan.dat on the 4500X-VSS ?
    #dir cat4000_flash:
    Directory of cat4000_flash:/
        1  -rw-        2236                    <no date>  vlan.dat
    sysObjectID (1.3.6.1.2.1.1.2)  is
    .iso.org.dod.internet.private.enterprises.cisco.ciscoProducts.cat4xxxVirtualSwitch 
    That is not the expected and supported value  "4500X-16"  above
    Update: Error on fetching running and startup config as well:
    [2014-12-09 20:24:21,818] [pool-37-thread-9] [service] [ERROR] - Thread Id : [10,013] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching RUNNINGCONFIG file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]
    [2014-12-09 20:25:31,882] [pool-37-thread-9] [service] [ERROR] - Thread Id : [10,013] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching STARTUPCONFIG file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]

  • 4500x VSS and SFP-H10GB-CU1M

    Hello
    I have (2) Cisco 4500x with a VSS config. I als have a couple cables "SFP-H10GB-CU1M".
    I want to make sure I have this physically setup correctly. I have searched but not found anything specific enough.
    Please review and advise.

    Yes, all device packages are installed (including 7.0) and the Pi 2.1.2 patch.
    Info from "ifm_config_archive.log" when trying Archive the Configuration:
    [2014-12-09 19:58:11,300] [pool-37-thread-5] [service] [ERROR] - Thread Id : [9,460] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching VLAN file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]'
    Maybe the Prime don't know where to find the vlan.dat on the 4500X-VSS ?
    #dir cat4000_flash:
    Directory of cat4000_flash:/
        1  -rw-        2236                    <no date>  vlan.dat
    sysObjectID (1.3.6.1.2.1.1.2)  is
    .iso.org.dod.internet.private.enterprises.cisco.ciscoProducts.cat4xxxVirtualSwitch 
    That is not the expected and supported value  "4500X-16"  above
    Update: Error on fetching running and startup config as well:
    [2014-12-09 20:24:21,818] [pool-37-thread-9] [service] [ERROR] - Thread Id : [10,013] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching RUNNINGCONFIG file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]
    [2014-12-09 20:25:31,882] [pool-37-thread-9] [service] [ERROR] - Thread Id : [10,013] : IFM_CONFIG_ARCHIVE_ERROR_DETAILS: [Error in fetching STARTUPCONFIG file] : IFM_CONFIG_ARCHIVE_ERROR: [com.cisco.ifm.config.archive.service.exceptions.XDEFeatureExecutionException: No device package found for the specified device.]

  • Error message on VSS

    Hi All,
    I would like to ask if you have see following error message and if it is realated to problem below..
    Aug 24 18:15:56 core.schmid.local 753: Aug 24 18:15:55: %FIB-2-FIBDISABLE: Fatal error, slot 41/0 (41): XDR disabled
    At the time of the performance problems was on active switch 1 switch We have switched to  Switch 2  8:24
    Changeover took place via the command: redundancy force-switchover
    On closer analysis, I have found that Switch 2 has not booted, but it was the SSO failover a problem with the module 9 on Switch 2
    The switch has reported this at 8:29 clock and then made the module normally. After automatic. Reload the module were all the services accessible again.
    Note: Module 9 = WS-X6904-40G = Terminals our Data Center Switches -> Shortly after entering the switchover all connections were interrupted to the Data Center.
    Aug 26 08:24:01: %LINK-3-UPDOWN: Interface Port-channel251, changed state to down
    Aug 26 08:24:02: %ARP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: 192.168.30.36, hw: 001a.647a.d77a by hw: 001a.647a.d77c
    Aug 26 08:24:02: %C6KPWR-4-PSOK: power supply 1 turned on.
    Aug 26 08:24:02: %C6KPWR-4-PSOK: power supply 2 turned on.scp_dnld_stdby_disable, No instance for CHILISLC_PROCESSOR found slot 9
    Aug 26 08:24:02: %OIR-3-SOFT_RESET_SSO: Module 9 is being soft reset as a part of switchover error recovery
    Aug 26 08:24:02: %C6KENV-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:24:03: %C6KENV-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 7 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:24:03: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.111.7 Port 514 started - CLI initiated
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/3, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/7, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/8, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/11, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/12, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/15, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/16, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/18, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/19, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/20, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/21, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/22, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/23, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/24, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/1, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/2, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/3, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/7, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/8, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/11, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/12, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/15, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/16, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/18, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/19, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/20, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/21, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/22, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/23, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/4, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/7, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/8, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/11, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/12, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/15, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/16, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/19, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/20, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/21, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/22, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/23, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/24, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/1, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/2, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/4, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/7, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/8, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/11, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/12, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/15, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/16, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/19, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/20, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/21, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/22, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/23, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/2, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/5, changed state to up
    Aug 26 08:24:04: %VSDA-3-LINK_DOWN: Interface Gi2/1/48 is no longer dual-active detection capable
    Aug 26 08:24:04: %VSDA-3-LINK_DOWN: Interface Gi2/2/24 is no longer dual-active detection capable
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/5, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/6, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/7, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/7, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/8, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/9, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/9, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/10, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/11, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/11, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/12, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/13, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/13, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/14, changed state to up
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/15, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/15, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/16, changed state to up
    Aug 26 08:24:05: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:24:05: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/17, changed state to up
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/18, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/17, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/18, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/19, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/20, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/20, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/21, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/22, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/22, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/23, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/24, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/24, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/1, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/2, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/2, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/3, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/4, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/4, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/5, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/6, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/7, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/6, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/7, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/8, changed state to up
    Aug 26 08:24:06: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:24:06: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface Port-channel250, changed state to down
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/9, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/10, changed state to up
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/11, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/12, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/12, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/13, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/14, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface Port-channel220, changed state to down
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface Port-channel210, changed state to down
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/14, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/15, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/16, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/17, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/18, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/16, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/17, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/18, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/19, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/20, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/20, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/21, changed state to up
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/22, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/22, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/23, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel20, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel21, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel22, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel23, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel24, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel25, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel26, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel27, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel28, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel29, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel30, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel31, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel32, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel33, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel34, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel35, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel36, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel37, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel38, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel39, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel40, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel41, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel42, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel43, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel44, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel45, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel46, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel47, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel48, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel49, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel50, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel51, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel52, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel53, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel54, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel55, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel56, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel57, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel58, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel59, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel60, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel61, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel62, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel63, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel64, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel65, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel66, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel20, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel21, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel22, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel23, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel24, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel25, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel26, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel27, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel28, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel29, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel30, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel31, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel32, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel33, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel34, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel35, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel36, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel37, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel38, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel39, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel40, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel41, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel42, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel43, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel44, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel45, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel46, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel47, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel48, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel49, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel50, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel51, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel52, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel53, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel54, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel55, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel56, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel57, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel58, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel59, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel60, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel61, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel62, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel63, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel64, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel65, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel66, changed state to up
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/25, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/26, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/27, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/28, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/29, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/30, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/31, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/32, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/33, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/34, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/35, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/37, changed state to administratively down
    Aug 26 08:24:14: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.111.7 Port 514 started - reconnection
    Aug 26 08:24:26: %HSRP-5-STATECHANGE: Vlan12 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan33 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan21 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan35 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan90 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan50 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan13 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan34 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan31 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan114 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan120 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan46 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan115 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan40 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan44 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan140 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan10 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan116 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan23 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan130 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan127 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan24 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan43 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan80 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan126 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan32 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan42 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan41 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan20 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan92 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan79 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan111 Grp 1 state Standby -> Active
    Aug 26 08:24:42: %HSRP-5-STATECHANGE: Vlan70 Grp 1 state Standby -> Active
    Aug 26 08:24:42: %HSRP-5-STATECHANGE: Vlan11 Grp 1 state Standby -> Active
    Aug 26 08:24:43: %HSRP-5-STATECHANGE: Vlan22 Grp 1 state Standby -> Active
    Aug 26 08:25:44: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
    Aug 26 08:25:44: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/4
    Aug 26 08:25:46: %VSLP-5-VSL_UP:  Ready for control traffic
    Aug 26 08:25:54: %PFREDUN-6-ACTIVE: Standby initializing for SSO mode
    Aug 26 08:26:36: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  inserted
    Aug 26 08:26:37: %QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT: QOS-HA-BLK-SYNC-PROCESS:  Failure in completing bulk sync before timeout
    Aug 26 08:26:45: %DIAG-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 08:27:00: %DIAG-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 08:27:02: %VSLP-5-VSL_UP:  Ready for data traffic
    Aug 26 08:27:02: %LINK-3-UPDOWN: Interface Port-channel251, changed state to up
    Aug 26 08:27:02: %LINK-3-UPDOWN: Interface Port-channel250, changed state to up
    Aug 26 08:27:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to up
    Aug 26 08:27:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to up
    Aug 26 08:27:02: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 1, physical slot 5, interfaces are now online
    *Aug 26 06:15:45.015: SW1_STBY: SP: Currently running ROMMON from S (Gold) region
    Aug 26 06:26:33.695: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 1
    Aug 26 06:26:33.703: %C6KPWR-SW1_STBY-4-PSOK: power supply 1 turned on.
    Aug 26 06:26:33.711: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 2
    Aug 26 06:26:33.711: %C6KPWR-SW1_STBY-4-PSOK: power supply 2 turned on.
    Aug 26 06:26:35.703: %C6KENV-SW1_STBY-4-FANHPMODE: Switch 1 Fan-tray 1 is operating in high power mode
    Aug 26 06:26:35.711: %FABRIC-SW1_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    Aug 26 06:26:45.507: %DIAG-SW1_STBY-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 06:26:45.507: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:26:45.507: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 5 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:26:55.919: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestChannel due to: the port is used as a VSL link.
    Aug 26 06:27:00.911: %DIAG-SW1_STBY-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 06:27:14.234: %SSH-SW1_STBY-5-DISABLED: SSH 1.99 has been disabled
    Aug 26 08:27:14: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:27:14 MESZ Mon Aug 26 2013 to 08:27:14 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:27:14: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:27:14 MESZ Mon Aug 26 2013 to 08:27:14 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:27:16: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:27:25: %SYS-SW1_STBY-5-RESTART: System restarted --
    Cisco IOS Software, s2t54 Software (s2t54-IPBASEK9-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 19:22 by prod_rel_team
    Aug 26 08:27:25: %SYS-SW1_STBY-6-BOOTTIME: Time taken to reboot after reload =  207 seconds
    Aug 26 08:27:25: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:27:26: %SYS-SW1_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:30 to ensure console debugging output.
    Aug 26 08:27:28: %C6KENV-SW1_STBY-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:27:30: SW1_STBY: TTY0: timer_create_bg error
    Aug 26 08:27:38: %VS_GENERIC-6-VS_HA_HOT_STANDBY_NOTIFY: Standby switch is in Hot Standby mode
    Aug 26 08:27:38: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
    Aug 26 08:27:38: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
    Aug 26 08:27:38: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:27:38: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:27:38: %PFREDUN-SW1_STBY-6-STANDBY: Ready for SSO mode
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  inserted
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  inserted
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  inserted
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-4-PSOUTPUTDROP: Power supply 1 output has dropped
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-2-PSFAIL: power supply 1 output failed.
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-4-PSREDUNDANTONESUPPLY: in power-redundancy mode, system is operating on one power supply.
    Aug 26 08:28:10: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/5/4: Link down
    Aug 26 08:28:10: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/5
    Aug 26 08:28:10: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/5/5: Link down
    Aug 26 08:28:10: %VSLP-2-VSL_DOWN:   Last VSL interface Te2/5/5 went down
    Aug 26 08:28:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to down
    Aug 26 08:28:10: %VSLP-2-VSL_DOWN:   All VSL links went down while switch is in ACTIVE role
    Aug 26 08:28:10: %LINK-3-UPDOWN: Interface Port-channel251, changed state to down
    Aug 26 08:28:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to down
    Aug 26 08:28:10: %LINK-3-UPDOWN: Interface Port-channel250, changed state to down
    Aug 26 08:28:10: %PFREDUN-6-ACTIVE: Standby processor removed or reloaded, changing to Simplex mode
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:29:01: %c6k_VSD_ROIR-6-TIMER_EVENT_RECV: ROIR::Receiver::Timer Process got TIMER event
    Aug 26 08:29:01: %c6k_VSD_ROIR-6-TIMER_EXPIRED: ROIR::Receiver::For Switch:2 Type 2 Phy Slot 9 - SWITCHOVER TIMER timer expired
    Aug 26 08:29:01: %OIR-3-VSS_PWRCYCLE: Card in Switch 2 module 9, is being power-cycled 'off (Switchover Failed)'
    Aug 26 08:29:01: %C6KPWR-4-DISABLED: power to module in slot 9 set off (Switchover Failed)
    Aug 26 08:29:16: %OIR-6-INSREM: Switch 2 Physical Slot 9 - Module Type LINE_CARD  inserted
    Aug 26 08:30:10: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
    Aug 26 08:30:10: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/4
    Aug 26 08:30:12: %VSLP-5-VSL_UP:  Ready for control traffic
    Aug 26 08:30:20: %PFREDUN-6-ACTIVE: Standby initializing for SSO mode
    *Mar  1 00:00:12.351: ppc_lc_ibc_subsys_init: ETSEC IBC INIT DONE
    Firmware compiled 02-Nov-12 11:44 by integ Build [101]
    Aug 26 06:30:02.155: DFC9: Switch mode info received by DFC..!
    Firmware Download OK:
    Firmware Download OK:
    Firmware Download OK:
    Firmware Download OK:
    Aug 26 06:30:23.979: %SYS-DFC9-5-RESTART: System restarted --
    Cisco IOS Software, c4lc Software (c4lc-SP-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 18:57 by prod_rel_team
    Aug 26 06:30:24.067: DFC9: Currently running ROMMON from S (Gold) region
    Aug 26 08:31:10: %DIAG-6-RUN_MINIMUM: Switch 2 Module 9: Running Minimal Diagnostics...
    Aug 26 08:31:13: %QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT: QOS-HA-BLK-SYNC-PROCESS:  Failure in completing bulk sync before timeout
    Aug 26 08:31:16: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  inserted
    Aug 26 08:31:24: %DIAG-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 08:31:38: %DIAG-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 08:31:39: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 1, physical slot 5, interfaces are now online
    Aug 26 08:31:40: %DIAG-6-DIAG_OK: Switch 2 Module 9: Passed Online Diagnostics
    Aug 26 08:31:40: %C6KENV-4-LOWER_SLOT_EMPTY: The lower adjacent slot of module 9 might be empty. Airdam must be installed in that slot to be NEBS compliant
    Aug 26 08:31:40: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/5, changed state to down
    Aug 26 08:31:40: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/6, changed state to down
    Aug 26 08:31:41: %VSLP-5-VSL_UP:  Ready for data traffic
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface Port-channel251, changed state to up
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface Port-channel250, changed state to up
    Aug 26 08:31:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to up
    Aug 26 08:31:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to up
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/13, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/14, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to down
    Aug 26 08:31:41: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 2, physical slot 9, interfaces are now online
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to down
    Aug 26 08:31:42: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/5, changed state to up
    Aug 26 08:31:42: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/6, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/13, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/14, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:48: %LINK-3-UPDOWN: Interface Port-channel210, changed state to up
    Aug 26 08:31:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/6, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/14, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel210, changed state to up
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface Port-channel220, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/5, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/13, changed state to up
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to down
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel220, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/17, changed state to up
    *Aug 26 06:20:21.975: SW1_STBY: SP: Currently running ROMMON from S (Gold) region
    Aug 26 06:31:10.101: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 1
    Aug 26 06:31:10.105: %C6KPWR-SW1_STBY-4-PSOK: power supply 1 turned on.
    Aug 26 06:31:10.105: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 2
    Aug 26 06:31:10.105: %C6KPWR-SW1_STBY-4-PSOK: power supply 2 turned on.
    Aug 26 06:31:12.141: %C6KENV-SW1_STBY-4-FANHPMODE: Switch 1 Fan-tray 1 is operating in high power mode
    Aug 26 06:31:12.165: %FABRIC-SW1_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    Aug 26 06:31:24.049: %DIAG-SW1_STBY-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 06:31:24.049: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:31:24.049: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 5 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:31:34.433: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestChannel due to: the port is used as a VSL link.
    Aug 26 06:31:38.941: %DIAG-SW1_STBY-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 06:31:54.717: %SSH-SW1_STBY-5-DISABLED: SSH 1.99 has been disabled
    Aug 26 08:31:54: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:31:54 MESZ Mon Aug 26 2013 to 08:31:54 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:31:54: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:31:54 MESZ Mon Aug 26 2013 to 08:31:54 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:31:57: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:32:06: %SYS-SW1_STBY-5-RESTART: System restarted --
    Cisco IOS Software, s2t54 Software (s2t54-IPBASEK9-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 19:22 by prod_rel_team
    Aug 26 08:32:06: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:32:07: %SYS-SW1_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:33 to ensure console debugging output.
    Aug 26 08:32:08: %C6KENV-SW1_STBY-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:32:19: %VS_GENERIC-6-VS_HA_HOT_STANDBY_NOTIFY: Standby switch is in Hot Standby mode
    Aug 26 08:32:19: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
    Aug 26 08:32:19: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
    Aug 26 08:32:19: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:32:19: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:32:19: %PFREDUN-SW1_STBY-6-STANDBY: Ready for SSO mode
    Aug 26 08:32:27: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  inserted
    Aug 26 08:32:28: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  inserted
    Aug 26 08:32:28: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  inserted
    Thank you

    You posted this Discussion
    Edit
    Delete
    error message on VSS
    Unanswered Question
    jozefstaruch 12 months ago
    Hi All,
    I would like to ask if you have see following error message and if it is realated to problem below..
    Aug 24 18:15:56 core.schmid.local 753: Aug 24 18:15:55: %FIB-2-FIBDISABLE: Fatal error, slot 41/0 (41): XDR disabled
    At the time of the performance problems was on active switch 1 switch We have switched to  Switch 2  8:24
    Changeover took place via the command: redundancy force-switchover
    On closer analysis, I have found that Switch 2 has not booted, but it was the SSO failover a problem with the module 9 on Switch 2
    The switch has reported this at 8:29 clock and then made the module normally. After automatic. Reload the module were all the services accessible again.
    Note: Module 9 = WS-X6904-40G = Terminals our Data Center Switches -> Shortly after entering the switchover all connections were interrupted to the Data Center.
    Aug 26 08:24:01: %LINK-3-UPDOWN: Interface Port-channel251, changed state to down
    Aug 26 08:24:02: %ARP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: 192.168.30.36, hw: 001a.647a.d77a by hw: 001a.647a.d77c
    Aug 26 08:24:02: %C6KPWR-4-PSOK: power supply 1 turned on.
    Aug 26 08:24:02: %C6KPWR-4-PSOK: power supply 2 turned on.scp_dnld_stdby_disable, No instance for CHILISLC_PROCESSOR found slot 9
    Aug 26 08:24:02: %OIR-3-SOFT_RESET_SSO: Module 9 is being soft reset as a part of switchover error recovery
    Aug 26 08:24:02: %C6KENV-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:24:03: %C6KENV-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 7 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:24:03: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.111.7 Port 514 started - CLI initiated
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/3, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/7, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/8, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/11, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/12, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/15, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/16, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/18, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/19, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/20, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/21, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/22, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/23, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/24, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/1, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/2, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/3, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/7, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/8, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/11, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/12, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/15, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/16, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/18, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/19, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/20, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/21, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/22, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet1/2/23, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/5, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/6, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/9, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/10, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/13, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/14, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/17, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/9/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/4, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/7, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/8, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/11, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/12, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/15, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/16, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/19, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/20, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/21, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/22, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/23, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/24, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/1, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/2, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/4, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/7, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/8, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/11, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/12, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/15, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/16, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/19, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/20, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/21, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/22, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/2/23, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/5, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/6, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/9, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/10, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/13, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/14, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/17, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/9/18, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/2, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/3, changed state to up
    Aug 26 08:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/4, changed state to up
    Aug 26 08:24:03: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/5, changed state to up
    Aug 26 08:24:04: %VSDA-3-LINK_DOWN: Interface Gi2/1/48 is no longer dual-active detection capable
    Aug 26 08:24:04: %VSDA-3-LINK_DOWN: Interface Gi2/2/24 is no longer dual-active detection capable
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/5, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/6, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/7, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/7, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/8, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/9, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/9, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/10, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/11, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/11, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/12, changed state to up
    Aug 26 08:24:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/13, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/13, changed state to up
    Aug 26 08:24:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/14, changed state to up
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/15, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/15, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/16, changed state to up
    Aug 26 08:24:05: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:24:05: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/17, changed state to up
    Aug 26 08:24:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/18, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/17, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/18, changed state to up
    Aug 26 08:24:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/19, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/20, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/20, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/21, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/22, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/22, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/23, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/24, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/24, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/1, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/2, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/2, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/3, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/4, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/4, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/5, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/6, changed state to up
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/7, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/6, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/7, changed state to up
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/8, changed state to up
    Aug 26 08:24:06: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:24:06: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:24:06: %LINK-3-UPDOWN: Interface Port-channel250, changed state to down
    Aug 26 08:24:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/9, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/10, changed state to up
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/11, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/12, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/12, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/13, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/14, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface Port-channel220, changed state to down
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface Port-channel210, changed state to down
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/14, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/15, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/16, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/17, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/18, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/16, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/17, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/18, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/19, changed state to up
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/20, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/20, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/21, changed state to up
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:24:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/2/22, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/22, changed state to up
    Aug 26 08:24:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2/23, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel20, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel21, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel22, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel23, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel24, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel25, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel26, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel27, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel28, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel29, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel30, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel31, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel32, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel33, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel34, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel35, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel36, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel37, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel38, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel39, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel40, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel41, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel42, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel43, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel44, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel45, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel46, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel47, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel48, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel49, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel50, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel51, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel52, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel53, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel54, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel55, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel56, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel57, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel58, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel59, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel60, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel61, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel62, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel63, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel64, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel65, changed state to up
    Aug 26 08:24:08: %LINK-3-UPDOWN: Interface Port-channel66, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel20, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel21, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel22, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel23, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel24, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel25, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel26, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel27, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel28, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel29, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel30, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel31, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel32, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel33, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel34, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel35, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel36, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel37, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel38, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel39, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel40, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel41, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel42, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel43, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel44, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel45, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel46, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel47, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel48, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel49, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel50, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel51, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel52, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel53, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel54, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel55, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel56, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel57, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel58, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel59, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel60, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel61, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel62, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel63, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel64, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel65, changed state to up
    Aug 26 08:24:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel66, changed state to up
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/25, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/26, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/27, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/28, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/29, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/30, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/31, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/32, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/33, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/34, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/35, changed state to administratively down
    Aug 26 08:24:08: %LINK-5-CHANGED: Interface GigabitEthernet2/1/37, changed state to administratively down
    Aug 26 08:24:14: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 192.168.111.7 Port 514 started - reconnection
    Aug 26 08:24:26: %HSRP-5-STATECHANGE: Vlan12 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan33 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan21 Grp 1 state Standby -> Active
    Aug 26 08:24:30: %HSRP-5-STATECHANGE: Vlan35 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan90 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan50 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan13 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan34 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan31 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan114 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan120 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan46 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan115 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan40 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan44 Grp 1 state Standby -> Active
    Aug 26 08:24:31: %HSRP-5-STATECHANGE: Vlan140 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan10 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan116 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan23 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan130 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan127 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan24 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan43 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan80 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan126 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan32 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan42 Grp 1 state Standby -> Active
    Aug 26 08:24:32: %HSRP-5-STATECHANGE: Vlan41 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan20 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan92 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan79 Grp 1 state Standby -> Active
    Aug 26 08:24:33: %HSRP-5-STATECHANGE: Vlan111 Grp 1 state Standby -> Active
    Aug 26 08:24:42: %HSRP-5-STATECHANGE: Vlan70 Grp 1 state Standby -> Active
    Aug 26 08:24:42: %HSRP-5-STATECHANGE: Vlan11 Grp 1 state Standby -> Active
    Aug 26 08:24:43: %HSRP-5-STATECHANGE: Vlan22 Grp 1 state Standby -> Active
    Aug 26 08:25:44: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
    Aug 26 08:25:44: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/4
    Aug 26 08:25:46: %VSLP-5-VSL_UP:  Ready for control traffic
    Aug 26 08:25:54: %PFREDUN-6-ACTIVE: Standby initializing for SSO mode
    Aug 26 08:26:36: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  inserted
    Aug 26 08:26:37: %QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT: QOS-HA-BLK-SYNC-PROCESS:  Failure in completing bulk sync before timeout
    Aug 26 08:26:45: %DIAG-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 08:27:00: %DIAG-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 08:27:02: %VSLP-5-VSL_UP:  Ready for data traffic
    Aug 26 08:27:02: %LINK-3-UPDOWN: Interface Port-channel251, changed state to up
    Aug 26 08:27:02: %LINK-3-UPDOWN: Interface Port-channel250, changed state to up
    Aug 26 08:27:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to up
    Aug 26 08:27:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to up
    Aug 26 08:27:02: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 1, physical slot 5, interfaces are now online
    *Aug 26 06:15:45.015: SW1_STBY: SP: Currently running ROMMON from S (Gold) region
    Aug 26 06:26:33.695: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 1
    Aug 26 06:26:33.703: %C6KPWR-SW1_STBY-4-PSOK: power supply 1 turned on.
    Aug 26 06:26:33.711: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 2
    Aug 26 06:26:33.711: %C6KPWR-SW1_STBY-4-PSOK: power supply 2 turned on.
    Aug 26 06:26:35.703: %C6KENV-SW1_STBY-4-FANHPMODE: Switch 1 Fan-tray 1 is operating in high power mode
    Aug 26 06:26:35.711: %FABRIC-SW1_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    Aug 26 06:26:45.507: %DIAG-SW1_STBY-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 06:26:45.507: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:26:45.507: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 5 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:26:55.919: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestChannel due to: the port is used as a VSL link.
    Aug 26 06:27:00.911: %DIAG-SW1_STBY-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 06:27:14.234: %SSH-SW1_STBY-5-DISABLED: SSH 1.99 has been disabled
    Aug 26 08:27:14: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:27:14 MESZ Mon Aug 26 2013 to 08:27:14 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:27:14: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:27:14 MESZ Mon Aug 26 2013 to 08:27:14 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:27:16: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:27:25: %SYS-SW1_STBY-5-RESTART: System restarted --
    Cisco IOS Software, s2t54 Software (s2t54-IPBASEK9-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 19:22 by prod_rel_team
    Aug 26 08:27:25: %SYS-SW1_STBY-6-BOOTTIME: Time taken to reboot after reload =  207 seconds
    Aug 26 08:27:25: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:27:26: %SYS-SW1_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:30 to ensure console debugging output.
    Aug 26 08:27:28: %C6KENV-SW1_STBY-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:27:30: SW1_STBY: TTY0: timer_create_bg error
    Aug 26 08:27:38: %VS_GENERIC-6-VS_HA_HOT_STANDBY_NOTIFY: Standby switch is in Hot Standby mode
    Aug 26 08:27:38: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
    Aug 26 08:27:38: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
    Aug 26 08:27:38: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:27:38: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:27:38: %PFREDUN-SW1_STBY-6-STANDBY: Ready for SSO mode
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  inserted
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  inserted
    Aug 26 08:27:47: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  inserted
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-4-PSOUTPUTDROP: Power supply 1 output has dropped
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-2-PSFAIL: power supply 1 output failed.
    Aug 26 08:28:07: %C6KPWR-SW1_STBY-4-PSREDUNDANTONESUPPLY: in power-redundancy mode, system is operating on one power supply.
    Aug 26 08:28:10: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/5/4: Link down
    Aug 26 08:28:10: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/5
    Aug 26 08:28:10: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/5/5: Link down
    Aug 26 08:28:10: %VSLP-2-VSL_DOWN:   Last VSL interface Te2/5/5 went down
    Aug 26 08:28:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to down
    Aug 26 08:28:10: %VSLP-2-VSL_DOWN:   All VSL links went down while switch is in ACTIVE role
    Aug 26 08:28:10: %LINK-3-UPDOWN: Interface Port-channel251, changed state to down
    Aug 26 08:28:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to down
    Aug 26 08:28:10: %LINK-3-UPDOWN: Interface Port-channel250, changed state to down
    Aug 26 08:28:10: %PFREDUN-6-ACTIVE: Standby processor removed or reloaded, changing to Simplex mode
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  removed
    Aug 26 08:28:10: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  removed
    Aug 26 08:29:01: %c6k_VSD_ROIR-6-TIMER_EVENT_RECV: ROIR::Receiver::Timer Process got TIMER event
    Aug 26 08:29:01: %c6k_VSD_ROIR-6-TIMER_EXPIRED: ROIR::Receiver::For Switch:2 Type 2 Phy Slot 9 - SWITCHOVER TIMER timer expired
    Aug 26 08:29:01: %OIR-3-VSS_PWRCYCLE: Card in Switch 2 module 9, is being power-cycled 'off (Switchover Failed)'
    Aug 26 08:29:01: %C6KPWR-4-DISABLED: power to module in slot 9 set off (Switchover Failed)
    Aug 26 08:29:16: %OIR-6-INSREM: Switch 2 Physical Slot 9 - Module Type LINE_CARD  inserted
    Aug 26 08:30:10: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
    Aug 26 08:30:10: %VSL-5-VSL_CNTRL_LINK:  New VSL Control Link  2/5/4
    Aug 26 08:30:12: %VSLP-5-VSL_UP:  Ready for control traffic
    Aug 26 08:30:20: %PFREDUN-6-ACTIVE: Standby initializing for SSO mode
    *Mar  1 00:00:12.351: ppc_lc_ibc_subsys_init: ETSEC IBC INIT DONE
    Firmware compiled 02-Nov-12 11:44 by integ Build [101]
    Aug 26 06:30:02.155: DFC9: Switch mode info received by DFC..!
    Firmware Download OK:
    Firmware Download OK:
    Firmware Download OK:
    Firmware Download OK:
    Aug 26 06:30:23.979: %SYS-DFC9-5-RESTART: System restarted --
    Cisco IOS Software, c4lc Software (c4lc-SP-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 18:57 by prod_rel_team
    Aug 26 06:30:24.067: DFC9: Currently running ROMMON from S (Gold) region
    Aug 26 08:31:10: %DIAG-6-RUN_MINIMUM: Switch 2 Module 9: Running Minimal Diagnostics...
    Aug 26 08:31:13: %QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT: QOS-HA-BLK-SYNC-PROCESS:  Failure in completing bulk sync before timeout
    Aug 26 08:31:16: %OIR-6-INSREM: Switch 1 Physical Slot 5 - Module Type LINE_CARD  inserted
    Aug 26 08:31:24: %DIAG-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 08:31:38: %DIAG-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 08:31:39: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 1, physical slot 5, interfaces are now online
    Aug 26 08:31:40: %DIAG-6-DIAG_OK: Switch 2 Module 9: Passed Online Diagnostics
    Aug 26 08:31:40: %C6KENV-4-LOWER_SLOT_EMPTY: The lower adjacent slot of module 9 might be empty. Airdam must be installed in that slot to be NEBS compliant
    Aug 26 08:31:40: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/5, changed state to down
    Aug 26 08:31:40: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/6, changed state to down
    Aug 26 08:31:41: %VSLP-5-VSL_UP:  Ready for data traffic
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface Port-channel251, changed state to up
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface Port-channel250, changed state to up
    Aug 26 08:31:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel251, changed state to up
    Aug 26 08:31:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel250, changed state to up
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/13, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/14, changed state to down
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to down
    Aug 26 08:31:41: %OIR-6-SP_INSCARD: Card inserted in Switch_number = 2, physical slot 9, interfaces are now online
    Aug 26 08:31:41: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to down
    Aug 26 08:31:42: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/5, changed state to up
    Aug 26 08:31:42: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/6, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/13, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/14, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to up
    Aug 26 08:31:43: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:48: %LINK-3-UPDOWN: Interface Port-channel210, changed state to up
    Aug 26 08:31:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/6, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/14, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel210, changed state to up
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface Port-channel220, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/5, changed state to up
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/13, changed state to up
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to down
    Aug 26 08:31:49: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to down
    Aug 26 08:31:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel220, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:50: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/9/17, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/10, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/18, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/9, changed state to up
    Aug 26 08:31:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/9/17, changed state to up
    *Aug 26 06:20:21.975: SW1_STBY: SP: Currently running ROMMON from S (Gold) region
    Aug 26 06:31:10.101: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 1
    Aug 26 06:31:10.105: %C6KPWR-SW1_STBY-4-PSOK: power supply 1 turned on.
    Aug 26 06:31:10.105: %OIR-SW1_STBY-6-INSPS: Power supply inserted in slot 2
    Aug 26 06:31:10.105: %C6KPWR-SW1_STBY-4-PSOK: power supply 2 turned on.
    Aug 26 06:31:12.141: %C6KENV-SW1_STBY-4-FANHPMODE: Switch 1 Fan-tray 1 is operating in high power mode
    Aug 26 06:31:12.165: %FABRIC-SW1_STBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
    Aug 26 06:31:24.049: %DIAG-SW1_STBY-6-RUN_MINIMUM: Switch 1 Module 5: Running Minimal Diagnostics...
    Aug 26 06:31:24.049: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:31:24.049: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 5 is skipped in TestLoopback due to: the port is used as a VSL link.
    Aug 26 06:31:34.433: %CONST_DIAG-SW1_STBY-6-DIAG_PORT_SKIPPED: Module 5 port 4 is skipped in TestChannel due to: the port is used as a VSL link.
    Aug 26 06:31:38.941: %DIAG-SW1_STBY-6-DIAG_OK: Switch 1 Module 5: Passed Online Diagnostics
    Aug 26 06:31:54.717: %SSH-SW1_STBY-5-DISABLED: SSH 1.99 has been disabled
    Aug 26 08:31:54: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:31:54 MESZ Mon Aug 26 2013 to 08:31:54 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:31:54: %SYS-SW1_STBY-6-CLOCKUPDATE: System clock has been updated from 08:31:54 MESZ Mon Aug 26 2013 to 08:31:54 MESZ Mon Aug 26 2013, configured from console by console.
    Aug 26 08:31:57: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:32:06: %SYS-SW1_STBY-5-RESTART: System restarted --
    Cisco IOS Software, s2t54 Software (s2t54-IPBASEK9-M), Version 15.0(1)SY3, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Mon 19-Nov-12 19:22 by prod_rel_team
    Aug 26 08:32:06: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:32:07: %SYS-SW1_STBY-3-LOGGER_FLUSHED: System was paused for 00:01:33 to ensure console debugging output.
    Aug 26 08:32:08: %C6KENV-SW1_STBY-4-ADJACENT_SLOTS_EMPTY: Two adjacent slots of module 5 might be empty. Airdams must be installed in these slots to be NEBS compliant
    Aug 26 08:32:19: %VS_GENERIC-6-VS_HA_HOT_STANDBY_NOTIFY: Standby switch is in Hot Standby mode
    Aug 26 08:32:19: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
    Aug 26 08:32:19: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
    Aug 26 08:32:19: %SSH-SW1_STBY-5-DISABLED: SSH 2.0 has been disabled
    Aug 26 08:32:19: %SSH-SW1_STBY-5-ENABLED: SSH 2.0 has been enabled
    Aug 26 08:32:19: %PFREDUN-SW1_STBY-6-STANDBY: Ready for SSO mode
    Aug 26 08:32:27: %OIR-6-INSREM: Switch 1 Physical Slot 1 - Module Type LINE_CARD  inserted
    Aug 26 08:32:28: %OIR-6-INSREM: Switch 1 Physical Slot 2 - Module Type LINE_CARD  inserted
    Aug 26 08:32:28: %OIR-6-INSREM: Switch 1 Physical Slot 9 - Module Type LINE_CARD  inserted
    Thank you
    1
    2
    3
    4
    5
    Average Rating: 0 (0 ratings)
    Following 
    Add Shortcut 
    Report 
    Reply
    Share:
    var switchTo5x = true;stLight.options({"publisher":"dr-8bbf8265-d0c9-5a4c-49f1-616fce884325"});
    <:section id=comments class=comment-wrapper sizset="57" sizcache044116127411908307="1">
    Replies
    Collapse all
    Recent replies first
    <:article class="comment comment-new comment-by-node-author comment-by-viewer odd" about="/comment/9891066#comment-9891066" typeof="sioc:Post sioct:Comment" cid="9891066" sizset="59" sizcache044116127411908307="1"> 
    jozefstaruch a moment ago
    I have this update from cisco:
    This is not buggy behavior. I have both researched for known issues, and
    checked with the dev folks, as well as have tried to reproduce the issue
    extensively but have not seen this behavior. After all these attempts
    this issue should be considered a one-time or transient occurrence.
    --> Would it always be best to do an OIR of the corresponding modul
    whenever we will get this message again or is there any other
    recommendation on how to react in this situation?
    While there are some known behaviors with the XDR process in older
    versions of code, we cannot generalize them in each case. XDR process
    can be a victim in some cases as well.
    Any errors seen with XDR process will require further review from TAC on
    a per case basis. Hence I would suggest getting in touch with TAC if you
    see errors with the XDR process, especially if you see the
    "%FIB-2-FIBDISABLE:" error.
    this should be one time error , remove card and place it back it should help

  • Help with error 16820

    help with error 16820 with trying to update acrobat

    Please refer to following links, might be helpful.
    http://answers.acrobatusers.com/While-updating-acrobat-error-code-showd-16820-solve-q7115. aspx
    http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/acrobat-co m-will-not-update-getting-error-16820/7bbbef64-df3e-4fbd-b552-fc1c7a5983c3?msgId=dcf838d8- a198-4a3a-b034-94a07c2e8648
    If this doesn't work, we need more information here.

  • RoboHelp Server 7 Help System Errors

    Whenever I publish my RH 7 Help project to server, I check
    the RoboHelp Server Web Administrator for errors. I always get Help
    System Error "Requested file cannot be found" for a file called
    bsscfp.txt. To my knowledge, this is a control file generated
    during the publishing process. If this is the case why is an error
    being generated for a file I have no control over? Also, I find the
    Troubleshooting section of RoboHelp Server Web Administrator to be
    rather useless in correcting issues. Is there any reference
    documentation that explains some of the cryptic error messages that
    appear in the Server Web Administrator screen?

    Hi, ouque and welcome to the forum.
    Just to clarify your setup. When you say "Project pane" are
    you referring to the Configuration Manager on the server itself.
    Or, are you referring to something you are seeing from the RoboHelp
    authoring client app's Server Administration pane?
    If you have access to the actual server desktop and view the
    Configuration Manager, sometimes on a new installation, you can do
    a "refresh" and the project will show up.
    A few more questions:
    Have you tried accessing the website and does the project
    come up in the web browser?
    On what kind of web server did you install RHS7? Windows
    2003, etc.?
    Is Microsoft Indexing Services turned on?
    Apparently you were able to successfully publish your project
    to the server so there is "communication" between your desktop and
    the server I gather.
    A few more details and we'll try to help.
    Thanx,
    john

  • Search help: Internal Error.

    Hi,
    I am getting information message : 'Search help: Internal Error' after incorporating code in RETURN event. My aim was to populate the value from Hit list to Value with restriction field and then by removing some search select criteria, again display the hit list. It is coming back to the value with restriction field screen  also populating the fields properly, below 1 information message is coming 'Search help: Internal Error'. If I remove some field from selection and again press the go button, it is doing nothing and system is hanging. The details are given below.
    I have created one search help ZTMVGR1 having the following details:
    Search help type : Elementary.
    Selection Method : MVKE
    Search help exit:  ZF4_MATGRP_EXIT1.
    Display value with restrictions : A
    Field          Import           EXPORT   LPOS      SPOS   SDis     Data Element
    MATNR       X                   X              5             5                     MATNR               
    VKORG      X                   X              1              1                     VKORG
    VTWEG      X                   X              2              2                     VTWEG
    MVGR1      X                   X               3             3                      MVGR1
    KONDM      X                   X               4             4                      KONDM
    MAKTX      X                   X               6              0                     MAKTX
    In the search help exit ZF4_MATGRP_EXIT1 I have used three events:
    1) PRESEL : Purpose of using this was I was not able to see F4 help for few fields in value with restriction screen . I found out that in SHLP-INTERFACE-F4FIELD is equal to 'X', sometimes in search help if that field's value is 'X' , F4 help does not come even if check table exists for that field.
    2) DISP : Purpose, I want to fetch material description field in exit only. MAKTX does not exist in MVKE, so either I need to create a view containing all my fields, or populate the one which is not there in selection method in exit.
    3) Return : Purpose,  I want to put VKORG, VTWEG and MATNR ( MATNR has collective search help, based on material description , we can put material ) . The hit list we get contains VKORG, VTWEG, MATNR, KONDM, MVGR1 and MAKTX. When we double click on hitlist the value returns , I want to populate these entries in value with restriction field. So KONDM and MVGR1 field will be populated. Now I will remove the value of material-low  from selection screen and find out for VKORG, VTWEG and MVGR1/KONDM what materials are there. But after writing the code for event RETURN I am getting information message 'Search Help: Internal Error'.
    My code snippet is given below.
    <removed by moderator>
    Moderator message: please post only relevant code parts, your posts must contain less than 5000 characters to preserve formatting.
    Edited by: Thomas Zloch on May 13, 2011 1:35 PM

    HI,
    In search help exit you need to use the below mentioned function modules
    'F4UT_PARAMETER_ALLOCATE'          For allocating fields
    'F4UT_PARAMETER_VALUE_GET'       Get Value
    'F4UT_PARAMETER_RESULTS_PUT'     put Value
    In the same order.
    Thanks & regards,
    Bhargav.

  • Please Help - "page error" / a system error occurred

    I am very basic with Coldfusion Developed websites and pretty awesome on HTML and PHP. While working on a website I made an HTML change and added a line to a page. All works well on the test website/server but after uploading the changed page the page went offline/errored a day later.
    I have an error receipt and am hoping to resolve this issue with some insight from a good Coldfusion Developer or Programmer.
    PLEASE HELP, see error below.
    A system error occurred: http://www.mix.co.zm/mix_schools.cfm?
    Error - struct
    Detail    Note: If you wish to use an absolute template path (for example, template="/mypath/index.cfm") with CFINCLUDE, you must create a mapping for the path using the ColdFusion Administrator. Or, you can use per-application settings to specify mappings specific to this application by specifying a mappings struct to THIS.mappings in Application.cfc. <br> Using relative paths (for example, template="index.cfm" or template="../index.cfm") does not require the creation of any special mappings. It is therefore recommended that you use relative paths with CFINCLUDE whenever possible.
    Message    Could not find the included template components/mix_documents2.cfm.
    MissingFileName    components/mix_documents2.cfm
    StackTrace    coldfusion.tagext.lang.IncludeTag$NoSuchIncludeTemplateException: Could not find the included template components/mix_documents2.cfm. at coldfusion.tagext.lang.IncludeTag.setTemplate(IncludeTag.java:349) at cfmix_schools2ecfm527774291.runPage(D:\hshome\mixnet\mix.co.zm\mix_schools.cfm:15) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:231) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:416) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:360) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:94) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70) at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:79) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:200) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at jrun.servlet.FilterChain.doFilter(FilterChain.java:86) at com.intergral.fusionreactor.filter.FusionReactorFilter.i(FusionReactorFilter.java:566) at com.intergral.fusionreactor.filter.FusionReactorFilter.c(FusionReactorFilter.java:258) at com.intergral.fusionreactor.filter.FusionReactorFilter.doFilter(FusionReactorFilter.java: 164) at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 ) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at jrun.servlet.FilterChain.service(FilterChain.java:101) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543) at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203) at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428) at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
    TagContext    Error - array
    1    Error - struct
    COLUMN    0
    ID    CFINCLUDE
    LINE    15
    RAW_TRACE    at cfmix_schools2ecfm527774291.runPage(D:\hshome\mixnet\mix.co.zm\mix_schools.cfm:15)
    TEMPLATE    D:\hshome\mixnet\mix.co.zm\mix_schools.cfm
    TYPE    CFML
    TagName    CFINCLUDE
    Type    MissingInclude

    With LR closed move the preferences file to the Trash as described at the below link. You will lose your Preferences settings, so you may want to record them if unsure what you have changed from the default settings.
    http://helpx.adobe.com/lightroom/kb/error-changing-modules-lightroom
    DO NOT RESTART LR!
    Next uninstall LR and then completely shutdown your system and turn the power OFF. Your catlog(s) will not be removed, so no worries.
    Restart your system and reinstall LR using the latest version download available (LR5.4, LR4.4).
    What version of LR and OS X are you using?

  • My macbook pro intel core duo 2 keeps restarting intermittenly. Help with error code.

    I have run a Hardware Test, and it gives the follwing error code. Can anyone tell me what this is? I recently had my logic board replaced within the last 3 months, so it shouldn't be a problem there.
    Thank you very much for any and all help.
    Error code:
    4SNS/I/40000000:TGOH-128.00

    Online references possible memory issue? Sensors?
    https://discussions.apple.com/thread/3140607?start=0&tstart=0
    Keep taking it back and they keep switching parts until the problem is gone.

  • Need help with error message 213:8

    Need help with error message 213:8, this error message prompted after re-installing CS5.5 on the same machine (W7 Pro)
    Thanks.

    Hi TKA_,
    Please try the solutions mentioned on following forum thread.
    http://support.muse.adobe.com/thread/1305941?start=0&tstart=0
    Let me know if it works?
    Regards,
    Sumit Singh

  • How to explicitely write PLSQL code for "Help - Display Error"? [SOLVED]

    I'm using menu DEFAULT&SMARTBAR and I'd like to write command in PLSQL code for "Help - Display Error" to display error. Has anyone any idea how to do this? I can not find syntaks in form help for this.
    Message was edited by:
    marussig

    Display_Error;

  • HELP PLEASE - ERROR ON PANSONIC P50VT20B AND Panso...

    HELP PLEASE - ERROR ON PANSONIC P50VT20B AND Panasonic HOME CINEMA SC-BTT775.
    the moment i login using the tv or blu-ray i cannot choose anything other than ' Back to homepage ' message which is displayed under my contactlist on tv... at times it says too many contacts... Kindly help... the camera is skyoe ty-cc10w for panasonic tv's and blu-ray...

    Same issue

Maybe you are looking for

  • Genre options - any way to change?

    Does anyone know if it is possible (if it isn't, I think this is a BIG flaw, if it is is, I've completely missed it) to change the options on an Ipod or in Itunes so that when I click on Genres (on my Ipod) and then on Soundtracks (hey, some people l

  • SQL Server 2014 Express Installation Failure

    Hi, Now trying to install SQL Server 2014 Express on my work machine.  Here is the error log.  Any ideas?  The error help link is useless. Overall summary:   Final result:                  Failed: see details below   Exit code (Decimal):           -2

  • Nano using Logitech Speakers ----

    I'm having this problem using my nano with Logitech MM50 speakers. When I plug in headphones it works, but when I plop the nano in the docking area of the Logitech speaker box, I get no audio sound? In checking to see if the docking station works, I

  • Byte to char casting

    Hi friends I am using some third part api  for my application. This api expects utf8 string from my application. I write some dirty methods to convert my string to utf8. It's works properly except some cases when second byte of character contains onl

  • When will the FMS 3.0 be released?

    Hi all, Anybody has idea that when will the FMS 3.0 be released? How can I contact to adobe via e-mail? I can't see any email address in the official site... Thanks a lot!