Reset Search
 

 

Article

7100 ResetAuto Neg Error in logs

« Go Back

Information

 
Title7100 ResetAuto Neg Error in logs
Symptoms
  • Reset
  • Logging buffer
<163>Aug 1 13:08:08 192.0.2.254 Bonding[2]The link with the VSB partner chassis 1 has been restored.
<163>Aug 1 13:08:08 192.0.2.254 Bonding[2]Restoring this chassis to the operational state.
<163>Aug 1 13:08:06 192.4.253.254 Bonding[1]The link with the VSB partner chassis 2 has failed.
<163>Aug 1 13:08:1920.2.253.254 Bonding[1]The link with the VSB partner chassis 2 has been restored.
<165>Aug 1 13:08:18 192.0.2.254 System[1]The board in slot 2 of the chassis is not operational.
<165>Aug 1 13:08:18 192.0.2.254 System[1]The board in slot 2 of the chassis is operational.
  • Debug log of show support ==============================================================================
Message 1/299 Syslog Message 08.32.02.0008 08/01/2018 13:08:10
<3>Bonding[1]The link with the VSB partner chassis 2 has been restored.
==============================================================================
Message 2/299 Syslog Message 08.32.02.0008 08/01/2018 13:08:06
<3>Bonding[1]The link with the VSB partner chassis 2 has failed.
==============================================================================
Message 3/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:37
<3>Bonding[1]The link with the VSB partner chassis 2 has been restored.
==============================================================================
Message 4/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:32
<3>Bonding[1]This chassis (identifier = 1 ) will remain operational due to its higher operational priority (priority = 200) than the partner cha ssis (identifier = 2, priority = 20).
==============================================================================
Message 5/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:22
<3>Bonding[1]The link with the VSB partner chassis 2 has failed.
==============================================================================
Messag 6/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:21
<3> MII[1.bcmLINK.0]getAutoConfig anState == AUTONEG_ADMIN_ENABLED but an
is FALSE
==============================================================================
Message 7/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:21
<3>MII[1.bcmLINK.0]getAutoConfig anState == AUTONEG_ADMIN_ENABLED but an is FALSE
==============================================================================
Message 8/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:21
<3>MII[1.bcmLINK.0]getAutoConfig anState == AUTONEG_ADMIN_ENABLED but an is FALSE
==============================================================================
Message 9/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:21
<3>MII[1.bcmLINK.0]getAutoConfig anState == AUTONEG_ADMIN_ENABLED but an is FALSE
==============================================================================
Message 10/299 Syslog Message 08.32.02.0008 08/01/2018 11:06:21
<3>MII[1.bcmLINK.0]getAut
Environment
  • 7100-Series
  • Firmware lower than 8.62.01.0034
Cause
Firmware bug
Resolution
Problems Corrected in 8.62.01.0034 
Upgrade to version higher than
8.62.01.0034
The system may unexpectedly reset itself. If this condition occurs, a message similar to the following appears in the persistent message log:
Assertion failed: !"TX Alarm not supported yet."
7.91.01
The following message may appear in the message log:
MII[1.bcmLINK.0]getAutoConfig anState == AUTONEG_ADMIN_ENABLED but an is FALSE
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255