ASR9001 module A9K-MPA-20X1GE issue

Hi all!
Who knows, what does these messages mean?
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)' 
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error)  : pkg/bin/lda_server : (PID=40990) :  -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
Is this hardware or software issue? What do you think?
I think we have faced with hardware issue of module A9K-MPA-20X1GE.
More outputs:
RP/0/RSP0/CPU0:asr9001#sh ver
Tue Oct 22 10:53:46.186 UTC
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 2.01(20130627:172232) [ASR9K ROMMON], 
asr9001 uptime is 6 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-4.3.2/0x100000/mbiasr9k-rp.vm"
cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
P4040 processor at 1500MHz, Revision 2.0
ASR-9001 Chassis
2 Management Ethernet
4 TenGigE
4 DWDM controller(s)
4 WANPHY controller(s)
219k bytes of non-volatile configuration memory.
2880M bytes of hard disk.
3932144k bytes of disk0: (Sector size 512 bytes).
Configuration register on node 0/RSP0/CPU0 is 0x102
Boot device on node 0/RSP0/CPU0 is disk0:
Package active on node 0/RSP0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
    Built on Sun Sep  1 19:23:39 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
    Built on Sun Sep  1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
    Built on Sun Sep  1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
    Built on Sun Sep  1 19:21:19 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
    Built on Sun Sep  1 19:21:22 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
    Built on Sun Sep  1 19:21:16 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
    Built on Sun Sep  1 19:27:30 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-mgbl, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-mgbl-4.3.2
    Built on Sun Sep  1 19:28:25 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-supp-4.3.2
    Built on Sun Sep  1 19:28:25 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-px-4.3.2
    Built on Sun Sep  1 19:28:37 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-4.3.2
    Built on Sun Sep  1 19:29:15 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-px-4.3.2
    Built on Sun Sep  1 19:29:40 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9K-doc-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9K-doc-supp-4.3.2
    Built on Sun Sep  1 19:29:07 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-doc-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-doc-px-4.3.2
    Built on Sun Sep  1 19:29:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
Boot device on node 0/0/CPU0 is mem:
Package active on node 0/0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
    Built on Sun Sep  1 19:23:39 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
    Built on Sun Sep  1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
    Built on Sun Sep  1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
    Built on Sun Sep  1 19:21:19 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
    Built on Sun Sep  1 19:21:22 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
    Built on Sun Sep  1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
    Built on Sun Sep  1 19:21:16 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
    Built on Sun Sep  1 19:27:30 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#sh log
Tue Oct 22 10:54:22.823 UTC
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
    Console logging: level warnings, 44 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 0 messages logged
    Buffer logging: level debugging, 148 messages logged
