[j-nsp] Duplicate IP addresses on interfaces

Daniel Roesen dr at cluenet.de
Tue Sep 30 19:12:35 EDT 2008


On Tue, Sep 30, 2008 at 02:31:57PM -0500, Chris Adams wrote:
> It does for circuits that have valid link-state (i.e. not ethernet).
> For example, we've had a T1 customer move to a new location, which
> requires ordering a new local loop.  We copy the provisioning from the
> old loop to the new loop, and when the customer moves, they unplug their
> CPE from the old loop, drive to the new location, and plug into the new
> loop, and it just works.

This works fine as long as the "local" route generated for the interface
IP address doesn't pose a problem for you.

I wonder why Juniper still generates this route even when an interface
(unit) is logically down... the ingenuity of that escapes me... anyone
could clue me in?

Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0


More information about the juniper-nsp mailing list