Fail over Question.

[fandikurnia]

Dear all,

I have a question, One of our customer that run at Centos VDS. They always implementation iptables to block eth0 and eth1, We already warn them to unblock private ip on vds, consequently their vds cannot work anymore. And we provisioning another vm for replace their old vm, but now they implement iptables only to block eth0 (public ip) and not root permit to login. But the problem is this vm VDS Centos cannot work again after they reboot that server, my question is how controller work to fail over or starting vm? and what should our client do, if they want implement iptables on their vds.


Regards


Fandi Kurnia
:):):):)

[PeterNic]

When the customer uses a VDS, it is similar to just a regular server; so iptables should be set up normally. The customer should enable eth1 (which, in CentOS/RedHat is the internal NIC). If they block this adapter, the appliance will not be able to report successful start and you will not be able to login from the grid controller.

Repair: you can always stop the VDS and manage the volume and correct the iptables

Alternative: mark the appliance as unmanaged, in which case it will still start OK but AppLogic will not know if the boot completed successfully and it won't be able to log in.

HTH,
- Peter

[fandikurnia]

Hi

I have a new isue, our customer has change their ssh port. Any suggestion for this issue ?

Regards

Fandi Kurnia

[JShelton]

Changing the ssh port will not affect the 'app start' process. It will however prevent you from doing a 'comp login' (using console=text still works) or using the ssh login from the editor.

[PeterNic]

Hi Fandi,

Josh is correct - changing the ssh port number will not affect the app start process.

If you want AppLogic to be able to do "comp login" from the controller into the appliance, you can change the console settings for the appliance - go to Edit Class Boundary, select Virtualization Mode and change the console value - from ssh:22 to ssh:XXX where XXX is the new port number (e.g, if the new port number for SSH is 10022, then change to ssh:10022).

Alternatively, the ssh server on the appliance can be configured to listed on port 22 on the default interface while listening on the custom port on the external interface (as the customer desires it). This way the console setting doesn't need to be changed but it may be a bit harder for some customers to set up.

Best regards,
- Peter