MIB Discovery
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). 9 (entPhysicalFirmwareRev)
OID : 1.3.6.1.2.1.47.1.1.1.1.9
TXT : iso. org. dod. internet. mgmt. mib-2. entityMIB. entityMIBObjects. entityPhysical. entPhysicalTable. entPhysicalEntry. entPhysicalFirmwareRev
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.47.1.1.1.1.9
Module ENTITY-MIB (CISCO)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (DELL)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (ietf)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Alcatel)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Force10-9.14.2.1)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)
Module ENTITY-MIB (Nexans)
NomentPhysicalFirmwareRev
Accesreadonly
Statuscurrent
DescriptionThe vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
SyntaxeSnmpAdminString (SNMP-FRAMEWORK-MIB)