- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: WEBES Errors discovering iLO's
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
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
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
11-12-2012 10:46 AM
11-12-2012 10:46 AM
Hi there, I also get WEBES errors from my iLO's shown below. How do I fix these errors?
Brief Description:
Failed to discover 10.x.x.x Callout ID:
hpSVCTOOLSTrapFull Description:
WEBES has failed to correctly discover the system named 10.xx.xx.xx at IP address xx.xx.xx.xx
Solved! Go to Solution.
- Tags:
- iLO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2012 12:07 PM
11-12-2012 12:07 PM
SolutionHi Rene,
Those messages are sent when WEBES recieves a trap from a device for the first time that it does not know about. In that case, it tries to discover what the device is. In this case it is an iLO from a ProLiant I assume. WEBES does not support traps from an iLO for analysis, only getting traps from the ProLiant itself. This causes the message to be sent.
You can safely ingore that message. You can prevent the message by removing the Central Management Server from the trap destination on the iLO. I don't know the steps for doing that off the top of my head, but it should be in the iLO documenation.