- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Query on IRSS
Insight Remote Support
1757033
Members
2008
Online
108858
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
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
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
06-30-2009 12:28 PM
06-30-2009 12:28 PM
Query on IRSS
Over the last couple weeks I migrated our HP-UX servers from ISEE to IRSS. I believe I did everything correctly but a couple of issues remain.
1. When we received the RAID 4Si Event error this morning the message came directly from the affected server. Upon checking the SEA and SIM I found no error messages related to that RAID 4Si Event. The IRSS Host gives no errors related to communicating with that server and the SIM sees the server as well. I can also go into Sys Mgmt Homepage and use various tools without a problem.
I also tested IRSS using the send_test_event disk_em command and it worked fine.
2. But that brings me to my next question. I have 3 servers, two are 11.23 and one is 11.11, that will not acknowledge the send_test_event test. I have several other servers that are configured in similar ways that have no issues. What I noticed was that those three servers are listed as having No Collections present. Also, servers that passed the test show their OS in the SEA while the 3 that aren’t getting the test do not.
When configuring the Managed Systems I installed the latest versions of the required software. I also changed the permissions on the sslshare directory (that worked for another server) and ran the swconfig *\ command with no errors. I even removed the Managed Systems from the SEA, reinstalled the software and then added them back. No errors but the send_test_event test still didn’t work.
The only other detail I noticed was that on some systems the the send_test_event is located at /etc/opt/resmon/lbin/ and on others it’s /opt/resmon/bin/send_test_event.
Is there a way to force collections?
3. The last issue is the least of them. We get the following error, which I read on HP forums is a bug:
Webes Health Check reported a problem at Tue, 30 Jun 2009 11:01:00 -0400
Hostname: xxxxx
Version: 1.0
Error Code: E2E
Description:Webes HeartBeat test failed to log event. Webes may not be in running state
CallStack:
Recommended Action:
Restart Webes Director or Contact HP services.
Is there a way to fix this? I tried turning the WEBES log notification off. That cut down on multiple emails but I’m still getting an email at 11am and 7pm.
Thank in advance
1. When we received the RAID 4Si Event error this morning the message came directly from the affected server. Upon checking the SEA and SIM I found no error messages related to that RAID 4Si Event. The IRSS Host gives no errors related to communicating with that server and the SIM sees the server as well. I can also go into Sys Mgmt Homepage and use various tools without a problem.
I also tested IRSS using the send_test_event disk_em command and it worked fine.
2. But that brings me to my next question. I have 3 servers, two are 11.23 and one is 11.11, that will not acknowledge the send_test_event test. I have several other servers that are configured in similar ways that have no issues. What I noticed was that those three servers are listed as having No Collections present. Also, servers that passed the test show their OS in the SEA while the 3 that aren’t getting the test do not.
When configuring the Managed Systems I installed the latest versions of the required software. I also changed the permissions on the sslshare directory (that worked for another server) and ran the swconfig *\ command with no errors. I even removed the Managed Systems from the SEA, reinstalled the software and then added them back. No errors but the send_test_event test still didn’t work.
The only other detail I noticed was that on some systems the the send_test_event is located at /etc/opt/resmon/lbin/ and on others it’s /opt/resmon/bin/send_test_event.
Is there a way to force collections?
3. The last issue is the least of them. We get the following error, which I read on HP forums is a bug:
Webes Health Check reported a problem at Tue, 30 Jun 2009 11:01:00 -0400
Hostname: xxxxx
Version: 1.0
Error Code: E2E
Description:Webes HeartBeat test failed to log event. Webes may not be in running state
CallStack:
Recommended Action:
Restart Webes Director or Contact HP services.
Is there a way to fix this? I tried turning the WEBES log notification off. That cut down on multiple emails but I’m still getting an email at 11am and 7pm.
Thank in advance
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2009 06:53 AM
09-24-2009 06:53 AM
Re: Query on IRSS
Vic,
to 30
this is a bug in WEBES. WEBES creates 3 scheduled tasks which operate at those times. they try to log a test evebnt, but are not able to due to this bug
workaround is to execute
desta whc e2e off
this disables the internal health check of WEBES director
optional you delete those 3 scheduled tasks, as they are not really necessary to have your systems monitored
Hope this helps
to 30
this is a bug in WEBES. WEBES creates 3 scheduled tasks which operate at those times. they try to log a test evebnt, but are not able to due to this bug
workaround is to execute
desta whc e2e off
this disables the internal health check of WEBES director
optional you delete those 3 scheduled tasks, as they are not really necessary to have your systems monitored
Hope this helps
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP