- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- ISEE/OSEM/WEBES - Tests work but no notification f...
Disk Enclosures
1754278
Members
2825
Online
108813
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
11-13-2007 07:36 AM
11-13-2007 07:36 AM
ISEE/OSEM/WEBES - Tests work but no notification for real EVA hardware problem
Here is what I am running:
- EVA 6100 on latest firmware
- Command View 7.0
- ISEE 4.0
- WEBES 4.5.1
- OSEM 1.4.4
Everything appears to be working correctly. Running 'wseatest' opens an incident inside ISEE that is closed by HP. When I look at the 'managedentities' section in WEBES, I can see both my Command View server and the EVA itself. I have already put the authentication information in. The entitlement for both the Command View server and the EVA were verified and closed. OSEM test alerts are also sent to ISEE.
However, nothing happens when there is a genuine hardware problem with the EVA. I do see the event logged in the Application Log on the Command View server, but it never makes it into ISEE. I have searched through the forums and manuals, but nothing I do is working.
Any thoughts?
Thank you.
- EVA 6100 on latest firmware
- Command View 7.0
- ISEE 4.0
- WEBES 4.5.1
- OSEM 1.4.4
Everything appears to be working correctly. Running 'wseatest' opens an incident inside ISEE that is closed by HP. When I look at the 'managedentities' section in WEBES, I can see both my Command View server and the EVA itself. I have already put the authentication information in. The entitlement for both the Command View server and the EVA were verified and closed. OSEM test alerts are also sent to ISEE.
However, nothing happens when there is a genuine hardware problem with the EVA. I do see the event logged in the Application Log on the Command View server, but it never makes it into ISEE. I have searched through the forums and manuals, but nothing I do is working.
Any thoughts?
Thank you.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2007 12:00 PM
11-13-2007 12:00 PM
Re: ISEE/OSEM/WEBES - Tests work but no notification for real EVA hardware problem
I had a similar problem. HP ensured me that if the 'wsea test' command puts an event into isee then there is no way that an event in the windows application log would not find its way to isee.
That said, they sent me the following steps to fix-up any issues that I might have had.
let me know if they work for you.
-stop desta with DOS>net stop desta_service
-stop wccproxy with DOS>net stop wccproxy
-run â ¦C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
-Disable fps creation, from the command line enter: DOS>wccproxy fpsoff
-Reset the automatic analysis database:
DOS>desta exec com.compaq.svctools.ca.services.database.resetAll
-Save and clear the Windows application event file.
-Use Task Manager to verify all WCCproxy, WCCAgents, and CAAgents processes are stopped
(if not may need to reboot)
-Restart desta with DOS>net start desta_service
-Start the SEA WUI
-After 4 minutes generate an SEATEST event using the command: DOS>wsea test
This should produce a SEATEST report in the WUI.
That said, they sent me the following steps to fix-up any issues that I might have had.
let me know if they work for you.
-stop desta with DOS>net stop desta_service
-stop wccproxy with DOS>net stop wccproxy
-run â ¦C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
-Disable fps creation, from the command line enter: DOS>wccproxy fpsoff
-Reset the automatic analysis database:
DOS>desta exec com.compaq.svctools.ca.services.database.resetAll
-Save and clear the Windows application event file.
-Use Task Manager to verify all WCCproxy, WCCAgents, and CAAgents processes are stopped
(if not may need to reboot)
-Restart desta with DOS>net start desta_service
-Start the SEA WUI
-After 4 minutes generate an SEATEST event using the command: DOS>wsea test
This should produce a SEATEST report in the WUI.
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