Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.3Redundant Line Control Function
Appendix A Messages and corrective actions > A.1 Messages Displayed by Redundant Line Control Function > A.1.2 Error output message (numbers 100 to 700)
PreviousNext

A.1.2 Error output message (numbers 100 to 700)

The meaning of and response to each message output by Redundant Line Control Function is listed below.

Table A.1 Message number 1xx - 2xx

Message number

Message

Meaning

Action

101

command can be executed only with super-user.

An unauthorized user performed the operation.

Only a user with super-user privilege can perform this operation.

102

this interface is already linked.

The specified virtual device has already been activated.

Execute the dsphanet command to make sure that the virtual interface is in the activated status.

105

invalid ip_address.

An invalid IP address is specified.

Specify the correct IP address for re-execution.

111

invalid parameter.

An invalid parameter is specified.

Read the appropriate command reference, and execute the command again.

112

invalid argument.

An invalid command argument was found.

Read the appropriate command reference, and execute the command again.

113

polling already active.

The HUB monitoring function has already been activated.

No action is required.

114

-r option value is invalid.

An invalid value is specified.

Read the appropriate command reference to get the correct value, and execute the command again.

115

-s -c option total value is invalid.

An invalid value is specified.

Specify the values (-s and -c) so that the product of the two values does not exceed 300, and execute the command again.

116

-s -c option value is invalid.

An invalid value is specified.

The values (-s and -c) must be selected from within a range of 1 to 300. Specify a number within the range for each value, and execute the command again.

117

polling already stopped.

The HUB monitoring function has already been deactivated.

No action is required.

118

interface is inactive.

The specified virtual interface has been deactivated.

Execute the dsphanet command to check the status of the specified virtual interface.

119

interface is active.

The specified virtual interface has been activated.

Execute the dsphanet command to check the status of the specified virtual interface.

120

invalid device name.

An invalid virtual interface name is specified.

Specify the correct virtual interface name, and execute the command again.

121

directory not found.

The specified directory was not found.

Specify a directory name that already exists, and execute the command again.

122

backup file not found.

The specified backup file was not found.

Specify a backup file that already exists, and execute the command again.

123

invalid backup file.

The specified backup file is invalid.

Specify the backup file that was created by the hanetbackup command, and execute the command again.

124

not directory

Directory name was not found where directory was expected.

Specify a directory, and execute the command again.

125

interface is Cluster interface.

The specified interface is available in the cluster operation.

Specify an interface that is not being used in the cluster operation, and execute the command again.

126

shared resource is not found.

An invalid common resource is specified.

Specify a correct common resource name, and execute the command again.

127

invalid key

An invalid resource key is specified.

Specify a correct resource key, and execute the command again.

128

invalid logicalIP.

An invalid logical IP address is specified.

Specify a correct logical IP address, and execute the command again.

129

logicalIP is already defined.

The specified logical IP address has been specified in configuration information.

Specify a different logical IP address, and execute the command again.

130

logicalIP is not specified.

No logical IP address is specified.

Specify a logical IP address, and execute the command again.

131

primaryIF is not specified.

No primary interface is specified.

Specify a primary interface, and execute the command again.

132

invalid primaryIF.

An invalid primary interface is specified.

Specify a correct primary interface, and execute the command again.

133

physicalIP is not specified.

No physical IP address is specified for the interface.

Specify a physical IP address for the interface, and execute the command again.

134

invalid physicalIP.

The physical IP address of the interface is invalid.

Specify a correct physical IP address, and execute the command again.

135

primary polling address is not specified.

No monitoring destination IP address is specified for the primary interface.

Specify a monitoring destination IP address for the primary interface, and execute the command again.

136

invalid primary polling address.

The monitoring destination IP address of the primary interface is invalid.

Specify a correct monitoring destination IP address, and execute the command again.

137

secondaryIF is not specified.

No secondary interface is specified.

Specify a secondary interface, and execute the command again.

138

invalid secondaryIF.

An invalid secondary interface is specified.

Specify a correct secondary interface, and execute the command again.

139

secondary polling address is not specified.

No monitoring destination IP address of the secondary interface is specified.

Specify a monitoring destination IP address of the secondary interface, and execute the command again.

140

invalid secondary polling address.

An invalid monitoring destination IP address is specified for the secondary interface.

Specify a correct monitoring destination IP address for the secondary interface, and execute the command again.

141

HUB-HUB polling flag is not specified.

Whether HUB-to-HUB communication monitoring is performed is not specified.

Specify whether to perform the HUB-to-HUB communication monitoring (ON or OFF), and execute the command again.

142

invalid HUB-HUB polling flag.

There is an error in the specification indicating whether HUB-to-HUB communication monitoring is performed.

Specify ON or OFF of the HUB-to-HUB communication monitoring, and execute the command again.

143

logicalIP is defined in physicalIP.

The IP address specified as a logical IP address overlaps the physical IP address.

Specify an IP address that is not specified in the virtual interface as the logical IP address, and execute the command again.

144

secondaryIF equal primaryIF.

The primary interface and the secondary interface are identical.

Specify different interfaces, and execute the command again.

145

interface is already defined in another set.

The specified interface is used in another operation set.

Specify an interface that is not used in other operation sets, and execute the command again.

146

interval is not specified.

No monitoring interval is specified.

Specify a monitoring interval, and execute the command again.

147

invalid interval specified.

The monitoring interval value is invalid.

Specify a correct monitoring interval, and execute the command again.

148

count is not specified.

No monitoring count is specified.

Specify a monitoring count, and execute the command again.

149

invalid count specified.

The monitoring count value is invalid.

Specify a correct monitoring count, and execute the command again.

150

invalid argument.

An invalid option is specified.

Refer to the command reference, and execute the command again.

151

logicalIP is active.

The specified processing could not be performed because the transmission line monitoring of the specified operation set was operating.

Stop the transmission line monitoring, and execute the command again.

152

logicalIP is inactive.

The specified processing could not be performed because the transmission line monitoring of the specified operation set was stopped.

Start the transmission line monitoring, and execute the command again.

153

logicalIP is not defined.

The specified operation set is not defined.

Specify a correct operation set.

154

logicalIP is registered to cluster resource.

The specified operation set is registered as a cluster resource.

Delete the operation set from the cluster resources.

155

invalid ping on/off.

HUB-to-HUB communication monitoring information specified in the operation set information is invalid.

Specify correct operation set information.

156

secondaryIF is not defined.

Because the secondary interface is not specified, interfaces cannot be switched.

Specify an operation set in which the secondary interface is defined.

157

product of interval and time should be less than 300.

The detection time (product of the monitoring interval and monitoring count) of line failure is too large.

Specify the monitoring interval and monitoring count so that their product does not exceed 300 seconds.

158

invalid interface count(max 32)

The maximum number of real interfaces that a virtual interface can bundle in GS linkage mode is exceeded (maximum 32).

Reduce the number of bundled real interfaces, and execute the command again.

159

MAC address is already defined.

The specified MAC address has already been specified.

Specify a different MAC address, and execute the command again.

160

specified devicename could not support cluster.

The specified device does not support cluster operation.

Specify an interface name that support cluster operation, and execute the command again.

161

polling function is defined.

The monitoring function is specified.

Delete a monitoring function with the name of the corresponding virtual interface, and execute again.

162

invalid MAC address.

An invalid MAC address is specified.

Specify a correct MAC address, and execute the command again.

163

IP address or Hostname is already defined.

The specified IP address or host name has already been specified.

Specify a different IP address or host name, and execute the command again. In addition, when a problem cannot be solved by this action, please perform the same action as the following messages. A problem may be solved.
Message number: 169, 170

164

interface name is already defined.

The specified interface name has already been specified.

Specify a different interface, and execute the command again. In addition, when a problem cannot be solved by this action, please perform the same action as the following messages. A problem may be solved.
Message number: 166

165

invalid interface name.

An invalid interface name is specified.

Specify a correct interface name, and execute the command again. When the virtual interface is registered in cluster resource, please execute it again after stopping RMS.

166

invalid mode.

A virtual interface configured with invalid operation mode or incompatible operation mode was specified.

Specify a virtual interface configured with valid operation mode or compatible operation mode.

167

parent device name not found.

No virtual interface corresponding to the logical virtual interface was found.

Specify a correct logical virtual interface, and execute the command again.

168

invalid hostname.

Specified host name or defined host name does not exist in /etc/hosts file. Or, specified host name is invalid.

Check for the existing host name specified in the command argument or hostname specified in configuration settings for redundant line control function, in /etc/hosts file. If the host name does not exit, create one and try again. If the host name exists in these files, check if the name contains characters other than alphanumeric characters, hyphen, and period. Also make sure it does not use non-alphanumeric characters for the first and last character. If it contains these characters, change the name and re-execute the command.

169

physical interface name is already defined.

The specified physical interface name has already been specified.

Specify a different physical interface name, and execute the command again. In addition, when a problem cannot be solved by this action, please perform the same action as the following messages. A problem may be solved.
Message number: 166

170

invalid physical interface name.

An invalid physical interface name is specified.

Specify the correct name of the physical interface (the name of the virtual interface when the mode is "p" or "q"), and execute again. When setting a standby patrol function, check that two physical interfaces are defined that configure a virtual interface to be monitored. In addition, when a problem cannot be solved by this action, please perform the same action as the following messages. A problem may be solved.
Message number: 164

171

trunking interface list is not specified.

No interface that operates in Fast switching mode is specified.

Specify an interface, and execute the command again.

172

mode p interface is defined.

A virtual interface in mode P is specified.

Delete the interface in mode P, and execute the command again.

173

mode c interface is activated.

An interface in mode C is activated.

Inactivate the interface in mode C, and execute the command again.

174

ifname is not defined in hanetconfig.

The specified virtual interface name is not specified in configuration information.

Create configuration information using the hanetconfig command, and execute the command again.

175

same polling addresses are specified.

Primary and Secondary interfaces specified the same monitor-to address.

Specify different monitoring destinations, and execute the command again.

176

polling target is not alive.

No response is received from the monitoring destination.

Check the monitoring destination, and execute the command again.

177

polling is active.

The monitoring function is operating.

Stop (OFF) the monitoring function using the hanetpoll command, and execute the command again.

178

invalid version.

An incorrect version is specified.

Specify the version of the backed up Redundant Line Control Function, and execute the command again.

179

invalid virtual interface count(max 128).

The number of virtual interfaces of the communication target exceeded the maximum number (maximum 128).

Delete unnecessary definitions, and execute the command again.

180

mode q interface is defined.

An invalid option is specified.

Deactivate an interface of mode q and execute again.

181

invalid client count(max 128).

An invalid option is specified.

Execute the command again with a correct value.

182

-p option value is invalid.

An invalid option is specified.

See the command reference and execute the command again with a correct value.

183

-b option value is invalid.

An invalid option is specified.

See the command reference and execute the command again with a correct value.

184

shared resource can not be specified.

An invalid option is specified.

See the command reference and execute the command again with a correct value.

185

function is already defined by another.

An invalid option is specified.

Check the configuration information again, delete unnecessary definitions, and execute again.

186

could not get information.

Communication between command-daemon failed.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

187

could not delete last 1 NIC.

It is not possible to delete if a using actual interface is only one when deleting dynamically an actual interface.

After stopped a virtual interface to process, delete or change the specified actual interface. When changing a definition of a virtual interface, delete or change a definition with hanetconfig command.

188

number of physical interface is already maximum.

The number of the physical interfaces that configures the specified virtual interface has reached the maximum number possible to bundle. Therefore, it is not possible to add an actual interface dynamically.

Review the number of the physical interfaces that configures a virtual interface, and change a definition using a hanetconfig command if necessary.

189

invalid network address.

The specified network address is invalid.

Check if or not the specified network address matches with that of a virtual interface network using hanetconfig print command. Specify a correct network address again.

190

virtual gateway function is defined.

A virtual gateway function is already set.

Delete a virtual gateway function with the name of the corresponding virtual interface, then execute again.

191

StandbyIP address function is defined.

A function to specify a standby IP address is already set.

Delete a function to specify a standby IP address with the name of the corresponding virtual interface, and execute again.

192

resource monitor process for virtual interface is running.

A resource monitor for the virtual interface is working.

Execute hvshut command provided by a cluster system, halt a resource monitor, and execute again.

193

Specified interface is already linked to IP.

The IP address is already assigned to the specified interface.

Check if or not there is /etc/sysconfig/network-scripts/ifcfg-ethX file.

194

Specified interface is not bundled by a virtual interface.

The specified interface is not defined as the one to configure a virtual interface.

Check the interface that configures a virtual interface using hanetconfig print command. Specify an interface name displayed in the Interface List, and execute the command again. In addition, when you add the interface which does not exist on a definition, please specify "-f" option of the hanetnic add command, and execute the command again.

195

Standby patrol function could not started.

It is not possible to execute a standby patrol function.

Check that the system has already recognized all physical interfaces that configure a virtual interface to be monitored by a standby patrol function, and execute again.

196

Standby patrol function is defined.

A standby patrol function is already set.

Delete a standby patrol function of the corresponding virtual interface name, and execute again.

197

specified physical interface is already unlinked.

Activation of the specified physical interface is already deleted.

Using dsphanet command, check that the specified physical interface is not used yet.

198

address family of takeover IP address incompatible.

The specified address form of a takeover IP address (an address family) is not compatible with that of a setting virtual interface.

Make an address form of a takeover IP address compatible with that of a setting virtual interface and execute again.

199

invalid takeover IP address.

The specified takeover IP address is invalid.

Check a value of the specified takeover IP address and execute again.

200

invalid hostname or prefix value.

The specified host name or prefix value is invalid.

Check the specified host name or prefix value and execute again.

201

dual stack interface can not be specified.

It is not possible to specify a virtual interface of dual stack configuration.

Delete a definition of the corresponding virtual interface and define newly.

202

address family of polling IP address incompatible.

The specified address form of a monitor-to IP address (an address family) is not compatible with that of a setting virtual interface.

Make an address form of a monitor-to IP address compatible with that of a setting virtual interface and execute again.

203

interfaces defined as cluster resources still exist.

One or more virtual interfaces registered as cluster resources exist.

Delete the cluster resources and execute the command again.

204

interface defined as cluster resource is still active.

A virtual interface is active as cluster resources.

Stop RMS and execute again.

205

mode can't be changed for dual stack interface.

Mode can't be changed if the virtual IF is a dual stack.

Temporary delete the configuration information of the virtual interface and reconfigure.

206

mode can't be changed for IPv6 interface.

Mode cannot be changed if the virtual IF is IPv6.

Temporary delete the configuration information of the virtual interface and reconfigure.

207

order of physical interface is different or invalid physical interface name.

Order of the interfaces is incorrect or the name of the interface is invalid.

Check the contents of the interface and retry.

208

configuration is not defined.

Valid configuration information or monitoring target's information is not configured.

Configure the valid configuration information or monitoring target's information.

209

specified address family is not defined.

The virtual interface for the specified address family is not defined.

Match the specifying address family with the address family of the virtual interface defined in the configuration then retry.

210

invalid address family.

The specified address family does not match the address family of the virtual interface.

Match the specifying address family with the address family of the virtual interface defined in the configuration then retry.

211

invalid MAC address(multicast or broadcast).

The specified MAC address is invalid.

Specify a MAC address other than a multicast address or broadcast address.

212

polling attribute of specified devicename cannot be changed individually.

The monitoring information of the virtual interface cannot be changed individually.

Specify the monitoring configuration value as changeable virtual interface that can be specified individually.

213

invalid interface name.(same physical interface)

Tagged VLAN interface created on the same physical interface was specified over the same physical interface.

Check the specified operation mode and tagged VLAN name (VLAN-ID). Then, retry the operation.

214

invalid interface name.(VLAN-ID is the same)

Identical logical device number of tagged VLAN interface is assigned.

Check the specified operation mode and tagged VLAN name (VLAN-ID). Then, retry the operation.

215

invalid interface name.(VLAN-ID different)

Disparate logical device number of tagged VLAN interface is assigned.

Check the specified operation mode and tagged VLAN name (VLAN-ID). Then, retry the operation.

216

When polling address is one, HUB-HUB polling flag must be OFF.

When polling address is one, HUB-to-HUB polling flag must be set OFF.

Set two polling targets or set the flag OFF, then retry the operation.

217

specified physical interface is inactive.

The specified physical interface is inactive.

Ensure the hostname configuration file (/etc/sysconfig/network-scripts/ifcfg-interface) for the physical interface exists. If it does no exist, create a new configuration file including physical IP address or hostname and then reboot the system After rebooting the system, execute the command. If the above file exists, run the following command:
/sbin/ifconfig "interface name" "physical IP address"
Then, execute the command again.

218

bundled interface does not exist.

A virtual interface bundling physical interface or tagged VLAN interface does not exist.

Ensure virtual interface bundling physical interface or tagged VLAN interface exists. Then re-execute the command.

219

invalid interface name.(physical interface is overlapped)

Specified Tagged VLAN interface is overlapped with part of physical interface or Tagged VLAN interfaces which belongs other virtual interface.

Specify un-overlapped or completely corresponding Tagged VLAN interfaces with other virtual interface.

222

invalid interface name.(unusable combination)

The physical interface name specified is invalid.

Check that the tagged VLAN interface is unmixed with the physical interface then execute the command again.

Table A.2 Message number 3xx

Message number

Message

Meaning

Action

301

could not open configuration file.

Failed to open the configuration information file.

Check whether the creation of configuration information has been completed.

302

invalid interface name.

An invalid virtual interface name was found in configuration information.

Review the configuration information.

303

hostname is not specified.

The host name is not specified in the configuration information.

Review the configuration information.

304

invalid hostname.

An invalid host name is specified in configuration information.

Review the configuration information.

305

trunking interface list is not specified.

The bundled physical interface is not specified in configuration information.

Review the configuration information.

306

invalid interface count(max 8).

The number of physical interfaces to be bundled exceeds the preset value.

Specify 8 or fewer physical interfaces as the number of interfaces to be bundled.

307

interface name is already defined.

The virtual interface name you want to specify has already been defined in the configuration information.

Specify a virtual interface so that it does not conflict with the other interfaces in the configuration information, and execute the command again.

308

physical interface name is already defined.

The physical interface name that you want to bundle in a virtual interface has already defined.

Review the configuration information.

309

interface address is already defined.

The same IP address is specified for more than one virtual interface.

Review the configuration information.

310

invalid physical interface name.

An invalid physical interface name is specified in the configuration information.

Review the configuration information.

311

invalid file format.

An invalid file format was found in configuration information.

