Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

critical reporter and critical service

Good Day CSS Experts,

I am configuring CSS 11503 in VIP and Virtual interface redundancy.

Client----L3S/w--- CSS1----CSS2 -----L2 (stack)--server1

I have understood that rather using upper and lower device ip for monitoring, we should use CSS interface IP in the critical service for best & fast failover result.. So I plan to use critical service to monitor CSS Int. & define the CSS interface IP addresses in the keepalive type script ap-kal-pinglist "client_side_CSS_int_ip Srvr_side_CSS_int_ip"

1. What IP address should I assign to the service used for critical server? I can define the above keepalive but, the service upstream_downstream_CSS, does not accepts the CSS IP address and so I can?t activate the service without IP address?


I understand that we can not use critical reporter vrid-peering & physical interface at the same time.

2. Should I use a critical reporter using vrid-peering or physical interface with the critical service I mentioned above?

Goal is to have best failover if any bit goes down with the related environment L3----CSS---L2---server1

Also, any best working solution opinion welcome!



New Member

Re: critical reporter and critical service

Good Day,

Any suggestions on the above shall be appreciated.

Also, do i need to have critical service and critical reporter configured on the standby CSS as well ?




Re: critical reporter and critical service


In your case, what you are trying to achieve is a topology called "fate sharing". A CSS has 2 circuits, a client side and server side. When we use 2 CSS as a failover pair, there were situations that client circuit of 1st CSS coupled to server circuit of 2nd CSS resulting in an asymmetric traffic flow lead to traffic disruptions. This is no good and we do not want this to happen. To avoid this we go for a solution using critical services and reporter services. You know what is a reporter service as I can see you had used it in the right sense.

When you use 'critical services' you need to monitor ip addresses that is always outside the CSS box. We then would use 2 ip addresses, one for each circuit.

1/ On your 'client side' circuit you need to monitor an ip usually your CSS's default gateway.

2/ On your 'server side' circuit you need to monitor an ip (usually the management ip) of the L2 switch.


service upstream_downstream

ip address

ip address


Yes on both the boxes configure the cri services same way, same ip addresses etc.

However on the reporter config will have different ips as per the circuit interface ip.

Hope this would help. Good luck!