Users Guide

Table Of Contents
Use case - DHCPv4 relay counters
Consider the following use case diagram in which three hosts (Host 1, Host 2 and Host 3) connected to the L2 switch in VLAN
100.
The DHCPv4 relay switch is connected to the L2 switch. The DHCPv4 relay is configured in interface Ethernet 1/1/14.
The DHCP server is connected to the DHCPv4 relay switch in VLAN 200. The DHCP packets to and from the DHCP clients
(Host 1, Host 2, and Host 3) are counted at the interface Ethernet 1/1/14 (client-connected interface). The DHCPv4 relay
switch maintains the aggregate counters of all the DHCP packets to and from all the hosts.
DHCP relay without route leaking
This feature enables you to support DHCP relay across VRFs without route leaking. DHCP relay with DHCP client and DHCP
server in different VRFs requires route reachability for the DHCP server. You can achieve route reachability using the route
leaking method.
To enable DHCP relay across VRFs without route leaking for SFD with open config model, the existing helper-address
configuration is modified to allow any VRF name. For this configuration to work, you must first configure a helper-address
reachable VRF.
Consider the scenario depicted in the following figure:
276
System management