PRIMECLUSTER Global Link Services Configuration and Administration Guide: Multipath Function (for Solaris(TM) Operating Environment)
Contents PreviousNext

Appendix A Messages> A.3 Activation Command Messages

A.3.1 mpnetinit Command Messages

Description of messages output at the mpnetinit command and the workaround are explained.

[List of error messages]

Message

Description

mpnetinit: already up mpnetX

Meaning

The mpnetX has already been activated.

Workaround

Normal operation. No action required.

MPNET: mpnetX: now up

Meaning

The mpnetX was activated.

Workaround

Normal operation. No action required.

MPNET: mpnetX: daemon started

Meaning

The MPNET monitoring daemon of mpnetX was started.

Workaround

Normal operation. No action required.

MPNET: mpnetX: daemon start failed

Meaning

Activation of the MPNET monitoring daemon of mpnetX failed.

Workaround

Contact your technical support.

mpnetinit: /opt/FJSVmpnet/sbin/mpnetlink not found

Meaning

/opt/FJSVmpnet/sbin/mpnetlink is missing.

Workaround

Verify whether the file is installed correctly. Contact your technical support if problem persists.

mpnetinit: /opt/FJSVmpnet/sbin/mpnetconf not found

Meaning

/opt/FJSVmpnet/sbin/mpnetconf is missing.

Workaround

Verify whether the file is installed correctly. Contact your technical support if problem persists.

mpnetinit: /etc/opt/FJSVmpnet/conf/config not found

Meaning

/etc/opt/FJSVmpnet/conf/config is missing.

Workaround

Verify whether the file is installed correctly. Contact your technical support if problem persists.

mpnetinit: /etc/opt/FJSVmpnet/conf/parameters not found

Meaning

/etc/opt/FJSVmpnet/conf/parameters is missing.

Workaround

Verify whether the file is installed correctly. Contact your technical support if problem persists.

mpnetinit: /opt/FJSVmpnet/daemon/mpnetd not found

Meaning

/opt/FJSVmpnet/daemon/mpnetd is missing.

Workaround

Verify whether the file is installed correctly. Contact your technical support if problem persists.

mpnetinit: /etc/opt/FJSVmpnet/conf/parameters configration error

Meaning

The environmental configuration is not defined in the /etc/opt/FJSVmpnet/conf/parameters file.

Workaround

Verify the environmental configuration is correctly defined in /etc/opt/FJSVmpnet/conf/parameters file

mpnetinit: /opt/FJSVmpnet/sbin/mpnetlink failed

Meaning

/opt/FJSVmpnet/sbin/mpnetlink abnormally ended.

Workaround

Check the error message about /opt/FJSVmpnet/sbin/mpnetlink to see if the environment is correctly defined.

mpnetinit: /opt/FJSVmpnet/sbin/mpnetconf failed

Meaning

/opt/FJSVmpnet/sbin/mpnetconf abnormally ended.

Workaround

Check the error message about /opt/FJSVmpnet/sbin/mpnetconf to see if the environment is correctly defined.

can't unload the module: Device busy

Meaning

The MPNET driver cannot be unloaded.

Workaround

Deactivate all the upper protocols that use the MPNET driver, and deactivate MPNET again

mpnetcntl: ERROR: /dev/xxx: NNNN NNNN

Meaning

Abnormality occurred in /dev/xxx.

Workaround

Verify the environmental configuration and installation of the driver. Contact your technical support if problem persists.

mpnetcntl: ERROR: /var/opt/FJSVmpnet/conf/mpnettab: No such file or directory

Meaning

/var/opt/FJSVmpnet/conf/mpnettab is missing.

Workaround

Verify the installation of the driver. Contact your technical support if problem persists.

mpnetcntl: ERROR: /var/opt/FJSVmpnet/conf/mpnettab: Link index not found

Meaning

LINK index is not found in /var/opt/FJSVmpnet/conf/mpnettab.

Workaround

Verify the interface name is specified correctly.

mpnetcntl: ERROR: /etc/opt/FJSVmpnet/conf/config: NNNN

Meaning

An abnormality is found in /etc/opt/FJSVmpnet/conf/config.

Workaround

Verify the installation of the driver. Contact your technical support if problem persists.

