Sorry for replying an old thread but my two cents about LB on Trio.
> Please take into consideration that the engineers that designed TRIO LB
> decided to simplify the LB options traditionally available on other
> chipsets, so you may find missing ones under the enhanced-hash-key. TRIO LB
> algo
On (2012-10-24 01:12 +0400), Tima Maryin wrote:
> Check KB24339 also
> (Hash key computation on MPC cards)
Is this accurate?
-
Payload recognition uses the following criteria to estimate the nature of
the payload:
IPv4 assumes the first nibble, which follows the bottom label, is 0x4. If
thi
On 23.10.2012 21:09, Paul Vlaar wrote:
This definitely seems like a bug. Worth submitting to Juniper TAC?
I don't think so.
Check KB24339 also
(Hash key computation on MPC cards)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck
On 23/10/12 6:37 PM, Olivier Benghozi wrote:
> I had previously (like you) the hash-key stuff configured on some
> MX80 gear, and removed it after reading David Roy's answer.
>
> I can confirm that the removal of this stuff left the tfeb in a
> strange state (running 11.4R5), with some funny logs
Hi Paul,
I had previously (like you) the hash-key stuff configured on some MX80 gear,
and removed it after reading David Roy's answer.
I can confirm that the removal of this stuff left the tfeb in a strange state
(running 11.4R5), with some funny logs at the commit (tfeb0
jnh_loadbalance_hashk
Hi Paul,
with MX TRIO you don't need to configure anything to achieve almost the
behaviour you need (almost = not per packet, read below).
TCP and UDP ports are taken into account on TRIO by default for both IPv6
and IPv4. Please be aware of some more info:
- TRIO doesn't support per-packet LB
Hi Magno,
that clarifies things a bit more for me, thank you.
However, am I right to conclude that I still need the hash-key stanza
for our 11.2 MX80s to make IPv6 source/destination hashing work for load
balancing?
As for what I am trying to do, well, that is pretty simple. We have ECMP
for a n
Hi Paul!
Leaving the hash-key stanza enabled for MX80 leaves room to unexpected
behaviours as you could observe yourself.
the only supported way to tweak load balancing input paramters for TRIO
based devices (I mean MPCs and MX80 for instance) is to use the
enhanced-hash-key stanza.
The culpr
Doug,
On 23/10/12 9:52 AM, Doug Hanks wrote:
> Pretty much. enhanced-hash-hey does a lot by default. Harry can elaborate.
So on 11.2 at least, enhanced-hash-key doesn't offer me any options to
set, as the defaults should already enable port based hashing:
mx80# set forwarding-options enhanced-ha
Pretty much. enhanced-hash-hey does a lot by default. Harry can elaborate.
On 10/23/12 2:38 AM, "Paul Vlaar" wrote:
>On 23/10/12 12:59 AM, Doug Hanks wrote:
>> hash-key = DPC (should never been been on or used on the MX80 - doesn't
>> even do anything when configured)
>>
>>
>> enhanced-hash-k
On 23/10/12 12:59 AM, Doug Hanks wrote:
> hash-key = DPC (should never been been on or used on the MX80 - doesn't
> even do anything when configured)
>
>
> enhanced-hash-key = MPC (which works on the MX80 as it's based on Trio)
mx80# set family inet ?
Possible completions:
+ apply-groups
hash-key = DPC (should never been been on or used on the MX80 - doesn't
even do anything when configured)
enhanced-hash-key = MPC (which works on the MX80 as it's based on Trio)
On 10/22/12 5:36 PM, "Paul Vlaar" wrote:
>I just upgraded one of our MX80s to 12.2R1.3, and the following occurs:
>
I just upgraded one of our MX80s to 12.2R1.3, and the following occurs:
mx80# show forwarding-options
[...]
##
## Warning: configuration block ignored: unsupported platform (mx80-48t)
##
hash-key {
family inet {
layer-3;
layer-4;
}
family inet6 {
layer-3;
13 matches
Mail list logo
