o B]5q@sTddlZddlZddlZddlTddlmZddlmZddlm Z ddl m Z e ddd d \ZZZe d d \Ze d ddddd\ZZZZZe ddddd\ZZZZGdddeZGdddeeZGdddeeZGdddeeZGd d!d!eeZ Gd"d#d#eeZ!Gd$d%d%eeZ"Gd&d'd'eeZ#Gd(d)d)eeZ$Gd*d+d+eeZ%Gd,d-d-eeZ&Gd.d/d/eeZ'Gd0d1d1eeZ(Gd2d3d3eeZ)Gd4d5d5eeZ*Gd6d7d7eeZ+Gd8d9d9eeZ,e j- :d;idedededed!e d#e!d%e"d'e#d)e$d+e%d-e&d/e'd1e(d3e)d5e*d7e+d9e,dS)<N)*)debug)univ)octets)Asn1ItemZASN1 OctetStringIntegerObjectIdentifierzASN1-ENUMERATION NamedValueszASN1-REFINEMENTConstraintsIntersectionConstraintsUnionSingleValueConstraintValueRangeConstraintValueSizeConstraintz SNMPv2-SMI Counter32 Unsigned32 TimeTicks Counter64c@sxeZdZdZdZdZdZdZeZ e Z e Z eZddZddZdd Zd d Zd d ZddZddZddZdS)TextualConventioncurrentcC|jSN) displayHintselfrr;/usr/lib/python3/dist-packages/pysnmp/smi/mibs/SNMPv2-TC.pygetDisplayHint!z TextualConvention.getDisplayHintcCrr)statusrrrr getStatus$rzTextualConvention.getStatuscCrr) descriptionrrrrgetDescription'rz TextualConvention.getDescriptioncCrr) referencerrrr getReference*rzTextualConvention.getReferencecCs|Sr)clonerrrrgetValue-szTextualConvention.getValuecCs|durtj}||Sr)rnoValuer&rvaluerrrsetValue0s zTextualConvention.setValuecCs^|jr|jj|ddr|r|jj|dds|jj|ddrd%dd}||jd\}}|dkr6d|S|d kr^zd t|t|t d t|fWSt y]t d t d w|dkrfd|S|dkr|}dg}|r|dd|d @|d L}|sqd|St d||jjf|jr |jj|ddr d}t|}|j}|r |r |ddkrt|d}} |d d}|d d}nd } d}d} |r|dtjvr| |d7} |d d}|r|dtjvs| st|} zt| } Wnt yt d| w|st d|j|d} |d d}|r:|dtjvr:|ddkr:|d} |d d}nd} |rT| rT|durT|d} d} |d d}nd} | r| d 8} | dkro||d| dd7}nt| dkr||d| dd7}nb| dvrd}|d| }|r|dK}z|t|dO}|d d}Wnt yt d |t d fw|s| dkr|d!|7}n| dkr|d"|7}n |d|7}nt d#| |r| r|| 7}|| d}| sY|r| r|| 7}|s|j}|r |s|St|jD]}t|ts)t|tr)| ||Sqt d$)&z"Implements DISPLAY-HINT evaluationFZmatchConstraintsrcS||fSrrtfrrr:z-TextualConvention.prettyOut..-xz0x%xdz%.*f float evaluation error: %soz0%obBz%dr(Unsupported numeric type spec "%s" at %srNBad octet length: %sShort octet length: %saasciiignorer/zutf-8r4r5r9#Display format eval failure: %s: %sz%02xz%03o#Unsupported display format char: %s3TEXTUAL-CONVENTION has no underlying SNMP base typer)!r_TextualConvention__integer isSuperTypeOfgetNamedValues_TextualConvention__unsigned32_TextualConvention__timetickssplitintfloatpow ExceptionSmiErrorsysexc_infoinsertjoin __class____name___TextualConvention__octetStringrZasOctetsrZoct2intstringdigitslendecodeinspectgetmro issubclassrr prettyOut)rr*_displayHintTypedecimalPrecision runningValue outputValuerZrepeatIndicatorZ repeatCount octetLength displayFormat displaySepZrepeatTerminatorZnumberZ numberStringbaserrrra5s $          $         ! YzTextualConvention.prettyOutcCst|jD]}t|tst|trnqtd|jr,|jj |ddr)| s:|j j |dds:|j j |ddr,t |}d+dd}||jd\}}|dkr|d s[|d rz"|drp||t|d d d  WS||t|dd d WStytdtdw|dkrz||tt|dt|WStytdtdw|dkr|ds|drz ||t|dWStytdtdw|dkr"|ds|dr"|d}|r|dd }n|dd }dd|D}d}|r||dK}|d=|s|||Std||jjf|jr|jj |ddrd ddd}ttjttjttjd } t|rdt|sd|||}n|||Std!} |} |j} | r| r| dd"krtd#|jjd!} | r| dtjvr| | d7} | dd } | r| dtjvs| st | } zt| } Wntytd$| w| std%|j| d}| dd } | r| dtjvr| dd"kr| d}| dd } nd!}|d&vr | | d | 7} n||vr|r$| !t|}|d'kr#t | }nt"t | D]}| || |vr9|}nq*t | }ztt#| d |||}Wntygtd(| d |tdfwg}|r|r~|$|d)@|dL}|spndg}t || kr|$dt || ks|%| t&|7} |r|d7}|} ntd*|| | d } | s|j} | r| sz||| S|||S),a\Implements DISPLAY-HINT parsing into base SNMP value Proper parsing seems impossible due to ambiguities. Here we are trying to do our best, but be prepared for failures on complicated DISPLAY-HINTs. Keep in mind that this parser only works with "text" input meaning `unicode` (Py2) or `str` (Py3). rFFr,rcSr-rrr.rrrr1r2z,TextualConvention.prettyIn..r3r40xz-0xNzinteger evaluation error: %sr8r5r6r7r90z-0rCzoctal evaluation error: %sr:r;z-BcSsg|] }|dkr dp dqS)ror8rr).0r4rrr sz.TextualConvention.prettyIn..r<rB)r4r9r5rrz$Can't parse "*" in DISPLAY-HINT (%s)r=r>)r?r/rDrErG)'r^r_rWr`rrrRrrHrIrJrKrLstrrM startswithprettyInrNrQrSrTrOrXrYrZstr2octsrZZ hexdigitsZ octdigitsr[Z isStringTypeZ isOctetsTyper\findrangeZocts2strappendreverseZ ints2octs)rr*rjrbrcrdnegativeZbinValueZnumBaseZ numDigitsrfrerrgrhriZguessedOctetLengthidxZnumZ num_as_bytesrrrrvs,    "                   $       _ zTextualConvention.prettyInN)rX __module__ __qualname__rr r"r$bitsrrHrrKrrLrrYrr!r#r%r'r+rarvrrrrrs& rc@(eZdZdZdZejeddZdZdS) DisplayString8Represents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length.rrrsZ255aN rXr}r~r"r r subtypeSpecrrrrrrru rc@eZdZdZdZdZdS) PhysAddressrr1x:N)rXr}r~r"r rrrrrr|rc@s,eZdZdZdZejeddZdZdZ dS) MacAddressaRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first.rrN) rXr}r~r"r rrrrZ fixedLengthrrrrrs rc@s.eZdZdZdZejeddZeddZ dS) TruthValuezRepresents a boolean value.rr8rn)truer8)ZfalsernN rXr}r~r"r rrr r namedValuesrrrrrs rc@s0eZdZdZdZejeddZdZddZ dS) TestAndIncraRepresents integer-valued information used for atomic operations. When the management protocol is used to specify that an object instance having this syntax is to be modified, the new value supplied via the management protocol must precisely match the value presently held by the instance. If not, the management protocol set operation fails with an error of `inconsistentValue'. Otherwise, if the current value is the maximum value of 2^31-1 (2147483647 decimal), then the value held by the instance is wrapped to zero; otherwise, the value held by the instance is incremented by one. (Note that regardless of whether the management protocol set operation succeeds, the variable- binding in the request and response PDUs are identical.) The value of the ACCESS clause for objects having this syntax is either `read-write' or `read-create'. When an instance of a columnar object having this syntax is created, any value may be supplied via the management protocol. When the network management portion of the system is re- initialized, the value of every object instance having this syntax must either be incremented from its value prior to the re-initialization, or (if the value prior to the re- initialization is unknown) be set to a pseudo-randomly generated value.rrcCsB|dur||kr t|d7}|dkrd}|durtj}||S)Nr8ir)InconsistentValueErrorrr(r&r)rrrr+s zTestAndIncr.setValueN) rXr}r~r"r rrrZ defaultValuer+rrrrrs  rc@eZdZdZdZdS)AutonomousTypezRepresents an independently extensible type identification value. It may, for example, indicate a particular sub-tree with further MIB definitions, or define a particular type of protocol or hardware.rNrXr}r~r"r rrrrrrc@r)InstancePointeracA pointer to either a specific instance of a MIB object or a conceptual row of a MIB table in the managed device. In the latter case, by convention, it is the name of the particular instance of the first accessible columnar object in the conceptual row. The two uses of this textual convention are replaced by VariablePointer and RowPointer, respectively.ZobsoleteNrrrrrrrrc@r)VariablePointerzSA pointer to a specific object instance. For example, sysContact.0 or ifInOctets.3.rNrrrrrrrrc@r) RowPointera!Represents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead).rNrrrrrrrrc @seZdZdZdZdZejedddddd d Ze d d d ddddZ e e d\Z ZZZZZZiee feefeefeefeefeefeefeefee feefeefeefeefeefeefeefee fee feefeefeefdefeefdefee fee feefeefeefdefeefdefee fee feefee feefee feefee fe e fde fiZddZdS) RowStatuszeA special kind of scalar MIB variable responsible for MIB table row creation/destruction. zThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].)...rrr8rnrlr)Z notExistsr)Zactiver8)Z notInServicern)ZnotReadyrl)Z createAndGor)Z createAndWaitr)ZdestroyrNcCs|durtj}||}|j|r|p|j|r|p|jftdf\}}|dur.tj}||}tj tj @oCt d||||f|durU|d|||f|d}||S)NzORowStatus state change from %r to %r produced new state %r, error indication %rzMException at row state transition from %r to %r yields state %r and exception)msgZsyntax) rr(r& stateMatrixgetZhasValue stNotExistsZMibOperationErrorrloggerZflagIns)rr*ZexcValueZnewStaterrrr+s6  zRowStatus.setValue)rXr}r~__doc__r"r rrr r rlistrxrZstActiveZstNotInServiceZ stNotReadyZ stCreateAndGoZstCreateAndWaitZ stDestroyZRowCreationWantedrZRowDestructionWantedrr+rrrrrsl                       rc@r) TimeStampa_The value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects.rNrrrrrrrrc@s$eZdZdZdZejeddZdS) TimeIntervalz4A period of time, measured in units of 0.01 seconds.rrrN)rXr}r~r"r rrrrrrrr src@r) DateAndTimeagA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present.rrC z2d-1d-1d,1d:1d:1d.1d,1a1d:1dNrrrrrrrrc@s:eZdZdZdZejedddddZedd d d d Z d S) StorageTypeaDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable.rr8rnrlrr)otherr8)Zvolatilern)Z nonVolatilerl)Z permanentr)ZreadOnlyrNrrrrrrsrc@r)TDomain0The SNMPv2-TM MIB module is defined in RFC 1906.zDenotes a kind of transport service. Some possible values, such as snmpUDPDomain, are defined in the SNMPv2-TM MIB module. Other possible values are defined in other MIB modules.rN)rXr}r~r$r"r rrrrr"rrc@s(eZdZdZdZdZejeddZdS)TAddressraDenotes a transport service address. A TAddress value is always interpreted within the context of a TDomain value. Thus, each definition of a TDomain value must be accompanied by a definition of a textual convention for use with that TDomain. Some possible textual conventions, such as SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM MIB module. Other possible textual conventions are defined in other MIB modules.rr8rsN) rXr}r~r$r"r rrrrrrrr(s r SNMPv2-TC)r).rSr^rZZpysnmp.smi.errorZpysnmprZ pyasn1.typerZ pyasn1.compatrZpyasn1.type.baserZ mibBuilderZ importSymbolsrrr r r r r rrrrrrobjectrrrrrrrrrrrrrrrrrZ exportSymbolsrrrrs    aP