How to build a CCIE rack with GNS3 / dynamips — Part 4, connect the switches to the GNS3 server

So now its time to connect our server to the 4 switches in order to make the lab setup complete!

We here need now our straight through patch cables. I ordered them in red to get a little color in here. Cables were cheap: length = 2m, price 0,70$ each.

First what I did was to take 4 of them, then plugged them into the first 4-port NIC and used cable zippers to let it look good.

Then take the other two nic cards and do it the same.
After that we have to connect those 12 cables to the switches as they represent the router interfaces of R1-R6 and BB2 and BB3. You actually dont need to know which interface of which nic is name eth4, eth9 and so on. We can figure that out later using CDP :).

Then plug them into the switches. Here are the interfaces (you can see this also within the INE topology for the R&S rack):

R1 Fa0/0 – SW1 Fa0/1
R2 Fa0/0 – SW2 Fa0/2
R3 Fa0/0 – SW1 Fa0/3
R3 Fa0/1 – SW3 Fa0/3
R4 Fa0/0 – SW2 Fa0/4
R4 Fa0/1 – SW4 Fa0/4
R5 Fa0/0 – SW1 Fa0/5
R5 Fa0/1 – SW3 Fa0/5
R6 Fa0/0 – SW2 Fa0/6
R6 Fa0/1 – SW4 Fa0/6
SW1 Fa0/1 – R1 Fa0/0
SW1 Fa0/3 – R3 Fa0/0
SW1 Fa0/5 – R5 Fa0/0
SW2 Fa0/2 – R2 Fa0/0
SW2 Fa0/4 – R4 Fa0/0
SW2 Fa0/6 – R6 Fa0/0
SW2 Fa0/24 – BB2 Ethernet
SW3 Fa0/3 – R3 Fa0/1
SW3 Fa0/5 – R5 Fa0/1
SW3 Fa0/24 – BB3 Ethernet
SW4 Fa0/4 – R4 Fa0/1
SW4 Fa0/6 – R6 Fa0/1

So with some cable zippers again it looks very nice I think :).
Dont mind the yellow cables, those are connected to each switch to fa/10, I will use it for management purposes like software updates and config saving via to my mgmt vlan.

So one issue we have now. We dont know which NIC goes to what Switchport here. To know this I configured a .NET file where one can easily find out. Prerequisite is that the switches should have names from SW1 to SW4 (for CDP to identify it) and all ports are open and CDP is activated. I configured this one here:

P I C T U R E of GNS3

So as you can see I added 12 routers. If you would like to know how to enable clouds and bridge them with your network card, please lookup the GNS3 documentation or write a comment, then I maybe if it is wanted I will add a post for that. Each router is connected to a cloud. R1 to a cloud that is bridged to eth1, R2 to eth2 and so on. Startup all routers, enable CDP on the connected interface (in my case it is fa0/0) and just enter a “show cdp neihgbors” to be able to see which ethernet adapter is connected to which switchport. Write that down onto a table, we will need it for a later chapter. (The box at the top of the rack is my remote power switch, its covered in the next chapter!)

My ports are connected that way:
eth1 – SW2 Fa0/6
eth2 – SW4 Fa0/6
eth3 – SW2 Fa0/24
eth4 – SW3 Fa0/24
eth5 – SW4 Fa0/4
eth6 – Sw2 Fa0/4
eth7 – SW1 Fa0/5
eth8 – SW3 Fa0/5
eth9 – SW2 Fa0/2
eth10- SW3 Fa0/3
eth11- SW1 Fa0/1
eth12- SW1 Fa0/3

