CIL over NIU2+CF

[ciberweb]

Hi all!

Ericsson has just installed a NIU2 with Compact Flash in my MD for using it with CIL.
I'm an "expert" ;-) using CIL over Ethernet but this is new for me.
I have in ALEX "CIL buffer on HDU", but I'm not sure if it's the same for Compact Flash (the same commands)

Any help? Any faq? Any list of needed commands?

Thx in advance!!

 

[singhbrindisi]

Hi,

Well i have a similar setup with NIU2 & CF alongwith additional HDU7/1...
In my case i prefeered to use the HDU7 as a backup for CIL rather than the CF which is primarily for data backup only..
Following is the list fo commands if you want to use CF..
In my case only diffrence is USR3 in place of USR1 which is on HDU7...
CLDFI:FILE=SALES,PATH= /SYSN/USR1/ACS/CIL,USER=CIL-2,PRIO=D;
CLOHI:FILE=SALES,FORM=2,DMPSIZ=4 [,DISCR=] [,LOGABN=];
CLODI:FILE=SALES [,ORIG=] [,DIAL=] [,TIME=];
CLTGI;
FIDAPATH=/SYSN/USR1/ACS/CIL/*.*;

For Last one year its working fine for me & i survived one virus attack on my billing system using the backup files on HDU7... So its really worth to have it...

If possible, i would like to learn from your experience about CIL on ethernet..

Cheers,

""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""

 

[ciberweb]

Thx, but I'm afraid I still feel a little bit lost.

After insert the NIU2+CF I made CNHUI and IOBPI, but what's the next steep.
If CF is managed as an storage device we should use IOSII then, but... what BTYPE we should use? (only ATA and SCSII appears on my ALEX documentation).

In fact, I don't know so much about FI commands. My mum told me not to use them ;-)
***********************************************************
Sing, about CIL on ethernet is quite simple if you know CIL on HDU. The only thing that changes is that you must start an IODEV on your NIU with USAGE=OUT and TYPE=NETWORK, and then, on CLDFI, use IODEV= instead of PATH=. You also must tell the MD where throw the Data with IONCI.
Example:
IOEQI:IODEV=NET,EQU=1-0-10-4,USAGE=OUT,TYPE=NETWORK;
IONCI:IODEV=NET,USER=CIL-1,IP=10.140.10.50,RPORT=8001;
CLDFI:FILE=TARIF1,IODEV=NET,USER=CIL-1,PRIO=A;
CLOHI:FILE=TARIF1,FORM=5,DMPSIZ=3,HRTBT=YES;
CLODI:FILE=TARIF1;
CLTGI;

I don't recommend this kind of CIL cause you loose data when network fails.
***********************************************************

 

[ciberweb]

Well...
Finally I programmed it, using BTYPE=ATA.

By the way, I had to make the directory /node/USR1/ACS/CIL with FIDII beacause in other path It shows "PATH NOT ASSIGNED" when I make the CLDFI. Do I have to use this directory yes or yes?

Thx!

 

[singhbrindisi]

Hi,

Yes you need to use the abovesaid path /node/USR1/ACS/CIL as i preassume that you don't have another HDU7/1
Also Btype is indeed ATA for CF...
So finally you are on the correct path...

Anyhow my query about CIL on network wasn't about commands but the kind of setup you have...
Do you have Call buffer equpt./Which kind/Capacity/reliability & how you extend the data to your server etc etc...
I also doesn't belives on my network guys & there setup, but sometimes for remote LIMS you need to look in for this possibility as a cost effective measure...
One guy told me about using AAU1 card & somehow i lost the idea..Still trying to reconstruct the thoughts about AAU1...

Cheers,



""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""

 

[fouesnant]

Hi all

Normally /node/USR1/ACS/CIL should not be used for an extra I/O board with HDU/CF for CIL over HDU. We have some users that have this feature and after data reload, SFCEI or LIM isolation, the path is lost.
You should put the CIL over HDU file directly under /node/USR1.
The system does not care under which directory the CIL file are stored. However, aver SFCEI/DATA RELOAD or other stuff like that, as the board is initated as I/O board with HDU and this directory /node/USR1/ACS, the system is looking for a dump and if it does not find it it destroy the directory (which can be reassigned with FI command, but what a waste of time).
We have learn this in a very hard way !!! and it is not explained in Alex.
The same for the partition : it should never ever be started with "SYSSUBFS", as the system definitively looks for dump.

Best regards