Feature Requirements |
Series |
Models |
|---|---|---|
In a DHCPv6 relay dual-device hot backup scenario, if the path of DHCPv6 reply messages is different from that of DHCPv6 request messages, the DHCPv6 relay agent and DHCPv6 client do not support double VLAN tags.otherwise, DHCPv6 reply messages cannot be encapsulated with correct VLAN IDs. As a result, users fail to go online. You are advised to configure different source IPv6 addresses on two DHCPv6 relay agents so that the incoming and outgoing paths of messages are consistent. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a master/slave scenario where the DHCPv6 Relay packet and the return packet are transmitted over different paths, the DHCPv6 relay configurations on relay interfaces must be consistent; on a DHCPv6 relay, different interfaces cannot be configured with the same link-address. The corresponding command is dhcpv6 relay link-address; double-layer VLAN scenario is not supported between Relay device and Client device. otherwise, DHCPv6 users fail to go online. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In scenarios where the DHCPv6 PD route advertised by the relay agent has a single next hop, if fast route refreshing is configured, additional route forwarding resources are occupied; if there are a large number of DHCPv6 PD users, the users may go online but traffic cannot be forwarded. You are advised to run the undo single-nexthop bgp fast-refresh enable command to disable fast route refreshing. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a DHCPv6 relay dual-device hot backup scenario, if the path of DHCPv6 reply messages is different from that of DHCPv6 request messages, DHCPv6 PD relay users cannot go online. You are advised to configure different source IPv6 addresses on two DHCPv6 relay agents so that the incoming and outgoing paths of messages are consistent. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
DHCPv6 relay can not relay RELAY-FORWARD packets that pass through other DHCPv6 relay agent and lightweight DHCP relay agent (LDRA). |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a DHCPv6 relay dual-device hot backup scenario, if the path of DHCPv6 reply messages is different from that of DHCPv6 request messages, different interfaces on the same DHCPv6 relay agent cannot be configured with the same gateway address.otherwise, DHCPv6 reply messages cannot be forwarded to the client side, and users fail to go online. You are advised to DHCPv6 reply messages cannot be forwarded to the client side, and users fail to go online. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of automatic restoration upon restart for DHCPv6 PD users supports up to 40K users. If more than 40K PD users exist, user data cannot be written into the file, and data cannot be restored after restart. The function of automatic restoration upon restart for DHCPv6 PD users supports up to 40K users. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a DHCPv6 relay dual-device hot backup scenario, if the path of DHCPv6 reply messages is different from that of DHCPv6 request messages, the DHCPv6 relay configurations on the relay interfaces of the two relay agents must be consistent.otherwise, DHCPv6 reply messages cannot be forwarded to the client side, and users fail to go online. You are advised to configure different source IPv6 addresses on two DHCPv6 relay agents so that the incoming and outgoing paths of messages are consistent. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |