In our environment everyday I am finding old (not current date) DataStage client connection "ESTABLISHED" which are not showing in web console, any idea
http://yfrog.com/2cdsconnectionj
[dsadm@jmkthappetl19 ~]$ ps -ef | grep dscs
dsadm 504 28233 0 10:35 ? 00:00:00 dscs 4 0 0
dsadm 3069 3050 0 12:14 pts/1 00:00:00 grep dscs
dsadm 3466 28233 0 01:10 ? 00:00:00 dscs 4 0 0
dsadm 4668 28233 0 01:18 ? 00:00:00 dscs 4 0 0
dsadm 17990 28233 0 Dec03 ? 00:00:00 dscs 4 0 0
dsadm 18813 28233 0 04:15 ? 00:00:00 dscs 4 0 0
dsadm 19088 28233 0 Dec04 ? 00:00:00 dscs 4 0 0
dsadm 22772 28233 0 Dec05 ? 00:00:00 dscs 4 0 0
dsadm 26405 28233 0 Dec05 ? 00:00:00 dscs 4 0 0
dsadm 32738 28233 0 10:26 ? 00:00:00 dscs 4 0 0
[dsadm@jmkthappetl19 ~]$ netstat -a | grep dsrpc
tcp 0 0 *:dsrpc *:* LISTEN
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:rkb-oscs ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:sonuscallsig ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:tl1-raw ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:netopia-vo2 ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:zephyr-hm ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:bfd-control ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.173.224:wap-push ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 10.11.244.44:64465 ESTABLISHED
tcp 0 0 jmkthappetl19:dsrpc 155.17.156.66:4233 ESTABLISHED
