The meaning of and response to each message output by the virtual NIC mode is listed below.
The following table shows facilities and priorities for the message numbers output to the system log file.
Facility | Priority | Message number |
|---|---|---|
user | error | 121, 501, 503, 505, 800s |
kern | notice | 502, 900s |
Message number | Message | Meaning | Action |
|---|---|---|---|
101 | command can be executed only with super-user. | Only a super-user can execute this command. | Execute with a super user authority. |
102 | invalid parameter. | An invalid parameter is specified. | Read the appropriate command reference, and execute the command again. |
103 | virtual interface is inactive. | Specified virtual interface is inactivated. | Check the status of the specified virtual interface with the rvnetstat command. |
104 | virtual interface is active. | Specified virtual interface is activated. |
|
105 | invalid interface name. | An invalid interface name is specified. | Specify a correct interface name, and execute the command again. |
106 | invalid virtual interface name. | An invalid virtual interface name is specified. | Specify a valid virtual interface name, and execute the command again. |
107 | invalid MAC address. | An invalid MAC address is specified. | Specify a correct MAC address, and execute the command again. Note that a multicast address or broadcast address cannot be specified as a MAC address. |
108 | MAC address is duplicated.(interface) | Duplicated MAC addresses are used. interface: Interface name in which the same MAC address is used | Specify a different MAC address, and execute the command again. |
109 | interface name is already defined. | The specified interface name has already been selected. | Specify a different interface name, and execute the command again. |
110 | virtual interface name is already defined. | The specified virtual interface name has already been selected. | Specify a different virtual interface name, and execute the command again. |
111 | virtual interface name is not defined. | The specified virtual interface name is not set in the configuration information. | Review the setting of the Redundant Line Control function. |
112 | specified interface is not bundled by a virtual interface. | The specified interface is not defined as one that configures a virtual interface. | Check the interface that configures a virtual interface with the rvnetadm print command. |
113 | failed to create a directory. | The specified directory cannot be created. | Check the specified directory. |
114 | number of interface is already maximum. | Unable to add an interface because the number of interfaces that configures the specified virtual interface has reached a maximum bundle number. | Review the number of interfaces that configures a virtual interface, and change the definition with the rvnetadm command if necessary. |
115 | number of virtual interface is already maximum. | The number of virtual interfaces exceeded the maximum number. The maximum number is 256. | Delete unnecessary definitions, and execute the command again. |
116 | interface is inactive. | The specified interface has been inactivated. | Check the status of the specified interface with the rvnetstat command. |
117 | specified interface is already connected. | The specified interface has already been connected. | Check the status of the specified interface with the rvnetstat command. |
118 | specified interface is already disconnected. | The specified interface has already been disconnected. | Check the status of the specified interface with the rvnetstat command. |
119 | directory not found. | The specified directory was not found. | Specify a directory name that already exists, and execute the command again. |
120 | virtual interface is not Active-Standby mode. | The specified virtual interface is not Active-Standby status. | Check the status of the specified interface with the rvnetstat command. |
121 | network monitoring could not start.(virtual-interface)(detail) | It is not possible to execute the network monitoring. virtual-interface: Virtual interface name detail: Detail | Check that the MAC address of the physical interface bundled by the virtual interface is not overlapping and the system has already recognized, and then execute again. |
122 | network monitoring is already started. (virtual-interface) | The network monitoring has already been started. virtual-interface: Virtual interface name | Check the monitoring status with the rvnetstat -s command. |
123 | network monitoring is already stopped. (virtual-interface) | The network monitoring has already been stopped. virtual-interface: Virtual interface name | Check the monitoring status with the rvnetstat -s command. |
124 | network monitoring is running. | The network monitoring is running. | Check the monitoring status with the rvnetstat -s command. |
125 | specified MTU is out of range. (min-max) | The value specified as the MTU value of a virtual interface exceeded the range which can be specified. min: the minimum value of MTU which can be specified max: the maximum value of MTU which can be specified | Specify the MTU value of a virtual interface not to exceed the MTU value of the interfaces bundled by the virtual interface, and execute the command again. |
126 | MTU of the virtual interface and bundled interface is inconsistent. | The MTU value of the interfaces bundled by a virtual interface is smaller than the MTU value of the virtual interface which bundles the interfaces. | The MTU value of the bundled interfaces must be the same as or larger than the MTU value of the virtual interface which bundles the interfaces. Specify the correct MTU value to a virtual interface and the interfaces bundled by the virtual interface, and execute the command again. |
127 | failed to add specified interface. (code) | An error was found when adding the specified interface. code: Detail code | Execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
128 | failed to connect specified interface.(code) | An error was found when connecting the specified interface again. code: Detail code | Execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
301 | could not open configuration file. (errno=XXX) | Failed to open the configuration information file. | Check whether the creation of configuration information has been completed. |
302 | could not write configuration file. (errno=XXX) | Failed to write to the configuration information. | Collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
303 | invalid interface name. (interface) | An invalid interface name is specified in the configuration information. interface: Interface name that a virtual NIC bundles | Check the status of the interface. |
501 | system call fail. (func=YYY, errno=XXX) | An error was found in the internal system call. | Check that there is no problem in the setting of the Redundant Line Control function. After verifying that everything is correct, execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
502 | unexpected error.(code) | An unexpected error occurred. code: Detail code | Check that there is no problem in the setting of the Redundant Line Control function. After verifying that everything is correct, execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
503 | ioctl() fail. (cmd=ZZZ, errno=XXX) | An error was found in the internal system call. | Check that there is no problem in the setting of the Redundant Line Control function. After verifying that everything is correct, execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
504 | failed to delete virtual interface. (errno=XXX) | Failed to delete a virtual interface. | Execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
505 | failed to allocate memory.(code) | Memory allocation failed. code: Detail code | Execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
506 | daemon process does not exist. | There is no daemon process. | Collect information for examination of a Redundant Line Control function, and contact field engineers. |
507 | failed to restart daemon. | Stop of the daemon was detected and restart was tried, but failed. | Collect information for examination of a Redundant Line Control function, and contact field engineers. |
508 | semaphore is broken. (errno). | Creates a semaphore again because it is deleted. | No action is required. |
509 | shared memory is broken. (errno) | Creates a shared memory again because it is deleted. | No action is required. |
510 | failed to get OS version. | Failed to get the OS version. | Execute the command again. If the same symptom still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
801 | network monitoring is established. (virtual-interface) | The network monitoring started normally. virtual-interface: Virtual interface name | No action is required. |
802 | monitoring detected a recovery. (virtual-interface) | The network monitoring detected a recovery. virtual-interface: Virtual interface name | No action is required. |
803 | monitoring detects a failure. (virtual-interface) | The network monitoring detects a failure. virtual-interface: Virtual interface name | Check that the connection between switches is correct. When a higher load is imposed on the network, 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. |
901 | link up detected: the interface link is up. (virtual-interface: interface) | An interface is linked up. virtual-interface: Virtual interface name | No action is required. |
902 | link down detected: the interface link is down. (virtual-interface: interface) | An interface is linked down. virtual-interface: Virtual interface name | Check the link status of the interface from the result of executing the dladm show-link command (displayed in STATE). When the interface link down is detected, check whether a failure has occurred in the adjacent switch. Also, check that the correct speed for the switch and server has been selected (such as Auto-negotiation and full-duplex). |
903 | link up detected: the virtual interface link is up. (virtual-interface) | A virtual interface is linked up. virtual-interface: Virtual interface name | No action is required. |
904 | link down detected: the virtual interface link is down. (virtual-interface) | A virtual interface is linked down. virtual-interface: Virtual interface name | Check the link status of the interface that a virtual NIC bundles. |
905 | the interface of the virtual interface was switched. (virtual-interface: from=interface1 to=interface2) | The virtual interface switched the interface used for communication. virtual-interface: Virtual interface name | Check the link status of the interface that a virtual NIC bundles. |
906 | failed to allocate memory for kernel.(code) | Kernel memory allocation failed. code: Detail code | No action is required. |
907 | changed to MAC tracking mode. (virtual-interface) | Changed the mode to MAC tracking. virtual-interface: Virtual interface name | No action is required. |
908 | changed to Active-Standby mode. (virtual-interface) | Changed the mode to Active-Standby. virtual-interface: Virtual interface name | No action is required. |
909 | failed to set multicast address. (virtual-interface:interface)(code) | Failed to register the multicast address. virtual-interface: Virtual interface name interface: Interface name that a virtual NIC bundles code: Detail code | The cause may be one of the following. Review the system environment.
If a problem still remains, collect troubleshooting information of the Redundant Line Control function, and then contact field engineers to report the error message. |
