SMUX-MIB.txt 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. SMUX-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. enterprises
  4. FROM RFC1155-SMI
  5. DisplayString
  6. FROM SNMPv2-TC
  7. OBJECT-TYPE
  8. FROM RFC-1212;
  9. unix OBJECT IDENTIFIER ::= { enterprises 4 }
  10. smux OBJECT IDENTIFIER ::= { unix 4 }
  11. smuxPeerTable OBJECT-TYPE
  12. SYNTAX SEQUENCE OF SmuxPeerEntry
  13. ACCESS not-accessible
  14. STATUS mandatory
  15. DESCRIPTION
  16. "The SMUX peer table."
  17. ::= { smux 1 }
  18. smuxPeerEntry OBJECT-TYPE
  19. SYNTAX SmuxPeerEntry
  20. ACCESS not-accessible
  21. STATUS mandatory
  22. DESCRIPTION
  23. "An entry in the SMUX peer table."
  24. INDEX { smuxPindex }
  25. ::= { smuxPeerTable 1}
  26. SmuxPeerEntry ::=
  27. SEQUENCE {
  28. smuxPindex
  29. INTEGER,
  30. smuxPidentity
  31. OBJECT IDENTIFIER,
  32. smuxPdescription
  33. DisplayString,
  34. smuxPstatus
  35. INTEGER
  36. }
  37. smuxPindex OBJECT-TYPE
  38. SYNTAX INTEGER
  39. ACCESS read-only
  40. STATUS mandatory
  41. DESCRIPTION
  42. "An index which uniquely identifies a SMUX peer."
  43. ::= { smuxPeerEntry 1 }
  44. smuxPidentity OBJECT-TYPE
  45. SYNTAX OBJECT IDENTIFIER
  46. ACCESS read-only
  47. STATUS mandatory
  48. DESCRIPTION
  49. "The authoritative designation for a SMUX peer."
  50. ::= { smuxPeerEntry 2 }
  51. smuxPdescription OBJECT-TYPE
  52. SYNTAX DisplayString (SIZE (0..255))
  53. ACCESS read-only
  54. STATUS mandatory
  55. DESCRIPTION
  56. "A human-readable description of a SMUX peer."
  57. ::= { smuxPeerEntry 3 }
  58. smuxPstatus OBJECT-TYPE
  59. SYNTAX INTEGER { valid(1), invalid(2), connecting(3) }
  60. ACCESS read-write
  61. STATUS mandatory
  62. DESCRIPTION
  63. "The type of SMUX peer.
  64. Setting this object to the value invalid(2) has
  65. the effect of invaliding the corresponding entry
  66. in the smuxPeerTable. It is an implementation-
  67. specific matter as to whether the agent removes an
  68. invalidated entry from the table. Accordingly,
  69. management stations must be prepared to receive
  70. tabular information from agents that correspond to
  71. entries not currently in use. Proper
  72. interpretation of such entries requires
  73. examination of the relative smuxPstatus object."
  74. ::= { smuxPeerEntry 4 }
  75. smuxTreeTable OBJECT-TYPE
  76. SYNTAX SEQUENCE OF SmuxTreeEntry
  77. ACCESS not-accessible
  78. STATUS mandatory
  79. DESCRIPTION
  80. "The SMUX tree table."
  81. ::= { smux 2 }
  82. smuxTreeEntry OBJECT-TYPE
  83. SYNTAX SmuxTreeEntry
  84. ACCESS not-accessible
  85. STATUS mandatory
  86. DESCRIPTION
  87. "An entry in the SMUX tree table."
  88. INDEX { smuxTsubtree, smuxTpriority }
  89. ::= { smuxTreeTable 1}
  90. SmuxTreeEntry ::=
  91. SEQUENCE {
  92. smuxTsubtree
  93. OBJECT IDENTIFIER,
  94. smuxTpriority
  95. INTEGER,
  96. smuxTindex
  97. INTEGER,
  98. smuxTstatus
  99. INTEGER
  100. }
  101. smuxTsubtree OBJECT-TYPE
  102. SYNTAX OBJECT IDENTIFIER
  103. ACCESS read-only
  104. STATUS mandatory
  105. DESCRIPTION
  106. "The MIB subtree being exported by a SMUX peer."
  107. ::= { smuxTreeEntry 1 }
  108. smuxTpriority OBJECT-TYPE
  109. SYNTAX INTEGER (0..'07fffffff'h)
  110. ACCESS read-only
  111. STATUS mandatory
  112. DESCRIPTION
  113. "The SMUX peer's priority when exporting the MIB
  114. subtree."
  115. ::= { smuxTreeEntry 2 }
  116. smuxTindex OBJECT-TYPE
  117. SYNTAX INTEGER
  118. ACCESS read-only
  119. STATUS mandatory
  120. DESCRIPTION
  121. "The SMUX peer's identity."
  122. ::= { smuxTreeEntry 3 }
  123. smuxTstatus OBJECT-TYPE
  124. SYNTAX INTEGER { valid(1), invalid(2) }
  125. ACCESS read-write
  126. STATUS mandatory
  127. DESCRIPTION
  128. "The type of SMUX tree.
  129. Setting this object to the value invalid(2) has
  130. the effect of invaliding the corresponding entry
  131. in the smuxTreeTable. It is an implementation-
  132. specific matter as to whether the agent removes an
  133. invalidated entry from the table. Accordingly,
  134. management stations must be prepared to receive
  135. tabular information from agents that correspond to
  136. entries not currently in use. Proper
  137. interpretation of such entries requires
  138. examination of the relative smuxTstatus object."
  139. ::= { smuxTreeEntry 4 }
  140. END