Description

Customer founds that all the MX-SPC3 cards failed to bring either the VMS unit interfaces, or mams unit intefaces to be up in the MX Virtual-Chassis box.

It looks like the MX-SPC3 can not communicate to the Routing-Engine properly.

 

{master:member0-re0}

lab@mxvc> show interfaces terse | match mams

mams-8/0/0 up up

mams-8/0/0.20 up down ams

mams-8/0/0.30 up down ams <------- no service-set info

 

lab@mxvc-fpc8:~# ps aux | grep flow

root 5977 0.0 0.0 9716 2608 ? Ss 08:36 0:00 /bin/bash /usr/bin/pfe-app-wrapper /etc/init.d/flowd_spc3 0 start

root 5986 0.0 0.0 9452 2416 ? S 08:36 0:00 /bin/bash /etc/init.d/flowd_spc3 start

root 5996 2670 1.3 127463960 1784028 ? RLl 08:36 5523:04 /usr/sbin/flowd_spc3.elf -d -r 1 -z 0 -M 12

 

FLOWD_SPC3-8.0(vty)# show ifl brief

Index Name Type Encapsulation Flags RT Index Channel FNP status

----- -------------------- ------------- -------------- ------ -------- ----------

0 .local..0 Unspecified Unspecified 0x0000000000000010 0 0

1 .local..1 Unspecified Unspecified 0x0000000000000052 0 0

2 .local..2 Unspecified Unspecified 0x0000000000000052 0 0

262016 .local..36735 Unspecified Unspecified 0x0000000000000052 0 0

262017 .local..36736 Unspecified Unspecified 0x0000000000000052 0 0

262018 .local..36737 Unspecified Unspecified 0x0000000000000052 0 0

131075 .pfe.0 Unspecified Unspecified 0x0000000000000040 0 0

131096 .pfe.1 Unspecified Unspecified 0x0000000000000040 0 0

 

FLOWD_SPC3-8.0(vty)# show services service-set

Service set Type Int ID Ext ID Opt

----------------------------------------------------------

 

FLOWD_SPC3-8.0(vty)#

Symptoms

mams unit interface stuck in down state

Solution

Further investigation found there has traceoptions enabled under the [security] stanza. Once the traceoptions is disabled, the problem is cleared.

{master:member1-re0}

lab@mxvc> show configuration security 

##

## inactive: security

##

flow {

  traceoptions {

    file flowlogs size 1g;

    flag all;

  }

}

traceoptions {

  file flowlogs size 1g;

  flag all;

}

 

This issue is under investigation by Juniper engineering team. As a workaround, customer can disable the traceoptions under the [security] stanza to make the MX-SPC3 work.

Modification History

2024-07-04 : Article Created