EIGRP

Tasks: Configure EIGRP AS 100 between R1,R2 and R3.
Advertise the networks 116.1.2.0/24 and 116.1.3.0/24, do not use the network statement.
Configure EIGRP between R1, R4 and R5. Include all Loopback Interfaces on R1 – R4

Redistribute Connected

Task: Advertise the networks 116.1.2.0/24 and 116.1.3.0/24, do not use the network statement.

To get the networks 116.1.2.0/24 and 116.1.3.0/24 into EIGRP without using the network statement, you will have to use redistribution. A way to do that is to redistributed connected into EIGRP and since we do not want to redistribute every connected interface into EIGRP (you can use the network statement for both other networks) we’ll use a route-map which only matches on those networks:

R2
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R2-Connected
 network 99.99.2.2 0.0.0.0
 network 116.1.123.2 0.0.0.0
 no auto-summary
!
ip prefix-list R2-fa0/0 seq 5 permit 116.1.2.0/24
!
route-map R2-Connected permit 10
 match ip address prefix-list R2-fa0/0

R3
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R3-Connected
 network 99.99.3.3 0.0.0.0
 network 116.1.123.3 0.0.0.0
 no auto-summary
!
ip prefix-list R3-fa0/0 seq 5 permit 116.1.3.0/24
!
route-map R3-Connected permit 10
 match ip address prefix-list R3-fa0/0

You can also use a match interface statement instead of matching with an ip prefix-list within the route-map.

EIGRP, Frame-Relay and split-horizon

Task: Configure EIGRP AS 100 between R1,R2 and R3.

To solve this task, you either have to configure EIGRP for unicast or assure that Frame-Relay transports multicast. I’ve chosen to configure Frame-Relay to transport multicast with the broadcast statement at the end of each frame-relay map statement so I did not have to do anything special within the EIGRP configuration.
Another thing to keep in mind, EIGRP is a distance vector protocol in some parts and uses the split-horizon rule. In that environment R1 will never advertise any routing information from R2 to R3 and vice versa due to the split horizon rule. You could use Frame-Rleay sub-interfaces on R1 but then you would not only use the physical interfaces as the Frame-Relay configuration task asks for. So the only way to pass those updates is to disable split-horizon on R1’s serial interface.

R1
interface Serial1/0
 ip address 116.1.123.1 255.255.255.0
 encapsulation frame-relay
 no ip split-horizon eigrp 100
 serial restart-delay 0
 frame-relay map ip 116.1.123.2 102 broadcast
 frame-relay map ip 116.1.123.3 103 broadcast
!
router eigrp 100
 network 0.0.0.0
 no auto-summary

R2
interface Serial1/0
 ip address 116.1.123.2 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 116.1.123.1 201 broadcast
 frame-relay map ip 116.1.123.3 201
!
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R2-Connected
 network 99.99.2.2 0.0.0.0
 network 116.1.123.2 0.0.0.0
 no auto-summary

R3
interface Serial1/0
 ip address 116.1.123.3 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 116.1.123.1 301 broadcast
 frame-relay map ip 116.1.123.2 301
!
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R3-Connected
 network 99.99.3.3 0.0.0.0
 network 116.1.123.3 0.0.0.0
 no auto-summary

Everything else within the EIGRP part is pretty straight forward, if not you can find the full configuration for every router at the end of this article.

EIGRP verification

A show ip route on R2 shows that it has all EIGRP routes in its routing table:

R2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     116.0.0.0/24 is subnetted, 4 subnets
C       116.1.123.0 is directly connected, Serial1/0
D EX    116.1.3.0 [170/2561024256] via 116.1.123.1, 00:24:17, Serial1/0
C       116.1.2.0 is directly connected, FastEthernet0/0
D       116.1.145.0 [90/2172416] via 116.1.123.1, 00:24:18, Serial1/0
     99.0.0.0/24 is subnetted, 5 subnets
D       99.99.1.0 [90/2297856] via 116.1.123.1, 00:24:18, Serial1/0
C       99.99.2.0 is directly connected, Loopback0
D       99.99.3.0 [90/2809856] via 116.1.123.1, 00:24:17, Serial1/0
D       99.99.4.0 [90/2300416] via 116.1.123.1, 00:24:18, Serial1/0

A side effect of the redistribute connected on R2 and R3 is that both of their interfaces are integrated as EIGRP external routes, it does not affect anything at the moment but keep that in mind for later.

OSPF

Tasks: Configure OSPF between R4,R5,R6. Do not use the neighbor statement to get the adjacencies up. Ensure that R6 is always the DR.
Configure OSPF between R6 and R7
Configure between R7 and R8
Include all Lo 0s from R5 – R7, ensure that they appear as /24 entries in the routing table.

OSPF and Frame-Relay

Task: Configure OSPF on R4,R5,R6. Do not use the neighbor statement to get the adjacencies up. Ensure that R6 is always the DR.

This task can be split in two parts:

• get the adjacencies up without using the neighbor statement
• Configure R6 to always be the DR on that circuit

OSPF uses the NONBROADCAST network type as default for Frame-Relay interfaces and hence you would have to configure the neighbors (at least on the hub) to get OSPF up and running. So to fulfill that requirement, you’ll have to change the network type for the interfaces. Basically the OSPF network types do not have to correlate to the L2 medium, we could configure NONBROADCAST on an Ethernet link on both sides with neighbor statements and it would still work. The network types “only” define how OSPF handles its timers (Hello, Dead and Wait), if a DR and a BDR are elected and how the updates are sent (unicast/multicast) which are all points that have to match to get a working OSPF adjacency. Its also not necessary that the network types on each router are the same, as long as their timers and DR/BDR settings match. So at the moment we could choose either the BROADCAST or the POINT-TO-MULTIPOINT network types. But since we need a DR/BDR election theres only one type left: BROADCAST, since the other one does not elect any DR/BDR.
The last part is easy, before OSPF forms its adjacencies, the Interfaces have to be configured for their DR priority (otherwise you would have to clear the OSPF process). The default is 1 for every interface, setting it to 0 (zero) on R4 and R5 will prevent them from getting elected as DR and setting the priority to 255 on R6 will assure that it will allways (well as long as we dont configure another router with 255) be the DR. During preparations for the CCIE Lab I was once told to min/max stuff like this, that’s why I set it to the maximum value possible on R6, leaving it to its default would do the same after the change to priority 0 on the other routers.

R4
interface Serial1/0
 ip address 116.1.156.4 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 116.1.156.5 406
 frame-relay map ip 116.1.156.6 406 broadcast
!
router ospf 1
 router-id 99.99.4.4
 log-adjacency-changes
 network 116.1.156.4 0.0.0.0 area 0

R5
interface Serial1/0
 ip address 116.1.156.5 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 116.1.156.4 506
 frame-relay map ip 116.1.156.6 506 broadcast
!
router ospf 1
 router-id 99.99.5.5
 log-adjacency-changes
 network 116.1.156.5 0.0.0.0 area 0

R6
interface Serial1/0
 ip address 116.1.156.6 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 255
 serial restart-delay 0
 frame-relay map ip 116.1.156.4 604 broadcast
 frame-relay map ip 116.1.156.5 605 broadcast
!
router ospf 1
 router-id 99.99.6.6
 log-adjacency-changes
 network 116.1.156.6 0.0.0.0 area 0

OSPF and Areas without a direct Backbone Area connection

Tasks:
Configure OSPF between R6 and R7
Configure between R7 and R8

OSPF between R6 and R7 is just a straight forward OSPF connection, nothing special about it. OSPF between R7 and R8 is not, as you probably already saw. OSPF areas always have to have a direct connection to the backbone area and well, area 78 doesnt have any connection to the backbone area so the rest of the network will never know about the routes from area 78 and later the ones from the RIP part until we connected area 78 to the backbone area. To connect it to the backbone area we basically got two options:

• OSPF virtual-link
• GRE-Tunnels

You can use both of them to get a full routing connectivty in that case, for the solution guide, I’ve taken the virtual-link path since its an OSPF tool. The virtual-link has to be configured between R6 (last router for the backbone area) and R7 (first router for area 78).

R6
interface FastEthernet0/0
 ip address 116.1.67.6 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.156.6 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 255
 serial restart-delay 0
 frame-relay map ip 116.1.156.4 604 broadcast
 frame-relay map ip 116.1.156.5 605 broadcast
!
router ospf 1
 router-id 99.99.6.6
 log-adjacency-changes
 network 116.1.67.6 0.0.0.0 area 67
 network 116.1.156.6 0.0.0.0 area 0

R7
interface Loopback0
 ip address 99.99.7.7 255.255.255.0
 ip ospf network point-to-point
!
interface FastEthernet0/0
 ip address 116.1.67.7 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 ip address 116.1.78.7 255.255.255.0
 duplex auto
 speed auto
!
router ospf 1
 router-id 99.99.7.7
 log-adjacency-changes
 area 67 virtual-link 99.99.6.6
 network 116.1.67.7 0.0.0.0 area 67
 network 116.1.78.7 0.0.0.0 area 78

R8
interface FastEthernet0/0
 ip address 116.1.78.8 255.255.255.0
 duplex auto
 speed auto
!
router ospf 1
 router-id 99.99.8.8
 log-adjacency-changes
 redistribute rip subnets
 network 116.1.78.8 0.0.0.0 area 78

OSPF and Loopback Interfaces

Task: Include all Lo 0s from R5 – R7, ensure that they appear as /24 entries in the routing table.

OSPF uses different network types for different interfaces types, the same goes for loopback interfaces, per default they are set to the loopback (what a wonder) network type. The special thing about a loopback network type is, that OSPF always does advertise its IP address as a host address (/32) no matter what kind of subnet mask we use:

R6#sh ip ospf int lo0
Loopback0 is up, line protocol is up
 Internet Address 99.99.6.6/24, Area 0
 Process ID 1, Router ID 99.99.6.6, Network Type LOOPBACK, Cost: 1
 Loopback interface is treated as a stub Host

R7#sh ip route 99.99.6.6
Routing entry for 99.99.6.6/32
 Known via "ospf 1", distance 110, metric 2, type intra area
 Last update from 116.1.67.6 on FastEthernet0/0, 00:02:20 ago
 Routing Descriptor Blocks:
 * 116.1.67.6, from 99.99.6.6, 00:02:20 ago, via FastEthernet0/0
 Route metric is 2, traffic share count is 1

So to get /24 for the loopback networks, you just have to change the network type to point-to-point. Cisco wont accept any other network type for a loopback Interface:

R6#sh run int lo 0
Building configuration...

Current configuration : 95 bytes
!
interface Loopback0
 ip address 99.99.6.6 255.255.255.0
 ip ospf network point-to-point

R6#sh ip ospf int lo0
Loopback0 is up, line protocol is up
 Internet Address 99.99.6.6/24, Area 0
 Process ID 1, Router ID 99.99.6.6, Network Type POINT_TO_POINT, Cost: 1
 Transmit Delay is 1 sec, State POINT_TO_POINT,
 Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
 oob-resync timeout 40
 Supports Link-local Signaling (LLS)
 Index 2/2, flood queue length 0
 Next 0x0(0)/0x0(0)
 Last flood scan length is 0, maximum is 0
 Last flood scan time is 0 msec, maximum is 0 msec
 Neighbor Count is 0, Adjacent neighbor count is 0
 Suppress hello for 0 neighbor(s)

R7#sh ip route 99.99.6.6
Routing entry for 99.99.6.0/24
 Known via "ospf 1", distance 110, metric 2, type intra area
 Last update from 116.1.67.6 on FastEthernet0/0, 00:01:55 ago
 Routing Descriptor Blocks:
 * 116.1.67.6, from 99.99.6.6, 00:01:55 ago, via FastEthernet0/0
 Route metric is 2, traffic share count is 1

OSPF verification

A show ip route on R4 shows that it has all OSPF routes in its routing table:

R4#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
 D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
 E1 - OSPF external type 1, E2 - OSPF external type 2
 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
 ia - IS-IS inter area, * - candidate default, U - per-user static route
 o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

 116.0.0.0/24 is subnetted, 4 subnets
O IA    116.1.67.0 [110/65] via 116.1.156.6, 00:20:40, Serial1/0
O IA    116.1.78.0 [110/66] via 116.1.156.6, 00:20:40, Serial1/0
C       116.1.145.0 is directly connected, FastEthernet0/0
C       116.1.156.0 is directly connected, Serial1/0
 99.0.0.0/24 is subnetted, 5 subnets
C       99.99.4.0 is directly connected, Loopback0
O       99.99.5.0 [110/65] via 116.1.156.5, 00:20:40, Serial1/0
O       99.99.6.0 [110/65] via 116.1.156.6, 00:20:40, Serial1/0
O IA    99.99.7.0 [110/66] via 116.1.156.6, 00:20:40, Serial1/0

RIPv2

Tasks: Configure RIP version 2 on R8 and R9, include all Loopback Interfaces on R9 and the Lo0 on R8.

Once again, nothing special here, just don’t forget to use the version 2 and no auto-summary commands.

R8
interface Loopback0
 ip address 99.99.8.8 255.255.255.0
!
interface FastEthernet0/1
 ip address 200.11.99.8 255.255.255.0
 duplex auto
 speed auto
!
router rip
 version 2
 network 99.0.0.0
 network 200.11.99.0
 no auto-summary

R9
interface Loopback0
 ip address 99.99.9.9 255.255.255.0
!
interface Loopback1
 ip address 200.172.5.9 255.255.255.0
!
interface Loopback2
 ip address 200.172.6.9 255.255.255.0
!
interface Loopback3
 ip address 200.172.7.9 255.255.255.0
!
interface Loopback4
 ip address 200.172.8.9 255.255.255.0
!
interface Loopback5
 ip address 200.172.9.9 255.255.255.0
!
interface Loopback6
 ip address 200.172.10.9 255.255.255.0
!
interface FastEthernet0/0
 ip address 200.11.99.9 255.255.255.0
 duplex auto
 speed auto
!
router rip
 version 2
 network 99.0.0.0
 network 200.11.99.0
 network 200.172.5.0
 network 200.172.6.0
 network 200.172.7.0
 network 200.172.8.0
 network 200.172.9.0
 network 200.172.10.0
 no auto-summary

RIP Verification

A show ip route on R9 shows, that it has all RIP routes in its routing table:

R8#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
 D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
 E1 - OSPF external type 1, E2 - OSPF external type 2
 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
 ia - IS-IS inter area, * - candidate default, U - per-user static route
 o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C    200.11.99.0/24 is directly connected, FastEthernet0/1
R    200.172.6.0/24 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1
 116.0.0.0/24 is subnetted, 7 subnets
C       116.1.78.0 is directly connected, FastEthernet0/0
R    200.172.7.0/24 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1
 99.0.0.0/24 is subnetted, 9 subnets
C       99.99.8.0 is directly connected, Loopback0
R       99.99.9.0 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1
R    200.172.8.0/24 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1
R    200.172.9.0/24 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1
R    200.172.10.0/24 [120/1] via 200.11.99.9, 00:00:19, FastEthernet0/1

Redistribution

Tasks: Configure mutual redistribution on R8 between RIPv2 and OSPF
Configure mutual redistribution on R4 and R5 between OSPF and EIGRP.
Ensure that R4 and R5 will not relearn routes advertised by R1 from OSPF.

Redistribution between RIP and OSPF

Task: Configure mutual redistribution on R8 between RIPv2 and OSPF

To get a mutual redistribution between RIPv2 and OSPF you’ll have to redistribute the routes from RIP into OSPF and from OSPF into RIP, thats all. The only thing worth to mention is to not forget the subnets keyword within the OSPF redistribution, otherwise OSPF will only redistribute major network addresses. In this case, every network from the 200 range would be redistributed while the loopback addresses from 99.0.0.0 wont.

R8
router ospf 1
 router-id 99.99.8.8
 log-adjacency-changes
 redistribute rip subnets
 network 116.1.78.8 0.0.0.0 area 78
!
router rip
 version 2
 redistribute ospf 1 metric 1
 network 99.0.0.0
 network 200.11.99.0
 no auto-summary

Redistribution between EIGRP and OSPF

Task: Configure mutual redistribution on R4 and R5 between OSPF and EIGRP.

Nothing special to add here, EIGRP asks to specify a default metric for the redistributed networks, which basically is something you can choose what you want but it is a good idea to make the metric as bad as possible, I’ll explain why in the next section. OSPF needs the subnets keyword again and then we got the mutual redistribution between both protocols on R4 and R5

R4
router eigrp 100
 redistribute ospf 1 metric 1 1 1 1 1500
 network 99.99.4.4 0.0.0.0
 network 116.1.145.4 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.4.4
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 116.1.156.4 0.0.0.0 area 0

R5
router eigrp 100
 redistribute ospf 1 metric 1 1 1 1 1500
 network 116.1.145.5 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.5.5
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 99.99.5.5 0.0.0.0 area 0
 network 116.1.156.5 0.0.0.0 area 0

Redistribution and Loops

Task: Ensure that R4 and R5 will not relearn routes advertised by R1 from OSPF.

What is going to happen here heavily depends on how you’ve set the EIGRP Metric for the routes redistributed from OSPF into EIGRP. If the metric for the distributed routes has been set worse enough, there wont be any issue for the reachability, if not the redistributed networks 116.1.2.0/24 and 116.1.3.0/24 wont be reachable on R4 to R9.
The issue here, no matter if the EIGRP metric is set worse enough or not is that either R4 or R5 will relearn those networks over OSPF. Simply due to the reason, that EIGRP external routes have an administrative distance of 170 while OSPF got an administrative distance of 110, no matter if the route is internal or external.
So lets say R4 redistributes those networks from EIGRP into OSPF, R4 then will advertise it through the OSPF domain, including R5. After R5 received the routes from OSPF with an AD of 110 from R4 and with an AD of 170 from R1, it will install the Routes from OSPF due to the better AD.

What is going to happen next now depends on the redistribution metric for EIGRP. If its set too good (better metric then the one from R1), both R1 and R4 will use R5’s advertisement for those routes and not the one to R1. And here we have our little loop no router will be able to ping 116.1.2.2 or 116.1.3.3.

R1#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560002816] via 116.1.145.5, 00:04:50, FastEthernet0/0
D EX    116.1.2.0 [170/2560002816] via 116.1.145.5, 00:04:50, FastEthernet0/0

R4#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560002816] via 116.1.145.5, 00:04:02, FastEthernet0/0
D EX    116.1.2.0 [170/2560002816] via 116.1.145.5, 00:04:02, FastEthernet0/0

R5#sh ip route | i 116.1.2.0|116.1.3.0
O E2    116.1.3.0 [110/20] via 116.1.156.4, 00:03:46, Serial1/0
O E2    116.1.2.0 [110/20] via 116.1.156.4, 00:03:46, Serial1/0

R1#ping 116.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 116.1.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

R7#ping 116.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 116.1.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

There wont be any loop if the redistribution metric for EIGRP has been set worse enough but still either R4 or R5 will relearn the route from OSPF, which is something the task asks to prevent.

R4#sh run | sec router eigrp
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 99.99.4.4 0.0.0.0
 network 116.1.145.4 0.0.0.0
 no auto-summary
<pre>R4#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560514816] via 116.1.145.1, 00:00:19, FastEthernet0/0
D EX    116.1.2.0 [170/2560514816] via 116.1.145.1, 00:00:19, FastEthernet0/0</pre>
R5#sh run | sec router eigrp
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 116.1.145.5 0.0.0.0
 no auto-summary

R5#sh ip route | i 116.1.2.0|116.1.3.0
O E2    116.1.3.0 [110/20] via 116.1.156.4, 00:10:58, Serial1/0
O E2    116.1.2.0 [110/20] via 116.1.156.4, 00:10:58, Serial1/0

R1#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560512256] via 116.1.123.3, 00:16:17, Serial1/0
D EX    116.1.2.0 [170/2560512256] via 116.1.123.2, 00:16:17, Serial1/0

R7#ping 116.1.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 116.1.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/108/128 ms

To solve this problem we got two tools:

• administrative distance manipulation
• route tagging

Manipulating the AD is the easier way for this task, since its only 1 command on each router. Route Tagging would imply to tag those routes on their entry point into the EIGRP domain and then again prevent them from reentering on R4 and R5.
One thing to mention here, it is not possible to change the AD for a set of external routes in EIGRP, even though you can configure it, it will not work (why ever, but there are several topics about that on the internet). So changing the AD on the OSPF side to something higher than 170 will do the trick.

R4
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 99.99.4.4 0.0.0.0
 network 116.1.145.4 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.4.4
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 116.1.156.4 0.0.0.0 area 0
 distance 171 0.0.0.0 255.255.255.255 EIGRP-Ext
!
ip access-list standard EIGRP-Ext
 permit 116.1.2.0 0.0.0.255
 permit 116.1.3.0 0.0.0.255

R5
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 116.1.145.5 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.5.5
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 99.99.5.5 0.0.0.0 area 0
 network 116.1.156.5 0.0.0.0 area 0
 distance 171 0.0.0.0 255.255.255.255 EIGRP-Ext
!
ip access-list standard EIGRP-Ext
 permit 116.1.3.0
 permit 116.1.2.0

R4#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560514816] via 116.1.145.1, 00:00:06, FastEthernet0/0
D EX    116.1.2.0 [170/2560514816] via 116.1.145.1, 00:00:07, FastEthernet0/0

R5#sh ip route | i 116.1.2.0|116.1.3.0
D EX    116.1.3.0 [170/2560514816] via 116.1.145.1, 00:00:19, FastEthernet0/0
D EX    116.1.2.0 [170/2560514816] via 116.1.145.1, 00:00:19, FastEthernet0/0

Testing the connectivity

To proof that the configuration works I’ve used the following TCL script and executed it on every router:

foreach LAB {
116.1.145.1
116.1.123.1
99.99.1.1
116.1.2.2
116.1.123.2
99.99.2.2
116.1.3.3
116.1.123.3
99.99.3.3
116.1.145.4
116.1.156.4
99.99.4.4
116.1.145.5
116.1.156.5
99.99.5.5
116.1.67.6
116.1.156.6
99.99.6.6
116.1.67.7
116.1.78.7
99.99.7.7
116.1.78.8
200.11.99.8
99.99.8.8
200.11.99.9
99.99.9.9
200.172.5.9
200.172.6.9
200.172.7.9
200.172.8.9
200.172.9.9
200.172.10.9
} {ping $LAB repeat 3 timeout 1}

Please do not forget to use tclsh before and tclquit after you executed the script.

Full Configuration

Following is every routers “full” (sanitized) configuration.

R1

interface Loopback0
 ip address 99.99.1.1 255.255.255.0
!
interface FastEthernet0/0
 ip address 116.1.145.1 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.123.1 255.255.255.0
 encapsulation frame-relay
 no ip split-horizon eigrp 100
 serial restart-delay 0
 frame-relay map ip 116.1.123.2 102 broadcast
 frame-relay map ip 116.1.123.3 103 broadcast
!
router eigrp 100
 network 0.0.0.0
 no auto-summary

R2

interface Loopback0
 ip address 99.99.2.2 255.255.255.0
!
interface FastEthernet0/0
 ip address 116.1.2.2 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.123.2 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 116.1.123.1 201 broadcast
 frame-relay map ip 116.1.123.3 201
!
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R2-Connected
 network 99.99.2.2 0.0.0.0
 network 116.1.123.2 0.0.0.0
 no auto-summary
!
ip prefix-list R2-fa0/0 seq 5 permit 116.1.2.0/24
!
route-map R2-Connected permit 10
 match ip address prefix-list R2-fa0/0

R3

interface Loopback0
 ip address 99.99.3.3 255.255.255.0
!
interface FastEthernet0/0
 ip address 116.1.3.3 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.123.3 255.255.255.0
 encapsulation frame-relay
 serial restart-delay 0
 frame-relay map ip 116.1.123.1 301 broadcast
 frame-relay map ip 116.1.123.2 301
!
router eigrp 100
 redistribute connected metric 1 1 1 1 1500 route-map R3-Connected
 network 99.99.3.3 0.0.0.0
 network 116.1.123.3 0.0.0.0
 no auto-summary
!
ip prefix-list R3-fa0/0 seq 5 permit 116.1.3.0/24
!
route-map R3-Connected permit 10
 match ip address prefix-list R3-fa0/0

R4

interface Loopback0
 ip address 99.99.4.4 255.255.255.0
!
interface FastEthernet0/0
 ip address 116.1.145.4 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.156.4 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 116.1.156.5 406
 frame-relay map ip 116.1.156.6 406 broadcast
!
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 99.99.4.4 0.0.0.0
 network 116.1.145.4 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.4.4
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 116.1.156.4 0.0.0.0 area 0
 distance 171 0.0.0.0 255.255.255.255 EIGRP-Ext
!
ip access-list standard EIGRP-Ext
 permit 116.1.2.0 0.0.0.255
 permit 116.1.3.0 0.0.0.255

R5

interface Loopback0
 ip address 99.99.5.5 255.255.255.0
 ip ospf network point-to-point
!
interface FastEthernet0/0
 ip address 116.1.145.5 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.156.5 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 0
 serial restart-delay 0
 frame-relay map ip 116.1.156.4 506
 frame-relay map ip 116.1.156.6 506 broadcast
!
router eigrp 100
 redistribute ospf 1 metric 1 300000 1 1 1500
 network 116.1.145.5 0.0.0.0
 no auto-summary
!
router ospf 1
 router-id 99.99.5.5
 log-adjacency-changes
 redistribute eigrp 100 subnets
 network 99.99.5.5 0.0.0.0 area 0
 network 116.1.156.5 0.0.0.0 area 0
 distance 171 0.0.0.0 255.255.255.255 EIGRP-Ext
!
ip access-list standard EIGRP-Ext
 permit 116.1.3.0
 permit 116.1.2.0

R6

interface Loopback0
 ip address 99.99.6.6 255.255.255.0
 ip ospf network point-to-point
!
interface FastEthernet0/0
 ip address 116.1.67.6 255.255.255.0
 duplex auto
 speed auto
!
interface Serial1/0
 ip address 116.1.156.6 255.255.255.0
 encapsulation frame-relay
 ip ospf network broadcast
 ip ospf priority 255
 serial restart-delay 0
 frame-relay map ip 116.1.156.4 604 broadcast
 frame-relay map ip 116.1.156.5 605 broadcast
!
router ospf 1
 router-id 99.99.6.6
 log-adjacency-changes
 area 67 virtual-link 99.99.7.7
 network 99.99.6.6 0.0.0.0 area 0
 network 116.1.67.6 0.0.0.0 area 67
 network 116.1.156.6 0.0.0.0 area 0

R7

interface Loopback0
 ip address 99.99.7.7 255.255.255.0
 ip ospf network point-to-point
!
interface FastEthernet0/0
 ip address 116.1.67.7 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 ip address 116.1.78.7 255.255.255.0
 duplex auto
 speed auto
!
router ospf 1
 router-id 99.99.7.7
 log-adjacency-changes
 area 67 virtual-link 99.99.6.6
 network 99.99.7.7 0.0.0.0 area 78
 network 116.1.67.7 0.0.0.0 area 67
 network 116.1.78.7 0.0.0.0 area 78

R8

interface Loopback0
 ip address 99.99.8.8 255.255.255.0
!
interface FastEthernet0/0
 ip address 116.1.78.8 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 ip address 200.11.99.8 255.255.255.0
 duplex auto
 speed auto
!
router ospf 1
 router-id 99.99.8.8
 log-adjacency-changes
 redistribute rip subnets
 network 116.1.78.8 0.0.0.0 area 78
!
router rip
 version 2
 redistribute ospf 1 metric 1
 network 99.0.0.0
 network 200.11.99.0
 no auto-summary

R9

interface Loopback0
 ip address 99.99.9.9 255.255.255.0
!
interface Loopback1
 ip address 200.172.5.9 255.255.255.0
!
interface Loopback2
 ip address 200.172.6.9 255.255.255.0
!
interface Loopback3
 ip address 200.172.7.9 255.255.255.0
!
interface Loopback4
 ip address 200.172.8.9 255.255.255.0
!
interface Loopback5
 ip address 200.172.9.9 255.255.255.0
!
interface Loopback6
 ip address 200.172.10.9 255.255.255.0
!
interface FastEthernet0/0
 ip address 200.11.99.9 255.255.255.0
 duplex auto
 speed auto
!
router rip
 version 2
 network 99.0.0.0
 network 200.11.99.0
 network 200.172.5.0
 network 200.172.6.0
 network 200.172.7.0
 network 200.172.8.0
 network 200.172.9.0
 network 200.172.10.0
 no auto-summary

Title: CCIE SP Lab Checklist

Author: Stephen Bowes

Version: 2.0

Date: February 2009

Abstract:

This is a compilation of notes, gotcha’s, pointers, etc from my research in preparation for my upcoming CCIE SP Lab exam which I have acquired over many years. Please feel free to notify me of more improved ways to those listed below and or errata through my CCIE blog at cciesplab.wordpress.com or by email at cciesp@rocketmail.com.

Points Scoring and Timings:

I am conscious of the number of candidates who have failed due to running out of time. There are a number of reasons for this, here they are and proposed solutions.

To this end my timing plan is as follows -> Total Time = 8 hours = 480 Minutes. Lab Points Total = 100 Points, allowing 30 minutes for opening moves [see below] and 50 minutes for checking, validation and verification at the end, gives me 400 minutes for configuration

=> 4 Minutes/Point.

Pre-Lab Actions:

1 Month:

Adjust your body to performing 8 hour labs – Stamina will be key – you will be no use to anyone if you get tired after 5 hours of labbing. With 1 month to go ensure you are not doing 4 hour mini-labs rather the longer ones.

1 Week:

Adjust your body clock to the lab time. In my case I work 11am-7pm GMT whereas the Lab Exam in Brussels starts at 0745. This is 0645 GMT so with a week to go I will be up, showered, and had breakfast and sitting at my desk at 0730 to start an 8 hour lab with lunch at 12 for 30 minutes. I need to be fully alert at 0745 on Lab Day.

Lab Exam Day:

• Get as much sleep as is feasible the night before, up, showered, breakfast complete and be at Cisco by 0730. I booked into the nearest hotel I could find 250m away so no reliance on transport, etc.
• Bring a number of layers of clothes in case the room is cool, bring ear plugs so that the 11 guys/girls typing next to you and also so that the CCIE Voice candidates testing faxes will not interfere with your concentration levels.
• Documentation Location is http://www.cisco.com/web/psa/products/index.html

Lab Action Plan: [Note: All times below are estimates and dependent on points values as per timing plan noted above]

Opening Moves: [30 Minutes: 0800->0830]

• After the proctor instructions, take a minute, calm yourself, open the booklet, read the exam end to end, visualise the Bridging/Switching, IGP, EGP, MPLS, etc.
• Draw a personalised diagram of the topology – Note: This is a talking point, some do, some don’t, and I think it’s advantageous especially from an IP/Interface perspective.
• Ignore the rush of the other candidates typing or the urge to get started.
• Create a point checklist on the rough paper provided. Here is my example.

Troubleshooting: [15 Minutes: 0830->0845]

A number of faults may have been entered into the pre-configured devices. Check your SecureCRT software – can you see each of the devices? Reload each device, look for any hardware errors on boot-up, now is the time to spot this, not 11am.

As any issues could have been introduced check everything, IP Addresses matching Interfaces, subnet masks, FR DLCI’s, FR Inverse-Arp, pre-defined VLAN’s, VTP Modes on 3550’s, watch any pre-defined configurations configured on correct interfaces, ATM configurations, NSAP, IP, etc, etc.

I am not an Alias guy but now would be the time to do this, type these into notepad and cut & paste onto the routers ‘show run | b Se’ – Remember for large or repetitive configurations such as BGP, use notepad and then copy and paste.

¨ Bridging & Switching:

Frame-Relay: [15 Minutes: 0845->0900]

• Use your diagram to draw out the FR Topology
• Configure Router by router not interface by interface
• Use [1] shut [2]enc frame-relay [3] no frame inverse-arp [4] no shut.
• Decide to use either frame-relay map or use sub-interfaces
• Ping from spoke to spoke if possible to validate.
• Extra mapping required if required to ping your own interface
• If PPP over FR, then always create VT first, user/password
• Save, reload, and then verify all working.
• FRTS – Know your CIR=Bc x 1000Tc; Be=(AR-CIR) x Tc/1000.
• DocCD Location => Main URL = http://www.cisco.com/web/psa/products/index.html

– Cisco IOS SW Release 12.4 Family – 12.4 Mainline – Configuration Guides – Cisco IOS Wide-Area Networking Configuration Guide, Release 12.4.

• Verification Tools – ping, show frame-relay map, show int virtual-template, show int virtual-access, show traffic-shape, show interfaces serial, show frame-relay lmi, show frame-relay pvc, clear frame-relay inarp, clear interface, debug serial interface, debug frame-relay lmi, debug frame-delay events, debug frame-relay packets

=> Golden Moment: Frame-Relay is the spinal cord of the inter-network, it must be 100% <=

Switching: [30 minutes: 0900->0930]

• Create VLAN’s as per instruction
• VTP Modes
• Trunking
• Access Ports
• Security/Other Requirements
• Ping vlan by vlan. Select only one device and ping all other on a specific vlan.
• No need to ping from multiple interfaces on the same vlan.
• Don’t wait for Arp resolution!
• If naming something, type it exactly as specified – Ref: Narbik
• Specify both Duplex and Speed as Auto-Sense can be troublesome – Ref: IEMentor & Gorito
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS LAN Switching Configuration Guide, Release 12.4
• Verification Tools => show interfaces, show interfaces trunk, show vlan brief, show vtp status, clear interface

Cell-Mode MPLS: [20 Minutes: 0930->0950]

• Configure any ATM interfaces required – PVC/SVC, NSAP Addressing,
• Watch for tag-switching or label-switching.
• Security authentication may be required
• Use ping to verify
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS Asynchronous Transfer Mode Configuration Guide, Release 12.4
• Verification Tools => show interfaces, show atm pvc, show atm svc, show atm map, show atm traffic,

PPP/Ethernet: [10 Minutes: 0950->1000]

• Configure PPPoE as required, PPPoE enable, pppoe-client, interface dialer, etc.
• Know security configurations, ping and validate.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS VPDN Configuration Guide, Release 12.4 & Cisco IOS Broadband Access Aggregation and DSL Configuration Guide, Release 12.4
• Verification Tools => show pppoe session

=> Golden Moment – Bridging & Switching Complete – Total Estimated Time 2 Hours! <=

¨ IGP:

OSPF: [30 Minutes: 1000->1030]]

• While reading the task, use your master diagram to configure OSPF router by router not area by area. Look for the following OSPF characteristics.
• Authentication, stub or nssa, virtual link
• Refer again to your master diagram, colour in the OSPF areas.
• Make a note on redistribution, summary, area-range, DR/BDR, OPSF network type.
• Get Area 0 working 100% first.
• Ensure Area 0 Contiguous, test, create GRE/Virtual-links, and test again.
• Configure other areas.
• Leave OSPF Security until last.
• From a time perspective, router by router saves you revisiting router and typing in additional commands after the fact.
• First Interface and then router ospf

Preferred sequence for configuring interface

1) OPSF network type based,

2) priority,

3) Authentication,

Preferred sequence for configuring OSPF process

1) router-id

2) area authentication,

3) area virtual link,

4) neighbor,

5) Network (copy paste from interface address)

• Validate everything is working (show ip os ne, show ip os vir, show ip os interface, show ip route)
• Do redistribute summary, area range, filtering [Be Careful!]
• Avoid any engagement with giant beasts. But make a note.
• Validate and verify prior to moving on.
• Save Configurations,
• Reload routers and final verification. Note: Some candidates do not reload, some do – I will.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
• Verification Tools => show ip ospf, show ip ospf interfaces, show ip ospf neighbor, show ip ospf database, show ip ospf virtual-links, debug ip ospf events, debug ip ospf hello, debug ip ospf packet

IS-IS: [30 minutes: 1030-> 1100]

• This has been noted by previous candidates and having quite a bit to do on the SP Exam! Refer again to your master diagram, colour in the ISIS areas.
• Configure ISIS on relevant routers
• Note what ISIS Levels are required – 1 or 2,
• Assign appropriate NET addresses
• Remember unlike other IGP’s, ISIS configured at Interface level and is essentially a L2 protocol.
• Verify adjacencies
• Due to ISIS only knowing two forms of media – LAN or point-to-point -> use the frame-relay map clns command to create maps for protocol to run.
• Configure any ISIS filtering/redistribution
• Configure Authentication if required.
• Configure any additional ISIS nuances/parameters such as metrics/timers, etc we encounter.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
• Verification Tools => show isis database, show isis topology, show clns protocol, show clns interface, show clns neighbors.

=> Golden Moment – IGP Complete – IGP Time 1 hour – Total Time 3 Hours <=

¨ BGP: [60 Minutes: 1100-1200]

• While reading task, draw BGP topology on master diagram, this is important.
• Determine Route Reflector or confederation or both to do full-mesh iBGP.
• See if neighbor peer-group is required,
• Configure router by router not BGP session-by-session
• Configure one AS then another – be AS focussed.
• Always put no sync and no auto-summary if allowed.
• Ensure reachability, one AS at a time.
• Spend enough time to be absolutely correct on route-filtering (ACL, prefix-list, as-path filer), route-aggregate(w/ as-set, summary-only, supress-map, attribute-map, advertise-map), route-manipulation( w/as-prepending, med, local-pref, weight, next-hop, advertise-map/non/existing-map, origin, community, etc ) route-dampening, etc.
• Resolve any next-hop-self issues which are easier to troubleshoot working one AS at a time.
• Validate config. Use “clear ip bgp * soft “not”, clear ip bgp *.
• Leave BGP Authentication until last.
• Save, reload and test.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
• Verification Tools => show ip bgp, show ip bgp summary, show ip route bgp, show ip bgp neighbors, show ip bgp neighbors neighbor-ip-address, debug ip bgp

=> Golden Moment – EGP Complete – Ensure full Reachability Maintained, Save Configs <=

Reachability Test: [Before lunch if possible followed be reloading routers]

Test full reachability with TCL Script. Check you get an ICMP response from every router to every router. If ping has no response, write down IP address and troubleshoot.

The master diagram will help here. Method involves – show ip alias, Copy to Notepad, Search and Replace to “Massage the Data and toss in the PING Command), Wrap what’s left in a TCL or Macro, Copy and Paste into a Router.

Run tclsh script

“foreach addr {

1.1.1.1 <http://1.1.1.1

…

} { ping $ addr}” Just copy past after tclsh – To quit, just type ” tclq”. Also to quote Scott Morris -> I’d leave “debug ip routing” turned on through the rest of the day. It can be a quick indicator to things getting messed up (like when you add ACLs!)

¨ MPLS: [30-45 Minutes: 1245->1330]

• Tag Switching v Label Switching, when to use which ones – Watch for IOS Bugs here!
• Watch any integration with EGP
• MPLS might be the final piece of the jigsaw for full lab reachability.
• Cell Mode v Frame Mode
• MPLS traffic Engineering – level
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS Multiprotocol Label Switching Configuration Guide, Release 12.4
• Verification Tools => show mpls forwarding-table, show mpls interfaces, show mpls ldp neighbor, show mpls ldp parameters, show mpls traffic-eng autoroute

¨ SP Multicast: [30-45 Minutes: 1330->1415]

• Setup PIM Mode as required – Sparse/Sparse-Dense – Use address-family ipv4 multicast were required
• Identify PIM RP or Bootstrap requirements
• Don’t forget ip multicast-routing
• Be aware of route filtering
• Join any IGMP Groups if required
• Check Unicast and multicast traffic work across different AS.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS IP Multicast Configuration Guide, Release 12.4
• Verification Tools => show ip igmp groups, show ip pim rp mapping, show ip mroute, show ip interfaces.

¨ SP QoS: [30 Minutes: 1415->1445]

• Be careful not to block or drop any IGP updates
• Draw a flow on paper
• Interpretation of what is required & which QoS Method to use is Key!!
• Determine classification method (ACL, NBAR) and direction.
• Determine Shaping v Policing
• Consider all options for queuing (legacy custom/priority, bandwidth/priority, shape average/peak, FRTS/GTS) – Always Outbound.
• Consider all options for policing ( police, rate-limit, ip multicast rate-limit, aggregate police( 3550))
• If frame-relay, don’t forget adaptive-shaping.( becn, fecn, foresight)
• Consider all dropping mode (random detect, ecn, tail drop, marking, etc)
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4
• Verification Tools => show ip rsvp, show class-map, show ip rsvp reservation, show mls qos, show policy-map, show queueing, show traffic-shape, etc.

¨ L3/L2 VPN: [45 Minutes: 1445->1530]

• Configure Multicast MPLS VPN if required, VRF Mapping, default MDT, data MDT, MDT Group Addresses
• Important to map out on your master diagram, the flow/direction of the VPN Traffic so that the correct configuration can be applied to the correct interface on the correct router in the correct direction!
• MP-BGP filtering, specifying route-targets, etc
• PE-CE Routing, RIP – Watch Split-Horizon is off on physical FR and ATM, authentication, version, auto-summary, etc; Other IGP/EGP considerations, configure router-by-router, CSC, etc.
• Be aware of various backup routes for the VPN traffic in the event of line/router failure,
• Be aware of VPN and Frame Relay specific limitations
• GRE/mGRE tunnels, when to use, how to configure.
• Be able to provide Internet Access from one portion of the inter-network to another.
• Be able to exchange EGP traffic across AS’s.
• QinQ/PPoE – benefits = reduce no of VLANs, scalability, encap dot1q, pppoe enabled, etc.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS Multiprotocol Label Switching Configuration Guide, Release 12.4
• Verification Tools => show ip vrf, show ip route, show ip route vrf vrf-name [prefix], show ip cef vrf vrf-name [ip-prefix], ping

¨ SP Security: [20 Minutes: 1530->1550]

• Be careful not to block or drop any IGP updates; Draw a flow on paper if required
• Consider all options for classification – std/ext/reflexive/dynamic ACL, IP Prefix List, IP inspect, tcp intercept, Unicast RFP, ip accounting output packet /access-violation/precedence.
• Be aware of various ways to configure MD5 for IGP
• When configuring Switchport port-security mac-address, be careful to include virtual and physical mac if HSRP is running
• Know response planning to common security attacks such as DOS, Smurf, etc.
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS Security Configuration Guide, Release 12.4
• Verification Tools => Multiple Commands.

¨ SP Management: [15 Minutes: 1550->1605]

• Know SNMP, setting up community strings, traps, RMON, pointing at various devices, etc
• Netflow, destination address, port no, version, etc
• NTP, master, server, source, etc.
• Know about various IP Services available in the IOS
• DocCD Location => Main URL, Cisco IOS SW Release 12.4 Family, 12.4 Mainline, Configuration Guides, Cisco IOS NetFlow Configuration Guide, Release 12.4 & Cisco IOS Network Management Configuration Guide, Release 12.4 & Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.4
• Verification Tools => Multiple Commands.

Timing Note: According to this schedule this only allows me 25 minutes for checking, saving, reloading, troubleshooting, etc. However I have taken the outer marking for Multicast & MPLS which may or may not give me back up to 30 minutes additional time thus leaving 55 Minutes.

Other Gotcha’s/Tips:

• Route Filtering – Know this cold, affects several areas, pass or fail the lab on this alone IMO!
• Skipping Difficult Sections – This is a dangerous but potentially rewarding path up the mountain but slippery and easy to fall down on – Risky Approach.
• Redistribution – Say no more, need to pass routes, this is it – potential failure point.
• Strategy has to be flexible depending on the progress through the day.
• Ensure the “gimme” questions are answered 100% – These are key to success.
• Ongoing Validation, via show commands and TCL Script, saving and reloading at least twice I believe is essential.
• Speed accessing resources on the DOCCD is essential – should be less than 90 seconds lookup per topic.

Authors Note: Please feel free to contact me if you can add value to this 2^nd Edition as I would like to think this can help other SP candidates with a lab structure going forward.

]]> http://datacomm.wordpress.com/2009/04/27/very-nice-article-from-stephen-bowes-about-ccie-sp-lab/feed/ 0 datacomm untitled http://datacomm.wordpress.com/2009/04/27/top-interview-questions/ http://datacomm.wordpress.com/2009/04/27/top-interview-questions/#comments Mon, 27 Apr 2009 00:19:36 +0000 datacomm http://datacomm.wordpress.com/?p=81 ]]>

Almost every April Fools’ Day (1 April) since 1989, the Internet Engineering Task Force has published one or more humorous RFC documents.

http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC

IOGEAR GBS301 Bluetooth Serial Adapter – Serial – 723Kbps
iUnitek Part: Manufacturer Part:	1558223 GBS301
Availability: In stock and ready for shipment.  Usually Ships Next Day.

http://www.iunitek.com/iunitek/index.cfm?fuseaction=shop.dspSpecs&part=1558223

The Alienware M17 notebook is powered by the world’s first-ever quad core mobile CPU. The Intel® Core™2 Quad delivers unrivaled power to the M17, supplying ample horsepower to the system so you can enjoy expanded multitasking abilities and faster speeds when taking on resource-intensive tasks .

By allocating tasks across four independent cores, the Core 2 Extreme Quad-Core processor allows you to take on resource-intensive tasks such as video editing, audio mixing and 3D rendering at higher speeds.

Quad-core processing also improves performance by more efficiently distributing resources to AI, physics and rendering without creating bottlenecks.  The Alienware M17 pairs quad-core processors with high-speed DDR3 memory for maximum efficiency and increased performance.

Intel loaded the Core 2 Extreme Quad-Core processor with an abundance of performance-rich technologies in order to bring the user the most exciting gaming experience possible.

• Intel Wide Dynamic Execution – delivers more instructions per clock cycle for faster execution times
• Intel Intelligent Power Capability – improves the energy efficiency of your notebook, increasing battery life

( this will be good for GNS3 LABS )

I listed below all Vrack websites that I found. If you are facing a problem to find a suitable time slot for your Rack please check them all.

http://www.internetworkexpert.com/ccie_rack_rentals.htm#3

http://proctorlabs.com/

http://www.iementor.com/ccie-service-provider-vrack-rental-week-p-172.html

http://www.cconlinelabs.com/rates.shtml

http://ccie2be.com/default.aspx

WoW  0.86$ per hour. this is the cheapest Vrack i found ( i will try them but not now). Note;-  internetworkexpert Vrack cost 2.4$ per hour.

http://www.iementor.com/ccie-service-provider-vrack-rental-week-p-172.html

If you want to buy your home Lab. Then Visits this web site.

http://www.ciscoauctions.com/CiscoCCIE.html