Smarts IP: Aggregate Ports (L2 Ports) are not being discovered on Arista Switches

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Aggregate Ports (L2 Ports) are not being discovered on Arista Switches

Environment

VMware Smart Assurance - SMARTS

Cause

To create AggregatePorts, the following generic MIB OIDs needs to be present:
dot3adAggMACAddress
{".1.2.840.10006.300.43.1.1.1.1.2"}
dot3adAggPortAttachedAggID
{".1.2.840.10006.300.43.1.2.1.1.13"}
dot3adAggPartnerSystemID
{".1.2.840.10006.300.43.1.1.1.1.8"}
dot3adAggActorSystemID
{".1.2.840.10006.300.43.1.1.1.1.4"}
dot3adAggPortPartnerOperPort
{".1.2.840.10006.300.43.1.2.1.1.17"}
dot3adAggPortActorPort
{".1.2.840.10006.300.43.1.2.1.1.14"}
dot3adAggPortActorSystemID
{".1.2.840.10006.300.43.1.2.1.1.3"}
dot3adAggPortPartnerOperSystemID
{".1.2.840.10006.300.43.1.2.1.1.9"}

SMARTS has all the necessary logic in place to create AggregatePorts from the generic MIB which is where 90% of the vendors expose it.

Resolution

These are generic ones, if Arista claims that they no longer use the above MIBs to expose the AggregatePort details and indeed use Enterprise specific MIBs, then they have to let us know which OID they use to expose those details.

Otherwise, if they claim that they indeed expose the AggregatePort information in the above MIB OIDs, then they have to clarify why those details are not present in the current walks collected from the device and a fix will need to be provided from them.

Additional Information

Only vendors like cisco, F5 use their own MIB implementation.