- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- IRSA for hpux servers
Insight Remote Support
1753808
Members
7913
Online
108805
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
тАО02-23-2010 11:54 PM
тАО02-23-2010 11:54 PM
IRSA for hpux servers
Hi,
I have problem in implementing IRSA 5.4 with hpux servers. i have successfully integrated EVA boxes with IRSA and its automatically logging a call with HP if any h/w failures.
But for HPUX server i am getting events in HP SIM but not logging a call with HP. there was some problem for generating incidents in System Event Analyzer. whereas i can see EVA's incidents in SEA
So please give me any support that it will help to integrate the IRSA
Regards,
Veera
I have problem in implementing IRSA 5.4 with hpux servers. i have successfully integrated EVA boxes with IRSA and its automatically logging a call with HP if any h/w failures.
But for HPUX server i am getting events in HP SIM but not logging a call with HP. there was some problem for generating incidents in System Event Analyzer. whereas i can see EVA's incidents in SEA
So please give me any support that it will help to integrate the IRSA
Regards,
Veera
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2010 06:50 AM
тАО02-24-2010 06:50 AM
Re: IRSA for hpux servers
Part of IRS is a product named WEBES (or SEA) that analyzes events and sends notification to HP through the ISEE back-end if necessary.
First, I suggest you configure WEBES to send e-mails notifications if you haven't done so, but it is possibly already done if you get SEA emails.
Then you need to have SIM subscribe to WBEM events on your server which is easy to do using mxwbemsub. Looks like you did this already. Then, you must ensure WEBES subscribes too; this happens automatically in theory, but experience here showed me it doesn't work in many cases as it will try to subscribe once as soon as it discovers the server as a new entity, but then it's hard to have it try again if that initial subscription fails.
To check if WEBES is subscribed, run this on your HP-UX system as root:
# evweb subscribe -b external -L
You should have a few "HPSIM_xxxxx" subscriptions, which are the ones SIM uses.
You must also have one subscription named "HPWEBES_xxxxx". If that one is not there, WEBES will not trap the hardward events.
If that happens, one trick is to delete your server from the WEBES managed system list, then stop and restart the director. Wait 15 minutes and run evweb again. WEBES should haved picked up your server from SIM and subscribed within that time frame.
Good luck
First, I suggest you configure WEBES to send e-mails notifications if you haven't done so, but it is possibly already done if you get SEA emails.
Then you need to have SIM subscribe to WBEM events on your server which is easy to do using mxwbemsub. Looks like you did this already. Then, you must ensure WEBES subscribes too; this happens automatically in theory, but experience here showed me it doesn't work in many cases as it will try to subscribe once as soon as it discovers the server as a new entity, but then it's hard to have it try again if that initial subscription fails.
To check if WEBES is subscribed, run this on your HP-UX system as root:
# evweb subscribe -b external -L
You should have a few "HPSIM_xxxxx" subscriptions, which are the ones SIM uses.
You must also have one subscription named "HPWEBES_xxxxx". If that one is not there, WEBES will not trap the hardward events.
If that happens, one trick is to delete your server from the WEBES managed system list, then stop and restart the director. Wait 15 minutes and run evweb again. WEBES should haved picked up your server from SIM and subscribed within that time frame.
Good luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2010 12:23 AM
тАО03-10-2010 12:23 AM
Re: IRSA for hpux servers
Hi Oliver
Thanks for your support
But in my case the one of the server is getting in ssh port but it should get the wbem-http port (5989). is that right?
How to change my listening port to 5989?
Now i am getting like this
--> tcp 0 0 Kaveri.22 drcxp20- 216.tcs.co.in.2197
But We should get output this in hpux server
--> tcp 0 0 Kaveri:wbem-https drcxp20-216.tcs.co.in.2197
see the below output in kaveri
---------------------------------------------
Value of TERM has been set to "xterm".
Kaveri-/>evweb subscribe -b external -L
Filter Name Handler Name Query Destinat Destination Url
================================================ ================================================= ========================================================================================= ======== =========================================
HPSIM_TYPE_1_sbidr_xp_cms_0 HPSIM_TYPE_1_sbidr_xp_cms_penna SELECT * FROM CIM_AlertIndication CIMXML https://10.192.20.216:50004/cimom/listen1
HPSIM_sbidr_xp_cms_0 HPSIM_sbidr_xp_cms select * from HP_DeviceIndication UNKNOWN
HPSIM_sbidr_xp_cms_1 HPSIM_sbidr_xp_cms select * from HP_ThresholdIndication UNKNOWN
HPSIM_isee_0 HPSIM_isee select * from HP_DeviceIndication UNKNOWN
HPSIM_isee_1 HPSIM_isee select * from HP_ThresholdIndication UNKNOWN
HPSIM_TYPE_1_isee_0 HPSIM_TYPE_1_isee_penna SELECT * FROM CIM_AlertIndication CIMXML https://isee:50004/cimom/listen1
EMS_INTERNAL_427491329 EMS_INTERNAL_427491329 SELECT * FROM HP_DeviceIndication WHERE ProviderName = "FPL_IndicationProvider" UNKNOWN
EMS_INTERNAL_427491334 EMS_INTERNAL_427491334 SELECT * FROM HP_DeviceIndication WHERE ProviderName = "CoreHardwareIndicationProviderIA" UNKNOWN
HPSIM_drcxp20-216_0 HPSIM_drcxp20-216 select * from HP_DeviceIndication UNKNOWN
HPSIM_drcxp20-216_1 HPSIM_drcxp20-216 select * from HP_ThresholdIndication UNKNOWN
HPWEBES_drcxp20-216_13_Filter_HP_AlertIndication HPWEBES_drcxp20-216_13_Handler_HP_AlertIndication select * from HP_AlertIndication UNKNOWN
Thanks for your support
But in my case the one of the server is getting in ssh port but it should get the wbem-http port (5989). is that right?
How to change my listening port to 5989?
Now i am getting like this
--> tcp 0 0 Kaveri.22 drcxp20- 216.tcs.co.in.2197
But We should get output this in hpux server
--> tcp 0 0 Kaveri:wbem-https drcxp20-216.tcs.co.in.2197
see the below output in kaveri
---------------------------------------------
Value of TERM has been set to "xterm".
Kaveri-/>evweb subscribe -b external -L
Filter Name Handler Name Query Destinat Destination Url
================================================ ================================================= ========================================================================================= ======== =========================================
HPSIM_TYPE_1_sbidr_xp_cms_0 HPSIM_TYPE_1_sbidr_xp_cms_penna SELECT * FROM CIM_AlertIndication CIMXML https://10.192.20.216:50004/cimom/listen1
HPSIM_sbidr_xp_cms_0 HPSIM_sbidr_xp_cms select * from HP_DeviceIndication UNKNOWN
HPSIM_sbidr_xp_cms_1 HPSIM_sbidr_xp_cms select * from HP_ThresholdIndication UNKNOWN
HPSIM_isee_0 HPSIM_isee select * from HP_DeviceIndication UNKNOWN
HPSIM_isee_1 HPSIM_isee select * from HP_ThresholdIndication UNKNOWN
HPSIM_TYPE_1_isee_0 HPSIM_TYPE_1_isee_penna SELECT * FROM CIM_AlertIndication CIMXML https://isee:50004/cimom/listen1
EMS_INTERNAL_427491329 EMS_INTERNAL_427491329 SELECT * FROM HP_DeviceIndication WHERE ProviderName = "FPL_IndicationProvider" UNKNOWN
EMS_INTERNAL_427491334 EMS_INTERNAL_427491334 SELECT * FROM HP_DeviceIndication WHERE ProviderName = "CoreHardwareIndicationProviderIA" UNKNOWN
HPSIM_drcxp20-216_0 HPSIM_drcxp20-216 select * from HP_DeviceIndication UNKNOWN
HPSIM_drcxp20-216_1 HPSIM_drcxp20-216 select * from HP_ThresholdIndication UNKNOWN
HPWEBES_drcxp20-216_13_Filter_HP_AlertIndication HPWEBES_drcxp20-216_13_Handler_HP_AlertIndication select * from HP_AlertIndication UNKNOWN
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