Vicious cycle of Error messages
I received a popup box "LR encountered an error when reading a catalog file and needs to quit. LR will attempt to diagnose the problem the next time it launches". I hit OK and It automatically shuts down and restarts and this message appears,"The last time LR ran it shut down prematurely due to a problem reading the catalog. LR must now check the catalog before proceeding". I hit ok and it tells me it's checking the integrity of LR 5 catalog, this may take several minutes, and sure enough it does! LR reloads and all seems fine and dandy until I attempt to click on a photo, doesn't matter which one, at which point I receive the first message again and the cycle restarts. What on earth am I supposed to do?
I backed up my catalog onto my external hard drive on Sept 28th, but have since uploaded pictures to my catalog that have not been backed up. I'm so new to this and not sure if I should access the back up, and if I will lose my pictures that have been uploaded since the backup if I do. Any thoughts on how I should proceed?
Thanks!
Is that the exact message or does it perhaps say “LR encountered an error when reading from its preview cache and needs to quit”
In which case try deleting the file in the catalog folder which ends Previews.lrdata
Do not touch the catalog itself which ends.lrcat
Otherwise go to:
File >> Optimize Catalog and then click the Optimize button
If you need to use the backup your recently imported images will still be in the folder on your hard drive and can be re-imported if you have not done much in the way of editing.
Choose File >> Open Catalog.
Navigate to the location of your backed up catalog file.
Select the backed up .lrcat file and click Open.
(Optional) Copy the backed up catalog to the location of the original catalog to replace it.
Similar Messages
-
Error Message 8003?? Download won't work!! Help PLEASE!
Hi--
I have a new iPod nano (2d gen) and tried to download music onto it from the iTunes store. Each time, I am foiled at the downloading cycle with "Error Message 8003--unknown error." The download basically freezes between the store and the computer. What am I doing wrong?? Please help!!
Many thanks!!Hello tbsphoto,
Welcome to the BlackBerry Support Community Forums.
Based on the information that you have provided it looks like during the software update the device was not able to re connect to the Mac which in turn caused the 507 error on your BlackBerry Smartphone. The 507 error basically indicates that there is no OS on the device. This issue can be resolved by reloading the software on your BlackBerry Smartphone. I am attaching a link to our knowledge base with instructions on how to go about doing so on a Mac.
Link: http://www.blackberry.com/btsc/KB19767
-DrP
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)! -
All sites work fine except Gmail will not load. I prefer Firefox, but to be fair, Chrome and IE are doing the same thing when I try to use them. Occasionally Gmail will pop up, most of the time it just endlessly cycles and I don't even get an error message. I'm going to have to get rid of gmail if this goes on.
It's maddening! I've tried everything I could find on mozilla support--restarted in safe mode, clear cache, cookies, etc. This is a brand new Windows 8 laptop. It started a few weeks after I got it. There is nothing else wrong with it, it had a fresh new OS installed before I got it. Please help! Thanks so much.'''Try Firefox Safe Mode''' to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
''(If you're not using it, switch to the Default theme.)''
* You can open Firefox 4.0+ in Safe Mode by holding the '''Shift''' key when you open the Firefox desktop or Start menu shortcut.
* Or open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
''Once you get the pop-up, just select "'Start in Safe Mode"''
'''''If the issue is not present in Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one. Please follow the [[Troubleshooting extensions and themes]] article for that.
''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.''
Please report back soon. -
Illustrator CS6 Constant Error Messages
Hi guys,
I purchased CS6 about 5 months ago now. And for the last 3 months I have been getting constant Error 16 messages when trying to start up the program. It has become a vicious cycle of uninstalling, deleting all my adobe products, then deleting all of my adobe file folders under the C: drive, App data folders, and my User folders, then having to reinstall everything. I have been doing this consistently for 3 months and it's getting to the point of seriously disabling my workflow and costing my business way to much time. I even now today had a new problem arise. When I reinstall Illustrator and enter my serial number during the installation process it accepts it and installs fine. But when I open up Illustrator it prompts me that my trial has expired and to enter in a serial number. So I enter in my serial number again and then it works for a bit. If I close the program and reopen it literally 5 minutes later it Error 16 again.
I'm running a Dell Inspiron 15R Intel i-7 processor, 8GB RAM and Windows 8. Does anybody have any ideas on why Illustrator continues to crash and/or Error 16 almost every other day/week?
Thanks.
Here is the Error:16 message
Besides the Error 16 message I am also still having trouble with the Activation and serial number recognition of Illustrator. I went to open Illustrator up today and I got this message:
It says "Activation Failed". The message is saying Product Activation is required to use this product. You must have a working internet connection to activate this product. I have full strength internet connection and I have already activated Illustrator when I did a fresh install on 12/12/13. First is was the Error:16, then it was the trial problem, and now This. What is going on?
My serial number is clearly validated and activated but the very next day I try to open Illustrator I get the message in the screenshot above. How can I fix this? Thanks.Jeff A Wright,
Thank you for your support on this. However, I am running into some problems for completing the steps listed on the help page you listed. In the SLStore the deselection of "Read-Only" is not being applied. I deselect that attribute and click Apply and then Ok. If I right click again on the folder the "Read-Only" attribute is still checked.
Also for step 3 Set Permissions I cannot change any of the permissions for the SLStore even though I am logged in as the Administrator. The PCD folder does not have an Owner tab and I cannot change the permissions for this folder either.
What can I do to fix the file permissions if I am having the problems above?
Thank you. -
Error message connecting a Vista Computer to WRT54G v6
I just bought a new computer and I am trying to connect it to the router by using EasyLink Connect.
I keep getting an error message that the computer doesn't have a wired connection to router. But it is connected correctly.
I disabled the firewall, but it didn't help.I hope Embarq is a DSL connection ::
Configuration for DSL connection:-
Before doing the following steps, you have to connect the modem to the
router's Internet Port and the computer to the Ethernet Port Number 1.
1. Press and hold the reset button for 30 seconds.
2. Then, unplug the power keep holding down the reset button for
another 30 Seconds.
3. Plug back the power back in, and keep holding down the reset button
for 30 Seconds.
4. Release the reset button.
===================================================================
Access the setup page of the router by launching an
Browser and type on the address bar, 192.168.1.1 and press enter. When
it prompts for the username and password, leave the username field
empty and provide password as "admin" (Without quotes)
click on ok.
On the main setup page the ""Internet Connection Type"" should be
on ""Obtain IP Automatically - DHCP ?. Click on the Save Settings
button.
Now click on the sub tab ""MAC address clone"".
- Click on enable
Click Clone & click save settings
Check WAN Ip on Status page of router ....
If getting Valid Ip .... try going online
If not ... power cycle for 4-5 minutes & then agian check the WAN Ip address .....
With these settings you will be able to go ONLINE!!! using the router wired as well as wireless. -
Error message "iTunes has detected an iPod that appears to be corrupted"
Everything used to work just fine until recently. On my Windows XP Home SP3 laptop, with iTunes (version 9.0.2.25) already open, I connect my 5th Generation iPod Nano and get the following message in iTunes:
"iTunes has detected an iPod that appears to be corrupted. You may need to restore this iPod before it can be used with iTunes. You may also try disconnecting and reconnecting the iPod."
If I plug the iPod into the computer without first starting iTunes, the Windows ‘Auto Play’ message comes up immediately then disappears and then the following message appears:
"Your iPod needs to be formatted for use with Windows. Would you like to run iTunes to restore your iPod Now?"
Otherwise, the iPod functions normally when not connected in iTunes. I can play the music, videos, and record videos with no problems.
The troubleshooting steps I took were:
I performed a reset of the Nano by first sliding the hold switch on/off a few cycles, leaving switch off (no orange showing), then pressed and held the Menu + Select button until the Apple logo appeared. Then I tried it in iTunes again; no such luck, same error. I then did a reset again, this time with the iPod connected to an AC power source; still no luck. I tried the reset numerous times and it didn’t help.
Next, I ran the diagnostics by pressing and holding the Menu + Select buttons immediately followed by the Select + Reverse buttons. I stepped through all the diagnostics tests and all tests passed as far as I could tell (there was no errors reported).
After this, I tried it in iTunes again and still no luck.
I even tried the iPod on my Windows Vista Home Premium (32 bit) machine and it behaved the same way. The version of iTunes on that machine was at an earlier version when I first tried it there. I then upgraded iTunes to the latest version but that didn’t help either.
I can sync my iPod Touch and 2nd gen Nano without any problems.
Sorry about be long winded about this but I am wondering if anyone else may have other suggestions. I want to try and avoid a restore if possible because I have some videos I recorded that I would like to get off the iPod. I’m not concerned about my music files as I have them always backed up but didn’t get the videos off yet.I am having this same problem with my brand new Mac Pro. It seems to be tied to the computer awaking from sleep (no I am not leaving the iPod connected while sleep... I am referring to waking the computer from sleep and then connecting iPod as opposed to restarting the computer and then connecting the iPod). In other words, if you are getting this error message, try ejecting the iPod, restart your computer, then connect the iPod and see if the error message goes away. For me it does, but I only get one shot at it, if I eject the iPod and then reconnect it, the error message returns. This happens on both iPods I have. I have rebooted (hold menu-select) and gone to disc mode (hold select-play) and the error message remains. The only way it goes away is to reboot the computer, then I get one shot at hooking up an iPod.
I NEVER had nor get this error message when I connect to the Windows PC that I started with. Perhaps the iPod does not like moving from PC to Mac? -
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 -
Adobe Flash Player 10 Error Message
About four days ago, I started getting this error message in a dialog box. It appears even with nothing open that would even require a need for Flash. I removed Adobe Flash Player 10 and rebooted, then added it back. The problem continues however.
Win-XP/SP3 fully patched and Malware free.
"A script in this movie is causing Adobe Flash Player 10 to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script? Yes / No.
Checking either option only gets rid of the pop-up for a few minutes.
Regards:
BruceIBI have just recently resolved my Flash Player issue.
My suggestion to all who have troubles with Slowing down players or error messages (like I was getting) is very similar to what has been suggested by Meln long ago.For windows machines- I don't know mac fix. but this might work.
1. remove/uninstall flash player from your system. ALL BROWSERS
2. reboot your system
3. goto the adobe site for flash player and have it check that you in fact DO NOT have flash player installed.
4. download the latest version of flash player and let it IMMEDIATELY do the install.
5. reboot
6. check how flash player works. If it is buggy and slow or kicking up errrors/messages go back to step 1. repeat this cycle as many times as necessary.
some notes:
Be careful when doing the install -DO NOT DOWNLOAD THE FLASH DEBUGGING VERSION- it will kick up errors galore.
Make certain you do noting else during the install and remove processes. You are problem solving -not being productive, so just wait it out patiently.
I know some will say, why would i remove, download and install multiple times - once should either work or not work.
OH how I wish this were true for funky software issues. There is some glitchy thing going on and where exactly it happens is anyones guess, or it would have been fixed. Without rhyme or reason one time though it will just work. when it does do a system restore point and put GOOD FLASH PLAYER as the note. after you do this fix you will know why you want a quick way back to this point.- you don't want to do it again.
i know this sounds stupid but after trying for months to "fix" my issue this is what worked on multiple PCs i had that had the issue(s) slowing down and messages. -
Error message while creating production order with KMAT material strategy25
Hi PP Gurus I am running variant configuration cycle...Strategy 25, Custermer Req KEK (KMAT Matrl)
Sales order & MRP Picked the components correctly as per the dependencies
written. So Planned order generated against sale order.
When I tried to convert planned order to Production order...I am getting the
below error message..
Error Message:
You cannot make an assignment to make-to-order stock Message no. CO684
Diagnosis The component cannot be allocated to an individual stock because
make-to-order production and engineer-to-order production cannot be executed
with this order.
A possible cause is that you are trying to create an order with reference to a
sales-order/project, where an account assignment to a sales order/project is not
allowed in the settlement profile that is assigned to the chosen order type.
This is inconsistant.
System response The following responses are possible:
Order processing is cancelled.
The system resets the special stock indicator back to the original value.
Procedure Choose another order type.
I used order type with SD1 as settelement profile.
OVZG: default 046, settlement profile = SD1
OPJH: Settlement profile = SD1
Plz through some light on this if u have worked on Variant Configuration/MTO
settlements.
Question:
1) Is creation of production order with KMAT material supported by SAP?
2) If yes, why the above error occurs?
Waiting for Ur reply
With Best RegardsDear R.Brahmankar,
I have check on the note, but it is not relevant to ecc6. The current system default setting is :
Standrad setting for reqt class 046
Special Stock E
Acct Assgt Cat. M
Valuation M
Settlmt Profile SD1
However if I change the Acct Assgt Cat. from M to E. It resolve the problem. I would like to know is this the right solution?
Config in Acct Assgt M
Consumption Posting = E
Config in Acct Assgt E
Consumption Posting = ' '
In F1 key of Consumption Posting field it shown following:
To flag the sales order item as cost- and revenue-carrying, enter an "E" (settlement via sales order).
If you do not wish to flag the sales order item as cost- and revenue-carrying, do not enter anything.
Dependencies
If you are working with nonvaluated sales order stock, always flag the sales order item as cost- and revenue-carrying.
If you are working with valuated sales order stock:
In the case of complex make-to-order production, flag the sales order item as cost- and revenue-carrying
In the case of sales-order-related mass production, do not flag the sales order item as cost- and revenue-carrying
Should we change to E?
Regards,
Ong -
Error Message "Error while Opening the Document"
Hi Friends,
I have a problem while opening the SFP transaction and Clicking on the Layout Tab the SAP System is giving an error message saying "Error while Opening the Document".
I have tried testing on several systems like IDES, ERP, Retail systems. But it is giving me same error. Is this the problem with ADOBE LIVECYCLE DESIGNER?
And when I click on the Performance Assistant it has given me some information:
Error while opening document
Message no. SOFFICEINTEGRATION143
Diagnosis
An error occurred in the desktop application while opening a document.
Friends can you help me in solving this problem.
Thanking yoy in Advance
Pradeep GoliPradeep,
Maybe Live Cycle Designer has not been uninstalled correctly from your system. So goto the following lcaotions and remove the Designer folder if you find them:-
C:\Program Files\Adobe
C:\Documents and Settings\<your-username>\Application Data\Adobe\
Alternatively try installing Live Cycle Designer on some other machine in your network and see if you encounter the same error.
Similar thread for reference : Error - Adobe Live Cycle designer
Chintan -
Error message "An Error occurred while performing this operation" while opening a document.
Hi Adobe..
We are using Live cycle ES and ES2 for applying security on the document..
With latest Mozilla and Chrome versions and with Adobe reader XI, if we try opening a document, we happens to see the below error message..
Please advise us in getting this issue resolved...
Thanks.To use XFA-based PDF forms on Firefox and Chrome, perform the following steps to configure Firefox and Chrome to open PDFs using Adobe Reader or Adobe Acrobat.
Firefox configuration:
1) Tools -> Options
2) Click Applications
3) In the Applications tab, type PDF in the search field.
4) For Portable Document Format (PDF) content type in the search result, select Use Adobe Acrobat (in Firefox) from the
Action drop-down list
Click OK and restart firefox.
Chrome configuration:
1) In Chrome, go to chrome://plugins/.
2) Click Disable under Chrome PDF Viewer, and click Enable under Adobe PDF Plug-In.
probably this would resolve the issue.
Thanks
Shivam -
HP 2025/XP: Error Message when printing envelopes wider than long
Is there any way to print envelopes wider than long (e.g., A2 through A7) without getting the error message "Unrecognized Paper" and encountering long cleaning cycles between each envelope. I prefer not to feed envelopes end-ways as they tend to gather due to the paper layers. I have had some success in using cut-to-size card stock under the flap (secured with a post-it) to make the printer "think" that the envelope is longer than wide, but this is time-consuming as well. Thanks for any help.
This seems to be a commercial product. For the best chance at finding a solution I would suggest posting in the forum for HP Business Support!
You can find the Commercial Laserjet board here:
http://h30499.www3.hp.com/t5/Printers-LaserJet/bd-p/bsc-413
Best of Luck!
You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too. -
Why is there an error message when I try to update to ios 5.1 on my iPod touch?
When I click "Install Now" it says "Verifying" then an error message pops up saying that there was an error updating and it dosent give me much more information.
This indicates an issue with the network.
Power cycle the ATV, router, and computer. -
Error messages in Console Log of Apple System Profiler
Today, I manually executed some CRON scripts from the Terminal window as part of a regular maintenance cycle. Before doing so, I ran the Apple System Profiler (OS 10.2.8), clicked on the Logs tab, and checked the Console Log. It had three days of error messages and other info (more on this later), but my intent was just to check the last entries in the log before running the CRON scripts, so that I could detect any additional errors logged as a result of the CRON scripts.
Having checked the log, I quit the Profiler and all other applications. Then I opened the Terminal window and entered:
sudo periodic monthly
I was prompted for my adminstrator password, and it then executed the script. It took just seconds to execute. Following this, I also executed
sudo periodic weekly
sudo periodic daily
The weekly CRON took about 2 minutes to finish, and the daily only a few seconds. I ran Apple System Profiler again and checked the console log and found this additional error message (not present prior to running the scripts):
Feb 15 13:43:10 Drake-Bradleys-Computer sendmail[865]: NOQUEUE:
SYSERR(root): /etc/mail/sendmail.cf: line 93: fileclass: cannot open '/
etc/mail/local-host-names': Group writable directory
(I have inserted hard returns to break the single-line error message into three lines to avoid requiring readers to use the horizontal scroll bar.)
Can anyone tell me what this error means, and what, if anything, I should do about it?
Following all of this, I next repaired my permissions with Disk Utility (and yes, after dragging iTunes 6.0.2 to the desktop). I then ran the profiler, checked the log, and encountered these two additional error messages:
file not in an order that can be processed (local relocation entries out
of place): ./Library/Frameworks/StuffIt.framework/Versions/A/StuffIt
file not in an order that can be processed (local relocation entries out
of place): ./Library/Frameworks/StuffIt.framework/Versions/A/StuffIt
(Again, hard returns are inserted.)
The errors are identical. They presumably were generated by my running disk permissions, as other applications were shut down. It appears the error refers to the Suffit application.
Any ideas what causes these errors?
Finally, a last question. (And thanks for being patient with such a long post.) The console log contains a large number of error messages for each day. This occurs even on days when I have had no apps hang, or any other system problems (power failures, etc.) that I was aware of. Many of the errors seem to involve windows manangement. The most common one is:
Feb 14 17:11:18 Drake-Bradleys-Computer /System/Library/
CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer:
kCGErrorIllegalArgument : CGSGetWindowGeometry: Invalid window
But other examples are:
Feb 14 17:42:21 Drake-Bradleys-Computer WindowServer[194]:
Cannot merge groups (yet) for wid 1877, otherwid 1881
Feb 15 10:34:37 Drake-Bradleys-Computer WindowServer[194]:
Reserved range exhausted. (0xbbf45000 to 0xbc271000 goes out of
bounds)
Feb 15 10:35:03 Drake-Bradleys-Computer WindowServer[194]:
CGXRemoveTrackingArea : Invalid tracking area
Is it fairly common for the console log to be filled with dozens of errors like this on a given day even though the iMac seems to be functioning normally?
Thanks for any advice,
Drake Bradley
P.S. I have a Casio digital camera and an HP printer hooked up to the iMac, and very recently, an Iomega HDD. (The latter was not connected for the tests reported above.)534/2980
Hi Drake,
Yes, it is common, and I wouldn't worry about it.
These "errors" are not about anything wrong. My guess is that it's a developer jargon to indicate that something didn't happen, only because there is no possibility of it happening given your specific settings/system options.
See for example the statements "System woke from sleep" or "System going to sleep" in "error_log"...
We don't know to what extend these "errors" belong to so many unmodified files that used to do something in UNIX 15 years ago, but are now completely useless, harmless and so small they can't affect Mac OS X performance in any way?
Enjoy your Mac!
Axl -
Error message FI 759: Fund does not exist in FM area
Hill!
I have to make a distribution in CO-OM (tr KSV5) according to fund
But if I customize fund as sender, choose fund from the fund catalog and make a formal chek of cycle I see an error message FI 759: Fund does not exist in FM area. How can I make it go away?Hi Irina,
As per the note 489315, you must choose a layout that contains the exact data for the active objects.
When planning for non-FM company codes you will have to change the profile/layout that only contain the elements that are active in the company code.
If you encounter error: KAFF002 while doing the above then please can you see if point 3 of note 555134 will help to by-pass the message.
Once you add the field Fund and set it to optional you should be able to use planning.
Note 555134:
3. The fields of the Funds Management are defined as 'Required entry
fields' in the standard layouts, in other words depending on the
permissibility of the initial value for a field an entry is always
demanded. To prevent this there are two options:
a) Copy the desired standard layout into an own (transaction KP65,
KPG5, OPO1) and via "Extras -> Variables -> Variables definition'
set the corresponding field to 'Optional". Then, add this layout
to your planner profile with transaction KP34.
b) Implement the attached program ZK555134 (correction instruction
461025). After the entry of planning area and layout all fields
of the Funds Management are set depending on your selection of
'Optional' or 'Not optional' (standard system). Like this you can
also change standard layouts. The check for the fields for which
'initial' is not a valid value is still carried out.
If you want to use FUND Accounting, I suggest you to read note 518610 for your reference. This note contains information about FUND Accounting and its effect.
If you only want to use 'Fund' in Funds Management, you do not have to activate the 'Fund' account assignment element.
If you activated the FUND account assignment element, which is at CLIENT level activation, the fund would always have to be filled as a required entry field in CO, FI-AA and HR for all company codes in the client concern.
Please also refer to notes 625262 and 659086.
or re-import the standard planning layout from the client 000. In the note 320197 is descriped how to do this.
I believe this will resolve your issue.
Best Regards,
Vanessa.
Maybe you are looking for
-
Java Video Issues in Snow Leopard
Hello, After a little help and adive.... Been trying to fathem out my trouble with Java videos and games, I have looked through previous posts and tried what has been sugested and still not working, only thing I havnt tried is reinstalling Java, as I
-
Printing picture in low resolution
I want to print Logo in Label Printer. But it is printing in low resolution. The dimensions of the Picture are 1,5 cm x 1,5 cm. When I insert the picture (dimensions 317 pixels x 292 pixels) in CR , I change Xscaling and Yscaling. When I printing CR
-
Hi, My client go live at 01.10.2008.Still they are not using AA. Now they want to upload assets on 01.10.2008. So I tried by followingu2026 Asset takeover date: 30.09.2008 Capitalization date in AS91:30.03.2008(I tried it by 30.03.2008) But when I go
-
Image source and FileReference.data dimmentions
Hello! How can I get the dimmentions (Width and Height) for 1. The source file of an Image component 2. The File selected in a FileReference variable Thanks!
-
Mail for Exchange sub folders, any plans?
Does any one know if there are any plans to bring out sub folder support in mail for exchange. I think this is almost a complete show stopper as current versions of exchange are designed to work with sub folders and the rules written for those sub fo