How to Install and Configure IIS Agent for VERITAS Cluster Server 1.2.1

Article:TECH11063  |  Created: 2001-01-14  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH11063
Article Type
Technical Solution


Environment

Issue



How to Install and Configure IIS Agent for VERITAS Cluster Server 1.2.1

Solution



Installation Prerequisites

The following list of prerequisites is critical to a proper installation and configuration of the VERITAS Cluster Server (VCS) NT IIS Agent.

1. Properly installed VCS-NT 1.2.1 .
2. Properly installed Internet Information Server (IIS) in a clustered environment. (Refer to the TechNote in the Related Document section.)
3. An available TCP/IP address for Virtual IP resource.


Installing the IIS Agent for VCS-NT

1. Log in as the NT Administrator and run setup.exe from your Agent Distribution or download. Click Next.

2. Select the desired nodes and click Next. (Figure 1)

Figure 1


3. Verify that the files are installed. Click Finish.

Configuring the IIS Agent

1. Log in to desired cluster through Cluster Manager.

2. Select Tools > Configuration Wizard from the menu bar. Click Next.

3. Enter a Service Group name. Select the nodes that you want part of the Service Group. Check the boxes marked Start-Up if Auto Starting of the Service Group is desired. If not checked, the Service Group must be started manually (Figure 2). Click Next.

Figure 2


4. Click Next to use a Template. (Figure 3)

Figure 3


5.Select the IISGroup from the templates menu in the configuration wizard (Figure 4). Select Next .

Figure 4


The Service Group will be created. (Figure 5) Click Next.

Figure 5


6. Select the Diskres resource in the left pane. (Figure 6)

Figure 6


7. Click on the button to the right of the attribute that is to be configured. The following attributes must be configured for the Diskres attribute:

Disks: the number of the shared disk that IIS was installed on. This can be found through Disk Administrator and the GetDrive utility.

Signature: The disk signature assigned by Windows NT to name the disk. Invoking the getdrive command at a command prompt will generate a file (driveinfo.txt) that will contain this information. (Figure 7)

Figure 7


8. Put the appropriate information in each attribute and click OK.

9. Select the IIS_IP resource in the left pane. The following attributes must configured correctly for the IIS Agent to function:

AdapterName: This the name of the public adapter, e.g., the one that is accessed by the network. To determine the name, invoke ipconfig /all at a command prompt. Ensure that the name is copied exactly. It is case-sensitive.
An example would be: E100B1

If node members are using Network Adapters with differing names, enter each node's Network Adapter name as a local value. Select Local option in the AdapterName attribute.

Address: This is the virtual IP address: an single IP address that describes all nodes in the cluster. This address must not be used by any other device on the network. When a client accesses the online cluster node, it will be transparent, as this address is reserved to cluster as a whole. Remember, the Virtual IP address is NOT an address assigned to a particular Network Adapter Card on the system. To ensure that this address is not being used at this time, invoke a ping command directed at that address. If no response is given, it is probably safe. (Figure 8.) Contact the network administrator to ensure that the IP address being used is available.

Figure 8


SubNetMask: This the subnet mask for the Virtual IP address above.

10. Select IIS_Mount from the left pane. (Figure 9)

Figure 9


The following attributes must be configured correctly for the IIS Agent to work properly:

DiskNo: the number of the shared disk that IIS was installed on. This can be found through Disk Administrator and the GetDrive utility.

DriveLetter: This is the drive letter that was used when Internet Information Server (IIS) was installed. In this example, drive letter X is where \inetpub is located. Remember: only enter the drive letter. Do NOT put a colon (:) in this field.

PartitionNo: This is the number of the partition on the disk (DiskNo). This can be found in Disk Administrator. The partition numbering starts at 1.

For example: The first partition displayed on a drive (left to right) in Disk Administrator is partition 1. The next to the right is partition 2 and so one. Also, if there is only one partition on the drive, it is also partition 1.

Signature: The disk signature assigned by Windows NT to name the disk. Invoking the getdrive command at a command prompt will generate a file (driveinfo.txt) that will contain this information. (Figure 7, displayed previously)

11. Select IIS_NIC from the left pane. Enter the same value from Step 9 in the AdapterName attribute field. Click Finish.

Onlining the Service Group for the first time.

1. Open Cluster Manager. Login to the desired cluster.

2. Right-click on the Service Group in the left pane

3. Select Enable Resources. Note that the IIS_NIC resource is online immediately. This is due to the resource being "persistent". This is normal and will be online on all nodes at the same time.

4. Right-click on the Service Group in the left pane. Select Online and the desired node (Figure 10). Select Yes

Figure 10


5. The Service Group will start to come online. Make sure to change the view to the node that you are bringing online. This can be selected by choosing desired node on the bottom of the right pane. (Figure 11)

Figure 11


The IIS Service Group is now online.




Legacy ID



236606


Article URL http://www.symantec.com/docs/TECH11063


Terms of use for this information are found in Legal Notices