11:51 p.m.
On Wed, Nov 04, 2020 at 05:27:38AM +0000, Vishal Deep Ajmera wrote:
Hi,
We are using NetworkManager in our deployments and want to enable
flow-control using nmcli or NetworkConnection configuration files.
Equivalent command using ethtool is:
# ethtool -A <if-name> rx on tx on
Can someone point me to configuration setting in NetworkManager?
Hi Thomas,
Any idea?
Unfortunately we cannot enable auto-negotiation for the port as it is
of FIBRE type.
Warm Regards,
Vishal Ajmera
--
Gris Ge
2:38 a.m.
New subject: Reg. flow-control settings using NetworkManager
On Wed, 2020-11-04 at 13:51 +0800, Gris Ge wrote:
On Wed, Nov 04, 2020 at 05:27:38AM +0000, Vishal Deep Ajmera wrote:
> Hi,
>
> We are using NetworkManager in our deployments and want to enable
> flow-control using nmcli or NetworkConnection configuration files.
>
> Equivalent command using ethtool is:
>
> # ethtool -A <if-name> rx on tx on
>
> Can someone point me to configuration setting in NetworkManager?
Hi Thomas,
Any idea?
Hi,
ethtool's "-A" (pause parameters) are currently not supported by
NetworkManager.
The workarounds could be (in possible order of preference):
- I am not sure, but I guess you would only need to set those
parameters once per interface. NetworkManager would not touch it.
Hence, I expect you also could set it via a udev rule when the
interface gets added.
- use a dispatcher script in /etc/NetworkManager/dispatcher.d (see `man
NetworkManager)
- in general, any scripting solution that works for you.
- use initscripts instead of NetworkManager (which supports
a ETHTOOL_OPTS setting).
Btw, no feature request for this exists. If you think this should be added,
please report an RFE at [1].
[1] https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%...
> Unfortunately we cannot enable auto-negotiation for the port as
it
> is
> of FIBRE type.
Can you elaborate what you mean with this?
best,
Thomas
10:37 p.m.
New subject: Reg. flow-control settings using NetworkManager
Hi Thomas,
Thanks for your suggestions. Some comments below.
Warm Regards,
Vishal Ajmera
ethtool's "-A" (pause parameters) are currently not supported by
NetworkManager.
The workarounds could be (in possible order of preference):
- I am not sure, but I guess you would only need to set those
parameters once per interface. NetworkManager would not touch it.
Hence, I expect you also could set it via a udev rule when the
interface gets added.
- use a dispatcher script in /etc/NetworkManager/dispatcher.d (see `man
NetworkManager)
- in general, any scripting solution that works for you.
- use initscripts instead of NetworkManager (which supports
a ETHTOOL_OPTS setting).
Thanks. We will try these options. The issue is that name of the interfaces is
provided by user using nmstate configuration which means no hard-coding can be
done in any scripts. If an option as part of nmstate configuration (for e.g.
flow-control: true) can be set and NetworkManager can act on it the deployment
becomes much cleaner.
Btw, no feature request for this exists. If you think this should be
added,
please report an RFE at [1].
[1]
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterpris
e%20Linux%208
> > Unfortunately we cannot enable auto-negotiation for the port as it
> > is
> > of FIBRE type.
Can you elaborate what you mean with this?
If we can enable auto-negotiation on the
port then flow-control can be enabled
via remote switch as part of negotiation. However FIBRE type ports does not
support setting of auto-negotiation.
1268
days inactive
1270
days old
nmstate-devel@lists.fedorahosted.org
2 comments
3 participants
participants (3)
-
Gris Ge -
Thomas Haller -
Vishal Deep Ajmera