mpnetcntl: ERROR: /etc/opt/FJSVmpnet/conf/config: Device configration error

Meaning

The wrong device name is specified in /etc/opt/FJSVmpnet/conf/config.

Workaround

Correct the device name specified in /etc/opt/FJSVmpnet/conf/config.

mpnetcntl: ERROR: /etc/opt/FJSVmpnet/conf/config: Device type error

Meaning

The specified device name and device type specified in /etc/opt/FJSVmpnet/conf/config are mismatched.

Workaround

Verify the device name and device type specified in /etc/opt/FJSVmpnet/conf/config are entered correctly.

mpnetcntl: ERROR: mpnetX: Select device error: yyy

Meaning

An error was found in device name yyy specified in mpnetX.

Workaround

Verify the specified device name yyy.

mpnetcntl: ERROR: configration device count error: mpnetX

Meaning

The number of specified devices exceeds the maximum number allowed.

Workaround

Verify the number of devices defined in /etc/opt/FJSVmpnet/conf/config does not exceed the maximum number allowed.

mpnetcntl: mpnetX: configration parameter error: /etc/opt/FJSVmpnet/conf/config

Meaning

The specified interface name is not found in /etc/opt/FJSVmpnet/conf/config.

Workaround

Verify the specified interface name is defined in /etc/opt/FJSVmpnet/conf/config correctly.

mpnetcntl: mpnetX: configration parameter error: /etc/opt/FJSVmpnet/conf/parameters

Meaning

The specified interface name is not found in /etc/opt/FJSVmpnet/conf/parameters.

Workaround

Confirm the specified interface name is defined in /etc/opt/FJSVmpnet/conf/parameters correctly.

mpnetcntl: XXX: unknown name

Meaning

An error was found in interface name XXX.

Workaround

Specify a correct interface name.

mpnetcntl: mpnetX: not enough memory

Meaning

Memory cannot be allocated due to insufficient memory.

Workaround

Increase memory to solve the problem and retry this command again.

mpnetcntl: mpnetX: /dev/mpnet: NNNN

Meaning

The /dev/mpnet file "OPEN" and the activation failed. (NNNN indicates the error information)

Workaround

Contact your technical support.

mpnetcntl: mpnetX: /etc/opt/FJSVmpnet/conf/config: NNNN

Meaning

The /etc/opt/FJSVmpnet/conf/config file "OPEN" failed. (NNNN indicates the error information)

Workaround

Contact your technical support.

mpnetcntl: mpnetX: /etc/opt/FJSVmpnet/conf/parameters: NNNN

Meaning

The /etc/opt/FJSVmpnet/conf/parameters file "OPEN" failed. (NNNN indicates the error information)

Workaround

Contact your technical support.

mpnetcntl: mpnetX: file definition error: /etc/opt/FJSVmpnet/conf/parameters

Meaning

Wrong information was found in the environmental configuration of /etc/opt/FJSVmpnet/conf/parameters.

Workaround

Check the environmental configuration of /etc/opt/FJSVmpnet/conf/parameters to see if there is error in the file.

mpnetcntl: mpnetX: file definition error: /etc/opt/FJSVmpnet/conf/parameters

Meaning

Wrong information was found in the environmental configuration of /etc/opt/FJSVmpnet/conf/parameters.

Workaround

Check the environmental configuration of /etc/opt/FJSVmpnet/conf/parameters to see if there is error in the file.

mpnetcntl: mpnetX: configuration device error: /etc/opt/FJSVmpnet/conf/config

Meaning

Wrong information was found in the environmental configuration of /etc/opt/FJSVmpnet/conf/config.

Workaround

Check the environmental configuration of /etc/opt/FJSVmpnet/conf/config to see if there is error in the file.

mpnetcntl: mpnetX: can't get Global MAC address: /etc/opt/FJSVmpnet/conf/parameters

Meaning

Obtaining the global MAC address failed.

Workaround

Contact your technical support.

mpnetcntl: mpnetX: configration device count error: mpnetX

Meaning

The number of specified devices exceeds the maximum number allowed.

Workaround

Verify the number of devices defined in /etc/opt/FJSVmpnet/conf/config does not exceed the maximum number allowed.


Contents PreviousNext

All Rights Reserved, Copyright (C) FUJITSU LIMITED 2005