The #CCNA exam can pack a punch with what looks like a simple question, and this latest practice question is just such an example. The question asks about switch forwarding, but it combines packet encapsulation concepts. Get either wrong, and
You can learn how a LAN switch forwards frames in just a few minutes, and then explore that idea in different contexts throughout your entire span of studying for #CCENT and #CCNA Routing and switching. This latest practice question asks
This lab was pretty straightforward, but this answer post makes little sense without looking at the lab post first. Read the requirements, remember the command, get the syntax right, and move on. Answers below the fold.
The CCENT and CCNA R&S certifications include many prominent features that need to be configured. VLANs. Trunking. Routing protocols. IPv4 addressing. IPv6 addressing. But there are also the occasional small topic or single command that might be forgotten. This lab
This lab asks you to work through a few login security options in IOS. Should be a quick and easy lab. Check out the requirements here first, and come back to this post for the answers.
One of the first configuration items that becomes second nature is the configuration of basic password settings. But it is also easy to forget about the small differences in password security configuration once you get used to configuring your own
Cisco Catalyst switches typically allow Telnet/SSH access as a matter of habit. For practice, check out the earlier lab exercise, create your own answer, and check your answer against this blog post.
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, such
Do you know how to configure local usernames, and enable their use for login security on a Cisco router? No more sharing the same login password among all the network engineers. If you want some quick practice, go back
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 to configure
