The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Sep> msg00072



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

RE: Cisco VPN Solution Center

  • From: Ross Chandler <ross@eircom.net>
  • Date: Wed, 11 Sep 2002 19:40:08 +0100
  • Resent-Date: Wed, 11 Sep 2002 16:23:38 -0400
  • To: Rui Francisco Negrão Valente <rui.valente@corp.vodafone.pt>, mpls-ops@mplsrc.com
  • X-Sender: ross@mail1.eircom.net

Title: RE: [MPLS-OPS]: Cisco VPN Solution Center
I agree and I shall try that. But in case of full mesh configuration?
 
Suppose that I already have a VPN configured and a new PE is added with a new costumer site connected. I have to go to all PEs and enter the commands manually.


If you don't use route reflectors to get the vpnv4 routes to the VPN-PEs
then you'll need to fully mesh all your VPN-PEs. Unless you have very
few routers I wouldn't do that..  In theory you could use VPNSCs template
feature to do a full mesh config but I wouldn't as it violates Occam's razor..


With RRs the BGP peering commands for the VPN-PEs will be identical
of course. The RRs themselves will need the VPN-PE loopbacks in the
peerings.

Any config that isn't directly related to setting up services for
your customers is best left to manual or simple template based
deployment.

Regards

Ross