Nested Editable Regions Error Message

I'm trying to create a dynamic template. I've saved a header
and footer as library items, and I want to include them in the
template. In addition I want to have an editable region between
them. For some reason, when I go to save as template, the error
message comes up. It says 'error at line 57, column 323(absolute
position 2998) of ... :nested editable regions' . I have narrowed
this error to be caused by the header (which was created as a
sliced image in photoshop), but for what reason I don't know. Any
ideas why I am getting this error message and what I can do to fix
it? The template won't save otherwise and I can't find any
information on dreamweaver 8 help menu.

There is a parent file and an included file. Here's an
example -
The parent file is this -
<html>
<head>
</head>
<body>
<!--#include file="foo.html" -->
</body>
</html>
and foo.html (the included file) is this -
<p>Hello World</p>
The file you have linked me to is a badly broken template
page. It's broken
because the Library items have not been made properly since
they contain
redundant <body> tags, CSS, and javascript as well.
This will never work the way you want, particularly not in
DW....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Genius2112" <[email protected]> wrote in
message
news:eo41an$93v$[email protected]..
>
http://www.lyncourtrec.com/Lyncourt%20Rec%20Website/Pages/Template.dwt.asp
>
>
> Sorry, I'm not quite sure what you meant by "being
included". The images
> aren't with the header b/c I didn't adjust their source
folder since I had
> to
> upload it on a different site (I don't have a hosting
plan for this site
> yet).
> Hope this is what you were looking for. Thank you for
your help.
>
>

Similar Messages

  • Editable Region Error Message

    I have one DW template (CS3) that gives an error message when
    you try to make a new page using the template: "You have made
    changes to code that is not marked as editable. If you retain those
    changes, they will be lost the next time you apply a template to
    this file. Do you want to retain the changes until then?
    This message appears immediately after you create new page
    from template and save. I can see the cursor in the code view and
    it clearly inside begin editable region tag. I've even crreated an
    alternate template from scratch and am still getting the
    message.

    The error message is likely a red herring. It can be
    triggered by any
    validation error on the page, including in linked CSS files.
    Does the page
    validate?
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "hexpix" <[email protected]> wrote in
    message
    news:gqgnak$102$[email protected]..
    >I have one DW template (CS3) that gives an error message
    when you try to
    >make a
    > new page using the template: "You have made changes to
    code that is not
    > marked
    > as editable. If you retain those changes, they will be
    lost the next time
    > you
    > apply a template to this file. Do you want to retain the
    changes until
    > then?
    >
    > This message appears immediately after you create new
    page from template
    > and
    > save. I can see the cursor in the code view and it
    clearly inside begin
    > editable region tag. I've even crreated an alternate
    template from scratch
    > and
    > am still getting the message.
    >

  • Nested Editable Region

    I am trying to save a template and update all the attached
    files but when I do, I get the following message:
    There is an error at line 8, column 7 (absolute position 507)
    of “E:fredbabb.com\index.html”: nested editable regions
    It comes up for each page that is connected to the template
    and once I click ok on each of them, it comes up with the following
    and nothing gets updated:
    Updating E:\fredbabb.com\
    index.html -- not updated, error in template or instance file
    wholesaleapp.html -- not updated, error in template or
    instance file
    wholesale.html -- not updated, error in template or instance
    file
    thankyou.html -- not updated, error in template or instance
    file
    contact.html -- not updated, error in template or instance
    file
    about.html -- not updated, error in template or instance file
    store.html -- not updated, error in template or instance file
    Done.
    files examined: 7
    files updated: 0
    files which could not be updated: 0
    total time: (0:01:10)
    I have tried to find a nested editable region and cannot find
    anything. If you know how to read code, you can check the source on
    the website to see if you can find anything...www.fredbabb.com
    Thanks. I need help.
    babbstudios

    Your Template is horked.
    Please upload it to the site and post a link to it so we can
    see the code.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "babbstudios" <[email protected]> wrote in
    message
    news:gfhuk9$rvl$[email protected]..
    >I am trying to save a template and update all the
    attached files but when I
    >do,
    > I get the following message:
    >
    > There is an error at line 8, column 7 (absolute position
    507) of
    > ?E:fredbabb.com\index.html?: nested editable regions
    >
    > It comes up for each page that is connected to the
    template and once I
    > click
    > ok on each of them, it comes up with the following and
    nothing gets
    > updated:
    >
    > Updating E:\fredbabb.com\
    > index.html -- not updated, error in template or instance
    file
    > wholesaleapp.html -- not updated, error in template or
    instance file
    > wholesale.html -- not updated, error in template or
    instance file
    > thankyou.html -- not updated, error in template or
    instance file
    > contact.html -- not updated, error in template or
    instance file
    > about.html -- not updated, error in template or instance
    file
    > store.html -- not updated, error in template or instance
    file
    > Done.
    > files examined: 7
    > files updated: 0
    > files which could not be updated: 0
    > total time: (0:01:10)
    >
    > I have tried to find a nested editable region and cannot
    find anything.
    > If
    > you know how to read code, you can check the source on
    the website to see
    > if
    > you can find anything...www.fredbabb.com
    >
    > Thanks. I need help.
    >
    > babbstudios
    >

  • OIF - can I edit specific error messages back to user?

    I've had a request from end-user support to change a specfic error message generated by OC4J /shareid app.
    At present if a user tries to access a session that's been invalidated (logout, session timeout, etc.) they are presented with an error:
    Identity Federation Error
    The signon or signoff to the partner domain could not be completed. Contact your administrator. (Error ID TSE016)
    I'd like to change that to something more actionable like "Please close your browser and try to access resource again."
    Is anyone aware of how to edit these error messages?

    Alright. If you can share the mod_rewrite approach you are planning, that would be great.
    In any case, you got me curious enough to poke around for the message catalog in question. The message is from shareid-user-messages*.properties inside $ORACLE_HOME/jlib/idmbridge.jar.
    To update these, you'll just need to update the jar file -
    cd $ORACLE_HOME/jlib
    jar -xvf idmbridge.jar shareid-user-messages_en.properties shareid-user-messages.properties
    Change both files to edit the message with ID ERP001 (it's the first one in the catalog) as you need, save the files, and then..
    jar -uvf idmbridge.jar shareid-user-messages_en.properties shareid-user-messages.properties
    Restart OIF and you should be done. In case you have users with browser languages other than English, you can update the other catalogs (shareid-user-messages_fr.properties, shareid-user-messages_de.properties etc.) as well.
    I can see why Oracle would rather have customers not do this, but I'm not sure why the user-facing messages are jarred up in the first place.
    Hope this helps.
    -Vinod

  • Please Help Nested Editable Region Image & Spry

    Please Help Me.
    New to Dreamweaver. I've been given a "grandchild" nested temple with only one editable region to alter. I've read and Googled since Saturday. My brain actually hurts.
    Goal
    - Insert my background image into region
    - Add Spry accordion to mid left
    - Add Spry collapsible to bottom right
    How can 3 things be so hard? Please, can someone walk me through this? Thank you

    I've been given a "grandchild" nested template with only one editable region to alter.
    Nested templates.  Aaaaaak! There's no advantage in nested templates, ever.  They're so problematic it makes my head hurt just thinking about them.
    If you have the parent and grandparent template.dwt files to work with, you'll need to insert Editable Regions to hold your scripts and other supporting widget code.
    If you don't have those files and you can't edit the <head>, you can't insert widgets into Template child or grandchild pages.  You'll need to detach the page from Templates.
    Nancy O.

  • Dreamweaver template giving up "instancebegineditable tag inside editable region" error

    I have been searching the internet and any forum I can find relating to Dreamweaver and find it has been a comman problem for a lot of people but the solutions they got have not helped me. I created a template by following steps via a helpvid.net tutorial and the site looked very good for being basic enough but since last night when I try save the template it gives up the error "there is an error at line 8, column 47 (absolute position 789) of "file address": InstanceBeginEditable tag inside editable region." Now from what I have read on the forums it usually means there is a mispelling or something placed inside the region when it shouldn't be but there is only 50 odd lines on it and can't see any problem. When I view the files it gives the error about, there are duplications of the "begin editable region" a number of times but they shouldn't be there because they aren't on the template. Im also finding that before this error came up the pages looked fine when uploaded but now the footer height which was set to 20px is 200px when uploaded and I have checked all coding for it and checked the Divs but still see no error. I have uploaded my tempalete and some of the pages that its giving errors about to see if that helps, not sure if its best to just paste wall of coding so ill post links to the files and if code needs to be pasted here ill do so. http://dublinmoulding.com/ <- site im working on, it can be seen the footer is very big. Should be 20px height but inspect element shows its 200px - #wrapper #footer {     color: #FFF;     height: 200px; On the template it is #wrapper #footer {     color: #FFF;     text-align: center;     margin: 0px;     font-size: 18px;     font-style: normal;     font-weight: lighter;     font-family: Arial, Helvetica, sans-serif;     padding-top: 5px;     padding-right: 0px;     padding-bottom: 5px;     padding-left: 0px;     height: 20px; http://dublinmoulding.com/dreamweaver/temp1.dwt <- my tempalate The error is given up on every page created using the template
    **Update**  I edited the file names of some of the pages that I used the template on so now it shows the coding.
    http://dublinmoulding.com/dreamweaver/index.html6  <- my index page
    http://dublinmoulding.com/dreamweaver/about.html6 <-about page

    No need for tricks.  We can view source code directly from our browsers or with Inspect Element.
    Like I said, I don't see any code errors in your Template or child pages. 
    If DW continues to display errors,  the first thing to try is Deleting Corrupted Cache in DW
    http://forums.adobe.com/thread/494811
    If that doesn't help, try Restore Preferences
    http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
    Nancy O.

  • Nested Repeat region error

    I am trying to create a simple nested repeat region and I get a mismatch error. I ran a SQL trace and it seems to not be passing the key from the master table , but rather @p1 in its place. any ideas?

    I am trying to create a simple nested repeat region and I get a mismatch error. I ran a SQL trace and it seems to not be passing the key from the master table , but rather @p1 in its place. any ideas?

  • HT201250 Time Machine + MyBook World Edition 2 Error message after update

    I purchase a 2TB MyBook World Edition 2 at my local Apple store to back up the computers on my home network.  After the latest update to Snow Leopard, Time Machine will no longer connect to the backup.  I get the following error message:  Connection Failed. The server "MyBookWorld.local" may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.

    Never mind, I fixed the problem by removing a lock feature from my external drive.

  • Editing Essbase SAI Error Message

    Perhaps a weird question.....
    But in 11.1.1.3, is there a way we can edit the Error Message that Spreadsheet Add In returns to the user?
    In particular, when a user has more than 65K rows and performs an Essbase function, it will give the user a error that has nothing to do with the #of rows. It is cryptic enough that it might incite panic on some of my users.
    "Essbase has encountered an internal Excel error. Your sheet will not be overwritten and none of your data will be lost. However, you are strongly urged to exit Ecel and restart in order to clear up the problem."
    After constraining the #of rows, we no longer get the message.
    So... we thought that maybe we can add "Limit your rows to less than 65K" to the message.
    Any thoughts?

    The particular error message the original poster referred to is specific to the Add-In - it isn't raised by the Essbase server or client per se, so I don't think you'll find it in essbase.mdb. Similar to "There are no active connections" (if you click 'Disconnect' in the Add-In without making a connection first), for example.

  • Edit Error Message

    When a portlet times out, or other reasons, you get the unknown error or timeout error message. Can we edit those error messages?

    You can search for that error in the in the message string files (it'll probably be in the browsing messages file), change it, and bounce your web server for the change to take effect. Be sure to change the message for every language, not just English.

  • 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

  • Edit Esbase Error Messgae

    Hell @all,
    i'm wondering if it is possible to edit essbase error message to make it friendlier for the end user. In my case i disabled all connections via maxl script, so that the user get error message "Application %App% is currently not accepting connections" while the calculation is being processed. After the calculation is completed all users are able to connect the application.
    I'm grateful for your support.
    many thanks,
    ilias

    Ilias,
    Error (1054009) application [%s] is currently not accepting connections
    The Application currently does not allow connections because
    - the "Allow connects" option is not checked
    or
    - the ENABLELOGIN command was not used in Esscmd script after the DISABLELOGIN command.
    You can try the following:
    1. In Application Properties
    Ensure that the ALLOW CONNECTS option is checked for this Application.
    In Essbase Administration Services (EAS) Console, under APPLICATION -> EDIT PROPERTIES -> GENERAL.
    Allow connects
    - When unchecked, prevents any user with a permission lower than Application Designer from making connections to the database that would require the databases to be started.
    - This includes using the ESSCMD SELECT function to start the database.
    - ALLOW CONNECTS option is on by default.
    ESSCMD Sessions
    When running ESSCMD Sessions - make sure to use ENABLELOGIN once all operations after DISABLELOGIN have completed.
    Stopping / unloading the application will automatically ENABLELOGIN, without the use of the command.
    Reference: Doc ID 590473.1
    Hope it helps...
    KosuruS

  • Legacy sequence importing - running out of regions error

    So it finally happened. I want to access several sequence files from older versions of Logic. Currently I'm most interested in opening some 6.3 platinum versions.
    I am running the latest greatest Logic 8 on an intel desktop...which obviously is useless for this portion of my exercise. I do have version 7 on a laptop, and version 6.3.1 on an old OS9 machine.
    Attempting to open with V7 prompts me with a "running out of regions" error message, then crashes the app when I select "cancel".
    Attempting with V6 yields a similar prompt "Running out of sequences" message. When I "cancel" I get another prompt "IsUnsorted: Track== NULL!" with "Bad" as my option, which then throws it into an endless loop, cycling the 2 statements.
    Anyone have any mojo for me? Is it some kind of plugin issue, or audio card, or moon cycle?
    This issue has really hit home the fact that we are creating an entire generation of music that will not be able to be accessed in element form. It also really points out just how **** old I am...sigh
    Thanks in advance for any and all info.
    Sean

    Visit The XLab FAQs and read the FAQ on freeing up space on the hard drive. Also, see Freeing space on your Mac OS X startup disk

  • Error message on PE 3.0.2.  Crash when pointer click on Titles

    Hello Everyone,
    Vista Prefeesional.
    AVI files and projected worked and stored on UBS pocket hard drive.
    All avi files in system and on time line.
    Produced Titles. Made mistake so want to edit. Every time I click to edit, get error message, click ok, the PE disapears and I'm looking at desk top.
    Other facts. Vedio shot on JVC GZ-HD3. It usess silly TOD files. Converted to avi using PRISM VIDEO CONVERTER. Shot in 1440 x 1080. Set up PE project on 1440 x 1080. JVC claim the firewire will work for streaming at 1440 x 1080. I have NEVER got it working. Want to chuck camera in bin.
    It is so bad now I am unable to finalise my project (my son competing in the solo (bag) pipes hampionships... he came first in state. Also recorded his band; they came first too. Project important for evaluation before next competition.
    Thanks for your interest in this forum. Rodney.

    Thanks Steve,
    Sorry about the long winded explanation. I have in fact taken a screen shot of the problem but not sure whether I can get it on this forum.
    Anyway, I'll put it more clearly.
    1. Have imported video clips and put them on time line.
    2. Have used jpegs and gifs as background (when I need them).
    3. Placed titles on graphics. These titles say who is playing (the bag pipes in this cast) and what song they are playing.
    4. To save time I 'copied' the titles and pasted the copies along the time line. these copies need editing. the words are to be changed but I wish to retain the format.
    5. I discovered when you copy and past these titles, they all remain the same. If you edit them, all the titles change. This is a personal problem - I can not do copy and past for individual titles in the future.
    6. The problem. When I double click on the title I wish to edit, PE3 says that it has encountered an error (no error code). When I click ok, then the program instantly shuts down and I find myself back at the desk top.
    7 I have reinstalled the program, but it still does it.
    Any ideas would be greatly appreciated. Thanks. Rodney.

  • Edge Animate could not find .html error message

    I have a series of animate files that I have created. When I try to open the files to make edits, this error message appears:
    All of the files are in the same folder, and I have not changed any file names or coding outside of animate. I can open the .html file and edit that, but when I go to save or publish, I get this message:
    I've seen the first message on a couple of discussion threads, but it didn't really seem to resolve the initial problem. I'd love it if someone had a fix for this.

    Hey guys,
    Sorry for the trouble you're running into -- maybe check these few things.
    Are you trying to open a published file? Only the original .html file can be opened with Animate; the published files aren't runtrippable.
    Has the .an or associated .html file been renamed? Have any of the dependant folders or files been renamed? The naming used when saving needs to remain in tact. In the future we're looking to loosen this restriction, but if you rename the .html or .an Animate will barf when you try and open.
    Is the file saved in a locked folder? Permission issues can arise if you have restrictions placed within the OS. If you're not sure where to look for this, Here's an article on how to change permissions on Windows. Be sure to check the directory you're saving to and publishing to. A quick test might be to copy the entire AN project/files onto a conventionally unlocked folder like the desktop and try running from there.
    For the users in this thread: Can you describe your operating system, and where your files are being saved and where Animate is installed? For example C:\Windows\Blah\Programs
    Thanks,
    Sarah

Maybe you are looking for

  • TS1559 why is my wifi greyed out

    SO FRUSTRATED, BOUGHT IPHONE 4 FROM A RELATIVE, WIFI IS GREYED OUT, ALSO BLUETOOTH, HAVE DONE FULL SOFTWARE RESTORE TWICE, NO GOOD WHAT IS THE DEAL?

  • Setting up the Mysql Driver

    Does anyone know of a good link, regarding the setup of a Mysql jdbc driver on a Unix platform. I need to setup a test page and do not know which *.jar file should be referenced in the classpath. Is it a matter of just downloading the [???] jar file

  • Windows vista help - AppleMobielDeviceHelper popup

    a window keeps popping up and saying AppleMobileDeviceHelper has stopped working, and it will close out, then op up, then close, then pop up again and it just keeps doing that unless i close itunes. has anyone else had this problem? and if so how can

  • I can't stand photo stream...help

    Hello, Now that photostream is on all of my devices, I can't figure out how it is supposed to work.  some of my photos are just under the photostream heading in iphoto, some are organized by date, and some are in both places.  How do I fix this.  can

  • Photo book with iPhoto on iPad?

    Hello is it possible to create a photo book with iPhoto on iPad? (Like with iPhoto on minimac) Reg ratouns84