3 weeks ago
I have a core switch. From there every other access switch connects directly to the core in a star configuration. Each switch can have a single vlan or multiple vlans which are also defined on the core switch.
The core switch has all the vlans that every other switch has and each vlan on the core has an ipaddress assigned to it and each acts as a gateway ip for their respective vlan.
I have a single DHCP server connected to a vlan on the core.
For each vlan on the core I have enabled IP forwarding.
I also enable bootprelay on vr-default
i.e. enable bootprelay ipv4 vr VR-Default
On the core switch I have configured a gloable bootprelay on vr VR-Default
i.e. configure bootprelay add 192.168.1.100 vr VR-Default
Basically all the bootprelay settings are configured on the core.
My question. Do I need to define bootprelay on the other access switches if everything is handled on the core? I think all I need to do is define the vlan on a "access switch" without an IP address and without ipforwarding, or bootprelay. I believe if I have the same vlan on an access switch plugged into a port on the core with the same vlan and I shouldn't need to define any bootprelay on the access switch.
Is that correct?
Thank you,
a week ago
Just configure bootreplay on the core switch. Only the core switch has information about all VLANs.
2 weeks ago
What I found out and what I did. All the bootprelay settings are done on the switch where the DHCP server is plugged in. In my case, the DHCP server is plugged directly to the core switch so I only had to define the bootprelay settings there. No configuration for bootprelay were needed on any of the access switches.
2 weeks ago
Have you enabled IP forwarding on core switch for all your VLANs with IP interfaces where are you expecting to relay DHCP?
2 weeks ago
I think you have to configure, "configure bootreplay vlan "xxx" add 192.168.1.100 ", on the core switch for each of the vlans you need dhcp on.
On the other switches you don't need to define bootprelay.