SCALAR OBJECTS

Name	Type	Access	OID	Description
1 netSnmpPassString	OCTETSTR Legal Lengths: 0 .. 255 SnmpAdminString	ReadWrite	.1.3.6.1.4.1.8072.2.255.1	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. Example string scalar object.
3 netSnmpPassTimeTicks	TICKS	ReadWrite	.1.3.6.1.4.1.8072.2.255.3	Example timetick object.
4 netSnmpPassIpAddress	IPADDR	ReadWrite	.1.3.6.1.4.1.8072.2.255.4	Example IP Address object.
5 netSnmpPassCounter	COUNTER	ReadOnly	.1.3.6.1.4.1.8072.2.255.5	Example counter object. Note that this object will always return the value '42'.
6 netSnmpPassGauge	GAUGE	ReadWrite	.1.3.6.1.4.1.8072.2.255.6	Example Gauge object.

TABLE OBJECTS

Table netSnmpPassTable

Table Name	netSnmpPassTable
In MIB	NET-SNMP-PASS-MIB
Registered at OID	.1.3.6.1.4.1.8072.2.255.2
Table Description	Example table
Row Description	Conceptual row in the example table.

netSnmpPassTable Indexes:

Name	Type	Access	Description
1 netSnmpPassIndex	INTEGER32	NoAccess	Arbitrary index into the netSnmpPassTable. Note that there will always be one row, with index 1

Other netSnmpPassTable Columns:

Name	Type	Access	Description
2 netSnmpPassInteger	INTEGER32	ReadWrite	Example Integer (table) object.
3 netSnmpPassOID	OBJECTID	ReadWrite	Example OID (table) object.

DEPRECATED OR OBSOLETE OR HISTORIC OBJECTS

NOTIFICATIONS

TEXTUAL CONVENTIONS

These TEXTUAL-CONVENTIONS are used in other parts of the document above. They are SNMP's way of defining a datatype that is used repeatedly by other MIB objects. Any implementation implementing objects that use one of these definitions must follow its DESCRIPTION clause as well as the DESCRIPTION clause of the object itself.

Name	Type	Description
SnmpAdminString	OCTETSTR	An octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters.

TREE VIEW

Tree view generated by running: snmptranslate -Tp NET-SNMP-PASS-MIB::netSnmpPassExamples