Dynamic Host Configuration Protocol and User Datagram Protocol Configuration

Table 1. Dynamic Host Configuration Protocol product support

Feature

Product

Release introduced

Dynamic Host Configuration Protocol (DHCP) Relay

5320 Series

Fabric Engine 8.6

5420 Series

VOSS 8.4

5520 Series

VOSS 8.2.5

5720 Series

Fabric Engine 8.7

7520 Series

Fabric Engine 8.10

7720 Series

Fabric Engine 8.10

VSP 4450 Series

VSP 4000 4.0

VSP 4900 Series

VOSS 8.1

VSP 7200 Series

VOSS 4.2.1

VSP 7400 Series

VOSS 8.0

VSP 8200 Series

VSP 8200 4.0

VSP 8400 Series

VOSS 4.2

VSP 8600 Series

VSP 8600 4.5

XA1400 Series

VOSS 8.0.50

DHCP Option 82

5320 Series

Fabric Engine 8.6

5420 Series

VOSS 8.4

5520 Series

VOSS 8.2.5

5720 Series

Fabric Engine 8.7

7520 Series

Fabric Engine 8.10

7720 Series

Fabric Engine 8.10

VSP 4450 Series

VSP 4000 4.0

VSP 4900 Series

VOSS 8.1

VSP 7200 Series

VOSS 4.2.1

VSP 7400 Series

VOSS 8.0

VSP 8200 Series

VSP 8200 4.0

VSP 8400 Series

VOSS 4.2

VSP 8600 Series

VSP 8600 4.5

XA1400 Series

VOSS 8.0.50

DHCP Smart Relay

5320 Series

Fabric Engine 8.10

5420 Series

Fabric Engine 8.10

5520 Series

Fabric Engine 8.10

5720 Series

Fabric Engine 8.10

7520 Series

Fabric Engine 8.10

7720 Series

Fabric Engine 8.10

VSP 4450 Series

VOSS 8.10

VSP 4900 Series

VOSS 8.10

VSP 7200 Series

VOSS 8.10

VSP 7400 Series

VOSS 8.10

VSP 8200 Series

VOSS 8.10

VSP 8400 Series

VOSS 8.10

VSP 8600 Series

Not Supported

XA1400 Series

VOSS 8.10

Table 2. Dynamic Host Configuration Protocol Relay for IPv6 product support

Feature

Product

Release introduced

IPv6 DHCP Relay

5320 Series

Fabric Engine 8.6

5420 Series

VOSS 8.4

5520 Series

VOSS 8.2.5

5720 Series

Fabric Engine 8.7

7520 Series

Fabric Engine 8.10

7720 Series

Fabric Engine 8.10

VSP 4450 Series

VOSS 4.1

VSP 4900 Series

VOSS 8.1

VSP 7200 Series

VOSS 4.2.1

VSP 7400 Series

VOSS 8.0

VSP 8200 Series

VOSS 4.1

VSP 8400 Series

VOSS 4.2

VSP 8600 Series

VSP 8600 6.2

XA1400 Series

Not Supported

In the case of asymmetric routing, when a DHCP message is received from the server, there must be a working forwarding path. You can achieve this in one of two ways: