Hi Community,
I have a small problem. When I start a Cisco IOSv image, no matter which L3 or L2, I get the output of show commands very very slowly.
I have enough resources allocated for the eve-ng and still I have this problem. I also get this problem with only one device in the lab.
You can't work properly with it.
For your information: I have tried all IOSv versions, always with the same result. If I start 20 IOL devices or ASAv or N9Kv, then everything works there immediately.
Only the IOSv images cause me problems. Should I possibly adjust something there?
Can you please help me?
Thank you in advance.
Max
Cisco VIRL/CML IOSv Images to slowly output by show commands
Moderator: mike
-
- Posts: 8
- Joined: Sun Oct 18, 2020 9:56 pm
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Cisco VIRL/CML IOSv Images to slowly output by show commands
It is vIOS issue sorry..
vIOS throughput comparing vs IOL is
vIOS 1.5. mbps !!! vs IOL 100mbps
makes sense?
Such is that image and nothing can be done..
it is ok for ping test only
vIOS throughput comparing vs IOL is
vIOS 1.5. mbps !!! vs IOL 100mbps
makes sense?
Such is that image and nothing can be done..
it is ok for ping test only
-
- Posts: 8
- Joined: Sun Oct 18, 2020 9:56 pm
Re: Cisco VIRL/CML IOSv Images to slowly output by show commands
Hello Uldis,
thank you very much for your answer.
Unfortunately, I don't understand it.
It's not about a data transfer between two nodes, but when I send a show run or show version to a node, I get the output displayed very slowly, the letters are practically written there one by one.
You say that IOSv has 1.5Mbit throughput, a COM/serial interface under Windows has 115Kbit and the output is displayed normally on the normal switch or router.
1.5Mbit should be sufficient for show commands, right?
I have now also seen that my eve ng shows 100% CPU load for only one node and only 25% CPU load for a Nexus 9K, which requires significantly more resources. Is this the reason?
Do you have to select any particular QUEMI version for IOSv Node?
thank you very much for your answer.
Unfortunately, I don't understand it.
It's not about a data transfer between two nodes, but when I send a show run or show version to a node, I get the output displayed very slowly, the letters are practically written there one by one.
You say that IOSv has 1.5Mbit throughput, a COM/serial interface under Windows has 115Kbit and the output is displayed normally on the normal switch or router.
1.5Mbit should be sufficient for show commands, right?
I have now also seen that my eve ng shows 100% CPU load for only one node and only 25% CPU load for a Nexus 9K, which requires significantly more resources. Is this the reason?
Do you have to select any particular QUEMI version for IOSv Node?
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Cisco VIRL/CML IOSv Images to slowly output by show commands
Where is EVE installed> and what Antivirus Software has your PC ??
It makse sense, some of AV inspecting VM machines and makes console extremely slow !!
This nested virtualization on AV must be disabled
I know where to disable it on Avast or AVG,,,,
It makse sense, some of AV inspecting VM machines and makes console extremely slow !!
This nested virtualization on AV must be disabled
I know where to disable it on Avast or AVG,,,,
-
- Posts: 8
- Joined: Sun Oct 18, 2020 9:56 pm
Re: Cisco VIRL/CML IOSv Images to slowly output by show commands
I have installed eve-ng on my Windows10 machine in VM-Ware Player. I use Microsoft Defender as antivirus.
As I said, only IOSv images cause these problems. Is there anything special to be aware of there? And why does only one IOSv node cause 100% CPU load?
As I said, only IOSv images cause these problems. Is there anything special to be aware of there? And why does only one IOSv node cause 100% CPU load?
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Cisco VIRL/CML IOSv Images to slowly output by show commands
No,
vIOS no need extra tweak, it must be ok after fully boots
vIOS no need extra tweak, it must be ok after fully boots