- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- ISEE Modle-2 client setup
Insight Remote Support
1752774
Members
4801
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
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
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-21-2006 04:11 PM
тАО03-21-2006 04:11 PM
ISEE Modle-2 client setup
Hello
I have installed ISEE client version A.3.95 on one of my client Proliant machine running on Windows OS. The OSEM (Event Handler) is installed on another host. Events are not reacing ISEE client host from OSEM Host via WCC proxy. Can anyone help me to clear the following:
How to check which version of WCC proxy is being installed with ISEE client software(any logs). How to view/remove WCC proxy component on ISEE client running on Windows OS.
Is there any incident interface to check between WCC proxy to ISEE client to work?
Is there any incident interface to check between OSEM host to WCC proxy to work?
I have checked one of the wcc log file,pl. go through the attatchment.
How to check whether SNMP traps/Gets are working fine between OSEM host to ISEE client host via WCC proxy.
Can anyone help me? ASAP
I have installed ISEE client version A.3.95 on one of my client Proliant machine running on Windows OS. The OSEM (Event Handler) is installed on another host. Events are not reacing ISEE client host from OSEM Host via WCC proxy. Can anyone help me to clear the following:
How to check which version of WCC proxy is being installed with ISEE client software(any logs). How to view/remove WCC proxy component on ISEE client running on Windows OS.
Is there any incident interface to check between WCC proxy to ISEE client to work?
Is there any incident interface to check between OSEM host to WCC proxy to work?
I have checked one of the wcc log file,pl. go through the attatchment.
How to check whether SNMP traps/Gets are working fine between OSEM host to ISEE client host via WCC proxy.
Can anyone help me? ASAP
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2006 02:07 PM
тАО03-22-2006 02:07 PM
Re: ISEE Modle-2 client setup
Anup,
OSEM sends Problem Reports using http over tcp/ip on port 7920 to the WCCProxy application running on the model 2 client. To determine what version of WCCProxy is installed you can run the following command: C:\>wccproxy status. The only way to determine whether or not WCCProxy is communicating to ISEE is by generating an SNMP Test Trap, using either the HP System Management Homepage http://localhost:2381 select the settings tab and then the SNMP and Agents link the click on the Sent Test Trap button or from the HP Management Agents API Start>Control Panel>HP Management Agents, select the SNMP Setting tab and generate a test event from there.
This should then send generate an SNMP Test Trap and send it to the OSEM host (if the Windows SNMP Service is configured correctly). OSEM should then create a Problem Report that can be viewed from the OSEM Viewer on the OSEM host http://localhost:2069 click on the Notifications link. After generating the Problem Report OSEM should send the report back to the WCCProxy application running on the remote client (if OSEM is configured to send events remotely to ISEE, check the Remote Delivery page in the OSEM viewer to confirm this).
SNMP GETS are not sent to WCCProxy on the remote client, they are sent to the IM Agents on the remote client. You can confirm whether or not the SNMP GETS are failing by viewing the OSEM subfolder log which is by default in C:\Program Files\Hewlett-Packard\OSEM\log on the OSEM host.
OSEM sends Problem Reports using http over tcp/ip on port 7920 to the WCCProxy application running on the model 2 client. To determine what version of WCCProxy is installed you can run the following command: C:\>wccproxy status. The only way to determine whether or not WCCProxy is communicating to ISEE is by generating an SNMP Test Trap, using either the HP System Management Homepage http://localhost:2381 select the settings tab and then the SNMP and Agents link the click on the Sent Test Trap button or from the HP Management Agents API Start>Control Panel>HP Management Agents, select the SNMP Setting tab and generate a test event from there.
This should then send generate an SNMP Test Trap and send it to the OSEM host (if the Windows SNMP Service is configured correctly). OSEM should then create a Problem Report that can be viewed from the OSEM Viewer on the OSEM host http://localhost:2069 click on the Notifications link. After generating the Problem Report OSEM should send the report back to the WCCProxy application running on the remote client (if OSEM is configured to send events remotely to ISEE, check the Remote Delivery page in the OSEM viewer to confirm this).
SNMP GETS are not sent to WCCProxy on the remote client, they are sent to the IM Agents on the remote client. You can confirm whether or not the SNMP GETS are failing by viewing the OSEM subfolder log which is by default in C:\Program Files\Hewlett-Packard\OSEM\log on the OSEM host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2006 03:33 AM
тАО03-23-2006 03:33 AM
Re: ISEE Modle-2 client setup
Attached file SNMPutilG is a graphical utility to test if there is snmp communication possible.
You can do SNMP GET with it.
Very useful when troubleshooting SNMP communication problems.
You can do SNMP GET with it.
Very useful when troubleshooting SNMP communication problems.
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