What is the workflow for setting up M&R Smarts SolutionPack?
7.x
Before you can view notifications or historical event reports from the M&R Report Library, you must install and configure the following:
The order in which you install Smarts SAM and M&R does not matter. But, the licensing and configuration of both products must be completed and the services for both products must be installed and running before you install the SolutionPack for Smarts.
This article covers the process and requirements to prepare M&R for deploying the Smarts SolutionPack after the initial installation is complete.
The following sections explain how to set up and assign non-administrator roles and users of the Smarts SolutionPack.
Setting role restrictions for non-administrator users of SolutionPack for Smarts
You can add non-administrator user roles such as oper (operator) or profiles in your Presentation SAM server. To configure these roles, you must set role restrictions after installing the SolutionPack for Smarts. This is done as follows:
SAM user profile mapping and M&R role-based access
After you set up the user profiles and assign them to roles in M&R, the administrator must associate those profiles and roles with users who need to access both Service Assurance Manager (SAM) Consoles and the M&R User Interface.
Administrator profile behavior
The M&R administrator role is mapped to the Smarts Admin profile when the SolutionPack for Smarts is installed.
User profile behavior
The administrator can assign a SAM profile to an M&R non-administrator user from Administration > Modules > Smarts.
Viewing notifications from the M&R User Interface
You can view notifications coming from the Presentation SAM server in the M&R User Interface.
Note 1:
The EMC M&R Tomcat server is the front end of the EMC M&R deployment and has web address http://<FQDN or IP of EMC M&R front end host>:58080. Use either IP or FQDN consistently when installing the solution pack and configuring the Smarts Service Assurance Managers runcmd_env.sh. That is, do not enter an IP address as the SM_CAS_SERVER parameter setting in the runcmd_env.sh file and then use an FQDN login for EMC M&R. Choose one convention and use it consistently.
Note 2:
The Smarts EDAA is the Tomcat server that points to the Smarts Service Assurance Suite Broker. In a default deployment the Smarts EDAA is installed alongside the Smarts Service Assurance Manager as the service smarts-tomcat and runs on port 8080. The web address would be http://<FQDN or IP of Smarts Service Assurance Manager>:8080.
Note 3:
The SolutionPack for EMC Smarts does not collect every class and instance that exists in the Smarts domains. It selects "top level" classes like Routers, Switch and some of their underlying components.