Notifications are blank
search cancel

Notifications are blank

book

Article ID: 333114

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

On a fresh install of M&R connecting to smarts notifications and topology data are blank.


Environment

M&R -7.x

Cause

  • This was caused by a mismatch in tomcat port between M&R and Smarts. M&R is set up by default to use SSL port 58443.
  • In this instance the customer did not wish to use SSL and had set up 58080 on the smarts side.

Resolution

 

  • If the customer does not wish to use SSL they must adjust the server.xml on the M&R side:
    • From the M&R Front end modify:  /opt/APG/Web-Servers/Tomcat/Default/conf/server.xml file:
  • Locate and remove the entry redirectPort="5###3"

    Before:
     
<Connector port="5###0" protocol="HTTP/1.1"
connectionTimeout="20000"
compression="2048"/>
redirectPort="5###3" URIEncoding="UTF-8" />
  • After you remove the entry it will look like this:
<Connector port="5###0" protocol="HTTP/1.1"
connectionTimeout="20000"
compression="2048"
URIEncoding="UTF-8" />
  • Then locate the following line and comment it out

    Before
<Valve className="com.watch4net.apg.v2.gui.tomcat.ForceSSL" />

after

<!-- <Valve className="com.watch4net.apg.v2.gui.tomcat.ForceSSL" /> -->
  • Then restart the tomcat service.
  • This can be done via the GUI in centralized management

 

 





  • or via CLI from the front end server
/opt/APG/bin/mange-modules.sh service restart tomcat Default
  •  Clear the browser cache, and then log in using HTTP.
  • If the customer wishes to use SSL:
1. Navigate to Centralized Management and expand SolutionPacks>Infrastructure from the left hand tree then Select EMC smarts.
2. Click the pencil icon by the 'Reports SolutionPackBlock'
3. Expand Tomcat Configuration and choose 'Add a new Tomcat configuration' in the drop down box.
4. Click the checkbox for 'HTTPS Enabled for EMC M&R and Smarts'
5.  Ensure the FQDN is specified for the Tomcat server and that it matches the SM_CAS_Server entry on SAM runcmd_env.sh file.
6. Verify that the entry in Smarts EDAA hostname or IP address field matches the SM_TOMCAT_SErver in the Presentation SAM runcmd_env.sh
7. Verify the ports default EMC M&R tomcat port number 58443. Default EDAA port number 8443
8.Verify remaining fields and click 'Reconfigure'
 



  • Then continue with SSL certificate generation import and export steps.
  • The changes will not take effect until the Tomcat servers are restarted in both SAM and EMC M&R.