Log Buffer (307200 bytes):
RP/0/RSP0/CPU0:Oct 22 10:47:29.090 : init[65540]: %OS-INIT-7-MBI_STARTED : total time 8.814 seconds
RP/0/RSP0/CPU0:Oct 22 10:47:29.113 : imio[64]: %PLATFORM-IMIO-3-OPERATION_NOTIFY : imio_main: cold start  
RP/0/RSP0/CPU0:Oct 22 10:48:42.672 : sysmgr[96]: %OS-SYSMGR-5-NOTICE : Card is COLD started 
RP/0/RSP0/CPU0:Oct 22 10:48:50.075 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 89.801 seconds
RP/0/RSP0/CPU0:Oct 22 10:48:51.803 : sysmgr[407]: %OS-SYSMGR-6-INFO : Backup system manager is ready 
RP/0/RSP0/CPU0:Oct 22 10:48:52.088 : sc_reddrv[376]: imio_lance2_init_interrupts:
RP/0/RSP0/CPU0:Oct 22 10:48:58.262 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : node set to DSC 
RP/0/RSP0/CPU0:Oct 22 10:49:04.763 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-SYSTEM_COLD_START : System cold start detected.  Resetting Line Cards.
RP/0/RSP0/CPU0:Oct 22 10:49:06.487 : pwr_mgmt[360]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM1/SP failure condition raised : Module input voltage out of range
RP/0/RSP0/CPU0:Oct 22 10:49:07.565 : online_diag_rsp[427]: %DIAG-DIAG-6-RUN_MINIMUM : ASR9001-RP 0/RSP0/CPU0: Running Minimum Diagnostics...
RP/0/RSP0/CPU0:Oct 22 10:49:09.369 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM : Fan tray RPM warning on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:49:12.761 : bpe[144]: %PLATFORM-BPE-5-INFO : successfully retrieved i2c eeprom
RP/0/RSP0/CPU0:Oct 22 10:49:12.969 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-7-CAN_INFO : Can API: slot 0 online event.
RP/0/RSP0/CPU0:Oct 22 10:49:12.991 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-3-POWER_SUPPLY_REDUNDANCY : Power Supply Failures are not protected.
RP/0/RSP0/CPU0:Oct 22 10:49:13.624 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/FT0/SP inserted 
RP/0/RSP0/CPU0:Oct 22 10:49:13.780 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM0/SP inserted 
RP/0/RSP0/CPU0:Oct 22 10:49:13.788 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM1/SP, state: FAILED
RP/0/RSP0/CPU0:Oct 22 10:49:13.789 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM1/SP inserted 
RP/0/RSP0/CPU0:Oct 22 10:49:13.800 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/RSP0/CPU0, state: IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:49:18.393 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_ERROR : Failed in envmon lwmconnect.message channel connection failed!,-1 error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511) 
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in envmon_fantray_alarms.7076, error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511) 
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-2-ENV_CONDITION : Outstanding environmental condition exists in the chassis
RP/0/RSP0/CPU0:Oct 22 10:49:19.815 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:20.816 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:21.817 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:22.843 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/RSP0/CPU0 inserted 
RP/0/RSP0/CPU0:Oct 22 10:49:27.313 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.  
RP/0/RSP0/CPU0:Oct 22 10:49:32.838 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_DISCOVERY : Node State Discovery complete
RP/0/RSP0/CPU0:Oct 22 10:49:32.854 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.905 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FT0/SP FAN TRAY state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.957 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/CPU0 inserted 
RP/0/RSP0/CPU0:Oct 22 10:49:35.224 : syslog_dev[94]: hsbi_fpd_agent[240]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:49:37.310 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to IOXR in state default 
RP/0/RSP0/CPU0:Oct 22 10:49:48.759 : syslog_dev[94]: netio[327]: > WARNING (BM) [/ws/akgoswam-bgl/hellhound/nto6.4-XR/cisco/lib/3rdparty/netcomm/NetCommSw/Peripherals/BM/bm.h:352 BmBpidGet]: No Ipc - can't validate bpid.^M
RP/0/RSP0/CPU0:Oct 22 10:50:02.721 : ipodwdm[275]: %L2-G709-6-INFO : /harddisk:/ipodwdm_log  Already present
RP/0/RSP0/CPU0:Oct 22 10:50:03.698 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/0/CPU0, RomMon Version: 2.1
RP/0/RSP0/CPU0:Oct 22 10:50:04.481 : shelfmgr[381]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : Remote location 0/0/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.3.2/lc/mbiasr9k-lc.vm validated
RP/0/RSP0/CPU0:Oct 22 10:50:04.499 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-BOOTING
RP/0/RSP0/CPU0:Oct 22 10:50:07.632 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to ACTV in state default 
RP/0/RSP0/CPU0:Oct 22 10:50:14.758 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED 
RP/0/RSP0/CPU0:Oct 22 10:50:14.764 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED 
RP/0/RSP0/CPU0:Oct 22 10:50:29.223 : placed[346]: LR-PLANE-READY DECLARATION
RP/0/RSP0/CPU0:Oct 22 10:50:31.360 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM_CLEAR : Fan tray RPM warning cleared on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:50:33.247 : ifmgr[242]: %PKT_INFRA-LINK-5-CHANGED : Interface MgmtEth0/RSP0/CPU0/1, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.257 : cfgmgr-rp[158]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/RSP0/0' has been restored.
RP/0/RSP0/CPU0:Oct 22 10:50:35.006 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM1/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.012 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM0/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.588 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:50:35.589 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED 
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED 
RP/0/RSP0/CPU0:Oct 22 10:51:23.316 : dsc[181]: %PLATFORM-DSC_CTRL-6-RACK_STATE :  Rack 1 is now Down 
RP/0/RSP0/CPU0:Oct 22 10:51:23.321 : gsp[239]: gsp_rack_down_handler: for node:0x1
RP/0/RSP0/CPU0:Oct 22 10:51:25.396 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-RUNNING
LC/0/0/CPU0:10: init[65540]: %OS-INIT-7-MBI_STARTED : total time 5.152 seconds
LC/0/0/CPU0:Oct 22 10:51:57.119 : sysmgr[91]: %OS-SYSMGR-5-NOTICE : Card is COLD started 
LC/0/0/CPU0:Oct 22 10:51:57.524 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 38.219 seconds
LC/0/0/CPU0:Oct 22 10:51:58.119 : sysmgr[341]: %OS-SYSMGR-6-INFO : Backup system manager is ready 
RP/0/RSP0/CPU0:Oct 22 10:52:11.473 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 UNKNOWN state:UNPOWERED
RP/0/RSP0/CPU0:Oct 22 10:52:11.896 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:POWER UP
LC/0/0/CPU0:Oct 22 10:52:12.716 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing  
RP/0/RSP0/CPU0:Oct 22 10:52:13.786 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:INITIALIZED
LC/0/0/CPU0:Oct 22 10:52:25.265 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
LC/0/0/CPU0:Oct 22 10:52:25.273 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
LC/0/0/CPU0:Oct 22 10:52:25.402 : lda_server[65]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : fpga3 instance 0 is down-rev (V0.07), upgrade to (V0.08). Use the "upgrade hw-module fpd" CLI in admin mode.
LC/0/0/CPU0:Oct 22 10:52:25.632 : sysmgr[91]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.  
LC/0/0/CPU0:Oct 22 10:52:27.651 : syslog_dev[89]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:52:37.663 : exec[65727]: %MGBL-exec-3-LOGIN_AUTHEN : Login Authentication failed. Exiting...
RP/0/RSP0/CPU0:Oct 22 10:52:43.079 : exec[65727]: %SECURITY-login-6-AUTHEN_SUCCESS : Successfully authenticated user 'shopik' from 'console' on 'con0_RSP0_CPU0'
RP/0/RSP0/CPU0:Oct 22 10:52:46.558 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.578 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.583 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 inserted 
LC/0/0/CPU0:Oct 22 10:52:58.858 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/6, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/4, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/0, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:53:00.041 : upgrade_fpd_cli[65763]: %PLATFORM-UPGRADE_FPD-6-STATUS : FPD upgrade started.
LC/0/0/CPU0:Oct 22 10:53:01.800 : lda_server[65]: %PLATFORM-SCC-2-BAD_ID_HW : Failed Identification Test in 0/130/0 [5/0] The module in 0/130/0 in this router may not be a genuineCisco product.  Cisco warranties and support programs onlyapply to genuine Cisco products.  If Cisco determines thatyour insertion of non-Cisco SPA cards or other modules into aCisco product is the cause of a support issue, Cisco maydeny support under your warranty or under a Cisco supportprogram such as SmartNet.  
RP/0/RSP0/CPU0:Oct 22 10:53:09.746 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:53:09.755 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: IOS XR RUN
LC/0/0/CPU0:Oct 22 10:53:31.822 : lda_server[65]: %PLATFORM-LDA-4-MPA_OIR_QUICK_BACK_TO_BACK_ERROR : OIR operation was performed on MPA in bay:0 while the system is initializing. Recommend waiting for two minutes after EP initialized.
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)' 
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error)  : pkg/bin/lda_server : (PID=40990) :  -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#show inventory
Tue Oct 22 11:01:32.251 UTC
NAME: "module 0/RSP0/CPU0", DESCR: "ASR 9001, Route Switch Processor with 8GB memory"
PID: ASR9001-RP, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/CPU0", DESCR: "ASR 9001, Modular Line Card"
PID: ASR9001-LC, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/0", DESCR: "ASR 9000 20-port 1GE Modular Port Adapter"
PID: A9K-MPA-20X1GE, VID: V00, SN: FOC1522XXXX
NAME: "module 0/0/2", DESCR: "ASR 9000 Virtual Module"
PID: A9K-MODULEv, VID: N/A, SN: N/A

Bryan,
We checked the "show hw-module fpd location all" and there is no "yes" in the last column.
http://pastebin.com/W1wuqYks
RP/0/RSP0/CPU0:asr9001#sh hw-module fpd location all
Thu Oct 24 13:40:19.487 UTC
===================================== ==========================================
                                      Existing Field Programmable Devices
                                      ==========================================
                                        HW                       Current SW Upg/
Location     Card Type                Version Type Subtype Inst   Version   Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0  ASR9001-RP                 1.0   lc   fpga2   0       1.14     No
                                              lc   cbc     0      22.114    No
                                              lc   rommon  0       2.01     No
0/FT0/SP     ASR-9001-FAN               1.0   ft   cbc     7      24.114    No
0/0/CPU0     ASR9001-LC                 1.0   lc   cbc     0      23.114    No
                                              lc   fpga2   0       1.18     No
                                              lc   fpga4   0       2.07     No
                                              lc   rommon  0       2.01     No

Similar Messages

  • Unable to power up MPA A9K-MPA-8X10GE state:FAILED

    Hi Guys, need your advice. We have installed the MPA A9K-MPA-8X10GE to the line card and try multiple commands but failed to bring that up. However if we we reset the line card and it works. We understand as per spec this card is supporting OIR. The question is there any special command that can initialise the card and make it work without reseting the linecard We are not able to reset the LC because it is life machine. LC/0/1/CPU0:Aug 21 20:04:46.656 AEST: pcie-server[77]: addup_resources: Alloc mem failed LC/0/1/CPU0:Aug 21 20:04:46.656 AEST: pcie-server[77]: addup_resources: Alloc mem failed LC/0/1/CPU0:Aug 21 20:04:56.659 AEST: pcie-server[77]: addup_resources: Alloc mem failed LC/0/1/CPU0:Aug 21 20:04:56.660 AEST: pcie-server[77]: addup_resources: Alloc mem failed LC/0/1/CPU0:Aug 21 20:04:56.660 AEST: lda_server[65]: %PLATFORM-LDA-3-MPA_POWER_FAILURE : Unable to power on MPA in bay:1. Reason:PCIE init failed (0x00000013-No such device) LC/0/1/CPU0:Aug 21 20:04:57.466 AEST: lda_server[65]: %L2-SPA-5-OIR_ERROR : timeout when waiting for hw signal for SPA in bay 1 LC/0/1/CPU0:Aug 21 20:04:57.466 AEST: lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 1 type A9K-MPA-8x10GE Initing RP/0/RSP0/CPU0:Aug 21 20:04:57.469 AEST: invmgr[257]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/1/1, state: FAILED RP/0/RSP0/CPU0:Aug 21 20:04:57.473 AEST: shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/1 A9K-MPA-8X10GE state:IN-RESET

    Hello,
    Have you seen this multiple times?
    Can you do OIRs without issue now?
    Do you have a TAC SR opened?
    Thanks,
    Sam

  • ASR9006/A9K-MPA-4X10GE

    Hi,
    we are new on ASR and IOS XR. We have an ASR 9006 with the line card in the discussion subject (A9K-MPA-4X10GE). The four leds on the card are red. Is there any command to activate? Is a Layer 1 problem?
    Our release is Cisco IOS XR Software, Version 4.3.0[Default].
    Thank You!!!

    Red LEDs mean that Port is physically down at layer-1. Are these ports connected at other end with 10G device??
    Can you please share the output of following;
    show int desc | i Te
    show int te x/x/x/x

  • Function Module GUI_DOWNLOAD: Type String Issue

    I am working in 4.6C. I have used this Function Module many times in the past without issue, but not at this site. It abends and gives me the error message:
    The call to the function module "GUI_DOWNLOAD" is incorrect:                                                                               
    The function module interface allows you to specify only fields          
    of a particular type under "FILENAME". The field "FNAME" specified here  
    has a different field type.                                              
    Here is the field declaration in the code:
    PARAMETER: fname type rlgrap-filename DEFAULT 'C:/New_PO_Format.xls'.
    The import parameter in GUI_DOWNLOAD for FILENAME is type STRING. When I double click on STRING in the FM I get "Unable to find a tool to process request". And, TYPE STRING does not exist in the system? I started making a Z version of GUI_DOWNLOAD, but it started giving me headaches because I had to start copying other SAP function modules.
    Am I missing something? Or, is there a new and improved version of GUI_DOWNLOAD to use?

    data : v_file type string.
    PARAMETER: fname type rlgrap-filename DEFAULT 'C:/New_PO_Format.xls'.
    start-of-selection.
    v_file = fname.
    use v_file in gui_download parameter.
    Thanks
    Seshu

  • Module Function Name Resolution - Issues with DefaultCommandPrefix

    Just getting started on module development, running PS4, and I've run into an... inconsistency... that I'm trying to understand. I've got two test functions, Get-Something and Set-Something in a script module. In my manifest file I specify a DefaultCommandPrefix
    of 'Test'.
    My issue is the function name resolution doesn't result in an executable result if you leave PowerShell up to it's own process.
    To begin with I closed all sessions and deleted all files in the CommandAnalysis directory. After starting a session I waited for the CommandAnalysis cache to populate. Then I ran a series of test commands to illustrate how, most of the time, the function
    name PowerShell registers with tab completion can't be executed because it lacks the 'Test' prefix. Even worse, much of the time tab completion won't recognize the correct (i.e., with prefix) name of the function and honor tab completion for it.
    Having just learned of the CommandAnalysis cache I assumed I would see it change as PowerShell 'learned' more about the module because the name resolves differently over time. I've included three files at the end of this post, the module code (ModuleTest.psm1),
    the manifest (ModuleTest.psd1) and the capture of output to the PowerShell session (ModuleTest.txt). I've tried to include the times I used <tab> and <ret> for tab completion and execution as well as (comments in parenthesis for things I did like
    starting a new session and checking the CommandAnalysis cache for changes).
    An example is, when first starting a session typing 'get-som<tab>' will resolve to 'Get-Something' (prefix 'Test' missing) and typing 'get-test<tab>' won't resolve to 'Get-TestSomething'. Try to execute the 'Get-Something' from tab completion
    and you'll get the 'name not recognized, blah, blah'.
    Now if you type 'get-som<tab>' PowerShell will resolve to 'ModuleTest\Get-Something' - looks promising... but no.  Try to execute the 'ModuleTest\Get-Something' from tab completion and you'll still get the 'name not recognized, blah, blah'.
    Even though the same key strokes resolved differently there were no changes made to the CommandAnalysis cache so I'm lost on why it produces two different (though equally useless) results.
    Manually importing the module and sometimes running Get-Command -Module ModuleTest will make tab completion of the function names behave correctly. Is this a known issue with using DefaultCommandPrefix in script modules or is there something I need to include
    in the manifest to enforce strict name recognition (including the prefix)?
    <ModuleTest.psm1>
    function Get-Something
     Write-Host "Get-Something Executed"
    function Set-Something
     Write-Host "Set-Something Executed"
    <ModuleTest.psd1>
    # Script module or binary module file associated with this manifest
    ModuleToProcess = 'ModuleTest.psm1'
    # Version number of this module.
    ModuleVersion = '1.0.0.0'
    # ID used to uniquely identify this module
    GUID = '241877ff-64be-40c8-a603-8d5acf7a48d8'
    # Author of this module
    Author = 'wb3'
    # Company or vendor of this module
    CompanyName = ''
    # Copyright statement for this module
    Copyright = '(c) 2015. All rights reserved.'
    # Description of the functionality provided by this module
    Description = 'Module description'
    # Minimum version of the Windows PowerShell engine required by this module
    PowerShellVersion = '2.0'
    # Name of the Windows PowerShell host required by this module
    PowerShellHostName = ''
    # Minimum version of the Windows PowerShell host required by this module
    PowerShellHostVersion = ''
    # Minimum version of the .NET Framework required by this module
    DotNetFrameworkVersion = '2.0'
    # Minimum version of the common language runtime (CLR) required by this module
    CLRVersion = '2.0.50727'
    # Processor architecture (None, X86, Amd64, IA64) required by this module
    ProcessorArchitecture = 'None'
    # Modules that must be imported into the global environment prior to importing
    # this module
    RequiredModules = @()
    # Assemblies that must be loaded prior to importing this module
    RequiredAssemblies = @()
    # Script files (.ps1) that are run in the caller's environment prior to
    # importing this module
    ScriptsToProcess = @()
    # Type files (.ps1xml) to be loaded when importing this module
    TypesToProcess = @()
    # Format files (.ps1xml) to be loaded when importing this module
    FormatsToProcess = @()
    # Modules to import as nested modules of the module specified in
    # ModuleToProcess
    NestedModules = @()
    # Default command prefix
    DefaultCommandPrefix = 'Test'
    # Functions to export from this module
    FunctionsToExport = '*'
    # Cmdlets to export from this module
    CmdletsToExport = '*'
    # Variables to export from this module
    VariablesToExport = '*'
    # Aliases to export from this module
    AliasesToExport = '*'
    # List of all modules packaged with this module
    ModuleList = @()
    # List of all files packaged with this module
    FileList = @()
    # Private data to pass to the module specified in ModuleToProcess
    PrivateData = ''
    <ModuleTest.output>
    PS C:\Scripts\PowerShell> Get-ChildItem -Path 'C:\Program Files\WindowsPowerShell\Modules' -Recurse<ret>
        Directory: C:\Program Files\WindowsPowerShell\Modules
    Mode                LastWriteTime     Length Name
    d----          3/5/2015   9:06 AM            ModuleTest
        Directory: C:\Program Files\WindowsPowerShell\Modules\ModuleTest
    Mode                LastWriteTime     Length Name
    -a---          3/5/2015   8:50 AM       2907 ModuleTest.psd1
    -a---          3/5/2015   9:01 AM        140 ModuleTest.psm1
    PS C:\Scripts\PowerShell> Get-Module -ListAvailable<ret>
        Directory: C:\Program Files\WindowsPowerShell\Modules
    ModuleType Version    Name                                ExportedCommands
    Script     1.0.0.0    ModuleTest                          {Get-Something, Set-Something}
    PS C:\Scripts\PowerShell> get-som<tab>
    PS C:\Scripts\PowerShell> Get-Something<ret>
    Get-Something : The term 'Get-Something' is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:1 char:1
    + Get-Something
    + ~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Get-Something:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-som<tab>
    PS C:\Scripts\PowerShell> ModuleTest\Get-Something<ret>
    ModuleTest\Get-Something : The term 'ModuleTest\Get-Something' is not recognized as the name of a cmdlet, function,
    script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
    correct and try again.
    At line:1 char:1
    + ModuleTest\Get-Something
    + ~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (ModuleTest\Get-Something:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-tes<tab>
    PS C:\Scripts\PowerShell> Get-TestSomething<ret>
    Get-Something Executed
    (New Session)
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-tes<tab><ret>
    get-tes : The term 'get-tes' is not recognized as the name of a cmdlet, function, script file, or operable program.
    Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:1 char:1
    + get-tes
    + ~~~~~~~
        + CategoryInfo          : ObjectNotFound: (get-tes:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    PS C:\Scripts\PowerShell> Import-Module ModuleTest<ret>
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-tes<tab><ret>
    PS C:\Scripts\PowerShell> Get-TestSomething
    Get-Something Executed
    (New Session)
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-tes<tab><ret>
    get-tes : The term 'get-tes' is not recognized as the name of a cmdlet, function, script file, or operable program.
    Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:1 char:1
    + get-tes
    + ~~~~~~~
        + CategoryInfo          : ObjectNotFound: (get-tes:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    PS C:\Scripts\PowerShell> Get-Command -Module ModuleTest<ret>
    CommandType     Name                                              
    ModuleName
    Function        Get-TestSomething                                 
    ModuleTest
    Function        Set-TestSomething                                 
    ModuleTest
    (No change in CommandAnalysis cache)
    PS C:\Scripts\PowerShell> get-tes<tab>
    PS C:\Scripts\PowerShell> Get-TestSomething<ret>
    Get-Something Executed
    PS C:\Scripts\PowerShell> moduletest\get<tab><ret>
    PS C:\Scripts\PowerShell> Get-TestSomething<ret>
    Get-Something Executed
    William Busby, PMP

    Hi William,
    yes, that's something you'll either have to do the hard way or live with admin confusion.
    If you're using Sapien's PowerShell Studio as an Editor (hint: Usually a great idea), you can very easily rename a function, even in a multi-file module project, by rightcklicking on the function-name and selecting "rename".
    Alternatively you can do a bulk rename with Powershell:
    Get all functions in your module (Load it and check exportedcommands)
    loop over each function-name
    calculate new name
    search your entire project for all references and replace them.
    Let me see ...
    function Rename-ModulePrefix
    [CmdletBinding()]
    Param (
    [Parameter(Position = 0, Mandatory = $true)]
    [string]
    $ModuleName,
    [Parameter(Position = 1, Mandatory = $true)]
    [string]
    $OldPrefix,
    [Parameter(Position = 2, Mandatory = $true)]
    [string]
    $NewPrefix,
    [Parameter(Position = 3)]
    [string]
    $Path
    # Catch all typos
    Import-Module $ModuleName -ErrorAction 'Stop'
    # Get root path if not manually passed
    if (-not $PSBoundParameters["Path"])
    $Path = (Get-Module $ModuleName).Path
    # Get module files
    $Files = Get-ChildItem -Path $path -Recurse -Include "*.ps1", "*.psm1", "*.psd1"
    # Iterate over each file
    foreach ($file in $Files)
    # Null variable in case you get an empty file somewhere and run this from Win 7
    $data = $null
    # Get Content of file
    $data = Get-Content $file
    # Replace strings
    foreach ($c in (Get-Module $ModuleName).ExportedCommands)
    $newName = $c.Name -replace $OldPrefix, $NewPrefix
    $data = $data | ForEach-Object { $_ -replace $c.Name, $newName }
    # Write back to file
    $data | Set-Content $file
    While I didn't proof it, in theory this should do it (Make a backup before running it :) ).
    Cheers,
    Fred
    There's no place like 127.0.0.1

  • SAP : ECC 6.0 Module : Production and MM Issue : Monthly and Yearly targets

    SAP : ECC 6.0
    Module : FICO
    Issue : Payment Mode and Type
    Domain : Chemicals
    How to Trap Bank Receipts / Bank Payments Mode of payment and doc no
    Ex : Any bank Receipt We need to enter the Mode of Receipt : Chq/ DD/ Order and Also need to enter the Instrument details
    In SAP standard F-28 form shows does not have the details to enter.
    What is the best approach to trap this in case of receipts and payments.

    Sreekanth
    Thanks for the reply
    If you want to maintain Cheque no., DD, etc.. You can enter those in assignment field or text field, While Document display you can see it in report.
    So this assignment filed can be used for All the DD-Chq details ?
    The information can queried on the Assignment field also ?

  • BlazeDS, multiple Module instances with Consumers issue

    I have an application that can load multiple instances of a module. The module has a consumer that connects to a destination and listens for messages pushed from a JMS topic. In order for me to be able to load and unload multiple instances of the module I'm appending a uid to the url of the swf. When the first instance of the module is loaded everything works as expected and the consumer successfully subscribes to the destination. However, if a second instance of the module is loaded the consumer fails to subscribe and I see the following error in the server log:
    [#|2010-10-28T15:05:33.666+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-1;|
    [BlazeDS]10/28/2010 [INFO] [Endpoint.General] Channel endpoint channel-streaming-amf received request.|#]
    [#|2010-10-28T15:05:33.671+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-1-in-streaming-mode;|
    [BlazeDS]10/28/2010 [WARN] [Endpoint.StreamingAMF] Endpoint with id 'channel-streaming-amf' received a duplicate streaming connection request from, FlexClient with id '4CA3967A-071C-AB24-D5B9-CAB9D20F14B5'. Faulting request.|#]
    [#|2010-10-28T15:05:33.671+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-1;|
    [BlazeDS]10/28/2010 [INFO] [Endpoint.FlexSession] Number of streaming clients for FlexSession with id '3275dcec0f5dc0c30a7381fa6044' is 0.|#]
    [#|2010-10-28T15:05:33.672+0100|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-1;|
    [BlazeDS]10/28/2010 [DEBUG] [Endpoint.StreamingAMF] Number of streaming clients for endpoint with id 'channel-streaming-amf' is 0.|#]
    [#|2010-10-28T15:05:33.673+0100|SEVERE|sun-appserver2.1|javax.enterprise.system.container. web|_ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-1;_RequestID=96f36b13-0da4-49ad-b788 -bc6d1413da3b;|StandardWrapperValve[MessageBrokerServlet]: PWC1406: Servlet.service() for servlet MessageBrokerServlet threw exception
    java.lang.IllegalStateException
    at org.apache.coyote.tomcat5.CoyoteResponseFacade.sendError(CoyoteResponseFacade.java:449)
    at flex.messaging.endpoints.BaseStreamingHTTPEndpoint.handleFlexClientStreamingOpenRequest(B aseStreamingHTTPEndpoint.java:732)
    at flex.messaging.endpoints.BaseStreamingHTTPEndpoint.serviceStreamingRequest(BaseStreamingH TTPEndpoint.java:1022)
    at flex.messaging.endpoints.BaseStreamingHTTPEndpoint.service(BaseStreamingHTTPEndpoint.java :430)
    at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:322)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.jav a:427)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:333)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncoding Filter.java:88)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76 )
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:246)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:313)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:28 7)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPi peline.java:98)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProces sorTask.java:666)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorT ask.java:597)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTas k.java:872)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultRead Task.java:341)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
    at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106 )
    |#]
    Can anyone explain to me what is happening here and suggest a solution please? I'm not sure if it's a BlazeDS issue or a Flex Module issue but I can't seem to find any references to this issue and the last 2 days have been spent trying to resolve this without any success.
    Any help appreciated.
    If I don't append the uid to the module url then the consumers subscribe as expected but then I'm unable to unload individual instances of the module as they all share the same url property.
    Thanks in advance.

    I have similar problem, but I don't understand your solution.
    Hypothetically, let’s say I use 2 separate sets of Consumer/Producer components in my flex app.
    There is no problem with connecting first set of Consumer/Producer to a particular channel.
    For second set of Consumer/Producer I create new ChannelSet  and new StreamingAMFChannel instances (but the channel has the same URL as the one used in first set, because I want to use the same channel).
    When I try to connect another set of Consumer/Producer to the same channel I get the error on BlazeDS: "... Endpoint with id 'streaming-amf' received a duplicate streaming connection request from, FlexClient with id ..."
    There is no such problem when I define additional channel in BlazeDS configuration an use this new channel with second set of Consumer/Producer components. This solution requires this additional channel so it’s not fully satisfying for me.
    Could you post some code samples of your solution or describe it in more detail?
    I will be grateful for any useful tips.

  • (IMP)application module and DB connection issue

    Hi,
    In my BC4J application, Application module is not releasing DB connection after the execution of the JSP page. It usually takes approx 3500-4000sec. to release it. On what parameters this time is dependent??
    I am using data-source to connect to DB. Application Module configurations parameters are set with default values.
    If i select "Disconnect Application Module Upon Release" from the configuration of Application module, it releases DBconnection at the end of http Request. Is it a proper solution to the issue ? any performance related issues with it?
    My JSP code's basic structure is
    try
    <jbo:ApplicationModule id="<AM ID>" definition="<Fully qualified AM classname>" releasemode="Stateless/stateFul" />
    // application code
    catch(Exception e)
    // Code to take necessary action if exception occurs
    finally
    <jbo:ReleasePageResources appid="<AM ID>" releasemode="Stateless/StateFul"/>
    Please guide me on this.
    Thanks in advance,
    Devang

    Hi john,
    Thanks for your reply... in other way can i restrict the number of connections created for the application module By selecting the Disconnect Application Module Upon Release in application module configuration.
    If i select that check box in Appmodule-->configurations->Edit->Pooling and Scalability means, while loading my screen number of connections are increased after completion of loading a screen immediatly connections also got reduced. if i select this check box whether it will give any other problems.
    Here am using the uishell dynamic tab after opening more number of tabs am getting connection pool error.not allways.. thats why am trying to restrict the no.of connections opening.
    please can you provide some info regarding this
    Reg,
    Brahma B

  • IMAP Sender channel, Content Conversion Module , target XSD structure issue

    Hi,
    I'm using the content conversion adapter module in my IMAP senderchannel , to transform a flat file into a IDOC ORDERS05 structure.
    I have some difficulties generating the right structure... how can I make a more deep structure ?
    My output is like this. All created segment is on the same level.
    <ORDERS05>
        <IDOC>
            <E1EDK01>
            <E1EDK03>
            <E1EDKA1>
            <E1EDK02>
            <E1EDKT1>
            <E1EDKT2>
            <E1EDKT2>
            <E1EDKT1>
            <E1EDKT2>
            <E1EDKT2>
        <IDOC>
    </ORDERS05>
    Here the E1EDKT2 should be a "level under" or "sub structure" to E1EDKT1, and not on the same level !
    The wanted result:
    <ORDERS05>
        <IDOC>
            <E1EDK01>
            <E1EDK03>
            <E1EDKA1>
            <E1EDK02>
            <E1EDKT1>
                <E1EDKT2>
                <E1EDKT2>
            <E1EDKT1>
                <E1EDKT2>
                <E1EDKT2>
        <IDOC>
    </ORDERS05>
    How can I solve this ????

    Hi,
    you can do it on adapter level too:
    but you cannot do it in standard content conversion I guess
    (if it has more then 2 levels)
    check this how you can do it:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/482aae19-0301-0010-3485-8efd618818d0
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • ASR-9001 - XR_434 - A9K-MPA-4x10GE - not fowarding packets

    In ASR-9001 with XR Version 434
    Connection between 2 devices, same platform, same XR Version (434) packets are not been foward.
    Change XR Version to 5.1.3 and the fowarding was sucesfull.
    Does anyone have the BUGs related to this and the SMUs that i can install to keep working with 434?
    Regards

    Noup, the ingress / egress counters keep in 0, some times ARP complete sometimes it dont.
    The router crash traing to do an OIR.
    RP/0/RSP0/CPU0:ASR-9001#admin show inst act summ
    Default Profile:
      SDRs:
        Owner
      Active Packages:
        disk0:asr9k-mini-px-4.3.4
        disk0:asr9k-k9sec-px-4.3.4
        disk0:asr9k-mcast-px-4.3.4
        disk0:asr9k-optic-px-4.3.4
        disk0:asr9k-fpd-px-4.3.4
        disk0:asr9k-doc-px-4.3.4
        disk0:asr9k-mpls-px-4.3.4
        disk0:asr9k-px-4.3.4.CSCul58246-1.0.0
        disk0:asr9k-px-4.3.4.CSCui94441-1.0.0
        disk0:asr9k-px-4.3.4.CSCug75299-1.0.0
        disk0:asr9k-px-4.3.4.CSCuj01579-1.0.0
        disk0:asr9k-px-4.3.4.CSCum51429-1.0.0

  • VSM module: A9K-VSM-500 CGN / IPv6 Performance

    Hi,
    I was wondering if there is more information regarding the VSM performance numbers similar to what is listed on the ISM datasheet for CGN and IPv6 migration features.
    http://www.cisco.com/c/en/us/products/collateral/routers/asr-9000-series-aggregation-services-routers/data_sheet_c78-663164.html
    ISM:
    ● Maximum 20 million simultaneous sessions for CGN and DS-Lite, and 15 million simultaneous sessions for NAT64.
    ● Maximum 1 million sessions set up per second
    VSM:
    Appreciate your response.
    thanks
    prashanth

    Thanks for the update!   Do you think the CGN numbers will be posted soon?
    regards
    -P

  • LC/0/0/CPU0:Dec 19 00:48:55 : lda_server[64]: %L2-SPA-5-OIR_ERROR : SPA (0): A SPA hardware or software error occurred on ASR9001

    Dear all,
    i got the problem, suddently my customer router generating that log :
    LC/0/0/CPU0:Dec 19 00:48:55 : lda_server[64]: %L2-SPA-5-OIR_ERROR : SPA (0): A SPA hardware or software error occurred,
    is it the line card is error, and need to be rma ?
    or is there any wrong configuration, or need to be upgraded with FPD.
    the IOS XR version is 4.2.3
    Thanks,
    Budi L

    Hi Alexei,
    here's the log and show hw-module fpd.
    LC/0/0/CPU0:Dec 19 00:48:55 : lda_server[64]: %L2-SPA-5-OIR_ERROR : SPA (0): A SPA hardware or software error occurred, please contact technical support  
    RP/0/RSP0/CPU0:Dec 19 00:48:55 : invmgr[254]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: FAILED
    LC/0/0/CPU0:Dec 19 00:48:56 : vic_0[363]: %L2-ETHERNET-6-MTU_NEAR_HW_LIMIT : The configured MTU of 9216 on GigabitEthernet0_0_0_14 is close to the H/W limit, and hence large 802.1Q or QinQ frames may be dropped as oversized frames
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/19, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/19, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/18, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/18, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/17, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/17, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/14, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/14, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/13, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/13, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/12, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/12, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/11, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/11, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/10, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/9, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/9, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/8, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/8, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/7, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:56 : ifmgr[201]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/7, changed state to Down
    LC/0/0/CPU0:Dec 19 00:48:58 : 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 Standard to Customer Facing
    LC/0/0/CPU0:Dec 19 00:48:58 : 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 Standard to Not Interested
    RP/0/RSP0/CPU0:Dec 19 00:48:58 : invmgr[254]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
    RP/0/RSP0/CPU0:Dec 19 00:49:02 : invmgr[254]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: DISABLED
    RP/0/RSP0/CPU0:CG-PE-05(admin)#show hw-module fpd location all
    Wed Dec 19 05:25:10.591 WIB
    ===================================== ==========================================
                                          Existing Field Programmable Devices
                                          ==========================================
                                            HW                       Current SW Upg/
    Location     Card Type                Version Type Subtype Inst   Version   Dng?
    ============ ======================== ======= ==== ======= ==== =========== ====
    0/RSP0/CPU0  ASR9001-RP                 1.0   lc   fpga2   0       1.12     No
                                                  lc   cbc     0      22.114    No
                                                  lc   rommon  0       1.29     No
    0/RSP0/CPU0  ASR-9001-FAN               1.0   lc   cbc     2      24.114    No
    0/0/CPU0     ASR9001-LC                 1.0   lc   cbc     0      23.114    No
                                                  lc   fpga2   0       1.15     No
                                                  lc   fpga4   0       2.06     No
                                                  lc   rommon  0       1.30     No
    0/0/0        A9K-MPA-20X1GE             1.0   spa  fpga3   0       0.08     No
    Thanks,
    Budi L

  • 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?

  • ASR 9010 licensing question

    Hi,
    any good cisco reference for installing licenses for ASR 9010 router?
    we need to "move" license to oper state
    (admin)#sho license
    Mon May 28 15:44:08.686 UTC
    FeatureID: A9K-AIP-LIC-B (Slot based, Permanent) 
      Total licenses 2
      Available for use         2
      Allocated to location     0
      Active                    0
      Store name             Permanent
      Store index               1
        Pool: Owner
          Total licenses in pool: 2
          Status: Available     2    Operational:    0
    thanks for help
    miro

    I have the same problem on asr 9001. A can't activate license regardless of the location.
    (admin)#sh license
    FeatureID: A9K-9001-AIP-LIC (Slot based, Permanent)
      Total licenses 1
      Available for use         1
      Allocated to location     0
      Active                    0
      Store name             Permanent
      Store index               1
        Pool: Owner
          Total licenses in pool: 1
          Status: Available     1    Operational:    0
    license A9K-9001-AIP-LIC
     location 0/RSP0/CPU0
    (admin)#sh platform
    Wed Oct  1 14:45:47.427 CEST
    Node            Type                      State            Config State
    0/RSP0/CPU0     ASR9001-RP(Active)        IOS XR RUN       PWR,NSHUT,MON
    0/FT0/SP            ASR-9001-FAN-V2           READY
    0/0/CPU0            ASR9001-LC                IOS XR RUN       PWR,NSHUT,MON
    0/0/0                  A9K-MPA-4X10GE            OK               PWR,NSHUT,MON
    0/0/1                 A9K-MPA-20X1GE            OK               PWR,NSHUT,MON
    0/PM0/SP        A9K-750W-AC               READY            PWR,NSHUT,MON
    0/PM1/SP        A9K-750W-AC               FAILED           PWR,NSHUT,MON
    Any suggestion?
    Regards,
    Nenad

  • ASR9k - ACL Counters

    Hi All,
    Apologies if this has already been asked but I want to know if there is a way to view access-list counters when it is used in a class-map and the policy-map is applied to an interface.
    I tried the following command but I get "unrecognized location".
    RP/0/RSP0/CPU0:R1# show access-lists ipv4 ACL-NETWORK-CONTROL-00001 hardware egress location 0/0/1
    Tue Jul  1 01:24:20.077 UTC
    Unrecognized location
    RP/0/RSP0/CPU0:R1# show platform
    Tue Jul  1 01:32:32.358 UTC
    Node            Type                      State            Config State
    0/RSP0/CPU0     ASR9001-RP(Active)        IOS XR RUN       PWR,NSHUT,MON
    0/0/CPU0        ASR9001-LC                IOS XR RUN       PWR,NSHUT,MON
    0/0/0           A9K-MPA-20X1GE            OK               PWR,NSHUT,MON
    0/0/1           A9K-MPA-4X10GE            OK               PWR,NSHUT,MON
    IOS-XR version 4.2.3 on ASR9001.
    Regards,
    Amit.

    Hi Amit,
    Since you are using access-list in a  service policy applied to an interface.
    Are you not seeing matches when you do "show policy-map interface g0/0/1/x in/out ?
    In order to see the "show access-list" output you have to apply the acl in/out to the interface.
    Best Regards,
    Bheem

Maybe you are looking for

  • Bridge CS4 won't open .NEF file in camera raw

    It says because photoshop CS4 does not recognize this type of file. I've opened plenty of Nikon .NEF files in Bridge. The difference is this is a D90 file and I've been getting D80 files. Is there a patch for newer camera models?

  • Excise Duty Value not flow from J1IJ to VF01

    Hi SAP Expert, I am facing the problem in Invoice to Customer(from Depot). Excise Values are not flowing from J1IJ for pricing procedure JINDEP. I maintained Alt Cal type as 356 in Pricing procedure JINDEP for Excise condition types JEXP. But it is s

  • Photos won't update

    When I upgraded to the iCloud photo library everything worked fine, and everything continues to work perfectly on my iPhone and iPad, however when I log into iCloud.com and go to the Photos tab, only a 465 photos and videos are there, and the 'updati

  • What does a zone in ORS map to on MWM ?

    Guys: I am using ORS right now and I know what a zone means in their terminology. Since zone is a common concept used by both MWM and ORS what data elements on the MWM side represent a zone ?

  • COM in Java

    Hi all, I'm wondering if it is possible to load a COM dll developed in Visual C++ into a Java program and use the method implemented on it. If yes, can you give me the link to the right docs? Thanx in advance, Fabio