We have a challenge with Cisco network devices, and deciding on a path to take.
What happens today:
- The pattern creates models based on what it finds in the MIB causing blank model records.
- The OID's cover multiple models, so if I use an OID, it generalizes the model, and does not reflect what we have.
- For instance - 1.3.6.1.4.1.9.1.2694 is an OID that is used across several actual models in our environment
- C9200L-24P-4G
- C9200L-4T-4G
- C9200L-48P-4X
- If I use the OID, I lose the actual model information
- If I use the models created by the MIB, I end up with multiple models for the same actual model, as the manufacturer in the MIB is different
-
| Name | Manufacturer |
| C9200L-48P-4G | AVAGO |
| C9200L-48P-4G | CISCO-AGILENT |
| C9200L-48P-4G | CISCO-OPNEXT |
| C9200L-48P-4G | CISCO-OEM |
| C9200L-48P-4G | INTELLINET |
| C9200L-48P-4G | CISCO-ACCELINK |
| C9200L-48P-4G | CISCO-AVAGO |
It even gets uglier, as sometimes, the MIB has no manufacturer, or it has To Be Filled By O.E.M.
Because of this, the one model gets spread across multiple model records.
Any suggestions on how, in HAM Pro, I can get these models to show for what they are, but merge them into one actual model for each model. i.e. all of the 7 models should become one C9200L-48P-4G
