smilint output for ./IANA-MAU-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| warning | 4 |
| Message Types |
|---|
| Type | Count |
|---|
| type-unref (warning) | 4 |
Messages:
IANA-MAU-MIB
1: -- extracted from rfc4836.txt
2: -- at Fri Apr 27 06:08:24 2007
70:
71: IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
71: warning -
warning: current type `IANAifMauTypeListBits' is not referenced in this module
72: STATUS current
73: DESCRIPTION
74: "This data type is used as the syntax of the ifMauTypeListBits
75: object in the (updated) definition of MAU-MIB's ifMauTable.
76: The most recent version of this textual convention is available
77: in the online version of this MIB module on the IANA web site.
78:
79: Requests for new values should be made to IANA via email
80: (iana@iana.org).
81:
82: Note that changes in this textual convention SHALL be
83: synchronized with relevant changes in the dot3MauType
84: OBJECT-IDENTITIES."
85: REFERENCE
86: "[IEEE802.3], Section 30.5.1.1.2"
87: SYNTAX BITS {
88: bOther(0), -- other or unknown
89: bAUI(1), -- AUI
90: b10base5(2), -- 10BASE-5
91: bFoirl(3), -- FOIRL
92:
93: b10base2(4), -- 10BASE-2
94: b10baseT(5), -- 10BASE-T duplex mode unknown
95: b10baseFP(6), -- 10BASE-FP
96: b10baseFB(7), -- 10BASE-FB
97: b10baseFL(8), -- 10BASE-FL duplex mode unknown
98: b10broad36(9), -- 10BROAD36
99: b10baseTHD(10), -- 10BASE-T half duplex mode
100: b10baseTFD(11), -- 10BASE-T full duplex mode
101: b10baseFLHD(12), -- 10BASE-FL half duplex mode
102: b10baseFLFD(13), -- 10BASE-FL full duplex mode
103: b100baseT4(14), -- 100BASE-T4
104: b100baseTXHD(15), -- 100BASE-TX half duplex mode
105: b100baseTXFD(16), -- 100BASE-TX full duplex mode
106: b100baseFXHD(17), -- 100BASE-FX half duplex mode
107: b100baseFXFD(18), -- 100BASE-FX full duplex mode
108: b100baseT2HD(19), -- 100BASE-T2 half duplex mode
109: b100baseT2FD(20), -- 100BASE-T2 full duplex mode
110:
111: b1000baseXHD(21), -- 1000BASE-X half duplex mode
112: b1000baseXFD(22), -- 1000BASE-X full duplex mode
113: b1000baseLXHD(23), -- 1000BASE-LX half duplex mode
114: b1000baseLXFD(24), -- 1000BASE-LX full duplex mode
115: b1000baseSXHD(25), -- 1000BASE-SX half duplex mode
116: b1000baseSXFD(26), -- 1000BASE-SX full duplex mode
117: b1000baseCXHD(27), -- 1000BASE-CX half duplex mode
118: b1000baseCXFD(28), -- 1000BASE-CX full duplex mode
119: b1000baseTHD(29), -- 1000BASE-T half duplex mode
120: b1000baseTFD(30), -- 1000BASE-T full duplex mode
121:
122: b10GbaseX(31), -- 10GBASE-X
123: b10GbaseLX4(32), -- 10GBASE-LX4
124: b10GbaseR(33), -- 10GBASE-R
125: b10GbaseER(34), -- 10GBASE-ER
126: b10GbaseLR(35), -- 10GBASE-LR
127: b10GbaseSR(36), -- 10GBASE-SR
128: b10GbaseW(37), -- 10GBASE-W
129: b10GbaseEW(38), -- 10GBASE-EW
130: b10GbaseLW(39), -- 10GBASE-LW
131: b10GbaseSW(40), -- 10GBASE-SW
132: -- new since RFC 3636
133: b10GbaseCX4(41), -- 10GBASE-CX4
134: b2BaseTL(42), -- 2BASE-TL
135: b10PassTS(43), -- 10PASS-TS
136: b100BaseBX10D(44), -- 100BASE-BX10D
137: b100BaseBX10U(45), -- 100BASE-BX10U
138: b100BaseLX10(46), -- 100BASE-LX10
139: b1000BaseBX10D(47), -- 1000BASE-BX10D
140: b1000BaseBX10U(48), -- 1000BASE-BX10U
141: b1000BaseLX10(49), -- 1000BASE-LX10
142: b1000BasePX10D(50), -- 1000BASE-PX10D
143: b1000BasePX10U(51), -- 1000BASE-PX10U
144: b1000BasePX20D(52), -- 1000BASE-PX20D
145: b1000BasePX20U(53) -- 1000BASE-PX20U
146: }
147:
148: IANAifMauMediaAvailable ::= TEXTUAL-CONVENTION
148: warning -
warning: current type `IANAifMauMediaAvailable' is not referenced in this module
149: STATUS current
150: DESCRIPTION
151: "This data type is used as the syntax of the
152: ifMauMediaAvailable and rpMauMediaAvailable objects in the
153: (updated) definition of MAU-MIB's ifMauTable and rpMauTable
154: respectively.
155:
156: Possible values are:
157: other(1) - undefined (not listed below)
158: unknown(2) - MAU's true state is unknown; e.g.,
159: during initialization
160: available(3) - link, light, or loopback is normal
161: notAvailable(4) - link loss, low light, or no loopback
162: remoteFault(5) - a fault has been detected at the
163: remote end of the link. This value
164: applies to 10BASE-FB, 100BASE-T4 Far
165: End Fault Indication and non-specified
166: remote faults from a system running
167: auto-negotiation
168: invalidSignal(6) - invalid signal has been received from
169: the other end of the link, 10BASE-FB
170: only
171: remoteJabber(7) - remote fault, due to jabber
172: remoteLinkLoss(8) - remote fault, due to link loss
173: remoteTest(9) - remote fault, due to test
174: offline(10) - offline, Clause 37 Auto-Negotiation
175: only
176: autoNegError(11) - Auto-Negotiation Error, Clause 37
177: Auto-Negotiation only
178: pmdLinkFault(12) - PMA/PMD receive link fault. In case
179: of PAF (2BASE-TL / 10PASS-TS PHYs),
180: all PMEs in the aggregation group have
181: detected a link fault
182: wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only
183: wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only
184: pcsLinkFault(15) - PCS receive link fault
185: excessiveBER(16) - PCS Bit Error Ratio monitor
186: reporting excessive error ratio
187: dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only
188: pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only
189: availableReduced(19) - link normal, reduced bandwidth,
190: 2BASE-TL / 10PASS-TS only
191: ready(20) - at least one PME in the aggregation
192: group is detecting handshake tones,
193: 2BASE-TL / 10PASS-TS only
194:
195: If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T,
196: 10BASE-F), then this is equivalent to the link test fail
197: state/low light function. For an AUI, 10BASE2, 10BASE5, or
198: 10BROAD36 MAU, this indicates whether loopback is detected on
199: the DI circuit. The value of this attribute persists between
200: packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and
201: 10BASEFP.
202:
203: At power-up or following a reset, the Media Available state
204: will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and
205: 10BASE-FP MAUs. For these MAUs loopback will be tested on each
206: transmission during which no collision is detected.
207: If DI is receiving input when DO returns to IDL after a
208: transmission and there has been no collision during the
209: transmission, then loopback will be detected. The Media
210: Available state will only change during noncollided
211: transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and
212: 10BASE-FP MAUs.
213:
214: For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX,
215: 100BASE-LX10, and 100BASE-BX10 PHYs the enumerations match the
216: states within the link integrity state diagram.
217: Any MAU that implements management of [IEEE802.3] Clause
218: 28 Auto-Negotiation, will map remote fault indication to
219: remoteFault(5).
220: Any MAU that implements management of Clause 37
221: Auto-Negotiation, will map the received RF1 and RF2 bits as
222: follows: Offline maps to offline(10), Link_Failure maps to
223: remoteFault(5), and Auto-Negotiation Error maps to
224: autoNegError(11).
225:
226: The value remoteFault(5) applies to 10BASE-FB remote
227: fault indication, the 100BASE-X far-end fault indication, and
228: nonspecified remote faults from a system running Clause 28
229: Auto-Negotiation.
230:
231: The value remoteJabber(7), remoteLink loss(8), or remoteTest(9)
232: SHOULD be used instead of remoteFault(5) where the reason for
233: remote fault is identified in the remote signaling protocol.
234: Where a Clause 22 MII or Clause 35 GMII is present, a logic
235: one in the remote fault bit maps to the value remoteFault(5),
236: a logic zero in the link status bit maps to the enumeration
237: notAvailable(4). The value notAvailable(4) takes precedence
238: over remoteFault(5).
239:
240: For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to
241: the condition where the PHY (PCS with connected PMEs) is
242: initializing, the value ready(20) maps to the condition where
243: the interface is down and at least one PME in the aggregation
244: group is ready for handshake, the value available(3) maps to
245: the condition where all the PMEs in the aggregation group are
246: up, the value notAvailable(4) maps to the condition where all
247: the PMEs in the aggregation group are down and no handshake
248: tones are detected, the value availableReduced(19) maps to the
249: condition where the interface is up, a link fault is detected
250: at the receive direction by one or more PMEs in the
251: aggregation group, but at least one PME is up and the
252: enumeration pmdLinkFault(12) maps to the condition where a link
253: fault is detected at the receive direction by all of the PMEs
254: in the aggregation group.
255:
256: For 10 Gb/s the enumerations map to value of the link_fault
257: variable within the Link Fault Signaling state diagram
258: as follows: the value OK maps to the value available(3),
259: the value Local Fault maps to the value notAvailable(4),
260: and the value Remote Fault maps to the value remoteFault(5).
261: The value pmdLinkFault(12), wisFrameLoss(13),
262: wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16), or
263: dxsLinkFault(17) SHOULD be used instead of the value
264: notAvailable(4), where the reason for the Local Fault state can
265: be identified through the use of the Clause 45 MDIO Interface.
266: Where multiple reasons for the Local Fault state can be
267: identified, only the highest precedence error SHOULD be
268: reported. This precedence in descending order is as follows:
269:
270: pxsLinkFault
271: pmdLinkFault
272: wisFrameLoss
273: wisSignalLoss
274: pcsLinkFault
275: excessiveBER
276: dxsLinkFault.
277:
278: Where a Clause 45 MDIO interface is present a logic zero in
279: the PMA/PMD Receive link status bit ([IEEE802.3]
280: Section 45.2.1.2.2) maps to the value pmdLinkFault(12),
281: logic one in the LOF status bit (Section 45.2.2.10.4) maps
282: to the value wisFrameLoss(13), a logic one in the LOS
283: status bit (Section 45.2.2.10.5) maps to the value
284: wisSignalLoss, a logic zero in the PCS Receive
285: link status bit (Section 45.2.3.2.2) maps to the value
286: pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched
287: high BER status bit (Section 45.2.3.12.2) maps to the value
288: excessiveBER, a logic zero in the DTE XS receive link status
289: bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17)
290: and a logic zero in the PHY XS transmit link status bit
291: (Section 45.2.4.2.2) maps to the value pxsLinkFault(18).
292:
293: The most recent version of this textual convention is available
294: in the online version of this MIB module on the IANA web site.
295:
296: Requests for new values should be made to IANA via email
297: (iana@iana.org)."
298: REFERENCE
299: "[IEEE802.3], Section 30.5.1.1.4"
300: SYNTAX INTEGER {
301: other(1),
302: unknown(2),
303: available(3),
304: notAvailable(4),
305: remoteFault(5),
306: invalidSignal(6),
307: remoteJabber(7),
308: remoteLinkLoss(8),
309: remoteTest(9),
310: offline(10),
311: autoNegError(11),
312: pmdLinkFault(12),
313: wisFrameLoss(13),
314: wisSignalLoss(14),
315: pcsLinkFault(15),
316: excessiveBER(16),
317: dxsLinkFault(17),
318: pxsLinkFault(18),
319: availableReduced(19),
320: ready(20)
321: }
322:
323: IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION
323: warning -
warning: current type `IANAifMauAutoNegCapBits' is not referenced in this module
324: STATUS current
325: DESCRIPTION
326: "This data type is used as the syntax of the
327: ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits, and
328: ifMauAutoNegCapReceivedBits objects in the (updated) definition
329: of MAU-MIB's ifMauAutoNegTable.
330:
331: The most recent version of this textual convention is available
332: in the online version of this MIB module on the IANA web site.
333:
334: Requests for new values should be made to IANA via email
335: (iana@iana.org)."
336: REFERENCE
337: "[IEEE802.3], Section 30.6.1.1.5"
338: SYNTAX BITS {
339: bOther(0), -- other or unknown
340: b10baseT(1), -- 10BASE-T half duplex mode
341: b10baseTFD(2), -- 10BASE-T full duplex mode
342: b100baseT4(3), -- 100BASE-T4
343: b100baseTX(4), -- 100BASE-TX half duplex mode
344: b100baseTXFD(5), -- 100BASE-TX full duplex mode
345: b100baseT2(6), -- 100BASE-T2 half duplex mode
346: b100baseT2FD(7), -- 100BASE-T2 full duplex mode
347: bFdxPause(8), -- PAUSE for full-duplex links
348: bFdxAPause(9), -- Asymmetric PAUSE for full-duplex
349: -- links
350: bFdxSPause(10), -- Symmetric PAUSE for full-duplex
351: -- links
352: bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for
353: -- full-duplex links
354: b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
355: -- duplex mode
356: b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
357: -- duplex mode
358: b1000baseT(14), -- 1000BASE-T half duplex mode
359: b1000baseTFD(15) -- 1000BASE-T full duplex mode
360: }
361:
362: IANAifJackType ::= TEXTUAL-CONVENTION
362: warning -
warning: current type `IANAifJackType' is not referenced in this module
363: STATUS current
364: DESCRIPTION
365: "Common enumeration values for repeater and interface MAU
366: jack types. This data type is used as the syntax of the
367: ifJackType and rpJackType objects in the (updated) definition
368: of MAU-MIB's ifJackTable and rpJackTable respectively.
369:
370: Possible values are:
371: other(1) - undefined or unknown
372: rj45(2) - RJ45
373: rj45S(3) - RJ45 shielded
374: db9(4) - DB9
375: bnc(5) - BNC
376: fAUI(6) - AUI female
377: mAUI(7) - AUI male
378: fiberSC(8) - SC fiber
379: fiberMIC(9) - MIC fiber
380: fiberST(10) - ST fiber
381: telco(11) - Telco
382: mtrj(12) - MT-RJ fiber
383: hssdc(13) - fiber channel style-2
384: fiberLC(14) - LC fiber
385: cx4(15) - IB4X for 10GBASE-CX4
386:
387: The most recent version of this textual convention is available
388: in the online version of this MIB module on the IANA web site.
389:
390: Requests for new values should be made to IANA via email
391: (iana@iana.org)."
392: SYNTAX INTEGER {
393: other(1),
394: rj45(2),
395: rj45S(3),
396: db9(4),
397: bnc(5),
398: fAUI(6),
399: mAUI(7),
400: fiberSC(8),
401: fiberMIC(9),
402: fiberST(10),
403: telco(11),
404: mtrj(12),
405: hssdc(13),
406: fiberLC(14),
407: -- new since RFC 3636
408: cx4(15)
409: }
410:
411: -- OBJECT IDENTITIES for MAU types
412: -- (see rpMauType and ifMauType of MAU-MIB for usage)
413: -- The following definitions has been moved from RFC 3636 and
414: -- no longer appear in its revision.