topic Static Routing on 2106 controller in Wireless

Static Routing on 2106 controller

Hugo Lynch — Sun, 04 Jul 2021 03:56:03 GMT

Hi,

after an unplanned power outage the WLAN in our office has stopped routing. Clients can associate and get an IP address from the DHCP server on the controller but cannot get past the controller. A PC on the LAN can ping the default gateway of the SSID (dynamic interface) but cannot ping the client. Attached is a diagram of the setup. I am trying to find out how to add a default/static route via the L3 switch that the controller is connected to but am unable to do so either through the CLI or GUI. Am I missing something? The controller (AIR-WLC2106-K9) is operating on ver 5.2.157.0.

Thanks for any advice,

Hugo

Static Routing on 2106 controller

pcroak — Fri, 14 Oct 2011 15:14:56 GMT

Hello Hugo,

The WLC is not a routing platform -- it connects to your switching infrastructure at Layer 2. The network routes you see in the CLI are meant for the service-port only -- which the 2100 platform does not have (so actually the show route summary command should not be there).

Could you send us the "show interface summary" from the WLC? We also would want to see your current switchport config where the WLC is connected (show run interface fast/gig x/y ...). Lastly, we would want to confirm your L3 interface configuration on the switch with a "show ip interface brief".

Based on your static route, it looks like you are trying to route traffic to the WLC -- this is not the intended functionality -- your switch/router should perform the routing and the connectivity to the WLC will be a L2 trunk.

-Pat

Static Routing on 2106 controller

Hugo Lynch — Fri, 14 Oct 2011 15:22:49 GMT

Hi Pat,

here is the interface summary and interface vlan11

(Cisco Controller) >show interface summary

Interface Name Port Vlan Id IP Address Type Ap Mgr Guest

-------------------------------- ---- -------- --------------- ------- ------ -----

ap-manager 1 untagged 10.6.0.244 Static Yes No

management 1 untagged 10.6.0.243 Static No No

virtual N/A N/A 1.1.1.1 Static No No

vlan11 1 11 10.6.5.250 Dynamic No No

vlan21 1 21 10.6.6.250 Dynamic No No

vlan30 1 30 10.6.7.250 Dynamic No No

(Cisco Controller) >show interface detailed vlan11

Interface Name................................... vlan11

MAC Address...................................... 00:21:55:9a:35:40

IP Address....................................... 10.6.5.250

IP Netmask....................................... 255.255.255.128

IP Gateway....................................... 10.6.5.250

VLAN............................................. 11

Quarantine-vlan.................................. 0

Physical Port.................................... 1

Primary DHCP Server.............................. 10.6.0.243

Secondary DHCP Server............................ Unconfigured

DHCP Option 82................................... Disabled

ACL.............................................. Unconfigured

AP Manager....................................... No

Guest Interface.................................. No

The switch is an Enterasys switch so I guess the information you want to see is the following:

router

enable

configure

ip route 0.0.0.0 0.0.0.0 10.203.1.1

ip route 10.6.5.128 255.255.255.128 10.6.0.243

interface vlan 200

no shutdown

ip address 10.6.0.251 255.255.255.128

exit

#vlan

set vlan create 11

set vlan create 200

set vlan egress 11 ge.1.38-40 tagged

set vlan egress 200 ge.1.38-40 untagged

The AP is connected to interface ge.1.38 and the WLC is connected to interface ge.1.40

Cheers,

Hugo.

Static Routing on 2106 controller

pcroak — Fri, 14 Oct 2011 15:34:05 GMT

Hi Hugo,

Alright, so, you are going to need to configure L3 interfaces on your switch for your other vlans (11, 21, 31). Again the WLC does not perform routing -- if you look at your vlan 11 interface details, the gateway is pointing to itself -- this gateway needs to be your router address for that subnet (which should be interface vlan 11 on your switch).

You will also want to remove your "ip route 10.6.5.128..." statement, because you should not send these packets to your WLC management interface. The WLC will communicate with your switch as a L2 trunk, the routing should all occur on the Enterasys switch in this case.

http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52mint.html#wp1117889

This picture explains how the WLC interfaces should operate with the connected switch. Please let me know if you have questions regarding this information.

-Pat

Re: Static Routing on 2106 controller

Stephen Rodriguez — Fri, 14 Oct 2011 15:36:53 GMT

Hugo,

Generally when working with L3 devices, you shouldn't need to have a static route for a VLAN that the devices has configured on it.

so in this case you shouldn't need the ip route 10.6.5.128 255.255.255.128 10.6.0.243

If vlan 200 exists at L3 on the switch, it should route for it with the need for a static route.

**as an aside, the network routes on a WLC are to force traffic out of the service port, as it does not have a gateway address.**

HTH,

Steve

----------------------------------------------------------------------------------------------------------

Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

Static Routing on 2106 controller

Hugo Lynch — Fri, 14 Oct 2011 15:39:53 GMT

Hi Pat,

since your reply I have created a L3 interface for vlan 11 on the switch of 10.6.5.251 and have modified the scope for vlan 11 on the DHCP server on the controller to show a new default gateway of 10.6.5.251. The client can now route to the big bad www. Many thanks for your help.

Hugo.