HP 6120XG HP ProCurve Series 6120 Blade Switches Multicast and Routing Guide - Page 101

Multiple Option 82 Relay Agents in a Client Request Path

Get HP 6120XG PDF manuals and user guides View all HP 6120XG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 101 highlights

IP Routing Features Configuring DHCP Relay Option 82 DHCP Client Request Packet Inbound to the Routing Switch Configuration Packet Has No Packet Includes an Option 82 Field Option 82 Field Drop Append an Option 82 Field Drop causes the routing switch to drop an inbound client request with an Option 82 field already appended. If no Option 82 fields are present, drop causes the routing switch to add an Option 82 field and forward the request. As a general guideline, configure drop on relay agents at the edge of a network, where an inbound client request with an appended Option 82 field may be unauthorized, a security risk, or for some other reason, should not be allowed. Multiple Option 82 Relay Agents in a Client Request Path Where the client is one router hop away from the DHCP server, only the Option 82 field from the first (and only) relay agent is used to determine the policy boundary for the server response. Where there are multiple Option 82 router hops between the client and the server, you can use different configuration options on different relay agents to achieve the results you want. This includes configuring the relay agents so that the client request arrives at the server with either one Option 82 field or multiple fields. (Using multiple Option 82 fields assumes that the server supports multiple fields and is configured to assign IP addressing policies based on the content of multiple fields.) Client Relay Agent "A" VLAN 10 VLAN 20 DROP Relay Agent "B" VLAN 20 VLAN 30 KEEP Relay Agent "C" VLAN 10 VLAN 20 KEEP DHCP Option 82 Server Figure 3-24. Example Configured To Allow Only the Primary Relay Agent To Contribute an Option 82 Field The above combination allows for detection and dropping of client requests with spurious Option 82 fields. If none are found, then the drop policy on the first relay agent adds an Option 82 field, which is then kept unchanged over the next two relay agent hops ("B" and "C"). The server can then enforce an IP addressing policy based on the Option 82 field generated by the edge relay agent ("A"). In this example, the DHCP policy boundary is at relay agent 1. 3-55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
IP Routing Features
Configuring DHCP Relay
Option 82
Configuration
DHCP Client Request Packet Inbound to the Routing Switch
Packet Has No
Option 82 Field
Packet Includes an Option 82 Field
Drop
Append an
Option 82 Field
Drop
causes the routing switch to drop an inbound client request with an Option
82 field already appended. If no Option 82 fields are present,
drop
causes the routing
switch to add an Option 82 field and forward the request. As a general guideline,
configure
drop
on relay agents at the edge of a network, where an inbound client
request with an appended Option 82 field may be unauthorized, a security risk, or
for some other reason, should not be allowed.
Multiple Option 82 Relay Agents in a Client Request Path
Where the client is one router hop away from the DHCP server, only the Option
82 field from the first (and only) relay agent is used to determine the policy
boundary for the server response. Where there are multiple Option 82 router
hops between the client and the server, you can use different configuration
options on different relay agents to achieve the results you want. This includes
configuring the relay agents so that the client request arrives at the server with
either one Option 82 field or multiple fields. (Using multiple Option 82 fields
assumes that the server supports multiple fields and is configured to assign
IP addressing policies based on the content of multiple fields.)
VLAN
10
DHCP
Option
82
Server
Client
DROP
VLAN
20
VLAN
20
VLAN
30
VLAN
10
VLAN
20
KEEP
KEEP
Relay Agent “A”
Relay Agent “B”
Relay Agent “C”
Figure 3-24. Example Configured To Allow Only the Primary Relay Agent To Contribute an Option 82 Field
The above combination allows for detection and dropping of client requests
with spurious Option 82 fields. If none are found, then the drop policy on the
first relay agent adds an Option 82 field, which is then kept unchanged over
the next two relay agent hops (“B” and “C”). The server can then enforce an
IP addressing policy based on the Option 82 field generated by the edge relay
agent (“A”). In this example, the DHCP policy boundary is at relay agent 1.
3-55