It turns out I am a little slow on the uptake! Dynagen 0.11.0 is now available.

One of the most exciting new features in the new release is the ability to setup PIX emulation. You can see it here in the updated tutorial!  So, there goes my Saturday nights!!Check out the release notes here.

I have done a fair bit of research into this and I am pretty sure that I have the configurations that are applied to the core routers and switches pretty well nailed! These files are provided as is with no express or implied warranty. Invurted.com is not responsible for any damage caused by using these files.

With considerable help from Arden (http://www.ardenpackeer.com), I could have this sweet virtual Cisco lab up and running.
Following is the Dynamips .net file. Due to limitations of windows, I have to split the routers across two seperate processes. Chewing up that much RAM in one process does not make Windows very happy at all. The computer I am running is my lenovo X60(6365CTO) laptop. It a dual core 1.6GHz with 2 GB RAM and even this gets a little sluggish running all eight of the required routers.

The batch files you will need are elsewhere on the site.

autostart = False
[localhost:21274]
[[3640]]
image = c:/Dynamips/images/c3640-ik9o3s-mz.124-7.bin
idlepc = 0x60601ed0
[[3660]]
image = c:/Dynamips/images/c3660-ik9o3s-mz.124-13b.bin
idlepc = 0x613501a0
[[ROUTER coswa]]
model = 3640
ram = 192
slot0 = NM-16ESW
slot1 = NM-16ESW
fa0/1 = woswa fa0/11
fa0/2 = woswb fa0/11
fa0/13 = coswb fa0/13
fa0/14 = coswb fa0/14
fa1/7 = coswc fa1/7
fa1/8 = coroa fa0/0
#fa1/9 = TFTP SERVER
[[ROUTER coswb]]
model = 3640
ram = 192
slot0 = NM-16ESW
slot1 = NM-16ESW
fa0/1 = woswa fa0/12
fa0/2 = woswb fa0/12
[[ROUTER coswc]]
model = 3640
ram = 192
slot0 = NM-16ESW
slot1 = NM-16ESW
fa0/1 = woswa fa0/1
fa0/2 = woroa fa0/1
fa0/3 = woswb fa0/1
fa0/4 = worob fa0/1
fa1/9 = coroa fa0/1
[[ROUTER coroa]]
model = 3660
ram = 192
slot1 = NM-4T
s1/2 = coroa s1/3
[localhost:21273]
udp = 21274
[[3640]]
image = c:/Dynamips/images/c3640-ik9o3s-mz.124-7.bin
idlepc = 0x60601ed0
[[3660]]
image = c:/Dynamips/images/c3660-ik9o3s-mz.124-13b.bin
idlepc = 0x613501a0
[[ROUTER woroa]]
model = 3660
ram = 192
slot1 = NM-4T
s1/0 = coroa s1/0
s1/1 = worob s1/1
[[ROUTER woswa]]
model = 3640
ram = 192
slot0 = NM-16ESW
slot1 = NM-16ESW
[[ROUTER worob]]
model = 3660
ram = 192
slot1 = NM-4T
s1/0 = coroa s1/1
[[ROUTER woswb]]
model = 3640
ram = 192
slot0 = NM-16ESW
slot1 = NM-16ESW

Incidentally, this configuration file will work equally well for both the CCENT and ICND2 courses. Different running configs are required, but this .net file will work as the physical infrastructure for both courses.

By default, Windows has a 2 GB per process limit that (after including the memory used by the virtual router RAM, cygwin, libraries, and “scratch space”) you are bumping up against. 32-bit Linux has a 3 GB per process limit by default.

One workaround for this problem is to use the sparsemem option.

Another is to run multiple instances of Dynamips on the same system listening on different control ports like so:

On Windows:

Create two .cmd files: dynagen-1.cmd and dynagen-2.cmd. The contents of both can look something like:

DYNAGEN-1.CMD

@echo off
rem Launch a local copy of dynamips
set dynamips=%CD%\dynamips.exe
cd %TEMP%
start /belownormal /B /wait "Dynamips" "%dynamips%" -H 7200
pause

DYNAGEN-2.CMD

@echo off
rem Launch a local copy of dynamips
set dynamips=%CD%\dynamips.exe
cd %TEMP%
start /belownormal /B /wait "Dynamips" "%dynamips%" -H 7200
pause

On Linux/Unix:
nice dynamips –H 7200 &
nice dynamips –H 7201 &

The only issue is that the UDP NIOs that Dynagen picks to make the various connections will “collide” because Dynagen thinks they are different servers and therefore those UDP ports safe to re-use. The workaround is to use the new “udp” option to change the starting UDP port for NIOs on one of the servers. So the relevant sections would look something like this:
 
[localhost]      # Talk to the 1st dynamips process on the default port 7200
[[7200]]
[[ROUTER R1]]
f0/0 = R2 f0/0

[localhost:7201] # Talk to the 2nd dynamips process on port 7201
udp = 11000     # Change the base udp port to 11000 (the default is 10000)
[[7200]]
[[ROUTER R2]]

Okay, I admit it; I’m a Dynagen n00b! It’s sort of embarrassing, so to help save anyone the shame, I figure that I will document the process. To that end, I am planning to write a series of articles about my experiences with Dynagen.

For the un-initiated, Dynagen is an easier front end to the Dynamips Cisco Emulator. The good thing about Dynagen is that it simplifies the  construction of quite complex switching and routed networks by providing an easy to understand syntax to automate the connection of devices used.

Dynagen can be installed on both Windows and Linux platforms. From observed results, there is better performance on the Linux platform, however, this article will focus on the installation and operation in a Windows environment. From observed results on a Lenovo X60 Tablet (Core Duo CPU L2400 1.66 Ghz, 1.99GB RAM), it will happily run eight 3660 routers.

First thing’s first: getting Dynagen. The Dynagen website is simple and easy to use. In the picture below, all I need to do is click on the “Download” link to be taken to a sourceforge.net page. The release I am using at the moment is Dynagen 0.10.1 and Dynamips 0.2.8-RC1 Windows XP installer released on September 9, 2007.

The only dependency Dynagen has is Winpcap 4.0.  From the Winpcap site, ,”… it allows applications to capture and transmit network packets bypassing the protocol stack, and has additional useful features, including kernel-level packet filtering, a network statistics engine and support for remote packet capture.” The version I used is WinPcap 4.0.2 (current at March 6, 2008).

Once you have these two programs downloaded, install Winpcap and then the Dynagen installer. Both are point and click installations. Nice and easy. Here, though, we strike a small hurdle; Dynagen, by default, installs itself into the C:\Program Files\Dynamips directory. Once successfully installed you can safely move the directory elsewhere on a local hard drive. The significance? Between nvram files for routers and other required files, the Dynmips directory can blow out to a fairly significant chunk of the hard drive it’s on. And we all know how Windows loves having a full system drive, so I say why tempt fate?

Now you have WinPcap and Dynagen successfully installed!! In the next article, we’ll look at what to do with the program and some advanced installation configuration.

In the meantime, some excellent resources are out there on the internet. Sites like Hacki’s Forum, The Dynamips Blog are excellent for extra information. And then there’s the ever amazing Ardenpackeer.com.

Until next time, remain a virtual-oso!

I notice in the latest dynamips version 0.2.8-RC1 that flash filesystem is not working like before. If I perform and “erase flash” then reboot.. the flash file system comes back unformatted. Usually after performing an erase flash on the 3600, the size would change. This is not reflected on the files in the working directory.

This means that vlans are not stored across reboots in the 3640 routers with the switch module.

 The work around is thus:

(config)#vtp file nvram:vlan.dat
Setting device to store VLAN database at filename nvram:vlan.dat.
#dir nvram:
Directory of nvram:/
123  -rw-        1720       startup-config
124  ----          24       private-config
  1  -rw-           0       Index-table
  2  -rw-         720       vlan.dat

Dynagen is a front-end for use with the Dynamips Cisco router emulator. It uses an INI-like configuration file to provision Dynamips emulator networks. It takes care of specifying the right port adapters, generating and matching up those pesky NIO descriptors, specifying bridges, frame-relay, ATM switches, etc. It also provides a management CLI for listing devices, suspending and reloading instances, determining and managing idle-pc values, performing packet captures, etc.

http://dynagen.org and http://7200emu.hacki.at for the forums.

Other useful stuff: http://ardenpackeer.com/2007/07/07/how-to-set-up-a-basic-dynamips-lab-using-dynagen-part-1/

Supported hardware: http://7200emu.hacki.at/viewtopic.php?t=1831 and is listed below:

===========1700s===========
1710
    Slots: 0 (available)
    WIC slots: 0
    CISCO1710-MB-1FE-1E  (1 FastEthernet port and 1 Ethernet port, automatically used)
    Note, interfaces do not use a slot designation (e.g. “f0”)
1720
    Note, interfaces do not use a slot designation (e.g. “f0”)
1721
    Note, interfaces do not use a slot designation (e.g. “f0”)
1750
    Note, interfaces do not use a slot designation (e.g. “f0”)
1751

1760
    Slots: 0 (available)
    WIC slots: 2
    C1700-MB-1ETH (1 FastEthernet port, automatically used)

Cards:
    – WIC-1T (1 Serial port)
    – WIC-2T (2 Serial ports)
    – WIC-1ENET (1 Ethernet ports)

===========2600s===========
2610
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-1E (1 Ethernet port, automatically used)
2611
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-2E (2 Ethernet ports, automatically used)
2620
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-1FE (1 FastEthernet port, automatically used)
2621
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-2FE (2 FastEthernet ports, automatically used)
2610XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-1FE (1 FastEthernet port, automatically used)
2611XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-2FE (2 FastEthernet ports, automatically used)
2620XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-1FE (1 FastEthernet port, automatically used)
2621XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-2FE (2 FastEthernet ports, automatically used)
2650XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-1FE (1 FastEthernet port, automatically used)
2651XM
    Slots: 1 (available)
    WIC slots: 3
    CISCO2600-MB-2FE (2 FastEthernet ports, automatically used)

Cards:
    – NM-1E        (Ethernet, 1 port)
    – NM-4E        (Ethernet, 4 ports)
    – NM-1FE-TX    (FastEthernet, 1 port)
    – NM-16ESW     (Ethernet switch module, 16 ports)
    – NM-NAM
    – NM-IDS
    – WIC-1T (1 Serial port)
    – WIC-2T (2 Serial ports)

===========3600s===========
3660
    Slots: 6 (available)
3640
    Slots: 4
3620
    Slots: 2

Cards:
    – NM-1E        (Ethernet, 1 port)
    – NM-4E        (Ethernet, 4 ports)
    – NM-1FE-TX    (FastEthernet, 1 port)
    – NM-16ESW     (Ethernet switch module, 16 ports)
    – NM-4T        (Serial, 4 ports)
    – Leopard-2FE  (Cisco 3660 FastEthernet in slot 0, automatically used)

===========3700s===========
2691 (The 2691 is essentially a 3700 with 1 slot)
    Slots: 1 (available)
    WIC slots: 3
3725
    Slots: 2 (available)
    WIC slots: 3
3745
    Slots: 4 (available)
    WIC slots: 3

Cards:
    – NM-1FE-TX    (FastEthernet, 1 port)
    – NM-4T        (Serial, 4 ports)
    – NM-16ESW     (Ethernet switch module, 16 ports)
    – GT96100-FE   (2 integrated ports, automatically used)
    – NM-NAM
    – NM-IDS
    – WIC-1T (1 Serial port)
    – WIC-2T (2 Serial ports)

===========7200s===========
7206
    Slots: 6 (available)

Chassis types:
- STD
- VXR

NPEs:
- NPE-100
- NPE-150
- NPE-175
- NPE-200
- NPE-225
- NPE-300
- NPE-400
- NPE-G2 (Requires the use of NPE-G2 IOS images)

Cards:
- C7200-IO-FE  (FastEthernet, slot 0 only)
- C7200-IO-2FE (FastEthernet, 2 ports, slot 0 only)
- C7200-IO-GE-E  (GigabitEthernet interface only, Ethernet not currently functional, slot 0 only)
- PA-FE-TX (FastEthernet)
- PA-2FE-TX (FastEthernet, 2 ports)
- PA-4E (Ethernet, 4 ports)
- PA-8E (Ethernet, 8 ports)
- PA-4T+   (Serial, 4 ports)
- PA-8T (Serial, 8 ports)
- PA-A1 (ATM)
- PA-POS-OC3 (POS)
- PA-GE (GigabitEthernet)

Now all I need to do is find some IOS’s to install into it!!