cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
488
Views
4
Helpful
6
Replies

CSS 11150 one-arm redundancy

mike
Level 1
Level 1

Hi, There:

I checked web site doc. I found there are some redundancy configuration for in-lin, did anyone try one-arm redundancy configuration?

Thanks,

6 Replies 6

Gilles Dufour
Cisco Employee
Cisco Employee

one-armed redundancy is just the same as any other redundancy setup. Nothing different.

If you do box-box redundancy, the standby is just the exact copy of the active.

All you need is a back-to-back connection between the 2 CSS.

If you do vip/interface redundancy, this is like configuring hsrp.

Weither you have only 1 vlan or more does not matter.

So, the sample config for inline will work for one-armed.

If you are concerned with a particular part of the config, let us know.

Regards,

Gilles.

Hi, Gilles:

Do you mind I could discuss via email, I setup Box-to-Box configuration, it was fine, but later I had the problem, randomly one if the vip I could not access, I have to reboot the box to make it work.

Thanks,

~ml

Hi, Gilles:

Here is the primary CSS configuration

app

app session 172.16.6.2

ip redundancy master

ip route 0.0.0.0 0.0.0.0 10.0.1.1 1

!************************* INTERFACE *************************

interface e11

bridge vlan 2

!************************** CIRCUIT **************************

circuit VLAN1

description "Primary CSS"

ip address 10.0.1.6 255.255.255.0

circuit VLAN42

ip address 172.16.6.1 255.255.255.0

redundancy-protocol

!************************** SERVICE **************************

service test1

ip address 10.0.1.94

keepalive type http

keepalive uri "/test.html"

active

service test2

keepalive type http

keepalive uri "/test.html"

ip address 10.0.1.37

active

service test3

ip address 10.0.1.46

keepalive uri "/monitor.html"

keepalive type http

active

service test4

ip address 10.0.1.45

keepalive uri "/monitor.html"

keepalive type http

active

service test6

ip address 10.0.1.47

active

service test5

ip address 10.0.1.43

active

!*************************** OWNER ***************************

owner rule1

content rule1-rule

add service test1

add service test2

vip address 10.0.1.18

active

owner test2

content test2-rule

add service test5

add service test6

vip address 10.0.1.17

active

owner test1

content test1-rule

add service test3

add service test4

vip address 10.0.1.19

active

!*************************** GROUP ***************************

group Server-rule1

vip address 10.0.1.18

add destination service test1

add destination service test2

active

group Servers-test1

vip address 10.0.1.19

add destination service test3

add destination service test4

active

group Servers-test2

vip address 10.0.1.17

add destination service test5

add destination service test6

active

2ndary CSS, I just changed following

ip redundancy,

app sess 172.16.6.1

circuit VLAN2

ip address 172.16.6.2 255.255.255.0

I sync the configuration with commit_redunancyconfig

sometime I have random problem to access one of the vip, but when I access real servers under that vip, it is ok, Is there a way to troubleshoot this?

Thanks

Mike,

does the problem occurs after a failover or not ?

Is it always the same vip showing the problem ?

To troubleshoot the issue, check with a sniffer trace if traffic is coming to the CSS.

See if the CSS forwards the traffic or not.

Check the destination mac address of traffic coming into the CSS and traffic leaving the CSS.

If you do not see traffic coming in, or if the destination mac address is incorrect, check the arp table of servers and gateways.

Regards,

Gilles.

Hi, Gilles:

the vip arp is the same as CSS interface VLAN1 arp,

If I reboot secondary CSS, the problem went away, even the secondary CSS come back online for a while.

I used the code ap0610412s

Thx

Hi, Gilles:

I think I might find the problem, I forgot to configure the redundancy under the circuit VLAN1

Thanks

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: