r the L1 route preference, that's what I don't understand. If R1/R2
> are getting each other's loopbacks through L2 with a preference of 18, but
> then I swap the L1/L2 preferences so that L2 now has a pref of 15, why would
> the L1 route always get preferred?
>
&
Eric,
Since R1 and R2 are L1/L2 routers they'll each always prefer the L1 route
over the L2 route due to default route preference. It's an interesting
situation for sure. Removing the loopback from L1 isolates R1 and R2 from
advertising their loopbacks to R3 and R4, but with the loopback enabled f
Tommy,
I just checked all PSN notifications associated with this SIRT bulletin and
*none* of them list 10.x as an affected release.
On Thu, Jan 7, 2010 at 2:58 PM, Tommy Perniciaro
wrote:
> How can that be the case when 10.x was released after 1/09 and it's on
> the list of affected junos versi
That message typically means that the router doesn't know where to send
joins upstream. Your outputs suggest that connectivity exists, but I'd check
the following:
1. Verify that a unicast route to the RP exists.
2. Verify that it exists in the same routing table PIM is using (inet.0 or
inet.2)
3.
Power down the router and insert the flash card. After you reboot just issue
the command:
request system snapshot partition
-Dan
On Tue, Mar 3, 2009 at 9:57 AM, Matthias Gelbhardt wrote:
> Hi!
>
> I would like to add a new 1 GB CF card in a M7i. I assume, there is none in
> that device at t
Joe,
You should be able to pass BPDU's through without any configuration tweaks.
>From the 9.2 docs:
http://www.juniper.net/techpubs/software/junos/junos92/swconfig-vpns/transmitting-nonstandard-bpdus.html#id-10110163
HTH
-Dan
On Wed, Feb 11, 2009 at 5:39 PM, Joseph Soricelli wrote:
> All-
>
Try this:
http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-multicast/id-13041423.html#id-13041423
On 5/20/08, Dave Diller <[EMAIL PROTECTED]> wrote:
>
> Normally, the system uses the vrf-target to import routes from
> bgp.l3vpn.0 to the correct VRF.inet.0. This is working fin
Joe,
Check out the interface restrictions at the bottom of this link to the 8.5
documentation:
http://www.juniper.net/techpubs/software/jseries/junos85/jseries85-admin-guide/jN1606C.html
On 5/13/08, Joe Abley <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I came across an oddity the other day tha
I'd have to say that's definitely incorrect.
As long as the VPNv4 NLRI is configured between the two peers and
negotiated correctly then the BGP RR will accept VRF routes in VPNv4
route format (route_distinguisher:prefix/mask).
On Juniper routers these routes are stored in the bgp.l3vpn.0 routing
>From the outputs you supplied the J6300 is accepting and installing a
majority of its BGP prefixes from your IBGP peer in as AS7849:
> 7849 72875 14981 0 6 45:22
> 223250/225922/0 0/0/0
The router is receiving 227904 routes via AS16657, but only install
How are you applying the policy? It should be applied to the
forwarding-table like this:
routing-options {
forwarding-table {
export TEST_POLICY;
}
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman
11 matches
Mail list logo
