Alcatel Carrier Internetworking Solutions 6648 - Manual (Page 297)

Troubleshooting Server Load Balancing Troubleshooting a Partial Failure
OmniSwitch Troubleshooting Guide September 2005 page 17-5
Troubleshooting a Partial Failure
The number one cause of a partial failure is misconfiguration. In the following area, we will show you
how to determine the SLB configuration.
The Troubleshooting Procedure
If you have reason to believe that the SLB cluster is operational, however inaccessible, Alcatel’s 7700/
7800/8800 provides useful commands for narrowing down the problem.
One of the most useful commands used in troubleshooting SLB problems on the 7700/7800/8800 product
line is the show ip slb clusters command.
For example:
-> show ip slb clusters
Admin Operational # %
Cluster Name VIP Status Status Srv Avail
----------------+----------------+--------+-------------------+-----+---------
WorldWideWeb
128.241.130.204 Enabled In Service 3 95
Intranet 128.241.130.205 Enabled In Service 2 100
FileTransfer 128.241.130.206 Enabled Out of Service 2 50
As shown in the example above, this command will provide pertinent information in verifying which
server cluster(s) are inaccessible or malfunctioning.
After you have determined which SLB cluster is not accessible, performing the show ip slb cluster
cluster-name command will provide more detailed information on the configuration and status of the
above named SLB cluster.
The show active policy rule and show policy condition commands are also useful when troubleshooting
SLB problems:
-> show active policy rule
Policy From Prec Enab Act Refl Log Save Matches
SLB-rule-FTP api 65000 Yes Yes No No Yes 7
( L3): SLB-cond-FTP -> SLB-act-FTP
-> show policy condition
Condition Name From Src -> Dest
SLB-cond-FTP api
*IP : Any -> 172.160.1.100