ENA internal identifiers

ENA object types

ENA device types

eosObjectID

ENA uses a series of codes to identify the types of objects it manages. These internal codes are useful when troubleshooting issues.

This article details the two types of codes and how they are used in a third, eosObjectID, to uniquely identify a managed object.

ENA object types:

ENA identifies different managed object types by assigning each their own unique identifier. This number is only used within ENA.

ENA device types:

ENA identifies different device types by assigning each their own unique identifier. This number is only used within ENA. For example, the discovery ping technology used by ENA for its maps can be configured through entuity.cfg to exclude certain device types - these device types are specified through their device identifiers.

eosObjectID:

eosObjectID is an internal ENA identifier that uniquely identifies ENA managed objects. eosObjectID is a bit mask with the format:

objectType.objectID.portID.StormWorksID

where:

• objectType is the internal ENA object type, e.g. 1 for port, 4 for device.
• objectID is the unique object, e.g. device identifier.
• portID is the unique port identifer, when used in the context of objectID.
• StormWorksID is the unique StormWorks identifier. It is set to 0 when the object does not have a StormWorks number.

Examples of valid eosObjectID identifiers:

• 1.131.17.36477
  represents port 17 on device 131. It also has the StormWorks identifer, 36477.
• 4.131.1.0
  represents device 131. It does not include a StormWorks identifier, 0.

eosObjectID is normally only used by internal ENA processes. However, they can be viewed in the following cases:

• ForkEvent forwards objectID and objectType as part of eosObjectID.
• ENA Remedy AR System integration module uses ForkEvent to forward objectID, objectType and StormWorksID as part of eosObjectID.
• Flex Reports allow you to report on StormWorks identifiers when you select Show Hidden Data.