Here you can see my .NET file for the GNS3 topology. Feel free to import that one (just copy the text and put a .net extension behind it and have fun with it! (Remember you need the same IOS images etc. for that!)

GNS3.NET FILE:

autostart = False
[127.0.0.1:7206]
workingdir = /tmp
udp = 10600
[[3725]]
image = /home/mwirth/c3725-adventerprisek9-mz.124-15.T14.bin
ram = 256
idlepc = 0x6026be14
ghostios = True
idlemax = 100
[[ROUTER R4]]
model = 3725
console = 4014
aux = 2103
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r4.txt
wic0/0 = WIC-2T
s0/0 = FRSW 3
s0/1 = R5 s0/1
f0/0 = nio_gen_eth:eth6
f0/1 = nio_gen_eth:eth5
x = 357.46399751
y = 53.0904972998
[[ROUTER R5]]
model = 3725
console = 4015
aux = 2104
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r5.txt
wic0/0 = WIC-2T
s0/0 = FRSW 2
s0/1 = R4 s0/1
f0/0 = nio_gen_eth:eth7
f0/1 = nio_gen_eth:eth8
x = 326.210244843
y = 232.558441227
[[FRSW FRSW]]
1:102 = 6:201
1:103 = 7:301
1:104 = 3:401
1:105 = 2:501
1:113 = 8:311
2:501 = 1:105
2:502 = 6:205
2:503 = 7:305
2:504 = 3:405
2:513 = 8:315
3:401 = 1:104
3:402 = 6:204
3:403 = 7:304
3:405 = 2:504
3:413 = 8:314
4:51 = 5:51
4:100 = 5:100
4:101 = 5:101
4:201 = 5:201
4:301 = 5:301
4:401 = 5:401
5:51 = 4:51
5:100 = 4:100
5:101 = 4:101
5:201 = 4:201
5:301 = 4:301
5:401 = 4:401
6:201 = 1:102
6:203 = 7:302
6:204 = 3:402
6:205 = 2:502
6:213 = 8:312
7:301 = 1:103
7:302 = 6:203
7:304 = 3:403
7:305 = 2:503
8:311 = 1:113
8:312 = 6:213
8:314 = 3:413
8:315 = 2:513
1 = R1 s0/0
2 = R5 s0/0
3 = R4 s0/0
4 = BB1 s0/0
5 = R6 s0/0
6 = R2 s0/0
7 = R3 s1/0
8 = R3 s1/1
x = -174.345360413
y = 39.0179537627
[127.0.0.1:7207]
workingdir = /tmp
udp = 10000
[[3725]]
image = /home/mwirth/c3725-adventerprisek9-mz.124-15.T14.bin
ram = 256
idlepc = 0x6026be14
ghostios = True
idlemax = 100
[[ROUTER R1]]
model = 3725
console = 4011
aux = 2114
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r1.txt
wic0/0 = WIC-2T
wic0/1 = WIC-1T
wic0/2 = WIC-1T
s0/0 = FRSW 1
s0/1 = R3 s1/2
f0/0 = nio_gen_eth:eth11
x = 15.0832611207
y = -262.416305603
[[ROUTER R2]]
model = 3725
console = 4012
aux = 2116
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r2.txt
wic0/0 = WIC-2T
wic0/1 = WIC-1T
wic0/2 = WIC-1T
s0/0 = FRSW 6
s0/1 = R3 s1/3
f0/0 = nio_gen_eth:eth9
x = -187.149278299
y = -135.13708499
[[ROUTER R3]]
model = 3725
console = 4013
aux = 2112
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r3.txt
wic0/0 = WIC-1T
wic0/1 = WIC-1T
wic0/2 = WIC-1T
f0/0 = nio_gen_eth:eth12
f0/1 = nio_gen_eth:eth10
slot1 = NM-4T
s1/0 = FRSW 7
s1/1 = FRSW 8
s1/2 = R1 s0/1
s1/3 = R2 s0/1
x = 272.470129472
y = -188.87720036
[127.0.0.1:7205]
workingdir = /tmp
udp = 10500
[[3725]]
image = /home/mwirth/c3725-adventerprisek9-mz.124-15.T14.bin
ram = 256
idlepc = 0x6026be14
ghostios = True
idlemax = 100
[[ROUTER R6]]
model = 3725
console = 4016
aux = 2105
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/r6.txt
wic0/0 = WIC-2T
s0/0 = FRSW 5
f0/0 = nio_gen_eth:eth1
f0/1 = nio_gen_eth:eth2
slot1 = NM-1FE-TX
x = 74.4802307403
y = 249.529003975
[[ROUTER BB3]]
model = 3725
console = 4019
aux = 2106
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/bb3.txt
wic0/0 = WIC-2T
s0/0 = BB1 s0/1
f0/0 = nio_gen_eth:eth4
x = -365.340187157
y = 296.198051534
[[ROUTER BB2]]
model = 3725
console = 4018
aux = 2107
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/bb2.txt
f0/0 = nio_gen_eth:eth3
x = -195.634559673
y = 214.173664916
[[ROUTER BB1]]
model = 3725
console = 4017
aux = 2108
cnfg = /home/mwirth/Wuala/Networking/GNS/BASECONFIG/bb1.txt
wic0/0 = WIC-1T
wic0/1 = WIC-1T
wic0/2 = WIC-1T
s0/0 = FRSW 4
s0/1 = BB3 s0/0
x = -390.79603128
y = 19.0121933088
[GNS3-DATA]
m11 = 0.707106781187
m22 = 0.707106781187
[[Cloud S3Fa5]]
x = 351.835136524
y = 377.950360213
connections = R5:f0/1:nio_gen_eth:eth8
[[Cloud S3Fa24]]
x = -591.445309579
y = 230.872149726
hx = 38.1005050634
hy = -37.7279220614
connections = BB3:f0/0:nio_gen_eth:eth4
[[Cloud S1Fa5]]
x = 511.641269072
y = 280.369624409
connections = R5:f0/0:nio_gen_eth:eth7
[[Cloud S1Fa3]]
x = 82.399494937
y = -383.87720036
connections = R3:f0/0:nio_gen_eth:eth12
[[Cloud S1Fa1]]
x = -109.84105371
y = -390.078210486
connections = R1:f0/0:nio_gen_eth:eth11
[[Cloud S2Fa6]]
x = 158.087878479
y = 379.364573775
connections = R6:f0/0:nio_gen_eth:eth1
[[Cloud S2Fa4]]
x = 510.22705551
y = -61.8700576851
connections = R4:f0/0:nio_gen_eth:eth6
[[Cloud S2Fa2]]
x = -285.827993849
y = -277.769552622
connections = R2:f0/0:nio_gen_eth:eth9
[[Cloud S4Fa4]]
x = 522.954977571
y = 161.57568517
connections = R4:f0/1:nio_gen_eth:eth5
[[Cloud S4Fa6]]
x = -66.7720779386
y = 380.778787338
connections = R6:f0/1:nio_gen_eth:eth2
[[Cloud S3Fa3]]
x = 473.457502888
y = -237.232539419
connections = R3:f0/1:nio_gen_eth:eth10
[[Cloud S2Fa24]]
x = -271.833044483
y = 401.991990773
connections = BB2:f0/0:nio_gen_eth:eth3

Advertisements

About markus.wirth

Living near Limburg in Germany, working as a Network Engineer around Frankfurt am Main.
This entry was posted in Part 4 and tagged , , , , , , , , , , , , , , , , , , . Bookmark the permalink.

24 Responses to How to build a CCIE rack with GNS3 / dynamips — Part 4, connect the switches to the GNS3 server

  1. ds says:

    The cabling looks good, unusual for a lab but justified as you aligned your topology to INE workbooks.

    The yellow cables connected to the switches made me curious Could you describe the management solution you implemented for updating software and saving configs in more detail?

  2. markus.wirth says:

    Hi!
    Its not that complex one might think. Its just a routed port on each switch in the subnet of my home network 192.168.1.0/24 and I put/get the configs of the switches and can (if I like to) monitor them via snmp. Thats all. Its just to have IP connectivity to the machines so that I dont have to run in the basement everytime I need to save the config to file.
    Regards!

  3. sheno says:

    dear thank you too much for your great explanation . but i get confused you said first that

    R3 Fa0/0 – SW1 Fa0/3
    R3 Fa0/1 – SW3 Fa0/3

    its ok according to ine topology

    but after that you said we will bridge every router binding to an ethernet card via cloud

    so R1 is linked to ether 1 soon… and R3 is linked to ethernet card 3

    here i get confused because i note that R3 has a tow link one to switch 1 and the other to switch 3

    so i was thinking that we have to link it with two cloud and every cloud represent an ethernet card in order to be able connect the R3 to the two switches SW1 AND SW3
    plz try to expalin it clearly to me because i confused
    ****************

    i read in the gns3 site there is some technology called the breakout sever
    but i didnt see it in your explanation

    i got confused too

    sorry because of my many question

    thank u too much

    • markus.wirth says:

      Hi sheno!
      Well good question…easy answer here. The eth3 for example is a linux interface card name that is physically (really) cabled to the interface the ine topology recommends (this can be fa0/1 of SwitchX).
      Hope this clears it up a little!
      If not just tell me.

      Regards!
      Markus

  4. Yes, you define the cloud as the connection to the physical interface.
    You then connect the router interface to that physical interface

    So, each interface-to-interface connection connects to a different cloud.

    I made a topology that was overly complex:
    that is, I used a linux server to do the backbone routers and connect to the switches, then run a remote dynamips server, to handle the other routers.

    Surprisingly, it works.
    not surprisingly, it is a minor hassle, as I had Windows XP for the remote hosts … let’s just say that next time I build a setup, I’ll just put it all on one machine, and call it a day.

    Also, it turned out I needed to test out some things, so my remote dynamips servers then became remote windows server boxes, and I’m now just looking to upgrade my main dynamips server (due to hardware limitations, it didn’t support enough RAM to run all the routers itself, and was hardware capped at 1 GB RAM … yes, it’s THAT old … need to upgrade it.

    Also, IOU works, but there are so many legal issues surrounding it.

    Heck, even “Cisco” uses GNS3:

    http://www.cisco.com/en/US/tech/tk872/technologies_configuration_example09186a0080b8a116.shtml

  5. 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 … 😀
    ## 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

  6. sheno says:

    actually dear markus i still confused

    because the eth3 ( which resemble the R3 ) U SAID ITS connected to SW2 Fa0/24

    but in the ine topology the R3 is connected to the sw1 and sw3

    so i dont understand

    i will be thankful to u for make it clear to me
    thank you alot

  7. markus.wirth says:

    Hi!
    You were right! The.net file I posted was an old one with the wrong ports. I updated the post with the correct one. Do you now come more clear with it?
    Thanks for seeing the error here!
    Regards!
    Markus

  8. sheno says:

    i think i am stupied but i will tell u what i got

    first of all i see that every Router interface in (gns3) inorder to connect to the real switch so it must connect to a cloud .
    and this cloud will represent a physical network card

    so for instance
    R6 has a 2 interface are connecting to a 2 switch so we need to connected them to a 2 cloud and link the 2 cloud with 2 different physiacl network card and then take acable from those network card and link it to the 2 switch so lets suppose that i linked the R6 fa0/0 with acloud (physical network card 1)and then coonect this network card 1 (starightthrough cable) to sw2 fa0/6.

    and after that R6 fa0/1 with acloud (physical network card 2)and then coonect this network card 2 (starightthrough cable) to sw4 fa0/6. right ?

    if it right thnks alot if i was mistaken correct me
    ******************************************************************
    the second point am i need to take this net file
    because actually i dont know how to use it
    coz i used to use gns3 directly no any dynamps net file
    so is it ok?
    but i see both of u markus and lewis are used a net file
    so i dont know what should i do

  9. markus.wirth says:

    Hi sheno!

    first of all i see that every Router interface in (gns3) inorder to connect to the real switch so it must connect to a cloud .
    and this cloud will represent a physical network card
    >> CORRECT!

    so for instance
    R6 has a 2 interface are connecting to a 2 switch so we need to connected them to a 2 cloud and link the 2 cloud with 2 different physiacl network card and then take acable from those network card and link it to the 2 switch so lets suppose that i linked the R6 fa0/0 with acloud (physical network card 1)and then coonect this network card 1 (starightthrough cable) to sw2 fa0/6.
    >> I dont understand the thing with the “2 interface”, “2 switch” etc. Usually you connect the interface of a GNS router to a cloud. Before doing this you configure the cloud (sorry that path is still missing in my blog due to time issues by myself and studying) to be bridged with an ethernet card lets say eth1. This eth1 card you connect physically with a straight through cable you your real geal Switch hanging in your rack.

    ******************************************************************
    the second point am i need to take this net file
    because actually i dont know how to use it
    coz i used to use gns3 directly no any dynamps net file
    so is it ok?
    >> When you use gns3 you also use dynamips. GNS3 is only a graphical interface for dynamips. The .net file maybe needs to be tuned for your machine as you have different CPU and ram probably. So the idlepc values may not match. I can give you the advice to setup a topology withing gns3 and then take a look at the .net file you saved and try to understand how it works. If you dont get it…come back here or at ieoc.com and we discuss it :).

    HTH!
    Regards!
    Markus

  10. sheno says:

    thank you dear for your great explanation now thx god i understand
    thank u dear markus

  11. shane says:

    Hi Markus,

    I’ve followed your guide and used Ubuntu 12.04 but I am having issues – apparently with dot1q.
    R6 is configured with 2 subinterfaces that are trunked to the physical switches.
    MTU of quad nics is set to 8100 (max the system will allow me) and I have tied both NIO options with the same result.

    This link works while not tagged, but while tagged the packet is not even shown in a tcpdump capture.

    Did you face this issue? Any ideas?

  12. markus.wirth says:

    Hi!
    What type of cards did you use? Others than DFE cards of DLINK?
    I guess so as you changed the MTU to a high value.
    Regards!
    Markus

    • shane says:

      Hi Markus,

      I’m using the same cards as you – although I also have Sun cards (which I dont use – same issue with 12.04, I thought it was the cards!).

      Anyway, after installing Debian it works perfect. Something has been changed in Ubuntu 12.04 I think.

      Thanks for the response and happy labbing!

  13. Senthil says:

    Hi Guys, i was just wondering. Can we have one cloud for one switch and add multiple physical interfaces (ports) to it instead? thats what i did. i just started setting up my lab. i was wondering it would be an issue in the future. As opposed to 1 cloud per interface.

    Thanks for this Markus

  14. EdwinBar says:

    I like and know it!I will share my experiences with you how I started with the rack.
    CCIE Rack Rental

  15. Stepan says:

    thanks for gns topology!!

  16. HBK says:

    Dear Markus,
    Thanks alot for your topology and the nice explanation. These days I am trying to gether equipment and have build a pc with Quad nics and got 2 3550 switches. I havent setup the INE topology yet as the equipment is not complete however I ran into a couple of issues with Quad Nics. As far as i think these are related to linux 12.04 but anyways im not a linux guy so I thought i should ask you:
    1. When I am connecting my 3550 to my onboard NIC..everything works as expected.
    2. When I m connecting my 3550 with anyport on any QuadNic, the ports(Switchport and QuadNIc port) are not coming up. (just simple cable connection not using any topology or GNS3)
    3. I connected my onboard nic with any of the quad nic port and they become up.
    Can you please tell me what I am doing wrong as I tried everything to figure it out but still the ports are not coming up when I m connecting them to switches.

  17. CarbonCobi says:

    Nice offer ! I think this kind of posting is much more helpful for prospective buyer. I like it.
    CCIE Service Provider Rack Rental

  18. Jack says:

    Hi
    Good idea ,I have already follow your way and made a CCIE rack . One question could you tell me , When I implement a router-on-a-stick configuration on f0/0 of R1 (gns3) , creat new sub ethernet f0/0.10 , encapsulation dot1q 10 ,setup IP address 30.30.10.1 . F0/0 port has connected
    g1/0/1 of SW1 (3750X). The g1/0/1 port already has been made trunk port ,and creat vlan 10 port ,setup ip address 30.30.10.6 . But they can’t ping successfully each other . Same test on Physic router (2821 ) ,it’s working . I think this question is about router-on-a-stick question .Did you meet it also ?

  19. Jack says:

    change operation system is working ,before is win2008 ,now is Centos 6.4.

  20. encryptic says:

    I am in pursuit to building this CCIE LAB, I understand most of what I see here….I need to find out whith reference those gray cable have. I dont see any mention to what relevance there have here

  21. harry says:

    just stumbled on this info and read it with interest … i’m considering taking the ccie plunge and would absolutely prefer my own lab … i’m familiar with gns3 and it’s underlying components (dynamips, dynagen, qemu, etc.) … i’m very curious about the layer 2 and perhaps layer 3 configs of those switches … the layer 1 diagram, while very detailed, generates several questions in terms of how the various switchports and vlans along with spanning tree and SVIs are potentially configured … i’ve not seen the ine workbooks that go along with their lab diagram … perhaps they would answer those questions … any info, switch configs, logical layer 2 and/or 3 diagrams would be of interest to me and appreciated.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s