Just a quick follow up on my previous post on using dynagen and GNS3. This one demonstrates the ability to mock up production networks for times when others are using your physical lab. Sure, you can’t emulate a 7600 or GSR, but the same principles apply for most situations (excluding platform specific configurations).
The above image is a GNS3 diagram of what I imported from my manually created dynagen network file. The has a mix of CE, PE, and P routers, as well as external AS routers. All routers are 7206s, excluding the CEs, which are 1721s.
As shown in the visio image above, we have a core OSPF area. The edges are separate areas. We also use MPLS explicit nulls in the LA and CR routers. Essentially, this is a redacted (IPs, auth keys, etc) configuration in use in a production service provider network.
You can download the visio here: Production Visio (VSD)
Configurations can be found here: Configurations (ZIP)
GNS/Dynagen configuration file: Confguration (TXT)
To telnet from router to router, use the following:
Password: cisco Enable: enable
The following ranges are what I use in this testbed.
- 172.16.0.0/24 – Range for Loopback IPs. This is what we use to source everything from in the P/PE routers (router-ids, bgp neighbors, etc)
- 10.0.0.0/24 – Range for WAN /31s
The routers are all configured with pretty thorough base config. It includes OSPF, BGP, MPLS, QoS, as well as basic Multicast (mvpn) and L3VPN configurations.
EASTCA1#sh ip bgp ipv4 mdt all sum BGP router identifier 172.16.0.101, local AS number 65500 BGP table version is 1, main routing table version 1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 172.16.0.30 4 65500 72 59 1 0 0 00:47:35 0 172.16.0.31 4 65500 71 58 1 0 0 00:47:35 0
I’ll be using this base configuration as I blog about technologies in future posts. Some of the topics I’ll be covering are (in no particular order):
- MPLS Traffic Engineering
- BGP Multihoming
- BGP Route Aggregation
- BGP Route Leaking
- MVPN Troubleshooting
- QoS Configuration and Troubleshooting
- IS-IS deployment
- IS-IS tuning
- IPv6
- OSPFv3
Stay tuned!
#1 by Ruben on January 23, 2010 - 4:40 am
Hello,
Thank you very much for sharing your mock up network!
I was wondering do you have config files for the AS routers? In the zip file linked in the post they are missing. I was just wondering.
Thanks!
#2 by jrowley on January 23, 2010 - 5:40 pm
Oops. Busted. Looks like I had forgot those configs.
I updated the post with links to updated configs and .net file. The ebgp stuff doesn’t dump a full table because I don’t need it. I mainly use it to test outbound announcements, aggregation, etc.
#3 by Ruben on January 24, 2010 - 1:22 pm
Awesome! Thanks for sharing !!
What are your system specs when running this simulation? Just wondering.. I’m having a bunch of ospf/bgp and ldp flapping when using the a low dead-interval, same thing with bgp.. I suspect my CPU is the culprit not sure yet
#4 by jrowley on January 24, 2010 - 4:08 pm
I’m running it on a dual Quad 1.6GHz Xeon with 8GB of ram. My load average is about 3.5 to 3.8
16:07:31 up 6 days, 20:56, 11 users, load average: 3.88, 3.60, 3.56
Have you tried adjusting the idle-pc settings? That might help out with the flaps.
#5 by Colby on February 3, 2010 - 8:30 pm
Why are you doing explicit null? The only reasoning I can find is the the preserve the markings. Is that why?
I asked Noah, but he was no help.:p
#6 by jrowley on February 7, 2010 - 8:16 pm
Sorry. Been recovering from some plague.
Yeah, we use it for qos. I can’t think of any other uses for it versus implicit null.
#7 by Colby on February 8, 2010 - 4:49 pm
Ok, thanks. Just wanted to make sure I wasn’t missing something cool.:)
Hope you feel better. We need more content!