[j-nsp] RE : Re: MX80 no more hash-key option in 12.2?

[david.roy at orange.com]

Yes and you can check current hash config with the pfe cmd

request pfe execute command "show jnh lb" target fpcX X=slot

David


Envoyé depuis mon Samsung Galaxy Ace d'Orange



Doug Hanks <dhanks at juniper.net> a écrit :


Pretty much. enhanced-hash-hey does a lot by default. Harry can elaborate.


On 10/23/12 2:38 AM, "Paul Vlaar" <paul at vlaar.net> 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-key = MPC (which works on the MX80 as it's based on Trio)
>
>mx80# set family inet ?
>Possible completions:
>+ apply-groups         Groups from which to inherit configuration data
>+ apply-groups-except  Don't inherit configuration data from these groups
>  incoming-interface-index  Include incoming interface index in the hash
>key
>  no-destination-port  Omit IP destination port in the hash key
>  no-source-port       Omit IP source port in the hash key
>  type-of-service      Include TOS byte in the hash key
>[edit forwarding-options enhanced-hash-key]
>
>I can only negate layer-4 information in the settings for that, does
>this imply that hashing on source / destination port is now the default
>even when I leave this setting out completely?
>
>So if I leave out any enhanced-hash-key setting, I can assume that
>traffic is hashed based on IP address, source and destination port?
>
>And does this mean ...
>
>services-loadbalancing {
>    family inet layer-3-services {
>    incoming-interface-index;
>    source-address;
>    }
>}
>
>... that only IPv4 based ECMP hashing is supported across the different
>PICs?
>
>Thanks,
>
>    ~paul
>



_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.