dynamips on mac
Tuesday, September 11th, 2007 | Dynamips-Links

dynamips on macIt runs pretty decently so far, just need to get couple things installed manually or via ports if available:
PLAIN TEXT
CODE:
- $ curl ‘http://www.mr511.de/software/libelf-0.8.6.tar.gz’ -o libelf.tgz
- Router>
I’ll admit getting it running on OS X isn’t as simple as on Windows, but I wouldn’t be able to sleep at night if I allowed someone to run dynamips in Windows on a Mac. Try this:
1. Download the dynamips binary from here: http://7200emu.hacki.at/download.php?id=324. Unzip it and copy it to /usr/local/bin (you might need to make this directory if it doesn’t exist). You will need to do this as root from the terminal.2. Download the latest Dynagen from here: http://7200emu.hacki.at/download.php?id=234. Unzip this and put it in Applications (or wherever you prefer).
3. Grab the Dynamips Launcher from here: http://7200emu.hacki.at/download.php?id=133 . Unzip it and also put it in Applications (or wherever.)
You can run dynamips by using the launcher. It uses sudo to run dynamips with root privileges so when it prompts for the password enter your current user password. Associate .net files with the Dynagen .app in Finder, then you can double-click your network files and they will launch in Dynagen just like in Windows.
Finally, you can download the free Terminal replacement “iTerm” and use the info in this post: http://7200emu.hacki.at/viewtopic.php?t=2054&highlight= to get all your consoles in a tabbed interface.
Let me know how this works out for you.
$ tar -zxf libelf.tgz
$ cd libelf-0.8.6
$ ./configure –prefix=/usr/local
$ make
$ sudo make install …
$ cd ../dynamips-0.2.5 && make
$ ./dynamips ../../c7200-ik9su2-mz.124-13b.bin
Cisco 7200 Simulation Platform (version 0.2.5-x86)
…
Cisco IOS Software, 7200 Software (C7200-IK9SU2-M), Version 12.4(13b), RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Wed 25-Apr-07 03:18 by prod_rel_team
Image text-base: 0×60008F10, data-base: 0×6258C180
…
I’ve not been able to make it work using the “gui launcher”.
The GUI Launcher required the dynamips file to be located
in a specific dir, but I couldn’t manage to put it there. So
I’ve developed an alternative (CLI) method that works well
for me.
I admit, it’s a “cluge” and it’s not “elegant” at all. But, it works.
All you need to do is create a shell script — within the
directory of you’re lab (or ‘.net’ file) — that points to
the dynamips/dynagen files.
This is how I start up a “rack” (or topology).
I create a shell script to start the dynamips server and
then start dynagen to call the “.net” file.
— Begin Script —
#!/bin/sh
# Start the dynamips server(s).
#
/Users/corp-mule/files/labs/dynamips-dynagen/labs-dynamips/dynamips -H 7200 &
# uncomment the following line if you need to run more than
# one dynamips server.
# Such as the Internetwork Expert labs.
#
#/Users/corp-mule/files/labs/dynamips-dynagen/labs-dynamips/dynamips -H 7201 &
# start dynagen
#
cd /Applications
Dynagen.app/Contents/MacOS/Dynagen /Users/corp-mule/dynamips-dynagen/labs-dynamips/vpn-bgp/vpn-bgp.net
— * —
After dynamips and dynagen is running and …I’ve started
the routers and switches, I telnet to them with the
following shell script.
— Begin Script —
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r1.sh
sleep 1
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r2.sh
sleep 1
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r3.sh
sleep 1
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r4.sh
sleep 1
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r5.sh
sleep 1
/Users/kelly/files/scripts/labs/shells/xterm/xterm-dynamips/r6.sh
sleep 1
# … etc.
— * —
This is what the shell scripts for each telnet session looks
like.
— Begin list —
# Each of the following lines are in seperate shell scripts.
#
# r1.sh
# r2.sh
# r3.sh
# r4.sh
# r5.sh
# r6.sh
# r7.sh
# r8.sh
# r9.sh
# r10.sh
# r11.sh
# r12.sh
# r13.sh
# r14.sh
# r15.sh
# r16.sh
#
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+1+4 -T r1 -e telnet localhost 2001 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+55+4 -T r2 -e telnet localhost 2002 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+108+4 -T r3 -e telnet localhost 2003 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+162+4 -T r4 -e telnet localhost 2004 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+216+4 -T r5 -e telnet localhost 2005 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+270+4 -T r6 -e telnet localhost 2006 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+324+4 -T r7 -e telnet localhost 2007 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+378+4 -T r8 -e telnet localhost 2008 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+378+4 -T r9 -e telnet localhost 2009 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+486+4 -T r10 -e telnet localhost 2010 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+540+4 -T r11 -e telnet localhost 2011 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+594+4 -T r12 -e telnet localhost 2012 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+648+4 -T r13 -e telnet localhost 2013 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+702+4 -T r14 -e telnet localhost 2014 &
xterm -fg white -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 85×54+756+4 -T r15 -e telnet localhost 2015 &
xterm -fg white -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 85×54+810+4 -T r16 -e telnet localhost 2016 &
# The following lines are duplicated from above, however
# the names of the devices are changed to match those of the
# Intenretwork Expert labs.
#
# ie-sw1.sh
# ie-sw2.sh
# ie-bb1.sh
# ie-bb2.sh
# ie-bb3.sh
#
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+324+4 -T ie-sw1 -e telnet localhost 2007 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+378+4 -T ie-sw2 -e telnet localhost 2008 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+432+4 -T ie-bb1 -e telnet localhost 2009 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+486+4 -T ie-bb2 -e telnet localhost 2010 &
xterm -fg green -bg black -fn -adobe-courier-medium-r-*-*-14-*-*-*-*-*-* -geometry 95×54+540+4 -T ie-bb3 -e telnet localhost 2011 &

PassGuide Cisco Training Materials Dumps
No comments yet.
