CIL on HDU and serial connection 1

[sylro]

Hi

I intend to obtain CIL data on the HDU7/1 (ATA) and then to throw the data from the HDU to a PC, through serial
connection (V.24) or Xmodem (I saw it in WinFiol 5.2). Ideally, to connect directly NIU2 output (V.24) to PC serial port.

I have a MD110 version BC12SP4/R1A, just 1 LIM (in fact, I am a radio specialist but now I have to administrate
this kind of thing); I've read some things from ALEX but still I'm confused.

<ioddp;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU I/O-BUS TYPE/USAGE STATUS AUTH
SYSN - 001-0-60 - - IN SERVICE
SYSN SYSDISK1 001-0-60-0 MASTER SanDisk IN SERVICE
SYSSUBFS11
SYSSUBFS21
SYSN SYSTERMINAL 001-0-60-1 - MML - 7
SYSN MML 001-0-60-4 - NETWORK/MML - 7
SYSN ETHERNET 001-0-60-4 - NETWORK/MML - 7
END

<IONPP:EQU=001-0-60-4;
NETWORK PORT CONFIGURATION DATA
EQU IP GATE MASK ETHERNET
001-0-60-4 10.51.15.59 10.51.15.1 255.255.255.0 00.01.EC.B4.4A.32
END


1. IOBPI:NODE=SYSN,BPOS=1-0-60;
-Probably I don't need this because my NIU2 was already initiated
-Can I use another name for the NODE (other than SYSN)? - I have only one NIU2
-May the subfile system span both over CompactFlash and HDU7/1 ? Or is it necessary to create a new NODE?

2. IOEQI:IODEV=DISK_SYL,EQU=1-0-60-4,USAGE=MML;

3. IOSII:NODE=SYSN,IODEV=DISK_SYL,BTYPE=ATA,SUBFS=SYL_LOG;

4. FIDIIATH=/SYSN/SYL_LOG/SYL_CIL

5.CLDFI:FILE=LOGCIL,PATH=/SYSN/SYL_LOG/SYL_CIL,USER=CIL-1,PRIO=A; (or IODEV ...)

6. CLOHI:FILE=LOGCIL,FORM=4,DMPSIZ=4;

7. CLODI:FILE=LOGCIL,ORIG=201&&212,TIME=0-05-00;

8. CLTGI;

What is the correct form of these commands?
(I'm afraid to use them in this form )

Hopefully,
sylro

 

[fouesnant]

Hi sylro

As soon as you have a node created, you cannot create a new one on the same equipment position.
In your case the node SYSN is used by the system for backup, reload, trafic measurment and so on.

In you configuration, you can add one disk, as you disk bus is ATA and support on master (Compact Flash card) and one slave, which will be an HDU7/1 in that case.
This implies some cable connection from the NIU2 to the disk.
Then you can enter command 3

For command 4, the way to access to that diska will be PATH=/SYSN/USR3, as SYSSUBFS11 is the partition mounted for /SYSN/USR1 and SYSSUBFS21 is the partition mounted for /SYSN/USR2
But I would recommend to avoid command line 4

Before initiating CIL on HDU you should verify if you have the right to do it by verfiying the licenses by command LIDAP and check for the line
CIL-HDU-INTERFACE FAL104710
If in the column ALLOWED you have 0, then you cannot initiate it. If in ALLOWED you have 1 or more than 1, verify that in column USED you a at least one possibility to creat your CIL on HDU.

Then you can enter the commands
CLDFI :FILE=LOGCIL,PATH=/SYSN/USR3,USER=CIL-0; (PRIO is used in case of many CIL ouput)
CLOHI:FILE=LOGFIL,FORM=4,DMPSIZ=4,LOGABN=YES;
CLODI:FILE=LOGCIL,ORIG=201&&212,TIME=0-05-00;
and CLTGI;

good luck

 

[sylro]

Thanks, fouesnant

But how do we know that PATH=/SYSN/USR3 containing the file LOGCIL is situated on the HDU and not on the CF?

We've just linked IODEV=DISK_SYL with ATA bus (BTYPE=ATA), with NIU2 (EQU=1-0-60-4) and with the new subfile system (SUBFS=SYL_LOG). Is there need anymore for a new subfile system?

USER=CIL-0 is a predefined application name or it'a a built-in MD110 application?

Best Regards
sylro

 

[fouesnant]

Hi sylro

The partitions created on one node are increasing the USR.
So
IOSII:NODE=SYSN,IODEV=SYSDISK1,SUBFS=SYSSUBFS11& SYSSUBFS21,BTYPE=ATA;
are created at the same time in the same command and in that order.
Therefore SYSSUBFS11 is associated to /SYSN/USR1 and SYSSUBFS21 is associated to /SYSN/USR2
Creating the command IOSII:NODE=SYSN,IODEV=SYSDISK1,SUBFS=SYSSUBFS21&SYSSUBFS11,BYTPE=ATA;
will associate SYSSUBFS11 to /SYSN/USR2 and SYSSUBFS21 to /SYSN/USR1, but the MD won't be able to use the disk, as there is some specific directory structure created with this command that need /SYSN/USR1 for SYSSUBFS11

Now as you add a new disk, you have to type a new partition on the same node, and therfore, this will use the next USR which will be USR3, ie IOSII:NODE=SYSN,IODEV=DISK_SYL,SUBFS=SYL_LOG,BTYPE=ATA;
Maybe you'll nedd to restart the NIU2 in order for it to discover the new bus topology.

The first IOSII command always apply to the Master Disk and the second IOSII command to the Slave.

If you create a new node, ie SMDR, then the partition will be assciated to /SMDR/USR1 and so on.

Normally nothing more is needed for creating partitions.

USER=CIL-0 is the first user but you can change it between CIL-0 to CIL-99.

Best regards

 

[sylro]

Hi fouesnant

I didn't ever think that a PABX can be such an interesting thing!

Thanks again for your patience, fouesnant!

However I still have a question: is it possible to "read" the CIL data from a V.24 port of NIU2 through a serial port reader installed on the PC? I found such software indicated on other thread in this site.

What do you think?

Thanks in advance
sylro

 

[fouesnant]

Hi sylro

Yes it is possible to read any file type, either from V24 port or from Telnet port, or to make an FTP connection, get the file and open it on a PC.
Usually, the CIL on HDU at customer site are fetched via FTP and analysed by the CIL application as it is normal text file,
but you can read it as you like directly from the MD with the command, ie:
FIFCPATH=/SYSN/USR3/LOGCILYYYYMMDD,FORMAT=ASCII;

PATH is the location of your file as well as the name of your file.

According to the data you provide to initiate the CIL on HDU, the system will take the name of the file and add a Date stamp in the format Year (4 digits) Month (2 digits) and Day (2 digits).

The file is opened and close for the day if you choose the day format. If I remember the week and month file format, the file will be opened the first day of the activation and close accordingly 7 days or 30 days after.

Take care that the file is never erased from the disk, so it can filled up your disk if your have big CIL information; that is the reason why at customer site we fetch the file with FTP and erase it after to avoid such disk space problem.

Best regards

 

[sylro]

Hi fouesnant

For the rest the only thing I need is carefulness.

Thanks again

sylro