Syslog messages appear by default in the /etc/messages file. For additional information about syslog messages, see Configuring message and event logging.
The following syslog messages are messages that you can take steps to address. By default they appear on the system console.
Message
|
Explanation
|
What you do
|
|---|
cf.timed.enable: timed
requires java which is
not enabled on this
system
|
Essential Java files are missing from the filer.
|
Follow these steps:
- Install the Java .zip files from
the distribution CD-ROM onto
the /etc/java directory of your
filers.
- Reboot.
|
Interconnect is down
|
The cluster interconnect is not working properly. Takeover capability is disabled.
|
Follow these steps:
- Check the cluster interconnect
cables to make sure that they
are seated properly.
- If the connections are secure
and the message returns, check
for cluster interconnect adapter
messages in the /etc/messages
file, then contact Network
Appliance Technical Support.
|
No disks were detected
on Fibre channel port
B; this filer will be
unable to takeover
correctly.
|
The B-port loop has not been connected to the local filer, which means that the local filer cannot take over its partner.
|
Follow these steps:
- Check the B-port loop
connections to the partner's
disk shelves and make sure that
they are securely connected.
- Verify that the LRC cards are
properly seated.
|
Root volume volume,
RAID group n is
missing n disks and is
unusable.
|
A disk shelf or adapter failed, or the root volume's disks might be spread between A-port and B-port loops.
|
Check the disk shelves and make sure that they are connected properly.
|
Volume volume is
missing a data disk
and has dirty parity.
|
The filer is refusing to perform a giveback because a volume is in degraded mode with dirty parity.
|
Caution
You can lose data if you perform a giveback with a volume that is missing a data disk and has dirty parity.
Follow these steps:
- Wait until one of these events
happen:
- Parity is clean.
- The data disk is reconstructed.
- Use the sysconfig -r
command to verify that one of
the events in Step 1 has
happened.
- Perform a giveback.
|
Volume volume is
missing n disks from
RAID group n and is
being taken offline
for this boot.
|
The volume's disks might be spread between A-port and B-port loops.
|
Follow these steps:
- Verify that the disk shelves are
wired properly.
- Reboot the filer to clear this
condition.
|
WARNING cluster
monitor fast timeout
was blocked for n
secs.
|
The Data ONTAP kernel is supposed to schedule the cluster monitor's fast timeout thread at regular intervals to ensure that mailbox data is read and written within specific time frames. If a filer does not receive the mailbox data because the fast timeout thread is blocked, it might assume that its partner is down and attempt to perform a takeover.
|
If this message happens frequently, gather system utilization data (sysstat, profiling data, and so on), then contact Network Appliance Technical Support so that they can characterize the system.
|
X link is down.
|
The cluster interconnect has detected a failure in one of its two communication channels.
This circumstance does not disable takeover but deserves investigation.
Note
This circumstance can also occur temporarily during the booting of a clustered filer. |
Check the X (top) cable connections to make sure that the cables are seated properly.
|
Y link is down.
|
The cluster interconnect has detected a failure in one of its two communication channels.
This circumstance does not disable takeover but deserves investigation.
Note
This circumstance can also occur temporarily during the booting of a clustered filer. |
Check the Y (bottom) cable connections to make sure that the cables are seated properly.
|
