MPLS Japan 2003

Tools and techniques for smooth installationand maintenance of MPLS network

Why the need for tools?
The trend is that the packet network will be
predominantly IP/MPLSAs a result, most user services will have to besupported over MPLS networks - be it Voice or
Wireless or even ATM/FR service
Clearly, MPLS network need to very well managed,
as the importance of the services it carries will bevery highThursday, January 23, 2003 Agilent Restricted

Page 2

Solution requires two pronged approach
Technical- Should be comprehensive- Features need to be suitable to testing network- Features need to be tailored to test MPLS
Logistical- Should not be expensive to implement- Should not be difficult to manage or operate

Thursday, January 23, 2003 Agilent Restricted

Page 3

Centralized Testing for Network
Why Centralized Troubleshooting/Management?
• A real business benefit• Simplifies existing methods• Reduce MTTR (Mean Time to Repair)

Implementing Centralized Troubleshooting• Various Elements Required• Sample Scenarios

Thursday, January 23, 2003 Agilent Restricted

Page 4

Today’s Carrier Network:
Residential/Enterprise

AccessServices
Platforms

Edge/MetroCore/Long Haul

PSTN
CL5 VoIP
Gateway SS7>200λ DWDM
Optical Core
Optical λSwitch

Gb/TbRouter

Residential/SOHO/Enterprise via xDSL,
Cable, Fiber, fixedwireless
SiMobileInternet
via 3G RANSiEnterprise/Campus LAN
FR/ATM/Gb Ethernet
Switches/Routers VPN
gateway
Thursday, January 23, 2003 Agilent Restricted

Metro
OpticalNetworks

Tb Router/
Optical Switch

ATM/ MPLS/Access
GbE Switch
Switch/Router,
SoftSwitch,
MSPPs etc.
Server Farms,
Content Caches,
Hosted Apps, etc.
Page 5

Converged Wireless Multi-services:
Benefit?
2.5G and 3GBroadband
Wireless Access

PSTN

Internet CoreATM,
IP/MPLS,WDM, etc.

ADSL, Cable,FR, etc

Broadband
Wireline Access
xDSL or Cable

For 2 million subscribers at aconservative average fee of$55/month, this represents$110,000,000/monthThursday, January 23, 2003 Agilent Restricted

Page 6

Extreme Productivity
Improvement:
Drastically Reduce the Time it Takes to Start Solving the Problem
350
300

Minutes250

Traditional Netw ork
Troubleshooting

200

Centralized Netw ork
Troubleshooting

150
100
500
Symptom to first
Measurement

Problem Domain
Identification

Root Cause Isolation

Source: Agilent Customer Base, 2002

Traditional Network Troubleshooting

Centralized Network Troubleshooting

Problem symptoms detected to first measurement: 60 – 240minutes

Problem symptoms detected to first measurement: 5 – 15 minutes
Problem domain isolation: 20 – 40 minutes

Problem domain isolation: 120 – 300 minutes
Root Cause identification: 30 – 90 minutes
Root Cause identification: 60 – 180 minutes
Mean Time to Repair (MTTR): 55 – 145 minutes
Meant Time to Repair (MTTR): 240 – 720 minutes

Thursday, January 23, 2003 Agilent Restricted

Page 7

How Much Time?
Centralized Network Troubleshooting
Dispatching Engineer carrying portable tools

70% FasterBill

Verification of Solution

Dispatch/Install Solution
Solution Investigation &DesignProblem Qualification

40% Less in OPEX

Trouble Ticket Received
020406080100120140160180

Time in Minutes

Thursday, January 23, 2003 Agilent Restricted

Page 8

Implementing Centralized Network Troubleshooting forManaging the Various Components of Mission Critical
Networks
Operational Support System (OSS)
Help desk

Development
Tools

Network Management System
Network system
Database Applications
Enterprise Management System

CRM, ERP,
CSM, e-business,
Network Management,
Network Gurus

Centralized IP-Network Analysis
Network Troubleshooting Center
Managing Elements(SW Agent)

