09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

After <strong>the</strong> supported SNMP version is determined, <strong>the</strong> management station uses that<br />

version <strong>to</strong> structure management data requests.<br />

SNMP Components<br />

Now, let's look at <strong>the</strong> different components of SNMP. As a <strong>network</strong> management<br />

pro<strong>to</strong>col, it defines <strong>the</strong> way <strong>network</strong> management information should be structured<br />

and interpreted. The basis of this functionality is SNMP's MIB. A MIB is <strong>the</strong> rule base<br />

for defining management data structures. The MIB is used by <strong>the</strong> management<br />

station and agents <strong>to</strong> format management data requests. SNMP defines <strong>the</strong><br />

formatting of <strong>the</strong> management data structures in <strong>the</strong> Structure of Management<br />

Information (SMI) definition. For SNMP v1, <strong>the</strong> SMI is described in RFC 1155. The<br />

SMI for SNMP v2 is described in RFC 1902. Since SNMP is a hardware-independent<br />

<strong>network</strong> manage ment pro<strong>to</strong>col, it needs <strong>to</strong> accommodate <strong>the</strong> different data<br />

representation generated by different types of devices. To facilitate this kind of<br />

communication, SNMP uses Abstract Syntax Notation One (ASN.1). All <strong>network</strong><br />

management data structure requests and responses are formatted using ASN.1. In<br />

order <strong>to</strong> transport <strong>the</strong>se management messages, <strong>the</strong>y must be encoded in<strong>to</strong> a<br />

format that will permit <strong>the</strong>ir transmission between managed devices and<br />

management stations. SNMP defines this format as a set of data encoding rules<br />

known as <strong>the</strong> Basic Encoding Rules (BER).<br />

SMI<br />

The SMIs for SNMP v1 and SNMP v2 define <strong>the</strong> hierarchical rules for describing<br />

management data structures. The <strong>to</strong>p of this structure is <strong>the</strong> MIB, which is<br />

essentially a container for specific management data structures, known as managed<br />

objects. Managed objects or MIB objects are <strong>the</strong> data mappings used by agents <strong>to</strong><br />

collect management data. A managed object exists for each management data<br />

variable that is collected by <strong>the</strong> agent. Each object can contain a single data type<br />

and value or a list of data types and values. The SNMP v1 and SMTPv2 SMIs define<br />

two groups of data types: simple and application-wide. ASN.1 is used for <strong>the</strong> actual<br />

representation and implementation of <strong>the</strong> SMI-defined data structures.<br />

BER<br />

The SNMP BER defines <strong>the</strong> process used <strong>to</strong> convert <strong>the</strong> ASN.1 format in<strong>to</strong> a binary<br />

format for transmission in <strong>the</strong> SNMP PDU. This serialized data is <strong>the</strong>n converted<br />

back in<strong>to</strong> ASN.1 format when it reaches its destination. The actual SNMP-PDU data<br />

is in BER hexadecimal form. The BER conversion is a function of <strong>the</strong> SNMP process<br />

operating on <strong>the</strong> managed device. Only a subset of BER is used for SNMP; its usage<br />

is a legacy of <strong>the</strong> CMIP standard, which uses <strong>the</strong> CCITT X.209 specification. From a

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!