Successfully Upgrade Cisco

CallManager 4.x to 6.x/7.x

with a Proven Framework
September 24th , 2009
 CIPTUG Webinar

Presenters
Gurmeet S. Lamba David Roberts
VP Product Development
Director, Product Managem
larus Systems Clarus Systems

2
© Copyright 2009. Clarus Systems, Inc–
 Agenda

• Context
• Core Migration Process, Issues
• Solution Space
• Real World Issues Observed
• The Framework – Process, Metrics
• Supporting Technology
• Benefits
• Q&A

3
© Copyright 2009. Clarus Systems, Inc–
 Context

A Successful Migration from Cisco CallManager 4.x to 6.x/7.x Requires

I. Executing on Cisco’s II. Benchmarking, Using

recommended steps for Metrics at Critical
migration. Steps, Testing,
Testing, Testing

Cisco Documentation

This Webinar presents a Framework:

A set of overlay Processes and Metrics that

maximize the probability of a successful
migration.
4
© Copyright 2009. Clarus Systems, Inc–
 CallManager 4.x to 7.x ‘Core’ Upgrade
Process

The ‘core’ upgrade process is prescriptive & well defined ….

Backup Apply Install DMA Build DMA Tar

(BARS) Upgrade Utility On Pub File, Backup.

Install CUCM
Restore Test
6.x/7.x

… but there are many sources of potential problems:

OS/Platform:
Scale: End Points, Locations
Windows -> Linux
Deployment Topology
Inherent Complexity of IPT
Changes
Visibility (or lack of)
UC Applications
into Service Levels

Version Compatibilities
5
© Copyright 2009. Clarus Systems, Inc–
 Real World Issues Observed

CfwdAll not carried over after upgrade

Every migration
End user accounts did not migrate
shows some unique
set of issues
Previously registered devices did not
recover

ntegration with Unity is no longer working

Problems exist even
before a migration
Fax lines are down starts

Main branch 800 numbers are unreachable

.
. 6
. © Copyright 2009. Clarus Systems, Inc–
 Solution Space

The impact of these problems on end-users

can be reduced / eliminated

By early detection & correction

Enabled by best practices encapsulated in a framework

Using well defined metrics and processes

Supported by technology for automation &

standardization

7
© Copyright 2009. Clarus Systems, Inc–
 The Basics: Questions to Ask Yourself

Pre-Migration Migration Post-Migration

•What are your Assets ? •Can I quickly get a broad•Is everything working
•What kind of Traffic are youhealth check ? equal or better ?
handling ? •Are all my end-points
•What SLA are you signed up back & correctly registered ?
for ?
•What Service Level are you
actually delivering ?

Validate

Monitor

Benchmark ‘Today’s’
System

8
© Copyright 2009. Clarus Systems, Inc–
 The Framework for a Successful Upgrade

Pre-Upgrade Upgrade Post-Upgrade

Benchmark Monitor Validate

#4 Real-
#1 Service Analysis Time #7 Service Analysis
Characterize Traffic Patterns Availabilit Changes in Traffic ? Why ?
y
Monitor Critical
Components
#2 Service Availability Corrective Action
#6 Service Availability
Regression
Test/Validate Existing Deployment Validation
Did Any Feature Break ?

#3 Configuration Analysis#5 Configuration Analysis

Existing Inventory / Set-Up Did the Configuration Change ?

9
© Copyright 2009. Clarus Systems, Inc–
 Pre-Upgrade: Benchmark (-10 to -1 Days)

#1: Service Analysis

Monitor & Characterize Daily
Traffic Patterns
• Call Volumes
– Peak Loads, Daily Call Volume
• Call Failures
– Volumes, Cause Codes for
Failures
• Voice Quality Trends
– Max/Min, Daily Trends
• Traffic Distribution
– Route Lists, Route Groups,
Gateways, Trunks

Corrective Action
Regression Validation
10
© Copyright 2009. Clarus Systems, Inc–
 Pre-Upgrade: Benchmark (-10 to -1 Days)

#2: Service Availability

Test & Validate whether you are
meeting your current SLA
• DID for each location

• Inter-Office calling

• Outbound Call Permissions

– Local, National, I18n, Toll-Free

• Forward to Voice Mail
• Conference Bridge
• Soft Key Functions
– Transfer, Park, Conf …
• Capacity: Voice Mail & Gateway
Port Loading
Corrective Action
Regression Validation
11
© Copyright 2009. Clarus Systems, Inc–
 Pre-Upgrade: Benchmark (-10 to -1 Days)
#3: Configuration Analysis

Review Inventory & Configuration

• Registration Status & Counts: Phones,
Gateways, CTI Ports
• System: Device Pools, Enterprise & Svc
Parameters, Installed Apps
• Route Plan: Route Patterns, Lists,
Groups, Translation Patterns
• Media: Conference Bridges, Media Resc
Groups, Term Pts
• Voice Mail: Subscribers, Ports
• Devices: Phone Config
• Services: Running

Corrective Action
Regression Validation
12
© Copyright 2009. Clarus Systems, Inc–
 Pre-Upgrade: Benchmark (-1 day)

Archive Service Baseline Before the Upgrade

• Service Analysis:
– Save the daily call patterns for post upgrade comparison
• Service Availability:
– Save the test plans and results for post upgrade
comparison.
• Configuration Analysis:
– Save all the inventory/configuration reports for post
upgrade comparison

t e
da ze
i
l ee ’
a
V fr ally d
e
th ctu ene
‘a p p
ha ! 13
© Copyright 2009. Clarus Systems, Inc–
 Upgrade: Monitor (+0 day)

#4: Real Time Availability

• Monitor Critical Components:
– Server Health, Services
– Gateways, Trunks
– Media Resources
• Monitor Device Registration:
– Phones
– Voicemail Ports
– CTI Route Points
– Gateways, Trunks
– Gatekeepers

14
© Copyright 2009. Clarus Systems, Inc–
 Post-Upgrade: Validate (+1 day)

#5: Validate new Configuration

• Compare the pre vs. post upgrade

Did The Inventory & Configurations
Configuration • Expect some changes in:
Change ? – Enterprise/Service Parameters
– Phones / Device Defaults
• Scrutinize any changes in:
Configuration – Number of Registered Devices
4.x = (phones, gateways ..)
Configuration – Route Plan, Routing Devices
7.x
– Media, Voice Mail

Corrective Action
Regression Validation

15
© Copyright 2009. Clarus Systems, Inc–
 Post-Upgrade: Validate (+1 day)

#6: Validate Service Availability

• Execute the same tests post

Are all end-user upgrade
features working • Compare Results
the same ?
• There ‘should’ be no change in
the base functionality: But if
you haven’t tested, there may
Test Results be something broken:
4.x =
– Changes made outside your
Test Results
7.x
control: Callmanager or
ancillary components
– Upgrade Errors
Corrective Action – Interoperability: IPCC, Unity
etc.
Regression Validation

16
© Copyright 2009. Clarus Systems, Inc–
 Post-Upgrade: Validate (up to +30 days)
#7: Service Analysis – Validate Traffic

• Monitor Call Traffic over the next few

weeks
Is there a change • Look out for changes in ‘daily’ patterns:
in Calls /
Traffic Patterns ? – Business Hour Call volumes
– Failed Calls, Usage, Voice Quality
– Call Distribution across Gateways
• This may not be a precise analysis,
Call Flows hence look for un-explained trends.
4.x = • Measure at all levels:
Call Flows – End User -> Location -> Cluster ->
7.x Enterprise

Corrective Action
Regression Validation

17
© Copyright 2009. Clarus Systems, Inc–
 Post Upgrade: Continuous Validation /
Monitoring

