Mailing List Archive

It's a UDP fragment ( offset 1760 ). If the port was on the initial
fragment, then "nothing wrong" (FSVO), if there was no initial fragment
with the port then "it's just broken"?
(Oh good, something else to have to support UDP frags for).

I guess this MX has more <something> than the other? interfaces/firewall
filters/counters maybe?

payload-size bytes (Optional) —Specify the maximum size of exported packets.
NOTE

The payload-size option is supported only on the following sensors:

-

/junos/system/linecard/interface/
-

/junos/system/linecard/interface/logical/usage/
-

/junos/system/linecard/firewall/

Default: 5000 bytes.

Range: 2000 through 9192 bytes.
NOTE

Junos Telemetry Interface does not export packets larger than 9192 bytes.

On Fri, 15 Feb 2019 at 13:06, Martyniak Lukasz <lmartyniak@man.szczecin.pl>
wrote:

> Hi All
>
> I have a question in junos telemetry. I have some MX telemetry streams
> with does not include the ports number into UPP packages
> Other MX is working fine (both have same hardware, software version
> 16.2R2.8 - mx104 and analytics config)
> Do any of you have similar issues ? Any know solution ?
>
> tcpdump on the collector server :
>
> from MX1 :
> 13:59:42.663324 IP (tos 0xc0, ttl 252, id 1532, offset 0, flags [none],
> proto UDP (17), length 1232)
> 10.200.10.3.1000 > 10.200.10.10.50000: [no cksum] UDP, length 1204
>
> from MX2:
>
> 13:46:48.141313 IP (tos 0xc0, ttl 254, id 1509, offset 1760, flags [none],
> proto UDP (17), length 1309)
> 10.200.10.2 > 10.200.10.10: ip-proto-17
>
> Best
> Lukasz
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp