Hands-On Lab: Quickly Identify the Fault Domain – Is It the Network, the Server or the Application?

ca Opscenter
Hands-On Lab: Quickly Identify the
Fault Domain – Is It the Network,
the Server or the Application?
Rob Webb
OCX67L #CAWorld
Advisor, Pre-Sales
CA Technologies

2 © 2014 CA. ALL RIGHTS RESERVED.
Abstract
Learn how to leverage CA Application Delivery
Analysis to simplify and shorten the time it
takes to identifying the performance fault
domain for effective problem triage and
reduced MTTR. (“Hands-On Lab Prerequisite:
Demo to Prepare for Hands-On Lab: Quickly
Identify the Fault Domain – Is It the Network,
the Server or the Application?” is a required
prerequisite for attending this lab.)
Rob Webb
CA Technologies
Advisor, Presales

Navigation
 Log into CAPC Demo
– http://pm.demo.ca.com
– User = anpm_u<n>
 Where <n> = your assigned pc number
– Password = anpmuser
 Dashboards / ANPM
– Applications
– Sort “Application Name” Column
 Descending Order ^

CA Performance Center
 Time Settings
– Yesterday
 08:00 - 16:00
Navigation

CA Performance Center
Navigation

TIXCHANGE T-1 Web (8080) Fault Domain
Tier-1
Clients
NETWORK SERVER/APPLICATION
Tier-1
Web

TIXCHANGE T-2 App (8080) Fault Domain
Tier-2
App
Tier-2
Clients

TIXCHANGE T-3 DB (3306) Fault Domain
Tier-3
DB
Tier-3
Clients

Well Defined/Mapped Applications
Tier-1
Tier-2
Tier-3

Poorly Defined Applications
What happens when the applications are already defined and
mapped out?
 Application Dependency Mapping

CA ADA Data Source
 Drill into “Links: Engineering…”
Filtered on
TIXCHANGE T-1 Web
(8080)
Drill into
“Links Engineering…”

CA ADA Engineering
 Go to
– Engineering
 Applications
– Drill Into TIXCHANGE T-1 Web (8080)

ADA User Impact
TIXCHANGE T-1 Web (8080)

08:30 Issue
 It’s the Network
– Retransmission Delay
– Network Round Trip Time
 Drill into “Network” link under Retransmission Delay
– Which Network is having issues?

Unknown Application
What if all we knew was that we have a user complaining about
performance when going to a particular server (or servers)?
 Let’s assume we do not know anything about this particular
application.
– Other than the server the users are accessing
– tixchange-web1

Find the First Server

Issue at 13:20
We already identified the network issue.

Server Becomes Client
 Copy the Server Name.
 Go to Settings.
 Remove the Existing Filter.
 Paste the Server Name into the Network Search field.
– Search and Select the Server as the “Network”.
 Click OK to Apply the New Filter.

Network = tixchange-web1

High SRT Dependency
 Note that with tixchange-web1 now used as a Network filter
– High SRT with tixchange-web1 as a client
– Click on Server Link inside of Server Response Time view
 Lists all severs tixchange-web1 was accessing during time referenced

Server List for tixchange-web1
Independent of any Application/Ports

Server = tixchange-app1

Network = tixchange-app1
 Now repeat the above process to look at the servers
tixchange-app1 has as dependencies
 Settings
– Clear existing filters.
– Search on tixchange-app1 as the “Network”.

Click Server Link to See Dependencies
Number of calls (observations) to DB increased significantly.

DB Client
 The Database Client is running on the App Server.
 The number of calls to the DB drastically increased during said
event.
 Fault Domain
– T-2 Client / T-3 Database

For More Information
To learn more about DevOps, please visit:
http://bit.ly/1wbjjqX
Insert appropriate screenshot and text overlay
from following “More Info Graphics” slide here;
ensure it links to correct page
DevOps

For Informational Purposes Only
© 2014 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty.
Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual
results may vary.
Terms of this Presentation

Hands-On Lab: Quickly Identify the Fault Domain – Is It the Network, the Server or the Application?

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Hands-On Lab: Quickly Identify the Fault Domain – Is It the Network, the Server or the Application?

Similar to Hands-On Lab: Quickly Identify the Fault Domain – Is It the Network, the Server or the Application? (20)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Hands-On Lab: Quickly Identify the Fault Domain – Is It the Network, the Server or the Application?