I am just starting with CML, installed 2.1.2 controller and created a 10 node IOSv simulation on a ESX VM with 12 vCPUs. Everything was OK until I implemented a udp-jitter sla test (only running once every 2 minutes) on one node, and now that node is 85-95% busy in the CML UI. I can login, but the IOS is extremely sluggish and often just hanging. I would like to give that IOSv device some more CPU resource to see if I can get it to be responsive, but the UI only lets me choose CPU percentages 20-100. The IOSv node definition only allows one CPU - I tried downloading and updating the yaml to make it 2 CPUs but nodes with that new definition just sit in QUEUED state and never boot up. Is there some easier way to resolve an IOS cpu bottleneck in CML? Thanks in advance for any tips.
