|
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.1.1:587 lc
-> 10.254.254.3:587 Route 1 0 0
-> 10.254.254.2:587 Route 1 0 0
TCP 10.0.1.1:80 lc
-> 10.254.254.3:80 Route 1 2 10
-> 10.254.254.2:80 Route 1 2 5
TCP 10.0.1.1:110 lc
-> 10.254.254.3:110 Route 1 0 6
-> 10.254.254.2:110 Route 1 0 7
TCP 10.0.1.1:25 rr
-> 10.254.254.3:25 Route 1 1 0
-> 10.254.254.2:25 Route 1 0 0
UDP 10.0.1.1:53 lc
-> 10.254.254.3:53 Route 1 0 221
-> 10.254.254.2:53 Route 1 0 215
TCP 10.0.1.1:53 lc
-> 10.254.254.3:53 Route 1 0 0
-> 10.254.254.2:53 Route 1 0 0
TCP 10.0.1.1:143 lc
-> 10.254.254.3:143 Route 1 0 0
-> 10.254.254.2:143 Route 1 0 0
FWM 1 lc persistent 600
-> 10.254.254.3:0 Route 1 0 0
-> 10.254.254.2:0 Route 1 0
0
Is normal all this upd to dns connections?
Today, my lvs-dr stop "directing" whitout any aparrent reazon...
I've having some troubles with my lvs director, sometimes I get kernel panics,
I belive is a memory issue,a fisical one, so I have changed the memory.
Everything was OK, til this morning, at 10:05 am, the director stop "directing"
on 110 service...
I log into the members and do a telnet localhost 110 and the pop server was ok.
Also I was getting strange behave with the www, and smtp..
I needed to reboot the director.. and i get this in messages.
The other thing I saw whas this in messages:
un 20 10:08:04 -dlvs kernel: eth0: RealTek RTL8139 Fast Ethernet at 0xccc01f00,
00:50:bf:d3:ba:9c, IRQ 9
Jun 20 10:08:06 -dlvs kernel: eth0: Setting 100mbps full-duplex based on
auto-negotiated partner ability 41e1.
Jun 20 10:08:16 -dlvs kernel: eth0: Setting 100mbps full-duplex based on
auto-negotiated partner ability 41e1.
eth0 negociates it's speed 3 times in the same minute.. any ideas?
How mane connections a lvs director can handle?
|
