Video není dostupné.
Omlouváme se.
Protect Your CLI! Simply.
Vložit
- čas přidán 18. 08. 2024
- Learn how to protect your CLI with simple tips in this video. Perfect for CCNA 200-301 exam prep and mastering Cisco password configuration.
Video Vs. the Books:
As with all the videos in this playlist, the content mirrors the scope of content in one section of the Cisco Press CCNA Cert Guides, Volumes 1 and 2. In this case:
- Volume 1
- Chapter 6
- Section 1
Chapters
00:00 Intro
01:36 Securing the Console
08:05 Securing User Mode: Telnet
10:26 Securing User Mode: SSH
14:15 Securing Privileged Mode
16:19 Securing the Web User Interface (WebUI)
21:26 Exam Success
21:42 Review Activities
23:05 Wendell’s Cool Command
Links - New Books in 2024
Cisco Makes Minor Updates to the CCNA Blueprint (Version 1.1)
• Cisco Reveals CCNA 200...
Major Updates to the CCNA Books
• Minor CCNA Blueprint U...
Which Blueprint Should You Pursue? (2024)
• Which CCNA Blueprint S...
Product Links
Click the links below if you'd like me to earn a small affiliate sales commission if you buy anything from the publisher!
Ciscopress.com/NewCerts Page (News, Announcements):
click.linksyne...
Wendell’s Website Products page
www.certskills...
I always liked to learn from experienced people. Hope you will get a bigger audience!
Thanks! On the audience... I'm taking baby steps. Anyone can help - when it comes to mind, share a video on social or your favorite study board! But I know I need to produce much more to help build it. Thanks for the encouragement!!
Hi Wendell. Great video on how to protect the CLI. Very helpful how you explained each topic on securing the network. Exciting section on "Securing the Web User Interface". Very enlightening words on "Exam Success". Thank you!
Gus - thanks! You're a CCNA study machine!! :-)
@@networkupskill You're welcome! Wendell, you are so kind. I learn from the best..You!! :)
Hi Wendell - I didn’t know that you could shorten sh running-configure to sh ru bri - Excellent thanks 👍
Glad you like that video-ending feature! I hope to do that a lot in the series.
As always, good video, Wendell!!!
I appreciate that
Informative video. Thank you 🙂
Sure!
Gracias!
De nada, Carlos!
This question is related to the next topic of this chapter "enabling ipv4for remote access"
Im always confused with this
""The IP address has nothing to do with how switches forward ethernet frames ;it simply exists to support overhead management traffic""(volume 1-pg140)
so the problem is wen im going layer by layer we send bits which is changed to frames at layer 2 and then Ip pakets at l3 .all the vlan concept is packet based and we are mking vlans at switches .is .How will a switch at subnet 1 accept IP packets from pcs ?
ip address at switches vlans is a separate thing from frames (like its a different concept just to support overhead mangement traffic)
and layer by layer transmission is a different concept .
Hi Sana,
I believe you're the same Sana from the blog - welcome!
So, I think you're imaging functions for a layer 2 switch that it simply does not perform. Layer 2 switches perform functions at TCP/IP layers 1 and 2. At layer 1, it receives energy (electricity and light) and interprets that as binary (when receiving), and it takes bits and encodes them as electricity or light (when transmitting.)
Then, for layer 2, it does all the kinds of actions introduced in chapters 4 and 5: Evaluate the bits as a layer 2 Ethernet frame, find the destination MAC address, compare to the MAC address table, choose the outgoing interfaces, and forward the frame out those ports.
From your question, it appears that you believe that a layer 2 switch has more to do for its purpose of forwarding ethernet frames. It doesn't. For instance, you wrote "... and then packets at l3" - it doesn't do that. And: "The vlan concept is packet based". It isn't, at least in the ways I interpret what you mean. Or, "How will a switch at subnet 1 accept packets from PCs" - switches think about Ethernet frames, and don't care about the IP packets encapsulated inside them, at least for their primary purpose of acting as a switch.
So, maybe take a step back. Do you understand how layer 2 switching works? Then, when you see a device that performs routing, like a router or a layer 3 switch, then you can start thinking about the routing logic that is not used or needed on a layer 2 switch.
Hope that helps,
Wendell
@@networkupskill
yes im the same sana.
layer 2 switches purpose i understand is to forwarding frames only .
and routers forwards ip packets
but vlan interfaces are inside switches( virtually ).so why are we assigning ip address to vlans .at layer 2 we have mac addresses ?
Thanks for always clarifying.
@@sanafatima5653 Of course, Sana. Happy to help.
I understand now what's confusing you. When you configure a VLAN interface in a LAN switch, you're not assigning an IP address to a VLAN. I know, sure seems like it, right? But you're not. You're assigning an IP address to a VLAN interface. The VLAN interface is the switch's Layer 3 interface into the VLAN. Notice that with the config commands, it's not "vlan 10", with a new config mode prompt, and then the "ip address" command. There isn't one there. That's where you configure the VLAN. Instead, you type "interface VLAN 10", then the "ip address" command. You're configuring the switch's layer 3 interface that connects (internally) to the VLAN.
So, for a layer 2 switch to be managed (SNMP, SSH, Telnet), it needs one VLAN interface with an IP address.
On the chance you didn't look there, check out Figure 6-6 (I think you have Vol 1 Edition 1 - the one that does NOT have the green bit with "Edition 2 on it) - and the surrounding text.
@@networkupskill thanks!
One question, 18:25 I understand that's the basic configuration to have on a device but that is not automated by a tool like Catalyst Center (DNAC), is that correct?
Well, it could be, but I wonder how much you would use the WebUI of individual devices if you also had Cat Center. But if you wanted the feature configured... I imagine you could do it with configuration templates. I can't recall seeing it in any of the GUI screens in DNAC, though... although I'm no expert there.
EG, you could add the config to a Day-0 template so when a device is onboarded it not only gets CLI passwords and SNMP settings but also the WebUI settings. Here's a nice link on the basics from Adam Radford: blogs.cisco.com/developer/dna-center-pnp-day-0
@@networkupskill thanks