Dear All,
I am planning to upgrade a few installations running on 3.10.2 to latest
4.x (what is the latest-known-to-be-running-well version btw?) via yum.
I've tried installing a test system with the latest 4.0.1 centos iso few
weeks ago but that throw error 'sipxecs package cant be located' when
the installer started and even though i tried the 'unstable' 4.0.1.x
Centos ISO and proceed the installation I've noticed the ZONE files
under /var/named/domain...... were different.
So far I am only aware of one URL, which is the wiki page for upgrading
3.10.x to 4.0.1, but that doesn't clearly indicates the possible issues
with ZONE files for named.
Taking into account the issues encountered by Martin and Dave (quoted
below) with ZONE files (being overwritten overnight) and the fact that
other installations are at remote locations where clear ISO installation
is not an option I've only one upgrade path which is through yum.
I'll attempt to carry the installation by following the Wiki tutorial
but I would like to check on how to solve the ZONE file issues.
As the same sipx boxes are used as local DNS server to their respective
LAN network, I am planning to backup the zone files (from 3.10.2 running
system) and then overwrite them back after the yum upgrade to latest 4.x
(which version do you advise?).
But the post from Martin and Dave and the wiki page not clarifying this
issue in details, sets me back in terms of going ahead.
I'll really appreciate your valuable input and advise on these.
On a related note, the phones are Polycom 330 running on ROM 4.0 with
SIP 2.2.2 (which was the only stable pair after trying various ROM and
SIP versions for 3.10.2 (upgraded from 3.8 CENTOS ISO installation via yum).
So I am not quite sure on which ROM and SIP version to use, assuming the
upgrade to latest 4.x goes well, that is known to be solid/stable?
All the best!
Subject:
Re: [sipX-dev] Upgrade problem
From:
"Martin Steinmann" <msteinm...@nortel.com>
Date:
Thu, 2 Jul 2009 10:05:27 -0400
To:
"Dave Deutschman" <ddeutsch...@innovational.net>,
<sipx-...@list.sipfoundry.org>
Precedence:
list
MIME-Version:
1.0
References:
<e4696b1964157942a51573402c7410d20448f...@zrtphxm2.corp.nortel.com>
<ffc2420bfaa447db9b65fb055b0bd...@ddlaptop2>
In-Reply-To:
<ffc2420bfaa447db9b65fb055b0bd...@ddlaptop2>
Message-ID:
<e4696b1964157942a51573402c7410d2044df...@zrtphxm2.corp.nortel.com>
Content-Type:
multipart/alternative; boundary="----_=_NextPart_001_01C9FB1E.28527AB1"
Message:
3
I am not sure how to exactly reproduce this, but I am apparently not the
only one seeing this (see below from Dave).
After I restored the zone file in /var/named after the upgrade, it got
overwritten again overnight. I.e. I restored the correct zone file and
let the sipXecs 4.0 system run overnight and in the morning it again
overwrote the zone file with a file that only includes the records
needed by the sipXecs system with all the other additional records gone.
There again is no backup of the original file left on the system that I
can find. It only overwrites the zone file and not the corresponding
reverse lookup (IN PTR) file.
--martin
------------------------------------------------------------------------
*From:* Dave Deutschman [mailto:ddeutsch...@innovational.net]
*Sent:* Wednesday, July 01, 2009 3:32 PM
*To:* Steinmann, Martin (BL60:2500)
*Subject:* RE: [sipX-dev] Upgrade problem
Martin,
Yes, we discovered that also. It also appears that it overwrites the
file if you add a domain alias. I was planning on opening a JIRA on the
issue but had not gathered all the data. You are correct that this is
an issue especially if you have your gateways defined as hosts.
DD
------------------------------------------------------------------------
*From:* sipx-dev-boun...@list.sipfoundry.org
[mailto:sipx-dev-boun...@list.sipfoundry.org] *On Behalf Of *Martin
Steinmann
*Sent:* Wednesday, July 01, 2009 12:21 PM
*To:* sipx-...@list.sipfoundry.org
*Subject:* [sipX-dev] Upgrade problem
Doing an upgrade from 3.10.3 to 4.0.1 it seems to silently overwrite the
DNS zone file on the machine -- without even creating a backup of the
file it overwrites. That is very un-nice
--martin
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
