You may remember me from such questions as "why isn't my IOS working, oh, it's not the right version, it has the wrong filename".
Well, the reason I wanted to upgrade is so that all my various 2960s across the network would have the ability to use DHCP Snooping...the last tool in my toolkit to help eliminate people plugging in home routers and switches and making headaches for the other users.
My question deals with the trusted port designation. My DHCP servers for my one enterprise vlan which the users are on (we'll call it vlan 42) are on various switches trunked through-out my network.
Since the DHCP servers reside so far away physically...when I attribute ports to be "trusted" do I put that attribute on the trunk ports of each switch until I get to the switch the DHCP servers are on and designate the actual physical ports they are connected to as trusted as well?
I am sorry to ask such a basic question...but everyone's diagrams are about DHCP servers that reside on the same physical switch as the network they are serving...and I can't imagine that for many of use this is the case.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...