Config Lab 200-301
Config Lab: Switch IP 1
A layer 2 switch does not need an IP address or default gateway for its primary purpose of forwarding layer 2 Ethernet frames. However, the switch does need an IP address and a default gateway for layer 3 communication, suchConfig Lab: Enabling SSH and Disabling Telnet
Many of us start out learning about the simplest Cisco security option: One password for all users to reach user mode, with no per-user login. By today’s standards, that security method is archaic. Today’s lab lets you upgrade from thatConfig Lab: CLI Passwords 2
The simplest way to protect the CLI uses passwords shared by all, rather than a per-user username and password. Using a per-user login method improves security. The easiest option for using per-user logins in a Cisco lab is configuring theConfig Lab: CLI Passwords 1
Protecting access to the CLI of Cisco routers and switches starts with basic password security. From there, you can move on to use per-user login security that requires both a username and password, whether using locally-configured username/password pairs or whetherAnswers: IPv6 Extended ACLs 1
This latest lab breaks the config lab mold just a tad, but for a good reason. It looks like a straightforward config lab, requiring just 10 minutes or so to do on paper. But it sets you up for one
IPv6 Extended ACLs 1
Are you comfortable matching packets with extended IPv6 ACLs? How about with TCP and UDP ports in those ACLs? Here’s a 10-minute lab exercise to practice; all you need is the time and a piece of paper or a place
Answers: IPv6 Standard ACL 1
The previous lab exercise requires you to configure a standard IPv6 ACL. The address range matching should be pretty straightforward. You also need to choose where to put the ACL, and for which direction of flow for the packets. As
IPv6 Standard ACL 1
IPv6 ACLs – new to #CCNA with the 2016 exam revisions – include both standard and extended ACLs. However, IPv6 standard and extended ACLs have only subtle configuration differences. This lab helps you notice those differences with a lab that
Answers: Protecting CLI Access 2
This lab was pretty direct: configure an ACL and use to to protect CLI access rather than filter packets being routed by the router. You know the drill – read lab, do lab, check here.