Connectrix SANnav: Services fail to start after upgrade to SANnav 2.1.1 if using port 8022 for internal SSHd server

The fe-consolidated-2 log may show the following:

The Tomcat connector configured to listen on port 8022 failed to start. The port may already be in use or the connector may be misconfigured.

Running the script "check-sannav-status.sh" shows either fe-consolidated-2 or filetransfer services restarting.

SANnav 2.1.1 requires TCP port 8022 for the fe-consolidated-2 service.

Work Around:

Prior to upgrading to SANnav 2.1.1, change the TCP port the SANnav internal SSHd server from 8022 to something else (6022 is recommended).

In SANnav 2.1.0a, this can be done using the script:

<SANnav install directory>/bin/change-internal-ssh-port.sh

If on SANnav 2.1.0, or 2.0.x, or 2.1.1:

The script can be requested by opening a case with Brocade Technical Assistance Center.

The script may not be available until the next business day following request.

Where an upgrade has been completed to SANnav 2.1.1:

Before changing the internal SSHd port, if the customer cannot wait for the script, the following may be done. Only *IF* a pre-upgrade backup is available:

1. Uninstall 2.1.1.

2. Reinstall the original version (version that the backup is from).

3. Restore backup.

4. Upgrade to 2.1.0a if that was not the original version. 

5. Run the change-internal-ssh-port.sh script to change the internal SSHd server port. 

6. Upgrade to 2.1.1

See product documentation for details on the above steps.

Resolution:

Change the SANnav internal SSHd server port prior to upgrading to SANnav 2.1.1.