The MPLS-OPS Archive

[Roger Clark Williams <rogerw@nordlink.com>]

Jacinto's points are all good. I would add, however, that I have found a 
growing interest in MPLS VPNs inside the enterprise  - for security 
reasons. By example, it is all very good to use ACLs and all, but the 
Accounting Dept. may still feel vulnerable, and useful access would demand 
a fair amount of ACL tweaking. An extranet VPN allows them their feeling of 
security while allowing others in the organization access to what is deemed 
acceptable. So the original stated benefits of MPLS that Jacinto refers to 
are not the only reasons to deploy. Within the healthcare industry there 
are sure to be reasons to parse out information only to those who need it, 
and VPNs serve this function well. Given MPLS's ability to support very 
complex VPN structures, there may well be a reason to have MPLS running 
where you are.

Roger Williams

At 12:37 PM 5/17/2002, you wrote:

>1-> There should not be any regarding the network, but due to mpls
>complexivity  the management of the network will need more attention.
>2-> I do not think changing to ISIS will introduce any benefit as it should
>not be a large network (I guess).
>3-> If we think about data traffic (not video) MPLS will not make it any
>much better in a small environment, probably you will encounter more
>benefits if talking about video packets.
>
>Regards,
>Jacinto
>
>
>
>
>
>
>
>
>jeffrey.welch@spectrum-health.org on 16/05/2002 21:09:00
>
>To:   mpls-ops@mplsrc.com
>cc:   ryan.brotherton@spectrum-health.org
>
>Subject:  [MPLS-OPS]: Ground up MPLS deployment
>
>
>
>
>  Ladies and Gentlemen,
>
>  I'm working on a complete network redesign that will replace an ATM core
>with a fully meshed redundant Gigabit ethernet core and edge solution. I've
>administered MPLS networks in the past, (OC-48 POS backbone running IS-IS,
>MPLS and RSVP.) but have never deployed it personally. As this is a brand
>new network being implemented, topology and all, it seemed like a good time
>to look at MPLS as a possible augmentation to the Gig-E network going into
>place. My questions are:
>
>1) Are there any known issues with utilizing MPLS in a smaller MAN (Metro
>Area Network) type environment?
>
>2) The current IGP of choice is OSPF. We are not running BGP across the
>core at all, as this is a hospital and the internal network that we're
>replacing is private. Would a protocol change to IS-IS be beneficial at
>all? OR will OSPF work just fine? (I think it will, but just want to be
>sure.)
>
>3) MPLS is a good fit within an ethernet environment due to the QoS
>constraints inherent in ethernet technology. Will MPLS provide the level of
>QoS needed to support the sensitive information contained in a hospital
>type network? (This is my first experience in a health care organization,
>where lives are literally at times dependant on the information provided
>across the network.) 5 nines seems to be the basic requirements here.
>
>  Any information, leads, or suggestions would be a big help.
>  Thank you all for your time.
>
>Jeffrey E. Welch
>Sr. Data Communications Specialist
>Network Infrastructure
>Office 616-391-2856
>Pager 616-931-6346
>Mobile 810-730-3169
>
>
>
>
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml