Configuring and Monitoring Oracle VDI

Transcription

1 Cnfiguring and Mnitring Oracle VDI eg Enterprise v5.6

2 Restricted Rights Legend The infrmatin cntained in this dcument is cnfidential and subject t change withut ntice. N part f this dcument may be reprduced r disclsed t thers withut the prir permissin f eg Innvatins, Inc. eg Innvatins, Inc. makes n warranty f any kind with regard t the sftware and dcumentatin, including, but nt limited t, the implied warranties f merchantability and fitness fr a particular purpse. Trademarks Micrsft Windws, Windws NT, Windws 2000, Windws 2003 and Windws 2008 are either registered trademarks r trademarks f Micrsft Crpratin in United States and/r ther cuntries. The names f actual cmpanies and prducts mentined herein may be the trademarks f their respective wners. Cpyright 2012 eg Innvatins, Inc. All rights reserved.

3 Table f Cntents CONFIGURING AND MONITORING THE ORACLE VIRTUALBOX CHALLENGES IN MONITORING THE ORACLE VIRTUALBOX EG'S SOLUTION TO ORACLE VIRTUALBOX MONITORING AGENT DEPLOYMENT MODELS The Agent-based Mnitring Apprach The Agentless Mnitring Apprach PRE-REQUISITES FOR MONITORING THE ORACLE VIRTUALBOX Pre-requisites fr Mnitring the Oracle VirtualBx in an Agent-based Manner General Pre-requisites Pre-requisites fr Aut-Discvering VMs and Obtaining their "Outside View" Pre-requisites fr Obtaining the "Inside View" f Windws VMs, using the eg VM Agent Pre-requisites fr Obtaining the "Inside View" f VMs, withut using the eg VM Agent Pre-requisites fr Mnitring the Oracle VirtualBx in an Agentless Manner General Pre-requisites Pre-requisites fr Aut-Discvering VMs and Obtaining their "Outside View" Pre-requisites fr Obtaining the "Inside View" f Windws VMs, using the eg VM Agent Pre-requisites fr Obtaining the "Inside View" f VMs, withut using the eg VM Agent CONFIGURING THE EG AGENT TO OBTAIN THE INSIDE VIEW OF WINDOWS VMS, USING THE EG VM AGENT Cmmunicatin between the eg Agent and the eg VM Agent Licensing f the eg VM Agent Benefits f the eg VM Agent CONFIGURING WINDOWS VIRTUAL MACHINES TO SUPPORT THE EG AGENT S INSIDE VIEW WITHOUT THE EG VM AGENT Enabling ADMIN$ Share Access n Windws Virtual Guests Enabling ADMIN$ Share Access n Windws 2000/2003 VMs Enabling ADMIN$ Share Access n Windws 2008 VMs Cnfiguring Windws Firewalls t Allw File and Print Sharing ADMINISTERING THE EG MANAGER TO MONITOR THE ORACLE VIRTUALBOX CONFIGURING USERS FOR VM MONITORING MONITORING THE ORACLE VIRTUALBOX TROUBLESHOOTING THE FAILURE OF THE EG REMOTE AGENT TO CONNECT TO OR REPORT MEASURES FOR LINUX GUESTS CONFIGURING AND MONITORING THE ORACLE VDI BROKER PRE-REQUISITES FOR MONITORING THE ORACLE VDI BROKER IN AN AGENT-BASED MANNER PRE-REQUISITES FOR MONITORING THE ORACLE VDI BROKER IN AN AGENTLESS MANNER ADMINISTERING THE EG MANAGER TO MONITOR AN ORACLE VDI BROKER MONITORING THE ORACLE VDI BROKER CONCLUSION...41

4 Table f Figures Figure 1.1: Architecture f the Oracle Virtual Desktp Infrastructure...2 Figure 1.2: Architecture f an Oracle VirtualBx...3 Figure 1.3: The layer mdel f Oracle VirtualBx...4 Figure 1.4: Agent-based mnitring f the Oracle VirtualBx...5 Figure 1.5: The Agentless apprach t mnitring the Oracle VirtualBx...6 Figure 1.6: Welcme screen f the eg VM Agent installatin wizard...11 Figure 1.7: Accepting the license agreement...11 Figure 1.8: Specifying the install directry f the eg VM Agent...12 Figure 1.9: Specifying the VM agent prt...12 Figure 1.10: A summary f yur specificatins...13 Figure 1.11: Finishing the installatin...13 Figure 1.12: The ADMIN$ share des nt exist...15 Figure 1.13: Admin$ share pre-exists...16 Figure 1.14: Creating the ADMIN$ share...16 Figure 1.15: Clicking the Add buttn...17 Figure 1.16: Selecting the administrative user t whm access rights are t be granted...17 Figure 1.17: The administratr accunt granted access permissins...18 Figure 1.18: Defining the Security settings fr the ADMIN$ share...18 Figure 1.19: Adding the administratr accunt...19 Figure 1.20: The Administratr accunt in the Security list...19 Figure 1.21: Selecting the Share ptin frm the shrtcut menu...20 Figure 1.22: Cicking n Advanced Sharing...21 Figure 1.23: Enabling the ADMIN$ share...21 Figure 1.24: Clicking n the Add buttn...22 Figure 1.25: Allwing a dmain administratr t access the flder...22 Figure 1.26: Allwing full access t the lcal/dmain administratr...23 Figure 1.27: Applying the changes...23 Figure 1.28: Selecting the guest OS...24 Figure 1.29: Opening the Windws Firewall...25 Figure 1.30: The General tab f the Windws Firewall dialg bx...25 Figure 1.31: Deselecting the 'Dn't allw exceptins' check bx...26 Figure 1.32: Enabling 'File and Printer Sharing'...26 Figure 1.33: Opening prts...27 Figure 1.34: Adding the Oracle VirtualBx cmpnent...27 Figure 1.35: List f Uncnfigured tests fr the Oracle VirtualBx...28 Figure 1.36: Cnfiguring the VM Status test...28 Figure 1.37: The VM user cnfiguratin page...32 Figure 1.38: Adding anther user...32 Figure 1.39: Assciating a single dmain with different admin users...33 Figure 2.1: Adding the Oracle VDI Brker in an agentless apprach...39 Figure 2.2: Adding the Oracle VDI Brker in an agent based apprach...39 Figure 2.3: List f Uncnfigured tests fr the Oracle VDI Brker...40 Figure 2.4: Cnfiguring the VDI Database Status test...40

5 Chapter 1 Cnfiguring and Mnitring the Oracle VirtualBx Oracle VDI (Virtual Desktp Infrastructure) prvides desktp virtualizatin t replace persnal cmputers with virtual machines (VMs) n a server. Users can access these VMs thugh any RDP client, r thrugh the web via Sun Secure Glbal Desktp (SGD). Oracle Virtual Desktp Infrastructure is made up f fur main cmpnents: virtualizatin platfrm, sessin management (Oracle VDI Cre), desktp access clients, and strage. Figure 1.1: Architecture f the Oracle Virtual Desktp Infrastructure The basis fr the Oracle Virtual Desktp Infrastructure architecture is the virtualizatin platfrm. In additin t creating and string virtual machines, the virtualizatin platfrm ffers the cre functinality needed fr virtual desktp management such as starting, stpping, and snapshtting virtual machines. Oracle Virtual Desktp Infrastructure 3.2 supprts Oracle VM VirtualBx (the Oracle VDI Hypervisr), VMware vcenter, Micrsft Hyper-V, and Micrsft Remte Desktp Services as virtualizatin platfrms. Oracle VM VirtualBx is crss-platfrm x86 virtualizatin sftware that extends the pwer f yur existing cmputers t run multiple perating systems, n the same hardware, at the same time, and alngside yur existing applicatins. 2

6 Oracle VM VirtualBx includes a hypervisr fr the hst platfrm, an applicatin prgramming interface (API) and sftware develpment kit (SDK) fr managing guest virtual machines, a cmmand-line tl fr managing guests lcally, a web service fr remte management f guests, a wizard-style graphical tl t manage guests, a graphical cnsle fr displaying guest applicatins n the lcal hst, and a built-in Remte Desktp Prtcl (RDP) server that prvides cmplete access t a guest frm a remte client. At the cre is the hypervisr, implemented as a ring 0 (privileged) kernel service. Figure 1.2 shws the relatinships between all f these cmpnents. Figure 1.2: Architecture f an Oracle VirtualBx The kernel service cnsists f a device driver named vbxsrv, which is respnsible fr tasks such as allcating physical memry fr the guest virtual machine, and several ladable hypervisr mdules fr things like saving and restring the guest prcess cntext when a hst interrupt ccurs, turning cntrl ver t the guest OS t begin executin, and deciding when VT-x r AMD-V events need t be handled. The hypervisr des nt get invlved with the details f the guest perating system scheduling. Instead, thse tasks are handled cmpletely by the guest during its executin. The entire guest is run as a single prcess n the hst system and will run nly when scheduled by the hst. If they are present, an administratr can use hst resurce cntrls such as scheduling classes and CPU caps r reservatins t give very predictable executin f the guest machine. Additinal device drivers will be present t allw the guest machine access t ther hst resurces such as disks, netwrk cntrllers, and audi and USB devices. In reality, the hypervisr actually des little wrk. Rather, mst f the interesting wrk in running the guest machine is dne in the guest prcess. Thus the hst's resurce cntrls and scheduling methds can be used t cntrl the guest machine behavir. In additin t the kernel mdules, several prcesses n the hst are used t supprt running guests. All f these prcesses are started autmatically when needed. 1.1 Challenges in Mnitring the Oracle VirtualBx What makes mnitring an Oracle VDI infrastructure a challenge is the large number f virtual desktps that will typically be cnfigured n the VirtualBxes and the large number f users t 3

7 the desktps. While it can be very difficult t keep track f which user is accessing which desktp n which VirtualBx, the live and autmatic migratin f desktps t ther VirtualBxes (if any) in the envirnment nly cmpunds the prblem. T make matters wrse, the users t the VDI service demand frm the virtual desktps the same quality f service that they are used t receiving frm their physical desktps. This means, quick access, uninterrupted cnnectivity, and stable peratins will be the criteria n which the user experience with the VDI service will be judged. Nn-availability f a desktp when a user needs it, r slwdwns in desktp peratins caused by a resurce cntentin at the desktplevel r at the hst-level may result in a deluge f user cmplaints and a bevy f dissatisfied users. T avid this, service desk shuld be able t: Cntinuusly mnitr the user activity t the virtual desktps perating n a VirtualBx; Knw which user accessed the desktp n which VirtualBx at what time; Track the pwered-n state f desktps; Study the resurce usage patterns f the virtual desktps t nail the rt-cause f resurce cntentins - is it wing t a resurce-hungry desktp? r a resurce-starved hst?; Prmptly alert users t ptential resurce drains n desktps r a sudden change in the desktp state, much befre users ntice the difference! 1.2 eg's Slutin t Oracle VirtualBx Mnitring The specialized Oracle VirtualBx mnitring mdel addresses all the requirements utlined abve and mre! This 100%, web-based slutin emplys a single eg agent t perfrm detailed 'In-N-Out' mnitring f the virtual desktps perating n an Oracle VirtualBx. Figure 1.3: The layer mdel f Oracle VirtualBx The metrics cllected by this eg agent reprt n the percentage f the Oracle VirtualBx hst's resurces that each f the VMs n the server are using - i.e., the relative lading f the guest VMs. This represents the view f hw a guest VM and its applicatins are ding - frm the utside - i.e., frm utside the guest VM. In additin, the eg agent als cnnects t each guest VM that is currently pwered n and determines the guest OS versin, the name(s) f the users wh are lgged n, the applicatins they are accessing, and the resurce usage f the applicatins running inside the 4

8 guest (as seen frm within the guest perating system). This represents the view frm within the guest perating system - i.e., the inside view. In additin, the same agent can als track the critical prcesses running n the Oracle VirtualBx hst and their resurce usage, the netwrk cnnectin t the hst, and the TCP cnnectivity f the hst, and thus reprt n the verall health f the hst. The agent is als capable f capturing and reprting n the live migratin f desktps frm ne VirtualBx t anther. Based n the mnitring apprach chsen, yu can deply this eg agent n the VirtualBx itself r n any remte Windws/Linux/Slaris hst in the envirnment. Sectin 1.3 discusses bth these deplyment mdels in detail. 1.3 Agent Deplyment Mdels eg Enterprise allws administratrs the flexibility t chse between the agent-based and agentless appraches t mnitring the Oracle VirtualBx The Agent-based Mnitring Apprach The agent-based apprach requires that the eg agent be installed n the hst perating system f the VirtualBx. Since Oracle VDI cmes bundled with an Oracle VirtualBx that runs an Oracle Slaris perating system, yu need t install a Slaris eg agent n the hst. T knw hw t install an eg agent n Slaris, refer t the eg Installatin Guide. Figure 1.4: Agent-based mnitring f the Oracle VirtualBx This agent shuld then be cnfigured t cmmunicate with the Oracle VirtualBx via SSH and run privileged Virtual Desktp Access (VDA) cmmands n the Oracle VirtualBx t determine the health f the hst, t discver the IP address and perating system f each f the guests n the hst, and t reprt hw each guest has utilized the hst's physical resurces (i.e., utside view). Fr cnnecting t the target Oracle VirtualBx via SSH, the eg agent has t be cnfigured with the credentials f a user with the required privileges. Als, t enable the eg agent t run VDA cmmands n the hst, a sud package has t be installed n the VirtualBx. T knw hw, refer t Sectin 1.4 belw. Once the guests are discvered, the eg agent remtely cmmunicates with each guest using SSH/WMI (depending upn the perating system f the guest) t btain the "inside view" f every guest. T establish this remte cnnectin with Windws VMs in particular, eg Enterprise requires that the eg agent be cnfigured with dmain administratr privileges. In 5

9 high-security envirnments, where the IT staff might have reservatins abut expsing the credentials f their dmain administratrs, this apprach t extracting inside view metrics might nt be preferred. In such envirnments therefre, eg Enterprise prvides administratrs the ptin t deply a piece f sftware called the eg VM Agent n every Windws VM, which allws the eg agent n the service cnsle t cllect inside view metrics frm the VMs withut dmain administratr rights. Refer t Sectin 1.5 fr mre details n the eg VM Agent The Agentless Mnitring Apprach The agentless apprach t mnitring the Oracle VirtualBx invlves the fllwing: Deplying the eg agent n a remte system running Micrsft Windws r Linux r Slaris; Cnfiguring the remte eg agent t cmmunicate with the target VirtualBx via SSH; Cnfiguring the remte eg agent t run Virtual Desktp Access (VDA) cmmands n the VirtualBx t perfrm guest discvery and t cllect hst-level and 'utside view' metrics; t run these cmmands, yu need t install a sud package n the VirtualBx - refer t Sectin 1.4 t knw hw. Cnfiguring the remte eg agent t cllect perfrmance metrics frm each f the guest VMs cnfigured n the VirtualBx using SSH/WMI; by default, the eg agent uses SSH/WMI (depending upn the virtual OS t be mnitred) t cmmunicate remtely with the virtual machines n the VirtualBx (see Figure 1.5) and cllect metrics. T establish this remte cnnectin with Windws VMs in particular, eg Enterprise requires that the eg agent be cnfigured with dmain administratr privileges. In high-security envirnments, where the IT staff might have reservatins abut expsing the credentials f their dmain administratrs, this apprach t extracting inside view metrics might nt be preferred. In such envirnments therefre, eg Enterprise prvides administratrs the ptin t deply a piece f sftware called the eg VM Agent n every Windws VM, which allws the eg agent t cllect inside view metrics frm the VMs withut dmain administratr rights. Refer t Sectin 1.5 fr mre details n the eg VM Agent. Figure 1.5: The Agentless apprach t mnitring the Oracle VirtualBx Regardless f the mnitring apprach chsen, certain pre-requisites need t be fulfilled befre attempting t mnitr the Oracle VirtualBx. Sectin 1.4 belw discusses these prerequisites. 6

10 1.4 Pre-requisites fr Mnitring the Oracle VirtualBx This sectin details the pre-requisites that need t be fulfilled fr mnitring an Oracle VirtualBx in an agent-based and an agentless manner Pre-requisites fr Mnitring the Oracle VirtualBx in an Agentbased Manner General Pre-requisites Enable the eg agent t cmmunicate with the eg manager prt (default: 7077) Pre-requisites fr Aut-Discvering VMs and Obtaining their "Outside View" Ensure that the eg agent is able t cnnect t the target VirtualBx via SSH. Make sure that the SSH prt (default: 22) is pened fr cmmunicatin between the eg agent and the Oracle VirtualBx. Cnfigure all the tests that the eg agent executes with the name and passwrd f a user wh has the right t access the target Oracle VirtualBx via SSH. T enable the eg agent t run VDA cmmands n the VirtualBx, install the sud package n the VirtualBx. T install this package, d the fllwing: Lgin t the Slaris system hsting the VirtualBx as a rt user. T dwnlad the sud package, cnnect t the URL: If the Slaris prcessr is Intel based, dwnlad the file TCMsud i386.pkg.gz frm the web site mentined abve. On the ther hand, if the Slaris hst uses a SPARC prcessr instead, dwnlad the file TCMsud sparc.pkg.gz frm the web site. Dwnlad the chsen file t any lcatin n the VirtualBx hst (say, /tmp). Frm the Slaris prmpt, switch t the directry hsting the dwnladed package and unzip the cmpressed package using the fllwing cmmand: gunzip <package_name> Fr instance: gunzip TCMsud sparc.pkg.gz Then, install the package by issuing the fllwing cmmand at the prmpt: pkgadd -d <package name> Fr instance: pkgadd d TCMsud sparc.pkg Once installatin is cmplete, yu will find that the package is installed in the /usr/lcal/ flder n the Slaris hst. All the tests run by the eg agent shuld be cnfigured with the full path t the install directry f the sud package; 7

11 Pre-requisites fr Obtaining the "Inside View" f Windws VMs, using the eg VM Agent Install the eg VM Agent n each Windws VM. Fr details n hw t install the eg VM Agent, refer t Sectin 1.5 f this dcument. Enable the eg agent t cmmunicate with the prt at which the eg VM Agent listens (default prt: 60001). Set the INSIDE VIEW USING flag fr all the inside view tests t eg VM Agent (Windws) Pre-requisites fr Obtaining the "Inside View" f VMs, withut using the eg VM Agent Ensure that the eg agent has IP cnnectivity t at least ne f the netwrk interfaces f the VMs. Typically, the Windws File and Print Sharing prt is 139. Enable the eg agent t cmmunicate with this prt. The ADMIN$ share shuld be enabled fr all Windws-based virtual guests being mnitred and the administrative accunt must have permissins t this share drive. Refer t Sectin f this dcument fr a step-by-step prcedure t achieve this. T enable the eg agent t cmmunicate with the Windws VMs, an administrative accunt lgin and passwrd (either a lcal accunt r a dmain accunt) must be prvided when cnfiguring the eg mnitring capabilities. In case f VMs with the Windws XP/Windws 2003/Windws 2008/Windws Vista/Windws 7 perating systems, the firewall n the guest shuld be explicitly cnfigured t allw Windws File and Print Sharing services which are required fr the agent t cmmunicate with the guest perating system. Refer t Sectin f this dcument fr a step-by-step prcedure t achieve this. Set the INSIDE VIEW USING flag fr all the inside view tests t Remte cnnectin t VM (Windws). Fr mnitring a Linux/Slaris VM, the SSH prt (TCP prt 22) must be enabled fr cmmunicatin between the eg agent and the VM being mnitred Pre-requisites fr Mnitring the Oracle VirtualBx in an Agentless Manner General Pre-requisites Enable the remte agent t cmmunicate with the eg manager prt (default: 7077). If VMs running n multi-byte perating systems are t be mnitred (eg., Windws Japanese), then the remte agent mnitring such VMs shuld als run n a multibyte perating system Pre-requisites fr Aut-Discvering VMs and Obtaining their "Outside View" Ensure that the remte agent has IP cnnectivity t the target VirtualBx. Ensure that the remte agent can cnnect t the target VirtualBx via SSH. 8

12 Cnfigure all the tests that the remte agent executes with the name and passwrd f a user wh is privileged t access the VirtualBx via SSH. T enable the remte agent t run VDA cmmands n the VirtualBx, a sud package has t be installed n the VirtualBx hst; t knw hw t install the sud package, refer t Sectin abve. After the sud package is installed, perfrm the fllwing steps n the VirtualBx hst: Lgin t the hst as a rt user; At the cmmand prmpt f the hst, issue the fllwing cmmand t create a new user: useradd d /exprt/hme/<username> m <username> Fr instance: useradd d /exprt/hme/eguser m eguser Next, issue the fllwing cmmand t set a passwrd fr the abve user: passwd <username> When prmpted t prvide the passwrd, specify the same. Then, prceed t edit the sud script by issuing the fllwing cmmand: usr/lcal/sbin/visud Add the fllwing entry t the script: <username> ALL=NOPASSWD:/usr/bin/VBxManage All the tests run by the eg agent shuld be cnfigured with the full path t the install directry f the sud package; Pre-requisites fr Obtaining the "Inside View" f Windws VMs, using the eg VM Agent Install the eg VM Agent n each Windws VM. Fr details n hw t install the eg VM Agent, refer t Sectin 1.5 f this dcument. Enable the remte agent t cmmunicate with the prt at which the eg VM Agent listens (default prt: 60001). Set the INSIDE VIEW USING flag fr all the inside view tests t eg VM Agent (Windws) Pre-requisites fr Obtaining the "Inside View" f VMs, withut using the eg VM Agent Ensure that the remte agent has IP cnnectivity t at least ne f the netwrk interfaces f the VMs. The ADMIN$ share shuld be enabled fr all Windws-based virtual guests being mnitred and the administrative accunt must have permissins t this share drive. Refer t Sectin f this dcument fr a step-by-step prcedure t achieve this. 9

13 T enable the remte agent t cmmunicate with the Windws VMs, an administrative accunt lgin and passwrd (either a lcal accunt r a dmain accunt) must be prvided when cnfiguring the eg mnitring capabilities. In case f VMs with the Windws XP/Windws 2003/Windws 2008/Windws Vista/Windws 7 perating systems, the firewall n the guest shuld be explicitly cnfigured t allw Windws File and Print Sharing services which are required fr the remte agent n the vsphere/esx hst t cmmunicate with the guest perating system. Refer t Sectin f this dcument fr a detailed prcedure. Fr mnitring a Windws VM, TCP prt 139 must be accessible frm the remte agent t the VM. Fr mnitring a Linux/Slaris VM, the SSH prt (TCP prt 22) must be enabled fr cmmunicatin between the remte agent and the VM being mnitred. Fr btaining the "inside view" f VMs running Windws Vista/Windws 7/Windws 2008 perating systems, the egurkhaagent service f the eg remte agent shuld be cnfigured t run using dmain administratr privileges. Refer t the eg User Manual fr the prcedure. Fr btaining the "inside view" f ther Windws VMs hwever, the remte agent service requires n such privileges. Set the INSIDE VIEW USING flag fr all the inside view tests t Remte cnnectin t VM (Windws). 1.5 Cnfiguring the eg Agent t Obtain the Inside View f Windws VMs, using the eg VM Agent T prvide the inside view f a Unix VM, the eg agent uses secure shell (SSH). T btain the inside view f a Windws VM, the eg agent ffers tw ptins. The first ptin uses Windws File & Print Sharing services t push mnitring cmpnents t the VMs. These mnitring cmpnents are then executed n the VM t cllect metrics frm the VMs. T push mnitring cmpnents t the VM and t peridically invke these cmpnents, the eg agent requires dmain administratr privileges t all the VMs being mnitred. In many prductin envirnments, strict security restrictins are enfrced, and it may nt be pssible t cnfigure a mnitring slutin with dmain administratin privileges fr each f the VMs. T handle such envirnments, the eg VM mnitr uses a lightweight mnitring cmpnent called the eg VM Agent, which is installed inside each f the VMs t btain metrics regarding the health f the VMs. The eg VM Agent can be best described as a sftware that can be installed n the Windws virtual machines f a virtual infrastructure t allw a single eg agent t btain an inside view f these VMs, withut dmain administratr privileges. Users have multiple ptins t chse frm when it cmes t installing the eg VM Agent. These ptins have been discussed belw: Manually install the eg VM Agent n every Windws VM using the executable that eg Enterprise includes; Bundle the eg VM Agent as part f a template VM, and use this template t create multiple VMs; this way, the eg VM Agent is autmatically available in all the VMs that are created using the template; Use a sftware distributin slutin such as Micrsft System Center t distribute the eg VM Agent sftware t existing VMs frm a central lcatin; Use the install prcedure that is ideal fr yur envirnment, and quickly get the eg VM Agent up and running. The detailed manual installatin prcedure has been discussed hereunder: 10

14 T install the eg VM Agent n a 32-bit VM, duble-click n the egvmagent.exe, and t install the same n a 64-bit VM, duble-click the egvmagent_64.exe. Figure 1.6 then appears. Click n the Next buttn in Figure 1.6 t cntinue. Figure 1.6: Welcme screen f the eg VM Agent installatin wizard 1. When Figure 1.7 appears, click n Yes t accept the displayed license agreement. Figure 1.7: Accepting the license agreement 2. Use the Brwse buttn in Figure 1.8 t indicate the lcatin in which the agent shuld be installed, and click the Next buttn t prceed. 11

15 Figure 1.8: Specifying the install directry f the eg VM Agent 3. Next, specify the prt at which the VM agent listens fr requests frm the eg agent. The default prt is After prt specificatin, click n the Next buttn in Figure 1.9 t prceed. Figure 1.9: Specifying the VM agent prt 4. A summary f yur specificatins then fllws (see Figure 1.10). Click Next t prceed. 12

16 Figure 1.10: A summary f yur specificatins 5. Finally, click the Finish buttn in Figure 1.11 t cmplete the installatin. Figure 1.11: Finishing the installatin Cmmunicatin between the eg Agent and the eg VM Agent At the time f the installatin f the eg VM agent, a flder named egvmagent is created in the install destinatin specified. The setup prgram als creates a Windws Service named egvmagent n the Windws VM. This service must be running fr the eg agent t btain the inside view f the virtual machine. Upn successful installatin, the eg VM agent starts autmatically and begins listening fr requests at default TCP prt Hwever, if, during the installatin prcess, yu have cnfigured a different prt fr the eg VM agent, then, after cmpleting the installatin, fllw the steps belw t make sure that the eg agent cmmunicates with the eg VM agent via the prt that yu have cnfigured: 13

17 Lgin t the eg manager hst. Edit the eg_tests.ini file in the <EG_INSTALL_DIR>\manager\cnfig directry. The WmiInsideViewPrt parameter in the [AGENT_SETTINGS] sectin f the file is set t by default. If the eg VM agent s prt is changed at the time f installatin, then yu will have t ensure that this parameter reflects the new prt. Therefre, change the default prt specificatin accrdingly. Save the file. At cnfigured intervals, the eg agent issues cmmands t each f the eg VM Agents (using the TCP prt cnfigured during the VM agent installatin). The eg VM Agent executes the cmmands, cllects the inside view metrics frm the Windws VM, and sends the utput back t the eg agent. The eg agent then analyzes the metrics and infrms the eg manager abut the status f the Windws VMs Licensing f the eg VM Agent The eg VM Agent is nt license-cntrlled. Therefre, yu can install and use any number f VM agents in yur infrastructure Benefits f the eg VM Agent The eg VM Agent ffers several key benefits: Ideal fr high-security envirnments: The eg VM Agent is capable f cllecting inside view metrics frm Windws VMs, withut dmain administratr privileges. It is hence ideal fr high-security envirnments, where administratrs might nt be willing t expse the credentials f the dmain administratrs. Easy t install, cnfigure: The eg Enterprise Suite ffers users the flexibility t chse frm multiple methdlgies fr installing the eg VM Agent n the target VMs. Even a manual installatin prcedure, wuld nt take mre than a few minutes. Mrever, since the eg VM agent cmmunicates nly with the eg agent and nt the eg manager, n additinal cnfiguratin needs t be perfrmed n the VM agent t facilitate the cmmunicatin. In additin, the VM agent starts autmatically upn installatin, thereby saving the time and truble invlved in manually starting each f the VM agents. License independent: Since the eg VM agent is nt license-cntrlled, yu can add any number f VM agents, as and when required, t yur envirnment. 1.6 Cnfiguring Windws Virtual Machines t Supprt the eg Agent s Inside View withut the eg VM Agent Fr the "inside" view, by default, the eg agent uses SSH/WMI (depending upn the virtual OS t be mnitred) t cmmunicate remtely with the virtual machines n VirtualBx and cllect metrics. T establish this remte cnnectin with Windws VMs in particular, eg Enterprise requires that the eg agent be cnfigured with dmain administratr privileges. Besides, the INSIDE VIEW USING flag f all inside view tests shuld be set t Remte cnnectin t a VM (Windws). In additin, the fllwing pre-requisites need t be fulfilled: The ADMIN$ share will have t be available n the Windws guests The Windws Firewall shuld be cnfigured t allw Windws File and Print Sharing 14

18 The sectins t cme discuss the prcedure t be fllwed fr fulfilling the 2 requirements abve Enabling ADMIN$ Share Access n Windws Virtual Guests Enabling ADMIN$ Share Access n Windws 2000/2003 VMs If the ADMIN$ share is nt available n any Windws-based virtual guest, create the share using the prcedure detailed belw: 1. Open the Windws Explrer n the virtual machine, brwse fr the crrespnding Windws directry in the C drive, right-click n it, and select the Sharing ptin frm the shrtcut menu. 2. If the ADMIN$ share des nt pre-exist n the Windws guest, then Figure 1.12 appears indicating the same. Figure 1.12: The ADMIN$ share des nt exist On the ther hand, if the ADMIN$ share pre-exists, Figure 1.13 appears. In such a case, first, remve the ADMIN$ share by selecting the D nt share this flder ptin frm Figure 1.13 and clicking the Apply and OK buttns. After this, yu will have t repeat step 1 f this prcedure t pen Figure Then, prceed as indicated by step 3 nwards. 15

19 Figure 1.13: Admin$ share pre-exists 3. T create (r re-create) the ADMIN$ share, select the Share this flder ptin frm Figure 1.14, and prvide ADMIN$ share against the Share name text bx (see Figure 1.14). Figure 1.14: Creating the ADMIN$ share 4. Next, t enable the eg agent t cmmunicate effectively with the Windws guest, yu need t ensure that the permissin t access the ADMIN$ share is granted t an administrative user (lcal/dmain); als, the credentials f this user shuld be passed while 16

20 cnfiguring the eg mnitring capabilities - i.e., while cnfiguring the VMware tests. T grant the access permissins, click n the Permissins buttn in Figure By default, the ADMIN$ share can be accessed by Everyne (see Figure 1.15). T grant access rights t a specific administrative (lcal/dmain) user, select the Add buttn in Figure When Figure 1.16 appears, select the dmain t search frm the Lk in list. The valid user accunts cnfigured n the chsen dmain then appear in the bx belw. Frm this bx, chse the administratr's accunt and click n the Add buttn t add the chsen user accunt t the bx belw the Add buttn. Figure 1.15: Clicking the Add buttn Figure 1.16: Selecting the administrative user t whm access rights are t be granted 6. Finally, click the OK buttn. Yu will then switch t Figure 1.17, where the newly added administratr accunt will appear. 17

21 Figure 1.17: The administratr accunt granted access permissins 7. Select the newly added administratr accunt frm Figure 1.17, and then, using the Permissins sectin, grant the administratr Full Cntrl, Change, and Read permissins. 8. Finally, click the Apply and OK buttns in Figure 1.17 t register the changes. 9. Once yu return t Figure 1.18, click n the Security tab t define the security settings fr the ADMIN$ share (see Figure 1.18). Figure 1.18: Defining the Security settings fr the ADMIN$ share 18

22 10. Here again, yu need t add the same administratr accunt, which was granted access permissins earlier. T d s, click the Add buttn in Figure 1.18, pick a dmain frm the Lk in list f Figure 1.19, select the said administratr accunt frm the dmain users list belw, and click the Add buttn (in Figure 1.19) t add the chsen accunt. Then, click the OK buttn in Figure Figure 1.19: Adding the administratr accunt 11. This will bring yu back t Figure 1.18, but this time, the newly added dmain administratr accunt will be listed therein as indicated by Figure Figure 1.20: The Administratr accunt in the Security list 19

23 12. Finally, click the Apply and OK buttns in Figure Enabling ADMIN$ Share Access n Windws 2008 VMs T enable the ADMIN$ share n a Windws 2008 VM, d the fllwing: 1. Open the Windws Explrer n the virtual machine, brwse fr the crrespnding Windws directry in the C drive, right-click n it, and select the Share ptin frm the shrtcut menu. Figure 1.21: Selecting the Share ptin frm the shrtcut menu Figure 1.22 will then appear. Click n Advanced Sharing in Figure

24 Figure 1.22: Cicking n Advanced Sharing Select the Share this flder check bx in Figure 1.23 that appears, enter ADMIN$ against Share name, and click n the Permissins buttn in Figure 1.23, t allw nly a lcal/dmain administratr t access the flder. Figure 1.23: Enabling the ADMIN$ share When Figure 1.24 appears, click n the Add buttn therein. 21

25 Figure 1.24: Clicking n the Add buttn T allw a dmain administratr t access the flder, first, ensure that a valid dmain is specified in the Frm this lcatin bx f Figure If yu want t grant access t a lcal administratr instead, ensure that the name f the lcal hst is displayed in the Frm this lcatin bx. T change this specificatin, use the Lcatins buttn in Figure Then, enter the name f the lcal/dmain administratr in the Enter the bject names t select text area, and click the OK buttn. Figure 1.25: Allwing a dmain administratr t access the flder The newly added user will be listed in the Grup r user names sectin, as depicted by Figure Select this user, and then, check all the three check bxes under Allw in the Permissins fr <user> sectin in Figure Then, click the Apply and OK buttns therein. 22

26 Figure 1.26: Allwing full access t the lcal/dmain administratr When Figure 1.27 appears, click n the Apply and OK buttns therein t register the changes. Figure 1.27: Applying the changes Alternatively, by adding a new entry in the Windws registry, yu can quickly enable the ADMIN$ share. The steps fr the same are discussed hereunder: 2. In Run prmpt type regedit t pen registry editr. Brwse thrugh the fllwing sub key: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\POLICIES\SYSTEM 23

27 Create a new entry with the belw infrmatin Key Name : LcalAccuntTkenFilterPlicy Key Type : DWORD (32-bit) Key Value : 1 Exit registry editr. Nte: As with any change t the registry, ensure that the abve-mentined change is als perfrmed with utmst care, s as t avid prblems in the functining f the perating system Cnfiguring Windws Firewalls t Allw File and Print Sharing In the case f virtual machines perating n Windws XP/Windws 2003/Windws 2008/Windws Vista/Windws 7, the firewall n the guest shuld be explicitly cnfigured t allw Windws File and Print Sharing services which are required fr the eg agent n the ESX hst t cmmunicate with the guest perating system. T achieve this, d the fllwing: 1. Open the Virtual Infrastructure Client cnsle, and frm the tree-structure in its left pane, select the guest OS (Windws XP/Windws 2003/Windws Vista/Windws 2008/Windws 7) n which the firewall shuld be cnfigured (see Figure 1.28). Figure 1.28: Selecting the guest OS 2. Fllw the menu sequence: Start -> All Prgrams -> Cntrl Panel (see Figure 1.29), and then duble-click n the Windws Firewall ptin within. 24

28 Figure 1.29: Opening the Windws Firewall 3. Figure 1.30 then appears, with the General tab selected by default. Figure 1.30: The General tab f the Windws Firewall dialg bx 4. Deselect the Dn't allw exceptins check bx as indicated by Figure

29 Figure 1.31: Deselecting the 'Dn't allw exceptins' check bx 5. Next, click n the Exceptins tab, and ensure that the File and Printer Sharing ptin is enabled (see Figure 1.32). Figure 1.32: Enabling 'File and Printer Sharing' 6. Then, click the Edit buttn in Figure 1.33 t pen the prts required fr the agent-guest cmmunicatin. Ensure that at least ne f the listed TCP prts are enabled. 26

30 Figure 1.33: Opening prts 7. Finally, click the OK buttn t register the changes. 1.7 Administering the eg Manager t mnitr the Oracle VirtualBx T achieve this, d the fllwing: 1. Lg int the eg administrative interface. 2. eg Enterprise cannt autmatically discver the Oracle VirtualBx. Yu need t manually add the cmpnent using the add/mdify cmpnents page (see Figure Figure 1.34) that appears when the Infrastructure -> Cmpnents -> Add/Mdify menu sequence is fllwed. Remember that cmpnents manually added are managed autmatically. Figure 1.34: Adding the Oracle VirtualBx cmpnent 27

31 3. Next, when yu try t signut f the administrative interface, a list f Uncnfigured tests will appear as shwn in Figure Figure 1.35: List f Uncnfigured tests fr the Oracle VirtualBx 4. Nw try t cnfigure the VM Status test as shwn in Figure Figure 1.36: Cnfiguring the VM Status test 5. Specify the fllwing as shwn in Figure TEST PERIOD - Hw ften shuld the test be executed HOST - The hst fr which the test is t be cnfigured PORT Refers t the prt used by the specified HOST. ORACLE HYPERVISOR USER - Specify the name f the user wh has the right t access the VirtualBx via SSH. 28

32 ORACLE HYPERVISOR PASSWORD - Prvide the passwrd f the ORACLE HYPERVISOR USER. CONFIRM PASSWORD - Cnfirm the passwrd by retyping it here. SUDOCMD - This test executes certain privileged VDA (Virtual Desktp Access) cmmands t pull ut the desired metrics frm the VirtualBx. T enable the test t run these cmmands, yu first need t install a sud package n the VirtualBx hst. The prcedure fr installing this package is detailed in Sectin f this dcument. Once the package is installed, yu need t specify the full path t the install directry f the sud package in the SUDOCMD text bx. IGNORE VMS INSIDE VIEW- Administratrs f sme high security virtualized envirnments might nt have permissins t internally mnitr ne/mre VMs. The eg agent can be cnfigured t ignre such inaccessible VMs using the IGNORE VMS INSISDE VIEW parameter. Against this parameter, yu can prvide a cmma-separated list f VM names, r VM name patterns, fr which the inside view need nt be btained. Fr instance, yur IGNORE VMS INSIDE VIEW specificatin can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used t dente leading and trailing spaces (as the case may be). By default, this parameter is set t nne indicating that the eg agent btains the inside view f all VMs n a VirtualBx hst by default. Nte: While perfrming VM discvery, the eg agent will nt discver the perating system f the VMs cnfigured in the IGNORE VMS INSIDE VIEW text bx. EXCLUDE VMS - Administratrs f sme virtualized envirnments may nt want t mnitr sme f their less-critical VMs - fr instance, VM templates - bth frm utside and frm inside. The eg agent in this case can be cnfigured t cmpletely exclude such VMs frm its mnitring purview. T achieve this, prvide a cmma-separated list f VMs t be excluded frm mnitring in the EXCLUDE VMS text bx. Instead f VMs, VM name patterns can als be prvided here in a cmma-separated list. Fr example, yur EXCLUDE VMS specificatin can be: *xp,*lin*,win*,vista. Here, the * (asterisk) is used t dente leading and trailing spaces (as the case may be). By default, this parameter is set t nne indicating that the eg agent btains the inside and utside views f all VMs n a virtual hst by default. By prviding a cmma-separated list f VMs/VM name patterns in the EXCLUDE VMS text bx, yu can make sure the eg agent stps cllecting inside and utside view metrics fr a cnfigured set f VMs. IGNORE WINNT - By default, the eg agent des nt supprt the inside view fr VMs executing n Windws NT perating systems. Accrdingly, the IGNORE WINNT flag is set t Yes by default. INSIDE VIEW USING - By default, this test cmmunicates with every VM remtely and extracts inside view metrics. Therefre, by default, the INSIDE VIEW USING flag is set t Remte cnnectin t VM (Windws). Typically, t establish this remte cnnectin with Windws VMs in particular, eg Enterprise requires that the eg agent be cnfigured with dmain administratr privileges. In high-security envirnments, where the IT staff might have reservatins abut expsing the credentials f their dmain administratrs, this apprach t extracting inside view metrics might nt be preferred. In such 29

33 envirnments therefre, eg Enterprise prvides administratrs the ptin t deply a piece f sftware called the eg VM Agent (Windws) n every Windws VM; this VM agent allws the eg agent t cllect inside view metrics frm the Windws VMs withut dmain administratr rights. Refer t Sectin 1.5 f Mnitring the Oracle VirtualBx dcument fr mre details n the eg VM Agent. T ensure that the inside view f Windws VMs is btained using the eg VM Agent, set the INSIDE VIEW USING flag t eg VM Agent (Windws). Once this is dne, yu can set the DOMAIN, ADMIN USER, and ADMIN PASSWORD parameters t nne. DOMAIN, ADMIN USER, ADMIN PASSWORD, and CONFIRM PASSWORD - By default, this test cnnects t each virtual guest remtely and attempts t cllect inside view metrics. In rder t btain a remte cnnectin, the test must be cnfigured with user privileges that allw remte cmmunicatin with the virtual guests. The first step twards this is t specify the DOMAIN within which the virtual guests reside. The ADMIN USER and ADMIN PASSWORD will change accrding t the DOMAIN specificatin. Discussed belw are the different values that the DOMAIN parameter can take, and hw they impact the ADMIN USER and ADMIN PASSWORD specificatins: 1. If the VMs belng t a single dmain: If the guests belng t a specific dmain, then specify the name f that dmain against the DOMAIN parameter. In this case, any administrative user in that dmain will have remte access t all the virtual guests. Therefre, an administratr accunt in the given dmain can be prvided in the ADMIN USER field and the crrespnding passwrd in the ADMIN PASSWORD field. Cnfirm the passwrd by retyping it in the CONFIRM PASSWORD text bx. 2. If the guests d nt belng t any dmain (as in the case f Linux/Slaris guests) : In this case, specify "nne" in the DOMAIN field, and specify a lcal administratr accunt name in the ADMIN USER belw. Prir t this, yu need t ensure that the same lcal administratr accunt is available r is explicitly created n each f the virtual machines t be mnitred. Then, prceed t prvide the passwrd f the ADMIN USER against ADMIN PASSWORD, and cnfirm the passwrd by retyping it in the CONFIRM PASSWORD text bx. If key-based authenticatin is implemented between the eg agent and the SSH daemn f a Linux guest, then, in the ADMIN USER text bx, enter the name f the user whse <USER_HOME_DIR> (n that Linux guest) cntains a.ssh directry with the public key file named authrized_keys. The ADMIN PASSWORD in this case will be the passphrase f the public key; the default public key file that is bundled with the eg agent takes the passwrd eginnvatins. Specify this as the ADMIN PASSWORD if yu are using the default private/public key pair that is bundled with the eg agent t implement key-based authenticatin. On the ther hand, if yu are generating a new public/private key pair fr this purpse, then use the passphrase that yu prvide while generating the pair. Fr the detailed prcedure n Implementing Key-based Authenticatin refer t Sectin 2.4 f Mnitring the Oracle VirtualBx dcument. 3. If the guests belng t different dmains - In this case, yu might want t prvide multiple dmain names. If this is dne, then, t access the guests in every cnfigured dmain, the test shuld be cnfigured with the required user privileges; this implies that alng with multiple DOMAIN names, multiple ADMIN USER names and ADMIN PASSWORDS wuld als have t be prvided. T help administratrs prvide these user details quickly and easily, the eg administrative interface embeds a special cnfiguratin page. T access this 30

34 page, simply click n the Click here hyperlink that appears just abve the parameters f this test in the test cnfiguratin page. T knw hw t use the special page, refer t Sectin 1.8 f this dcument. 4. If the INSIDE VIEW USING flag is set t eg VM Agent (Windws) - In this case, the inside view can be btained withut dmain administratr privileges. Therefre, set the DOMAIN, ADMIN USER, and ADMIN PASSWORD parameters t nne. REPORT BY USER - While mnitring a VirtualBx, this flag is set t Yes by default, indicating that by default, the guest perating systems n the VirtualBx are identified using the lgin f the user wh is accessing the guest perating systems. If this flag is set t N, then the guests will be identified using the hst name specified f the guest perating system. REPORT POWERED OS - This flag is set t Yes by default. This flag is clsely related t the REPORT BY USER flag. As already mentined, the REPORT BY USER flag is set t Yes by default. In this case, the default Yes status f the REPORT POWERED OS flag implies that this test will reprt measures fr even thse VMs that d nt have any users lgged in, as lng as the VM is pwered-n. Such guests will be identified by their virtual machine name and nt the user name. If the status f the REPORT POWERED OS flag is changed t N, then this test will nt reprt measures fr thse pwered-n VMs t which n users are lgged in currently. If the REPORT BY USER flag is set t N, then the eg Enterprise system will disregard the status f the REPORT POWERED OS flag (be it Yes r N). In ther wrds, this test will cntinue t reprt measures fr every pwered-n VM n the server. DETAILED DIAGNOSIS - T make diagnsis mre efficient and accurate, the eg suite embeds an ptinal detailed diagnstic capability. With this capability, the eg agents can be cnfigured t run detailed, mre elabrate tests as and when specific prblems are detected. T enable the detailed diagnsis capability f this test fr a particular server, chse the On ptin. T disable the capability, click n the Off ptin. The ptin t selectively enable/disable the detailed diagnsis capability will be available nly if the fllwing cnditins are fulfilled: The eg manager license shuld allw the detailed diagnsis capability Bth the nrmal and abnrmal frequencies cnfigured fr the detailed diagnsis measures shuld nt be Finally click n the Update buttn and signut f the administrative interface. 1.8 Cnfiguring Users fr VM Mnitring In rder t enable the eg agent t cnnect t VMs in multiple dmains and pull ut metrics frm them, the eg administrative interface prvides a special page using which the different DOMAIN names, and their crrespnding ADMIN USER names and ADMIN PASSWORDS can be specified. T access this page, just click n the Click here hyperlink in any f the VM test cnfiguratin pages as shwn in Figure

35 Upn clicking, Figure 1.37 will appear, using which the VM user details can be cnfigured. T add a user specificatin, d the fllwing: Figure 1.37: The VM user cnfiguratin page First, prvide the name f the Dmain t which the VMs belng (see Figure 1.37). If ne/mre VMs d nt belng t any dmain, then, specify nne here. The eg agent must be cnfigured with user privileges that will allw the agent t cmmunicate with the VMs in a particular dmain and extract statistics. If nne is specified against Dmain, then a lcal user accunt can be prvided against Admin User. On the ther hand, if a valid Dmain name has been specified, then a dmain administratr accunt can be prvided in the Admin User text bx. If key-based authenticatin is implemented between the eg agent and the SSH daemn f a Linux guest, then, in the ADMIN USER text bx, enter the name f the user whse <USER_HOME_DIR> (n that Linux guest) cntains a.ssh directry with the public key file named authrized_keys. The ADMIN PASSWORD in this case will be the passphrase f the public key; the default public key file that is bundled with the eg agent takes the passwrd eginnvatins. Specify this as the ADMIN PASSWORD if yu are using the default private/public key pair that is bundled with the eg agent t implement key-based authenticatin. On the ther hand, if yu are generating a new public/private key pair fr this purpse, then use the passphrase that yu prvide while generating the pair. Fr the detailed prcedure n Implementing Key-based Authenticatin refer t Sectin 1.10 f this dcument. The passwrd f the specified Admin User shuld be mentined in the Admin Pwd text bx. Cnfirm the passwrd by retyping it in the Cnfirm Pwd text bx. T add mre users, click n the buttn in Figure This will allw yu t add ne mre user specificatin as depicted by Figure Figure 1.38: Adding anther user In sme virtualized envirnments, the same Dmain culd be accessed using multiple Admin User names. Fr instance, t lgin t a Dmain named egitlab, the eg agent can use the Admin User name labadmin r the Admin User name jadmn. Yu can cnfigure the eg agent with the credentials f bth these users as shwn by Figure

36 The same Dmain mapped t different Admin Users Figure 1.39: Assciating a single dmain with different admin users When this is dne, then, while attempting t cnnect t the dmain, the eg agent will begin by using the first Admin User name f the specificatin. In the case f Figure 1.39, this will be labadmin. If, fr sme reasn, the agent is unable t lgin using the first Admin User name, then it will try t lgin again, but this time using the secnd Admin User name f the specificatin - i.e., jadmin in ur example (see Figure 1.39). If the first lgin attempt itself is successful, then the agent will ignre the secnd Admin User name. T clear all the user specificatins, simply click the Clear buttn in Figure T remve the details f a particular user alne, just click the buttn in Figure T save the specificatin, just click n the Update buttn in Figure This will lead yu back t the test cnfiguratin page as shwn in Figure 1.36, where yu will find the multiple dmain names, user names, and passwrds listed against the respective fields. 1.9 Mnitring the Oracle VirtualBx T mnitr the Micrsft Oracle VirtualBx, d the fllwing: 1. Lgin as a mnitr / supermnitr user. 2. Click n the cmpnents ptin in the menu bar, and select the Servers ptin frm the cmpnents menu. 3. Frm the cmpnent list page, click n the Oracle VirtualBx cmpnent fr which yu wish t view measurements Trubleshting the Failure f the eg Remte Agent t Cnnect t r Reprt Measures fr Linux Guests By default, the eg agent uses secure shell (SSH) t cnnect t Linux guests, and cllect perfrmance metrics frm them. Passwrd Authenticatin is the default methd fr SSH cnnectins in eg Enterprise. If the eg agent fails t reprt measures fr a Linux guest r is unable t cnnect t a guest, it culd imply that the Linux guest des nt supprt SSH r that passwrd authenticatin is nt supprted by the SSH daemn running n the Linux guest. Under such circumstances, yu can perfrm either f the fllwing: Enable Passwrd Authenticatin in the SSH daemn n the Linux guest; r, Implement Key-Based Authenticatin between eg agent and the SSH daemn f the Linux guest. 33

37 If yu pick ptin (1), then fllw the steps given belw t enable passwrd authenticatin: Lgin t the Linux guest t be mnitred. Edit the sshd_cnfig file in the /etc/ssh directry. Check whether the Passwrd Authenticatin flag in the sshd_cnfig file is set t n. If s, set it t yes. Then, save the file and restart/signal the SSH daemn (eg., using kill -1 <sshd_cnfig PID>). On the cntrary, if yu chse t enable key-based authenticatin [i.e, ptin (2)], then yu will have t generate a public/private key pair. A public/private key pair is available in the <EG_INSTALL_DIR>\agent\sshkeys directry (n Windws; n Unix, this will be /pt/egurkha/agent/sshkeys) f the eg agent. While the private key is available in the file named id_rsa, the public key is cntained within the file authrized_keys. Yu nw have the ptin t prceed with the default keys r generate a different key pair. If yu decide t g with the keys bundled with the eg agent, d the fllwing: T enable key-based authenticatin, the private key shuld remain in the <EG_INSTALL_DIR>\agent\sshkeys directry (n Windws; n Unix, this will be /pt/egurkha/agent/sshkeys), and the public key shuld be cpied t each f the Linux guests t be mnitred. T achieve this, first lgin t the Linux guest t be mnitred as the eg user. Create a directry named.ssh in the <USER_HOME_DIR> n the guest perating system, using the cmmand: mkdir ~/.ssh. Next, cpy the authrized_keys file frm the <EG_INSTALL_DIR>\agent\sshkeys directry (n Windws; n Unix, this will be /pt/egurkha/agent/sshkeys) n the eg remte agent hst t the <USER_HOME_DIR>/.ssh directry n the Linux guest. Make sure that the permissin f the.ssh directry and the authrized_keys file is 700. Finally, n the eg manager hst, edit the <EG_INSTALL_DIR>\manager\cnfig\eg_tests.ini file. Against the EgJavaSSHKeyFile parameter, enter: agent/sshkeys/id_rsa.pub, and save the file. On the ther hand, if yu want t generate a new key pair, then d the fllwing: Lgin t any Linux hst in yur envirnment (even a Linux VM) as an eg user. Frm the <USER_HOME_DIR>, execute the cmmand: ssh-keygen -t rsa. Upn executing the cmmand, yu will be requested t specify the full path t the file t which the key is t be saved. By default, a directry named.ssh will be created in the <USER_HOME_DIR>, t which the key pair will be saved. T g with the default lcatin, simply press Enter. Generating public/private rsa key pair. Enter file in which t save the key (/hme/egurkha/.ssh/id_rsa): Next, yu will be prmpted t prvide a pass phrase. Prvide any pass phrase f yur chice. Enter passphrase (empty fr n passphrase): eginnvatins Enter same passphrase again: eginnvatins If the key pair is created successfully, then the fllwing messages will appear: Yur identificatin has been saved in /hm 34

