#!/bin/sh # This is `snmp2.13' (part 13 of snmp2). # Do not concatenate these parts, unpack them in order with `/bin/sh'. # File `snmp2/mib.txt' is being continued... # touch -am 1231235999 $$.touch >/dev/null 2>&1 if test ! -f 1231235999 && test -f $$.touch; then shar_touch=touch else shar_touch=: echo echo 'WARNING: not restoring timestamps. Consider getting and' echo "installing GNU \`touch', distributed in GNU File Utilities..." echo fi rm -f 1231235999 $$.touch # if test ! -r _sharseq.tmp; then echo 'Please unpack part 1 first!' exit 1 fi shar_sequence=`cat _sharseq.tmp` if test "$shar_sequence" != 13; then echo "Please unpack part $shar_sequence next!" exit 1 fi if test ! -f _sharnew.tmp; then echo 'x - still skipping snmp2/mib.txt' else echo 'x - continuing file snmp2/mib.txt' sed 's/^X//' << 'SHAR_EOF' >> 'snmp2/mib.txt' && X have been accepted and processed by the SNMP X protocol entity." X ::= { snmp 18 } X X snmpInTraps OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP Trap PDUs which have X been accepted and processed by the SNMP protocol X entity." X ::= { snmp 19 } X X snmpOutTooBigs OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP PDUs which were X generated by the SNMP protocol entity and for X which the value of the error-status field is X `tooBig.'" X ::= { snmp 20 } X X X snmpOutNoSuchNames OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP PDUs which were X generated by the SNMP protocol entity and for X which the value of the error-status is X `noSuchName'." X ::= { snmp 21 } X X snmpOutBadValues OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP PDUs which were X generated by the SNMP protocol entity and for X which the value of the error-status field is X `badValue'." X ::= { snmp 22 } X X -- { snmp 23 } is not used X X snmpOutGenErrs OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP PDUs which were X generated by the SNMP protocol entity and for X which the value of the error-status field is X `genErr'." X ::= { snmp 24 } X X snmpOutGetRequests OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP Get-Request PDUs which X have been generated by the SNMP protocol entity." X ::= { snmp 25 } X X snmpOutGetNexts OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X X X DESCRIPTION X "The total number of SNMP Get-Next PDUs which have X been generated by the SNMP protocol entity." X ::= { snmp 26 } X X snmpOutSetRequests OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP Set-Request PDUs which X have been generated by the SNMP protocol entity." X ::= { snmp 27 } X X snmpOutGetResponses OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP Get-Response PDUs which X have been generated by the SNMP protocol entity." X ::= { snmp 28 } X X snmpOutTraps OBJECT-TYPE X SYNTAX Counter X ACCESS read-only X STATUS mandatory X DESCRIPTION X "The total number of SNMP Trap PDUs which have X been generated by the SNMP protocol entity." X ::= { snmp 29 } X X snmpEnableAuthenTraps OBJECT-TYPE X SYNTAX INTEGER { enabled(1), disabled(2) } X ACCESS read-write X STATUS mandatory X DESCRIPTION X "Indicates whether the SNMP agent process is X permitted to generate authentication-failure X traps. The value of this object overrides any X configuration information; as such, it provides a X means whereby all authentication-failure traps may X be disabled. X X Note that it is strongly recommended that this X object be stored in non-volatile memory so that it X remains constant between re-initializations of the X network management system." X X X ::= { snmp 30 } X END X DEMO-MIB DEFINITIONS ::= BEGIN X EXPORTS -- everything --; X IMPORTS X OBJECT-TYPE, OBJECT-GROUP, Counter64, Gauge32, NsapAddress X FROM SMP-SMI X ifIndex X FROM RFC1213-MIB; X X mtrDemo OBJECT IDENTIFIER ::= X { joint-iso-ccitt mhs(6) group(6) mtr(200) 5 } X X mtrDemoGroup OBJECT-GROUP X OBJECTS { mtrBigNumber, mtrNsapAddress, mtrBitString, mtrColumn } X DESCRIPTION X "The demo group." X ::= { mtrDemo 1 } X mtrBigNumber OBJECT-TYPE X SYNTAX Counter64 X MAX-ACCESS read-write X STATUS mandatory X DESCRIPTION X "A big number. On startup, the agent initializes this to the value X X 18,023,456,790,123,456,789 X " X ::= { mtrDemoGroup 1 } X mtrNsapAddress OBJECT-TYPE X SYNTAX NsapAddress X MAX-ACCESS read-write X STATUS mandatory X DESCRIPTION X "An OSI Network Address. On startup, the agent initializes this to X the value X X NS+47000580ffff000000012301230123456789ab01 X " X ::= { mtrDemoGroup 2 } X mtrBitString OBJECT-TYPE X SYNTAX BIT STRING { X rejectA-A(0), X rejectA-B(1), X rejectA-S(2), X rejectA-M(3), X rejectB-A(4), X rejectB-B(5), X rejectB-S(6), X rejectB-M(7), X rejectS-A(8), X rejectS-B(9), X rejectS-S(10), X rejectS-M(11), X rejectM-A(12), X rejectM-B(13), X rejectM-S(14), X rejectM-M(15) X } X MAX-ACCESS read-write X STATUS mandatory X DESCRIPTION X "A string of bits. On startup, the agent initializes this to the value X X '0000000000000000'B X " X ::= { mtrDemoGroup 3 } X mtrTable OBJECT-TYPE X SYNTAX SEQUENCE OF MtrEntry X MAX-ACCESS not-accessible X STATUS mandatory X DESCRIPTION X "A mtr table used for testing..." X ::= { mtrDemoGroup 4 } X mtrEntry OBJECT-TYPE X SYNTAX MtrEntry X MAX-ACCESS not-accessible X STATUS mandatory X DESCRIPTION X "An entry (conceptual row) in the mtrTable." X INDEX { mtrIndex } X ::= { mtrTable 1 } X MtrEntry ::= X SEQUENCE { X mtrIndex INTEGER (0..50000), X mtrColumn Integer32 X } X mtrIndex OBJECT-TYPE X SYNTAX INTEGER (0..50000) X MAX-ACCESS not-accessible X STATUS mandatory X DESCRIPTION X "The auxilary variable used to identify (conceptual) rows in the X mtrTable." X ::= { mtrEntry 1 } X mtrColumn OBJECT-TYPE X SYNTAX Integer32 X MAX-ACCESS read-only X STATUS mandatory X DESCRIPTION X "The column." X ::= { mtrEntry 2 } X X END SNMPv2-SMI DEFINITIONS ::= BEGIN; X X security OBJECT IDENTIFIER ::= { internet 5 } X X snmpV2 OBJECT IDENTIFIER ::= { internet 6 } X X -- transport domains X snmpDomains OBJECT IDENTIFIER ::= { snmpV2 1 } X X -- transport proxies X snmpProxys OBJECT IDENTIFIER ::= { snmpV2 2 } X X -- module identities X snmpModules OBJECT IDENTIFIER ::= { snmpV2 3 } X END X SNMPv2-TC DEFINITIONS ::= BEGIN X X IMPORTS X ObjectSyntax, Integer32, TimeTicks X FROM SNMPv2-SMI; X X X DisplayString ::= TEXTUAL-CONVENTION X DISPLAY-HINT "255a" X STATUS current X DESCRIPTION X "Represents textual information taken from the NVT X ASCII character set, as defined in pages 4, 10-11 X of RFC 854. Any object defined using this syntax X may not exceed 255 characters in length." X SYNTAX OCTET STRING (SIZE (0..255)) X X PhysAddress ::= TEXTUAL-CONVENTION X DISPLAY-HINT "1x:" X STATUS current X DESCRIPTION X "Represents media- or physical-level addresses." X SYNTAX OCTET STRING X X MacAddress ::= TEXTUAL-CONVENTION X DISPLAY-HINT "1x:" X STATUS current X DESCRIPTION X "Represents an 802 MAC address represented in the X 'canonical' order defined by IEEE 802.1a, i.e., as X if it were transmitted least significant bit X first, even though 802.5 (in contrast to other X 802.x protocols) requires MAC addresses to be X transmitted most significant bit first." X SYNTAX OCTET STRING (SIZE (6)) X X TruthValue ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Represents a boolean value." X SYNTAX INTEGER { true(1), false(2) } X X X TestAndIncr ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Represents integer-valued information used for X atomic operations. When the management protocol X is used to specify that an object instance having X this syntax is to be modified, the new value X supplied via the management protocol must X precisely match the value presently held by the X instance. If not, the management protocol set X operation fails with an error of X 'inconsistentValue'. Otherwise, if the current X value is the maximum value of 2^31-1 (2147483647 X decimal), then the value held by the instance is X wrapped to zero; otherwise, the value held by the X instance is incremented by one. (Note that X regardless of whether the management protocol set X operation succeeds, the variable-binding in the X request and response PDUs are identical.) X X The value of the ACCESS clause for objects having X this syntax is either 'read-write' or 'read- X create'. When an instance of a columnar object X having this syntax is created, any value may be X supplied via the management protocol." X SYNTAX INTEGER (0..2147483647) X X X AutonomousType ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Represents an independently extensible type X identification value. It may, for example, X indicate a particular sub-tree with further MIB X definitions, or define a particular type of X protocol or hardware." X SYNTAX OBJECT IDENTIFIER X X InstancePointer ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "A pointer to a specific instance of a conceptual X row of a MIB table in the managed device. By X convention, it is the name of the particular X instance of the first columnar object in the X conceptual row." X SYNTAX OBJECT IDENTIFIER X X X RowStatus ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "The RowStatus textual convention is used to X manage the creation and deletion of conceptual X rows, and is used as the value of the SYNTAX X clause for the status column of a conceptual row X (as described in Section 7.7.1 of [2].) X X The status column has six defined values: X X - 'active', which indicates that the X conceptual row is available for use by the X managed device; X X - 'notInService', which indicates that the X conceptual row exists in the agent, but is X unavailable for use by the managed device X (see NOTE below); X X - 'notReady', which indicates that the X conceptual row exists in the agent, but is X missing information necessary in order to be X available for use by the managed device; X X - 'createAndGo', which is supplied by a X management station wishing to create a new X instance of a conceptual row and to have it X available for use by the managed device; X X - 'createAndWait', which is supplied by a X management station wishing to create a new X instance of a conceptual row but not to have X it available for use by the managed device; X and, X X - 'destroy', which is supplied by a X management station wishing to delete all of X the instances associated with an existing X conceptual row. X X Whereas five of the six values (all except X 'notReady') may be specified in a management X protocol set operation, only three values will be X returned in response to a management protocol X X X retrieval operation: 'notReady', 'notInService' or X 'active'. That is, when queried, an existing X conceptual row has only three states: it is either X available for use by the managed device (the X status column has value 'active'); it is not X available for use by the managed device, though X the agent has sufficient information to make it so X (the status column has value 'notInService'); or, X it is not available for use by the managed device, X because the agent lacks sufficient information X (the status column has value 'notReady'). X X NOTE WELL X X This textual convention may be used for a MIB X table, irrespective of whether the values of X that table's conceptual rows are able to be X modified while it is active, or whether its X conceptual rows must be taken out of service X in order to be modified. That is, it is the X responsibility of the DESCRIPTION clause of X the status column to specify whether the X status column must be 'notInService' in order X for the value of some other column of the X same conceptual row to be modified. X X X To summarize the effect of having a conceptual row X with a status column having a SYNTAX clause value X of RowStatus, consider the following state X diagram: X X STATE X +--------------+-----------+-------------+------------- X | A | B | C | D X | |status col.|status column| X |status column | is | is |status column X ACTION |does not exist| notReady | notInService| is active X --------------+--------------+-----------+-------------+------------- X set status |noError ->D|inconsist- |inconsistent-|inconsistent- X column to | or | entValue| Value| Value X createAndGo |inconsistent- | | | X | Value| | | X --------------+--------------+-----------+-------------+------------- X set status |noError see 1|inconsist- |inconsistent-|inconsistent- X column to | or | entValue| Value| Value X createAndWait |wrongValue | | | X --------------+--------------+-----------+-------------+------------- X set status |inconsistent- |inconsist- |noError |noError X column to | Value| entValue| | X active | | | | X | | or | | X | | | | X | |see 2 ->D| ->D| ->D X --------------+--------------+-----------+-------------+------------- X set status |inconsistent- |inconsist- |noError |noError ->C X column to | Value| entValue| | X notInService | | | | X | | or | | or X | | | | X | |see 3 ->C| ->C|wrongValue X --------------+--------------+-----------+-------------+------------- X set status |noError |noError |noError |noError X column to | | | | X destroy | ->A| ->A| ->A| ->A X --------------+--------------+-----------+-------------+------------- X set any other |see 4 |noError |noError |noError X column to some| | | | X value | ->A| see 1| ->C| ->D X --------------+--------------+-----------+-------------+------------- X X X (1) goto B or C, depending on information X available to the agent. X X (2) if other variable bindings included in the X same PDU, provide values for all columns which are X missing but required, then return noError and goto X D. X X (3) if other variable bindings included in the X same PDU, provide values for all columns which are X missing but required, then return noError and goto X C. X X (4) at the discretion of the agent, either noError X or inconsistentValue may be returned. X X NOTE: Other processing of the set request may X result in a response other than noError being X returned, e.g., wrongValue, noCreation, etc. X X Conceptual Row Creation X X There are four potential interactions when X creating a conceptual row: selecting an instance- X identifier which is not in use; creating the X conceptual row; initializing any objects for which X the agent does not supply a default; and, making X the conceptual row available for use by the X managed device. X X Interaction 1: Selecting an Instance-Identifier X X The algorithm used to select an instance- X identifier varies for each conceptual row. In X some cases, the instance-identifier is X semantically significant, e.g., the destination X address of a route, and a management station X selects the instance-identifier according to the X semantics. X X In other cases, the instance-identifier is used X solely to distinguish conceptual rows, and a X management station without specific knowledge of X the conceptual row might examine the instances X X X present in order to determine an unused instance- X identifier. (This approach may be used, but it is X often highly sub-optimal; however, it is also a X questionable practice for a naive management X station to attempt conceptual row creation.) X X Alternately, the MIB module which defines the X conceptual row might provide one or more objects X which provide assistance in determining an unused X instance-identifier. For example, if the X conceptual row is indexed by an integer-value, X then an object having an integer-valued SYNTAX X clause might be defined for such a purpose, X allowing a management station to issue a X management protocol retrieval operation. In order X to avoid unnecessary collisions between competing X management stations, 'adjacent' retrievals of this X object should be different. X X Finally, the management station could select a X pseudo-random number to use as the index. In the X event that this index was already in use and an X inconsistentValue was returned in response to the X management protocol set operation, the management X station should simply select a new pseudo-random X number and retry the operation. X X A MIB designer should choose between the two X latter algorithms based on the size of the table X (and therefore the efficiency of each algorithm). X For tables in which a large number of entries are X expected, it is recommended that a MIB object be X defined that returns an acceptable index for X creation. For tables with small numbers of X entries, it is recommended that the latter X pseudo-random index mechanism be used. X X Interaction 2: Creating the Conceptual Row X X Once an unused instance-identifier has been X selected, the management station determines if it X wishes to create and activate the conceptual row X in one transaction or in a negotiated set of X interactions. X X X Interaction 2a: Creating and Activating the X Conceptual Row X X The management station must first determine the X column requirements, i.e., it must determine those X columns for which it must or must not provide X values. Depending on the complexity of the table X and the management station's knowledge of the X agent's capabilities, this determination can be X made locally by the management station. X Alternately, the management station issues a X management protocol get operation to examine all X columns in the conceptual row that it wishes to X create. In response, for each column, there are X three possible outcomes: X X - a value is returned, indicating that some X other management station has already created X this conceptual row. We return to X interaction 1. X X - the exception 'noSuchInstance' is returned, X indicating that the agent implements the X object-type associated with this column, and X that this column in at least one conceptual X row would be accessible in the MIB view used X by the retrieval were it to exist. For those X columns to which the agent provides read- X create access, the 'noSuchInstance' exception X tells the management station that it should X supply a value for this column when the X conceptual row is to be created. X X - the exception 'noSuchObject' is returned, X indicating that the agent does not implement X the object-type associated with this column X or that there is no conceptual row for which X this column would be accessible in the MIB X view used by the retrieval. As such, the X management station can not issue any X management protocol set operations to create X an instance of this column. X X Once the column requirements have been determined, X a management protocol set operation is accordingly X X X issued. This operation also sets the new instance X of the status column to 'createAndGo'. X X When the agent processes the set operation, it X verifies that it has sufficient information to X make the conceptual row available for use by the X managed device. The information available to the X agent is provided by two sources: the management X protocol set operation which creates the X conceptual row, and, implementation-specific X defaults supplied by the agent (note that an agent X must provide implementation-specific defaults for X at least those objects which it implements as X read-only). If there is sufficient information X available, then the conceptual row is created, a X 'noError' response is returned, the status column X is set to 'active', and no further interactions X are necessary (i.e., interactions 3 and 4 are X skipped). If there is insufficient information, X then the conceptual row is not created, and the X set operation fails with an error of X 'inconsistentValue'. On this error, the X management station can issue a management protocol X retrieval operation to determine if this was X because it failed to specify a value for a X required column, or, because the selected instance X of the status column already existed. In the X latter case, we return to interaction 1. In the X former case, the management station can re-issue X the set operation with the additional information, X or begin interaction 2 again using 'createAndWait' X in order to negotiate creation of the conceptual X row. X X X NOTE WELL X X Regardless of the method used to determine X the column requirements, it is possible that X the management station might deem a column X necessary when, in fact, the agent will not X allow that particular columnar instance to be X created or written. In this case, the X management protocol set operation will fail X with an error such as 'noCreation' or X 'notWritable'. In this case, the management X station decides whether it needs to be able X to set a value for that particular columnar X instance. If not, the management station X re-issues the management protocol set X operation, but without setting a value for X that particular columnar instance; otherwise, X the management station aborts the row X creation algorithm. X X Interaction 2b: Negotiating the Creation of the X Conceptual Row X X The management station issues a management X protocol set operation which sets the desired X instance of the status column to 'createAndWait'. X If the agent is unwilling to process a request of X this sort, the set operation fails with an error X of 'wrongValue'. (As a consequence, such an agent X must be prepared to accept a single management X protocol set operation, i.e., interaction 2a X above, containing all of the columns indicated by X its column requirements.) Otherwise, the X conceptual row is created, a 'noError' response is X returned, and the status column is immediately set X to either 'notInService' or 'notReady', depending X on whether it has sufficient information to make X the conceptual row available for use by the X managed device. If there is sufficient X information available, then the status column is X set to 'notInService'; otherwise, if there is X insufficient information, then the status column X is set to 'notReady'. Regardless, we proceed to X interaction 3. X X X Interaction 3: Initializing non-defaulted Objects X X The management station must now determine the X column requirements. It issues a management X protocol get operation to examine all columns in X the created conceptual row. In the response, for X each column, there are three possible outcomes: X X - a value is returned, indicating that the X agent implements the object-type associated X with this column and had sufficient X information to provide a value. For those X columns to which the agent provides read- X create access, a value return tells the X management station that it may issue X additional management protocol set X operations, if it desires, in order to change X the value associated with this column. X X - the exception 'noSuchInstance' is returned, X indicating that the agent implements the X object-type associated with this column, and X that this column in at least one conceptual X row would be accessible in the MIB view used X by the retrieval were it to exist. However, X the agent does not have sufficient X information to provide a value, and until a X value is provided, the conceptual row may not X be made available for use by the managed X device. For those columns to which the agent X provides read-create access, the X 'noSuchInstance' exception tells the X management station that it must issue X additional management protocol set X operations, in order to provide a value X associated with this column. X X - the exception 'noSuchObject' is returned, X indicating that the agent does not implement X the object-type associated with this column X or that there is no conceptual row for which X this column would be accessible in the MIB X view used by the retrieval. As such, the X management station can not issue any X management protocol set operations to create X X X an instance of this column. X X If the value associated with the status column is X 'notReady', then the management station must first X deal with all 'noSuchInstance' columns, if any. X Having done so, the value of the status column X becomes 'notInService', and we proceed to X interaction 4. X X Interaction 4: Making the Conceptual Row Available X X Once the management station is satisfied with the X values associated with the columns of the X conceptual row, it issues a management protocol X set operation to set the status column to X 'active'. If the agent has sufficient information X to make the conceptual row available for use by X the managed device, the management protocol set X operation succeeds (a 'noError' response is X returned). Otherwise, the management protocol set X operation fails with an error of X 'inconsistentValue'. X X NOTE WELL X X A conceptual row having a status column with X value 'notInService' or 'notReady' is X unavailable to the managed device. As such, X it is possible for the managed device to X create its own instances during the time X between the management protocol set operation X which sets the status column to X 'createAndWait' and the management protocol X set operation which sets the status column to X 'active'. In this case, when the management X protocol set operation is issued to set the X status column to 'active', the values held in X the agent supersede those used by the managed X device. X X If the management station is prevented from X setting the status column to 'active' (e.g., due X to management station or network failure) the X conceptual row will be left in the 'notInService' X or 'notReady' state, consuming resources X X X indefinitely. The agent must detect conceptual X rows that have been in either state for an X abnormally long period of time and remove them. X This period of time should be long enough to allow X for human response time (including 'think time') X between the creation of the conceptual row and the X setting of the status to 'active'. It is X suggested that this period be approximately 5 X minutes in length. X X Conceptual Row Suspension X X When a conceptual row is 'active', the management X station may issue a management protocol set X operation which sets the instance of the status X column to 'notInService'. If the agent is X unwilling to do so, the set operation fails with X an error of 'wrongValue'. Otherwise, the X conceptual row is taken out of service, and a X 'noError' response is returned. It is the X responsibility of the the DESCRIPTION clause of X the status column to indicate under what X circumstances the status column should be taken X out of service (e.g., in order for the value of X some other column of the same conceptual row to be X modified). X X Conceptual Row Deletion X X For deletion of conceptual rows, a management X protocol set operation is issued which sets the X instance of the status column to 'destroy'. This X request may be made regardless of the current X value of the status column (e.g., it is possible X to delete conceptual rows which are either X 'notReady', 'notInService' or 'active'.) If the X operation succeeds, then all instances associated X with the conceptual row are immediately removed." X X X SYNTAX INTEGER { X -- the following two values are states: X -- these values may be read or written X active(1), X notInService(2), X X -- the following value is a state: X -- this value may be read, but not written X notReady(3), X X -- the following three values are X -- actions: these values may be written, X -- but are never read X createAndGo(4), X createAndWait(5), X destroy(6) X } X X X TimeStamp ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "The value of MIB-II's sysUpTime object at which a X specific occurrence happened. The specific X occurrence must be defined in the description of X any object defined using this type." X SYNTAX TimeTicks X X TimeInterval ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "A period of time, measured in units of 0.01 X seconds." X SYNTAX INTEGER (0..2147483647) X X X DateAndTime ::= TEXTUAL-CONVENTION X DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d" X STATUS current X DESCRIPTION X "A date-time specification. X X field octets contents range X ----- ------ -------- ----- X 1 1-2 year 0..65536 X 2 3 month 1..12 X 3 4 day 1..31 X 4 5 hour 0..23 X 5 6 minutes 0..59 X 6 7 seconds 0..60 X (use 60 for leap-second) X 7 8 deci-seconds 0..9 X 8 9 direction from UTC '+' / '-' X 9 10 hours from UTC 0..11 X 10 11 minutes from UTC 0..59 X X For example, Tuesday May 26, 1992 at 1:30:15 PM X EDT would be displayed as: X X 1992-5-26,13:30:15.0,-4:0 X X Note that if only local time is known, then X timezone information (fields 8-10) is not X present." X SYNTAX OCTET STRING (SIZE (8 | 11)) X END SNMPv2-PARTY-MIB DEFINITIONS ::= BEGIN X X IMPORTS X MODULE-IDENTITY, OBJECT-TYPE, snmpModules, X UInteger32 X FROM SNMPv2-SMI X TEXTUAL-CONVENTION, RowStatus, TruthValue X FROM SNMPv2-TC X MODULE-COMPLIANCE, OBJECT-GROUP X FROM SNMPv2-CONF; X X partyMIB MODULE-IDENTITY X LAST-UPDATED "9304010000Z" X ORGANIZATION "IETF SNMP Security Working Group" X CONTACT-INFO X " Keith McCloghrie X X Postal: Hughes LAN Systems X 1225 Charleston Road X Mountain View, CA 94043 X US X X Tel: +1 415 966 7934 X Fax: +1 415 960 3738 X X E-mail: kzm@hls.com" X DESCRIPTION X "The MIB module describing SNMPv2 parties." X ::= { snmpModules 3 } X X X -- textual conventions X X Party ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Denotes a SNMPv2 party identifier. X X Note that agents may impose implementation X limitations on the length of OIDs used to identify X Parties. As such, management stations creating X new parties should be aware that using an X excessively long OID may result in the agent X refusing to perform the set operation and instead X returning the appropriate error response, e.g., X noCreation." X SYNTAX OBJECT IDENTIFIER X X TAddress ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Denotes a transport service address. X X For snmpUDPDomain, a TAddress is 6 octets long, X the initial 4 octets containing the IP-address in X network-byte order and the last 2 containing the X UDP port in network-byte order. Consult [5] for X further information on snmpUDPDomain." X SYNTAX OCTET STRING X X X Clock ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "A party's authentication clock - a non-negative X integer which is incremented as specified/allowed X by the party's Authentication Protocol. X X For noAuth, a party's authentication clock is X unused and its value is undefined. X X For v2md5AuthProtocol, a party's authentication X clock is a relative clock with 1-second X granularity." X SYNTAX UInteger32 X X Context ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Denotes a SNMPv2 context identifier. X X Note that agents may impose implementation X limitations on the length of OIDs used to identify X Contexts. As such, management stations creating new X contexts should be aware that using an excessively X long OID may result in the agent refusing to X perform the set operation and instead returning X the appropriate error response, e.g., noCreation." X SYNTAX OBJECT IDENTIFIER X X X StorageType ::= TEXTUAL-CONVENTION X STATUS current X DESCRIPTION X "Describes the memory realization of a conceptual X row. A row which is volatile(2) is lost upon X reboot. A row which is nonVolatile(3) is backed X up by stable storage. A row which is permanent(4) X cannot be changed nor deleted." X SYNTAX INTEGER { X other(1), -- eh? X volatile(2), -- e.g., in RAM X nonVolatile(3), -- e.g., in NVRAM X permanent(4) -- e.g., in ROM X } X X X -- administrative assignments X X partyAdmin OBJECT IDENTIFIER ::= { partyMIB 1 } X X -- definitions of security protocols X X partyProtocols OBJECT IDENTIFIER ::= { partyAdmin 1 } X X -- the protocol without authentication X noAuth OBJECT IDENTIFIER ::= { partyProtocols 1 } X X -- the protocol without privacy X noPriv OBJECT IDENTIFIER ::= { partyProtocols 2 } X X -- the DES Privacy Protocol [4] X desPrivProtocol X OBJECT IDENTIFIER ::= { partyProtocols 3 } X X -- the MD5 Authentication Protocol [4] X v2md5AuthProtocol X OBJECT IDENTIFIER ::= { partyProtocols 4 } SHAR_EOF : || echo 'restore of snmp2/mib.txt failed' fi echo 'End of snmp2 part 13' echo 'File snmp2/mib.txt is continued in part 14' echo 14 > _sharseq.tmp exit 0