User manual

BOOTP/DHCP Relay
Page 26-8
Because the clients in group 3 are not on the same segment as the DHCP server, they must
request an IP address via the BOOTP relay routing entity in the switch. When a DHCP request
frame is received by the BOOTP relay entity, it will be forwarded from group 3 to group 2. All
the DHCP-ready clients in group 3 must be members of the same VLAN, and the switch must
have the BOOTP relay function configured.
Example 2
This application example has a single group in a network with a mix of DHCP-ready and non-
DHCP clients. DHCP-ready and non-DHCP clients can coexist in the same network, group, or
segment. There are two types of AutoTracker policies defined within the group—IP address
and IP protocol.
AutoTracker IP Policy Places DHCP Clients in Same VLAN
Whenever AutoTracker receives an
IP frame, it examines the frame for an IP network layer
policy match. In the case of DHCP, the client generates an IP frame without an IP address.
Without an IP address, AutoTracker will not be able to place the client into a
VLAN based on
IP address. Therefore, the client will become a member of the
VLAN defined by a general IP
Protocol policy (i.e., VLAN 30).
Omni Switch/Router
12345678
123456
VLAN 20VLAN 10
UDP Relay
VLAN 30
IP Network 130.0.0.0
IP Network 125.0.0.0
IP Protocol Policy
DHCP Server
125.0.0.1
140.0.0.2
130.0.0.11
130.0.0.12
Non-DHCP
DHCP Client
140.0.0.22
130.0.0.13
140.0.0.20
130.0.0.14
DHCP Client
130.0.15
Non-DHCP Non-DHCP Non-DHCP Non-DHCP Non-DHCP
Group 2