OID reference
1.3.6.1.4.1.629.204.1.4.2.1.2
Some Gigabit Ethernet compatible SFP transeivers, such as SFP-FDSGMII-M and SFP-FDSGMII-LR, have a built-in SGMII PHY. Those that do require special autonegotiation processing, without which autonegotiation will fail and the port will be unable to pass traffic. If the SFP has a built-in SGMII PHY, the user should set …
Identification
{1 3 6 1 4 1 629 204 1 4 2 1 2}
| Value | Name |
|---|---|
| 1 | notSupported |
| 2 | no |
| 3 | yes |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: nbsSffMsxPhysicalIfIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.629.204.1.4.2.1.2
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
nbsSffMsxHasSgmiiPhy OBJECT-TYPE
SYNTAX INTEGER {
notSupported (1),
no (2),
yes (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Some Gigabit Ethernet compatible SFP transeivers, such as
SFP-FDSGMII-M and SFP-FDSGMII-LR, have a built-in SGMII PHY.
Those that do require special autonegotiation processing,
without which autonegotiation will fail and the port will be
unable to pass traffic.
If the SFP has a built-in SGMII PHY, the user should set this
to yes(3)."
DEFVAL { no }
::= { nbsSffMsxEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Some Gigabit Ethernet compatible SFP transeivers, such as SFP-FDSGMII-M and SFP-FDSGMII-LR, have a built-in SGMII PHY. Those that do require special autonegotiation processing, without which autonegotiation will fail and the port will be unable to pass traffic. If the SFP has a built-in SGMII PHY, the user should set this to yes(3).
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: nbsSffMsxHasSgmiiPhy
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"nbsSffMsxHasSgmiiPhy",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notSupported",
"(",
"1",
")",
",",
"no",
"(",
"2",
")",
",",
"yes",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Some Gigabit Ethernet compatible SFP transeivers, such as SFP-FDSGMII-M and SFP-FDSGMII-LR, have a built-in SGMII PHY. Those that do require special autonegotiation processing, without which autonegotiation will fail and the port will be unable to pass traffic. If the SFP has a built-in SGMII PHY, the user should set this to yes(3).\"",
"DEFVAL",
"{",
"no",
"}",
"::=",
"{",
"nbsSffMsxEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notSupported",
1
],
[
"no",
2
],
[
"yes",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Some Gigabit Ethernet compatible SFP transeivers, such as SFP-FDSGMII-M and SFP-FDSGMII-LR, have a built-in SGMII PHY. Those that do require special autonegotiation processing, without which autonegotiation will fail and the port will be unable to pass traffic. If the SFP has a built-in SGMII PHY, the user should set this to yes(3)."
],
null,
null,
null,
[
"DEFVAL",
"no"
]
]
}Vendor MIB copy from the LibreNMS archive.
Module: NBS-SFF-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'NBS-MIB': ['nbs', 'NbsTcMHz'], 'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['Unsigned32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'OBJECT-IDENTITY'], 'NBS-CMMCENUM-MIB': ['NbsCmmcChannelBand']}Related source files and packages:
Same file in Observium Community.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.629.204.1.4.2.1.1 | nbsSffMsxPhysicalIfIndex | 0 | 0 |