How can I import the CML cat9kv image into Catalyst Center?

[KristofB]

Hello CML community!

I'm using CML to build all kinds of demos. I’ve successfully onboarded virtual Catalyst 9k switches via PNP into Catalyst Center and was able to build 802.1X and TrustSec labs, nice! 

However, there's one thing that’s been frustrating me for a while, and I just can’t seem to figure it out...

How can I import the CML cat9kv image into Catalyst Center? 

My CML devices are recognized as Cisco Catalyst 9000 UADP 8 Port Virtual Switch device family. 

Since "Install Mode" is used, this image cannot be easily set as golden to import the image automatically.

Typically, you just upload the .bin to Catalyst Center, however; 

• I downloaded version 17.12.02 from cisco, but it is not recognized as the same software version  (17.12.02.0.2739 vs 17.12.02.0.1943) 
• The software on the cat9kv itself isn't a .bin file, it consist out of two .pkg (?) these file types cannot be imported into Catalyst Center.
• I did find and download the qcow2 image from the internet and was able to import it to Catalyst Center. However, I can mark it as golden, but it shows up in UNKNOWN device family

So I'm out of options.... 

Why do I want this? 

Because I want to build a setup to easily test/show/demo the RMA workflow in Catalyst Center. 

Unfortunately, this workflow requires that the image of the faulty device is imported into Catalyst Center 

Does anyone have any idea?

Kristof

[Arne Bier]

@KristofB - I have exactly the same situation. I wanted to test the Hardware Replace feature in Cat Center, and the prerequisite for that appears that the software image has to exist in Cat Center.

Unaware of your experience (this thread) or any documented limitations, I blindly tried something similar with my CML 2.8.1 setup - the v9K image form CML 2.8.1 is 17.15.01.0.126 - I copied the file off of the device's Flash and the image name ends in .pkg - which Cat Center can't/won't import. I renamed the file to .SPA and then the import worked.

However, Cat C can't verify the image (it has internet can verify other images), and therefore I can't Assign the image to any device type.

Seems that the image from the device is not supported

I then imported the .QCOW file from the CML refplat file.

But the end result is no good - the Family Name is UNKNOWN and you can mark this as golden, but you can't assign this to the virtual C9K - it doesn't look like Cisco have planned to allow this device type to be upgraded.