WLC 2504 and VLANs

[Chris Pohlad-Thomas]

Ok, so with my WLC2504 implementation, I use the 4 ports to physically segment my wireless networks. Here is my setup:

Port 1 (Management) - Internal IP so I can manage the WLC from our internal network (Untagged)

Port 2 - Connected to our core stack and tagged with VLAN 14

Port 1 and 2 are both connected to the same core stack

Port 3 - Connected to a RV016 Linksys which is connected to our fiber connection to the outside (Untagged) - External connection for laptops

Port 4 - Connected to a Linksys wireless router (with wireless disabled) (Untagged) - External connection for smartphones

The TAC engineer I talked to just told me that I can only have one untagged interface on the WLC. If they are physically connected to different switches, thus physically segmenting the network, should it matter?

The wireless works just fine. What I am having issues with is getting a client that is hard-wire connected to the RV016 to get a DHCP address from the WLC.

[Scott Fella]

Yes you only can have one untagged interface. I would tag your management and then put a switch in between your guest network which is port 3 and port 4 and then tag each vlan. The switch will have to be managed.

Sent from Cisco Technical Support iPhone App

[Chris Pohlad-Thomas]

The two external interfaces are connected to completely different equipment. They are also not connected to any kind of managed switch.

[George Stefanick]

Chris,

Understood .. I would still tag it .. Your WLC is a wireless switch. When you mark 2 untagged you are asking for problems. Again, I would tag it all ..

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Chris Pohlad-Thomas]

Ok, so let me ask this, and it might very well be a dumb question:

Both of these external interfaces are connected to equipment that I believe cannot handle tagged traffic (and RV016) and a linksys E series wireless router.

The one hanging off the RV016 has an IP subnet of 192.168.45.0/24

The one hanging off the E series has an IP subnet of 192.168.21.0/24

Should I tag them with 45 and 21 respectively?

[George Stefanick]

Chris,

Its a matter of best pratice. If it works great, but when you have issues TAC rightfully so will suggest best pratice reommendations. You cant blame them.

From my experince, I would tag everything. A year ago I had IP conflicts and learned after talking to the BU the controller was likley leaking packets internally. After I tagged the ports issue went away ..

Just my 2 cents my friend ..

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Scott Fella]

Or what you can do if you want it o work now, is to create two vlans on the stack but don't create any layer 3 interface. Connect one router to one vlan aling with port 3 and the other router to a different vlan along with port 4. This way you are still segmenting and there is no routing allowed. Then you setup each port as a trunk only allowing the vlan for that port.

Sent from Cisco Technical Support iPhone App

[Scott Fella]

You need to tag them and the device I connects to needs to understand the tag. I was trying I explain how you can get it to work with what you have. How you have it setup will not work as you can't have more than one interface as untagged. Your soho routers most likely do not support vlan tagging and this why it will not work.

Sent from Cisco Technical Support iPhone App

[Chris Pohlad-Thomas]

Thanks all for the assistance. My not so graceful work-around was to setup a non-conflicting DHCP pool on this RV016. The hard-wired connections get their DHCP addresses from the RV016 and the wireless get theirs from the WLC. Again, not graceful.

Thanks again!

[Scott Fella]

Doesn't the RV016 and the E-Series support vlan tagging?  If so, you could get it to work, but I haven't touched the RV016 and I'm guessing the E-Series is a switch?

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"