How can devices move from "Cisco ISO - SSH Capable" to a "Custom NCM Device family" in DX Spectrum?

[Rohit Vashishth]

I have created a custom device family and would like to move devices dynamically from "Cisco ISO - SSH Capable" to "custom NCM device family" based on device type. In addition to that, newly created devices should also move to "custom NCM device family" as soon as they are added to the spectrum based on device type instead of "Cisco ISO - SSH Capable."

"Cisco ISO - SSH Capable" -----> "custom NCM device family"

Created a rule as well to move the devices to "custom NCM device family." However, it does not work, Device are still available in "Cisco ISO - SSH Capable" and not moving to custom device family.

 Will appreciate any input in this regard.

Thanks,

Rohit

[Jose Vicente Espinosa]

Hi Rohit,

the way I have to move a device from one device family to other is using the CLI (with spectrum user)

cd $SPECROOT/vnmsh

./connect

./destroy association rel=NCM_Family_Has_Device lmh=${OLD_DF_MH} rmh=${DEVICE_MH}

./create association rel=NCM_Family_Has_Device lmh=${NEW_DF_MH} rmh=${DEVICE_MH}

./disconnect

where:

• • ${OLD_DF_MH} is the model handle of the current device family
  • ${NEW_DF_MH} is the model handle of the target device family
  • ${DEVICE_MH} is the model handle of device being moved

Regards

[Rohit Vashishth]

Hi Jose,

Thank You for the input.

It will be really helpful.

Thanks

RohitK

[Rohit Vashishth]

Hi Jose,

Can above commands work in case of multiple landscapes?

in my case "Cisco ISO - SSH Capable" is created within  Main location spectrum server(MLS). When i run above command from Location server(LS) where device model is modeled, it gives error "Destroy assocation : association does not exist between given models"

However, for devices  that are modeled within MLS server and above commands work perfectly fine.

[Rohit Vashishth]

Hi Jose ,

It is working and moving to custom NCM family. However, if someone right click the device from console and preform "revaluate NCM device family" Devices move back to previous out of the box family such as "Cisco ISO - SSH Capable"  is there any way to force them  to remain in the custom NCM family?

[Jose Vicente Espinosa]

Hi Rohit,

sorry for the late reply

While some aspects of a device can be locked to not be modified (like model_name, model_type, etc), there is no way to avoid what you are describing

Here a KB document that confirms it.

https://knowledge.broadcom.com/external/article/195827

Anyway, I have raised the question internally to re-confirm it.

Regards