MIB Discovery

Recherche :

1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 47 (entityMIB). 1 (entityMIBObjects). 1 (entityPhysical). 1 (entPhysicalTable). 1 (entPhysicalEntry). 7 (entPhysicalName)
OID : 1.3.6.1.2.1.47.1.1.1.1.7
TXT : iso. org. dod. internet. mgmt. mib-2. entityMIB. entityMIBObjects. entityPhysical. entPhysicalTable. entPhysicalEntry. entPhysicalName
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.47.1.1.1.1.7
Module ENTITY-MIB (CISCO)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name (e.g., `console') or a simple component number (e.g., port or module number, such as `1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (DELL)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name, such as `console' or a simple component number (e.g., port or module number), such as `1', depending on the physical component naming syntax of the device. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (ietf)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name (e.g., `console') or a simple component number (e.g., port or module number, such as `1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Alcatel)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name (e.g., `console') or a simple component number (e.g., port or module number, such as `1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Force10-9.14.2.1)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name (e.g., `console') or a simple component number (e.g., port or module number, such as `1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Nexans)
NomentPhysicalName
Accesreadonly
Statuscurrent
DescriptionThe textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
D. Fournier - 2024