Using CSM modules running 3.1.4 in a GSLB setup with ressources in two data centers - east/west - I would like to achieve load balancing between the two data centers (3 servers per location running same application) based on the source IP of the client. To make this work I have to return VIP east/west based on the client IP.
Problem is that the client gets the VIP east/west from the client DNS - not directly from the CSM-DNS. As I see it one way to achieve the balancing could be to return VIP depending on requesting DNS server (as east clients will primarilly be using one and west users another)
Can anyone point me to configuration guides concerning DNS-VIP serverfarm configuration where the answer (local or remote VIP) is based on the source in the DNS packet requesting the VIP.
Also does anyone know if it is possible to change the DNS load balancing algorithm depending on the load of the servers in the farm (ex. return local until load is xx then return leastloaded if remote VIP is less loaded)
The CSS DNS feature enables you to configure one or more CSSs to construct highly available, distributed, and load-sensitive websites. Groups of CSSs may host many distributed websites concurrently. These groups make decisions that can be configured independently for each distributed website using local and remote load-balancing and domain information.
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
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...