NetworkHand- AnalyzersHeld
Testers

RMON
ProbesManaging Elements(SW Agent)Managing Elements(SW Agent)Servers

Switches

Clients

Routers

Independent
Managing
SW Elements,
Appl. Engineers

MIBs, Agents,
Hardware,Technicians

NetworkThursday, January 23, 2003 Agilent Restricted

Page 9

Converged Network Architecture: What
if…
I could use the SW Agents already existing in my network elements?
PBX

VideoPOTS

Servers
1000

1000
11Gbps
GbpsSwitch
SwitchMedia
Media
Gateway
Gateway

WAN

T1/E1
DS3/E3OC-3/STM-1
OC-12/STM-4
Metro GigE

100
100100 Mbps Switch
100 Mbps Switch
100100Mbps
MbpsSwitch
SwitchHigh bandwidth users

IP Phone100

10/10010/100Mbps
MbpsHub
Hub

10/10010/100Mbps
MbpsHub
Hub
10010SW Agent
Medium bandwidth users

Thursday, January 23, 2003 Agilent Restricted

Low bandwidth users

Page 10

And What if I Could Also doTroubleshooting?
TDM/PCM(100101111)

Network Analyzer: Traffic Statistics
E-WAN

HDLC
WAN
1000

Media
Media
Gateway
GatewayATM

100
Frame Relay

HTTP/Telnet/H.323/SIP
TCP/UDP
IP/MSDP/PIM/RSVP
LLC/DSAP/SSAP/SNAP
Ethernet MAC

HTTP/Telnet/H.323/SIP
TCP/UDP
IP/OSPF/IGRP/BGP
ATM/FR/HDLC/PPP
Optical/Wire/WirelessThursday, January 23, 2003 Agilent Restricted

Tool Optimized for IP over Any Topology
Page 11

Centralized Network Analysis

Metro Multi-Tenant UnitsMTU Services:•Internet
hosting access and Web

Aggregated Traffic Stats

FSO•Programmable bandwidth•VPN connectivity

PSTN

10/10010/10010/100GigE
GigEIP
Network

SONET/SDH/10GigE

Thursday, January 23, 2003 Agilent Restricted

GigE
Hardware Probe

Page 12Aggregated Status from Mission Critical Areas

LANs

Thursday, January 23, 2003 Agilent Restricted

Switches

WANs

Page 13

Why is MPLS a “special” problem?
No unique source/destination pair in header as in IP packets
No unique VPI/VCI identifier like in ATM packets
Header for a “circuit” changes on traversing a node, hencechanges over every physical link - making it difficult to track
Only unique identifier is LSP ID or LSP “name” which isnetwork specific
The LSP ID is not carried in data packets, hence need tolook at MIBs
Above applies for MPLS VPNs in the same way (thoughinner label remains intact it is not intended to be looked at,
as it may not flow over a predetermined physical path)Thursday, January 23, 2003 Agilent Restricted

Page 14Looking into the MIB is a requirement
Info Source

MPLSMIBs

Data Collection

Central Server

Reporting
Tool

AgentServerRouter
Database

Thursday, January 23, 2003 Agilent Restricted

Page 15

End-to-End QoS for a VPN Environment
Customer Service View and Characterization
Customer-SpecificUtilization

Customer-SpecificUtilization
VPN End-to-End QoSdelivered by Provider
ProviderAccess Routers

Internet orCore NetworkPE

MPLSCEPE
Central Site

PECE
RemoteOffice

Customer
Edge Router--may or may not be
managed by Provider

CE

RemoteOffice
Customer
Edge Routers--may or may not be
managed by ProviderThursday, January 23, 2003 Agilent Restricted

Page 16

VPN Product Requirements
Service Management based on Class-of-Service for converged networks
CoS monitoring for Data (best effort, business, priority), Voice, Video
End-to-end monitoring of service health, per VPN with SAA active tests
Correlate performance events with Service and Customer impact

