03-07-2010 10:37 PM
Dear All,
I have the set up which I have attached. To brief, I have 2 CSS 11501 in two different locations connected each other via fibre and running redundnacy protocol on the link as heartbeat.
The problem I am facing is if the interface through which the services are running fails the redundancy is not happening the master remains the master and the standby is standby and we have a services unavailable.
the configuration is given below
CSS_ACTIVE# sh run
!Generated on 03/07/2010 22:26:21
!Active version: sg0810106
configure
!*************************** GLOBAL ***************************
username admin des-password lcof1eugqece2afd superuser
bridge spanning-tree disabled
arp timeout 1400
no restrict web-mgmt
ip redundancy master
app
app session 10.90.1.2
ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
!************************* INTERFACE *************************
interface e1
trunk
vlan 11
default-vlan
vlan 20
vlan 21
interface e9
description "REDUNDANCY - CSS-STANDBY PORT 9"
bridge vlan 23
!************************** CIRCUIT **************************
circuit VLAN11
description "MANAGEMENT IP ADDRESS"
ip address 10.7.10.20 255.255.255.0
circuit VLAN20
description "CSS_SERVER_VLAN"
redundancy
ip address 10.50.7.4 255.255.255.0
circuit VLAN21
description "CSS_CLIENT_VLAN"
redundancy
ip address 10.50.9.7 255.255.255.0
circuit VLAN23
description "REDUNDANT LINK TO CSS-STANDBY"
ip address 10.90.1.1 255.255.255.0
redundancy-protocol
!************************** SERVICE **************************
service Web1
ip address 10.50.7.5
active
service Web2
ip address 10.50.7.6
active
!*************************** OWNER ***************************
owner KIM
content web
add service Web1
add service Web2
vip address 10.50.9.2
advanced-balance sticky-srcip
active
CSS_ACTIVE#
CSS_STANDBY# sh run
!Generated on 03/07/2010 22:31:42
!Active version: sg0810106
configure
!*************************** GLOBAL ***************************
ip redundancy
bridge spanning-tree disabled
arp timeout 1400
no restrict web-mgmt
app
app session 10.90.1.1
ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
!************************* INTERFACE *************************
interface e1
description "TRUNK "
trunk
vlan 11
default-vlan
vlan 20
vlan 21
interface e9
description "REDUNDANCY - CSS-STANDY PORT 9"
bridge vlan 23
interface Ethernet-Mgmt
phy 10Mbits-FD
admin-shutdown
!************************** CIRCUIT **************************
circuit VLAN11
description "MANAGEMENT IP ADDRESS"
ip address 10.7.10.21 255.255.255.0
circuit VLAN20
description "CSS_SERVER_VLAN"
redundancy
ip address 10.50.7.4 255.255.255.0
circuit VLAN21
description "CSS_CLIENT_VLAN"
redundancy
ip address 10.50.9.7 255.255.255.0
circuit VLAN23
description "REDUNDANT LINK TO CSS-STANDBY"
ip address 10.90.1.2 255.255.255.0
redundancy-protocol
!************************** SERVICE **************************
service Web1
ip address 10.50.7.5
active
service Web2
ip address 10.50.7.6
active
!*************************** OWNER ***************************
owner KIM
content web
add service Web1
add service Web2
vip address 10.50.9.2
advanced-balance sticky-srcip
active
CSS_STANDBY#
If the interface e1 fails on active the redundancy is not shifting to standby.
Solved! Go to Solution.
03-08-2010 05:06 AM
You have setup box-to-box redundancy.
This mechanism is very basic and only detects a box failure. So, as long as the master can send heartbeat through the 'redundancy protocol' interface it will stay master.
You should use interface/vip redundancy.
A little bit more complex to configure but much more robust and with more features including interface failure detection.
Gilles.
03-08-2010 05:06 AM
You have setup box-to-box redundancy.
This mechanism is very basic and only detects a box failure. So, as long as the master can send heartbeat through the 'redundancy protocol' interface it will stay master.
You should use interface/vip redundancy.
A little bit more complex to configure but much more robust and with more features including interface failure detection.
Gilles.
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: