Replace with ipu

[notsniw]

Hi all,
I ve bc12 sp6 system.I/O board is NIU 1.Niu is position 1-0-60.But i want to change with IPU.Niu is mine,IPU is my customer.Can i change the boards?System will be not close.

Thanks for help...

 

[lancbomb]

the answer is yes, but you will need to add "an" ipu first in a different slot
then remove the niu, then configure the slot for ipu, then put the ipu in there

???thinks??? that should work

good luck

lb

 

[notsniw]

Hi lancomb,
im writing commands,

CNHUI:BPOS=1-0-40;
IOBPI:NODE=SYSN2,BPOS=1-0-40;
IOEQI:IODEV=SYSTERMINAL1,BPOS=1-0-40-01;

and then,
for niu
IOEQE:IODEV=SYSTERMINAL;
IOEQE:IODEV=SCDR;
CNBOE:BPOS=1-0-60;
IS IT OK
and then,
for ipu
CNHUI:BPOS=1-0-60;
IOBPI:NODE=SYSN,BPOS=1-0-60;
IOEQI:IODEV=SYSTERMINAL,BPOS=1-0-60-01;

and then
for other ipu

IOEQE:IODEV=SYSTERMINAL;
CNBOE:BPOS=1-0-40;

the commands ?s ?t true?

thanks for help....

 

[Avstral]

notsniw,

Full procedure is this:

1. Initiate another I/O-board (IPU or NIU) node as SYSN1.
At least one MML-port are needed at the new node.
2. Unmount and end system node (SYSN) on NIU with commands
FIMOE/IOSIE/IOEQE (for MML) and last IOBPE to remove SYSN I/O-node.
3. Initiate the new IPU as system node (SYSN)(CNHUI, IOBPI), either at same place as the old NIU or at a new position.
Initiate the three MML-ports (SYSTERMINAL at least).
4. Connect HDU with the old dump and initiate it at the new IPU (IOSII/FIMOI).
5. IOBPE temporary I/O bord with SYSN1 and kill it with CNBOE.
6. Perform a system dump (DUSYI).
7. Verify that the dump is OK and valid (DUBDP).
8. Reload LIM 1 by pressing the LPU-button twice to refresh the system mailboxes in PLF. This procedure updates the PLF with the new I/O-board configuration.

If this part is missing, any reload of non-I/O LIM will fail.

The I/O-board could always be changed without any special procedures during a release change (starting from INL).

Regards

 

[notsniw]

Thanks for help

 

[RFBOI]

Do not attempt to do this without contacting your /// partner first as it will not work.

1. Systems above BC10 are licenced therefor the IO LIM IPU will need to be reprommed with a new chip containing the site EIC number, i.e. 02-XXXX. Without this your licences will be invalid.

2. The NIU will have had the EIC number writen to it using niux commands, these cannot be overwriten and require the NIU to be returned to ericsson to be reset. This NIU can only be used within this sytem, If you put it in another exchange it will cause it to crash as there will be conflicts within the licences.

3. The IPU is no longer supported in BC12 for IO LIM working, although I have got them working on other LIM's for remote access etc.

In theory, theory and practice are the same. In practice, they are not.

RFBOI

 

[mdfan]

I agree with RFBOI, the IPU has no way to write EIC code to it (at least no standard procedure) and this is needed for the system to work OK.

The customer better buy your NIU card from you .

 

[Avstral]

RFBOI,

Could you, please, read original question?
The swapping procedure assumed that NIU and IPU BOTH has correct LIC in there.

Your's comments N 2&3 and mdfan's response can be described with one word only. BULLSHIT. Nothing personal.

Explanations:

"The NIU will have had the EIC number writen to it using niux commands, these cannot be overwriten and require the NIU to be returned to ericsson to be reset"
RFBOI, please, make the search on this site an you will easily find, how to do this....

"The IPU is no longer supported in BC12 for IO LIM working"
O God! Have you ever tryed to load BC12 with IPU as I/O board ??????
If not - I've greate chistmas surprise for you!
It perfectly works.

This is for you:
<cadap;
CALENDAR DATA
IDENTITY=BC12-WITH-IPU
VERSION=CXP1010106/2/BC12SP6/R3B
15:31:26
MON 13 DEC 2004
END

<ioddp;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU I/O-BUS TYPE/USAGE STATUS AUTH
SYSN - 001-0-50 - - IN SERVICE
SYSN SYSDISK1 001-0-50-0 SCSI/3 SEAGATE IN SERVICE
SYSSUBFS11
SYSSUBFS21
SYSN SYSTERMINAL 001-0-50-1 - MML - 7
END

<cnbip:bpos=1-0-50;

DEVICE BOARD REVISION INFORMATION
DATE: 13DEC04 TIME: 15:31:55

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND

001-0-50 69 NO ANSWER FROM BOARD

END


For mdfan.
"IPU has no way to write EIC code to it (at least no standard procedure)"
Buddy, if EPROM-burned is not a standard equipment for you, bad of you...

"In theory, theory and practice are the same. In practice, they are not."

Can't say better ))

Regards

 

[mdfan]

Avstral , I know about EPROM but it is not the standard way of installing the license since BC10.
Entering the NIUX and type writeeic command requires only that a license file is given to the customer.

Is it also a standard customer delivery procedure to hand over the same license file as a EPROM ?

That was my point.

 

[Avstral]

mdfan,
Very often, following STANDARD procedure means - you can't do a job.

My poit is: if you afraid to step aside of standard, you are BAD engineer.

As RFBOI noted earler, theory and practice are not the same.

Standard procedures, standard live, odinary person, estimated standard salary....

As usual - no offence.

Regards

 

[mdfan]

Avstarl , I totally agree with you on this . And believe me I tend to proceed with non standard or non officially documented procedures whenever I have the opportunity to do it.
But the question is whether notsniw has this possibility to get hold on the needed LIC burned EPROM.
Sure if he works for Damovo which is the primary Ericsson service provider.
But any other service provider of Ericsson , do they have this kind of opportunity ? Just asking.


No offence taken .