o BŠ]ý`ã@se dddd¡\ZZZe dd¡\Ze dddd d d ¡\ZZZZ Z e d d ddd¡\Z Z Z Ze dddd¡\ZZZe dddddddddddd d!d"d#d$d%d&d'¡\ZZZZZZZZZZZZZZZ Z!Z"Z#e d(d)d*d+d,d-d.d/d0¡ \Z$Z%Z&Z'Z(Z)Z*Z+ed1ƒZ,ej-rƒe, .d2¡ej-r‹e, /d3¡ej-r“e, 0d4¡ej-r›e, 1d5¡ej-r£e, 2d6¡ed7ƒZ3ed8ƒZ4Gd9d:„d:e&eƒZ5Gd;d<„d¡Z8ej-rÎe8 9d?¡ej-rÖe8 2d@¡edAƒZ:ej-râe: 9d?¡ej-rêe: 2dB¡edCƒ ;dD¡Zej-re> 9d?¡ej-r!e> 2dJ¡edKe*ƒƒ 7dL¡Z?ej-r3e? 9d?¡ej-r“d¶eF“Žd·S)¹ZASN1ÚObjectIdentifierÚIntegerÚ OctetStringzASN1-ENUMERATIONÚ NamedValueszASN1-REFINEMENTÚConstraintsIntersectionÚValueSizeConstraintÚConstraintsUnionÚSingleValueConstraintÚValueRangeConstraintzSNMP-FRAMEWORK-MIBÚSnmpAdminStringÚSnmpSecurityLevelÚSnmpMessageProcessingModelÚSnmpSecurityModelz SNMPv2-CONFÚModuleComplianceÚ ObjectGroupÚNotificationGroupz SNMPv2-SMIÚ MibIdentifierÚ MibScalarÚMibTableÚ MibTableRowÚMibTableColumnÚisoÚ Counter32ÚObjectIdentityÚBitsÚNotificationTypeÚ Unsigned32Ú IpAddressÚ Integer32ÚModuleIdentityÚ snmpModulesÚ TimeTicksÚGauge32Ú Counter64z SNMPv2-TCÚ TimeIntervalÚ RowStatusÚTextualConventionÚ TestAndIncrÚTAddressÚ StorageTypeÚTDomainÚ DisplayString)ééér+r-r,é )z2002-10-14 00:00z1998-08-04 00:00z1997-07-14 00:00Z 200210140000ZzIETF SNMPv3 Working Groupa WG-email: snmpv3@lists.tislabs.com Subscribe: majordomo@lists.tislabs.com In message body: subscribe snmpv3 Co-Chair: Russ Mundy Network Associates Laboratories Postal: 15204 Omega Drive, Suite 300 Rockville, MD 20850-4601 USA EMail: mundy@tislabs.com Phone: +1 301-947-7107 Co-Chair: David Harrington Enterasys Networks Postal: 35 Industrial Way P. O. Box 5004 Rochester, New Hampshire 03866-5005 USA EMail: dbh@enterasys.com Phone: +1 603-337-2614 Co-editor: David B. Levi Nortel Networks Postal: 3505 Kesterwood Drive Knoxville, Tennessee 37918 EMail: dlevi@nortelnetworks.com Phone: +1 865 686 0432 Co-editor: Paul Meyer Secure Computing Corporation Postal: 2675 Long Lake Road Roseville, Minnesota 55113 EMail: paul_meyer@securecomputing.com Phone: +1 651 628 1592 Co-editor: Bob Stewart Retireda)This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3413; see the RFC itself for full legal notices. )r+r,r-r+r-r,r.r+)r+r,r-r+r-r,r.r,c@ó8eZdZdZdZdZejeddƒZdZ dZ dd „Z d S) Ú SnmpTagListacAn octet string containing a list of tag values. Tag values are 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 character encoding scheme described in RFC 2279. 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. The use of control codes should be avoided, except as described below. 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 representation is identical to the US-ASCII encoding. An object of this type contains a list of tag values which are used to select a set of entries in a table. A tag value is an arbitrary string of octets, but may not contain a delimiter character. Delimiter characters are defined to be one of the following: - An ASCII space character (0x20). - An ASCII TAB character (0x09). - An ASCII carriage return (CR) character (0x0D). - An ASCII line feed (LF) character (0x0A). Delimiter characters are used to separate tag values in a tag list. Only a single delimiter character may occur between two tag values. A tag value may not have a zero length. These constraints imply certain restrictions on the contents of this object: - There cannot be a leading or trailing delimiter character. - There cannot be multiple adjacent delimiter characters. Some examples of valid tag lists are: - '' -- an empty list - 'acme' -- list of one tag - 'host router bridge' -- list of several tags Note that although a tag value may not have a length of zero, an empty string is still valid. This indicates an empty list (i.e. there are no tag values in the list). The use of the tag list to select table entries is application and MIB specific. Typically, an application will provide one or more tag values, and any entry which contains some combination of these tag values will be selected.ÚcurrentÚ255tééÿúutf-8©ú Ú ú r9cCsZd}t|ƒD]}||jvr|rt d|¡‚d}qd}q|r'|r't d|¡‚t ||¡S)NTz9Leading or multiple delimiters not allowed in tag list %rFz-Dangling delimiter not allowed in tag list %r©ÚstrÚ _delimitersÚerrorZSmiErrorrÚprettyIn)ÚselfÚvalueZinDelimÚv©rBúA/usr/lib/python3/dist-packages/pysnmp/smi/mibs/SNMP-TARGET-MIB.pyr>)s   zSnmpTagList.prettyInN© Ú__name__Ú __module__Ú __qualname__Ú descriptionÚstatusZ displayHintrÚ subtypeSpecrÚencodingr<r>rBrBrBrCr0!ó r0c@r/) Ú SnmpTagValuea An octet string containing a tag value. Tag values are 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 character encoding scheme described in RFC 2279. 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. The use of control codes should be avoided, and certain control codes are not allowed as described below. 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 representation is identical to the US-ASCII 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 [RFC1905]. An object of this type contains a single tag value which is used to select a set of entries in a table. A tag value is an arbitrary string of octets, but may not contain a delimiter character. Delimiter characters are defined to be one of the following: - An ASCII space character (0x20). - An ASCII TAB character (0x09). - An ASCII carriage return (CR) character (0x0D). - An ASCII line feed (LF) character (0x0A). Delimiter characters are used to separate tag values in a tag list. An object of this type may only contain a single tag value, and so delimiter characters are not allowed in a value of this type. Note that a tag value of 0 length means that no tag is defined. In other words, a tag value of 0 length would never match anything in a tag list, and would never select any table entries. Some examples of valid tag values are: - 'acme' - 'router' - 'host' The use of a tag value to select table entries is application and MIB specific.r1r2r3r4r5r6cCs.t|ƒD] }||jvrt d¡‚qt ||¡S)Nz#Delimiters not allowed in tag valuer:)r?r@rArBrBrCr>?s   ÿ zSnmpTagValue.prettyInNrDrBrBrBrCrM7rLrM) r+r,r-r+r-r,r.r+r+Z readwriter1aUThis object is used to facilitate modification of table entries in the SNMP-TARGET-MIB module by multiple managers. In particular, it is useful when modifying the value of the snmpTargetAddrTagList object. The procedure for modifying the snmpTargetAddrTagList object is as follows: 1. Retrieve the value of snmpTargetSpinLock and of snmpTargetAddrTagList. 2. Generate a new value for snmpTargetAddrTagList. 3. Set the value of snmpTargetSpinLock to the retrieved value, and the value of snmpTargetAddrTagList to the new value. If the set fails for the snmpTargetSpinLock object, go back to step 1.) r+r,r-r+r-r,r.r+ézMA table of transport addresses to be used in the generation of SNMP messages.) r+r,r-r+r-r,r.r+rNr+)r+úSNMP-TARGET-MIBÚsnmpTargetAddrNamez©A transport address to be used in the generation of SNMP operations. Entries in the snmpTargetAddrTable are created and deleted using the snmpTargetAddrRowStatus object.) r+r,r-r+r-r,r.r+rNr+r+r+é )rJzVThe locally arbitrary, but unique identifier associated with this snmpTargetAddrEntry.) r+r,r-r+r-r,r.r+rNr+rNZ readcreatezgThis object indicates the transport type of the address contained in the snmpTargetAddrTAddress object.) r+r,r-r+r-r,r.r+rNr+r,z~This object contains a transport address. The format of this address depends on the value of the snmpTargetAddrTDomain object.) r+r,r-r+r-r,r.r+rNr+éiÜaùThis object should reflect the expected maximum round trip time for communicating with the transport address defined by this row. When a message is sent to this address, and a response (if one is expected) is not received within this time period, an implementation may assume that the response will not be delivered. Note that the time interval that an application waits for a response may actually be derived from the value of this object. The method for deriving the actual time interval is implementation dependent. One such method is to derive the expected round trip time based on a particular retransmission algorithm and on the number of timeouts which have occurred. The type of message may also be considered when deriving expected round trip times for retransmissions. For example, if a message is being sent with a securityLevel that indicates both authentication and privacy, the derived value may be increased to compensate for extra processing time spent during authentication and encryption processing.) r+r,r-r+r-r,r.r+rNr+ér3r4r,zÝThis object specifies a default number of retries to be attempted when a response is not received for a generated message. An application may provide its own retry count, in which case the value of this object is ignored.) r+r,r-r+r-r,r.r+rNr+r-zoThis object contains a list of tag values which are used to select target addresses for a particular operation.) r+r,r-r+r-r,r.r+rNr+ézÂThe value of this object identifies an entry in the snmpTargetParamsTable. The identified entry contains SNMP parameters to be used when generating messages to be sent to this transport address.) r+r,r-r+r-r,r.r+rNr+éZ nonVolatilez–The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.) r+r,r-r+r-r,r.r+rNr+é aúThe status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTargetAddrRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding instances of snmpTargetAddrTDomain, snmpTargetAddrTAddress, and snmpTargetAddrParams have all been set. The following objects may not be modified while the value of this object is active(1): - snmpTargetAddrTDomain - snmpTargetAddrTAddress An attempt to set these objects while the value of snmpTargetAddrRowStatus is active(1) will result in an inconsistentValue error.) r+r,r-r+r-r,r.r+r,zQA table of SNMP target information to be used in the generation of SNMP messages.) r+r,r-r+r-r,r.r+r,r+)r+rOÚsnmpTargetParamsNamezŠA set of SNMP target information. Entries in the snmpTargetParamsTable are created and deleted using the snmpTargetParamsRowStatus object.) r+r,r-r+r-r,r.r+r,r+r+zXThe locally arbitrary, but unique identifier associated with this snmpTargetParamsEntry.) r+r,r-r+r-r,r.r+r,r+rNzWThe Message Processing Model to be used when generating SNMP messages using this entry.) r+r,r-r+r-r,r.r+r,r+r,iÿÿÿaThe Security Model to be used when generating SNMP messages using this entry. An implementation may choose to return an inconsistentValue error if an attempt is made to set this variable to a value for a security model which the implementation does not support.) r+r,r-r+r-r,r.r+r,r+rRzqThe securityName which identifies the Principal on whose behalf SNMP messages will be generated using this entry.) r+r,r-r+r-r,r.r+r,r+rSzPThe Level of Security to be used when generating SNMP messages using this entry.) r+r,r-r+r-r,r.r+r,r+r-) r+r,r-r+r-r,r.r+r,r+rTaiThe status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTargetParamsRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding snmpTargetParamsMPModel, snmpTargetParamsSecurityModel, snmpTargetParamsSecurityName, and snmpTargetParamsSecurityLevel have all been set. The following objects may not be modified while the value of this object is active(1): - snmpTargetParamsMPModel - snmpTargetParamsSecurityModel - snmpTargetParamsSecurityName - snmpTargetParamsSecurityLevel An attempt to set these objects while the value of snmpTargetParamsRowStatus is active(1) will result in an inconsistentValue error.) r+r,r-r+r-r,r.r+rRÚreadonlyzˆThe total number of packets received by the SNMP engine which were dropped because the context contained in the message was unavailable.) r+r,r-r+r-r,r.r+rSz„The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unknown.) r+r,r-r+r-r,r.r,r+) r+r,r-r+r-r,r.r,rN) r+r,r-r+r-r,r.r,r+r+)rOÚsnmpTargetCommandResponderGroupzYThe compliance statement for SNMP entities which include a command responder application.) r+r,r-r+r-r,r.r,rNr+)rOÚsnmpTargetSpinLock)rOÚsnmpTargetAddrTDomain)rOÚsnmpTargetAddrTAddress)rOÚsnmpTargetAddrTagList)rOÚsnmpTargetAddrParams)rOÚsnmpTargetAddrStorageType)rOÚsnmpTargetAddrRowStatus)rOÚsnmpTargetParamsMPModel)rOÚsnmpTargetParamsSecurityModel)rOÚsnmpTargetParamsSecurityName)rOÚsnmpTargetParamsSecurityLevel)rOÚsnmpTargetParamsStorageType)rOÚsnmpTargetParamsRowStatuszSA collection of objects providing basic remote configuration of management targets.) r+r,r-r+r-r,r.r,rNrN)rOÚsnmpTargetAddrTimeout)rOÚsnmpTargetAddrRetryCountzªA collection of objects providing remote configuration of management targets for applications which generate SNMP messages for which a response message would be expected.) r+r,r-r+r-r,r.r,rNr,)rOÚsnmpUnavailableContexts)rOÚsnmpUnknownContextszhA collection of objects required for command responder applications, used for counting error conditions.rOrgrbrdÚsnmpTargetParamsTableÚsnmpTargetAddrEntryr^rcrarZr\ÚsnmpTargetResponseGroupÚsnmpTargetCompliancesÚ snmpTargetMIBriÚ$snmpTargetCommandResponderComplianceÚsnmpTargetParamsEntryrjrWr[ÚsnmpTargetAddrTableÚsnmpTargetObjectsÚsnmpTargetBasicGrouprhr]r`rerYÚsnmpTargetConformancerfÚsnmpTargetGroupsZPYSNMP_MODULE_IDrPr_N)rO)[Z mibBuilderZ importSymbolsrrrrrrrrr r r r r rrrrrrrrrrrrrrrrrrr r!r"r#r$r%r&r'r(r)r*roZ loadTextsZ setRevisionsZsetLastUpdatedZsetOrganizationZsetContactInfoZsetDescriptionrsrur0rMZ setMaxAccessrZZ setStatusrrZ setIndexNamesrlZsubtyperPr[r\Zclonergrhr]r^r_r`rkrqrWrarbrcrdrerfrirjrnrvZ setObjectsrprtrmrYZ exportSymbolsrBrBrBrCÚs R*&  &â