Mailing List Archive

zc with RSS kill the management interface of my host
hi,
I have 2 capture interfaces(p1p1 and p1p2, 10Gb) and 1 management interface
in my server. After I have setup the number of rss queue of p1p1 with
'pf_ringcfg
--configure-driver ixgbe --rss-queues 2', I tried to start up two pfcount
to do some test: 'pfcount -i zc:p1p1@0' and 'pfcount -i zc:p1p1@1'. After
the second pfcount started, I lost my ssh session with my server and I
cannot ping it neither. Everything came back after several minutes waiting
without doing anything.
My pfring version is 7.5.0, and Is there anything wrong with it?

thanks,
wang
Re: zc with RSS kill the management interface of my host [ In reply to ]
Hi Wang
please provide:

1. lspci | grep Eth
2. ifconfig
3. ethtool -i {p1p1,p1p2,<management>}

Thank you
Alfredo

> On 21 Jan 2020, at 08:44, Wang <cnwangyong@gmail.com> wrote:
>
> hi,
> I have 2 capture interfaces(p1p1 and p1p2, 10Gb) and 1 management interface in my server. After I have setup the number of rss queue of p1p1 with 'pf_ringcfg --configure-driver ixgbe --rss-queues 2', I tried to start up two pfcount to do some test: 'pfcount -i zc:p1p1@0' and 'pfcount -i zc:p1p1@1'. After the second pfcount started, I lost my ssh session with my server and I cannot ping it neither. Everything came back after several minutes waiting without doing anything.
> My pfring version is 7.5.0, and Is there anything wrong with it?
>
> thanks,
> wang
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: zc with RSS kill the management interface of my host [ In reply to ]
sorry but I do not have lspci installed in this host. What I know is that I
have 2 onboard 1Gb ports and one 2-port 82599em and one 4-port intel 1Gb
NIC.
I have installed zc license for p1p1. The management port is em1.
the ifconfig and ethtool info are listed here:

[root@r510 ~]# ethtool -i p1p1
driver: ixgbe
version: 5.5.3
firmware-version: 0x2b2c0001
expansion-rom-version:
bus-info: 0000:08:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes


[root@r510 ~]# ethtool -i p1p2
driver: ixgbe
version: 5.5.3
firmware-version: 0x2b2c0001
expansion-rom-version:
bus-info: 0000:08:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes


[root@r510 ~]# ethtool -i em1
driver: bnx2
version: 2.2.6
firmware-version: 6.0.1 bc 5.2.3 NCSI 2.0.10
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no


