Dell PowerEdge M520 Dell PowerConnect M6220/M6348/M8024 Switches Configuration - Page 45

bindin, Tentative, Complete, DISCOVER, REQUEST, DECLINE, RELEASE

Get Dell PowerEdge M520 PDF manuals and user guides View all Dell PowerEdge M520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

snooping removes bindings in response to DECLINE, RELEASE, and NACK messages. DHCP Snooping application ignores the ACK messages as reply to the DHCP Inform messages received on trusted ports. The administrator can also enter static bindings into the binding database. The DHCP binding database resides on a configured external server or locally in flash depending upon the user configuration. When a switch learns of new bindings or when it loses bindings, the switch immediately updates the entries in the database. The switch also updates the entries in the bindings file. The frequency at which the file is updated is based on a configurable delay, and the updates are batched. If the absolute lease time of the snooping database entry expires, the entry is removed. If the system time is not consistent across reboots, snooping entries will not expire properly. If a host sends a DHCP release while the switch is rebooting, when the switch receives the DHCP discovery or request, the client's binding will go to the tentative binding. Figure 3-3. DHCP Binding DISCOVER, REQUEST No binding RELEASE, NACK Tentative binding DECLINE, NACK DISCOVER ACK Complete binding The DHCP snooping component does not forward server messages since they are forwarded in hardware. DHCP snooping forwards valid DHCP client messages received on un-trusted interfaces to all trusted interfaces within the VLAN. The binding's database includes the following information for each entry: • Client MAC address • Client IP address • Time when client lease expires • Client VLAN ID • Client port Switching Configuration 45

  • 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
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
Switching Configuration
45
snooping removes bindings in response to DECLINE, RELEASE, and NACK messages. DHCP
Snooping application ignores the ACK messages as reply to the DHCP Inform messages received on
trusted ports. The administrator can also enter static bindings into the binding database.
The DHCP binding database resides on a configured external server or locally in flash depending upon
the user configuration. When a switch learns of new bindings or when it loses bindings, the switch
immediately updates the entries in the database. The switch also updates the entries in the bindings file.
The frequency at which the file is updated is based on a configurable delay, and the updates are batched.
If the absolute lease time of the snooping database entry expires, the entry is removed. If the system time
is not consistent across reboots, snooping entries will not expire properly. If a host sends a DHCP release
while the switch is rebooting, when the switch receives the DHCP discovery or request, the client's
binding will go to the tentative binding.
Figure 3-3.
DHCP Binding
The DHCP snooping component does not forward server messages since they are forwarded in hardware.
DHCP snooping forwards valid DHCP client messages received on un-trusted interfaces to all trusted
interfaces within the VLAN.
The binding's database includes the following information for each entry:
•
Client MAC address
•
Client IP address
•
Time when client lease expires
•
Client VLAN ID
•
Client port
No
bindin
g
Tentative
binding
Complete
binding
DISCOVER,
REQUEST
DISCOVER
DECLINE,
NACK
ACK
RELEASE,
NACK