Unsolved
This post is more than 5 years old
3 Posts
0
2164
Trying to setup a x4012 for multiple VLANs
I've never done a VLAN before and I'm rather stumped. I setup the x4012 with the default IP on VLAN1, added VLAN2 at our internal IP range (199.5.249.175) and VLAN3 at 192.168.18.175. I have my PC setup on VLAN1 at IP 192.168.2.10 with 192.168.2.1 set as the gateway. I can ping and access the GUI of the 4012X on all the IP addresses I listed, but I'm unable to access anything on the existing 199.5.249 network. I also can't see the 4012X from my existing 199.5.249 network. I setup the 3 VLANS by going into NET ADMIN -> VLAN -> STANDARD -> EDIT -> ADD then I setup the IP addresses by going to SWITCH MANAGEMENT -> IP4 ADDRESSING -> EDIT. Finally, I set some ports by going to Network Admin -> VLAN -> Standard VLAN and setting 2 ports as TRUNK and 1 as LAYER 3 (just to see if it would help). I haven't been able to set a gateway on the router and the manual says I don't need to with a Layer 2+ switch.
I'm simply out of my depth and am asking for a bit of help, if anyone might be able.
EdgyB
3 Posts
0
June 5th, 2018 05:00
I did a bit of reading last night and went into the CONSOLE this morning, logged in, entered CONFIGURE and then IP ROUTING. Saved the configuration and rebooted the switch with no change.
After the reboot, I went into NETWORK ADMINISTRATION -> PORT SETTINGS -> PORTS -> PORT PROFILE and set the TRUNK ports to PROFILE-SWITCH which now allows my machines on 199.5.249 to see the X4012 at 199.5.249.175 (sadly, not 192.168.2.1 or 192.168.18.175, which makes me think that the switch still isn't routing). Is it possible that I'll simply have to segment the switch into a couple of VLANS (192.168.18 and 199.5.249) and purchase a router to connect the 2 VLANS together?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 5th, 2018 06:00
It sounds like you are getting close to having this working. I suggest looking at the ports modes and adjusting as needed.
Most end devices, laptop, desktop, printers, etc. Are all VLAN unaware devices and will send untagged packets. For these connections the switch should be placed in access mode for the desired VLAN. You could also leave the interface in Trunk/General mode and change the native/pvid to reflect the desired untagged VLAN.
For VLAN aware devices, switch to switch connections, configure these interfaces as Trunk/General mode. This will allow multiple VLANs to traverse the same connection.
From here you can begin testing, I recommend testing with two clients that plug directly into the X4012 but are in different VLANs. One on Access mode VLAN1 and the other on VLAN2. Once you get these two to communicate while on the same switch, then you can work your way out to the rest of the network.
EdgyB
3 Posts
0
June 13th, 2018 07:00
Thank you so much! Sorry I haven't replied in a while. I'm still stuck at the same spot. I reset the switch and started over (a few times). I configured the switch the same way as before, but now I set VLAN1 to 192.168.1.175 and added VLAN2 at 192.168.2.175 and VLAN4 at 192.168.4.175. I'm not planning on doing anything with VLAN1 at this time.
I set Port-9 to VLAN2 and Port-12 to VLAN4. I then hooked up a couple of laptops to these ports. The laptops can ping the switch (x4012) at 192.168.2.175 and 192.168.4.175 (with those IPs set as the laptop's gateway addresses) but they can't ping across (182.168.2.x can't ping anything at 192.168.4.x and vice versa) the switch or each other.
Not sure what I'm missing, Also, could you explain what you meant by "For these connections the switch should be placed in access mode for the desired VLAN"?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 13th, 2018 12:00
Sorry, I forgot you already tried the IP routing command and it did not work. What shows up in the ARP tables?
Network Administration >Route Settings> IPv4 Route Settings >ARP Table.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 13th, 2018 12:00
There are different switchport modes an interface can be placed in. Access mode means that the interface will send and receive untagged packets. Trunk and General mode means the interface can send and receive Tagged and Untagged packets. Interfaces connecting to end devices will usually be placed in access mode or General mode with the PVID set.
Could you please try issuing the command #ip routing, and then test pinging from VLAN to VLAN again.