[j-nsp] CHASSISD_SHUTDOWN_NOTICE: Shutdown reason: TFEB connection lost
Samol
molasian at gmail.com
Fri Dec 12 02:38:51 EST 2014
Just update on this case : now i got another log message different from the
previous one, but caused the same problem is "TFEB connection lost" below
is the log :
Dec 12 12:09:15 TSSYDRTBDR01 tfeb0 DDR: detected 1 SDRAM single-bit error
Dec 12 12:09:15 TSSYDRTBDR01 tfeb0 DDR: last error at addr 0x5d8536a8, bad
data/mask 0xbad80ffebadc0ffe/0x0004000000000000 bad ecc/mask=0xa5/0x00
Dec 12 15:31:16 TSSYDRTBDR01 tfeb0 DDR: detected 1 SDRAM single-bit error
Dec 12 15:31:16 TSSYDRTBDR01 tfeb0 DDR: last error at addr 0x5d8527d0, bad
data/mask 0xbad40ffebadc0ffe/0x0008000000000000 bad ecc/mask=0xa5/0x00
Dec 12 15:33:20 TSSYDRTBDR01 tfeb0 DDR: detected 1 SDRAM single-bit error
Dec 12 15:33:20 TSSYDRTBDR01 tfeb0 DDR: last error at addr 0x5d8736a8, bad
data/mask 0xbad80ffebadc0ffe/0x0004000000000000 bad ecc/mask=0xa5/0x00
Dec 12 17:54:09 TSSYDRTBDR01 chassisd[1219]: CHASSISD_SHUTDOWN_NOTICE:
Shutdown reason: TFEB connection lost
*Dec 12 17:54:09 rcv: ch_ipc_dispatch() null ipc read for args 0x1f374c0
pipe 0x1f34f00, fru TFEB 0 errno 60*
*Dec 12 17:54:09 -- TFEB 0, last request 0, state Online*
*Dec 12 17:54:09 CHASSISD_SHUTDOWN_NOTICE: Shutdown reason: TFEB connection
lost*
*Dec 12 17:54:12 TFEB 0 added*
*Dec 12 17:54:12 Bring TFEB 0 out of reset*
Regards,
2014-12-10 9:20 GMT+07:00 Samol <molasian at gmail.com>:
>
> Thanks Tyler,
>
> MIC on device is :
>
> MIC 0 BUILTIN BUILTIN 4x 10GE XFP
> MIC 0 REV 05 750-032826 YH2273 48x 1GE(LAN) RJ45
>
> Probably i need to upgrade to 12.x ?
>
> Regards,
>
> 2014-12-09 12:47 GMT+07:00 Tyler Christiansen <
> tyler.christiansen at t.adap.tv>:
>
>> What MICs do you have? I ran into a bug that killed the TFEB connection
>> with the 20x1G MIC. I don't recall the PR or affected versions, but it was
>> one of the 11.x releases.
>>
>> Sorry I couldn't be more help.
>>
>> On Mon, Dec 8, 2014 at 6:25 PM, Samol <molasian at gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We're using MX80 running 11.4R6.6 version. We got the the below messages
>>> before our device went down. We had this problem few weeks back, and I
>>> found this link "
>>> https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR816253
>>> "
>>> mentioning about broadcast storm from fxp0 management interface. i did
>>> the
>>> upgrade to current version as per recommendation. But I didn't solve the
>>> problem as it happened again last night. Did anyone meet this problem and
>>> any recommendation to solve this ? I haven't tried to reset the TFEB yet.
>>>
>>> One more notice is that, before the " *CHASSISD_SHUTDOWN_NOTICE: Shutdown
>>> reason: TFEB connection lost*" message, we got LACP related message
>>>
>>> happened. Is there known problem with LACP to cause TFEF connection lost
>>> ?
>>>
>>>
>>>
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/0/1
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/0/1: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/0/2
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: ae_bundlestate_ifd_change: bundle
>>> ae3: bundle IFD minimum links not met 0 < 1
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/0/2: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACP_INTF_DOWN: ae3: Interface
>>> marked down due to lacp timeout on member ge-1/0/2
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/0/3
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/0/3: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/0/4
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: ae_bundlestate_ifd_change: bundle
>>> ae4: bundle IFD minimum links not met 0 < 1
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/0/4: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACP_INTF_DOWN: ae4: Interface
>>> marked down due to lacp timeout on member ge-1/0/4
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/3/0
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/3/0: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/3/1
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: ae_bundlestate_ifd_change: bundle
>>> ae1: bundle IFD minimum links not met 0 < 1
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/3/1: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACP_INTF_DOWN: ae1: Interface
>>> marked down due to lacp timeout on member ge-1/3/1
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/3/2
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/3/2: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: KERN_LACP_INTF_STATE_CHANGE:
>>> lacp_update_state_userspace: new state is 0 cifd ge-1/3/3
>>> Dec 9 04:08:29 TSSYDRTBDR01 /kernel: ae_bundlestate_ifd_change: bundle
>>> ae2: bundle IFD minimum links not met 0 < 1
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACPD_TIMEOUT: ge-1/3/3: lacp
>>> current while timer expired current Receive State: CURRENT
>>> Dec 9 04:08:29 TSSYDRTBDR01 lacpd[1241]: LACP_INTF_DOWN: ae2: Interface
>>> marked down due to lacp timeout on member ge-1/3/3
>>> Dec 9 04:08:30 TSSYDRTBDR01 rpd[1318]: RPD_OSPF_NBRDOWN: OSPF neighbor
>>> 103.237.92.34 (realm ospf-v2 irb.21 area 0.0.0.0) state changed from Full
>>> to Down due to KillNbr (event reason: interface went down)
>>> Dec 9 04:08:30 TSSYDRTBDR01 rpd[1318]: RPD_OSPF_NBRDOWN: OSPF neighbor
>>> 103.237.92.114 (realm ospf-v2 irb.25 area 0.0.0.0) state changed from
>>> Full
>>> to Down due to KillNbr (event reason: interface went down)
>>> *Dec 9 04:08:33 TSSYDRTBDR01 chassisd[1225]: CHASSISD_SHUTDOWN_NOTICE:
>>> Shutdown reason: TFEB connection lost*
>>> Dec 9 04:08:33 TSSYDRTBDR01 chassisd[1225]: CHASSISD_IFDEV_DETACH_FPC:
>>> ifdev_detach_fpc(0)
>>> Dec 9 04:08:33 TSSYDRTBDR01 chassisd[1225]: CHASSISD_SNMP_TRAP10: SNMP
>>> trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 1,
>>> jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC @ 0/*/*, jnxFruType 3,
>>> jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0,
>>> jnxFruLastPowerOn 0)
>>> Dec 9 04:08:33 TSSYDRTBDR01 eventd: sendto: Network is down
>>> Dec 9 04:08:33 TSSYDRTBDR01 chassisd[1225]: CHASSISD_IFDEV_DETACH_FPC:
>>> ifdev_detach_fpc(1)
>>> Dec 9 04:08:33 TSSYDRTBDR01 /kernel: pfe_send_failed(index 0, type 17),
>>> err=32
>>>
>>> Regards,
>>> --
>>> Samol Khoeurn
>>> (855) 077 55 64 02 / (855) 067 41 88 66
>>> Network Engineer
>>> Cisco: CCNA/CCNP SP/CCIP/
>>> Juniper: JNCIA/JNCIS-ENT,SP,SEC/JNCIP-ENT
>>> www.linkedin.com/in/samolkhoeurn
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>
>
> --
> Samol Khoeurn
> (855) 077 55 64 02 / (855) 067 41 88 66
> Network Engineer
> Cisco: CCNA/CCNP SP/CCIP/
> Juniper: JNCIA/JNCIS-ENT,SP,SEC/JNCIP-ENT
> www.linkedin.com/in/samolkhoeurn
>
--
Samol Khoeurn
(855) 077 55 64 02 / (855) 067 41 88 66
Network Engineer
Cisco: CCNA/CCNP SP/CCIP/
Juniper: JNCIA/JNCIS-ENT,SP,SEC/JNCIP-ENT
www.linkedin.com/in/samolkhoeurn
More information about the juniper-nsp
mailing list