Next, a little cosmetic stuff for the client switch. Of course, you can use an external DHCP server, but this is a convenient spot.īldg-a-dist(config-if)#vstack dhcp-localserver SMARTPOOLīldg-a-dist(config-vstack-dhcp)# address-pool 10.0.0.0 255.255.255.0īldg-a-dist(config-vstack-dhcp)# file-server 10.0.2.10īldg-a-dist(config-vstack-dhcp)# default-router 10.0.0.1 Whatever happened to dynamic desireable by default?īldg-a-dist(config)#interface FastEthernet0/2īldg-a-dist(config-if)# switchport mode dynamic desirableįirst, we need to tell the switch it will be doing DHCP. Set your trunking correctly so the new switch can come up. Just place it where you need it, and make sure the switch can reach it. My TFTP server is directly attached, so my final configuration will have a local VLAN and SVI, but that is not necessary. Although, as you will see, this is the only “regular” DHCP command you will see.īldg-a-dist(config)#ip dhcp excluded-address 10.0.0.50 10.0.0.254 If needed, exclude the usual areas for the VLAN from DHCP as per your usual rules. Here I am being original, as this is the distribution switch for fictional Building A: Put an IP address on VLAN1 SVI, as we will use the switch as the DHCP server for the client switches: The Smart Install uses the vstack commands, but first some basic housekeeping. Now we start configuring the distribution switch. You can make a standardized template configuration for each switch type, model or even stack member put in passwords, TACACS+, whatever as you need it. No need for configuring 24 ports, plus it only has one Gigabit port. In this case, I am using a C2960PD-8TT-L, so I am calling the configuration file “2960_8_baseconfig.txt” for the 8-port switch. A configuration file you want to upload to the new client switchīy naming your files appropriately, keeping switch models separate, you can create custom base configs for different types – 8-port, 24-port, PoE, and so on.The configuration is slightly more involved, but it lets you prepare for the future without having to back out a single model config. I am going to prep this as if I was going to be using a couple of different model workgroup switches. However, I have used the director switch as the DHCP server for the management VLAN, as it seems a logical place to do it, although you could futz around with your central DHCP server to do the job, too. The director can host the TFTP server locally, although if you have a mixed client-switch environment, this can become cumbersome I prefer a centrally-located TFTP server. Cisco calls the switch that provides the information (image names, configurations, etc) the “director”. Where I worked, this was the typical building network block a C3750-class distribution switch and C2960 workgroup switches. For more information on that, see the Cisco documentation.īelow is a diagram of the setup I am going to use. The true zero-touch install requires that the “client” switch be at least version 12.2(52)SE, although there are methods whereby switches with older software can be bootstrapped. Another useful thing is that Smart Install has a neat backup facility which is on by default. The Cisco Smart Install process can be useful so you can send out an unopened new switch, have your remote arms-and-legs rack it up and magically, the switch comes on line with a current image and a standard configuration. Or maybe you just want to make sure all new switches have the latest IOS image you are using and a basic standard configuration. Working in an environment where you have few staff resources, especially at remote sites, deploying workgroup switches can be a bit of a pain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |