The Host Configuration tab for NCM is grayed out or Different Type Model alarms show in the CA Spectrum OneClick UI

Products

CA Spectrum

Issue/Introduction

If the Host Configuration tab is grayed out or there are "Different Type Model" alarms in the CA Spectrum OneClick GUI, check to see if the device is certified:

https://netops-certification.broadcom.com/vendors(default-header:vendors)

If it is not certified, but is very similar to or the same as other devices that are certified, then you may be able to work around this depending on the device. The Host Configuration
functionality is not available on the "generic" modeltypes such as the GnSNMPDev and/or GnCisocDev. When you model a device that is not certified in Spectrum, Spectrum will
select one of the generic modeltypes. If you change the modeltype to one of the "enhanced" modeltypes like SwCiscoIOS or CiscoNXOS, assuming all other prerequisites of NCM
are met, the Host Configuration will be enabled. For example, if you have a Cisco Nexus device that has not been certified in Spectrum and is modeled as the GnSNMPDev modeltype
but the standard Cisco Nexus firmware is running, then most likely you can change the modeltype to the CiscoNXOS and Host Configuration will now work.

This only works for:

1. Devices that are of a similar type

2. Devices that have an enhanced model type in Spectrum

3. The device meets the mib criteria of NCM

Environment

Release: Any
Component:

Resolution

Use the Device Certification utility and change the mapping of the System Object ID to use an enhanced model type.

Here is an example of how to change a Cisco Nexus device modeled as a GnSNMPDev to be a CiscoNXOS.

To do this:

Locate an existing Cisco Nexus model type in OneClick that is not showing in a Device Family for NCM and/or does not have the Host Configuration tab enabled.
Look at the Model Type of the device and confirm it is a generic modeltype, like GnSNMPDev or GnCiscoDev etc.
Make note of the Model Type Name and System Object ID (available in the Spectrum Modeling Information area on the device).
Right click on the device model and go to the Utilities Menu -> Device Certification...
In the Device Certification utility, double click the selected System Object ID to open it for edit. If the System Ojbect ID is not highlighted, then search for it and double click the entry.
In the "Edit" window, change the Model Type Name to be the enhanced modeltype. In this example, it will be the CiscoNXOS modeltype.
Click Ok to close.
Click the Save button to save the changes to the SSdb catalog.
You then need to update the modeltype of the existing devices. This can be done by either:
1. Destroying and recreating the device models or
2. Run the $SPECROOT/Install-Tools/PostInstall/NewMM.pl script to update the existing model to the newly mapped model type

To run the NewMM.pl Script:

As the Spectrum owner, open a command line (bash -login shell for Windows) on the SpectroSERVER where the device is modeled.
cd to $SPECROOT/Install-Tools/PostInstall directory
Run the following command: ./NewMM.pl -m
Enter the host name of IP address of the SpectroSERVER you wish to connect to and hit enter.
Enter the Landscape Handle, in Hex format. Example: 0x100000
Enter the System Object ID of the device you want to search for. Example: 1.3.6.1.4.1.9.12.3.1.3.1712
Enter the current Model Type Name. Example: GnSNMPDev
Enter the Destination Model Type Name. This is the new Model Type Name you wish to use. Example: CiscoNXOS

The script will search the SSdb database for existing GnSNMPDev models with the System OID 1.3.6.1.4.1.9.12.3.1.3.1712, and report back any models found that are
eligible for conversion, and ask if you want to convert them. Enter "y" to continue with the conversion or "n" to exit out.

The script will create a log file for the conversion. The file name will be something like NewMM_log_<month>_<day>_<year>_<hour>_<min>_<sec>_<AM/PM>.
You can review the log to see what models were converted if needed.

Repeat for any other modified System Object IDs.