14 10:21:44 AM
Subject: [j-nsp] MX ping - ToS overrided
Hi,
I'm experiencing issues when initating ToS ping from MX devices. The specified
ToS argument just seems to be overrided to dec 192 when leaving the interface.
I verified this with the traffic monitor on the egress interface:
user@
You are monitoring ToS in ICMP ECHO REPLY, not request.
And that can be set/overridden anywhere by QoS policies, i.e.
- on Google DNS server 8.8.8.8 itself
- on any transit network
HTH
Thanks
Alex
On 22/01/2014 14:21, Arash Alizadeh wrote:
Hi,
I'm experiencing issues when initating ToS ping f
; To: david@orange.com; aras...@hotmail.se; juniper-nsp@puck.nether.net
> Date: Wed, 22 Jan 2014 15:40:50 +0100
> Subject: RE: [j-nsp] MX ping - ToS overrided
>
> I meant host-outbound-traffic ;)
>
>
> David Roy
> IP/MPLS NOC engineer - Orange France
> Ph. : +33 2 99 87 64 7
-boun...@puck.nether.net] De la part de
david@orange.com
Envoyé : mercredi 22 janvier 2014 15:39
À : 'Arash Alizadeh'; juniper-nsp@puck.nether.net
Objet : Re: [j-nsp] MX ping - ToS overrided
Not the case with 12.3R4 for me :
ping 8.8.8.8 tos 96
15:37:03.950763 Out IP (tos 0x60, tt
nsp-boun...@puck.nether.net] De la part de
Arash Alizadeh
Envoyé : mercredi 22 janvier 2014 15:22
À : juniper-nsp@puck.nether.net
Objet : [j-nsp] MX ping - ToS overrided
Hi,
I'm experiencing issues when initating ToS ping from MX devices. The specified
ToS argument just seems to be overrided to dec 192 whe
Hi,
I'm experiencing issues when initating ToS ping from MX devices. The specified
ToS argument just seems to be overrided to dec 192 when leaving the interface.
I verified this with the traffic monitor on the egress interface:
user@node> ping 8.8.8.8 tos 96
64 bytes from 8.8.8.8: icmp_seq=
6 matches
Mail list logo