Exterior Gateway Routing
Note: Non BGP speaking devices do not need IP reachability to BGP learned prefixes
4.1. BGP
Peering
• Configure BGP on the following devices with the following AS numbers: Device
BGP AS
R3 200
R4
100
R6
100
BB1
54
BB2
254
BB3
54
• Configure the BGP peering sessions as follows:
Device 1
Device 2
R6
BB1
R6
BB3
R6
R3
R6
R4
R3
BB2
• All BGP traffic between R4 and R6 should traverse the VPN tunnel.
• Configure R3 to authenticate its BGP peering session with BB2 using the password CISCO.
2 Points
4.2. BGP Bestpath Selection
• Administrators of your network have reported congestion on the Ethernet segment between R6 and BB3. In order to alleviate this congestion administrators of AS 100 have decided to send traffic for all prefixes learned from AS 54 to BB1.
• Configure your network to reflect this policy.
• Do not use local preference to accomplish this.
2 Points
Copyright © 2007 Internetwork Expert
www.InternetworkExpert.com
- 131 -
CCIE Routing & Switching Lab Workbook Version 4.0
Lab 6
4.3. BGP
Filtering
• Memory usage on your BGP speaking devices in getting dangerously high. After investigating the problem, you have determined that the BGP
table is consuming too much memory. In order to help cut down on the memory requirements throughout the BGP domain, your design team has implemented a new filtering policy. This policy states that AS 100 will not accept any prefixes from AS 54 with a mask longer than a /20.
• Configure R6 to reflect this policy.
• The prefix-list used to accomplish this should only have one line.
2 Points
4.4. BGP
Summarization
• Configure R3 to advertise a summary of your major network, 191.X.0.0/16, and your Loopback 0 addresses, 150.X.0.0/20, into BGP.
• Do not use the aggregate-address command to accomplish this.
• You are allowed to use two static routes on R3 to accomplish this.
3 Points
4.5. BGP Table Stability
• High CPU utilization has been reported on R6. After further investigation, you have discovered that the prefixes 112.0.0.0/8 and 113.0.0.0/8 from AS
54’s customers have been constantly flapping and causing R6 to continuously recalculate the BGP topology.
• In order to minimize the impact of this flapping on the rest of the BGP
domain, configure R6 so that these prefixes are not advertised if they are consistently unstable.
• No other prefixes should be affected by this configuration.
2 Points
Copyright © 2007 Internetwork Expert
www.InternetworkExpert.com
- 132 -
CCIE Routing & Switching Lab Workbook Version 4.0
Lab 6
5. IP Multicast
5.1. PIM
• Configure IP Multicast routing on R1, R2, R3, R5, and SW1.
• Configure PIM dense mode on the following interfaces:
Device
Interface
R1 S0/0
R1
S0/1
R2 Fa0/0
R2
S0/1
R3 E0/0
R3
E0/1
R3
S1/2
R3
S1/3
R5
E0/0
R5
S0/0
SW1
Fa0/2
SW1
VL7
2 Points
5.2. PIM
Filtering
• A media server located on VLAN 32 will be streaming a video feed to clients located on VLAN 5.
• The network administrator has requested that the Frame Relay connection between R1 and R5 be used as sparingly as possible for multicast traffic.
• To help avoid excess multicast flooding and pruning behavior over this Frame Relay connection, R1 should not allow R5 to become a PIM
neighbor. However, R5 should still allow clients on VLAN 5 to receive multicast traffic for this group.
• Configure your network to support this arrangement.
2 Points
Copyright © 2007 Internetwork Expert
www.InternetworkExpert.com
- 133 -
CCIE Routing & Switching Lab Workbook Version 4.0
Lab 6
5.3. IGMP
• The network administrator has reported that clients in VLAN 363 will be using Windows® 95, which supports only IGMP version 1.
• Configure R3 to only support clients running IGMP version 1 on this interface.
2 Points
5.4. Multicast
Testing
• The network administrator is trying to troubleshoot a problem relating to the multicast group 225.25.25.25 and has requested that SW1 forward traffic for this multicast group into VLAN 7. However, the testing application he is using will not be generating IGMP join messages.
• Configure SW1 to accommodate this request, but do not allow SW1 to process switch this traffic.
2 Points
6. IPv6
6.1. IPv6
Addressing
• The network administrator has requested you to configure a test deployment of IPv6 between VLAN 5 and BB2.
• Configure IPv6 on R3's interface connecting to BB2 using the network 2001:192:10:X::Y/64.
• Configure IPv6 on the Serial connection between R2 and R3 using the network 2001:CC1E:X:23::Y/64.