[j-nsp] per-flow load balancing hash and ICMP traffic
Mark Miklic
mmiklic at gmail.com
Thu Dec 7 17:43:14 EST 2006
Ok, problem solved (thanks Ray;).
Seems like the source-port for layer-4 hash equals to datagram id for ICMP.
Really interesting...
Mark
2006/12/7, Mark Miklic <mmiklic at gmail.com>:
>
> Actually,
>
> it is enough if I exclude source-port from the hash. This is even more
> confusing... I thought mtr had nothing to do with layer-4 source ports and
> such, being ICMP. Is perhaps the sequence number treated as the source port?
> Any ideas?
>
> Thanks,
> Mark
>
>
> 2006/12/7, Mark Miklic <mmiklic at gmail.com>:
> >
> > Anyone knows how ICMP is being treated when layer-4 hash option (any of
> > them) is being turned on?
> >
> > I was doing some tests today, and the only way I could ensure a
> > consistent path for MTR through the per-flow lb-ed network was to exclude
> > layer-4 parameter hashing completely.
> >
> > The only thing that comes to my mind is that Juniper introduces random
> > values if there is no layer-4 information in the datagram...Is there any
> > option to bypass this, or perhaps I am barking at the wrong tree?
> >
> > Thanks,
> > Mark
> >
>
>
More information about the juniper-nsp
mailing list