Node-Red configuration
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

SNMPv2-TC.mib 31KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535
  1. SNMPv2-TC DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. ObjectSyntax, TimeTicks FROM SNMPv2-SMI;
  4. -- definition of textual conventions
  5. TEXTUAL-CONVENTION MACRO ::=
  6. BEGIN
  7. TYPE NOTATION ::=
  8. DisplayPart
  9. "STATUS" Status
  10. "DESCRIPTION" Text
  11. ReferPart
  12. "SYNTAX" Syntax
  13. VALUE NOTATION ::=
  14. value(VALUE Syntax)
  15. DisplayPart ::=
  16. "DISPLAY-HINT" Text
  17. | empty
  18. Status ::=
  19. "current"
  20. | "deprecated"
  21. | "obsolete"
  22. ReferPart ::=
  23. "REFERENCE" Text
  24. | empty
  25. -- uses the NVT ASCII character set
  26. Text ::= """" string """"
  27. Syntax ::=
  28. type(ObjectSyntax)
  29. | "BITS" "{" Kibbles "}"
  30. Kibbles ::=
  31. Kibble
  32. | Kibbles "," Kibble
  33. Kibble ::=
  34. identifier "(" nonNegativeNumber ")"
  35. END
  36. DisplayString ::= TEXTUAL-CONVENTION
  37. DISPLAY-HINT "255a"
  38. STATUS current
  39. DESCRIPTION
  40. "Represents textual information taken from the NVT ASCII
  41. character set, as defined in pages 4, 10-11 of RFC 854.
  42. To summarize RFC 854, the NVT ASCII repertoire specifies:
  43. - the use of character codes 0-127 (decimal)
  44. - the graphics characters (32-126) are interpreted as
  45. US ASCII
  46. - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
  47. meanings specified in RFC 854
  48. - the other 25 codes have no standard interpretation
  49. - the sequence 'CR LF' means newline
  50. - the sequence 'CR NUL' means carriage-return
  51. - an 'LF' not preceded by a 'CR' means moving to the
  52. same column on the next line.
  53. - the sequence 'CR x' for any x other than LF or NUL is
  54. illegal. (Note that this also means that a string may
  55. end with either 'CR LF' or 'CR NUL', but not with CR.)
  56. Any object defined using this syntax may not exceed 255 characters in length."
  57. SYNTAX OCTET STRING (SIZE (0..255))
  58. PhysAddress ::= TEXTUAL-CONVENTION
  59. DISPLAY-HINT "1x:"
  60. STATUS current
  61. DESCRIPTION
  62. "Represents media- or physical-level addresses."
  63. SYNTAX OCTET STRING
  64. MacAddress ::= TEXTUAL-CONVENTION
  65. DISPLAY-HINT "1x:"
  66. STATUS current
  67. DESCRIPTION
  68. "Represents an 802 MAC address represented in the
  69. `canonical' order defined by IEEE 802.1a, i.e., as if it
  70. were transmitted least significant bit first, even though
  71. 802.5 (in contrast to other 802.x protocols) requires MAC
  72. addresses to be transmitted most significant bit first."
  73. SYNTAX OCTET STRING (SIZE (6))
  74. TruthValue ::= TEXTUAL-CONVENTION
  75. STATUS current
  76. DESCRIPTION
  77. "Represents a boolean value."
  78. SYNTAX INTEGER { true(1), false(2) }
  79. TestAndIncr ::= TEXTUAL-CONVENTION
  80. STATUS current
  81. DESCRIPTION
  82. "Represents integer-valued information used for atomic
  83. operations. When the management protocol is used to specify
  84. that an object instance having this syntax is to be
  85. modified, the new value supplied via the management protocol
  86. must precisely match the value presently held by the
  87. instance. If not, the management protocol set operation
  88. fails with an error of `inconsistentValue'. Otherwise, if
  89. the current value is the maximum value of 2^31-1 (2147483647
  90. decimal), then the value held by the instance is wrapped to
  91. zero; otherwise, the value held by the instance is
  92. incremented by one. (Note that regardless of whether the
  93. management protocol set operation succeeds, the variable-
  94. binding in the request and response PDUs are identical.)
  95. 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.
  96. 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."
  97. SYNTAX INTEGER (0..2147483647)
  98. AutonomousType ::= TEXTUAL-CONVENTION
  99. STATUS current
  100. DESCRIPTION
  101. "Represents an independently extensible type identification
  102. value. It may, for example, indicate a particular sub-tree
  103. with further MIB definitions, or define a particular type of
  104. protocol or hardware."
  105. SYNTAX OBJECT IDENTIFIER
  106. InstancePointer ::= TEXTUAL-CONVENTION
  107. STATUS obsolete
  108. DESCRIPTION
  109. "A pointer to either a specific instance of a MIB object or
  110. a conceptual row of a MIB table in the managed device. In
  111. the latter case, by convention, it is the name of the
  112. particular instance of the first accessible columnar object
  113. in the conceptual row.
  114. The two uses of this textual convention are replaced by VariablePointer and RowPointer, respectively."
  115. SYNTAX OBJECT IDENTIFIER
  116. VariablePointer ::= TEXTUAL-CONVENTION
  117. STATUS current
  118. DESCRIPTION
  119. "A pointer to a specific object instance. For example,
  120. sysContact.0 or ifInOctets.3."
  121. SYNTAX OBJECT IDENTIFIER
  122. RowPointer ::= TEXTUAL-CONVENTION
  123. STATUS current
  124. DESCRIPTION
  125. "Represents a pointer to a conceptual row. The value is the
  126. name of the instance of the first accessible columnar object
  127. in the conceptual row.
  128. 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)."
  129. SYNTAX OBJECT IDENTIFIER
  130. RowStatus ::= TEXTUAL-CONVENTION
  131. STATUS current
  132. DESCRIPTION
  133. "The RowStatus textual convention is used to manage the
  134. 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].)
  135. The status column has six defined values:
  136. - `active', which indicates that the conceptual row is
  137. available for use by the managed device;
  138. - `notInService', which indicates that the conceptual
  139. row exists in the agent, but is unavailable for use by
  140. the managed device (see NOTE below);
  141. - `notReady', which indicates that the conceptual row
  142. exists in the agent, but is missing information
  143. necessary in order to be available for use by the
  144. managed device;
  145. - `createAndGo', which is supplied by a management
  146. station wishing to create a new instance of a
  147. conceptual row and to have its status automatically set
  148. to active, making it available for use by the managed
  149. device;
  150. - `createAndWait', which is supplied by a management
  151. station wishing to create a new instance of a
  152. conceptual row (but not make it available for use by
  153. the managed device); and,
  154. - `destroy', which is supplied by a management station
  155. wishing to delete all of the instances associated with
  156. an existing conceptual row.
  157. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady').
  158. NOTE WELL
  159. This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'.
  160. Also note that whenever any elements of a row exist, the RowStatus column must also exist.
  161. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram:
  162. STATE
  163. +--------------+-----------+-------------+-------------
  164. | A | B | C | D
  165. | |status col.|status column|
  166. |status column | is | is |status column
  167. ACTION |does not exist| notReady | notInService| is active
  168. --------------+--------------+-----------+-------------+-------------
  169. set status |noError ->D|inconsist- |inconsistent-|inconsistent-
  170. column to | or | entValue| Value| Value
  171. createAndGo |inconsistent- | | |
  172. | Value| | |
  173. --------------+--------------+-----------+-------------+-------------
  174. set status |noError see 1|inconsist- |inconsistent-|inconsistent-
  175. column to | or | entValue| Value| Value
  176. createAndWait |wrongValue | | |
  177. --------------+--------------+-----------+-------------+-------------
  178. set status |inconsistent- |inconsist- |noError |noError
  179. column to | Value| entValue| |
  180. active | | | |
  181. | | or | |
  182. | | | |
  183. | |see 2 ->D| ->D| ->D
  184. --------------+--------------+-----------+-------------+-------------
  185. set status |inconsistent- |inconsist- |noError |noError ->C
  186. column to | Value| entValue| |
  187. notInService | | | |
  188. | | or | | or
  189. | | | |
  190. | |see 3 ->C| ->C|wrongValue
  191. --------------+--------------+-----------+-------------+-------------
  192. set status |noError |noError |noError |noError
  193. column to | | | |
  194. destroy | ->A| ->A| ->A| ->A
  195. --------------+--------------+-----------+-------------+-------------
  196. set any other |see 4 |noError |noError |see 5
  197. column to some| | | |
  198. value | | see 1| ->C| ->D
  199. --------------+--------------+-----------+-------------+-------------
  200. (1) goto B or C, depending on information available to the agent.
  201. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, then return noError and goto D.
  202. (3) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, then return noError and goto C.
  203. (4) at the discretion of the agent, the return value may be either:
  204. inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or
  205. inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or
  206. noError: because the agent chooses to create the instance.
  207. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A.
  208. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned.
  209. NOTE: Other processing of the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc.
  210. Conceptual Row Creation
  211. There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device.
  212. Interaction 1: Selecting an Instance-Identifier
  213. The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics.
  214. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.)
  215. Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different.
  216. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation.
  217. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used.
  218. Interaction 2: Creating the Conceptual Row
  219. Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.
  220. Interaction 2a: Creating and Activating the Conceptual Row
  221. The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes:
  222. - a value is returned, indicating that some other
  223. management station has already created this conceptual
  224. row. We return to interaction 1.
  225. - the exception `noSuchInstance' is returned,
  226. indicating that the agent implements the object-type
  227. associated with this column, and that this column in at
  228. least one conceptual row would be accessible in the MIB
  229. view used by the retrieval were it to exist. For those
  230. columns to which the agent provides read-create access,
  231. the `noSuchInstance' exception tells the management
  232. station that it should supply a value for this column
  233. when the conceptual row is to be created.
  234. - the exception `noSuchObject' is returned, indicating
  235. that the agent does not implement the object-type
  236. associated with this column or that there is no
  237. conceptual row for which this column would be
  238. accessible in the MIB view used by the retrieval. As
  239. such, the management station can not issue any
  240. management protocol set operations to create an
  241. instance of this column.
  242. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'.
  243. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using
  244. `createAndWait' in order to negotiate creation of the conceptual row.
  245. NOTE WELL
  246. Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm.
  247. Interaction 2b: Negotiating the Creation of the Conceptual Row
  248. The management station issues a management protocol set operation which sets the desired instance of the status
  249. column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3.
  250. Interaction 3: Initializing non-defaulted Objects
  251. The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes:
  252. - a value is returned, indicating that the agent
  253. implements the object-type associated with this column
  254. and had sufficient information to provide a value. For
  255. those columns to which the agent provides read-create
  256. access (and for which the agent allows their values to
  257. be changed after their creation), a value return tells
  258. the management station that it may issue additional
  259. management protocol set operations, if it desires, in
  260. order to change the value associated with this column.
  261. - the exception `noSuchInstance' is returned,
  262. indicating that the agent implements the object-type
  263. associated with this column, and that this column in at
  264. least one conceptual row would be accessible in the MIB
  265. view used by the retrieval were it to exist. However,
  266. the agent does not have sufficient information to
  267. provide a value, and until a value is provided, the
  268. conceptual row may not be made available for use by the
  269. managed device. For those columns to which the agent
  270. provides read-create access, the `noSuchInstance'
  271. exception tells the management station that it must
  272. issue additional management protocol set operations, in
  273. order to provide a value associated with this column.
  274. - the exception `noSuchObject' is returned, indicating
  275. that the agent does not implement the object-type
  276. associated with this column or that there is no
  277. conceptual row for which this column would be
  278. accessible in the MIB view used by the retrieval. As
  279. such, the management station can not issue any
  280. management protocol set operations to create an
  281. instance of this column.
  282. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4.
  283. Interaction 4: Making the Conceptual Row Available
  284. Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of
  285. `inconsistentValue'.
  286. NOTE WELL
  287. A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device.
  288. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of
  289. time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absense of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row.
  290. Conceptual Row Suspension
  291. When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified).
  292. Conceptual Row Deletion
  293. For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed."
  294. SYNTAX INTEGER {
  295. -- the following two values are states:
  296. -- these values may be read or written
  297. active(1),
  298. notInService(2),
  299. -- the following value is a state:
  300. -- this value may be read, but not written
  301. notReady(3),
  302. -- the following three values are
  303. -- actions: these values may be written,
  304. -- but are never read
  305. createAndGo(4),
  306. createAndWait(5),
  307. destroy(6)
  308. }
  309. TimeStamp ::= TEXTUAL-CONVENTION
  310. STATUS current
  311. DESCRIPTION
  312. "The value of the sysUpTime object at which a specific
  313. occurrence happened. The specific occurrence must be
  314. defined in the description of any object defined using this
  315. type."
  316. SYNTAX TimeTicks
  317. TimeInterval ::= TEXTUAL-CONVENTION
  318. STATUS current
  319. DESCRIPTION
  320. "A period of time, measured in units of 0.01 seconds."
  321. SYNTAX INTEGER (0..2147483647)
  322. DateAndTime ::= TEXTUAL-CONVENTION
  323. DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
  324. STATUS current
  325. DESCRIPTION
  326. "A date-time specification.
  327. field octets contents range
  328. ----- ------ -------- -----
  329. 1 1-2 year 0..65536
  330. 2 3 month 1..12
  331. 3 4 day 1..31
  332. 4 5 hour 0..23
  333. 5 6 minutes 0..59
  334. 6 7 seconds 0..60
  335. (use 60 for leap-second)
  336. 7 8 deci-seconds 0..9
  337. 8 9 direction from UTC '+' / '-'
  338. 9 10 hours from UTC 0..11
  339. 10 11 minutes from UTC 0..59
  340. For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
  341. 1992-5-26,13:30:15.0,-4:0
  342. Note that if only local time is known, then timezone information (fields 8-10) is not present."
  343. SYNTAX OCTET STRING (SIZE (8 | 11))
  344. StorageType ::= TEXTUAL-CONVENTION
  345. STATUS current
  346. DESCRIPTION
  347. "Describes the memory realization of a conceptual row. A
  348. row which is volatile(2) is lost upon reboot. A row which
  349. is either nonVolatile(3), permanent(4) or readOnly(5), is
  350. backed up by stable storage. A row which is permanent(4)
  351. can be changed but not deleted. A row which is readOnly(5)
  352. cannot be changed nor deleted.
  353. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be modified. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5).
  354. 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."
  355. SYNTAX INTEGER {
  356. other(1), -- eh?
  357. volatile(2), -- e.g., in RAM
  358. nonVolatile(3), -- e.g., in NVRAM
  359. permanent(4), -- e.g., partially in ROM
  360. readOnly(5) -- e.g., completely in ROM
  361. }
  362. TDomain ::= TEXTUAL-CONVENTION
  363. STATUS current
  364. DESCRIPTION
  365. "Denotes a kind of transport service.
  366. Some possible values, such as snmpUDPDomain, are defined in 'Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)'."
  367. SYNTAX OBJECT IDENTIFIER
  368. TAddress ::= TEXTUAL-CONVENTION
  369. STATUS current
  370. DESCRIPTION
  371. "Denotes a transport service address.
  372. For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the IP-address in network-byte order and the last 2 containing the UDP port in network-byte order. Consult 'Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)' for further information on snmpUDPDomain."
  373. SYNTAX OCTET STRING (SIZE (1..255))
  374. END