Saturday, November 6, 2021

VMware cpu hog issue with Cisco ise image

So I have a lab setup on gns3 on my laptop to practice Cisco ise.

Diagram shown below:

http://imgur.com/a/K9B8wq7

Just a simple topology with the Cisco ise connected to a layer 3 switch and a mgmt PC connected to switch via which it will access the ise.

Now the problem is that the link between the ise and the switch (e0 to e2/11) is completely saturated as when I do a "show interface gigabitethernet 0" on the ise I get the following:

http://imgur.com/a/8p4Z6Xo

Interface is going crazy as you can see the RX packets is like 517gb (and keeps increasing as i keep the interface turned on), this is what I believe is causing the error that I see on the switch (cpu hog errors) and the switch becomes unusable which means I cannot access the gui from the mgmt PC.

I have some other screenshots below which show the settings of the VMware workstation:

http://imgur.com/a/fwQ7Oam

http://imgur.com/a/ybDjeIm

Also when I do a packet capture on the link between the ise and switch (e0 to e2/11) this is what I see:

http://imgur.com/a/MGWCM4B

Bunch of connections from 192.168.117.1 to 192.168.117.30 which is what I'm assuming the 517gb data is. The 192.168.117.0/24 subnet belongs to the vmnet2 as shown in the one of the links that I shared above. No idea what the hell is going on here.

All I want to do is be able to lab the Cisco ise. It was actually working fine the first time I set it up with no such issues and I was able to access the gui from the mgmt PC. Then I put the laptop to sleep and when I logged in the next day could never access it again. I reimaged the ise multiple times but to no effect. Know for sure that this is not an issue with resource allocation(cpu,ram, etc) as it was working flawlessly before. I tried recreating the switch as well multiple times to no effect.

So please help!!



No comments:

Post a Comment