Remote 'Graceful' reboot

Good morning,
I remotely connect to my Mac, and it seems my VNC connection is stale, and I have to reboot. I use an app called Remote Buddy which allows me to restart the machine remotely. I can also run any script from a directory.
Unfortunately, two apps (Safari and Terminal) are normally running and prevent the reboot. I'm new to scripting on the Mac, but can someone point me in the direction of a graceful reboot that will force quit any apps that are preventing shutdown/reboot?
Thanks in advance,
Marc

Hello,
I am a newbie to VNC, but I am currently using LogMeIn with my Mac(s) and it has the ability to correctly reboot. I use it from both a PC and a Mac to help my mom with her iMac. LogMeIn has a free and paid product, I use the free one and it works great. Like I said, I am a newbie to VNC and trying to get an actual VNC client to work. I have Apple Remote desktop, and Real VNC and cant get either of them to work with the iMac...for now. LogMeIn isn't as powerful as having an actual VNC setup, but it does work very easily and properly reboots the system.

Similar Messages

Remote system reboots due to error when exporting config.

I have a PXI-8196 controller operating on a network in a PXI-1052 chassis. I am trying to export the config and the remote system reboots due to system error.

Your Computer looks to be a Late 2010 iMac, if so is the RAM spec as shown below?
Maximum Memory
16 GB
Memory Slots
4 - 204-pin PC3-10600 (1333 MHz) DDR3 SO-DIMM

Reboot AirPort Extreme Remotely Off Network?

Is there a way I can access my Airport Extreme remotely to reboot it? I mean totally off my home network like with my iPhone or something? I know the IP of my Airport Extreme but cannot figure out a way to connect to it remotely when not on the same network. I just want to be able to reboot it.
Thanks...

Yes this is possible, if Back to My Mac is enabled in AirPort Utility, using your Apple ID:
Select your Extreme with the button "Other AirPort Base Stations" then Base Station > Restart...

Remote can't find the library

Hi everyone,
Have the same problem since I updated iTunes to version 9 (and sup.) and iPhone OS to versi

Sorry my post has been cut...
So, I have this problem since I updated iTunes to version 9 (and sup.) and iPhone OS to version 3 (and sup.).
I can enter the code on iTunes, then after telling me I can remote control my iTunes from my iPhone, I cannot connect and allways have the same message "can't find the library".
What I've already done :
completely reinstall my computer
deactivate Windows firewall and Base Filtering Engine, then restart it
deactivate my router firewall
deactivate any filter on my router, then reboot it
delete Remote from my iPhone, reboot it, then reinstall Remote, and reboot again
activate library share on iTunes
activate public folders share on Windows
remove sim card to be sure to use wifi, and only wifi
enter the 4 digits code on iTunes (worked)
still the same message on iPhone : can't find the library
I've seen many posts saying that the computer needs to been wifi connected, and not via Ethernet. Is it true ??? It perfectly worked with older versions of these programs, why would Apple have made a change like this ??
Anyone with an idea?
Thx

HT201335 It got nA new router today and wanted to turn on apple tv but my remote app on iPad and iPhone will not recognize apple tv. Btw- I do not have apple tv remote.

It got A new router today and wanted to turn on apple tv but my remote app on iPad and iPhone will not recognize apple tv. Btw- I do not have apple tv remote.

It reboots it but unplugging can also rectify communication issues like this. A restore would be the next step.

Remote problem

hi everyone!
the last 3 days i spent figuring out, how to get my iphone back on my desktop's itunes library, i hope, someone can help me
my whole story:
everything worked perfect. after updating to os3 i had these strange wifi-problems. i brought it back, and after 4 weeks i got a new one back. everything seemed perfect again, but then i then i tried to start connecting via remote, but my iphone just shows up on my laptop.
because this was the only reason to change my iphone, i seriously tried everything, to make it work again. so i checked firewall settings, router settings, re-installed itunes, and then the whole computer.
now in win7 i had the same problem, so i again checked a lot of preferences, but did not suceed.
i am using a thomson cable router, getting my ip adresses automatically and have ssid/wpa2 running.
however, i hope someone can help me getting my phone back to my standard desktop.
thanks in advance
andrew

Hi everyone !
Have the same problem since I updated iTunes to version 9 (and sup.) and iPhone OS to version 3 (and sup.).
I can enter the code on iTunes, then after telling me I can remote control my iTunes from my iPhone, I cannot connect and allways have the same message "can't find the library".
What I've already done :
- completely reinstall my computer
- deactivate Windows firewall and Base Filtering Engine, then restart it
- deactivate my router firewall
- deactivate any filter on my router, then reboot it
- delete Remote from my iPhone, reboot it, then reinstall Remote, and reboot again
- activate library share on iTunes
- activate public folders share on Windows
- remove sim card to be sure to use wifi, and only wifi
- enter the 4 digits code on iTunes (worked)
- still the same message on iPhone : can't find the library
I've seen many posts saying that the computer needs to been wifi connected, and not via Ethernet. Is it true ??? It perfectly worked with older versions of these programs, why would Apple have made a change like this ??
Anyone with an idea ???

Hyper-V Failover Cluster virtual guests suddenly reboots

The environment is Server 2012 R2 using dual clusters--a Hyper-V Failover Cluster running guest application virtual machines and a Scale-Out File Server Cluster using Tiered Storage Spaces which are used to supply SMB3 shares
for Quorum and CSV. Has anyone had this problem?

Anything relevant in the host or guest event logs? I would also check the cluster event logs to see if there are any indications there as well.
Does the guest go down hard or gracefully reboot?
Need more info.
Andy Syrewicze
Come talk more about Hyper-V and the Microsoft Server Stack at
Syrewiczeit.com and the Altaro Hyper-V Hub!
Post are my own and in no way reflect the views of my employer or any other entity in which I produce technical content for.

Remotely restart FIOS (MI424WR) Router

My router frequently slows speeds to a crawl or stops working.
Does the router have an easy way to do this, or has anyone came up with a script to: automatically login remotely to reboot the router?
The router doens't have SSH and I refuse to use telnet. I'm gonna try to use linux/curl to script the behavior of logging in and clicking the reboot router link.

I have the same problem and have to reboot my gen 3 actiontec router every few days as my upload speeds come to a crawl, oddly download speeds are fine. So here is what I ended up doing. This is from a Windows 7 64 bit PC and this automtically reboots the fios actiontec gen 3 router every night. The PC that runs this script needs to be powered on at the time this script runs.
1) Enabled Telent Access for Local Access Only (that means while only on my local network). I did this by
a) login with browser to 192.168.1.1 with admin id and password
b) Go to Advanced .. Local Administration .... Allow local telnet access ... Using Primary Telnet Port (23)
2) Download Telnet Scripting Tool a.k.a TST10.exe from http://www.theworldsend.net/download.php?get=TST10&extension=zip
3) I unziped this download and placed the file TST10.exe file from the TST10.zip in this directory
"F:\My Documents-James\Dropbox\Dropbox\reboot-router"
4) I enabled Telnet Client on the Windows 7 PC I am running this from by turing on the telnet client windows feature
. Here is how to do that
http://social.technet.microsoft.com/wiki/contents/articles/910.how-to-enable-telnet-client-in-window...
5) I created this script and called it "reboot-router.txt" and placed in the same folder as the tst10.exe program. Here are the exact contents of this file, except replace "admin" with the administrator id if you changed it on your router (I did) and place the password for this admin id (fios admin password) on the 5th line of the script
192.168.1.1
WAIT "Username:"
SEND "admin\m"
WAIT "Password:"
SEND "enteryouradminpassswordhere\m"
WAIT ">"
SEND "system reboot\m"
WAIT ">"
6) Now from a command prompt I would run this command
tst10.exe /r:reboot-router.txt
This would reboot the router. Now the challenge was to get this program to run automatically with "parameters" via windows scheduler. I could not get that to work for some reason via the add arguments. So I had to create a batch file.
7) Create a batch file called "reboot-router.bat" and I placed it in the same folder with the .txt file and .exe file
"F:\My Documents-James\Dropbox\Dropbox\reboot-router". Here are the exact contents of this .bat file.
title reboot router
F:
cd "F:\My Documents-James\Dropbox\Dropbox\reboot-router"
@echo:
sleep 2
tst10.exe /r:reboot-router.txt /o:output.txt /m
@echo:
8) Create a windows task to run every day at 4 am to run this reboot-router.bat file. Here is how I did that
a)Right Click My Computer from desktop ....
b) Click Manage (to be at Computer Management) ...
c) Click Task Scheduler under System tools
d) Under actions on right side click "Create a basic task"
e) give it a name such as reboot router..
f) click Next
g) Keep Daily radio button checked and click Next
h) select the time you want to have this run and keep other defaults of recur every day "1" and Start date
i) Select "Start a program" for "What actions do you want the task to perform"
j) For Program or Script click the browse button and point it to reboot-router.bat
in my case it was "F:\My Documents-James\Dropbox\Dropbox\reboot-router\reboot-router.bat"
k) click Next
l) give it name
9) You are now done!!!!
I tested this at step 6 to make sure I had everything working
Good luck to everyone, James Stroud

9001 XR Interface Failure

Hi Guys, i am new to XR IOS, just recently deployed some 9001 XR on our network, had a prblem recently where one devices interfaces loose traffic, all the neighbours go down as per the below log, i am trying to find the reason for this as it keeps happening on 5Hour intervals. Thanks
RP/0/RSP0/CPU0:Jun 30 03:25:08.437 : eem_ed_oir[190]: Messge received content : Event 1 NodeId: 0x828
RP/0/RSP0/CPU0:Jun 30 03:25:08.440 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.35: state Standby -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.442 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB32: Bundle-Ether1.32: state Active   -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.443 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB31: Bundle-Ether1.31: state Standby -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.444 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB15: Bundle-Ether1.15: state Standby -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.447 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB30: Bundle-Ether1.307: state Active -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.448 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB34: Bundle-Ether1.34: state Active   -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.449 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB33: Bundle-Ether1.33: state Standby -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.449 : invmgr[255]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: BRINGDOWN
RP/0/RSP0/CPU0:Jun 30 03:25:08.450 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB60: Bundle-Ether1.360: state Standby         -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.452 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB49: Bundle-Ether1.49: state Active   -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.453 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.305: state Standby         -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.455 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB12: Bundle-Ether1.312: state Active -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.455 : mpls_ldp[1043]: %ROUTING-LDP-5-GR : GR session 172.29.0.8:0 (instance 1) disconnected
RP/0/RSP0/CPU0:Jun 30 03:25:08.457 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB11: Bundle-Ether1.311: state Standby         -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.457 : mpls_ldp[1043]: %ROUTING-LDP-5-NBR_CHANGE : Neighbor 172.29.0.8:0, DOWN (Interface state down)
RP/0/RSP0/CPU0:Jun 30 03:25:08.458 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB16: Bundle-Ether1.16: state Active   -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.460 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB29: Bundle-Ether1.29: state Active   -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.461 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB27: Bundle-Ether1.27: state Standby -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:08.463 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB79: Bundle-Ether1.709: state Standby         -> Init
RP/0/RSP0/CPU0:Jun 30 03:25:38.635 : shelfmgr[395]: %PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/0/CPU0, RomMon Version: 1.30
RP/0/RSP0/CPU0:Jun 30 03:25:38.637 : shelfmgr[395]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : Remote location 0/0/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.2.3.CSCue55886-1.0.0/lc/mbiasr9k-lc.vm validated
RP/0/RSP0/CPU0:Jun 30 03:25:38.640 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-BOOTING
RP/0/RSP0/CPU0:Jun 30 03:26:56.660 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-RUNNING
RP/0/RSP0/CPU0:Jun 30 03:27:13.194 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.11 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:19.774 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.6 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:40.594 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.1 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:40.806 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.2 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:43.563 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.8 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:45.142 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.12 Down - BGP Notification sent, hold time expired (VRF: default)
LC/0/0/CPU0:10: init[65540]: %OS-INIT-7-MBI_STARTED : total time 5.229 seconds
LC/0/0/CPU0:Jun 30 03:27:00.002 : insthelper[61]: %INSTALL-INSTHELPER-7-PKG_DOWNLOAD : MBI running; starting software download
LC/0/0/CPU0:Jun 30 03:27:41.274 : sysmgr[90]: %OS-SYSMGR-5-NOTICE : Card is COLD started
LC/0/0/CPU0:Jun 30 03:27:41.757 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 51.189 seconds
LC/0/0/CPU0:Jun 30 03:27:42.383 : sysmgr[352]: %OS-SYSMGR-6-INFO : Backup system manager is ready
RP/0/RSP0/CPU0:Jun 30 03:27:51.664 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.5 Down - BGP Notification sent, hold time expired (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:27:55.337 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:UNPOWERED
RP/0/RSP0/CPU0:Jun 30 03:27:55.449 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:POWER UP
LC/0/0/CPU0:Jun 30 03:27:56.275 : lda_server[64]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing
RP/0/RSP0/CPU0:Jun 30 03:27:57.309 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:INITIALIZED
LC/0/0/CPU0:Jun 30 03:27:57.435 : kdscrape-lc[62]: KERNEL-DUMP: Copied LC1.130630-012501.e500 to /harddisk:/dumper
LC/0/0/CPU0:Jun 30 03:27:57.542 : kdscrape-lc[62]: KERNEL-DUMP: Copied LC1.130630-012501.crashinfo.by.p40x0mc to /harddisk:/dumper
RP/0/RSP0/CPU0:Jun 30 03:27:57.585 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 0 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:27:59.193 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 1 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:00.795 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 2 is inserted, state: 1
LC/0/0/CPU0:Jun 30 03:28:01.269 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_1_FAIL_0 : Set|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 1 Failure on FIA 0
LC/0/0/CPU0:Jun 30 03:28:01.271 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_0_FAIL_0 : Set|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 0 Failure on FIA 0
RP/0/RSP0/CPU0:Jun 30 03:28:01.974 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 3 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:03.577 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 4 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:05.181 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 5 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:06.785 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 6 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:08.386 : mpls_ldp[1043]: %ROUTING-LDP-5-GR : GR session 172.29.0.1:0 (instance 1) timed out
RP/0/RSP0/CPU0:Jun 30 03:28:08.389 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 7 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:08.458 : mpls_ldp[1043]: %ROUTING-LDP-5-GR : GR session 172.29.0.8:0 (instance 1) timed out
LC/0/0/CPU0:Jun 30 03:28:09.559 : prm_server_ty[303]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
LC/0/0/CPU0:Jun 30 03:28:09.563 : prm_server_ty[303]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
RP/0/RSP0/CPU0:Jun 30 03:28:09.993 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 8 is inserted, state: 1
LC/0/0/CPU0:Jun 30 03:28:10.011 : sysmgr[90]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
RP/0/RSP0/CPU0:Jun 30 03:28:11.180 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 9 is inserted, state: 1
LC/0/0/CPU0:Jun 30 03:28:13.005 : syslog_dev[88]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
LC/0/0/CPU0:Jun 30 03:28:15.980 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Invalid to Customer Facing
LC/0/0/CPU0:Jun 30 03:28:15.984 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Invalid to Not Interested
RP/0/RSP0/CPU0:Jun 30 03:28:16.600 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/0 port_num: 11 is inserted, state: 1
RP/0/RSP0/CPU0:Jun 30 03:28:33.471 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:OK
RP/0/RSP0/CPU0:Jun 30 03:28:33.488 : invmgr[255]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
RP/0/RSP0/CPU0:Jun 30 03:28:33.495 : invmgr[255]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 inserted
RP/0/RSP0/CPU0:Jun 30 03:28:33.496 : eem_ed_oir[190]: Messge received content : Event 0 NodeId: 0x828
RP/0/RSP0/CPU0:Jun 30 03:28:33.498 : eem_ed_oir[190]: Messge received content : Event 0 NodeId: 0x828
LC/0/0/CPU0:Jun 30 03:28:34.330 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_1_FAIL_0 : Clear|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 1 Failure on FIA 0
LC/0/0/CPU0:Jun 30 03:28:34.331 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_0_FAIL_0 : Clear|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 0 Failure on FIA 0
LC/0/0/CPU0:Jun 30 03:28:44.631 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.632 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.633 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.633 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.637 : cfgmgr-lc[134]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/0/2' has been restored.
LC/0/0/CPU0:Jun 30 03:28:47.602 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Customer Facing to Core Facing
LC/0/0/CPU0:Jun 30 03:28:47.603 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Not Interested to Core Facing
RP/0/RSP0/CPU0:Jun 30 03:28:51.005 : shelfmgr[395]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:IOS XR RUN
RP/0/RSP0/CPU0:Jun 30 03:28:51.010 : invmgr[255]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: IOS XR RUN
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.023 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.023 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.026 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.026 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.030 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.031 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.031 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.033 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.035 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.035 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.043 : cfgmgr-lc[134]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/0/0' has been restored.
LC/0/0/CPU0:Jun 30 03:28:57.029 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Core Facing to Standard
LC/0/0/CPU0:Jun 30 03:28:57.030 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Core Facing to Standard
LC/0/0/CPU0:Jun 30 03:28:58.163 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Up
LC/0/0/CPU0:Jun 30 03:28:58.165 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.171 : BM-DISTRIB[1148]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/6 is Active as part of Bundle-Ether1
RP/0/RSP0/CPU0:Jun 30 03:29:00.171 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.174 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.178 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.35, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.178 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.32, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.179 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.31, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.179 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.15, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.180 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.307, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.180 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.34, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.181 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.33, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.181 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.360, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.182 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.49, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.182 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.305, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.183 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.40, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.183 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.312, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.183 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.311, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.184 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.16, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.184 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.29, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.184 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.27, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.185 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether1.709, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.192 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.35, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.192 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.32, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.192 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.31, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.192 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.15, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.193 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.307, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.193 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.34, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.193 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.33, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.194 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.360, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.194 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.49, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.194 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.305, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.195 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.40, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.195 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.312, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.195 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.311, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.195 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.16, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.195 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.29, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.196 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.27, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:00.196 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether1.709, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.825 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.827 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.840 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.841 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.855 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.857 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:04.016 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:04.018 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:04.022 : BM-DISTRIB[1148]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/4 is Active as part of Bundle-Ether1
RP/0/RSP0/CPU0:Jun 30 03:29:04.349 : ospf[1011]: %ROUTING-OSPF-5-ADJCHG : Process 200, Nbr 172.29.0.1 on GigabitEthernet0/0/0/0 in area 0 from LOADING to FULL, Loading Done,vrf default vrfid 0x60000000
LC/0/0/CPU0:Jun 30 03:29:05.811 : pfm_node_lc[291]: %PLATFORM-SFP-3-HIGH_RX_POWER_WARNING : Set|envmon_lc[143443]|SFP(0x1029001)|Port_0/01
LC/0/0/CPU0:Jun 30 03:29:05.811 : pfm_node_lc[291]: %PLATFORM-SFP-3-HIGH_RX_POWER_WARNING : Set|envmon_lc[143443]|SFP(0x1029002)|Port_0/02
RP/0/RSP0/CPU0:Jun 30 03:29:05.849 : BM-DISTRIB[1148]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/1 is Active as part of Bundle-Ether2
RP/0/RSP0/CPU0:Jun 30 03:29:05.849 : BM-DISTRIB[1148]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/2 is Active as part of Bundle-Ether2
RP/0/RSP0/CPU0:Jun 30 03:29:05.850 : ifmgr[243]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether2, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:05.852 : ifmgr[243]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface Bundle-Ether2, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:05.877 : ospf[1011]: %ROUTING-OSPF-5-ADJCHG : Process 200, Nbr 172.29.0.8 on Bundle-Ether2 in area 0 from LOADING to FULL, Loading Done,vrf default vrfid 0x60000000
RP/0/RSP0/CPU0:Jun 30 03:29:05.928 : mpls_ldp[1043]: %ROUTING-LDP-5-NBR_CHANGE : Neighbor 172.29.0.8:0, UP
RP/0/RSP0/CPU0:Jun 30 03:29:06.730 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.1 Up (VRF: default)
LC/0/0/CPU0:Jun 30 03:29:06.914 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:06.915 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Up
RP/0/RSP0/CPU0:Jun 30 03:29:06.984 : mpls_ldp[1043]: %ROUTING-LDP-5-NBR_CHANGE : Neighbor 172.29.0.11:0, UP
RP/0/RSP0/CPU0:Jun 30 03:29:07.079 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.12 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:07.894 : mpls_ldp[1043]: %ROUTING-LDP-5-NBR_CHANGE : Neighbor 172.29.0.1:0, UP
RP/0/RSP0/CPU0:Jun 30 03:29:08.134 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.2 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:08.924 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.11 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:09.511 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.5 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:10.033 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.6 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:12.443 : ospf[1011]: %ROUTING-OSPF-5-ADJCHG : Process 200, Nbr 172.29.0.11 on GigabitEthernet0/0/0/3 in area 0 from LOADING to FULL, Loading Done,vrf default vrfid 0x60000000
RP/0/RSP0/CPU0:Jun 30 03:29:13.192 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 172.29.0.8 Up (VRF: default)
RP/0/RSP0/CPU0:Jun 30 03:29:21.056 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB32: Bundle-Ether1.32: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.056 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB32: Bundle-Ether1.32: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.063 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB29: Bundle-Ether1.29: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.064 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB29: Bundle-Ether1.29: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.074 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB79: Bundle-Ether1.709: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.074 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB79: Bundle-Ether1.709: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.105 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB34: Bundle-Ether1.34: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.105 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB34: Bundle-Ether1.34: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.123 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB12: Bundle-Ether1.312: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.123 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB12: Bundle-Ether1.312: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.123 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB16: Bundle-Ether1.16: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.124 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB16: Bundle-Ether1.16: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.139 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB31: Bundle-Ether1.31: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.139 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB31: Bundle-Ether1.31: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.145 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB30: Bundle-Ether1.307: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.146 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB30: Bundle-Ether1.307: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.152 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB27: Bundle-Ether1.27: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.153 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB27: Bundle-Ether1.27: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.172 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB49: Bundle-Ether1.49: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.172 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB49: Bundle-Ether1.49: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.172 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB11: Bundle-Ether1.311: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.173 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB11: Bundle-Ether1.311: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.180 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.35: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.180 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.35: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.187 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.305: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.187 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.305: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.196 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB33: Bundle-Ether1.33: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.196 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB33: Bundle-Ether1.33: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.201 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB15: Bundle-Ether1.15: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.202 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB15: Bundle-Ether1.15: state Standby -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:21.212 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB60: Bundle-Ether1.360: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:21.212 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB60: Bundle-Ether1.360: state Standby         -> Active
RP/0/RSP0/CPU0:Jun 30 03:29:37.354 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.305: state Active -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.452 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB31: Bundle-Ether1.31: state Active   -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.606 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB79: Bundle-Ether1.709: state Active -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.631 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB33: Bundle-Ether1.33: state Active   -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.727 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB27: Bundle-Ether1.27: state Active   -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.815 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB11: Bundle-Ether1.311: state Active -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:37.862 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB60: Bundle-Ether1.360: state Active -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:38.037 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB15: Bundle-Ether1.15: state Active   -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:38.349 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.35: state Active   -> Speak
RP/0/RSP0/CPU0:Jun 30 03:29:47.355 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.305: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.453 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB31: Bundle-Ether1.31: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.607 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB79: Bundle-Ether1.709: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.632 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB33: Bundle-Ether1.33: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.728 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB27: Bundle-Ether1.27: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.815 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB11: Bundle-Ether1.311: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:47.863 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB60: Bundle-Ether1.360: state Speak   -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:48.038 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB15: Bundle-Ether1.15: state Speak    -> Standby
RP/0/RSP0/CPU0:Jun 30 03:29:48.350 : hsrp[1085]: %IP-STANDBY-6-INFO_STATECHANGE : SB35: Bundle-Ether1.35: state Speak    -> Standby

Hi Also the Crash dump looks like this:
RP/0/RSP0/CPU0:HOSTNAME#more LC1.130630-012501.crashinfo.by.p40x0mc
LC/0/0/CPU0:Jun 30 03:24:57.075 : p40x0mc[74]: ====== L3 CACHE ERROR #1 ======
LC/0/0/CPU0:Jun 30 03:24:57.080 : p40x0mc[74]: CPC Registers:        OFF      CPC1        CPC2
LC/0/0/CPU0:Jun 30 03:24:57.084 : p40x0mc[74]: CPCERRDET*            e40 0x80000008 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.088 : p40x0mc[74]: CPCCAPTECC            e28 0xc9000009 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.093 : p40x0mc[74]: CPCERRINTEN           e48 0x000000ec 0x000000ec
LC/0/0/CPU0:Jun 30 03:24:57.097 : p40x0mc[74]: CPCERRATTR            e4c 0x7082011d 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.102 : p40x0mc[74]: CPCERRADDR            e54 0x0fef1210 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.106 : p40x0mc[74]: CPCCSR0               000 0xc0000000 0xc0000000
LC/0/0/CPU0:Jun 30 03:24:57.110 : p40x0mc[74]: CPCCFG0               008 0x50b7c010 0x50b7c010
LC/0/0/CPU0:Jun 30 03:24:57.115 : p40x0mc[74]: CPCHDBCR0             f00 0x015e0000 0x015e0000
LC/0/0/CPU0:Jun 30 03:24:57.119 : p40x0mc[74]: CPCCAPTDTHI           e20 0x01001001 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.124 : p40x0mc[74]: CPCCAPTDTLO           e24 0x79d54656 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.128 : p40x0mc[74]: CPCPIR0x0             200 0xffffffff 0xffffffff
LC/0/0/CPU0:Jun 30 03:24:57.132 : p40x0mc[74]: CPCPAR0x0             208 0x000003fb 0x000003fb
LC/0/0/CPU0:Jun 30 03:24:57.137 : p40x0mc[74]: CPCPWR0x0             20c 0xffffffff 0xffffffff
LC/0/0/CPU0:Jun 30 03:24:57.140 : p40x0mc[74]: ====== DDR CONTROLLER ERROR #1 ======
LC/0/0/CPU0:Jun 30 03:24:57.144 : p40x0mc[74]: DDR Registers:        OFF      DDR1        DDR2
LC/0/0/CPU0:Jun 30 03:24:57.149 : p40x0mc[74]: ERR_DETECT*           e40 0x80000008 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.153 : p40x0mc[74]: ERR_INT_EN            e48 0x0000018d 0x0000018d
LC/0/0/CPU0:Jun 30 03:24:57.158 : p40x0mc[74]: CAPTURE_ATTRIBUTES    e4c 0x10832001 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.162 : p40x0mc[74]: CAPTURE_ADDRESS       e50 0x0fef1200 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.167 : p40x0mc[74]: CAPTURE_DATA_HI       e20 0x03001001 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.171 : p40x0mc[74]: CAPTURE_DATA_LO       e24 0x77a7f528 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.175 : p40x0mc[74]: CAPTURE_DATA_ECC      e28 0x21212121 0x00000000
LC/0/0/CPU0:Jun 30 03:24:57.317 : p40x0mc[74]: EISR0: 0x00000110 [DDR1|CPC1]
LC/0/0/CPU0:Jun 30 03:24:57.321 : p40x0mc[74]: DDR1 ERR_DETECT : 0x80000008 [MME|MBE] Count = 1
LC/0/0/CPU0:Jun 30 03:24:57.327 : p40x0mc[74]: CPC1 CPCERRDET   : 0x80000008 [MULLERR|DMBECCERR] Count = 1
LC/0/0/CPU0:Jun 30 03:24:57.330 : p40x0mc[74]: Shutting down node due to fatal error
LC/0/0/CPU0:Jun 30 03:24:59.343 : p40x0mc[74]: reboot_internal: Incomplete graceful reboot cleanup (Connection timed out)
LC/0/0/CPU0:Jun 30 03:24:59.343 : p40x0mc[74]: Sun Jun 30 03:24:57 2013:sync start
LC/0/0/CPU0:Jun 30 03:24:59.343 : p40x0mc[74]: Sun Jun 30 03:24:57 2013:sync end
LC/0/0/CPU0:Jun 30 03:24:59.343 : p40x0mc[74]: Sun Jun 30 03:24:57 2013:platform_reboot_op start
RP/0/RSP0/CPU0:HOSTNAME#more LC1.130630-102042.crashinfo.by.p40x0mc
LC/0/0/CPU0:Jun 30 01:27:00.002 : insthelper[61]: %INSTALL-INSTHELPER-7-PKG_DOWNLOAD : MBI running; starting software download
LC/0/0/CPU0:Jun 30 01:27:41.274 : sysmgr[90]: %OS-SYSMGR-5-NOTICE : Card is COLD started
LC/0/0/CPU0:Jun 30 01:27:41.757 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 51.189 seconds
LC/0/0/CPU0:Jun 30 01:27:42.383 : sysmgr[352]: %OS-SYSMGR-6-INFO : Backup system manager is ready
LC/0/0/CPU0:Jun 30 01:27:56.275 : lda_server[64]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing
LC/0/0/CPU0:Jun 30 01:27:57.435 : kdscrape-lc[62]: KERNEL-DUMP: Copied LC1.130630-012501.e500 to /harddisk:/dumper
LC/0/0/CPU0:Jun 30 01:27:57.542 : kdscrape-lc[62]: KERNEL-DUMP: Copied LC1.130630-012501.crashinfo.by.p40x0mc to /harddisk:/dumper
LC/0/0/CPU0:Jun 30 01:28:01.269 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_1_FAIL_0 : Set|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 1 Failure on FIA 0
LC/0/0/CPU0:Jun 30 01:28:01.271 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_0_FAIL_0 : Set|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 0 Failure on FIA 0
LC/0/0/CPU0:Jun 30 01:28:09.559 : prm_server_ty[303]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
LC/0/0/CPU0:Jun 30 01:28:09.563 : prm_server_ty[303]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
LC/0/0/CPU0:Jun 30 01:28:10.011 : sysmgr[90]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
LC/0/0/CPU0:Jun 30 01:28:13.005 : syslog_dev[88]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
LC/0/0/CPU0:Jun 30 03:28:15.980 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Invalid to Customer Facing
LC/0/0/CPU0:Jun 30 03:28:15.984 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Invalid to Not Interested
LC/0/0/CPU0:Jun 30 03:28:34.330 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_1_FAIL_0 : Clear|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 1 Failure on FIA 0
LC/0/0/CPU0:Jun 30 03:28:34.331 : pfm_node_lc[291]: %FABRIC-FIA-1-DATA_SB_SERDES_0_FAIL_0 : Clear|fialc[139329]|Fabric Interface(0x103b000)|Data SB Serdes Link 0 Failure on FIA 0
LC/0/0/CPU0:Jun 30 03:28:44.631 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.632 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.633 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.633 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:44.637 : cfgmgr-lc[134]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/0/2' has been restored.
LC/0/0/CPU0:Jun 30 03:28:47.602 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Customer Facing to Core Facing
LC/0/0/CPU0:Jun 30 03:28:47.603 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Not Interested to Core Facing
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.022 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.023 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.023 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.024 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.025 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.026 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.026 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.030 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.031 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.031 : ifmgr[201]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.032 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.033 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.034 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.035 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.035 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Jun 30 03:28:51.043 : cfgmgr-lc[134]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/0/0' has been restored.
LC/0/0/CPU0:Jun 30 03:28:57.029 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv4 role of the card has changed from Core Facing to Standard
LC/0/0/CPU0:Jun 30 03:28:57.030 : rsi_agent[318]: %OS-RSI_AGENT-6-CARD_ROLE_CHANGE : Based on the card configuration/type, the AFI IPv6 role of the card has changed from Core Facing to Standard
LC/0/0/CPU0:Jun 30 03:28:58.163 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/6, changed state to Up
LC/0/0/CPU0:Jun 30 03:28:58.165 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.825 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/0, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.827 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.840 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/1, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.841 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.855 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/2, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:03.857 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:04.016 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/4, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:04.018 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:05.811 : pfm_node_lc[291]: %PLATFORM-SFP-3-HIGH_RX_POWER_WARNING : Set|envmon_lc[143443]|SFP(0x1029001)|Port_0/01
LC/0/0/CPU0:Jun 30 03:29:05.811 : pfm_node_lc[291]: %PLATFORM-SFP-3-HIGH_RX_POWER_WARNING : Set|envmon_lc[143443]|SFP(0x1029002)|Port_0/02
LC/0/0/CPU0:Jun 30 03:29:06.914 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : #ALMLOC#: Interface GigabitEthernet0/0/0/3, changed state to Up
LC/0/0/CPU0:Jun 30 03:29:06.915 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : #ALMLOC#: Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Up
LC/0/0/CPU0:Jun 30 12:20:38.138 : p40x0mc[74]: ====== DDR CONTROLLER ERROR #1 ======
LC/0/0/CPU0:Jun 30 12:20:38.142 : p40x0mc[74]: DDR Registers:        OFF      DDR1        DDR2
LC/0/0/CPU0:Jun 30 12:20:38.146 : p40x0mc[74]: ERR_DETECT*           e40 0x80000008 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.151 : p40x0mc[74]: ERR_INT_EN            e48 0x0000018d 0x0000018d
LC/0/0/CPU0:Jun 30 12:20:38.155 : p40x0mc[74]: CAPTURE_ATTRIBUTES    e4c 0x50852001 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.159 : p40x0mc[74]: CAPTURE_ADDRESS       e50 0x0ec80810 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.164 : p40x0mc[74]: CAPTURE_DATA_HI       e20 0x7ccf5002 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.168 : p40x0mc[74]: CAPTURE_DATA_LO       e24 0x00000264 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.173 : p40x0mc[74]: CAPTURE_DATA_ECC      e28 0x39393939 0x00000000
LC/0/0/CPU0:Jun 30 12:20:38.284 : p40x0mc[74]: EISR0: 0x00000100 [DDR1]
LC/0/0/CPU0:Jun 30 12:20:38.289 : p40x0mc[74]: DDR1 ERR_DETECT : 0x80000008 [MME|MBE] Count = 1
LC/0/0/CPU0:Jun 30 12:20:38.292 : p40x0mc[74]: Shutting down node due to fatal error
LC/0/0/CPU0:Jun 30 12:20:40.305 : p40x0mc[74]: reboot_internal: Incomplete graceful reboot cleanup (Connection timed out)
LC/0/0/CPU0:Jun 30 12:20:40.305 : p40x0mc[74]: Sun Jun 30 12:20:38 2013:sync start
LC/0/0/CPU0:Jun 30 12:20:40.305 : p40x0mc[74]: Sun Jun 30 12:20:38 2013:sync end
LC/0/0/CPU0:Jun 30 12:20:40.305 : p40x0mc[74]: Sun Jun 30 12:20:38 2013:platform_reboot_op start
I am getting cisco to help with replacing the card, but what are the odds of the issue coming back? can we say the LC is faulty?

How to choose RT System at Run Time

Variations of this question have been asked, but I'm not sure if they've been answered.
We use LabVIEW RT to do a variety of behavior tests. We have multiple experimenters using the same hardware, and each has his/her own set of "What I want to do" requirements.
Originally, we used LabVIEW 7.0 (i.e. Before Project) to develop a Host and Remote (PXI) application. The Host application was built as an .EXE, while the Remote was saved as an .LLB, copied to the PXI, and "invoked" at Run Time by calls to VI Server. Note that this means that the code on the Remote might (is?) not be as compact, efficient, or optimized as if we had built an .EXE. But we definitely can have Bob's Experiment, Jane's Experiment, and Joe's Experiment on the PC (as separate executables), and each could respectively call Bob's RT, Jane's RT, or Joe's RT on the PXI at run time. No need to have LabVIEW (or LabVIEW expertise) on this system, and Bob, Jane, and Joe can be "ordinary users".
"Modern LabVIEW" takes a slightly different (and probably better) view towards Real-Time -- both the Host and Remote programs are built as Executables (the RT is built as an .RTEXE). We can "pre-deploy" the RT code to the PXI, and set it to run at Startup. This makes getting the RT side "running" semi-automatic -- all you need to do (if it isn't running) is reboot the PXI.
But what if you want Bob, Jane, and Joe's version, selectable by running (on the Host) Bob, Jane, or Joe's Host application?
I'm playing with the following algorithm, which seems to work. I'm presenting it here to get feedback, especially if there is a "better way" to do this.
The key to this method is that there is an .INI file on the Remote, C:\ni-rt.ini, that contains, among other things, the RT Target's Startup Application path (by default, this is C:\ni-rt\startup\startup.rtexe).
Consider three Projects, Project Bob, Project Jane, and Project Joe. Within each Project, a Host executable is built having a name like "UI Bob" (or "Jane" or "Joe"), while the Target executable is given the name "RT Bob" (or "Jane" or "Joe"). The three .RTEXE files are copied to the Target and placed in the Startup folder, C:\ni-rt\startup.
Now run one of the Host executables. It does the following:
FTP a copy of C:\ni-rt.ini from the Target to itself.
Get the name of the Startup .RTEXE.
If it is the "appropriate" name (i.e. if the Host program is UI Bob.exe, the Remote should be RT Bob.rtexe), do nothing, as the Target is already running the right code.
Otherwise, we need to force the Target to run the correct Target code. We can do this by changing the Startup entry in the .INI file to the Remote code we need (for example, RT Bob.rtexe), then tell the Remote to Reboot. When it comes back, it will be running the appropriate RT code.
The Host now goes ahead and tries to connect to the Remote. If a connection cannot be established (for example, the Remote code might have stopped), a Reboot of the Remote might fix things up.
Short of trying to write a single enormous program that encompasses every experimental scenario and situation (i.e. have a big Case Statement with a Bob, Jane, or Joe "choice", and a single executable that had everyone's code in it), this seemed to be a fairly simple way to have the robustness of compiled executables on both the Host and Remote machines, yet maintain the flexibility to let the (non-LabVIEW-guru) User choose which executable to run.
I haven't fully deployed this system -- I'm currently at "Proof-of-Concept" stage, but I've got the various "pieces" working. Does this seem like a sensible appropach? Are there other, simpler, ways to accomplish this?
Bob Schor

Hey Bob.
So I assume you're -completely- working with built executables? You're not going to work in the editor environment to modify your projects at all?
If this is the case, then having a generic deployment phase at the beginning of the executable (with a "setting up hardware for your app" splash screen) isn't a bad idea -
Check the binary on the target, ensure it matches the binary you have on the host machine (in case you ever decide to update).
If they don't match, FTP the new file down to replace the old one.
FTP the ni-rt.ini file, ensure the startup exe is enabled and is pointing to the correct location.
If it's not enabled or not pointing to the correct startup file, modify the .INI file and FTP back to the target.
If you had to update the INI file, ask target to reboot itself. Wait 30 seconds, and wait for target to become available again.
Connect to the target. If you cannot connect, reboot target. If the target comes back and you still cannot connect to the app, notify user.
That's almost exactly how we handle installation and deployment via MAX.
The big assumption here is that the built executables were all built with the same version of LabVIEW Real-Time. If not, you'd need a system replication step in there to make sure the proper version of LabVIEW is on the target before launching the built .rtexe.
-Danny

Server can't get to internet

File server:
SunFire X4140
OpenSolaris
SunOS 5.11 svn_111b
Hi,
I'm new to sysadmin, and very new to solaris. Any help would be very much appreciated - I'm trying to get a file server back on the internet that a couple dozen people are waiting for! It's part of a small ad hoc cluster in a rack. It had been working fine every since I started to take care of things part-time 6 months ago. The other day it just dropped off the internet. Then, when I tried a console GUI login at that point it froze up (the GUI, at least). I had to use the serial management port to do a graceful reboot.
There is an external switch to which all servers are connected, and a local switch used by several (but not all) of the servers in the rack with the file server. I've inherited this system and am unsure of the full rationale of the local switch, but imagine it's for faster local file transfer.
Other servers in the rack are online, BUT they're running linux variants. The file server runs opensolaris to be able to use zfs. There's another opensolaris server in the rack but it's stuck booting up kubuntu, looking for an NFS mount and I can't get it to skip the mount - haven't focused on this b/c it's non-essential.
The file server system (see above) boots and I can login, but cannot get online. I get these errors at boot:
1) The 'opensolaris' graphical boot screen (with the moving orange progress bar) seems to hang. After several minutes I hit return to enter CLI mode. At that point I see errors 2 and 3. I can login.
2) WARNING: /pci@0,0/pci10de,cb84@2 (ohci0): Connecting device on port 2 failed
I'm not sure if this is the built-in NIC's, or built-in rear USB ports - or something else. Haven't been able to determine for sure. The rear USB ports don't seem to be working - I have to plug the keyboard into the front usb port to get it to work, so maybe it's the usb.
3) in.ndpd[429]: interface nge[0|1|2|3] has been removed from the kernel. in.ndpd will no longer use it
The server has 4 built-in ethernet ports, no others. There are three ethernet cables plugged in - two for the external switch, one for the internal switch. The error for a given interface is only generated when there is a cable plugged into the port, and regardless of whether it goes to local or external switch. Then it repeats the error every minute for 2 of the 3 cables - haven't found a pattern as to which.
If I connect only one cable, either to internal or external switch, I don't get this error. But, I still don't IPv4 address, see below.
"ifconfig -a" output (transcribed)
(cables are plugged into ports 1,2 and 3 (as labeled on the hardware) but not 0):
lo0: flags=2001000849 <skip>
     inet 127.0.0.1 netmask ff000000
nge0: flags=1004803<UP,BROADCAST,MULTICAST,DHCP,IPv4> mtu 1500 index 2
     inet 0.0.0.0 netmask ff000000
     ether 0:21:28:3d:6d:2
nge1: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 3
     inet 0.0.0.0 netmask ff000000
     ether 0:21:28:3d:6d:3
nge2: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 4
     inet 0.0.0.0 netmask ff000000
     ether 0:21:28:3d:6d:4
nge3: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
     inet 0.0.0.0 netmask ff000000
     ether 0:21:28:3d:6d:5
lo0: flags=2002000849 <skip>
     inet6 ::1/128
nge[1|2] [changes to the nge that was not most recently reported as removed by in.ndpd error.]: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index [3|4]
     inet6 fe80::221:28ff:fe3d:6d0[3|4]/10
     ether 0:21:28:3d:6d:4
Phew. Thanks very much for any help or suggestions!
-Michael
Edited by: 979786 on Jan 3, 2013 11:04 AM
Edited by: 979786 on Jan 3, 2013 11:08 AM
Edited by: 979786 on Jan 3, 2013 11:10 AM
Edited by: 979786 on Jan 3, 2013 12:09 PM

There might be some eventual replies to your inquiry, but you may need to realize that an online forum is the worst place to hope for help for business-critical issues. The anonymous nature of such a forum is that there is no obligation that there ever be a reply and there is no guarantee that replies are correct for your issue.
Such a system as you have described needs to be on a support contract (even though OpenSolaris isn't a supportable OS -- it's a discontinued Open Source experiment ). You need to use your support contract to contact Technical Support and open a Service Request to figure out why you have no IPV4 IP addresses, nor any current IPV6 IP addresses.
... but I do give you props for at least trying.
:)

Booting into recovery mode and Web service in 10.7 server

I have two servers: Server A is running 10.6 server and server B is running 10.7 server. Both are on the same LAN at a data center. My questions are as follows:
1 - is there a way to restart server B into recovery mode remotely? (and not using a KVM)
2 - if server B was booted successfully into recovery mode is there a way to screen share with it from server A? If so how would this be done?
3 - can Apple Remote Desktop reboot a 10.7 machine into recovery mode and still continue to see its screen?
4 - in the Server app of 10.7 server there is a default website setup in the Web service. it doesn't seem possible to edit any of the information for this default website, is this true?
5 - is there any way to get the Web service in the 10.7 Server Admin tools? it is missing among many other services.
Thanks

Probability is very high that you have a hardware failure. You should get an external bootable drive (or startup with a bootable DVD if you can) JUST to prove that it's not the motherboard, but probably the hard drive that's failed.

Cant add Apps to login items with profile manager

I can set up profile manager successfully, and set certain settings like the Dock, the login window, etc. But when I click on Login Items, and try to add an Application, the list of applications is blank. Tried it from my server, tried it logged in remotely, tried rebooting, tried it on several accounts and several groups, and its always empty.

found it:
/usr/bin/osascript -e 'tell application "System Events" to make new login item with properties { path: "/Applications/iChat.app", hidden:false } at end'

UFC 163 Not Showing In Program List

Hello,
This event is supposed to be on BT Sport tonight, but the tv guide does not show it.
Is it still on?
Solved!
Go to Solution.

Ok, i solved it by holding down the power button on the remote, Vision rebooted and the channels have their correct info.

NLA Disabled. Still can't RDP; "requires Network Level Authentication"

Had a server I could RDP onto without any issue running Hyper V.
I removed the Hyper V role.
I then rebooted and attempted to RDP onto the server and can't:
The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using
the options on the Remote tab of the System Properties dialog box.
OK... Never needed before.
I checked the network settings remotely with netsh and confirmed correct DC as DNS. So I'm scratching my head why Microsoft are lying to me?
OK, so I check the NLA settings remotely, sure enough is enabled. So I disabled via remote registry, reboot the machine, confirm the registry is set to NLA disabled again remotely and attempt to connect.
And... Same message.
I can access any other of the 2012 R2 servers on my domain without issue. I can open AD or any other Domain tools from other servers with the same DC as the problem server as their primary DNS.
How can I get that message when both the DC is contactable and NLA is disabled?
How did removing a role cause this BS suddenly?

Hi,
Thank you for posting in Windows Server Forum.
Which version of client RDP you are using?
You can use RDP v8.1 for better performance.
Apart from above, Use local admin account to log on to the virtual machine and set the DNS to point to your DC. Alternatively, assign the IP address of the DC/DNS under DNS servers of virtual network.
Also when trying to remote desktop check the option “Allow connection from computers running any version of Remote desktop (less secure)” under system properties.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote 'Graceful' reboot

Similar Messages

Maybe you are looking for