Alcatel Unleashed

Hi guys...

I feel great became a member of this forum, actualy I'm a new bie at alcatel, and I have problem at my customer with R4.1.1 and patch d1311 the problem is when I try to backup OPS to CPU disk I got message ;

Confirm the saving of OPS files on your cpu disk (Y/N) y
Cleaning the unexpected file /DHS3data/mao/sl10e05a.zip.zip
rm: //DHS3data/mao/sl10e05a.zip.zip non-existent
Warning rack 2: unknown OPS shelf type found
ops 2.0.2: operation successful
Updating hardware.mao according to data base ok
Found 2 *.zip files in /DHS3data/mao. 1 is expected. Canceled operation

Does anyone have this problem too and how to solve it.

Thanks and Regards,

t3

You have two *.zip files in /usr3/mao (database catalog). Delete one.

Hai Vad, thanks alot for the information, I have already delete 1 file .zip at usr3/mao and the OPS Backup is working, but the message still indicated

Warning Tack 2 : Unknown OPS shelf type found
ops 2.0.2:Operation successful
Updataing hardware.mao according to data base ok
copyin SL10e06A.zip
copyin SOFTWARE.MAO
copyin SL10e06A.SW
copyin HARDWARE.MAO
copyin HARDWARE.OLD
copyin SL10e06A.HW

Is this normal procedure or not.

Cheers,

In hardware.mao file (usual text file) you have hardware description - cabinet, shelfs, boards.
When on PBX you open some feature (IP phone, hybrid link ...) system will automatically create hybrid helf (virtual) - in OPS file this shelf unknown - you have notification about this during OPS installation.
This is normal situation.
The same you will have if you create manually additional shelf. During OPS loading you will have notification about this.
Equipment not known in OPS files will be present in system and works after OPS files installation.

well... nice to hear that.... at least there is no system failure. Thanks vad for the explaination...


Regrads,

Muchlis

Hi there.

I have change OPS files in my system, five times this year and I have the same warning. This warning exists on my system for 5 years. I also have canged 3 releases from 3.2 to 6.0.1.

There is no problem