Problem Statement:
When you do a fresh install of 2.3.4 RTM kits or do an upgrade to 2.3.4 RTM kits, if you discover Huawei device that supports both “Huawei CPU” and “Huawei Entity CPU” VCs, you will see CPU components getting
discovered with both the VCs “Huawei CPU” and “Huawei Entity CPU”. This causes Average CPU Utilization data on System Health tab of Huawei device to be wrong since Huawei CPU components show aggregate CPU Utilization data of individual Huawei Entity CPU components.
This is happening due to the new Vendor Cert Priority Grouping functionality we added in 2.3.4 release. This capability allows the ability to be able to group multiple VCs together so that if more than one VC is supported by the device for a metric family in the Priority group, then we discover every VC that is supported in that group. Previously we would pick only one VC per MF. Along with this capability we also grouped some of the Huawei CPU VC’s together so that they could be discovered simultaneously if the device supported them.
Here is the screenshot of Huawei device supporting both “Huawei CPU” and “Huawei Entity CPU” VCs with 2.3.4 kits:
Workaround:
This behavior can be reverted by pulling out the “Huawei Entity CPU” VC from the Priority Group via rest web services.
Please follow these steps to update the vendor cert priorities for CPU MF via rest web services:
1) Go to web browser and get the vendor cert priorities by going to this web service:
http://<DA_HOST>:8581/rest/vendorpriorities
2) Get the MetricFamilyVendorPriority ID for NormalizedCPUInfo MF from this above output
3) In REST Client, use the HTTP Method “GET” to export the vendor cert priorities for NormalizedCPUInfo MF by entering this URL:
http://<DA_HOST>:8581/rest/vendorpriorities/<ID>
4) Now Copy this output and in REST Client, change the HTTP Method to “PUT” and paste it in the Body tab. Make the following changes:
Remove the second line from top such as <ID>88</ID>
Also Remove the second last line from bottom such as <MetricFamilyID>{http://im.ca.com/normalizer}NormalizedCPUInfo</MetricFamilyID>
Update the PriorityGroup to blank for HuaweiEntityCPUMib2 VC as below:
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiEntityCPUMib2</VendorCertID>
<PriorityGroup></PriorityGroup>
</CertificationOrder
5) Now use the HTTP Method “PUT” to update the vendor cert priorities for NormalizedCPUInfo MF by entering this URL:
http://<DA_HOST>:8581/rest/vendorpriorities/<ID>
6) Here is the sample of xml to be used for updating the vendor cert priorities for update for NormalizedCPUInfo MF :
<MetricFamilyVendorPriority version="1.0.0">
<CertificationOrderList>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CiscoCPUMibRev</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CiscoCPUMibDeprecated</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CiscoCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}AirespaceSwitchingCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CommworksIWFCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}JuniperErxCpu</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}JuniperCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}JuniperCPUSPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}JuniperIveCpuMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}NetscreenRHModCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}NetscreenRHCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}ArubaCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CrossbeamCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}StarentMobileWirelessCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}AlcatelCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}TimetraCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}F5BigipMultiHostCpu</VendorCertID>
<PriorityGroup>F5</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}F5BigipCPUMib</VendorCertID>
<PriorityGroup>F5</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}F5V45CPU</VendorCertID>
<PriorityGroup>F5</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}InfobloxCpu</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}RADCpuMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}SystemEDGELPARProcessorMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}EnterasysCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiMusaMA5100CPUMib</VendorCertID>
<PriorityGroup>HuaweiMusa</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}NetintactABProcessingLoadCPUMib</VendorCertID>
<PriorityGroup>CPU</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}NetintactABCPUMib</VendorCertID>
<PriorityGroup>CPU</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiS6506CPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiAR46XXCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiHangzhouH3CCPUMib</VendorCertID>
<PriorityGroup>HuaweiHangzhou</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiCPUMib</VendorCertID>
<PriorityGroup>Huawei</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiHangzhouH3CEntityCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}HuaweiEntityCPUMib2</VendorCertID>
<PriorityGroup></PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}AlteonMPCPUMib</VendorCertID>
<PriorityGroup>Alteon</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}AlteonSPCPUMib2</VendorCertID>
<PriorityGroup>Alteon</PriorityGroup>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}ExtremeCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}ACMEPacketCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}JuniperRouter7MinsCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CANSMr11WinCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}CANSMr11UnixCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}EmpireCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}UCDavisCPUMib</VendorCertID>
<PriorityGroup/>
</CertificationOrder>
<CertificationOrder>
<CollectionID>43</CollectionID>
<VendorCertID>{http://im.ca.com/certifications/snmp}hrCPUMib</VendorCertID>
<PriorityGroup>HuaweiHangzhou</PriorityGroup>
</CertificationOrder>
</CertificationOrderList>
</MetricFamilyVendorPriority>
Expected Results:
After updating the vendor cert priorities for CPU MF, you will see only CPU components for “Huawei CPU” VC and you will no longer see the CPU components for “Huawei Entity CPU” VC in CAPC UI. These CPU components for “Huawei Entity CPU” VC will stop polling and they will go in Retired state. Sometimes too many retired components cause performance issues. To remove retired components you can use the script /opt/IMDataAggregator/scripts/remove_retired_items.sh if there are too many CPU items in Retired state.
In case you want to see the components for “Huawei Entity CPU” VC discovered instead of the components for “Huawei CPU” VC, then you will need to change the vendor cert priorities in the Metric Family UI. This process is documented in the product guide.
Here is the screenshot of Huawei device supporting both “Huawei CPU” and “Huawei Entity CPU” VCs after applying this workaround:
If you have any issues after following these guidelines, please raise a support issue as normal so we can review further.
Regards
Pete
Peter Bennett
CA Technologies | Support Delivery Manager