ViPR SRM 3.6 – Install the Virtual Appliance

Table of Contents

Virtual appliance installation overview

Learn how to install ViPR SRM as an appliance in a supported VMware environment.

Any new vApp (4VM or 1VM) installations require VMware vSphere 5.x. This includes adding a vApp VM to an existing installation.

Use the vApp deployment only for new installations. If you are upgrading, use the binary installation package to migrate to a newer release.

Do not add any VMs into the vApp other than the vApp VMs provided by EMC.

The procedures enable you to install two types of software:

Core software
A reporting solution built on a scalable architecture of distributed backends, frontends, collectors, and databases. When you install the core software platform, you establish the foundation for the suite, which provides common capabilities, functions and user interfaces available to suite users.
SolutionPack software
A software component in the suite that supports EMC and third-party storage infrastructure components. Each SolutionPack enables you to select a specific report in the UI. To learn more about the SolutionPacks that ViPR SRM supports, see the following documents:
  • EMC ViPR SRM Support Matrix
  • EMC ViPR SRM Release Notes

ViPR SRM vApps are distributed using Open Virtualization Format (OVF) files. Depending on your environment's requirements, you can use two types of OVF installations:

Four VM installation procedure
Enables you to install four VMs that are preconfigured to communicate with each other (Frontend, Primary Backend, Additional Backend, and Collector).
One VM installation option
Enables you to install any suite appliance (Frontend, Primary Backend, Additional Backend, and Collector) as a single VM. You can use this option to install a single, consolidated VM for evaluation purposes or to add additional Backend and Collector appliances to scale out the environment.
Back to Top

Installing the 4 VM vApp

You can deploy the ViPR SRM 4 VM appliance from an OVF template using a vSphere Client.

Before you begin

Procedure

  1. Open vSphere Client and connect to the vCenter Server that manages your VMware environment.
  2. Select the resource pool where you want to deploy the VMs for ViPR SRM.
  3. Select File > Deploy OVF Template.
  4. In the Source step, locate the EMC_MnR_4VM_vApp.ovf file.
    Sample file path: /opt/ovf/EMC_MnR_4VM_vApp.ovf
    Sample URL: http://myHost.emc.com/ovf/snapshot/92/EMC_MnR_4VM_vApp.ovf
  5. Click Next.
    To save time, deploy the appliance in the same local area network (LAN) that your VMware ESX/ESXi servers share. Deployment takes approximately 5 to 15 minutes. Deployment across a WAN can take 2 hours or more.
  6. In the OVF Template Details step, review the details of the loaded .ovf file, and then click Next.
  7. In the End User License Agreement step, review the license agreement. Click Accept, and then click Next.
  8. In the Name and Location step:
    1. Accept the default name (ViPR SRM) or type a Name for the appliance.
    2. Specify an Inventory Location for the appliance in your VMware environment.
    3. Click Next.
  9. Select the host or cluster where you want to run the deployed template, and then click Next.
  10. Select the destination storage for the virtual machine files, and then click Next.
  11. In the Disk Format step, select the storage space provisioning method, and then click Next.
    Option Description
    Thin-provisioned format On-demand expansion of available storage, used for newer data store file systems.
    Thick-provisioned format Appliance storage that is allocated immediately and reserved as a block.
    Note Image
    EMC recommends the Thin provisioned format option when the vApp is deployed in a high performance environment.

  12. In the Network Mapping step, select a destination network that has an IP Pool associated with it for each of the VMs, and then click Next.
  13. In the IP Address Allocation step, choose the IP allocation policy and IP protocol to use, and then click Next.
  14. In the Properties step, provide the values for each of the VMs, and then click Next.
  15. In the Ready to Complete step, review the list of properties for the appliance, and then click Finish.
    A status bar opens in the vSphere Client showing the deployment progress.
  16. After you finish deployment, in the Deployment Completed Successfully dialog box, click Close.
Back to Top

Starting the vApp

Use the vSphere client to start the vApp.

Procedure

  1. In the vSphere client, navigate to the Host and Cluster view.
  2. From the configured resource pool, find the resource pool that you selected for the appliance.
    The new appliance is listed under the resource pool.
  3. Right-click each VM, and then select Open Console.
  4. Right-click the vApp, and then select Power On.
    Each VM in the vApp is powered on. After the initial startup and module installations are complete, the login prompt displays.
Back to Top

Logging in to the User Interface

Log in to view reports or test user access.

Procedure

  1. Open a browser, and then type the URL.
    Example: http://<Frontend-hostname>:58080/APG
  2. Log in.
    1. Type the login credentials.
      The default username is admin. The default password is changeme.
    2. Click Sign In.

After you finish

You are automatically logged off after four hours.

Back to Top

Passwords

Use passwords to control access to the appliance.

If you set the appliance console password while you deployed the OVF, the password that you entered is the default password.

Passwords must conform to the following requirements.:
  • Be at least eight characters and no more than 40 characters
  • Contain at least one numeric character
  • Contain at least one uppercase and one lowercase character
  • Contain at least one non-alphanumeric character such as # or !
  • Cannot contain the single quote character (') because it is a delimiter for the password string
Note Image
These requirements do not apply to the Linux passwords.

Back to Top

Verifying if the EMC M&R platform services are running

Verify the EMC M&R platform services are running on each host by obtaining the status.

Before you begin

Ensure that you have a login with root, APG, or system administrator privileges. The user apg is the account that the EMC M&R platform application uses instead of root.

Procedure

  1. Type the command for your operating system from the bin directory of the EMC M&R platform installation:
    Operating system Command
    UNIX ./manage-modules.sh service status all
    Windows manage-modules.cmd service status all
  2. Verify that each service has a status of running in the output.

Results

Note Image
The list of available services will vary depending upon choices (Collector, Backend, Frontend, Default, or Minimal) made during installation.

Example:
* Checking 'topology-mapping-service Default'... [ running ]
* Checking 'webservice-gateway Default'... [ running ]
* Checking 'mysql Default'... [ running ]
* Checking 'alerting-backend Default'... [ running ]
* Checking 'backend Default'... [ running ]
* Checking 'collector-manager Default'... [ running ]
* Checking 'collector-manager Generic-SNMP'... [ running ]
* Checking 'collector-manager Load-Balancer'... [ running ]
* Checking 'collector-manager emc smarts'... [ running ]
* Checking 'event-processing-manager emc smarts'... [ running ]
* Checking 'tomcat Default'... [ running ]
* Checking 'task-scheduler Default'... [ running ]

Back to Top

Troubleshooting service start-up problems on UNIX

Check the log files when services do not start.

Before you begin

Ensure that you have logged in with root or APG privileges to check the log files.

Procedure

Look for log files in these /opt/APG/ directory paths.
The list of available log files will vary depending upon choices made during installation. (Collector, Backend, Frontend, Default, or Minimal installations will generate different sets of log files.)
Databases/MySQL/Default/data/[SERVER NAME].err
Backends/Alerting-Backend/Default/logs/alerting-0-0.log
Backends/APG-Backend/Default/logs/cache-0-0.log
Collecting/Collector-Manager/Default/logs/collecting-0-0.log
Web-Servers/Tomcat/Default/logs/service.log
Tools/Task-Scheduler/Default/logs/scheduler-0-0.log
Tools/Webservice-Gateway/Default/logs/gateway-0-0.log
Back to Top

Adding disk space

Add a virtual machine disk to a running system for use by suite virtual machines.

Procedure

  1. From the vSphere Console, add a new disk to a virtual machine.
  2. Select Edit Settings on the virtual machine.
  3. Click Add.
  4. Select Hard Disk, then click Next.
  5. Select Create a new virtual disk, then click Next.
  6. Specify the disk size, the provisioning type, and the location of the disk, then click Next.
  7. Specify the virtual device node (the default value should be OK), then click Next.
  8. Review the options, and then click Finish.
  9. Access a Linux login prompt. You can access a login prompt through the vSphere Console or using an SSH tool such as PuTTY.
  10. Log in to Linux.
  11. At the system prompt, type the command expand_disk.pl.
Back to Top

Configuring the user process limits for a Linux installation

Increase the user process limits for the user account to a maximum of 65534. This modification enables services to open 65534 files and 65534 processes when needed.

Before you begin

Procedure

  1. Open the /etc/security/limits.conf file.
  2. Add the following lines for the user.
    In this example, the user is apg.
    apg   hard  nofile  65534
    apg   soft  nofile  65534
    apg   hard  nproc   65534
    apg   soft  nproc   65534
    
  3. Save the file.
  4. To restart the services, type the following commands from the bin directory of the installation:
    ./manage-modules.sh service stop all
    ./manage-modules.sh service start all
  5. To verify the changes, type su apg -c 'ulimit -n -u'
Back to Top

Related Articles

Using the 1VM vApp to Scale Out the EMC ViPR SRM Environment - Describes a simple way to add backends and collectors to an existing EMC ViPR SRM base instance.

Using the Binary Installer to Scaleout the ViPR SRM Environment - Describes how to manually install a ViPR SRM solution that consists of a frontend, backend, additional backend, and one collector.

Back to Top