OIDs that can be used to build the aggregate objects, if PAgP is unavailable on device snmpwalk

Products

• VMware Smart Assurance

Issue/Introduction

This article helps list out the OIDs that can be used to build the aggregate objects, if PAgP is unavailable on device snmpwalk 

Environment

Smarts - 10.1.x / 2.x
TCSA - 2.x

Resolution

SMARTS uses the PAgP (Port Aggregate Protocol) to build aggregate objects (ports and interfaces).
When PAgP is not available, one can use the LACP (Link Aggregate Control Protocol)/LAG (Link Aggregate Group) to build aggregate objects.
For LACP/LAG to build aggregate objects, the following OIDs need to be populated:

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"}

Once the above OIDs are populated, SMARTS can use this information to build the aggregate objects.