Skip to main content

re-patching the lab for netmaster

In this topology I have 4 switches (2x3560 and 2x3550) and 6 virtual routers 3725 with Tbased IOS (pc with 12 network cards).I haven't tested the configuration against the netmasterclas workbooks,yet. Some features are missing on this platform or at least on this version of IOS like "object track" in ACL. The first visible difference is that there is no backbone routers as we used to have on INE labs.



This is my configuration:

"netmasterclass.net"

autostart = False
[localhost:7200]
workingdir = /home/nabromov/dynamips/working
udp = 11000

[[3725]]
image = /home/nabromov/dynamips/images/c3725-adventerprisek9-mz.124-15.T14.bin
ram = 256
nvram = 256
ghostios = True
idlepc = 0x60c06028


[[Router R1]]

model = 3725
console = 2001
# R1 e0/0 to SW1 fa0/1
f0/0 = NIO_linux_eth:eth0
# R1 f0/1 to SW2 fa0/1
f0/1 = NIO_linux_eth:eth1
s1/0 = FRSW 1
s1/1 = R3 s1/1


[[ROUTER R2]]
model = 3725
console = 2002
# R2 e0/0 to SW1 fa0/2
f0/0 = NIO_linux_eth:eth3
# R2 e0/1 to SW2 fa0/2
f0/1 = NIO_linux_eth:eth4
s1/0 = FRSW 2
s1/1 = FRSW 22

[[ROUTER R3]]
model = 3725
console = 2003
# R3 e0/0 to SW1 fa0/3
f0/0 = NIO_linux_eth:eth5
# R3 00/1 to SW2 fa0/3
f0/1 = NIO_linux_eth:eth6
s1/0 = FRSW 3

[localhost:7201]
workingdir = /home/nabromov/dynamips/working
udp = 11000

[[3725]]
image = /home/nabromov/dynamips/images/c3725-adventerprisek9-mz.124-15.T14.bin
ram = 256
nvram = 256
ghostios = True
idlepc = 0x60c06028

[[Router R4]]
model = 3725
console = 2004
# R4 e0/0 to SW1 fa0/4
f0/0 = NIO_linux_eth:eth7
# R4 e0/1 to SW2 fa0/4
f0/1 = NIO_linux_eth:eth8
s1/0 = FRSW 4
s1/1 = R5 s1/1

[[Router R5]]
model = 3725
console = 2005
# R5 e0/0 to SW1 fa0/5
f0/0 = NIO_linux_eth:eth9
# R5 e0/1 to SW2 fa1/5
f0/1 = NIO_linux_eth:eth10
s1/0 = FRSW 5


[[Router R6]]
model = 3725
console = 2006
# R6 f0/0 to SW1 fa0/6
f0/0 = NIO_linux_eth:eth11
# R6 f0/1 to SW2 fa0/6
f0/1 = NIO_linux_eth:eth12
s1/0 = FRSW 6
s1/1 = FRSW 66

[[FRSW FRSW]]



# R1 to FRSW

1:102 = 2:201

1:103 = 3:301

1:104 = 4:401

1:105 = 5:501

1:106 = 6:601

1:112 = 22:211

1:116 = 66:611



# R2 to FRSW

2:203 = 3:302

2:204 = 4:402

2:205 = 5:502

2:206 = 6:602

22:213 = 3:312

22:214 = 4:412

22:215 = 5:512

22:216 = 66:612



# R3 to FRSW

3:304 = 4:403

3:305 = 5:503

3:306 = 6:603

3:316 = 66:613



# R4 to FRSW

4:405 = 5:504

4:406 = 6:606

4:416 = 66:614

# R5 to FRSW

5:506 = 6:605

5:516 = 66:615


# R6 to FRSW

Popular posts from this blog

IOS on Unix (IOU)

source http://evilrouters.net/2011/01/18/cisco-iou-faq/ What is IOU? From the Cisco Engineering Education web site (a long time ago): IOS on Unix (IOU) is a fully working version of IOS that runs as a user mode UNIX (Solaris) process. IOU is built as a native Solaris image and run just like any other program. IOU supports all platform independent protocols and features. What operating systems does IOU run on? It is my understanding that, initially, IOU was Solaris (SPARC) only. Nowadays, however, there are also builds for OS X and Linux. Similar to dynamips, IOU allows you to build out a network topology on a computer, without the need for physical routers. This is useful for validating designs, proof-of-concept testing, and certification self-study. Is my system compatible with IOU? You will need to be running the operating system that your IOU image were built for, obviously. Other than that, there are no special requirements to run IOU. It is not very CPU- or memory-intensive, unlik...

Impressed with Poly brand for conference headphones

I previously used my Sony XM4 headphones for calls and initially found them versatile for multiple purposes. However, as my meetings extended to several hours, I noticed they became less comfortable. To address this, I upgraded to wireless headphones from Poly, which offer significantly improved comfort. While I don’t plan to use them for music listening, my initial impression is very positive.

Juniper IS-IS summary

##################################################################################################### ## ISIS ##################################################################################################### # Be sure to set family iso on the interface to be placed into ISIS set interfaces <interface> family iso # By default Junos places interfaces as L1/L2 # Default route leaking:         L1 to L2 - all internal routes         L2 to L1 - 0/0 route # L1/L2 will send the attached-bit down to L1 and it will act as a NSSA-like area.  When the L1 interface # receives the attached-bit it will inject a 0/0 route into the RIB point to the L1/L2 interface. # To disable the attached bit use: set protocols isis ignore-attached-bit # Be careful with the "interface all" command, as it may have some unexpected consequences such as trying # to establish a neighbor on your fxp0 management...