|
OK
Thanks: now the administration interface (10.0.4.XX) is accesible. Only one "strange" thing about the web GUI and the administration interfaces: I've defined a virtual IP for the cluster and configured the GUI service to listen only at the "cluster interface" BUT then the GUI service DOESN'T LISTEN AT THE VIRTUAL IP, but only at the physical IPs...is this normal/right? * when using clusters GUI service only allow 2 options: cluster interface and "all interfaces"...and obviously I consider use "all interfaces" is too "insecure" (perhaps I'm a little paranoid ;-) ). * If I select to listen at "all interfaces" then GUI service listens at ALL interfaces, including the cluster virtual IP, so in this case the behaviour is as expected Example: in my case: node1: eth0=10.0.4.99, node2: eth0=10.0.4.98 and cluster virtual IP: eth0:1=10.0.4.100, and when select "cluster interface" make the GUI service to listen only at 10.0.4.98/99 but NOT at 10.0.4.100 If this is the right behaviour...Can I suggest as an enhancement to do the GUI service listen also at the virtual IP when cluster and listen on "cluster interface" are selected/defined? Regards. 
Jose Manuel Blanco Cortiñas
|
------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
