- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: Unable to send testtrap
Insight Remote Support
1752777
Members
6641
Online
108789
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
03-07-2007 01:11 PM
03-07-2007 01:11 PM
Unable to send testtrap
I have just installed ISEE onto ML350G4p server(WindowsServer2003R2) without problem.
But ISEE is unable to send testtrap to hp.
Entitlement verification is success.
Connecting to "http://isee.asiapac.hp.com/mots/motserv" is success.
Sending testtrap to SIM on Intranet is success.
But ISEE is unable to send testtrap to hp.
Entitlement verification is success.
Connecting to "http://isee.asiapac.hp.com/mots/motserv" is success.
Sending testtrap to SIM on Intranet is success.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2007 12:01 AM
03-09-2007 12:01 AM
Re: Unable to send testtrap
Was OSEM installed on the server? OSEM is the event handling application and is required to capture the SNMP trap and convert it into http and deliver to the ISEE Client Software. You can download OSEM from http://h18023.www1.hp.com/support/svctools/OSEM/index.html
Is the Windows SNMP Trap Service set to Manual and started? The Windows SNMP Trap Service is required to recieve the SNMP Trap initially and deliver it to the SNMP registered applications (OSEM) on the server.
Is the Windows SNMP Service configured to send the trap to the localhost? This is configured on the SNMP Service Traps Tab.
Check the community name, if changed from the default of public then make the change on the OSEM Viewer (http://localhost:2069)>Internal Page>, click on the Advanced Internal Settings link at the bottom of that page and change the value of the Default SNMP GET Community Name variable.
Check the C:\Program Files\Hewlett-Packard\OSEM\logs\RSM_log.0.log file, is there any mention of a trap being received by OSEM from the localhost? If not send a trap from a remote host, if this is not received by OSEM, then suspect something is wrong with your SNMP Trap Service or your Windows registry.
Is the Windows SNMP Trap Service set to Manual and started? The Windows SNMP Trap Service is required to recieve the SNMP Trap initially and deliver it to the SNMP registered applications (OSEM) on the server.
Is the Windows SNMP Service configured to send the trap to the localhost? This is configured on the SNMP Service Traps Tab.
Check the community name, if changed from the default of public then make the change on the OSEM Viewer (http://localhost:2069)>Internal Page>, click on the Advanced Internal Settings link at the bottom of that page and change the value of the Default SNMP GET Community Name variable.
Check the C:\Program Files\Hewlett-Packard\OSEM\logs\RSM_log.0.log file, is there any mention of a trap being received by OSEM from the localhost? If not send a trap from a remote host, if this is not received by OSEM, then suspect something is wrong with your SNMP Trap Service or your Windows registry.
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