Reset Search
 

 

Article

KB44408 - Recommendations / Best Practices for Virtual Appliance Deployments & the logs needed for analysis/troubleshooting

« Go Back

Information

 
Last Modified Date3/20/2020 12:50 PM
Synopsis
This article outlines the recommendations & Best Practices for Virtual Appliance Deployments & the logs needed for analysis/troubleshooting.
Problem or Goal
What are the recommendations & Best Practices for Virtual Appliance Deployments & the logs needed for analysis/troubleshooting?
Cause
Solution
Deployment :
 
  1. The Storage pre-allocation type recommended is Thick Provisioning. 
  2. Please go through the “Supported Platforms Guide” to understand the Supported Virtual Platforms viz., VMWare, KVM, Hyper-V & other finer details from Pulse Secure Techpubs.
  3. Please allocate the CPUs & RAM as below,
Virtual PlatformRAM AllocationCPU Allocation
PSA-3000V8 GB2 Cores
PSA-5000V8 GB4 Cores
PSA-7000V32 GB8 Cores

       4. LSI Logic or LSI SAS (SCSI Controller) is preferred.
       5. Network Driver : VMXNET 3 / E1000e is preferred.
       6. For optimal throughput, the Physical Network interfaces of the Hypervisor should have 10 gigabit capability.
       7. The Virtual appliance should have only one source of Time Sync (Hypervisor or NTP Server, not both). This can result in a lot of side-effects.



Upgrade :
 
  1. Ensure that the software on the Virtual appliance (e.g. OVF) is upgraded in a Major Release version sequence i.e. If an appliance needs the software to be upgraded from 8.3Rx to 9.1Rx, please upgrade from 8.3Rx to 9.0Rx and then to 9.1Rx.
  2. 8.3R3 onwards the number of Software upgrades on an OVF is not limited.

Log Required for Freeze / Hang issue :
 
  1. Console Output Screenshot.
  2. Virtual Appliance (OVF) Version.
  3. ESXi version
  4. VMWare Host spec :

    CPU
    Storage
    Network
  5. Features Used (Such as Pulse L3, PSAM, Rewriter, HTML5, etc.,)
  6. Confirm if Local/SAN storage doesn’t have any issues from their corresponding logs (Provide a set of logs to us for reference if possible).
  7. Upon restart, if the VM doesn’t boot properly and gives the “Dump Diagnostics” as a Console Option, please Select it and record the Console message/output.
  8. If the restart, boots the VM just fine, collect the following logs for analysis/RCA,
 
    1. Complete Dashboard/Overview Graphs from all the nodes with timeframes of 1 day, 1 week & 1 Month (System -> Status -> Overview).
    2. PCS Logs (User/Events/Admin) \\ (System -> Log/Monitoring -> Events -> Save All Logs).
    3. System Snapshot from all the nodes (With “System Config” & “Debug Log” selected) \\ Maintenance -> Troubleshooting -> System Snapshot).
    4. System/user config :
  • Maintenance -> Import/Export -> Import/Export Configuration -> Save Config As.
  • Maintenance -> Import/Export -> Import/Export Users -> Save Config As.
        9. Analysis of any other Hypervisor (e.g. VMWare) Logs from the admin as relevant. 

Note - For any other issue, the logs would be similar to that of a Physical Appliance
Related Links
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255