Page 1 of 1

Appliance Beta5 issues

Posted: Wed Aug 29, 2012 10:42 am
by AndreasST
Griaß di!
I downloaded the beta-OVA zca-8.0.0.0-116_OVF10.ova and installed on vSphere5 Hypervisor (free edition).

After deploying the OVA, the VM starts normaly (i thought), and the "welcome screen" is displayed in the console.

Screen says that all IPs are 127.0.0.1

OK - lets change in the appropriate system file. Done - works (i'm very proud of this, 'cause i am a windows guy...).

After a little testing i shutted down the VM for holidays.

Started the Vm after my holidays, all IP changes are gone.
Let's search for information...

In the forum i found this post http://www.zimbra.com/forums/installation/57513-zcs-8-0-beta-5-appliance.html#post244849 with the network properties screenshot.

During the deploymant of the OVA i never was asked for the IP configuration.

I tried a new deployment, but no screen for the IP config.
Did i miss something?

Appliance Beta5 issues

Posted: Thu Aug 30, 2012 2:04 am
by friedmar
Nope, same here!

Appliance Beta5 issues

Posted: Thu Aug 30, 2012 4:52 pm
by 1542brian
The IP configuration prompts only appear when deploying against vCenter. The IP address reverting vSphere, Workstation and Fusion is addressed in the GA release which will be out shortly.

Appliance Beta5 issues

Posted: Thu Sep 13, 2012 11:33 pm
by Tim.iTelework
This was not addressed as of: 8.0.0 GA Release (zca-8.0.0.0-1147_OVF10.ova)
I just installed today on vSphere Server (Img: ESXi-5.0.0-20120302001-standard) using vSphere Client 5.0.0 (Build: 623373) and still no method to set or configure the network settings.
All IP's on the "initial configuration and virtual appliance managment interface" (start-up blue screen) are set to 127.0.0.1
Any attempts to configure the network (i.e. Select Login at the blue screen and run: /opt/vmware/share/vami/vami_config_net) are OVERWRITTEN once the VM restarts.
As far as I can tell, there has been no solution or fix for this. I've been searching / troubleshooting / trying things going on 6 hours now (today) and nothing useful yet.

Appliance Beta5 issues

Posted: Fri Sep 14, 2012 3:03 pm
by sreeni
Could you please execute ovfenv at the console and attach the output here ?
Also, please attach the log file /opt/vmware-zca-installer/zca-fixhosts.log content.
We have verified that this works, but we would like to see if this is a different kind of a problem.
[quote user="Tim.iTelework"]This was not addressed as of: 8.0.0 GA Release (zca-8.0.0.0-1147_OVF10.ova)
I just installed today on vSphere Server (Img: ESXi-5.0.0-20120302001-standard) using vSphere Client 5.0.0 (Build: 623373) and still no method to set or configure the network settings.
All IP's on the "initial configuration and virtual appliance managment interface" (start-up blue screen) are set to 127.0.0.1
Any attempts to configure the network (i.e. Select Login at the blue screen and run: /opt/vmware/share/vami/vami_config_net) are OVERWRITTEN once the VM restarts.
As far as I can tell, there has been no solution or fix for this. I've been searching / troubleshooting / trying things going on 6 hours now (today) and nothing useful yet.[/QUOTE]

Appliance Beta5 issues

Posted: Fri Sep 14, 2012 4:25 pm
by Tim.iTelework
Results of: ovfenv

--

root@mail103:~# ovfenv

Unable to find the ovf environment.

--
zca-fixhosts.log repeats the same few lines, and since I couldn't get attachment to work, I will just paste a few iterations of the repeated log entries:
root@mail103:~# cat /opt/vmware-zca-installer/zca-fixhosts.log

Tue Jul 10 22:41:20 UTC 2012 : debug started

Tue Jul 10 22:41:21 2012 :Starting zca-set-network script

zca_ip=127.0.0.1

zca_netmask=255.255.255.0

zca_gateway=default

Updating network with 127.0.0.1 255.255.255.0 default

Tue Jul 10 22:41:21 2012:Done.

Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.

Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.

Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.

Thu Sep 13 16:45:10 UTC 2012 : debug started

Thu Sep 13 16:45:28 2012 :Starting zca-set-network script

zca_ip=127.0.0.1

zca_netmask=255.255.255.0

zca_gateway=default

Updating network with 127.0.0.1 255.255.255.0 default

Thu Sep 13 16:45:28 2012:Done.

Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.

Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.

Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.

Thu Sep 13 10:18:54 PDT 2012 : debug started

Thu Sep 13 10:19:12 2012 :Starting zca-set-network script

zca_ip=127.0.0.1

zca_netmask=255.255.255.0

zca_gateway=default

Updating network with 127.0.0.1 255.255.255.0 default

Thu Sep 13 10:19:12 2012:Done.

Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.

Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.

Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.

Appliance Beta5 issues

Posted: Mon Sep 17, 2012 6:37 pm
by Tim.iTelework
After poking around in /opt/vmware-zca-installer/bin/zca-fixhosts, I can see that it does a lot of editing of the network config AND runs on start-up. Most likely this is the culprit.
I also found: /opt/vmware/share/vami/vami_get_network
Which results in:

------------

root@mail103:~# /opt/vmware/share/vami/vami_get_network

interface: eth0

config_present: true

config_flags: STATICV4

config_ipv4addr: 127.0.0.1

config_netmask: 255.255.255.0

config_broadcast: 127.0.0.255

config_gatewayv4:

config_ipv6addr:

config_prefix:

config_gatewayv6:

autoipv6:

active_ipv4addr: My.Correct.Internal.IP

active_netmask: 255.255.255.0

active_broadcast: My.Correct.B.Cast

active_ipv6addr:

active_prefix:

active_gatewayv4: My.Correct.Gateway.IP

active_gatewayv6:

hasdhcpv6: 0

managed: Managed Internally

------------
I will try to disable / configure correctly some how!

Appliance Beta5 issues

Posted: Wed Sep 19, 2012 12:53 pm
by sreeni
Hi,
Sorry for late response. But can you please do these steps.
1) clear the log file zca-fix-hosts.log
2) re-configure the network with /opt/vmware/share/vami/vami_config_net
3) re-boot the appliance.
4) and please send us the log file and also check whether the network parameters stayed.
Some how the network parameters did not get set correctly. If the OVFENV says nothing available,

we won't fix any network stuff.