cc/td/doc/product/iaabu/localdir
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring the MNLB Services Manager

Configuring LocalDirector as Services Manager

Services Manager Configuration Examples


2

Configuring the MNLB Services Manager


This chapter describes how to configure a LocalDirector as an MSLB Services Manager to operate in conjunction with routers serving as Forwarding Agents

The components of the MNLD Feature Set for LocalDirector are described in Chapter 1, " Overview: Load Balancing with the MNLB Feature Set for LocalDirector."

Configuring LocalDirector as Services Manager

The MNLB Services Manager chooses the best server for each new packet that arrives, based on the type of load balancing that is configured. The Services Manager notifies the Forwarding Agents of that choice. The Forwarding Agents then direct all subsequent packets of that packet stream to the chosen server.

To configure LocalDirector as a Services Manager, use the following commands:

Step
Command
Purpose

1

casa service-manager port port [password password [password_timeout]]

Sets the UDP ports through which the Services Managercommunicates. The recommended port is 1638.

2

casa service-manager multicast-ttl value

Configures the Services Manager multicast connection time-to-live value.

3

virtual virtual_name | virtual_ip [:virtual_port]:[bind-id]:[protocol]] [service-state]

Defines the virtual servers.

4

real real_name | real_ip[:[port]:[bind-id]:[protocol]] [service-state]

Defines the real servers.

5

bind virtual_id real_id [real_id...]

Associates the virtual server the real server and establishes the load-balancing relationship between the virtual and real servers.

6

redirection virtual_id dispatched casa

Specifies the type of load balancing redirection for the virtual server.


Services Manager Configuration Examples

This section provides an example configuration for a LocalDirector configured as a Services Manager. The network configured is shown in .


Note   The virtual address must not be in the same subnet as the IP address of the Services Manager.


Figure 1 MNLB Feature Set for LocalDirector Configuration

MNLB Services Manager Configuration for SM

SM# wr t
Building configuration...
: Saved
: LocalDirector 420 Version 3.0.0.127
syslog output 20.3
no syslog console
enable password 000000000000000000000000000000 encrypted
hostname SM
no shutdown ethernet 0
no shutdown ethernet 1
no shutdown ethernet 2
no shutdown ethernet 3
interface ethernet 0 auto
interface ethernet 1 auto
interface ethernet 2 auto
interface ethernet 3 auto
mtu 0 1500
mtu 1 1500
mtu 2 1500
mtu 3 1500
multiring all
no secure 0
no secure 1
no secure 2
no secure 3
ping-allow 0
ping-allow 1
ping-allow 2
ping-allow 3
ip address 172.26.56.19 255.255.255.0
route 172.26.10.249 255.255.255.255 172.26.56.20 1
route 206.10.20.33 255.255.255.255 172.26.56.17 1
route 206.10.20.34 255.255.255.255 172.26.56.18 1
no rip passive
failover ip address 0.0.0.0
failover
password cisco
telnet 161.0.0.0 255.0.0.0
no snmp-server contact
no snmp-server location
casa service-manager port 1638
casa service-manager multicast-ttl 60
tftp-server 172.26.10.249 /tftpboot/LD
virtual 12.12.12.1:0:0:tcp is
redirection 12.12.12.1:0:0:tcp dispatched casa wildcard-ttl 60 fixed-ttl 60 igmp 224.0.1.2 port 1637
real 172.26.56.34:0:0:tcp is
real 172.26.56.33:0:0:tcp is
bind 12.12.12.1:0:0:tcp 172.26.56.33:0:0:tcp 172.26.56.34:0:0:tcp
: end

hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Jun 20 12:57:17 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.