All MIBs › RFC1285-MIB › snmpFddiPORTChipSet
snmpFddiPORTChipSet
Module: RFC1285-MIB
OID (symbolic): RFC1285-MIB::snmpFddiPORTChipSet
OID (numeric): 1.3.6.1.2.1.10.15.4.2.1.24
Node type: OBJECT-TYPE
Type: OBJECT IDENTIFIER
Access: read-only
Description: This object identifies the hardware chip(s) which is (are) principally responsible for the implementation of the PORT (PHY) function. A few OBJECT IDENTIFIERS are identified elsewhere in this memo. For those The assignment of additional OBJECT IDENTIFIERs to various types of hardware chip sets is managed by the IANA. For example, vendors whose chip sets are not defined in this memo may request a number from the Internet Assigned Numbers Authority (IANA) which indicates the assignment of a enterprise specific subtree which, among other things, may be used to allocate OBJECT IDENTIFIER assignments for that enterprise's chip sets. Similarly, in the absence of an appropriately assigned OBJECT IDENTIFIER in this memo or in an enterprise specific subtree of a chip vendor, a board or system vendor can request a number for a subtree from the IANA and make an appropriate assignment. It is desired that, whenever possible, the same OBJECT IDENTIFIER be used for all chips of a given type. Consequently, the assignment made in this memo for a chip, if any, should be used in preference to any other assignment and the assignment made by the chip manufacturer, if any, should be used in preference to assignments made by users of those chips. If the hardware chip set is unknown, the object identifier
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownChipSet is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this
value.
What is snmpFddiPORTChipSet?
Identifies, via an OBJECT IDENTIFIER, the specific hardware chipset implementing this port's PHY (physical layer) function, or unknownChipSet if not identifiable. Admins use this for hardware inventory or chipset-specific troubleshooting, mirroring snmpFddiMACChipSet but for the port's physical-layer silicon.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.15.4.2.1.24 snmpwalk -v2c -c public <target> RFC1285-MIB::snmpFddiPORTChipSet
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.10.15.4.2.1.24.1 snmpget -v2c -c public <target> RFC1285-MIB::snmpFddiPORTChipSet.1
Start monitoring vendor-neutral, standards-based MIB, FDDI ring stations, concentrators, and router FDDI interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1285-MIB::snmpFddiPORTChipSet OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, FDDI ring stations, concentrators, and router FDDI interfaces from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.10.15 | fddi | FDDI-SMT73-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.15.4 | snmpFddiPORT | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2 | snmpFddiPORTTable | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2.1 | snmpFddiPORTEntry | RFC1285-MIB |
| 1.3.6.1.2.1.10.15.4.2.1.24 | snmpFddiPORTChipSet | RFC1285-MIB |