Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

IP SLA views

All of our IP SLA web and TCP connect operation views have changed to VOIP UDP jitter views recently. Not sure how this happened, we upgraded to 10.1 and IPSLA 3.5.1 a few weeks ago.

What is the easiest way to change the operations back to the correct views without editing each one?

TIA

Find more posts tagged with

Accepted answers

JasonFerree

You’ll need to edit the IP SLA views for your account. On the web page, go to settings then account manager. Select your account and edit. Scroll to the bottom and look for the + for IP SLA. Once expanded you’ll see different views for each operation, set them to default. It sounds like they are set to VoIP right now. If that doesn’t resolve it you’ll want to open a support ticket.

All comments

tom.rybka

The problem you are describing sounds very similar to the one we have already observed, in order to verify that I would like to ask you several questions:

1. Which version of Orion have you upgraded from?

2. Do I understand correctly that detail views for all types of operations show VoIP UDP Jitter resources now? Can you see VoIP UDP Jitter in the title of the page?

Thanks.

FormerMember

Thanks for the response.

1. Upgraded from Orion 10 sp1 to 10.1. I do recall updating IPSLA to 3.5.1 prior to the Orion upgrade.

2. Correct, all operations now have VOIP UDP jitter resources. At the top the description is still correct, e.g. HTTP Operation Detail - sitex to Internet. Under customize page the names are changed to "IP SLA UDP Jitter Operation Details View". The name of the view is IPSlaOperationsDetails.

tom.rybka

Updating IPSLA first shouldn't cause the problem, anyway there is probably something wrong happening, so I recommend you to open a support ticket for this issue, we will need you to grab diagnostics for your installation, so that we can explore the situation in more detail.

Thanks.

netwiz2007

We have the same issue, I believe it happened after upgrade to NPM 10.1.1 sp1 - has anyone heard anything as to how this can be fixed?

Thanks