Bad Score Style Deleted... error message?
I can't recall having this ever happen before...
I'm trying to open a song I was working on yesterday, but the latest version, as well as all back-ups, give me the message "Bad Score Style Deleted" when I try an open it, and even though there is an "OK" button to click, all that happens is I click the "OK" button repeatedly, and the error message remains, never goes away, and the song never opens.
This particular song was started from a SMF that the drummer had sent me along with his audio tracks, but I've done that many times before, without any problems.
Any ideas what this means, and how to get past it, before I start all over...
Thanks...
Adobe Digital Editions
Similar Messages
-
Deleting error messages in PI 7.1
Hi ALL,
I cancelled system error messages from Message monitoring of RWB I need to know what happens to that message is that completely removed from the tables if yes how does it happen.
Is there any other method of removing messages which are error and successfully processed...I am told there is a method of archiving and deletion of messages can you send some document for that we are using PI 7.1.
What will be the retention period of messages ideally.?
Thanks
SouzThe archiving and deletion of messages happens from the DB and the configuration is the same as it happened for lower versions.
So the document for PI7.0 should hold good for PI7.1 also.
Regards,
Abhishek. -
Deleting error messages in ABAP stack and JAVA stack
Hello,
found some useful answers here about deleting messages
which are successfully delivered!
What I miss is an answer about:
a) Error messages in RWB
In Component monitoring -> Archiving you can plan a job to delete messages in status "successful" or "Cancelled with errors".
To cancel jobs you have to do this one by one. With reaction time from page manual cancellation needs hours for 100 messages (Ok, there is a multiple selection button you can use to tag per list screen!).
Now I have lots of message here
- System error
- to be delivered
- cancelled with errors (from system, special case, see next question)
ready to be erased (yes, sure about that!)
Is this the only way here to proceed?
Other question: looks like there is a default time frame for the job which looks like it is more than two months for "successful". "Cancelled with errors" is only deleted from list when reaching this status with the available button "Cancel" but not for messages with status "Cancelled with errors" set by the system.
Any chance to change that time frame.
And what about the messages "Cancelled...." by the system?
b) ABAP stack
OK, delete job is running. But looks like there is a default time frame "delete older than 2 months" (different from a! where it is more than 2 months)
I tried to delete some error messages with function "Cancel message with errors".
Now these messages are cancelled in SXMB_MONI (displayed with different status sign "Pencil").
Starting deletion job has no effect on them. Why? Because they are cancelled today and are not considered by the time frame of the deletion job?
Any help is appreciated!
(This tool is confusing me more and more! )
Hm, looks like nobody knows about this issue?
Regards
DirkHi Dirk,
I am also facing the issue for deleting the messages with errors or if i have cancelled them.
Did you find any solution for these issues. Kindly let me know if you have find out any solution.
thanks
Gopesh -
Issue on deleting error message in WebUI
Hi Experts,
I have deleted one standard error message in DO_PREPARE_OUTPUT with some condition in header level but I am having below issues.
Issue one :
Now error is not showing in webui at header overview screen but allocated space for that error message is showing in output screen with white space.
Please help me how to remove that space.
Issue two:
When I open Item overview screen, again that message is showing in Item overview screen.
I am using the below code to delete the message and its successfully deleting the message but when I switch to other screen its again showing.
Please help me how to delete it completely on one go.
Code:
zcl_crm_ic_tools=>delete_message( iv_number = '419' iv_id = 'CRM_PRODUCT_I' ).
Method: delete_message
ls_message-number = iv_number.
ls_message-id = iv_id.
ls_message-type = iv_type.
APPEND ls_message TO zcl_static_reference=>gt_delete_msg.
endmethod.
Appreciate your help.
Kind Regards,
ShaikHi Shaik,
Refer to the following links
How to remove Std. CRM Messages
Delete UI Messages
You can also use COLLECT_MESSAGES with Delete Flag of CL_BSP_WD_MESSAGE_SERVICE class.
Thanks,
Chirag. -
Deleting error messages from EOIO Queue Automatically at run time
Hi Experts,
I am sending data from proxy to database. In case of error message i want that mesage to be cancelled at the run time and the remaining messages in queue should be processed, whether the error is in Integration engine or adapter engine. Please suggest me how to cancel the error or failed messages automatically (Alert has to be raised for the failed messages) so that my queue is processed successfuly
and failed messages can be sent manually.
Thanks
Ajay GargHi,
for creating and sending Alert check the links.
Alert Configuration
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Inbox
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Defining Alert Classifications
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Triggering Alerts
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Setting up alerts
Setting up alerts in RZ20
Alert Management
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04141e8-0f11-2a10-adaa-9d97b062c2df
Alert Notification
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90f449a8-a6db-2910-a386-d2b5999f5751
Regards,
Phani -
How do I resolve "Parse Failed: Bad Connect String: Database" error message
I have a user who is editing a select statement in a BOXI 3.1 Web Intelligence query. He is gettng the error message in the subject line.
Hi
can you please try to run the edited SQL statement directly against the SQL server? Do you get any errors then?
Regards,
Stratos -
What is the procedure to delete Error messages in SXMB_MONI?
How to schedule an archiving job / delete job in SXMB_ADM?
How to get rid of the messages with errors in SXMB_MONI?
Thanks,
BhaskarHi Bhaskar,
<i>>> How to schedule an archiving job / delete job in SXMB_ADM?</i>
Have a look at the following link :
http://help.sap.com/saphelp_nw04/helpdata/en/cd/20bc3ff6beeb0ce10000000a114084/frameset.htm
Regards
Suraj -
Getting error message CT bad param: invalid matrix
When we try to print this form in Reader 9 or X, we're getting the CT bad param: invalid matrix error message. Any thoughts on what's causing this and how to fix it?
Thanks,
MDawnjava.sql.SQLException: ORA-00904: "SANDY": invalid identifier
Looks like the sql you are submitting is invalid.
Print out a copy of the sql you are trying to run and you will probably get:
SELECT * FROM OURUSERS WHERE usr = Sandy and password = secretThat isn't valid sql. It is missing quotes around the values you are checking.
This is the corrected sql query:
SELECT * FROM OURUSERS WHERE usr = 'Sandy' and password = 'secret'so one solution would be:
String sql = "SELECT * FROM OURUSERS WHERE usr = '" + user + "' and password = '" + pwd + "' ";However that is not optimal. It exposes your code to sql injection attack.
The better way is to use a prepared statement:
String sql = "SELECT * FROM OURUSERS WHERE usr = ? and password =?";
st = con.prepareStatement(sql);
st.setString(1, user);
st.setString(2, password);
rs = st.executeQuery();cheers,
evnafets -
How do I delete error message that says "unable to purchase certain book and 4 others". Have reset account ant credit info. any ideas?
Have you tried tapping on your id in Settings > Stores on your phone and logging ouy of your account and then logging back in and seeing if that 'refreshes' the account on it ?
-
Populating the error message log (while executing BAdI implementation)
Hi there,
I have a BAdI to implement CRM_ORDERADM_H_BADI where it will check certain header data. If there is a certain condition that is met, we must not allow the transaction to continue by adding error message on the top (the red button). How can we populate this error log within the BAdI implementation (putting it in codes in the method of the BAdI implementation).
Many thanks in advance,
Regards,
MuJiput like this
data: w_msg type standard table of shp_badi_error_log initial size 0,
msg like line of w_msg.
if sy-subrc ne 0.
msg-msgty = 'E'.
msg-msgid = 'YW2'.
msg-msgno = '041'.
msg-msgv1 =
'PGI not allowed ,Pls Enter Truck No in Bill of lad.Field'.
append msg to ct_log.
endif.
<b>In BADI u cannt raise Error Messages but u can Post the Messages to Application Logs, So u have to Update ur messages to CT_LOG.</b>Regards
Prabhu
Message was edited by: Prabhu Peram -
Error Message : Object does not exist (status management)
Hi Gurus,
I am working on tcode IW52(Change Notifications). and using badi's for validations at different points.
1. Order level,
2. Notification,
3. Task level validations.
In the task level validations, I have an requirement that if certain condition is met, than user should not be able to delete the task. I have no problem doing that, I am able to restrict it.
Now the issue is :
Say you have 6 tasks, and condition is met for the 5th task and I try to delete it. then the error message "can not delete task" is getting triggered from the badi.
and after this error message if you try to do any functionality on the 6th task, I am experiencing error message "Object does not exist (status management)".
Is anyone aware of this error message, any suggestions are highly appreciated.
Thanks in advance.
Shrikant
Edited by: Alvaro Tejada Galindo on Mar 17, 2008 1:56 PMHi ,
You have posted this question long back that is one and half year back nearly.
You got an error message in IW52 stating Object does not exist ( status management ).
Now iam also facing the same problem in iw22 transaction. Can you say me how you solved if you remember. -
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 youYou 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 -
Customer error message in sales order on save
Hi Friends,
as per requirement i have to raise the error message and system should enable the field to change values. This should happen when condition is not met on Saving of Sales order.
For this, i have used the user exit USEREXIT_SAVE_DOCUMENT_PREPARE. But the problem is system throwing error message and all r in display mode only. as per my requirement system should allow to change the error value field.
i have verified many posting in this SDN, but nothing is working out.
Please guide me, how to raise the error message and system should enable that filed.
My doubt is where should i raise the error message in sales order (MV45AFZZ)??? if any badi to raise the error message also fine for me. I tried many ways like... message with display like..... and set / get parameters and badis.... but not able to find the correct solution.
Thanks in Advance.
BalaHi
You need to use check for enahcement spot, which will be help to you.
Bcz you are throwing custom error message in the standard transaction, once the error is display, you could not able to change the values. your prob can be solved by using the enhancement sport.
This is include name (Include:MV45AF0B_BELEG_SICHERN).
In the above include, you need to create a enhancement spot after this spot (ENHANCEMENT 16 OI0_COMMON_SAPMV45A.)
write your custom code and while displaying an error message. set flag = 'x', then use below code. It will display error message once you press ENTER, you will get the sale order in change mode, you change the values.
IF flag = 'X'.
fcode = fcode_gleiche_seite.
perform fcode_bearbeiten.
ch_subrc = 4.
exit.
ENDIF. -
Issue with Archiving & Deletion of messages in PI ,SXMB_MONI messages
Hello experts
I am working on Archiving & Deletion of messages in PI ,SXMB_MONI, i have fallowed all the steps which are avialable in /people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2, but the messages still there in SXMB_MONI.
please help me to resolve this issue.
regards
chandraHi Krish
i have fallowed steps like....
in SXMB_ADM
>>>step 1: Define the interface for archivng and retnetion period
>>>step2):Schedule Archive Jobs,
after this i have checked the in SM37 the jobs got sheduled and released after that it showing finished.
>>>step3):ARV_BC_XMB_WRP<date> (archiving, step 1)
ARV_BC_XMB_DEL<date> (archiving, step 2)
here i am getting message like "0 XML messages got archived".
"0 XML message for deleated".
I have doubt in SXMBPMAST table here when i check the status of interface , ITFACTION field is containing the value INIT and if I understood correctly it job deletes only those messages where ITFACTION is set to DEL.
We are actually trying to delete the messages avoiding archiving but what I am seeing is we cannot delete error messages and for them we must have to go through archiving. Please correct me if I am wrong.
Thanks
Chandra -
How do i pass the error message at header level in CRMD_order
Hi all,
i got one requirement like when i create/change the sevice order (CRMD_ORDER)
if net_value is more than 1000 i have to set the message 'E' like 'order is blocked'
else 'approved' at header level before going to save the order.
please help me out it is high priority and as i am new to CRM.
thanks in advance.
Thank you,
Madhu.Anil
You have to look for a BADI to add the Error Message.
Also use the FM CRM_MESSAGES_DISPLAY to display the message !
Thanks
<b>Allot points if this helps!</b>
Maybe you are looking for
-
Treating loops as a whole, not separately - Smartform
Hi, In a smartform, each table and it's loop is treated separately. For example, if a table has a loop into a structure, the table will process each record of the loop. How do you treat the loops as a whole of several tables? For example, table 1 loo
-
When I plug in my ipod, it doesn't show up in itunes at all. but it charges fine, and it shows up in my computer. What do I do?
-
Premiere CC "Not Responding" Message after opening
Hi, Two of my projects (one last week that I managed to get open) have crashed. They open up on CC, then the project loads and I can see everything fine. However, when I click anywhere, Premiere goes white and it says "Not Responding" on the top. I
-
What is the correct procedure for repairing permissions
I am getting ready to upgrade to Tiger from Panther. I have used the disk utility to repair permissions after an upgrade or hardware addition. I have always done it using the disk utility and not from a boot up on the OS install dvd. Is there a diffe
-
I need help hooking my Samsung 27" Class 1080p LED HDTV T27B350ND to my macbook pro
I tried hooking my mac bool pro to this samsung monitor and all I get is the picture of the universe that came with the laptop and my mouse is on the monitor, but that is it.... help?