INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Simple loadbalancing config not working on a 11500

Simple loadbalancing config not working on a 11500

(OP)
Hi!

I'm trying to get the following very simple config to work:

CODE

!Generated on 01/03/2007 09:14:03
!Active version: sg0810106

configure


!*************************** GLOBAL ***************************
 
  ip route 0.0.0.0 0.0.0.0 10.55.12.129 1

!************************* INTERFACE *************************
interface e2
   bridge vlan 10

!************************** CIRCUIT **************************
circuit VLAN1

  ip address 10.55.12.155 255.255.255.192

circuit VLAN10

  ip address 10.55.14.75 255.255.255.192

!************************** SERVICE **************************
service ciis0014
  keepalive type http
  ip address 10.55.14.85
  active

service ciis0015
  keepalive type http
  ip address 10.55.14.86
  active

!*************************** OWNER ***************************
owner Radar-A

  content Radar-A-Frontends
    protocol tcp
    port 80
    vip address 10.55.12.157
    add service ciis0014
    add service ciis0015
    active

Everyting shows up as 'active', if I telnet to port 80 of the VIP, I get a hit, but no webpage.

What is wrong here?

RE: Simple loadbalancing config not working on a 11500

Looks alright initially.

What are the default gateways and subnet masks of the servers on 10.55.14.85 and 10.55.14.86?

RE: Simple loadbalancing config not working on a 11500

(OP)
This is the routing table of 86. The table of 85 is basically the same:

CODE

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      10.55.12.65      10.55.12.86      1
      10.55.12.64  255.255.255.192      10.55.12.86      10.55.12.86      1
      10.55.12.86  255.255.255.255        127.0.0.1        127.0.0.1      1
      10.55.14.64  255.255.255.192      10.55.14.86      10.55.14.86      1
      10.55.14.86  255.255.255.255        127.0.0.1        127.0.0.1      1
   10.255.255.255  255.255.255.255      10.55.12.86      10.55.12.86      1
   10.255.255.255  255.255.255.255      10.55.14.86      10.55.14.86      1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      172.16.4.13  255.255.255.255      10.55.12.66      10.55.12.86      1
      172.16.4.19  255.255.255.255      10.55.12.66      10.55.12.86      1
      172.16.4.48  255.255.255.255      10.55.12.66      10.55.12.86      1
      172.16.4.56  255.255.255.255      10.55.12.66      10.55.12.86      1
        224.0.0.0        240.0.0.0      10.55.12.86      10.55.12.86      1
        224.0.0.0        240.0.0.0      10.55.14.86      10.55.14.86      1
  255.255.255.255  255.255.255.255      10.55.12.86      10.55.12.86      1
  255.255.255.255  255.255.255.255      10.55.14.86      10.55.14.86      1
Default Gateway:       10.55.12.65
===========================================================================
Persistent Routes:
  None

CODE

CSS11501# sh summ
Global Bypass Counters:
   No Rule Bypass Count:     0
   Acl Bypass Count:         0

Owner            Content Rules    State     Services         Service Hits

Radar-A          Radar-A-Frontend Active    ciis0014         3
                                            ciis0015         4


CSS11501# sh keepalive-summary
Keepalives:
AUTO_nexthop00002                State: Alive          10.55.12.129
AUTO_ciis0014                    State: Alive          10.55.14.85
AUTO_ciis0015                    State: Alive          10.55.14.86

I can ping the VIP, and from the switch I can ping the target machines.


RE: Simple loadbalancing config not working on a 11500

Ok from .86 can you ping 10.55.12.65? If so, can you tell me what this device is?

RE: Simple loadbalancing config not working on a 11500

(OP)
The .65 is another router so that means the return traffic is not going back to the loadbalancer.

Another problem is that I'm testing from one of the loadbalanced machines. Might also not work?

RE: Simple loadbalancing config not working on a 11500

Reading your configurations you have a problem where you are using "circuit VLAN1" with a l3 subnet but you don't define which interface to use. The second problem is that VLAN1 is defined local to the system. I recommend defining a second vlan and assigning that to an interface. This would resolve the problem with device #1. You would need to do the same thing with device #2. I have modified your original config with the one that I have provided.




!Generated on 01/03/2007 09:14:03
!Active version: sg0810106

configure


!*************************** GLOBAL ***************************
 
  ip route 0.0.0.0 0.0.0.0 10.55.12.129 1

!************************* INTERFACE *************************
interface e2
   bridge vlan 10

interface e3
   bridge vlan 100


!************************** CIRCUIT **************************
circuit VLAN100

  ip address 10.55.12.155 255.255.255.192

circuit VLAN10

  ip address 10.55.14.75 255.255.255.192

!************************** SERVICE **************************
service ciis0014
  keepalive type http
  ip address 10.55.14.85
  active

service ciis0015
  keepalive type http
  ip address 10.55.14.86
  active

!*************************** OWNER ***************************
owner Radar-A

  content Radar-A-Frontends
    protocol tcp
    port 80
    vip address 10.55.12.157
    add service ciis0014
    add service ciis0015
    active


Michael

WarpZero Technologies
http://www.warpzero.com/

RE: Simple loadbalancing config not working on a 11500

I forgot to mention that you will have to wire interface e3 in order to have traffic communicate to the end systems. This is a supported topology design by Cisco. The second design is a one-arm topology but you are then limited to the throughput of the arm (ie: 100Mb or 1Gb shared) where a 2 arm topology you can have 100Mb to the client and 100Mb to the application.


Michael

WarpZero Technologies
http://www.warpzero.com/

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close