Sputnik software (server and firmware) can be updated by locating the install script "scc_install.pl", changing to its directory, and typing the following commands (as root):

[root@server home]# cd /root

[root@server root]# rm scc_install.pl

[root@server root]# wget http://www.sputnik.com/scc_install.pl

[root@server root]# chmod +x scc_install.pl

[root@server root]# /sbin/service httpd stop

[root@server root]# /sbin/service scc_mgmtd stop

[root@server root]# /sbin/service jabberd stop

[root@server root]# ./scc_install.pl --lsk='LSK_STRING' --yum update "Sputnik*"

...where LSK_STRING is your Sputnik Control Center license key. You can retrieve this value from the database with the following command:

# su - postgres -c "echo \"select kconfig_value from kconfig where kconfig_key='lsk'\" | psql VSITE"

...where VSITE is the name of your Sputnik Control Center virtual site.

[root@server root]# /sbin/service jabberd start

[root@server root]# /sbin/service scc_mgmtd start

[root@server root]# /sbin/service httpd start

Verify that the site management process is running:

# ps aux | grep scc

(look for "running" in parentheses after your vsite name)

When you see that the state is running, continue by starting the web server:

[root@server root]# /sbin/service httpd start

Afterward, you may want to verify that the site management process is still active (see ps command above) and that the logs do not show strange errors. For example, check out the tail end of the log:

# tail -50 /var/log/messages

And finally, log into your SCC admin UI and make sure that the checkpoints flag shows a number < 300 seconds.

To update non-Sputnik packages on your server, use up2date or yum. To update both Sputnik and non-Sputnik packages, you can use the following command in place of the second line above:

[root@server root]# ./scc_install.pl --yum update

After the server software is updated, you can go to the admin UI and remotely update AP firmware from each unit's Edit Setting