Вы находитесь на странице: 1из 3

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_PortUniversal FC port. The base Fibre Channel port type and all unidentified, or
uninitiated
ports are listed as U_Ports.
L_/FL_PortFabric Loop port. Connects public loop devices.
G_PortGeneric port. Acts as a transition port for non-loop fabric-capable devices.
E_PortExpansion port. Assigned to ISL links.
F_PortFabric port. Assigned to fabric-capable devices.
EX_PortA 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_PortA 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_PortA 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.
The FCP auto discovery process enables private storage devices that accept the process
login (PRLI) to communicate in a fabric.

If device probing is enabled, the embedded port logs in (PLOGI) and attempts a PRLI into the
device to retrieve information to enter into the name server. This enables private devices
that do not perform a fabric login (FLOGI), but accept PRLI, to be entered in the name server
and receive full fabric citizenship. Private hosts require the QuickLoop feature which is not
available in Fabric OS v4.0.0 and later.

A fabric-capable device will register information with the Name Server during a FLOGI. These
devices will typically register information with the name server before querying for a device
list. The embedded port will still PLOGI and attempt PRLI with these devices.
Link issues:
Symptom LEDs are flashing.

Connection problems:
If a host is unable to detect its target, for example, a storage or tape device, you should
begin
troubleshooting the problem at the switch.
Checking the logical connection:-
1. Enter the switchShow command.
2. Review the output from the command and determine if the device successfully logged
into the switch.
3. If the missing device is logically connected, proceed to the next troubleshooting
procedure(checking the Name Server).
4. If the missing device is not logically connected, check the device and everything on that
side of the
data path.