Index
A
B
C
D
E
F
G
H
I
K
L
M
N
O
P
Q
R
S
T
U
V
W
A
- accessibility
- active cookie affinity
(1), (2), (3)
- add
- adding
- address mapping file
- advisors
- CBR component
- cbrcontrol
- controllers
- custom sample
- Dispatcher component
- Caching Proxy advisor
- customize
- fast-failure detection
- interval for
(1), (2)
- list of
(1), (2)
- name of
- port for
- report
- report on the state of
- report timeout
(1), (2)
- self advisor
(1), (2)
- server connect timeout
(1), (2), (3)
- server receive timeout
(1), (2), (3)
- server retry
(1), (2), (3)
- starting
(1), (2)
- starting/stopping
- stopping
- version of
- dscontrol
- HTTP advisor request/response
- limitation on Solaris
- list of
- sample configuration file
- Site Selector
- fast-failure detection
- interval
- interval for
- list
- list of
(1), (2)
- loglevel
- name of
- port for
(1), (2)
- report on the state of
(1), (2)
- report timeout
(1), (2)
- server connect timeout
(1), (2), (3)
- server receive timeout
(1), (2), (3)
- server retries
- server retry
- starting
(1), (2)
- stopping
(1), (2)
- version of
(1), (2)
- sscontrol
(1), (2)
- URL option, HTTP advisor
- advisors, Load Balancer component
- affinity (sticky)
- active cookie
(1), (2), (3)
- affinity address mask
- cross port affinity
(1), (2), (3)
- how it works
- passive cookie
(1), (2), (3)
- port affinity override
- quiesce now
(1), (2), (3)
- rule option
- SSL ID (cbr forwarding)
(1), (2)
- sticky (port affinity override)
(1), (2), (3)
- stickymask
(1), (2), (3)
- stickytime
(1), (2), (3), (4), (5)
- URI
(1), (2), (3)
- affinity address mask
(1), (2)
- AIX
- alerts
- alias
B
C
- Caching Proxy
- Caching Proxy advisor
- CBR
- cbr forwarding method
(1), (2)
- cbrcontrol command
- cbrserver
- ccocontrol command
- ccoserver
- checking for
- Cisco CSS Controller
- Cisco CSS Controller component
- cluster
- cluster-specific
- collocate
- collocate, Load Balancer and client
- collocate, Load Balancer and server
(1), (2), (3), (4), (5), (6)
- collocate with nat
- collocated (keyword)
(1), (2)
- command line
- command references
- commands
- configuration
- connections, setting proportion of importance
(1), (2)
- connecttimeout
- consultant
- ccocontrol
(1), (2)
- Cisco CSS Controller
- nalcontrol
(1), (2)
- Nortel Alteon Controller
- starting
(1), (2)
- Content Based Routing
- content rule
(1), (2)
- controller
- controllers
- cross port affinity
(1), (2)
- custom (customizable) advisor
(1), (2)
D
- DB2 advisor
- default.cfg
(1), (2), (3)
- defining
- deleting
- Denial of service attack detection
- diagnosing problems
- advisors and reach targets mark all servers down (Windows)
(1), (2), (3)
- advisors not working
- advisors not working in high availability setup after network outage (Windows)
- alias returned instead of local address
- blue screen displays when starting Load Balancer executor
- cannot create registry on port 13099
- cannot create registry on port 14099
- CBR will not run
- cbrcontrol fails on Solaris
- cbrcontrol or lbadmin command fails
- ccocontrol or lbadmin command fails
- ccoserver will not start
- Client requests fail when attempting return of large page responses
- common problems and solutions
(1), (2), (3), (4), (5), (6), (7)
- configuring metric server in a two-tier configuration
- consultant connection error
(1), (2)
- corrupted Latin-1 national characters appear (Windows)
- Corrupted Latin-1 national characters appear (Windows)
(1), (2), (3), (4)
- delay when loading Load Balancer configuration
- disconnect from host, using Web administration
(1), (2), (3), (4), (5)
- Dispatcher, Microsoft IIS, and SSL do not work
- Dispatcher and server will not respond
- Dispatcher high availability not working
- Dispatcher requests not routed
- Dispatcher will not run
- do not use IP address add command for aliasing loopback (Linux)
- dscontrol or lbadmin command fails
- error message when trying to view online Help
- error running Dispatcher with Caching Proxy installed
- extra routes
- GUI does not display correctly
- GUI does not start correctly
- help panels disappear
- High availability, configuration tips
- high availability in the wide area mode of Load Balancer does not work
- IP address conflict when using high availability
- IP address not resolving over remote connection
- Java memory/ thread error (HP-UX)
(1), (2)
- Java memory/thread error (HP-UX)
(1), (2), (3)
- Java warning message appears when installing service fixes
- Korean fonts undesirable on AIX and Linux
- lbadmin disconnects from server after updating configuration
- Load Balancer cannot process and forward a frame
- Load Balancer processes end (Solaris)
- Metric Server IOException on Windows
- Metric Server log reports "Signature is necessary for access to agent"
- Metric Server not reporting loads
- Metric value returns -1 after start Metric Server
- nalcontrol or lbadmin command fails
- nalserver will not start
- not registering server loads
- on AIX, ps -vg command output becomes corrupted
- On Linux, Dispatcher forwards packets, but not received by backend server
- On Linux, HA Dispatcher may fail to synchronize
- On Linux, limitations when using zSeries or S/390 servers
- On Linux, memory leak occurs when using manager and advisors
- on Solaris, scripts produce unwanted console messages
- On Windows, "server not responding" error occurs
- On Windows system, problem with high availability takeover
- Path to Discovery prevents return traffic with Load Balancer
- port numbers used by CBR
- port numbers used by Cisco CSS Controller
- port numbers used by Nortel Alteon Controller
- port numbers used by Site Selector
- port numbers used by the Dispatcher
- primary and backup machines active in high availability configuration
- problem resolving IP address to host name (Windows)
(1), (2)
- refresh command not updating configuration
(1), (2)
- requests not being load balanced
- router address not specified or not valid for port method
- Site Selector does not load-balance correctly
- Site Selector does not round-robin (Solaris)
- Site Selector will not run
- slow response time
- sscontrol or lbadmin command fails
- ssserver failing to start on Windows
- Syntactical or configuration error
- Unable to add heartbeat
- unexpected behavior loading large configuration file
- unexpected behavior with "rmmod ibmlb"
- unexpected GUI behavior with Matrox AGP cards
(1), (2), (3), (4), (5)
- Upgrading Java provided with the installation
- Web server binding to 0.0.0.0
- weights not updated by switch
(1), (2)
- Dispatcher
- Dispatcher component
- displaying
- global values and their default settings
- internal counters
- list of
- advisors currently providing metrics
(1), (2)
- report on the state of an advisor
(1), (2), (3)
- statistics report
(1), (2), (3)
- status of
- version number
- down, marking a server as
(1), (2), (3)
- DPID2
- dscontrol command
- dsserver
E
F
G
H
I
- IBM Firewall (restriction)
- ibmlb.conf
- ibmproxy
(1), (2)
- ifconfig command
(1), (2), (3), (4)
- information, gathering
- installing
- interval, setting how often
- the advisor queries the servers
(1), (2)
- the manager queries the executor
(1), (2)
- the manager updates the weights to the executor
(1), (2), (3), (4)
K
L
- lbkeys
(1), (2), (3)
- lbwebaccess
(1), (2)
- Linux
- Load Balancer
- benefits
- configuration tasks, advanced
(1), (2)
- configuring
- functions
(1), (2)
- installing
- operating and managing
(1), (2), (3), (4), (5)
- overview
(1), (2)
- planning considerations
(1), (2)
- quick start example
- troubleshooting
- updating
(1), (2), (3)
- load-balancing settings (optimizing)
(1), (2)
- log
- binary, for server statistics
- file, setting the name of
- level, setting
- size, setting
- for the advisor
(1), (2), (3), (4)
- for the consultant
- for the manager
(1), (2), (3), (4), (5), (6)
- for the server
(1), (2)
- for the subagent
(1), (2)
- using CBR logs
- using Cisco CSS Controller logs
(1), (2)
- using Load Balancer logs
- using Metric Server logs
- using Site Selector logs
- logstatus
- loopback
- loopback device
M
N
O
P
Q
R
- refresh configuration remotely
- remote administration
(1), (2), (3), (4)
- remote administration (Web-based)
- remove
- report
- requirements
- resolution, GUI
- restart all servers to normalized weights
(1), (2), (3)
- RMI (Remote Method Invocation)
(1), (2), (3), (4), (5), (6)
- route command
(1), (2)
- routes, delete extra
- routes, extra
- rule
- rules-based load balancing
- active connections to port
(1), (2)
- always true
(1), (2), (3), (4), (5)
- choice of rules, by component
- client IP address
(1), (2), (3), (4), (5)
- client port
(1), (2)
- connections per second
(1), (2)
- content of request
(1), (2), (3)
- evaluate option
- metric all
- metric average
- metricall
- metricavg
- reserved bandwidth
(1), (2), (3), (4)
- server evaluate option
- shared bandwidth
(1), (2), (3), (4)
- time of day
(1), (2), (3), (4), (5)
- type of service (TOS)
(1), (2), (3)
S
- sample configuration files
- scripts
- Secure Sockets Layer
- sensitivity threshold
- sensitivity to weights update, setting
(1), (2), (3), (4)
- server
- adding
(1), (2)
- address
- advisorrequest
- advisorresponse
- cbrcontrol
- ccocontrol
- collocated
(1), (2)
- collocated with nat
- cookievalue
- defining to a port
(1), (2), (3)
- dscontrol
- fixedweight
- logical
- mapport
(1), (2)
- marking as being down
(1), (2), (3)
- marking as being up
(1), (2), (3)
- nalcontrol
- nonsticky (port affinity override)
(1), (2)
- partitioning
- physically
- protocol
- quiescing
(1), (2), (3), (4)
- removing
(1), (2), (3)
- reset a down server
- restarting all to normalized weights
(1), (2), (3)
- returnaddress
- router
- setting the weight
(1), (2)
- sscontrol
- unquiescing
- weight
- service
- set
- setting
- cluster address
- how often the manager should query the executor
(1), (2)
- interval time
- for the advisor to query the servers
(1), (2)
- for the manager to update the executor
(1), (2), (3), (4)
- logging level
- maximum size of the log
- maximum weight
- for servers on a specific port
(1), (2)
- name of log file
- nonforwarding address
- proportion of importance in load balancing
- sensitivity to weights update
(1), (2), (3), (4)
- smoothing index
(1), (2), (3), (4)
- weight for a server
(1), (2), (3), (4)
- settings, displaying all global values
- showing
- global values and their default settings
- internal counters
- list of
- advisors currently providing metrics
(1), (2)
- report on the state of an advisor
(1), (2), (3)
- statistics report
(1), (2), (3)
- status of
- version number
- Simple Network Management Protocol (SNMP)
- Site Selector
- sitename
- smoothing index, setting
(1), (2), (3), (4)
- SNMP
(1), (2)
- software requirements
- Solaris
- sscontrol command
- SSL
- SSL connections
- ssl2http advisor
(1), (2)
- ssserver
- stale timeout
(1), (2), (3), (4)
- starting
- advisor
(1), (2), (3), (4), (5)
- CBR
- Cisco CSS Controller
(1), (2), (3)
- Dispatcher
- executor
(1), (2)
- manager
(1), (2), (3), (4), (5)
- Metric Server
- Nortel Alteon Controller
(1), (2)
- server
(1), (2)
- Site Selector
(1), (2)
- starting and stopping
- statistics snapshot report, displaying
(1), (2), (3)
- status
- status, displaying
- sticky (affinity)
- active cookie
(1), (2), (3)
- affinity address mask
- cross port affinity
(1), (2), (3)
- how it works
- passive cookie
(1), (2), (3)
- port affinity override
- quiesce now
(1), (2), (3)
- sticky (port affinity override)
(1), (2), (3)
- stickymask
(1), (2), (3)
- stickytime
(1), (2), (3), (4), (5)
- URI
(1), (2)
- stopping
- subagents
(1), (2)
- switch consultant
- syntax diagrams
- system metrics
T
- testing
- tls advisor
- trademarks
(1), (2)
- troubleshooting
- advisors and reach targets mark all servers down (Windows)
(1), (2), (3)
- advisors not working
- advisors not working in high availability setup after network outage (Windows)
- alias returned instead of local address
- blue screen displays when starting Load Balancer executor
- cannot create registry on port 13099
- cannot create registry on port 14099
- CBR will not run
- cbrcontrol fails on Solaris
- cbrcontrol or lbadmin command fails
- ccocontrol or lbadmin command fails
- ccoserver will not start
- Client requests fail when attempting return of large page responses
- common problems and solutions
(1), (2), (3), (4), (5), (6), (7)
- configuring metric server in a two-tier configuration
- consultant connection error
(1), (2)
- corrupted Latin-1 national characters appear (Windows)
- Corrupted Latin-1 national characters appear (Windows)
(1), (2), (3), (4)
- delay when loading Load Balancer configuration
- disconnect from host, using Web administration
(1), (2), (3), (4), (5)
- Dispatcher, Microsoft IIS, and SSL do not work
- Dispatcher and server will not respond
- Dispatcher high availability not working
- Dispatcher requests not routed
- Dispatcher will not run
- do not use IP address add command for aliasing loopback (Linux)
- dscontrol or lbadmin command fails
- error message when trying to view online Help
- error running Dispatcher with Caching Proxy installed
- extra routes
- GUI does not display correctly
- GUI does not start correctly
- help panels disappear
- High availability, configuration tips
- high availability in the wide area mode of Load Balancer does not work
- IP address conflict when using high availability
- IP address not resolving over remote connection
- Java memory/ thread error (HP-UX)
(1), (2)
- Java memory/thread error (HP-UX)
(1), (2), (3)
- Java warning message appears when installing service fixes
- Korean fonts undesirable on AIX and Linux
- lbadmin disconnects from server after updating configuration
- Load Balancer cannot process and forward a frame
- Load Balancer processes end (Solaris)
- Metric Server IOException on Windows
- Metric Server log reports "Signature is necessary for access to agent"
- Metric Server not reporting loads
- Metric value returns -1 after start Metric Server
- nalcontrol or lbadmin command fails
- nalserver will not start
- not registering server loads
- on AIX, ps -vg command output becomes corrupted
- On Linux, Dispatcher forwards packets, but not received by backend server
- On Linux, HA Dispatcher may fail to synchronize
- On Linux, limitations when using zSeries or S/390 servers
- On Linux, memory leak occurs when using manager and advisors
- on Solaris, scripts produce unwanted console messages
- On Windows, "server not responding" error occurs
- On Windows system, problem with high availability takeover
- Path to Discovery prevents return traffic with Load Balancer
- port numbers used by CBR
- port numbers used by Cisco CSS Controller
- port numbers used by Nortel Alteon Controller
- port numbers used by Site Selector
- port numbers used by the Dispatcher
- primary and backup machines active in high availability configuration
- problem resolving IP address to host name (Windows)
(1), (2)
- refresh command not updating configuration
(1), (2)
- requests not being load balanced
- router address not specified or not valid for port method
- Site Selector does not load-balance correctly
- Site Selector does not round-robin (Solaris)
- Site Selector will not run
- slow response time
- sscontrol or lbadmin command fails
- ssserver failing to start on Windows
- Syntactical or configuration error
- Unable to add heartbeat
- unexpected behavior loading large configuration file
- unexpected behavior with "rmmod ibmlb"
- unexpected GUI behavior with Matrox AGP cards
(1), (2), (3), (4), (5)
- Upgrading Java provided with the installation
- Web server binding to 0.0.0.0
- weights not updated by switch
(1), (2)
- troubleshooting tables
U
V
W