Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
194 Troubleshooting bundled agents Troubleshooting network agents The subnet mask specified in the configuration file does not match with the subnet mask for the configured adapter. Recommended Action: Verify the subnet mask specified in the MultiNetInfo attribute is correct. WINS address specified in the configuration is not found in the adapter's WINS address list The specified WINS address does not exist in the WINS address list of the adapter. Recommended Action: Verify the WINS address specified in the MultiNetInfo attribute is correct. Attempt to start ‘Veritas Cluster Server Helper’ service has failed. (error_type: Error Type, error_code: Error Code) The agent failed to start the specified service. Recommended Action: Verify whether the service is installed on the node. Also verify whether the user, in whose context the service will run, has the required permissions. Attempt to stop ‘Veritas Cluster Server Helper’ service has failed. (error_type: Error Type, error_code: Error Code) The agent failed to stop the specified service. Recommended Action: Verify whether the service is installed on the node. Also verify whether the user, in whose context the service will run, has the required permissions. Attempt to online the Lanman resource has failed. (error_type: Error Type, error_code: Error Code) The agent failed to online the Lanman resource. This is a VCS internal error. Recommended Action: See the Windows error code for more information. Contact Symantec Technical Support if the problem persists. V-16-10051-3051 No DNS servers IPv6 address found. Cannot update DNS. Please provide IPv6 addresses for the DNS servers either on the NIC or the Lanman configuration. This error is specific to an IPv6 environment. The Lanman agent has failed to update the virtual IPv6 address entry in the DNS records as the DNS server details are not specified. The Lanman resource itself is able to come online, but other resources in the service group that depend on the Lanman resource (FileShare for example) may fail to come online as the virtual server name that uses an IPv6 address is not updated in the DNS.
Troubleshooting bundled agents Troubleshooting FileShare agents 195 In an IPv6 environment, the Lanman agent relies on the DNS records to validate the server name on the network. Recommended Action: If the virtual IP is an IPv6 address then you must specify the DNS server details, either in the network adapter properties or in the Lanman agent’s AdditionalDNSServers attribute. Troubleshooting FileShare agents FileShare agents comprise the FileShare agent and the CompositeFileShare agent. FileShare agent error messages Attribute value(s) invalid for attr_name The specified attribute name has invalid value. Recommended Action: Verify the configuration file and make sure the correct attribute value is specified. Failed to open folder folder_name [ErrorType:Error Code] The agent failed to open the folder specified in the ShareName attribute. Recommended Action: Verify whether the specified folder exists. Check the permissions for the folder. Folder folder_name (\\\\system_name\\share_name) already shared The specified folder name is already shared. Recommended Action: Verify the configuration file for the specified ShareName. Failed to share folder folder_name as (\\\\system_name\\share_name) [ErrorType:Error Code] The agent failed to share the specified folder. Recommended Action: Verify the configuration file for the specified ShareName. MaxUsers for share share_name is less than configured The number of users authorized to access a share is less than the number of users specified in the MaxUsers attribute. Recommended Action: Make sure the number of users authorized to access a share and the number of users specified in the MaxUsers attribute is same. Failed to unshare folder folder_name as (\\\\system_name\\share_name) [ErrorType:Error Code] The agent failed to unshare the specified folder.
- Page 143 and 144: VCS infrastructure and support agen
- Page 145 and 146: VCS infrastructure and support agen
- Page 147 and 148: VCS infrastructure and support agen
- Page 149 and 150: VCS infrastructure and support agen
- Page 151 and 152: VCS infrastructure and support agen
- Page 153 and 154: VCS infrastructure and support agen
- Page 155 and 156: VCS infrastructure and support agen
- Page 157 and 158: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
- Page 165 and 166: VCS hardware replication agent for
- Page 167 and 168: VCS hardware replication agent for
- Page 169 and 170: VCS hardware replication agent for
- Page 171 and 172: Chapter 9 Troubleshooting bundled a
- Page 173 and 174: Troubleshooting bundled agents Trou
- Page 175 and 176: Troubleshooting bundled agents Trou
- Page 177 and 178: Troubleshooting bundled agents Trou
- Page 179 and 180: Troubleshooting bundled agents Trou
- Page 181 and 182: Troubleshooting bundled agents Trou
- Page 183 and 184: Troubleshooting bundled agents Trou
- Page 185 and 186: Troubleshooting bundled agents Trou
- Page 187 and 188: Troubleshooting bundled agents Trou
- Page 189 and 190: Troubleshooting bundled agents Trou
- Page 191 and 192: Troubleshooting bundled agents Trou
- Page 193: Troubleshooting bundled agents Trou
- Page 197 and 198: Troubleshooting bundled agents Trou
- Page 199 and 200: Troubleshooting bundled agents Trou
- Page 201 and 202: Troubleshooting bundled agents Trou
- Page 203 and 204: Troubleshooting bundled agents Trou
- Page 205 and 206: Troubleshooting bundled agents Trou
- Page 207 and 208: Troubleshooting bundled agents Trou
- Page 209 and 210: Troubleshooting bundled agents Trou
- Page 211 and 212: Troubleshooting bundled agents Trou
- Page 213 and 214: Troubleshooting bundled agents Trou
- Page 215 and 216: Troubleshooting bundled agents Trou
- Page 217 and 218: Troubleshooting bundled agents Trou
- Page 219 and 220: Index Symbols
- Page 221 and 222: Index 221 FileOnOnly agent (continu
- Page 223 and 224: Index 223 Process agent agent funct
194<br />
Troubleshooting bundled agents<br />
Troubleshooting network agents<br />
The subnet mask specified in the configuration file does not match with the subnet<br />
mask for the configured adapter.<br />
Recommended Action: Verify the subnet mask specified in the MultiNetInfo<br />
attribute is correct.<br />
WINS address specified in the configuration is not found in the adapter's WINS<br />
address list<br />
The specified WINS address does not exist in the WINS address list of the adapter.<br />
Recommended Action: Verify the WINS address specified in the MultiNetInfo<br />
attribute is correct.<br />
Attempt to start ‘<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> Helper’ service has failed. (error_type:<br />
Error Type, error_code: Error Code)<br />
The agent failed to start the specified service.<br />
Recommended Action: Verify whether the service is installed on the node. Also<br />
verify whether the user, in whose context the service will run, has the required<br />
permissions.<br />
Attempt to stop ‘<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> Helper’ service has failed. (error_type:<br />
Error Type, error_code: Error Code)<br />
The agent failed to stop the specified service.<br />
Recommended Action: Verify whether the service is installed on the node. Also<br />
verify whether the user, in whose context the service will run, has the required<br />
permissions.<br />
Attempt to online the Lanman resource has failed. (error_type: Error Type,<br />
error_code: Error Code)<br />
The agent failed to online the Lanman resource. This is a VCS internal error.<br />
Recommended Action: See the Windows error code for more information. Contact<br />
Symantec Technical Support if the problem persists.<br />
V-16-10051-3051 No DNS servers IPv6 address found. Cannot update DNS.<br />
Please provide IPv6 addresses for the DNS servers either on the NIC or the<br />
Lanman configuration.<br />
This error is specific to an IPv6 environment. The Lanman agent has failed to<br />
update the virtual IPv6 address entry in the DNS records as the DNS server details<br />
are not specified.<br />
The Lanman resource itself is able to come online, but other resources in the<br />
service group that depend on the Lanman resource (FileShare for example) may<br />
fail to come online as the virtual server name that uses an IPv6 address is not<br />
updated in the DNS.
Change language