This article provides an example of how to perform self-certification for network devices.
- Discovered arrayNetworks device in snmpcollector probe.
- The device has CPU usage oid (1.3.6.1.4.1.7564.30.1) as per the vendor MIB. However, snmpcollector probe uses UC-Davis oid (1.3.6.1.4.1.2021) to calculate CPU usage rather than the vendor MIB.
We would like to change it, but according to the device support portal, vendor MIB (1.3.6.1.4.1.7564.30.1) does not appear to be officially certified.
Please explain how to use self-certification to meet my requirement.
Prerequisites
1. Obtain all required vendor MIBs for your device (including what is listed in the IMPORTS section of the MIB or MIBs)
2. Identify the SNMP OIDs you would like to use/monitor
3. Self-cert portlet/webapp (ump_selfcert) has been deployed and is available in the Operator Console respectively
INSTRUCTION FOR THIS EXAMPLE
- arrayNetworks MIB
- Goal: develop one custom certification to support CPU usage with vendor mib as follows:
[Metric Family] CPU
[Metric] Utilization
[oid] cpuUtilization (1.3.6.1.4.1.7564.30.1)
Step1 - Open self-cert webapp/portlet, select the snmpcollector probe instance you would like to work with.
Step2 - Input information of the specific device you would like to certify.
Step3 - Open MIB File Manager, Add ALL of the required MIBs. To add your vendor MIB files, select and Load it.
Step4 - You will see the "private" tree, enterprises -> arrayNetworks > performance > cpuUtilization OID, [Click Add to OID Cart].
Step5 - For this example scenario, highlight CPU Metric Families in 'CPUs' tree.
Step6 - Highlight [Names] and input the name of the metric.
In this example, we are using "CPU".
- For the string part, please make sure your string is surrounded by "double quotes."
- This name is used for the QOS target, so take the time to consider the best name and keep it short.
Step7 - Highlight [Utilization] and click "Create expression."
In this example, double click the "cpuUtilization" variable.
Step8 - Click 'Save' as a new custom certification.
A new cert file is then created in the <UIM>/probes/network/snmpcollector/CustomVendorCertifications folder.
Step9 - Deactivate and Activate the snmpcollector probe to reflect the new cert file.
Step10 - Rediscover the device profile (Force Component Rediscovery).
Step11 - Highlight the newly discovered CPU component, click option, "Run Vendor Certification Test," and make sure the new cert is applied.
Attached you will find a few samples of cert files created in this example.
If you would like to develop custom certifications for multiple Metric Families (for example, CPU Usage and Memory Usage), you need to iterate the same steps for every Metric Family, as multiple Metric Families cannot be included in one custom certification.
Limitations of Self-Certification
- It is not possible to create new Metric Families
- It is not possible to create new Metrics
Please review the self-certification process for 23.4 or higher at the url below: