This is caused by Vendor Certification Priority (VCP) Priority Group configurations.
The Interface MF NormalizedPortInfo
shows these VCP entries for the ifXTable
(High Speed Interface VC) and CiscoAirespaceWirelessMib
(Cisco Airespace Mobile Interface VC).
<VendorCertID>{http://im.ca.com/certifications/snmp}IfXTableMib</VendorCertID>
<PriorityGroup>HuaweiQosHS,TimetraMPLSPortHS,AlteonPortHS,NetScreenHS,CeragonPortHS,StarentScreenHS,RadwareQosHS,RedBackPortHS,NetscalerIfStatHS,DSLPortHS</PriorityGroup>
<VendorCertID>{http://im.ca.com/certifications/snmp}CiscoAirespaceWirelessMib</VendorCertID>
<PriorityGroup>RedBackPortHS,RedBackPortLS</PriorityGroup>
Because the IfXTableMib
is supported, and has RedBackPortHS
in the PriorityGroup
, it ties it back to the other PriorityGroup
linked to a VC that the device supports. That would be the CiscoAirespaceWirelessMib
.
Discovery finds support for and creates elements against IfXTableMib
VendorCertID. It then looks to find VCs in its PriorityGroup
that exist in PriorityGroup
entries for other VendorCertID
entries. RedBackPortHS
is in the PriorityGroup for both. The device does support the CiscoAirespaceWirelessMib
VC.
The elements get discovered.
Grouping vendor certification priorities lets you use more than one vendor certification for the same device. A single vendor certification priority can belong to as many priority groups as necessary for your application. When a device is discovered, all vendor certifications in the priority group are supported on the device.
Important! Do not update PriorityGroup and change the order of the vendor certifications in the same REST call. Changing both simultaneously may disrupt automatic rediscovery. For more information, see Automatic Rediscovery Does Not Run After Updating Vendor Group Priority.
To group vendor certification priorities, use the REST Web Services. You cannot group vendor certification priorities using the UI.
Follow these steps:
http://<DA_HOST>:8581/rest/vendorpriorities/
http://<DA_HOST>:8581/rest/vendorpriorities/ID
<CertificationOrder>
<CollectionID>167</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}F5BigipMultihostCpu</VendorCertID>
<PriorityGroup>F5</PriorityGroup>
</CertificationOrder>
<PriorityGroup>F5, Huawei</PriorityGroup>
<ID>
and <MetricFamilyID>
tags from the vendor certification priority XML.http://<DA_HOST>:8581/rest/vendorpriorities/ID
In this situation the following specific change was made to have PriorityGroup for the CiscoAirespaceWirelessMib
VC now show:
<PriorityGroup>RedBackPortLS</PriorityGroup>
After the change was made an Update Metric Families run was requested from the devices Polled Metric Families tab. When it completed the second Interface Metric Family entry was removed.
After some time the elements should show in PC as Inactive. Their DA DS is sync'ing Inactive or Not Present items.
Once that takes place we can then use the cleanupComponents.sh script to remove the inactive elements from cluttering the system. That script is found on the Data Aggregator in (default path) /opt/IMDataAggregator/scripts
.