Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 122)

106 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Miscellaneous options
2
Miscellaneous options
Changing a real server’s IP address
The Brocade Virtual ADX enables you to easily change a real server’s IP address, even when the
real server is active. This capability is useful when you want to perform some maintenance on the
real server (either the server itself or the server’s configuration on the Brocade Virtual ADX) or
when the network topology has changed.
By default, when you change a server’s IP address, the Brocade Virtual ADX performs the change
gracefully, as follows:
• Existing connections are allowed to continue on the old IP address until they terminate
normally.
• New client requests are sent to the new IP address.
Optionally, you can force all existing connections to be reset instead of waiting for them to
terminate normally. When you force the connections to be reset, the Brocade Virtual ADX
immediately resets a connection when it receives client data for the connection.
To change a real server’s IP address, enter commands such as the following.
Virtual ADX(config)#server real rs1
Virtual ADX(config-rs-rs1)#ip-address 10.6.7.8
Syntax: [no] ip-address ip-addr [force-shutdown]
The ip-addr variable specifies the new IP address for the real server.
The force-shutdown parameter immediately resets a client’s connection to the IP address when the
Brocade Virtual ADX receives TCP data from the client. By default, the Brocade Virtual ADX allows
existing connections to terminate normally following the address change.
Full err The number of times the Brocade Virtual ADX could not add a new PBSLB entry to
the table because the PBSLB is already full. This value should indicate the number by
which the downloaded pbslb table size exceeds the value that the Brocade Virtual
ADX supports.
When the PBSLB list is downloaded, it is first populated into a flat table that does not
have any hierarchy. After populating this table, the MP will construct the DP table to
actually store the PBSLB entries for later lookups. Even when the MP synchs the
PBSLB info to the BPs, it is the flat table that is pushed down and not the DP table.
Full error refers to those error cases where new entries cannot be added to the DP
table because the tree is already full. Table full error refers to those error cases
where no more entries can be added to the flat table because the flat table is filled
up.
Unknown err Is used to catch miscellaneous unexpected errors. For example, if the download
buffer of the PBSLB table from MP to BP is corrupted. Another example is when we
try to add an entry to the tree and the entry cannot be added due to an unexpected
error.
TABLE 12 Error messages (Continued)
Message Description