9-0-60-00: FAULTY I/O BOARD OR CONNECTED I/O DEVICE

[MDUserSergey]

Hello, experts.
Can I get a help about my MD110 ?
About 2 months MD begin write a next error:
<ALLOP;
ALARM LOG
IDENTITY:
VERSION: CXP1010139/4/TSWSP06/R7D

DATE: 06SEP15 TIME: 12:31:53
CLASS: 3
106 FAULTY I/O BOARD OR CONNECTED I/O DEVICE
DATE TIME ALP NOIF EQU BRDID INF1 INF2
06SEP15 12:31:37 1 1 009-0-60-00 106 9 0


LAST ALREI: 06SEP15, 12:31:37

END

By why !?
In BPOS=9-0-60-00 works a NIU2-board. And at any ports of it I initialise a CIL. CIL work fine more then 1 year.
<IODDP;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU I/O-BUS TYPE/USAGE STATUS AUTH
...................................................................................
SYSNOLD - 009-0-60 - - IN SERVICE
SYSNOLD CILDISC 009-0-60-0 MASTER UNIGEN IN SERVICE
CILSUBFS
SYSNOLD SYSTERMINAL2 009-0-60-1 - MML - 7
SYSNOLD CIL 009-0-60-3 - OUT IN SERVICE
SYSNOLD CILNET 009-0-60-4 - NETWORK/OUT IN SERVICE
SYSNOLD TELNET 009-0-60-4 - NETWORK/MML - 7
...................................................................................
END

<CLINP;
CALL LOGGING DATA
CALL LOGGING MODE: ACTIVATED
MOBILITY LOGGING MODE: NOT ACTIVATED
HEADER FORM DMPSIZ DISCR IN SERVICE LOGABN LOGFAL HRTBT
TARIF 5 3 0 YES YES 0 NO
ORIG DIAL TIME
ALL ALL ALL
DIR LIM BPOS EVENT

HEADER FORM DMPSIZ DISCR IN SERVICE LOGABN LOGFAL HRTBT
LOGS 5 4 0 YES YES 3 NO
ORIG DIAL TIME
ALL ALL ALL
DIR LIM BPOS EVENT


END

CIL work fine without problems. All the DUMPs are well, all of them writes fine every night by DUFQI sheduler.
Yesterday I do any RFPUI:
RFPUI:LIM=9,UNIT=NIP;
RFPUI:LIM=9,UNIT=TWP3;
Today I RFEXI my MD110. But error still visible !
Now I able to BLEQI or BLEQE my EQU=9-0-60-00. But error still visible !
What can I do ?

 

[jinjin]

How about remove the alarm code + reset + reinstate the code back?
ALDAR:CODE=106;
ALREI;
ALDAS:CODE=106,CLA=3;

 

[himdp]

Do you have O&M Library?
Look up error code 106 and it states "Is the value in ADD INFO 1 = 9, a subfile system cannot be mounted?
Use command FIFTI with parameter SUBFS to decide which subfile system is faulty."

Instead of restarting units and the exchange perhaps it would be more productive to check the CILSUBFS to see if there is an issue with that.