Re: Reg. flow-control settings using NetworkManager
by Gris Ge
On Wed, Nov 18, 2020 at 10:12:10AM +0000, Vishal Deep Ajmera wrote:
> Hi Greg, Thomas,
>
> I have opened a new feature request for addition support for pause settings
> via nmstate. Let me know if any other information is needed.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1898910
Hi Vishal,
Thanks for the bug report!
I will work on the nispor for query part and NetworkManager
will do the applying support, once done, we will have it in nmstate.
--
Gris Ge
2 years, 4 months
Re: Reg. flow-control settings using NetworkManager
by Vishal Deep Ajmera
Hi Greg, Thomas,
I have opened a new feature request for addition support for pause settings
via nmstate. Let me know if any other information is needed.
https://bugzilla.redhat.com/show_bug.cgi?id=1898910
Regards,
Vishal
> -----Original Message-----
> From: Vishal Deep Ajmera <vishal.deep.ajmera(a)ericsson.com>
> Sent: Friday, November 6, 2020 10:08 AM
> To: Thomas Haller <thaller(a)redhat.com>; Gris Ge <fge(a)redhat.com>
> Cc: Ganesh Vasudevan <ganesh.vasudevan(a)ericsson.com>; nmstate-
> devel(a)lists.fedorahosted.org; Anurag Agarwal
> <anurag.agarwal(a)ericsson.com>
> Subject: [nmstate-devel] Re: 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.
2 years, 4 months
Re: Reg. flow-control settings using NetworkManager
by Gris Ge
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 years, 4 months
Reg. flow-control settings using NetworkManager
by Vishal Deep Ajmera
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?
Unfortunately we cannot enable auto-negotiation for the port as it is of
FIBRE type.
Warm Regards,
Vishal Ajmera
2 years, 4 months