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). 3 (entityMapping). 1 (entLPMappingTable). 1 (entLPMappingEntry)
OID : 1.3.6.1.2.1.47.1.3.1.1
TXT : iso. org. dod. internet. mgmt. mib-2. entityMIB. entityMIBObjects. entityMapping. entLPMappingTable. entLPMappingEntry
Enfants
Détails
OID1.3.6.1.2.1.47.1.3.1.1
Module ENTITY-MIB (CISCO)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized.
Module ENTITY-MIB (DELL)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized.
Module ENTITY-MIB (ietf)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized.
Module ENTITY-MIB (Alcatel)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized.
Module ENTITY-MIB (Force10-9.14.2.1)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical entity to physical equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIBs used to manage a particular logical entity to infer how physical component information is utilized.
Module ENTITY-MIB (Nexans)
NomentLPMappingEntry
Statuscurrent
DescriptionInformation about a particular logical-entity-to-physical- equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIB modules used to manage a particular logical entity to infer how physical component information is utilized.