CML-P 2.1

[AndrewColemab8965]

I've been using CML-P 2.0 since release, and noticed today the 2.1 is out. 

Do I need to "De-register" first,  before importing CML-P 2.1 into VMware and trying to get everything set up and working, or should I just be able to nuke the previous 2.0 VM, import the new one, and hit the ground running? 

I've noticed the registration token is *slightly* different from the 2.0 token.  It's like 98% the same, but with missing 2 letters present in at the end of the previous token. 

Just want to make sure I don't end up twiddling my thumbs, waiting on someone to tell me if I missed a step. 

[Martin L · Accepted solution]

Good question; I though we can do software upgrade.  see if u get more info from https://developer.cisco.com/docs/modeling-labs/#!cml-users-guide  

OR from CML discussions  https://learningnetwork.cisco.com/s/topic/0TO3i00000094ZjGAI/cisco-modeling-labs-personal-community

Regards, ML
**Please Rate All Helpful Responses **

[AndrewColemab8965]

Looks like you have to de-register any time you switch to a different VM (and I overlooked the fact that I could use that .rpm to upgrade my existing install).  

Thanks!   

[2200069405409]

I don't follow?

[AndrewColemab8965]

Right before I downloaded the 2.1  .ova,   I clicked on the 2.x access token in my account page (expecting them to be the same).  The thing is, it was almost completely identical, except the token was now two characters shorter than then the previous one:

<crazy long string>0ACM

versus

<crazy long string>0A

I wasn't sure if the old token would still work.  After checking the links Martin provided,  Cisco made it clear that you have to de-register, before trying to import and run a newer version of CML-P

If I had noticed that one of the links was to an update .rpm,   I would've used that instead,  but too late.     

Got 2.1 imported and working fine now, using that shorter token. 

[Martin L]

Good to know, thanks for info; have fun !