Execute the check command for the configuration information, and take the appropriate action according to the output message.

312

parent device name not found.

The configuration information does not contain the virtual interface with the logical virtual interface.

Review the configuration information.

313

invalid mode.

An invalid operation mode is specified in the configuration information.

Review the configuration information.

314

target is not defined.

The destination information for monitoring does not contain the address information of the monitoring destination.

Review the destination information for monitoring.

315

polling device is already defined.

The destination information for monitoring contains multiple specification entries with the same virtual interface name.

Review the destination information for monitoring.

316

same polling addresses are specified.

Primary/Secondary interfaces specified the same monitor-to address.

Review the destination information for monitoring.

317

interface name is not defined.

The virtual interface name is not specified in the destination information for monitoring.

Review the destination information for monitoring.

318

invalid device count(max 64).

The number of specified virtual interfaces exceeds 64.

Review the configuration information or destination information for monitoring.

319

Invalid logical device count(max 63).

The number of specified logical virtual interfaces exceeds 63 (i.e., the maximum number for one virtual interface).

Review the configuration information.

320

Configuration is invalid.

The configuration information contains invalid data.

Review the configuration information.

321

Configuration is not defined.

Failed to find valid configuration information or destination information for monitoring.

Define the settings for the configuration information or destination information for monitoring.

322

invalid define count(max 64).

The total of defined virtual interfaces and defined logical virtual interfaces exceeds 64 (i.e., the maximum number for definition).

Review the configuration information.

323

logicalIP is already max.

The number of logical IP addresses exceeded the maximum defined number.

Review the configuration information.

324

current configuration is invalid.

No operation set can be created because the definition of the created operation set contains invalid information.

Review the operation set information.

325

invalid ping on/off.

ON/OFF information for monitoring is not specified in the operation set information.

Review the operation set information.

326

invalid logicalIP.

The logical IP address is invalid.

Review the configuration information.

327

logicalIP is already defined.

The logical IP address has already been specified.

Review the configuration information.

328

logicalIP not found.

The logical IP address was not found.

Review the configuration information.

329

primaryIF not found.

The primary interface was not found.

Review the configuration information.

330

invalid primaryIF.

The primary interface is invalid.

Review the configuration information.

331

physicalIP not found.

The physical IP address was not found.

Review the configuration information.

332

invalid physicalIP.

The physical IP address is invalid.

Review the configuration information.

333

primary polling address not found.

No monitoring destination address of the primary interface was found.

Review the monitoring destination information and configuration information.

334

invalid primary polling address.

The monitoring destination address of the primary interface is invalid.

Review the monitoring destination information and configuration information.

335

invalid secondaryIF.

The secondary interface is invalid.

Review the configuration information.

336

secondary polling address not found.

No monitoring destination address of the secondary interface was found.

Review the monitoring destination information and configuration information.

337

invalid secondary polling address.

The monitoring destination address of the secondary interface is invalid.

Review the monitoring destination information and configuration information.

338

HUB-HUB polling flag not found.

Whether HUB-to-HUB communication monitoring is performed is not specified.

Review the monitoring destination information and configuration information.

339

logicalIP equal physicalIP.

The same value is specified as the logical IP address and physical IP address.

Review the configuration information.

340

secondaryIF equal primaryIF.

The same value is specified as the primary interface and secondary interface.

Review the monitoring destination information and configuration information.

341

interface is already defined in another set.

An interface used in another operation set is specified.

Review the configuration information.

342

invalid HUB-HUB poll on/off.

There is an error in the specification indicating whether HUB-to-HUB communication monitoring is performed.

Review the monitoring destination information and configuration information.

343

physicalIP is already defined in another set.

A logical IP address used in another operation set is specified.

Review the configuration information.

344

polling information is different.

Different information is specified in the operation set sharing a physical interface.

Review the operation set information.

345

cluster configuration is incomplete.

The transmission line monitoring cannot be started because the cluster system settings are incomplete.

Review the setting of a cluster system, and reboot a machine.

346

invalid client count.

The number of the clients is improper.

Execute the command again with the correct number of the clients.

347

client address is already defined.

Already defined the specified client address.

See the client definition information, specify an address not redundant, and execute again.

348

invalid client address.

The specified client address is improper.

Check the client address and execute the command again.

349

invalid PmgropeID.

The PM group ID is improper.

Check the PM group ID and execute the command again.

350

invalid network address.

The specified network address is improper.

Check the network address and execute the command again.

351

observ information is not defined.

Monitoring destination information is not defined.

Define the monitoring destination information with the hanetobserv command.

352

routed is not started.

Not yet activated a routing daemon (routed).

Change a system definition (check if or not there is /etc/defaultrouter file, change a name or delete it if exists) to activate a routing daemon (routed) and reboot the system.

353

invalid prefix value

A prefix value is invalid.

Check the specified IP address and prefix value.

354

interface is specified redundantly.

Redundancy was found on the specified virtual interface.

Specify the valid virtual interface and re-execute the command again.

356

could not get polling information.

Failed to obtain polling information.

Configure the polling information and re-execute the command. If the same error occurs after re-executing the command, then collect appropriate logs for Redundant Line Control function and contact field engineers with the reported error message.

357

different network addresses are inappropriate.

Network addresses set for the NICs to be used are different.

Set the same network addresses for the NICs to be used. Review the assigned IP address (hostname) and netmask (prefix length).

358

the same network addresses are inappropriate.

The network addresses assigned between the interfaces cannot be the same network address.

Review the assigned IP address (hostname) and network mask (prefix length). The network addresses between must use different network address. Assign the different network addresses between the interfaces.

359

virtual gateway information is not defined.

A virtual gateway is not defined.

Define the virtual gateway information with the hanetgw command.

360

takeover ip address is not defined.

A takeover IP address is not set.

Review the setting of a Redundant Line Control Function and a cluster system.

361

virtual interface is not defined.

A virtual interface is not set.

Review the setting of a Redundant Line Control Function and a cluster system.

367

could not delete file. file=ifcfg-shaX

A file cannot be deleted.

Check the operation status of the "ifcfg-shaX" file, which is to be deleted, under /etc/sysconfig/network-scripts/. After confirming that there is no problem with "ifcfg-shaX" file, delete it.

368

file already exists. file=ifcfg-shaX

The file has already existed.

Check the operation status of the "ifcfg-shaX" file under /etc/sysconfig/network-scripts/. If there is no problem, no action is required.

369

file not found. file=/XXXX/YYYY

A file cannot be found.

Check whether the corresponding file exits or not and its authority. After confirming that there is no problem, with "hanetconfig delete", delete the virtual interface setting of the GLS most recently created with "hanetconfig create". Then create the virtual interface setting of the GLS with "hanetconfig create" again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

370

path not found. path= /XXXX/YYYY

A path cannot be found.

Check that the appropriate path exists. After confirming that there is no problem, with "hanetconfig delete", delete the virtual interface setting of the GLS most recently created with "hanetconfig create". Then create the virtual interface setting of the GLS with"hanetconfig create" again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

371

invalid configuration parameter. file=/XXXX/YYYY

A parameter is invalid.

Check whether the corresponding file exits or not and its contents of the setting. After confirming that there is no problem, inactivate the virtual interface with "stphanet", and then activate it with "strhanet".

372

could not set vlan load balance.

Setting of VLAN load balance is failed.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

373

file not found. file=/XXXX/YYYY

A file cannot be found.

Check that the appropriate path exists. After confirming that there is no problem, with "hanetconfig delete", delete the virtual interface setting of the GLS most recently created with "hanetconfig create". Then create the virtual interface setting of the GLS with"hanetconfig create" again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

Table A.3 Message number 5xx

Message number

Message

Meaning

Action

501

socket() fail.

An error was found in the internal system call.

Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. After checked there is no mistake, execute a command again. 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 field engineers. See the manual of a cluster system as to the materials necessary for examining a cluster system.

502

ioctl(SIOCGIFCONF) fail.

An error was found in the internal system call.

Check that there is no mistake in the setting of a Redundant Line Control Function and a cluster system. After checked there is no mistake, execute a command again. 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 field engineers. See the manual of a cluster system as to the materials necessary for examining a cluster system.

510

could not allocate memory.

An error was found in the internal system call.

Execute a command again. 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 field engineers. See the manual of a cluster system as to the materials necessary for examining a cluster system.

511

could not open file.

An error was found in the internal system call.

Execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

512

could not read file.

An error was found in the internal system call.

Execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

513

could not write file.

An error was found in the internal system call.

Execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

514

open() fail.

An error was found in the internal system call.

Execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

515

ioctl(SHAIOCSETPARAM) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

516

ioctl(I_PUNLINK) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

517

ioctl(SHAIOCGETLID) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

518

ioctl(I_PLINK) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

519

ioctl(SHAIOCPLUMB) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

525

ioctl(SHAIOCGETINFO) fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

538

total entry is negative value.

An unexpected error occurred during reading configuration information.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

539

ioctl(SHAIOCNODENAME) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

540

ioctl(SHAIOCIPADDR) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

541

ioctl(SHAIOCSAP) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

542

ioctl(SHAIOCDEBUG) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

543

ioctl(SHAIOCWATCHDOG) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

544

ioctl(SHAIOCDISCARD) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

545

ioctl(SHAIOCMESSAGE) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

546

unexpected error.

An unexpected system call error occurred.

Execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

547

ioctl(SIOCGIFFLAGS) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

548

ioctl(SIOCGIFNUM) fail.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

549

polling process is inactive.

An internal process was not executed.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

550

opendir failed.

An unexpected system call error occurred.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

551

semaphore lock failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

552

semaphore unlock failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

553

shared memory attach failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

554

shared memory dettach failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

555

IPC key generate failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

556

get semaphore failed.

An error was found in the internal system call.

No action is required because recovery is automatically made. However, the message is output repeatedly, follow the procedure described bellow.
The following system resources are required for a Redundant Line Control Function:
* semsys:seminfo_semmni (The maximum number of the semaphore identifiers) : One or greater
* semsys:seminfo_semmns (The maximum number of the semaphores in a system) : One or greater
If the values are not sufficient, edit the kernel parameter file (/etc/system) and add the required value to the original parameter value.
If the problem continues to occur after correcting the kernel parameter values, then there is a possibility that the semaphore identifier for the Redundant Line Control Function(0xde......) has already been used by another application. Verify if the same identifier is used in the system using ipcs command.
If the problem still remains even after the identifier has been changed, collect examination materials of a Redundant Line Control Function and contact field engineers.

557

get shared memory segment identifier failed.

An error was found in the internal system call.

No action is required because recovery is automatically made. However, the message is output repeatedly, follow the procedure described bellow.
The following system resources are required for a Redundant Line Control Function:
* shmsys:shminfo_shmmax (The maximum size of the shared memory segment) : 5120 or greater
* shmsys:shminfo_shmmni (The maximum number of the shared memory segments) : two or greater
If the values are not sufficient, edit the kernel parameter file (/etc/system) and add the required value to the original parameter value.
Additionally, do not specify shmsys:shminfo_shmmin(minimum size of the shared memory segment).
If the problem continues to occur after correcting the kernel parameter values, then there is a possibility that the shared memory identifier for the Redundant Line Control Function(0xde......) has already been used by another application. Verify if the same identifier is used in the system using ipcs command.
If the problem still remains even after the identifier has been changed, collect examination materials of a Redundant Line Control Function and contact field engineers.

558

control semaphore failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

559

internal error.

An internal error occurred.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

560

control shared memory failed.

An error was found in the internal system call.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

561

daemon process does not exist.

An internal error occurred.

If not rebooted after the installation, first reboot, then execute again. If the same message is output even after rebooted, collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

562

failed to alloc memory.

Failed to acquire memory.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

563

failed to activate logicalIP.

An internal error occurred.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

564

failed to inactivate logicalIP.

An internal error occurred.

Collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

565

ioctl(SHAIOCPATROLL) fail.

An error was found in the internal system call.

Execute the command again. If the same error message is output, contact a field engineers about the error message.

566

ether_aton() fail.

An error was found in the internal system call.

Check that there is no a mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute a command again. If the same phenomenon occurs, collect materials for examination of a Redundant Line Control Function, and tell an error message to field engineers.

567

ioctl(SIOCGIFADDR) fail.

An error occurred in the internally used system call.

Check there is no mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute the command again. If the same phenomenon still occurs, collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

568

ioctl(SIOCGIFNETMASK) fail.

An error occurred in the internally used system call.

Check there is no mistake in the setting of a Redundant Line Control Function. After checked there is no mistake, execute the command again. If the same phenomenon still occurs, collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

569

could not communicate with daemon process.

Failed to communicate between a command and a daemon.

Collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

570

failed to get socket.

An error occurred in the internally used system call.

Collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

571

failed to send request.

An error occurred in the internally used system call.

Collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

572

failed to receive response.

An error occurred in the internally used system call.

Collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

573

request timeout.

An error occurred in the internally used system call.

Collect materials for examination of a Redundant Line Control Function, and tell field engineers an error message.

574

failed to delete virtual interface.

Failed to delete a virtual interface.

Execute the command again. If the same phenomenon still occurs, collect the examination materials of a Redundant Line Control Function and inform field engineers about an error message.

575

failed to restart hanet.

Failed to reactivate a Redundant Line Control Function.

Execute the command again. If the same phenomenon still occurs, collect the examination materials of a Redundant Line Control Function and inform field engineers about an error message.

576

failed to enable configuration.

An error has occurred while processing the configured values.

Restart the Redundant Line Control function; (/opt/FJSVhanet/usr/sbin/resethanet -s) and review the reflected configuration values. If the same error occurs after rebooting the system, then collect appropriate logs for Redundant Line Control function and contact field engineers with the reported error message.

577

failed to create a directory.

Creation of a work directory failed when the command for collecting troubleshooting information was executed.

Check if a directory on which the troubleshooting information should be stored exists, and the user has access privileges. If there is nothing wrong with the above, execute the command again. If there are any problems, solve the problems then execute the command again.

578

could not create file.

A file cannot be created.

With "hanetconfig delete", delete the virtual interface setting of the GLS most recently created with "hanetconfig create". Then create the virtual interface setting of the GLS with "hanetconfig create" again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

579

could not create symbolic link.

A symbolic link cannot be created.

With "hanetconfig delete", delete the virtual interface setting of the GLS most recently created with "hanetconfig create". Then create the virtual interface setting of the GLS with "hanetconfig create" again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

580

could not execute script. script=/XXX/YYY/ZZZ

Script execution has failed.

Check whether the corresponding script exits or not and its authority. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, uninstall the package of the GLS and install it again.

581

system call fail. func=XXXX errno=YY

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

582

could not start monitoring.

Network monitoring cannot be started.

Start network monitoring with the " hanetpathmon on" command. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

583

could not stop monitoring.

Network monitoring cannot be stopped.

Stop network monitoring with the "hanetpathmon off" command. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

585

network path monitoring is running.

As network monitoring is running, monitoring parameters cannot be changed.

Execute the command again after stopping network monitoring with the "hanetpathmon off" command.

586

virtual interface is inactive.

As the virtual interface is inactivated, network monitoring cannot be started.

Execute the command again after activating the virtual interface with the "strhanet" command.

Table A.4 Message number 7xx

Message number

Message

Meaning

Action

700

invalid network mask.

The specified subnet mask is invalid.

Specify the correct subnet mask and execute the command again.

701

ipv6 module is not loaded.

ipv6 module is not loaded.

Configure the system to load ipv6 module during the system startup and then reboot the system.

702

the number of specified IP address is different.

The number of specified IP addresses is different.

Specify the correct number of IP address and re-execute the command.

703

could not switch interface because standby interface does not exist.

As there is no interface in standby state, an interface cannot be switched.

Check that there is a physical interface in standby state with "dsphanet" command.

704

specified interface is connected to a virtual bridge.

The specified virtual interface is connected to a virtual bridge.

Disconnect from a virtual bridge and execute the command again.

705

invalid VLAN-ID.

The specified VLAN ID is invalid.

Specify the valid VLAN ID and execute the command again.

706

could not start hanetpathmd.

Network monitoring daemon cannot be activated.

Check that there is no problem in the network monitoring setting. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

707

the name of the virtual interface is already used..name=xxx

The name of the virtual interface has already been used.

With " ifconfig -a", find the interface which has the same name. If it is the virtual bridge, delete it with the "brctl" command.

708

bundled interface is unused because the vlan interface is created.

As the VLAN interface is created for the bundled physical interface, a physical interface was not used.

Check whether the interface is created for the bundled physical interface with "ifconfig -a". If so, delete the VLAN interface with the "vconfig" or "ip" command and execute the command again.

730

different network addresses are inappropriate.

Network addresses set for the NICs to be used are different.

Set the same network addresses for the NICs to be used. Review the assigned IP address (hostname) and netmask (prefix length).

760

ioctl(SHAIOCSETPDEVRCV) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control function is correctly set. If no problem has been found, re-execute the command. If the same error occurs, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message.

761

ioctl(SHAIOCDELPDEVRCV) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control function is correctly set. If no problem has been found, re-execute the command. If the same error occurs, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message.

762

ioctl(SHAIOCTCPABORT) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control function is correctly set. If no problem has been found, re-execute the command. If the same error occurs, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message.

763

A process has failed on some of the NIC shared virtual interfaces.

A process has failed on some of the virtual interfaces sharing NICs.

Re-execute the command. If the same error occurs, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message.

764

failed to get ip address information.

Failed to get the IP address information.

The IP address information for the specified NIC may not be set in the /etc/sysconfig/network-script/ifcfg-ethX file (X indicates the device number). Set the IP address information in the /etc/sysconfig/network-script/ifcfg-ethX file and re-execute the command. If the same error occurs, collect materials for the examination of the Redundant Line Control function and contact field engineers to report the error message.

766

ioctl(SHAIOCSETNICCHANGE) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

767

ioctl(SHAIOCGETSHADEVATTR) fail.

An error occurred in the internally used system call

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

768

ioctl(SHAIOCSETLBMODE) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

769

ioctl(SHAIOCLBCTL) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

770

ioctl(SHAIOCGETLBPARAM) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

771

ioctl(SHAIOCGETLBINFO) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

772

ioctl(SHAIOCPREUNPLUMB) fail.

An error occurred in the internally used system call.

Check that the Redundant Line Control Function is correctly set. After confirming that there is no problem, execute the command again. If the same phenomenon occurs, collect materials for the examination of the Redundant Line Control Function and contact field engineers to report the error message.

PreviousNext
Copyright FUJITSU LIMITED 2008-2013