port conflict with two zimbra servers on the same lan

[ecobrazim]

zcs-NETWORK-6.0.9_GA_2686.UBUNTU10_64

Hi all,

My setup will help explain my problem so here it is:

I have a single server running kvm. on that server I have zimbra oss 6.0.8 (live)
and I added a vm to test zimbra ne 6.0.9 (test)

I only have a single IP.

At installation I changed all the default ports to avoid any conflicts with the live zimbra server. so 993 became 1993, etc.

The only port which I can't seem to change is the admin port 7071.

I tried the following as the user zimbra:

$ zmprov ms `zmhostname` zimbraAdminPort 17071

$ zmprov mcf zimbraAdminPort 17071

$ zmlocalconfig -e zimbra_admin_service_port=17071

... each time restarting zimbra with:

$ zmcontrol restart

sadly the port remains on 7071.

Any advice on how to change the admin port or simply setup the two servers to work together without any risk of affecting the live one is very welcome! :)

[ecobrazim]

Did anyone ever manage to change the admin port? I'd really like to try out the network edition but I can't have the admin console conflict with the one in production.

Thoughts and experiences anyone?

[phoenix]

Originally Posted by ecobrazim

Did anyone ever manage to change the admin port? I'd really like to try out the network edition but I can't have the admin console conflict with the one in production.

Thoughts and experiences anyone?

Why don't you set it up in a Split Domain?

[ecobrazim]

Hi phoenix,

Thanks for your reply.

I thought about it but wasn't sure about two things which you might be able to answer:

1. Will I be able to properly test all functionalities of the network edition?
2. How complex will it be to revert back to the original situation?

I have a zimbra oss in 'prod' which I'd like to move to an ne edition but can not risk down time or headaches.

Maybe the easiest would be to ask for an extra ip for a couple of months to test ne properly.

Anyway, any thoughts on the risk to the original infrastructure are welcome

[psgandalf]

If you don't have to be able to access the admin page from outside there is no problem having the same port on two machines. If you need to access from the outside either if you have a firewall/router that can forward port to different port numbers NAT ex:
port 7071 -> port 7071 on prod. server. Port 8081 -> port 7071 on test. server. If that's not an option put a server with pound Apsis Gmbh or another reverse proxy. With such you can forward for an example test.yourdomain.com to testserver port 7071

[phoenix]

Originally Posted by ecobrazim

Hi phoenix,

Thanks for your reply.

I thought about it but wasn't sure about two things which you might be able to answer:

1. Will I be able to properly test all functionalities of the network edition?
2. How complex will it be to revert back to the original situation?

I have a zimbra oss in 'prod' which I'd like to move to an ne edition but can not risk down time or headaches.

Maybe the easiest would be to ask for an extra ip for a couple of months to test ne properly.

Anyway, any thoughts on the risk to the original infrastructure are welcome

There should be no problem using a split domain, you can test the functionality in that environment. The NE would relay through your production server and the production server would forward mail for accounts which don't exist in it's server. To reverse the split domain you need to disable the attributes you've set in the command examples in the wiki article - there's details in the wiki (IIRC) and in the forums on what's needed. Obviously the only thing you woin't get is a full load for incoming email but that shouldn't be a problem.

[ecobrazim]

Hi all,

Thank you so much for your help! I still find it odd that neither of my commands ever changed the default admin port but hey, no matter. I decided to simply buy an extra IP to avoid hours of fiddling on a production environment. That way I might have a few days left to test before the license runs out.

Thanks again for your help and advice.