Re: DCB Auto turn off when link become up with Intel 82599ES ixgbe driver

On Tue, Jul 5, 2016 at 8:17 AM, ayuj [off-list ref] wrote:

I'm trying to configure DCB in back-to-back scenario.
System details

OS :- CentOS 7.2
kernel 3.10.0-327.el7.x86_64
lldpad:- lldpad v0.9.46
dcbtool:- v0.9.46
ixgbe :- ixgbe-4.3.15

steps followed:-

# modporbe ixgbe
# service lldpad start
    Redirecting to /bin/systemctl start  lldpad.service


# service lldpad status
Redirecting to /bin/systemctl status  lldpad.service
● lldpad.service - Link Layer Discovery Protocol Agent Daemon.
   Loaded: loaded (/usr/lib/systemd/system/lldpad.service; disabled; vendor
preset: disabled)
   Active: active (running) since Tue 2016-07-05 05:49:12 EDT; 1s ago
 Main PID: 133737 (lldpad)
   CGroup: /system.slice/lldpad.service
           └─133737 /usr/sbin/lldpad -t

Jul 05 05:49:12 localhost.localdomain systemd[1]: Started Link Layer
Discovery Protocol Agent Daemon..
Jul 05 05:49:12 localhost.localdomain systemd[1]: Starting Link Layer
Discovery Protocol Agent Daemon....


# dcbtool gc p3p2 dcb
Command:        Get Config
Feature:        DCB State
Port:           p3p2
Status:         Successful
DCB State:      off

# dcbtool sc p3p2 dcb on
Command:        Set Config
Feature:        DCB State
Port:           p3p2
Status:         Successful

# dcbtool gc p3p2 dcb
Command:        Get Config
Feature:        DCB State
Port:           p3p2
Status:         Successful
DCB State:      on


Similar configuration on another system.

But as soon as I do "ifconfig p3p2 up and check dcb

# dcbtool gc p3p2 dcb
Command:        Get Config
Feature:        DCB State
Port:           p3p2
Status:         Successful
DCB State:      off

Initially suspecting issue with lldpad daemon/ixgbe driver. I replaced them
(downloaded from repo) with latest packages.
Same behaviour observed.

- Tried disabling other dcb features like fcoe. Same issue.
- Disabled selinux etc


Can any 1 help me regarding this.

I'm adding e1000-devel as that is the mailing list for the ixgbe maintainers.

You might want to go through and also check the number of TCs and how
you have them mapped to your priority groups.  It is possible that one
end or the other may only have 1 TC configured and if I am not
mistaken that is interpreted as having DCB disabled by the hardware.

Hope that helps.

- Alex