Difference between revisions of "SNMPv1"
(New page: === What is "SNMP" ? === '''Simple Network Management Protocol''' (SNMP) is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). SNMP is use...) |
|||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
Source: RFC 3411 — An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks. | Source: RFC 3411 — An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks. | ||
Check the Wikipedia entry for an introduction to the topic. | Check the Wikipedia Simple Network Management Protocol entry for an introduction to the topic. | ||
=== What is the MIB ? === | === What is the MIB ? === | ||
SNMP itself does not define which information (which variables) a managed system should offer. Rather, SNMP uses an extensible design, where the available information is defined by the ''' Management Information Base''' (MIB). There is only '''one''' MIB. Not multiple MIBs as Wikipedia suggests. The MIB is a hierachical namespace which guarantees type uniqueness of the objects defined within it. The objects are defined by unique identifiers (OIDs). Under this structure MIB files are or can be defined to describe the structure of the management data of a device subsystem. Each OID identifies a variable that can be read or set via SNMP. The MIB uses the notation defined by ASN.1. | SNMP itself does not define which information (which variables) a managed system should offer. Rather, SNMP uses an extensible design, where the available information is defined by the ''' Management Information Base''' (MIB). There is only '''one''' MIB. Not multiple MIBs as Wikipedia suggests. The MIB is a hierachical namespace which guarantees type uniqueness of the objects defined within it. The objects are defined by unique identifiers (OIDs). Under this structure MIB files are or can be defined to describe the structure of the management data of a device subsystem. Each OID identifies a variable that can be read or set via SNMP. The MIB uses the notation defined by ASN.1. | ||
| Line 12: | Line 13: | ||
==== MIB II ==== | ==== MIB II ==== | ||
A standard MIB file was included in SNMPv1. This is "Management Information Base for Network Management of TCP/IP-based internets" defined in RFC 1156. Usually known as MIB II. Barix supports this as a default in all products where SNMP is included. | A standard MIB file was included in SNMPv1. This is "Management Information Base for Network Management of TCP/IP-based internets" defined in RFC 1156. Usually known as MIB II. Barix supports this as a default in all products where SNMP is included. | ||
==== Barix MIB ==== | ==== Barix MIB Registration Authority ==== | ||
This is the authority for defining MIB items under barix { enterprises 17491 }. | |||
It is actually just a document where the Barix MIB branches are maintained. | |||
Any OID definitions which are used in more than one Barix project are included in the Barix.mib file. | |||
If new branches are needed then this file is updated. | |||
==== Barix MIB files as at 12th June 2008 ==== | |||
Display friendly summary of Barix.mib branches. This is just a hint, read the mib file for the exact and up to date definitions. | |||
barix OBJECT IDENTIFIER ::= { enterprises 17491 } | |||
products OBJECT IDENTIFIER ::= { barix 1 } | |||
systems OBJECT IDENTIFIER ::= { barix 2 ) | |||
unit OBJECT IDENTIFIER ::= { barix 3 } | |||
barionet OBJECT IDENTIFIER ::= { products 1 } | |||
exstreamer OBJECT IDENTIFIER ::= { products 2 } | |||
instreamer OBJECT IDENTIFIER ::= { products 3 } | |||
annuncicom OBJECT IDENTIFIER ::= { products 4 } | |||
abcl OBJECT IDENTIFIER ::= { products 5 } | |||
audio OBJECT IDENTIFIER ::= { systems 1 } | |||
net OBJECT IDENTIFIER ::= { unit 1 } | |||
io OBJECT IDENTIFIER ::= { unit 2 } | |||
streamer OBJECT IDENTIFIER ::= { exstreamer 2 } | |||
gpt OBJECT IDENTIFIER ::= { abcl 1} | |||
To create a project MIB file using the existing OIDs, start by cutting and pasting what you need from the Barix MIB Registration Authority mib files. This hint is mainly for Barix internal developers, the required MIB files should be included in the project zip file. | |||
To use the following as mib files rename example: Barix_mib.txt to Barix.mib<br> | |||
The Barix MIB Registration Authority<br> | |||
[[media:Barix.mib.txt]]<br> | |||
The Barix Audio MIB file<br> | |||
[[media:BARIXAUDIOSNMP.mib.txt]]<br> | |||
Traps defined for abcl products (under barix.products.abcl<br> | |||
[[media:barix_abcl_trap.mib.txt]]<br> | |||
The Barionet MIB file<br> | |||
[[media:Barionet.mib.txt]]<br> | |||
Latest revision as of 11:53, 17 April 2013
What is "SNMP" ?
Simple Network Management Protocol (SNMP) is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). SNMP is used in network management systems to monitor network-attached devices for conditions that warrant administrative attention. It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects.
Source: RFC 3411 — An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.
Check the Wikipedia Simple Network Management Protocol entry for an introduction to the topic.
What is the MIB ?
SNMP itself does not define which information (which variables) a managed system should offer. Rather, SNMP uses an extensible design, where the available information is defined by the Management Information Base (MIB). There is only one MIB. Not multiple MIBs as Wikipedia suggests. The MIB is a hierachical namespace which guarantees type uniqueness of the objects defined within it. The objects are defined by unique identifiers (OIDs). Under this structure MIB files are or can be defined to describe the structure of the management data of a device subsystem. Each OID identifies a variable that can be read or set via SNMP. The MIB uses the notation defined by ASN.1.
What SNMP versions does Barix support?
SNMPV1
What MIB values do Barix support?
MIB II
A standard MIB file was included in SNMPv1. This is "Management Information Base for Network Management of TCP/IP-based internets" defined in RFC 1156. Usually known as MIB II. Barix supports this as a default in all products where SNMP is included.
Barix MIB Registration Authority
This is the authority for defining MIB items under barix { enterprises 17491 }. It is actually just a document where the Barix MIB branches are maintained. Any OID definitions which are used in more than one Barix project are included in the Barix.mib file. If new branches are needed then this file is updated.
Barix MIB files as at 12th June 2008
Display friendly summary of Barix.mib branches. This is just a hint, read the mib file for the exact and up to date definitions.
barix OBJECT IDENTIFIER ::= { enterprises 17491 }
products OBJECT IDENTIFIER ::= { barix 1 }
systems OBJECT IDENTIFIER ::= { barix 2 )
unit OBJECT IDENTIFIER ::= { barix 3 }
barionet OBJECT IDENTIFIER ::= { products 1 }
exstreamer OBJECT IDENTIFIER ::= { products 2 }
instreamer OBJECT IDENTIFIER ::= { products 3 }
annuncicom OBJECT IDENTIFIER ::= { products 4 }
abcl OBJECT IDENTIFIER ::= { products 5 }
audio OBJECT IDENTIFIER ::= { systems 1 }
net OBJECT IDENTIFIER ::= { unit 1 }
io OBJECT IDENTIFIER ::= { unit 2 }
streamer OBJECT IDENTIFIER ::= { exstreamer 2 }
gpt OBJECT IDENTIFIER ::= { abcl 1}
To create a project MIB file using the existing OIDs, start by cutting and pasting what you need from the Barix MIB Registration Authority mib files. This hint is mainly for Barix internal developers, the required MIB files should be included in the project zip file.
To use the following as mib files rename example: Barix_mib.txt to Barix.mib
The Barix MIB Registration Authority
media:Barix.mib.txt
The Barix Audio MIB file
media:BARIXAUDIOSNMP.mib.txt
Traps defined for abcl products (under barix.products.abcl
media:barix_abcl_trap.mib.txt
The Barionet MIB file
media:Barionet.mib.txt
