Setting Up Dynamips with Linux Central, and Windows Remote

I posted this on some guy's blog, here: http://chasingmyccie.wordpress.com/2012/01/28/how-to-build-a-ccie-rack-with-gns3-dynamips-part-4-connect-the-switches-to-the-gns3-server/

(Then, I realized, hey, this could be an article here!)

Here’s the topology file I used, might give you some ideas:

(I noticed I said to turn something off, but I put the setting on “true” hah, disregard)

How it works:
(1) stage directories, image files, and install dynamips/gns3 as required
(2) have script on Linux server to start the dynamips processes
(3) have script on Windows machines to start the remote dynamips processes
(4) run this topology file on the linux host

If you’ve enabled remote connect, you can remote to the box, and connect to the process there, OR … if you know the IP/port number combination, you can just telnet into the routers remotely.

Do … whatever works for you.

## Access server in GNS3
## IP Addresses
## 192.168.2.111 – Local Linux Server
## 192.168.2.33 – XP03
## 192.168.2.44 – X04
## Dynamips Ports
## Linux01: 7300, 7301 (for lab 3) 7400, 7401 (for lab 4)
## XPO3: 7200, 7201, 7202, 7203
## XP04: 7200, 7201, 7202, 7203
## UDP Ports:
## Linux01: 10300, 10350, 10400, 10450
## XP03: 13000, 13100, 13200, 13300
## XP04: 14000, 14100, 14200, 14300
## Directories:
## Linux01:
## working = /home/owner/gns3/working/lab3, /home/owner/gns3/working/lab4
## configs = /home/owner/gns3/configs/lab3, /home/owner/gns3/configs/lab4
## image = /home/owner/gns3/ios
## XP03:
## working = c:\gns3\working
## configs = c:\gns3\configs
## image = c:\gns3\ios
###########################################
##
## Do not automatically start the routers
##
#############################################
autostart = True

#################################
##
## This router keeps the switches up
## Switches must connect to at least one router
## Depending on your lab, this will not be a necessary step
## It worked OK for me, so I kept the switches
## Probably could have done without it, but once I got a working
## topology … you know how it is … :D
## Actually, the original idea was an access server, then I
## just decided I’d keep this one in every lab, to keep the switches
## “UP”
##
#######################

[192.168.2.111:7300]
workingdir = /home/owner/gns3/working/lab3
udp = 10300
[[3725]]
image = /home/owner/lab/ios/C3725-adventerprisek9-mz124-15.T7image.bin
ram = 128
idlepc = 0x60bf77a8
idlemax = 100
sparsemem = True
ghostios = True

[[ROUTER SK]]
model = 3725
console = 2000
cnfg = /home/owner/gns3/configs/lab3/SK.txt
slot 1 = NM-16ESW
f1/1 = R4F1 3
f1/2 = R3F1 3
f1/3 = R2F0 3
f1/4 = R1F0 3
f1/5 = R6F1 3
f1/6 = R5F1 3
f1/7 = R4F0 3
f1/8 = R3F0 3
f1/9 = BB2F0 3
f1/10 = BB3F0 3
f1/11 = R6F0 3
f1/12 = R5F0 3

#################################
##
## This server runs the switches that connect to the clouds.
##
#######################

[192.168.2.111:7301]
workingdir = /home/owner/gns3/working/lab3
udp = 10350

[[ETHSW R4F1]]
1 = access 1 nio_gen_eth:eth1
2 = access 1 R4 f0/1
3 = access 1 SK f1/1

[[ETHSW R3F1]]
1 = access 1 nio_gen_eth:eth2
2 = access 1 R3 f0/1
3 = access 1 SK f1/2

[[ETHSW R2F0]]
1 = access 1 nio_gen_eth:eth3
2 = access 1 R2 f0/0
3 = access 1 SK f1/3

[[ETHSW R1F0]]
1 = access 1 nio_gen_eth:eth4
2 = access 1 R1 f0/0
3 = access 1 SK f1/4

[[ETHSW R6F1]]
1 = access 1 nio_gen_eth:eth5
2 = access 1 R6 f0/1
3 = access 1 SK f1/5

[[ETHSW R5F1]]
1 = access 1 nio_gen_eth:eth6
2 = access 1 R5 f0/1
3 = access 1 SK f1/6

[[ETHSW R4F0]]
1 = access 1 nio_gen_eth:eth7
2 = access 1 R4 f0/0
3 = access 1 SK f1/7