Continue Monitoring the ‘new’ CallManager deployment

Components going Are These Upgrades

through Upgrades / Coordinated ?
Patches: • Are they all in ‘your’
• UC Applications control & supervision ?
• Unified Messaging • Can failures in any
component impact your
• Directory & Email
Voice / Communications
Servers Service Level ?
• Gateways, Routers
• Trunks …
24x7 Policy Based Continuous Monitoring /
Alerting for Configuration Changes and
Service Availability is necessary
18
© Copyright 2009. Clarus Systems, Inc–
 Summary: Framework for Successful Cisco
CallManager Upgrade

Pre-Upgrade Upgrade Post-Upgrade

Benchmark Monitor Validate
• Service Analysis:
– Benchmark Traffic: Call / Traffic patterns pre and post upgrade
• Service Availability:
– Benchmark Availability: Test both before and after the upgrade
– End user focused testing from the endpoints (i.e. phones)
• Configuration Analysis:
– Configuration Reports comparing pre vs post upgrade gives insights intoRegression Validation
Corrective Action

inventory and settings. Use a CMDB targeted for IP Telephony.

• Real-time views of server health & device registrations
– Accelerates an upgrade and quickly isolates common problems
• Continuous Monitoring:
– Upgrades are happening all the time. Utilize 24x7 Policy Based Monitoring
for Configuration Changes and Service Availability

19
© Copyright 2009. Clarus Systems, Inc–
 Technology supporting this Framework:
ClarusIPC®
End-to-End Cisco VoIP Management
Four Pillars that Empower Unified Communications
I. Automated Testing
– If you haven't tested it, it's probably broken. Exercise all the functionality that the
user relies on as well as integrating into business processes.
– Troubleshooting & Diagnostics: Providing troubleshooting and remote phone
applications that allow Tier-1 help desk personnel become more productive for voice.
I. Performance Management
– Policy-based, sophisticated rules engine that alerts on problems in voice quality and
service, performance, security, and KPI’s.
I. Configuration Management
– Assists users in all aspects of Configuration Management including routinely
discovering data to populate CMDB, automating inventory reports, and alerting on
non-compliant configuration changes.
I. Business Intelligence
– Data collection, reporting & analytics of inventory, tests and KPI’s that Business and
IT can leverage to reduce costs and create competitive advantages.

20
© Copyright 2009. Clarus Systems, Inc–
 Benefits

Ensure a successful migration using these

processes, metrics and supporting technology

 Dramatically Improve Service Availability and Performance

Post Migration for your End Users

 Reduce the time taken for upgrade

 Reduce the resources needed to manage the upgrade

 Have confidence: before, during and after the upgrade

21
© Copyright 2009. Clarus Systems, Inc–
 Clarus Systems

Strength & Foundation

• Leader in Products & Services for

Management of Enterprise IP
Clarus Systems has Telephony
validated many
• Comprehensive approach of
large, complex Cisco
Active Testing, Passive
CallManager Monitoring and Analytics gives
upgrades, Un-paralleled Confidence
uncovering and • Complete Life Cycle Coverage:
resolving hundreds Deployment, Operations and
of problems before Upgrades / Optimization.
end users getting • CIPTUG End User Recognition:
impacted 2008 “BoD Choice” & 2007 “Best
Tools” Awards
• Strategic Partnerships with Cisco,
22
HP © Copyright 2009. Clarus Systems, Inc–
 Questions & Comments

For more information, visit

www.clarussystems.com
or contact:
sales@clarussystems.com

2200 Bridge Parkway 2200 Bridge Parkway

Gurmeet S. Suite 101
David Roberts Suite 101
Lamba Redwood City, CA 94065 Director, Product Redwood City, CA 94065
SVP, Product Phone: 650.632.2877 Management Phone: 650.632.2852
glamba@clarussystems.com droberts@clarussystems.com
Development

23
© Copyright 2009. Clarus Systems, Inc–