Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
60 Network agents Lanman agent If security policies are enabled on Windows Server 2008, ensure that the startup type of the Server Service is set to Automatic. Dependency The Lanman resource depends on the IP (in case of IPv4) and IPv6 (incase of IPv6) resource. If you change your Lanman resource dependency to a new IP resource and bring the Lanman resource online, a ping to the virtual name might respond from the IP address of the previous IP resource until the next WINS broadcast. The WINS broadcast updates the WINS database with the changed association. For example, if you took the Lanman resource offline, changed the Lanman resource dependency from IP_A to IP_B, and brought the Lanman resource online, a ping to the virtual name might still respond from IP_A. Note that the IP_A resource is kept online during this process. The ping will respond from IP_B after the next WINS broadcast updates the WINS database. Agent functions Online Offline Monitor Binds the IP addresses with the specified virtual computer name. The agent also queries the name server of the domain for Host (A), PTR, and CNAME records and adds or updates the records on the name server . Removes the IP address binding from the virtual computer name. Verifies the IP addresses are bound to the virtual computer name. If DNSUpdateRequired and DNSRefreshRequired is enabled and the resource is online, then the Lanman agent refreshes the resource records on the DNS servers. The agent queries the name servers for DNS records. It reports back ONLINE if the response from all the name servers contains the Host (A), PTR, and CNAME records. If no servers return the appropriate records, the monitor reports the resource as OFFLINE. State definitions ONLINE OFFLINE Indicates the IP addresses are bound to the virtual computer name and the DNS records are as expected. Indicates the IP addresses are not bound to the virtual computer name or the agent failed to create the DNS records or the expected DNS records were not found.
Network agents Lanman agent 61 UNKNOWN Indicates the agent could not determine the status of the resource. Resource type definition type Lanman ( static keylist LogDbg = {DBG_21} static i18nstr ArgList[] = {VirtualName, MultiNet, "IPResName:Address", "IPResName:SubNetMask", "IPResName:MACAddress", MultiNetInfo, DNSUpdateRequired, ADUpdateRequired, DNSCriticalForOnline, ADCriticalForOnline, ADContainer, DNSOptions, AdditionalDNSServers, DNSRefreshInterval, DNSZones, AliasName, TSIGKeyFile, TTL} str VirtualName str IPResName boolean MultiNet = 0 str MultiNetInfo[] boolean DNSUpdateRequired = 0 boolean ADUpdateRequired = 0 boolean DNSCriticalForOnline = 0 boolean ADCriticalForOnline = 0 str ADContainer str DNSOptions[] str AdditionalDNSServers{} int DNSRefreshInterval = 0 str DNSZones{} str AliasName = "" str TSIGKeyFile = "" int TTL = 0 ) Attribute definitions Table 3-5 Lanman agent required attributes Required Attributes IPResName Description The name of the IP resource on which the Lanman resource depends. Do not define a value for this attribute if the MultiNet attribute is set to 1. Type and Dimension: string-scalar
- Page 9 and 10: Contents 9 Attribute definitions ..
- Page 11 and 12: Contents 11 Sample configuration ..
- Page 13 and 14: Contents 13 Resource type definitio
- Page 15 and 16: Chapter 1 Introducing VCS bundled a
- Page 17 and 18: Introducing VCS bundled agents Attr
- Page 19 and 20: Introducing VCS bundled agents Cate
- Page 21 and 22: Introducing VCS bundled agents Whic
- Page 23 and 24: Chapter 2 Storage agents This chapt
- Page 25 and 26: Storage agents DiskReservation (Dis
- Page 27 and 28: Storage agents Mount agent 27 Mount
- Page 29 and 30: Storage agents Mount agent 29 Table
- Page 31 and 32: Storage agents Volume Manager Diskg
- Page 33 and 34: Storage agents Volume Manager Diskg
- Page 35 and 36: Storage agents MountV agent 35 Tabl
- Page 37 and 38: Storage agents MountV agent 37 str
- Page 39 and 40: Storage agents MountV agent 39 Tabl
- Page 41 and 42: Storage agents VVRSnap agent 41 Sam
- Page 43 and 44: Storage agents VMwareDisks agent 43
- Page 45 and 46: Storage agents VMwareDisks agent 45
- Page 47 and 48: Storage agents VMNSDg agent 47 Agen
- Page 49 and 50: Storage agents NativeDisks agent 49
- Page 51 and 52: Chapter 3 Network agents This chapt
- Page 53 and 54: Network agents NIC agent 53 Resourc
- Page 55 and 56: Network agents IP agent 55 IP agent
- Page 57 and 58: Network agents IPv6 agent 57 The IP
- Page 59: Network agents Lanman agent 59 IPv6
- Page 63 and 64: Network agents Lanman agent 63 Tabl
- Page 65 and 66: Network agents Lanman agent 65 Tabl
- Page 67 and 68: Network agents Lanman agent 67 Tabl
- Page 69 and 70: Network agents Lanman agent 69 Tabl
- Page 71 and 72: Network agents Lanman agent 71 LANM
- Page 73 and 74: Chapter 4 FileShare agents This cha
- Page 75 and 76: FileShare agents FileShare agent 75
- Page 77 and 78: FileShare agents FileShare agent 77
- Page 79 and 80: FileShare agents FileShare agent 79
- Page 81 and 82: FileShare agents FileShare agent 81
- Page 83 and 84: FileShare agents CompositeFileShare
- Page 85 and 86: FileShare agents CompositeFileShare
- Page 87 and 88: FileShare agents CompositeFileShare
- Page 89 and 90: FileShare agents CompositeFileShare
- Page 91 and 92: FileShare agents CompositeFileShare
- Page 93 and 94: Chapter 5 PrintShare agents This ch
- Page 95 and 96: PrintShare agents PrintSpool agent
- Page 97 and 98: PrintShare agents PrintShare agent
- Page 99 and 100: PrintShare agents PrintShare agent
- Page 101 and 102: PrintShare agents PrintShare agent
- Page 103 and 104: Chapter 6 Services and applications
- Page 105 and 106: Services and applications agents In
- Page 107 and 108: Services and applications agents In
- Page 109 and 110: Services and applications agents In
60<br />
Network agents<br />
Lanman agent<br />
If security policies are enabled on Windows <strong>Server</strong> 2008, ensure that the startup<br />
type of the <strong>Server</strong> Service is set to Automatic.<br />
Dependency<br />
The Lanman resource depends on the IP (in case of IPv4) and IPv6 (incase of IPv6)<br />
resource.<br />
If you change your Lanman resource dependency to a new IP resource and bring<br />
the Lanman resource online, a ping to the virtual name might respond from the<br />
IP address of the previous IP resource until the next WINS broadcast. The WINS<br />
broadcast updates the WINS database with the changed association.<br />
For example, if you took the Lanman resource offline, changed the Lanman<br />
resource dependency from IP_A to IP_B, and brought the Lanman resource online,<br />
a ping to the virtual name might still respond from IP_A. Note that the IP_A<br />
resource is kept online during this process. The ping will respond from IP_B after<br />
the next WINS broadcast updates the WINS database.<br />
Agent functions<br />
Online<br />
Offline<br />
Monitor<br />
Binds the IP addresses with the specified virtual computer name. The<br />
agent also queries the name server of the domain for Host (A), PTR,<br />
and CNAME records and adds or updates the records on the name<br />
server .<br />
Removes the IP address binding from the virtual computer name.<br />
Verifies the IP addresses are bound to the virtual computer name. If<br />
DNSUpdateRequired and DNSRefreshRequired is enabled and the<br />
resource is online, then the Lanman agent refreshes the resource<br />
records on the DNS servers. The agent queries the name servers for<br />
DNS records. It reports back ONLINE if the response from all the name<br />
servers contains the Host (A), PTR, and CNAME records. If no servers<br />
return the appropriate records, the monitor reports the resource as<br />
OFFLINE.<br />
State definitions<br />
ONLINE<br />
OFFLINE<br />
Indicates the IP addresses are bound to the virtual computer name<br />
and the DNS records are as expected.<br />
Indicates the IP addresses are not bound to the virtual computer name<br />
or the agent failed to create the DNS records or the expected DNS<br />
records were not found.
Change language