100%(3)3 out of 3 people found this document helpful
This preview shows page 163 - 165 out of 195 pages.
Click Run. Synchronize GSLB Configuration, window will appear. Observe the sync process. Click Close, once the process completes Click Close. 5.View Synchronization State to verify that synchronization worked: Click View Synchronization Stateunder GSLB Configuration. In case a message, Some of the commands failed, is reported under Applying Changes, please ignore the error message. Click Close. About GSLB Synchronization: More than likely, GSLB synchronization was successful for the intended GSLB Services and GSLB Virtual Servers. However, the GSLB configuration also synchronizes content-switching virtual servers and related entities. You receive a report of a failure; some of the load balancing virtual servers used with an existing CS virtual server configuration in the lab did not replicate to the partner NetScaler. We will manually confirm that the replication completed successfully. 6.NSHA MGMT (192.168.10.103) - Save the NetScaler configuration and confirm. 7.Switch to NS_VPX_03 (172.22.15.201).
164 8.Verify that GSLB configuration synchronized successfully: View GSLB Sites: Browse to Traffic Management >GSLB >Sites. Verify that both GSLB sites are present and in an UP state. This should not have changed. Verify GSLB Services: Browse to Traffic Management >GSLB >Services. Refresh the NetScaler view, if needed. Verify that both services, gslb_svc_ffmand gslb_svc_tok, are present and in an UP state. Verify GSLB Virtual Servers: Browse to Traffic Management >GSLB >Virtual Servers. Refresh the view, if needed. Verify that gslb_vsrv_globalis present and in an UPsate. Select gslb_srv_globaland click Edit. Verify that both services are bound. Verify that the FQDNglobalweb.training.lab is bound under Domains. Click Done. 9.NS_VPX_03 (172.22.15.201) - Save the NetScaler configuration and confirm. The GSLB Synchronization option to save the configuration will not apply to remote nodes if there are synchronization command failures. So, the save configuration must be manually performed. Takeaways: GSLB Sites are configured to represent the NetScaler appliances participating in the GSLB configuration. NetScaler appliances in a GSLB configuration communicate to the GSLB Site IP address of partner NetScaler. GSLB Services represent the potential IP addresses that the FQDN can be resolved to by GSLB. The GSLB Services generally correspond to the IP address of the intended target virtual servers where the traffic will be sent. In this case, the GSLB service IP addresses correspond to the target load balancing virtual server IPs (lb_vsrv_ffm and lb_vsrv_tok). GSLB Services have an UP and DOWN status like regular services. GSLB virtual servers will only select a GSLB service in an UP state. GSLB Service status is controlled by the MEP communication between sites. If monitors are bound to GSLB services, then monitors control the UP and DOWN state of the service, overriding MEP.