03-23-2004 01:53 PM
New to CSS 11506, trying to determine best method for fate sharing when using ASR. Have figured out VIP and Virtual Interface (I think, see below). But can't find any design info about whether to use ip critical-service (and how...) or ip critical-reporter (and how...)?
Are these choices based in some way upon the services?
Thanks,
Joe
</start)
configure
!*************************** GLOBAL ***************************
arp timeout 60
!************************* INTERFACE *************************
interface 1/1
description "Primary port for ASR"
isc-port-one
interface 1/2
description "Secondary port for ASR"
isc-port-two
interface 4/1
bridge vlan 60
phy 100Mbits-FD
interface 4/2
bridge vlan 61
phy 100Mbits-FD
interface 4/3
bridge vlan 62
phy 100Mbits-FD
!************************** CIRCUIT **************************
circuit VLAN60
ip address 10.11.12.217 255.255.255.240
description Main connection to DMZ GW on vlan60
ip virtual-router 60 priority 110
ip redundant-interface 60 10.11.12.219
ip redundant-vip 60 10.11.12.221
ip redundant-vip 60 10.11.12.220
circuit VLAN61
ip address 192.168.232.1 255.255.255.224
description Connection to Vlan 61 for webfarmA
ip virtual-router 61 priority 110
ip redundant-interface 61 192.168.232.3
circuit VLAN62
ip address 192.168.232.33 255.255.255.224
description Connection to Vlan 62 for webfarmB
ip virtual-router 62 priority 110
ip redundant-interface 62 192.168.232.35
!************************** SERVICE **************************
service webfarmA-1
ip address 192.168.232.4
redundant-index 61
protocol tcp
port 80
keepalive type http
keepalive method get
keepalive uri "/index.html"
!active
service webfarmA-2
ip address 192.168.232.5
redundant-index 61
protocol tcp
port 80
keepalive type http
keepalive method get
keepalive uri "/index.html"
!active
service webfarmB-1
ip address 192.168.232.36
redundant-index 62
protocol tcp
port 80
keepalive type http
keepalive method get
keepalive uri "/index.html"
!active
service webfarmB-2
ip address 192.168.232.37
redundant-index 62
protocol tcp
port 80
keepalive type http
keepalive method get
keepalive uri "/index.html"
!active
!*************************** OWNER ***************************
owner web-ownerA
address See So&So at 310-555-9999
content weba-present-rule
protocol tcp
vip address 10.11.12.221
port 80
?? url /*
?? stickiness rules? e.g., advanced-balance sticky-srcip
redundant-index 61 OR 60 ????
active
owner webB-owner
address See So & So at 310-555-9999
content webB-present-rule
protocol tcp
vip address 10.11.12.220
port 80
?? keepalives?
?? stickiness rules?
redundant-index 61 OR 60 ????
active
!*************************** GROUP ***************************
</end>
03-23-2004 03:38 PM
if you are running version 7.3, then you have a choice. The critical reporter is a step in Virtual Router peering, which is a more predictable method of fate sharing than using critical services. It is preferable as long as you meet the following requirements:
--Ensure that you have configured VIP and virtual interface redundancy properly.
--VRID peering is not supported with shared VIP redundancy.
--Ensure that a VR exists before you attempt to configure it on a reporter.
--All VRs associated with a VRID peering reporter must have the same priority and preempt configurations.
--Do not configure the same IP address and VRID on more than one reporter.
--You can configure a maximum of 128 reporters on a CSS.
--You can configure a maximum of four reporters of type VRID peer on a CSS.
--You can configure a maximum of eight VRIDs on a reporter of type VRID peer.
If you meet those requirements then I would suggest reporters. You can see the Virtual Router ID peering
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_730/redundgd/vipredun.htm#1109382
hope that helps
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide