Interface storming for validation of physical interface robustness

I am testing to ensure line rate traffic run for N days between Juniper and the System Under Test is stable/error free and I want to not introduce a dedicated traffic generator (Ixia/Spirent/Etc...). The idea is to generate a handful of frames from the System Under Test using the broadcom tool and the storm those same frames between all interfaces under test for N days.

Scenario:

SUT Port A ----> Port A MX480 Port B MX480 ----> Port B SUT

Note SUT is the same system in the same forwarding domain (vlan 1600)

Question: is there a way to enable Juniper Mx480 ports to be a 'dumb pass through' for a storm? I have my config below which uses bridge domains for vlan switching.

The problem I am having is that the Juniper interface seems to be dropping duplicate SA's and detecting the storm before it starts (theory at this point)

So far what I’m seeing is that one of the two interfaces is dropping the traffic at the interface level;

  MAC statistics:                      Receive         Transmit                                                                                                                                 

    Total octets              1037260846183188  993994070084256

    Total packets               15253859753479   14621189768338

    Unicast packets                 2872399475       1255040236

    Broadcast packets           15250987353091   14558226155616

    Multicast packets                        0                0

    CRC/Align errors                         0                0

    FIFO errors                              0                0

    MAC control frames                       0                0

    MAC pause frames                         0      61708575023

    Oversized frames                         0

    Jabber frames                            0

    Fragment frames                          0

    VLAN tagged frames          15253455467148

    Code violations                          0

    Total errors                             0                0

  Filter statistics:

    Input packet count          15253794449457

    Input packet rejects             392361777

    Input DA rejects                         0

    Input SA rejects                         0

    Output packet count                          14621127169687

    Output packet pad count                                   0

    Output packet error count                                 0

    CAM destination filters: 0, CAM source filters: 0

I’m curious why the input packet rejects doesn’t indicate SA or DA rejects?

Configuration

# add interfaces to the bridge domain

set interfaces et-5/0/2 vlan-tagging
set interfaces et-5/0/2 encapsulation extended-vlan-bridge
set interfaces et-5/0/2 unit 100 vlan-id 100

set interfaces et-5/0/5 vlan-tagging
set interfaces et-5/0/5 encapsulation extended-vlan-bridge
set interfaces et-5/0/5 unit 100 vlan-id 100


# add bridge domain interface config

set bridge-domains vlan-100 domain-type bridge bridge-options no-mac-learning
set bridge-domains vlan-100 interface et-5/0/2.100
set bridge-domains vlan-100 interface et-5/0/5.100

Any ideas, possible solutions, or even suggestions would be appreciated. Thank you in advance