- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: End to End detection failed
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО07-29-2007 09:52 PM
тАО07-29-2007 09:52 PM
End to End detection failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2007 08:01 AM
тАО07-30-2007 08:01 AM
Re: End to End detection failed
"OSEM remote delivery down". It is three or four below your post.
I ran into this same issue.
Some info that would help
What version of ISEE and OSEM are you running? Have you recently upgraded HPSIM? Which version of HPSIM are you running? Was it working before? What changed since you then?
Have you installed Remote Support Software Manager?
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2007 04:48 PM
тАО07-30-2007 04:48 PM
Re: End to End detection failed
After some time living with it, we upgraded and the error disappeared.
Ole Thomsen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2007 01:51 AM
тАО07-31-2007 01:51 AM
Re: End to End detection failed
WEBES had "e2e" issue with v4.5, so a downgrade could still se the same issue.
WEBES Engineering had developed the "end to end" detection, because with prior versions, "desta" would just stop working and the customer would then notice light on a drive and wonder why no notification.
WEBES v5.0 has some fixes for "e2e" and false "e2e" issues. If an upgrade is not possible, the following is in SAW and has helped resolve most issues.
********************
* stop desta with (desta stop)
* stop wccproxy with (wccproxy stop)
* run ├в ┬жC:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
Because there may be many Fiber Port Stat events I would have them do the FPS procedure to disable FPS collections:
* Disable fps creation, from the command line enter: wccproxy fpsoff
* Reset the automatic analysis database:
desta exec com.compaq.svctools.ca.services.database.resetAll
* Check the Windows Application event file size
On the desktop, right click on My Computer or My Appliance, and select Manage.
Click on Event Viewer, and the right click on Application and select Properties.
Make sure MAX LOG SIZE is set to at least 8192KB and no more then 16960KB.
Also make sure "Overwrite events as needed is selected"
Click Apply and OK
* Save and clear the Windows application event file.
* use Task Manager to verify all WCCproxy, WCCAgents, and CAAgents processes are stopped
(try to stop them via Task Manager if present, if not may need to reboot)
* restart desta with (net start desta_service)
* After 4 minutes generate an SEATEST event using the command: wsea test.
********************
....
Sam Cofield
HP Services
(Remote Technology Support)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2008 12:43 PM
тАО10-09-2008 12:43 PM
Re: End to End detection failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-31-2008 11:38 AM
тАО12-31-2008 11:38 AM
Re: End to End detection failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-31-2008 11:42 AM
тАО12-31-2008 11:42 AM
Re: End to End detection failed
Not sure of the version we were running prior to this, but our HP rep said that these updates needed to be installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-01-2009 03:22 AM
тАО01-01-2009 03:22 AM
Re: End to End detection failed
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2009 04:14 AM
тАО06-05-2009 04:14 AM
Re: End to End detection failed
Start menu...Systems Event Analyzer -> WEBES Notification Settings. From there I switched the WEBES log notification to ON.
There is a Windows AT command that performs a check every 8 hours. This is one of the items it checks.
I'm curious if this same fix works for everyone, or if there are other detection issues also. Please let me know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2009 07:44 PM
тАО06-09-2009 07:44 PM
Re: End to End detection failed
I had recently installed HP SIM Ver 5.3,WEBES 5.5. I also faced the same E2E DETECTION FAILED ISSUE. applied suggestions , upgrading WEBES, WEBES Notification Settings in SEA and re-installing the WEBES
from this forum but didn't help,
Solution: What has resolved problem for me.
Setting WEBES Notification Settings in SEA and re-installing the webes 5.5 in folder C:\Program Files\Hewlett-Packard\, by default it was installed in the C:\Program Files\HP\.
I hope it works for you guys as well.
Good Luck.