Alcatel Unleashed

I had seen the same issue. After a lot of attemps with the workaround it works. I have used an other Custom Repository (1 didn't work - but 2) and also only download.... than with the 5...6 test it works at me. The problem occours not with fresh installed OV (last MR before 4.3R1).
regards
Silvio

Hi GeraldS,

Sorry for the late reply. I did not see it until now. To answer your question, no. OmniVista 2500 is still dead in the water.

did you use a fresh repository (never used before) with the following settings?

Repository Name: MyALECentralRepository
Repository URL host: ovrepo.fluentnetworking.com
Repository URL location: ov

At me it did work after some trials.
regards
Silvio

That´s a known problem @ALE R&D (seems not all ALE TAC engineers are aware at the moment):

This is the known issue on 422MR2. The root cause is ALE central repo missed the info of 43R01 Repo

1) The user is using a fresh OV422 MR2 to upgrade OV 4.3R1 : We just select “the repo “ALE Central Repo” for upgrading
2) The user is using OV 422 MR2 that was upgraded from previous release (Ex: … -> 4.2.2 GA -> 4.2.2.MR2)

Workaround:

a) Create the custom repo from a fresh custom repo (e.g. this custom repo has never been configured) with the following info

Repository Name – 43R01Repo
Repository URL Host – ovrepo.fluentnetworking.com
Repository URL Location – ov


b) If all custom repos were configured earlier, please follow the steps

+ Edit /etc/yum.repos.d/ALECentralRepo.repo to append the below info
[ALECentralRepo_4.3R1]
name=ALE Central Repo 4.3R1
baseurl=https://ovrepo.fluentnetworking.com/ov/4.3R1
enabled=1
gpgcheck=1
gpgkey=file:///etc/yum/ov/ovnmse-4.3R1.pub

+ Then select the repo “ALE Central Repo” for upgrading

Option (b) did it in my case (no unused repository has left..

btw - there´s also a solution for the original problem of this thread:

Running version 4.2.2.R01 MR-2 Build 115 patch 2. Upgraded from 4.2.1 yesterday and now ovclient fails to start. have rebooted several times including a full power down. ovclient always stays at "starting". Any suggestions?

That´s also a known issue - workaround:
- Upgrade to 4.3R1 (there is a fix included)
or
- revert the snapshot (hopefully you´ve taken a snapshot of the OV-VM before)
- perform a backup via the Virtual Appliance Menu - [4] Upgrade VA - [7] Backup/Restore OmniVista 2500 NMS Data
- perform the upgrade

During the upgrade 4.2.1 -> 4.2.2 the upgrade script is searching for a backup-file (as far i could remember for DB migration?). If no backup is found there are a lot of services which will not start.

Hi,
thanks for sharing this info
regards
Silvio