Version Information

From Swivel Knowledgebase
Revision as of 12:52, 11 May 2017 by Admin (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Overview

This article can help you determine the version of Swivel Core and the underlying Appliance Version if you use an appliance. To see Swivel version details see Versions FAQ and also appliance type see Appliance General FAQ.


Prerequisites

  • Swivel 3.x
  • Appliance version 2.x with CMI


Version Information via the CMI

Login to the appliance using the PuTTY How To Guide.

From the main menu, select Advanced Options -> Version Information. You will be presented with the following information:

Swivel Maintenance (c) 2012                                             Single

Appliance and software versions

CMI             : 0.12
CMI Backup      : 0.16
CMI Restore     : 0.16
CMI Certs.      : 0.10
CMI Diags.      : 0.6
Appliance Build : 2.0.14
Swivel Version  : 3.9.7.996
Tomcat Version  : 5.5.28
Java Version    : 1.6.0_18
Webmin Version  : 1.510

Press Return to continue
  • Swivel Version is the version of the Swivel Core software installed in Webapps;
  • Appliance Build is the appliance version.


Version information from the command line

Check the login message from the console.

run the following command

 grep APPLIANCE_VERS /etc/pinsafe.conf|cut -d\= -f2

If not, inspect the /etc/pinsafe.conf file manually.

Other components can be found from the following commands on older appliances:

Apache Tomcat:

 ls /usr/local|grep apache|cut -d\- -f3

Java:

 ls /usr/java|grep jre|cut -d\e -f2

MySQL (if used):

 mysql --version|cut -d\  -f6|cut -d\, -f1

Webmin:

 cat /etc/webmin/version


What appliance do I have? Am I running standalone, Active/Passive, Active/Active, or a DR?

A). A lot of installs appear to be the same from the external view, and may require command line access to determine the type.

Standalone: Running on its own using the internal Swivel data store. A Standalone appliance may be Hardware or VMware.

Active/Passive: These are only hardware appliances and a VMware is not available. HA pair with a cross over cable between the secondary interface, it uses a Virtual IP address that switches from the Active machine to the standby machine when it is fails over and file replication to share data between systems, using a process called drbd. In this configuration there is only one Swivel instance to configure, the entire file system including the Swivel application automatically fails over. This system may not scale to more than two Swivel servers. To see if this system is running enter:

 cat /proc/drbd

Expected Results:

primary

 drbd driver loaded OK; device status:
 version: 0.7.14 (api:77/proto:74)
 SVN Revision: 1989 build by buildcentos@build-i386, 2006-03-18 19:03:54
  0: cs:Connected st:Primary/Secondary ld:Consistent
     ns:8492552 nr:22716 dw:8515268 dr:284982 al:106 bm:2286 lo:0 pe:0 ua:0 ap:0

secondary

 drbd driver loaded OK; device status:
 version: 0.7.14 (api:77/proto:74)
 SVN Revision: 1989 build by buildcentos@build-i386, 2006-03-18 19:03:54
  0: cs:Connected st:Secondary/Primary ld:Consistent
     ns:22716 nr:10565672 dw:10588388 dr:36158 al:20 bm:128 lo:0 pe:0 ua:0 ap:0

Active/Active: These may be hardware or VMware. Each Swivel appliance is able to receive authentication requests regardless of the state of the other. On the appliance this will be used with a MySQL database, although it would be possible to use another external Database. Using the Virtual IP address is optional. To verify it is in active/active mode, check from the Swivel Administration console to see if the MySQL database is being used and mode is synchronised.

DR or Slave: These may be hardware or VMWare. Here each Swivel appliance is able to receive authentication requests regardless of the state of the other. The appliance may appear to be Active/Passive if the deployment scenario directs all authentication requests to one Swivel appliance, although it is an Active/Active deployment. On the appliance a MySQL database is used, although it would be possible to use another external Database. To verify it is in DR or slave mode and not an Active server, check from the Swivel Administration console to see if the MySQL database is being used and mode is slave.


Software only installation - Swivel Core

When you visit the Swivel Administration Console on port 8080, in the top right hand corner you will see the version number of the Swivel Core. Note that this is not the version of the underlying appliance.

Core version.PNG