CallManager 5.1.1 Upgrade to 5.1.1a warning...

In situations like this, where you are upgrading to get rid of a
deferred release, I think it's better to revert to the previous
version anyway.

That said, it just reinforces how awesome of a feature the inactive
partition is (yes I work for cisco but that doesn't detract from how
stupendously awesome this feature is).

-Ryan

On Dec 29, 2006, at 2:34 PM, Jonathan Charles wrote:

OK, so, I have a test box that is running CCM5.04... I grabbed the
5.1.1 upgrade when it came out and applied it...

Cisco withdrew it a few days later (apparently it sux and stuff), and
they released 5.1.1a

So, I figure, let's apply it...

It won't.

Apparently, CCM5.1.1 does not see the 5.1.1a file as a valid upgrade
and ignores it.

My guess is that it was designed to be applied to 5.0(4)a and not
5.1.1...

Good thing it is a test box.

BTW, here is the message I get from 5.1.1: "The directory was located
and searched but no valid options or upgrades were available. Note, a
machine cannot be downgraded so option and upgrade files for previous
releases were ignored."

Here is the version info:

Active Version: 5.1.1.1000-7

Here is the file I was truing to use as the upgrade:

cisco-ipt-k9-patch5.1.1.2000-2.tar.gz.sgn

BTW, just a note on how not bad this is, I am going to revert the
system to 5.04 (which is the inactive version on the box) and then
upgrade it...

I will let you know.

Jonathan
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

That is one of the driving forces for us to upgrade...... Hoping around
Spring break.

Scott

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Friday, December 29, 2006 12:05 PM
To: Jonathan Charles
Cc: cisco-voip@puck-nether.net
Subject: Re: [cisco-voip] CallManager 5.1.1 Upgrade to 5.1.1a warning...

In situations like this, where you are upgrading to get rid of a
deferred release, I think it's better to revert to the previous
version anyway.

That said, it just reinforces how awesome of a feature the inactive
partition is (yes I work for cisco but that doesn't detract from how
stupendously awesome this feature is).

-Ryan

On Dec 29, 2006, at 2:34 PM, Jonathan Charles wrote:

OK, so, I have a test box that is running CCM5.04... I grabbed the
5.1.1 upgrade when it came out and applied it...

Cisco withdrew it a few days later (apparently it sux and stuff), and
they released 5.1.1a

So, I figure, let's apply it...

It won't.

Apparently, CCM5.1.1 does not see the 5.1.1a file as a valid upgrade
and ignores it.

My guess is that it was designed to be applied to 5.0(4)a and not
5.1.1...

Good thing it is a test box.

BTW, here is the message I get from 5.1.1: "The directory was located
and searched but no valid options or upgrades were available. Note, a
machine cannot be downgraded so option and upgrade files for previous
releases were ignored."

Here is the version info:

Active Version: 5.1.1.1000-7

Here is the file I was truing to use as the upgrade:

cisco-ipt-k9-patch5.1.1.2000-2.tar.gz.sgn

BTW, just a note on how not bad this is, I am going to revert the
system to 5.04 (which is the inactive version on the box) and then
upgrade it...

I will let you know.

Jonathan
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

I couldn't agree more... The essentially live upgrade process and the
CNTRL-Z backout is impressive.

BTW, when you revert back... it REALLY reverts... I didn't realize how many
little things I had done with it.

The coolest part is how easy it is to change a password from the command
line now...

Jonathan

On 12/29/06, Ryan Ratliff <rratliff@cisco.com> wrote:
>
> In situations like this, where you are upgrading to get rid of a
> deferred release, I think it's better to revert to the previous
> version anyway.
>
> That said, it just reinforces how awesome of a feature the inactive
> partition is (yes I work for cisco but that doesn't detract from how
> stupendously awesome this feature is).
>
> -Ryan
>
> On Dec 29, 2006, at 2:34 PM, Jonathan Charles wrote:
>
> OK, so, I have a test box that is running CCM5.04... I grabbed the
> 5.1.1 upgrade when it came out and applied it...
>
> cisco withdrew it a few days later (apparently it sux and stuff), and
> they released 5.1.1a
>
> So, I figure, let's apply it...
>
> It won't.
>
> Apparently, CCM5.1.1 does not see the 5.1.1a file as a valid upgrade
> and ignores it.
>
> My guess is that it was designed to be applied to 5.0(4)a and not
> 5.1.1...
>
> Good thing it is a test box.
>
> BTW, here is the message I get from 5.1.1: "The directory was located
> and searched but no valid options or upgrades were available. Note, a
> machine cannot be downgraded so option and upgrade files for previous
> releases were ignored."
>
> Here is the version info:
>
> Active Version: 5.1.1.1000-7
>
> Here is the file I was truing to use as the upgrade:
>
> cisco-ipt-k9-patch5.1.1.2000-2.tar.gz.sgn
>
> BTW, just a note on how not bad this is, I am going to revert the
> system to 5.04 (which is the inactive version on the box) and then
> upgrade it...
>
> I will let you know.
>
>
>
> Jonathan
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Interesting.  Mine worked.  I used FTP for file transfer.  I haven't
activated it yet though.

Cisco Unified Communications
Operating System Administration

Active Version: 5.1.1.1000-7
Inactive Version: 5.1.1.2000-2
Administration Version: 2.0.0.1-1

Charlie

> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of
> Jonathan Charles
> Sent: Friday, December 29, 2006 11:34 AM
> To: cisco-voip@puck-nether.net
> Subject: [cisco-voip] CallManager 5.1.1 Upgrade to 5.1.1a warning...
>
> OK, so, I have a test box that is running CCM5.04... I
> grabbed the 5.1.1 upgrade when it came out and applied it...
>
> cisco withdrew it a few days later (apparently it sux and
> stuff), and they released 5.1.1a
>
> So, I figure, let's apply it...
>
> It won't.
>
> Apparently, CCM5.1.1 does not see the 5.1.1a file as a valid
> upgrade and ignores it.
>
> My guess is that it was designed to be applied to 5.0(4)a and
> not 5.1.1...
>
> Good thing it is a test box.
>
> BTW, here is the message I get from 5.1.1: "The directory was
> located and searched but no valid options or upgrades were
> available. Note, a machine cannot be downgraded so option and
> upgrade files for previous releases were ignored."
>
> Here is the version info:
>
> Active Version: 5.1.1.1000-7
>
> Here is the file I was truing to use as the upgrade:
>
> cisco-ipt-k9-patch5.1.1.2000-2.tar.gz.sgn
>
> BTW, just a note on how not bad this is, I am going to revert
> the system to 5.04 (which is the inactive version on the box)
> and then upgrade it...
>
> I will let you know.
>
>
>
> Jonathan
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

 iD8DBQFFlbwccGGHuFdGSWARAoF8AJ9lT7HT1gWY
/M1EuMA6h1VRjUff2QCfTIqF
tQK9HEPg+YXNAuya6kSuv6o=
=h3cD
-----END PGP SIGNATURE-----

Well, after reverting, the upgrade worked fine, and it looks like I was
logging in with the wrong username (the upgrade file was in a path for a
different user...)...

Okay... so, either way, no big.

Jonathan

On 12/29/06, Charles J. Boening <charlieb@cot.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Interesting.  Mine worked.  I used FTP for file transfer.  I haven't
> activated it yet though.
>
> cisco Unified Communications
> Operating System Administration
>
> Active Version: 5.1.1.1000-7
> Inactive Version: 5.1.1.2000-2
> Administration Version: 2.0.0.1-1
>
>
>
>
> Charlie
>
>
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (MingW32)
>
>  iD8DBQFFlbwccGGHuFdGSWARAoF8AJ9lT7HT1gWY
/M1EuMA6h1VRjUff2QCfTIqF
> tQK9HEPg+YXNAuya6kSuv6o=
> =h3cD
> -----END PGP SIGNATURE-----
>