I have been trying for a couple of days to set up a very simple Vlan. This is vlan 107 (IOT vlan 192.168.107.1/24) but not made it work
I create the vlan 107 on the Route 10 on the Gbic port that connects to port 8 on an 8 port switch. When I get to the config on the Switch the vlan is there but on all Ports, Not able to edit the list so delete vlan 107 and manually create it on port 8 (back to the router) and port 4 for the attached device) Edit the device to work on Vlan 107. This devices is a small pc that I can observer the ethernet set up and am never offered a 192.168.107.x IP adrress. I unplug the ethernet to force renegiotation of DHCP nothing. For such a simple proposition I cant get it to work. What am I doing wrong? To revert the vlan configs i delete the Vlans on the router and the switch and ammend the device profile to be velan 1 (I never leave it blank) I think the cloud management lags real time changes but have waited 5 mins between steps. Have explored the docker image but as its not downloading at the moment its a none starter. Both GBIC ports on the Route10 run at 1GB with the other being the PPPoE wan connection. The simplest I can get is Vlan 1 everywhere but this kit is overkill for that.
What make/model of switch are you connecting to @don.mclean?
Quackers instructions are correct. PVID is short for Port VLAN Identifier and sets the default VLAN ID for untagged traffic on a port.
Does your PC’s NIC support 802.1q VLAN tagging? Your alternative is to leave the PVID alone on the switch and set the VLAN tag to 107 on the network interface of the PC.
My New network is 100% Alta Labs 1 x Route10, 3 x 8 port powered switches and two AP’s of which one is a Pro.
So Im setting up an “Internet of Things” Vlan and these devices are very basic so no concept of Vlans. I also dont believe they should be vlan aware. The entire Vlan configuration should exist within the Alta sphere or Alta Universe.
The Routes 10 has direct connections to the three switches and powers the AP via PoE from ports 2 and 3 with the switches connecting to ports1,4 and gbic in 5. Port 6 is gbic to PPPoe to my service Provider. Vlan 1 will be the management VLAN by default. Vlan 107 IOT, Vlan 200 will be for Media (TV, Satellite boxes etc) and possible yVlan 80 will be for all browsing traffic to the internet. Thus segmentating the different yypes of traffice. Its not overly complicated as I asubscribe to Keep It So Simple )KISS) as there is less to go wrong and easier to fix if something does go wrong. IM happy to reset everything to defaults and start from scratch but im likely to make the same mistakes again. Is there a Knowledge Article that describes the type of Vlan (Router to End device on switch) which I require and the distinct steps to implement this? There is one for switches but when I configure the Route10 with Vlan xxx or yyy these are propagated through the network making the switch configuration KA starting point invalid. I know these are just teething issue. Hopefully later I will be able to enable QOS on the Media and Normal traffic vlans…
So for the last six hours I have been trying to understand these issue more indepth. I CAN do vlans over the WiFi which solves most of my IOT issues. However i am puzzled on how the router configured VLANS are propagated through the network… I decided to rest every device back to factory reset and restart from a known Vanilla starting point. How naive I was.
During the factory reset of the Route10 it does not issue dhcp Ip addresses out of Port 1 (The port my pc is connected to with the ISP going be configured on on WAN2 Port6 with a 1 GB gbic, as its only 500Mb/s
Connecting onto the Cloud controller I can see the Route10 and other alta labs devices I thought I had deleted before initiating the factory reset on all devices. It asks as this device has been reset do I want to reconfigure it again YES was my answer
The “cloud” has remembered the node name I gave the router previously .
2)Ports 1 and 4 on the router have a T displayed on the interface icon. when examing the port One, I can see its called WAN1 but configured as Standard and shows a native Vlan of 200 in existance./ Port 4 is known as Lan3 and has Native vlan 200 configured.
Im convinced these are orphaned remenents of previous configurations long ago deleted. Also Wan1 is named as AP-Downstairs and has never had an AP connected to it as I have to connect AP’s to port 2 and 3 for POE+
There is a large list of end devices which I have previously removed prior to factory reset. Interestingly several of the devices are in BOLD. I have deleted these devices several times but they persist. Thr route10 is on the table in front of me with two connections 1 to the internert 2 to my local pc as no alta wifi device switched on. After performing all the above Port4 (my PC) would no longer issue DHCP addresses. so I hade to move the cable into port three to type this. Another factory reset and I can see the phantom Native Vlans are again present.
Presently I have no Alta network as I cant get back to a known steady state condition to restart configuration again. Running my house on the wifi on my Iphone to keeps things ticking along. If your wondering why I’m a bit grumpy please let me apologise I had a total Knee rplacement 3 days ago and for some reason it keeps distracting me.
To sum up to me it looks like the cloud controller is provisioning bits of config that has previously been deleted along with the foible with the Route 10 not sending dhcp address out of port 1.
Hopefully someone will have the Flash of Light and point me in the correct direction how to set up and uses vlans from Route10 to ports on the Ethernet switches. Unfortunately its not beer time in the uk yet
The easiest way forward is probably to create a new site and build from scratch in there.
The VLAN settings are applied to your site, not your router. VLANs need to be communicated to the switches and APs, even if you don’t have a Route10, so the settings for VLANs will persist. You can manually clear them instead to prevent the Route10 from automatically provisioning with them.
HI Josh, Yes I do have a route10 as outlined above several times. I am now into my 3rd different Site rebuild due to orphaned bits of config appearing in devices and disrupting the configuration. Is this a known issue with the Cloud configuration system ?
Ill give this one last try and if I encounter any corruptions issues I will seek a refund as this is not working as expected. Can you point me definitively to how to configure the Vlans in a Route10 and switch combination so I can follow a documented path that guarentees a sucsessful vlan deployment.
This is a snipet from setting up Vlans in the Alta Documentation
Quote It’s important to note that, generally speaking, VLANs terminate at the router. We strongly recommend that you configure the router for the desired VLAN number on the correct interface along with DHCP for that VLAN (if desired) to ensure minimal disruption to the network. We also highly recommend setting DHCP Lease Times on all pertinent subnets to a low value, such as 1-2 minutes. This will allow you to make changes and see them reflected in 1-2 minutes. If you have a device on the network with a 12 hour lease, then change the VLAN (which, in turn, changes the subnet), then you will need to reboot the device, cycle the link on that device, or wait a minimum of 6 hours for the DHCP half life to renew
I would like to first note that you are not likely experiencing orphaned configuration settings. These settings are assigned to the site as a whole, regardless of whether you have a Route10. The fact that you have a Route10 doesn’t change that those VLAN settings are assigned to the actual site itself. This is because VLANs do not apply exclusively to routers; the switches and APs also need to know about them. As a result, nothing you do with the Route10 will clear your existing VLANs. You must manually clear them instead – they are not orphaned.
The reason I recommend building in a new fresh site is that I am simply confused by all the notes you’ve left so far, and it’s always important to troubleshoot with the absolute narrowest possible case. In that regard, please disconnect the rest of your LAN as well – often I make a mistake that causes my network to act extremely badly or even kicks me offline so I have to start unplugging things that might be causing conflicts.
Could you also clearly describe the symptoms you are experiencing alongside a screenshot of the VLAN configuration that you have created? Please limit the details to just the technical aspects, and leave out the steps you’ve taken to troubleshoot anything so far. I would like to get a current survey of your situation with as few variables as possible. When you find an issue, please document it in isolation from other issues for the time being.
Morning Josh, Thanks for the reply. At the moment the Route10 will not factory reset and provide an DHCP IP address to configure the WAN to my isp. I have never succeeded in a Bluetooth connection to the device either.
I get what you are saying about manually deleting things from the Route10 , but then The factory restoration of the default config file is not working. Factory Reset is an industry recognised term which means the eradication of any configuration that has been entered. It reverts to a known state, you cant have it both ways. I do see Phantom Vlans prevailing after a factory restoration of the config when the Route10 is being set up. There should be no carry over of and manual configuration data. The router is STAND ALONE during the initial set up so no vlan data can be propagated into the RouterIO locally. Its becoming from somewhere.
Alta keep pointing out what’s wrong but until now have been unwilling to take the steps to assist. The aspects of whats wrong Have not been configured recently but have been removed from all the config as I reverse the changes I have made. It was this that raised my interest as to how this could happen.
Reference the Route1o factory reset as far as I know the conditions are
Press the reset button for 10 seconds whilst the device is on.
Have the Internet connected to either WAN1 or WAN2
Connect a device into one of the other ethernet ports to be issued a 192.168.1.x address and proceed to configure the Internet link on 192.168.1.1.
As to what do I wish for ? A simple network consisting of Ethernet devices and WIfi devices, which their traffic can be allocated into a Number of Vlans and tick away for years with minor improvements. If Alta can assist me in that goal it would be appreciated. If not then I will return the goods and ask for a refund saying based on my experience they equipment did not work as expected.
To clarify again, the factory reset on the Route10 works exactly as you described. However, the VLAN settings are not tied to the Route10. They are tied to the actual site itself. When you click setup, those VLANs get provisioned back onto the unit, because you set the site up that way. This is not a phantom VLAN. It’s a VLAN configured on your site. If you do not want to propagate those VLAN settings to the Route10, clear the VLAN configurations out of the site manually. We hope to make this easier in the near future, so you can clear the old configurations out with 1 click instead of digging all of them out one by one yourself.
To understand what I mean, click on the device icon for one of your switches – you will find the same VLAN configuration field exists there as well because it’s not tied to the Route10. The APs and switches need that information too, so it is unsafe to simply discard your VLANs when you reset a Route10. The VLANs on your switches would persist after resetting any vendor’s router as well – VLANs are network wide, not tied to a router.
I’m not sure what you mean here – The only engagement I have with this entire thread is an effort to assist you. I don’t understand where you find this unwillingness. Maybe you are referring to a different thread somewhere perhaps?
The article for this is set to be published soon. The plain steps are as follows:
Adding a VLAN to your site
From the main Network tab in the controller:
Click the icon of the Route10 (or switch)
Click the + icon
Input the VLAN number (this must match across all devices handling this VLAN)
Optionally, but recommended, add a Description. This is solely for organizational and informational purposes and has no effect on the functionality of the VLAN
Provide the Router IP, this will be used as the Gateway IP in DHCP
Click Save
Adding VLAN to an Alta Labs S8-POE
Click the icon of the S8-POE
Click the + icon
Input the VLAN number (this must match across all devices handling this VLAN)
Optionally, but recommended, add a Description. This is solely for organizational and informational purposes and has no effect on the functionality of the VLAN
Click Save
The VLAN is now added to the switch and trunked across all ports.
Unplug the power, hold reset, plug in the power, continue holding reset until the logo lights up (any color is fine). Release the button and wait a couple minutes for the LED to return to a solid white color for at least 1 full minute. Optimally, you will have zero other LAN devices connected during this process to reduce potential complications or conflicts.
This is a power-on reset, which does expect the internet to be reachable at the time of reset. It will not change the results of your presumed phantom VLANs unless you clear those from the site manually, but it will reach out to flash a known-good firmware version.