[[ETHSW R3F0]]
1 = access 1 nio_gen_eth:eth8
2 = access 1 R3 f0/0
3 = access 1 SK f1/8

[[ETHSW BB2F0]]
1 = access 1 nio_gen_eth:eth9
2 = access 1 BB2 f0/0
3 = access 1 SK f1/9

[[ETHSW BB3F0]]
1 = access 1 nio_gen_eth:eth10
2 = access 1 BB3 f0/0
3 = access 1 SK f1/10

[[ETHSW R6F0]]
1 = access 1 nio_gen_eth:eth11
2 = access 1 R6 f0/0
3 = access 1 SK f1/11

[[ETHSW R5F0]]
1 = access 1 nio_gen_eth:eth12
2 = access 1 R5 f0/0
3 = access 1 SK f1/12

#################################
##
## Remote Windows XP Server
## Just finish connecting the interfaces
## and specifying the .bin files and idlepc
##
###############
##
## Hypervisor for FRS
##
###########################

[192.168.2.33:7200]
workingdir = c:\gns3\working
udp = 13000

[[3725]]
image = c:\gns3\ios\C3725-adventerprisek9-mz124-15.T7image.bin
ram = 128
idlepc = 0x60bf77a8
idlemax = 100
sparsemem = True
ghostios = True

[[ROUTER FRS]]
model = 3725
console = 2000
cnfg = c:\gns3\configs\FRS.txt
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = R1 s0/0
s0/1 = R2 s0/0
s0/2 = R3 s1/0
s0/3 = R3 s1/1
s0/4 = R4 s0/0
s0/5 = R5 s0/0
slot 1 = NM-4T
s1/0 = R6 s0/0
s1/1 = BB1 s0/0

# Hypervisor #1 R1, R2, and R3

[192.168.2.33:7201]
workingdir = c:\gns3\working
udp = 13100

[[3725]]
image = c:\gns3\ios\C3725-adventerprisek9-mz124-15.T7image.bin
ram = 128
idlepc = 0x60bf77a8
idlemax = 100
sparsemem = True
ghostios = True

[[ROUTER R1]]
model = 3725
console = 2001
cnfg = c:\gns3\configs\R1.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s0/0
s0/1 = R3 s1/2
f0/0 = R1F0 2

[[ROUTER R2]]
model = 3725
console = 2002
cnfg = c:\gns3\configs\R2.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s0/1
s0/1 = R3 s1/3
f0/0 = R2F0 2

[[ROUTER R3]]
model = 3725
console = 2003
cnfg = c:\gns3\configs\R3.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s1/0 = FRS s0/2
s1/1 = FRS s0/3
s1/2 = R1 S0/1
S1/3 = R2 S0/1
f0/0 = R3F0 2
f0/1 = R3F1 2

# Hypervisor #2 – R4, R5, and R6
[192.168.2.33:7202]
workingdir = c:\gns3\working
udp = 13200

[[3725]]
image = c:\gns3\ios\C3725-adventerprisek9-mz124-15.T7image.bin
ram = 128
idlepc = 0x60bf77a8
idlemax = 100
sparsemem = True
ghostios = True

[[ROUTER R4]]
model = 3725
console = 2004
cnfg = c:\gns3\configs\R4.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s0/4
s0/1 = R5 S0/1
f0/0 = R4F0 2
f0/1 = R4F1 2

[[ROUTER R5]]
model = 3725
console = 2005
cnfg = c:\gns3\configs\R5.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s0/5
s0/1 = R4 S0/1
f0/0 = R5F0 2
f0/1 = R5F1 2

[[ROUTER R6]]
model = 3725
console = 2006
cnfg = c:\gns3\configs\R6.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s1/0
f0/0 = R6F0 2
f0/1 = R6F1 2

# Hypervisor #3 – BB1,BB2, and BB3
[192.168.2.33:7203]
workingdir = c:\gns3\working
udp = 13300

[[3725]]
image = c:\gns3\ios\C3725-adventerprisek9-mz124-15.T7image.bin
ram = 128
idlepc = 0x60bf77a8
idlemax = 100
sparsemem = True
ghostios = True

[[ROUTER BB1]]
model = 3725
console = 2007
cnfg = c:\gns3\configs\BB1.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = FRS s1/1
s0/1 = BB3 S0/0

[[ROUTER BB2]]
model = 3725
console = 2008
cnfg = c:\gns3\configs\BB2.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
f0/0 = BB2F0 2

[[ROUTER BB3]]
model = 3725
console = 2009
cnfg = c:\gns3\configs\BB3.txt
slot 1 = NM-4T
wic 0/0 = WIC-2T
wic 0/1 = WIC-2T
wic 0/2 = WIC-2T
s0/0 = BB1 S0/1
f0/0 = BB3F0 2

[GNS3-DATA]

[[CLOUD R4F1-ETH1]]
connection = R4F1:1:nio_gen_eth:eth1

[[CLOUD R3F1-ETH2]]
connection = R3F1:1:nio_gen_eth:eth2

[[CLOUD R2F0-ETH3]]
connection = R2F0:1:nio_gen_eth:eth3

[[CLOUD R1F0-ETH4]]
connection = R1F0:1:nio_gen_eth:eth4

[[CLOUD R6F1-ETH5]]
connection = R6F1:1:nio_gen_eth:eth5

[[CLOUD R5F1-ETH6]]
connection = R5F1:1:nio_gen_eth:eth6

[[CLOUD R4F0-ETH7]]
connection = R4F0:1:nio_gen_eth:eth7

[[CLOUD R3F0-ETH8]]
connection = R3F0:1:nio_gen_eth:eth8

[[CLOUD BB2F0-ETH9]]
connection = BB2F0:1:nio_gen_eth:eth9

[[CLOUD BB3F0-ETH10]]
connection = BB3F0:1:nio_gen_eth:eth10

[[CLOUD R6F0-ETH11]]
connection = R6F0:1:nio_gen_eth:eth11

[[CLOUD R5F0-ETH12]]
connection = R5F0:1:nio_gen_eth:eth12


=======================

As always, you know where you can reach me, Lewis Lampkin, III, on Linked In: http://www.linkedin.com/in/lewislampkin (I usually accept invitations to connect ... Am I better than anyone else? [The answer is NO, if you're wondering.]

Or here on this website: http://www.lewislampkin.com


Comments

Post a Comment

Popular posts from this blog

Orphaned No More: Adopting AWS Lambda

Image
Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture is fully automated on AWS. The architecture is not ready for go-live. All actions so far are for a proof-of-concept that is presented to the Chief Technical Officer (CTO) for review. During the weekly team meeting, Ko (User Experience Lead) reports that his team has performed thousands of tests against the infrastructure, with moves, adds, and changes, and is not finding any issues in the application user interface. Woo (Infrastructure Lead) reports that there are hundreds of 'orphaned' files in the S3 bucket. (These files are considered 'orphaned' because they do not have corresponding records in the DynamoDB table.) Kim (Tech Lead) reports that there is not a trigger to delete the file from the bucket when a user is deleted from the DynamoDB database. Brady (Lawyer) reports that not deleting t...
Read more

Containing the Chaos! | A Three-Part Series Demonstrating the Usefulness of Containerization to HumanGov

Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture requires Amazon Elastic Compute Cloud (EC2) instances that are maintained by the HumanGov systems administrators. The systems administrators handle all the patching, operations, etc. Due to states wanting their data separate from each other, each state gets a separate set of EC2 instances, which means that as the application scales from one state up to 50 states, the systems administrators will have to patch 50x as many EC2 instances. The system administrators report that they have begun to schedule more and more overtime to handle the maintenance windows for updating the EC2 instances. The lead developer remarked that it was taking longer and longer for new application deployments to get rolled out as the infrastructure grew and more states came on board. By the way, the development environment does not have standa...
Read more

Ansible is the Answer! | A Three-Part Series Demonstrating the Usefulness of Ansible to HumanGov

This is a three (3) part series that demonstrates how Ansible can be useful/leveraged for configuring your infrastructure. The background story here is that HumanGov is a multi-tenant cloud application that requires that each of the fifty (50) states has its own separate infrastructure. The HumanGov Infrastructure Engineers are trying to figure out how they can get it done, and they are considering using Ansible to help them deploy the application. Part 1 sets up the base infrastructure for the scenario. The HumanGov Infrastructure Engineers are accustomed to using Terraform to efficiently deploy infrastructure, but they are not very experienced with Ansible. Part 1 of 3: HumanGov: Ansible is the Answer! | Terraform | AWS Cloud9 | AWS IAM | AWS EC2 | AWS DynamoDB | AWS S3 Part 2 attempts to setup HumanGov via a MANUAL process. Part 2 goes through the steps to MANUALLY install Python, Nginx AND application files as well as MANUALLY configuring the firewall in Ubuntu. After g...
Read more