ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins.Read more for important details.
Ensign Ensign
Ensign
289 views

NNMi report error like this: Configured Filter MIB Variable is a scalar MIB: not applicable for MIB

Jump to solution

I want collect datea from LR77v2 like this:

.iso.org.dod.internet.private.enterprises.conel.mobile.mobileSignalStrength

with MIB Browser it works but my custom poller not.

This Error occurs: Configured Filter MIB Variable is a scalar MIB: not applicable for MIB 

Berst regards

Bernd

Labels (1)
1 Solution

Accepted Solutions
Ensign Ensign
Ensign
[famundt@bems-ovnnm-01 ~]$ sudo /opt/OV/bin/nnmsnmpwalk.ovpl -T 10.197.34.1 mobile
.1.3.6.1.4.1.30140.4.1.0 : INTEGER: 14
.1.3.6.1.4.1.30140.4.2.0 : OCTET STRING- (ascii): 26201
.1.3.6.1.4.1.30140.4.3.0 : OCTET STRING- (ascii): 1CBF800
.1.3.6.1.4.1.30140.4.4.0 : OCTET STRING- (ascii): 1300
.1.3.6.1.4.1.30140.4.5.0 : INTEGER: -93
.1.3.6.1.4.1.30140.4.6.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.7.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.8.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.9.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.10.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.11.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.12.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.13.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.14.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.15.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.16.0 : Timeticks: (42792700) 4 days, 22:52:07.00
.1.3.6.1.4.1.30140.4.17.0 : Counter: 1615971445
.1.3.6.1.4.1.30140.4.18.0 : Counter: 0
.1.3.6.1.4.1.30140.4.19.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.20.0 : IpAddress: 10.69.125.185
.1.3.6.1.4.1.30140.4.21.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.22.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.23.0 : INTEGER: 4
.1.3.6.1.4.1.30140.4.24.0 : OCTET STRING- (ascii): Telekom.de
.1.3.6.1.4.1.30140.4.25.0 : OCTET STRING- (ascii): 0032
.1.3.6.1.4.1.30140.4.26.0 : INTEGER: -8
.1.3.6.1.4.1.30140.4.27.0 : INTEGER: 9
.1.3.6.1.4.1.30140.4.28.0 : INTEGER: 0

View solution in original post

7 Replies
Micro Focus Expert
Micro Focus Expert

Hi,

Which type of collection it is - Bulk or Instance? Do you define any Filter variable?

https://docs.microfocus.com/itom/Network_Node_Manager_i:2020.11/SettingsCustomPollCollect

I guess, your collection should be "single" Instance, no Filter variable (or that is "self" filtering  trick to apply in some cases).

BR,

Ensign Ensign
Ensign

Hi thanks for your question:

This is the snmp-mib-defination

mobileSignalStrength OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION ""
::= { mobile 5 }

Yes in my custom poller I define a filter.

Best Regards

Bernd

Micro Focus Expert
Micro Focus Expert

If there is no instance, no need to define a filter. Please let me see the nnmsnmpwalk.ovpl -T <IP> mobile

Ensign Ensign
Ensign
[famundt@bems-ovnnm-01 ~]$ sudo /opt/OV/bin/nnmsnmpwalk.ovpl -v 2c -c luft0815guete 10.197.34.1 mobile
mobileTechnology.0 : INTEGER: 14
mobilePLMN.0 : OCTET STRING- (ascii): 26201
mobileCell.0 : OCTET STRING- (ascii): 1CBF800
mobileChannel.0 : OCTET STRING- (ascii): 1300
mobileSignalStrength.0 : INTEGER: -92
mobileChannelN1.0 : OCTET STRING-
mobileSignalStrengthN1.0 : INTEGER: 0
mobileChannelN2.0 : OCTET STRING-
mobileSignalStrengthN2.0 : INTEGER: 0
mobileChannelN3.0 : OCTET STRING-
mobileSignalStrengthN3.0 : INTEGER: 0
mobileChannelN4.0 : OCTET STRING-
mobileSignalStrengthN4.0 : INTEGER: 0
mobileChannelN5.0 : OCTET STRING-
mobileSignalStrengthN5.0 : INTEGER: 0
mobileUpTime.0 : Timeticks: (42748000) 4 days, 22:44:40.00
mobileConnect.0 : Counter: 1615971445
mobileDisconnect.0 : Counter: 0
mobileCard.0 : INTEGER: 0
mobileIPAddress.0 : IpAddress: 10.69.125.185
mobileLatency.0 : INTEGER: 0
mobileReportPeriod.0 : INTEGER: 0
mobileRegistration.0 : INTEGER: 4
mobileOperator.0 : OCTET STRING- (ascii): Telekom.de
mobileLAC.0 : OCTET STRING- (ascii): 0032
mobileSignalQuality.0 : INTEGER: -8
mobileCSQ.0 : INTEGER: 10
.iso.org.dod.internet.private.enterprises.conel.mobile.28.0 : INTEGER: 0
0 Likes
Micro Focus Expert
Micro Focus Expert

Hello Bernd,

Why do you put communication settings into an argument of command line - this is worrying point, as there is no need to do so when NNMi Communication settings are correct. The nnmsnmpwalk retrieves everything from NNMi DB.

You don't need to specify also a Filter variables for this collection, as that is a single-instance variable, each of those. To each you need to have one collection, and, the collection variable should be till the end with .0.

BR,

0 Likes
Ensign Ensign
Ensign
[famundt@bems-ovnnm-01 ~]$ sudo /opt/OV/bin/nnmsnmpwalk.ovpl -T 10.197.34.1 mobile
.1.3.6.1.4.1.30140.4.1.0 : INTEGER: 14
.1.3.6.1.4.1.30140.4.2.0 : OCTET STRING- (ascii): 26201
.1.3.6.1.4.1.30140.4.3.0 : OCTET STRING- (ascii): 1CBF800
.1.3.6.1.4.1.30140.4.4.0 : OCTET STRING- (ascii): 1300
.1.3.6.1.4.1.30140.4.5.0 : INTEGER: -93
.1.3.6.1.4.1.30140.4.6.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.7.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.8.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.9.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.10.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.11.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.12.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.13.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.14.0 : OCTET STRING-
.1.3.6.1.4.1.30140.4.15.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.16.0 : Timeticks: (42792700) 4 days, 22:52:07.00
.1.3.6.1.4.1.30140.4.17.0 : Counter: 1615971445
.1.3.6.1.4.1.30140.4.18.0 : Counter: 0
.1.3.6.1.4.1.30140.4.19.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.20.0 : IpAddress: 10.69.125.185
.1.3.6.1.4.1.30140.4.21.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.22.0 : INTEGER: 0
.1.3.6.1.4.1.30140.4.23.0 : INTEGER: 4
.1.3.6.1.4.1.30140.4.24.0 : OCTET STRING- (ascii): Telekom.de
.1.3.6.1.4.1.30140.4.25.0 : OCTET STRING- (ascii): 0032
.1.3.6.1.4.1.30140.4.26.0 : INTEGER: -8
.1.3.6.1.4.1.30140.4.27.0 : INTEGER: 9
.1.3.6.1.4.1.30140.4.28.0 : INTEGER: 0

View solution in original post

Ensign Ensign
Ensign

Thanks for yor help, the custom poller works fine.

Best Regards

Bernd

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.