I am a final year M.C.A. graduate student . I'm doing my final semester
project using the NET-SNMP package .
My project is about to communicate with the ADC [ Analog to Digital
Converter ] using the SNMP protocol.
I am going to develop this project using C & Rt-Linux . I am using
Net-Snmp version 5.1.1.
I don't know how to design a good mib . Now i have designed a simple mib
after reading some materials from the net.
But i don't know whether it is correct or not. When i was using the
command snmptranslate , the command won't take my own
mib. But it usually takes SNMPv2-MIB file which was in the
/usr/local/share/snmp/mibs/ path.
Here by i have attached my code & the MIB file .
I have also put my mib file which is named SNMP-MIB.txt in the
same default directory .
I have already used the export comand as export MIBS=+SNMP-MIB.
But after that there was no change in the result .
It print the id's from the SNMPv2-MIB & displays the error message as
"SNMP-MIB no file or directory".
But when i saw the export , the file name was set as"SNMP-MIB".
I don't know how to solve it .
Please help me how to solve it .
Thanks in advance ,
V.Balaji
SNMP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,snmpModules, mib-2
FROM SNMPv2-SMI
DisplayString FROM SNMPv2-TC
snmpMIB MODULE-IDENTITY
ORGANIZATION "Data Patterns (India) Pvt Ltd-Chennai"
CONTACT-INFO
"WG-EMail: [EMAIL PROTECTED]
Subscribe: [EMAIL PROTECTED]
Co-Chair: Chaman Lal
postal: SDG ,Data Patterns India Pvt Limited,
19,Arya Gowder Road,West Mambalam,
Chenai-India"
DESCRIPTION
"The MIB module for SNMP entities".
::= { snmpModules 1 }
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
-- ::= { snmpMIBObjects 1 } this OID is obsolete
-- ::= { snmpMIBObjects 2 } this OID is obsolete
-- ::= { snmpMIBObjects 3 } this OID is obsolete
-- the System group
--
-- a collection of objects common to all managed systems.
system OBJECT IDENTIFIER ::= { mib-2 1 }
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the entity. This value should
include the full name and version identification of
the system's hardware type, software operating-system,
and networking software."
::= { system 1 }
sysObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor's authoritative identification of the
network management subsystem contained in the entity.
This value is allocated within the SMI enterprises
subtree (1.3.6.1.4.1) and provides an easy and
unambiguous means for determining `what kind of box' is
being managed. For example, if vendor `Flintstones,
Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
it could assign the identifier 1.3.6.1.4.1.424242.1.1
to its `Fred Router'."
::= { system 2 }
ENDSNMP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,snmpModules, mib-2
FROM SNMPv2-SMI
DisplayString FROM SNMPv2-TC
snmpMIB MODULE-IDENTITY
ORGANIZATION "Data Patterns (India) Pvt Ltd-Chennai"
CONTACT-INFO
"WG-EMail: [EMAIL PROTECTED]
Subscribe: [EMAIL PROTECTED]
Co-Chair: Chaman Lal
postal: SDG ,Data Patterns India Pvt Limited,
19,Arya Gowder Road,West Mambalam,
Chenai-India"
DESCRIPTION
"The MIB module for SNMP entities".
::= { snmpModules 1 }
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
-- ::= { snmpMIBObjects 1 } this OID is obsolete
-- ::= { snmpMIBObjects 2 } this OID is obsolete
-- ::= { snmpMIBObjects 3 } this OID is obsolete
-- the System group
--
-- a collection of objects common to all managed systems.
system OBJECT IDENTIFIER ::= { mib-2 1 }
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the entity. This value should
include the full name and version identification of
the system's hardware type, software operating-system,
and networking software."
::= { system 1 }
sysObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor's authoritative identification of the
network management subsystem contained in the entity.
This value is allocated within the SMI enterprises
subtree (1.3.6.1.4.1) and provides an easy and
unambiguous means for determining `what kind of box' is
being managed. For example, if vendor `Flintstones,
Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
it could assign the identifier 1.3.6.1.4.1.424242.1.1
to its `Fred Router'."
::= { system 2 }
END
