Knowledge Search


×
 

[MX] Polling of SNMP LAG MIB dot3adAggPortTable tables is failing

  [KB34836] Show Article Properties


Summary:

This article describes why polling of the dot3adAggPortTable SNMP link aggregation group (LAG) MIB tables may fail after a LAG configuration change is implemented or the FPC is reset. It also points out the Junos OS releases in which the issue has been resolved and gives the steps to perform as a workaround in the meantime.

 

Symptoms:

When the LAG configuration is changed or an FPC reset is performed:

  • Polling of dot3adAggPortTable LAG MIB tables (dot3adAggPortDebugTable, dot3adAggPortPartnerOperPort, dot3adAggPortAttachedAggID, and dot3adAggPortPartnerOperSystemID) may fail

  • An mib2d process core may occur

  • Unexpected values may be seen for the LAG MIB OIDs

 

Example

{MASTER}
lab@router> show snmp mib walk dot3adAggPortPartnerOperPort       
Request failed: General error

{MASTER}
lab@router> show snmp mib walk dot3adAggPortAttachedAggID      
Request failed: General error

{MASTER}
lab@router> show snmp mib walk dot3adAggPortPartnerOperSystemID
Request failed: General error

{MASTER}
lab@router> show snmp mib walk dot3adAggPortTable | no-more 
Request failed: General error

 

Cause:

The LAG MIB table polling failure and other issues mentioned above occur because of the presence of the AE interfaces, lc-* and pfh-*, which should not actually exist.

The issue might be seen when the LAG configuration is changed by adding or removing LAG bundles and child links, or an FPC reset is performed:

{MASTER}
lab@router> show interfaces ae24 extensive | find link:
    Link:
      lc-7/2/0.32769
        Input :             0          0             0            0
        Output:             0          0             0            0
      pfh-7/0/0.16383
        Input :             0          0             0            0
        Output:             0          0             0            0
      pfh-11/0/0.16383
        Input :             0          0             0            0
        Output:             0          0             0            0
      lc-9/2/0.32769
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/0/1.32767
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/0/2.3450
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/1/1.32767
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/2/1.32767
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/2/2.3448
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/3/1.3451
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-0/0/2.32767
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-9/1/1.3817
        Input :             0          0             0            0
        Output:             0          0             0            0
      xe-1/0/0.0
        Input :  160846771414     108610 216186122602347   1168118112
        Output:    1333291066        495 1003504082615      4028304
      xe-1/1/0.0
        Input :  160265648981      86345 215404962719132    927451472
        Output:    3151105328        544 3444795435380      4008528
<omitted>

 

Solution:

As per PR1060202, the issue has been resolved in Junos OS releases 13.3R7-S3, 13.3R9, 14.1R5, 14.1X51-D50, 14.1X51-D55, 14.1X53-D28, 14.2R6, and 15.1R1.

Meanwhile, a workaround is to perform the following steps:

  1. Deactivate the LAG configuration.
  2. Restart mib2d.

  3. Activate the LAG configuration.

 

Related Links: