HP 6120XG HP ProCurve Series 6120 Blade Switches Advanced Traffic Management G - Page 43

Multiple Forwarding Database Operation,

Page 43 highlights

Static Virtual LANs (VLANs) Multiple VLAN Considerations reason, the 6600 discards some packets directed through it for the 6120 switch, resulting in poor performance and the appearance of an intermittent or broken link. The Solution. To avoid the preceding problem, use only one cable or port trunk between the single-forwarding and multiple-forwarding database devices, and configure the link with multiple, tagged VLANs. PC "A" VLAN 1 VLAN 1 Switch VLAN 1& 2 A1 VLAN 2 C1 VLAN 1 & 2 6120 Switch VLAN 2 PC "B" This switch has a single forwarding database. This switch has multiple forwarding databases. Figure 2-10. Example of a Solution for Single-Forwarding to Multiple-Forwarding Database Devices in a Multiple VLAN Environment Now, the 6600 forwarding database always lists the 6120 MAC address on port A1, and the 6600 will send traffic to either VLAN on the 6120. To increase the network bandwidth of the connection between the devices, you can use a trunk of multiple physical links rather than a single physical link. Multiple Forwarding Database Operation If you want to connect one of the switches covered by this guide to another switch that has a multiple forwarding database, you can use either or both of the following connection options: ■ A separate port or port trunk interface for each VLAN. This results in a forwarding database having multiple instances of the same MAC address with different VLAN IDs and port numbers. (See table 2-4.) The fact that the switches covered by this guide use the same MAC address on all VLAN interfaces causes no problems. ■ The same port or port trunk interface for multiple (tagged) VLANs. This results in a forwarding database having multiple instances of the same MAC address with different VLAN IDs, but the same port number. Allowing multiple entries of the same MAC address on different VLANs enables topologies such as the following: 2-20

  • 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

2-20
Static Virtual LANs (VLANs)
Multiple VLAN Considerations
reason, the 6600 discards some packets directed through it for the 6120
switch, resulting in poor performance and the appearance of an intermit-
tent or broken link.
The Solution.
To avoid the preceding problem, use only one cable or port
trunk between the single-forwarding and multiple-forwarding database
devices, and configure the link with multiple, tagged VLANs.
Figure 2-10.
Example of a Solution for Single-Forwarding to Multiple-Forwarding
Database Devices in a Multiple VLAN Environment
Now, the 6600 forwarding database always lists the 6120 MAC address on port
A1, and the 6600 will send traffic to either VLAN on the 6120.
To increase the network bandwidth of the connection between the devices,
you can use a trunk of multiple physical links rather than a single physical link.
Multiple Forwarding Database Operation
If you want to connect one of the switches covered by this guide to another
switch that has a multiple forwarding database, you can use either or both of
the following connection options:
A separate port or port trunk interface for each VLAN. This results in a
forwarding database having multiple instances of the same MAC address
with different VLAN IDs and port numbers. (See table 2-4.) The fact that
the switches covered by this guide use the same MAC address on all VLAN
interfaces causes no problems.
The same port or port trunk interface for multiple (tagged) VLANs. This
results in a forwarding database having multiple instances of the same
MAC address with different VLAN IDs, but the same port number.
Allowing multiple entries of the same MAC address on different VLANs
enables topologies such as the following:
Switch
VLAN 1
VLAN 2
6120 Switch
VLAN 1
VLAN 2
This switch has multiple
forwarding databases.
This switch has a single
forwarding database.
PC “A”
PC “B”
VLAN
1 &
2
VLAN
1 & 2
A1
C1