Table 14: System Log Messages - D-Link DWS-4000 Series Cli Command Reference

D-Link Unified Switch CLI Command Reference
Component Message
NIM NIM: event(x),intf(x),component(x), in wrong
phase
NIM NIM: Failed to notify users of interface change
NIM NIM: failed to send message to NIM message
Queue.
NIM NIM: Failed to notify the components of
L7_CREATE event
NIM NIM: Attempted event (x), on USP x.x.x before
phase 3
NIM NIM: incorrect phase for operation
NIM NIM: Component(x) failed on event(x) for
intIfNum(x)
NIM NIM: Timeout event(x), intIfNum(x) remainingMask
= xxxx
Component Message
SYSTEM Configuration file fastpath.cfg size is 0 (zero) bytes The configuration file could not be read. This
SYSTEM could not separate SYSAPI_CONFIG_FILENAME The configuration file could not be read. This
SYSTEM Building defaults for file <file name> version
<version num>
SYSTEM File <filename>: same version (version num) but
the sizes (<version size>-><expected version size)
differ
SYSTEM Migrating config file <filename> from version
<version num> to <version num>
SYSTEM Building Defaults
© 2009 D-Link Corporation. All Rights Reserved
522
Table 13: NIM Log Messages (Cont.)

Table 14: System Log Messages

Cause
An event was issued to NIM during the wrong
configuration phase (probably Phase 1, 2, or
WMU).
Event was not propagated to the system.
NIM message queue full or non-existent.
Interface not created.
A component issued an interface event during the
wrong initialization phase.
An API call was made during the wrong
initialization phase.
A component responded with a fail indication for an
interface event.
A component did not respond before the NIM
timeout occurred.
Cause
message may occur on a system for which no
configuration has ever been saved or for which
configuration has been erased.
message may occur on a system for which no
configuration has ever been saved or for which
configuration has been erased.
Configuration did not exist or could not be read for
the specified feature or file. Default configuration
values will be used. The file name and version are
indicated.
The configuration file which was loaded was of a
different size than expected for the version
number. This message indicates the configuration
file needed to be migrated to the version number
appropriate for the code image. This message may
appear after upgrading the code image to a more
current release.
The configuration file identified was migrated from
a previous version number. Both the old and new
version number are specified. This message may
appear after upgrading the code image to a more
current release.
Configuration did not exist or could not be read for
the specified feature. Default configuration values
will be used.