I have some clients that are unable to get a DHCP address during the PXE boot. The clients are directly connected to a 48-port switch module on a Cat4006 chassis. I have enable spantree portfast on all ports that the clients are connected to. IP Helper is also configured on the vlan interface. Is there an additional configuration needed on the port or switch for PXE to work. Is it that this is not possible on the switch?
I will test these options and will go from there. Unfortunately I will not be able to test until next week.
I would like to add something that I should have added in my first post. I have other clients that are on the same vlan but just not directly conencted to the switch module on the chassis. They are connected to a 3500XL switch and then fiber to the chassis. Ports on the 3500XL switch are set to portfast. These clients are able to pickup a DHCP address fine. Which leads me to believe that the DHCP and PXE Server are configured correctly. Is it that clients that are connected to the switch module need these options set? Also, once the troubled workstations boot into the operating system, they are able to pick an address.
Let me know if you have any thoughts on this. I will look into the dhcp options.
One thing you can do is to connect this same client having problem to the switch where you said clients are not having problem. I do not think it is a switch specific issue but this is one way you can confirm. If the same clients having problem in the 4006 is also having problem while connected to 3500XL then that would tell you that the problem is not switch related. compare the clients not working and the ones working such as their settings.
I ended up adding an access switch (3500XL) and connected the troubled clients there instead of to the chassis. I am uplinking that switch to the chassis using fiber. All works fine that way. There is nothing wrong with the clients. There is something on the chassis switch module's configuration that I may be missing. This will be my permanent solution, but I would like to figure out what the issue is regardless.
What command did you use to enable portfast on the 4006 . I have seen in the past in certain situations that portfast may not work (most cases it does ) , try using the command "set port host" on all client user ports , this will also turn off any trunking and channeling on the ports which adds to the delay on port activation.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...