Fame Glow Feed

Premium fame highlights with sleek curation.

news

Sample load-balancer- Cisco 11500 Series Content Services Switch - Documentation for Remedy Action Request System 20.02

Writer Matthew Cannon

The BMC Software Quality Assurance department tested a load-balancing configuration using the Cisco 11500 Series Content Services Switch (CSS) with software version WebNS 4.10, 5, 6, 7, build 17s. The two BMC Remedy AR System servers shared a database on another computer, as shown in the following figure. Specific ports were not defined, and the default setting (ON) was used for the persistence (sticky) option. The default setting of round robin was used for our load-balancing technique.

Load-balancer configuration tested by BMC Software

(Click the image to expand it.)

The following configuration was used for the CSS appliance:

!*************************** GLOBAL ***************************
username admin1 des-password <encrypted_password> superuser
username admin2 des-password <encrypted_password> superuser
username admin3 des-password <encrypted_password> superuser
ip route 0.0.0.0 0.0.0.0 172.23.32.1 1
!************************* INTERFACE *************************
interface e5 bridge vlan 10
interface e6 bridge vlan 20
!************************** CIRCUIT **************************
circuit VLAN10 ip address 172.23.32.15 255.255.248.0
circuit VLAN20 ip address 172.23.41.5 255.255.255.0
!************************** SERVICE **************************
service www-server1 ip address 172.23.41.15 active
service www-server2 ip address 172.23.41.16 active
!*************************** OWNER ***************************
owner sample content rule1 add service www-server1 add service www-server2 vip address 172.23.33.95 active

For information about how to configure a load balancer with the Cisco CSS, see the Cisco Systems website at . The following documents are relevant to load-balancer configuration:

Note

Website addresses change frequently. If you have difficulty finding these documents, go to and navigate to the Documentation pages.