APA Lan communication fails randomly

[kumasudh]

Hi,

I am facing issues with my APA configuration. I have configure APA between two hosts. After every almost 20 min. the communication get disrupted though we dont see any lan failure incident reported in syslog. Could you please help to troubleshoot this issue ?

Here is the status of my platform network config

On Machine A:

/usr/bin/netstat -rn :
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.168.81.210 192.168.81.210 UH 0 lan900:1 4136
192.168.81.200 192.168.81.200 UH 0 lan900 4136
192.168.254.101 192.168.254.101 UH 0 lan1 4136
192.168.81.168 192.168.81.168 UH 0 lan901 4136
194.251.33.172 194.251.33.172 UH 0 lan0 4136
192.168.254.96 192.168.254.101 U 2 lan1 1500
194.251.33.160 194.251.33.172 U 2 lan0 1500
192.168.81.160 192.168.81.168 U 2 lan901 1500
192.168.81.192 192.168.81.200 U 3 lan900 1500
192.168.81.192 192.168.81.210 U 3 lan900:1 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 194.251.33.161 UG 0 lan0 0

----------------------
/usr/bin/netstat -an :
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 127.0.0.1.49256 127.0.0.1.49255 ESTABLISHED
tcp 0 0 194.251.33.172.49259 194.251.33.172.6000 ESTABLISHED
tcp 0 0 194.251.33.172.51488 194.251.33.172.51449 ESTABLISHED
tcp 0 0 194.251.33.172.51487 194.251.33.172.6000 ESTABLISHED
tcp 0 0 194.251.33.172.6000 194.251.33.172.51487 ESTABLISHED
tcp 0 0 127.0.0.1.49163 127.0.0.1.49164 ESTABLISHED
tcp 0 0 *.5989 *.* LISTEN
tcp 0 0 127.0.0.1.49169 *.* LISTEN
tcp 0 0 *.22 *.* LISTEN
tcp 0 0 *.543 *.* LISTEN
tcp 0 0 *.544 *.* LISTEN
tcp 0 72 192.168.81.210.4303 192.168.81.208.64426 ESTABLISHED
tcp 0 0 127.0.0.1.49243 127.0.0.1.5302 ESTABLISHED
......

On Machine B:

/usr/bin/netstat -rn :
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.168.81.208 192.168.81.208 UH 0 lan900 4136
192.89.191.168 192.89.191.168 UH 0 lan3 4136
192.168.81.164 192.168.81.164 UH 0 lan9 4136
192.89.191.184 192.89.191.184 UH 0 lan7 4136
194.251.33.170 194.251.33.170 UH 0 lan0 4136
192.168.81.132 192.168.81.132 UH 0 lan5 4136
192.89.191.160 192.89.191.168 U 2 lan3 1500
192.89.191.176 192.89.191.184 U 2 lan7 1500
194.251.33.160 194.251.33.170 U 2 lan0 1500
192.168.81.128 192.168.81.132 U 2 lan5 1500
192.168.81.160 192.168.81.164 U 2 lan9 1500
192.168.81.192 192.168.81.208 U 2 lan900 1500
62.0.0.0 192.89.191.184 U 0 lan7 1500
62.0.0.0 192.89.191.168 U 0 lan3 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 194.251.33.161 UG 0 lan0 0

----------------------
/usr/bin/netstat -an :
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 127.0.0.1.6694 127.0.0.1.49998 ESTABLISHED
tcp 0 0 127.0.0.1.49949 127.0.0.1.6673 ESTABLISHED
tcp 0 0 127.0.0.1.6673 127.0.0.1.49949 ESTABLISHED
tcp 0 0 127.0.0.1.49913 127.0.0.1.4302 ESTABLISHED
tcp 0 0 *.6772 *.* LISTEN
tcp 0 1 192.168.81.208.50816 192.168.81.210.4303 SYN_SENT
tcp 0 0 127.0.0.1.6669 127.0.0.1.49830 ESTABLISHED
tcp 0 0 127.0.0.1.49849 127.0.0.1.6669 ESTABLISHED
tcp 0 0 127.0.0.1.6671 127.0.0.1.49831 ESTABLISHED
tcp 0 0 127.0.0.1.49848 127.0.0.1.6669 ESTABLISHED
tcp 0 0 192.168.81.132.49778 192.168.81.132.6010 ESTABLISHED


The IP address "192.168.81.208" is APA on machine B and IP address "192.168.81.210" is APA on machine A.

Best Regards
Sudhir

[Taifur]

Hi,

Check below link as follows,

http://docs.hp.com/en/J4240-90046/apbs01.html

Rgds//
Taifur

[Mel Burslan]

The routing table data does not tell anyone outside your company network team and may be you, anything about the reason why you are having network disruptions. But just by going out on a limb here, looking at your statement indicating "nothing in the syslog", makes me think that your network switches are not configured properly and every 20 minutes or so, they were having to redo their routing, (god forbid, they might even be going into a spanning tree route calculation) disrupting your network traffic. If you have an APA disconnect or a network drop out of operation, you should at least get some sort of indication in the syslog, unless of course you or some other clever admin disabled alarms going into the syslog.

Again as I said before, the data you provided gives a very little to go forward.