HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2. - Page 51

Testing components to and from the HBA, Segmented fabrics

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

Segmented fabrics 3 [-nframes count]-Specify the number of frames to send. [-lb_mode mode]-Select the loopback point for the test. [-spd_mode mode]-Select the speed mode for the test. [-ports itemlist]-Specify a list of user ports to test. Testing components to and from the HBA 1. Connect to the switch and log in as admin. 2. Enter the portTest command (see the Fabric OS Command Reference for information on the command options). See Table 7 on page 35 for a list of additional tests that can be used to determine the switch components that are not functioning properly. See the Fabric OS Command Reference for additional command information. TABLE 7 Test Switch component tests Function portLoopbackTest Performs a functional test of port N to N path. Verifies the functional components of the switch. turboRamTest Verifies that the on chip SRAM located in the 2 Gbps ASIC is using the Turbo-Ram BIST circuitry. This allows the BIST controller to perform the SRAM write and read operations at a much faster rate. Related Switch Test Option: itemList Restricts the items to be tested to a smaller set of parameter values that you pass to the switch. Segmented fabrics Fabric segmentation is generally caused by one of the following conditions: • Incompatible fabric parameters (see "Reconciling fabric parameters individually," next). • Incorrect PID setting (see Fabric OS Administrator's Guide). • Incompatible zoning configuration (see Chapter 9, "Zone Issues"). • Domain ID conflict (see "Reconciling fabric parameters individually" on page 36). • Fabric ID conflict (see Chapter 7, "Virtual Fabrics"). • Incompatible security policies. • Incorrect fabric mode. • Incorrect policy distribution. There are a number of settings that control the overall behavior and operation of the fabric. Some of these values, such as the domain ID, are assigned automatically by the fabric and can differ from one switch to another in the fabric. Other parameters, such as the BB credit, can be changed for specific applications or operating environments, but must be the same among all switches to allow the formation of a fabric. The following fabric parameters must be identical on each switch for a fabric to merge: Fabric OS Troubleshooting and Diagnostics Guide 35 53-1001187-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
Fabric OS Troubleshooting and Diagnostics Guide
35
53-1001187-01
Segmented fabrics
3
[
-nframes
count
]—Specify the number of frames to send.
[
-lb_mode
mode
]—Select the loopback point for the test.
[
-spd_mode
mode
]—Select the speed mode for the test.
[
-ports
itemlist
]—Specify a list of user ports to test.
Testing components to and from the HBA
1.
Connect to the switch and log in as admin.
2.
Enter the
portTest
command (see the
Fabric OS Command Reference
for information on the
command options).
See
Table 7
on page 35 for a list of additional tests that can be used to determine the switch
components that are not functioning properly. See the
Fabric OS Command Reference
for
additional command information.
Segmented fabrics
Fabric segmentation is generally caused by one of the following conditions:
•
Incompatible fabric parameters (see
“Reconciling fabric parameters individually,”
next).
•
Incorrect PID setting (see
Fabric OS Administrator’s Guide
).
•
Incompatible zoning configuration (see
Chapter 9, “Zone Issues”
).
•
Domain ID conflict (see
“Reconciling fabric parameters individually”
on page 36).
•
Fabric ID conflict (see
Chapter 7, “Virtual Fabrics”
).
•
Incompatible security policies.
•
Incorrect fabric mode.
•
Incorrect policy distribution.
There are a number of settings that control the overall behavior and operation of the fabric. Some
of these values, such as the domain ID, are assigned automatically by the fabric and can differ
from one switch to another in the fabric. Other parameters, such as the BB credit, can be changed
for specific applications or operating environments, but must be the same among all switches to
allow the formation of a fabric.
The following fabric parameters must be identical on each switch for a fabric to merge:
TABLE 7
Switch component tests
Test
Function
portLoopbackTest
Performs a functional test of port N to N path. Verifies the functional components of the
switch.
turboRamTest
Verifies that the on chip SRAM located in the 2 Gbps ASIC is using the Turbo-Ram BIST
circuitry. This allows the BIST controller to perform the SRAM write and read operations at a
much faster rate.
Related Switch Test Option:
itemList
Restricts the items to be tested to a smaller set of parameter values that you pass to the
switch.