Author
Post by pierky:
GNS3-Topology: Dual WAN connection on Cisco with Policy-based routing (PBR)
Written on April 14th, 2009 | 5 CommentsPierky put together a great exercise lab giving you a scenario and objective. The solution is in a DOC file in the archive package.
Scenario
We have a router connected to the ISP with two WAN connections:
- a Bronze link, with little bandwidth, on which we have a /30 subnet;
- a Gold link, with good performances, on which we have a /30 point-to-point subnet and an additional /24 routed subnet.
Note that ISP does not accept inbound traffic coming from a subnet that is not the one routed through the ingress interface: for example, we can’t send traffic from 1.1.1.0/24 out the Bronze link. One subnet, one link.
Core and 2 distribution blocks with L3 and L2 access switches
Written on March 7th, 2009 | 23 CommentsI just arranged this lab I used when I was studying for CCNP, I hope someone will find it useful.
We have a 2 distribution blocks network linked with the core layer; all elements are dual linked to the upstream layer for redundancy.
Block 1 has L3 access switches, running EIGRP as stub routers. Distribution routers send default route only to the access switches, and perform route aggregation toward core routers.
GNS3 Topology: MPLS VPN and Traffic Engineering
Written on January 23rd, 2009 | 28 CommentsAnother great lab from Pierky! Thanks!!
Routers P1, P2, P3 and P4 are in the core, just running OSPF in area 0. Each router has Loopback 0 with address 10.0.1.x (where x is the router number - P1 = 10.0.1.1).
Provider-edge routers PE1, PE2, PE3 and PE4 run OSPF in area 0 too; they have Loopback 0 with address 10.0.2.x.
Each PE routers has iBGP with P3, that is the route-reflector for AS 100.
All P and PE routers run LDP and are enabled for MPLS traffic-engineering.
GNS3 Topology: Multicasting - PIM Sparse-Mode - Anycast RP and MSDP - IPmc Lab
Written on November 22nd, 2008 | 9 CommentsHere is a very new lab to GNS3-Labs which we havent had before. We have plenty of OSPF, RIP and all the other common routing protocols and what not. Pierky has created this very cool lab featuring Multicast, PIM Sparse-mode, Anycast RP, MSDP. Hope you enjoy!
A source (Sender) needs to send a multicast ping to some receivers (R0, R1 and R2) on multicast group 239.1.2.3.
SW1 and SW2 have equal-cost paths trought C1 and C2; all links are L3, ip pim sparse-mode and EIGRP are running.
C1 and C2 are RPs (on Anycast IP 192.168.1.254) and MSDP peers:
hostname C1
!
interface Loopback0
ip address 192.168.1.254 255.255.255.255
!
interface Loopback1
ip address 192.168.1.1 255.255.255.255
!
ip msdp peer 192.168.1.2 connect-source Loopback1
ip msdp originator-id Loopback1hostname C2
!
interface Loopback0
ip address 192.168.1.254 255.255.255.255
!
interface Loopback1
ip address 192.168.1.2 255.255.255.255
!
ip msdp peer 192.168.1.1 connect-source Loopback1
ip msdp originator-id Loopback1
Before starting to ping the multicast group from Sender, I suggest you to ping R0, R1 and R2, to wake up connections.
Topology: Multilayer Switching in a “Campus” Network
Written on September 22nd, 2008 | 36 CommentsHey we have yet another great lab from a contributor. His name is Pierky and this is one great lab ..
You can also post your labs by sending them to me or by creating an account or making the post yourself and I will approve it once its complete ..
I’m working on CCNP BCMSN exam and I created this lab just to have something quite similar to a campus switched network.
There are 2 core switches, cross connected to 3 distribution switches (1 is both distrib and access) and 2 access switches, think to it as a 2 switching block. 3 routers work as PC.
A total of 10 routers are in the topology; with the right idle-pc it’s possible to have them working fine without burning the CPU!
Distribution switches have STP load balancing 2 Vlans, with 2 HSRP instances for the Vlans default gateways. You can (and have to) enable VTP on one of the switches, so that Vlans will propagate in the network (no global config mode, just vlan database mode). I put EIGRP on top of the core switches too, in order to enable “inter-blocks” routing.
I know, it’s bad to span L2 to the core, but I did it just to have a bigger spanning-tree diameter.
Lot of thinks are missing too, many can’t be done cause commands are not available on 3640.
Any comments or suggestions would be really appreciated!!
Subscribe to GNS3 Labs :: Cisco Router Simulator Network Topologies
