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
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.
ip address 10.30.31.5
ip address 10.30.41.15
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.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...