Clarke,
thanks for your response.
On 23/10/12 10:59 PM, Clarke Morledge wrote:
> ---
> My question for you would be if you have an IRB interface associated
> with the bridge-domain that your mirror source port is in, and if the
> ICMP traffic coming
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
Paul,
You asked:
"This is the interface which I want to mirror:
mx80# show interfaces ge-1/0/2
description app3.igb0;
encapsulation ethernet-bridge;
unit 0 {
family bridge {
filter {
input mirror;
output mirror;
}
}
}
.
I'm trying to do basic L2 port mirroring based on the Juniper document
called "MX Series Ethernet Services Routers Layer 2 Configuration Guide
Release 10.1". I have the following config for L2 port mirroring on an
MX80 running 12.2R1.3.
The port-mirroring configuration:
mx80> show configuration
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
> > As for "high speed link to an EX" something along those lines has now
> > been announced as "Node Unifier" for FEX-like support.
> >
> >
> > It's a shame that the sum total of detail on that feature on Juniper's
> public website is two paragraphs that give very little detail on it.
>
> "
> Jun
* Craig Askings [2012-10-23 05:44]:
> Junos Node Unifier
> Junos Node Unifier is a platform clustering program for MX Series 3D
> Universal Edge Routers that centralizes management and automates device
> configuration to enable the connection of thousands of router and switch
> ports attached to M
This is another way to possibly port mirror in L2 to multiple ports:
http://www.juniper.net/techpubs/software/junos/junos95/swconfig-layer-2/id-l2-mirror-next-hop-example.html#id-l2-mirror-next-hop-example
Roughly following the example code for the firewall filter, I get:
[edit firewall family i
On 23/10/12 10:34 AM, david@orange.com wrote:
> Sorry i forgot that it was a mx80 i play too much with mx960. Yes sounds
> good. You can see that trio based card like mx80 adds by default layer 4
> in the key buffer. Unlike ichip based card.
>
> I written a post regarding this on my blog. Ht
Sorry i forgot that it was a mx80 i play too much with mx960. Yes sounds good.
You can see that trio based card like mx80 adds by default layer 4 in the key
buffer. Unlike ichip based card.
I written a post regarding this on my blog. Http://www.junosandme.net
Regards
David
Envoyé depuis mon
On 23/10/12 10:23 AM, david@orange.com wrote:
> Yes and you can check current hash config with the pfe cmd
>
> request pfe execute command "show jnh lb" target fpcX X=slot
First time I hear of this (hidden?) command. Doesn't work quite how you say:
mx80> request pfe execute command "show jn
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 a écrit :
Pretty much. enhanced-hash-hey does a lot by default. Harry can elaborate.
On 10/23/12 2:38 AM
There is none. But the enterprise switching book is very good
> Date: Tue, 23 Oct 2012 00:15:36 +0400
> From: nick.krit...@gmail.com
> To: dha...@juniper.net
> CC: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] Juniper MX5 vs Brocade CER
>
> Doug,
>
> thanks for the book. Nice to see the kin
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
20 matches
Mail list logo
