[Top] [All Lists]

Réf. : [nv-l] Virtual Routing and Forwarding (VRF)

To: nv-l@lists.us.ibm.com
Subject: Réf. : [nv-l] Virtual Routing and Forwarding (VRF)
From: thierry.van-mol@ciev.vd.ch
Date: Mon, 7 Nov 2005 16:56:51 +0100
Delivery-date: Mon, 07 Nov 2005 15:58:06 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <OF1C966772.FFCCD5FA-ON852570B2.0053E39A-852570B2.005456AC@lnotes-gw.ent.nwie.net>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

Well, the question is where do you plan to put Netview,
and what do you want to manage? I mean, is Netview on a LAN which
is itself in a VRF, or is it in a LAN which is in the Global Routing table?

If you want to manage several VRF, it may be a good ideas to create a
special "management vrf" which imports the route of all the VRF you want
to manage. On the other side, you need to export also the routes of this
"management vrf" to all other vrf's. You place then Netview in a LAN which is
in this "management VRF". Netview is not "aware" of VRF in the routers, you
don't get, by default, any special maps, by vrf, etc. But at least you can manage
all the PE and CE of your network.

If you need also to manage the backbone, you need also to connect in a way
this "management vrf" to the Global Routing table. There are tricks to do that, but
all this depends of your design: routing protocols used, etc.

Regarding technical papers,  I highly recommends all Jim Guichard books on the subjet
of MPLS VPN. There are 3, all published by Cisco Press.


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web