Additional Scripts
You can re-start, stop, and start the SANnav Management Portal and SANnav Global View severs with additional scripts. You can also run a script to replace self-signed certificates with third-party signed certificates. Run these scripts only if required.
The following scripts apply to both SANnav Management Portal and SANnav Global View and, for SANnav Management Portal, apply to both single-node and multi-node installations.
Restarting the Server
To stop the currently running SANnav server and restart the SANnav application, perform the following:
Go to the <install_HOME>/bin folder and run the following script:
./restart-server.sh
Stopping the Server
To stop the currently running SANnav server and re-start the server, perform the following:
Go to the <install_HOME>/bin folder and run the following script:
./stop-server.sh
Starting the Server
To start the stopped SANnav server, perform the following:
Go to the <install_HOME>/bin folder and run the following script:
./start-server.sh
Checking the Server Health
Once the installation is complete, you can check the health of the SANnav server anytime. If any of the services is down, it will be listed.
To check the health of the server, perform the following:
Go to <install_HOME>/bin/diag folder and run the following script:
./check-server-status.sh
Note: If any service is found down while checking server health status, it will be automatically started by system-monitor within 20 minutes.
The following is sample output of a healthy server.
-bash-4.2# sh ./check-server-status.sh
SANnav server is healthy. All the services are currently in running state.
The following is sample output of an unhealthy server.
-bash-4.2# sh ./check-server-status.sh
Following services are currently down or starting
filters-middleware
topology-middleware
SANnav Disk Usage Alert monitors the disk space used for every ten minutes. There are three threshold levels: 70%, 80%, and 90%. An event is sent when the threshold levels exceed or drop below the defined level. The following is the list of event severity:
• Warning - 70%
• Error - 80%
• Critical - 90%
Changing the Self-Signed Certificates for Client and Server Communication
You can replace the self-signed certificates with third-party signed certificates by performing the following:
Make sure that the SSL certificate and key files are copied to this host or VM.
Go to the <install_HOME>/bin folder and run the following script:
./replace-server-cert.sh
When you run this script, SANnav is automatically restarted for the new certificates to take effect. After the server is back up, you must rediscover or unmonitor and then monitor all switches that are registered for telemetry data; otherwise, the new certificates do not take effect.
Changing the Self-Signed Certificates for the Kafka Brokers
By default, when SANnav is installed, self-signed certificates for Kafka are generated; these certificates are valid for two years. You can replace the self-signed certificates with third-party signed certificates by performing the following:
Ensure that the following requirements are met before you run the script:
• The common name (CN) of the certificate must match the fully qualified domain name (FQDN) of the host.
• If you have root and intermediate CA certificates, they must be chained into a single certificate.
Go to the <install_HOME>/bin folder and run the following script:
./replace-kafka-certificates.sh
When you run this script, SANnav is automatically restarted for the new certificates to take effect. After the server is back up, you must rediscover or unmonitor and then monitor all switches that are registered for telemetry data; otherwise, the new certificates do not take effect.
Parent topic