Pb with script monitor in AIX

Pb with script monitor in AIX

Hello,



I�m trying your Application Manager 7 and I find problem with script monitor.

I have already add a server monitor on a system AIX and it works perfectly. But when I try to put a script monitor in the same system it said �Could not establish a session with the host. Kindly check the host information. �. I ran a tcpdump for seeing if they saw themself (below).

tcpdump -i en0 -n src 172.30.20.250 or dst 172.30.20.250 and not arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en0, link-type 1, capture size 96 bytes
17:14:57.243647 IP 172.30.20.250.4182 > 172.30.170.4.23: S 4276307771:4276307771(0) win 65535 <mss 1460,nop,nop,sackOK>
17:14:57.243733 IP 172.30.170.4.23 > 172.30.20.250.4182: S 1647473228:1647473228(0) ack 4276307772 win 65535 <mss 1460>
17:14:57.244183 IP 172.30.20.250.4182 > 172.30.170.4.23: . ack 1 win 65535
17:14:57.812232 IP 172.30.170.4.23 > 172.30.20.250.4182: P 1:7(6) ack 1 win 65535
17:14:57.812593 IP 172.30.20.250.4182 > 172.30.170.4.23: P 1:2(1) ack 7 win 65529
17:14:57.853532 IP 172.30.170.4.23 > 172.30.20.250.4182: . ack 2 win 65535
17:14:57.853746 IP 172.30.20.250.4182 > 172.30.170.4.23: P 2:7(5) ack 7 win 65529
17:14:57.853846 IP 172.30.170.4.23 > 172.30.20.250.4182: P 7:16(9) ack 7 win 65535
17:14:57.854043 IP 172.30.20.250.4182 > 172.30.170.4.23: P 7:9(2) ack 16 win 65520
17:14:58.053541 IP 172.30.170.4.23 > 172.30.20.250.4182: . ack 9 win 65535
17:14:58.053716 IP 172.30.20.250.4182 > 172.30.170.4.23: P 9:17(8) ack 16 win 65520
17:14:58.056376 IP 172.30.170.4.23 > 172.30.20.250.4182: P 16:70(54) ack 17 win 65535
17:14:58.056686 IP 172.30.20.250.4182 > 172.30.170.4.23: P 17:20(3) ack 70 win 65466
17:14:58.254604 IP 172.30.170.4.23 > 172.30.20.250.4182: . ack 20 win 65535
17:14:58.254857 IP 172.30.20.250.4182 > 172.30.170.4.23: P 20:44(24) ack 70 win 65466
17:14:58.258269 IP 172.30.170.4.23 > 172.30.20.250.4182: P 70:76(6) ack 44 win 65535
17:14:58.258620 IP 172.30.20.250.4182 > 172.30.170.4.23: P 44:45(1) ack 76 win 65460
17:14:58.457019 IP 172.30.170.4.23 > 172.30.20.250.4182: . ack 45 win 65535
17:14:58.457163 IP 172.30.20.250.4182 > 172.30.170.4.23: P 45:47(2) ack 76 win 65460
17:14:58.515649 IP 172.30.170.4.23 > 172.30.20.250.4182: P 76:203(127) ack 47 win 65535
17:14:58.516261 IP 172.30.20.250.4182 > 172.30.170.4.23: P 47:56(9) ack 203 win 65333
17:14:58.516456 IP 172.30.170.4.23 > 172.30.20.250.4182: P 203:213(10) ack 56 win 65535
17:14:58.626429 IP 172.30.20.250.4182 > 172.30.170.4.23: . ack 213 win 65323
17:14:58.626461 IP 172.30.170.4.23 > 172.30.20.250.4182: P 213:233(20) ack 56 win 65535
17:14:58.827786 IP 172.30.20.250.4182 > 172.30.170.4.23: . ack 233 win 65303
17:15:29.144212 IP 172.30.20.250.4182 > 172.30.170.4.23: F 56:56(0) ack 233 win 65303
17:15:29.144269 IP 172.30.170.4.23 > 172.30.20.250.4182: . ack 57 win 65535
17:15:29.165152 IP 172.30.170.4.23 > 172.30.20.250.4182: F 233:233(0) ack 57 win 65535
17:15:29.165455 IP 172.30.20.250.4182 > 172.30.170.4.23: . ack 234 win 65303

As we can see there is a connection between the two system. I try the sequence: telnet + run the script and it works.
Is there some information in your application to see where the problem is?

Thank you











































                New to ADSelfService Plus?