Can't receive an IP from a newly created VLAN using DHCP

Hi,

the 169.254 is a self assigned IP address, nothing to do with the DHCP server, basically the address indicates that the device is not connected other VLAN. Please advise which version of XG you are running? Are your switched setup for L2 or L3 VLANs because earlier versions of XG only worked with L3 VLANs.

Ian

Hi,

the 169.254 is a self assigned IP address, nothing to do with the DHCP server, basically the address indicates that the device is not connected other VLAN. Please advise which version of XG you are running? Are your switched setup for L2 or L3 VLANs because earlier versions of XG only worked with L3 VLANs.

Ian

Are you referring to the firmware? If yes, here it is.

Our switches are setup for L3 VLANS

Thank you for the details. Do you have the VLANs terminating on the XG or on your core switch?

Ian

Here are the VLAN configured on XG

while these are the VLAN conifgured on the Core

Those VLANs are properly working (The other tech created those, but he's not around anymore). but then when I create a new VLAN, (for example, VLAN 130), i do not get a valid IP

Thank you, the port connected to the XG should be tagged and the other ports on the VLAN 130 untagged.

Ian

Here it is. But I still don't get a valid IP under VLAN 130

When you review the logviewer system what do you see?
ian

Your switch and the Sophos VLAN130 Interface have the same IP address, this won't work.

Give the 10.5.130.254 to port 4.130, this should work, then.

Hi. I tried changing the IP for Port4.130 to 10.5.130.254, but I can't still receive a valid IP. However, when I tried to put a valid IP Address statically on my test machine I was able to access the internet as well as our network. Can you help me? 

Did you restart the DHCP service?