I’ve created the ArubaOS_CX model type with the Model Type Editor. I used the ArubaOS as Base Model Type. After I assign the ArubaOS_CX model type to be used for specific system object IDs in the Device Certification tool, I get the confirmation the change was saved in the database (Successfully updated Device Identification values.), but it is not, because, if I click on the refresh icon (Reload content), the previous entry is visible.
If I discover a device by IP, the default model type is used (GnSNMPDev).
If I discover by model type pre-selecting ArubaOS_CX, I get a DIFFERENT TYPE MODEL alarm, but model type ArubaOS_CX is used.
Please check, why the Device Certification tool doesn't store the change of the ArubaOS_CX model type as the new model type to be used for the selected sysOIDs.
List of OIDs to certify for ArubaOS_CX:
184.108.40.206.4.1.47220.127.116.11.1.50 Auto GnSNMPDev Auto Unregistered Simple
18.104.22.168.4.1.4722.214.171.124.1.100 Auto GnSNMPDev Auto Unregistered Simple
126.96.36.199.4.1.47188.8.131.52.1.101 Auto GnSNMPDev Auto Unregistered Simple
184.108.40.206.4.1.47220.127.116.11.1.150 Auto GnSNMPDev Auto Unregistered Simple
Release : 20.2
Component : Spectrum Core / SpectroSERVER
The process is all through MTE and there is no need to use the device Certification utility.
add the model type ArubaOS_CX from based model type arubaOS and the root model.
Make it instantiable.
Change the Disposable_Precedence attribute to 12.
change the sysOIDverify list attribute to add only the oids the new model type.
save and exit MTE.
That is all you need to do. Any new device with the correct oid will be modeled as ArubaOX_CX.
FYI you do not need to do anything in the device cert tool in OC but you will not be able to see the new model type there until you restart tomcat.