Description:

The HP Chassis model created in Spectrum is not present in SOI as a CI through the Spectrum SOI Integration, but all of its port/interfaces models are present in SOI.

Solution:

The device involved in this specific case is, per the CA Spectrum Device Certification Page:

Device Name: HP BladeSystem OA

System Object Identifier: 1.3.6.1.4.1.11.5.7.1.2

SPECTRUM 9.2:

Release: Initial
Firmware: N/A
Model Type: HPBladeOnboardAdmin
Support Level: ENHANCED

SPECTRUM 9.1

Release: 9.1.2
Firmware: N/A
Model Type: xHPBladeOnboardAdmin
Support Level: ENHANCED

When this particular device is modeled, it has the following attribute values relevant to this issue:

 	Modeltype_Name = HPBladeOnboardAdmin       
   Model_Class = Chassis 

Further relevant to this issue is the fact that in Spectrum network devices given the Model_Class value of Chassis are not considered 'Device' models in Spectrum. But in this device models instance it is the exception to the rule and is indeed considered a Device model despite its Model_Class value setting of Chassis.

As of Spectrum 9.2.2, there are new Locator searches that help reveal this issue and possibly others.

In the Locator tab in Spectrum 9.2.2, there is now an Integrations folder which contains these searches:

<Please see attached file for image>

Now since these are default Spectrum searches, their filter criteria cannot be viewed via the Edit Search UI. In order to do so, you must make a copy of the default search and save it. Once saved, we can then examine the criteria, which for the Devices search is:

<Please see attached file for image>

Now related to this specific device and its model, we can see that while it is a device and should normally be included for transfer to SOI as a CI, because it is also Model_Class equal to Chassis, it ends up excluded due to the search criteria 'Model Class Not Equal To "Chassis"'.

This is Functioning as Designed and is not broken. To have this changed in a future release of Spectrum, please open an issue with CA Spectrum support to request an Enhancement Request to be logged requesting that this model type be included out of the box for transfer to SOI as a CI.

Until that is done, to resolve the problem, we will need to edit/update the Devices.xml file on the SOI Connector so that it includes this model but still excludes all other 'Model_Class=Chassis' models. To do this:

1. Make a back up copy of the existing Devices.xml file found in the following directory on the SOI Connector Host server:
   
   $SOI_HOME\resources\Configurations\SpectrumIM
   
   
2. Open the Devices.xml file and replace the default content with the following content:
   

   <search-criteria>
   <filtered-models>
   <or>
   <and>
   <equals>
   <model-type>0x591002d</model-type>
   </equals>
   <equals>
   <model-class>11</model-class>
   </equals>
   </and>
   <and>
   <does-not-equal>
   <model-class>11</model-class>
   </does-not-equal>
   <not-is-derived-from>
   <model-type>Dialup_Link</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>INB</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>SFSmartCell</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>Coax_Segment</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>Fanout</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>WA_Segment</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>GenFDDIMac_NM</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>Provider_Cloud</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>GenTRStn_NM</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>GenRptrR4Port</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>RptrPort</model-type>
   </not-is-derived-from>
   <not-is-derived-from>
   <model-type>DLCI_Port</model-type>
   </not-is-derived-from>
   <is-derived-from>
   <model-type>Device</model-type>
   </is-derived-from>
   </and>
   </or>
   </filtered-models>
   </search-criteria>

   
   
3. Save the changes to the Devices.xml file.
   
   
4. For these changes to be put into affect on the Spectrum SOI Connector it will need to be cycled. Cycle the SOI Connector Host IFW Service.

Once the connector is restarted, the missing device should be brought over to SOI as a CI to be added to a Service.

Release:
Component: SPCINT