IMPAX 6.5.1 Application Server Knowledge Base > Load balancing: Distributing data requests over multiple Application Servers > Maintaining the load-balanced system
The following configuration file represents a distributed mode configuration where three Application Servers are included in the Application Server content pool. The configuration also load balances traffic from modalities (DICOM TCP port 104) to two Network Gateway systems and ASPFTP traffic (TCP port 3040) from the Client to four cache locations.
Cisco supports a subset of the VRRP standard to implement redundant load balancers; therefore, eliminating them as the single-point-of-failure in the environment.
Name: RADAPP Owner: HosptialA State: Active Type: HTTP Balance: Least Connections Failover: N/A Persistence: Enabled Param-Bypass: Disabled Session Redundancy: Disabled IP Redudancy: Not Redundant L3: 10.30.9.65 L4: TCP/Any URL: Redirect: "" TCP RST client if service unreachable: Disabled Rule Services & Weights: 1: RADAPP1-Alive, S-1 2: RADAPP2-Alive, S-1 3: RADAPP3-Suspended, S-1 4: RADAPP4-Suspended, S-1 >>>>>>>>>>>>>> Name: RADNWG Owner: HosptialA State: Active Type: FTP Balance: Least Connections Failover: N/A Persistence: Enabled Param-Bypass: Disabled Session Redundancy: Disabled IP Redudancy: Not Redundant L3: 10.30.9.62 L4: TCP/Any URL: Redirect: "" TCP RST client if service unreachable: Disabled Rule Services & Weights: 1: RADNWG1-Alive, S-1 2: RADNWG2-Alive, S-1 >>>>>>>>>>>>>> Name: RADASPFTP Owner: HosptialA State: Active Type: HTTP Balance: Least Connections Failover: N/A Persistence: Disabled Param-Bypass: Disabled Session Redundancy: Disabled IP Redudancy: Not Redundant L3: 10.30.9.66 L4: TCP/3040 URL: Redirect: "" TCP RST client if service unreachable: Disabled Rule Services & Weights: 1: RADCUR1-Alive, S-1 2: RADCUR2-Alive, S-1 3: RADNWG1-Alive, S-1 4: RADNWG2-Alive, S-1 HospitalA_11501(config)# show run configure !*********************GLOBAL*************************** no restrict xml no restrict web-mgmt bridge spanning-tree disabled ftp non-standard-ports dns primary 10.237.245.144 dns suffix testlab.local ip route 0.0.0.0 0.0.0.0 10.30.9.1 1 !*********************INTERFACE*************************** interface e1 description "test interface" !*********************CIRCUIT*************************** circuit VLAN1 description "base network" ip address 10.30.9.111 255.255.255.0 !*********************SERVICE*************************** service RADAPP1 ip address 10.30.9.54 keepalive type http active service RADAPP2 ip address 10.30.9.46 keepalive type http active service RADAPP3 ip address 10.30.9.55 keepalive type http service RADAPP4 ip address 10.30.9.47 keepalive type http service RADCUR1 ip address 10.30.9.57 active service RADCUR2 ip address 10.30.9.49 active service RADNWG1 ip address 10.30.9.58 protocol tcp port 0 active service RADNWG2 ip address 10.30.9.50 port 0 protocol tcp active !*********************OWNER*************************** owner HospitalA content RADAPP vip address 10.30.9.65 sticky-inact-timeout 10 balance leastconn add service RADAPP1 add service RADAPP2 add service RADAPP3 add service RADAPP4 protocol tcp active content RADASPFTP vip address 10.30.9.66 add service RADCUR1 add service RADCUR2 advanced-balance sticky-srcip balance leastconn protocol tcp port 3040 add service RADNWG1 add service RADNWG2 sticky-inact-timeout 10 no persistent active content RADNWG vip address 10.30.9.62 add service RADNWG1 protocol tcp add service RADNWG2 balance leastconn sticky-inact-timeout 10 port 104 add service RADNWG1 application ftp-control active !*********************GROUP*************************** group DICOM vip address 10.30.9.62 add service RADNWG1 add service RADNWG2 active
See also
Recommended Cisco settings for a load-balanced environment
Topic number: 57889 Applies to: IMPAX 6.5.1 Application Server Knowledge Base |