Sample device dataset definitions
Sample port dataset definitions
Sample ~Atrium Data Export job
Entuity integration for BMC Atrium CMDB exports data from ENA using Data Export. Please see the Datasets section for further help and information on managing export dataset defintions and jobs.
Data Export extracts device and port details from the main Entuity database to a second database, AtriumExport. AtriumExport is populated through two dataset definitions run by one job.
These datasets and jobs cannot be amended in Entuity, as indicated by the tilda (~) prefix. When the supplied datasets and job do not match your requirements, it is recommended that you consult Entuity Professional Services and create new datasets and jobs.
Sample device dataset definitions:
During discovery, Entuity creates the data export dataset definitions, and also the defined job. The ~Atrium Devices dataset specifies the device attributes to export:
Attribute | Description |
---|---|
Location | physical location of the device. |
Manufacturer | manufacturer name. |
Model | device model. |
Name | device name. |
Polled IP Addresses | IP address Entuity uses to poll the device. |
Serial Number | device serial number. |
System Description | manufacturer's device description. |
Version | device version number. |
Sample port dataset definitions:
The ~Port Devices dataset definition specifies the following port attributes to export:
Attribute | Description |
---|---|
Alias | port's alias. |
Interface Description | brief description of the port. |
Outbound Speed | port's outbound interface speed, used e.g. when Entuity calculates port utilization. |
Short Description | brief description of the port. |
Type (IANA) | interface type, e.g. ethernet6. |
Device _> StormWorks ID | internal Entuity identifier of the port's device. It is used to maintain the association between port and device in the exported dataset. |
Sample ~Atrium Data Export job:
~Atrium Export Job includes the two datasets to export and the database to export to. By default, the Data Export job is not enabled. When enabled, it:
- runs against a single View as specified in its job definition.
- is scheduled to run each day.
- checks for any missing data in the target database over the previous two days, and would export it as part of the current job.
Comments
0 comments
Please sign in to leave a comment.