QoS Reporting per VPN, per application by CoS
Latency, Jitter, Packet Loss
Availability
In/Out traffic policy including drops
Actual traffic (bandwidth, e-2-e flow delivery ratios, via PerfE passive monitoring)??

Monitor and report on VPN Device HealthConfigurable device availability and performance data reports via PerfE MIB collector
Management platform health monitoring (PerfE, VPNSC, QoS Manager)

SLA management and Reporting by CoS
Active SLA management per VPN, customer
Real-time SLA alerting and reporting
Historical SLA reporting per customer, service

Performance alerting and analysis
Configurable alerting thresholds
Performance metric Baselines and trend reports
Configurable Notification and Action services
Thursday, January 23, 2003 Agilent Restricted

Page 17

MPLS/VPN Management Solutionwith optional Managed CE
QoS Manager Server
VPN Inventory Data

VPN Database

QoS Tests*
CE Data:• Utilization• Error Rates• Router Health• Latency• Packet Loss
• Jitter• DNS• LDAP• etc.

MIB Agent
PE Interface
Data:• Utilization• Error Rates• Router Health

CE* For Managed CE Services

PE

Data Collectors

QoS Tests
DNS, RADIUS, LDAP, etc

Full Mesh PE PE:• Latency• Packet Loss
• Jitter• Core I/F Utilization & Rates

MPLS
MPLS
Core
Core

Service Tests:• DNS• LDAP• RADIUS• etc.

PEDownstream PE• Latency• Packet Loss
• Jitter

CE:CE

Active Test
Thursday, January 23, 2003 Agilent RestrictedPage 18

Testing Services at the same time..
• Wireless Signaling• Voice and VoIP Signaling

Thursday, January 23, 2003 Agilent Restricted

Page 19

Use Model for Mobile and 2.5G and 3G
Networks
SS72G Cellular

Um

SCE
BTS

Abis

SMS

BSC

SUP
A

BSS

SCP
Core Network
GSM & GPRS
Gb

E

MSC

SMS-GMSCSMS– GMSCSMS-IWMSC

Iu-CS
DI

EIR
Gl

Uu

Gr

SGSN
RNC
Iu-PS

Uu

Iur

NODE B

HLR

STP

STP

STP

STP

Gs

3G Cellular

Iub

STP

C

VLR

Iub

STP

SMS - IWMSC
MAP

NODE B

SS7Gn

Gc

SGSN

LE

RNC

UTRANThursday, January 23, 2003 Agilent Restricted

Page 20

Testing & Troubleshooting VoIP Signaling
Need to Drill-Down to any ConnectionNode:209.218.18.72
UDP RTPTCP.H245
TCP Q931
UDP RAS• Measure Bandwidth used for each Node, Connection & Protocol• Measure the impact of data on the Performance of VoIP
• Measure the BW used by Voice and correlate to Voice Quality
Thursday, January 23, 2003 Agilent Restricted

Page 21

Find Signalling Problems quickly
1: Click on “call trace” to start

2: Configure & trace calls graphically

3: See all the signaling messages for each callThursday, January 23, 2003 Agilent Restricted

Page 22

Centralized Troubleshooting Summary
Don’t bring the network
engineer to the problem, …

OSS… bring the problem tothe network engineer!

EventsCentralTroubleshooting
Tool

For example,
Measure end
to end QoS

Analyzer
SW

Application Analyzer
HardwareprobesRMON Agent
10/100 Ethernet
10/100 Ethernet
Gigabit Backbone
Switch/Router
Thursday, January 23, 2003 Agilent Restricted

ATM/Frame Relay
IP Network

Gigabit Backbone
Switch/Router
Page 23

References• Calculating ROI for Centralized IP Network Analysis
Systems in Large Enterprise Networks
A White Paper by Leo De Rosa, Agilent Technologies• Network Troubleshooting (book), by Othmar Kyas
An Agilent Technologies Publication

Thursday, January 23, 2003 Agilent Restricted

Page 24

Questions & Answers