Veritas Cluster Server Bundled Agents Reference Guide
Share Embed Flag
Download ePaper

Veritas Cluster Server Bundled Agents Reference Guide

Veritas™ Cluster Server Bundled Agents Reference Guide - Symantec Veritas™ Cluster Server Bundled Agents Reference Guide - Symantec

d1mj3xqaoh14j0.cloudfront.net
from d1mj3xqaoh14j0.cloudfront.net More from this publisher
17.08.2015 Views

62 Network agents Lanman agent Table 3-5 Lanman agent required attributes (continued) Required Attributes VirtualName Description The virtual computer name to be assigned to the server. The virtual name must be fewer than 15 characters. Note that if you specify a virtual computer name in lowercase letters, the agent converts it to uppercase. For example, the name VCSServer is converted to VCSSERVER. Type and Dimension: string-scalar Table 3-6 Lanman agent optional attributes Optional Attributes ADContainer Description Specifies the distinguished name of the Active Directory container or the organizational unit (OU) for the newly created computer object. If no value is specified for this attribute, the Lanman resource creates the computer object in the default container "Computers." Note that the user account for VCS Helper service must have adequate privileges on the specified container to create and update computer accounts. Refer to Microsoft documentation for information on assigning user privileges for a container. By default, the attribute contains no value. Note: Value specified for this attribute will be effective only if ADUpdateRequired is set to 1. Type and Dimension: string-scalar ADCriticalForOnline Defines whether the Lanman resource faults if the agent fails to update the Active Directory. The value 1 indicates that the resource faults in case of a failure to update the Active Directory. The value 0 indicates that it does not. Default is 0. Type and Dimension: boolean-scalar

Network agents Lanman agent 63 Table 3-6 Lanman agent optional attributes (continued) Optional Attributes AdditionalDNSServers Description An array that specifies the IP addresses of the additional DNS servers that will be updated by the Lanman resource. For all the Windows DNS servers, the forward and reverse lookup zones must be configured. For all the Berkeley Internet Name Domain (BIND) servers, only the forward lookup zones are required. All additional DNS servers are considered as Windows DNS servers by default. If any additional DNS server is a Berkeley Internet Name Domain (BIND) server, you will have to specify it in the attribute value. Example: "{"10.212.108.9" = "","10.212.108.10" = "BIND"}" Where 10.212.108.9 is the IP address of a Windows DNS server, and 10.212.108.10 is the IP address of a BIND DNS server. By default, the attribute contains no value. Values specified for this attribute will be effective only if DNSUpdateRequired is set to 1. The Lanman agent creates only CNAME records on BIND servers. You must also specify the AliasName attribute in case of BIND server updates. Note: The Lanman agent supports BIND version 8 and above. Note: In cases where the default DNS is a BIND DNS server, set the value of the DNSOptions attribute to IgnoreDefault, and specify the BIND DNS server details in this attribute. Note: If the BIND DNS servers are configured for secure updates, then you must configure the TSIG keys either in the DNSZones attribute or the TSIGKeyFile attribute. Type and Dimension: string-association ADUpdateRequired Defines whether the Lanman resource updates the Active Directory with the virtual name. The value 1 indicates that the agent updates the Active Directory. The value 0 indicates it does not. Default is 0. Type and Dimension: boolean-scalar

Network agents<br />

Lanman agent<br />

63<br />

Table 3-6<br />

Lanman agent optional attributes (continued)<br />

Optional Attributes<br />

AdditionalDNS<strong>Server</strong>s<br />

Description<br />

An array that specifies the IP addresses of the additional DNS<br />

servers that will be updated by the Lanman resource. For all<br />

the Windows DNS servers, the forward and reverse lookup<br />

zones must be configured. For all the Berkeley Internet Name<br />

Domain (BIND) servers, only the forward lookup zones are<br />

required.<br />

All additional DNS servers are considered as Windows DNS<br />

servers by default. If any additional DNS server is a Berkeley<br />

Internet Name Domain (BIND) server, you will have to specify<br />

it in the attribute value.<br />

Example:<br />

"{"10.212.108.9" = "","10.212.108.10" = "BIND"}"<br />

Where 10.212.108.9 is the IP address of a Windows DNS server,<br />

and 10.212.108.10 is the IP address of a BIND DNS server.<br />

By default, the attribute contains no value. Values specified<br />

for this attribute will be effective only if DNSUpdateRequired<br />

is set to 1.<br />

The Lanman agent creates only CNAME records on BIND<br />

servers. You must also specify the AliasName attribute in case<br />

of BIND server updates.<br />

Note: The Lanman agent supports BIND version 8 and above.<br />

Note: In cases where the default DNS is a BIND DNS server,<br />

set the value of the DNSOptions attribute to IgnoreDefault,<br />

and specify the BIND DNS server details in this attribute.<br />

Note: If the BIND DNS servers are configured for secure<br />

updates, then you must configure the TSIG keys either in the<br />

DNSZones attribute or the TSIGKeyFile attribute.<br />

Type and Dimension: string-association<br />

ADUpdateRequired<br />

Defines whether the Lanman resource updates the Active<br />

Directory with the virtual name. The value 1 indicates that<br />

the agent updates the Active Directory. The value 0 indicates<br />

it does not.<br />

Default is 0.<br />

Type and Dimension: boolean-scalar

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!