Brocade Communications Systems 12.4.00 Manual De Usuario
ServerIron ADX Global Server Load Balancing Guide
19
53-1002437-01
Proxy for DNS server
1
Syntax: [no] server real-name <text> <ip-addr>
Syntax: [no] port dns proxy
Syntax: [no] port <port> [disable | enable]
Syntax: [no] port <port> [keepalive]
Syntax: [no] server virtual-name-or-ip <text> [<ip-addr>]
Syntax: [no] bind <port> <real-server-name> <port>
Enabling the GSLB protocol
For security, remote ServerIron ADXs do not listen to TCP port 182 (the GSLB protocol port) by
default. This means the GSLB protocol is disabled on remote site ServerIron ADXs by default. For a
remote ServerIron ADX to use the protocol, you must enable the protocol on the remote ServerIron
ADX (not the GSLB controller).
default. This means the GSLB protocol is disabled on remote site ServerIron ADXs by default. For a
remote ServerIron ADX to use the protocol, you must enable the protocol on the remote ServerIron
ADX (not the GSLB controller).
To enable the GSLB protocol on the site ServerIron ADXs, enter the following command.
ServerIronADX(config)#gslb protocol
Syntax: [no] gslb protocol
The ServerIron ADX uses TCP port 182 for the GSLB protocol by default. You can change the port
number if needed. Refer to
number if needed. Refer to
You also can secure access to a ServerIron ADX by configuring Access Control Lists (ACLs). For
example, you can configure ACLs to control access to the device on TCP port 182. See the “Access
Control Lists (ACLs)“ chapter of the ServerIron ADX Security Guide.
example, you can configure ACLs to control access to the device on TCP port 182. See the “Access
Control Lists (ACLs)“ chapter of the ServerIron ADX Security Guide.
Configuring a site
When you create a site, you give it a name and identify the ServerIron ADXs in it. You can also
enable the administrative preference.
enable the administrative preference.
To configure the server sites shown in
on page 4, enter commands such as the following:
ServerIronADX(config)# gslb site sunnyvale
ServerIronADX(config-gslb-site-sunnyvale)# si-name slb-1 209.157.22.209
ServerIronADX(config-gslb-site-sunnyvale)# si-name slb-2 209.157.22.210
ServerIronADX(config)# gslb site atlanta
ServerIronADX(config-gslb-site-atlanta)# si-name slb-1 192.108.22.111
ServerIronADX(config-gslb-site-atlanta)# si-name slb-2 192.108.22.112
These commands configure two GSLB sites: one in Sunnyvale, the other in Atlanta. Each site
contains two ServerIron ADXs, slb-1 and slb-2, that load balance traffic across server farms. The
GSLB ServerIron ADX you are configuring will use information provided by the other ServerIron
ADXs when it evaluates the servers listed in DNS replies.
contains two ServerIron ADXs, slb-1 and slb-2, that load balance traffic across server farms. The
GSLB ServerIron ADX you are configuring will use information provided by the other ServerIron
ADXs when it evaluates the servers listed in DNS replies.
To set the administrative preference for a site ServerIron ADX to 255, enter a command such as the
following:
following:
ServerIronADX(config-gslb-site-sunnyvale)# si-name slb-1 209.157.22.20 255
To change the preference for a site ServerIron ADX you have already configured, use the same
command syntax. You do not need to reconfigure other site parameters when you change the
preference. For example, to change the preference for a site ServerIron ADX from the default (128)
to 200, enter a command such as the following:
command syntax. You do not need to reconfigure other site parameters when you change the
preference. For example, to change the preference for a site ServerIron ADX from the default (128)
to 200, enter a command such as the following: