Cisco Content Switch Module Configuration.

Hi,

I am runnig CSM ver 4.3(4) latest CSM Software on WS-C6513 , IOS (12.2(18)SXF8) I had Configured CSM as below:


vlan 170 client // Routed VLAN
  description *** CSM Client VLAN ***
  ip address 172.30.170.8 255.255.255.0
  gateway 172.30.170.1
!
 vlan 172 server // Layer 2 VLAN & its configured on PIX Firewall.
  description *** CSM Servers VLAN ***
  ip address 172.30.172.253 255.255.255.0
  gateway 172.30.172.245 // Firewall Interafce
!
probe HTTP http
  description *** P8_Application_Engine ***
  port 80
!
!
serverfarm CONTENT_ENGINE
  nat server
  no nat client
  predictor leastconns
  description *** P8_Content_Engine ***
  failaction reassign
  real 172.30.172.52
inservice
  real 172.30.172.53
inservice
  health retries 3 failed 30
probe HTTP
!
sticky 1 netmask 255.255.255.255 timeout 180
!
policy CONTENT_ENGIN_P
  sticky-group 1
  serverfarm CONTENT_ENGINE
!
!
vserver CONTENT_ENGINE
  description *** VIP_Content_Engine ***
  virtual 172.30.170.250 any
  serverfarm CONTENT_ENGINE
  advertise active
  inservice

interface Vlan170
 description **** CSM Client VLAN ****
 ip address 172.30.170.3 255.255.255.0
 no ip proxy-arp
 glbp 170 ip 172.30.170.1
 glbp 170 priority 99
 glbp 170 preempt
 glbp 170 load-balancing host-dependent
end




The VLAN 170 Configured as Routed VLAN Interface & Defualt Gateway for VLAN 170 is 172.30.170.1.

The VLAN 172 is Layer 2 VLAN where is routed to firewall & all Servers member of this VLAN as (VLAN access 172)

The Porblem is that if configured the above I am able to ping the Virtual IP but I can not open Port 80 & I had test by run (telnet 172.30.170.250 80) but no luck.
when I ping The VIP the Servers (172.30.172.52 & 172.30.172.53) are replaing but I am not able to open port 80 http using Virtual Address(VIP).

Note:
1. from the test machine I am able to Open Port 80 for the reals Servers (172.30.172.52 / 172.30.172.53),
2. There is  static route configured to route all traffic (172.30.172.53)
to the PIX firewall.
3. & there was no  any logs indicte the problem

Best Regards,
Mohanad