After Spectrum Upgrade , there are getting numerous " DIFFERENT MODEL TYPE" alarms in the console

book

Article ID: 104899

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

After upgrading Spectrum, we are seeing numerous " DIFFERENT MODEL TYPE" alarms in the console. What is causing this?

Cause

The "Different Model Type" alarm  means that Spectrum is using the wrong Model Type to manage that device. This most likely can happen that those devices were originally modeled ( when they were certified) prior to the present or new upgrade/install or someone customized it. Once a device has been Certified and Spectrum is aware of the proper Model Type for that device, if models of that same type exist already in the database and have a different Model Type than what is listed for the official certification, then Spectrum will assert the alarm "Different Model Type" 
 

Environment

CA Spectrum - 10.2.1 / 10.X
Operating System - Linux / Windows
 

Resolution

First, after any Spectrum Upgrade, check to see if there has been any Certification Paks released since the version you upgraded to was released. This is to ensure the version you upgraded to also has the most recent Certifications. You can find Certification paks listed here: 

https://techdocs.broadcom.com/us/product-content//recommended-reading/technical-document-index/ca-spectrum-r10-2-solutions-patches.html
https://techdocs.broadcom.com/us/product-content//recommended-reading/technical-document-index/ca-spectrum-r10-3-solutions-patches.html


Second, after any Spectrum Upgrade, it is recommended to run the provided "NewMM.pl" script located in <SPECROOT>/Install-Tools/PostInstall

The NewMM.pl script will check for any existing models based on System Object ID and compare the Model Type assigned. If the Model Type on the current device is different than what is listed for the Official Certification, the NewMM.pl script will change the model to the correct Model Type.

Then, for any models still showing "DIFFERENT MODEL TYPE" alarms that did not get resolved by NewMM.pl, then you want to manually edit the Certification of the device to manually assign the correct Model Type. To do this, you first want to check the official certification of the device based on its System Object ID to see what Model Type is was certified as. Then using Device Certification utility in OneClick, you can correct the Model Type manually. See these steps below: 

1. Select the respective alarm in the OneClick Console. 

2. In the Component Details Pane -> Information -> CA Spectrum Modeling Information -> System Object ID. Copy the SysObjID.

3. Note the sysObjectID and then look for it at https://netops-certification.broadcom.com/vendors(default-header:vendors)

4. When you will see the results click on the first line in the first column.

5. A new page will open with all the details related to that respective SystemID / device. 

6. You will see the Model Type in this new window. See below -




7. Go back to OneClick console and right click on the selected alarm. 



8. Utilities-> Device certification -> There will be a column with Model Type where you will see the Model Type. 

9. Edit that incorrect Model Type with the correct one ( which you found in the Device certification page ). 


10. Save Device Certification changes and exit the utility if you are done. 

11. From here, the model must be Rediscovered in order for Spectrum to model the device under the new correct Model Type. Note that Rediscovering the device will result in a new model handle for the device, and will reset the Events stream and NCM configuration logs back to initial. 

 

 

Additional Information

Information on running NewMM.pl: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/spectrum/10-2/search.html?q=newmm.pl

Attachments

1558699971052000104899_sktwi1f5rjvs16jxn.png get_app
1558699968903000104899_sktwi1f5rjvs16jxm.png get_app
1558699966935000104899_sktwi1f5rjvs16jxl.png get_app