Smarts IP: Cisco CRS devices are not creating AggregateInterface

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

Discovery of the Cisco CRS devices did not create the AggregateInterface objects.
When you turn on discovery debug you can see within the log that "Create Interface" was called:

$ grep -i "Create Interface:" Twincast_IP942HF9_en_US_UTF-8.log | wc -l 768

Out of these interfaces, we can see come are aggregate by the word BUNDLE:

$ grep -i "Create Interface:" Twincast_IP942HF9_en_US_UTF-8.log | grep -i bundle | awk ' {print $4 $5}

IF-Device-1/1111[Bundle-Ether1100]
IF-Device-1/2222[Bundle-Ether3318]
IF-Device-1/3333[Bundle-Ether3307]
IF-Device-1/4444[Bundle-Ether3317]
IF-Device-1/5555[Bundle-Ether3325]

But when discovery is done, there is no AggregateInterface object.

Environment

VMware Smart Assurance - SMARTS

Cause

As per design and since this is a Cisco device, SMARTS walks the below oid to figure out if these above represented bundle descriptive indexes are exposed:

pagpGroupIfIndexOID  {".1.3.6.1.4.1.9.9.98.1.1.1.1.8"}

The OID represents both the physical port index that is taking part in the bundled environment along with the LAG port index in the following format.

pagpGroupIfIndexOID "." phyPortIndex:integer fs lagPortIndex:integer

These lagPortIndex is what being created as AggregateInterface.
While creating these AggregateInterface, SMARTS will be removing the interface object associated with the same index and then replace it with the AggregateInterface class.
From the debug log, there are no debug prints executed.  This means none of the rule was called that creates the AggregateInterface.
The only possibility could be that there are no data being populated in the above said oid (i.e pagpGroupIfIndexOID {".1.3.6.1.4.1.9.9.98.1.1.1.1.8"})

Resolution

Check if there are data populated in above OID by performing a selective walk on the pagpGroupIfIndex MIB oid.
if there are no data, then that explains why SMARTS is not creating the AggregateInterfaces.
However, even without the support of the PAgP (Port Aggregate Protocol), with LACP (Link Aggregation Control Protocol)/LAG (Link Aggregate Group) there should be enough information to build the AggregateInterface objects.
 

Additional Information

If there exist data, then please enable packet capture during the course of discovery to see if there are any abnormalities while probing pagpGroupIfIndex OIDs