[j-nsp] Ex8208 TRAP
Rohit Ghodke
rohit.nw at gmail.com
Mon May 21 05:26:45 EDT 2018
a process on the line card probably crashed , disconnecting it from the
chassis. Or less likely a hardware issue. Definitely open a case with jtac
for this
On Sun., 20 May 2018, 15:45 Mohammed Abu Sultan, <abusulttan at msn.com> wrote:
> Hi All,
>
>
> I have a strange issue in my Ex 8208 Core switch that a suddenly trap
> causing a network down when I check the logs I found
>
>
> Core-SW-8208> show log messages
>
> May 19 20:42:52 Core-SW-8208 chassisd[1338]: CHASSISD_SNMP_TRAP10: SNMP
> trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 1,
> jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC: 8x 10GE SFP+ @ 0/0/*,
> jnxFruType 11, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff
> 20675705, jnxFruLastPowerOn 20686688)
> May 19 20:42:53 Core-SW-8208 /kernel: pic_listener_connect: conn
> established: mgmt addr=0x81000010,
> May 19 20:42:52 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/0
> May 19 20:42:53 Core-SW-8208 /kernel: kernel overwrite ae0 link-speed
> with child speed 10000000000
> May 19 20:42:53 Core-SW-8208 /kernel: drv_ge_misc_handler: ifd:148 new
> address:b0:c6:9a:c9:ae:03
> May 19 20:42:53 Core-SW-8208 /kernel: drv_ge_misc_handler: ifd:149 new
> address:b0:c6:9a:c9:ae:03
> May 19 20:42:52 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/1
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/2
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/3
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/4
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/5
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/6
> May 19 20:42:53 Core-SW-8208 chassisd[1338]:
> CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for
> xe-0/0/7
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 2 SFP
> receive power low alarm set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 2 SFP
> receive power low warning set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 3 SFP
> receive power low alarm set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 3 SFP
> receive power low warning set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 7 SFP
> laser bias current low alarm set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 7 SFP
> output power low alarm set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 7 SFP
> laser bias current low warning set
> Jun 14 02:32:18 Core-SW-8208 member0-fpc0 chassism[118]: link 7 SFP
> output power low warning set
> May 19 20:42:53 Core-SW-8208 member0-fpc0 pfe_pme_max 24
> May 19 20:42:53 Core-SW-8208 member0-fpc0
> PFE_L2,mrvl_brg_port_stg_entry_set():7472:Received MSTI-default-rt, not
> expected
> May 19 20:42:54 Core-SW-8208 member0-fpc0 Error: Adding
> filter(block_pvst) cntr(pvst) plcr((null)) index(1) entry
> May 19 20:42:52 Core-SW-8208 member0-fpc1 chassism[120]:
> ccm_fm_hsl2_sid_plane_ctl_ack: FPC SID_PLANE_CTL_ACK fpc 1 sent; err=0
> May 19 20:44:24 Core-SW2-8208 member0-fpc0 chassism[118]: CM:
> cm_hcm_pfem_resync_done: fpc_slot: 0
> May 19 20:44:24 Core-SW-8208 member0-fpc0 chassism[118]: CM:
> cm_hcm_pfem_resync_done: FPC PFEM resync_done fpc 0 sent; err:0
>
>
> as per your experience what is this issue and why it cause also how to fix
> it.
>
>
> appreciate your support in advanced
>
>
> Regards,
>
> Mohammed
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list