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.

functional perspective, BER employs a least <strong>to</strong> most significant bit ordering scheme<br />

(little-endian), using 8-bit octets. ASN.1 data types are encoded using three<br />

variable length fields. The first field, defined as <strong>the</strong> tag field, indicates <strong>the</strong> ASN.1<br />

data type. The second field, <strong>the</strong> length field, indicates how many octets make up <strong>the</strong><br />

actual ASN.1 data type. The third field is <strong>the</strong> value field, and it consists of x amount<br />

of octets that make up <strong>the</strong> actual ASN.1 data.<br />

ASN.1<br />

ASN.1 is a platform and implementation-independent data description language<br />

developed by <strong>the</strong> ISO for unambiguous data representation. ASN.1 presents data in<br />

an abstract form using a highly structured syntax that only describes <strong>the</strong> ASN.1 data<br />

types and <strong>the</strong> assignment of values <strong>to</strong> those data types. ASN.1 is not interested in<br />

how <strong>the</strong> data will be processed, only with its correct presentation. ASN.1 is a very<br />

complex language that offers a broad set of data type definitions. This makes it an<br />

ideal <strong>to</strong>ol for representing data on any system type. The SNMP SMI defines only a<br />

small group of ASN.1 data types for use with SNMP. ASN.1 uses <strong>the</strong> following basic<br />

structure <strong>to</strong> define data types and values:<br />

data type value name | data type identifier ::= data value or { data type<br />

identifier<br />

(data value)}<br />

Data type name labels can be specifically defined through <strong>the</strong> use of a unique data<br />

identifier that appears in initial lowercase, uppercase form (for example,<br />

sysContact). The data type identifier is ei<strong>the</strong>r a named data type expressed in title<br />

form (such as MacAddress) or as an ASN.1-defined data type, expressed as an<br />

ASN.1 keyword in uppercase form (for example, INTEGER). Data values are<br />

expressed as alphanumeric characters in all lowercase form (for example,<br />

linkstatus 0).<br />

NOTE<br />

ASN.1 is a programming language, and a ra<strong>the</strong>r complicated one at that. Its<br />

complete syntax, grammar, and implementation are far beyond <strong>the</strong> scope of this<br />

book. Unless you are planning <strong>to</strong> develop your own MIBs, an intimate knowledge of<br />

ASN.1 is not required. Table 11.3 lists some of <strong>the</strong> more commonly used ASN.1<br />

keywords used with SNMP MIB's. The goal in this section is <strong>to</strong> provide you with a<br />

basic understanding of how SNMP messages are constructed. Additional references<br />

on SNMP are listed at <strong>the</strong> end of <strong>the</strong> chapter.

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

Saved successfully!

Ooh no, something went wrong!