Are you facing issues collecting a Supportsave from a switch using SANnav? This guide explains why the process may fail and how to resolve it. The most common cause is an SSH port conflict between SANnav and the Linux server. We’ll show you how to check the current port settings, update SANnav’s SSH configuration, and verify the changes. By the end of this video, you’ll be able to run Supportsave without errors. Perfect for administrators managing Brocade SAN environments.
Hi everyone! Attempting to collect a Supportsave from a switch using SANnav may result in a failed status. In this video, we will walk through the steps to troubleshoot and resolve this issue. There may be a conflict between SANnav SSH port and the Linux server SSH port.
In order to check this, go to the conf directory in SANnav home. and "grep" this value. You can see that SANnav is using SSH port 22. Next we need to determine the value currently configured on the Linux SSH server. To check this, navigate to the SSHD config file in "/etc/ssh" directory. If this is also port 22 or commented out, then Linux is using port 22 as well. If both the SANnav SSH and Linux server SSH port are using port 22, then the switch Supprotsave will fail due to the conflict.
To free port 22 for SANnav Management Portal, navigate to SANnav home bin directory and run the script: "manage-sannac-configurations.sh". Choose option 6. Hit enter until you get the following question. Update SANnav Management Portal SSH server. Note that, whatever port you select here must be available and allowed in the firewall.
There's also a note: In order to use the SANnav Management Port internal SSH server on a custom port for downloading Fabric OS two switches and chassis, the Fabric OS version must be v8.2.2 or higher. In other words, for switches running Fabric OS versions earlier than 8.2.2. If you change to a port number other than 22, you must always use an external FTP, SCP, or SFTP server for switch Supportsave and firmware download functionality. Here, let us enter port 6022.
This will restart the file transfer services on SANnav Management Portal. Press <escape>, hit <enter>. In order to verify the changes, navigate to SANnav "home/conf" folder. Check the file "server.properties | Grep dcm.ssh.server.port". Now you can see that the SANnav SSH port value is changed to 6022.
You can also verify the Linux SSH port. The port 22 is in use by Linux SSH server. So now we have changed the SANnav SSH port and the Linux SSH port, you can run switch Supportsave without any conflict.
Thank you for watching.
