Bug 1353659

Summary:	[fcoe] While DCB is enabled, VLAN FCoE interface is not created using AUTO_VLAN
Product:	Red Hat Enterprise Linux 7	Reporter:	Elad <ebenahar>
Component:	fcoe-utils	Assignee:	Chris Leech <cleech>
Status:	CLOSED WONTFIX	QA Contact:	guazhang <guazhang>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	acanan, cleech, danken, dholler, guazhang, jcastillo
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:42:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Elad 2016-07-07 16:07:31 UTC

Description of problem:
While DCB=yes for an FCoE interface in /etc/fcoe/cfg-<interface> and AUTO_VLAN is unable to detect the FCoE VLAN and to create a VLAN interface for this interface.
I'm using a special hook for RHEV VDSM for FCoE interface configuration (the hook is attached).


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.2 (Maipo)
fcoe-utils-1.0.30-3.git91c0c8c.el7.x86_64
lldpad-1.0.1-2.git986eb2e.el7.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Host with FCoE CNA connected to an FCoE compatible switch 
2. Enable the hook on the server with the following fcoe interface parameters:
enable=yes,dcb=yes,auto_vlan=yes

This will create the FCoE interface file configuration under /etc/fcoe:

DCB_REQUIRED="yes"
FCOE_ENABLE="yes"
MODE="fabric"
AUTO_VLAN="yes"


Actual results:

[root@RHEL7 ~]# fcoeadm -i
No FCoE interfaces created.



Changed the configuration file /etc/fcoe/cfg-em1_1 with DCB_REQUIRED="no" and checked 'fcoeadm -i':


[root@RHEL7 ~]# fcoeadm -i
    Description:      NetXtreme II BCM57800 1/10 Gigabit Ethernet Multi Function
    Revision:         10
    Manufacturer:     Broadcom Corporation
    Serial Number:    1866DA56CC3C
    Driver:           bnx2x 1.710.51-0
    Number of Ports:  1

        Symbolic Name:     bnx2fc (QLogic BCM57800) v2.4.2 over em1_1.1020-fcoe
        OS Device Name:    host17
        Node Name:         0x20001866DA56CC3D
        Port Name:         0x20011866DA56CC3D
        FabricName:        0x1000F8BC12273D20
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048
        FC-ID (Port ID):   0x013300
        State:             Online

        Symbolic Name:     bnx2fc (QLogic BCM57800) v2.4.2 over em2_1.1020-fcoe
        OS Device Name:    host18
        Node Name:         0x20001866DA56CC3F
        Port Name:         0x20011866DA56CC3F
        FabricName:        0x1000F8BC12273D20
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048
        FC-ID (Port ID):   0x013000
        State:             Online




For FCoE to work properly, I changed the conf file to DCB_REQUIRED="yes" again (using the hook). 
But this causes the FCoE VLAN interface to disappear after host reboot.




Expected results:
While DCB=yes and AUTO_VLAN=yes, FCoE VLAN interface should get created successfully.


Additional info:
hook, /var/log/

Comment 1 Elad 2016-07-07 16:11:13 UTC

FCoE hook and /var/log/ dir 

http://file.tlv.redhat.com/ebenahar/bug2.tar.gz

Comment 3 Jose Castillo 2016-07-08 08:12:41 UTC

Elad, for FCoE capable Broadcom NetXtreme II cards, DCB must be always off. More information about the cards using the bnx2fc module can be found here:

https://www.kernel.org/doc/Documentation/scsi/bnx2fc.txt

You mentioned the following in an email:

------------------------------------------------------------
I disabled DCB for the interface and the VLAN interface created successfully:

[root@RHEL7 fcoe]# fcoeadm -i
    Description:      NetXtreme II BCM57800 1/10 Gigabit Ethernet Multi
Function
    Revision:         10
    Manufacturer:     Broadcom Corporation
    Serial Number:    1866DA56D22A
    Driver:           bnx2x 1.710.51-0
    Number of Ports:  1

        Symbolic Name:     bnx2fc (QLogic BCM57800) v2.4.2 over
em1_1.1020-fcoe
        OS Device Name:    host17
        Node Name:         0x20001866DA56D22B
        Port Name:         0x20011866DA56D22B
        FabricName:        0x0000000000000000
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048
        FC-ID (Port ID):   0xFFFFFFFF
        State:             Offline

But the interface state remain Offline.

We must have DCB enabled for the FCoE VLAN interface to get online.
I configured the interface with DCB enabled after its VLAN interface got
created and now it is online:

[root@RHEL7 fcoe]# fcoeadm -i
    Description:      NetXtreme II BCM57800 1/10 Gigabit Ethernet Multi
Function
    Revision:         10
    Manufacturer:     Broadcom Corporation
    Serial Number:    1866DA56D22A
    Driver:           bnx2x 1.710.51-0
    Number of Ports:  1

        Symbolic Name:     bnx2fc (QLogic BCM57800) v2.4.2 over
em1_1.1020-fcoe
        OS Device Name:    host17
        Node Name:         0x20001866DA56D22B
        Port Name:         0x20011866DA56D22B
        FabricName:        0x1000F8BC12273D20
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2048
        FC-ID (Port ID):   0x013800
        State:             Online


So the workaround for now is to set the fcoe custom property with dcb=no
and confirm setup networks (so the VLAN interface will get created),
re-setup network and configure dcb=yes for the interface and confirm setup
network so the VLAN interface will get online.
------------------------------------------------------------

I don't think re-enabling DCB should be the solution here, because then you have DCB on chip and software DCB running at the same time. 
Question: After configuring the interface with the hook (with DCB=no), have you tried restarting the server and seeing if the interfaces get online

Comment 4 Elad 2016-07-08 09:07:31 UTC

(In reply to Jose Castillo from comment #3)
> So the workaround for now is to set the fcoe custom property with dcb=no
> and confirm setup networks (so the VLAN interface will get created),
> re-setup network and configure dcb=yes for the interface and confirm setup
> network so the VLAN interface will get online.
> ------------------------------------------------------------

Yes, that's the exact workaround I used.

> I don't think re-enabling DCB should be the solution here, because then you
> have DCB on chip and software DCB running at the same time. 
> Question: After configuring the interface with the hook (with DCB=no), have
> you tried restarting the server and seeing if the interfaces get online

After reboot, while DCB is set to 'yes', 'fcoeadm -i' reports that no interfaces exist.

Comment 5 Elad 2016-07-10 07:43:37 UTC

While dcb=no, after reboot the interfaces get created successfully.

Comment 9 RHEL Program Management 2020-12-15 07:42:49 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.