Professional Documents
Culture Documents
MPLS MP Training Session
MPLS MP Training Session
Training Agenda
Overview of IP/MPLS Design and Optimization Services SP Guru Demo MPLS TE Design Example (China Unicom) MPLS Network Assessment Example (Bell Canada) MPLS TE Design Example for VoIP (PaeTec) Performance Analysis Example for VoIP (PaeTec) FY06 Service Development Plan Q&A Supporting Information Contacts Supporting Documents & Information SP Guru 11.5 Installation Instructions
analysis
Given a network topology and a set of traffic demands, profiles
Topology Information
Reports
Reports
and failure analysis, and discrete event simulation for performance evaluation.
Typical deliverables: Class based link bandwidth allocation Recommendations for scheduling, policing policies, network changes to achieve customers performance requirements Simulation based performance analysis including end-to-end delay, packet loss, jitter, etc. Routing and failure analysis Network configuration reports showing errors/misconfigurations etc. Detailed reports, logs, graphical views
LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
8
requirements and candidate link types (OC-3, OC-12, etc.) and other requirements, design minimum cost link placement
Cost can be represented and combined in numerous ways: Fixed link costs, for example $1000 per OC-3 link deployed Mileage costs, for example $100/mile Bandwidth costs, for example $5 per Mbps of subscribed LSP bandwidth Costs can also be based on tariffs if the links are to be leased, these could be obtained from tariff tables Even more general non-currency metrics such as number of hops and link distance can be used The design service also supports additional requirements
including:
Maximum link utilization/subscription Protection options determined through failure analysis
LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
10
Node Information
Greenfield Design
Reports
Performance Analysis
Reports
11
12
13
VoIP, VPN, 3G, Internet Access etc.) with different service requirements, perform multi-class traffic engineering, design
and optimization
Typical service requirements include bandwidth allocation per
class, multi-class LSPs vs. multiple single-class LSPs, protection schemes (for example, path based, FRR facility bypass, FRR 1+1), hop and delay constraints, performance requirements, etc.
The design service provides a minimum cost network design and
network design and performance analysis for multi-class traffic-engineered MPLS networks
The high level workflow of this service is as follows:
Input Multi-Class traffic and/or LSP information, (VoIP, VPN, 3G, IA, etc.), protection options (Path, FRR, etc.)
Reports
Reports
15
17
18
SP Guru Demos
19
SP Guru Demonstration
China Unicom study demo MPLS network design study to compare different MPLS TE design options for a core network carrying internet access and VPN traffic Performed using SP Guru version 11.0 Beta3 Bell Canada study demo Network configuration assessment for a large service provider network Performed using SP Guru version 11.0 Beta3 PaeTec design study demo Multi-year design study for VoIP service providers MPLS/IP core network comparing different voice codes and architectural options Performed using SP Guru version 11.0 Beta3 PaeTec performance study demo VoIP performance study for PaeTec network Performed using SP Guru version 11.0 Beta3
20
21
traffic
IA traffic is best effort, LDP based and VPN traffic has four
22
23
24
25
Link utilization report and GUI link utilization view LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
26
Traffic intensity:
Total Internet Access (IA) traffic is 5508 Mbps
- IA demands are from the non-gateway locations (Chengdu, Xian, Wuhan, Shenyang) to the closest two gateways, in each direction
IP-VPN Customer Distribution Avg. Number of Nodes per IP VPN Customer Access Speed Distribution
28
traffic rates to be carried, plus the required MPLS overhead The type of LSP (single/multi class) depends on the design scenario LSPs are configured with link disjoint backup paths
Link properties:
100% of link bandwidth is available to TE subscription
29
Design
Scenario 1 0.00
Scenario 2 0.00 Scenario 3 0.00
LWS Training, Oct. 24, 2005
31
32
files the part of the study presented here focused on the core network
The study involved the following steps: Import network into SP Guru from Cisco configuration files Run Identify Unreachable Interfaces to see if there are any unreachable destinations in the network Run NetDoctor with IP routing rules selected to analyze network for configuration errors or inconsistencies Gather further information using Flow Analysis and the associated routing reports
33
apparent connection
Not connected
34
Backbone Area
35
36
37
these 5 routers:
On core1-toronto12: interface [POS3/3] (64.230.203.109/30)
Note: in all cases no routing protocol is running on the interface, which could be a possible explanation for the unreachable interfaces
64.230.251.164/30:
64.230.251.166/30 64.230.251.165/30
64.230.251.160/28:
64.230.251.161/28 64.230.251.164/28
38
BC: Static Routes with Unreachable Next Hops Flow Analysis Details
Router Name
core2-montreal02
Destination Address
67.69.180.0/27 67.69.180.0/27
core3-toronto63
core2-torontodc
core1-fortmcmurray
* Note: This is an unreachable next hop when only the core network is considered. However, reachable next hop exists when whole network is considered. LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
39
BC: Static Routes with Unreachable Next Hops Flow Analysis Details, Cont.d
Router Name
core1-grandprairie
Destination Address
172.16.0.0/12 127.0.0.0/8 10.0.0.0/8 192.168.0.0/16 ` 206.108.96.172/32 199.243.34.0/24
? ?
core1-abbotsford
0.0.0.0/0 206.172.102.0/24
64.230.248.157/30 64.230.214.82/32
core2-vancouve ATM0/0/0.33 ?
core1-kamloops
172.16.0.0/12
Null0
127.0.0.0/8
10.0.0.0/8 192.168.0.0/16 206.108.96.218/32 199.243.32.0/24
Null0
Null0 Null0 64.230.251.67/32 64.230.251.82/32 ? ?
core1-kelowna
206.172.198.0/24
64.230.214.18/32
core1-princegeorge
199.243.37.0/24
64.230.214.50/32
core1-vernon
199.243.36.0/24
64.230.251.242/32
40
BC: Static Routes with Unreachable Next Hops Flow Analysis Details, Cont.d
Router Name
core1-medicinehat
Destination Address
172.16.0.0/12 127.0.0.0/8 10.0.0.0/8 192.168.0.0/16 199.243.33.0/24 199.243.33.241/32
? ?
core1-reddeer
199.243.31.0/24
199.243.31.241/32
64.230.251.146/32
64.230.251.146/32
?
?
41
bx3-toronto12
Area 0.0.0.105:
Area 0.0.0.107: Area 0.0.0.122: Area 0.0.0.124:
Area 0.0.0.191:
Area 0.0.0.208: Area 0.0.0.232: Area 0.0.0.244: Area 0.0.1.64:
42
43
44
with 11 nodes (Cisco 12410 routers), and an initial mix of OC-3 and OC-12 links
Voice traffic (originating/terminating at 8 of the nodes) to be
45
46
47
demands
# of Routed VoIP Demands Total Consumed Voice BW (Mbps) Max. Hop Length (Links) Avg. Hop Length (Links) Max. Link Util. (%) Avg. Link Util. (%)
56/56
10870.27
2.14
489.68
187.95
bandwidth to 100% of the link capacity in order to find a solution with no over-subscribed links.
# of Routed LSPs/ demands 23/56 Total Consumed Voice BW (Mbps) 3456.79 Max. LSP Hop Length (Links) 3 Avg. LSP Hop Length (Links) 1.61 Max. Link Sub. (%) 93.84 Avg. Link Sub. (%) 58.44
does not have enough capacity to route all 56 LSPs to carry all VoIP traffic demands
LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
50
option is to use traffic engineering to be able to better make use of existing resources
52
100% of the link capacity in order to find a solution with no over-subscribed links using traffic engineering
# of Routed LSPs/ demands 56/56 Total Consumed Voice BW (Mbps) 11526.75 Max. LSP Hop Length (Links) 5 Avg. LSP Hop Length (Links) 2.27 Max. Link Sub. (%) 99.91 Avg. Link Sub. (%) 72.54
routed to carry the voice traffic within the existing network capacity, without having to add or upgrade links
The increase in total consumed bandwidth and hop
VoIP traffic over MPLS LSPs while maintaining link utilization at less than 100%
carried on existing capacity without capacity upgrade expenditures, with minimal increase in total bandwidth consumed and hop length
54
55
performance analysis to estimate VoIP quality measures such as end-to-end delay, packet loss, etc. (then translate to MOS scores)
The study involved the following steps:
Import network into SP Guru using text import files Import data flows into SP Guru using spreadsheet import files Prepare network for VoIP performance simulation Create detailed VoIP traffic flows for G.711 or G.729a codec using traffic flow generator in SP Guru for performance simulation Run performance simulation for selected VoIP demands to estimate
56
shown) is also included, but performance data is not collected for these
57
Aggregation Router
58
59
60
protection or FRR) and unprotected traffic for various classes of services according to carriers protection policy
B. MPLS cost optimization Address minimal-cost network
design considering both CapEx and OpEx for existing MPLS networks
C. 3G over MPLS Consider network design and optimization
61
Hybrid MPLS protection created by Bell Labs will be integrated with SP Guru M&P for FRR and Hybrid protection using SP Guru and integrated Bell Labs algorithms
62
and, if necessary, new algorithms to enable CAPEX/OPEX reduction by eliminating equipment and capacity. Numerous modes of operation could be supported including constraints on where and how much equipment/capacity can be removed, required spare capacity and acceptable traffic performance (in terms of loss, delay etc.) following equipment/capacity removal.
63
3G Over MPLS
Deliverables Traffic profiles covering most common 3G applications (web browsing, IM, video streaming, VoIP, etc) and their bandwidth and performance requirements Traffic modeling that converts 3G application demands to point-to-point traffic as input to MPLS design and optimization Guidelines for class of service design for 3G applications M&P for 3G over MPLS design and optimization and performance assessment using SP Guru (FLAN, DES)
64
to p2p VoIP traffic) Design of multiple CT to assure quality of VoIP in the presence of other data traffic, protection of VoIP traffic, and assessment of VoIP quality using SP Gurus DES feature over the designed and optimized MPLS network
65
the import of NetInventory discovered network data into OPNET for further analysis and design
66
Optus NTT
A, B A, B
A, B, D A, B
Sprint
67
US Cellular BT 21 Century
B, D B, D
T-Mobile UK
A, B, C
UPC
A, B, D
AUNA KBW
A, B A, D
68
Q&A
69
Supporting Information
70
Contacts
Ahmet Akyamac akyamac@lucent.com (732) 949-5413
71
When you first run SP Guru, it will create the op_admin and
op_models directories
op_admin contains the log files and administrative information op_models contains the project and model files and is the initial
default directory
LWS Training, Oct. 24, 2005
Lucent Technologies 2005 - All Rights Reserved - Proprietary
73