![]() On my home network, I have a Cisco ASA5505 doing DHCP assignments without having to worry about UPnP nor have any of my large scale business network designs. You don't really ever see this in a business application. UPnP is a feature only found in the home market. If there is, the switch just moves to the next IP in the scope and checks that for assignment. ![]() The other feature the 6509 has was the ability to pre-ping an IP address it is about to assign to ensure there is no device on the network already responding to that IP. ![]() The Cisco 6509 switch I used for the DHCP server allowed me to have DHCP redundancy which was not possible with Windows server. The other was the ability to do more with the network configuration I did. One is the need to configure DHCP relays on the network to forward the DHCP requests from the various devices to the DHCP server. If I did the server route, I would have a number of challenges. The setup was a building with 8 floors, about 500 ish workstations, and multiple network subnets. The last system I built had a migration away from the AD server doing the DHCP duties and the core network switch picking it up. There are two schools of thought for where the DHCP server resides: on a network device or on a server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |