Display the state of all Fibre Channel ports. The output will show key information about each Fibre Channel port. For example:
iPXE> fcstat net0: 20:00:52:54:00:12:34:56 id 18.ae.02 node 10:00:52:54:00:12:34:56 [Link: up, 20:00:ae:a5:83:a2:78:1a fabric node 10:00:ae:a5:83:a2:78:1a] 20:00:ae:a5:83:a2:78:1a: [Link: up, port net0 id ff.ff.fc] 20:00:00:1f:16:bc:fe:2f: [Link: up, port net0 id 18.ae.01] [Type 08 usage 0 link: up, params 00:00:01:b2]
In this example you can see that there is a single Fibre Channel port (an FCoE port attached to network interface
net0), which has a port name of
20:00:52:54:00:12:34:56, a port ID of
18.ae.02, and a node name of
The more detailed information shows that the port is attached to a fabric via a Fibre Channel switch port which has a port name of
20:00:ae:a5:83:a2:78:1a and a node name of
The list of Fibre Channel peers shows that iPXE has successfully logged in to the Fibre Channel name server (with the well-known port ID
ff.ff.fc), and to a Fibre Channel Protocol target with the port ID
Fibre Channel ports are created automatically for any capable network interfaces. You will not see any Fibre Channel ports listed by
fcstat until the underlying network interface has been opened (e.g. using
ifopen). It can take a few seconds after the network interface has been opened for iPXE to create the corresponding Fibre Channel port.
You can use the
fcels command to control the process of logging in to the Fibre Channel fabric and to other Fibre Channel peers.
Fibre Channel over Ethernet (FCoE) typically operates over a VLAN network interface that is created automatically during the Fibre Channel fabric login process. You can also create the relevant VLAN interfaces manually using