Interconnecting Cisco Network Devices, Part 2 (ICND2) v2.0 Global Knowledge European n Remote Labs Instructor Guide Revision Draft 0.

Transcription

1 Interconnecting Cisco Network Devices, Part 2 (ICND2) v2.0 Global Knowledge European Remote Labs Instructor Guide

2 1. Contents 1. Contents Introduction Remote Labs Topology, Connections and Setup Initial Lab Configurationn Set-up Lab Clear Down Procedure Lab Exercisess Support Information Telephone Other Contact Methods Page 2

3 2. Introduction This guide has been produced to assist in understanding the specific issues relating to delivering the Cisco Interconnecting Cisco Network Devices, D Part 2 v2.0 training course, using Global Knowledge European Remote Labs equipment. It is intended to complement the Cisco documentation and a should only be used in conjunctionn with the Cisco Coursee Administration (CAG) and Student Lab Guides. Page 3

4 3. Remote Labs Topology, Connections and Setup Page 4

5 4. Initial Lab Configuration Set-up Devicee Configuration Load the Base configurations for all devices from the Device on the Instructor Web Access page. Management tool Core Device Logins HQ Router: Student level 2 enable password: <none> (privilege level 2 set on vty lines) Instructor level 15 enable password: globalk Student PC Logins administrator / admin Page 5

6 5. Lab Clear Down Procedure Load the Base configurations for all devices, from the Device Management tool on the Instructor Web Access page. Notify Remote Lab Support that you have finished usingg the equipment by replying to the End of Course Confirmation , which will have been sent to you during the week. Please do NOT reply to t the End of Course Confirmatio n forr ANY other purpose (e.g. a support request) this may cause confusion and your rack may be disconnected or cleared before your class has finished as a result..!! Should you have not received thee above by the time that your class has finished, please send an too the Support address (Section 2 above), confirming the Course and Rack used, that you have completed the class and finished using the equipment, along with any commentss or follow-up required. Page 6

7 6. Lab Exercises Lab S-1: Review Lab Setup Nothing further required. Base configurations for f all devices were loaded as part of the Initial Lab Setup (Section 4). Job Aids: Topology and IP Addressing Device Interface HQ HQ HQ SW1 SW2 PC1 PC2 Loopback 10 FastEthernet0/0.1 (vlan 1) FastEthernet0/0.10 (vlan 10) FastEthernet0/0.20 (vlan 20) FastEthernet0/1 Serial0/0/0 FastEthernet0/1 Serial1/X Loop0 VLAN1 VLAN1 Class LAB Interface Class LAB Interface IP Address & Subnet Mask / / :DB8:0A01:10P::1/ / :DB8:0A01:A0P::1/ / :DB8:0A01:140P::1/ / / / :DB8:C0A8:10P::1/ / / / :DB8:C0A8:10P::2/644 (for X see Serial Port tablee below) / / / / /244 In the above table P is to be replaced with the Pod Number. N Job Aids: Serial Interface Table Pod HQ Router Serial Interface Serial1/0 Serial1/1 Serial1/2 Serial1/3 Serial1/4 Serial1/5 Page 7

8 Task 1 Step 18: Important Note: The Remote Lab setup uses the Core Switch to distribute the PC connections. This switch will advertise itself with its own internal MACC Address and this will disrupt the Port Security lab, unless the commands are issued in the specific order listed below (also refer to the Cisco CAG guide, where this issue is discussed). On the Pod Switch, issue the Port Security commands in i the following order: switchport port-security violation protect switchport port-security maximum 1 switchport port-security mac-addresss hhhh.hhhh.hhhh switchport port-security Note that the last command switchport port-security is the command that actually initiates the port security feature. Provided that the PC mac m address is already entered and also the violation is set to protect before port p securityy is initiated, then only the configured mac will be allowed. All other mac addresses a also seen will be rejected (the violation protect allows the port to still function, as opposed the disabling the port). Task 2 Step 6: Enable the FastEthernet0/00 interface on o the router. Note: For ALL lab steps that specify the GigabitEthernet interfaces, please substitute FastEthernet instead. Task 3 Step 3: Add network (VLAN 1) to the ACL. This is required for later labs. Task 4 Activity Verification stepp 5: Each Remote Lab rack use a shared HQ router, with each pod configured individually, using vrf-lite. Thiss requires students to use a pod-specific form of certain commands on the HQ router to view the correct vrf routing table. In this step, to view the correct Pod vrf router table use the command format: show ip route vrf PodP (where P is the specific pod number. Note also that the P of Podd is uppercase) e.g.. for Pod 2, the command would be show ip route vrf Pod2 Refer to the Job Aids: Serial Interface Table for the correct interface visible per Pod vrf route table. Configuration Note: Successful completion of this review lab is vital for the following labs. Therefore, to assist, an End of Lab S-1 configuration has been provided, if required to ensure a complete Pod network setup. Load via the Device Management tool on either the Instructor or Pod Web Access pages. Page 8

9 Lab 1-1: Troubleshooting VLANss and Trunks Setup Students to load the Podd, SW1 and SW2 Lab 1-11 configurations via the Devicee Management tool on the Student Pod Web Access page. Task 1 All OK Task 2 All OK Lab 1-2: Optimizing STP Setup No additional setup required. Instructor to load the pod SW1 and SW2 Lab 1-2 configuration(s), if student(s) have not completed Lab 1-11 successfully. Note: During the lab steps, students are advised to determine which Switch is the Root Bridge for specific vlans andd then make changes to t move thee Root to the other Switch. To avoid confusion, it may be best to revise this and require students to set a fixed configuration of the following: VLAN 1 VLAN 10 VLAN 20 Task 1 All OK Task 2 All OK Task 3 All OK Task 4 All OK Root Bridge -> SW1 Root Bridge -> SW1 Root Bridge -> SW2 Lab 1-3: Configuring EtherChannel Setup No additional setup required. Instructor to load the pod SW1 and SW2 Lab 1-3 configuration(s), if student(s) have not completed Lab 1-2 successfully. Task 1 All OK Task 2 All OK Page 9

10 Lab 2-1: Troubleshooting IP Connectivity Setup Students to load the Podd Lab 2-1 configuration viaa the Device Management tool on the t Studentt Pod Web Access page. Instructor to load the pod SW1 and SW2 Lab 2-1 configuration(s), if student(s) have not completed Lab 1-3 successfully. Task 1 All OK Task 2 All OK Task 3 Note: The Cisco CAG guide requires that the Instructor amends the Default Gateway address all of the Pod PC1 s. This iss impractical on the Remote Lab setup. However, in order to provide thee troubleshooting lab, the IP address of the router has been amended in the configurationn to /24. This will have the same effect ass changingg the PC default gateway, however students may need to add extraa steps to review the B router config to discover the fault. Although the PC default gateway could be amended to reflect the router r IP, to maintain compatibility withh later labs, students should s amend the route IP back to /24 Page 10

11 Lab 3-1: Implementing EIGRP Setup No additional setup required. Instructor to load the pod Lab 3-1 configuration( (s), if student(s) have not completed Lab 2-1 successfully. Task 1 All OK Task 2 All OK Task 3 All OK Task 4 All OK Lab 3-2: Troubleshooting EIGRP Setup Students to load the Podd Lab 3-2 configuration viaa the Device Management tool on the t Studentt Pod Web Access page. Task 1 All OK Task 2 Step 2: On the HQ router, enter: show ip protocols vrf PodPP (where P is the pod number) e.g. for Pod 2, the command would be show ip protocols vrf Pod2 Task 3 Step 2: On the HQ router, enter: show ip protocols vrf PodPP (where P is the pod number) Page 11

12 Lab 3-3: Implementing EIGRP for IPv6 Setup Instructor to load l the HQ Lab 3-3 configurationn via the Device Management tool on the Instructor Web Accesss page. Instructor to load the pod Lab 3-3 configuration( (s), if student(s) have not completed Lab 3-2 successfully. This lab will use the pod-specific c IPv6 addressing as detailed in the Amended Job Aids table detailed earlier in thiss guide. Task 1 All OK Task 2 Activity Verification: Step 1: The command should read: show ipv6 eigrp interfacee Step 4: Note: As this is a shared network, if all are correctly configured, students will see other pod networks in the routing tables. Task 3 All OK Task 4 All OK Lab 4-1: Configuring Multiarea OSPF Setup Instructor to load l the HQ Lab 4-1 configurationn via the Device Management tool on the Instructor Web Accesss page. Instructor to load the pod Lab 4-1 configuration( (s), if student(s) have not completed Lab 3-3 successfully. Task 1 All OK Task 2 Step 1: The HQ routerr Neighbour ID will be pod-specific: 1.1.P.11 e.g. for Pod 3 the Neighbour ID would be: Step 5: On the HQ router, enter: show ip route vrf PodP ospf (where P is the pod number) Page 12

13 Lab 4-2: Troubleshooting Multiarea OSPF Setup Instructor to load l the HQ Lab 4-2 configurationn via the Device Management tool on the Instructor Web Accesss page. Students to load the Pod Lab 4-2 configuration via v the Device Management tool on the Student Pod Web Access page. Task 1 Step 13: Due to the vrf f setup on the HQ router, when accessing the HQ router, students MUST view and configure the correct OSPF O Process. Configure the pod-specific OSPF process with the following configuration command: router ospf P vrf PodP (where P is the pod number) E.g for Pod 2, the command would be: router ospf 2 vrf Pod2 Task 2 Steps 2 & 3: Due to thee vrf setup on the HQ router, r when accessing the HQ router, students MUST view and configure the correct OSPF Process. Step 2: Use the command: show ip protocols vrf PodPP (where P is the pod number) E.g for Pod 3, the command would be: show ip protocols vrf Pod3 Step 3: Configure the pod-specificc OSPF process with the t followingg configuration command: router ospf P vrf PodP Step 4: Students are not permitted to save changes to the t HQ router. They should only save changes to their t h router. Task 3 All OK Page 13

14 Lab 4-3: Configuring OSPF for IPv6 Setup Instructor to load l the HQ Lab 4-3 configurationn via the Device Management tool on the Instructor Web Accesss page. This lab will use the pod-specific c IPv6 addressing as detailed in the Amended Job Aids table detailed earlier in thiss guide. Task 1 Step 1: On the h router, configure the OSPFv3 routing process with process ID 1. The router must have router ID 2.1.P.2 (where P is the pod number). Step 4: On the router, enable OSPFv3 in Area 0 on the interface Serial0/0/0. Enable OSPFv3 in Area P on interfaces FastEthernet0/ 0.1, 0/0.10 & 0/0.20 Note: Although all pods could usee Area 1 for their FastEthernet interfaces and the lab will still work, this would implyy a dis-contiguous Areaa 1 and is not good practice. Activity Verification Step 4: Students will seee other podss in their OSPF routing table. These other Pod routes should appear as OI (Inter-Area) routes. Page 14

15 Lab 5-1: Configuring and Troubleshooting a Serial Connection Setup Instructor to load l the HQ Lab 5-1 configurationn via the Device Management tool on the Instructor Web Accesss page. Students to load the Pod Lab 5-1 configuration via v the Device Management tool on the Student Pod Web Access page. Task 1 Step 4: The debug pp pp negotiation command will produce a LOT of output. Students will have to wait a long time after issuing the no debug all command for the output to cease. It may be preferred to power-cycle the router, via the Pod or Instructor Power Control tool to clear the t debug output. Step 8: It is advisable at this point to issue the shutdownn commandd to the router Serial0/0/0 interface. This will ensure a clearer output of the debug pppp authentication command in Step 10: Step 10: On the router, Serail0/0/0 interface, issue the no shutdown. Observe the PPP authentication debug output. Task 2 Step 2: The HQ routerr Serial interfaces are pod-specific. Students MUST configure theirr correct pod-specific interface. Job Aids: Serial Interface Table Pod HQ Router Serial Interface Serial1/0 Serial1/1 Serial1/2 Serial1/3 Serial1/4 Serial1/5 Task 2 Step 5: Students are not permitted to save changes to the HQ router. They should only save changes to theirr router. Page 15

16 Lab 5-2: Establishing a Frame Relay WAN Setup Instructor to load l the HQ Lab 5-2 configurationn via the Device Management tool on the Instructor Web Accesss page. Task 1 Step 4: Students MUST configure the correct pod-specific Serial interface on the HQ router, as detailed in the previouss lab notess above. e.g. for Pod 4, the commands sett would be: frame-relay switching! interface Serial1/3 encapsulation frame-relay frame-relay map ip frame-relay interface-dlci 120 frame-relay intf-type dce Task 2 All OK Task 3 Step 6: On the HQ router, configure the correct pod-specific Serial interface. Step 7: Students are not permitted to save changes to the t HQ router. They should only save changes to their t h router. Page 16

17 Lab 5-3: Establishing a GRE Tunnel Setup - No additional setup required. Task 1 Step 1: Additionally, it is recommended to configure c keepalive on the router Tunnel0 interface. Otherwise the interface status will not correctly reflect the tunnel status. i.e. will show up/up, even though the corresponding HQ tunnel interfacee is actually shutdown and showing up/down. Note: The HQ router Tunnel interfaces are pod-specific. However, they are configured within the pod-specific vrf, so the addressing is NOT T pod-specific and should be configured as per lab steps. Step 2: Use telnet to connect to the HQ router and enable interface TunnelP (where P is the pod number). Task 2 Step 9: Students are not permitted to save changes to the HQ router. They should only save changes to theirr router. Lab 6-1: SNMP and Syslog Basicc Configuration Setup - No additional setup required. Task 1 All OK Task 2 All OK Page 17

18 Lab 6-3: Managing Cisco Devices and Licensing Setup Students to load the Podd Lab 6-3 configuration viaa the Device Management tool on the t Studentt Pod Web Access page. Task 1 Perform the configuration load as described inn Setup above. Task 2 Step 2: Power-cycle the router via the pod webb page Power Control tool. To issue the BREAK console key sequence: If using TeraTerm: ALT+B If using Putty: Right-click Puttyy Title Bar, select Special Command and Break Task 3 The TFTP Server is already configured with a directory of C:\tftp Task 4 All OK Task 5 Step 1 Lab router installed licenses are: Feature: Gatekeeperr Feature: gsmamrnb-codec-pack Page 18

19 Lab S-2: ICND2 Super Lab Setup Instructor to load l the HQ S-2 Super Lab configuration via the Devicee Management tool on the t Instructor Web Access page. Students to load the Pod, SW1 and SW2 S-2 Super Lab configurations via the Devicee Management tool on the Student Pod Web Access page. Job Aids: Topology and IP Addressing Device Interface FastEthernet0/0.1 (vlan 1) FastEthernet0/0.10 (vlan 10) FastEthernet0/0.20 (vlan 20) FastEthernet0/1 IP Address & Subnet Mask ipv4: / /24 ipv6: 2001:DB8:0A01:10P::1/64 ipv4: /24 ipv6: 2001:DB8:0A01:A0P::1/64 ipv4: /24 ipv6: 2001:DB8:0A01:140P::1/ :DB8:D1A5:C90P::1/64 HQ HQ SW1 SW2 PC1 PC2 Serial0/0/0 FastEthernet0/1.9P LoopP (ipv4) Loop0 (ipv6) VLAN1 VLAN1 Class LAB Interface Class LAB Interface / :DB8:D1A5:C90P::2/64 ipv4: /24 ipv6: 2001:DB8:AC10:100::64/ / / / /244 Task 1 Step 5: Use the router interfaces ass in the table above. Task 2 All OK Task 3 All OK Task 4 All OK Task 5 All OK Task 6 All OK Page 19

20 Task 7 Step 2: Use router interface FastEthernet0/1 inn place of interface Serial0/0/0 Interface FastEthernet0/0.1 (vlan 1) FastEthernet0/0.10 (vlan 10) FastEthernet0/0.20 (vlan 20) FastEthernet0/1 IP Address & Subnet Mask 2001:DB8:0A01:10P::1/ :DB8:0A01:A0P::1/ :DB8:0A01:140P::1/ :DB8:D1A5:C90P::1/64 Task 8 All OK Task 9 All OK Task 10 Step 1: On the router, enable the following interfaces for OSPFv3 in Area 0. Use OSPFv33 process ID 1: FastEthernet0/1 (in place of S0/0/90) FastEthernet0/0.1 FastEthernet0/0.10 FastEthernet0/0.20 Task 11 Students can telnet too the HQ router and use u the show access-lists able to modify this to fix. However, they can amend the IP address of o PC2 to to command to verify the ACL is blocking the pings. They will not be prove that it is the ACL blockingg only the.100 address. Page 20

21 7. Support Information is our preferred primary method of contact. The Support Team address Telephone Support Direct Telephone Line: +44 (0) Other Contact Methods We do not normally encourage contact methods (e.g. Skype, Lync, MSN etc.) ), other than the above, as these other methods often do not easily providee a means to t record and track support information. Such information is importantt to us, as it allows us to continually monitor and improve our support service to you. Page 21