Redundant Error Messages
Officejet J4580
When I open the Solution Center, two error boxes come up repeatedly. I cancel them over and over again and eventually the regular Solution Center screen comes up and works normally. I use the Solution Center for Scanning only.
The messages are:
1. The feature you are trying to use is on a network resource that is unavailable...
2. An installation package for the product Solution Center cannot be found....
How can I get rid of these annoying messages ?
Thank you.
Hello Jackwi,
I see that this is your first visit with us here on the HP Forums. Please let me take a moment to say "Welcome".
I hope you enjoy your experience!
To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I see that you are having some issues with pop up error messages when attempting to open the HP Solution Center.
So I can better assist you, please let me know what Windows operating system you are using on your computer.
When you loaded the software and drivers for the printer, did you install with the use of the C.D or a download?
One step that you can try is to run the HP Print and Scan Doctor to see if it comes up with any errors or failures. Please let me know if it does generate any error codes and what they are.
Please write me back when you have time and I will be more than happy to help.
Thank you.
Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
W a t e r b o y 71
I work on behalf of HP
Similar Messages
-
StorE steel 640GB - data error (cyclic redundancy check) message
Hi
I have had the StorE drive for a few months, so lots of data on it.
Today windows detects it as a local drive and when I attempt to access it I get a message telling me the disk needs to be formatted, when I select no, I get a message saying *data error (cyclic redundancy check*) message.
Help.
I have tried two other laptops, both give same response.
Thanks
GuyHi, thx for the reply.
I ran chkdsk see below.
C:\Users\DADDIO>chkdsk/f
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
help!
Guy -
Error message when installing CS5
When trying to re-install CS5 after harddisk crash I get error message with this text from log:
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 1 fatal error(s), 3 error(s), 1 warning(s)
WARNING: Payload cannot be installed due to dependent operation failure
ERROR: The following payload errors were found during install:
ERROR: - Adobe Photoshop CS5 Swedish Language Pack_AdobePhotoshop12-sv_SE: Install failed
ERROR: - Adobe Photoshop CS5 Core: Failed due to Language Pack installation failure
FATAL ERROR: Cannot create extract assets at 'C:\Program Files (x86)\Common Files\Adobe\Installers\adobeTemp\{7DFEBBA4-81E1-425B-BBAA-06E9E5BBD97E}' from zip file 'E:\Adobe CS5\payloads\AdobePhotoshop12-Core\Assets1_1.zip'. Error 23 Datafel (CRC-fel, Cyclic Redundancy Check)
Now what??Hi P.Daguerre,
Use the Adobe Cleaner Tool to remove whatever Adobe softwares are there on the system.: http://www.adobe.com/support/contact/cscleanertool.html
Please refer the Kb Doc : http://helpx.adobe.com/creative-suite/kb/error-exit-6-exit-7.html.
Please see Troubleshoot with install logs | CS5, CS5.5, CS6 - http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5 -cs5.html for information on how to review your installation logs
Basic troubleshooting steps :
> Enable the hidden Admin Account on Windows 7 ( Ref : http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-adminis trator-account-on-windows-vista/ )
> Disable all Non-Microsoft Startup Services. (Ref : http://helpx.adobe.com/x-productkb/global/disable-startup-items-servic es-windows.html )
> Disable all the Antivirus softwares like CA, Norton,Mc Afee etc. temporarily from the computer.
Reboot and Install in the enabled Administrator account and check. -
How can i get the error message from the thrown/raised exception?
DB version:10gR2
Examples for this thread taken from
Want Stored Procs to get exectuted regardless of preceeding SPs Success or
I have a package with several functions and procedures inside.I created a caller procedure called callProcs, which will execute various procedures within the package in the appropriate order.
In the below example i cannot get the error message thrown from line 20
create or replace package body mypackage
is
variable_proc1 number;
variable_proc2 number;
variable_proc3 number;
v_result number;
my_exception exception;
procedure proc1
is
begin
select 8/0 into variable_proc1 from dual;
exception
when others
then raise my_exception; ----line 20
end;
procedure proc2
is
begin
select 1 into variable_proc2 from dual;
exception
when others
then
null;
end;
procedure proc3
is
begin
select 3 into variable_proc3 from dual;
exception
when others
then
null;
end;
Procedure caller_proc
is
begin
proc1;
proc2;
proc3;
v_result:=variable_proc2+variable_proc3;
dbms_output.put_line('The output is '||v_result);
exception
when my_exception
then
dbms_output.put_line('Heyyyyy the error is '||SQLERRM); -- exception caught at line 64 of caller proc
end;
end mypackage;
When i try executing the caller proc, i don't get the error. Instead i get the text User-Defined Exception as shown below
set serveroutput on
exec mypackage.caller_proc;
Heyyyyy the error is User-Defined Exception
PL/SQL procedure successfully completed.Edited by: user10633418 on Mar 10, 2009 11:30 PMThank you justin.
Sorry my earlier post was a bit ambiguous.
I wanted the error generated at proc1 to be captured at caller proc's Exception handling section (line 64) so that i could log the error to an ERR_LOG table.
I can actually log this error at proc1 itself like
exception
when others
THEN
error_message :='My custom message for the particular proc '||SQLERRM;
dbms_output.put_line(error_message);
logerror(error_message); --an autonomous error logging proc
raise;But there is a RAISE statement in proc1's exception handling, so the exception gets propogated to caller proc's exception handling section {color:#ff0000}*and another redundant row will be created at ERR_LOG table for the same error because there is a*{color}
logerror(error_message);--an autonomous error logging proc
in the WHEN OTHERS section of exception handling section of the caller proc
I want to avoid the creation of this redundant row in ERR_LOG table. -
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 -
RAID degraded - RedundancyScrub error message
Hi all,
Even though my problem is not on an X-Serve box but on a MacPro (2008), I run OSX Server 10.5.4 and have not found anything in the MacPro or Server OS forums, hence my post here in the hope of an experienced admin being able to help here.
After having a new RAID 5 setup on 4x500GB Seagate SATA drives and Apple's RAID card running fine for over 2 months, I ran the 10.5.4 update (after much deliberation on the pro's and con's) and promptly had this issue. Only found out a few days after running the update though, and after going through all logs, I could pin the problem to exactly the time of immediately after the OS update. I have searched high and low to find anything in the RAID and OS Server forums, but haven't found anything there to resolve this error message with or without cli:
The "RedundancyScrub" command could not be executed. (The request failed because a volume service is currently running)
Yes, have tried to verify RAID, only to get an error popup when trying to verify...
Could not verify the RAID set "RS1". there was a problem communicating with the device.
Since it is basically still running ok, but degraded, I need to do something, even if it means a wipe and re-install of the entire Server OS and RAID setup. I have had a few issues with Leopard anyway, and was thinking of doing a final clean install when .5 update is out that may tidy up a few more issues. But, any help in the meantime from an experienced RAID or X-Serve admin would be much appreciated.
Thanks
ChrisI had to go on to Apple's list to find this, sorry about the length...it fixed my problem
A client of mine accidentally removed a drive from his RAID-5
array on an Intel XServe. He reinserted the drive and all three 1
TB drives show up as good, but the set is showing as degraded.
The log shows Degraded RAID Set R0-1 No Spare Available for
Rebuild.
When I attempt to run a verify, it says "Could not verify the
RAIDset R0-1, There was a problem communicating with the device."
After that the log shows "The redundancy Scrub command could not
be executed. The request failed because a volume service is
currently running."
Googling this brings up a similar problem that two other people
are having, but no one has a solution. Have any of you run into
this?
Hi, Mike,
If you just replaced Apple Drive modules, the new one still will
not be as spare drive for your raid set. You have to tell RAID
card a spare drive came.
You can do for this both CLI and GUI.
CLI:
- - use 'raidutil' command.
$ sudo raidutil modify drive --addglobalspare -d <DriveBayNumber>.
For more information, see raidutil(8).
GUI:
- - Launch /Applications/Utilities/RAID Utility.app
Select 'Make Spare...' from menu 'RAID' after you selected the
new drive.
Cheers,
- -takanori
I think you misunderstand what happened, perhaps I should have been
more specific. T
he person took a drive out of a working RAID-5 while it was
running. Then he replaced it. He pulled the drive from the wrong
XServe in a rack, intending to pull a bad drive from a different
server.
Now we are unable to clear the "Degraded" message that it has. My
assumption would be that it should have simply gone into a degraded
state and then rebuilt itself automatically.
Perhaps the drive should be pulled again and formatted, and then
inserted and added as a spare?
Hi, Mike,
Ok. I got your condition.
I had same situation couple weeks ago. I've also thought when drive
module of raid set set back, Apple RAID Card would start rebuilding
immediately . But it would not. So you have to mark spare to the
drive module which was pulled out accidentally and set back same bay
of xserve. You don't have to format it again. You can mark it spare
drive right way.
In my case, Apple RAID Card said it was a part of another raid set
when I set the drive module back after my staff pulled it out
carelessly. So Apple RAID Card never start rebuilding using with a
part of raid set. I think it is good as fool-safe mechanism.
The way of marking spare is as same as what I wrote above. If you
decide to use CLI, you may have to use another subcommand of
raidutil before making it spare. I repaired my raid set of xserve
with RAID Utility.app just select 'Make Spare...' from menu 'RAID'.
Careful and cheers,
- -takanori
Thank you Takanori, that was the thing to do. The RAID is rebuilding
now. -
Upgrade/install/uninstall problems, error messages etc.
After upgrading to version 7 everything seemed to be fine for a while then out of the blue I got this message:
Error writing to file C:\Program Files\iTunes\iTunes.Resources\ko.lproj\iPodHelpchm. Verify that you have access to that directory
I am an admin on this computer, hadn't made any changes lately.
After some searching online, I tried uninstalling... iTunes uninstalled but Quicktime is still causing problems. I get similar error messages (2330) when trying to uninstall quicktime.
Now I can't get either to reinstall or uninstall!
I'm really frustrated, version 6 worked great for me.
I get this error message when trying to delete the iTunes and quicktime folders from Program Files: "Data Error (cyclic redundancy check)"
The programs appear uninstalled except these folders cannot be deleted. I have opened the folders and deleted everything inside that I could delete without receiving the same error message... but I'm still left with files on my computer and still cannot reinstall the latest iTunes/quicktime properly.
This seems to be the step that is preventing any of the previously suggested fixes for my iTunes problems on this forum from working.
I've been watching and waiting on a fix for this for months. I finally switched to an iTunes alternative for windows users, but I do miss my iTunes. I used to shop the iTunes store frequently but after this I don't know... I'm ready to give up!
Does anyone have any new insight on this???
Dell Inspiron 5100 Windows XP
Dell Inspiron 5100 Windows XP
Dell Inspiron 5100 Windows XPthank you kindly for the detailed information.
Error writing to file C:\Program Files\iTunes\iTunes.Resources\ko.lproj\iPodHelpchm. Verify that you have access to that directory
2330s citing language resource folders (you seem to be having trouble with one of the Korean ones) are typically caused by damaged files, or disk damage in the area of those files. i'd lean towards the disk damage possibility given the "Cyclic redundancy check" message.
so first let's try running a chkdsk over your C drive. see:
How to perform disk error checking in Windows XP
does the chkdsk find/repair any damage? if so, do you still get the 2330 next time you try an install? -
Nested Editable Regions Error Message
I'm trying to create a dynamic template. I've saved a header
and footer as library items, and I want to include them in the
template. In addition I want to have an editable region between
them. For some reason, when I go to save as template, the error
message comes up. It says 'error at line 57, column 323(absolute
position 2998) of ... :nested editable regions' . I have narrowed
this error to be caused by the header (which was created as a
sliced image in photoshop), but for what reason I don't know. Any
ideas why I am getting this error message and what I can do to fix
it? The template won't save otherwise and I can't find any
information on dreamweaver 8 help menu.There is a parent file and an included file. Here's an
example -
The parent file is this -
<html>
<head>
</head>
<body>
<!--#include file="foo.html" -->
</body>
</html>
and foo.html (the included file) is this -
<p>Hello World</p>
The file you have linked me to is a badly broken template
page. It's broken
because the Library items have not been made properly since
they contain
redundant <body> tags, CSS, and javascript as well.
This will never work the way you want, particularly not in
DW....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Genius2112" <[email protected]> wrote in
message
news:eo41an$93v$[email protected]..
>
http://www.lyncourtrec.com/Lyncourt%20Rec%20Website/Pages/Template.dwt.asp
>
>
> Sorry, I'm not quite sure what you meant by "being
included". The images
> aren't with the header b/c I didn't adjust their source
folder since I had
> to
> upload it on a different site (I don't have a hosting
plan for this site
> yet).
> Hope this is what you were looking for. Thank you for
your help.
>
> -
New error messages related to OHW - filling up error logs.
We've recently received a new delivery of help files (new helpset), but there have also been many other changes to our base software system in the interim. This makes it hard to nail down the culprit.
That said, we are now seeing two messages in the error log any time we access help. I'm wondering if anyone else has seen these, and have suggestions as to the root cause. They are as follows:
...<OHWLoggerUtils> <errorFoundLinkToInvalidTopicID> invalid topic id link: STADG reported from http://127.0.0.1:7101/sta-help/faces/helppages/config.OHW+Servlet+1/locale.en/
<OHWLoggerUtils> <errorFoundLinkToInvalidTopicID> invalid topic id link: STAIN reported from http://127.0.0.1:7101/sta-help/faces/helppages/config.OHW+Servlet+1/locale.en/
<OHWLoggerUtils> <errorFoundLinkToInvalidTopicID> invalid topic id link: STAAG reported from http://127.0.0.1:7101/sta-help/faces/helppages/config.OHW+Servlet+1/locale.en/
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS.
<DocumentUtils> <getDocument> ADFv: Trouble getting the mutable document from MDS....
We are seeing many of these messages in a row, but they are all like the two types you see above.
Just for completeness, there is one other error message filling our log which we also have not been able to resolve. This one has been around for a while longer:
<OHWFilter> <doFilter> Resource URLs should not contain "helppages.resource"; they should go through the servlet path "/ohr".
<OHWFilter> <doFilter> Resource URLs should not contain "helppages.resource"; they should go through the servlet path "/ohr".
... <more of the same>
Any help or pointers would be appreciated. We are using JDev 11.1.2.3.0, and OHW 5.0
Mitch
< name, title, organization, telephone information deleted by moderator -- you need to post this to MOSC and not this public forum >Hey, tried uploading my first DPS app since August 28 and got rejected. I edited my folio and re- created the app, did the hole process again and today I uploaded the new app thru App loader. Everything was ok, but as soon as I clicked the review app in itunes connect, and the status changed to: "Waiting for review" Got an itunes Email saying this: ..."REDUNDANT BINARY UPLOAD - there already exists a binary upload with build version '32.0.0.8.99116' for train '1.0.7'... Once these issues have been corrected, you can then redeliver the corrected binary."...
I am completely lost, I don't know how to solve this issue, don't know what steps to follow and im in desperate need of help. The app is a magazine and they've been waiting its launch since September 1st.
The hole precess relies on me and I ran out of options... Can someone Help me? -
App world keeps giving me the error message
I have a blackberry Q10 and everytime I try and download something from the app world it keeps giving me the error message of ' an error has occured. Please try again later' this started happening when I upgraded my app world.
Hi and Welcome to the Community!
With a strong carrier network signal (e.g., not merely WiFi), I suggest the following steps, in order, even if they seem redundant to what you have already tried (step 1 should result in a message coming to your BB...please wait for that before proceeding to the next step):
1) Register HRT
KB00510 How to register a BlackBerry smartphone with the wireless network
Please wait for one "registration" message to arrive
2) Reboot
Pre-BB10 Devices ONLY. With power ON, remove the back cover and pull out the battery. Wait about a minute then replace the battery and cover. Power up and wait patiently through the long reboot -- ~5 minutes.
BB10 Devices. Hold the top button down until the counter reaches zero. Wait for the device to be fully shut down (e.g., nothing at all displayed on the screen, no LED lights, etc.). Hold the top button until the red LED is lit. Wait through the full boot-up process. IF this fails, you can attempt the battery-pull method above, but it is normally NOT recommended unless nothing else works.
See if things have returned to good operation. Like all computing devices, BB's suffer from memory leaks and such...with a hard reboot being the best cure.
Hopefully that will get things going again for you! If not, then you should contact your mobile service provider for formal support. Also check your BB10 OS level to be sure it also is up to date.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
How can I disable RPS error messages in the AS5300 ?
How can I disable de error message:
" %RPS-3-MULTFAIL: There is more than one failure with the Redundant Power System; please resolve problems immediately "
in the AS5300 with RPS Chassis and normal single power supply ?If you only have a single power supply,
I would try swapping it (or swapping
slots) to verify if it is the problem. -
Cyclic Redundancy Error while copying QT movies to Windows computer
I have created a series of short instructional videos in QuickTime Pro for Mac that are used by a number of both Mac and Windows users. Occasionally a Windows user attempting to copy one of these videos from the supplied DVD media will get an error message that says "Cannot copy (file name) Date Error Cyclic Redundancy Check." The copy aborts and sometimes locks up the computer.
Is this a drive issue, a media problem or a Quicktime thing? Don't know what it is, but it sure is tough to isolate.
Any help would be appreciated!I think it very unlikely that copying a file from a DVD to the computer would have anything to do with QuickTime, since QT isn't involved in file copies, only with playback. So it's probably either an issue with the duplication of the media or perhaps with some drives and the brand of media being used.
Are you burning disks youself, or have they been commercially pressed? If you're having the disks commercially duplicated, then you probably want to take this up with your pressing house.
If you're burning the disks yourself, you might try a different brand of media. Also, if you're using the Mac OS X Finder burn to create your disks, you might try a dedicated DVD burning utility such as Roxio's Toast; that's often more successful in burning a hybrid Mac/Windows disk.
Hope this helps. -
Error message on Catalyst 6513 Urgent!!!
Hi the Catalyst 6513 is giving me this message:
Nov 1 21:34:09: %PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slaveflash:s720
33-pk9sv-mz.122-17d.SXB1.bin is not present in standby
but it seems to me that everything is Ok bootflash is copy on both supervisors
#sh boot
BOOT variable = flash:s72033-pk9sv-mz.122-17d.SXB1.bin,12
CONFIG_FILE variable does not exist
BOOTLDR variable = bootflash:s72033-pk9sv-mz.122-17d.SXB1.bin
Configuration register is 0x2102
Standby is up
Standby has 458752K/65536K bytes of memory.
Standby BOOT variable = flash:s72033-pk9sv-mz.122-17d.SXB1.bin,12
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable = bootflash:s72033-pk9sv-mz.122-17d.SXB1.bin
Standby Configuration register is 0x2102
Can somebody explain to me why it is happening?
Regards
Thanks
LpHello,
here is what the error message decoder says:
1. %PFREDUN-4-BOOTSTRING_INVALID: The bootfile [chars] is not present in standby
This message indicates that the bootfile that is configured is not present on the redundant supervisor engine. If the redundant supervisor engine resets, it will not come up because it will not find the image specified in the bootstring.
Looks like you need to configure the bootfile on the redundant supervisor...
HTH,
GP -
Cannot download blackberry app world apps - "enable cookies" error message keeps coming
Hi,
I have a Curve 3920, running v7.1.0 OS.
Back in July I kept getting low memory messages and it kept getting stuck so I had to un-install apps such as Linkedin or What's App. Then I realized I only had 2GB memory so upgraded to a 16GB one.
Now the blackberry works ok but it is impossible to re-install Linkedin or World Apps app or any other from Blackberry World interface, it keeps coming coming up with ""BlackBerry ID Services. We detect that cookies have been disabled in your browser. Please enable cookies in order to continue." error message, even though I have correct set-up in the device browser option set-up menu.
However I successfully managed to download What's App, but not from app world page.
Any idea of what can be done?
Many thanks in advance.
VladUK
Solved!
Go to Solution.Hi and Welcome to the Community!!
Please try this sequence:
1) Remove both AppWorld AND the Identity App from your BB
KB10040 How to view or remove installed applications on a BlackBerry smartphone
If it requests that you reboot the BB, do so
2) Do a Batt-Pull reboot (power on, remove battery, wait, insert battery, wait), even if redundant to the one you did in step 1.
3) Install (on your BB) a fresh copy of AppWorld (during which a fresh version of the Identity App should also install)
http://blackberry.com/appworld/download
Again, if it requests to reboot, do so.
4) Do another Batt-Pull reboot
5) See if it now works.
Cheers!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code -
Linux/Unix error messages & troubleshooting notes
I am looking for some book/notes where i can check linux/unix error messages and what's there meaning? & possible what's fix? & any troubleshooting guide would help too....
eg
SQL> connect /as sysdba;
ERROR:
ORA-09925: Unable to create audit trail file
IBM AIX RISC System/6000 Error: 89: Invalid file system control data detected
Additional information: 9925
ORA-09925: Unable to create audit trail file
IBM AIX RISC System/6000 Error: 89: Invalid file system control data detected
Additional information: 9925DBA2008 wrote:
I am looking for some metalink notes# /document for Linux Troubleshooting, i want to know more about these topics
1. Troubleshooting Techniques
Troubleshooting methods
Best practices
Tools
2. Troubleshooting Boot Issues
Working with advanced GRUB features
Rescue and GRUB CDs
Advanced ext2/ext3 filesystem repair
Rescuing RAID and LVM volumes
3. Local Configuration
Tools to identify configuration problems
4. Hardware
Preempting hardware failures (looking for the signs)
Protecting against hardware failures
Redundant configurations
Tools to help identify hardware failures and intermittent problems
5. Applications
Tools and techniques for troubleshooting applications
Common application problems and how to solve them
6. Network
Manual configuration of network cards
Troubleshooting advanced setups (bonded interfaces, virtual interfaces)
Connectivity issues
Network diagnostic tools
7. Security
Working effectively with (and not against) security tools, including SELinux, SSL, and authentication
8. Red Hat Resources and Reporting Problems
Support options
Knowledgebase
Certified training
Initiating support calls
TAM support
Developer support
Bugzillas
Support workflow
Diagnostic and information-gathering tools
Edited by: DBA2008 on May 14, 2009 4:02 PMHave you done and got the training for RHCT/RCHE or taken advantage of training, eg cdrom or classrom, as listed here:
[http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getsearchpage?page_id=13&p_search_category_id=1345]
or
[http://education.oracle.com/pls/web_prod-plq-dad/show_desc.redirect?dc=D46590GC10&p_org_id=28&lang=US]
That would seem the most sensible way of covering that vastness of ground.
Maybe you are looking for
-
HT201263 My 4th gen ipod touch is 6 mos old and will not turn on
My 4th gen ipod touch is 6 mos old. Tried to turn on today and nothing. Plugged into computer held down sleep/wake button and plugged into computer with usb. Nothing. It has not been dropped or bumped. It has been stored as I don't use it often o
-
How to: Embed YouTube in Ibook/Location of File, Open in Dashboard Widget Code?
Hi, I am new to the whole Mac experience and loving it after 25 years locked into the MSGATES paradigm. I have been playing around with Ibook and have made a book. I would like to embed a You Tube file and it seems it is not as simple as slecting an
-
Complaint regarding my Lumia 920
To the person responsible, My name is Rana Abraham. I have a Lumia 920. IMEI number of the same is 3**************. The problems with this handset is that it overheats when any application that work based on internet is used.(The problem persists in
-
Large Photo vs. Small photo when someone calls
When I receive calls from a specific contact, the photo of that person appears in the top right of the screen with the larger wallpaper being that of my specified wallpaper. However, if anyone else ever calls, the entire screen background is filled w
-
FPGA CRIO LabView - Why No Signal or Low signal?
I'm programming LabView 8.2/RealTime 8.2 on a CRIO-9002 equipt with a 9102 chassis. I have a some 4-20mA modules, +-10v modules and last but MOST IMPORTANTLY a 9233 +-5v module. I've programmed the FPGA and realtime and have been able to acquire and