[MX] FPC log messages are reported only to the local primary Routing Engine

Summary:

On an MX-VC environment, log messages of the Flexible PIC Concentrator (FPC) reports can only be seen on the local member primary Routing Engine (RE).

Symptoms:

Only mem0-fpc5 logs on member0 log message file is seen:

{master:member1-re0}

labroot@router-re0> request routing-engine login master member 0 

Last login: Thu Jul 27 15:46:38 from member1-master



--- JUNOS 15.1R4-S2.1 Kernel 64-bit  JNPR-10.1-20160724.331042_builder_stable_10

JUNOS tip:

Use 'request system software validate' to validate the incoming software

against the current configuration without impacting the running system.



warning: This chassis is operating in a non-master role as part of a virtual-chassis (VC) system.

warning: Use of interactive commands should be limited to debugging and VC Port operations.

warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.

warning: The VC-M can be identified through the show virtual-chassis status command executed at this console.

warning: Please logout and log into the VC-M to use CLI.



{backup:member0-re0}

labroot@router-re0> show log messages |match "jnh_expand_partition failed"   

Jul 24 02:30:46.405 2017  router-re0 : %PFE-3: member0-fpc5 jnh_partition_ok(13841): jnh_expand_partition failed, inst 0, jnh_app unilist-selector, dwords 65536

..snip

There was no member0-fpc5 logs on member1(VC-Mm) message log file. Only mem1-fpc5 logs on member1 log message file is seen:

{master:member1-re0}

labroot@router-re0> show log messages |match member1-fpc5    

Jul 24 02:30:52.453 2017  router-re0 : %PFE-3: member1-fpc5 nh_unilist_resource_check:353NH: nh_id:1085333, proto:ipv4, type:Unilist not installed in H/W(resource low)

..snip

Cause:

The syslog server of FPC is set member local primary. For example, all logs reported from FPC should be sent to member local primary RE. This is part of the Junos MX-VC design.

{master:member1-re0}
labroot@router-re0> request pfe execute target member0-fpc5 command "show syslog info"
Jul 28 12:19:29
SENT: Ukern command: show syslog info
GOT:
GOT:  syslog is enabled, timestamps are enabled, logging at level 7 (Debug)
GOT:  syslog is enabled on the console, enabled on 1 tty(s)
GOT:  syslog is enabled to a network server (129.0.0.1:6333)
GOT:  syslog queue depth is 512
GOT:  syslog fifo size is 3000
GOT:  315837 messages logged, 0 lost (no buffers), 13984 queue overflows
LOCAL: End of file
 
{master:member1-re0}
labroot@router-re0> request pfe execute target member1-fpc5 command "show syslog info"   
Jul 28 12:19:40
SENT: Ukern command: show syslog info
GOT:
GOT:  syslog is enabled, timestamps are enabled, logging at level 7 (Debug)
GOT:  syslog is enabled on the console, enabled on 1 tty(s)
GOT:  syslog is enabled to a network server (130.0.0.1:6333)
GOT:  syslog queue depth is 512
GOT:  syslog fifo size is 3000
GOT:  3187 messages logged, 0 lost (no buffers), 0 queue overflows
LOCAL: End of file
 
{master:member1-re0}
 labroot@router-re0> file show /etc/hosts.junos | grep "129.0.0.1 "         
Jul 28 12:21:14
129.0.0.1        lcc0-master member0-master member0
 
{master:member1-re0}
labroot@router-re0> file show /etc/hosts.junos | grep "130.0.0.1 "
Jul 28 12:21:30
130.0.0.1        lcc1-master member1-master member1
 
{master:member1-re0}
labroot@router-re0>

Solution:

This behavior is by design for MX-VC.

As an alternative, check the syslog on the remote syslog server because both VC-Mm and VC-Bm should send these FPC logs to the remote syslog server.

Modification History:

2021-04-07: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives

Knowledge Base