Scribd
Upload
7 views2 pages

Runtime - V4debuglogs - Collection - For - HS

The document provides instructions for creating Runtime V4Debug logs for OPSWAT Hostscan on Unix and Windows platforms, detailing the file placement paths for v4debug.json. It outlines the log file creation paths for both user and service processes, as well as methods for collecting the logs manually or using the DART tool. Additionally, it explains the expected behavior regarding log deletion after DART collects the logs, noting differences between Unix and Windows systems.

Uploaded by

arihantlunkar1993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views2 pages

Runtime - V4debuglogs - Collection - For - HS

The document provides instructions for creating Runtime V4Debug logs for OPSWAT Hostscan on Unix and Windows platforms, detailing the file placement paths for v4debug.json. It outlines the log file creation paths for both user and service processes, as well as methods for collecting the logs manually or using the DART tool. Additionally, it explains the expected behavior regarding log deletion after DART collects the logs, noting differences between Unix and Windows systems.

Uploaded by

arihantlunkar1993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Collection of Runtime V4Debug Logs for OPSWAT

Steps to Create the Runtime V4 Debug Logs for Hostscan:

1. Create a file called v4debug.json at the following paths for respective


platforms:

a) Unix:

v4debug.json has to be placed at


/opt/cisco/secureclient/securefirewall posture/ v4debug.json.
If path not available, then place the file at
~/.cisco/secureclient/ securefirewallposture/v4debug.json

b) Windows:

v4debug.json has to be placed at C:\Program Files (x86)\Cisco\


Cisco Secure Client\Secure Firewall Posture\ v4debug.json.

If path not available, then place the file at %LocalAppData%/


Cisco/Cisco Secure Client/Secure Firewall Posture/v4debug.json

NOTE:

 If v4debug.json placed in SFP_Predeploy Path - Runtime V4Debug logs


are generated for both user and service process.
 If v4debug.json placed in SFP_Home Path - Runtime V4Debug logs are
generated only for user process.

2. Runtime V4Debug Log Files Creation Path:

• User process:

a) Unix: ~/.cisco/secureclient/securefirewallposture

b) Windows: %LocalAppData%/Cisco/Cisco Secure Client/Secure Firewall


Posture

• Service Process:

a) Unix: /opt/cisco/secureclient/securefirewallposture

b) Windows: C:/Program Files (x86)/Cisco/Cisco Secure Client/Secure


Firewall Posture

3. Collection of Runtime V4Debug Log Files:

• Users can manually copy the files present in the above locations for
each platform.

Cisco Confidential
• Users can also run the DART version of the same Cisco Secure Client
installed, which will collect the V4Debug logs from both the user and service
paths.

• On DART, To differentiate V4Debug logs collected during Runtime and


Wadiagnose execution, we are placing the Runtime V4Debug logs inside
directories SFPV4DebugRTUserLogs and SFPV4DebugRTServiceLogs.

4. After DART Collects the Logs:

• The V4Debug logs are expected to be deleted from the original path
since they are part of the DART bundle.

a) Unix: Deletion happens properly.

b) Windows: Only the user process-created V4Debug logs are deleted.


To delete the Runtime V4Debug logs present in the service path on Windows,
the DART process must be run with administrator privileges.

Cisco Confidential

You might also like