Lab 1: Performance Problems with the Horizon Connection Server
Objective and Tasks
In this lab, you address performance problems with the Connection Server 01:
- Log In to the Control Center
- Verify the Horizon Connection Server CPU and Memory
- View the Event Logs
- Confirm Java Heap Use in Logs
- Change the Horizon Connection Server CPU and Memory
- Verify the New Java Heap Size
- In this task, you log in to the ControlCenter to set up for the lab.
- ControlCenter.techseals.co is your domain controller DNS server and Root CA server
- Its also your primary landing desktop into your assigned vAPP
- Access the ControlCenter in the lab environment. Use these credentials:
- User name: techseals\Administrator
- Password: Pa$$w0rd
- Note: Its also your primary landing desktop into your assigned vAPP
In this task, You would use ControlCenter to access the infrastructure.
- On the ControlCenter Server
- Open Chrome Browser
- From the Favourites bar,
- Select vCenter-01a
- Login with
- [email protected]
- Pa$$w0rd
- Once logged it to the vCenter,
- From the Inventory, navigate to VMs and Templates.
- Expand vcenter-01a.techseals.co>Region01A Datacenter
- Identify the HZN-01c VM.
- Select the HZN-01c VM and click the Summary tab
- Under VM Hardware find and record the values for CPU and RAM allocated to this VM.
- Right-click HZN-01c VM in the left navigation pane and select Power > Restart Guest OS
- To Confirm the Guest OS Restart, click Yes
- Wait 2-3 minutes to allow time for the VM to reboot before continuing to the next task
-
Note
- Regular reboots can ensure that the cache is cleared and logs are easier to navigate.
-
Note
In this task, you review the Horizon 1c Event Logs using Horizon console.
- From the ControlCenter Server, open a new Chrome tab and click the Horizon 1c bookmark.
- Log in to the Horizon Connection Server Horizon 1c admin console .
- User name: administrator
- Password: Pa$$w0rd
- From the left navigation pane, expand Monitor and select Events.
- On the Events page, click the Filter icon to open the Event Filters page.
- Change the Time Period to Last Week
- From the Severity menu, select Warning and click Submit.
- Note: A list of warning messages about the Horizon Connection Server physical memory appears.
In this task, you confirm that Java Heap Use log entries appear in the Horizon 1c VM logs.
- From the ControlCenter Desktop, open an Remote Desktop > Site1
- Connect to HZN-01c VM using RDP icon in the folder
- You should automatically login as techseals\Administrator
-
Access the Connection Server Logs
- Navigate to:
- %programdata%\Omnissa\Horizon\logs
- Double-click the latest debug log file or right click and select to Edit with Notepad++
- The log file opens.
- Navigate to:
- Scroll to the bottom of the log file:
- From here, search back up through the log file, searching for the phrase java heap size
- Record the values for xmx.
- You find three entries, one for Tunnel Service, one for Tomcat, and one for MessageBus. Record the values for each service.
- Observe that the Tomcat service and the MessageBus service have been allocated the same amount of memory.
- From here, search back up through the log file, searching for the phrase java heap size
- Shut down the HZN-01c VM from the RDP session.
In this task, you correct the Horizon 1c underresourcing issue.
- Return to vSphere Client Access in the chrome browser
- Confirm that HZN-01c is powered Off. If necessary, Login:
- Username: [email protected]
- Password: Pa$$w0rd
- From the vCenter Inventory, right click the Hzn-01c and select Edit settings
- Observe the current values for CPU and Memory
- Change the CPU to 4
- Change the Memory to 10
- click OK
- Power On the VM.
In this task, you review the new Java Heap Use log entries that appear in the Horizon 1c Connection Server
- From the ControlCenter Desktop, open an Remote Desktop > Site1
- Connect to HZN-01c VM
- You should automatically login as techseals\Administrator
- Access the Connection Server Logs
- Navigate to:
- %programdata%\Omnissa\Horizon\logs
- Double-click the latest debug log file or right click and select to Edit with Notepad++
- The log file opens.
- Navigate to:
- Scroll to the bottom of the log file:
- From here, search back up through the log file, searching for the phrase java heap size
- You find three entries, one for Tunnel Service, one for Tomcat, and one for MessageBus. Record the values for each service.
- Compare the new CPU and Memory values with their original values.
- The increased value for the three services indicates an increase in memory.
- Close the RDP session to the Horizon 1c VM but leave the VM powered on. The change in memory ensures that the Horizon Connection Server VM operates within expected parameters.
0 Comments
Add your comment