38 e/egurkha/.ssh/id_rsa. Yur public key has been saved in /hme/egurkha/.ssh/id_rsa.pub. The key fingerprint is: 09:f4:02:3f:7d:00:4a:b4:6d:b9:2f:c1:cb:cf:0e:e1 The messages indicate that the private key has been saved t a file named id_rsa in the <USER_HOME_DIR>/.ssh, and the public key has been saved t a file named id_rsa.pub in the same directry. Nw, t enable key-based authenticatin, lgin t the Linux guest t be mnitred as the eg user. Create a directry named.ssh in the <USER_HOME_DIR> n the guest perating system, using the cmmand: mkdir ~/.ssh. Next, cpy the id_rsa.pub file frm the <USER_HOME_DIR>/.ssh directry n the Linux hst t the <USER_HOME_DIR>/.ssh directry n the Linux guest. Ensure that the id_rsa.pub file n the Linux guest is renamed as authrized_keys. Repeat this prcedure n every Linux guest t be mnitred. Then, lck the file permissins dwn t prevent ther users frm being able t read the key pair data, using the fllwing cmmands: chmd g-w ~/ chmd 700 ~/.ssh chmd g-rwx ~/.ssh/* Finally, n the eg manager hst, edit the <EG_INSTALL_DIR>\manager\cnfig\eg_tests.ini file. Against the EgJavaSSHKeyFile parameter, enter: agent/sshkeys/id_rsa.pub, and save the file. Instead f chsing between the authenticatin mdes (Passwrd r Key-based), yu can als disable the usage f the Java SSH client, and use plink t cnnect t Linux guests. T achieve this, fllw the steps given belw: Edit the eg_tests.ini file in the /pt/egurkha/manager/cnfig directry (n Unix; n Windws, this will be <EG_INSTALL_DIR>\manager\cnfig directry). Set the JavaSSHFrVm flag in the [AGENT_SETTINGS] sectin f the file t false; by default, this is set t true indicating that the eg agent uses Java SSH by default. By setting the flag t false, yu can ensure that the eg agent des nt use Java SSH, and instead uses the plink cmmand t cnnect t Linux guests. The plink cmmand exists in the <EG_INSTALL_DIR>\lib\vmgfiles directry (n Windws; n Unix, this will be /pt/egurkha/lib/vmgfiles) f the eg agent. T use the plink cmmand, yu need t explicitly cnfigure the SSH keys, s that the eg agent is able t cmmunicate with the Linux guests using SSH. T d this, fllw the steps given belw: G t the cmmand prmpt and switch t the directry cntaining the plink cmmand. Then, execute the plink cmmand t cnnect t any f the Linux-based virtual machines n the vsphere hst. The syntax fr the plink cmmand is as fllws: plink -ssh <user>@<ip_f_target_hst> <cmmand> 35

39 Fr example, assume that yu want t cnnect t the virtual machine, , as user jhn with passwrd jhn, t knw its hstname. The syntax f the plink cmmand in this case will be: plink -ssh jhn@ hstname, where hstname is the cmmand t be executed n the remte hst fr extracting its hstname. T ensure that yu d nt cnnect t an impster hst, SSH2.x presents yu with a unique hst key fingerprint fr that hst, and requests yur cnfirmatin t save the displayed hst key t the cache. The server's hst key is nt cached in the registry. Yu have n guarantee that the server is the cmputer yu think it is. The server's rsa2 key fingerprint is:<hst key> If yu trust this hst, enter "y" t add the key t PuTTY's cache and carry n cnnecting. If yu want t carry n cnnecting just nce, withut adding the key t the cache, enter "n". If yu d nt trust this hst, press Return t abandn the cnnectin. Stre key in cache? (y/n) y Once yu cnfirm the hst key strage and prvide the user's passwrd t cnnect t the virtual guest, this message will nt appear during yur subsequent attempts t cnnect t any Linux-based virtual machine n the mnitred vsphere/esx hst. In ther wrds, the eg agent will be able t execute tests n all Linux guests n the target ESX hst withut any interruptin. Therefre, press y t cnfirm key strage. 36

40 Cnfiguring and Mnitring the Oracle VDI Brker Chapter 2 Cnfiguring and Mnitring the Oracle VDI Brker Oracle VDI (Virtual Desktp Infrastructure) prvides desktp virtualizatin t replace persnal cmputers with virtual machines (VMs) n a server. Users can access these VMs thugh any RDP client, r thrugh the web via Sun Secure Glbal Desktp (SGD). This chapter deals with the steps invlved in the cnfiguring and mnitring the Micrsft Sharepint 2007 servers. 2.1 Pre-requisites fr Mnitring the Oracle VDI Brker in an Agent-based Manner In case f an agent-based apprach, the fllwing pre-requisites need t be fulfilled t enable the eg agent t run the VDA cmmands: A sud package has t be installed n the brker hst; t install this package, d the fllwing: Lgin t the Slaris system hsting the brker as a rt user. T dwnlad the sud package, cnnect t the URL: If the Slaris prcessr is Intel based, dwnlad the file TCMsud i386.pkg.gz frm the web site mentined abve. On the ther hand, if the Slaris hst uses a SPARC prcessr instead, dwnlad the file TCMsud sparc.pkg.gz frm the web site. Dwnlad the chsen file t any lcatin n the brker hst (say, /tmp). Frm the Slaris prmpt, switch t the directry hsting the dwnladed package and unzip the cmpressed package using the fllwing cmmand: gunzip <package_name> Fr instance: gunzip TCMsud sparc.pkg.gz Then, install the package by issuing the fllwing cmmand at the prmpt: pkgadd -d <package name> Fr instance: 37

41 Cnfiguring and Mnitring the Oracle VDI Brker pkgadd d TCMsud sparc.pkg Once installatin is cmplete, yu will find that the package is installed in the /usr/lcal/ flder n the Slaris hst. All the tests run by the eg agent shuld be cnfigured with the full path t the install directry f the sud package; 2.2 Pre-requisites fr Mnitring the Oracle VDI Brker in an Agentless Manner In case f an agentless apprach, the fllwing pre-requisites need t be fulfilled t enable the eg agent t run the VDA cmmands: A sud package has t be installed n the brker hst; t knw hw t install the sud package, refer t Sectin 1.1 abve. After the sud package is installed, perfrm the fllwing steps n the brker hst: Lgin t the brker hst as a rt user; At the cmmand prmpt f the hst, issue the fllwing cmmand t create a new user: useradd d /exprt/hme/<username> m <username> Fr instance: useradd d /exprt/hme/eguser m eguser Next, issue the fllwing cmmand t set a passwrd fr the abve user: passwd <username> When prmpted t prvide the passwrd, specify the same. Then, prceed t edit the sud script by issuing the fllwing cmmand: usr/lcal/sbin/visud Add the fllwing entries t the script: <username> ALL=NOPASSWD:/pt/SUNWvda/sbin/vda <username> ALL=NOPASSWD:/usr/sbin/cacaadm <username> ALL=NOPASSWD:/pt/SUNWvda/sbin/vda-db-status <username> ALL=NOPASSWD:/pt/SUNWvda/sbin/vda-webadmin All the tests run by the eg agent shuld be cnfigured with the full path t the install directry f the sud package; Once these pre-requisites are fulfilled, the eg agent will use the sud package t run the VDA cmmands and extract the measures fr the tests. 2.3 Administering the eg Manager t mnitr an Oracle VDI Brker T achieve this, d the fllwing: 1. Lg int the eg administrative interface. 2. eg Enterprise cannt autmatically discver the Oracle VDI Brker. Yu need t manually add the cmpnent using the add/mdify cmpnents page (see Figure 2.1) that appears 38

42 Cnfiguring and Mnitring the Oracle VDI Brker when the Infrastructure -> Cmpnents -> Add/Mdify menu sequence is fllwed. Remember that cmpnents manually added are managed autmatically. Yu can either fllw the agentless apprach r agent based apprach t d s. If yu set the Agentless flag t Yes, then select the OS as Linux and Mde as Rexec besides prviding the required User and passwrd fields. Figure 2.1: Adding the Oracle VDI Brker in an agentless apprach 3. Otherwise yu can set the Agentless flag t N and add the cmpnent as shwn in Figure 2.2 Figure 2.2: Adding the Oracle VDI Brker in an agent based apprach 4. Upn adding the cmpnent, try t signut f the administrative interface. A list f uncnfigured tests will appear as shwn in Figure

43 Cnfiguring and Mnitring the Oracle VDI Brker Figure 2.3: List f Uncnfigured tests fr the Oracle VDI Brker 5. Nw cnfigure the VDI Database Status test as shwn in Figure Specify the fllwing in Figure 2.4 Figure 2.4: Cnfiguring the VDI Database Status test TEST PERIOD - Hw ften shuld the test be executed HOST - The hst fr which the test is t be cnfigured PORT Refers t the prt used by the specified HOST. SUDOPATH - This test executes certain privileged VDA (Virtual Desktp Access) cmmands t pull ut the desired metrics frm the brker. T enable the test t run these cmmands, yu first need t install a sud package n the brker hst. The prcedure fr installing this package is detailed in Sectin 1.1 f this dcument. Once the package is installed, yu need t specify the full path t the install directry f the sud package in the SUDOPATH text bx. 7. Finally, click n the Update buttn t register the changes and signut f the administrative interface. 2.4 Mnitring the Oracle VDI brker T mnitr the Oracle VDI Brker, d the fllwing: 1. Lgin as a mnitr / supermnitr user. 2. Click n the cmpnents ptin in the menu bar, and select the Servers ptin frm the cmpnents menu. 3. Frm the cmpnent list page, click n the Micrsft Oracle VDI Brker cmpnent fr which yu wish t view measurements. 40

44 Cnclusin Chapter 3 Cnclusin This dcument has described in detail the steps fr cnfiguring and mnitring the Oracle VDI. Fr details f hw t administer and use the eg Enterprise suite f prducts, refer t the user manuals. We will be adding new measurement capabilities int the future versins f the eg Enterprise suite. If yu can identify new capabilities that yu wuld like us t incrprate in the eg Enterprise suite f prducts, please cntact [email protected]. We lk frward t yur supprt and cperatin. Any feedback regarding this manual r any ther aspects f the eg Enterprise suite can be frwarded t [email protected]. 41