Troubleshooting

This section provides the information needed to troubleshoot GigaVUE‑FM integration with OpenStack. Refer to

Refer to the following sections for details:

■

OpenStack Connection Failed

■

Handshake Alert: unrecognized_name

■

GigaVUE V SeriesNode or UCT-V Controller is Unreachable

OpenStack Connection Failed

The connFailed state indicates that the OpenStack connection has failed. Check the following troubleshoot tips to restore the connection:

■

Verify if GigaVUE‑FM is able to reach the OpenStack cloud controller.

■

Check if the OpenStack cloud controller is DNS resolvable from GigaVUE‑FM.

■

Verify if the region name provided while launching the instance is accurate.

■

Ensure that all the security group rules required for communication between GigaVUE‑FM and OpenStack cloud controller OR GigaVUE‑FM and DNS server are accurately setup.

■

Check if the Compute Servers that the nova API returns are reachable from GigaVUE‑FM. Refer to Handshake Alert: unrecognized_name.

Handshake Alert: unrecognized_name

When setting up the OpenStack connection in GigaVUE‑FM, the GigaVUE‑FM logs might show a handshake alert: unrecognized_name error. This error is related to a Server Name Indication (SNI) error. Starting with Java 7, the JDK does not ignore the unrecognized name warning. To resolve this issue, perform either of the following:

■

Fix the configuration on the server where the error is occurring.

■

Ignore the warning on the client side (GigaVUE‑FM server) by using the Java system property --Djsse.enableSNIExtension=false while launching GigaVUE‑FM.

Contact support for information on how to use the Java system property. However, this is not recommended for security reasons.

GigaVUE V SeriesNode or UCT-V Controller is Unreachable

If GigaVUE V Series node or UCT-V Controller is unreachable, verify the following:

■

The correct version of the image is uploaded.

■

The network is reachable.