لطفا منتظر باشید ...
Summary
Deploying pseudowire emulation services in MPLS networks can be a rather sophisticated task when you take factors such as routing, network resource utilization, and path protection into account. This chapter discussed some of the most common but complex deployment scenarios you might encounter when offering pseudowire emulation services, as follows:
Load share across multiple equal-cost paths.
Forward pseudowire traffic through a preferred path using the IP Routing protocol.
Direct pseudowire traffic through an explicit path using an MPLS traffic engineering tunnel.
Dynamically route pseudowire traffic through an MPLS traffic engineering tunnel with a specific bandwidth requirement.
Protect pseudowire traffic from pocket loss with the MPLS traffic engineering fast reroute capability.
Provide inter-AS pseudowire connectivity through dedicated circuits.
Provide inter-AS pseudowire connectivity using BGP IPv4 label distribution and IGP redistribution.
Provide inter-AS pseudowire connectivity and improve scalability with BGP IPv4 label distribution and IBGP peering.
Authenticate for pseudowire signaling.
Verify pseudowire data connectivity and provide troubleshooting.
Configure general and protocol-specific pseudowire QoS.
This is not intended to be an exhaustive list of all possible deployment scenarios for AToM. Rather, it serves as a building block for more complex deployment of a large scale.
