Funny you mention Draft Rosen because my interest stemmed from multicast
testing.
-Chip
-Original Message-
From: Sean Clarke [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 1:57 AM
To: cp
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] reusing loopback 0 ip address in
I would say common practice - if you're using VRF's in a multivendor
environment with draft-rosen for instance, I believe you MUST use the
same IP address in the lo0.x interface, as the "other" vendor expects
the lo0.0 address (which the Juniper won't send). Of course all Juniper
network won't
On Wed, Nov 19, 2008 at 2:44 PM, David Ball <[EMAIL PROTECTED]> wrote:
> I would expect it to work. Never tried it, and dunno if it'd be
> common practice, but lo0 is largely just an interface, and just as
> have 2 customers come in across a tagged Gig trunk to be dumped into
> separate VRFs sho
On Wed, Nov 19, 2008 at 1:28 PM, cp <[EMAIL PROTECTED]> wrote:
> Does anyone see a problem or have any experiences with using the same
> loopback unit 0 IP addresses for other loopback unit in VRFs? Is this a
> common practice? For example, loopback unit 0 is 172.16.1.1/32 and
> lives in inet.0.
I would expect it to work. Never tried it, and dunno if it'd be
common practice, but lo0 is largely just an interface, and just as
have 2 customers come in across a tagged Gig trunk to be dumped into
separate VRFs should work, so too should the same IP in diff logical
units on lo0. Only 1 way t
Does anyone see a problem or have any experiences with using the same
loopback unit 0 IP addresses for other loopback unit in VRFs? Is this a
common practice? For example, loopback unit 0 is 172.16.1.1/32 and
lives in inet.0. loopback 425 is 172.16.1.1/32 lives in a vrf.
-Chip
___
6 matches
Mail list logo
