Customer changed the OAM protocol iterator-profile tlv size to be 500. Afer that, the MX304 fpc went into cyclic core dump state on both RE0 & RE1.

{master}

lab@MX304> show configuration protocols oam 

ethernet {

  connectivity-fault-management {

    performance-monitoring {

      enhanced-sla-iterator;

      sla-iterator-profiles {

        IDDM {

          measurement-type two-way-delay;

          cycle-time 1000;

          iteration-period 2000;

        }

      }

    }

    enhanced-cfm-mode;

<...>

    maintenance-domain 22bt-j34-bse-31-net_L3 {

      level 3;

      name-format character-string;

      maintenance-association IXRe_L3 {

        continuity-check {

          interval 1s;

          loss-threshold 3;

        }

        mep 721 {

          interface et-0/0/2.911;

          direction down;

          priority 0;

          auto-discovery;

          remote-mep 4721 {  

            action-profile generate-trap;

            sla-iterator-profile IDDM {

              priority 3;

              data-tlv-size 500;

            }

          }

        }

      }

    }

  }

}

With the above customer configure, MX304 FPC keeps core dumping.

Customer can either reduce the data-tvl-size to less than 500, or to upgrade to a JUNOS with PR1820187 fix.