Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM 9.1/9.2: Slow initial broker/domain connection time seen in WebConsole and Business Dashboard after upgrading from earlier Smarts SAM version (372986)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3066Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After upgrading to Smarts Service Assurance Manager (Smarts SAM) 9.1 or 9.2, the initial connection of Smarts SAM Business Dashboard or Smarts SAM Web Console to the Smarts broker and domains is slow

Cause

The above issue has been found to occur when there is a lack of Entropy on the system. Entropy is required by the Transport Layer Security (TLS) protocol used by Smarts 9.1 and later applications, and a lack of Entropy in the system will cause a delay in establishing a TLS session, resulting in a slow broker/domain connection. Smarts Foundation software started using the industry standard TLS protocol as the inter-process communication protocol for EMC Smarts applications. TLS replaces the Smarts proprietary IPC protocol in Smarts 9.1 and later.

Resolution

If you encounter this issue, you can do either of the following:

Disable TLS

Set the java "egd" parameter on the system where the browser runs

The following sections explain the requirements, considerations, and steps for each of these options.

Disabling TLS
Disabling TLS should be done in accordance with the local network security policies. Disabling TLS can be done as follows:

On the machine where the Smarts tomcat server is started, open the webconsole.properties file in the following directory:

<BASEDIR>/smarts/tomcat/webapps/webconsole

Add the following line (or set existing parameter to "true"):

# Flag to disable TLS
com.smarts.no_tls=true

Save and close the webconsole.properties file.

Restart tomcat after this change is made.

Setting the java "egd" parameter on the system where the browser runs
Setting the "java.security.egd" parameter must be done on every Linux/Solaris machine where connection slowness is observed in the browser. There are a few ways to do this, but updating the java.security file in the JRE/JDK should resolve the issue. This is done as follows:

On the Linux/Solaris machine where connection slowness is observed, open the java.security file in the following location:

<JDK/JRE>/lib/security/java.security

Find the following line:

securerandom.source=file:/dev/urandom

Change the above line to the following:

securerandom.source=file:/dev/./urandom

IMPORTANT! The extra "./" in the above file path is required. Without it, the "file:/dev/urandom" path is sometimes mapped back to "file:/dev/random" (see http://bugs.sun.com/view_bug.do;?bug_id=6521844).

Save and close the java.security file.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant