I have a few MS120 switches in use. According to the Routing & DHCP page these switches should support DHCP relay (but no other L3 functions). I'm currently using my MX67 for DHCP relay but I thought I'd test it out on the MS120 to see what happened. Well, it doesn't work, no DHCP messages are seen at the DHCP server sourced from the switch. I'd expect to see a forwarded DHCP request with the GiAddr set, but nothing shows up. As soon as I enable DHCP relay on the MX67 again, for the same VLAN, the messages start appearing, so I would expect the switch to do the same.
Has anyone tried and/or tested this on the MS120? It seems broken to me. My switch is running whatever the current stable release is. I haven't jumped on the beta release yet to see if that changes anything.
The port that the DHCP server is in. Is that a trunk port? You also said it's in a different VLAN are you sure the VLAN on the MX is configured correctly to route to other VLANs. I know sometimes you have to enable it on MX ports.
I think for DHCP relay to work (not sure on this one) the MS120 management IP address would need to be in the source VLAN that is being forwarded.
Do you have DHCP Scopes setup? We have a single domain that uses 5 different /19 scopes across our sites, with MS320s setup to relay to Windows DHCP servers. However, the one that has it's interface IP set in the same scope as the DHCP server cannot be set to relay. If I recall right, the web interface won't allow you to make this change if that's the case. I wouldn't imagine it's much different for the MS120.
@Adam2104 What is the IP address of your DHCP server and the IP address of the interface on the MS120 from the Routing and DHCP page?
From what I can tell, a DHCP relay should work on all but the VLAN 40.
Essentially it should look like this (I think):
Int IP 172.28.0.250
DHCP Relay to 172.28.4.254
Rinse and repeat, except for VLAN 40 which should not be able to have a relay set. Again, this is my experience with my MS320s which are a bit more robust on L3, but I do have some MS220s that are comparable to the 120 and that looks like an appropriate config for them. I can check later when I won't interfere with business functions.
There used to be a bug that existed on the MS120 where configured pseudo-L3 interfaces (for IGMP / DHCP) did not respond to received ARP requests. This was fixed in MS 10.42. I know you mention you are running stable firmware, currently 10.45. If somehow you're below 10.42 though, an upgrade would be worthwhile to rule out the known issue.
I actually just tested this on current 11.x with an MS120 and I do see it responding to ARPs for pseudo interfaces configured with DHCP relay. You may want to open a support case in the event something else is going on in the environment. Note if the interface is configured only for IGMP and not DHCP relay, it may not respond to ARPs. The IGMP case is even simpler, it just transmits a flooded IGMP multicast packet periodically. There is no ARP or next-hop resolution involved with this.
I can share two data points regarding these interfaces that are helpful to be aware of:
1. Packets generated by the pseudo interface which need to be routed, such as a DHCP Discover being routed to the configured relay IP(s), will always route to the next hop of the gateway being used for the uplink interface of the switch. You will note when configuring a pseudo interface, there is no configuration for subnet. This is because packets always route to the default gateway in use by the uplink interface. So whatever this gateway is, it will need to accept and route this traffic properly.
2. Pseudo interfaces will not respond to ICMP / pings. They only accept and route the requisite DHCP packets. They are very limited in terms of additional functionality that would work on a full fledged SVI. This is because they exist on an L2 switch -- the switching ASIC using on the MS120 does not support L3 routing, so the very specific use cases of having an IGMP querier and DHCP relay endpoint are implemented in software.
On Cisco "classic" you have to put ip-helper addresses to the VLAN´s to allow DHCP requests over different VLANs:
description Management VLAN
ip address 10.1.0.1 255.255.254.0
ip helper-address 10.1.2.10
ip helper-address 10.1.2.11
ip helper-address 10.1.2.12
no ip redirects
ip directed-broadcast 101
no ip proxy-arp
arp timeout 60
maybe you can do this on a MX ?