Junos OS

Expand all | Collapse all

MS-MPC error message

Jump to Best Answer
  • 1.  MS-MPC error message

    Posted 10-18-2020 03:36

    Dear all

    Juniper MS960 version 18.4r3

     

    I got this message during the last 4 days and 3 from 4 ms pics wend down

     

    Oct 18 12:15:20 XXXXXXX (FPC Slot 2, PIC Slot 1) ms21 mspmand[240]: jbuf_alloc_init: Small jframe (recovered:8987) from (Max:9000)
    Oct 18 12:15:48 XXXXXXX (FPC Slot 2, PIC Slot 1) ms21 mspmand[240]: jbuf_alloc_init: Small jframe (recovered:8984) from (Max:9000)
    Oct 18 12:15:58 XXXXXXX (FPC Slot 2, PIC Slot 0) ms20 mspmand[239]: jbuf_alloc_init: Small jframe (recovered:8967) from (Max:9000)
    Oct 18 12:15:59 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 1 seconds
    Oct 18 12:16:00 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 2 seconds
    Oct 18 12:16:01 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 3 seconds
    Oct 18 12:16:02 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 4 seconds
    Oct 18 12:16:03 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 5 seconds
    Oct 18 12:16:03 XXXXXXX fpc2 Prolonged flow-control asserted by MAC on ms-2/0, bringing interface down
    Oct 18 12:16:03 XXXXXXX fpc2 ms-2/0: MAC stuck, trigger reset
    Oct 18 12:16:04 XXXXXXX chassisd[6498]: CHASSISD_IFDEV_DETACH_PIC: ifdev_detach_pic(2/0)
    Oct 18 12:16:04 XXXXXXX kernel: if_pfe_services_ifd_nh_get: ifd-nh-entry doesn't exist for ifd 206 porttype 102if_pfe_services_ifd_nh_delete: ifd-nh-entry doesn't exist for ifd 206 porttype 102
    Oct 18 12:16:04 XXXXXXX kernel: if_pfe_ams_process_single_event: ifd:mams-2/0/0, ev = AMS_EV_MEMBER_DEL agg_state UP, member_state: ACTIVE, member_present_count = 2
    Oct 18 12:16:04 XXXXXXX kernel: if_pfe_ams_update_per_member_nh: Unknown operation (0) on
    Oct 18 12:16:04 XXXXXXX last message repeated 3 times
    Oct 18 12:16:04 XXXXXXX kernel: if_pfe_services_ifd_nh_get: ifd-nh-entry doesn't exist for ifd 208 porttype 154if_pfe_services_ifd_nh_delete: ifd-nh-entry doesn't exist for ifd 208 porttype 154
    Oct 18 12:16:04 XXXXXXX (FPC Slot 2, PIC Slot 2) ms22 mspmand[239]: ha_type is not one-to-one
    Oct 18 12:16:04 XXXXXXX (FPC Slot 2, PIC Slot 3) ms23 mspmand[237]: ha_type is not one-to-one
    Oct 18 12:16:04 XXXXXXX mib2d[6505]: SNMP_TRAP_LINK_DOWN: ifIndex 651, ifAdminStatus up(1), ifOperStatus down(2), ifName ms-2/0/0
    Oct 18 12:16:04 XXXXXXX mib2d[6505]: SNMP_TRAP_LINK_DOWN: ifIndex 652, ifAdminStatus up(1), ifOperStatus down(2), ifName pc-2/0/0
    Oct 18 12:16:04 XXXXXXX (FPC Slot 2, PIC Slot 1) ms21 mspmand[240]: ha_type is not one-to-one
    Oct 18 12:16:04 XXXXXXX mib2d[6505]: SNMP_TRAP_LINK_DOWN: ifIndex 653, ifAdminStatus up(1), ifOperStatus down(2), ifName mams-2/0/0
    Oct 18 12:16:04 XXXXXXX chassisd[6498]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 8, jnxFruL1Index 3, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC: MS-MPC-PIC @ 2/0/*, jnxFruType 11, jnxFruSlot 2, jnxFruOfflineReason 8, jnxFruLastPowerOff 54497161, jnxFruLastPowerOn 2061691)
    Oct 18 12:16:04 XXXXXXX chassisd[6498]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperDisabled (entPhysicalIndex 118, entStateAdmin 2, entStateAlarm 0)
    Oct 18 12:16:04 XXXXXXX chassisd[6498]: CHASSISD_SNMP_TRAP0: ENTITY trap generated: entConfigChanged
    Oct 18 12:16:05 XXXXXXX chassisd[6498]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 3, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName PIC: MS-MPC-PIC @ 2/0/*, jnxFruType 11, jnxFruSlot 2, jnxFruOfflineReason 2, jnxFruLastPowerOff 54497161, jnxFruLastPowerOn 54497264)
    Oct 18 12:16:05 XXXXXXX chassisd[6498]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperEnabled (entPhysicalIndex 118, entStateAdmin 4, entStateAlarm 0)
    Oct 18 12:16:05 XXXXXXX chassisd[6498]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for ms-2/0/0
    Oct 18 12:16:05 XXXXXXX chassisd[6498]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for pc-2/0/0
    Oct 18 12:16:05 XXXXXXX chassisd[6498]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for mams-2/0/0

     

    Maybe someone had a similar problem before
    thanks



  • 2.  Re: MS-MPC error message
    Best Answer

    Posted 10-18-2020 04:10

    Hello,

     


    ppetro@mail.lviv.ua wrote:


    Oct 18 12:16:03 XXXXXXX fpc2 ms-2/0: Transient flow-control asserted by XLP MAC over link 1 for 5 seconds
    Oct 18 12:16:03 XXXXXXX fpc2 Prolonged flow-control asserted by MAC on ms-2/0, bringing interface down


     

    The transient flow-control followed by prolonged flow-control typically happens when MS-MPC officially supported parameters such as session setup rate, or session count are exceeded.

    Please check Your MS-MPC utilization and lower the MS-MPC NPU load by spreading the traffic more evenly or add more MS-MPC resources.

    HTH

    Thx

    Alex  

     

     

     



  • 3.  Re: MS-MPC error message

    Posted 10-18-2020 09:51

    Thank you for the advice