Juniper RPM probe monitoring

Hi all

I have a Juniper SRX240 with a set of SLA probes that I want to monitor. Until VNQM supports Juniper, I have been trying to use UnDP's without much success. I can poll the JUNIPER-RPM-MIB and obtain the values from the tables but I can't find a way to correlate the label to a probe name. Has anyone had much success with this? Or suggest an alternative?

There is a feature request for this as well but as far as I know there is no ETA or guarantee of implementation. http://thwack.solarwinds.com/ideas/1297

jnxRpmResCalcAverage - Label	jnxRpmResCalcAverage
7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.1.1	563
7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.2.1	563
7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.4.1	1024
8.105.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.1.1	500
8.105.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.2.1	500
8.105.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.4.1	2224
9.108.100.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.1.1	780
9.108.100.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.2.1	780
9.108.100.114.45.118.115.115.48.49.10.98.101.115.116.101.102.102.111.114.116.4.1	2228

Thanks

Find more posts tagged with

sla

juniper

vnqm

probe

Accepted answers

All comments

sja

I know :-) ....

If VNQM will be open to "non cisco proprietary features" :-)

so that one is very handy to have.

The same as SIP & Nortel CS MS lync.

/SJA

ahmed.soliman

till the feature request is fulfilled by solarwinds, what is the problem to monitor/alert/report on the UnDP results ?

shuth

This is now going back a few years and I had to dig up some old emails for this content but hopefully the below makes a bit of sense.

It's a bit of an admin nightmare to monitor these probes via UnDPs. For some reason in the Juniper MIB they don't have a table of the probe name that you can link to the probe statistics - the OID itself contains the probe name. Each of those numbers above correspond to the probe name.

There are a couple of tables to get the Probe Owner and Test Names.

jnxPingResultsOwnerIndex - Probe Owner
jnxPingResultsTestName - Test Name
jnxRpmResCalcAverage - latency, but the sub-OIDs are decimal conversions of the ASCII name
jnxRpmResCalcPkToPk - jitter, but the sub-OIDs are decimal conversions of the ASCII name
jnxResSumPercentLost - packet loss, but the sub-OIDs are decimal conversions of the ASCII name

If you want to view the latency, jitter, and packet loss information then you need separate UnDPs for each probe/test.

In my original post I listed some OIDs for the RTT;

7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.1.1

7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.2.1

7.98.110.101.45.114.48.49.10.98.101.115.116.101.102.102.111.114.116.4.1

jnxRpmResCalcAverage."bne-r01"."besteffort".1.1 = 563

jnxRpmResCalcAverage."bne-r01"."besteffort".2.1 = 563

jnxRpmResCalcAverage."bne-r01"."besteffort".4.1 = 1024

Effectively, you need to create a custom UnDP for each RPM probe, test, and statistic and with a lot of probes and tests, you will end up needing hundreds of UnDps.

And then the subsequent alerting for each probe...

Reporting and charts. Also not fun.

ahmed.soliman

thx man

sja

Please Vote

They can't ignore that feature request for ever..

/SJA