PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

A.1.3 Console output messages (numbers 800 to 900)

The following describes the messages output on the console by Redundant Line Control function, explanation, and operator response.

[Message number 8xx]

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.
	line status changed: Link Down at RIP mode (target=host_name)	An error occurred in the communication with the remote host system (host_name).	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.
	line status changed: Link Up at RIP mode (target=host_name)	The communication with the remote host system (host_name) 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 tell an error message to Fujitsu system engineer (SE).
803	file read failed.	Failed to read the file.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
804	pipe create failed.	Failed to create the internal communication pipe.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
805	internal error.	An internal error occurred.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
806	cannot get my process id	Failed to obtain the local process ID.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
814	cannot up interface.	Failed to up the virtual interface.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
815	sha device open failed.	Failed to open the "sha" driver.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
816	ioctl(SHAIOCSETRSCMON) failed.	Failed to send the monitor start request.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
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 tell an error message to Fujitsu system engineer (SE). 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 tell an error message to Fujitsu system engineer (SE). 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 tell an error message to Fujitsu system engineer (SE). 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 tell an error message to Fujitsu system engineer (SE).
825	signal send failed.	Failed to send the signal.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
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 tell an error message to Fujitsu system engineer (SE).
827	could not allocate memory.	Failed to obtain the memory.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
828	fork failed.	The fork () failed.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
829	child process execute failed.	Failed to generate the child process.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
830	getmsg failed.	Failed to receive the data from the "sha" driver.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
831	shared library address get failed.	Failed to obtain the shared library address.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
832	poll failed.	The poll () failed.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
833	ioctl(SHAIOCSETIPADDR) failed.	Failed to notify the IP address.	Collect materials for examination of a Redundant Line Control function, and tell an error message to Fujitsu system engineer (SE).
840	polling device name is not defined in configuration information. polling is not started.	The virtual interface name for router monitoring is not defined in the configuration information. Thus, the router monitoring function for this virtual interface cannot be enabled.	Define the virtual interface name for router monitoring in the configuration information. Then, activate the virtual interface and inactivate/activate the router monitoring function.
841	all polling device name is not defined in configuration information. polling is not started.	No virtual interface for router monitoring is defined in the configuration information. Thus, the router monitoring function cannot be enabled.	Define the virtual interface name for router monitoring in the configuration information. Then, activate the virtual interface and inactivate/activate the router monitoring function.
842	device mode is invalid. polling is not started.	The operation mode of a virtual interface for router monitoring is invalid. Thus, the router monitoring function for this virtual interface cannot be enabled.	The operation mode of the virtual interface for router monitoring is defined as Fast switching mode. In Fast switching mode, line monitoring with the router monitoring function cannot be performed. Delete from the monitoring destination information the virtual interfaces whose operation mode is Fast switching mode.
843	polling device is not specified. polling is not started.	No monitoring destination information is specified. Or specified monitoring destination information contains invalid an error. Thus, the router monitoring function cannot be enabled.	Specify the monitoring destination information. Or correct the error in the settings. Then, disable and enable the router monitoring function.
844	polling address is invalid. polling is not started.	The monitoring destination address or host name specified in the monitoring destination information is invalid. Thus, the router monitoring function cannot be enabled.	Correct the monitoring destination address specified in the monitoring destination information. Then, disable and enable the router monitoring function.
845	could not restart in.routed.	Failed to restart the routing daemon. The router 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 tell an error message to Fujitsu system engineer (SE). See the manual as to the materials necessary for examining a cluster system.
846	could not restart in.rdisc.	Failed to restart the router discovery daemon. The router 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 tell an error message to Fujitsu system engineer (SE). See the manual as to the materials necessary for examining a cluster system.
847	internal error retry over. polling stop.	A router monitoring internal error occurred. The router 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 tell an error message to Fujitsu system engineer (SE). See the manual as to the materials necessary for examining a cluster system.
848	device is inactive. polling stop.	The virtual interface for router monitoring is not activated. The router monitoring function is disabled.	Activate the virtual interface. Then, inactivate and activate the router 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 router monitoring function is disabled.	Check the line failure. After checking the line recovery, inactivate and activate the router monitoring function.
850	cannot down interface.	Failed to inactivate the 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 tell an error message to Fujitsu system engineer (SE).
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 Pollip: Monitoring destination IP	Check for any failure on the communication path to the monitoring destination.
852	secondry 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	phisical 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 tell an error message to Fujitsu system engineer (SE).
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 tell an error message to Fujitsu system engineer (SE).
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 tell an error message to Fujitsu system engineer (SE). 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.
858	observe information is not defined.	Monitoring destination information is not defined.	Define monitoring destination information using the hanetobserv command.
859	in.routed is not started.	Routing daemon is not started.	Please change a setup and reboot a system so that /usr/sbin/in.routed is started. (Please check whether a /etc/defaultrouter file exists. If exists, change a file name or delete. Furthermore, please change the file name of /usr/sbin/in.rdisc into /usr/sbin/in.rdisc.saved etc.)
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.
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 router/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.
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.
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.
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, not necessary to deal with.
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.	Not necessary to deal with.
882	shared memory is broken. (errno)	Creates a shared memory again because it is deleted.	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. ifname: interface name	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. ifname: interface name	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)	It detected that the route by the side of standby was recovered by standby patrol. ifname: interface name of standby patrol	Not necessary to deal with.
886	recover from route error is noticed.(ifname)	The recovery was notified from the remote system. ifname: Interface name	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	Not necessary to deal with.
888	interface is activated. (ifname)	The physical interface was activated. ifname: Interface name	Not necessary to deal with.
889	interface is inactivated. (ifname)	The physical interface was inactivated. ifname: Interface name	Not necessary to deal with.
890	logical IP address is activated. (logicalIP)	The logical IP address was activated. logicalIP: Logical IP	Not necessary to deal with.
891	logical IP address is inactivated. (logicalIP)	The logical IP address was inactivated. logicalIP: Logical IP	Not necessary to deal with.
892	logical virtual interface is activated. (ifname)	The logical virtual interface was activated. ifname: Interface name	Not necessary to deal with.
893	logical virtual interface is inactivated. (ifname)	The logical virtual interface was inactivated. ifname: Interface name	Not necessary to deal with.
894	virtual interface is activated. (ifname)	The virtual interface was activated. ifname: Interface name	Not necessary to deal with.
895	virtual interface is inactivated. (ifname)	The virtual interface was inactivated. ifname: Interface name	Not necessary to deal with.
896	path to standby interface is established. (ifname)	Monitoring by standby patrol started normally. Ifname: A name of a standby patrol interface.	Not necessary to deal with.
897	immediate exchange to primary interface is canceled. (ifname)	Restrained prompt failback to the primary interface by standby patrol. ifname: A name of an interface. This message is output when the monitor-to information to set by a hanetpoll create command is other than HUB.	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.
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"). If the setting of a virtual interface is NIC switching mode (operation mode "e"), please change the setting of corresponding monitoring information.

[Message number 9xx]

Message number	Message	Meaning	Action
901	failed to takeover logical interface used in zone.	Takeover of the logical interface for the non-global zone failed.	The following causes are suspected: * The number of logical interfaces reaches the maximum. * The same IP address is used for two or more interfaces in the system. * The same IP address is used for the other node and IPv6.Check the network interface and network environment in the system.
902	logical interface of zone was added to a secondaryIF.	The logical interface for the non-global zone was added to the secondary interface.	The secondary interface is set to the network interface of the non-global zone. Changing the interface to the primary interface is highly recommended. However, this will not affect ongoing operations because the logical interface for the non-global zone will automatically be taken over to the primary interface.
903	succeeded in takeover logical interface used in zone.	The logical interface for the non-global zone was succeeded.	Not necessary to deal with.
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.