SRX

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  FPC Restarting

    Posted 09-29-2009 00:37
    Bascially the fpc restarts itself and it shows the following in the log: ep 27 05:54:05 pe-0/0/0: large delay buffer clearedSep 27 05:54:05 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for gr-0/0/0Sep 27 05:54:05 gr-0/0/0: large delay buffer clearedSep 27 05:54:05 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ip-0/0/0Sep 27 05:54:05 ip-0/0/0: large delay buffer clearedSep 27 05:54:05 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ls-0/0/0Sep 27 05:54:05 ls-0/0/0: large delay buffer clearedSep 27 05:54:06 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for mt-0/0/0Sep 27 05:54:06 mt-0/0/0: large delay buffer clearedSep 27 05:54:06 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for lt-0/0/0Sep 27 05:54:06 lt-0/0/0: large delay buffer clearedSep 27 05:54:06 PIC (fpc 0 pic 0) message operation: add. ifd count 23, flags 0x3 in mesgSep 28 13:13:14 rcv: ch_ipc_dispatch() null ipc read for args 0xe22b60 pipe 0xe23200, fru FWDD 0Sep 28 13:13:15 -- FWDD 0, last request 0, state OnlineSep 28 13:13:15 CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: ErrorSep 28 13:13:15 fpc_down slot 0 reason Error cargs 0xe22b60Sep 28 13:13:15 fpc_srxsme_disconnect slot is 0 Sep 28 13:13:15 CHASSISD_IFDEV_DETACH_FPC: ifdev_detach(0)Sep 28 13:13:15 LS: PIC DELETE: Deleting IFDs(#0) on pic 0 slot 0  ls_ifdev_detachSep 28 13:13:15 ifd ge-0/0/0 marked as goneSep 28 13:13:15 ifd ge-0/0/1 marked as goneSep 28 13:13:15 ifd ge-0/0/2 marked as goneSep 28 13:13:15 ifd ge-0/0/3 marked as goneSep 28 13:13:15 ifd ge-0/0/4 marked as goneSep 28 13:13:15 ifd ge-0/0/5 marked as goneSep 28 13:13:15 ifd ge-0/0/6 marked as goneSep 28 13:13:15 ifd ge-0/0/7 marked as goneSep 28 13:13:15 ifd ge-0/0/8 marked as goneSep 28 13:13:15 ifd ge-0/0/9 marked as goneSep 28 13:13:15 ifd ge-0/0/10 marked as goneSep 28 13:13:15 ifd ge-0/0/11 marked as goneSep 28 13:13:15 ifd ge-0/0/12 marked as goneSep 28 13:13:15 ifd ge-0/0/13 marked as goneSep 28 13:13:15 ifd ge-0/0/14 marked as goneSep 28 13:13:15 ifd ge-0/0/15 marked as goneSep 28 13:13:15 ifd pd-0/0/0 marked as goneSep 28 13:13:15 ifd pe-0/0/0 marked as goneSep 28 13:13:15 ifd gr-0/0/0 marked as goneSep 28 13:13:15 ifd ip-0/0/0 marked as goneSep 28 13:13:15 ifd ls-0/0/0 marked as goneSep 28 13:13:15 ifd mt-0/0/0 marked as goneSep 28 13:13:15 ifd lt-0/0/0 marked as goneSep 28 13:13:15 fpc_offline_now - slot 0, reason: Error, error OKSep 28 13:13:15 Power off FPC 0Sep 28 13:13:15 CHASSISD_IPC_WRITE_ERR_NULL_ARGS: FRU has no connection arguments fru_send_msg FWDDSep 28 13:13:15 send: fwdd, fpc 0 powered offSep 28 13:13:15 hwdb: entry for fpc 1867 at slot 0 deleted Sep 28 13:13:15 PIC (fpc 0 pic 0) message operation: change. ifd count 23, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 22, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 21, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 20, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 19, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 18, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 17, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 16, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 15, flags 0x2 in mesgSep 28 13:13:16 PIC (fpc 0 pic 0) message operation: change. ifd count 14, flags 0x2 in mesg

     


    #FPC


  • 2.  RE: FPC Restarting

    Posted 09-29-2009 01:17

    These messages are typical syslog entries recorded after FPC restart, not much information there.

    Check if there is FPC core dump under /var/crash:

     

    show system core-dumps

     

    - then open a JTAC case and upload the core file to ftp.juniper.net (JTAC will provide you instructions on how to upload).



  • 3.  RE: FPC Restarting

    Posted 09-29-2009 09:47

    Is chassis cluster configured for this node which shows the FPC going offline? If it is the case then please include your config from the device.

     

    Thanks



  • 4.  RE: FPC Restarting

    Posted 09-29-2009 23:54
    Juniper engineering have found a workaround for the problem by disabling the anti-virus service.