Configuring The Dhcp Operation - H3C SR6600-X Configuration Manual

Step
8. (Optional.) Specify the
source IP address of ICMP
echo requests.
9. (Optional.) Specify the next
hop for ICMP echo requests.

Configuring the DHCP operation

The DHCP operation measures whether or not the DHCP server can respond to client requests. DHCP
also measures the amount of time it takes the NQA client to obtain an IP address from a DHCP server.
The NQA client simulates the DHCP relay agent to forward DHCP requests for IP address acquisition
from the DHCP server. The interface that performs the DHCP operation does not change its IP address.
When the DHCP operation completes, the NQA client sends a packet to release the obtained IP address.
To configure the DHCP operation:
Step
1. Enter system view.
2. Create an NQA operation
and enter NQA operation
view.
3. Specify the DHCP type and
enter its view.
4. Specify the IP address of the
DHCP server as the
destination IP address of
DHCP packets.
5. (Optional.) Specify an
output interface for DHCP
request packets.
Command
•
Specify the IP address of the
specified interface as the source
IP address:
source interface interface-type
interface-number
•
Specify the source IP address:
source ip ip-address
next-hop ip-address
Command
system-view
nqa entry admin-name
operation-tag
type dhcp
destination ip ip-address
out interface interface-type
interface-number
13
Remarks
By default, no source IP address is
specified. The requests take the
primary IP address of the output
interface as their source IP address.
If you configure both the source ip
and source interface commands,
the most recent configuration takes
effect.
The specified source interface must
be up. The source IP address must
be the IP address of a local
interface, and the interface must be
up. Otherwise, no probe packets
can be sent out.
By default, no next hop is
configured.
Remarks
N/A
By default, no NQA operation is created.
N/A
By default, no destination IP address is
specified.
By default, the output interface for DHCP
request packets is not specified. The NQA
client determines the output interface based
on the routing table lookup.