[ipxe-devel] [Patch] Add fcoestat command

Clark, Steven sclark at crossbeam.com
Wed Jun 27 21:41:48 UTC 2012

Thanks for your help.
I'm trying to get vn2vn mode working so no FCF involved.
I'll try out your suggestions.  So far I haven't tried using VLAN but I can set it up that way if needed.  


> -----Original Message-----
> From: Michael Brown [mailto:mbrown at fensystems.co.uk]
> Sent: Wednesday, June 27, 2012 5:14 PM
> To: Clark, Steven
> Cc: ipxe-devel at lists.ipxe.org
> Subject: Re: [ipxe-devel] [Patch] Add fcoestat command
> On Wednesday 27 Jun 2012 19:53:30 Clark, Steven wrote:
> > The problem I'm chasing right now is that I get fcoe ports but no fc ports.
> > Since they are not 1:1 I found it helpful to dump some status.
> OK.  It sounds as though you're having problems with FIP.  Useful things to
> try would be to build with DEBUG=fcoe and (if possible) to try capturing the
> traffic.  Capturing traffic might be difficult given that FCoE tends to use VLANs.
> iPXE will use FIP VLAN discovery to detect an FCoE VLAN.  You can see if any
> VLAN devices have been created via "ifstat".  Once a VLAN has been discovered
> (or VLAN discovery has timed out), iPXE will use FIP to detect an FCF.  The FC
> device (visible via "fcstat") will be created only once a FCF has been
> detected (or FCF detection has timed out).
> Common problems with iPXE FCoE are:
> a) NIC drivers that don't strip the Ethernet CRC from the received packet:
> this doesn't affect TCP or UDP but will break FCoE
> b) NIC drivers that don't enable promiscuous mode
> Michael

More information about the ipxe-devel mailing list