My local Control was getting a DHCP address from the Route 10 for the VLAN it’s on. I wanted to make that a static address, so I went to the Control under devices and set the VLAN and the IP (an IP within the static range (first 10 IPs) and now I can’t access the controller. Ping fails on static IP and ping to ddns address shows default VLAN. I am able to recover by plugging the control into a port on my Alta 8 port switch that’s on the default VLAN. I can then reset the device VLAN and IP back to default and then plug it back into the Route 10 and it gets a default VLAN IP. I then can change the VLAN on the port and the Control with get the original DHCP IP again. Am I missing something when trying to set it to a static IP?
Sounds related to this:
and this:
and similar to my own issue:
The problem seems to be that changes in the Device’s card changes the port settings in a somewhat unintuitive way.
Could you show a screenshot of how you are configuring the VLAN?
Thanks @ebuckland81 Sounds like I may be hitting some bugs
And how have you defined the VLAN 460? Can you share that screenshot as well?
Right now I have it plugged into the Alta 8 port switch and that port is configured for a Default VLAN. So it got a DHCP IP from there. That’s how I can access it and provide you these screenshots.
What does the original port, that it was attached to, but sent off from / locked out of, look like now?
Thanks. Have you configured this VLAN on the Route10 interface as the Native VLAN?
check what is selected in “Allowed VLANs”. I bet 460 isn’t checked…
Right now Allowed is showing Default (in screenshot above) which I thought would just tag everything
maybe check what you want individually and give it a try? I am starting to wonder if it really does what we think.
I’m just plugging the control into that port so I wouldn’t think I would need anything else. I would think I just need the native VLAN since this is basically an access port.
The port in the screenshot is the one used after recovery, right?! Do you also have info on the port that it was plugged into when being kicked off.
The screenshots are of the port the control was originally plugged into. Right now I have it plugged into a POE port on the Alta Labs 8 ports switch. That ports is configured Default. See screenshots.
My guess is the port setting takes precedent over the device setting. So since the port is Default, the Control is getting a Default IP even though the device says it should be on 460 with a 10.4.60 IP. Doesn’t explain why the port on the Route 10 that’s currently showing 460 as the VLAN doesn’t issues the static IP to the Control when it’s plugged in there.
Right now I can set the port on the Route 10 back to Default and set the Native VLAN and IP on the device back to Default and blank IP. Then bring the Control back over there to the Route 10 and plugit back in and it will come online. I can then change the Native VLAN to 460 and it will get a 460 DHCP IP. However if I set the device to 460 and give it an IP while it’s over there, then the connection is lost.
Thanks. So it seems like your trouble is with just the device override setting specifically. Is that correct?