TP-Link T2600G-52TS TL-SG3452 T2600G-52TS V1 User Guide - Page 98

Gvrp

Page 98 highlights

Step Operation 1 Create VLAN entries. 2 Enable VLAN function for port. 3 Create SP Provider) VLAN Description Mapping Required. On the VLAN→VLAN VPN→VLAN Mapping page, configure the VLAN Mapping entries basing on the actual application. Mapping Required. On the VLAN→VLAN VPN→Port Enable page, enable VLAN Mapping function for the ports. (Service Optional. On the VLAN→802.1Q VLAN page, create the SP VLAN. For the steps of creating VLAN, please refer to 802.1Q VLAN. 6.8 GVRP GVRP (GARP VLAN Registration Protocol) is an implementation of GARP (generic attribute registration protocol). GVRP allows the switch to automatically add or remove the VLANs via the dynamic VLAN registration information and propagate the local VLAN registration information to other switches, without having to individually configure each VLAN.  GARP GARP provides the mechanism to assist the switch members in LAN to deliver, propagate and register the information among the members. GARP itself does not work as the entity among the devices. The application complied with GARP is called GARP implementation, and GVRP is the implementation of GARP. When GARP is implemented on a port of device, the port is called GARP entity. The information exchange between GARP entities is completed by messages. GARP defines the messages into three types: Join, Leave and LeaveAll. • Join Message: When a GARP entity expects other switches to register certain attribute information of its own, it sends out a Join message. And when receiving the Join message from the other entity or configuring some attributes statically, the device also sends out a Join message in order to be registered by the other GARP entities. • Leave Message: When a GARP entity expects other switches to deregister certain attribute information of its own, it sends out a Leave message. And when receiving the Leave message from the other entity or deregistering some attributes statically, the device also sends out a Leave message. • LeaveAll Message: Once a GARP entity starts up, it starts the LeaveAll timer. After the timer times out, the GARP entity sends out a LeaveAll message. LeaveAll message is to deregister all the attribute information so as to enable the other GARP entities to re-register attribute information of their own. Through message exchange, all the attribute information to be registered can be propagated to all the switches in the same switched network. The interval of GARP messages is controlled by timers. GARP defines the following timers: • Hold Timer: When a GARP entity receives a piece of registration information, it does not send out a Join message immediately. Instead, to save the bandwidth resources, it starts the Hold timer, puts all registration information it receives before the timer times out into one Join message and sends out the message after the timer times out. 88

  • 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278

88
Step
Operation
Description
1
Create
VLAN
Mapping
entries.
Required. On the
VLAN
VLAN VPN
VLAN Mapping
page, configure the VLAN Mapping entries basing on the
actual application.
2
Enable
VLAN
Mapping
function for port.
Required. On the
VLAN
VLAN VPN
Port Enable
page,
enable VLAN Mapping function for the ports.
3
Create
SP
(Service
Provider) VLAN
Optional. On the
VLAN
802.1Q VLAN
page, create the
SP VLAN. For the steps of creating VLAN, please refer to
802.1Q VLAN
.
6.8 GVRP
GVRP (GARP VLAN Registration Protocol) is an implementation of GARP (generic attribute
registration protocol). GVRP allows the switch to automatically add or remove the VLANs via the
dynamic VLAN registration information and propagate the local VLAN registration information to
other switches, without having to individually configure each VLAN.
GARP
GARP provides the mechanism to assist the switch members in LAN to deliver, propagate and
register the information among the members. GARP itself does not work as the entity among the
devices. The application complied with GARP is called GARP implementation, and GVRP is the
implementation of GARP. When GARP is implemented on a port of device, the port is called
GARP entity.
The information exchange between GARP entities is completed by messages. GARP defines the
messages into three types: Join, Leave and LeaveAll.
Join Message:
When a GARP entity expects other switches to register certain attribute
information of its own, it sends out a Join message. And when receiving the Join message
from the other entity or configuring some attributes statically, the device also sends out a Join
message in order to be registered by the other GARP entities.
Leave Message:
When a GARP entity expects other switches to deregister certain attribute
information of its own, it sends out a Leave message. And when receiving the Leave
message from the other entity or deregistering some attributes statically, the device also
sends out a Leave message.
LeaveAll Message:
Once a GARP entity starts up, it starts the LeaveAll timer. After the timer
times out, the GARP entity sends out a LeaveAll message. LeaveAll message is to deregister
all the attribute information so as to enable the other GARP entities to re-register attribute
information of their own.
Through message exchange, all the attribute information to be registered can be propagated to all
the switches in the same switched network.
The interval of GARP messages is controlled by timers. GARP defines the following timers:
Hold Timer:
When a GARP entity receives a piece of registration information, it does not
send out a Join message immediately. Instead, to save the bandwidth resources, it starts the
Hold timer, puts all registration information it receives before the timer times out into one Join
message and sends out the message after the timer times out.