40• To support Option 82, related configuration is required on both the DHCP server and relay agent.• If the handling strategy of the DHCP relay agent is configured as replace, you need to configure a paddingformat for Option 82. If the handling strategy is keep or drop, you need not configure any padding format.• If sub-option 1 (node identifier) of Option 82 is padded with the device name (sysname) of a node, the devicename must contain no spaces. Otherwise, the DHCP relay agent will drop the message.Displaying and maintaining DHCP relay agentconfigurationTo do… Use the command… RemarksDisplay information about DHCP server groupscorrelated to a specified or all interfacesdisplay dhcp relay { all |interface interface-type interface-number }Available in any viewDisplay Option 82 configuration informationon the DHCP relay agentdisplay dhcp relay information{ all | interface interface-typeinterface-number }Display information about bindings of DHCPrelay agentsdisplay dhcp relay security [ ip-address | dynamic | static ]Display statistics information about bindings ofDHCP relay agentsdisplay dhcp relay securitystatisticsDisplay information about the refreshinginterval for entries of dynamic IP-to-MACbindingsdisplay dhcp relay securitytrackerDisplay information about the configuration ofa specified or all DHCP server groupsdisplay dhcp relay server-group { group-id | all }Display packet statistics on relay agent display dhcp relay statistics [server-group { group-id | all } ]Clear packet statistics from relay agent reset dhcp relay statistics [server-group group-id ]Available in userviewDHCP relay agent configuration examplesDHCP relay agent configuration exampleNetwork requirementsAs shown in Figure 11, DHCP clients reside on network 10.10.1.0/24. The IP address of the DHCP serveris 10.1.1.1/24. Because the DHCP clients reside on a different network with the DHCP server, a DHCP
