Re: netmap memory config query

[Vincenzo Maffione]

Hi,
  The parameter to increase is "ring_size". FreeBSD or Linux does not
matter (except for how you modify the parameter, i.e. sysctl on FreeBSD and
sysfs in Linux).

Cheers,
  Vincenzo

2018-03-14 20:59 GMT+01:00 Joe Buehler :

> When I increase the ixgbevf rx ring size from 1024 to 4096 I get this:
>
> [ 5526.651780] 851.135009 [ 931] netmap_obj_malloc netmap_ring
> request size 65792 too large
> [ 5526.652779] 851.136008 [1802] netmap_mem2_rings_create  Cannot allocate
> RX_ring
>
> What netmap module parameters do I need to tweak to get past this?
>
> I am using LINUX should it matter.
>
> Joe Buehler
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>



-- 
Vincenzo Maffione
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

netmap memory config query

[Joe Buehler]

When I increase the ixgbevf rx ring size from 1024 to 4096 I get this:

[ 5526.651780] 851.135009 [ 931] netmap_obj_malloc netmap_ring request 
size 65792 too large
[ 5526.652779] 851.136008 [1802] netmap_mem2_rings_create  Cannot allocate 
RX_ring

What netmap module parameters do I need to tweak to get past this?

I am using LINUX should it matter.

Joe Buehler
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Cisco shows LACP not enabled on 11.1U2, BCM 57810S-t, 2960X IOS 15.2

[Rob Hutton]

Thanks for your help on this!

On Tue, Mar 13, 2018 at 9:09 PM Eugene Grosbein  wrote:

> 14.03.2018 1:28, Rob Hutton wrote:
>
> > Trying to get to a LACP Trunk config working on FreeNAS, but I'm not sure
> > if this is an upstream issue.  First step is just LACP bundle in edge
> mode
> > (no vlans) and bundle will not form.  The FreeNAS side shows it as being
> > active.  The switch is reporting that LACP is not enabled on the
> individual
> > ports.  We have tried multiple versions of IOS from 15.0 to 15.2(6)E1.  I
> > have about 10 windows servers with the same NICs on the same switch that
> > are negotiating LACP successfully as well as tagging vlans, so the
> hardware
> > pieces seem to be OK.  I have tried configuring from both the GUI and the
> > CL with the same result.
> >
> > Cisco 2960X
> >
> > switch config:
> > interface Port-channel10
> > switchport access vlan 1900
> > switchport mode access
> > !
> > interface GigabitEthernet1/0/27
> > switchport access vlan 1900
> > switchport mode access
> > channel-group 10 mode active
> > !
> > interface GigabitEthernet1/0/28
> > switchport access vlan 1900
> > switchport mode access
> > channel-group 10 mode active
> >
> > logs from switch:
> > Mar 13 17:38:09.626: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/27,
> > changed state to up
> > Mar 13 17:38:09.665: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28,
> > changed state to up
> > Mar 13 17:38:15.753: %EC-5-L3DONTBNDL2: Gi1/0/28 suspended: LACP
> currently
> > not enabled on the remote port.
> > Mar 13 17:38:16.005: %EC-5-L3DONTBNDL2: Gi1/0/27 suspended: LACP
> currently
> > not enabled on the remote port.
> >
> > Switch#sh etherc summ
> > Flags:  D - down P - bundled in port-channel
> > I - stand-alone s - suspended
> > H - Hot-standby (LACP only)
> > R - Layer3   S - Layer2
> > U - in use   N - not in use, no aggregation
> > f - failed to allocate aggregator
> >
> > M - not in use, minimum links not met
> > m - not in use, port not aggregated due to minimum links not met
> > u - unsuitable for bundling
> > w - waiting to be aggregated
> > d - default port
> >
> > A - formed by Auto LAG
> >
> >
> > Number of channel-groups in use: 1
> > Number of aggregators:1
> >
> > Group  Port-channel  Protocol Ports
> >
> --+-+---+---
> > 10  Po10(SD) LACP   Gi1/0/27(w) Gi1/0/28(w)
> >
> > Switch#sh int gi1/0/27
> > GigabitEthernet1/0/27 is up, line protocol is down (notconnect)
> >
> > Switch#sh int gi1/0/28
> > GigabitEthernet1/0/28 is up, line protocol is down (notconnect)
> >
> >
> > FreeNAS
> > ifconfig
> >
> > bxe0: flags=8843 metric 0 mtu
> 1500
> >
> options=527bb > M,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
> >ether 00:0e:1e:86:7c:70
> >hwaddr 00:0e:1e:86:7c:70
> >nd6 options=9
> >media: Ethernet autoselect (10Gbase-T )
> >status: active
> >
> > bxe1: flags=8843 metric 0 mtu
> 1500
> >
> options=527bb > M,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
> >ether 00:0e:1e:86:7c:70
> >hwaddr 00:0e:1e:86:7c:72
> >nd6 options=9
> >media: Ethernet autoselect (10Gbase-T )
> >status: active
> >
> > lagg0: flags=8843 metric 0 mtu
> 1500
> >
> options=527bb > M,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
> >ether 00:0e:1e:86:7c:70
> >nd6 options=9
> >media: Ethernet autoselect
> >status: active
> >groups: lagg
> >laggproto lacp lagghash l2,l3,l4
> >laggport: bxe0 flags=0<>
> >laggport: bxe1 flags=0<>
> >
> > Last edited: 12 minutes ago
>
> See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
>
> In short: bxe(4) driver fails to setup hardware so it would receive
> incoming
> multicast LACP frames unless switched to promisc. mode.
>
> For now, replace the NIC with one from distinct manufacturer (Intel etc.)
>
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"