HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.x administrator guide (569 - Page 317

How port mirroring works, F_Port Connection

Page 317 highlights

How port mirroring works Port mirroring reroutes the data frames between two devices to the mirror port. Rerouting introduces latency for the data flow. The latency depends on the location of the mirror port. For a given port, the traffic received from the point of view of the switch can be captured before leaving this ASIC. Each user port is connected to an ASIC port. The user port's ingress traffic is routed to another user port on this chip, uplinks to the core switch, or E_Ports to remote domains. Mirroring is used on user ports, uplink ports (C_Ports), or E_Ports to capture the received traffic. The user port's destination to source traffic can come from any of the E_Ports or user ports, either on the the same chip or a different chip. When the destination port is on a different CP or is a remote switch port, port mirroring installs ingress (traffic received) filters on the C_Ports. If the destination port is on the same ASIC, an egress (traffic sent) filter is installed on the source port. A port configured as a mirror port is configured so that the transmitter is looped back to the receiver. In addition, the transmit traffic is sent out of the transmit port. You could connect an analyzer to this port to collect all the traffic exiting this port. The traffic looped back will then be routed to the final destination. Traffic received externally from this port does not affect loopback traffic. The performance server daemon (psd) maintains the port mirroring database, which contains the source identifier, destination identifier, and a mirror port. Adding a new mirror connection adds the connection to the database, where the information is saved. Deleting the connection removes the mirror connection from the database. F_Port Connection-A port mirror connection containing both the source identifier and destination identifier on the same chip is called a "local chip connection." In this type of connection, only two ports are involved to capture the sent and received traffic. The destination port mirrors the received (from the switch's point of view) traffic. • Traffic is received at the source port and the switch routes these frames to the destination port. • The destination port has a port mirror, which redirects matching frames to the mirror port. • The mirror port then routes those frames it receives back to the destination port. FC_Port Connection-A port mirror connection between two F_Ports on different CPs but in the same switch, as in core-edge platforms. If one port is sending traffic to another port on a different chip, the port must send the traffic to the core to reach the edge ports located on another chip. • Traffic is received at the source port destined to another port on a different chip. The frame is routed to one of the C_Ports connected to the core. • All C_Ports have a port mirror filter to redirect those frames that match the filter to the mirror port. • 3.The mirror port then routes those frames it receives back to a C_Port. FCE_Port Connection-Port mirror connections on which the source identifier on the local switch and destination identifier is on a different switch is called an FCE_Port connection. In this type of connection, the source port, all the E-ports located on the same chip as the source port and all C_Ports located on the source chip are involved with this connection type. In addition, the C_Ports on other blades that have E_Ports are involved in this type of connection too. The received traffic can be sent to any E_Port, regardless of whether the port is on the same or another chip. The port mirrors the received traffic on all C_Ports and all E_Ports on that source identifier's chip. • Traffic is received at the source port destined to a remote port. The switch routes these frames to either a local E+Ports on this chip or to the C_Ports to reach another E-ports on a different blade. • The C_Ports and E_ports have a port mirror filter on these ports to redirect those frames that match the filter to the mirror port. • The mirror port then routes those frames it receives back to the either the C_ports or E_ports port. Fabric OS 5.3.0 administrator guide 329

  • 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
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465

Fabric OS 5.3.0 administrator guide
329
How port mirroring works
Port mirroring reroutes the data frames between two devices to the mirror port. Rerouting introduces latency
for the data flow. The latency depends on the location of the mirror port.
For a given port, the traffic received from the point of view of the switch can be captured before leaving this
ASIC. Each user port is connected to an ASIC port. The user port's ingress traffic is routed to another user
port on this chip, uplinks to the core switch, or E_Ports to remote domains.
Mirroring is used on user ports,
uplink ports (C_Ports), or E_Ports to capture the received traffic.
The user port's destination to source traffic can come from any of the E_Ports or user ports, either on the the
same chip or a different chip.
When the destination port is on a different CP or is a remote switch port, port mirroring installs ingress
(traffic received) filters on the C_Ports. If the destination port is on the same ASIC, an egress (traffic sent)
filter is installed on the source port.
A port configured as a mirror port is configured so that the transmitter is looped back to the receiver. In
addition, the transmit traffic is sent out of the transmit port. You could connect an analyzer to this port to
collect all the traffic exiting this port. The traffic looped back will then be routed to the final destination.
Traffic received externally from this port does not affect loopback traffic.
The performance server daemon (psd) maintains the port mirroring database, which contains the source
identifier, destination identifier, and a mirror port. Adding a new mirror connection adds the connection to
the database, where the information is saved. Deleting the connection removes the mirror connection from
the database.
F_Port Connection
—A port mirror connection containing both the source identifier and destination
identifier on the same chip is called a “local chip connection.” In this type of connection, only two ports
are involved to capture the sent and received traffic. The destination port mirrors the received (from the
switch’s point of view) traffic.
Traffic is received at the source port and the switch routes these frames to the destination port.
The destination port has a port mirror, which redirects matching frames to the mirror port.
The mirror port then routes those frames it receives back to the destination port.
FC_Port Connection
—A port mirror connection between two F_Ports on different CPs but in the same
switch, as in core-edge platforms. If one port is sending traffic to another port on a different chip, the port
must send the traffic to the core to reach the edge ports located on another chip.
Traffic is received at the source port destined to another port on a different chip. The frame is routed to
one of the C_Ports connected to the core.
All C_Ports have a port mirror filter to redirect those frames that match the filter to the mirror port.
3.The mirror port then routes those frames it receives back to a C_Port.
FCE_Port Connection
—Port mirror connections on which the source identifier on the local switch and
destination identifier is on a different switch is called an FCE_Port connection. In this type of connection,
the source port, all the E-ports located on the same chip as the source port and all C_Ports located on the
source chip are involved with this connection type. In addition, the C_Ports on other blades that have
E_Ports are involved in this type of connection too.
The received traffic can be sent to any E_Port, regardless of whether the port is on the same or another
chip. The port mirrors the received traffic on all C_Ports and all E_Ports on that source identifier's chip.
Traffic is received at the source port destined to a remote port. The switch routes these frames to either a
local E+Ports on this chip or to the C_Ports to reach another E-ports on a different blade.
The C_Ports and E_ports have a port mirror filter on these ports to redirect those frames that match the
filter to the mirror port.
The mirror port then routes those frames it receives back to the either the C_ports or E_ports port.