Gather BCAAA debug logs

Products

• CDP Integration Server
• PacketShaper
• ProxySG Software - SGOS

Issue/Introduction

You want to collect BCAAA debug logs for analysis by a support engineer.

Resolution

Enable BCAAA debug logging when asked to do so by Symantec Technical Support. Run the debug log only long enough to collect data while the problem occurs. Once the required data has been collected, disable debugging mode. The log grows exponentially depending on the number of requests sent to BCAAA agent.

IWA debugging

1. Go to the %ProgramFiles%\Blue Coat Systems\BCAAA\ directory.
   The installation folder depends on what was chosen during the installation process.
2. Open/Edit the BCAAA.ini file in that directory.
3. Go to the bottom of the BCAAA.ini file and add the following lines:
   [Debug]
DebugLevel=0xFFFFFFFF
4. Save changes.
5. Click on Start > Run and type in "services.msc". The Windows Services opens.
6. Look for the BCAAA entry. Double click on it. Click on Stop, then Start.
7. Duplicate the issue.
8. Remove the debug entries in the BCAAA.ini file added in step 3.
9. Collect the bcaaa.log file and any other bcaaa-NNNN.log files from the Windows server. The bcaaa.log file and bcaaa-NNNN.log files are located in the %ProgramFiles%\Blue Coat Systems\BCAAA\ directory.
10. Repeat steps 5 and 6 (stop and start BCAAA).
11. Zip up the BCAAA debug log.
12. Attach the files to the case.

Windows SSO debugging

1. Go to the %ProgramFiles%\Blue Coat Systems\BCAAA\ directory
   The installation folder depends on what was chosen during the installation process.
2. Open/Edit the SSO.INI file in that directory.
3. In the [DCQSetup] section, add the following line:
   DCQDebug=1
4. Save changes.
5. Click on Start > Run and type in "services.msc". The Windows Services opens.
6. Look for the BCAAA entry. Double click on it. Click on Stop, then Start.
7. Duplicate the issue.
8. Remove the debug entry in the SSO.INI file added in step 3.
9. Collect the debug_dcq_primary_full.sso and debug_dcq_primary_inc.sso files from the Windows server. The debug_deq_primary_*.sso files are located in the %ProgramFiles%\Blue Coat Systems\BCAAA directory.
10. Repeat steps 5 and 6 (stop and start BCAAA).
11. Zip up the SSO debug files.
12. Attach the files to the case.

Novell SSO debugging

1. Go to the %ProgramFiles%\Blue Coat Systems\BCAAA\ directory
   The installation folder depends on what was chosen during the installation process.
2. Open/Edit the SSO.INI file in that directory.
3. In the [NovellSetup] section, add the following line:
   NovellDebug=1
4. Save changes.
5. Click on Start > Run and type in "services.msc". The Windows Services opens.
6. Look for the BCAAA entry. Double click on it. Click on Stop, then Start.
7. Duplicate the issue.
8. Remove the debug entry in the SSO.INI file added in step 3.
9. Collect the debug_novell_primary_full.sso and debug_novell_primary_inc.sso files from the Windows server. The debug_novell_primary_*.sso files are located in the %ProgramFiles%\Blue Coat Systems\BCAAA directory.
10. Repeat steps 5 and 6 (stop and start BCAAA).
11. Zip up the SSO debug files.
12. Attach the files to the case.

 

Note: The BCAAA service is unavailable each time it is stopped and started. This interruption in service may disrupt authentication while the BCAAA service is unavailable. Plan accordingly. If the Edge SWG (ProxySG) has both a Primary BCAAA and Alternate BCAAA configured, end-user interruption may not occur.