Network-Wide
MPLS VPN Traffic Visibility
Given the importance of Layer 3 MPLS VPN services
as well as the size and complexity of their underlying
networks, Service Providers need global visibility
into the routing and traffic dynamics across the
entire network in order to effectively respond
to dynamically changing conditions and customer
requirements. Yet, while many MPLS VPN traffic
analysis tools promise global visibility, they
are based on traditional network management approaches
that fall far short of meeting this need by offering
data only on Provider Edge (PE) router to Customer
Edge (CE) router interfaces, with no visibility
into core network dynamics or comprehensive views
into individual customer VPNs. Even with these
limitations, traditional network management methods
exact a heavy toll on the network and operational
budgets in terms of required traffic flow collection
or deployed hardware probes .
VPN Traffic Explorer uniquely combines Packet
Design’s patent-pending route analytics technology,
Netflow/IPFIX traffic flow analysis, and MPLS
control plane protocol awareness to deliver an
integrated view of the entire network’s VPN routing
and traffic dynamics with minimal network overhead,
allowing engineers for the first time to answer
critical questions such as:
- Which routers and links are (or were) carrying
a specific VPN customer’s traffic?
- Are all the sites of a customer’s VPN connected
and reachable to each other through the VPN
network?
- What is the breakdown of traffic by Class
of Service (CoS) on any given link in the network?
- What is the growth trend for a VPN customer?
- If current VPN traffic growth continues, will
the current QoS configurations in the network
still be valid in the future or will network
changes or capacity upgrades be needed?
- Will adding a new customer impact meeting
existing customer SLAs?
Without VPN Traffic Explorer’s network-wide understanding
of MPLS VPNs, network managers are left to guess
at root causes of customer issues, how to sufficiently
plan for customer growth, and how to prevent configuration
mistakes. |