MariaDB database corruption
An issue in MariaDB can cause the database to restart, when a certain query undertaken by the vipman process runs on larger installations. This risks causing database corruption. A fix for this has been released in ENA patch P01.
In response to this bug, the ENA v17.0 GA image has been removed from the Entuity FTP server. This has now been replaced with a single image containing ENA v17.0 and patch P01.
Users that have already installed ENA v17.0 GA, or are looking to install ENA v17.0 GA, must see our article on installing ENA patches for further information on this fix.
Services - permissions
In ENA, services should only be editable by users who have the 'Service Administration' permission. However, as of ENA release in June 2018, the Service Administration permission is missing (only Service Creation exists). This means that, currently, services are only editable by administrators and the original creator of the service. This will be fixed in a future patch, so that services will only be editable by users who have the Service Administration permission (regardless of which user originally created the service).
Services - managed objects
In ENA, managed objects should not be automatically considered as part of a View, just because they are in a service that is in that View. This is working for some managed objects (e.g. devices and ports), but not for others (e.g. a pure StormWorks object). The following objects in a service could be erroneously added to a View when they should not be:
- IP Address.
- IP SLA Base Poller (and all derived types, e.g. IP SLA DHCP Poller, IP SLA DNS Poller etc).
- Network Path
- Power Supply
- BGP Peer
- ATM Virtual Channel
- Frame Relay DLCI
AWS has several regions. At the time of ENA GA release (June 2018), ENA only recognizes some of these regions (please see below for a list). If the user has one or more VMs in a non-supported region, then ENA will fail to get status, performance, storage, and network I/O data for any VMs in any region within AWS. However, it will continue to get VM inventory.
This will be fixed in a future patch. In the meantime, users should contact Entuity Support, who will be able to provide a hot fix.
If the user's Azure-based cloud has any storage accounts with no table service, then ENA will fail to get status, performance, storage, and network I/O data for any VMs within Azure. It will continue to get VM inventory.
This will be fixed in a future path. In the meantime, users should contact Entuity support, who will be able to provide a hot fix.
[The metrics ENA collects about the VMs in the Azure cloud are stored in a storage account, before being pulled back to ENA. Within the storage account, these metrics are stored in a Windows Advanced Diagnostics (WAD) table. The storage account will have a table service that provides access to any table(s) in the storage account, such as the WAD table. However, users can create storage accounts with no tables and therefore no table service. If this is the case, the above issue will occur.]