Just another Cisco blog
Archive for April, 2010
RIP Lab #2
Apr 30th
This is the second and last RIP post I’ll be doing to prepare for the CCIE.
I’ve tried to include a lot in this one without making it too long. Here’s the topology:
(Click image for fullsize)
Click here for the initial configs
Here is task one:
1. Configure RIPv2 on all routers and advertise their directly connected interfaces. Ensure that these routers have full NLRI to all the loopback interfaces advertised into RIP. Ensure that all routers can ping all loopbacks. Configure RIP not to advertise on any interface by default.
Let’s go through the config:
R1(config)#router rip R1(config-router)# version 2 R1(config-router)# no auto-summary R1(config-router)# network 1.0.0.0 R1(config-router)# network 10.0.0.0 R1(config-router)# passive-interface default R1(config-router)# no passive-interface Serial0/0.102 R1(config-router)# no passive-interface Serial0/0.103 |
I’m only showing R1 here as the other routers will be nearly identical. First we enable RIP, configure the version, turn of auto-summary and configure our network statements. Then we use the “passive-interface default” command, which tells RIP that all interfaces are passive unless explicity configured otherwise. Last we configure the configure s0/0.102 and s0/0.103 NOT to be passive.
Guest Post On NF Blog
Apr 29th
I wrote a BGP Lab post on the Networking-Forum Blog. Here’s a preview:
Topology:
Tasks:
1. Configure the Oustside Border Router in AS 6500. Peer with ISP-1 and ISP-2. Ensure that the DMZ subnet is advertised to the internet.
2. Prevent AS 6500 from being used as a transit between ASes 1111 and 2222.
3. The link through ISP-1 is much faster than the link through ISP-2. Configure outgoing traffic to use ISP-1 as the primary, only use the link through ISP-2 if the primary link is down.
4. Configure incoming traffic to use the link through ISP-1 as the primary.
5. Ensure that NAT is setup to use both ISPs.
RIP Lab #1
Apr 27th
This is the first in a series of lab posts I’ll be doing to prepare for the CCIE.
Today’s lab is from Narbik’s Volume One workbook. It’s a RIPv2 lab with some tricks thrown in. Here’s the topology:
(Click image for fullsize)
Click here for the initial configs
Here is task one:
1. Configure RIPv2 on all routers and advertise their directly connected interfaces. Ensure that these routers have full NLRI to all the loopback interfaces advertised into RIP. Ensure that all routers can ping all loopbacks.
Let’s go through the config:
R1: R1(config)#router rip R1(config-router)#ver 2 R1(config-router)#no auto R1(config-router)#network 10.0.0.0 R1(config-router)#network 1.0.0.0 R2: R2(config)#router rip R2(config-router)#ver 2 R2(config-router)#no auto R2(config-router)#network 10.0.0.0 R2(config-router)#network 2.0.0.0 R3: R3(config)#router rip R3(config-router)#ver 2 R3(config-router)#no auto R3(config-router)#network 10.0.0.0 R3(config-router)#network 3.0.0.0 |
Looks pretty simple, but I’m sure you guys see that this won’t work correctly. Let’s look at R2 and R3′s routing tables:
R2#sh ip route
...
R 1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:15, Serial0/0
C 2.0.0.0/8 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, Serial0/0
R3#sh ip route
...
R 1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:06, Serial0/0
C 3.0.0.0/8 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, Serial0/0 |
Weekly Open Ended Question #11
Apr 26th
The answer to the tenth question has been added to the post.
Eleventh question:
What is PIM, what are its modes and how do they differ?
Please post answers in the comments (without Googling)!
Highlight for answer:
PIM is “Protocol Independent Multicast”. Its two modes are Dense and Sparse. Dense mode is a pudh model, while Sparse Mode is a pull model.
Plan of Attack
Apr 23rd
So I need to get some kind of structure together for lab study. This isn’t really my thing, I typically just wing it, but I don’t think that’s going to work as well for the lab, lol. Here’s the blueprint in its entirety:
| 1.00 | Implement Layer 2 Technologies | |
| 1.10 | Implement Spanning Tree Protocol (STP) | |
| (a) 802.1d | ||
| (b) 802.1w | ||
| (c) 801.1s | ||
| (d) Loop guard | ||
| (e) Root guard | ||
| (f) Bridge protocol data unit (BPDU) guard | ||
| (g) Storm control | ||
| (h) Unicast flooding | ||
| (i) Port roles, failure propagation, and loop guard operation | ||
| 1.20 | Implement VLAN and VLAN Trunking Protocol (VTP) | |
| 1.30 | Implement trunk and trunk protocols, EtherChannel, and load-balance | |
| 1.40 | Implement Ethernet technologies | |
| (a) Speed and duplex | ||
| (b) Ethernet, Fast Ethernet, and Gigabit Ethernet |
Recent Comments