New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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


Help with MIB Import

Votes:

0

Your Vote:

Up

Down

I am unable to get a MIB file to import:

The file is:

DCSW-SSV-MONITOR-MIB DEFINITIONS ::= BEGIN

IMPORTS
    enterprises
        FROM RFC1155-SMI
    OBJECT-TYPE
        FROM RFC-1212
    TRAP-TYPE
        FROM RFC-1215
    DisplayString
        FROM RFC1213-MIB;
				
    datacore    OBJECT IDENTIFIER ::= { enterprises 7652 } 
    objects     OBJECT IDENTIFIER ::= { datacore 1 }
    traps       OBJECT IDENTIFIER ::= { datacore 2 }

   -- a multi-row table describing the monitors 

    monitorTable  OBJECT-TYPE 
        SYNTAX SEQUENCE OF MonitorEntry 
        ACCESS not-accessible 
        STATUS mandatory 
        DESCRIPTION "table"
        ::= { objects 1 } 

    monitorEntry OBJECT-TYPE 
        SYNTAX MonitorEntry
        ACCESS not-accessible 
        STATUS mandatory 
        DESCRIPTION "entry"
        INDEX { monitorId } 
        ::= { monitorTable  1 }

        MonitorEntry::= 
            SEQUENCE { 
                monitorId
                    OCTET STRING (SIZE(16)),
                monitoredId
                    OCTET STRING (SIZE(16)),
                monitorState
                    DisplayString,
                monitorDesc
                    DisplayString,
                monitorCaption
                    DisplayString
            }

    monitorId OBJECT-TYPE 
        SYNTAX OCTET STRING (SIZE(16))
        ACCESS read-only 
        STATUS mandatory 
        DESCRIPTION "Monitor GUID"
        ::= { monitorEntry 1 }

    monitoredId OBJECT-TYPE 
        SYNTAX OCTET STRING (SIZE(16))
        ACCESS read-only 
        STATUS mandatory 
        DESCRIPTION "Monitored GUID"
        ::= { monitorEntry 2 }

    monitorState OBJECT-TYPE 
        SYNTAX DisplayString
        ACCESS read-only 
        STATUS mandatory 
        DESCRIPTION "Monitor state ENUM"
        ::= { monitorEntry 3 }

    monitorDesc OBJECT-TYPE 
        SYNTAX DisplayString
        ACCESS read-only 
        STATUS mandatory 
        DESCRIPTION "Monitor Description"
        ::= { monitorEntry 4 }
			
    monitorCaption OBJECT-TYPE 
        SYNTAX DisplayString
        ACCESS read-only 
        STATUS mandatory 
        DESCRIPTION "Monitored Object Caption"
        ::= { monitorEntry 5 }

   -- trap definitions

     trapMonitorEvent TRAP-TYPE 
        ENTERPRISE  traps
        VARIABLES { monitorId, monitoredId, monitorState, monitorDesc, monitorCaption  } 
        DESCRIPTION "Trap sent when an update to a SANsymphony-V monitor occurs" 
        ::= 1

END

Result is as follows:

Import successful!


Report for C:\Program Files\Paessler MIB Importer V2\DCSW-SSV-MONITOR.MIB:
Sucessfully included files: 9 of 9
Sucessfully imported OIDs: 0 of 0
OIDs that were useful for PRTG: 0

prtg9 snmp snmp-import

Created on May 1, 2013 12:59:47 AM by  Art Ronci (0) 1

Last change on Jul 28, 2015 7:39:10 AM by  Luciano Lingnau [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Hello,

which MIB importer did you use?

the Importer simply can not find any OIDs that can be used with PRTG.

If you did use the old MIB Importer 2.1, then please try with the new alpha 3.4.6

https://www.paessler.com/tools/mibimporter

Created on May 1, 2013 5:22:48 AM by  Aurelio Lombardi [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.