You say that they both are disabled after midnight routine is done. When you say that you can enable and test them in the morning, have you got both working and syncronized?
Have you tried to split the machine and checked if this occurs if it is in split mode?
My thought is if this has something to do with the SCPU wich is made every midnigt-routine.
We had the same problem.
See this nortel bulletin:
PRODUCT ADVISORY
Meridian 1 IODU/C Access Issue
This product bulletin is being issued as an advisory about a possible problem observed on a few sites
where an IODU/C NT5D61AB card has not been accessible to the Meridian 1 system. The cards in
question are:
NT5D61AB releases 4 and 6 – IODU/C (Input-Output Disk Unit with CD-ROM) cards
Problem Description:
It has been observed on 2 sites in North America, that one of each site’s IODU/C card stopped being
accessible. During the midnight routines at these sites, the inaccessibility was noticed by the system, the
card was disabled and the storage requirement defaulted to the other IODU/C card. On one site, this
resulted in an initialization (INI) of the switch.
Though rare, it is felt that the potential for problems still remains and we would like to put out the
appropriate information on how to recognize when the problem occurs and what can be done about it.
The problem occurs because of a timing issue between the M1 and the IDE to SCSI interface of the hard
drive controller that is used in the IODU/C product. The interface and drive in question are used only in the
NT5D61AB releases 4 and 6 (release 5 was never introduced). During idle times when the hard drive is
not in use, the hard drive may stop functioning and will no longer be accessible to the switch. The next
time that the switch attempts to access the drive, such as during a midnight routine, the inaccessibility will
be discovered and the IODU/C card will be disabled. Messages issued at this point will vary depending on
the files that the system was trying to access, but they will commonly report that the drive was
inaccessible.
Immediate symptoms may include TTY messages with one or both hard disks indicating “CMDU disabled
not responding” and the failed IODU/C pack hard drive LED flashes four times repeatedly.
The impact of this is that the system will continue to run exclusively off of the non-disabled drive, until the
drive in question is reseated or replaced.
Expected Scope:
Although the problem occurs rarely, the potential for this problem is on all release 4 and 6 NT5D61AB
cards. These releases were manufactured between April 1999 and August 2000.
Expected Solution:
This problem has been resolved in release 7 of the NT5D61AB, which is now being shipped. Field returns
of release 4 and 6 boards will be modified with the new interface and upgraded to release 8 of the
NT5D61AB card starting Oct 30, 2000.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.