There are no rrd files generated by netstream coming from Huawei router

[Tekila]

Hi,

Could someone advise on further steps how to launch AS-STATS with Huawei router?

The flow is coming from the Huawei router to the server, but there are no rrd files:

tcpdump -nnpi any port 9000 -vv
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
08:25:52.837079 IP (tos 0x0, ttl 254, id 11383, offset 0, flags [none], proto UDP (17), length 1444)
X.X.X.X.40000 > Y.Y.Y.Y.9000: [no cksum] UDP, length 1416

From Cisco router flows are also received and RRD files are created:

08:27:46.969196 IP (tos 0x0, ttl 254, id 7276, offset 0, flags [none], proto UDP (17), length 84)
Z.Z.Z.Z.56848 > Y.Y.Y.Y.9000: [udp sum ok] UDP, length 56

Cisco router config:

ip flow-export source Loopback0
ip flow-export version 5 origin-as
ip flow-aggregation cache as
cache entries 16384
cache timeout active 3
export destination Y.Y.Y.Y 9000
enabled

interface X/y
ip flow ingress

Huawei router config:

slot 3
ip netstream sampler to slot self

ip netstream timeout active 1
ip netstream timeout inactive 15
ip netstream export version 5 origin-as
ip netstream sampler random-packets 100 inbound
ip netstream sampler random-packets 100 outbound
ip netstream export source Z.Z.Z.Z
ip netstream export host Y.Y.Y.Y 9000
ip netstream aggregation as
enable
template timeout-rate 2
ip netstream export source Z.Z.Z.Z
ip netstream export host Y.Y.Y.Y 9000

interface X/y
ip netstream inbound

[Tekila]

There was an issue with inputint index.

[Felipe Kopp Klasen]

Em sexta-feira, 1 de junho de 2018 05:52:04 UTC-3, Tekila escreveu:
> There was an issue with inputint index.

Hi Tekila!

Do you recall what was the issue?
I'm having the same problem :(

[Leslye andrade]

Dear, I have same problem with huawei ne40, anyone have the solution?

thanks

[Felipe Kopp Klasen]

Hi!

The ifindex exported by the netstream is not the same as the one used by the SNMP.

There's more information about this in the link below:

https://support.huawei.com/enterprise/en/knowledge/EKB1000193522

Regards;

--
You received this message because you are subscribed to the Google Groups "AS-Stats users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to as-stats-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/as-stats-users/9604a7fd-a7e3-4c3f-a921-e441d9dc68db%40googlegroups.com.

[Leslye andrade]

Thanks for the reply, the link will be very useful, the problem that occurs is that not even with the wrong index I receive the stream, the problem I have is that I do not receive any stream, below the config and the result of the capture:

system

ip netstream export version 9

ip netstream export index-switch 32

ip netstream as-mode 32

ip netstream timeout active 1

ip netstream timeout inactive 15

ip netstream tcp-flag enable

ip netstream export template timeout-rate 1

ip netstream export template option sampler

ip netstream export template option timeout-rate 1

ip netstream export template option refresh-rate 30

ip netstream export template option application-label

ip netstream sampler fix-packets 400 inbound

ip netstream sampler fix-packets 400 outbound

ipv6 netstream export version 9

ipv6 netstream as-mode 32

ipv6 netstream timeout active 1

ipv6 netstream timeout inactive 15

ipv6 netstream tcp-flag enable

ipv6 netstream export template timeout-rate 1

ipv6 netstream export template option sampler

ipv6 netstream export template option timeout-rate 1

ipv6 netstream export template option refresh-rate 30

ipv6 netstream sampler fix-packets 400 inbound

ipv6 netstream sampler fix-packets 400 outbound

ip netstream monitor NFDUMP

 ip netstream export source xxx.xxx.xxx.xxx

 ip netstream export host xxx.xxx.xxx.xxx 2055 version 9

slot 3

interface GigabitEthernet0/3/3.10

 ip netstream inbound

 ip netstream outbound

 ip netstream monitor NFDUMP inbound

 ip netstream monitor NFDUMP outbound

interface GigabitEthernet0/3/3.34

 ip netstream inbound

 ip netstream outbound

 ip netstream monitor NFDUMP inbound

 ip netstream monitor NFDUMP outbound

slot

 slot 3:ip netstream sampler to slot self

 slot 3:ipv6 netstream sampler to slot self

 slot 3:ip netstream export sequence-mode flow

nfcapd -E -p 2055 -l / tmp / nfcap-test
nfdump -r /tmp/nfcap-test/nfcapd.202001072123 -s srcip / bytes
nfdump -r /tmp/nfcap-test/nfcapd.202001071857 -s srcip / bytes
No matched flows

root@as-stats:~# tcpdump -n dst port 2055 -vv
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
09:45:50.680342 IP (tos 0x0, ttl 255, id 34553, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:50.820350 IP (tos 0x0, ttl 255, id 34554, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:50.910376 IP (tos 0x0, ttl 255, id 34555, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:50.970354 IP (tos 0x0, ttl 255, id 34556, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.030330 IP (tos 0x0, ttl 255, id 34557, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.600316 IP (tos 0x0, ttl 255, id 34558, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.720324 IP (tos 0x0, ttl 255, id 34559, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.870329 IP (tos 0x0, ttl 255, id 34560, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.950329 IP (tos 0x0, ttl 255, id 34561, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:51.980346 IP (tos 0x0, ttl 255, id 34562, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432
09:45:52.060345 IP (tos 0x0, ttl 255, id 34563, offset 0, flags [none], proto UDP (17), length 1460)
yyy.yyy.yyy.yyy.40000 > yyy.yyy.yyy.yyy.2055: [no cksum] UDP, length 1432

I am thinking that is the connectivity between the source and the destination of the collector because they are in different subnets, any tips for not getting the flow on the server correctly?

thanks

Em quarta-feira, 8 de janeiro de 2020 10:23:31 UTC-3, Felipe Kopp Klasen escreveu:

Hi!

The ifindex exported by the netstream is not the same as the one used by the SNMP.

There's more information about this in the link below:

https://support.huawei.com/enterprise/en/knowledge/EKB1000193522

Regards;

On Sun, Jan 5, 2020 at 7:23 PM Leslye andrade <laislye...@gmail.com> wrote:

Dear, I have same problem with huawei ne40, anyone have the solution?

thanks

Em sexta-feira, 22 de março de 2019 08:45:13 UTC-3, Felipe Kopp Klasen escreveu:

Em sexta-feira, 1 de junho de 2018 05:52:04 UTC-3, Tekila  escreveu:
> There was an issue with inputint index.

Hi Tekila!

Do you recall what was the issue?
I'm having the same problem :(

--
You received this message because you are subscribed to the Google Groups "AS-Stats users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to as-stat...@googlegroups.com.