What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

APC Infrastruxure and Netbotz rack monitor

Votes:

0

Has anyone successfully figured out a way to monitor a Netbotz rack monitor that is connected to APC Infrastruxure central? I am looking to get the environmental data from the Netbotz but am running into a few issues.

  1. The netbotz is on a network that can only be accessed via the proxy connection through Infrstuxure central. So the netbotz is on an isolated network 192.168.0.0 /24 and the Infrstuxure central device is accessed via the normal LAN network (10.1.1.0 /24). From what I know, you can only manage the Netbotz through Infrstuxure central.
  2. There doesn't seem to be a clear MIB for Netbotz device through APC even if I could connect directly to it.

Any suggestions?

apc netbotz snmp

Created on Jun 24, 2016 2:37:51 PM

Last change on Jun 27, 2016 5:31:54 AM by Luciano Lingnau [Paessler]



5 Replies

Votes:

0

Hello Keith,
thank you for your post.

I'm not familiar with APC Infrastruxure central, but can it be monitored/queried with SNMP?

If it offers SNMP Support, enable SNMP. Then download our latest SNMP Tester, run it on the PRTG Host (or host of the Remote Probe), and perform a Walk against the target device providing the "1.3.6" OID (without quotes) as parameter. This will tell you which OID's it responds to and may allow you to locate an appropriate MIB file. Feel free to share the output (if any).

Alternatively, check whenever you can use an additional vNIC on one of your PRTG Probes to ingress directly on the LAN/VLAN of the 192.168.0.0/24 isolated network, then monitor it as usual.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Jun 27, 2016 11:55:00 AM by Luciano Lingnau [Paessler]



Votes:

0

Luciano,

I have performed the walk like you said and this is the first part of the output (the Walk produced 5,500 lines of results) :

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: PRTG Interface: 10.1.1.15
7/1/2016 10:33:22 AM (2 ms) : Device: 10.1.1.12
7/1/2016 10:33:22 AM (4 ms) : SNMP V2c
7/1/2016 10:33:22 AM (5 ms) : Walk 1.3.6
7/1/2016 10:33:22 AM (8 ms) : 1.3.6.1.2.1.1.1.0 = "Linux localhost.domain.office 2.6.25-14.fc9.x86_64 #1 SMP Thu May 1 06:06:21 EDT 2008 x86_64" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (11 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.318.1.3.25.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (13 ms) : 1.3.6.1.2.1.1.3.0 = "1537979957" [ASN_TIMETICKS]
7/1/2016 10:33:22 AM (16 ms) : 1.3.6.1.2.1.1.4.0 = "" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (18 ms) : 1.3.6.1.2.1.1.5.0 = "localhost.domain.office" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (20 ms) : 1.3.6.1.2.1.1.6.0 = "" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (23 ms) : 1.3.6.1.2.1.1.8.0 = "5" [ASN_TIMETICKS]
7/1/2016 10:33:22 AM (35 ms) : 1.3.6.1.2.1.1.9.1.2.1 = "1.3.6.1.6.3.10.3.1.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (39 ms) : 1.3.6.1.2.1.1.9.1.2.2 = "1.3.6.1.6.3.11.3.1.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (42 ms) : 1.3.6.1.2.1.1.9.1.2.3 = "1.3.6.1.6.3.15.2.1.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (45 ms) : 1.3.6.1.2.1.1.9.1.2.4 = "1.3.6.1.6.3.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (49 ms) : 1.3.6.1.2.1.1.9.1.2.5 = "1.3.6.1.2.1.49" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (52 ms) : 1.3.6.1.2.1.1.9.1.2.6 = "1.3.6.1.2.1.4" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (55 ms) : 1.3.6.1.2.1.1.9.1.2.7 = "1.3.6.1.2.1.50" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (59 ms) : 1.3.6.1.2.1.1.9.1.2.8 = "1.3.6.1.6.3.16.2.2.1" [ASN_OBJECT_ID]
7/1/2016 10:33:22 AM (63 ms) : 1.3.6.1.2.1.1.9.1.3.1 = "The SNMP Management Architecture MIB." [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (67 ms) : 1.3.6.1.2.1.1.9.1.3.2 = "The MIB for Message Processing and Dispatching." [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (71 ms) : 1.3.6.1.2.1.1.9.1.3.3 = "The management information definitions for the SNMP User-based Security Model." [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (76 ms) : 1.3.6.1.2.1.1.9.1.3.4 = "The MIB module for SNMPv2 entities" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (81 ms) : 1.3.6.1.2.1.1.9.1.3.5 = "The MIB module for managing TCP implementations" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (86 ms) : 1.3.6.1.2.1.1.9.1.3.6 = "The MIB module for managing IP and ICMP implementations" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (90 ms) : 1.3.6.1.2.1.1.9.1.3.7 = "The MIB module for managing UDP implementations" [ASN_OCTET_STR]
7/1/2016 10:33:22 AM (95 ms) : 1.3.6.1.2.1.1.9.1.3.8 = "View-based Access Control Model for SNMP." [ASN_OCTET_STR]

I tried using the to MIB files that APC gives out at this page: http://www.apc.com/us/en/tools/download/index.cfm under "firmware upgrades - MIB". Both didn't work in PRTG. One have an SNMP 2222 error and the other said no interfaces found. Weird there would be SNMP capability with no MIB files to be found.

Created on Jul 1, 2016 7:08:59 PM

Last change on Jul 4, 2016 10:04:55 AM by Felix Saure [Paessler Support]



Votes:

0

Dear Keith,

You can also use the SNMP Tester and choose the Scan OIDLIB option. This will list all OIDs which are supported by the target device.

Best regards, Felix

Created on Jul 4, 2016 10:09:28 AM by Felix Saure [Paessler Support]

Last change on Jul 7, 2016 2:24:11 PM by Felix Saure [Paessler Support]



Votes:

0

Felix,

I am not seeing that Scan OIDLIB option in the MIB-Importer. I am using V3.4.8 alpha. Just so I understand, you want me to create a new OIDlib then scan the 1.3.6 OID and save that as a new MIB file?

Thanks,

Keith

Created on Jul 6, 2016 2:23:35 PM



Votes:

0

Dear Keith,

Please excuse me, I wanted to refer to the SNMP Testing Tool.

Note: I corrected my previous post for future users of PRTG.

Best, Felix

Created on Jul 7, 2016 2:22:52 PM by Felix Saure [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.