ISEE client installaton on HP-UX machine

[tr10385]

ia64 hp server rx8620
OS info:
sysname = HP-UX
release = B.11.23
machine = ia64
ISEEPlatform.ISEE A.03.95.510.46 ISEE

this is Advanced ISEE setup, with SPOP in DMZ.

The client configuration is not complete. The following error's are seen in Mad.log (with log level 5 and Network time out 15)

Original mad.log: (Network_time_out = 5)
140208 10:30:32.629 STDOUT,[Comm] writing data: 2048 bytes
140208 10:30:32.629 STDOUT,[Comm] writing data: 128 bytes
140208 10:32:12.620 STDOUT,[Comm] Socket::close()
140208 10:32:12.620 ERROR,[Comm] mmsg.cpp:36 NetworkException (10): Socket::read(): recv() timeout [[172.16.1.3]]

Time between "write" and NE = 100 seconds.


Latest mad.log after the "GlobalSettings/NETWORK_TIMEOUT" entry had been increased from 5 to 15:
270208 10:12:19.444 STDOUT,[Comm] writing data: 2048 bytes
270208 10:12:19.444 STDOUT,[Comm] writing data: 1952 bytes
270208 10:12:49.437 STDOUT,[Comm] Socket::close()
270208 10:12:49.437 ERROR,[Comm] mmsg.cpp:36 NetworkException (10): Socket::read(): recv() timeout [[172.16.1.3]]

Equals only a 30 second difference.

Could you pls. give me the reasons for Network Exception 10. I believe this some where related to keepalive value between two peer networking devices.

If needed further mad.log entries, i can provide.

[ITRC Test-CH]

Hello,

This looks about a connection problem between the ISEE client and the SPOP.
The description of this error says:
NetworkException (10): Socket::connect()
..
..
Possible Cause:
This error occurs when the internet communication route between the client and HP/SPOP is garbled, corrupted, or inhibited. Usually, there is a connection but the reply is corrupted or non-existent.
Resolution:
The known reason for this error is an incorrect Network Address Translation on the customer firewall.

Please check also, that established back (reply from your SPOP) is possible.

Regards,
Werner

[tr10385]

Hello Werner

i checked the NAT at customer firewall, and this is working in place. I am trying to access the ISEE client UI from SPOP, this could establish connect to hp-ux client fir via Natted IP and later to client real IP. I also tried to changed the Network timeout falue from default 5 to 15 tp 30, but every time the time difference between witing data to Socket close is same as the network timeout value.
Pls. tell me if, chaning the network timeout valuev does help me?

[Liem Nguyen]

Hi,

One way you can try is to increase NETWORK_TIMEOUT=240 (or 120). You must stop/start hpservices after making the change to motprefs.

Also, make sure the SPOP NIC's properties is set to the correct Speed & Duplex (i.e 100 MB Full), do not leave it as AUTO.

Does "telnet spop 80" works?

Hope this helps,

[tr10385]

I have changed the Network timeout value to 300 (5 min)

030308 14:09:29.180 STDOUT,[Comm] writing data: 2048 bytes
030308 14:09:29.181 STDOUT,[Comm] writing data: 2048 bytes
030308 14:14:29.172 STDOUT,[Comm] Socket::close()
030308 14:14:29.173 ERROR,[Comm] mmsg.cpp:36 NetworkException (10): Socket::write(): send() timeout [[172.16.1.3]]

030308 14:20:29.848 STDOUT,[Comm] writing data: 2048 bytes
030308 14:20:29.848 STDOUT,[Comm] writing data: 2048 bytes
030308 14:25:29.840 STDOUT,[Comm] Socket::close()
030308 14:25:29.840 ERROR,[Comm] mmsg.cpp:36 NetworkException (10): Socket::write(): send() timeout [[172.16.1.3]]

For both the observations Time between "write" and NE = 300 seconds as configured via motprefs for network timeout value.

I haven't checked the SPOP NIC properties, but would check and let you know.

REgarding telnet 80 is restricted either from hp-ux client to SPOP or from SPOP to hp-ux. since SPOP is in DMZ, customer restricted the telnet.

I have run the nettl for the hp-ux machine, if needed I could send you via mail.

[Liem Nguyen]

Hi,

Please run "telnet spop 80", this is not a standard telnet, what you are doing is to connect through port 80, even telnet is disabled, telnet to port 80 should still be working.

Do you have other clients that worked or this is the only client so far? This is an important question.

Seems to me you are not gettting through, so time-out is not a factor anymore. You can change it back.

If you logon to the SPOP and launch ISEE client (http://localhost:5060/start.html), does this work or do you get error saying it can't connect to motserv?