Description

During a Virtual Chassis (VC) global switchover on MX Series devices, the following authd logs will be seen on the new VC primary chassis' primary Routing Engine for a few seconds.

Jul  7 17:04:43.623 2020  router-member1-re0 authd[6509]: %DAEMON-3: db env state is invalid 6, re-init
Jul  7 17:04:43.623 2020  router-member1-re0 authd[6509]: %DAEMON-3: Attempting to close SDB while DOWN

This article explains that these logs indicate a transition state and are expected during a VC global switchover with no known service impact.

 

Symptoms

When you perform a VC global switchover on member0-re1 (the VC primary chassis' primary RE):

{master:member0-re1}
router-member0-re1> request virtual-chassis routing-engine master switch         
Toggle mastership between routing engines ? [yes,no] (no) yes
Jul 07 17:04:41

The new VC state changes to below:

member0-re0 - Backup chassis' master RE (VC-Bm) 
member0-re1 - Backup chassis' backup RE (VC-Bb) 
Member1-re0  - Master chassis' master RE  (VC-Mm)   <<<< New VC primary
Member1-re1  - Master chassis' backup RE  (VC-Mb)

Observe the following logs on Member1-re0, which is the new primary chassis' primary RE:

Jul  7 17:04:41.999 2020  router-member1-re0 authd[6509]: %DAEMON-3: db env state is invalid 6, re-init
Jul  7 17:04:41.999 2020  router-member1-re0 authd[6509]: %DAEMON-3: Attempting to close SDB while DOWN
….
….
<snip….> 
Jul  7 17:04:46.935 2020  router-member1-re0 authd[6509]: %DAEMON-3: db env state is invalid 6, re-init
Jul  7 17:04:46.935 2020  router-member1-re0 authd[6509]: %DAEMON-3: Attempting to close SDB while DOWN

 

Solution

The logs indicate a transition state during VC global switchover wherein authd (the authentication daemon) is trying to connect to sdb (the subscriber database). These messages will stop when the transition is complete.

 

No action is required because these logs are expected during VC global switchover and there is no service impact. They are informational and can be safely ignored.

 

Modification History

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