Troubleshooting
Problem
Guardium STAPs are showing as red or Inactive in the GUI console after upgrading a Guardium Collector from patch 704 to patch 706 . This problem has been seen using Guardium STAP version 7.0.1.27 on Windows
Resolving The Problem
Upgrading the Windows Guardium STAP to the latest available Version 7 may fix the issue.
It is always wise to make sure that the STAP agent is at the highest level for the Guardium Collector Version concerned.
At the time of writing (August 2012) the latest Guardium STAPs and Appliances are at V8.2
The following example describes one specific problem encountered with a specific version 7 STAP
In this example, having upgraded a Guardium Collector to Version 7.0p706 the STAPs showed as Inactive. The Windows STAP Version was 7.0.1.27. Upgrading the STAP to the latest available at the time ( V7.0.1.40 ) allowed the STAPs to become Active .
The Guardium STAP Version number can be seen in the configuration_file
From Windows
Start -> All Programs -> Guardium Inc -> GuardiumSTAP_700 -> Configuration_file
In this configuration file you will see the version listed towards the top of the file - for example .
[VERSION]
STAP_CLIENT_BUILD=7.0.1.40
PROTOCOL_VERSION=7.0.0
Whenever upgrading to a new STAP be sure to restart the STAP service.
On Windows this is done by:
- Control Panel -> Administrative Tools -> Services
- find the GUARDIUM_STAP service.
- Click on Restart the service
More generally - there can be other reasons why STAPs can be shown as red in the GUI console and these include the following - this may not be an exhaustive list .
- Guardium sniffer is not running ( start inspection-core as user cli may fix this )
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21495680