ISEE is not able to send alerts to HP Response center

[JUGAL KISHORE MAHESHWAR]

Hi

We had a disk faliure on one of the our HP-UX server who has generated ems alert ISEE Client captured the alret & try to send to ISEE Server , but the incedant status is showing SEND , where as should be RECEIVED
What could be the problem.

[Frauke Denker_2]

Hello,
you need to check the /var/opt/hpservices/log/mad.log for error messages and you might need to trace the network connection to be able to tell why the connection to HP does not work. If you are using a proxy check wether the connection still works with the values entered.
Regards
Frauke

[JUGAL KISHORE MAHESHWAR]

Hi

We have two similar servers , but one server is connecting to HP Network where as other is not connecting , in above mentioned log file send/receive is faling
but one server is able to communication.
Could some one tell me how to compare the settings of both the servers.
what are the files which need to be checked.

Thanks & Regards

Jugal

[Pravin Salgaonkar]

hi

check whether u r able to open the webite of isee url is
isee.asiapac.hp.com/mots/motserv through xwindow

if u have a proxy save the username and passwd in the netscape browser by checking the save the password box

then after opening the isee page go to configuration options and see whether u have entered proxy userid and password correct

do the same setting as in the server where it is working

also run the program
/var/opt/hpservices/bin/enttilementverification(pls check the path i am not sure )

this should solve the problem

[Liem Nguyen]

Hi,

This looks like a Networking issue where your Server is unable to communicate with HP Backend (isee.asiapac.hp.com or 192.170.77.107).

You can try few simples commands:
nslookup isee.asiapac.hp.com
telnet isee.asiapac.hp.com 80

You can also look at the Proxy setting and compare with your working server.

If you are using Microsoft NTLM Proxy, you must setup rules that allows each client or a group of clients to bypass Proxy authentication.

NOTE: ISEE Clients are communicating with HP over port 80.

[JUGAL KISHORE MAHESHWAR]

Hi
The server used is HP Internal network so no proxy setting are required , also I am able to do nslookup & telnet on port 80

If you have any more suggession please let me know

[Pravin Salgaonkar]

hi

can u send the mad log file
var/opt/hpservices/log/mad.log

regards
Pravin S

[JUGAL KISHORE MAHESHWAR]

Hi Praveen

Atteching the file with message

[Liem Nguyen]

Hi,

Here is the error:
NetworkException (8): host not found

Your ISEE Server is unable to resolve the host (isee.asiapac.hp.com 192.170.77.107). You may need to add this host with it's IP to /etc/hosts.
Make sure /etc/nsswitch.conf is configured to Hosts file in addition to DNS.

Let me know if this helps.

[JUGAL KISHORE MAHESHWAR]

Hi
But nslookup is resolving the server
[ROOT sgpob06]/etc # nslookup isee.asiapac.hp.com
Name Server: sgp-resolver.asiapac.hp.net
Address: 15.211.128.51

Trying DNS
Name: sgnsecev.sg.external.hp.com
Address: 192.170.77.107
Aliases: isee.asiapac.hp.com

Regards

[Pravin Salgaonkar]

Hi

I Agree With Liem There is some problem for u r side on the network it is not able to reach the server.Have u supplied me with the whole or part of the mad.log

Regards
Pravin S

[JUGAL KISHORE MAHESHWAR]

Hi Praveen

I have supped whole mad.log
I would like to know when dns is able to resolve the isee server ip then how it can become a network problem.

Regards

Jugal

[Liem Nguyen]

This is likely DNS issue, does this work:

nslookup localhost?
nslookup 127.0.0.1?
nslookup this_server_hostname?

Also, asiapac is not inside HP network as you can see, it's in a DMZ (192.) while your server is either in (15. or 16.), you may need to configure Proxy Server.