The following describes the messages output on the console by Redundant Line Control Function, explanation, and operator response.
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. | Collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
803 | file read failed. | Failed to read the file. | Collect materials for examination of a 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 a 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 a 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 a Redundant Line Control Function, and then contact field engineers to report the error message. |
814 | cannot up interface. | Failed to up the virtual interface. | If HWADDR is set in the operating system configuration file (ifcfg-ethX), check whether the file is set to disable HOTPLUG (for example, HOTPLUG=no). 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 then contact field engineers to report the error message. |
815 | sha device open failed. | Failed to open the "sha" driver. | Collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
816 | ioctl(SHAIOCSETRSCMON) failed. | Failed to send the monitor start request. | Collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
817 | ClOpen failed. | The connection to the cluster failed. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual of a cluster system as to the materials necessary for examining a cluster system. |
822 | no data in cluster event. | No data was found in the cluster event. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual of a cluster system as to the materials necessary for examining a cluster system. |
823 | ClSetStat failed. | The cluster resource status could not be set. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual of a cluster system as to the materials necessary for examining a cluster system. |
824 | directory open failed. | Failed to open the directory. | Collect materials for examination of a 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 a 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 a 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 a 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 a 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 a 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 a Redundant Line Control Function, and then contact field engineers to report the error message. |
831 | shared library address get failed. | Failed to obtain the shared library address. | Collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
832 | poll failed. | The poll () failed. | Collect materials for examination of a 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 a Redundant Line Control Function, and then contact field engineers to report the error message. |
834 | interface does not exist. | The interface defined in NIC switching mode does not exist. | Please check that there is no error in the definition of a Redundant Line Control Function, and the definition of a system. Moreover, please check about the existence of the corresponding interface using the ifconfig command. When abnormalities cannot be discovered, collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
845 | could not restart routed. | Failed to restart the routing daemon. The HUB monitoring function is stopped and cluster switching is performed. | Check that there is no mistake in the setting of a system, a Redundant Line Control Function, and a cluster system. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual as to the materials necessary for examining a cluster system. |
846 | could not restart rdisc. | Failed to restart the router discovery daemon. The HUB monitoring function is stopped and cluster switching is performed. | Check that there is no mistake in the setting of a system, a Redundant Line Control Function, and a cluster system. If the same phenomenon occurrs, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual as to the materials necessary for examining a cluster system. |
847 | internal error retry over. polling stop. | A HUB monitoring internal error occurred. The HUB monitoring is stopped. | Check that there is no mistake in the setting of a system, a Redundant Line Control Function, and a cluster system. If the same phenomenon occurrs, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual as to the materials necessary for examining a 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. |
849 | poll fail retry over. polling stop. | The transmission line failed as many times as specified by the retry count consecutively. The HUB monitoring function is disabled. | Check the line failure. After checking the line recovery, inactivate and activate the HUB monitoring function. |
850 | cannot down interface. | Failed to inactivate the physical interface. | Check that the Redundant Line Control function and the system are correctly set. If HWADDR is set in the operating system configuration file (ifcfg-ethX), check whether the file is set to disable HOTPLUG (for example, HOTPLUG=no). 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 then contact field engineers to report the error message. |
851 | primary polling failed. lip=logicalIP, target=pollip. | An error of path to the primary monitoring destination was detected in the initial check of the physical interface. LogicalIP: Logical IP | Check for any failure on the communication path to the monitoring destination. |
852 | secondary polling failed. lip=logicalIP, target=pollip. | An error of path to the secondary monitoring destination was detected in the initial check of the physical interface. LogicalIP: Logical IP, pollip: Monitoring destination IP | Check for any failure on the communication path to the monitoring destination. |
853 | physical interface up failed. | Failed to activate a physical interface. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
854 | logical interface up failed. | Failed to activate a logical interface. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function, and then contact field engineers to report the error message. |
855 | cluster logical interface is not found. | The logical interface registered with the cluster was not found. | Check that there is no mistake in the setting of a system, a Redundant Line Control Function, and a cluster system. If the same phenomenon occurrs, collect materials for examination of a Redundant Line Control Function and a cluster system, and then contact field engineers to report the error message. See the manual as to the materials necessary for examining a cluster system. |
856 | cluster configuration is incomplete. | The logical IP address cannot be activated because the cluster settings are incomplete. | Review the cluster system settings, and reboot the system |
857 | polling information is not defined. | Monitoring destination information is not defined. | Define monitoring destination information using the hanetpoll command. |
860 | interface does not exist. | There is no interface which NIC switching mode is using. | Collect materials for examination of a 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 a Redundant Line Control Function, and then contact field engineers to report the error message. |
870 | polling status changed: Primary polling failed. (ifname,target=pollip) | Line monitoring on the primary side failed. ifname: Interface name, pollip: Monitoring destination address | Check for any failure on the communication path to the monitoring destination. Review "D.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
871 | polling status changed: Secondary polling failed. (ifname,target=pollip) | Line monitoring on the secondary side failed. ifname: Interface name, pollip: Monitoring destination address | Check for any failure on the communication path to the monitoring destination. If monitoring stopped after checking the recovery of the communication path, make a HUB monitoring function invalid and valid using the hanetpoll command. 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 "D.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
872 | polling status changed: PrimaryHUB to SecondaryHUB polling failed. (ifname,target=pollip) | HUB-to-HUB communication monitoring on the primary side failed. ifname: Interface name, pollip: Monitoring destination address | Check for any failure on the communication path to the monitoring destination. Review "D.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
873 | polling status changed: SecondaryHUB to PrimaryHUB polling failed. (ifname,target=pollip) | HUB-to-HUB communication monitoring on the secondary side failed. ifname: Interface name, pollip: Monitoring destination address | Check for any failure on the communication path to the monitoring destination. Review "D.3.1 Error messages(870) and corresponding actions for HUB monitoring". |
874 | polling status changed: HUB repair (target=pollip) | Line failure in HUB-to-HUB communication monitoring was repaired. pollip: Monitoring destination address | No action is required. |
875 | standby interface failed.(ifname) | An error involving standby interface was detected in the standby patrol. ifname: Interface name | Check that there is no error in a transfer route of the standby side. When it takes long time to link up, occasionally a recovery message is output immediately after this message is output. In this case, a transfer route of the standby side is normal. Therefore, it is not necessary to deal with. Review "D.3.2 Error messages(875) and corresponding actins for standby patrol". |
876 | node status is noticed.(sourceip:status) | A node status change was notified from the remote system. sourceip: Source address, status: Notified status | Check the status of the source. |
877 | route error is noticed.(sourceip) | A communication path failure was notified from the remote system. sourceip: Source address | 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. IP: Remote system address | 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. srcaddr: Source address | 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. dstip: Destination address | 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) | Since the interface was unjustly activated 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 abnormality occurred. |
884 | unexpected interface deactivation has been detected. (ifname) | Since the interface was unjustly deactivated 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 abnormality occurred. |
885 | standby interface recovered.(ifname) | The remote system interface recovered. | It is not necessary to deal with. |
886 | recover from route error is noticed.(ifname) | The recovery was notified from the remote system. ifname: Interface name | It is not necessary to deal with. |
887 | recover from route error is detected. (target=IP) | The recovery of the remote system was detected. IP: Remote system address | It is not necessary to deal with. |
888 | interface is activated. (ifname) | The physical interface was activated. ifname: Interface name | It is not necessary to deal with. |
889 | interface is inactivated. (ifname) | The physical interface was inactivated. ifname: Interface name | It is not necessary to deal with. |
890 | logical IP address is activated. (logicalIP) | The logical IP address was activated. logicalIP: Logical IP | It is not necessary to deal with. |
891 | logical IP address is inactivated. (logicalIP) | The logical IP address was inactivated. logicalIP: Logical IP | It is not necessary to deal with. |
892 | logical virtual interface is activated. (ifname) | The logical virtual interface was activated. ifname: Interface name | It is not necessary to deal with. |
893 | logical virtual interface is inactivated. (ifname) | The logical virtual interface was inactivated. ifname: Interface name | It is not necessary to deal with. |
894 | virtual interface is activated. (ifname) | The virtual interface was activated. ifname: Interface name | It is not necessary to deal with. |
895 | virtual interface is inactivated. (ifname) | The virtual interface was inactivated. ifname: Interface name | It is not necessary to deal with. |
896 | path to standby interface is established. (ifname) | Monitoring by standby patrol started normally. | It is not necessary to deal with. |
897 | immediate exchange to primary interface is canceled. (ifname) | Restrained prompt failback to the primary interface by standby patrol. | It is not necessary to deal with. When executing prompt failback, use a hanetpoll modify command and change the monitor-to information to a host name or an IP address of HUB. |
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 |
|---|---|---|---|
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. |
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 a Redundant Line Control function, and then 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 the recovery procedure. |
976 | hanetctld error has been detected. | GLS daemon error has been detected. | If a recovery message is displayed, no action is required. If not displayed, follow the recovery procedure. |
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 (FJSVhanet) 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. | Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. If there is no mistake, collect materials for examination of a Redundant Line Control Function, 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 /sbin/ifconfig ifname command (RUNNING 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 /sbin/ifconfig ifname command (RUNNING 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, full-duplex, etc) for the switch and server are correctly set. |
