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). 3 (entityMapping). 2 (entAliasMappingTable). 1 (entAliasMappingEntry)
OID : 1.3.6.1.2.1.47.1.3.2.1
TXT : iso. org. dod. internet. mgmt. mib-2. entityMIB. entityMIBObjects. entityMapping. entAliasMappingTable. entAliasMappingEntry
Enfants
Détails
OID1.3.6.1.2.1.47.1.3.2.1
Module ENTITY-MIB (CISCO)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular physical equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
Module ENTITY-MIB (DELL)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular physical equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values which represent physical ports (i.e. associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
Module ENTITY-MIB (ietf)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular physical equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
Module ENTITY-MIB (Alcatel)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular physical equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
Module ENTITY-MIB (Force10-9.14.2.1)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular physical equipment, logical entity to external identifier binding. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
Module ENTITY-MIB (Nexans)
NomentAliasMappingEntry
Statuscurrent
DescriptionInformation about a particular binding between a logical entity/physical component pair and an external identifier. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero object DESCRIPTION clause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
D. Fournier - 2024