- Series: Networking Technology
- Paperback: 552 pages
- Publisher: Cisco Press; 1 edition (March 24, 2005)
- Language: English
- ISBN-10: 1587142414
- ISBN-13: 978-1587142413
- Product Dimensions: 7.2 x 1.2 x 9 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #1,655,844 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Definitive MPLS Network Designs (paperback) (Networking Technology) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2018 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
From the Back Cover
Field-proven MPLS designs covering MPLS VPNs, pseudowire, QoS, traffic engineering, IPv6, network recovery, and multicast
- Understand technology applications in various service provider and enterprise topologies via detailed design studies
- Benefit from the authors' vast experience in MPLS network deployment and protocol design
- Visualize real-world solutions through clear, detailed illustrations
- Design studies cover various operator profiles including an interexchange carrier (IXC), a national telco deploying a multiservice backbone carrying Internet and IP VPN services as well as national telephony traffic, an international service provider with many POPs all around the globe, and a large enterprise relying on Layer-3 VPN services to control communications within and across subsidiaries
- Design studies are thoroughly explained through detailed text, sample configurations, and network diagrams
About the Author
Jim Guichard, CCIE® No. 2069, is a system architect at Cisco Systems®, with a primary focus on MPLS/IP Layer-2 and Layer-3 VPN technologies. During the last eight years at Cisco®, and previously at IBM, Jim has been involved in the design, implementation, and planning of many large-scale WAN and LAN networks.
François Le Faucheur is a system architect at Cisco Systems working in product development and IETF standardization in the area of IP QoS and MPLS. Prior to joining Cisco, he worked for several telecom carriers in France and Australia on the development of enhanced services on ATM, Frame Relay, SMDS, and IP.
Jean-Philippe Vasseur is Cisco Distinguished Engineer where he works on IP/MPLS architecture specifications, focusing on IP, TE, and network recovery. He holds an engineering degree from France and an M.S. from the SIT (New Jersey, USA). Before joining Cisco, he worked for several service providers in large multiprotocol environments. He is an active member of the IETF, co-chair of the IETF PCE (Path Computation Element) Working Group and coauthor of several IETF RFCs. He is a regular speaker at various international conferences and is involved in various projects in the area of IP and MPLS. He has also filed several patents in the area of IP and MPLS and is the coauthor of “Network Recovery".
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The examples are:
1. An interexchange carrier that provides data and long-distance services throughout the U.S. including LATA services and 31 flavors of data services. The example is based on a fictitious company that owns its fiber and transmission facilities as Layer 2 switching infrastructure (ATM and Frame Relay).
2. Another fictitious company is a telco that operates an ISP in addition to being an existing telecom provider in Asia or Europe.
3. The next fictitious example operates in more than 60 countries serving medium and large international companies, and is using virtual POPs based on co-location of some routers in regional service providers' premises.
4. The final example is a fictitious European bank holding company originally based in the UK that has expanded into a multi-continent organization with insurance and brokerage operations. The organization wants to keep the flexibility to quickly add other acquired financial institutions to its base.
The first two chapters provide about a hundred pages on the basics of MPLS. I found it easy to follow, and I'm not an engineer nor a software professional. For those with advanced questions, this material in fact may be a little too simple.
I would have liked the book a lot better if it had dealt more with a process for making design decisions rather than providing so many cases.
All four of these mythical entities build Layer 3 MPLS services, but they each have different requirements for QoS, restoration, traffic engineering, and other services provided by MPLS. USCom is a long distance voice service provider who needs very fast (telco quality) recovery over unprotected core transport. Telecom Kingland is adding a multiservice backbone that will be trunking public telephony as well as new services such as IPv6 and carrier of carrier services (in which all VPNs from one carrier are trunked in a single VPN across another carrier's backbone). GlobeNet has unique traffic engineering concerns and a need to create viable peering agreements with local service providers in order to provide services in a shared fashion. Thus, inter-AS Layer 3 VPNs are discussed in detail here. EuroBank, with its vast resources, is building out its own MPLS core to support the variety of access infrastructures it has inherited. Each of these strawmen are described in terms of their design objectives, the services they offer, their topologies, and the constraints that lead to the choices made in building out these networks. Configuration snippets are provided throughout for illustration purposes.
The problem that this book solves is that there really is no one-size-fits-all design for any network technology, and MPLS is no exception. The set of services offered by network operators and enterprises vary greatly from one implementation to the next, and the best you can do is try to scaffold a set of likely use cases and thus provide a starting point for the network designers and engineers that have to take on unique project.
These case studies all validate the reasons that MPLS has emerged as a way to give you the simplicity and power of Layer 3 networks and still retain everything you loved about your last generation Layer 2 Frame Relay or ATM network-the per-subscriber separation of virtual circuits, robustness against attacks, and the virtualization of the core infrastructure. The real sale in terms of manageability is the ability to maintain only a single converged network instead of many disparate networks. Initially it was the traffic separation capabilities in the form of Layer 3 VPNs that put MPLS on the way to wide acceptance, but with the growth of multimedia traffic and the trends towards advanced network services, the demand for resiliency, restoration and traffic engineering on a scale more commonly associated with optical transport has provided another wide area for MPLS to show its strengths.
Chances are that any network engineer responsible for turning up or maintaining an MPLS network is only going to be responsible for a network resembling one of the reference designs illustrated in this book. But it is well worth browsing all the different implementations to get an idea of the power of MPLS to fit into these different models. Finally, what really drives this book to 5 stars is the comprehensive technology primers it provides before even getting into the case studies. The first chapter is more edge-oriented and provides an excellent backgrounder on MPLS VPN services, as well as multicast, IPv6, and pseudowire. Chapter 2 covers core issues such as the many varieties of MPLS traffic engineering and QoS facilities. These chapters give you most of the hooks you need to hang onto the concepts that are introduced in the case studies, and they provide nice reference material in general to get a feel for these technologies before you go digging through the documentation for implementation specifics.