From: ayuj <ayuj.verma@gmail.com>
To: netdev@vger.kernel.org
Subject: Configure traffic class to bringup DCB in back-to-back setup
Date: Wed, 13 Jul 2016 09:09:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20160713T110657-740@post.gmane.org> (raw)
I just checked TLV's. Below are the 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....
lldptool -t -i p3p2 -n
Chassis ID TLV
MAC: 00:1b:21:bb:2e:da
Port ID TLV
MAC: 00:1b:21:bb:2e:da
Time to Live TLV
120
IEEE 8021QAZ ETS Configuration TLV
Willing: yes
CBS: not supported
MAX_TCS: 8
PRIO_MAP: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
TC Bandwidth: 0% 0% 0% 0% 0% 0% 0% 0%
TSA_MAP: 0:strict 1:strict 2:strict 3:strict 4:strict 5:strict 6:strict
7:strict
IEEE 8021QAZ PFC TLV
Willing: yes
MACsec Bypass Capable: no
PFC capable traffic classes: 8
PFC enabled: none
End of LLDPDU TLV
Please help me in configuring traffic classes. I want to bringup DCB setup
in a back-to-back senario.
next reply other threads:[~2016-07-13 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 9:09 ayuj [this message]
2016-07-13 17:44 ` [Intel-wired-lan] Configure traffic class to bringup DCB in back-to-back setup John Fastabend
2016-07-13 17:44 ` John Fastabend
2016-07-14 9:35 ` ayuj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160713T110657-740@post.gmane.org \
--to=ayuj.verma@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.