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

SRM/Watch4net: How to configure Solutions Enabler in client/server model in SRM or Watch4net environment (332130)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 7211Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

This article explains how to set up Solution Enabler in Client/Server model on VMAX collector host for SRM or Watch4net

The following error message may be seen in SRM or Watch4net collecting.0.0.log file:

SEVERE   -- [2014-02-14 14:08:58 IST] -- AbstractXmlJob::b(): VMAX-BCVREPLICAS: 000294900920:net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException:

Premature end of file.

at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:418)

at net.sf.saxon.event.Sender.send(Sender.java:214)

at net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:30)

at com.watch4net.apg.v2.collector.plugins.xmlcollector.engine.NuxXmlJob.a
(SourceFile:377)    at com.watch4net.apg.v2.collector.plugins.xmlcollector.engine.AbstractXmlJob.b
(SourceFile:131)    at com.watch4net.apg.v2.collector.plugins.xmlcollector.engine.AbstractXmlJob.call
(SourceFile:30)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

at java.lang.Thread.run(Thread.java:662)

Caused by: org.xml.sax.SAXParseException: Premature end of file.

at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)    ... 15 more

---------

While setting the client/server model in SRM or Watch4net, if the Environment variables are not set persistent then if the machine reboots the Environment variables are lost and VMax discovery may not work . The user has to set the environment variables manually every time

VMAX Report information in SRM is not up-to-date

VMAX Discovery does not complete

Cause

The above issue indicates that the client is unable to report the Symmetrix arrays. List settings should be verified on both the server and client.

Resolution

To Prepare for EMC Vmax Discovery in SRM Suite , Identify the information required to support data collection before installing the SolutionPack for EMC VMAX and perform the necessary pre-configuration.

SRM Suite requires EMC Solutions Enabler to collect array topology details for VMAX arrays;

optionally SRM Suite requires UniSphere for VMAX and/or the EMC SMI-S Provider to collect array performance details. If both EMC Solutions Enabler and EMC SMI-S Provider are present, they must be on the same host.

As part of this , the following System environment variables should be set on the client host attached to the VMAX

-these env. variables must be set as persistent variables in order to be preserved across client Host reboots :

SYMCLI_CONNECT=SYMAPI_SERVER

SYMCLI_CONNECT_TYPE=REMOTE

The step-by-step procedure to configure Solutions Enabler in Client/Server model is as follows:

On the server, check the security level in symapi\config\options file. Remove # (comment tag) from the security mode in the environment netcnfg file. The following is an example for NONSECURE mode.

#SYMAPI_SECURITY_LEVEL = SECURE

SYMAPI_SECURITY_LEVEL = NONSECURE

On the client, open the options file (SYMAPI\config\options and add "apg storapid all" at the end of the file.

Set environment variables according to the operating environment:

Windows: Run the following SYMCLI commands to set the server's environment variables:

set SYMCLI_CONNECT_TYPE=REMOTE
set SYMCLI_CONNECT=SYMAPI_SERVER
symcfg list -service

To add in the System Environment Variable, press "Windows Key + Pause">Click Advanced system Settings>Advanced> Environment Variables>System variables>New>
"SYMCLI_CONNECT_TYPE" and "SYMCLI_CONNECT" will be variables and "REMOTE" and "SYMAPI_SERVER" will be values respectively.

Linux: Run the following commands:

Login to the collector host as root and navigate to \etc folder.
Then vi to etc/environment file and enter the Variables as below

SYMCLI_CONNECT_TYPE=REMOTE
SYMCLI_CONNECT=SYMAPI_SERVER

Save and quit vi.

Run the below commands :

export SYMCLI_CONNECT_TYPE=REMOTE

export SYMCLI_CONNECT=SYMAPI_SERVER
symcfg list - service

Edit symapi/config/netcnfg file and add the Solutions Enabler server hostname and IP address as below

SYMAPI_SERVER  -  TCPIP example.emc.com 10.x.x.x 2707  NONSECURE

Use symacl list to check user authorization on Symmetrix array. Skip this step if Symmetrix authorization is disabled.

Create a file named role.txt and add either of the following to the file:

assign user apg to role Monitor;
OR
assign user H:\W4NColl\apg to role Monitor;

Check the SRM Suite 3.0 Installation and Configuration Guide for more information

Related Information

Check the SYMAPI logs to find the exact host name that is accessing the Solutions Enabler server

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 - Watch4Net/M&R

Take Our Survey

Support Assistant