====== Issue Fibre Channel ELS request ======

===== Synopsis =====

    fcels [--port <port>] [--id <peer port id>] <request>

===== Examples =====

=== Log in to the peer 18.ae.01 ===

    fcels --id 18.ae.01 plogi

=== Ping the peer 18.ae.01 ===

    fcels --id 18.ae.01 echo

=== Log out from the fabric ===

    fcels logo

===== Description =====

Issue the specified Fibre Channel ELS request to the specified peer port ID via the specified Fibre Channel port.  The request must be one of the following:

  * ''flogi'' - Log in to Fibre Channel fabric
  * ''plogi'' - Log in to Fibre Channel port
  * ''prli-fcp'' - Log in to FCP initiator or target
  * ''logo'' - Log out
  * ''echo'' - Ping

If no port is explicitly specified, iPXE will use the first Fibre Channel port as shown by ''[[:cmd:fcstat]]''

If no peer port ID is explicitly specified, iPXE will attempt to use a sensible default port ID as follows:

  *  if the port is attached to a fabric via a Fibre Channel switch, iPXE will use the well-known port ID ''ff.ff.fe'',

  *  if the port is attached directly to another Fibre Channel peer, iPXE will use the ID of the peer port.

===== Command status =====

^ Success   | The ELS request received a successful response        |
^ Failure   | The ELS request did not receive a successful response |

===== See also =====

  * ''[[:cmd:fcstat]]''
  * [[:cmd|List of all iPXE commands]]

===== Build options =====

This command is available only when the build options ''[[:buildcfg:NET_PROTO_FCOE]]'' and ''[[:buildcfg:FCMGMT_CMD]]'' are enabled.

===== Notes =====

You can use the ''[[:cmd:fcstat]]'' command to view the state of Fibre Channel ports and peers.

Fibre Channel ELS requests are generally issued automatically as needed.  You should only need to use the ''fcels'' command if you need to debug Fibre Channel problems.