Tài liệu CCIE_Train-01(2) ppt

Table of contents Exercise 1) Remote frame relay switching 2 Exercise 2) IP across frame relay 3 Exercise 3) IPX across frame relay 4 Exercise 4) Appletalk across frame relay 5 Exercise 5) Decnet across frame relay 6 Exercise 6) Banyan vines across frame relay 7 Exercise 7) Trouble shoot your network 8 Exercise 8) DLCI prioritization 9 Exercise 9) Stun and X.25 10 Exercise 10) Hot standby router protocol (HSRP) 11 Exercise 11) Advanced bgp-4 12 Exercise 12) EIGRP 13 Exercise 13) IPX 14 Exercise 14) Auto install 15 Exercise 15) IGRP-BGP-OSPF 16 Exercise 16) Policy routing 17 Exercise 17) Network Address Translation 18 Exercise 18) Protocol translation 19 Exercise 19) Route tagging 20 Exercise 20) CLNS and IS-IS 21 Exercise 21) DLSW+ 22 Exercise 1) Remote frame relay switching Objective: The objective of this exercise is configure Sydney and Melbourne (refer diagram 1) for remote frame relay switching. As such they will tunnel frame relay traffic between the 2 serial0 interfaces by encapsulating this traffic in IP and sending it across an IP backbone. a) Cable your routers as shown on diagram 1. Gibe all 4 routers appropriate hostnames and passwords. Also add clocking on serial interfaces. Do NOT clock faster then 38.4kbps if you have V.24 cables. b) Use network 131.108.0.0 and a /20 mask to create 3 subnets. c) Configure Sydney and Melbourne Ethernet0 for IP routing using of the allocated subnets. d) Create one loopback interface on each of Melbourne and Sydney, and assign each an IP address from the remaining 2 subnets. e) On Sydney and Melbourne configure RIP to advertise network 131.108.0.0 f) Create a tunnel connecting Melbourne and Sydney across the Ethernet IP backbone, Use the loopback interfaces as end points. g) Configure Melbourne and Sydney as frame relay (FR) switches on serial 0. Create 2 PVC’s at each end. Assign them DLCI numbers 50 and 51. h) Connect Brisbane/Canberra to Melbourne/Sydney via their serial 0. Create 2 PVC’s between Brisbane and Canberra. Use a NBMA approach, ie. No subinterfaces. i) Use Cisco LMI signaling between Brisbane and Melbourne. Use ANSI signaling between Sydney and Canberra. j) Configure Brisbane/Canberra to poll the switches every 5 seconds. k) Use show frame-relay pvc to verify that both DLCI’s are active between Brisbane and Canberra. Exercise 2) IP across frame relay Objective: The objective of this exercise is configure Brisbane and Canberra for IP connectivity across the frame relay service established in the previous exercise. This will be an OSPF network. a) Create one loopback interface on each of Brisbane and Canberra. Configure IP routing on both the loopback interface and frame relay interface. Use 192.1.1.0 with a /26 mask to allocate the appropriate IP addressing. b) Use a frame relay map statement to map between next hot IP address and DLCI on Brisbane and Canberra. Map DLCI 50 only. It is necessary to turn off inverse ARP for all protocols, to avoid DLCI’s going up and down. c) Configure Brisbane and Canberra for OSPF. Make the FR cloud the backbone area. Put the loopback interface on Brisbane in area 1 and the loopback interface on Canberra in area 2. d) Force the backup designated router to become the designated router on the FR cloud. Use show IP OSPF int s0 verifies your result. e) Verify that Brisbane can IP ping the loopback interface on Canberra. Can Brisbane ping the Ethernet interface on Sydney? Is this the result you expected? Exercise 3) IPX across frame relay Objective: The objective of this exercise is to configure Brisbane and Canberra for IPX connectivity across the frame relay service established in the initial exercise. This network will use EIGRP/IPX as the routing protocol. a) Configure IPX addressing on the loopback and frame relay interfaces of Canberra and Brisbane. Use the following addressing: Router Interface IPX network Brisbane loop0 10 Brisbane s0 20 Canberra loop0 30 Canberra s0 20 b) Use a frame relay map statement to map between next hop IPX address and DLSI on Brisbane and Canberra. Map DLCI 50 only. Do not use inverse ARP. c) Configure the network for EIGRP/IPX. d) Configure a static SAP on loopback interface of Brisbane. Verify that it is visible on Canberra. e) Verify that Brisbane can IPX ping the loopback interface on Canberra. Exercise 4) Appletalk across frame relay Objective: The objective of this exercise is to configure Brisbane and Canberra for Appletalk connectivity across the frame relay service established in the initial exercise. For the sake of variety we will tunnel the Appletalk across the frame relay cloud using generic route encapsulation (GRE) over IP. a) Connect Brisbane and Canberra via a TCP/IP tunnel. Use the loopback interfaces as tunnel endpoints. b) Configure Appletalk (AT) cable-ranges and zones on the tunnel interfaces of Brisbane and Canberra. Use GRE encapsulation. Appletalk does not work on loopback interface so configure Appletalk on the ethernet0 interfaces instead, but turn off keep alives to force the line protocol up. Router Interface Cable range Zone Brisbane ether0 10-10 QLD Brisbane tunnel0 20-20 Australia Canberra tunnel0 20-20 Australia Canberra ether0 30-30 ACT c) Verify that Brisbane can Appletalk ping the ethernet0 interface on Canberra, and vice versa. Exercise 5) DecNet across frame relay Objective: The objective of this exercise is to configure Brisbane and Canberra for DecNet connectivity across the frame relay service established in the initial exercise. Brisbane and Canberra will be in different DecNet areas. a) Configure DecNet on Brisbane and Canberra. Use the following addressing Router Area Node Brisbane 10 1 Canberra 30 1 b) Use a frame relay map statement to map between next hop DecNet address and DLCI on DLCI 50. c) Verify that Brisbane can DecNet ping Canberra, and vice versa. Exercise 6) Banyan vines across frame relay Objective: The objective of this exercise is to configure Brisbane and Canberra for Banyan Vines connectivity across the frame relay service established in the initial exercise. a) Configure Banyan Vines on Brisbane and Canberra. Enable vines on both loopback and serial interfaces. b) Use a frame relay map statement to map between next hop Bines address and DLCI on DLCI 50. c) Verify that Brisbane can Vines ping Canberra, and vice versa. Exercise 7) Troubleshoot your network Objective: The objective of this exercise is to troubleshoot the network that you have created so far. This is a simulation of what you will be asked to do at the real CCIE lab. a) Verify that you have end-to-end connectivity for IP, IPX, AT, DecNet and Vines. This working network is now baseline. b) Leave the room while your instructor inserts 6 trouble tickets into your network. c) When asked to return, troubleshoot your network and bring it back to baseline. You have max 2 hours to complete this exercise. While troubleshooting, document your approach. As an absolute minimum list the problems you find, some suspected causes, and the actual fault once you find it. At the CCIE lab you will be given credit for this documentation, even if you do not manage to resolve all problems. Exercise 8) DLCI prioritization Objective: The objective of this exercise is to configure DLCI prioritization between Brisbane and Canberra. Recall that 2 parallel DLCI’s connect these 2 routers. DLCI prioritization will control which traffic goes on which DLCI. a) Now that you have regained full connectivity, configure DLCI prioritization on both Brisbane and Canberra so that: - Telnet traffic is given high priority. - Traffic to TCP port ‘daytime’ is given low priority. - Everything else is given medium priority. b) Put high and medium traffic on DLCI 50. Put the normal and low traffic on DLCI 51. c) Verify your configuration by turning on ‘debug priority’ and ‘debug frame relay packet’. From Brisbane telnet to the daytime port on Canberra (telnet Canberra daytime). Examine the debug output to verify that traffic is sent down DLCI 51 only when you telnet to daytime. Exercise 9) STUN and X.25 Objective: The objective of this exercise is to configure X.25 between Brisbane and Canberra. Because these 2 routers are separated by Sydney and Melbourne we will configure Sydney and Melbourne to STUN the X.25 across. a) Reconfigure the serial ports on Melbourne and Sydney for STUN. Tunnel in basic mode between the 2 serial interfaces using TCP/IP encapsulation. b) Reconfigure the serial0 interfaces on Brisbane and Canberra for X.25. Canberra and Brisbane will appear as if they are running X.25 back to back, so make Brisbane X.25 DCE. c) Configure the X.25 interfaces with the following characteristics: - Brisbane X.121 address is 11111 - Canberra X.121 address is 22222 - Use a single SVC to carry multiprotocol traffic (RFC-1356) - Use virtual circuit number 53 as a two way multiprotocol SVC - Incoming/outgoing packet size of 1024 bytes - Incoming/outgoing window of 7 d) Add the necessary X.25 map statements to make the existing IP, IPX, AT, DecNet and Vines configuration on the Canberra and Brisbane work across the X.25 cloud. Use Multiprotocol encapsulation (RFP 1356) e) Verify that IP, IPX, Appletalk, DecNet and Vines all work by pinging from Brisbane to Canberra. . created so far. This is a simulation of what you will be asked to do at the real CCIE lab. a) Verify that you have end-to-end connectivity for IP, IPX, AT,. find, some suspected causes, and the actual fault once you find it. At the CCIE lab you will be given credit for this documentation, even if you do not