MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 10 (transmission). 7 (dot3). 2 (dot3StatsTable). 1 (dot3StatsEntry). 19 (dot3StatsDuplexStatus)
OID : 1.3.6.1.2.1.10.7.2.1.19
TXT : iso. org. dod. internet. mgmt. mib-2. transmission. dot3. dot3StatsTable. dot3StatsEntry. dot3StatsDuplexStatus
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.10.7.2.1.19
Module EtherLike-MIB (CISCO)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)
Module EtherLike-MIB (DELL)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)
Module EtherLike-MIB (ietf)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)
Module EtherLike-MIB (Alcatel)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)
Module EtherLike-MIB (Force10-9.14.2.1)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)
Module EtherLike-MIB (Nexans)
Nomdot3StatsDuplexStatus
Accesreadonly
Statuscurrent
DescriptionThe mandatory mode of operation of the MAC entity. 'unknown' indicates that the mandatory duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the mandatoryly operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
SyntaxeEnumeration (1-unknown, 2-halfDuplex, 3-fullDuplex)