Discovery 1: Investigate the CAMThrough this discovery, you will investigate the contents and properties of the CAM table of a switch. You can display the CAM table to verify the information that the switch has learned. The table will also tell you out of which port the address was learned, along with the VLAN information. |
Discovery 2: Analyze Cisco Express ForwardingIn this discovery lab, you will verify Cisco Express Forwarding operations. You will inspect both the FIB and adjacency table, and see how their content updates to reflect changes in the control plane. You will also learn how to enable and disable Cisco Express Forwarding. |
Discovery 3: Troubleshoot VLAN and Trunk IssuesThis discovery will guide you through a scenario involving VLAN configuration, Layer 2 connectivity, and IP connectivity. The topology diagram is intentionally vague and there is no connectivity table. Imagine you are on your first day at a new job as a network engineer. You are not yet familiar with the network of your organization. A member of the security team comes to you because the intrusion prevention system has flagged malicious traffic from the IP address 10.10.10.182. You are asked to help in isolating this system and removing it from the network. |
Discovery 4: Tuning STP and Configuring RSTPIn this discovery, there are two loops in this topology: SW1-SW2-SW3 and SW2-SW3. The network has been wired in such a way that it provides redundancy. But, Layer 2 loops will also occur in this topology if STP does not block redundant links. |
Discovery 5: Configure Multiple Spanning Tree ProtocolIn this discovery, you will learn how to configure and verify MST. |
Discovery 6: Troubleshoot EtherChannelIn this lab, you have two switches, SW1 and SW2 connected via four Ethernet links. The Ethernet interfaces have been bundled to form two EtherChannels as shown in Topology. The interfaces E0/0 and E0/1 have been grouped to form Port-channel 1 while interfaces, E0/2 and E0/3 have been grouped to for PortChannel 2 on the two switches. PC1 and PC2 are in VLAN 11. Dot1q trunking has been enabled on the interfaces. The switches are intended to operate with devices of other vendors, therefore, only standardized protocols should be used. Switch SW1 needs to initiate the EtherChannel while switch SW2 should only respond to it. |
Discovery 7: Implement Multiarea OSPFThrough this discovery, you will learn how to configure and establish OSPF neighbor relationships in a multiarea environment. You will observe the impact of the interface MTU and OSPF hello and dead timer parameters on the OSPF neighbor relationship formation. In addition, you will learn about the roles of DR and BDR routers, and how to control how they are elected to those roles. |
Discovery 8: Implement OSPF TuningIn this discovery, you will learn how to tune the behavior of OSPF. You will first start by investigating the network topology and the current OSPF configuration. You will then enable passive interfaces on DIST and BR, configure OSPF default routing, investigate Equal-Cost Multipath load balancing, and adjust OSPF default and interface cost values. |
Discovery 9: Apply OSPF OptimizationThrough this discovery, you will explore OSPF optimization by first implementing route summarization on ABRs and ASBRs in an OSPF environment, and then examining the impact of summarization on the OSPF database and internal routing. |
Discovery 10: Implement OSPFv3Through this discovery, you will learn how to implement OSPFv3 in a dual-stack (IPv4/IPv6) environment. The routers R2, R3, and R4 have been completely pre-configured. R1 has been preconfigured with the necessary IPv4/IPv6 addresses but does not have any routing protocol configuration. On R1, you will first configure OSPFv3 for IPv6 in the traditional way, in which a dedicated OSPF process serves the IPv6 protocol. Then you will migrate the configuration to the newest configuration approach, in which a single OSPFv3 process serves both IPv4 and IPv6 address families. |
Discovery 11: Configure and Verify Single-Homed EBGPIn this discovery lab, you will configure external BGP between a service provider and its two customers. You will configure the provider router (SP1) to establish a separate, single-homed EBGP session with each of the customer routers (R1 and R2). |
Discovery 12: Implementing HSRPHot Standby Router Protocol (HSRP) is a Cisco proprietary protocol that wasdeveloped to allow several multilayer switches or routers to appear as a single gateway IP address. |
Discovery 13: Configure VRRPVRRP is similar to HSRP, both in operation and configuration. The VRRP master is analogous to the HSRP active gateway, while the VRRP backup is analogous to the HSRP standby gateway. A VRRP group has one master device and one or multiple backup devices. A device with the highest priority is the elected master. The priority can be a number between 0 and 255. The priority value 0 has a special meaning—it indicates that the current master has stopped participating in VRRP. This setting is used to trigger backup devices to quickly transition to master without having to wait for the current master to time out. |
Discovery 14: Implement NATIn this discovery lab, the internal network consists of three subnets using private addressing. Each subnet will be used to demonstrate the configuration of one type of NAT implementation: static, dynamic, and PAT, to access an Internet resource. |
Discovery 15: Configure and Verify VRFThrough this discovery, you will implement path isolation using VRF-Lite. First you will verify the existing OSPFv2 configuration on all Customer routers. You will then deploy VRFs on the ISP router for each Customer. Finally, you will enable OSPFv2 on the ISP router for both Customers and verify that routing and path isolation has been successfully implemented. |
Discovery 16: Configure and Verify a GRE TunnelThis discovery will guide you through the configuration, verification, and usage of a GRE (Generic Routing Encapsulation) tunnel to connect IP (Internet Protocol) networks by using a completely different IP network as a transit link. The live virtual lab is prepared with the devices that are represented in the topology diagram and the connectivity table. All devices have their basic configurations in place, including hostnames and IP addresses on the Ethernet and loopback interfaces. |
Discovery 17: Configure Static VTI Point-to-Point TunnelsIn this task, you will implement a static VTI point-to-point tunnel configuration on the R2 router to enable it to establish a VTI point-to-point tunnel with the R3 router. This will enable hosts at the R2 site and hosts at the R3 site to securely exchange data across the Internet. Hosts on each network will be able to access resources on the other network as if directly connected to the other private network, while benefiting from the functionality, security, and management policies of that private network. |
Discovery 18: Configure Wireless Client Authentication in a Centralized DeploymentIn this activity, you will configure the Cisco 9800-CL Campus WLC to provide security in a centralized WLAN deployment by implementing WPA2-PSK, 802.1x EAP, and WebAuth security. Finally, it will be important to verify and test each security method. Note: This is a heavy lab, it loads in arround five minutes. Allow extra ten minutes after lab loads for Cisco ISE to be ready. |
Discovery 19: Troubleshoot Wireless Client Connectivity IssuesIn this discovery lab, clients are to connect to one of two different WLANs, Sales (VLAN 30) or Accounting (VLAN 40). The AP the clients are connecting with has been configured via a Cisco 9800 WLC. Both WLANs are part of a location called Campus. The users connecting to the Sales WLAN are to use PSK authentication, and the users connecting to the Accounting WLAN are to use 802.1x authentication with an external RADIUS server (ISE). The Job Aids section has more device information such as IP addresses, usernames, and passwords. Note: This is a heavy lab, it loads in arround five minutes. Allow extra ten minutes after lab loads for Cisco ISE to be ready. |
Discovery 20: Configure SyslogThe objective of this discovery lab is to provide you with some experience with the syntax of basic syslog configuration to facilitate the management of Cisco IOS devices. This lab is prepared with the router and server that is represented in the topology diagram and the connectivity table. The devices have their basic configurations in place, including hostnames and IP addresses. |
Discovery 21: Configure and Verify Flexible NetFlowThe objective of this discovery lab is to provide you with some experience with the syntax of a Flexible NetFlow configuration to facilitate the capture of a traffic flow. This lab is prepared with the devices that are represented in the topology diagram and the connectivity table. The devices have their basic configurations in place, including hostnames and IP addresses. |
Discovery 22: Configuring Cisco IOS Embedded Event Manager (EEM)In this Lab, you use the Embedded Event Manager (EEM) built into IOS to create track and classify events and create notification options for these events. |
Discovery 23: Troubleshoot Connectivity and Analyze Traffic with Ping, Traceroute, and DebugIn this discovery lab, you will learn how to troubleshoot connectivity and analyze traffic on Cisco devices, using the ping, traceroute, and debug tools. |
Discovery 24: Configure and Verify Cisco IP SLAsTo verify that response times across the WAN are within an acceptable range that is defined in the corporate SLA, you will configure Cisco IOS IP SLAs to perform an ICMP echo and a UDP jitter test. |
Discovery 25: Configure Standard and Extended ACLsThrough this discovery, you will review the implementation of standard and extended ACLs using both numbered and named configuration methods. SRV2 is a public DNS server. The domain names of the devices are the same as their hostnames. SRV1 and SRV2 are also HTTP/HTTPS servers. |
Discovery 26: Configure Control Plane PolicingThrough this discovery, you will learn how to configure a CoPP policy. CoPP allows you to use the MQC (Modular QoS CLI) framework to permit, deny, or rate-limit traffic that goes to the route processor. For this discovery, you will police OSPF, VRRP, ICMP, and Telnet traffic being sent to R1’s control plane. |
Discovery 27: Implement Local and Server-Based AAAThrough this discovery, you will review the configuration of SSH, and enable both local and server-based authentication, authorization and accounting. |
Discovery 28: Writing and Troubleshooting Python ScriptsYour configuration tasks are as follows: Write a Hello World Script. Write a Network Script. Analyze and troubleshoot a script. |
Discovery 29: Explore JSON Objects and Scripts in PythonIn this lab exercise, you will first learn to work with basic JSON objects using the JSON module in Python. It will become important to understand and know as you start working with REST APIs that are returning data in JSON. |
Discovery 30: Use NETCONF Via SSHThe first step in seeing NETCONF and YANG in action is to use the SSH connection to the NETCONF server on the IOS XE devices. This connection allows you to test and verify that NETCONF is working, and to see what NETCONF and YANG look like on the wire when they are accessed directly via SSH. When using NETCONF and YANG integrated with your own automation and network management systems, you would most likely use one of several development libraries and tools, such as ncclient and the Yang Development Kit (YDK). |
Discovery 31: Use RESTCONF with Cisco IOS XE SoftwareRESTCONF, defined in the draft, is a mapping of NETCONF operations and datastores, with YANG models, to a RESTful API. In this discovery lab, you will see how RESTCONF works with Cisco IOS XE Software. The use cases that you will examine here will mirror those cases that you examined with NETCONF and ncclient in the previous discovery lab, so you can compare and contrast the different API approaches. It is important to note that although RESTCONF tries to implement NETCONF-like behavior, there are many differences. Also note that RESTCONF is still evolving and is not yet a formal RFC standard. Cisco IOS XE implements a much earlier version of the current draft, so the RESTCONF that you use in this lab may differ from RESTCONF as other technologies implement it. |