Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater

6-12
IP Services—IP Settings, DHCP, and DNS
IP Routing
IP Routing
As discussed in Chapter 1: Introduction, the Wireless Edge Services xl Mod-
ule and its internal uplink port operate at Layer 3 of the Open Systems
Interconnection (OSI) model. As part of this Layer 3 functionality, the Wireless
Edge Services xl Module maintains a route table. You can view the route table,
which automatically lists directly connected interfaces, and you can add static
routes to the route table. You can also assign IP addresses to as many as eight
VLANs, which then become directly connected interfaces, and you can enable
routing between these VLANs.
The Wireless Edge Services xl Module’s route table is completely separate
from the route table maintained by the wireless services-enabled switch. The
IP addresses that you assign to VLANs on the module are stored and main-
tained in the module’s running-config. If you want to assign IP addresses to
VLANs on the wireless services-enabled switch, you must access the com-
mand line interface (CLI), the menu system, or the Web browser interface for
the switch itself.
By default, IP routing is disabled. Turning routing on enables these functions:
■ DHCP relay
■ the internal firewall, including IP ACLs applied to logical (VLAN or tunnel)
interfaces
■ Network Address Translation (NAT)
Route Table
When the Wireless Edge Services xl Module receives an IP address from a
DHCP server, the address is assigned to the default management interface,
which is typically VLAN 1. The module automatically recognizes the subnet-
work directly connected to the default management interface and lists this
information in its route table. In the example shown in Figure 6-8, the default
management interface (which, in this case, is VLAN 1) is directly connected
to network 10.4.1.0/24.