HPE GreenLake Administration
- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: Insight RSA Service Heath Communication Failur...
Insight Remote Support
1833008
Members
2491
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2010 12:51 AM
11-17-2010 12:51 AM
Insight RSA Service Heath Communication Failures
I have Insight RSA 5.50 installed on a Windows 2008 R2 Server (with SIM 6.2).
On the Service Heath page, it reports some communication failures:-
1. Windows 2003 R2 Server - WBEM communication failure. (SNMP ok)
2. SIM CMS server - ELMC communication failure. (SNMP and WBEM ok).
How do I correct these errors? The server that has the WBEM failure is identical to three other servers which are ok. Also, I can browse to the system page of this server and the WBEM information is showing ok.
On the Service Heath page, it reports some communication failures:-
1. Windows 2003 R2 Server - WBEM communication failure. (SNMP ok)
2. SIM CMS server - ELMC communication failure. (SNMP and WBEM ok).
How do I correct these errors? The server that has the WBEM failure is identical to three other servers which are ok. Also, I can browse to the system page of this server and the WBEM information is showing ok.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2010 12:32 PM
11-18-2010 12:32 PM
Re: Insight RSA Service Heath Communication Failures
Just after you started up the WEBES desta_service it could be that you can get such a Health state.
WBEM 1: Are you able to connect to port 5989 from your management server? Check the SIM Credential for this server (From the System page of the server->Tools Tab->System credential). If you do not see credential for the WBEM/WMI communication you should check for possible firewalls or you had the wrong WBEM credential.
ELMC 2: Perhaps your wccproxy Service is no longer running. You can check if the service is running with the cmd command "wccproxy status". Even a better test is "wccproxy test" this command will trigger the hole alarming chain. A test event is sent to HP an closed at HP.
If you have a lot of servers you should open a HW call at HP explaining that your RSA is not working correct. Remote support is now shipped together with a log file collection utility which allows HP support to analyze the case much faster as in the past.
WBEM 1: Are you able to connect to port 5989 from your management server? Check the SIM Credential for this server (From the System page of the server->Tools Tab->System credential). If you do not see credential for the WBEM/WMI communication you should check for possible firewalls or you had the wrong WBEM credential.
ELMC 2: Perhaps your wccproxy Service is no longer running. You can check if the service is running with the cmd command "wccproxy status". Even a better test is "wccproxy test" this command will trigger the hole alarming chain. A test event is sent to HP an closed at HP.
If you have a lot of servers you should open a HW call at HP explaining that your RSA is not working correct. Remote support is now shipped together with a log file collection utility which allows HP support to analyze the case much faster as in the past.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP