CA Cloud Service Delivery Platform

Transcription

1 CA Cloud Service Delivery Platform Monitoring Service Implementation Guide Release 1.1

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4 CA Technologies Product References This documentation set references the following products that constitute the CA Cloud Service Delivery Platform. Foundation Products: CA Service Catalog CA Business Intelligence CA Embedded Entitlements Manager (CA EEM) CA Process Automation CA SiteMinder CA Service Desk Manager (CA SDM) Monitoring Service Products: CA Service Operations Insight CA Spectrum CA Nimsoft Monitor

5 Contents Chapter 1: Introduction to Monitoring Services 7 Monitoring Service Capabilities... 7 Chapter 2: Deployment Prerequisites 9 Infrastructure... 9 Central Deployment... 9 Regional Deployment Create a Private Heartbeat Network Download the Appliances Prepare the Deployment Worksheet Chapter 3: Monitoring Services Deployment 13 Manual Deployment Deploy Monitoring Services Configure Nimsoft Server Disks Verify Deployment Verify CA Nimsoft Server Cluster Verify CA Nimsoft Infrastructure Manager Verify CA Nimsoft Unified Management Portal Verify CA Spectrum Verify Alarm Notifier Execution on CA Spectrum Main Landscape Server Verify CA Spectrum OneClick Verify CA Service Operations Insight Chapter 4: Post Deployment Tasks for Monitoring Service 39 Monitor CA CSDP Servers Set the Password for Bulk Upload of Users Change IP address of MaaS-NMSCluster in CA Spectrum Validate IP Address on CA Nimsoft Central Disable IP Validation in CA Nimsoft Central Settings to Ignore IP Validation Deactivate and Activate the Discovery Server Probe Create Access Control Lists in CA Nimsoft Access Control and LDAP Group Lists Permissions for Access Control Contents 5

6 Apply License to the CA Nimsoft Regional Hub Chapter 5: Register the Monitoring Services 51 Central Deployment Regional Deployment Prerequisite for Regional Deployment Appendix A: Server Access Credentials and Port List 65 Appendix B: Troubleshooting and Best Practices 67 Restart or Power Down CA Spectrum Add Permission for Users to View Reports Remove Permission to Reports Configure CA Nimsoft Monitor Server from Command Prompt Monitoring Service Implementation Guide

7 Chapter 1: Introduction to Monitoring Services System administrators offer Monitoring-as-a-Service (MaaS) on the CSDP platform. We assume that you are familiar with how your organization has deployed CA CSDP. The monitoring service is a packaged set of content that you use with the CSDP platform to deliver Monitoring-as-a-Service (MaaS). It includes the connectors, processes, forms, payloads, and scripts that are required for service fulfillment and delivery. Each service individually represents a service offering and is delivered as a singular unit to automate and deliver that service. Monitoring Service Capabilities Monitoring-as-a-Service (MaaS) extends the capabilities of the CSDP platform to monitor and assure the availability and performance of services and underlying resources. The service can detect faults of services or resources that are offered to the customers. Monitoring service offers the following capabilities: Monitoring of Resources and Services Monitors and manages resources, services, service level agreements, and any faults that are associated with them. Data Collection and Metrics Billing Collects data to track and monitor the services, and resources, health, and utilization for reporting purposes. This data can be used to identify faults and so that you can take necessary corrective actions. Generates data that can be used for billing purposes. Collecting Probe Usage Collects the usage of probes from CA Nimsoft, to support the billing utility. Chapter 1: Introduction to Monitoring Services 7

8

9 Chapter 2: Deployment Prerequisites As a service provider administrator, you meet the requirements for the implementation and then prepare a worksheet for reference throughout the implementation. Next, you deploy the appliances, configure them, and then verify the implementation. Important! ESX password must include only alphanumerical characters. Infrastructure The solution requires VMware environment with VMware vcenter 4.1or above with VMware ESX 4.1 or above servers for deploying virtual machines. Before you install the appliances, work with your administrator to ensure that the VMware ESX resources meet the following minimum requirements: Number of vcpus: 22 Total RAM: 80 GB Total Storage: 700 GB Number of Static IP Addresses: 13 Central Deployment The following table lists the requirements for each appliance: Appliances vcpus RAM Storage Network MaaS-SOI GB 18 GB to 40 GB One IP address MaaS-Spectrum GB 40 GB to 80 GB Two IP addresses Nimsoft UMP MaaS-UMP 2 4 GB 44 GB maas-rpol 2 4 GB 44 GB Nimsoft NMS maas-nms1 2 8 GB 89 GB maas-nms2 2 8 GB 89 GB Spectrum maas-oneclick 2 4 GB 44 GB Two IP addresses Four IP addresses Three IP addresses Chapter 2: Deployment Prerequisites 9

10 Infrastructure Appliances vcpus RAM Storage Network maas-spectrum 2 8 GB 48 GB maas-ss 2 4 GB 44 GB SOI maas-soi 2 8 GB 48 GB One IP address Regional Deployment The following table lists the requirements for each appliance: Appliances vcpus RAM Storage Network Nimsoft MaaS- Nimsoft Regional Hub 2 4 GB 44 GB Nimsoft Regional Poller 2 4 GB 44 GB Spectrum Spectrum Regional (MaaS-DSS) 2 8 GB 43 GB Two IP address One IP address Create a Private Heartbeat Network Create a private heartbeat network for the CA Nimsoft Monitor cluster on the host. Follow these steps: 1. Click ESX, and then click the Configuration tab. 2. Click Networking on the left pane. 3. Click Add Networking to open the Add Network wizard. 4. Select default of Virtual Machine and click Next. 5. Select Create a vsphere standard switch, and click Next. Important! Ensure that all check boxes are cleared. 6. Provide a name for the Network Label. For example, CA Nimsoft Monitor Heartbeat. 7. Click Next. 8. Review Setup and click Finish. A private heartbeat network for the CA Nimsoft Monitor cluster is created on the host. 10 Monitoring Service Implementation Guide

11 Download the Appliances Download the Appliances The virtual appliances are preconfigured application stacks that are prebuilt to provide the monitoring service. The following appliances are comprised of virtual machines that are packaged as a unit and managed in Open Virtualization Format (OVF). OVF is an open standard for packaging and distributing the appliances. Important! Before you download, verify that the system to which you are downloading the service has a minimum of 100 GB free disk space. Go to download the following appliance ZIP files in any order, and extract them to a local drive in any order: CA Service Operations Insight.zip Prioritizes and resolves problems. CA Spectrum Infrastructure Manager zip Automates fault management across infrastructures and tailoring the information views. MaaS-DSS.zip Enables the distribution of management for portions of a large-scale network, across multiple servers in a single physical location. Improves managing computing infrastructure by distributing the network load that management introduces, traffic, and delegating management functions to remote workstations. CA Nimsoft Unified Monitoring Portal 6.6.zip The CA Nimsoft Unified Management Portal (UMP) manages devices. Alarms are viewed and managed, dashboards are created and viewed, and users are managed. CA CSDP enables you to view and manage the device information about each Tenant, Location, and Support departments. CA Nimsoft Monitor Server Regional.zip This appliance allows you to set up distributed regional Nimsoft Hubs that manage devices within that region and work with the Central/Primary Nimsoft setup. CA Nimsoft Monitor Server Cluster 6.5.zip This appliance is the core of Nimsoft and is also referred to as the Central/Primary Nimsoft setup. The appliance is a cluster setup which is designed to provide high availability (active/passive). All other Nimsoft appliances work with this appliance to manage devices seamlessly. Download and extract the appliances. Each extracted appliance contains Open Virtualization Format (OVF) files that are used while deploying the monitoring service. After you download and extract the appliances, do one of the following actions: Chapter 2: Deployment Prerequisites 11

12 Prepare the Deployment Worksheet If you deploy the monitoring service automatically, specify the location of the virtual appliances. If you deploy the monitoring service manually, note the location to use when required in vspehere client. Prepare the Deployment Worksheet Before you deploy the appliances, gather the information in a worksheet. Use the worksheet details as you work through the installation prompts while deploying the OVF templates using the VMware vsphere Client. For more information, see the Prepare the Deployment Worksheet under Implementation Checklist on the bookshelf main page. 12 Monitoring Service Implementation Guide

13 Chapter 3: Monitoring Services Deployment When the service provider administrator registers for monitoring services and they select the deployment method from the service offerings, the request goes through an automated workflow. Deploying the appliances creates preconfigured virtual machines in your VMware ESX server. To deploy the monitoring service, use the OVF templates that are provided in each appliance. You can deploy the monitoring service using one of the following methods: Automatic Deployment Deploys the monitoring service automatically from CA CSDP, Deploy Monitoring Service-Central. The deployment is available if you have access to the VMware environment at your organization. Note: This release of Monitoring Services supports only manual deployment. Manual Deployment Deploys the monitoring service manually by deploying and configuring the OVF templates using VMware vsphere Client. The deployment is required if you do not have access to the VMware environment at your organization. Note: For more information, see Register the Monitoring Services (see page 51). Important! Do not re-deploy a service that is active. Manual Deployment Before you register the monitoring services environment, you must deploy all the OVFs and must validate the environment. Deploy Monitoring Services Deploying the appliances creates preconfigured virtual machines on your VMware ESX Server. To deploy the monitoring service, use the OVF templates that are provided in each appliance. Note: Enter the values that are required during the deployment process, in the worksheet. Chapter 3: Monitoring Services Deployment 13

14 Manual Deployment Follow these steps: 1. Log in to the VMware vcenter Server as an administrator using VMware vsphere Client. 2. Disregard the security warning and click Ignore to continue. 3. Click File, Deploy OVF Template. The Source page opens in the Deploy OVF Template window. 14 Monitoring Service Implementation Guide

15 Manual Deployment 4. Browse to the first template, and select the OVF template that you want to deploy and click Next. The OVF templates must be deployed in the following sequence: Important! Install the templates in the following sequence because deployment and configuration are interdependent. We do not support any deviations from these procedures. These procedures also assume that you have the required infrastructure and non-ca Technologies software installed. 1. MaaS-NMS 2. MaaS-UMP 3. MaaS-Spectrum MaaS-SOI MaaS-DSS - Deployed only if a regional deployment is required. 6. CA Nimsoft Monitor Server Regional - Deployed only if a regional deployment is required. The OVF Template Details page opens with details stored in the OVF template such as the download size, available disk size, and vendor name. Chapter 3: Monitoring Services Deployment 15

16 Manual Deployment 5. Verify the template details and click Next. The Name and Inventory Location page opens. You add a name to identify the OVF and specify the datacenter where you want to provision the server. 16 Monitoring Service Implementation Guide

17 Manual Deployment 6. Enter the server name in the Name field, select the Inventory Location, and then click Next. Note: By default, the name that is specified in the OVF template displays in the Name field. Retain the default name for the template. The Resource Pool page opens. Chapter 3: Monitoring Services Deployment 17

18 Manual Deployment 7. Select the resource pool on which you want to deploy the OVF templates and then click Next. The Disk Format page opens. 18 Monitoring Service Implementation Guide

19 Manual Deployment 8. Select Thick Provision Eager Zeroed, for MaaS-NMS OVF. For the others select Thin Provision, and click Next. The Network Mapping page opens. 9. Select the network for the solution with all the servers in CA CSDP. When deploying the MaaS-NMS cluster you are prompted to enter a second network. Select the private network for the NMS Servers. Your VM administrator provides the network name. Note: For more information, see Create a Private Heartbeat Network. The Private Network must be accessible only to the NMS servers in the NMS cluster. Do not use this network for any other deployment. Chapter 3: Monitoring Services Deployment 19

20 Manual Deployment The Properties page opens to customize the software solution for this deployment. This page contains the Host settings. Note: The mandatory field descriptions are marked in red. 20 Monitoring Service Implementation Guide

21 Manual Deployment 10. Enter the values for each field using the information that you gathered in the Deployment Worksheet and then click Next. The Ready to Complete page opens and displays a summary of the details you entered in the previous pages. 11. Verify the entered details, select Power on after deployment, and then click Finish. 12. Stop and configure the virtual machines, while deploying the NMS Server cluster (MaaS-NMS). Ensure that the Windows cluster is set up correctly before continuing with other deployments. The NMS Server cluster must be configured properly before you can start any virtual machines. Note: For more information about configuring NMS Cluster, see Configure Nimsoft Server Disks. 13. Repeat the steps to deploy the other templates and complete deployment of all OVF templates. The deployment of monitoring service is complete. Note: For CA CSDP to function properly, synchronize the dates, times, and time zones of your Windows appliances. Chapter 3: Monitoring Services Deployment 21

22 Manual Deployment Configure Nimsoft Server Disks Inflate Hard Disks To configure the Nimsoft Server Disks, do the following actions: Inflate the hard disks Share the virtual disk Configure the Nimsoft Server using the interface, if: you use a vcenter version lower than v5.x you could not select ZeroEager for the CA Nimsoft Monitor server cluster while deploying the OVFs Note: For the steps to configure the CA Nimsoft Monitor server using the command prompt, see the section Configure CA Nimsoft Monitor Server from Command Prompt (see page 68). Configure the disks on the host VMware ESX server. Note: Skip this section if you could deploy using Thick ZeroEager. Important! Complete the following process before you power on the CA Nimsoft Monitor Server 6.5 vapp for the first time. Inflate hard disk 2 and hard disk 3, in the VMware vsphere Client. Follow these steps: 1. Right-click the OSS-NMS1 virtual machine and select Edit Settings. The virtual machine Properties window opens. 2. Select Hard Disk 2 and 3 from the hardware list and write down the Disk File name. Note: Make sure that the names are readily available for the further steps. Example:[datastore] MaaS-NMS1/MaaS-NSMS1_1.vmdk. [Datastore name] Folder name/disk file name.vmdk (ends in vmdk) 3. Click Cancel. 4. Click the Summary tab on OSS-NMS1. 5. Right-click Datastore, and select Browse Datastore. 22 Monitoring Service Implementation Guide

23 Manual Deployment The datastore name displays. 6. Double-click the folder name, for example, OSS-NMS1, to open the folder. 7. Select and right-click the hard disk2 name, for example, OSS-NMS1_1.vmdk. 8. Click Inflate. Sharing the Virtual Disk 9. Repeat steps 4 through 8 for hard disk 3. The CA Nimsoft Monitor Server 6.5 Cluster requires shared disks between the two Virtual Machines that are the nodes of the cluster. Follow these steps: 1. Right-click the OSS-NMS1 virtual machine, and select Edit Settings. Chapter 3: Monitoring Services Deployment 23

24 Manual Deployment The OSS-NMS1-Virtual Machine Properties page opens. 2. Select SCSI controller 1, from the Hardware list. 24 Monitoring Service Implementation Guide

25 Manual Deployment 3. Select Virtual, from Set SCSI Bus Sharing section. 4. Repeat steps 2 through 3 for SCSI controller Select Hard Disk 2 and 3 from the device list and write down the Disk File name. Example: [datastore] MaaS-NMS1/MaaS-NMS1_1.vmdk Note: Make sure that the names are readily available for the further steps. 6. Click OK. 7. Repeat steps 1 through 4 of this procedure for the OSS-NMS2 virtual machine. Chapter 3: Monitoring Services Deployment 25

26 Manual Deployment Note: If you could not select Thick EagerZero, when deploying the OVF, you must add the disks for OSS-NMS2. Note: If you do not see Hard disk 2 and Hard disk 3, skip step 7 and In the OSS-NMS2 virtual machine, select Hard disk 2 and click Remove. 9. Select Remove from virtual machine and delete files from disk, in the Removal Options. 10. Repeat step 7 for Hard Disk Click Add. The Add Hardware wizard opens. 26 Monitoring Service Implementation Guide

27 Manual Deployment Note: Adding the hard disk also adds the SCSI Controller. 12. Select Hard Disk, and click Next. 13. Select Use an existing virtual disk, and click Next. Chapter 3: Monitoring Services Deployment 27

28 Manual Deployment 14. Click Browse to navigate to the Disk File location you noted in step 5 and then click Next. 28 Monitoring Service Implementation Guide

29 Manual Deployment Note: Ensure that you navigate to the location for Disk Set the Virtual Device Node to SCSI (1:0), and click Next. Chapter 3: Monitoring Services Deployment 29

30 Manual Deployment 16. Review the options, and click Finish on the Ready to Complete page. 30 Monitoring Service Implementation Guide

31 Verify Deployment 17. Repeat steps 9 to14 using the Disk File location noted earlier for Disk 3 and set the Virtual Device Node to SCSI (2:0). The New SCSI controller is added. 18. Select the new SCSI controllers and ensure that the SCSI bus sharing is set to Virtual. 19. Click OK. The virtual disk configuration is complete. 20. Right-click the CA Nimsoft Monitor Server 6.5 vapp and select Power On. Note: Ignore the warning about starting from the vapp, and click OK. Verify Deployment After you deploy the appliances for monitoring services, verify that you can successfully log in to the virtual machines. Note: To enter the specific values that are required during the verification process, use the Server Access Credentials for Monitoring Services worksheet. Chapter 3: Monitoring Services Deployment 31

32 Verify Deployment Verify the deployment of the following components: Verify CA Nimsoft Server Cluster (see page 32) Verify CA Nimsoft Infrastructure Manager (see page 33) Verify CA Nimsoft Unified Management Portal (see page 34) Verify CA Spectrum (see page 34) Verify Alarm Notifier Execution on CA Spectrum Main Landscape Server (see page 35) Verify CA Spectrum OneClick (see page 36) Verify CA Service Operations Insight (see page 37) Verify CA Nimsoft Server Cluster To verify the deployment, log in to one of the Nimsoft Cluster nodes in virtual machines NMS1 or NMS2. Ensure that the CA Nimsoft Server Cluster is deployed on the virtual machine. Follow these steps: 1. Log in to the virtual machine with domain administrator credentials. 2. Click Start, Administrative Tools, and then click Failover Cluster Manager. 32 Monitoring Service Implementation Guide

33 Verify Deployment 3. Verify that the status of the cluster name, drive, and Nimsoft Robot Watcher Service is Online. You have verified that the CA Nimsoft Server Cluster is deployed successfully. Verify CA Nimsoft Infrastructure Manager To verify the deployment, log in to the virtual machine where the CA Nimsoft Infrastructure Manager is deployed. Follow these steps: 1. Log in to Nimsoft Infrastructure Manager host with administrator credentials. 2. Click Start, All Programs, Nimsoft Monitoring, Infrastructure Manager. The Nimsoft Infrastructure Manager window opens. 3. Verify that you have a parent child relationship for Domains, MaaS-Central-Domain, MaaS-Central-Hub, and MaaS-Central-Robot. Chapter 3: Monitoring Services Deployment 33

34 Verify Deployment You have verified that Nimsoft Infrastructure Manager is deployed. Verify CA Nimsoft Unified Management Portal To verify the deployment, log in to the virtual machine where the CA Nimsoft Unified Management Portal (UMP) is deployed. Follow these steps: 1. Open the browser and type the URL: 2. Log in as an administrator. The UnifiedServiceManager page displays with the following items as peers at the root level: Groups, Geo View, Discovery, and Search Results You have verified that Nimsoft UMP is deployed. Verify CA Spectrum To verify the deployment, log in to the virtual machine where the SpectroSERVER is deployed. 34 Monitoring Service Implementation Guide

35 Verify Deployment Follow these steps: 1. Log in to the virtual machine with administrator credentials. 2. Click Start, All Programs, CA, and then start SPECTRUM Control Panel. The CA Spectrum Login page opens. 3. Select maas-spectrum, when prompted to select host machine. 4. Ensure that the SpectroSERVER status is RUNNING. 5. Click File, Select Host Machine from the Spectrum Control Panel menu bar. 6. Select maas-ss, when prompted to select host machine. 7. Ensure that the Spectrum SERVER status is RUNNING. You have verified that SpectroSERVER is deployed and running on the maas-spectrum and maas-ss machines. Verify Alarm Notifier Execution on CA Spectrum Main Landscape Server Restart the server and then verify that the alarm notifier process is executed. Chapter 3: Monitoring Services Deployment 35

36 Verify Deployment Follow these steps: 1. Start the Windows Task Manager and click the Processes tab. 2. Locate the process Image Name AlarmNotifier.exe. 3. Confirm that the Command Line includes CMDB.Synch.alarmrc. Note: The alarm notifier is executed only if the SpectroServer process is executed. 4. If the alarm notifier is not executed, do the following steps: a. Log in to Spectrum Main Landscape Server (MaaS-Spectrum) with the user name as Spectrum. b. Open the command prompt, and navigate to {Spectrum installation directory}\notifier directory. c. Execute the following command in a command prompt: AlarmNotifier -r CMDB.Synch\.alarmrc d. Close the command prompt. You have verified that the alarm notifier process is executed on the main landscape server. Verify CA Spectrum OneClick To verify the deployment, log in to the virtual machine where the CA Spectrum OneClick is deployed. Follow these steps: 1. Log in to the virtual machine with administrator credentials. 2. Click Start, All Programs, CA, and then start CA Spectrum OneClick Console. The CA Spectrum OneClick Login page opens. 3. Log in to the application with administrator credentials. The CA Spectrum OneClick Home page opens. 4. Review maas-spectrum and maas-ss under My CA Services. They appear green when viewing in OneClick. You have verified that the CA Spectrum OneClick server is deployed. 36 Monitoring Service Implementation Guide

37 Verify Deployment Verify CA Service Operations Insight To verify the CA Service Operations Insight deployment, do one of the following: Log in to the maas-soi machine where CA Service Operations Insight is deployed, or Type the URL: If you log in to the maas-soi machine, follow these steps: 1. Log in to the maas-soi machine with the administrator credentials. 2. Click Start, All Programs, CA, Service Operations Insight, and then start CA Service Operations Insight User Interface. If you log in from the URL, follow these steps: 1. On the CA Service Operations Insight web console log in to the system with administrator cerdentials. 2. Click the Administration tab. 3. Verify that the Spectrum Connector status is online, from Administration, Connector Configuration, MaaS-SOI, Chapter 3: Monitoring Services Deployment 37

38

39 Chapter 4: Post Deployment Tasks for Monitoring Service This section describes the tasks that you must perform after you deploy and verify the Monitoring Service. Monitor CA CSDP Servers The service provider administrator adds CA CSDP servers for the Monitoring Service before offering the service to customers. The servers help to monitor the services. If the system detects a fault, it raises an alarm. The service provider attends to the alarm and takes corrective actions. The service provider creates a customer, and adds a support department and region. The service provider subscribes the newly created customer to the monitoring service and adds the components listed in the table. To add the components, use the Add Object offering from the service portal. Navigate from Home, Requests, My Services, CA_Monitoring Services, to Add Object. The following table lists the components for CA CSDP. You can reference the table when adding the servers to the Monitoring Service. Component Name Hostname SQL Active Directory Server CA SiteMinder CA Embedded Entitlements Manager CA Service Catalog Server CA SDM CA Process Automation CA Spectrum oss-sql1 oss-sql2 oss-dc oss-sso oss-eem1 oss-eem2 oss-sc1 oss-sc2 oss-sdm1 oss-pam1 oss-pam2 maas-spectrum maas-oneclick Chapter 4: Post Deployment Tasks for Monitoring Service 39

40 Set the Password for Bulk Upload of Users Component Name CA Service Operations Insight CA Business Intelligence Hostname maas-soi oss-sdm2 Set the Password for Bulk Upload of Users To upload users in bulk, set the right password. Follow these steps: 1. Log in to CA Process Automation Manager. 2. Click the Library tab. 3. Expand Project Austin, Util. 4. On the right-hand side, right-click Bulk_Upload_UserDS and click Edit. 5. Click Check Out. 6. Enter as the Value for PAM_Host_Password. 7. Click Check In. The password is set and you can upload users in bulk. Change IP address of MaaS-NMSCluster in CA Spectrum After you deploy the monitoring service, you must change the configuration of the IP address of MaaS-NMS Cluster in CA Spectrum. Follow these steps: 1. Launch the One-Click console. 2. Expand maas-spectrum. 3. Expand Universe. 4. Select MaaS-NMSCluster. 5. On the right-hand side, in the Component Detail section, click the Information tab. 6. In the Network Address field, click Set and enter the IP Address assigned for the MaaS-NMSCluster while deploying the CA Nimsoft cluster. The IP address is changed. 40 Monitoring Service Implementation Guide

41 Validate IP Address on CA Nimsoft Central Validate IP Address on CA Nimsoft Central CA Nimsoft resets the security as soon as the IP address is changed. To reset the security settings related to the IP address, do the following tasks: Disable IP Validation in CA Nimsoft Central (see page 41) Settings to Ignore IP Validation (see page 41) Deactivate and Activate the Server Probe (see page 42) Disable IP Validation in CA Nimsoft Central After deployment disable the IP validation in CA Nimsoft Central. Follow these steps: 1. Log in to Nimsoft Infrastructure Manager as Administrator. 2. Under list of hubs and robots on the left-hand pane, select the hub robot for which the IP has changed. 3. Under list of probes on the right-hand pane, select the HUB Probe. 4. Right-click the probe and click Configure. 5. Select the Disable IP Validation check box, in the General tab, and click OK. The IP validation is disabled. Settings to Ignore IP Validation You can ignore the IP validation. Follow these steps: 1. Log in to Nimsoft Infrastructure Manager as an Administrator. 2. Under list of hubs and robots on the left hand pane, select the hub robot for which the IP has changed. 3. Under list of probes on the right hand pane, select the HUB probe and press Ctrl+P. 4. From the drop-down, select the command: hubsec_setup_put key: ignore_ip value: yes. Chapter 4: Post Deployment Tasks for Monitoring Service 41

42 Create Access Control Lists in CA Nimsoft 5. Click the Send command request icon. 6. To verify that the IP validation is disabled, select the command: hubsec_setup_get Under the key enter the value: ignore_ip The IP validation is set to ignore. Deactivate and Activate the Discovery Server Probe After you disable IP validation and set IP validation to Ignore, you must deactivate and then activate the discovery_server probe. Follow these steps: 1. Open CA Nimsoft Infrastructure Manager. 2. Click MaaS-Central-Robot. 3. Under list of probes on the right hand pane, select the discovery_server probe. 4. Right-click the probe and click De-activate. 5. Right-click the probe and click Activate. The discovery server is set to use the new IP address. Create Access Control Lists in CA Nimsoft You create access control lists to provide the LDAP group with permissions. Follow these steps: 1. Log in to MaaS-UMP machine through RDP (mstsc), with the following credentials: User Name: Administrator Password: 2. Click Start, All Programs, Nimsoft Monitoring, and then open Infrastructure Manager. 3. (Optional) If you receive a security initialize message, select yes and enter the following credentials: User Name: Administrator Password: Austin@ Navigate to Security, Manage Access Control List. 42 Monitoring Service Implementation Guide

43 Create Access Control Lists in CA Nimsoft 5. Click New, and enter a role from the Access Control and LDAP Group table. 6. In the Copy Settings From field, enter a role. For example, Operator. 7. Click OK. The operator receives all the permissions. 8. Click Set LDAP Group, select the LDAP Group, grant permissions to the group, and copy roles from, as listed in the Permissions for Access Control table, and click OK. Access Control and LDAP Group Lists Listed are the access control list (ACLs) and the LDAP groups. ACL Name LDAP Group Permissions Copy Settings From SP_Admin Service Provider Administrator SP Admin Superuser SP_AM SP_BRM SP_CM SP_DM SP_FM SP_IM SP_ISM SP_OP SP_PM SP_RFG SP_SLM Service Provider Availability Manager Service Provider Business Relationship Manager Service Provider Configuration Manager Service Provider Demand Manager Service Provider Financial Manager Service Provider Incident Manager Service Provider Information Security Manager Service Provider Operations Manager Service Provider Problem Manager Service Provider Request Fulfillment Group Service Provider Service Level Manager Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Other SP Roles Operator SP_AM SP_BRM SP_CM SP_DM SP_FM SP_IM SP_ISM SP_OP SP_PM SP_RFG SP_SO Service Provider Service Owner Other SP Roles SP_SLM SP_SR Service Provider Support Rep Other SP Roles SP_SO Chapter 4: Post Deployment Tasks for Monitoring Service 43

44 Create Access Control Lists in CA Nimsoft ACL Name LDAP Group Permissions Copy Settings From SP_TM Service Provider Test Manager Other SP Roles SP_SR Customer_Adm in <none> Customer Admin SP_Admin Customer_User <none> Customer_User SP_Admin Customer_Mon itor <none> Customer Admin SP_Admin Permissions for Access Control Listed are the permissions for the LDAP group. Permission SP Admin Other SP Roles Customer Admin Customer User Accept Yes Yes Yes Yes Acknowledge Yes Yes Yes Yes Alarm Details Yes Yes Yes Yes Alarm History Yes Yes Yes Yes Alarm Management Yes No Yes Yes Assign Yes No No No Dynamic Views States Yes Yes Yes Yes Invisible Alarms Yes No No No Reassign Yes No No No Unassign Yes No No No Automation - Change configuration items Automation - Create and Modify workflows Automation - View Items Yes No No Yes Yes No No Yes Yes Yes Yes Yes Dashboard Design Yes No No No Dashboard Download Yes No No No Dashboard Upload Yes No No No 44 Monitoring Service Implementation Guide

45 Create Access Control Lists in CA Nimsoft Permission SP Admin Other SP Roles Customer Admin Customer User Discovery Yes No No No Dynamic Views Yes Yes Yes Yes Web Publish Yes No No No Archive Management Yes No No No Basic Management Yes No No No Distribution Yes No No No Extended Security Yes No No No License Management Yes No No No Maintenance Mode Yes No No No Manage ACL Yes No No No Manage Profiles Yes No No No Management Tools Yes No No No Modify Profiles Yes No No No Portal Administration Yes No No No Probe Configuration Yes No No No Program Options Yes No No No User Administration Yes No No No Execution Level1 Yes No No No Execution Level2 Yes No No No Execution Level3 Yes No No No Account Administration Yes No No No Alarm Summary Yes Yes Yes No Change Password Yes No No Yes Custom Dashboards Yes Yes Yes Yes Custom Reports Yes Yes Yes Yes Dashboard Designer Yes No No No Dashboard Publish Yes No No No Chapter 4: Post Deployment Tasks for Monitoring Service 45

46 Create Access Control Lists in CA Nimsoft Permission SP Admin Other SP Roles Customer Admin Customer User Default Customization Discovery Management Yes No No No Yes No No No Discovery Pie Yes Yes Yes No Dynamic Views Dashboards Dynamic Views Reports Yes Yes Yes Yes Yes Yes Yes Yes Report Designer Yes Yes No No Unified Reports Yes Yes Yes Yes User Customization Yes Yes Yes Yes User Monitoring Yes Yes No No QoS Access Yes Yes Yes Yes SLM Admin Yes No No No SLM View Yes Yes Yes Yes SLO Access Yes Yes Yes Yes Cloud UE Monitor Yes Yes Yes Yes List Designer Yes No No No List Viewer Yes Yes Yes Yes NetFlow Yes Yes Yes Yes Report Scheduler Yes Yes Yes Yes Service Desk Yes Yes Yes Yes USM Automatic Robot Installation Yes Yes Yes Yes USM Basic Yes Yes Yes Yes USM Edit Monitoring Templates USM Group Modification USM Modify Individual Monitors for Computer Systems Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 46 Monitoring Service Implementation Guide

47 Apply License to the CA Nimsoft Regional Hub Permission SP Admin Other SP Roles Customer Admin Customer User USM Self Service Monitoring Yes Yes Yes Yes Web Service Yes No No No Apply License to the CA Nimsoft Regional Hub During the deployment the IP address is changed. The change results in clearing the CA Nimsoft License in the regional hub. To enable the regional hub, copy the license information from the central hub and apply it to the regional hub. Follow these steps: 1. Log in to CA Nimsoft Infrastructure Manager as an administrator. 2. Select MaaS-Central-Robot in the Console. Chapter 4: Post Deployment Tasks for Monitoring Service 47

48 Apply License to the CA Nimsoft Regional Hub 3. Double-click hub in the Probe column. The hub probe settings window opens. 4. Click Modify in the License Information section. 5. Copy the license content from the Nimbus Hub License field and close the wizard. 6. Select the robot for the regional hub in the Console from the CA Nimsoft Infrastructure Manager window, and select hub from the Probe column. Note: Regional hub has a dynamic host name. 7. Double-click the regional hub probe. 48 Monitoring Service Implementation Guide

49 Apply License to the CA Nimsoft Regional Hub The hub probe settings window opens. 8. Click Modify in the License Information section under the General tab. 9. Paste the license content copied in Step 5 from the MaaS-Central-Robot hub in the Nimbus Hub License wizard. 10. Click OK in the Edit License wizard and then in the Hub Settings window. The license is applied to the regional hub. 11. Select all the probes that are indicated in Red from the list of probes, right-click and select Security, Validate. The probe is enabled and the color of the probe turns green. The license is applied to the regional hub. Chapter 4: Post Deployment Tasks for Monitoring Service 49

50

51 Chapter 5: Register the Monitoring Services Monitoring as a Service (MaaS) is available to customers after deployment. By default, only the service provider administrator has rights to deploy and maintain the service. Customers can subscribe for the service after the service provider registers the service. The following deployment choices specify the size and scalability of monitoring components: Deploy Monitoring Service - Central Supports 2,500 devices and 100,000 interfaces by default. Important! The central deployment is a one-time task. The system does not allow you to redeploy the service. Deploy Monitoring Service - Regional Supports an extra 2,500 devices and 100,000 interfaces. To add more devices and interfaces to the centrally deployed resources, add regional deployment. You provide the deployment details for a central deployment using the service portal form to register the service. First select the central deployment option. After you deploy the service centrally, select the regional deployment option to deploy the services in one of the regions. The service portal lets you deploy the monitoring services automatically or manually. Note: This release of Monitoring Services supports only manual deployment. Important! Do not abort the CA Process Automation flow while deploying the monitoring service or registering tenants. Central Deployment You register a service for central deployment using the service portal. Follow these steps: 1. Log in to the service portal. 2. Click Requests, Service Administration, Register Services, CA_Monitoring Service_1.1, Deploy Monitoring Service - Central. Chapter 5: Register the Monitoring Services 51

52 Regional Deployment By default, the Deploy Monitoring Service-Central form opens with the Automatic Deployment check box as enabled. Important! The Deploy Monitoring Service-Central is a one-time task. The system does not allow you to redeploy the service. Note: This release of Monitoring Services supports only manual deployment. 3. Clear the Automatic Deployment check box, to enable manual deployment. 4. Click Submit on the Deploy Monitoring Service-Central form. You receive an with a task for the service provider. 5. Open the task and provide the details of CA Service Operations Insight, CA Spectrum, and Nimsoft in the forms. 6. Click Finish. The services are activated on CA CSDP. You have now deployed the service. You receive an that describes the type of deployment requested. The contains a link that directs you to CA Process Automation to complete the task. Regional Deployment To add more devices and interfaces to the centrally deployed resources, add a regional deployment. Note: If the VMs that are part of a regional deployment appliance are placed behind a Firewall, follow specific considerations for the servers. For the Spectrum server: See the chapter Communication Across Firewalls in the Distributed SpectroSERVER Environment, in the CA Spectrum Distributed SpectroSERVER Administrator Guide. For the Nimsoft server: See the chapter Working with Firewalls and DMZs, in the CA Nimsoft Server Installation Guide, Release The information helps you to set up the connection between the regional Hub and the central Hub. Follow these steps: 1. Log in to the service portal. 52 Monitoring Service Implementation Guide

53 Regional Deployment 2. Click Requests, Service Administration, Run Book Automation, CA_Monitoring Service_1.1, Deploy Monitoring Service - Regional. By default, the Deploy Monitoring Service-Central form opens with the Automatic Deployment check box as enabled. Note: This release of Monitoring Services supports only manual deployment. 3. Clear the Automatic Deployment check box, to enable manual deployment. 4. Complete the remaining form fields, and click Submit. You have now deployed the service. You receive an that describes the type of deployment that is requested. The contains a link that directs you to CA Process Automation to complete the task. Prerequisite for Regional Deployment The service provider configures the regional deployment. After a regional deployment of the monitoring service, CA Spectrum and CA Service Operations Insight require specific configurations. A tenant can subscribe for that particular region after the necessary configurations are complete. The configurations that you require are: Deployment Checklist LDAP Configuration (see page 54) Load the CA Spectrum Landscape Content (see page 54) Add the Landscape to Spectrum Main Location Server (see page 55) Install the Catalyst Connector (see page 62) Set the Connector Controls (see page 62) Chapter 5: Register the Monitoring Services 53

54 Regional Deployment LDAP Configuration To use the central hub as an LDAP proxy, change the LDAP configuration in the regional hub. Follow these steps: 1. Log in to CA Nimsoft Infrastructure Manager and navigate to the Regional Hub. 2. Right-click the hub probe on the regional server and select Configure. 3. Click Settings on the General tab and go to the LDAP tab. 4. Make the following changes: a. Select the Nimsoft Proxy Hub option. b. Check the box for Proxy LDAP Authentication and click Refresh. c. Proxy Hub = /MaaS-Central-Domain/MaaS-Central-Hub/MaaS-Central-Robot/hub d. Proxy Retries = 3 (default) e. Authentication Sequence = LDAP > Nimsoft (default) f. Proxy Timeout = 10 (default) 5. Click OK. 6. Click Apply, then OK. 7. Restart the regional hub. You have successfully configured the LDAP to use Central Hub as an LDAP Proxy. Load the CA Spectrum Landscape Content During a regional deployment, after you deploy the Open Virtualization Format (OVF), load the content to CA Spectrum landscape to configure CA Spectrum and CA Service Operations Insight. All procedures must be executed on the CA Spectrum landscape platform. Perform the following tasks before you add the content: Copy the C:\SpectrumDSSContent\spectrum-ls Content folder, that is located in MaaS-Spectrum host to local directory in Spectrum Landscape Server newly created. This directory is referred to as the Spectrum Content Directory. Install Spectrum Landscape, if the OVF is deployed and the landscape is installed. Log on to the CA Spectrum server with administrator rights. 54 Monitoring Service Implementation Guide

55 Regional Deployment Add the Landscape to Spectrum Main Location Server During a regional deployment, the CA Spectrum landscape and the CA Nimsoft regional hub are deployed. The service provider loads the spectrum content manually during the regional deployment. You must establish communication between the servers: Landscape server (LS) Spectrum main location server (MLS) The main location server monitors the landscape server. You manually set up the monitoring process. Follow these steps: 1. Log in to the CA Spectrum OneClick application using the following login credentials: User name: Spectrum Password: Austin@ Click the Administration tab, in the CA Spectrum Oneclick page. 3. Click Landscapes. A list of the currently attached spectrum landscapes opens in the Monitored landscapes page. 4. (Optional) If the new landscape does not appear in the list, enter the host name of the landscape in the Landscape Name field. 5. Verify that the Parent Connection Status column displays Connection established. 6. (Optional) If the connection is not established, perform the following steps to establish the connection: a. Log in to the regional landscape location server using the Spectrum login credentials. b. Click Start, Spectrum Control Panel, on the landscape server. c. Select the landscape name as the host name. Chapter 5: Register the Monitoring Services 55

56 Regional Deployment The Spectrum Control Panel opens with the status as Inactive. d. Click Host Security, and ensure that the Server list displays a plus sign (+) only. e. Click Start SpectroServer, and wait until the status changes to Running. 7. Create two users in the CA Spectrum Landscape. a. Click Control, Users, from the menu in the Spectrum Control Panel. b. Click Create, on the Users page. User name: spectrum Note: The user name field is case-sensitive. Password: Austin@123 User name: Administrator Note: The user name field is case-sensitive. Password: Austin@123 Add New CA Spectrum Model Types c. In the CA Spectrum Oneclick Administration window, on the Monitored Landscapes page, click Refresh. d. Verify that the Parent Connection Status column displays Connection established. You have linked the landscape to the main location server. After you add the landscape, proceed with loading the content in CA Spectrum. Add new model types to CA Spectrum landscape to create models. Follow these steps: 1. Click Start, Spectrum Control Panel as the Initial Spectrum user. Note: If prompted for a server, select the server where you want to add the model. 2. Click Stop SpectroSERVER. 3. Click Yes, in the confirmation dialog. Note: Wait until the status is INACTIVE before proceeding. Leave the Spectrum Control Panel open. 4. Copy Model.Attribute.Extensions.xml to the SS folder. a. Navigate to the model_extension directory in the Spectrum Content Directory. b. Select and copy the Model.Attribute.Extensions.xml file. c. Navigate to the {SpectrumInstallation directory}\ss folder and paste the Model.Attribute.Extensions.xml file. 56 Monitoring Service Implementation Guide

57 Regional Deployment Add New Event Processing 5. Use dbtool to import Model.Attribute.Extensions.xml a. Open a command prompt. b. Change to the SS directory under the Spectrum root directory. c. Run..\SS-Tools\dbtool import Model.Attribute.Extensions.xml. 6. Return to the Spectrum Control Panel and click Start SpectroSERVER. Note: Wait until the status is RUNNING. The status may take several minutes to change. The new CA Spectrum model type is added. You create an event processing and add it to CA Spectrum. Follow these steps: 1. Copy the CMDB.Synch.evd to the custom/events/eventdisp. a. Navigate to the custom\eventdisp directory in the Spectrum Content Directory. b. Open the CMDB.Synch.evd file in a text editor. c. Select all the contents and copy them to the clipboard. d. Close CMDB.Synch.evd. e. Navigate to the Spectrum root directory. f. Navigate to the custom/events folder. Note: If an EventDisp file is not available under the custom folder, create it. g. Open the EventDisp file in a text editor. h. Navigate to the bottom of the file and paste the copied contents of the CMDB.Synch.evd file. i. Save and close the EventDisp file. 2. Copy Nimsoft Alarm Events to the custom/events/eventdisp file. a. Navigate to the custom\events directory in Spectrum Content Directory. b. Select and copy CsEvFormat, CsPCause, gen_app_gw, and the MaaS folders. c. Navigate to the Spectrum root directory. Chapter 5: Register the Monitoring Services 57