The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
RE: Basic MPLS VPN Design Question
-
From: "Irwin Lazar" <ILazar@burtongroup.com>
-
Date: Thu, 7 Aug 2003 09:39:42 -0600
-
Resent-Date: Thu, 7 Aug 2003 12:06:47 -0400
-
Thread-Index: AcNc7Jdz2CGDV157TJWNfgRg6ZwCeAADTtYg
-
Thread-Topic: [MPLS-OPS]: Basic MPLS VPN Design Question
-
To: <chris.waterbury@hstp.com>, <mpls-ops@mplsrc.com>
A lot
will depend on your carrier. Many carriers still offer separate PVCs for
voice, as they don't support QoS on their MPLS-VPN services. If this is
the case with your carrier then you will likely need to buy a dedicated voice
service.
For
security reasons, it is generally advisable to isolate voice traffic within your
LAN into a separate VPN. However if you can prioritize over the WAN, I see
no need for logical isolation.
Irwin
------
Irwin Lazar
Phone:
703-742-9659
Greetings,
I'm currently in the
process of designing an MPLS based network. I'm also somewhat new to
MPLS. A question has been raised about voice services. This
provider will be supplying both voice and data. Some of our engineers
are suggesting that all customer voice VLAN's be in the same VPN. Others
are suggesting that each customer have two VPN's, one data and one
voice. Still others suggest that the customer have one VPN for
both.
I haven't been able to
find any "best practices" documents on MPLS VPN design so I thought I
would ask the list. Any ideas would be greatly
appreciated.
Thanks!
Chris Waterbury, CCNP
Principal Consultant
Heatseeker Technology Partners
612.636.5335
| |
|