Go ahead and close the session running the IOS node in CLI. Now go back to the SSH session running “top” and see how the CPU is doing:Īs can be seen, a single IOS instance is only taking 1% CPU instead of 25% which is much better! Then start the IOS session over but appended with “–idle-pc=” and the value selected. The highest count is usually the best value to use, so quit out of the IOS session with “Ctrl+]” and then”q”. To do this, navigate back to the SSH session running the IOS emulation and use the keyboard combination “Ctrl+]” and then hit “i”: To fix this issue, we need to have Dynamips (the software that emulates the Cisco IOS) calculate a better IDLE PC value compared to the default. Once the IOS device completes booting (after exiting the initial configuration dialog) navigate back to the first SSH session with top running and observe the CPU load:Īs will be noticed, the CPU is running pretty high for a single IOS device running. Now run the IOS from the second CLI, for this tutorial I will be issuing the IDLE PC for a C7200 node: Open a second SSH session to the EVE-NG CLI, while leaving the first SSH session open. This post is going to be a quick guide on configuring the default IDLE PC settings for EVE-NG.įirst ssh to the EVE-NG CLI and issue the “top” command: Doing extensive Google searching only resulted in a single document on the “old” way of configuring the default IDLE PC and a bunch of hits for GNS3 configuration. For example, configuring the default IDLE PC for a Cisco IOS node in GNS3 is very straightforward. A draw back I’ve run into with EVE-NG is its lack of quick and easy customization. One thing I really like about EVE-NG is the ability to use a web client instead of needing a thick client like you do for GNS3 and VIRL. As I continue on my quest for the perfect lab I have been messing around with EVE-NG (a competitor to GNS3 and VIRL).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |