THÔNG TIN TÀI LIỆU
CCIE R/S Lab Bootcamp Workbook Authored By: Khawar Butt CCIE # 12353 (R/S, Security, SP, Voice) CCIE R/S Lab Bootcamp Workbook Netmetric Solutions http://www.netmetric-solutions.com Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Module – Frame Relay Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Lab – Hub-n-Spoke using Frame-relay map statements R1 R2 R4 Frame-Relay R3 IP addressing and DLCI information Chart Routers IP address Local DLCI Connecting to: R1 S0/0: 192.1.234.1/24 R2 S0/0: 192.1.234.2 /24 102 103 104 201 R2 R3 R4 R1 R3 S0/0: 192.1.234.3 /24 301 R1 R4 S0/0: 192.1.234.4 /24 401 R1 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Task Configure the frame-relay cloud in a hub and spoke topology using frame-relay map statements The frame-relay switch is configured in a full mesh; these routers should NOT reply to inverse-arp inquiries R1 R2 Int S0/0 Ip address 192.1.234.1 255.255.255.0 Encapsulation frame Frame-relay map ip 192.1.234.2 102 b Frame-relay map ip 192.1.234.3 103 b Frame-relay map ip 192.1.234.4 104 b No frame-relay inverse-arp No shut R3 Int S0/0 Ip address 192.1.234.2 255.255.255.0 Encapsulation frame Frame-relay map ip 192.1.234.1 201 b No frame-relay inverse-arp No shut R4 Int s0/0 Ip address 192.1.234.3 255.255.255.0 Encapsulation frame Frame-relay map ip 192.1.234.1 301 b No frame-relay inverse-arp No shut Int s0/0 Ip address 192.1.234.4 255.255.255.0 Encapsulation frame Frame-relay map ip 192.1.234.1 401 b No frame-relay inverse-arp No shut Task Ensure that every router can ping every address connected to the frame-relay cloud including their own R1 R2 Int S0/0 Frame-relay map ip 192.1.234.1 102 R3 Int S0/0 Frame-relay map ip 192.1.234.3 201 Frame-relay map ip 192.1.234.4 201 Frame-relay map ip 192.1.234.2 201 R4 Int S0/0 Frame-relay map ip 192.1.234.2 301 Frame-relay map ip 192.1.234.4 301 Frame-relay map ip 192.1.234.3 301 Int S0/0 Frame-relay map ip 192.1.234.2 401 Frame-relay map ip 192.1.234.3 401 Frame-relay map ip 192.1.234.4 401 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Task Erase the startup config and reload the routers before proceeding to the next lab Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Lab –Configuring Frame-relay point-to-point sub-interfaces R1 R2 R4 Frame-Relay R3 IP addressing and DLCI information Chart Routers IP address Local DLCI Connecting to: R1 R2 S0/0.12: 192.1.12.1/24 S0/0.13: 192.1.13.1/24 S0/0.14: 192.1.14.1/24 S0/0.21: 192.1.12.2/24 102 103 104 201 R2 R3 R4 R1 R3 S0/0.31: 192.1.13.3 /24 301 R1 R4 S0/0.41: 192.1.14.4 /24 401 R1 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Task Configure the frame-relay cloud in a hub and spoke topology; the routers should be configured in a point-to-point configuration R1 R2 Int S0/0 Encap frame-relay No shut Exit ! Int S0/0.12 point-to-point Ip address 192.1.12.1 255.255.255.0 Frame-relay interface-dlci 102 ! Int S0/0.13 point-to-point Ip address 192.1.13.1 255.255.255.0 Frame-relay interface-dlci 103 ! Int S0/0.14 point-to-point Ip address 192.1.14.1 255.255.255.0 Frame-relay interface-dlci 104 R3 Int S0/0 Encap frame-relay No shut Exit ! Int S0/0.21 point-to-point Ip address 192.1.12.2 255.255.255.0 Frame-relay interface-dlci 201 Int S0/0 Encap frame-relay No shut Exit ! Int S0/0.31 point-to-point Ip address 192.1.13.3 255.255.255.0 Frame-relay interface-dlci 301 Int S0/0 Encap frame-relay No shut Exit ! Int S0/0.41 point-to-point Ip address 192.1.14.4 255.255.255.0 Frame-relay interface-dlci 401 R4 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 Lab – Point-to-point and Multipoint R1 R2 R4 Frame-Relay R3 Task Configure the routers connected to the frame-relay cloud as follows: o R1 (The HUB) must be configured with two sub-interfaces, one of the two sub-interfaces must be configured to connect R1 to R4, this sub-interface should be configured in a point-to-point manner using the following IP addressing: R1 = 192.1.14.1 /24, and R4 = 192.1.14.4 /24 o The second sub-interface on R1 must be configured in a multipoint manner, and this sub-interface must be configured to connect R1 to routers R2 and R3 using the following IP addressing: R1 = 192.1.123.1 /24, R2 = 192.1.123.2 /24 and R3 = 192.1.123.3 /24 o Make sure that you are pretending that R1 is not a Cisco router when configuring the Encapsulation Framing Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 o Routers R2, R3 should not be configured with a sub-interface and these routers should NOT rely on Inverse-arp o R4 should be configured with a sub-interface in a point-to-point manner o The routers connecting to the frame-relay cloud should be configured in a hub and spoke, with R1 being the hub and R2, R3 and R4 the spokes o Ensure that the routers can ping every IP address including their own within their IP address space R1 R2 Int S0/0 Encapsulation frame-relay ietf No frame-relay inverse No shut ! Int S0/0.14 point-to-point Ip address 192.1.14.1 255.255.255.0 Frame-relay interface-dlci 104 ! Int S0/0.123 multipoint Ip address 192.1.123.1 255.255.255.0 Frame-relay map ip 192.1.123.1 102 Frame-relay map ip 192.1.123.2 102 b Frame-relay map ip 192.1.123.3 103 b R3 Int S0/0 Ip address 192.1.123.2 255.255.255.0 Encapsulation frame No frame-relay inverse Frame-relay map ip 192.1.123.1 201 ietf b Frame-relay map ip 192.1.123.3 201 ietf Frame-relay map ip 192.1.123.2 201 ietf No shut Exit R4 Int S0/0 Int S0/0 Encapsulation frame Encap frame Ip address 192.1.123.3 255.255.255.0 No frame-relay inverse Frame-relay map ip 192.1.123.1 301 ietf b No shut Frame-relay map ip 192.1.123.2 301 ietf ! Frame-relay map ip 192.1.123.3 301 ietf Inter S0/0.41 point-to-point No frame-relay inverse Ip address 192.1.14.4 255.255.255.0 No shut Frame-relay interface 401 ietf Task Ensure that R1 and R4 use CHAP authentication using Cisco as the password These routers must authenticate each other before they can communicate Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com of 229 R1 R4 Username R4 password Cisco Username R1 password Cisco Interface S0/0.14 No ip address Inter S0/0.41 No ip address Inter virtual-template Ip address 192.1.14.1 255.255.255.0 Ppp authentication chap Inter virtual-template Ip address 192.1.14.4 255.255.255.0 Ppp authentication chap Int S0/0.14 Frame-relay interface-dlci 104 ppp virtualtemplate Int S0/0.41 Frame-relay interface-dlci 401 ppp virtualtemplate Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 10 of 229 R5 should not have a neighbor relationship with R3 Advertise the Loopback 125 networks on the appropriate routers Configure the neighbor relationship with redundancy in mind All IBGP routers using the most secure authentication method Use CCIE as the password R1: R2 Int loopback125 Ip address 125.1.1.1 255.255.255.0 R3 Int loopback125 Ip address 125.2.2.2 255.255.255.0 R4: Int loopback125 Ip address 125.3.3.3 255.255.255.0 ! router bgp 345 no auto-summary no sync network 125.3.3.0 mask 255.255.255.0 neighbor 44.44.44.44 remote-as 345 neighbor 44.44.44.44 password CCIE neighbor 44.44.44.44 update-source Loopback0 Int loopback125 Ip address 125.4.4.4 255.255.255.0 ! router bgp 345 no auto-summary no sync network 125.4.4.0 mask 255.255.255.0 neighbor 33.33.33.33 remote-as 345 neighbor 33.33.33.33 password CCIE neighbor 33.33.33.33 update-source Loopback0 neighbor 33.33.33.33 route-reflector-client neighbor 55.55.55.55 remote-as 345 neighbor 55.55.55.55 password CCIE neighbor 55.55.55.55 update-source Loopback0 neighbor 55.55.55.55 route-reflector-client R6: R5 Int loopback125 Ip address 125.5.5.5 255.255.255.0 ! router bgp 345 no auto-summary no sync neighbor 44.44.44.44 remote-as 345 neighbor 44.44.44.44 password CCIE neighbor 44.44.44.44 update-source Loopback0 Int loopback125 Ip address 125.6.6.6 255.255.255.0 SW1 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 215 of 229 Int loopback125 Ip address 125.21.21.21 255.255.255.0 3.2 – EBGP (3 Points) Configure a EBGP relationship between AS and AS 345 Use R5 in AS 345 to set this relationship up Advertise the Loopback 125 network in BGP on R2 Don’t use the network command to accomplish task The origin should be internal Configure a EBGP relationship between AS and AS 65500 Authenticate this relationship Advertise the Loopback 125 network in BGP on R6 Configure R1 in AS Advertise the Loopback 125 network under BGP Configure a EBGP neighbor relation between AS 345 and AS AS 345 sees AS in AS 1000 Configure the remote-as as 1000 for AS on R4 Configure SW2 in AS 21 Advertise the Loopback 125 network under BGP Configure an EBGP neighbor relation between AS 21 and AS 345 based on the network diagram Also configure an EBGP neighbor relation between AS 21 and AS based on the network diagram R1 R2 router bgp no auto-summary no sync network 125.1.1.0 mask 255.255.255.0 neighbor 192.1.3.21 remote-as 21 neighbor 192.1.3.21 ebgp-multihop 255 neighbor 192.1.14.4 remote-as 345 neighbor 192.1.14.4 local-as 1000 route-map RC-2-BGP permit 10 match interface Loopback125 set origin igp ! router bgp no auto-summary no sync redistribute connected route-map RC-2BGP neighbor 192.1.26.6 remote-as 65500 neighbor 192.1.26.6 password CCIE neighbor 192.1.45.5 remote-as 345 neighbor 192.1.45.5 ebgp-multihop 255 R4 R3 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 216 of 229 router bgp 345 neighbor 192.1.3.21 remote-as 21 R5 router bgp 345 neighbor 192.1.14.1 remote-as 1000 R6 router bgp 345 neighbor 192.1.234.2 remote-as neighbor 192.1.234.2 ebgp-multihop 255 router bgp 65500 no auto-summary no sync network 125.6.6.0 mask 255.255.255.0 neighbor 192.1.26.2 remote-as neighbor 192.1.26.2 password CCIE SW2 router bgp 21 network 125.21.21.0 mask 255.255.255.0 neighbor 192.1.3.3 remote-as 345 neighbor 192.1.14.1 remote-as neighbor 192.1.14.1 ebgp-multihop 255 3.3 – Route Aggregation (2 Points) Create the following loopback on R1: o Loopback 191: 199.1.4.1/24 o Loopback 192: 199.1.5.1/24 o Loopback 193: 199.1.6.1/24 o Loopback 194: 199.1.7.1/24 Advertise these networks under BGP Summarize these networks on R1 Suppress the specific routes from getting propagated to BGP neighbors except for 199.1.5.0/24 This route should get propagated in addition to the summary route R1 interface Loopback191 ip address 199.1.4.1 255.255.255.0 ! interface Loopback192 ip address 199.1.5.1 255.255.255.0 ! interface Loopback193 ip address 199.1.6.1 255.255.255.0 ! interface Loopback194 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 217 of 229 ip address 199.1.7.1 255.255.255.0 ! router bgp network 199.1.4.0 network 199.1.5.0 network 199.1.6.0 network 199.1.7.0 aggregate-address 199.1.4.0 255.255.252.0 summary-only suppress-map SM ! access-list 131 deny 199.1.5.0 0.0.0.255 access-list 131 permit any ! route-map SM permit 10 match ip address 131 3.4 – Filtering Private AS number (2 Points) R2 should not send the Private AS number in the AS Path for route(s) from AS 65500 to AS 345 You can use a single command under the BGP Routing process to accomplish this task R2 Router bgp neighbor 192.1.45.5 remove-private-as 3.5 – Path Attributes (2 Points) Configure AS 345 such that it uses AS 21 to get to AS routes Do not use the AS-Path or Weight Attributes to accomplish this task Configure AS 21 such that it uses AS to get to AS routes R3 SW2 ip as-path access-list permit _1$ ! route-map LP permit 10 match as-path set local-preference 200 ! route-map LP permit 20 ! Router bgp 234 ip as-path access-list permit _2$ ! route-map LP permit 10 match as-path set local-preference 200 ! route-map LP permit 20 ! Router bgp 21 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 218 of 229 neighbor 192.1.3.21 route-map LP in neighbor 192.1.14.1 route-map LP in Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 219 of 229 Section – Security (8 points) 4.1 – Dot 1X Authentication (3 Points) Configure Ports F 0/13 – 18 on Switch for Dot1X authentication Assign them to VLAN 250 Authentication should be done based on a RADIUS Server located at 192.1.3.100 Use cciers as the secret key If the host does not support Dot1X authentication, it should be put in VLAN 300 SW1 Vlan 250 Vlan 300 ! Under all trunk interfaces: switchport trunk allowed vlan add 250,300 ! aaa new-model aaa authentication dot1x default group radius ! dot1x system-auth-control ! radius-server host 192.1.3.100 key cciers ! Interface range F0/13-18 Switchport mode access Switchport access vlan 250 dot1x port-control auto dot1x guest-vlan 300 4.2 – SSH Configuation (3 Points) Configure R3 such that remote management can only be done by SSH Configure a Local User SSHADMIN with a password of cciers SSH authentication should be done based on the local database Only allow Remote Management from VLAN R3: username SSHADMIN password cciers ! Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 220 of 229 ip domain name ccie.com ! crypto key generate rsa ! access-list permit 192.1.3.0 0.0.0.255 ! line vty access-class in login local transport input ssh line vty 1180 access-class in login local transport input ssh 4.3 – ACL Configuration (2 Points) Configure RFC 1918 filtering on R5 for anti-spoofing from the Frame cloud Also make sure packets with internal address as source addresses should not be allowed in Do not use an ACL for this task There is a web server located at 192.1.15.25 This web server will be going down for Maintenance on Friday, Saturday and Sunday from 9:00 PM to 11:30 PM R5 should block access to this server during the Maintenance times This should be in affect for the month of December R5 access-list 141 deny ip 10.0.0.0 0.255.255.255 any access-list 141 deny ip 172.16.0.0 0.15.255.255 any access-list 141 deny ip 192.168.0.0 0.0.255.255 any access-list 141 permit ip any any ! Interface F0/0.2 ip verify unicast source reachable-via rx ip access-group 141 in ! time-range SM absolute start 00:00 01 December 2008 end 23:59 31 December 2008 periodic Friday 21:00 to 23:30 periodic Saturday 21:00 to 23:30 periodic Sunday 21:00 to 23:30 ! Access-list 142 deny ip any host 192.1.15.25 time-range SM Access-list 142 permit ip any any Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 221 of 229 ! Interface f0/0.1 ip access-group 142 in Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 222 of 229 Section – IOS Services (12 points) 5.1 – IOS DHCP Server (3 Points) Enable R5 as a DHCP Server with the following information: o o o o o o IP ADDRESS : 192.1.15.0/24 WINS ADDRESS : 192.1.15.5 DNS ADDRESS : 192.1.15.6 DEFAULT GATEWAY : 192.1.15.1 LEASE TIME : Days Exclude-addresses : 192.1.15.1-192.1.15.10 R5 ip dhcp pool CCIE network 192.1.15.0 255.255.255.0 netbios-name-server 192.1.15.5 dns-server 192.1.15.6 default-router 192.1.15.1 lease ! ip dhcp excluded-address 192.1.15.1 192.1.15.10 5.2 – Core Dumps (3 Points) Configure R1 to send a Core DUMP to a FTP server located at 192.1.12.100 Set the Dump size to 32768 Use CCIE as the Username to log into the FTP with a password of 12353 R1 exception protocol ftp exception region-size 32768 exception dump 192.1.12.100 ! ip ftp username CCIE ip ftp password 12353 5.3 – NAT (3 Points) Configure a Loopback 10 on R1 Assign it an address of 10.0.0.1/8 Configure NAT on R1 to allow the 10.0.0.0 network to access the rest of routers using S 0/0 interface address Do not create a pool to accomplish this Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 223 of 229 There is a web server that will be installed at 10.0.0.80 There is a DNS Server located at 10.0.0.81 Allow the outside user’s access to these servers using a common outside address of 192.1.14.83 R1 Interface Loopback10 Ip address 10.0.0.1 255.0.0.0 Ip nat inside ! Interface S 0/0.1 Ip nat outside ! Access-list 161 permit 10.0.0.0 0.255.255.255 any ! ip nat inside source list 161 interface S 0/0.1 overload ip nat inside source static tcp 192.1.14.83 80 10.0.0.80 80 extendable ip nat inside source static udp 192.1.14.83 53 10.0.0.81 53 extendable 5.4 – DRP (3 Points) R5 will be queried by Cisco DistributedDirector from the following IP Addresses: o 195.1.5.15 o 195.1.7.35 Enable the DRP Server Agent on R5 Only allow DRP Queries from the above listed DistributedDirector’s R5 should be configured to authenticate the DistributedDirector with a key of ccie R5 access-list 15 permit 195.1.5.15 access-list 15 permit 195.1.7.35 ! key-chain DRP key key-string ccie ! ip drp server ip drp access-group 15 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 224 of 229 ip drp authentication key-chain DRP Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 225 of 229 Section – Multicasting (6 points) 6.1 – Configuring PIM Sparse Mode (3 Points) Configure VLAN 26 to receive and send multicast Traffic from and to VLAN 45 Perform configurations on R2 and R4 using PIM-Sparse-Mode R2 should be the RP for 224.2.2.2 and R4 should be the RP for 224.4.4.4 R2 R4 Ip multicast-routing ! Interface s0/0 Ip pim sparse-mode ! Interface F 0/0 Ip pim sparse-mode ! ip pim rp-address 2.2.2.2 31 ip pim rp-address 4.4.4.4 32 ! access-list 31 permit 224.2.2.2 access-list 32 permit 224.4.4.4 Ip multicast-routing ! Interface s0/0.234 Ip pim sparse-mode ! Interface F 0/0 Ip pim sparse-mode ! ip pim rp-address 2.2.2.2 31 ip pim rp-address 4.4.4.4 32 ! access-list 31 permit 224.2.2.2 access-list 32 permit 224.4.4.4 6.2 – Configuring IGMP (3 Points) Configure R2 to statically join multicast group 224.2.2.2 and R4 to statically join the multicast group 224.4.4.4 R2 and R4 should be able to ping both Multicast groups R2 R4 Interface F 0/0 Ip igmp join-group 224.2.2.2 Interface F 0/0 Ip igmp join-group 224.4.4.4 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 226 of 229 Section –QoS (8 points) 7.1 – Configuring CB-WFQ using NBAR (3 Points) Configure R3 such that traffic going towards the Frame Cloud uses the following QoS parameters: o All HTTP traffic towards a Web Server http://www.netmetricsolutions.com should be assigned a minimum bandwidth of 35% o Telnet Traffic should be assigned a minimum bandwidth of 10% Configure it for LLQ o FTP traffic should be limited to 256 kbps R3 class-map match-all TELNET match protocol telnet class-map match-all HTTP match protocol http url "*http://www.netmetric-solutions.com*" class-map match-all FTP match protocol ftp ! ! policy-map QoS class HTTP bandwidth percent 35 class TELNET priority percent 10 class FTP police 256000 ! Interface s0/0/0 service-policy output QoS 7.2 – Configuring Policing using MQC (3 Points) R3-R4 has a CIR of 256 and Peak CIR of 512 Configure R4 such that all HTTP and HTTPS traffic going from 192.1.15.0 networks towards Network 6.0.0.0 should have a Precedence of if it is within the CIR If it exceeds the CIR, it should be set with a Precedence of Also, set the DE bit on, if it exceeds the CIR If it exceeds the Peak, the packet should be dropped The rest of the traffic should to set to a Precedence of R4 Access-list 171 permit tcp 192.1.15.0 0.0.0.255 6.0.0.0 0.255.255.255 eq www Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 227 of 229 Access-list 171 permit tcp 192.1.15.0 0.0.0.255 6.0.0.0 0.255.255.255 eq 443 ! class-map match-all WEB match access-group 171 ! policy-map POLICE class WEB ! police cir 256000 pir 512000 conform-action set-prec-transmit exceed-action set-prec-transmit exceed-action set-frde-transmit violate-action drop class class-default set precedence ! Interface s0/0.234 service-policy output POLICE 7.3 – SRR (2 Points) Configure SRR on Switch such that F 0/10 port using the following parameters: CoS Value 3, 4, ,7 0,1 Srr Queue Configure Shaping on the first queue It should used 25% percent of the interface Bandwidth Configure Sharing on the remaining queues Queues 2, and should be shared with a percentage breakdown of 45 30 and 25 percentage respectively SW1 Mls qos ! mls qos srr-queue output cos-map queue mls qos srr-queue output cos-map queue mls qos srr-queue output cos-map queue mls qos srr-queue output cos-map queue 4 ! interface FastEthernet0/10 srr-queue bandwidth share 45 30 25 srr-queue bandwidth shape 0 Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 228 of 229 Section – IPV6 (4 points) 8.1 – Configuring IPV6 (2 Points) Configure R3 and R6 with the following IPv6 Addresses: Router R3 R3 R6 R6 Interface Loopback E 0/0.2 Loopback E 0/0.2 IPv6 Address 2222:1111:3333:3333::3/64 2222.1111:3333:3636::3/64 2222:1111:6666:6666::6/64 2222:1111:2222:3636::6/64 R3 R6 Interface F0/0.2 ipv6 address 2222:1111:3333:3636::3/64 Interface loopback0 ipv6 address 2222:1111:3333:3333::3/64 Interface F0/0.2 ipv6 address 2222:1111:2222:3636::6/64 Interface loopback0 ipv6 address 2222:1111:6666:6666::6/64 8.2 – Running RIPng (2 Points) Enable IPv6 Unicast Routing Run RIPng between R3 and R6 and advertise the Loopback networks R3 R6 ipv6 unicast-routing ! Interface F0/0.2 ipv6 rip RIPNG enable Interface loopback0 ipv6 rip RIPNG enable ipv6 unicast-routing ! Interface F0/0.2 ipv6 rip RIPNG enable Interface loopback0 ipv6 rip RIPNG enable Copyrights Netmetric Solutions 2006-2010 Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com 229 of 229 ... 192.1. 23. 2 Subnet Mask 255.0.0.0 255.255.255.0 255.255.255.0 IP Address 3. 3 .3. 3 192.1. 23. 3 192.1 .34 .3 Subnet Mask 255.0.0.0 255.255.255.0 255.255.255.0 R2 Interface Loopback E 0/0 S 0/0 R3 Interface... 0/0 Ip address 192.1. 23. 2 255.255.255.0 Encap frame-relay No frame-relay inverse-arp Frame-relay map ip 192.1. 23. 3 2 03 broad No shut R4 R3 Interface Loopback Ip address 3. 3 .3. 3 255.0.0.0 Interface... 1 235 3 AUTH Ip authentication mode eigrp 1 235 3 MD5 ! Interface E 0/0 Ip authentication key-chain eigrp 1 235 3 AUTH Ip authentication mode eigrp 1 235 3 MD5 R4 R3 Key chain AUTH Key Key-string ccie
Ngày đăng: 27/10/2019, 22:27
Xem thêm: