TUNNEL-MIB 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774
  1. TUNNEL-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. MODULE-IDENTITY, OBJECT-TYPE, transmission,
  4. Integer32, IpAddress FROM SNMPv2-SMI -- [RFC2578]
  5. RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579]
  6. MODULE-COMPLIANCE,
  7. OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
  8. InetAddressType,
  9. InetAddress FROM INET-ADDRESS-MIB -- [RFC4001]
  10. IPv6FlowLabelOrAny FROM IPV6-FLOW-LABEL-MIB -- [RFC3595]
  11. ifIndex,
  12. InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
  13. IANAtunnelType FROM IANAifType-MIB; -- [IFTYPE]
  14. tunnelMIB MODULE-IDENTITY
  15. LAST-UPDATED "200505160000Z" -- May 16, 2005
  16. ORGANIZATION "IETF IP Version 6 (IPv6) Working Group"
  17. CONTACT-INFO
  18. " Dave Thaler
  19. Microsoft Corporation
  20. One Microsoft Way
  21. Redmond, WA 98052-6399
  22. EMail: dthaler@microsoft.com"
  23. DESCRIPTION
  24. "The MIB module for management of IP Tunnels,
  25. independent of the specific encapsulation scheme in
  26. use.
  27. Copyright (C) The Internet Society (2005). This
  28. version of this MIB module is part of RFC 4087; see
  29. the RFC itself for full legal notices."
  30. REVISION "200505160000Z" -- May 16, 2005
  31. DESCRIPTION
  32. "IPv4-specific objects were deprecated, including
  33. tunnelIfLocalAddress, tunnelIfRemoteAddress, the
  34. tunnelConfigTable, and the tunnelMIBBasicGroup.
  35. Added IP version-agnostic objects that should be used
  36. instead, including tunnelIfAddressType,
  37. tunnelIfLocalInetAddress, tunnelIfRemoteInetAddress,
  38. the tunnelInetConfigTable, and the
  39. tunnelIMIBInetGroup.
  40. The new tunnelIfLocalInetAddress and
  41. tunnelIfRemoteInetAddress objects are read-write,
  42. rather than read-only.
  43. Updated DESCRIPTION clauses of existing version-
  44. agnostic objects (e.g., tunnelIfTOS) that contained
  45. IPv4-specific text to cover IPv6 as well.
  46. Added tunnelIfFlowLabel for tunnels over IPv6.
  47. The encapsulation method was previously an INTEGER
  48. type, and is now an IANA-maintained textual
  49. convention.
  50. Published as RFC 4087."
  51. REVISION "199908241200Z" -- August 24, 1999
  52. DESCRIPTION
  53. "Initial version, published as RFC 2667."
  54. ::= { transmission 131 }
  55. tunnelMIBObjects OBJECT IDENTIFIER ::= { tunnelMIB 1 }
  56. tunnel OBJECT IDENTIFIER ::= { tunnelMIBObjects 1 }
  57. -- the IP Tunnel MIB-Group
  58. --
  59. -- a collection of objects providing information about
  60. -- IP Tunnels
  61. tunnelIfTable OBJECT-TYPE
  62. SYNTAX SEQUENCE OF TunnelIfEntry
  63. MAX-ACCESS not-accessible
  64. STATUS current
  65. DESCRIPTION
  66. "The (conceptual) table containing information on
  67. configured tunnels."
  68. ::= { tunnel 1 }
  69. tunnelIfEntry OBJECT-TYPE
  70. SYNTAX TunnelIfEntry
  71. MAX-ACCESS not-accessible
  72. STATUS current
  73. DESCRIPTION
  74. "An entry (conceptual row) containing the information
  75. on a particular configured tunnel."
  76. INDEX { ifIndex }
  77. ::= { tunnelIfTable 1 }
  78. TunnelIfEntry ::= SEQUENCE {
  79. tunnelIfLocalAddress IpAddress, -- deprecated
  80. tunnelIfRemoteAddress IpAddress, -- deprecated
  81. tunnelIfEncapsMethod IANAtunnelType,
  82. tunnelIfHopLimit Integer32,
  83. tunnelIfSecurity INTEGER,
  84. tunnelIfTOS Integer32,
  85. tunnelIfFlowLabel IPv6FlowLabelOrAny,
  86. tunnelIfAddressType InetAddressType,
  87. tunnelIfLocalInetAddress InetAddress,
  88. tunnelIfRemoteInetAddress InetAddress,
  89. tunnelIfEncapsLimit Integer32
  90. }
  91. tunnelIfLocalAddress OBJECT-TYPE
  92. SYNTAX IpAddress
  93. MAX-ACCESS read-only
  94. STATUS deprecated
  95. DESCRIPTION
  96. "The address of the local endpoint of the tunnel
  97. (i.e., the source address used in the outer IP
  98. header), or 0.0.0.0 if unknown or if the tunnel is
  99. over IPv6.
  100. Since this object does not support IPv6, it is
  101. deprecated in favor of tunnelIfLocalInetAddress."
  102. ::= { tunnelIfEntry 1 }
  103. tunnelIfRemoteAddress OBJECT-TYPE
  104. SYNTAX IpAddress
  105. MAX-ACCESS read-only
  106. STATUS deprecated
  107. DESCRIPTION
  108. "The address of the remote endpoint of the tunnel
  109. (i.e., the destination address used in the outer IP
  110. header), or 0.0.0.0 if unknown, or an IPv6 address, or
  111. the tunnel is not a point-to-point link (e.g., if it
  112. is a 6to4 tunnel).
  113. Since this object does not support IPv6, it is
  114. deprecated in favor of tunnelIfRemoteInetAddress."
  115. ::= { tunnelIfEntry 2 }
  116. tunnelIfEncapsMethod OBJECT-TYPE
  117. SYNTAX IANAtunnelType
  118. MAX-ACCESS read-only
  119. STATUS current
  120. DESCRIPTION
  121. "The encapsulation method used by the tunnel."
  122. ::= { tunnelIfEntry 3 }
  123. tunnelIfHopLimit OBJECT-TYPE
  124. SYNTAX Integer32 (0 | 1..255)
  125. MAX-ACCESS read-write
  126. STATUS current
  127. DESCRIPTION
  128. "The IPv4 TTL or IPv6 Hop Limit to use in the outer IP
  129. header. A value of 0 indicates that the value is
  130. copied from the payload's header."
  131. ::= { tunnelIfEntry 4 }
  132. tunnelIfSecurity OBJECT-TYPE
  133. SYNTAX INTEGER {
  134. none(1), -- no security
  135. ipsec(2), -- IPsec security
  136. other(3)
  137. }
  138. MAX-ACCESS read-only
  139. STATUS current
  140. DESCRIPTION
  141. "The method used by the tunnel to secure the outer IP
  142. header. The value ipsec indicates that IPsec is used
  143. between the tunnel endpoints for authentication or
  144. encryption or both. More specific security-related
  145. information may be available in a MIB module for the
  146. security protocol in use."
  147. ::= { tunnelIfEntry 5 }
  148. tunnelIfTOS OBJECT-TYPE
  149. SYNTAX Integer32 (-2..63)
  150. MAX-ACCESS read-write
  151. STATUS current
  152. DESCRIPTION
  153. "The method used to set the high 6 bits (the
  154. differentiated services codepoint) of the IPv4 TOS or
  155. IPv6 Traffic Class in the outer IP header. A value of
  156. -1 indicates that the bits are copied from the
  157. payload's header. A value of -2 indicates that a
  158. traffic conditioner is invoked and more information
  159. may be available in a traffic conditioner MIB module.
  160. A value between 0 and 63 inclusive indicates that the
  161. bit field is set to the indicated value.
  162. Note: instead of the name tunnelIfTOS, a better name
  163. would have been tunnelIfDSCPMethod, but the existing
  164. name appeared in RFC 2667 and existing objects cannot
  165. be renamed."
  166. ::= { tunnelIfEntry 6 }
  167. tunnelIfFlowLabel OBJECT-TYPE
  168. SYNTAX IPv6FlowLabelOrAny
  169. MAX-ACCESS read-write
  170. STATUS current
  171. DESCRIPTION
  172. "The method used to set the IPv6 Flow Label value.
  173. This object need not be present in rows where
  174. tunnelIfAddressType indicates the tunnel is not over
  175. IPv6. A value of -1 indicates that a traffic
  176. conditioner is invoked and more information may be
  177. available in a traffic conditioner MIB. Any other
  178. value indicates that the Flow Label field is set to
  179. the indicated value."
  180. ::= { tunnelIfEntry 7 }
  181. tunnelIfAddressType OBJECT-TYPE
  182. SYNTAX InetAddressType
  183. MAX-ACCESS read-write
  184. STATUS current
  185. DESCRIPTION
  186. "The type of address in the corresponding
  187. tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress
  188. objects."
  189. ::= { tunnelIfEntry 8 }
  190. tunnelIfLocalInetAddress OBJECT-TYPE
  191. SYNTAX InetAddress
  192. MAX-ACCESS read-write
  193. STATUS current
  194. DESCRIPTION
  195. "The address of the local endpoint of the tunnel
  196. (i.e., the source address used in the outer IP
  197. header). If the address is unknown, the value is
  198. 0.0.0.0 for IPv4 or :: for IPv6. The type of this
  199. object is given by tunnelIfAddressType."
  200. ::= { tunnelIfEntry 9 }
  201. tunnelIfRemoteInetAddress OBJECT-TYPE
  202. SYNTAX InetAddress
  203. MAX-ACCESS read-write
  204. STATUS current
  205. DESCRIPTION
  206. "The address of the remote endpoint of the tunnel
  207. (i.e., the destination address used in the outer IP
  208. header). If the address is unknown or the tunnel is
  209. not a point-to-point link (e.g., if it is a 6to4
  210. tunnel), the value is 0.0.0.0 for tunnels over IPv4 or
  211. :: for tunnels over IPv6. The type of this object is
  212. given by tunnelIfAddressType."
  213. ::= { tunnelIfEntry 10 }
  214. tunnelIfEncapsLimit OBJECT-TYPE
  215. SYNTAX Integer32 (-1 | 0..255)
  216. MAX-ACCESS read-write
  217. STATUS current
  218. DESCRIPTION
  219. "The maximum number of additional encapsulations
  220. permitted for packets undergoing encapsulation at this
  221. node. A value of -1 indicates that no limit is
  222. present (except as a result of the packet size)."
  223. REFERENCE "RFC 2473, section 4.1.1"
  224. ::= { tunnelIfEntry 11 }
  225. tunnelConfigTable OBJECT-TYPE
  226. SYNTAX SEQUENCE OF TunnelConfigEntry
  227. MAX-ACCESS not-accessible
  228. STATUS deprecated
  229. DESCRIPTION
  230. "The (conceptual) table containing information on
  231. configured tunnels. This table can be used to map a
  232. set of tunnel endpoints to the associated ifIndex
  233. value. It can also be used for row creation. Note
  234. that every row in the tunnelIfTable with a fixed IPv4
  235. destination address should have a corresponding row in
  236. the tunnelConfigTable, regardless of whether it was
  237. created via SNMP.
  238. Since this table does not support IPv6, it is
  239. deprecated in favor of tunnelInetConfigTable."
  240. ::= { tunnel 2 }
  241. tunnelConfigEntry OBJECT-TYPE
  242. SYNTAX TunnelConfigEntry
  243. MAX-ACCESS not-accessible
  244. STATUS deprecated
  245. DESCRIPTION
  246. "An entry (conceptual row) containing the information
  247. on a particular configured tunnel.
  248. Since this entry does not support IPv6, it is
  249. deprecated in favor of tunnelInetConfigEntry."
  250. INDEX { tunnelConfigLocalAddress,
  251. tunnelConfigRemoteAddress,
  252. tunnelConfigEncapsMethod,
  253. tunnelConfigID }
  254. ::= { tunnelConfigTable 1 }
  255. TunnelConfigEntry ::= SEQUENCE {
  256. tunnelConfigLocalAddress IpAddress,
  257. tunnelConfigRemoteAddress IpAddress,
  258. tunnelConfigEncapsMethod IANAtunnelType,
  259. tunnelConfigID Integer32,
  260. tunnelConfigIfIndex InterfaceIndexOrZero,
  261. tunnelConfigStatus RowStatus
  262. }
  263. tunnelConfigLocalAddress OBJECT-TYPE
  264. SYNTAX IpAddress
  265. MAX-ACCESS not-accessible
  266. STATUS deprecated
  267. DESCRIPTION
  268. "The address of the local endpoint of the tunnel, or
  269. 0.0.0.0 if the device is free to choose any of its
  270. addresses at tunnel establishment time.
  271. Since this object does not support IPv6, it is
  272. deprecated in favor of tunnelInetConfigLocalAddress."
  273. ::= { tunnelConfigEntry 1 }
  274. tunnelConfigRemoteAddress OBJECT-TYPE
  275. SYNTAX IpAddress
  276. MAX-ACCESS not-accessible
  277. STATUS deprecated
  278. DESCRIPTION
  279. "The address of the remote endpoint of the tunnel.
  280. Since this object does not support IPv6, it is
  281. deprecated in favor of tunnelInetConfigRemoteAddress."
  282. ::= { tunnelConfigEntry 2 }
  283. tunnelConfigEncapsMethod OBJECT-TYPE
  284. SYNTAX IANAtunnelType
  285. MAX-ACCESS not-accessible
  286. STATUS deprecated
  287. DESCRIPTION
  288. "The encapsulation method used by the tunnel.
  289. Since this object does not support IPv6, it is
  290. deprecated in favor of tunnelInetConfigEncapsMethod."
  291. ::= { tunnelConfigEntry 3 }
  292. tunnelConfigID OBJECT-TYPE
  293. SYNTAX Integer32 (1..2147483647)
  294. MAX-ACCESS not-accessible
  295. STATUS deprecated
  296. DESCRIPTION
  297. "An identifier used to distinguish between multiple
  298. tunnels of the same encapsulation method, with the
  299. same endpoints. If the encapsulation protocol only
  300. allows one tunnel per set of endpoint addresses (such
  301. as for GRE or IP-in-IP), the value of this object is
  302. 1. For encapsulation methods (such as L2F) which
  303. allow multiple parallel tunnels, the manager is
  304. responsible for choosing any ID which does not
  305. conflict with an existing row, such as choosing a
  306. random number.
  307. Since this object does not support IPv6, it is
  308. deprecated in favor of tunnelInetConfigID."
  309. ::= { tunnelConfigEntry 4 }
  310. tunnelConfigIfIndex OBJECT-TYPE
  311. SYNTAX InterfaceIndexOrZero
  312. MAX-ACCESS read-only
  313. STATUS deprecated
  314. DESCRIPTION
  315. "If the value of tunnelConfigStatus for this row is
  316. active, then this object contains the value of ifIndex
  317. corresponding to the tunnel interface. A value of 0
  318. is not legal in the active state, and means that the
  319. interface index has not yet been assigned.
  320. Since this object does not support IPv6, it is
  321. deprecated in favor of tunnelInetConfigIfIndex."
  322. ::= { tunnelConfigEntry 5 }
  323. tunnelConfigStatus OBJECT-TYPE
  324. SYNTAX RowStatus
  325. MAX-ACCESS read-create
  326. STATUS deprecated
  327. DESCRIPTION
  328. "The status of this row, by which new entries may be
  329. created, or old entries deleted from this table. The
  330. agent need not support setting this object to
  331. createAndWait or notInService since there are no other
  332. writable objects in this table, and writable objects
  333. in rows of corresponding tables such as the
  334. tunnelIfTable may be modified while this row is
  335. active.
  336. To create a row in this table for an encapsulation
  337. method which does not support multiple parallel
  338. tunnels with the same endpoints, the management
  339. station should simply use a tunnelConfigID of 1, and
  340. set tunnelConfigStatus to createAndGo. For
  341. encapsulation methods such as L2F which allow multiple
  342. parallel tunnels, the management station may select a
  343. pseudo-random number to use as the tunnelConfigID and
  344. set tunnelConfigStatus to createAndGo. In the event
  345. that this ID is already in use and an
  346. inconsistentValue is returned in response to the set
  347. operation, the management station should simply select
  348. a new pseudo-random number and retry the operation.
  349. Creating a row in this table will cause an interface
  350. index to be assigned by the agent in an
  351. implementation-dependent manner, and corresponding
  352. rows will be instantiated in the ifTable and the
  353. tunnelIfTable. The status of this row will become
  354. active as soon as the agent assigns the interface
  355. index, regardless of whether the interface is
  356. operationally up.
  357. Deleting a row in this table will likewise delete the
  358. corresponding row in the ifTable and in the
  359. tunnelIfTable.
  360. Since this object does not support IPv6, it is
  361. deprecated in favor of tunnelInetConfigStatus."
  362. ::= { tunnelConfigEntry 6 }
  363. tunnelInetConfigTable OBJECT-TYPE
  364. SYNTAX SEQUENCE OF TunnelInetConfigEntry
  365. MAX-ACCESS not-accessible
  366. STATUS current
  367. DESCRIPTION
  368. "The (conceptual) table containing information on
  369. configured tunnels. This table can be used to map a
  370. set of tunnel endpoints to the associated ifIndex
  371. value. It can also be used for row creation. Note
  372. that every row in the tunnelIfTable with a fixed
  373. destination address should have a corresponding row in
  374. the tunnelInetConfigTable, regardless of whether it
  375. was created via SNMP."
  376. ::= { tunnel 3 }
  377. tunnelInetConfigEntry OBJECT-TYPE
  378. SYNTAX TunnelInetConfigEntry
  379. MAX-ACCESS not-accessible
  380. STATUS current
  381. DESCRIPTION
  382. "An entry (conceptual row) containing the information
  383. on a particular configured tunnel. Note that there is
  384. a 128 subid maximum for object OIDs. Implementers
  385. need to be aware that if the total number of octets in
  386. tunnelInetConfigLocalAddress and
  387. tunnelInetConfigRemoteAddress exceeds 110 then OIDs of
  388. column instances in this table will have more than 128
  389. sub-identifiers and cannot be accessed using SNMPv1,
  390. SNMPv2c, or SNMPv3. In practice this is not expected
  391. to be a problem since IPv4 and IPv6 addresses will not
  392. cause the limit to be reached, but if other types are
  393. supported by an agent, care must be taken to ensure
  394. that the sum of the lengths do not cause the limit to
  395. be exceeded."
  396. INDEX { tunnelInetConfigAddressType,
  397. tunnelInetConfigLocalAddress,
  398. tunnelInetConfigRemoteAddress,
  399. tunnelInetConfigEncapsMethod,
  400. tunnelInetConfigID }
  401. ::= { tunnelInetConfigTable 1 }
  402. TunnelInetConfigEntry ::= SEQUENCE {
  403. tunnelInetConfigAddressType InetAddressType,
  404. tunnelInetConfigLocalAddress InetAddress,
  405. tunnelInetConfigRemoteAddress InetAddress,
  406. tunnelInetConfigEncapsMethod IANAtunnelType,
  407. tunnelInetConfigID Integer32,
  408. tunnelInetConfigIfIndex InterfaceIndexOrZero,
  409. tunnelInetConfigStatus RowStatus,
  410. tunnelInetConfigStorageType StorageType
  411. }
  412. tunnelInetConfigAddressType OBJECT-TYPE
  413. SYNTAX InetAddressType
  414. MAX-ACCESS not-accessible
  415. STATUS current
  416. DESCRIPTION
  417. "The address type over which the tunnel encapsulates
  418. packets."
  419. ::= { tunnelInetConfigEntry 1 }
  420. tunnelInetConfigLocalAddress OBJECT-TYPE
  421. SYNTAX InetAddress
  422. MAX-ACCESS not-accessible
  423. STATUS current
  424. DESCRIPTION
  425. "The address of the local endpoint of the tunnel, or
  426. 0.0.0.0 (for IPv4) or :: (for IPv6) if the device is
  427. free to choose any of its addresses at tunnel
  428. establishment time."
  429. ::= { tunnelInetConfigEntry 2 }
  430. tunnelInetConfigRemoteAddress OBJECT-TYPE
  431. SYNTAX InetAddress
  432. MAX-ACCESS not-accessible
  433. STATUS current
  434. DESCRIPTION
  435. "The address of the remote endpoint of the tunnel."
  436. ::= { tunnelInetConfigEntry 3 }
  437. tunnelInetConfigEncapsMethod OBJECT-TYPE
  438. SYNTAX IANAtunnelType
  439. MAX-ACCESS not-accessible
  440. STATUS current
  441. DESCRIPTION
  442. "The encapsulation method used by the tunnel."
  443. ::= { tunnelInetConfigEntry 4 }
  444. tunnelInetConfigID OBJECT-TYPE
  445. SYNTAX Integer32 (1..2147483647)
  446. MAX-ACCESS not-accessible
  447. STATUS current
  448. DESCRIPTION
  449. "An identifier used to distinguish between multiple
  450. tunnels of the same encapsulation method, with the
  451. same endpoints. If the encapsulation protocol only
  452. allows one tunnel per set of endpoint addresses (such
  453. as for GRE or IP-in-IP), the value of this object is
  454. 1. For encapsulation methods (such as L2F) which
  455. allow multiple parallel tunnels, the manager is
  456. responsible for choosing any ID which does not
  457. conflict with an existing row, such as choosing a
  458. random number."
  459. ::= { tunnelInetConfigEntry 5 }
  460. tunnelInetConfigIfIndex OBJECT-TYPE
  461. SYNTAX InterfaceIndexOrZero
  462. MAX-ACCESS read-only
  463. STATUS current
  464. DESCRIPTION
  465. "If the value of tunnelInetConfigStatus for this row
  466. is active, then this object contains the value of
  467. ifIndex corresponding to the tunnel interface. A
  468. value of 0 is not legal in the active state, and means
  469. that the interface index has not yet been assigned."
  470. ::= { tunnelInetConfigEntry 6 }
  471. tunnelInetConfigStatus OBJECT-TYPE
  472. SYNTAX RowStatus
  473. MAX-ACCESS read-create
  474. STATUS current
  475. DESCRIPTION
  476. "The status of this row, by which new entries may be
  477. created, or old entries deleted from this table. The
  478. agent need not support setting this object to
  479. createAndWait or notInService since there are no other
  480. writable objects in this table, and writable objects
  481. in rows of corresponding tables such as the
  482. tunnelIfTable may be modified while this row is
  483. active.
  484. To create a row in this table for an encapsulation
  485. method which does not support multiple parallel
  486. tunnels with the same endpoints, the management
  487. station should simply use a tunnelInetConfigID of 1,
  488. and set tunnelInetConfigStatus to createAndGo. For
  489. encapsulation methods such as L2F which allow multiple
  490. parallel tunnels, the management station may select a
  491. pseudo-random number to use as the tunnelInetConfigID
  492. and set tunnelInetConfigStatus to createAndGo. In the
  493. event that this ID is already in use and an
  494. inconsistentValue is returned in response to the set
  495. operation, the management station should simply select
  496. a new pseudo-random number and retry the operation.
  497. Creating a row in this table will cause an interface
  498. index to be assigned by the agent in an
  499. implementation-dependent manner, and corresponding
  500. rows will be instantiated in the ifTable and the
  501. tunnelIfTable. The status of this row will become
  502. active as soon as the agent assigns the interface
  503. index, regardless of whether the interface is
  504. operationally up.
  505. Deleting a row in this table will likewise delete the
  506. corresponding row in the ifTable and in the
  507. tunnelIfTable."
  508. ::= { tunnelInetConfigEntry 7 }
  509. tunnelInetConfigStorageType OBJECT-TYPE
  510. SYNTAX StorageType
  511. MAX-ACCESS read-create
  512. STATUS current
  513. DESCRIPTION
  514. "The storage type of this row. If the row is
  515. permanent(4), no objects in the row need be writable."
  516. ::= { tunnelInetConfigEntry 8 }
  517. -- conformance information
  518. tunnelMIBConformance
  519. OBJECT IDENTIFIER ::= { tunnelMIB 2 }
  520. tunnelMIBCompliances
  521. OBJECT IDENTIFIER ::= { tunnelMIBConformance 1 }
  522. tunnelMIBGroups OBJECT IDENTIFIER ::= { tunnelMIBConformance 2 }
  523. -- compliance statements
  524. tunnelMIBCompliance MODULE-COMPLIANCE
  525. STATUS deprecated
  526. DESCRIPTION
  527. "The (deprecated) IPv4-only compliance statement for
  528. the IP Tunnel MIB.
  529. This is deprecated in favor of
  530. tunnelMIBInetFullCompliance and
  531. tunnelMIBInetReadOnlyCompliance."
  532. MODULE -- this module
  533. MANDATORY-GROUPS { tunnelMIBBasicGroup }
  534. OBJECT tunnelIfHopLimit
  535. MIN-ACCESS read-only
  536. DESCRIPTION
  537. "Write access is not required."
  538. OBJECT tunnelIfTOS
  539. MIN-ACCESS read-only
  540. DESCRIPTION
  541. "Write access is not required."
  542. OBJECT tunnelConfigStatus
  543. MIN-ACCESS read-only
  544. DESCRIPTION
  545. "Write access is not required."
  546. ::= { tunnelMIBCompliances 1 }
  547. tunnelMIBInetFullCompliance MODULE-COMPLIANCE
  548. STATUS current
  549. DESCRIPTION
  550. "The full compliance statement for the IP Tunnel MIB."
  551. MODULE -- this module
  552. MANDATORY-GROUPS { tunnelMIBInetGroup }
  553. OBJECT tunnelIfAddressType
  554. SYNTAX InetAddressType { ipv4(1), ipv6(2),
  555. ipv4z(3), ipv6z(4) }
  556. DESCRIPTION
  557. "An implementation is only required to support IPv4
  558. and/or IPv6 addresses. An implementation only needs to
  559. support the addresses it actually supports on the
  560. device."
  561. ::= { tunnelMIBCompliances 2 }
  562. tunnelMIBInetReadOnlyCompliance MODULE-COMPLIANCE
  563. STATUS current
  564. DESCRIPTION
  565. "The read-only compliance statement for the IP Tunnel
  566. MIB."
  567. MODULE -- this module
  568. MANDATORY-GROUPS { tunnelMIBInetGroup }
  569. OBJECT tunnelIfHopLimit
  570. MIN-ACCESS read-only
  571. DESCRIPTION
  572. "Write access is not required."
  573. OBJECT tunnelIfTOS
  574. MIN-ACCESS read-only
  575. DESCRIPTION
  576. "Write access is not required."
  577. OBJECT tunnelIfFlowLabel
  578. MIN-ACCESS read-only
  579. DESCRIPTION
  580. "Write access is not required."
  581. OBJECT tunnelIfAddressType
  582. SYNTAX InetAddressType { ipv4(1), ipv6(2),
  583. ipv4z(3), ipv6z(4) }
  584. MIN-ACCESS read-only
  585. DESCRIPTION
  586. "Write access is not required.
  587. An implementation is only required to support IPv4
  588. and/or IPv6 addresses. An implementation only needs to
  589. support the addresses it actually supports on the
  590. device."
  591. OBJECT tunnelIfLocalInetAddress
  592. MIN-ACCESS read-only
  593. DESCRIPTION
  594. "Write access is not required."
  595. OBJECT tunnelIfRemoteInetAddress
  596. MIN-ACCESS read-only
  597. DESCRIPTION
  598. "Write access is not required."
  599. OBJECT tunnelIfEncapsLimit
  600. MIN-ACCESS read-only
  601. DESCRIPTION
  602. "Write access is not required."
  603. OBJECT tunnelInetConfigStatus
  604. MIN-ACCESS read-only
  605. DESCRIPTION
  606. "Write access is not required, and active is the only
  607. status that needs to be supported."
  608. OBJECT tunnelInetConfigStorageType
  609. MIN-ACCESS read-only
  610. DESCRIPTION
  611. "Write access is not required."
  612. ::= { tunnelMIBCompliances 3 }
  613. -- units of conformance
  614. tunnelMIBBasicGroup OBJECT-GROUP
  615. OBJECTS { tunnelIfLocalAddress, tunnelIfRemoteAddress,
  616. tunnelIfEncapsMethod, tunnelIfHopLimit, tunnelIfTOS,
  617. tunnelIfSecurity, tunnelConfigIfIndex, tunnelConfigStatus }
  618. STATUS deprecated
  619. DESCRIPTION
  620. "A collection of objects to support basic management
  621. of IPv4 Tunnels. Since this group cannot support
  622. IPv6, it is deprecated in favor of
  623. tunnelMIBInetGroup."
  624. ::= { tunnelMIBGroups 1 }
  625. tunnelMIBInetGroup OBJECT-GROUP
  626. OBJECTS { tunnelIfAddressType, tunnelIfLocalInetAddress,
  627. tunnelIfRemoteInetAddress, tunnelIfEncapsMethod,
  628. tunnelIfEncapsLimit,
  629. tunnelIfHopLimit, tunnelIfTOS, tunnelIfFlowLabel,
  630. tunnelIfSecurity, tunnelInetConfigIfIndex,
  631. tunnelInetConfigStatus, tunnelInetConfigStorageType }
  632. STATUS current
  633. DESCRIPTION
  634. "A collection of objects to support basic management
  635. of IPv4 and IPv6 Tunnels."
  636. ::= { tunnelMIBGroups 2 }
  637. END