Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 107

Understanding D_Port, Advantages of D_Port

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

Page 107 highlights

Diagnostic Port (D_Port) 10 Understanding D_Port The D_Port does not carry any user traffic, and is designed to run only specific diagnostics tests on it for identifying link-level faults or failures. Basically, in order to bring up a port in D_Port mode, you must configure both ends of the link between a given pair of switches (or switches configured as Access Gateways), and you must disable the existing port before you can configure it as a D_Port. Figure 3 illustrates an example D_Port connection between a pair of switches through SFPs (port assignments will vary). (For all topologies supported, see "Supported topologies" on page 93.) FIGURE 3 Example of a basic D_Port connection between switches Once the ports are configured as D_Ports, the following basic test suite is executed in the following order, depending on the SFPs installed: 1. Electrical loopback (with 16G SFP+ only) 2. Optical loopback (with 16G SFP+ only) 3. Link traffic (with 10G SFPs and 16G SFP+) 4. Link latency and distance measurement (with 10G SFPs and 16G SFP+) NOTE Electrical and optical loopback tests are not supported for ICLs. The fundamentals of D_Port testing are as follows: 1. The user configures the desired ports on both ends of the connection. 2. Once both sides are configured, a basic test suite is initiated automatically when the link comes online, conducting diagnostic tests in the following order: (1) electrical loopback, (2) optical loopback, and (3) link traffic. 3. After the automatic test is complete, the user can view results (through CLI or GUI) and rectify issues (if any) that are reported. 4. The user can also start (and restart) the test manually to verify the link. Advantages of D_Port Use the D_Port tests for the following situations: • Testing a new link before adding it to the fabric • Testing a trunk member before joining it with the trunk • Testing long-distance cables and SFPs Tests can be run with the following options: • Number of test frames to transmit Fabric OS Troubleshooting and Diagnostics Guide 91 53-1002751-01

  • 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
Fabric OS Troubleshooting and Diagnostics Guide
91
53-1002751-01
Diagnostic Port (D_Port)
10
Understanding D_Port
The D_Port does not carry any user traffic, and is designed to run only specific diagnostics tests on
it for identifying link-level faults or failures. Basically, in order to bring up a port in D_Port mode, you
must configure both ends of the link between a given pair of switches (or switches configured as
Access Gateways), and you must disable the existing port before you can configure it as a D_Port.
Figure 3
illustrates an example D_Port connection between a pair of switches through SFPs (port
assignments will vary). (For all topologies supported, see
“Supported topologies”
on page 93.)
FIGURE 3
Example of a basic D_Port connection between switches
Once the ports are configured as D_Ports, the following basic test suite is executed in the following
order, depending on the SFPs installed:
1.
Electrical loopback (with 16G SFP+ only)
2.
Optical loopback (with 16G SFP+ only)
3.
Link traffic (with 10G SFPs and 16G SFP+)
4.
Link latency and distance measurement (with 10G SFPs and 16G SFP+)
NOTE
Electrical and optical loopback tests are not supported for ICLs.
The fundamentals of D_Port testing are as follows:
1.
The user configures the desired ports on both ends of the connection.
2.
Once both sides are configured, a basic test suite is initiated automatically when the link
comes online, conducting diagnostic tests in the following order: (1) electrical loopback, (2)
optical loopback, and (3) link traffic.
3.
After the automatic test is complete, the user can view results (through CLI or GUI) and rectify
issues (if any) that are reported.
4.
The user can also start (and restart) the test manually to verify the link.
Advantages of D_Port
Use the D_Port tests for the following situations:
•
Testing a new link before adding it to the fabric
•
Testing a trunk member before joining it with the trunk
•
Testing long-distance cables and SFPs
Tests can be run with the following options:
•
Number of test frames to transmit