The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Oct> msg00096



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

RE: REG: MPLS Design issue

  • From: "Luciano Salata" <salata-list@ifxnw.com.ar>
  • Date: Thu, 17 Oct 2002 15:21:52 -0300
  • Importance: Normal
  • Resent-Date: Thu, 17 Oct 2002 16:22:57 -0400
  • To: "Joseph Anthony" <tonyjoe20002002@yahoo.co.in>, <mpls-ops@mplsrc.com>

What about if you inject into cutomer VRF a route pointing to the NMS (from de Global Routing Table).
For the returning traffic from NMS to the VPN, if you put a route in Global Routing Table pointing insde the VPN, it won't be a VPN any longer.
But if you do NAT and you translate customer's ip space when it goes to NMS, you can put a single route to "semi" public ip address (translated address) and it will be still a VPN.
 
I don't know if it makes the scenario more complicated, i mean, without any sense.
 
Regards,
 
Luciano
 
 
-----Mensaje original-----
De: Joseph Anthony [mailto:tonyjoe20002002@yahoo.co.in]
Enviado el: Jueves, 17 de Octubre de 2002 03:11 p.m.
Para: Luciano Salata; mpls-ops@mplsrc.com
Asunto: RE: [MPLS-OPS]: REG: MPLS Design issue

Hi Luciano,

Basically the system is based on a distributed architecture with numerous backend components that are spread acorss the provider network, and also hence putting the same as part of an independent VPN may be a little complex. But the customer just needs to connect to a  single front end reporting server for details that he may require. Any suggestions?

Regards,

Tony.

 

Yahoo! Properties Special new Buy, sell, rent...your flat, or even post an ad