Alcatel Unleashed

Hallo!

We hardly ever use(d) S0 extensions, but for some remote service purposes now need it (again). But I lost the settings in our OXE 6.0.1.

When I check listerm on the coupler I get:

| Cry:Cpl:ac:term| neqt | typ term | dir nb | Out of service cause |
|-------------------------------------------------------------------------|
| 0 15 0 0 | 00461 | FANTOMICT0 | | S . . . . . . . . . |
| 0 15 0 1 | 00462 | T_RESU | | . . . . . . . . . . |
| 0 15 2 0 | 00479 | FANTOMICT0 | | S . . . . . . . . . |
| 0 15 2 1 | 00480 | TYUSGS0 | 9010 | . . . . . . . . . . |

S0 port 2 is running but port 0 got lost.

I tried to install a new set on port 4 and it worked for a moment, looking similar to the one on port 2 but then (I do not know what I did) it stopped working and looked again like port 1.
It could also be I have cabling problems.

Can anyone tell me, how to install S0 sets?

I remember that it was important in which order one proceeds.
I first created the S0 Bus on Shelf ... Board ... BRA ...
then I created the user as S0 on this physical addres.

Thank you for any tip

Egidio

What release ?

OXE 6.0.1.

or do you need other info?

I remember I had issued with a 6.x

The creation setup should be in the documentation. As far as I remember, you have to create a BUS first under shelf / boards / s0 , and assign a number. Then you can create the number and make it a part of the BUS. I think this is it. If not, let me know, and i ll check the doc.

after the creation of S0 bus and S0 user, remember to reset the board
( sometime need an hardware reset )

best regards

Thank you for your tipps.

Now I found that listerm is not very hepful in checking S0-Busses.
A local Alc-Technician told me, he had to call the user after installation, before listerm would recognice it.
And so it happens with me too.
After calling the extension it is no longer T_Resu. Strange but true.

Unfortunately I also have two physically broken ports on my BRA2 so this helped getting me confused. The Installation process was ok - coupler reset was not necessary (in this case).