HP StorageWorks 8/80 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53- - Page 31

Connections Issues, In this Port initialization and FCP auto discovery process

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

Connections Issues Chapter 3 This chapter provides information on troubleshooting basic connectivity issues and the most common procedures to use to diagnose and recover from basic connection problems. In this chapter •Port initialization and FCP auto discovery process 17 •Link issues 19 •Connection problems 19 •Link failures 21 •Marginal links 24 •Device login issues 25 •Media-related issues 29 •Segmented fabrics 31 Port initialization and FCP auto discovery process The steps in the port initialization process represent a protocol used to discover the type of connected device and establish the port type and port speed. The possible port types are as follows: • U_Port-Universal FC port. The base Fibre Channel port type and all unidentified, or uninitiated ports are listed as U_Ports. • L_/FL_Port-Fabric Loop port. Connects public loop devices. • G_Port-Generic port. Acts as a transition port for non-loop fabric-capable devices. • E_Port-Expansion port. Assigned to ISL links. • F_Port-Fabric port. Assigned to fabric-capable devices. • EX_Port-A type of E_Port. It connects a Fibre Channel router to an edge fabric. From the point of view of a switch in an edge fabric, an EX_Port appears as a normal E_Port. It follows applicable Fibre Channel standards as other E_Ports. However, the router terminates EX_Ports rather than allowing different fabrics to merge as would happen on a switch with regular E_Ports. • VE_Port-A virtual E_Port. However, it terminates at the switch and does not propagate fabric services or routing topology information from one edge fabric to another. • VEX_Port-A virtual EX_Port. It connects a Fibre Channel router to an edge fabric. From the point of view of a switch in an edge fabric, a VEX_Port appears as a normal VE_Port. It follows the same Fibre Channel protocol as other VE_Ports. However, the router terminates VEX_Ports rather than allowing different fabrics to merge as would happen on a switch with regular VE_Ports. Fabric OS Troubleshooting and Diagnostics Guide 17 53-1000853-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
Fabric OS Troubleshooting and Diagnostics Guide
17
53-1000853-01
Chapter
3
Connections Issues
This chapter provides information on troubleshooting basic connectivity issues and the most
common procedures to use to diagnose and recover from basic connection problems.
In this chapter
•
Port initialization and FCP auto discovery process . . . . . . . . . . . . . . . . . . . .
17
•
Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
•
Connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
•
Link failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
•
Marginal links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
•
Device login issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
•
Media-related issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
•
Segmented fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Port initialization and FCP auto discovery process
The steps in the port initialization process represent a protocol used to discover the type of
connected device and establish the port type and port speed. The possible port types are as
follows:
•
U_Port—Universal FC port. The base Fibre Channel port type and all unidentified, or uninitiated
ports are listed as U_Ports.
•
L_/FL_Port—Fabric Loop port. Connects public loop devices.
•
G_Port—Generic port. Acts as a transition port for non-loop fabric-capable devices.
•
E_Port—Expansion port. Assigned to ISL links.
•
F_Port—Fabric port. Assigned to fabric-capable devices.
•
EX_Port—A type of E_Port. It connects a Fibre Channel router to an edge fabric. From the point
of view of a switch in an edge fabric, an EX_Port appears as a normal E_Port. It follows
applicable Fibre Channel standards as other E_Ports. However, the router terminates EX_Ports
rather than allowing different fabrics to merge as would happen on a switch with regular
E_Ports.
•
VE_Port—A virtual E_Port. However, it terminates at the switch and does not propagate fabric
services or routing topology information from one edge fabric to another.
•
VEX_Port—A virtual EX_Port. It connects a Fibre Channel router to an edge fabric. From the
point of view of a switch in an edge fabric, a VEX_Port appears as a normal VE_Port. It follows
the same Fibre Channel protocol as other VE_Ports. However, the router terminates VEX_Ports
rather than allowing different fabrics to merge as would happen on a switch with regular
VE_Ports.