Mailing List Archive

NT_InfoOpen() failed: NT Service is not started
Recently when I tried to configure an additional interface I got the
following error:

[zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
not started"
NT_Init() failed: NT Service is not started
[zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
not started"
NT_InfoOpen() failed: NT Service is not started
13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
error [Socket operation on non-socket] Please check that zc:<xxx> is
up and not already used

I get this error when running:
sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p

which works perfectly fine for 4 other interfaces. The only
difference being that each interface gets assigned its own clusterid.

The box is Supermicro with XL170 NICs running Ubuntu 14.04.

Any thoughts on how I might approach this?

Cheers.
_______________________________________________
Ntop-misc mailing list
Ntop-misc@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Jeremy
are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)

Cheers Luca

> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>
> Recently when I tried to configure an additional interface I got the
> following error:
>
> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
> not started"
> NT_Init() failed: NT Service is not started
> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
> not started"
> NT_InfoOpen() failed: NT Service is not started
> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
> error [Socket operation on non-socket] Please check that zc:<xxx> is
> up and not already used
>
> I get this error when running:
> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>
> which works perfectly fine for 4 other interfaces. The only
> difference being that each interface gets assigned its own clusterid.
>
> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>
> Any thoughts on how I might approach this?
>
> Cheers.
> _______________________________________________
> 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: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
The NICs are all XL710 and not Napatech.

On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
> Jeremy
> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>
> Cheers Luca
>
>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>
>> Recently when I tried to configure an additional interface I got the
>> following error:
>>
>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>> not started"
>> NT_Init() failed: NT Service is not started
>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>> not started"
>> NT_InfoOpen() failed: NT Service is not started
>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>> up and not already used
>>
>> I get this error when running:
>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>
>> which works perfectly fine for 4 other interfaces. The only
>> difference being that each interface gets assigned its own clusterid.
>>
>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>
>> Any thoughts on how I might approach this?
>>
>> Cheers.
>> _______________________________________________
>> 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
_______________________________________________
Ntop-misc mailing list
Ntop-misc@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Hi Jeremy
please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.

Thank you
Alfredo

> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>
> The NICs are all XL710 and not Napatech.
>
> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>> Jeremy
>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>
>> Cheers Luca
>>
>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>
>>> Recently when I tried to configure an additional interface I got the
>>> following error:
>>>
>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>> not started"
>>> NT_Init() failed: NT Service is not started
>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>> not started"
>>> NT_InfoOpen() failed: NT Service is not started
>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>> up and not already used
>>>
>>> I get this error when running:
>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>
>>> which works perfectly fine for 4 other interfaces. The only
>>> difference being that each interface gets assigned its own clusterid.
>>>
>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>
>>> Any thoughts on how I might approach this?
>>>
>>> Cheers.
>>> _______________________________________________
>>> 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
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Here is the output of “cat /proc/net/pf_ring/dev/*/info”

Name: <site>_inet_<isp1>_1
Index: 21
Address: 0C:C4:7A:BC:A3:C8
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096
Name: <site>_inet_<isp2>_1
Index: 23
Address: 0C:C4:7A:BC:A3:CA
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096
Name: <site>_inet_<isp3>_1
Index: 33
Address: 0C:C4:7A:BC:9C:84
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096
Name: <site>_inet_<isp4>_1
Index: 24
Address: 0C:C4:7A:BC:A3:CB
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096
Name: <site>_ptp_<isp2>_1
Index: 22
Address: 0C:C4:7A:BC:A3:C9
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096
Name: bond0
Index: 20
Address: 00:00:00:00:00:00
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 16
# Used RX Queues: 16
Name: cap10
Index: 27
Address: 0C:C4:7A:BC:A3:C6
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap11
Index: 28
Address: 0C:C4:7A:BC:A3:C7
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap12
Index: 29
Address: 0C:C4:7A:BC:9C:90
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap13
Index: 30
Address: 0C:C4:7A:BC:9C:91
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap14
Index: 31
Address: 0C:C4:7A:BC:9C:92
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap15
Index: 32
Address: 0C:C4:7A:BC:9C:93
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap5
Index: 34
Address: 0C:C4:7A:BC:9C:85
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap6
Index: 35
Address: 0C:C4:7A:BC:9C:86
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap7
Index: 36
Address: 0C:C4:7A:BC:9C:87
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap8
Index: 25
Address: 0C:C4:7A:BC:A3:C4
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: cap9
Index: 26
Address: 0C:C4:7A:BC:A3:C5
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 1
# Used RX Queues: 1
Name: eth0
Index: 3
Address: 0C:C4:7A:6E:7C:3E
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 20
# Used RX Queues: 20
Name: eth1
Index: 5
Address: 0C:C4:7A:6E:7C:3F
Polling Mode: NAPI
Type: Ethernet
Family: Standard NIC
# Bound Sockets: 0
Max # TX Queues: 20
# Used RX Queues: 20


On Thu, Jul 14, 2016 at 9:00 PM, Alfredo Cardigliano
<cardigliano@ntop.org> wrote:
> Hi Jeremy
> please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.
>
> Thank you
> Alfredo
>
>> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>
>> The NICs are all XL710 and not Napatech.
>>
>> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>>> Jeremy
>>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>>
>>> Cheers Luca
>>>
>>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>
>>>> Recently when I tried to configure an additional interface I got the
>>>> following error:
>>>>
>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>> not started"
>>>> NT_Init() failed: NT Service is not started
>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>> not started"
>>>> NT_InfoOpen() failed: NT Service is not started
>>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>>> up and not already used
>>>>
>>>> I get this error when running:
>>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>>
>>>> which works perfectly fine for 4 other interfaces. The only
>>>> difference being that each interface gets assigned its own clusterid.
>>>>
>>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>>
>>>> Any thoughts on how I might approach this?
>>>>
>>>> Cheers.
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
_______________________________________________
Ntop-misc mailing list
Ntop-misc@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Which one is not working?

Alfredo

> On 14 Jul 2016, at 16:37, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>
> Here is the output of “cat /proc/net/pf_ring/dev/*/info”
>
> Name: <site>_inet_<isp1>_1
> Index: 21
> Address: 0C:C4:7A:BC:A3:C8
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
> Name: <site>_inet_<isp2>_1
> Index: 23
> Address: 0C:C4:7A:BC:A3:CA
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
> Name: <site>_inet_<isp3>_1
> Index: 33
> Address: 0C:C4:7A:BC:9C:84
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
> Name: <site>_inet_<isp4>_1
> Index: 24
> Address: 0C:C4:7A:BC:A3:CB
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
> Name: <site>_ptp_<isp2>_1
> Index: 22
> Address: 0C:C4:7A:BC:A3:C9
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
> Name: bond0
> Index: 20
> Address: 00:00:00:00:00:00
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 16
> # Used RX Queues: 16
> Name: cap10
> Index: 27
> Address: 0C:C4:7A:BC:A3:C6
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap11
> Index: 28
> Address: 0C:C4:7A:BC:A3:C7
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap12
> Index: 29
> Address: 0C:C4:7A:BC:9C:90
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap13
> Index: 30
> Address: 0C:C4:7A:BC:9C:91
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap14
> Index: 31
> Address: 0C:C4:7A:BC:9C:92
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap15
> Index: 32
> Address: 0C:C4:7A:BC:9C:93
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap5
> Index: 34
> Address: 0C:C4:7A:BC:9C:85
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap6
> Index: 35
> Address: 0C:C4:7A:BC:9C:86
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap7
> Index: 36
> Address: 0C:C4:7A:BC:9C:87
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap8
> Index: 25
> Address: 0C:C4:7A:BC:A3:C4
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: cap9
> Index: 26
> Address: 0C:C4:7A:BC:A3:C5
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 1
> # Used RX Queues: 1
> Name: eth0
> Index: 3
> Address: 0C:C4:7A:6E:7C:3E
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 20
> # Used RX Queues: 20
> Name: eth1
> Index: 5
> Address: 0C:C4:7A:6E:7C:3F
> Polling Mode: NAPI
> Type: Ethernet
> Family: Standard NIC
> # Bound Sockets: 0
> Max # TX Queues: 20
> # Used RX Queues: 20
>
>
> On Thu, Jul 14, 2016 at 9:00 PM, Alfredo Cardigliano
> <cardigliano@ntop.org> wrote:
>> Hi Jeremy
>> please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.
>>
>> Thank you
>> Alfredo
>>
>>> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>
>>> The NICs are all XL710 and not Napatech.
>>>
>>> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>>>> Jeremy
>>>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>>>
>>>> Cheers Luca
>>>>
>>>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>
>>>>> Recently when I tried to configure an additional interface I got the
>>>>> following error:
>>>>>
>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>> not started"
>>>>> NT_Init() failed: NT Service is not started
>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>> not started"
>>>>> NT_InfoOpen() failed: NT Service is not started
>>>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>>>> up and not already used
>>>>>
>>>>> I get this error when running:
>>>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>>>
>>>>> which works perfectly fine for 4 other interfaces. The only
>>>>> difference being that each interface gets assigned its own clusterid.
>>>>>
>>>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>>>
>>>>> Any thoughts on how I might approach this?
>>>>>
>>>>> Cheers.
>>>>> _______________________________________________
>>>>> 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
>>> _______________________________________________
>>> 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
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Name: <site>_inet_<isp3>_1
Index: 33
Address: 0C:C4:7A:BC:9C:84
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel i40e
Max # TX Queues: 1
# Used RX Queues: 1
Num RX Slots: 4096
Num TX Slots: 4096

On Thu, Jul 14, 2016 at 10:42 PM, Alfredo Cardigliano
<cardigliano@ntop.org> wrote:
> Which one is not working?
>
> Alfredo
>
>> On 14 Jul 2016, at 16:37, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>
>> Here is the output of “cat /proc/net/pf_ring/dev/*/info”
>>
>> Name: <site>_inet_<isp1>_1
>> Index: 21
>> Address: 0C:C4:7A:BC:A3:C8
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>> Name: <site>_inet_<isp2>_1
>> Index: 23
>> Address: 0C:C4:7A:BC:A3:CA
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>> Name: <site>_inet_<isp3>_1
>> Index: 33
>> Address: 0C:C4:7A:BC:9C:84
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>> Name: <site>_inet_<isp4>_1
>> Index: 24
>> Address: 0C:C4:7A:BC:A3:CB
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>> Name: <site>_ptp_<isp2>_1
>> Index: 22
>> Address: 0C:C4:7A:BC:A3:C9
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>> Name: bond0
>> Index: 20
>> Address: 00:00:00:00:00:00
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 16
>> # Used RX Queues: 16
>> Name: cap10
>> Index: 27
>> Address: 0C:C4:7A:BC:A3:C6
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap11
>> Index: 28
>> Address: 0C:C4:7A:BC:A3:C7
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap12
>> Index: 29
>> Address: 0C:C4:7A:BC:9C:90
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap13
>> Index: 30
>> Address: 0C:C4:7A:BC:9C:91
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap14
>> Index: 31
>> Address: 0C:C4:7A:BC:9C:92
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap15
>> Index: 32
>> Address: 0C:C4:7A:BC:9C:93
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap5
>> Index: 34
>> Address: 0C:C4:7A:BC:9C:85
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap6
>> Index: 35
>> Address: 0C:C4:7A:BC:9C:86
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap7
>> Index: 36
>> Address: 0C:C4:7A:BC:9C:87
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap8
>> Index: 25
>> Address: 0C:C4:7A:BC:A3:C4
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: cap9
>> Index: 26
>> Address: 0C:C4:7A:BC:A3:C5
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Name: eth0
>> Index: 3
>> Address: 0C:C4:7A:6E:7C:3E
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 20
>> # Used RX Queues: 20
>> Name: eth1
>> Index: 5
>> Address: 0C:C4:7A:6E:7C:3F
>> Polling Mode: NAPI
>> Type: Ethernet
>> Family: Standard NIC
>> # Bound Sockets: 0
>> Max # TX Queues: 20
>> # Used RX Queues: 20
>>
>>
>> On Thu, Jul 14, 2016 at 9:00 PM, Alfredo Cardigliano
>> <cardigliano@ntop.org> wrote:
>>> Hi Jeremy
>>> please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.
>>>
>>> Thank you
>>> Alfredo
>>>
>>>> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>
>>>> The NICs are all XL710 and not Napatech.
>>>>
>>>> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>>>>> Jeremy
>>>>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>>>>
>>>>> Cheers Luca
>>>>>
>>>>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>>
>>>>>> Recently when I tried to configure an additional interface I got the
>>>>>> following error:
>>>>>>
>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>> not started"
>>>>>> NT_Init() failed: NT Service is not started
>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>> not started"
>>>>>> NT_InfoOpen() failed: NT Service is not started
>>>>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>>>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>>>>> up and not already used
>>>>>>
>>>>>> I get this error when running:
>>>>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>>>>
>>>>>> which works perfectly fine for 4 other interfaces. The only
>>>>>> difference being that each interface gets assigned its own clusterid.
>>>>>>
>>>>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>>>>
>>>>>> Any thoughts on how I might approach this?
>>>>>>
>>>>>> Cheers.
>>>>>> _______________________________________________
>>>>>> 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
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
_______________________________________________
Ntop-misc mailing list
Ntop-misc@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
Hi Jeremy
I made some fix to the dev code in github, rebuilding new packages right now.
Please check if the problem still persistes and let us know.

Thank you
Alfredo

> On 14 Jul 2016, at 17:25, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>
> Name: <site>_inet_<isp3>_1
> Index: 33
> Address: 0C:C4:7A:BC:9C:84
> Polling Mode: NAPI/ZC
> Type: Ethernet
> Family: Intel i40e
> Max # TX Queues: 1
> # Used RX Queues: 1
> Num RX Slots: 4096
> Num TX Slots: 4096
>
> On Thu, Jul 14, 2016 at 10:42 PM, Alfredo Cardigliano
> <cardigliano@ntop.org> wrote:
>> Which one is not working?
>>
>> Alfredo
>>
>>> On 14 Jul 2016, at 16:37, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>
>>> Here is the output of “cat /proc/net/pf_ring/dev/*/info”
>>>
>>> Name: <site>_inet_<isp1>_1
>>> Index: 21
>>> Address: 0C:C4:7A:BC:A3:C8
>>> Polling Mode: NAPI/ZC
>>> Type: Ethernet
>>> Family: Intel i40e
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Num RX Slots: 4096
>>> Num TX Slots: 4096
>>> Name: <site>_inet_<isp2>_1
>>> Index: 23
>>> Address: 0C:C4:7A:BC:A3:CA
>>> Polling Mode: NAPI/ZC
>>> Type: Ethernet
>>> Family: Intel i40e
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Num RX Slots: 4096
>>> Num TX Slots: 4096
>>> Name: <site>_inet_<isp3>_1
>>> Index: 33
>>> Address: 0C:C4:7A:BC:9C:84
>>> Polling Mode: NAPI/ZC
>>> Type: Ethernet
>>> Family: Intel i40e
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Num RX Slots: 4096
>>> Num TX Slots: 4096
>>> Name: <site>_inet_<isp4>_1
>>> Index: 24
>>> Address: 0C:C4:7A:BC:A3:CB
>>> Polling Mode: NAPI/ZC
>>> Type: Ethernet
>>> Family: Intel i40e
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Num RX Slots: 4096
>>> Num TX Slots: 4096
>>> Name: <site>_ptp_<isp2>_1
>>> Index: 22
>>> Address: 0C:C4:7A:BC:A3:C9
>>> Polling Mode: NAPI/ZC
>>> Type: Ethernet
>>> Family: Intel i40e
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Num RX Slots: 4096
>>> Num TX Slots: 4096
>>> Name: bond0
>>> Index: 20
>>> Address: 00:00:00:00:00:00
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 16
>>> # Used RX Queues: 16
>>> Name: cap10
>>> Index: 27
>>> Address: 0C:C4:7A:BC:A3:C6
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap11
>>> Index: 28
>>> Address: 0C:C4:7A:BC:A3:C7
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap12
>>> Index: 29
>>> Address: 0C:C4:7A:BC:9C:90
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap13
>>> Index: 30
>>> Address: 0C:C4:7A:BC:9C:91
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap14
>>> Index: 31
>>> Address: 0C:C4:7A:BC:9C:92
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap15
>>> Index: 32
>>> Address: 0C:C4:7A:BC:9C:93
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap5
>>> Index: 34
>>> Address: 0C:C4:7A:BC:9C:85
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap6
>>> Index: 35
>>> Address: 0C:C4:7A:BC:9C:86
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap7
>>> Index: 36
>>> Address: 0C:C4:7A:BC:9C:87
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap8
>>> Index: 25
>>> Address: 0C:C4:7A:BC:A3:C4
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: cap9
>>> Index: 26
>>> Address: 0C:C4:7A:BC:A3:C5
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 1
>>> # Used RX Queues: 1
>>> Name: eth0
>>> Index: 3
>>> Address: 0C:C4:7A:6E:7C:3E
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 20
>>> # Used RX Queues: 20
>>> Name: eth1
>>> Index: 5
>>> Address: 0C:C4:7A:6E:7C:3F
>>> Polling Mode: NAPI
>>> Type: Ethernet
>>> Family: Standard NIC
>>> # Bound Sockets: 0
>>> Max # TX Queues: 20
>>> # Used RX Queues: 20
>>>
>>>
>>> On Thu, Jul 14, 2016 at 9:00 PM, Alfredo Cardigliano
>>> <cardigliano@ntop.org> wrote:
>>>> Hi Jeremy
>>>> please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.
>>>>
>>>> Thank you
>>>> Alfredo
>>>>
>>>>> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>
>>>>> The NICs are all XL710 and not Napatech.
>>>>>
>>>>> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>>>>>> Jeremy
>>>>>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>>>>>
>>>>>> Cheers Luca
>>>>>>
>>>>>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>>>
>>>>>>> Recently when I tried to configure an additional interface I got the
>>>>>>> following error:
>>>>>>>
>>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>>> not started"
>>>>>>> NT_Init() failed: NT Service is not started
>>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>>> not started"
>>>>>>> NT_InfoOpen() failed: NT Service is not started
>>>>>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>>>>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>>>>>> up and not already used
>>>>>>>
>>>>>>> I get this error when running:
>>>>>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>>>>>
>>>>>>> which works perfectly fine for 4 other interfaces. The only
>>>>>>> difference being that each interface gets assigned its own clusterid.
>>>>>>>
>>>>>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>>>>>
>>>>>>> Any thoughts on how I might approach this?
>>>>>>>
>>>>>>> Cheers.
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>> _______________________________________________
>>>>> 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
>>> _______________________________________________
>>> 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
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: NT_InfoOpen() failed: NT Service is not started [ In reply to ]
That seemed to fix it. Thanks.

On Fri, Jul 15, 2016 at 12:17 AM, Alfredo Cardigliano
<cardigliano@ntop.org> wrote:
> Hi Jeremy
> I made some fix to the dev code in github, rebuilding new packages right now.
> Please check if the problem still persistes and let us know.
>
> Thank you
> Alfredo
>
>> On 14 Jul 2016, at 17:25, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>
>> Name: <site>_inet_<isp3>_1
>> Index: 33
>> Address: 0C:C4:7A:BC:9C:84
>> Polling Mode: NAPI/ZC
>> Type: Ethernet
>> Family: Intel i40e
>> Max # TX Queues: 1
>> # Used RX Queues: 1
>> Num RX Slots: 4096
>> Num TX Slots: 4096
>>
>> On Thu, Jul 14, 2016 at 10:42 PM, Alfredo Cardigliano
>> <cardigliano@ntop.org> wrote:
>>> Which one is not working?
>>>
>>> Alfredo
>>>
>>>> On 14 Jul 2016, at 16:37, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>
>>>> Here is the output of “cat /proc/net/pf_ring/dev/*/info”
>>>>
>>>> Name: <site>_inet_<isp1>_1
>>>> Index: 21
>>>> Address: 0C:C4:7A:BC:A3:C8
>>>> Polling Mode: NAPI/ZC
>>>> Type: Ethernet
>>>> Family: Intel i40e
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Num RX Slots: 4096
>>>> Num TX Slots: 4096
>>>> Name: <site>_inet_<isp2>_1
>>>> Index: 23
>>>> Address: 0C:C4:7A:BC:A3:CA
>>>> Polling Mode: NAPI/ZC
>>>> Type: Ethernet
>>>> Family: Intel i40e
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Num RX Slots: 4096
>>>> Num TX Slots: 4096
>>>> Name: <site>_inet_<isp3>_1
>>>> Index: 33
>>>> Address: 0C:C4:7A:BC:9C:84
>>>> Polling Mode: NAPI/ZC
>>>> Type: Ethernet
>>>> Family: Intel i40e
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Num RX Slots: 4096
>>>> Num TX Slots: 4096
>>>> Name: <site>_inet_<isp4>_1
>>>> Index: 24
>>>> Address: 0C:C4:7A:BC:A3:CB
>>>> Polling Mode: NAPI/ZC
>>>> Type: Ethernet
>>>> Family: Intel i40e
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Num RX Slots: 4096
>>>> Num TX Slots: 4096
>>>> Name: <site>_ptp_<isp2>_1
>>>> Index: 22
>>>> Address: 0C:C4:7A:BC:A3:C9
>>>> Polling Mode: NAPI/ZC
>>>> Type: Ethernet
>>>> Family: Intel i40e
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Num RX Slots: 4096
>>>> Num TX Slots: 4096
>>>> Name: bond0
>>>> Index: 20
>>>> Address: 00:00:00:00:00:00
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 16
>>>> # Used RX Queues: 16
>>>> Name: cap10
>>>> Index: 27
>>>> Address: 0C:C4:7A:BC:A3:C6
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap11
>>>> Index: 28
>>>> Address: 0C:C4:7A:BC:A3:C7
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap12
>>>> Index: 29
>>>> Address: 0C:C4:7A:BC:9C:90
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap13
>>>> Index: 30
>>>> Address: 0C:C4:7A:BC:9C:91
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap14
>>>> Index: 31
>>>> Address: 0C:C4:7A:BC:9C:92
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap15
>>>> Index: 32
>>>> Address: 0C:C4:7A:BC:9C:93
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap5
>>>> Index: 34
>>>> Address: 0C:C4:7A:BC:9C:85
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap6
>>>> Index: 35
>>>> Address: 0C:C4:7A:BC:9C:86
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap7
>>>> Index: 36
>>>> Address: 0C:C4:7A:BC:9C:87
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap8
>>>> Index: 25
>>>> Address: 0C:C4:7A:BC:A3:C4
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: cap9
>>>> Index: 26
>>>> Address: 0C:C4:7A:BC:A3:C5
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 1
>>>> # Used RX Queues: 1
>>>> Name: eth0
>>>> Index: 3
>>>> Address: 0C:C4:7A:6E:7C:3E
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 20
>>>> # Used RX Queues: 20
>>>> Name: eth1
>>>> Index: 5
>>>> Address: 0C:C4:7A:6E:7C:3F
>>>> Polling Mode: NAPI
>>>> Type: Ethernet
>>>> Family: Standard NIC
>>>> # Bound Sockets: 0
>>>> Max # TX Queues: 20
>>>> # Used RX Queues: 20
>>>>
>>>>
>>>> On Thu, Jul 14, 2016 at 9:00 PM, Alfredo Cardigliano
>>>> <cardigliano@ntop.org> wrote:
>>>>> Hi Jeremy
>>>>> please provide all interface names and the output of “cat /proc/net/pf_ring/dev/ethX/info” for all the interfaces.
>>>>>
>>>>> Thank you
>>>>> Alfredo
>>>>>
>>>>>> On 14 Jul 2016, at 14:31, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>>
>>>>>> The NICs are all XL710 and not Napatech.
>>>>>>
>>>>>> On Thu, Jul 14, 2016 at 1:43 AM, Luca Deri <deri@ntop.org> wrote:
>>>>>>> Jeremy
>>>>>>> are you using Napatech NICs perhaps? If so, you need to start the napatech services (/opt/napatech….)
>>>>>>>
>>>>>>> Cheers Luca
>>>>>>>
>>>>>>>> On 13 Jul 2016, at 19:27, Jeremy Ashton <jeremy.ashton@shopify.com> wrote:
>>>>>>>>
>>>>>>>> Recently when I tried to configure an additional interface I got the
>>>>>>>> following error:
>>>>>>>>
>>>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>>>> not started"
>>>>>>>> NT_Init() failed: NT Service is not started
>>>>>>>> [zbalance_ipc] NT_ExplainError: Code=0x20000013 Error="NT Service is
>>>>>>>> not started"
>>>>>>>> NT_InfoOpen() failed: NT Service is not started
>>>>>>>> 13/Jul/2016 17:21:25 [zbalance_ipc.c:566] ERROR: pfring_zc_open_device
>>>>>>>> error [Socket operation on non-socket] Please check that zc:<xxx> is
>>>>>>>> up and not already used
>>>>>>>>
>>>>>>>> I get this error when running:
>>>>>>>> sudo /usr/local/bin/zbalance_ipc -i zc:<xxx> -c 50 -n 2 -m 2 -g 0 -p
>>>>>>>>
>>>>>>>> which works perfectly fine for 4 other interfaces. The only
>>>>>>>> difference being that each interface gets assigned its own clusterid.
>>>>>>>>
>>>>>>>> The box is Supermicro with XL170 NICs running Ubuntu 14.04.
>>>>>>>>
>>>>>>>> Any thoughts on how I might approach this?
>>>>>>>>
>>>>>>>> Cheers.
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>> _______________________________________________
>>>>>> 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
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
_______________________________________________
Ntop-misc mailing list
Ntop-misc@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop-misc