Unsolved
This post is more than 5 years old
18 Posts
0
2332
Importing WLA Data from ControlCenter
Hi All,
I'm currently in the process of setting up our ProSphere environment.
We want to import WLA data from controlcenter, so I took the Administration Manual and read the Migration from ControlCenter chapter.
Added a data source which is pointing to the host that is running the WLA archiver process.
Checked on the WLA host if port 30103 is listening:
TCP 0.0.0.0:30103 0.0.0.0:0 LISTENING 7944
[WlaHttpServer.exe]
Checked for any firewalls:
Windows Firewall is turned off.
Clicked import.
Since then it is displaying "Pending".
There is only one thing I can think of why it is still on pending is that ProSphere does not have all hosts discovered that are in the history of the WLA.
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
November 29th, 2012 07:00
Hi Mamer,
Prerequisites for WLA Archiver Data Source import
ProSphere will ignore any objects not discovered when importing ControlCenter WLA data so that should not be the cause of the issue
How long has the it been in pending state?
If you press the refresh button on the top right of the UI do you get an updated message or if you close the Import Performance Data from Controlcenterr UI and again select Import Performance Data does the state of the job update?
As a note at the bottom of the Import Performance Data from ControlCenter is the follow message "Click here for tips on how to view the status of the imported CLS" if you click here page that opens has the following details " ProSphere provides URIs to troubleshoot importing EMC ControlCenter Performance Manager data into ProSphere. Follow this procedure to view the status of the specific imported job details for the CIs and troubleshoot. "
for example open a browser and type the URI http://{ProsphereSRM servername}/srm/system/migration/jobs/performance in the address bar to view the list of WLA Archiver Data Source or WLA hosts and press Enter.
Within the feed you will see an entry similar to the following look for the FQDN of your WLA agent host.
What is the and tags displaying in the feed?
http://schemas.emc.com/srm/namespace/SRM/1.0 "> 1 ECCWLAhost.emc.com 30103 true 2012-11-29 15:19:21.599 2012-11-29 15:19:29.184 7secs Completed Failed Not able to connect to the WLA Archiver agent 0
/srm/system/migration/jobs/performance/ECCWLAhost.emc.com
2012-11-29T15:23:55.78Z
Regards
Conor
mamer1
18 Posts
0
November 29th, 2012 07:00
Hi Conor,
It has been in a pending state since I clicked Import more then a week ago.
It says pending.
Not much as you can see.
I also tried to add the host on IP address, but then it says this, which for me says that DNS is working properly:
Regards,
Martijn
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
November 29th, 2012 08:00
Hi Martijn,
The feed does not give any details for the issue and I am assuming the feed for /srm/system/migration/jobs/performance/ecprdc02.rdc.local will be the same.
Please open an SR with support attaching the ProSphere logs from Admin > System > Manage logs.
The health of the services on a ProSphere VMs as reported by mon is available from this URL.
https://{hostname}/cgi-bin/mon.cgi
Confirm all service are Green on the VMS expect the srm-msa-config-proxy service its disabled so yellow.
Regards
Conor
mamer1
18 Posts
0
November 30th, 2012 01:00
Oh...![](https://prod-care-community-cdn.sprinklr.com/community/687062f5-603c-4f5f-ab9d-31aa7cacb376/ReImportingWLADatafromControlC-bd9834f6-4392-4344-92e7-f34544afd134-48077700)
I will make an SR then and attach the logs.
Thanks,
Martijn
mamer1
18 Posts
0
November 30th, 2012 01:00
I think this can be the problem...
srm_msa_config_proxy is disabled.
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
November 30th, 2012 01:00
Hi Martijn,
the srm-msa-config-proxy is disabled as it not used by 1.6
Regards
Conor