HTTP/HTTPS Ports

GigaVUE-FM uses the standard HTTP configuration shown in the following figure:

 

In this release, you can change the HTTPS port for GigaVUE-FM but the HTTP port is hard-coded to 80. As long as HTTP redirect to HTTPS is enabled (the default), connections to the fixed HTTP port of 80 will redirect to whatever the configured HTTPS port is.

Make Sure the Web Server is Enabled on Nodes to be Managed

GigaVUE-FM can only discover and manage nodes with their web servers enabled and operating on the default HTTP port of 80. Both G and H Series nodes have their web servers enabled by default. However, if you disabled a node’s web server or changed its HTTP port, you will need to restore the settings before GigaVUE-FM can manage it.

GigaVUE-FM can manage nodes operating on custom HTTPS ports. Incoming HTTP connections redirect to the custom HTTPS port.

The show web_server and show web output listed below summarizes the necessary HTTP settings for G and H Series GigaVUE nodes managed by GigaVUE-FM. The items shown in red are required settings.

G Series

G Series>show web_server
Admin      : 1 (Must be enabled)
Operation  : 1
HTTP port  : 80 (Must remain at its default setting of 80)
HTTPS port : 8000 (Can be set to any custom value; HTTP redirects here)
Timeout    : 5 (minutes)
HTTPS Cert : Default Certificate

H Series

H Series (config) # show web
Web-based management console enabled: yes
HTTP enabled:           yes (Must be enabled)
HTTP port:              80 (Must remain at its default setting of 80)
HTTP redirect to HTTPS: yes (Must remain enabled)
HTTPS enabled:          yes (Must remain enabled)
HTTPS port:             443 (Can be set to any custom value; HTTP                              redirects here)
Listen enabled:         yes
No Listen Interfaces.
Inactivity timeout:     15 min
Session timeout:        2 hr 30 min
Session renewal:        30 min
Web proxy enabled: no