Alteon AD4 configuration problem

Hello i'm trying to set up alteon AD4 web switch making config directly from manual and it's not working alteon is connected to switch using first port all servers and vip are in the same subnet and it's not working... can anyone give me the clue why ? here is my config i'm trying to connect using client connected to the same switch in the same subnet (tryied already to connect form client in another and still no success)

script start "Alteon AD4" 4 /**** DO NOT EDIT THIS LINE! /* Configuration dump taken 15:38:30 Wed Sep 21, 2005 /* Version 10.0.28.5, Base MAC address 00:0e:62:f5:74:60 /c/stp 1/off /c/ip/if 1 ena addr 10.10.2.2 mask 255.255.255.0 broad 10.10.2.255 /c/ip/gw 1 ena addr 10.10.2.1 /c/ip/frwd/off dirbr disabled /c/slb on /c/slb/real 1 ena rip 10.10.2.98 tmout 2 inter 30 name "rdp0" /c/slb/real 2 ena rip 10.10.2.99 tmout 2 name "rdp1" /c/slb/port 1 client ena proxy ena pip 10.10.2.27 /c/slb/port 2 pip 10.10.2.21 /c/slb/port 3 pip 10.10.2.22 /c/slb/port 4 pip 10.10.2.23 /c/slb/port 5 pip 10.10.2.24 /c/slb/port 6 pip 10.10.2.25 /c/slb/port 7 pip 10.10.2.26 /c/slb/port 8 proxy ena pip 10.10.2.20 /c/slb/layer7/redir / script end /**** DO NOT EDIT THIS LINE!

When using PIPs you don't need to enable server processing... normally anyway. 10.0.28.5 is old and buggy. Get the latest code.

Also, it's probably not related, but try enabling IP forwarding. PIP may require this even though it's all on one subnet. Seems to ring a bell.

Also a real server of tmout=2 is highly discouraged as a session can be aged out too early (before a FIN or RST is received by the switch).

Oh... and most important of all, your configuration is missing a virtual server and service (VIP and VPORT). Maybe you didn't paste it in?

Angler

Michael Roberts wrote:

I did not know that regarding PIP. We have avoided using PIP in our configuration because it has a tendency to scew our logs. Good info.. Thx.

-mike

Angler wrote:

oh i send bad config good one below still no success.. IP forwarding is enabled

script start "Alteon AD4" 4 /**** DO NOT EDIT THIS LINE! /* Configuration dump taken 17:22:49 Thu Sep 22, 2005 /* Version 10.0.28.5, Base MAC address 00:0e:62:f5:74:60 /c/sys http ena wport 8081 /c/stp 1/off /c/sys/sshd/on /c/ip/if 1 ena addr 10.133.1.107 mask 255.255.255.240 broad 10.133.1.111 /c/ip/gw 1 ena addr 10.133.1.97 /c/ip/frwd/off dirbr disabled /c/slb on /c/slb/real 1 ena rip 10.133.1.98 tmout 2 name "web1" /c/slb/real 2 ena rip 10.133.1.99 tmout 2 name "web2" /c/slb/real 3 ena rip 10.133.1.100 tmout 2 name "web3" /c/slb/group 1 metric roundrobin add 1 add 2 add 3 name "webs" /c/slb/port 1 client ena server ena proxy ena pip 10.133.1.103 /c/slb/port 2 pip 10.10.2.51 /c/slb/port 3 pip 10.10.2.52 /c/slb/port 4 pip 10.10.2.53 /c/slb/port 5 pip 10.10.2.54 /c/slb/port 6 pip 10.10.2.55 /c/slb/port 7 pip 10.10.2.56 /c/slb/port 8 pip 10.10.2.57 /c/slb/virt 1 ena vip 10.133.1.106 cont 256 /c/slb/virt 1/service ssh group 1 cont 256 / script end /**** DO NOT EDIT THIS LINE!

WS

I just noticed that your PIPs on ports 2-8 are on a different subnet than the IF, RIPs and VIPs. The PIP on port 1 is correct so I am assuming that you thought that all client traffic would get PIPed to the port 1 PIP? This is NOT the case when VMA is enabled (/cfg/slb/adv/mat en). Your session may get sent to ANY of the ports so those PIPs also come into play.

To fix it do ONE of the following:

1) Change your PIPs on ports 2-8 to IP addresses on the 10.113.1.96/20 subnet. If you have any available, that is. If not, re-subnet if possible.

2) Change your real servers' default GW to point to the Alteon. Since the Alteon owns those PIPs it knows how to route the session to the correct port for processing.

2) Disable VMA, /cfg/slb/adv/mat dis. This will force all traffic to be processed on the ingress port, which in this case I believe is port

1. This may affect performance if you have many sessions.

Hope this helps... Angler

ws wrote:

yes this was it, now it works thank You very much

best regards

WS