Problem with keepalive for LVS-NAT

["Bishop, Cass" <cbishop@xxxxxxxxxxxxxxxxx>]

I am trying to use keepalive with LVS-NAT for a project.  I have keepalives
failover working correctly but I cannot get it to configure the LVS portion.
Here is my config and the result of starting keepalived with the -d option.
None of the LVS Topology or the Health Checker section shows up.  If I run
ipvsadm it shows nothing is configured.  I can't figure out what I have
missed.  Can anyone spot any problems?  I am using LVS-NAT on a single
network.

global_defs {
   notification_email {
     me@xxxxxx
   }
   notification_email_from cass@xxxxxxxx
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   lvs_id Disp_test2
}

vrrp_instance VI_A {
    state MASTER
    interface eth0
    lvs_sync_daemon_interface eth0
    virtual_router_id 1
    priority 200
    advert_int 1
    smtp_alert
    authentication {
        auth_type PASS
        auth_pass Disp
    }
    virtual_ipaddress {
        172.27.7.239
    }
}

virtual_server 172.27.7.239 8080{
    delay_loop 6
    lb_algo rr
    lb_kind NAT
    nat_mask 255.255.252.0
    persistence_timeout 300
    protocol TCP

    real_server 172.27.7.24 8080 {
        weight 10
        TCP_CHECK {
                connect_timeout 3
                connect_port 8080
        }
    }

}

_________________________________

Jan 30 09:33:51 vespasian Keepalived: Starting Keepalived v1.0.0 (06/01,
2003)
Jan 30 09:33:51 vespasian Keepalived: Configuration is using : 43887 Bytes
Jan 30 09:33:51 vespasian Keepalived: Registering Kernel netlink reflector
Jan 30 09:33:51 vespasian Keepalived: ------< Global definitions >------
Jan 30 09:33:51 vespasian Keepalived:  LVS ID = Disp_test2
Jan 30 09:33:51 vespasian Keepalived:  Smtp server = 127.0.0.1
Jan 30 09:33:51 vespasian Keepalived:  Smtp server connection timeout = 30
Jan 30 09:33:51 vespasian Keepalived:  Email notification from =
cass@xxxxxxxxxxxxxxx
Jan 30 09:33:51 vespasian Keepalived:  Email notification =
cbishop@xxxxxxxxxxxxxxxxx
Jan 30 09:33:51 vespasian Keepalived:  Email notification =
2144371548@xxxxxxxxx
Jan 30 09:33:51 vespasian Keepalived: ------< VRRP Topology >------
Jan 30 09:33:51 vespasian Keepalived:  VRRP Instance = VI_A
Jan 30 09:33:51 vespasian Keepalived:    Want State = MASTER
Jan 30 09:33:51 vespasian Keepalived:    Runing on device = eth0
Jan 30 09:33:51 vespasian Keepalived:    Runing LVS sync daemon on interface
= eth0
Jan 30 09:33:51 vespasian Keepalived:    Virtual Router ID = 1
Jan 30 09:33:51 vespasian Keepalived:    Priority = 200
Jan 30 09:33:51 vespasian Keepalived:    Advert interval = 1sec
Jan 30 09:33:51 vespasian Keepalived:    Preempt Active
Jan 30 09:33:51 vespasian Keepalived:    Authentication type =
SIMPLE_PASSWORD
Jan 30 09:33:51 vespasian Keepalived:    Password = Disp
Jan 30 09:33:51 vespasian Keepalived:    VIP count = 1
Jan 30 09:33:51 vespasian Keepalived:      VIP1 = 172.27.7.239/32
Jan 30 09:33:51 vespasian Keepalived:    Using smtp notification
Jan 30 09:33:51 vespasian Keepalived: VRRP sockpool: [ifindex(2),
proto(112), fd(5)]
Jan 30 09:33:52 vespasian Keepalived: VRRP_Instance(VI_A) Transition to
MASTER STATE
Jan 30 09:33:53 vespasian Keepalived: VRRP_Instance(VI_A) Entering MASTER
STATE
Jan 30 09:33:53 vespasian Keepalived: VRRP_Instance(VI_A) setting protocol
VIPs.
Jan 30 09:33:53 vespasian Keepalived: VRRP_Instance(VI_A) Sending gratuitous
ARP on eth0
Jan 30 09:33:53 vespasian Keepalived: Remote SMTP server [127.0.0.1:25]
connected.
Jan 30 09:33:53 vespasian Keepalived: SMTP alert successfully sent.
Jan 30 09:33:58 vespasian Keepalived: VRRP_Instance(VI_A) Sending gratuitous
ARP on eth0


I'm not sure if my problem is with LVS or keepalived so I am posting to both
lists.

Cass Bishop
Web/Voice Systems Engineer
ATX Technologies
972-753-6289

CONFIDENTIALITY NOTICE:  The information in this e-mail is privileged and
confidential.  Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.