Upgrade issues migrating NAC 4.1.6 to 4.8.0

[JUAN HUICAB]

Upgrade issues migrating 4.1.6 to 4.8.0 passing through 4.6.1 here the

procedure that I followed:

[root@CAM store]# tar xzvf cca_upgrade-4.6.1-NO-WEB.tar.gz

<<Information not displayed>>

.

.

.

[root@CAM store]# ls
cca_upgrade-4.6.1  cca_upgrade-4.6.1-NO-WEB.tar.gz
[root@CAM store]# cd cca_upgrade-4.6.1
[root@CAM cca_upgrade-4.6.1]# ls
agent-version.sh          dmidecode           RPMS               version.sh
cca_upgrade-4.1.6.tar.gz  initrd.img          server-upgrade.sh
checksum.txt              manager-upgrade.sh  showstate.sh
checksum.txt.sig          notes.html          UPGRADE.sh
[root@CAM cca_upgrade-4.6.1]#
[root@CAM cca_upgrade-4.6.1]# ./UPGRADE.sh
Please choose whether to upgrade Windows Agent to 4.6.2.113 (It's highly recommended to upgrade) (y/n)? [y]
Please choose whether to upgrade Mac Agent to 4.6.0.3 (It's highly recommended to upgrade) (y/n)? [y]

...stopping CCA Manager...
Start upgrading database's encoding to UTF8...

Welcome to the CCA Manager migration utility.

...Upgrading to newer rpms of 4.6.1...done.
...Upgrading CCA files...done
Windows Agent version upgraded to 4.6.2.113.
Mac Agent was upgraded to version 4.6.0.3.
Clearing Tomcat cache...checking ssl configuration...done.
[root@CAM cca_upgrade-4.6.1]# cd ..

[root@CAM store]#
[root@CAM store]# ls
cca_upgrade-4.6.1                cca_upgrade-4.8.0-from-4.6.x.tar.gz
cca_upgrade-4.6.1-NO-WEB.tar.gz
[root@CAM store]# tar xzvf cca_upgrade-4.8.0-from-4.6.x.tar.gz
cca_upgrade-4.8.0/
cca_upgrade-4.8.0/nac.iso
cca_upgrade-4.8.0/UPGRADE.sh
[root@CAM store]# ls
cca_upgrade-4.6.1                cca_upgrade-4.8.0
cca_upgrade-4.6.1-NO-WEB.tar.gz  cca_upgrade-4.8.0-from-4.6.x.tar.gz
[root@CAM store]# cd cca_upgrade-4.8.0
[root@CAM cca_upgrade-4.8.0]# ls
nac.iso  UPGRADE.sh
[root@CAM cca_upgrade-4.8.0]# ./UPGRADE.sh
Identified platform is 3310
Checking for a free partition to use for upgrade
Found free partition to use at /dev/sda3
Free partition size is 1044225 KB
Free partition doesn't have enough disk space for upgrade
Upgrade needs free partition of at least 1 GB.
Exiting.
[root@CAM cca_upgrade-4.8.0]# cd ..
[root@CAM store]#

looking for answers, does any one pass throught this? I just recently made an upgrade from 4.6.1 to 4.8.0 without this problem the difference basically is that the CAM/CAS originally has the 4.6.1 from factory.

It looks like a bug, am I right??

[Faisal Sehbai]

Hi,

Did you reboot after upgrading to 4.6.1?

Faisal

[JUAN HUICAB]

I´ve tried both ways, in one of them I reboot the appliance applying "Service Perfigo Reboot" and the other without rebooting, same result "not enogh space in partition"

[a.chernomazov]

Try the steps 4.6.1 - 4.7.2 -4.8.0
On CAS 3310 I did so

[JUAN HUICAB]

We´re working in a "workaround" the thing is that the partition  4.1.6 --> 4.6.1 upgrade use for any reason the space reamin ocuped with something that we dont´know, making imposible upgrade to any version over this one.

Once we finsh the upgrade I´ll put the result for you could see the procedure that we followed.

Regards

[Prasanth Mathews]

Can you tell me the status of the workaround? did it work? what did you do?

Regards

Prasanth Mathews

[JUAN HUICAB]

Hi,

Finally I could tell you that the upgrade script  to  take 4.1.6 to 4.6.1 has something that affects the CAM Lite edition that´s why any other procedure after that fails.

In my case this was only a Lab to prepare to a mayor movement over a HA-Supercams(2) with 10 HA-CAS (20) OOBVG/IBVG.

We start the procedure with three choices: (our main option was b)

a) Start the normal upgrade steps then if the failure occurs take option "b" or "c" , if not, finish the upgrade following the documentation.

b) We prepare the movement by open a TAC SR in wich the engineer convert the data base in their labs and then, in case "a" fail we could apply the ISO of 4.8.0 and then restore the snapshot.

c) Start the procedure  first go from 4.1.6 to 4.6.1 then make a snapshot, backup that file, apply the ISO for 4.6.1 then restore the snapshot and continue the upgrade to 4.8.0.

Conclusion: The "bug" only affect the CAM Lite Family, option "a" works for Super Cams

Regards