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

IPSLA is not recolecting information and have to shutdown all services for fix it

Hello friends. Hope you can help me with this.

i have NPM SLX running for 915 nodes. 305 of that nodes have 2 IPSLA operations running (UDP Jitter and VoIP Jitter).

Sometimes the IPSLA stops recollecting information from nodes, even if the nodes are up, all at the same time. I have to go to the Orion service manager and shutdown all and then start all for IPSLA show me again statistics. last time i have to do this was last Friday (11/2/11) and today again at 9:15 am.

I dont know if is related, but every time i have to add an operation inside the IPSLA i have to do this procedure, that was given to me the fist time i have a frozen process of adding an operation (when i had a support contract):

To replace a corrupted Job Engine schedule data file:
1. Click Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
2. Stop all services. You may need to use Task Manager to stop the Netperfmon process.
3. Navigate to C:\Documents and Settings\All Users\Application Data\SolarWinds\JobEngine\Data\, and rename the existing JobEngine35.sdf file to JobEngine35.old. Then rename JobEngine35 - Blank.sdf to JobEngine35.sdf
4. Remove the read-only atttribute from the new JobEngine35.sdf
5. Open the Orion Service Manager again, and start all services again.

Find more posts tagged with

Accepted answers

tom.rybka

Angel24,

I think we need to take a closer look at your system. Please, open a support ticket and send a diagnostics package which you should create when you stop seeing graphs again.

All comments

tom.rybka

Angel24,

I am afraid we need a little more information to help you. I have a couple of questions for the start:

1. Which version of IPSLA Manager do you use?

2. Do you need to restart all the services or just "SolarWinds Orion Module Engine" service would help?

3. Do you have operations created in IPSLA Manager or do you monitor manually created operations? (I assume the first case, but asking for me to be sure.)

4. You mentioned the procedure of replacing JobEngine35.sdf file due to problems with adding operations - can you please describe the problem more? E.g. this happens no matter if you are adding one or more operations, which step is frozen, etc.

Thanks.

Angel24

Hi Tomas. Thanks a lot for reply.

1. This is the version of my software: SolarWinds Orion Core 2010.1.0, IPSLAMGR 3.5, NCM 6.0, NPM 10.0.0, NTA 3.6.

2. I usually restart all the services. I havent proved restart the solarwinds orion module engine only.

3. I monitor manually created operations on my routers: one for UDP Jitter and one for VoIP Jitter

4. This problem always present when pass more than three weeks i replaced the JobEngine35. I added fist the nodes (new sites) and then, when i go to the wizard and select Monitor existing operation , and then Manually enter operation numbers , i select the nodes, then its frozen when it test the credentials. Can be all nigth in that state. This happens even if the node is up and the SNMP credentials are correct. It doesnt matter if i add one or multiple operations.

tom.rybka

Angel24,

Thanks for the information. I assume you configure your operations manually with forever lifetime, i.e. you don't need to re-configure them again they stop collecting data in IPSLA Manager.

Then, for better diagnostics, it would be good to see which service restart helps. I would be interested in SolarWinds Orion Module Engine or SolarWinds Job * services.

If this information doesn't help us, I recommend to open a support ticket and send a diagnostics package for closer look.

Angel24

Hi again

Yes, my operation are manually and live forever like these:

ip sla 845

udp-jitter «SALIDA_NODOS_LAN» 17000 source-ip «IP_WAN_871» codec g729a codec-numpackets 100 codec-size 100 advantage-factor 20

tos 184

timeout 5000

frequency 300

ip sla schedule 845 life forever start-time now

Today i noticed that i have t restart the services, so i began to restart the module engine: result... not fixed.

Then i restarted both Job services.. result, not fixed. Then i restarted the web, result not fixed. I restarted the Network performance and not fixed yet. So, i go to restart everything and it works.

So...conclusion, i have to restart everything.

Please help me. What else can i do?