System information

DHCP Clients on D-LINK-
NET2 SSID
NA 192.168.3.x/24 Wireless
4.2. Switch1 & Switch2 LAN Configuration
The configuration in this section takes place on Unified Switch1 and Unified Switch2, and all
features are under the LAN tab on the navigation panel. Please follow the steps you have learned
from previous scenarios to configure the VLANs, interfaces, and addresses on the systems.
4.2.1. DHCP
Configure DHCP Server parameters and pools on Unified Switch1 to provide addresses for AP1,
Guest, Sales, and RD Tunneled WLAN Clients and for AP2 on Unified Switch2.
4.2.2. Configure routes on Switch1, Switch2, and L3 device
You must configure routes on the Unified Switch and L3 core device to provide IP connectivity
between the Unified Switches, APs, and servers. You can either configure static routes for each
network you need access to at the Unified Switch or you can configure a default route. The
Unified Switch at a minimum requires IP access to the other Unified Switch to allow peering to
occur and the APs must have IP access to the RADIUS server for WPA2. Other routes (or a
default route) provide access for clients to reach other networks.
The following default and static routes should be configured.
Note: The static route toward AP1, AP2, and the Radius server is needed only for WPA2-EAP
authentication.
Note: A default route above will direct all unknown IP traffic from the Unified Switch to the
“customer” L3 switch and configured a route on the L3 switch to direct traffic to the Unified
Switch to reach the AP2 subnet a routing loop will occur when you pull power on the AP
connected to the Unified Switch. This occurs because when you pull power to the AP, the link to
the switch goes down and if this was the only link on the AP1 subnet, the local route will also go
down. The Unified Switch continues to attempt communications with the AP for approximately a
minute until it decides that the AP has failed. Since the Unified Switch no longer has an IP route
to the APs subnet however, it will forward the traffic to the configured default gateway which is
on the “customer” L3 device which in turn might have a route pointing back to the Unified
Switch – causing a routing loop. The loop will saturate the link between the Unified Switch and
the L3 device and can cause the Unified Switch to lose communications with the “remote” AP
causing the wireless demo network to go down. This issue will resolve itself after the Unified
Switch declares AP1 failed. In a real-world environment most likely the AP will not fail, and a
Device Network Address Mask Next Hop IP Address
Unified Switch1 0.0.0.0 0.0.0.0 172.17.5.254
Unified Switch2 0.0.0.0 0.0.0.0 172.17.6.254
L3 Device 192.168.101.0 255.255.255.0 172.17.5.253
L3 Device 192.168.102.0 255.255.255.0 172.17.6.253
L3 Device 192.168.4.0 255.255.255.0 172.17.6.253
L3 Device 192.168.10.0 255.255.255.0 172.17.5.253
L3 Device 192.168.20.0 255.255.255.0 172.17.6.253
L3 Device 192.168.5.0 255.255.255.0 172.17.5.253