sounds like you're missing proxy arp entries for these addresses on your
outside interface.
such as:
set security nat proxy-arp interface ge-0/0/0.0 address 59.1.1.5/32
set security nat proxy-arp interface ge-0/0/0.0 address 59.1.1.6/32
Jon Paulhamus [CCNP, JNCIP-ENT, MCSE]
Assistant Directo
Hi Mike,
I'm definitely winging this since I don't use OSPF much, but would
you be able to use a combination of VRRP interface tracking and groups
to do this? i.e. -
ge-1/3/0 {
}
unit 0 {
family inet {
address 192.168.1.2/24 {
In-line with
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of tim tiriche
Sent: Friday, September 28, 2012 11:50 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Juniper CoS question?
4 fwd classes defined (tra
4 fwd classes defined (transmit/buffer size percentages and priority)
on 10G interface
EF (5% strict-high) AF(80% - high), BE(10%-low), NC(5%-low)
case1: if i send 80% traffic on BE and no other traffic - should the
traffic be dropped if it is out of profile but bandwidth available?
case2: if i se
Have you enabled proxy ARP for those addresses?
Oliver
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Hi,
I had "dhcp-relay" configuration active on M10i(10.4R9.2). This
feature requires "scale-subscriber" license. I replaced "dhcp-relay"
configuration with "helpers bootp" configuration. However, the "show
system license" and "show system alarms" still indicate that I'm using
"dhcp-relay" feature:
Hey all,
we recently replaced our old Nortel Core (L2) with a large EX4500 VC
and are quite happy with the simplicity of a collapsed core.
During the last few days we where hit by two packet storms,
the logging of this event does not really help to identify
the course of the problem eq. VLAN-ID,
I notice it is using a new field in the update and that it is tied to the label
block of the PE so it might be that a single update can now wipe all MAC
address routes for a PE rather than having to send a route withdrawal for every
MAC address which could take some time?
Regards,
Caillin
Sen
Thanks for the info, I can get NAT working when using the ext interface/ip
as the egress type, but when I try to use a Nat pool with the same address
range as the
interface IP, it doesn't work.
Ext. Interface IP is: 59.1.1.1/24 and Nat Pool using 59.1.1.5/24 to
59.1.1.6/24
Have also tried 59.1
It seems also "mac-flush" is now available with BGP based VPLS - before that
was only supposed to work with LDP based.
Possibly that is a more important improvement.
> I see that there is a new "best-site" feature in Junos 12.2 for improving the
> convergence time in VPLS multi-homed environmen
10 matches
Mail list logo
