The ProxySG appliance Management Console looks different when loaded via Director.
For example, the tab order is different (Configuration | Maintenance | Statistics instead of Maintenance | Configuration | Statistics) and the Visual Policy Manager does not load (you receive the error "Errors Occurred while retrieving settings from ProxySG Appliance”).
When the ProxySG appliance is added to Director, four JAR files are downloaded to the Director disk as sg-jars:
These files are saved in a directory in /local/sg-jars/ and named in the formar "r<build number>”.
sh-3.2# ls -l /local/sg-jars/ drwxr-xr-x 2 admin root 4096 Mar 25 13:21 default drwxr-xr-x 2 admin priv15 4096 Aug 9 16:02 r101423 drwxr-xr-x 2 admin priv15 4096 Aug 12 07:52 r88916
The above directories are for the “default", build 101423, and build 88916. These directories contain their respective JAR caches.
sh-3.2# ls -l /local/sg-jars/r88916/ -rw-r--r-- 1 admin priv15 1685300 Aug 12 07:52 VPM.jar -rw-r--r-- 1 admin priv15 3147296 Aug 12 07:52 applets.jar -rw-r--r-- 1 admin priv15 125719 Aug 12 07:52 sgcommon.jar -rw-r--r-- 1 admin priv15 1602384 Aug 12 07:52 vpmhelp.jar
When the “configure” option is selected for a particular ProxySG appliance, the corresponding build’s JAR files are given to the client’s Java Runtime Environment. These files are not stored in Java cache; thus, clearing the cache of browser and Java files won’t clear them. Their default location in Windows XP is C:\Documents and Settings\<User>\bluecoat\SgJars\.
JAR files for each build are downloaded when a ProxySG appliance with that build is selected for “configure” and the directory naming follows the “r<build number>” format. To troubleshoot ProxySG Management Console issues:
Navigate to this location and delete all the directories that start with “r”.
Select the “configure” option in Director to download the specific build files again. If this does not resolve the issue, the issue is that Director does not have the SgJar caches for the specific build. As a result, Director passes the contents of the “default” directory to the client. These default files might not be enough for loading an SGOS 6.x interface.
If performing the Troubleshooting steps did not resolve the issue, you must manually download the SGJars files from one of the devices with that build number. Issue the following command: download sg-jar https://<ProxySG_IP_address>:8082/Secure/Local/console/r<build_number>
This command will re-populate the /local/sg-jars/ r<build_number> directory with the corresponding JAR files. This process is automated, which means that Director is supposed to download the files when the “configure” option in selected.
Note: Checking the /var/log/messages could provide an insight to any download issues: tail –f /var/log/messages
Note: For a specific customer, the issue was caused as they changed the “web configuration port” from 8082 to 8081 as they were only using HTTP-Console. They disabled the HTTPS-Console on port 8082 on the ProxySG appliance. When Director tried to download the SGJar files, its expected the connection to be SSL-based (HTTPS). So the connection was initated towards Proxy-IP:8081 starting with a “client hello”. Since the ProxySG was expecting a “GET”, it closed the connection. Due to this issue the specific build’s files were not present in Director /local/sg-jars location. Director was always giving back the contents of “default” directory which is not capable of loading the SGOS 6.x interface.
Imported Document ID: 000008895
Subscribing will provide email updates when this Article is updated. Login is required.