Support for enAliasMappingTable Question ?

[Nasir Siddiqui <nsiddiqui@catena.com>]

Hi All,

I have been looking at some autodiscovery-table requirements, and RFC 2737
says that entAliasMappingTable is only required when you have a SNMP agent
with multiple contexts (SNMPv3) or logical entities (SNMP v1/v2). These
contexts give the ability to view multiple logical network elements in a
single box. The entAliasMapping table seems to give the ability to map an
ifIndex'ed object to a physical location or resource. 

If in a product there is only one network element and therefore only one
naming scope. In addition, if you want to know the physical location of an
interface (ifTable) or a port (entPhysicalTable), the information resides in
the ifDescr MIB objects of ifTable and entPhysicalName MIB objects of
entPhysicalTable. 

In this situation is there a support required  for entAliasMappingTable from
the entity MIB. Or  using ifDescr from if MIB is enough ?

Can that effect configuring multiple communities for one network element ?

Regards,

Nasir.