The workaround restored the counter I needed, showing UP status, but doesn't populate with any values, so I guess my only other option is SNMP.
What's frustrating is that though SNMP is enabled and working on the node itself, and we've verified the configuration for the correct blackberry SNMP registry keys, MIB location locally on the target node, and file paths for .dll's, I keep getting an 'OID is invalid' for the RIM library of .3530 when doing MIB or SNMP walks or searches from two separate Orion NPM instances.
I have the benefit of comparing the non-working node to a virtually identical Blackberry node, and config is identical for SNMP registry keys, MIB, and file paths for .dlls, and MIB library files on the local machine with a similar, but not exact BES version number.
I can walk and find the .3530 RIM directory on the working node from both NPM instances, and tried both NPM against the non-working one with no success.
Could there be a step missing, where one has to 'compile' the MIB's on the actual blackberry instance itself that was missed even though the BLACKBERRYSERVERMIB-SMIV2.mib is staged in the correct directory.
Both NPM instances share the same Solar Winds MIB.cfg file on the NPM instance, and I can 'walk' on the NPM instances and see the OID's I want, it should simply work, particularly since all the registry keys and paths show a successful SNMP blackberry installation on both target machines.
The OID I want to monitor is: .1.3.6.1.4.1.3530.5.2.0
Anything I'm missing here?