Operational notes
This topic explains important aspects of Flex Appliance 7.0 operations that may not be documented elsewhere in the documentation.
The following list contains the notes and the known issues that apply for the Flex Appliance 7.0 software:
After an abrupt power cycle, the Flex Appliance Console may display a "Bad Gateway" error.
To fix this issue:
Log in to the Flex Appliance Shell.
Verify the container status using the command.
If the container is unhealthy, restart the service using the command.
Verify that the container is in a healthy state using the command.
Log in to the Flex Appliance Console.
The AutoSupport notification UMI V‑475‑600‑904 is delivered via SMTP and HTTP (SHI). If SNMP is the only configured AutoSupport delivery method, the notification will not be received, as SNMP delivery is not enabled for it.
When a VLAN tag that is created on a physical network interface is deleted, the associated network configuration is removed successfully but the corresponding VLAN tag entry may continue to be displayed in the Flex Web Console UI.
This occurs because Flex Appliance consolidates network interfaces from multiple sources, which can cause a stale VLAN entry to remain visible on the Console after deletion. This behavior is not observed when the VLAN tag is created on a bonded interface.
Wait for up to 15 minutes and refresh the Flex Appliance Console. The stale VLAN tag entry will be automatically removed.
When the appliance turns on, you may receive the following false alerts if the services take longer than usual to start:
V-475-130-30007: The metrics-node service is not in an optimal state.
V-475-130-30009: The metrics-storage service is not in an optimal state.
If you have not received a second alert after four hours, you can safely ignore these alerts.
If you have more than 10 VLAN tags configured with an IPv6 network, instances may not start cleanly. To avoid this issue, do not configure more than 10 VLAN tags with an IPv6 network.
Flex Appliance does not currently restrict you from adding a local user and a remote user with the same username. However, upgrade issues can occur if you do. Do not use duplicate usernames across local and remote users.
If a server communicates with the appliance with a domain name that is not in the appliance
hostsfile, the server name is not masked in the logs.If you generate a Data Collect log package with data masking enabled, the
private_mapfile that is included uses the same key value for multiple entries.Alerts are not currently sent for the metrics that can be set with the set alerts hardware-threshold command.
During a firmware update, an issue can occur with the storage shelf controller that causes an update failure message to appear. If you see a failure message, it may have appeared in error, and the update may still have worked. Run the following command to confirm the firmware version:
show hardware-health primaryshelf component=controller
When you install application add-ons on an instance, the Flex Appliance Console lets you select different versions of the same OST plug-in. However, this configuration is not supported, and if you select more than one version of the same plug-in, the Install add-ons page shows duplicate entries. Only install one version of each OST plug-in on an instance. If you need to change the version of an OST plug-in that is already installed, first uninstall it, and then install the new version.