New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Port identification using custom OID

Votes:

1

Your Vote:

Up

Down

I have a SAN switch from Brocade and sadly they store user configured port names under their own SNMP tree, under OID 'SNMPv2-SMI::enterprises.1588.2.1.1.1.6.2.1.36'.

Is there any chance that in the future releases automatic port identification will be possible using a custom OID, beside the standard IF-MIB::ifDescr, ifName, ifAlias ?

custom identification ifalias ifdescr ifname port prtg snmp-traffic wishlist

Created on Dec 19, 2014 9:53:32 AM by  vobelic (12) 2

Last change on Dec 22, 2014 11:37:00 AM by  Greg Campion [Paessler Support]



6 Replies

Votes:

0

Your Vote:

Up

Down

If you want to use a custom OID for the port identification, this isn't a request that we get often but I'll change this into a feature request and if others post on here, we will consider putting this into the software.

The Port name itself can be set to use a custom OID, just not the Port Identification. In the field Port Name Template you can define a specific OID and PRTG will use that to create the names of the interfaces.

Created on Dec 22, 2014 11:36:42 AM by  Greg Campion [Paessler Support]

Last change on Dec 22, 2014 11:40:33 AM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Uh can you explain how it's possible to define the OID in the Port Name Template? Did you mean editing the .odt file itself or?

Created on Dec 22, 2014 5:07:55 PM by  vobelic (12) 2



Votes:

0

Your Vote:

Up

Down

In the settings for the device under the SNMP Compatibility Options, you should be able to use [1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36] for the port name template and PRTG should be able to use that for the names of the ports.

OID Settings

Large Image

Created on Dec 23, 2014 2:44:17 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I tried already using a custom OID in the "port name template" but I'm getting "No such name (SNMP Error #2)".

This is the config for the group of devices from which i'm trying to get port names based on custom OID:

Port Name Template: ([port]) [ifName] [1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36]

Port Name Update: Automatic ...

Port Identification: Use IfName

This is the output using snmpget/walk:

# snmpwalk -v2c -c public sansw01 IF-MIB::ifName
IF-MIB::ifName.1073741824 = STRING: 0/0
IF-MIB::ifName.1073741825 = STRING: 0/1
IF-MIB::ifName.1073741826 = STRING: 0/2
IF-MIB::ifName.1073741827 = STRING: 0/3
IF-MIB::ifName.1073741828 = STRING: 0/4
IF-MIB::ifName.1073741829 = STRING: 0/5
IF-MIB::ifName.1073741830 = STRING: 0/6
IF-MIB::ifName.1073741831 = STRING: 0/7
IF-MIB::ifName.1073741832 = STRING: 0/8
IF-MIB::ifName.1073741833 = STRING: 0/9
IF-MIB::ifName.1073741834 = STRING: 0/10
IF-MIB::ifName.1073741835 = STRING: 0/11
IF-MIB::ifName.1073741836 = STRING: 0/12
IF-MIB::ifName.1073741837 = STRING: 0/13
IF-MIB::ifName.1073741838 = STRING: 0/14
IF-MIB::ifName.1073741839 = STRING: 0/15
IF-MIB::ifName.1073741840 = STRING: 0/16
IF-MIB::ifName.1073741841 = STRING: 0/17
IF-MIB::ifName.1073741842 = STRING: 0/18
IF-MIB::ifName.1073741843 = STRING: 0/19
IF-MIB::ifName.1073741844 = STRING: 0/20
IF-MIB::ifName.1073741845 = STRING: 0/21
IF-MIB::ifName.1073741846 = STRING: 0/22 
IF-MIB::ifName.1073741847 = STRING: 0/23 

Sadly no ifDescr is used but manufacturer custom OIDs are used:

# snmpwalk -On -v2c -c public sansw01 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.3 = INTEGER: 3
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.4 = INTEGER: 4
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.5 = INTEGER: 5
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.6 = INTEGER: 6
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.7 = INTEGER: 7
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.8 = INTEGER: 8
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.9 = INTEGER: 9
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.10 = INTEGER: 10
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.11 = INTEGER: 11
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.12 = INTEGER: 12
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.13 = INTEGER: 13
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.14 = INTEGER: 14
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.15 = INTEGER: 15
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.16 = INTEGER: 16
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.17 = INTEGER: 17
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.18 = INTEGER: 18
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.19 = INTEGER: 19
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.20 = INTEGER: 20
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.21 = INTEGER: 21
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.22 = INTEGER: 22
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.23 = INTEGER: 23
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.1.24 = INTEGER: 24

# snmpwalk -On -m -ALL -v2c -c public sansw01 SNMPv2-SMI::enterprises.1588.2.1.1.1.6.2.1.36
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.1 = STRING: "stc02:fc1"
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.2 = STRING: "stc01:fc1"
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.3 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.4 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.5 = STRING: "fs009:fc0"
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.6 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.7 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.8 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.9 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.10 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.11 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.12 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.13 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.14 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.15 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.16 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.17 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.18 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.19 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.20 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.21 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.22 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.23 = ""
.1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36.24 = ""

I'm guessing the problem is that standard OIDs (IF-MIB::ifName) have these huge integers as port index and the manufacturer OIDs use indexing 1-24 for 24 ports.

Is there any hint how to make this work?

Created on Jan 22, 2015 4:11:18 PM by  vobelic (12) 2

Last change on Jan 26, 2015 8:37:48 AM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

bump

Created on Jan 30, 2015 6:34:47 PM by  vobelic (12) 2



Votes:

0

Your Vote:

Up

Down

We were not able to reproduce the issue. Using the OID you provided in the "Port Name Template" should work without problems.

Please use the Paessler SNMP Tester to create a walk over the OID 1.3.6.1 and show us the output. This will allow us to more closely simulate your device.

Created on Feb 2, 2015 10:02:19 AM by  Yannic Stolz [Paessler Support]



Please log in or register to enter your reply.


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.