Hello,
Here, is the information. but the Junipes's don't see each other.
o...@m10_a> show configuration interfaces ge-0/2/0
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50 inner 100;
fami
This is a very valid point.
I have also verified that if no user-defined policer is applied and only
the internal __default_arp_policer__ is in place, this policer is a
global policer and drops arp-req from any interface if a single
interface is under ARP attack
Another point of having user-defined
Hello all, is there a way to view default config of certain defaults in
JUNOS...like _default_arp_policer or default_scheduler etc..
Cheers
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On Tuesday 20 October 2009 02:23:04 pm sth...@nethelp.no
wrote:
> Not compatible. Somebody f'ed up in the EX series ASIC
> design, and as a result of this the EX series can only do
> *one* MPLS label.
Well, perhaps not a totally complete screw-up from a
commercial point of view :-).
Mark.
si
On Fri, 16 Oct 2009, Bit Gossip wrote:
https://puck.nether.net/pipermail/juniper-nsp/2009-May/013325.html
...
and only ~4 arp requests received a reply from M7i
which makes roughly ~222 arp-reply/sec
...
My conclusion is that the setting for __default_arp_policer__
are perfectly fine and
5 matches
Mail list logo