CSM and Bridging mode

[tholmes]

Hello

I need to configure a CSM into bridging mode (its routed at the moment - and working fine via the VIP)

Some users need admin access to the servers via their real IP addresses

When I tried the following configuration it crashed the users on VLAN128, I couldn't PING VLAN128 IP address

If anyone could give this config a quick 'once over' and see if it looks ok I'd appreciate it, I'm going back in Sunday to try again

Thanks Tony

module ContentSwitchingModule 9

vlan 128 client

ip address 10.129.128.10 255.255.252.0

gateway 10.129.128.1

vlan 110 server

ip address 10.129.128.10 255.255.252.0

!

real 10.129.128.101

inservice

real 10.129.128.102

inservice

serverfarm WEB1

nat server

no nat client

real 10.129.128.101

inservice

real 10.129.128.102

inservice

exit

!

vserver VIP1

virtual 10.129.128.254 any

serverfarm WEB1

advertise active

persistent rebalance

inservice

!

interface GigabitEthernet6/3

description *** Real Server 1 ***

no ip address

switchport

switchport access vlan 110

!

interface GigabitEthernet6/4

description *** Real Server 2 ***

no ip address

switchport

switchport access vlan 110

interface Vlan128

user vlan

ip address 10.129.128.1 255.255.252.0

!

[Gilles Dufour]

so can you ping the msfc ip address from the clients ?

If yes, can you ping 10.129.128.10 from the msfc ?

can you ping 10.129.128.10 from the clients ?

The config looks good.

I would check the arp table of msfc and csm.

sho mod csm 9 arp

Regards,

Gilles.

[tholmes]

Thanks for the speedy reply Gilles, I'm not on site now so can't PING test at the moment.

I recall PINGs failed from the clients to the MSFC IP address though. I cleared the arp cache a few times to no avail before having to reload the switch to get them working again (Major car manufacturer - not overly pleased :-) )

I've got a nagging doubt over the fact that the MSFC IP address VLAN(D/G for the real clients) is in the same subnet as the CSM Client and CSM Server IP addresses range.

I think the config is ok too, maybe converting from routed to bridged in a live environment wasn't such a good idea, I'll clear it off and reload before configuring bridging.

Cheers Tony

[Gilles Dufour · Accepted solution]

If you could not ping the MSFC either, there was a L2 issue somewhere.

I would suggest to configure the MSFC first.

Verify connectivity between MSFC and client.

Then configure the CSM.

Do you know you do not need bridge mode to access the server directly ?

You could catch the traffic using a vserver with ip/mask equal to the subnet of the server and a predictor forward serverfarm.

Thanks,

Gilles.

[tholmes]

Hi Gilles,

Thanks for your help, the company dictated using bridge mode so I was stuck with it.

I think you were right, it was a layer 2issue. I reconfigured this morning and it all worked first time!

Cheers for the assistance

Tony