Zenoss Resource Manager Configuration Guide

Transcription

1 Zenoss Resource Mnger Configurtion Guide Relese Zenoss, Inc.

2 Zenoss Resource Mnger Configurtion Guide Copyright 2017 Zenoss, Inc. All rights reserved. Zenoss, Own IT, nd the Zenoss logo re trdemrks or registered trdemrks of Zenoss, Inc., in the United Sttes nd other countries. All other trdemrks, logos, nd service mrks re the property of Zenoss or other third prties. Use of these mrks is prohiited without the express written consent of Zenoss, Inc., or the third-prty owner. Amzon We Services, AWS, nd EC2 re trdemrks of Amzon.com, Inc. or its ffilites in the United Sttes nd/or other countries. Flsh is registered trdemrk of Adoe Systems Incorported. Orcle, the Orcle logo, Jv, nd MySQL re registered trdemrks of the Orcle Corportion nd/or its ffilites. Linux is registered trdemrk of Linus Torvlds. RitMQ is trdemrk of Pivotl Softwre, Inc. SNMP Informnt is trdemrk of Grth K. Willims (Informnt Systems, Inc.). Syse is registered trdemrk of Syse, Inc. Tomct is trdemrk of the Apche Softwre Foundtion. VMwre is registered trdemrk or trdemrk of VMwre, Inc. in the United Sttes nd/or other jurisdictions. Windows is registered trdemrk of Microsoft Corportion in the United Sttes nd other countries. All other compnies nd products mentioned re trdemrks nd property of their respective owners. Prt Numer: Zenoss, Inc Four Points Drive Bldg 1 - Suite 300 Austin, Texs

3 Contents Aout this guide...5 Chpter 1: Enling ccess to rowser interfces...6 Creting nd chnging pulic endpoints... 6 Configuring nme resolution for virtul hosts Chpter 2: Configuring Resource Mnger...15 Strting Resource Mnger...15 Defult server psswords...16 Deleting the RitMQ guest user ccount Creting weekly mintennce script...21 MriDB dtse utilities Optionl: Assigning virtul IP ddress to resource pool Optionl: Replcing the defult digitl certificte Optionl: Enling monitoring on IPv6 networks Optionl: Customiztion mngement...26 Optionl: Configuring OpenTSDB compction Chpter 3: Prepring for monitoring Extending monitoring with ZenPcks Prepring network devices...30 Prepring storge devices Prepring server devices...33 Prepring hypervisor devices...34 Vlidting configurtion using Inspector tool...35 Optionl: Enling monitoring on IPv6 networks Chpter 4: Modeling devices...37 Configuring Windows devices to provide dt through SNMP Configuring Linux devices to provide dt through SNMP Modeling devices using SSH/COMMAND Using device clss to monitor devices using SSH...39 Using the /Server/Scn device clss to monitor with port scn...40 Modeling devices using port scn...40 Aout modeler plugins Deugging the modeling process Next steps...42 Appendix A: Externl HBse configurtion...43 Configuring OpenTSDB for n externl HBse cluster...43 Configuring the OpenTSDB service strtup commnd...44 Disling the Resource Mnger HBse cluster...44 Appendix B: Configuring MriDB for high-vilility deployments

4 4 Moving MriDB services into the mster resource pool... 46

5 Aout this guide Aout this guide Zenoss Resource Mnger Configurtion Guide descries how to set up Zenoss Resource Mnger (Resource Mnger) nd to prepre your environment for monitoring. Use this guide fter completing ll of the steps required for your deployment in Zenoss Resource Mnger Instlltion Guide. Relted Resource Mnger pulictions Title Zenoss Resource Mnger Administrtion Guide Zenoss Resource Mnger Configurtion Guide Zenoss Resource Mnger Instlltion Guide Zenoss Resource Mnger Plnning Guide Zenoss Resource Mnger Relese Notes Zenoss Resource Mnger Upgrde Guide Description Provides n overview of Resource Mnger rchitecture nd fetures, s well s procedures nd exmples to help use the system. Provides required nd optionl configurtion procedures for Resource Mnger, to prepre your deployment for monitoring in your environment. Provides detiled informtion nd procedures for creting deployments of Control Center nd Resource Mnger. Provides oth generl nd specific informtion for prepring to deploy Resource Mnger. Descries known issues, fixed issues, nd ltereking informtion not lredy provided in the pulished documenttion set. Provides detiled informtion nd procedures for upgrding deployments of Resource Mnger. Additionl informtion nd comments If you hve technicl questions out this product tht re not nswered in this guide, plese visit the Zenoss Support site or contct Zenoss Support. Zenoss welcomes your comments nd suggestions regrding our documenttion. To shre your comments, plese send n emil to docs@zenoss.com. In the emil, include the document title nd prt numer. The prt numer ppers t the end of the list of trdemrks, t the front of this guide. 5

6 Zenoss Resource Mnger Configurtion Guide Enling ccess to rowser interfces 1 Control Center nd Resource Mnger hve independent rowser interfces tht re served y independent we servers. Both we servers re configured to use SSL/TLS communictions. The Control Center we server listens t the hostnme of the Control Center mster host nd port 443. For Control Center mster host with the fully qulified domin nme (FQDN) cc-mster.exmple.com, the hostnme URL is You cn sustitute n IP ddress for the hostnme portion of the URL. The Resource Mnger we server cn listen t port pulic endpoints nd virtul host pulic endpoints. A port pulic endpoint is comintion of the IP ddress or hostnme of the Control Center mster host nd port numer. The defult configurtion of Resource Mnger does not include ny port pulic endpoints. If the Control Center mster host hs more thn one interfce, you cn configure port pulic endpoints with different hostnmes. Also, you cn disle TLS communictions for port pulic endpoint. To use port pulic endpoint to gin ccess to the Resource Mnger rowser interfce, no dditionl network nme resolution entries re required. The defult entries for the network interfces of the Control Center mster host re sufficient. The defult virtul host pulic endpoint is the text zenoss5 prepended to the hostnme of the Control Center mster host nd port 443. For the FQDN cc-mster.exmple.com, the URL of the defult virtul host pulic endpoint is You cn chnge the nme of the defult virtul host nd configure dditionl virtul host pulic endpoints. To use virtul host pulic endpoint to gin ccess to the Resource Mnger rowser interfce, you must dd nme resolution entries for the virtul host to the DNS servers in your environment or to the hosts files of individul client systems. The following sections provide dditionl informtion out pulic endpoints, nd instructions for creting pulic endpoints nd configuring virtul hostnme resolution. Creting nd chnging pulic endpoints This section provides instructions for creting nd chnging port pulic endpoints nd virtul host pulic endpoints. 6

7 Enling ccess to rowser interfces Creting pulic endpoints overview The following tle lists communiction requirements nd outlines the process for creting pulic endpoints. Step-y-step instructions follow this overview. Port pulic endpoint Port pulic endpoints cn communicte with or without SSL/TLS. 1 Crete the endpoint. 2 Configure the Zope service. Virtul host pulic endpoint Virtul host pulic endpoints must use SSL/TLS communictions. 1 Crete the endpoint. 2 Configure the Zope service. 3 Configure virtul hostnme resolution. Chnging pulic endpoints To chnge n existing pulic endpoint, crete new endpoint nd then delete the existing endpoint. Creting port pulic endpoint Use this procedure to crete new port pulic endpoint. Port pulic endpoints cn communicte with or without SSL/TLS. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 3 On the right, ove the Pulic Endpoints tle, click Add Pulic Endpoints. The defult view of the Add Pulic Endpoint dilog ox displys the fields for creting port pulic endpoint. 7

8 Zenoss Resource Mnger Configurtion Guide 4 Define new port pulic endpoint. c d e f In the Type re, click Port. From the Service - Endpoint list, select Zenoss.resmgr - zproxy. The selection is the lst entry in the list. In the Host field, enter hostnme or IP ddress tht is ssigned to network interfce on the Control Center mster host. The defult vlue is the hostnme tht ws dded with the Deployment Wizrd when Resource Mnger ws initilly deployed. If the Control Center mster host hs more thn one network interfce, you cn dd the hostnme or IP ddress tht is ssigned to nother interfce. In the Port field, enter sfe, unused port numer tht is greter thn or equl to 1024 nd less thn or equl to For list of ports tht re considered unsfe, see Unsfe ports on Chrome. For the list of ports tht the Control Center mster host uses, refer to the Zenoss Resource Mnger Plnning Guide. In the Protocol field, select HTTPS or HTTP. Optionlly, you cn set up secure proxy server to hndle HTTP requests tht re sent to port pulic endpoint. Click Add. Next step: Configure the Zope service to use the new port pulic endpoint. Choose one of the configurtion options in the following tle. Zope configurtion HTTPS nd the defult secure proxy server HTTP nd no proxy server Note tht when you configure Zope for HTTP protocol nd no proxy server, you cn only gin ccess to the Resource Mnger rowser interfce through port pulic endpoints tht re configured for HTTP. Becuse virtul host pulic endpoints must use HTTPS protocol, ny existing virtul host pulic endpoints stop working. HTTP nd secure proxy server other thn the defult Procedure Configuring Zope for HTTPS nd the defult secure proxy server on pge 9 Configuring Zope for HTTP nd no proxy server on pge 10 Configuring Zope for HTTP nd secure proxy server on pge 10 8

9 Enling ccess to rowser interfces Configuring Zope for HTTPS nd the defult secure proxy server Before performing this procedure, crete port pulic endpoint or virtul host pulic endpoint to use the HTTPS protocol. Use this procedure to configure the Zope service for SSL/TLS communictions nd the secure proxy server tht is included in Resource Mnger. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 3 In the Services tle, expnd Zenoss > User Interfce, nd then click Zope. The Zope service detils pge ppers. 4 In the Configurtion Files tle, locte pth /opt/zenoss/etc/zope.conf, nd in the Actions column, click Edit. The Edit Configurtion window ppers. 5 Configure Zope for secure communictions with the proxy server. Locte the cgi-environment directive. The directive is out one-third of the wy down from the top of the file, on or ner line 380. Configure the proxy server for SSL/TLS communictions: <cgi-environment> HTTPS ON </cgi-environment> 6 Configure the Beker dd-on product to use secure communictions. Locte the product-config directive. The directive is t the ottom the file, on or ner line Set the vlue of the session.secure key to True. 7 Click Sve. Next steps: If you creted port pulic endpoint efore performing this procedure, the endpoint is redy to use. If you creted virtul host pulic endpoint efore performing this procedure, proceed to Configuring nme resolution for virtul hosts on pge 13. 9

10 Zenoss Resource Mnger Configurtion Guide Configuring Zope for HTTP nd no proxy server Before performing this procedure, crete port pulic endpoint to use the HTTP protocol. For more informtion, see Creting port pulic endpoint on pge 7. Use this procedure to configure the Zope service for insecure communictions with Resource Mnger rowser interfce clients. Note When you configure Zope for insecure communictions, existing virtul host pulic endpoints stop working. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 3 In the Services tle, expnd Zenoss > User Interfce, nd then click Zope. The Zope service detils pge ppers. 4 In the Configurtion Files tle, locte pth /opt/zenoss/etc/zope.conf, nd in the Actions column, click Edit. The Edit Configurtion window ppers. 5 Configure Zope for insecure communictions with the proxy server. Locte the cgi-environment directive. The directive is out one-third of the wy down from the top of the file, on or ner line 380. Configure the proxy server for insecure communictions: <cgi-environment> HTTPS OFF </cgi-environment> 6 Configure the Beker dd-on product to use insecure communictions. Locte the product-config directive. The directive is t the ottom the file, on or ner line Set the vlue of the session.secure key to Flse. 7 Click Sve. Configuring Zope for HTTP nd secure proxy server Before performing this procedure, crete port pulic endpoint to use the HTTP protocol. For more informtion, see Creting port pulic endpoint on pge 7. 10

11 Enling ccess to rowser interfces Use this procedure to configure the Zope service for SSL/TLS communictions nd secure proxy server tht is ville on your network. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 3 In the Services tle, expnd Zenoss > User Interfce nd then click Zope. The Zope service detils pge ppers. 4 In the Configurtion Files tle, locte pth /opt/zenoss/etc/zope.conf, nd in the Actions column, click Edit. The Edit Configurtion window ppers. 5 Configure Zope for secure communictions with your proxy server. Locte the cgi-environment directive. The directive is out one-third of the wy down from the top of the file, on or ner line 380. Configure the proxy server for SSL/TLS communictions: <cgi-environment> HTTPS ON </cgi-environment> 6 Configure the Beker dd-on product to use secure communictions. Locte the product-config directive. The directive is t the ottom the file, on or ner line Set the vlue of the session.secure key to True. 7 Click Sve. Creting virtul host pulic endpoint Use this procedure to crete new virtul host pulic endpoint. Virtul host pulic endpoints must use SSL/TLS communictions. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 11

12 Zenoss Resource Mnger Configurtion Guide 3 On the right, ove the Pulic Endpoints tle, click Add Pulic Endpoints. 4 Define new virtul host pulic endpoint. In the Type re, click VHost. c From the Service - Endpoint list, select Zenoss.resmgr - zproxy. The selection is the lst entry in the list. In the VHost Hostnme field, enter virtul hostnme. The hostnme must e different from the Control Center hostnme. For exmple, if the Control Center host is then the virtul hostnme cnnot e zenoss-123. The following strings of text re vlid in this field: d A fully qulified domin nme (FQDN). Any string of text tht includes one or more full stop chrcters (.) is treted s n FQDN. A string of text tht contins only letters nd one or more hyphen chrcters (-). The string is prepended to the hostnme of the Control Center mster host, with full stop chrcter (.) seprting the string nd the hostnme. Click Add. Configuring Zope for HTTPS nd the defult secure proxy server Before performing this procedure, crete port pulic endpoint or virtul host pulic endpoint to use the HTTPS protocol. Use this procedure to configure the Zope service for SSL/TLS communictions nd the secure proxy server tht is included in Resource Mnger. 1 Log in to the Control Center rowser interfce. 2 In the Appliction column of the Applictions tle, click the ppliction nme (Zenoss.resmgr). 3 In the Services tle, expnd Zenoss > User Interfce, nd then click Zope. The Zope service detils pge ppers. 12

13 Enling ccess to rowser interfces 4 In the Configurtion Files tle, locte pth /opt/zenoss/etc/zope.conf, nd in the Actions column, click Edit. The Edit Configurtion window ppers. 5 Configure Zope for secure communictions with the proxy server. Locte the cgi-environment directive. The directive is out one-third of the wy down from the top of the file, on or ner line 380. Configure the proxy server for SSL/TLS communictions: <cgi-environment> HTTPS ON </cgi-environment> 6 Configure the Beker dd-on product to use secure communictions. Locte the product-config directive. The directive is t the ottom the file, on or ner line Set the vlue of the session.secure key to True. 7 Click Sve. Next steps: If you creted port pulic endpoint efore performing this procedure, the endpoint is redy to use. If you creted virtul host pulic endpoint efore performing this procedure, proceed to Configuring nme resolution for virtul hosts on pge 13. Configuring nme resolution for virtul hosts To enle ccess to rowser interfces y virtul hosts, dd nme resolution entries to the DNS servers in your environment or to the hosts files of individul client systems. On Windows client systems, the hosts file is C:\Windows\System32\drivers\etc\hosts. On Linux nd OS/X client systems, the hosts file is /etc/hosts. 13

14 Zenoss Resource Mnger Configurtion Guide Nme resolution syntx The following line shows the syntx of the entry to dd to nme resolution file: IP-Address FQDN Hostnme zenoss5.hostnme For exmple, the following entry identifies Control Center mster host t IP ddress , hostnme cc-mster, in the exmple.com domin cc-mster.exmple.com cc-mster zenoss5.cc-mster Configuring nme resolution on Windows 7 system To perform this procedure, you need Windows Administrtor privileges. 1 Log in to the Windows 7 system s user with Administrtor privileges. 2 Click Strt > All Progrms > Accessories > Notepd. 3 Right click Notepd nd then select Run s dministrtor. 4 Click File > Open, nd then enter the following file pth: C:\Windows\System32\drivers\etc\hosts 5 At the end of the file, dd nme resolution entry. For more informtion, see Nme resolution syntx on pge Sve the file, nd then exit Notepd. Configuring nme resolution on Linux or OS/X system To perform this procedure, you need superuser privileges on the client system. 1 Log in to the client system s root or s user with sudo privileges. 2 In text editor, Open the /etc/hosts file. 3 At the end of the file, dd nme resolution entry. For more informtion, see Nme resolution syntx on pge Sve the file, nd then close the editor. 14

15 Configuring Resource Mnger Configuring Resource Mnger 2 This chpter contins configurtion procedures tht you perform fter Resource Mnger is instlled. Some of the procedures re optionl, nd indicted s such in the section title. For instlltion nd deployment instructions, refer to the Zenoss Resource Mnger Instlltion Guide. Strting Resource Mnger You cn strt Resource Mnger from the Control Center rowser interfce or from the commnd-line interfce. Using the Control Center rowser interfce to strt Resource Mnger To perform this procedure, you need: A tested client system nd rowser A user ccount on the Control Center mster host with ccess privileges for the Control Center rowser interfce For more informtion, refer to the Zenoss Resource Mnger Instlltion Guide. 1 Log in to the Control Center rowser interfce. 2 In the Actions column of the Applictions tle, click Strt for Zenoss.resmgr. 3 In the Strt Service dilog, click Strt Service nd x Children. 4 Optionl: Monitor the strtup, if desired. In the Applictions tle, click Zenoss.resmgr. Scroll down to the Services tle nd review the Helth icon for ech service. As services re strted the Helth icon chnges to check mrk. Using the commnd line to strt Resource Mnger To perform this procedure, you need serviced CLI privileges. For more informtion, refer to the Zenoss Resource Mnger Instlltion Guide. 1 Log in to the Control Center mster host s user with serviced CLI privileges. 2 Strt Resource Mnger: serviced service strt Zenoss.resmgr 15

16 Zenoss Resource Mnger Configurtion Guide 3 Optionl: Monitor the strtup, if desired: serviced service sttus Zenoss.resmgr Defult server psswords Resource Mnger dds glol configurtion prmeters to the run-time environments (Docker continers) of every service. The prmeters include the defult psswords of two MriDB dtse servers, RitMQ server, nd Zope uthentiction server. The defult psswords re the sme in ll Resource Mnger distriutions. To void security issues, Zenoss recommends chnging the defult psswords of the preceding servers. Note Chnges to glol configurtion prmeters persist cross upgrdes. The following list ssocites the ffected servers, their Resource Mnger services, nd their ccount informtion. Note The list includes oth ccount nmes nd psswords. Zenoss recommends chnging the psswords of ech ccount nd strongly discourges chnging the ccount nmes. MriDB server for the events dtse Service: mrid-events Administrtor ccount: glol.conf.zep-dmin-user Administrtor pssword: glol.conf.zep-dmin-pssword User ccount: glol.conf.zep-user User pssword :glol.conf.zep-pssword MriDB server for the models dtse Service: mrid-model Administrtor ccount: glol.conf.zod-dmin-user Administrtor pssword: glol.conf.zod-dmin-pssword User ccount: glol.conf.zod-user User pssword: glol.conf.zod-pssword RitMQ server Service: RitMQ User ccount: glol.conf.mqpuser User pssword: glol.conf.mqppssword Zope uthentiction server Service: Zuth User ccount: glol.conf.zuth-usernme User pssword: glol.conf.zuth-pssword Chnging MriDB psswords Use this procedure to chnge the psswords of the MriDB dtses for event nd model dt. To perform this procedure, the mrid-events nd mrid-model child services of Resource Mnger must e running. 1 Log in to the Control Center mster host s root, or s user with superuser privileges. 16

17 Configuring Resource Mnger 2 Chnge the psswords of the events dtse server. Log in to the Docker continer of the mrid-events service s zenoss. c d serviced service ttch mrid-events su - zenoss Strt n interctive session. export TERM=dum; mysql -u root Access the dministrtion dtse. USE mysql Set the pssword of the root user. Replce New-Pssword with new pssword: SET PASSWORD FOR 'root'@' ' = PASSWORD('New-Pssword'); SET PASSWORD FOR 'root'@'loclhost' = PASSWORD('New-Pssword'); e Record the pssword for use in susequent step. Updte the pssword of the zenoss user. Replce New-Pssword with new pssword: SET PASSWORD FOR 'zenoss'@' ' = PASSWORD('New-Pssword'); SET PASSWORD FOR 'zenoss'@'%' = PASSWORD('New-Pssword'); f Record the pssword for use in susequent step. Exit the interctive session. QUIT g The MriDB server lods the grnt tles into memory immeditely when ccount mngement sttements like SET PASSWORD re used, so the FLUSH PRIVILEGES sttement is not necessry. Log out of the Docker continer. exit 3 Chnge the psswords of the model dtse server. Log in to the Docker continer of the mrid-model service s zenoss. c d serviced service ttch mrid-model su - zenoss Strt n interctive session. export TERM=dum; mysql -u root Access the dministrtion dtse. USE mysql Set the pssword of the root user. Replce New-Pssword with new pssword: SET PASSWORD FOR 'root'@' ' = PASSWORD('New-Pssword'); SET PASSWORD FOR 'root'@'loclhost' = PASSWORD('New-Pssword'); 17

18 Zenoss Resource Mnger Configurtion Guide e Record the pssword for use in susequent step. Updte the pssword of the zenoss user. Replce New-Pssword with new pssword: SET PASSWORD FOR 'zenoss'@' ' = PASSWORD('New-Pssword'); SET PASSWORD FOR 'zenoss'@'%' = PASSWORD('New-Pssword'); f g Record the pssword for use in susequent step. Exit the interctive session. QUIT Log out of the Docker continer. exit 4 Log in to the Control Center rowser interfce. 5 In the Applictions tle, click Zenoss.resmgr. 6 In the ppliction title line, click Edit Vriles. Initilly, the ppliction title line ppers immeditely elow the Control Center nner t the top of the pge. When you scroll down the pge, the ppliction title line persists t the top of the pge. Figure 1: Edit Vriles dilog 7 Updte the psswords of the event dtse server. In the Edit Vriles dilog, locte the glol.conf.zep-pssword vrile. Replce its vlue with the pssword specified previously for the zenoss user of the events dtse server. c Locte the glol.conf.zep-dmin-pssword vrile. d Replce its vlue with the pssword specified previously for the root user of the events dtse server. 8 Updte the psswords of the model dtse server. Locte the glol.conf.zod-pssword vrile. Replce its vlue with the pssword specified previously for the zenoss user of the model dtse server. c Locte the glol.conf.zod-dmin-pssword vrile. d Replce its vlue with the pssword specified previously for the root user of the model dtse server. e At the ottom of the Edit Vriles dilog, click Sve Chnges. 9 In the ppliction title line, click Restrt. 18

19 Configuring Resource Mnger Chnging the RitMQ server pssword Use this procedure to chnge the pssword of the RitMQ server. To perform this procedure, the mrid-model child services of Resource Mnger must e running. 1 Log in to the Control Center mster host s root, or s user with superuser privileges. 2 Chnge the pssword of the zenoss user. Log in to the Docker continer of the RitMQ service s root. serviced service ttch ritmq Chnge the pssword. Replce New-Pssword with new pssword: ritmqctl chnge_pssword zenoss New-Pssword c Record the pssword for use in susequent step. Log out of the Docker continer. exit 3 Log in to the Control Center rowser interfce. 4 In the Applictions tle, click Zenoss.resmgr. 5 In the ppliction title line, click Edit Vriles. Initilly, the ppliction title line ppers immeditely elow the Control Center nner t the top of the pge. When you scroll down the pge, the ppliction title line persists t the top of the pge. Figure 2: Edit Vriles dilog 6 Chnge the pssword of the RitMQ server. In the Edit Vriles dilog, locte the glol.conf.mqppssword vrile. Replce its vlue with the new pssword specified previously. c At the ottom of the Edit Vriles dilog, click Sve Chnges. 7 Restrt the RitMQ service. Scroll down to the Services tle, nd then locte the RitMQ service. In the Actions column of the service, click the Restrt control. 19

20 Zenoss Resource Mnger Configurtion Guide Chnging the Zope uthentiction server pssword Use this procedure to chnge the pssword of the Zope uthentiction server. To perform this procedure, the Resource Mnger ppliction must e running. During the procedure, Resource Mnger must e restrted. 1 Log in to the Resource Mnger rowser interfce s zenoss_system. The defult pssword is MY_PASSWORD. 2 Click the ADVANCED t, nd then click Settings. 3 From the left column, select Users. 4 In the UserId tle, click the zenoss_system link. 5 In the USER SETTINGS re, enter new pssword in the Set New Pssword field, nd then enter it gin, in the Confirm New Pssword field. Record the pssword for use in susequent step. 6 In the Current Pssword for zenoss_system field, enter the pssword you used to log in s zenoss_system. 7 Click Sve Settings, nd then log out of the rowser interfce. 8 Log in to the Control Center rowser interfce. 9 In the Applictions tle, click Zenoss.resmgr. 10 In the ppliction title line, click Edit Vriles. Figure 3: Edit Vriles dilog 11 Updte the pssword of the zenoss_system user ccount. In the Edit Vriles dilog, locte the glol.conf.zuth-pssword vrile. This vrile sets the pssword of the Zope uthentiction server. Replce its vlue with the pssword specified previously for the zenoss_system user ccount. c At the ottom of the Edit Vriles dilog, click Sve Chnges. 12 In the ppliction title line, click the Restrt control. Deleting the RitMQ guest user ccount By defult, RitMQ distriutions include the guest user ccount. To prevent security issues, Zenoss recommends deleting the ccount. 1 Log in to the Control Center mster host s user with serviced CLI privileges. 20

21 Configuring Resource Mnger 2 Attch to the RitMQ continer. serviced service ttch ritmq 3 Delete the guest user ccount. ritmqctl delete_user guest 4 Exit the continer session. exit 5 Restrt the RitMQ service. serviced service restrt ritmq Creting weekly mintennce script The Resource Mnger dtses require regulr mintennce to perform optimlly. This procedure cretes script for weekly invoction, to perform the required mintennce. 1 Log in to the Control Center mster host s root, or s user with superuser privileges. 2 Determine whether the cronie-ncron pckge is instlled. Serch the list of instlled pckges. rpm -q grep -i ncron If the commnd returns no result, perform the next sustep. If the commnd returns result, skip to the next step. Instll the pckge, if necessry. yum instll cronie-ncron 3 Determine whether script is lredy instlled. Some pckges of Resource Mnger instll the script. ls -l /etc/cron.weekly If the result includes serviced-zenossdpck, the mintennce script is instlled. Stop performing this procedure. If the result does not include serviced-zenossdpck, the mintennce script is instlled. Complete this procedure. 4 Crete shell script for weekly invoction. Open /etc/cron.weekly/serviced-zenossdpck with text editor. The file is empty. Add the following content to the file. c #!/in/sh ${SERVICED:=/opt/serviced/in/serviced} service run zope zenossdpck Sve the file, nd then close the text editor. 21

22 Zenoss Resource Mnger Configurtion Guide 5 Set file permissions. chmod 0755 /etc/cron.weekly/serviced/zenossdpck MriDB dtse utilities The Percon Toolkit is collection of helpful utilities for MySQL nd MriDB dtses. For licensing resons, Zenoss cn not distriute it. Zenoss strongly recommends tht ll instlltions of Resource Mnger instll the Percon Toolkit. Instlling the Percon Toolkit with internet ccess To perform this procedure, you need one of the following: login ccount on the mster host tht is memer of the docker group the pssword of the root user ccount For more informtion, refer to the Zenoss Resource Mnger Instlltion Guide. 1 Log in to the Control Center mster host. 2 Instll the pckge. serviced service run zope instll-percon At the end of the instlltion process, the messge Continer not commited ppers. This is norml. The tools re instlled in the distriuted file system, not in n imge. Instlling the Percon Toolkit without internet ccess To perform this procedure, you need one of the following: login ccount on the mster host tht is memer of the docker group the pssword of the root user ccount In ddition, you need the Percon Toolkit pckge file. This procedure includes steps for downloding it to client system, nd then copying it to the Control Center mster host. 1 On client system, use we rowser to downlod the ltest version of the Percon Toolkit pckge. 2 Log in to the Control Center mster host. 3 Prepre the pckge for instlltion. On the Control Center mster host, crete directory for the pckge, nd then chnge directory. c mkdir /tmp/percon && cd /tmp/percon Copy the pckge to the temporry loction. You my use file trnsfer utility such s WinSCP. Updte the ccess permissions of the file nd directory. chmod -R 777 /tmp/percon 4 Strt shell s the zenoss user in Zope continer. 22

23 Configuring Resource Mnger Chnge directory to the loction of the Percon Toolkit file. cd /tmp/percon Strt n interctive shell in Zope continer nd sve snpshot nmed PerconToolkit. mysnp=instllpercontoolkit serviced service shell -i -s $mysnp zope sh c Switch user to zenoss. su - zenoss 5 Instll the pckge nd exit the Zope continer. Crete directory for the pckge. PERCONADIR=/vr/zenoss/percon mkdir -p $PERCONADIR Extrct the pckge files. Replce Version with the version numer of the pckge file: tr --strip-components=1 -C $PERCONADIR -xzvf \ /mnt/pwd/percon-toolkit-version.tr.gz c Exit the zenoss shell. exit d Exit the Zope continer. exit 6 Commit the nmed snpshot. serviced snpshot commit $mysnp 7 Restrt the zeneventserver service. serviced service restrt zeneventserver Optionl: Assigning virtul IP ddress to resource pool The zentrp nd zensyslog services re designed to receive dt from devices in your environment t specific IP ddress. Typiclly, the ddress is ssigned to specific host. However, if the host fils, then no dt is received. To void this issue, you cn ssign virtul IP ddress to resource pool, nd then Control Center cn crete virtul IP interfce on ny host in the pool. Zenoss recommends using virtul IP with resource pools tht include Resource Mnger collection services s est prctice. To perform this procedure, you need n unused IPv4 ddress in the sme sunet s the other hosts in the resource pool to modify. To void conflicts, sk your networking specilist to ssign or reserve the ddress. In ddition, ll of the hosts in the resource pool to modify must hve the sme network interfce nmes. Note For dditionl informtion out network interfce nmes, contct Zenoss Support. 23

24 Zenoss Resource Mnger Configurtion Guide 1 Log in to the Control Center rowser interfce. 2 At the top of the pge, click Resource Pools. 3 In the Resource Pool column of the Resource Pools tle, click the nme of the resource pool to modify. 4 At the right side of the Virtul IPs tle, click Add Virtul IP. 5 In the Add Virtul IP dilog, specify the virtul IP. c d In the IP field, enter n IPv4 ddress. The ddress must e in the sme sunet s the other hosts in the current resource pool. In the Netmsk field, enter n IPv4 sunet msk. The msk must mtch the rnge of ddresses in the current resource pool. The following tle ssocites commonly-used sunet msks with the numer of ddresses they include. Sunet msk Addresses in sunet In the Interfce field, enter the nme of the network interfce tht is used on ll hosts in the resource pool. At the ottom of the Add Virtul IP dilog, click Add Virtul IP. When you configure devices to send syslog or SNMP trp messges, use the virtul IP ddress ssigned to resource pool. Optionl: Replcing the defult digitl certificte The defult configurtion of the Resource Mnger we server uses Zenoss self-signed certificte for SSL/ TLS communictions. Use this procedure to instll your own digitl certificte. Note If your environment uses reverse proxy, contct Zenoss Support for customized ssistnce. To perform this procedure, you need: the certificte nd key files of digitl certificte from certificte uthority or from digitl certificte creted with utility such s OpenSSL Note Currently, certifictes tht require pssphrse re not supported. superuser privileges on the Control Center mster host 1 Log in to the Control Center mster host. 2 Copy the certificte nd key files of your digitl certificte to /etc on the mster host. You cn store the files in ny loction tht remins unchnged during operting system upgrdes. 3 Configure Control Center to use your digitl certificte. c d e Open /etc/defult/serviced with text editor. Locte the SERVICED_CERT_FILE declrtion, nd then replce its vlue with the solute pth of your certificte file. Remove the numer sign chrcter (#) from the eginning of the line. Locte the SERVICED_KEY_FILE declrtion, nd then replce its vlue with the solute pth of your key file. Remove the numer sign chrcter (#) from the eginning of the line. 24

25 Configuring Resource Mnger f Sve the file, nd then close editor. 4 Relod the Control Center service. systemctl relod serviced Optionl: Enling monitoring on IPv6 networks This procedure descries how to configure Resource Mnger to enle monitoring of devices tht re locted on n IPv6 network. The network must e rechle from the IPv4 network environment in which Control Center is deployed. Use this procedure to route n IPv6 ddress lock to Control Center using Docker's virtul ridge interfce, docker0. Resource Mnger cn monitor IPv6 devices tht hve ddresses in the routed lock. To perform this procedure, ech Control Center host needs unique IPv6 prefix routed to it y n upstrem router, nd the Docker service on ech Control Center host must e configured to forwrd IPv6 pckets. For exmple, multi-host deployment with one mster host nd three delegtes could hve the IPv6 configurtion in the following tle. Control Center host IPv6 link prefix IPv6 routed prefix Mster 2001:DB8:ABCD:1000::500/ :DB8:ABCD:2000::/64 Delegte :DB8:ABCD:1000::501/ :DB8:ABCD:2001::/64 Delegte :DB8:ABCD:1000::502/ :DB8:ABCD:2002::/64 Delegte :DB8:ABCD:1000::503/ :DB8:ABCD:2003::/64 The following exmple shows how to configure the sttic routes in the preceding tle on n upstrem Cisco router: ipv6 route 2001:DB8:ABCD:2000::/ :DB8:ABCD:1000::500 ipv6 route 2001:DB8:ABCD:2001::/ :DB8:ABCD:1000::501 ipv6 route 2001:DB8:ABCD:2002::/ :DB8:ABCD:1000::502 ipv6 route 2001:DB8:ABCD:2003::/ :DB8:ABCD:1000::503 Perform the following steps on ech Control Center host: 1 Log on to the Control Center host s root, or s user with superuser privileges. 2 Configure IPv6 pcket forwrding. Open /etc/sysctl.d/ipv6.conf with text editor. Add or edit the following line: net.ipv6.conf.ll.forwrding=1 c Sve the file, nd then close the text editor. 3 Enle IPv6 pcket forwrding without reooting the host. sysctl -w net.ipv6.conf.ll.forwrding=1 4 Configure Docker for IPv6 communictions. Open /etc/sysconfig/docker with text editor. Add the following flgs to the end of the OPTIONS declrtion. 25

26 Zenoss Resource Mnger Configurtion Guide Replce Sunet-Block with the IPv6 sunet to route to Control Center, in CIDR nottion: c --ipv6 --fixed-cidr-v6="sunet-block" Chnge the delimiter of the OPTIONS declrtion to the postrophe chrcter ('). The defult delimiter of the OPTIONS declrtion is the quottion mrk chrcter ("), which is the sme delimiter used with the --fixed-cidr-ipv6 flg. d Sve the file, nd then close the text editor. 5 Restrt the Docker service. systemctl restrt docker After ll Control Center hosts re configured, test IPv6 y using the Docker continer of the zenping service to ping known ddress: serviced service ttch zenping ping6 -c 1 ipv6.google.com If the ping is successful, Docker is le to resolve IPv6 ddresses nd you cn monitor devices on the IPv6 network. If you re unle to rech n IPv6 ddress, or you need help with this procedure, contct Zenoss Support. Optionl: Customiztion mngement Resource Mnger softwre is distriuted s Docker imges. Upgrdes often replce imges, so customiztions of Resource Mnger services re lost, unless customiztions re instlled with chnge mngement system. Quilt is utility for mnging softwre chnges, nd Zenoss recommends instlling it to mnge customiztions. Instlling Quilt with internet ccess To perform this procedure, you need superuser privileges on the Control Center mster host. Use this procedure to dd the Quilt ptch mngement system to Resource Mnger. 1 Log in to the Control Center mster host. 2 Instll the Quilt pckge. serviced service run zope instll-quilt Instlling Quilt without internet ccess To perform this procedure, you need superuser privileges on the Control Center mster host nd the Quilt pckge file. This procedure includes steps for downloding the pckge to client system, nd then copying it to the Control Center mster host. Use this procedure to dd the Quilt ptch mngement system to Resource Mnger. 1 On client system, use we rowser to downlod the ltest version of the Quilt pckge. 2 Log in to the Control Center mster host. 3 Prepre the pckge for instlltion. 26

27 Configuring Resource Mnger c On the Control Center mster host, crete directory for the pckge, nd then chnge directory. mkdir /tmp/quilt && cd /tmp/quilt Copy the pckge to the temporry loction. You my use file trnsfer utility such s WinSCP. Updte the ccess permissions of the file nd directory. chmod -R 777 /tmp/quilt 4 Strt shell s the zenoss user in Zope continer. Chnge directory to the loction of the Quilt pckge file. c cd /tmp/quilt Strt n interctive shell in Zope continer nd sve snpshot nmed InstllQuilt. mysnp=instllquilt serviced service shell -i -s $mysnp zope sh Switch user to zenoss. su - zenoss 5 Extrct the pckge files, nd then compile nd instll Quilt. Extrct the pckge files. tr xzvf /mnt/pwd/quilt-*.tr.gz -C /tmp Compile nd instll the pckge. cd /tmp/quilt-* &&./configure --prefix=/opt/zenoss/vr/ext \ && mke && mke instll 6 Exit the continer. Exit the zenoss shell. exit Exit the Zope continer. exit 7 Commit the nmed snpshot. serviced snpshot commit $mysnp Optionl: Configuring OpenTSDB compction Resource Mnger uses OpenTSDB to store the monitoring dt it collects. When OpenTSDB compction is enled, multiple columns in n HBse row re merged into single column, to reduce disk spce. In testing, Zenoss hs oserved tht these merges result in duplicte dt points, so y defult, compction is disled. Duplicte dt points do not ffect dt integrity. 27

28 Zenoss Resource Mnger Configurtion Guide Note Enling compction slows performnce nd is not recommended. For dditionl ssistnce, contct Zenoss Support. 1 Log in to the Control Center rowser interfce. 2 In the Applictions tle, click Zenoss.resmgr. 3 In the ppliction title line, click Edit Vriles. Initilly, the ppliction title line ppers immeditely elow the Control Center nner t the top of the pge. When you scroll down the pge, the ppliction title line persists t the top of the pge. Figure 4: Edit Vriles dilog 4 In the Edit Vriles dilog, scroll to the ottom of the list. 5 Chnge the vlue of the tsd.storge.enle_compction vrile from Flse to True. 6 Click Sve Chnges. 7 Restrt the OpenTSDB services. Scroll down the pge to the Services tle, nd then locte the opentsd service. In the Actions column of the opentsd service, click the Restrt control. 28

29 Prepring for monitoring Prepring for monitoring 3 Resource Mnger uses stndrd mngement APIs to collect performnce dt, nd therefore does not instll proprietry gents on your infrstructure devices to collect monitoring dt. However, Zenoss recommends tht you review the informtion in this chpter to verify tht the devices to you wnt to monitor re redy to respond to requests for dt. Note This chpter descries how to prepre the most common IT infrstructure. If the infrstructure you wnt to monitor is not descried here, plese refer to the corresponding ZenPck documenttion in the ZenPck ctlog. When your infrstructure is redy to monitor, the Resource Mnger Setup Wizrd guides you through the process of discovering devices on your network nd dding devices y ctegory nd type. Extending monitoring with ZenPcks Dt centers typiclly contin mny different types of hrdwre, softwre, nd cloud services from long list vendors. To keep your compny's dt secure, ll devices, network infrstructure, nd services must e monitored. Resource Mnger is redy to monitor lrge numer of common devices nd network infrstructure s soon it is instlled. However, you cn monitor n even lrger numer of devices in Resource Mnger through the use of ZenPcks. A ZenPck is plug-in tht extends not only monitoring cpilities, ut lso dds new cpilities to the Resource Mnger itself. This cn e s simple s dding new device clsses or monitoring templtes, or s complex s extending the dt model nd providing new collection demons. There re hundreds of ZenPcks ville, some developed, supported, nd mintined y Zenoss, nd mny others tht re developed nd mintined y the Zenoss user community. You cn use ZenPcks to dd: Monitoring templtes Dt sources Grphs Event clsses User commnds Reports Model extensions Product definitions 29

30 Zenoss Resource Mnger Configurtion Guide Simple ZenPcks cn e creted completely within the Resource Mnger. More complex ZenPcks require development of scripts or demons, using Python or nother progrmming lnguge. ZenPcks cn lso e distriuted for instlltion on other Resource Mnger systems. For informtion on how to crete new ZenPck, refer to Zenoss Resource Mnger Administrtion Guide. ZenPck informtion resources Resource Mnger includes link (the question mrk icon) to the documenttion of the ZenPcks tht re included in your instlltion of Resource Mnger. It lso provides ccess to the ZenPck ctlog, which provides detiled descriptions of ll of the ZenPcks developed y Zenoss. You my lso crete your own ZenPcks, or downlod nd instll ZenPcks developed y others. The following list identifies ZenPck resources: ZenPck SDK Zenoss Community, which includes ZenPck development forum Pulic Zenoss repositories on GitHu Displying instlled ZenPcks in Resource Mnger To disply the pre-instlled ZenPcks on Resource Mnger: 1 In the rowser interfce, select the ADVANCED t. 2 In the left column, select ZenPcks. The following figure shows n exmple list of ZenPcks. 3 To monitor infrstructure tht does not pper in the Loded ZenPcks list, downlod the required ZenPck from the ZenPck ctlog. Once the ZenPck is instlled, you cn then dd the infrstructure to Resource Mnger. Prepring network devices This chpter provides instructions for prepring devices for monitoring. 30

31 Prepring for monitoring Prepring switches nd routers To prepre switch or router device for monitoring, verify tht n SNMP gent is instlled nd currently running on the device. Note This rest of this section descries how to prepre Zenoss network devices for monitoring. For other device types, refer to the ZenPck ctlog documenttion. Prepring Cisco UCS network devices Resource Mnger uses SNMP to provide customized or generlized support for mny Zenoss products. The following tle ssocites Zenoss products with the customized Resource Mnger device types tht support them. Device types re listed in the Network re of the Add Infrstructure wizrd, which is oth prt of the setup wizrd nd ville through the Resource Mnger rowser interfce. Note The following device considertions pply: Some supported devices, such s the Cisco Nexus 7000 nd 9000 switches, represent lrge numer of discrete monitoring endpoints. If you re unsure which Resource Mnger deployment size supports the numer of high-density devices you wish to monitor, contct your Zenoss representtive. To monitor Cisco Nexus 9000 Series devices, you must first enle NX-API with the feture mnger CLI commnd on the device. For detiled instructions on performing this tsk, refer to the Cisco documenttion for the Nexus Cisco product Cisco Ctlyst 6500 nd 3560 Series Switches Cisco Nexus 5000 Series Switches Cisco Nexus 7000 Series Switches Cisco Nexus 1000v Series Switches Cisco Nexus 3000 Series Switches Cisco Nexus 9000 Series Switches Cisco Ctlyst 6500 Series Virtul Switching Systems Cisco MDS 9000 Series Multilyer Switches Device type Cisco 6500 (SNMP) Cisco Nexus 5000 (SNMP + Netconf) Cisco Nexus 7000 (SNMP + Netconf) Cisco Nexus 1000V (SNMP + Netconf) Cisco Nexus 3000 (SNMP + Netconf) Cisco Nexus 9000 (NX-API) Cisco VSS (SNMP) Cisco MDS 9000 (SNMP) In ddition, Resource Mnger provides two generlized device types. Cisco product Cisco CtOS-sed switches or routers Cisco IOS-sed switches or routers Device type Generic Switch/Router (SNMP) Cisco IOS (SNMP) Prepring storge devices This section descries how to prepre NetApp nd EMC storge devices for monitoring. For other device types, refer to the ZenPck ctlog documenttion. 31

32 Zenoss Resource Mnger Configurtion Guide Legcy NetApp filers Resource Mnger uses SNMP to monitor legcy NetApp filers tht do not support the Dt ONTAP API (ZAPI). The dt gthered re pproximte ecuse the vlues for mny ojects (Aggregte, Volume, Plex, nd RAID group) re not exposed y the NetApp MIB. To prepre legcy NetApp filer for monitoring, verify tht SNMPv2 is instlled, nd then strt n SNMP gent. Recent NetApp filers Resource Mnger uses HTTP to monitor NetApp filers tht support the Dt ONTAP API (ZAPI). To prepre recent NetApp filers for monitoring, verify the following conditions: The filer is running in 7-Mode or C-Mode. A supported version of ZAPI is instlled nd enled. The minimum required version is 8.x. The user nme nd pssword of your ccount on the filer is uthorized to use ZAPI. EMC storge rrys Resource Mnger uses the We-Bsed Enterprise Mngement (WBEM) protocol to send queries to EMC Storge Mngement Inititive Specifiction (SMI-S) providers tht re ssocited with EMC VMAX nd VNX storge rrys. To prepre EMC rrys for monitoring: At lest one EMC SMI-S provider must e running for ech type of rry to monitor. (The VMAX nd VNX dt models re different.) Before dding n SMI-S provider to Resource Mnger, Zenoss recommends tht you confirm tht it is responding to requests. You need the following informtion: user nme nd pssword for n ccount tht is uthorized to collect dt on ech SMI-S provider IP ddress of ech SMI-S provider port numer t which ech SMI-S provider listens for requests whether to use SSL Note When sttistics logging is disled on the EMC device, grphs for component types of EMC rrys disply NN. The logging feture hs low defult timeout vlue nd must e set to higher vlue or turned on gin periodiclly. Verifying n SMI-S provider on EMC devices To perform this procedure, you need Linux host tht hs network pth to the SMI-S providers of the rrys to monitor. Note Do not perform this procedure on the Resource Mnger host. Perform this procedure to verify tht the SMI-S providers ssocited with EMC rrys re configured correctly, nd re responding to WBEM queries from commnd line tools. 1 Log in to Linux host s root, or s user with superuser privileges. 32

33 Prepring for monitoring 2 Instll WBEM commnd-line interfce pckge, such s wemcli. 3 Verify the SMI-S provider. Replce the vriles with vlues tht re vlid in your environment. wemcli IP-Address:Port -u dmin \ -p 'Pssword' -n root/emc --no-sslei('emc_diskdrive') The expected result is list of Disk Drive clsses. Prepring server devices This section descries how to prepre Linux nd Windows servers for monitoring. Note For other device types, refer to the ZenPck ctlog documenttion. Prepring Linux servers for monitoring Resource Mnger uses SNMP or SSH to monitor Linux servers. For SNMP monitoring, instll n SNMP pckge on the server (for exmple, Net-SNMP) nd strt the gent. For SSH monitoring: Instll n SSH server pckge (for exmple, OpenSSH) nd strt the SSH demon. Monitoring Linux servers requires the ility to run the pvs, vgs, lvs, systemctl, initctl, nd service commnds remotely on your Linux server(s) using SSH. By defult, most of these commnds re only llowed to e run loclly y the root user. If you wnt the root user to remotely run these commnds, perform the following: 1 Instll the sudo pckge on your server. 2 Allow the root user to execute commnds vi SSH without TTY. c d Edit the /etc/sudoers file. Find the line contining root ALL=(ALL) ALL. Add the following line eneth it: Defults:root!requiretty Sve the chnges nd exit. Alterntely, you cn lso set up non-root user to remotely run these commnds. Perform the following: 1 Crete user nmed zenmonitor on your Linux servers for monitoring purposes. 2 Instll the sudo pckge on your server. 3 Allow the zenmonitor user to run the commnds vi SSH without TTY. Edit /etc/sudoers.d/zenoss or /etc/sudoers, if sudoers.d is not supported nd dd the following lines to the ottom of the file: Defults:zenmonitor!requiretty Cmnd_Alis ZENOSS_LVM_CMDS = /sin/pvs, /sin/vgs, /sin/lvs, \ /usr/sin/pvs, /usr/sin/vgs, /usr/sin/lvs Cmnd_Alis ZENOSS_SVC_CMDS = /in/systemctl list-units *, \ /in/systemctl sttus *, /sin/initctl list, /sin/service -- sttus-ll, \ 33

34 Zenoss Resource Mnger Configurtion Guide /usr/sin/dmidecode zenmonitor ALL=(ALL) NOPASSWD: ZENOSS_LVM_CMDS, ZENOSS_SVC_CMDS Sve the chnges, ensuring ll the pths for these commnds re correct. Prepring Windows servers for monitoring Resource Mnger uses SNMP or WinRM to monitor Microsoft Windows systems s follows: Microsoft Windows Server WinRM only. SNMP support does not exist for Windows Server Microsoft Windows Server 2012 nd 2012 R2 - WinRM only. SNMP support does not exist for Windows Server Microsoft Windows Server 2008 R2 - SNMP v1/v2 or WinRM. SNMP v3 support does not exist for Windows Server 2008 R2. To prepre Windows 2008 system for SNMP monitoring, strt the SNMP service. To prepre Windows system for WinRM monitoring, refer to the support rticle tht descries the options nd provides the procedures for configuring your systems. To prepre Windows system for WinRM monitoring, refer to the ppendix, "Prepring Windows Systems." Prepring hypervisor devices This section descries how to prepre vsphere nd Hyper-V hypervisors for monitoring. Note For other device types, refer to the ZenPck ctlog documenttion. vsphere endpoint Resource Mnger uses SOAP to monitor VMwre vsphere servers running the following versions of vsphere: To prepre to monitor VMwre vsphere server: Verify tht you re running supported version of the softwre. Otin the user nme nd pssword of n ccount on the server tht is uthorized to use the vsphere API. Determine whether to use SSL. Hyper-V Resource Mnger uses WinRM to monitor the following Microsoft Hyper-V systems: Microsoft Hyper-V Server 2016 Microsoft Hyper-V Server 2012 nd 2012 R2 Microsoft Hyper-V Server 2008 nd 2008 R2 34

35 Prepring for monitoring To prepre Hyper-V system for WinRM monitoring, refer to the support rticle tht descries the options nd provides the procedures for configuring your systems. Vlidting configurtion using Inspector tool Once you hve set up your environment, you cn vlidte your configurtion using Inspector. The Inspector tool is typiclly instlled on the Control Center mster host nd performs red-only checks on your environment nd provides dvice on resolving potentil issues. For more informtion on the Inspector tool, including downlod nd instlltion instructions see the following knowledge se rticle: Inspector: A tool to vlidte configurtion. Optionl: Enling monitoring on IPv6 networks This procedure descries how to configure Resource Mnger to enle monitoring of devices tht re locted on n IPv6 network. The network must e rechle from the IPv4 network environment in which Control Center is deployed. Use this procedure to route n IPv6 ddress lock to Control Center using Docker's virtul ridge interfce, docker0. Resource Mnger cn monitor IPv6 devices tht hve ddresses in the routed lock. To perform this procedure, ech Control Center host needs unique IPv6 prefix routed to it y n upstrem router, nd the Docker service on ech Control Center host must e configured to forwrd IPv6 pckets. For exmple, multi-host deployment with one mster host nd three delegtes could hve the IPv6 configurtion in the following tle. Control Center host IPv6 link prefix IPv6 routed prefix Mster 2001:DB8:ABCD:1000::500/ :DB8:ABCD:2000::/64 Delegte :DB8:ABCD:1000::501/ :DB8:ABCD:2001::/64 Delegte :DB8:ABCD:1000::502/ :DB8:ABCD:2002::/64 Delegte :DB8:ABCD:1000::503/ :DB8:ABCD:2003::/64 The following exmple shows how to configure the sttic routes in the preceding tle on n upstrem Cisco router: ipv6 route 2001:DB8:ABCD:2000::/ :DB8:ABCD:1000::500 ipv6 route 2001:DB8:ABCD:2001::/ :DB8:ABCD:1000::501 ipv6 route 2001:DB8:ABCD:2002::/ :DB8:ABCD:1000::502 ipv6 route 2001:DB8:ABCD:2003::/ :DB8:ABCD:1000::503 Perform the following steps on ech Control Center host: 1 Log on to the Control Center host s root, or s user with superuser privileges. 2 Configure IPv6 pcket forwrding. Open /etc/sysctl.d/ipv6.conf with text editor. Add or edit the following line: c net.ipv6.conf.ll.forwrding=1 Sve the file, nd then close the text editor. 35

36 Zenoss Resource Mnger Configurtion Guide 3 Enle IPv6 pcket forwrding without reooting the host. sysctl -w net.ipv6.conf.ll.forwrding=1 4 Configure Docker for IPv6 communictions. c Open /etc/sysconfig/docker with text editor. Add the following flgs to the end of the OPTIONS declrtion. Replce Sunet-Block with the IPv6 sunet to route to Control Center, in CIDR nottion: --ipv6 --fixed-cidr-v6="sunet-block" Chnge the delimiter of the OPTIONS declrtion to the postrophe chrcter ('). The defult delimiter of the OPTIONS declrtion is the quottion mrk chrcter ("), which is the sme delimiter used with the --fixed-cidr-ipv6 flg. d Sve the file, nd then close the text editor. 5 Restrt the Docker service. systemctl restrt docker After ll Control Center hosts re configured, test IPv6 y using the Docker continer of the zenping service to ping known ddress: serviced service ttch zenping ping6 -c 1 ipv6.google.com If the ping is successful, Docker is le to resolve IPv6 ddresses nd you cn monitor devices on the IPv6 network. If you re unle to rech n IPv6 ddress, or you need help with this procedure, contct Zenoss Support. 36

37 Modeling devices Modeling devices 4 To model devices, the system cn use: SSH WinRM SNMP (legcy option) Note SSH nd WinRM re the recommended options. The modeling method you select depends on your environment, nd on the types of devices you wnt to model nd monitor. By defult the system remodels ech known device every 720 minutes (12 hours). Note You cn chnge the frequency with which devices re remodeled. Edit the vlue of the Modeler Cycle Intervl in the collector's configurtion. For lrger deployments, modeling frequency my impct performnce. In such environments, you should set the strtt configurtion setting inside the zenmodeler.conf file to chnge the scheduling of the demon. The strtt vlue only dicttes the initil strt time of zenmodeler. Ech susequent run intervl is determined y the zenmodeler cycle time (numer of minutes etween runs) configured on the demon settings pge inside the prent's collector folder which cn e ccessed in Control Center. See the following KB rticle for more informtion: How To Edit The Zenmodeler File To Configure Model Scheduling In Zenoss 5.x The following figure shows how the zenmodeler demon fits into the modeling devices portion of the Resource Mnger rchitecture. Note tht MriDB hs replced ZenDS (MySQL) in version 5.x nd stores the oject dtse (ZODB). 37

38 Zenoss Resource Mnger Configurtion Guide Figure 5: Device Modeling Architecture Configuring Windows devices to provide dt through SNMP To monitor Microsoft Windows Server 2008 R2 systems, Resource Mnger uses SNMP v1/v2 or WinRM. (There is no SNMP v3 support.) For Windows 2012, there is no SNMP support. By defult, Windows my not hve SNMP instlled. To instll SNMP on your prticulr version of Windows, plese refer to the Microsoft documenttion. After setting up nd configuring the SNMP service, you must set the zsnmpcommunity string in Resource Mnger to mtch, to otin SNMP dt. If you wnt processor nd memory monitoring, instll SNMP-Informnt on the device. To collect Windows event logs or log files from Windows ox using syslog, instll the SyslogAgent Windows dd-on. Configuring Linux devices to provide dt through SNMP To configure Linux mchine for monitoring, it must hve SNMP instlled. A good Linux SNMP ppliction is net-snmp. Downlod, instll, nd configure net-snmp to then use SNMP to monitor Linux devices. Modeling devices using SSH/COMMAND You cn gther dditionl informtion y running commnds on the remote device nd interpreting the results. This provides more sclle nd flexile wy to gther informtion tht my not e ville through ny other mens. Ech uilt-in modeling commnd plugin is differentited y the pltform on which it runs. To determine the pltform for the device you wnt to model, run the unme commnd in shell on the device. To model device using commnd plugins, first dd the device y using the protocol "none," nd then choose the plugins you wnt to pply: 1 From the Nvigtion menu, select Infrstructure. 2 Click the Add Devices icon nd select Add Single Device from the drop-down list. The Add Single Device window ppers. 38

39 Modeling devices 3 Enter vlues for Nme or IP nd Device Clss. 4 Cler the Model Device option. 5 Click Add. 6 After dding the device, select the device nme in the devices list. The Device Overview pge ppers. 7 In the left pnel, select Configurtion Properties. 8 If necessry, set the vlues of the zcommndusernme nd zcommndpssword configurtion properties to the user nme nd pssword of the device (or set up uthentiction y using RSA/DSA keys.) Note ~/.ssh/id_rs 9 In the left pnel, select Modeler Plugins. The list of plugins ppers. The left column displys ville plugins; the right column shows those currently selected. 10 Select zenoss.cmd.unme from the Aville list, nd then use the right rrow control to move it to the Selected list on the right. Use the controls to plce it t the top of the list. Figure 6: Add plugin 11 Use the left rrow control to move the other Selected plugins from the Selected list to the Aville list. 12 Click Sve. 13 Model the device y clicking the Model Device utton. Using device clss to monitor devices using SSH The /Server/Cmd device clss is n exmple configurtion for modeling nd monitoring devices using SSH. The zcollectorplugins hve een modified (see the section titled "Modeling Using SSH/Commnd"), nd the device, file system, nd Ethernet interfce templtes used to gther dt over SSH hve een creted. You cn use this device clss s reference for your own configurtion; or, if you hve device tht needs to e modeled or monitored vi SSH/Commnd, you cn plce it in this device clss to use the pre-configured templtes nd configurtion properties. You lso must set the zcommndusernme nd zcommndpssword configurtion properties to the pproprite SSH login informtion for ech device. 39

40 Zenoss Resource Mnger Configurtion Guide Using the /Server/Scn device clss to monitor with port scn The /Server/Scn device clss is n exmple configurtion for modeling devices y using port scn. You cn use this device clss s reference for your own configurtion; or, if you hve device tht will use only port scn, you cn plce it under this device clss nd remodel the device. Modeling devices using port scn You cn model IP services y doing port scn, using the Nmp Security Scnner. You must provide the full pth to your system's nmp commnd. To determine where nmp is instlled, t the commnd line, enter: which nmp If your system returns result similr to: /usr/in/which: no nmp in (/opt/zenoss/in:/usr/kereros/in:/usr/locl/ in:/in:/usr/in:/opt/zenoss/in) then nmp is not instlled. Instll it, nd then try gin. After locting the nmp commnd (including the directory eginning with /), enter the following s the zenoss user on the Resource Mnger server: cd $ZENHOME/liexec ln -s Full_Pth_to_nmp Note To execute commnd using $ZENHOME (/opt/zenoss for the zenoss user), you must e ttched to the continer holding the Resource Mnger ppliction. See the Control Center documenttion for serviced commnds. To model device using port scn: 1 Select the device in the device list. 2 In the left pnel, select Modeler Plugins. 3 Select the zenoss.nmp.ipservicemp plugin in the list of Aville plugins, nd then use the right rrow control to move it to the list of Selected plugins. 4 Click Sve. 5 Remodel the device y clicking the Model Device utton. Aout modeler plugins Resource Mnger uses plug-in mps to mp rel world informtion into the stndrd model. Input to the plugins cn come from SNMP, SSH or Telnet. Selection of plug-ins to run ginst device is done y mtching the plug-in nme ginst the zcollectorplugins configurtion property. DeviceMp Collects sic informtion out device, such s its OS type nd hrdwre model. InterfceMp Collects the list of network interfces on device. RouteMp Collects the network routing tle from the device. IpServicesMp Collects the IP services running on the device. FileSystemMp Collects the list of file systems on device. 40

41 Modeling devices Viewing nd editing modeler plugins for device Plugins re controlled y regulr expressions tht mtch their nmes. To view list of plugins for ny device: 1 Click the device nme in the devices list. 2 In the Device summry pge, select Modeler Plugins. The Modeler Plugins pge ppers. Adding plugins To dd plugin to device: 1 Use the right rrow control to move one or more plugins from the Aville list (on the left) to the Selected list (on the right). 2 Click Sve. Reordering plugins Plugins run in the order in which they re listed. To re-order plugins, use the up nd down rrow controls, nd then click Sve. Deleting plugins from device To delete plugin from device, use the left rrow control to move the plugin from the Selected list to the Aville list. Deugging the modeling process You cn run the modeler from the commnd line ginst single device. This feture is useful when deugging issues with plugin. By pssing the --collect commnd to the modeler, you cn control which modeler plugins re used. For exmple, the following commnd runs only the interfce plugin ginst the uild.zenoss.loc device: 1 Log in to the Control Center host s user with serviced CLI privileges. 2 Attch to the zenmodeler service. serviced service ttch zenmodeler 3 Chnge to the zenoss user. su - zenoss 4 Run the zenmodeler commnd. $ zenmodeler run -v10 --collect=ipinterfce -d uild.zenoss.loc If the commnd returns ny stck trces, forwrd these detils to Zenoss Support for ssistnce: Commnd you rn Stck trce or stck trces returned Version of your Resource Mnger instnce OS version nd ptch level for the remote device 41

42 Zenoss Resource Mnger Configurtion Guide Next steps Resource Mnger is now configured to monitor your IT infrstructure. Your next steps in the monitoring process my include some of the following items: Customize the Dshord Review events in the Events Console Orgnize devices nd infrstructure in to logicl groupings on the Infrstructure pge View dt collection grphs from the Infrstructure pge Generte nd review reports on the Reports pge Refine dt collection on the Advnced pge For more informtion on these nd other procedures, refer to the Zenoss Resource Mnger Administrtion Guide. 42

43 Externl HBse configurtion Externl HBse configurtion A Resource Mnger cn e configured to use n externl HBse cluster, rther thn the cluster tht is included in the ppliction. Note If you do not lredy hve n externl HBse cluster, there is no need to crete one. The procedures in this section re for customers who wish to use n existing HBse cluster for Resource Mnger dt. The version of HBse instlled in your externl HBse cluster must e comptile with the version of OpenTSDB used y the Resource Mnger ppliction. The minimum supported version of HBse is Perform the procedures in the following sections in order. Configuring OpenTSDB for n externl HBse cluster To perform this procedure, instll nd strt Resource Mnger. This procedure configures OpenTSDB to use n externl HBse cluster, rther thn the HBse cluster tht is included in the Resource Mnger ppliction. 1 Log in to the Control Center rowser interfce. 2 In the Applictions tle, click Zenoss.resmgr. 3 Scroll down to the Services tle nd locte the OpenTSDB services reder nd writer. If you do not see reder nd writer, expnd the OpenTSDB service node. 4 Click reder or writer. You will repet the procedure for the other service. 5 On the service detils pge, scroll down to the Configurtion Files tle nd in the Actions column, click Edit. 6 In the Edit Configurtion dilog ox, replce the vlue of the tsd.storge.hse.zk_quorum key with the ZooKeeper quorum of the externl HBse cluster. Delete the existing vlue. The defult vlue is Go lnguge templte expression. Specify the ZooKeeper quorum of the externl HBse cluster. To specify ZooKeeper quorum, crete comm-seprted list of ll quorum memers. Specify ech memer of the quorum with hostnme or IP ddress, the colon chrcter (:), nd then the port numer on which the ZooKeeper service is listening. 43

44 Zenoss Resource Mnger Configurtion Guide Note If you use hostnmes, the Control Center mster host must e le to resolve them to IPv4 ddresses, either through nmeserver on the network or through entries in /etc/hosts. The following exmple shows the correct syntx for 3-memer ZooKeeper quorum: zk-1.exmple.com:2181,zk-2.exmple.com:2181,zk-3.exmple.com:2181 c Click Sve. 7 At the top of the pge, click Stop, nd then click Strt. 8 For the other OpenTSDB service (reder or writer), repet the preceding steps. Configuring the OpenTSDB service strtup commnd This procedure configures the OpenTSDB service to use the externl HBse cluster on strtup. 1 Log in to the Control Center rowser interfce. 2 In the Applictions tle, click Zenoss.resmgr. 3 Scroll down to the Services tle nd locte the OpenTSDB services reder nd writer. If you do not see reder nd writer, expnd the OpenTSDB service node. 4 Click reder or writer. You will repet the procedure for the other service. 5 Ner the top of the service detils pge, click Edit Service. 6 In the Edit Service dilog ox, chnge the vlue of the Strtup Commnd field. Delete the Go lnguge templte expression. The expression is everything fter strt-opentsd.sh. Specify the ZooKeeper quorum of the externl HBse cluster. To specify ZooKeeper quorum, crete comm-seprted list of ll quorum memers. Specify ech memer of the quorum with hostnme or IP ddress, the colon chrcter (:), nd then the port numer on which the ZooKeeper service is listening. Between strt-opentsd.sh nd the ZooKeeper quorum list, include t lest one empty spce. Note If you use hostnmes, the Control Center mster host must e le to resolve them to IPv4 ddresses, either through nmeserver on the network or through entries in /etc/hosts. The following exmple shows the correct syntx for 3-memer ZooKeeper quorum: zk-1.exmple.com:2181,zk-2.exmple.com:2181,zk-3.exmple.com: Click Sve Chnges. 8 At the top of the pge, click Stop, nd then click Strt. 9 For the other OpenTSDB service (reder or writer), repet the preceding steps. Disling the Resource Mnger HBse cluster This procedure disles the HBse cluster tht is included in the Resource Mnger ppliction. 1 Log in to the Control Center mster host s root, or s user with superuser privileges. 2 Stop the Resource Mnger HBse cluster. serviced service stop HBse 3 Disle utomtic strt of the HBse services. 44

45 Externl HBse configurtion Chnge the configurtion of ech service. for svc in hmster regionserver zookeeper do serviced service list $svc \ sed -e 's/"lunch": "uto"/"lunch": "mnul"/' \ serviced service edit $svc done The serviced commnd displys the new configurtion fter ech edit. Verify tht ech service is set to mnul strt. for svc in hmster regionserver zookeeper do serviced service list $svc egrep '"Lunch":' done 4 Remove the OpenTSDB prerequisite for the Resource Mnger HBse cluster. Depending on your version of Control Center, the OpenTSDB service is either opentsd or two seprte services, reder nd writer. Edit opentsd, or one of reder or writer. serviced service edit reder The serviced commnd opens the service's configurtion in the defult text editor. Locte the Prereqs section, nd then remove everything etween the left squre rcket ([) nd the right squre rcket (]) chrcters. The following lines show n exmple Prereqs section: "Prereqs": [ { "Nme": "HBse Regionservers up", "Script": "{{with $rss := (child (child (prent) \"HBse \")).Instnces }}" } ], After editing, the section should look like the following exmple: c d "Prereqs": [], Sve the file, nd then exit the text editor. If your version of Resource Mnger includes two OpenTSDB services (reder nd writer) repet the preceding susteps for the other service. 45

46 Zenoss Resource Mnger Configurtion Guide Configuring MriDB for high-vilility deployments B In high-vilility deployments, the mrid-events nd mrid-model services must e in the sme resource pool s the mster host nodes. Use the following procedure to move the services from their defult pool. Moving MriDB services into the mster resource pool To perform this procedure, oth Control Center mster host nodes must hve sufficient RAM nd CPU resources for Control Center services nd for the MriDB services. For more informtion out the mount of RAM nd CPU resources tht re required, contct your Zenoss representtive. Use this procedure to move the mrid-model nd mrid-events services to the mster resource pool. If the services re lredy in the mster resource pool, skip this procedure. 1 Log in to the Control Center rowser interfce. 2 In the Applictions tle, click Zenoss.resmgr. 3 Scroll down to the Services tle, nd then expnd the Infrstructure entry. 4 In the Service column of the Services tle, click mrid-events. 5 On the mrid-events pge, click Edit Service. 6 In the Edit Service dilog ox, select mster from the list in the Resource Pool ID field. 7 At the ottom of the Edit Service dilog ox, click Sve Chnges. 8 On the mrid-events pge, click Restrt. 9 Repet steps 3-8 for the mrid-model service. 46