1IANA-MAU-MIB DEFINITIONS ::= BEGIN 2 3 IMPORTS 4 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 5 FROM SNMPv2-SMI 6 TEXTUAL-CONVENTION 7 FROM SNMPv2-TC 8 ; 9 10 ianaMauMIB MODULE-IDENTITY 11 LAST-UPDATED "200704210000Z" -- April 21, 2007 12 ORGANIZATION "IANA" 13 CONTACT-INFO " Internet Assigned Numbers Authority 14 15 Postal: ICANN 16 4676 Admiralty Way, Suite 330 17 Marina del Rey, CA 90292 18 19 Tel: +1-310-823-9358 20 EMail: iana&iana.org" 21 22 DESCRIPTION 23 "This MIB module defines dot3MauType OBJECT-IDENTITIES and 24 IANAifMauListBits, IANAifMauMediaAvailable, 25 IANAifMauAutoNegCapBits, and IANAifJackType 26 27 TEXTUAL-CONVENTIONs, specifying enumerated values of the 28 ifMauTypeListBits, ifMauMediaAvailable / rpMauMediaAvailable, 29 ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits / 30 ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects 31 respectively, defined in the MAU-MIB. 32 33 It is intended that each new MAU type, Media Availability 34 state, Auto Negotiation capability and/or Jack type defined by 35 the IEEE 802.3 working group and approved for publication in a 36 revision of IEEE Std 802.3 will be added to this MIB module, 37 provided that it is suitable for being managed by the base 38 objects in the MAU-MIB. An Expert Review, as defined in 39 RFC 2434 [RFC2434], is REQUIRED for such additions. 40 41 The following reference is used throughout this MIB module: 42 43 [IEEE802.3] refers to: 44 IEEE Std 802.3, 2005 Edition: 'IEEE Standard for 45 Information technology - Telecommunications and information 46 exchange between systems - Local and metropolitan area 47 networks - Specific requirements - 48 Part 3: Carrier sense multiple access with collision 49 detection (CSMA/CD) access method and physical layer 50 specifications'. 51 52 This reference should be updated as appropriate when new 53 MAU types, Media Availability states, Auto Negotiation 54 capabilities, and/or Jack types are added to this MIB module. 55 56 Copyright (C) The IETF Trust (2007). 57 The initial version of this MIB module was published in 58 RFC 4836; for full legal notices see the RFC itself. 59 Supplementary information may be available at: 60 http://www.ietf.org/copyrights/ianamib.html" 61 62 REVISION "200704210000Z" -- April 21, 2007 63 DESCRIPTION "Initial version of this MIB as published in 64 RFC 4836." 65 ::= { mib-2 154 } 66 67 -- Textual Conventions 68 69 IANAifMauTypeListBits ::= TEXTUAL-CONVENTION 70 STATUS current 71 DESCRIPTION 72 "This data type is used as the syntax of the ifMauTypeListBits 73 object in the (updated) definition of MAU-MIB's ifMauTable. 74 75 The most recent version of this textual convention is available 76 in the online version of this MIB module on the IANA web site. 77 78 Requests for new values should be made to IANA via email 79 (iana&iana.org). 80 81 Note that changes in this textual convention SHALL be 82 synchronized with relevant changes in the dot3MauType 83 OBJECT-IDENTITIES." 84 REFERENCE 85 "[IEEE802.3], Section 30.5.1.1.2" 86 SYNTAX BITS { 87 bOther(0), -- other or unknown 88 bAUI(1), -- AUI 89 b10base5(2), -- 10BASE-5 90 bFoirl(3), -- FOIRL 91 92 b10base2(4), -- 10BASE-2 93 b10baseT(5), -- 10BASE-T duplex mode unknown 94 b10baseFP(6), -- 10BASE-FP 95 b10baseFB(7), -- 10BASE-FB 96 b10baseFL(8), -- 10BASE-FL duplex mode unknown 97 b10broad36(9), -- 10BROAD36 98 b10baseTHD(10), -- 10BASE-T half duplex mode 99 b10baseTFD(11), -- 10BASE-T full duplex mode 100 b10baseFLHD(12), -- 10BASE-FL half duplex mode 101 b10baseFLFD(13), -- 10BASE-FL full duplex mode 102 b100baseT4(14), -- 100BASE-T4 103 b100baseTXHD(15), -- 100BASE-TX half duplex mode 104 b100baseTXFD(16), -- 100BASE-TX full duplex mode 105 b100baseFXHD(17), -- 100BASE-FX half duplex mode 106 b100baseFXFD(18), -- 100BASE-FX full duplex mode 107 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 108 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 109 110 b1000baseXHD(21), -- 1000BASE-X half duplex mode 111 b1000baseXFD(22), -- 1000BASE-X full duplex mode 112 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 113 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 114 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 115 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 116 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 117 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 118 b1000baseTHD(29), -- 1000BASE-T half duplex mode 119 b1000baseTFD(30), -- 1000BASE-T full duplex mode 120 121 b10GbaseX(31), -- 10GBASE-X 122 b10GbaseLX4(32), -- 10GBASE-LX4 123 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 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 173 remoteLinkLoss(8) - remote fault, due to link loss 174 remoteTest(9) - remote fault, due to test 175 offline(10) - offline, Clause 37 Auto-Negotiation 176 only 177 autoNegError(11) - Auto-Negotiation Error, Clause 37 178 Auto-Negotiation only 179 pmdLinkFault(12) - PMA/PMD receive link fault. In case 180 of PAF (2BASE-TL / 10PASS-TS PHYs), 181 all PMEs in the aggregation group have 182 detected a link fault 183 wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only 184 wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only 185 pcsLinkFault(15) - PCS receive link fault 186 excessiveBER(16) - PCS Bit Error Ratio monitor 187 reporting excessive error ratio 188 dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only 189 pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only 190 availableReduced(19) - link normal, reduced bandwidth, 191 2BASE-TL / 10PASS-TS only 192 ready(20) - at least one PME in the aggregation 193 group is detecting handshake tones, 194 2BASE-TL / 10PASS-TS only 195 196 If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T, 197 10BASE-F), then this is equivalent to the link test fail 198 state/low light function. For an AUI, 10BASE2, 10BASE5, or 199 10BROAD36 MAU, this indicates whether loopback is detected on 200 the DI circuit. The value of this attribute persists between 201 packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and 202 10BASEFP. 203 204 At power-up or following a reset, the Media Available state 205 will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and 206 10BASE-FP MAUs. For these MAUs loopback will be tested on each 207 transmission during which no collision is detected. 208 If DI is receiving input when DO returns to IDL after a 209 transmission and there has been no collision during the 210 transmission, then loopback will be detected. The Media 211 Available state will only change during noncollided 212 transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and 213 10BASE-FP MAUs. 214 215 For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX, 216 100BASE-LX10, and 100BASE-BX10 PHYs the enumerations match the 217 states within the link integrity state diagram. 218 Any MAU that implements management of [IEEE802.3] Clause 219 28 Auto-Negotiation, will map remote fault indication to 220 remoteFault(5). 221 222 Any MAU that implements management of Clause 37 223 Auto-Negotiation, will map the received RF1 and RF2 bits as 224 follows: Offline maps to offline(10), Link_Failure maps to 225 remoteFault(5), and Auto-Negotiation Error maps to 226 autoNegError(11). 227 228 The value remoteFault(5) applies to 10BASE-FB remote 229 fault indication, the 100BASE-X far-end fault indication, and 230 nonspecified remote faults from a system running Clause 28 231 Auto-Negotiation. 232 233 The value remoteJabber(7), remoteLink loss(8), or remoteTest(9) 234 SHOULD be used instead of remoteFault(5) where the reason for 235 remote fault is identified in the remote signaling protocol. 236 Where a Clause 22 MII or Clause 35 GMII is present, a logic 237 one in the remote fault bit maps to the value remoteFault(5), 238 a logic zero in the link status bit maps to the enumeration 239 notAvailable(4). The value notAvailable(4) takes precedence 240 over remoteFault(5). 241 242 For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to 243 the condition where the PHY (PCS with connected PMEs) is 244 initializing, the value ready(20) maps to the condition where 245 the interface is down and at least one PME in the aggregation 246 group is ready for handshake, the value available(3) maps to 247 the condition where all the PMEs in the aggregation group are 248 up, the value notAvailable(4) maps to the condition where all 249 the PMEs in the aggregation group are down and no handshake 250 tones are detected, the value availableReduced(19) maps to the 251 condition where the interface is up, a link fault is detected 252 at the receive direction by one or more PMEs in the 253 aggregation group, but at least one PME is up and the 254 enumeration pmdLinkFault(12) maps to the condition where a link 255 fault is detected at the receive direction by all of the PMEs 256 in the aggregation group. 257 258 For 10 Gb/s the enumerations map to value of the link_fault 259 variable within the Link Fault Signaling state diagram 260 as follows: the value OK maps to the value available(3), 261 the value Local Fault maps to the value notAvailable(4), 262 and the value Remote Fault maps to the value remoteFault(5). 263 The value pmdLinkFault(12), wisFrameLoss(13), 264 wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16), or 265 dxsLinkFault(17) SHOULD be used instead of the value 266 notAvailable(4), where the reason for the Local Fault state can 267 be identified through the use of the Clause 45 MDIO Interface. 268 Where multiple reasons for the Local Fault state can be 269 identified, only the highest precedence error SHOULD be 270 271 reported. This precedence in descending order is as follows: 272 273 pxsLinkFault 274 pmdLinkFault 275 wisFrameLoss 276 wisSignalLoss 277 pcsLinkFault 278 excessiveBER 279 dxsLinkFault. 280 281 Where a Clause 45 MDIO interface is present a logic zero in 282 the PMA/PMD Receive link status bit ([IEEE802.3] 283 Section 45.2.1.2.2) maps to the value pmdLinkFault(12), 284 logic one in the LOF status bit (Section 45.2.2.10.4) maps 285 to the value wisFrameLoss(13), a logic one in the LOS 286 status bit (Section 45.2.2.10.5) maps to the value 287 wisSignalLoss, a logic zero in the PCS Receive 288 link status bit (Section 45.2.3.2.2) maps to the value 289 pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched 290 high BER status bit (Section 45.2.3.12.2) maps to the value 291 excessiveBER, a logic zero in the DTE XS receive link status 292 bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17) 293 and a logic zero in the PHY XS transmit link status bit 294 (Section 45.2.4.2.2) maps to the value pxsLinkFault(18). 295 296 The most recent version of this textual convention is available 297 in the online version of this MIB module on the IANA web site. 298 299 Requests for new values should be made to IANA via email 300 (iana&iana.org)." 301 REFERENCE 302 "[IEEE802.3], Section 30.5.1.1.4" 303 SYNTAX INTEGER { 304 other(1), 305 unknown(2), 306 available(3), 307 notAvailable(4), 308 remoteFault(5), 309 invalidSignal(6), 310 remoteJabber(7), 311 remoteLinkLoss(8), 312 remoteTest(9), 313 offline(10), 314 autoNegError(11), 315 pmdLinkFault(12), 316 wisFrameLoss(13), 317 wisSignalLoss(14), 318 pcsLinkFault(15), 319 320 excessiveBER(16), 321 dxsLinkFault(17), 322 pxsLinkFault(18), 323 availableReduced(19), 324 ready(20) 325 } 326 327 IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION 328 STATUS current 329 DESCRIPTION 330 "This data type is used as the syntax of the 331 ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits, and 332 ifMauAutoNegCapReceivedBits objects in the (updated) definition 333 of MAU-MIB's ifMauAutoNegTable. 334 335 The most recent version of this textual convention is available 336 in the online version of this MIB module on the IANA web site. 337 338 Requests for new values should be made to IANA via email 339 (iana&iana.org)." 340 REFERENCE 341 "[IEEE802.3], Section 30.6.1.1.5" 342 SYNTAX BITS { 343 bOther(0), -- other or unknown 344 b10baseT(1), -- 10BASE-T half duplex mode 345 b10baseTFD(2), -- 10BASE-T full duplex mode 346 b100baseT4(3), -- 100BASE-T4 347 b100baseTX(4), -- 100BASE-TX half duplex mode 348 b100baseTXFD(5), -- 100BASE-TX full duplex mode 349 b100baseT2(6), -- 100BASE-T2 half duplex mode 350 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 351 bFdxPause(8), -- PAUSE for full-duplex links 352 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 353 -- links 354 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 355 -- links 356 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 357 -- full-duplex links 358 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 359 -- duplex mode 360 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 361 -- duplex mode 362 b1000baseT(14), -- 1000BASE-T half duplex mode 363 b1000baseTFD(15) -- 1000BASE-T full duplex mode 364 } 365 366 IANAifJackType ::= TEXTUAL-CONVENTION 367 STATUS current 368 369 DESCRIPTION 370 "Common enumeration values for repeater and interface MAU 371 jack types. This data type is used as the syntax of the 372 ifJackType and rpJackType objects in the (updated) definition 373 of MAU-MIB's ifJackTable and rpJackTable respectively. 374 375 Possible values are: 376 other(1) - undefined or unknown 377 rj45(2) - RJ45 378 rj45S(3) - RJ45 shielded 379 db9(4) - DB9 380 bnc(5) - BNC 381 fAUI(6) - AUI female 382 mAUI(7) - AUI male 383 fiberSC(8) - SC fiber 384 fiberMIC(9) - MIC fiber 385 fiberST(10) - ST fiber 386 telco(11) - Telco 387 mtrj(12) - MT-RJ fiber 388 hssdc(13) - fiber channel style-2 389 fiberLC(14) - LC fiber 390 cx4(15) - IB4X for 10GBASE-CX4 391 392 The most recent version of this textual convention is available 393 in the online version of this MIB module on the IANA web site. 394 395 Requests for new values should be made to IANA via email 396 (iana&iana.org)." 397 SYNTAX INTEGER { 398 other(1), 399 rj45(2), 400 rj45S(3), 401 db9(4), 402 bnc(5), 403 fAUI(6), 404 mAUI(7), 405 fiberSC(8), 406 fiberMIC(9), 407 fiberST(10), 408 telco(11), 409 mtrj(12), 410 hssdc(13), 411 fiberLC(14), 412 -- new since RFC 3636 413 cx4(15) 414 } 415 416 -- OBJECT IDENTITIES for MAU types 417 418 -- (see rpMauType and ifMauType of MAU-MIB for usage) 419 -- The following definitions has been moved from RFC 3636 and 420 -- no longer appear in its revision. 421 422 dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 } 423 424 dot3MauTypeAUI OBJECT-IDENTITY 425 STATUS current 426 DESCRIPTION "no internal MAU, view from AUI" 427 REFERENCE "[IEEE802.3], Section 7" 428 ::= { dot3MauType 1 } 429 430 dot3MauType10Base5 OBJECT-IDENTITY 431 STATUS current 432 DESCRIPTION "thick coax MAU" 433 REFERENCE "[IEEE802.3], Section 7" 434 ::= { dot3MauType 2 } 435 436 dot3MauTypeFoirl OBJECT-IDENTITY 437 STATUS current 438 DESCRIPTION "FOIRL MAU" 439 REFERENCE "[IEEE802.3], Section 9.9" 440 ::= { dot3MauType 3 } 441 442 dot3MauType10Base2 OBJECT-IDENTITY 443 STATUS current 444 DESCRIPTION "thin coax MAU" 445 REFERENCE "[IEEE802.3], Section 10" 446 ::= { dot3MauType 4 } 447 448 dot3MauType10BaseT OBJECT-IDENTITY 449 STATUS current 450 DESCRIPTION "UTP MAU. 451 Note that it is strongly recommended that 452 agents return either dot3MauType10BaseTHD or 453 dot3MauType10BaseTFD if the duplex mode is 454 known. However, management applications should 455 be prepared to receive this MAU type value from 456 older agent implementations." 457 REFERENCE "[IEEE802.3], Section 14" 458 ::= { dot3MauType 5 } 459 460 dot3MauType10BaseFP OBJECT-IDENTITY 461 STATUS current 462 DESCRIPTION "passive fiber MAU" 463 REFERENCE "[IEEE802.3], Section 16" 464 ::= { dot3MauType 6 } 465 466 dot3MauType10BaseFB OBJECT-IDENTITY 467 STATUS current 468 DESCRIPTION "sync fiber MAU" 469 REFERENCE "[IEEE802.3], Section 17" 470 ::= { dot3MauType 7 } 471 472 dot3MauType10BaseFL OBJECT-IDENTITY 473 STATUS current 474 DESCRIPTION "async fiber MAU. 475 Note that it is strongly recommended that 476 agents return either dot3MauType10BaseFLHD or 477 dot3MauType10BaseFLFD if the duplex mode is 478 known. However, management applications should 479 be prepared to receive this MAU type value from 480 older agent implementations." 481 REFERENCE "[IEEE802.3], Section 18" 482 ::= { dot3MauType 8 } 483 484 dot3MauType10Broad36 OBJECT-IDENTITY 485 STATUS current 486 DESCRIPTION "broadband DTE MAU. 487 Note that 10BROAD36 MAUs can be attached to 488 interfaces but not to repeaters." 489 REFERENCE "[IEEE802.3], Section 11" 490 ::= { dot3MauType 9 } 491 492 ------ new since RFC 1515: 493 dot3MauType10BaseTHD OBJECT-IDENTITY 494 STATUS current 495 DESCRIPTION "UTP MAU, half duplex mode" 496 REFERENCE "[IEEE802.3], Section 14" 497 ::= { dot3MauType 10 } 498 499 dot3MauType10BaseTFD OBJECT-IDENTITY 500 STATUS current 501 DESCRIPTION "UTP MAU, full duplex mode" 502 REFERENCE "[IEEE802.3], Section 14" 503 ::= { dot3MauType 11 } 504 505 dot3MauType10BaseFLHD OBJECT-IDENTITY 506 STATUS current 507 DESCRIPTION "async fiber MAU, half duplex mode" 508 REFERENCE "[IEEE802.3], Section 18" 509 ::= { dot3MauType 12 } 510 511 dot3MauType10BaseFLFD OBJECT-IDENTITY 512 STATUS current 513 DESCRIPTION "async fiber MAU, full duplex mode" 514 515 REFERENCE "[IEEE802.3], Section 18" 516 ::= { dot3MauType 13 } 517 518 dot3MauType100BaseT4 OBJECT-IDENTITY 519 STATUS current 520 DESCRIPTION "4 pair category 3 UTP" 521 REFERENCE "[IEEE802.3], Section 23" 522 ::= { dot3MauType 14 } 523 524 dot3MauType100BaseTXHD OBJECT-IDENTITY 525 STATUS current 526 DESCRIPTION "2 pair category 5 UTP, half duplex mode" 527 REFERENCE "[IEEE802.3], Section 25" 528 ::= { dot3MauType 15 } 529 530 dot3MauType100BaseTXFD OBJECT-IDENTITY 531 STATUS current 532 DESCRIPTION "2 pair category 5 UTP, full duplex mode" 533 REFERENCE "[IEEE802.3], Section 25" 534 ::= { dot3MauType 16 } 535 536 dot3MauType100BaseFXHD OBJECT-IDENTITY 537 STATUS current 538 DESCRIPTION "X fiber over PMT, half duplex mode" 539 REFERENCE "[IEEE802.3], Section 26" 540 ::= { dot3MauType 17 } 541 542 dot3MauType100BaseFXFD OBJECT-IDENTITY 543 STATUS current 544 DESCRIPTION "X fiber over PMT, full duplex mode" 545 REFERENCE "[IEEE802.3], Section 26" 546 ::= { dot3MauType 18 } 547 548 dot3MauType100BaseT2HD OBJECT-IDENTITY 549 STATUS current 550 DESCRIPTION "2 pair category 3 UTP, half duplex mode" 551 REFERENCE "[IEEE802.3], Section 32" 552 ::= { dot3MauType 19 } 553 554 dot3MauType100BaseT2FD OBJECT-IDENTITY 555 STATUS current 556 DESCRIPTION "2 pair category 3 UTP, full duplex mode" 557 REFERENCE "[IEEE802.3], Section 32" 558 ::= { dot3MauType 20 } 559 560 ------ new since RFC 2239: 561 dot3MauType1000BaseXHD OBJECT-IDENTITY 562 STATUS current 563 564 DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode" 565 REFERENCE "[IEEE802.3], Section 36" 566 ::= { dot3MauType 21 } 567 568 dot3MauType1000BaseXFD OBJECT-IDENTITY 569 STATUS current 570 DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode" 571 REFERENCE "[IEEE802.3], Section 36" 572 ::= { dot3MauType 22 } 573 574 dot3MauType1000BaseLXHD OBJECT-IDENTITY 575 STATUS current 576 DESCRIPTION "Fiber over long-wavelength laser, half duplex 577 mode" 578 REFERENCE "[IEEE802.3], Section 38" 579 ::= { dot3MauType 23 } 580 581 dot3MauType1000BaseLXFD OBJECT-IDENTITY 582 STATUS current 583 DESCRIPTION "Fiber over long-wavelength laser, full duplex 584 mode" 585 REFERENCE "[IEEE802.3], Section 38" 586 ::= { dot3MauType 24 } 587 588 dot3MauType1000BaseSXHD OBJECT-IDENTITY 589 STATUS current 590 DESCRIPTION "Fiber over short-wavelength laser, half 591 duplex mode" 592 REFERENCE "[IEEE802.3], Section 38" 593 ::= { dot3MauType 25 } 594 595 dot3MauType1000BaseSXFD OBJECT-IDENTITY 596 STATUS current 597 DESCRIPTION "Fiber over short-wavelength laser, full 598 duplex mode" 599 REFERENCE "[IEEE802.3], Section 38" 600 ::= { dot3MauType 26 } 601 602 dot3MauType1000BaseCXHD OBJECT-IDENTITY 603 STATUS current 604 DESCRIPTION "Copper over 150-Ohm balanced cable, half 605 duplex mode" 606 REFERENCE "[IEEE802.3], Section 39" 607 ::= { dot3MauType 27 } 608 609 dot3MauType1000BaseCXFD OBJECT-IDENTITY 610 STATUS current 611 DESCRIPTION "Copper over 150-Ohm balanced cable, full 612 613 duplex mode" 614 REFERENCE "[IEEE802.3], Section 39" 615 ::= { dot3MauType 28 } 616 617 dot3MauType1000BaseTHD OBJECT-IDENTITY 618 STATUS current 619 DESCRIPTION "Four-pair Category 5 UTP, half duplex mode" 620 REFERENCE "[IEEE802.3], Section 40" 621 ::= { dot3MauType 29 } 622 623 dot3MauType1000BaseTFD OBJECT-IDENTITY 624 STATUS current 625 DESCRIPTION "Four-pair Category 5 UTP, full duplex mode" 626 REFERENCE "[IEEE802.3], Section 40" 627 ::= { dot3MauType 30 } 628 629 ------ new since RFC 2668: 630 dot3MauType10GigBaseX OBJECT-IDENTITY 631 STATUS current 632 DESCRIPTION "X PCS/PMA, unknown PMD." 633 REFERENCE "[IEEE802.3], Section 48" 634 ::= { dot3MauType 31 } 635 636 dot3MauType10GigBaseLX4 OBJECT-IDENTITY 637 STATUS current 638 DESCRIPTION "X fiber over WWDM optics" 639 REFERENCE "[IEEE802.3], Section 53" 640 ::= { dot3MauType 32 } 641 642 dot3MauType10GigBaseR OBJECT-IDENTITY 643 STATUS current 644 DESCRIPTION "R PCS/PMA, unknown PMD." 645 REFERENCE "[IEEE802.3], Section 49" 646 ::= { dot3MauType 33 } 647 648 dot3MauType10GigBaseER OBJECT-IDENTITY 649 STATUS current 650 DESCRIPTION "R fiber over 1550 nm optics" 651 REFERENCE "[IEEE802.3], Section 52" 652 ::= { dot3MauType 34 } 653 654 dot3MauType10GigBaseLR OBJECT-IDENTITY 655 STATUS current 656 DESCRIPTION "R fiber over 1310 nm optics" 657 REFERENCE "[IEEE802.3], Section 52" 658 ::= { dot3MauType 35 } 659 660 dot3MauType10GigBaseSR OBJECT-IDENTITY 661 662 STATUS current 663 DESCRIPTION "R fiber over 850 nm optics" 664 REFERENCE "[IEEE802.3], Section 52" 665 ::= { dot3MauType 36 } 666 667 dot3MauType10GigBaseW OBJECT-IDENTITY 668 STATUS current 669 DESCRIPTION "W PCS/PMA, unknown PMD." 670 REFERENCE "[IEEE802.3], Section 49 and 50" 671 ::= { dot3MauType 37 } 672 673 dot3MauType10GigBaseEW OBJECT-IDENTITY 674 STATUS current 675 DESCRIPTION "W fiber over 1550 nm optics" 676 REFERENCE "[IEEE802.3], Section 52" 677 ::= { dot3MauType 38 } 678 679 dot3MauType10GigBaseLW OBJECT-IDENTITY 680 STATUS current 681 DESCRIPTION "W fiber over 1310 nm optics" 682 REFERENCE "[IEEE802.3], Section 52" 683 ::= { dot3MauType 39 } 684 685 dot3MauType10GigBaseSW OBJECT-IDENTITY 686 STATUS current 687 DESCRIPTION "W fiber over 850 nm optics" 688 REFERENCE "[IEEE802.3], Section 52" 689 ::= { dot3MauType 40 } 690 691 ------ new since RFC 3636: 692 dot3MauType10GigBaseCX4 OBJECT-IDENTITY 693 STATUS current 694 DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable" 695 REFERENCE "[IEEE802.3], Section 54" 696 ::= { dot3MauType 41 } 697 698 dot3MauType2BaseTL OBJECT-IDENTITY 699 STATUS current 700 DESCRIPTION "Voice grade UTP copper, up to 2700m, optional PAF" 701 REFERENCE "[IEEE802.3], Sections 61 and 63" 702 ::= { dot3MauType 42 } 703 704 dot3MauType10PassTS OBJECT-IDENTITY 705 STATUS current 706 DESCRIPTION "Voice grade UTP copper, up to 750m, optional PAF" 707 REFERENCE "[IEEE802.3], Sections 61 and 62" 708 ::= { dot3MauType 43 } 709 710 dot3MauType100BaseBX10D OBJECT-IDENTITY 711 STATUS current 712 DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km" 713 REFERENCE "[IEEE802.3], Section 58" 714 ::= { dot3MauType 44 } 715 716 dot3MauType100BaseBX10U OBJECT-IDENTITY 717 STATUS current 718 DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km" 719 REFERENCE "[IEEE802.3], Section 58" 720 ::= { dot3MauType 45 } 721 722 dot3MauType100BaseLX10 OBJECT-IDENTITY 723 STATUS current 724 DESCRIPTION "Two single-mode fibers, long wavelength, 10km" 725 REFERENCE "[IEEE802.3], Section 58" 726 ::= { dot3MauType 46 } 727 728 dot3MauType1000BaseBX10D OBJECT-IDENTITY 729 STATUS current 730 DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km" 731 REFERENCE "[IEEE802.3], Section 59" 732 ::= { dot3MauType 47 } 733 734 dot3MauType1000BaseBX10U OBJECT-IDENTITY 735 STATUS current 736 DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km" 737 REFERENCE "[IEEE802.3], Section 59" 738 ::= { dot3MauType 48 } 739 740 dot3MauType1000BaseLX10 OBJECT-IDENTITY 741 STATUS current 742 DESCRIPTION "Two sigle-mode fiber, long wavelength, 10km" 743 REFERENCE "[IEEE802.3], Section 59" 744 ::= { dot3MauType 49 } 745 746 dot3MauType1000BasePX10D OBJECT-IDENTITY 747 STATUS current 748 DESCRIPTION "One single-mode fiber EPON OLT, 10km" 749 REFERENCE "[IEEE802.3], Section 60" 750 ::= { dot3MauType 50 } 751 752 dot3MauType1000BasePX10U OBJECT-IDENTITY 753 STATUS current 754 DESCRIPTION "One single-mode fiber EPON ONU, 10km" 755 REFERENCE "[IEEE802.3], Section 60" 756 ::= { dot3MauType 51 } 757 758 dot3MauType1000BasePX20D OBJECT-IDENTITY 759 STATUS current 760 DESCRIPTION "One single-mode fiber EPON OLT, 20km" 761 REFERENCE "[IEEE802.3], Section 60" 762 ::= { dot3MauType 52 } 763 764 dot3MauType1000BasePX20U OBJECT-IDENTITY 765 STATUS current 766 DESCRIPTION "One single-mode fiber EPON ONU, 20km" 767 REFERENCE "[IEEE802.3], Section 60" 768 ::= { dot3MauType 53 } 769 770END 771