The following describes the messages output on the console by Redundant Line Control Function, explanation, and operator response.
The following table shows facilities and priorities for the message numbers output to the system log.
Facility | Priority | Message number |
|---|---|---|
kern | info | 800, 801, 990, 991, 992 |
kern | error | 910, 911, 912, 913, 914 |
user | info | 888, 889, 890, 891, 892, 893, 894, 895 |
user | warning | 848 |
user | error | other than those above |
Note
Messages with the following message numbers are not output on the console but output only on the system log.
888, 889, 890, 891, 892, 893, 894, 895
Message number | Message | Meaning | Action |
|---|---|---|---|
800 | line status changed: Link Down at TRUNKING mode (interface on devicename, target=host_name) | An error occurred in the communication with the remote host system (host_name) using the physical interface (interface) controlled by the virtual interface (devicename) that is operating in the Fast switching mode. | Check whether an error has occurred on the communication path to the remote host system. |
801 | line status changed: Link Up at TRUNKING mode (interface on devicename, target=host_name) | The communication with the remote host system (host_name) using the physical interface (interface) controlled by the virtual interface (devicename) is recovered. | No action is required. |
802 | file open failed. | Failed to open the file. | No action is required. |
803 | file read failed. | Failed to read the file. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
804 | pipe create failed. | Failed to create the internal communication pipe. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
805 | internal error. | An internal error occurred. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
806 | cannot get my process id | Failed to obtain the local process ID. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
814 | cannot up interface. | Failed to up the virtual interface. | Check if the operating system configuration file (ifcfg-ethX) is correct. For details, see "3.2.2 Network configuration". If a virtual bridge has been connected to the virtual interface, check that the virtual bridge has been activated. If no problem has been found, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message. |
815 | sha device open failed. | Failed to open the "sha" driver. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
822 | no data in cluster event. | No data was found in the cluster event. | Make sure that the Redundant Line Control Function and the cluster system are correctly set. If there is no problem, collect materials for the examination of the Redundant Line Control Function and the cluster system, and then contact field engineers to report the error message. See the manual of the cluster system as to the materials necessary for examining the cluster system. |
823 | ClSetStat failed. | The cluster resource status could not be set. | Make sure that the Redundant Line Control Function and the cluster system are correctly set. If there is no problem, collect materials for the examination of the Redundant Line Control Function and the cluster system, and then contact field engineers to report the error message. See the manual of the cluster system as to the materials necessary for examining the cluster system. |
824 | directory open failed. | Failed to open the directory. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
825 | signal send failed. | Failed to send the signal. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
826 | command can be executed only with super-user. | The execution-time authority is invalid. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
827 | could not allocate memory. | Failed to obtain the memory. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
828 | fork failed. | The fork () failed. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
829 | child process execute failed. | Failed to generate the child process. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
830 | getmsg failed. | Failed to receive the data from the "sha" driver. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
833 | ioctl(SHAIOCSETIPADDR) failed. | Failed to notify the IP address. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
847 | internal error retry over. polling stop. | A HUB monitoring internal error occurred. The HUB monitoring is stopped. | Make sure that the system, the Redundant Line Control Function, and the cluster system are correctly set. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and the cluster system, and then contact field engineers to report the error message. See the manual of the cluster system as to the materials necessary for examining the cluster system. |
848 | device is inactive. polling stop. | The virtual interface for HUB monitoring is not activated. The HUB monitoring function is disabled. | Activate the virtual interface. Then, inactivate and activate the HUB monitoring function. This message may be displayed when cluster switching occurs during cluster operation, but in this case, no action is needed. |
850 | cannot down interface. | Failed to inactivate the physical interface. | Check if the Redundant Line Control function and the system are correctly set, and check if the operating system configuration file (ifcfg-ethX) is correct. For details, see "3.2.2 Network configuration". If no problem has been found, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message. |
853 | physical interface up failed. | Failed to activate a physical interface. | Make sure that the Redundant Line Control Function and the system are correctly set. If there is no problem, collect materials for the examination of the Redundant Line Control Function, and then contact field engineers to report the error message. |
857 | polling information is not defined. | Monitoring destination information is not defined. | Define monitoring destination information using the hanetpoll command. |
858 | observe information is not defined. | Monitoring destination information is not defined. | Define monitoring destination information using the hanetobserv command. |
860 | interface does not exist. | There is no interface which NIC switching mode is using. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
861 | cannot set interface flags. | The flag operation to an interface in use became failure. | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
870 | polling status changed: Primary polling failed. (ifname,target=pollip) | Ping monitoring on the primary side has failed. | Check that there is no problem in communication routes to the monitoring destination. Perform recovery steps as needed (see "H.3.1 Error messages(870) and corresponding actions for HUB monitoring"). When monitoring is failed even if communication is normal, tuning is required for the monitoring interval and the number of monitoring. |
polling status changed: Primary polling failed. (ifname,target=pollip, vlan=vlanid) | |||
871 | polling status changed: Secondary polling failed. (ifname,target=pollip) | Ping monitoring on the secondary side has failed. | Check that there is no problem in communication routes to the monitoring destination. Perform recovery steps as needed (see "H.3.1 Error messages(870) and corresponding actions for HUB monitoring"). When monitoring is failed even if communication is normal, tuning is required for the monitoring interval and the number of monitoring. |
polling status changed: Secondary polling failed. (ifname,target=pollip, vlan=vlanid) | |||
872 | polling status changed: PrimaryHUB to SecondaryHUB polling failed. (ifname,target=pollip) | An error in the secondary HUB was detected by HUB-to-HUB communication monitoring from the primary interface. | Check for any failure on the communication path to the monitoring destination. If monitoring fails even though possible to communicate normally, tune the intervals and the number of the times of monitoring, and the time to wait for a linkup with the hanetpoll command. Review "H.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
873 | polling status changed: SecondaryHUB to PrimaryHUB polling failed. (ifname,target=pollip) | An error in the primary HUB was detected by HUB-to-HUB communication monitoring from the secondary interface. | Check for any failure on the communication path to the monitoring destination. If monitoring fails even though possible to communicate normally, tune the intervals and the number of the times of monitoring, and the time to wait for a linkup with the hanetpoll command. Review "H.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
874 | polling status changed: HUB repair (target=pollip) | Line failure in ping monitoring has repaired. | No action is required. |
polling status changed: HUB repair (target=pollip,vlan=vlanid) | |||
875 | standby interface failed.(ifname) | Route failure was detected by the standby patrol. | Check that there is no problem in communication routes between the operating NIC and the standby NIC. Perform recovery steps as needed (see "H.3.2 Error messages(875) and corresponding actions for standby patrol"). When monitoring is failed even if communication is normal, tuning is required for the monitoring interval and the number of monitoring. |
standby interface failed.(ifname, vlan=vlanid) | |||
876 | node status is noticed.(sourceip:status) | A node status change was notified from the remote system. | Check the status of the source. |
877 | route error is noticed.(sourceip) | A communication path failure was notified from the remote system. | Check for any failure on the communication path to the source. |
878 | route error is detected.(target=IP) | A communication path failure was detected from the remote system. | Check for any failure on the communication path to the source. |
879 | message received from unknown host.(srcaddr) | A message was received from an unregistered remote system. | Register the corresponding remote host using the hanetobserve command. |
880 | failed to send node down notice by time out. (dstip) | Node status notification failed due to timeout. | Check for any failure of the remote system and on the communication path to the remote system. |
881 | semaphore is broken. (errno) | Creates a semaphore again because it is deleted. | It is not necessary to deal with. |
882 | shared memory is broken. (errno) | Creates a shared memory again because it is deleted. | It is not necessary to deal with. |
883 | activation of a wrong interface has been detected. (ifname) (code) | Since the interface was unjustly activated by the user, the state of an interface is restored. | Check that the interface has been recovered correctly. |
884 | unexpected interface deactivation has been detected. (ifname) (code) | Since the interface was unjustly deactivated by the user, the state of an interface is restored. | Check that the interface has been recovered correctly. |
885 | standby interface recovered.(ifname) | The recovery of the route in the standby side was detected by standby patrol. | It is not necessary to deal with. |
standby interface recovered.(ifname, vlan=vlanid) | |||
886 | recover from route error is noticed.(ifname) | The recovery was notified from the remote system. | It is not necessary to deal with. |
887 | recover from route error is detected. (target=IP) | The recovery of the remote system was detected. | It is not necessary to deal with. |
888 | interface is activated. (ifname) | The physical interface was activated. | It is not necessary to deal with. |
889 | interface is inactivated. (ifname) | The physical interface was inactivated. | It is not necessary to deal with. |
890 | logical IP address is activated. (logicalIP) | The logical IP address was activated. | It is not necessary to deal with. |
891 | logical IP address is inactivated. (logicalIP) | The logical IP address was inactivated. | It is not necessary to deal with. |
892 | logical virtual interface is activated. (ifname) | The logical virtual interface was activated. | It is not necessary to deal with. |
893 | logical virtual interface is inactivated. (ifname) | The logical virtual interface was inactivated. | It is not necessary to deal with. |
894 | virtual interface is activated. (ifname) | The virtual interface was activated. | It is not necessary to deal with. |
895 | virtual interface is inactivated. (ifname) | The virtual interface was inactivated. | It is not necessary to deal with. |
896 | path to standby interface is established. (ifname) | Monitoring by standby patrol has started normally. | It is not necessary to deal with. |
path to standby interface is established. (ifname, vlan=vlanid) | |||
897 | immediate exchange to primary interface is canceled. (ifname) | The immediate automatic fail-back to the primary interface by the standby patrol was restrained. | It is not necessary to deal with. |
898 | unexpected interface flags have been detected. (ifname) (code) | Since the interface was unjustly changed by the user, the state of an interface is restored. | Check that the interface has been recovered correctly. In addition, when this message is displayed to the user operating nothing, please investigate the cause of the interface flag change. |
899 | route to polling address is inconsistent. | The network address defined to virtual interface and monitoring target is not the same, or since inappropriate routing information was registered into routing table, the mistaken monitoring is performed. | Please correct, when you check monitoring target address and there is an error. When there is no error in monitoring target address, please check whether inappropriate routing information is registered into the routing table. When using tagged VLAN interface, please confirm whether a virtual interface is a setting of NIC switching mode (operation mode "d"). |
Message number | Message | Meaning | Action |
|---|---|---|---|
900 | routing information has inconsistency. | Routing information of the communication target, which is set by using the hanetobserv command, is not registered into the routing table, or inconsistent routing information is registered. | Check if there is any inconsistency between the following information:
|
906 | route error to virtual ip address is detected. (target=xxx.xxx.xxx.xxx) | Every monitoring path for the virtual addresses of the remote system failed. | Check that there is no problem with the communication path to the virtual IP addresses of the remote system. |
907 | recover from route error to virtual ip address is detected. (target=xxx.xxx.xxx.xxx) | Monitoring the virtual IP addresses of the remote system is now possible. | No action is required. |
908 | hanetctld restarted. | The control daemon of the GLS is restarted. | No action is required. |
909 | failed to restart daemon. | Restarting the control daemon of the GLS is failed. | Restart the Redundant Line Control Function for recovery (/opt/FJSVhanet/usr/sbin/resethanet -s). When recovery is failed, restart the OS. |
910 | link up detected: the physical interface link is up. (devicename: ifname) | The physical interface is linked up. devicename: Virtual interface name ifname: Physical interface name | No action is required. |
911 | link down detected: the physical interface link is down. (devicename: ifname) | The physical interface is linked down. devicename: Virtual interface name ifname: Physical interface name | Check the link state based on the execution results of the /usr/sbin/ip addr show ifname command (LOWER_UP flag displayed) and the /sbin/ethtool ifname command ("Link detected: yes" displayed). If the link is down, check whether the neighboring switch works, and whether the speed settings (auto negotiation, full-duplex, etc) for the switch and server are correctly set. |
912 | link up detected: the virtual interface link is up. (devicename) | The virtual interface is linked up. devicename: Virtual interface name | No action is required. |
913 | link down detected: the virtual interface link is down. (devicename) | The virtual interface is linked down. devicename: Virtual interface name | Check the link status of the physical interface bundled by the virtual interface. |
914 | the physical interface of the virtual interface was switched. (devicename: vlantype from=ifname1 to=ifname2) | The physical interface which is used for communication of the virtual interface has been switched. devicename: Virtual interface name vlantype: "untagged" or "tagged" ifname1: Physical interface before switching ifname2: Physical interface after switching | Check the link status of the physical interface bundled by the virtual interface. No action is required when the "hanetnic change" command is executed. *vlantype The "vlantype" is output when a tagged VLAN interface is created on the virtual interface. Take note that depending on the OS version, the "vlantype" is output even when a virtual bridge is created on the virtual interface. |
916 | monitoring function detected failures in the entire transfer route. (ifname) | Failures in all transfer routes are detected by the network monitoring function. ifname: Interface name | Check that there is no problem in transfer routes to the monitoring destination and transfer routes between the operating NIC and the standby NIC. |
monitoring function detected failures in the entire transfer route. (ifname, vlan=vlanid) | |||
923 | physical interface is already linked by another network device. (device:ifname) | The specified physical interface cannot be bundled. It has already been used by another network device such as bonding. device: Virtual interface name ifname: Physical interface name | Review the setting of the interface. |
927 | physical interface settings is incorrect.(name=device ifname=interface param=XXXX) | There is an error in the physical interface settings. | Modify the physical interface configuration file (/etc/sysconfig/network-scripts/ifcfg-ethX). For details, see "3.2.2 Network configuration." After the modification is completed, restart the operating system. |
928 | physical interface configuration file not found.(name=device ifname=interface) | There is no physical interface configuration file. | Failed to see the physical interface configuration file (/etc/sysconfig/network-scripts/ifcfg-ethX). Check the file. For details, see "3.2.2 Network configuration." After the modification is completed, restart the operating system. |
929 | SHAMACADDR is not specified. (name=device) | SHAMACADDR is not specified. device: Virtual interface name | It is necessary to specify SHAMACADDR on a guest OS on VMware or on Hyper-V. Check the setting of SHAMACADDR in the virtual interface configuration file (/etc/sysconfig/network-scripts/ifcfg-shaX). |
930 | SHAMACADDR is invalid MAC address. (name=device) | The MAC address specified to SHAMACADDR is invalid. device: Virtual interface name | Specify the correct MAC address to SHAMACADDR. After that, restart the operating system. |
931 | hangup of ping command has been detected. (target=pollip) | A hang-up of the ping command for the monitoring destination is detected. pollip: Monitoring destination IP address | Collect materials for examination of Redundant Line Control Function, and then contact field engineers to report the error message. |
932 | cannot send fhsp message. (dest=hostip, code) | The message of Fujitsu Hot Standby Protocol failed to be sent. hostip: Destination IP address code: Detailed code | Check if the setting to pass through the firewall is correctly set for Fujitsu Hot Standby Protocol (UDP: port number 1807). If no problem has been found, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message. |
973 | failed to startup self-checking. | The self-checking function failed to start. | Follow the instructions of the previously displayed message. |
974 | sha driver error has been detected. | GLS driver error has been detected. | Follow "3.11.2.2 Error detection of the self-checking function" to take the appropriate action. |
976 | hanetctld error has been detected. | GLS daemon error has been detected. | If a recovery message of 977 is displayed, no action is required. If not displayed, follow "3.11.2.2 Error detection of the self-checking function" to take the appropriate action. |
977 | hanetctld recovery has been detected. | GLS daemon recovery has been detected. | No action is required. |
979 | failed to execute a shell script. | User script execution has failed. | Check that the user script file is present. Also, check whether the system resources are running out by checking the message output time. |
980 | sha driver does not exist. | The virtual driver is not installed. | Check whether the GLS package is installed. |
981 | hanetctld does not exist. | The control daemon is not running. | Check whether the GLS package (FJSVhanet) is installed. Also, check that the system has been rebooted after installation. |
987 | configuration is invalid. | Failed to switch virtual networks on the virtual machine. | Review the setting referenced in the message. |
988 | The virtual network link operation failed. | Failed to switch virtual networks on the virtual machine. | Make sure that the system, the Redundant Line Control Function, and the cluster system are correctly set. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and the cluster system, and then contact field engineers to report the error message. |
989 | The virtual network link operation ended normally. | Successfully switched virtual networks on the virtual machine. | No action is required. |
990 | line status changed: all lines disabled: (devicename: interface1=Down, interface2=Down, ...) | In Fast switching mode, it is not possible to continue communicating with the other end host because all physical interfaces (interfaceN) bundled by a virtual interface in operation (devicename) became Down. | Check if or not there is any error in a transfer route of communication to the other end host for all physical interfaces. |
991 | line status changed: some lines in operation: (devicename: interface1=[Up|Down], interface2=[Up|Down], ...) | In Fast switching mode, part of the physical interfaces (interfaceN) bundled by a virtual interface in operation (devicename) became Down (or Up). | Check if or not there is any error in a transfer route of communication to the other end host for physical interfaces in Down status. |
992 | line status changed: all lines enabled: (devicename: interface1=Up, interface2=Up, ...) | In Fast switching mode, all physical interfaces (interfaceN) bundled by a virtual interface in operation (devicename) became Up and communication with the other end host recovered. | No action is required. |
993 | link down detected: Primary polling failed. (ifname,target=pollip) | Link is down for the primary interface in use. ifname: interface name polip: monitoring destination address | Check the link state based on the execution results of the /usr/sbin/ip addr show ifname command (LOWER_UP flag displayed) and the /sbin/ethtool ifname command ("Link detected: yes" displayed). If the link is down, check whether the neighboring switch works, and whether the speed settings (auto negotiation, full-duplex, etc) for the switch and server are correctly set. |
994 | link down detected: Secondary polling failed. (ifname,target=pollip) | Link is down for the primary interface in use. ifname: interface name polip: monitoring destination address | Check the link state based on the execution results of the /usr/sbin/ip addr show ifname command (LOWER_UP flag displayed) and the /sbin/ethtool ifname command ("Link detected: yes" displayed). If the link is down, check whether the neighboring switch works, and the speed settings (auto negotiation, fullduplex, etc) for the switch and server are correctly set. |
995 | failed to start daemon. | Control daemon of GLS failed to be started. | Restart the redundant line control function (/opt/FJSVhanet/usr/sbin/resethanet -s) for the restoration. If the restoration fails, reboot the system. |
996 | polling status changed: Primary polling recovered.(ifname,target=pollip) | Primary monitoring has recovered. ifname: interface name pollip: monitoring destination address | No action is required. |
GLS: Global Link Services
