Clarke,
On 9/11/12 11:37 PM, Clarke Morledge wrote:
If the packet's L2 destination MAC matches the router's IRB MAC
address Its important to note that any bridge family filters applied
to the related Layer 2 IFLs, or to the FT [forwarding table] in the BD
itself, are not evaluated or
it.
Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187
On Tue, 23 Oct 2012, Paul Vlaar wrote:
On 23/10/12 10:59 PM, Clarke Morledge wrote:
---
My question for you
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
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 jnh lb
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.
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
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
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
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 at
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
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
Chuck,
thanks for the pointer and for the example code. This would definitely
work, but I'd still like to see if I can do this without an additional
switch.
I've been playing with L2 port mirroring and this config came out so far:
mx80# show forwarding-options port-mirroring family vpls
output
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;
Alex,
On 19/10/12 7:33 AM, Alex Arseniev wrote:
You could do cascaded PM. In a nutshell:
1/ port-mirror original packet, send the original packet on its way
2/ send the COPY into a loop (cable loop or looped tunnel)
3/ take the looped COPY and mirror it once again, creating 2nd copy.
4/ send
Hi, I've currently successfully gotten port mirroring setup to more than
one port, using the following config:
port-mirroring {
family inet {
output {
next-hop-group default-collect;
}
}
next-hop-group default-collect {
group-type inet;
interface
Hi, I've currently successfully gotten port mirroring setup to more than
one port, using the following config:
port-mirroring {
family inet {
output {
next-hop-group default-collect;
}
}
next-hop-group default-collect {
group-type inet;
interface
16 matches
Mail list logo
