Junos OS

Expand all | Collapse all

atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

Jump to Best Answer
  • 1.  atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

    Posted 08-15-2019 20:30

    Hi all,

     

    I am continuously seeing the log below in the chassisd file of a MX960 router. 

    Does anyone have a clue? Is it something normal and informational or it can be a hardware issue?

    I am using RE-S-2000, MPC7E, MPC2E and SCBE2.

     

    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 vfail_reg1 0x00000055
    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 vfail_reg2 0x00000000
    Aug 15 00:31:28 atlas_i2cs_power_ok:641 CB-1 i2c_id 0x00000bac
    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 Power Up State 0x0000007c
    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 Power Disable Cause 0x00000000
    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 Power VFail 1 Cause 0x00000000
    Aug 15 00:31:28 atlas_i2cs_power_ok: CB-1 Power VFail 2 Cause 0x00000000
    Aug 15 01:20:59 atlas_i2cs_power_ok: FPC-0 Power Up State 0x00000068
    Aug 15 01:20:59 atlas_i2cs_power_ok: FPC-0 Power Disable Cause 0x00000000
    Aug 15 01:20:59 atlas_i2cs_power_ok: FPC-0 Power VFail 1 Cause 0x00000000
    Aug 15 01:20:59 atlas_i2cs_power_ok: FPC-0 Power VFail 2 Cause 0x00000000
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 vfail_reg1 0x00000000
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 vfail_reg2 0x00000055
    Aug 15 07:11:51 atlas_i2cs_power_ok:641 CB-0 i2c_id 0x00000bac
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 Power Up State 0x0000007c
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 Power Disable Cause 0x00000008
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 Power VFail 1 Cause 0x00000000
    Aug 15 07:11:51 atlas_i2cs_power_ok: CB-0 Power VFail 2 Cause 0x00000040
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 vfail_reg1 0x00000000
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 vfail_reg2 0x00000055
    Aug 15 09:45:32 atlas_i2cs_power_ok:641 CB-0 i2c_id 0x00000bac
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 Power Up State 0x0000007c
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 Power Disable Cause 0x00000008
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 Power VFail 1 Cause 0x00000000
    Aug 15 09:45:32 atlas_i2cs_power_ok: CB-0 Power VFail 2 Cause 0x00000040

     

    Thanks in advance.



  • 2.  RE: atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

     
    Posted 08-15-2019 20:35

    This looks like a hardware issue , mostly CB0 

    Can you make CB1/RE1 master and check whether you are getitng those logs 

     

    Thx

    Anish 



  • 3.  RE: atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

    Posted 08-16-2019 05:38

    Thanks for the feedback.

     

    Sure, I will do that. Strange enough we are seeing those logs on two different MXs.

     

    Best regards.



  • 4.  RE: atlas_i2cs_power_ok continuous log in the file chassisd (MX960)
    Best Answer

    Posted 09-02-2019 10:59

    Hello Anish,

     

    I received feedback from JTAC that we can safely ignore those messages. 

     

    vfail_reg2 status register should be 0 (no voltage issue detected), but we see instead 0x00000055. But we can assure that the components are ok, even in the lab.

     

    Thanks much.



  • 5.  RE: atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

     
    Posted 08-16-2019 08:57
    While you ware waiting to switchover the mastership please check if there is any alarm on the device and does all component look okay show chassis alarm show chassis environment | no-more Also, did you perform any recent upgrade on the device? Thanks Vishal


  • 6.  RE: atlas_i2cs_power_ok continuous log in the file chassisd (MX960)

    Posted 09-02-2019 10:57

    Hello Singh,

     

    No, there is no alarm on the MX.

     

    I received feedback from JTAC that we can safely ignore those messages. 

     

    vfail_reg2 status register should be 0 (no voltage issue detected), but we see instead 0x00000055. But we can assure that the components are ok, even in the lab.

     

    Thanks much.