Improving Services for Telecommuters at AIM Speciality Health

Post on 06-Jan-2017

4.384 views 0 download

Transcript of Improving Services for Telecommuters at AIM Speciality Health

One Year InThousandEyes at AIM

AIM Specialty Health Healthcare Sector Benefits Portal US Market 50 Payors 40% of Fortune 50 42 Million Lives 5 sites 5,000 endpoints

WHOIS

Ivan Shepherd Networks &

Technical Security AS35961 Data Center Campus Application Delivery Technical Security Money Politics

Requirements✘Connect users across the continental US

✘“Plug and Play”

✘Data / voice experience comparable to campus user.

Everything was good, then we had to

go outside.

VOICE

DATA

SVIs

CONCENTRATOR

Telecommuter POC

Issues✘Data provider BGP stability

✘Users reporting terrible quality

✘Circuit utilization and 4.2.2.2 responding well. “We don’t see it”

Existing MonitoringPing SNMP CURL

Syslog NetFlow IP SLA

Issues

Issues

ThousandEyes Cloud Agent✘Gain visibility into service delivery

✘Gain visibility into BGP

✘Make informed decisions on remediation

Production Design✘Selected optimal carriers

✘Traffic engineering to avoid problematic transit

✘Data and visibility into operations

Telecommuter Production

Enterprise Agents✘Need comparable tools on private

transport

✘Meshed monitoring

✘Have visibility into delivery

Endpoint Agents✘Need per user data

✘Monitor and assess quality of application performance

✘“Plug and Play” persistent data

Endpoint Agents✘Deployed via MSI

✘200 stations in testing

✘ W@H is the primary use case

Endpoint Deploy✘Approximately 200 currently deployed

Endpoint Deploy✘Approximately 200 currently deployed

Endpoint – Current state✘Visibility into connection quality

✘ Public path obscured by private IP transit

✘Grouping and alerting

Endpoint – Near term✘Address browser compatibility mode

issues

✘ Leverage tracking beacon to get W@H public telemetry

✘Metrics and reporting

Questions?