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?

Similar Messages

  • Authorisations for users receiving Alerts on Interface Failure

    Dear All,
    I have configured alerts to send out mails to relevant users in case of Interface failure.
    Now I need to know that what strategy is followed in Alerting. As in, how many user groups should be created and what all authirisations should be given to these users.
    As per my understanding, there should be 2 user groups to receive alerts:
    1) Business Users
    2) PI Support team.
    Please tell me if the above approach is fine and what authorisations should be given to each in both ABAP and Java side.
    thanks,
    Piyush

    Hi Piyush,
    If you are to send alerts to a specific user group through your alert category, the way could be to create a user account with basic authentications for PI monitoring and add this user as a fixed receipient for the Alert Category in ALRTCATDEF. Then assign a group mail id (add the required users to this group mail id in you mail server) to this user in SU01. This way the alert triggered against this particular alert category will be forwarded to this group mail id.
    Ideally both the adapter engine and integration engine alerts are forwarded to Support team, but for the business users only the Integration Engine alerts are meaningful (mostly mapping conditional failures). So it is good practice to create two separate alert categories for adapter engine and integration engine and then add fixed receipients accordingly.
    The other approach is to configure receipients via user role (create Z roles) for each alert category (ALRTCATDEF) and then assign the role to the specific users in the PI system.
    The smart approach is to cofigure subscription authorizations in ALRTCATDEF and then individual users can subscribe to alert categories as per their need from Alert Inbox in RWB (there is an option for alert subscription) and can unsubscribe when they desire.
    Regards,
    Suddhasatta

  • ODI 11.1.1.5 interface failure when loading to Essbase 11.1.2.1

    I just upgraded my ODI env from ODI 11.1.1.3 to ODI 11.1.1.5 and I get the weird java error. All my oracle interfaces are working great but when I try to load essbase interface it fails. I have staging area as Sunopsis_Memory_Engine. Even tried Memory Engine and Oracle_Staging schema(Which is my source schema). I am using IKM SQL to Hyperion (DATA) KM. Pls let me know if anyone faced this issue before.
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (most recent call last):
    File "<string>", line 20, in <module>
         at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
         at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
         at org.hsqldb.jdbc.JDBCStatement.executeQuery(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
    java.sql.SQLException: java.sql.SQLException: incompatible data type in operation
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2457)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
         at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         at java.lang.Thread.run(Thread.java:662)

    Have a read of http://john-goodwin.blogspot.com/2011/09/odi-series-issues-with-11115-and.html as the issue you are experiencing maybe related.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Cisco Prime 2.0 - Interface failure

    Last week I setup PI 2.0 on an ESX server using the OVA template. I can access the PI through the WebGUI without issue.
    Because of our network topology, I need to use 3 interfaces to properly manage our environment. Through vCenter, I added 2 additional interfaces, and rebooted the server.  All three interfaces show up properly in the CLI as well as in the GUI. I configured all three itnerfaces with the appripriate IP addresses, and configured a single default gateway out interface Gi 0.
    Gi 1 connects to our TACACs server as well as our swith infrastructure. Gi 2 connects to our WLAN infrastrcuture, and will be used to manage WISM2s (and the WLAN controllers in the new 4500 SUP-8 when the software gets released).
    I managed to setup TACACS to our old ACS 4.2 server thgough Gi 1, as well as add a couple of switches to PI.
    I could not however add the WISM2 through int Gi 2 (PI and controller in the same subnet). I could ping the controller from the PI, and viceversa, but could not poll the device, not access it via SSH.
     After hours of troubleshooting and getting now where, I swapped interface Gi 1 and Gi 2, and reconfigured the IP addresses appropriatly, i.e. Gi 1 is now conencted to the WLAN infrastrcture, and Gi 2 connected to the switch infrastrcture.
    After the change I could no longer access the PI using TACACS, nor could I update or add any devices connected through Gi 2.  They still show as reachable (as I beleive the reachability is ICMP-based), but that's it. I had no issues connecting the WISM2 to the PI once the WLAN mgmt interface was moved to Gi 1.
    Does anyone know of any restrictions in PI regarding the number of supported interfaces? I search bug tracker and the documentaiton, and could nto find anything related.
    My only conclusion is that PI 2.0 does not properly support more than 2 interfaces.
    Has anyone else run into this "feature"? Any advice would be appreciated.

    Did you add "ip route" statements for the additional NICs?

  • Eno1 interface failure at boot

    Hi all,
    EDIT: I've now spent most of the day on this, but unfortunately haven't progressed at all. I've gone through the debugging steps suggested in the Networking Configuration article. I've also been reading through lots of other posts about networking problems. It sounds like it *might* be a race condition brought on by the kernel and udev having different names for the device? So the kernel starts doing stuff and then udev changes it's name, or something like that. Unfortunately, I still don't have any idea how to push this forward. Any advice, even just regarding where to look next, would be super helpful.
    I've run Arch as my home workstation for a couple of years now, but I've recently installed it on a new machine and I'm out of my depth with the new networking tools and conventions. I'm hoping you can point me to the best place to look for debug information.
    The recently created machine was working well for a couple of weeks, but a recent update has caused it to lose the eno1 device.
    # ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu ...
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    (by the way, because the machine has no connection to the outside world, I'm typing all this output by hand, so I'm truncating much of it)
    # lspci -v | grep -A 9 Ethernet
    00:19.0 Ethernet controller: Intel Corporaion 82579V Gigabit Network Connection (rev 06)
    Subystem: ASUSTek Computer Inc. P8P67 Deluxe Motherboard
    Flags: bus master, fast devsel, latency 0, IRQ15
    ... (some stuff about it's ports and memory)
    Note: I know that previously lspci was able to also tell me the kernel driver used for the ethernet device. It was e1000e. Now, for some reason, that information is not longer listed there.
    # dmesg | grep e1000e
    That kernel driver is not automatically loaded. I did try modprobe e1000e, but that didn't seem to make any difference. There's probably something else I'd have to do after that, but I don't know what.
    # cat /etc/systemd/system/multi-user.target.wants/[email protected]
    [Unit]
    Description=dhcpcd on %I
    Wants=network.target
    Before=network.target
    BindsTo=sys-subsystem-net-devices-%i.device
    After=system-subsystem-net-devices-%i.device
    [Service]
    Type=forking
    PIDFile=/run/dhcpcd-%I.pid
    ExecStart=/usr/bin/dhcpcd -q -w %I
    ExecStop=/usr/bin/dhcpcd -x %I
    [Install]
    WantedBy=multi-use.target
    Note: I did not create this file. I'm pretty sure it was created for me when I ran systmctl enable [email protected] (or something like that) during initial installation.
    # journalctl -x -u network
    nothing here. Grep-ing for eno1 shows something like: (it's a lot of text, so I'm paraphrasing)
    # journalctl -x | grep eno1
    Expecting device sys-subsystem-net-devices-eno1.device...
    Job sys-subsystem-net-devices-eno1.device/start timed out.
    Timed out waiting for device sys-subsystem-net-devices-eno1.device
    Subject: Unit sys-subsystem-net-devices-eno1.device has failed.
    Dependency failed for dhcpcd on eno1.
    Subject: Unit [email protected] has failed
    As I was debugging (using this post, and this post for ideas) I found a log saying "renaming eth0 to eno1", but I can't figure out what command or file displayed that information. Note that, I as far as I know, the wired network device has been called eno1 since the initial installation. I've never configured it to be called eth0. This document seems to suggest that the kernel uses eth0 to name the device before it turns things over to udev.
    Unfortunately, other than searching the machine for useful error messages, I haven't been able to progress much farther than that. I'm at a loss as to what to do next.
    The very first thing I'd *like* to do is manually get the interface working, so that I can connect to this board via that machine. Being able to copy/paste would save me a ton of time in future posts.
    Any suggestions?
    Last edited by aarondev (2014-04-13 22:51:30)

    solved! if I change host in sabnzbd from localhost (the default) to 0.0.0.0 it works
    not sure why? I'm a new user so have a lot to learn it seems =/

  • Check for transaction interface failure from POS to POSDM

    Dear experts,
    Would like to see if in your experience, you have encountered any report or functions that allow users in POSDM to check if sales transaction from a particular store has failed to do the inbound interface from POS to POSDM?
    I am personally not aware of this, so if there is no such report based on your knowledge, would you have any workaround solution that you can suggest me?
    Thanks so much.
    Dominic

    Link for Duplication Check process: http://scn.sap.com/docs/DOC-47529
    Link for info on POS DM: http://help.sap.com/saphelp_posdm/helpdata/en/4e/9617be3aec6ea9e10000000a42189b/content.htm
    Hi Dominic,
    There are certain validation checks we have in POS DM to validate the transaction data when it comes to POS DM. These validations are like Master Data check, Duplication check, Sequence check for missing transactions and so on.
    You can find more about the same in the given link. I don't know my editor is behaving strangely so the link is on the top. I am not able to paste the links in editor links are coming on top. Might be my IE issue.
    Regarding implementing such validation in POSDM for incoming transaction you can refer my posted document for Duplication check in POSDM. From this document you will get an idea about how to implement the validation check.
    Let me know if you need any other information.
    Regards,
    Amit

  • NTP source interface failure

    NTP always uses the outbound interface, regardless of configuration of source interface.
    Managed to get it to work by combining the source interface on the server command line. So instead of:
    ntp server xxxxx
    ntp source Loopback0
    we used the command
    ntp server xxxx source Loopback0
    Be sure to eliminate the other ntp server and source commands.

    If you're referring to applets, the command is "source-interface" as an argument to the mail action:
    action X mail to "[email protected]" from "[email protected]" server 10.1.1.1 subject "Test" body "this is a test" source-interface Gi0/0

  • PCI-MXI interface failure

    I have two PCI-MXI-2 interface cards 1 and 2 and two machines A B following are the results:
    A2 works
    A1 resman hangs
    B2 works
    B1 resman hangs
    I think this implicates interface card 1. This card is about 15 months old. The serial number may be D32483. How can I get a working card?

    Dear Doman,
    Before you have this card repaired or replaced, I recommend you try to restore the EEPROM with the factory settings. I have attached a tutorial that will explain setting the EEPROM.
    If restoring the EEPROM does not solve your problem, then you will need to send this board into National Instruments for repair. Please visit www.ni.com/support to generate a phone support request. You can then call in and speak with an Applications Engineer who can RMA your board.
    Regards,
    David Shatila
    Applications Engineer
    National Instruments
    www.ni.com/support
    1-866-ASK-MY-NI
    Attachments:
    Restoring_EEPROM_Configuration_Settings_on_a_VXI-VME_Controller_-_MAX.doc ‏72 KB

  • ASR 9001 management interfaces

    I need to configure my management interfaces for out-of-band. Do I need to put them in a vrf? The config guide doesn't mention it but is very cryptic. It also says to put a static route (BUT IT'S NOT UNDER A VRF???)  That could potentially break routing?
    Any advice would be helpful.
    Thanks,
    Vin

    no special configuration is needed, and you can put the mgmt ports in a vrf, but its not a must. Forwarding between Mgmt port and Linecard Interface ports is disabled by default. From a routing percpetive treat it like any interface.
    Eddie.

  • Weird artifacting/interface failure on screen

    I've had my AppleTV for two months -- no complaints. But now if I'm playing an album and decide to "go up" from the album view, the prior screen REMAINS on the screen. Or, if I'm playing a show on HuluPlus and decide to leave to "main menu", the episode will continue to play behind the AppleTV main screen. Weird! It happens regularly, but not all the time.
    The only change I've made recently is to move from Ethernet hook-up to Wifi of the AppleTV. It's the only change I can think of.

    Try the following steps, check whether things are working after each step where appropriate, before trying the next.
        1.    Restart the Apple TV (Settings > General > Restart).
        2.    Restart the Apple TV by removing ALL the cables for 30 seconds.
        3.    Restart your router. (Also try removing it’s power cord for at least 30 seconds)
        4.    Reset the Apple TV (Settings > General > Reset > Reset all settings)
        5.    Restore the Apple TV (Settings > General > Reset > Restore)

  • Interface failure with the error : Transfer to Process Engine

    Hello All,
    We are receiving 2 messages for one SiteMaster idoc triggerred from SAP ECC. Its a BPE scenario.
    1. We are not sure why we are getting 2 entries in SXMB_MONI.
    2. 1 of the message status shows Successful Flag but its queue id : XBQO$PE_WS95000004 is in failed state in SMQ2. We have tried Execute LUW and its not working, hence we have given Save  LUW and saved it SMQ3.
    3. The second entry shows the status as 'Transfer to Process Engine' with a proper queue id.
    Attached the screenshots. Kindly check. Thanks in advance.
    Regards,
    KarthiSP

    ANy how if you want to delete those BPM runtime instance you can do so by deleting the logical instance of the BPM instance
    go to SXMB_MONI and click on PE which got stuck and it will take you PE engine go to list technical options and chose workflow log option and then chose delete logical instance option
    /people/michal.krawczyk2/blog/2009/03/18/xipi-bpe-admin--logical-deletion-of-a-process-instance
    Rajesh

  • Difference between PI/XI interface and ABAP interface

    Hello Experts,
    We are in the process of identifying interfaces for our current client. I am looking for some documentation or any specific information that will help me to differentiate between SAP PI interface and ABAP Interface. Basically I want to know what are the advantages of PI interface over ABAP interface. What is better? and why?
    Any information would be of great help. Thanks.

    PI (versus point to point ABAP) advantages are:
    1)     Centralized control over data security
    2)     More effective (centralized) interface failure monitoring and resolution
    3)     Elimination of redundant development and maintenance costs

  • CSS- traffic orignating from real server + Virtual interface

    Hi all,
    I am designing a solution at the moment, in which I shall have 2 servers behind a pair of CSS & their default gateway will be the Virtual Interface ip address of CSS.
    Is there any problem forseen in traffic getting initiated from the server to any other subnet in the network and the return traffic to the server.
    Servers shall connect to a pair of 3750 being used as L2 in stack .
    The Stacked 3750's shall be placed below the CSS pair & the CSS pair shall further connects to a single 6509 upstream....
    Each 3750-L2 connects single port to each CSS
    (3750-L2-1 to CSS1 &
    3750-L2-2 to CSS 2)
    Both CSS connect to the SINGLE 6509 on diff blades. for better redundency.
    The CSS shall not be connected to each other directly.
    Both 3750-L2 connect to each other as well
    IIS-1---L2_Sw1---CSS1---6509---Othr_Subent
    IIS-1---L2_Sw2---CSS2---6509---Othr_Subent
    Note: I shall have VIP/Virtual Interface config on my CSS's.
    Appreciate validation and recomendations on this design.
    Many Thanks,
    gagan

    Hi Gilles,
    Many thanks for the confirmation.
    Request verification on the below as well~
    1. With the above scenario; I do not require any group (NAT) configuration, either for my servers initiating traffic for going out or for clients hitting the VIP to reach servers. The client & server shall be in diff VLAN?s of course.
    2. With VIP & Virtual Interface configuration & couple of server VLAN's below on server side, I should be able to use both the gigabit interfaces on the 11503 to connect up and down stream as TRUNK. I mean to ask Virtual intf. & VIP has no problems working on the same TRUNK interface?
    3. I understand that Fate sharing and critical service helps full failover (client & server side).
    As an upstream router or L3 switch fails or the upstream connecting gigabit interface on CSS fails, the failover happens.
    Will the same be applicable to downstream L2 switch & CSS interface failure? If any of these on the downstream fails will the CSS failover to the standby unit.
    I think this above should work, just need confirmation coz I have not done this before.
    Thanks a lot again,
    Gagan

  • Redundacy Not happening after interface goes down.

    Dear All,
    I have the set up which I have attached. To brief, I have 2 CSS 11501 in two different locations connected each other via fibre and running redundnacy protocol on the link as heartbeat.
    The problem I am facing is if the interface through which the services are running fails the redundancy is not happening the master remains the master and the standby is standby and we have a services unavailable.
    the configuration is given below
    CSS_ACTIVE# sh run
    !Generated on 03/07/2010 22:26:21
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      username admin des-password lcof1eugqece2afd superuser
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      ip redundancy master
      app
      app session 10.90.1.2
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDBY PORT 9"
      bridge vlan 23
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.20 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.1 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_ACTIVE#  
    CSS_STANDBY# sh run
    !Generated on 03/07/2010 22:31:42
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      ip redundancy
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      app
      app session 10.90.1.1
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      description "TRUNK "
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDY PORT 9"
      bridge vlan 23
    interface Ethernet-Mgmt
      phy 10Mbits-FD
      admin-shutdown
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.21 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.2 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_STANDBY#
    If the interface e1 fails on active the redundancy is not shifting to standby.

    You have setup box-to-box redundancy.
    This mechanism is very basic and only detects a box failure.  So, as long as the master can send heartbeat through the 'redundancy protocol' interface it will stay master.
    You should use interface/vip redundancy.
    A little bit more complex to configure but much more robust and with more features including interface failure detection.
    http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20_v8.10/configuration/redundancy/guide/VIPRedun.html
    Gilles.

  • Interfacing error notified via email

    Hi Gurus.
    My client is going to implement interfacing between Mercia ( Third party software) to SAP for some functionality.
    The requirement is
    The business will need to be notified via email or SAP Idoc when an error has occurred with Mercia or SAP that prevents users accessing the Mercia database, weekly schedule run, month end procedures, and any other interface failure. (depending upon the error should determine which method either email or Idoc)
    How can user will recieved mail If interfacing program having some error.

    Hi,
    try using IDOCMSG business object.
    Create a custom event to trigger to workflow. Find out some user exit or BAdi to trigger the workflow.
    Then use a send mail step and send a notification to the desired user.
    Regards,
    Raj

Maybe you are looking for

  • Problem between windows and unix

    i got a class and a text file whith characters like '�' in it. when i launch my class on windows there'no problem. The file is read and the data are record in Oracle correctly (whith the accents). When i copy the data and the class on unix i got '?'

  • Cancel download method when the user cancel the download file

    I have a method that download a file ("downloadLog_action()")when the user click over the comandlink component and the dialog box is opening to save the file, but how to know that the user canceled the download file to cancel all accions. This is the

  • Clarification on how Edge works

    Hello - just want to confirm how the Edge program works before getting new iPhone 6's for the family. We have 5 lines and only 1 is a smartphone (iPhone 4 on the unlimited plan). We will be dropping 1 of the 5 line completely because it is not being

  • This is urgent please help!  long running job in sm37 but not in sm66

    Hi, Can someone please help for an explanation as to why if you call sm37, you can see that the job is long running (example about 70,000 sec), but when you look at the PID where the job is running in sm66 it does not show 70,000 sec but only around

  • IDOC ABAP-PI Port Function Module not called

    HI all, i am using a scenario where i am sending (outbound) idocs via abap proxy to PI. I have assigned the function module to the abap-pi port. when i am trying to send a test idoc via we19, i get the message "IDoc '0000000000198029' transferred to