[root@r510 ~]# ifconfig
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.66.101 netmask 255.255.255.0 broadcast 192.168.66.255
inet6 fe80::2001:70e3:7246:b725 prefixlen 64 scopeid 0x20<link>
ether 84:2b:2b:78:8a:62 txqueuelen 1000 (Ethernet)
RX packets 26069 bytes 3177036 (3.0 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 5945 bytes 1443645 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 84:2b:2b:78:8a:63 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 19 bytes 1737 (1.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19 bytes 1737 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p1p1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
ether 48:f8:db:7e:da:5c txqueuelen 1000 (Ethernet)
RX packets 6322614433 bytes 3091202586919 (2.8 TiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 869 bytes 147082 (143.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdd300000-dd380000

p1p2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 48:f8:db:7e:da:5d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdd380000-dd400000

p2p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:1b:21:b0:5c:a8 txqueuelen 1000 (Ethernet)
RX packets 287 bytes 98154 (95.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdebc0000-debdffff

p2p2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:b0:5c:a9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdebe0000-debfffff

p2p3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:b0:5c:ac txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xddbc0000-ddbdffff

p2p4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:b0:5c:ad txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xddbe0000-ddbfffff

On Tue, Jan 21, 2020 at 6:08 PM Alfredo Cardigliano <cardigliano@ntop.org>
wrote:

> Hi Wang
> please provide:
>
> 1. lspci | grep Eth
> 2. ifconfig
> 3. ethtool -i {p1p1,p1p2,<management>}
>
> Thank you
> Alfredo
>
> On 21 Jan 2020, at 08:44, Wang <cnwangyong@gmail.com> wrote:
>
> hi,
> I have 2 capture interfaces(p1p1 and p1p2, 10Gb) and 1
> management interface in my server. After I have setup the number of rss
> queue of p1p1 with 'pf_ringcfg --configure-driver ixgbe --rss-queues 2',
> I tried to start up two pfcount to do some test: 'pfcount -i zc:p1p1@0'
> and 'pfcount -i zc:p1p1@1'. After the second pfcount started, I lost my
> ssh session with my server and I cannot ping it neither. Everything came
> back after several minutes waiting without doing anything.
> My pfring version is 7.5.0, and Is there anything wrong with it?
>
> thanks,
> wang
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: zc with RSS kill the management interface of my host [ In reply to ]
Please update to latest package/code as I pushed a fix that *could* address this

Alfredo

> On 21 Jan 2020, at 16:06, Wang <cnwangyong@gmail.com> wrote:
>
> sorry but I do not have lspci installed in this host. What I know is that I have 2 onboard 1Gb ports and one 2-port 82599em and one 4-port intel 1Gb NIC.
> I have installed zc license for p1p1. The management port is em1.
> the ifconfig and ethtool info are listed here:
>
> [root@r510 ~]# ethtool -i p1p1
> driver: ixgbe
> version: 5.5.3
> firmware-version: 0x2b2c0001
> expansion-rom-version:
> bus-info: 0000:08:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
>
> [root@r510 ~]# ethtool -i p1p2
> driver: ixgbe
> version: 5.5.3
> firmware-version: 0x2b2c0001
> expansion-rom-version:
> bus-info: 0000:08:00.1
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
>
> [root@r510 ~]# ethtool -i em1
> driver: bnx2
> version: 2.2.6
> firmware-version: 6.0.1 bc 5.2.3 NCSI 2.0.10
> expansion-rom-version:
> bus-info: 0000:01:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: no
>
>
> [root@r510 ~]# ifconfig
> em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.66.101 netmask 255.255.255.0 broadcast 192.168.66.255
> inet6 fe80::2001:70e3:7246:b725 prefixlen 64 scopeid 0x20<link>
> ether 84:2b:2b:78:8a:62 txqueuelen 1000 (Ethernet)
> RX packets 26069 bytes 3177036 (3.0 MiB)
> RX errors 0 dropped 1 overruns 0 frame 0
> TX packets 5945 bytes 1443645 (1.3 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 84:2b:2b:78:8a:63 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1000 (Local Loopback)
> RX packets 19 bytes 1737 (1.6 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 19 bytes 1737 (1.6 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> p1p1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
> ether 48:f8:db:7e:da:5c txqueuelen 1000 (Ethernet)
> RX packets 6322614433 bytes 3091202586919 (2.8 TiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 869 bytes 147082 (143.6 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xdd300000-dd380000
>
> p1p2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 48:f8:db:7e:da:5d txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xdd380000-dd400000
>
> p2p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> ether 00:1b:21:b0:5c:a8 txqueuelen 1000 (Ethernet)
> RX packets 287 bytes 98154 (95.8 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xdebc0000-debdffff
>
> p2p2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:b0:5c:a9 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xdebe0000-debfffff
>
> p2p3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:b0:5c:ac txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xddbc0000-ddbdffff
>
> p2p4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:b0:5c:ad txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device memory 0xddbe0000-ddbfffff
>
> On Tue, Jan 21, 2020 at 6:08 PM Alfredo Cardigliano <cardigliano@ntop.org <mailto:cardigliano@ntop.org>> wrote:
> Hi Wang
> please provide:
>
> 1. lspci | grep Eth
> 2. ifconfig
> 3. ethtool -i {p1p1,p1p2,<management>}
>
> Thank you
> Alfredo
>
>> On 21 Jan 2020, at 08:44, Wang <cnwangyong@gmail.com <mailto:cnwangyong@gmail.com>> wrote:
>>
>> hi,
>> I have 2 capture interfaces(p1p1 and p1p2, 10Gb) and 1 management interface in my server. After I have setup the number of rss queue of p1p1 with 'pf_ringcfg --configure-driver ixgbe --rss-queues 2', I tried to start up two pfcount to do some test: 'pfcount -i zc:p1p1@0' and 'pfcount -i zc:p1p1@1'. After the second pfcount started, I lost my ssh session with my server and I cannot ping it neither. Everything came back after several minutes waiting without doing anything.
>> My pfring version is 7.5.0, and Is there anything wrong with it?
>>
>> thanks,
>> wang
>> _______________________________________________
>> Ntop-misc mailing list
>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>_______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc