Unsolved
This post is more than 5 years old
6 Posts
0
30678
August 2nd, 2012 08:00
Need help configuring PowerConnect 3424 as a "vanilla" Ethernet Switch
I have 2 PowerConnect 3424 switches with GBICs (fiber) adapters installed on each. We plan to use both the local and remote 3424's as the isolated switches off one port on our Dell SonicWALL E5500, so that they can support the SonicPoints (wireless access points). We're using the remote 3424 to support a SonicPoint which is located beyond the range of the copper cable runs.
The SonicPoints have physical addresses on the subnet associated with the port to which they are connected on the SonicWALL. (the WLAN interface): 192.168.50.1 We had 3 SonicPoints plugged into a inexpensive 5-port 10/100 switch, which was then connected to the WLAN associated port of the E5500 and everything worked fine.
It's important to note that each of the SonicPoints is running in Virtual Access Point mode, so they each support 2 SSIDs/subnets by using VLANS so that the WLAN port also has VLAN 100 (192.168.100.x) and VLAN 200 (192.168.200.x) associated with it.
Obviously, with the simple 5 port "bare bones" switch attached to the SonicWALL WLAN port and the SonicPoints attached to that switch, everything works great. Everything is routed properly and wireless users can connect to their assigned SSIDs and subnets.
One we introduced the Dell PowerConnect 3424 into the equation (instead of the "bare bones" 5-port switch) we ran into problems immediately. We cleared the startup configuration from the 3424 and assigned a management address on the primary subnet (192.168.50.x), thinking that this would clear up any issues, but no.
Although we could access all the IP's for the attached SonicPoints, it's clear that the VLAN tagged traffic isn't making it back through the switch to the SonicWALL (no wireless users can get a DHCP IP address when attached to the Dell switch, but the SoncPoints work fine on the simple switch).
So, is there a way to configure this switch and all ports to just pass everything and ignore the VLAN tags (so that it functions just like the "bare bones" switch)?
Or, what would be the best way to configure it such that we can properly route all the VLANS and the "base" subnet?
Thanks!
DELL-Willy M
802 Posts
0
August 2nd, 2012 10:00
You will need to set up a switchport mode general on the port that is connecting to the Sonicwall devices. This configuration will allow multiple VLANs to traverse back and forth freely.
General Links consist of a combination of VLAN Trunk and Access Links.
General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged. All untagged frames are sent to the native VLAN.
The native VLAN still applies to the General LINK. While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID. The PVID represents the native VLAN.
While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN.
Sample CLI
console# configure
console(config)# interface ethernet e11
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 100 tagged
console(config-if)# switchport general allowed vlan add 101 untagged
console(config-if)# end
charlesnh
6 Posts
0
August 2nd, 2012 13:00
I've tried as you suggested but it still isn't working. I cleared the startup config from the 3424 and configured it as you suggested (except I used ethernet e1 rather than 11).
Im still getting the same problem. Do I need to configure the rest of the ethernet ports and the gbic ports?
charlesnh
6 Posts
0
August 2nd, 2012 14:00
I'm confused as to your answer since the SonicWALL AND the SonicPoints are BOTH VLAN aware devices. Yes I did add the vlans to he database.
charlesnh
6 Posts
0
August 2nd, 2012 14:00
I also looked at your reply to Michael Van Sickle (essentially the same scenario) but again, it seems to be lacking in detail. where do I go from here?
DELL-Willy M
802 Posts
0
August 2nd, 2012 14:00
Any ports that are connecting with VLAN unaware devices ie server/workstation/laptop would need to have switchport mode access configured.
console# configure
console(config)# interface ethernet xxx
console(config-if)# switchport mode access
console(config-if)# switchport access vlan xxx
console(config-if)# end
Also, you will need to have a similar command set up on the other end of the general mode connection (Ethernet e1) on the Sonicwall.
Did you actually create the needed VLANs on the switch?
Creating VLANs
console> enable
console# config
console(config)# vlan database
console(config-vlan)# vlan 2
console(config-vlan)# exit
console(config)# interface vlan 2
console(config-if)# name Marketing
console(config-if)# end
console# show vlan
DELL-Willy M
802 Posts
1
August 2nd, 2012 17:00
Sorry for the confusion. All the ports that are connecting to the Sonic devices need to be in General mode adding the VLANS as tagged. Then all the VLANs that are crossing thru the 3424 will need to be added to the VLAN database. From what I'm reading you have VLAN 100 and 200
console(config)# interface ethernet e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 100 tagged
console(config-if)# switchport general allowed vlan add 200 tagged
You would need to have this same configuration on every port that is connecting to a Sonic device.
Can you post a Show run once you have this configuration set up?