The management VPN configuration is for example going to be like the
following:
mgmt {
description "-- management vpn --";
instance-type vrf;
# - e.g. management vlan 100
interface ge-0/0/0.100;
interface lo0.110;
vrf-export mgmt-export-policy;
vrf-target import target:
Some notes inline:
On 4/06/2009, at 9:13 PM, Jeff Meyers wrote:
Truman Boyes schrieb:
Hi,
thanks for your answer so far.
You then need to define a route-distinguisher, and route targets
(or simply vrf-target under the VRF) to import/export the routes
for this VPN from other PEs.
Can yo
s.
-Jeff
From: juniper-nsp-boun...@puck.nether.net [juniper-nsp-boun...@puck.nether.net]
On Behalf Of Jeff Meyers [jeff.mey...@gmx.net]
Sent: Thursday, June 04, 2009 4:13 AM
To: Truman Boyes
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] MPLS for management VPN
Truman Boyes schrieb:
Hi,
thanks for your answer so far.
You then need to define a route-distinguisher, and route targets (or
simply vrf-target under the VRF) to import/export the routes for this
VPN from other PEs.
Can you provide an example for that? That would be a L3VPN, right? Why
wou
Your PE routers can provide a way to reach your management segments
around the network. You can create a routing-instance (VRF) for
management, then put an IP address on the PE router for VLAN100. You
will do this at each M-series.
You then need to define a route-distinguisher, and route ta
Hi,
we currently have a small number of PoPs, each equippped with a Juniper
M-series router. On each PoP we use a local Vlan 100 for the management
with RFC1918 ip adresses - 192.168.0.0/16.
Unfortunately, this results in scalability problems as the network grows
since it's not possible to m
6 matches
Mail list logo
