Home » HP Manuals » Storage Devices » HP ProLiant DL380G5-WSS » Manual Viewer

HP ProLiant DL380G5-WSS HP StorageWorks Clustered File System 3.2.1 Windows St - Page 175

Change a Host Bus Adapter or Driver

Get HP ProLiant DL380G5-WSS PDF manuals and user guides

View all HP ProLiant DL380G5-WSS manuals

Add to My Manuals
Save this manual to your list of manuals

Page 175 highlights

Chapter 16: SAN Maintenance 166 Change a Host Bus Adapter or Driver HP Clustered File System and the psd driver must be disabled when you add, remove, or update a Host Bus Adapter or its driver. The following procedure describes how to change a Host Bus Adapter or driver on a cluster server. All commands are run from the Command Prompt. 1. Stop HP Clustered File System: net stop matrixserver 2. Disable the HP Clustered File System service: mxservice -uninstall 3. Remove the psd driver from the driver stack: psdcoinst -uninstall 4. Reboot the server. The server will come up without HP Clustered File System and the psd driver. 5. Make the necessary change to the HBA or driver. Reboot the system if the HBA installation prompts you to do so. 6. (Optional.) Verify that the new HBA is supported: mxcheck 7. Update the registry: regedit /s psd.reg 8. Enable HP Clustered File System and the psd driver: mxservice -install psdcoinst -install 9. Reboot the server to return the psd driver to the driver stack. 10. When the system is rebooted, HP Clustered File System will still be disabled in the Windows Services Control Panel. Re-enable it for Automatic startup if desired. 11. Start HP Clustered File System (or wait until the next reboot). net start matrixserver

Section	Page
Contents	3
HP Technical Support	10
HP Storage Web Site	10
HP NAS Services Web Site	11
Introduction	12
Product Features	12
Overview	14
The Structure of a Cluster	14
Software Components	15
Shared SAN Devices	17
Volume Manager	17
PSFS Filesystems	17
HP Clustered File System Databases	18
Virtual Hosts and Failover Protection	18
Service and Device Monitors	19
Event Notification	20
Cluster Design Guidelines	20
Server Memory	20
Supported Configurations	21
Single FC Port, Single FC Switch, Single Fabric	21
Single FC Port, Dual FC Switch, Single Fabric	22
3	23
Cluster Administration	23
Administrative Considerations	23
Using Active Directory with HP Clustered File System	25
Tested Configuration Limits	26
Cluster Management Applications	26
Manage a Cluster with the Management Console	27
Start the Management Console	27
Disconnect from a Cluster	28
Exit a Management Console Session	28
Manage a Cluster from the Command Line	28
The HP CFS Management Console	28
Virtual Hosts Tab	30
Notifiers Tab	31
Filesystems Tab	32
Applications Tab	33
Cluster Alerts	34
Assign or Change Passwords	35
Start HP StorageWorks Clustered File System	36
Stop HP Clustered File System	36
Back Up the Cluster Configuration	36
4	37
Configure Servers	37
Add or Modify a Server	37
Other Server Configuration Procedures	39
Move a Server	39
Delete a Server	39
Disable a Server	39
Enable a Server	40
Change the IP Address for a Server	40
1. Stop HP Clustered File System on server S2.	40
2. Change the IP address of server S2. We will now identify the server as S2a.	40
3. Start HP Clustered File System on server S2a. The server joins the cluster, which now consists of servers S1, S2, S3, and S2a. Server 2 is down and S1, S2a, and S3 are up.	40
4. Delete server S2 from the cluster. This step will remove references to the server.	40
5. Update virtual hosts and any other cluster entities that used server S2 to now include S2a.	40
HP Clustered File System License File	41
Upgrade the License File	41
Refresh the License File	41
Supported HP Clustered File System Features	41
Migrate Existing Servers to HP Clustered File System	42
Configure Servers for DNS Load Balancing	43
5	46
Configure Network Interfaces	46
Overview	46
Administrative Traffic	46
Network Topology	47
Virtual Hosts	47
Network Interfaces and the Management Console	47
Administrative Network Failover	48
Making Network Changes	49
Add or Modify a Network Interface	49
Remove a Network Interface	50
Allow or Discourage Administrative Traffic	51
Enable or Disable a Network Interface for Virtual Hosting	51
6	52
Configure the SAN	52
Overview	52
SAN Configuration Requirements	52
Storage Control Layer Module	52
Device Database and Membership Partitions	53
Import SAN Disks	53
Deport SAN Disks	55
Local Disk Information	56
Display Disk Information with sandiskinfo	57
7	60
Configure Dynamic Volumes	60
Overview	60
Basic and Dynamic Volumes	60
Types of Dynamic Volumes	61
Dynamic Volume Names	61
Configuration Limits	61
Guidelines for Creating Dynamic Volumes	62
Create a Dynamic Volume	62
Dynamic Volume Properties	65
View Stripeset Information	66
Extend a Dynamic Volume	67
Destroy a Dynamic Volume	69
Recreate a Dynamic Volume	70
Convert a Basic Volume to a Dynamic Volume	72
8	74
Configure PSFS Filesystems	74
Overview	74
Filesystem Features	74
Concurrent Access by Multiple Servers	74
Standard Filesystem Operations and Semantics	74
Journaling Filesystem	75
Server Registry	75
Filesystem Management and Integrity	76
Filesystem Synchronization and Device Locking	76
Crash Recovery	77
Create a Filesystem	77
Create a Filesystem from the Management Console	78
Recreate a Filesystem	79
Create a Filesystem from the Command Line	80
The mx Command	80
The psfsformat Command	80
Drive Letters and Mount Paths	81
Assign Drive Letters or Paths	81
View Drive Letter or Path Assignments	82
Remove Drive Letter or Path Assignments	83
Filesystem Mounts	84
View or Change Filesystem Properties	84
Volume Tab	84
Extend a Mounted Filesystem	85
Features Tab	86
View Filesystem Status from the Command Line	86
Suspend a Filesystem for Backups	87
Check a Filesystem	88
Perform a Filesystem Check	88
Enable or Disable FZBMs	90
9	91
Cluster Operations on the Applications Tab	91
Applications Overview	91
Create Applications	91
The Applications Tab	92
Application States	93
Filter the Applications Display	94
Using the Applications Tab	95
Applications	96
Servers	96
Virtual Hosts	96
Service and Device Monitors	97
10	98
Configure Virtual Hosts	98
Overview	98
Cluster Health and Virtual Host Failover	99
Guidelines for Creating Virtual Hosts	100
Add or Modify a Virtual Host	101
Configure Applications for Virtual Hosts	104
Other Procedures	104
Enable or Disable a Virtual Host	104
Delete a Virtual Host	105
Change the Virtual IP Address for a Virtual Host	105
1. At the Command Prompt, run the following command:	105
2. Edit the mxdump.out file, replacing all occurrences of the old IP address with the new IP address.	105
3. At the beginning of the mxdump.out file, add a line such as the following to remove the old IP address from the virtual host configuration:	105
4. Delete any lines in mxdump.out that do not need to change.	105
5. Run the following command to update the cluster configuration with the new IP address:	105
Re-Host Virtual Hosts	106
Virtual Hosts and Failover	106
Virtual Host Activeness Policy	107
1. If the virtual host is disabled, it is not made active anywhere.	107
2. ClusterPulse considers the list of servers that are both up and enabled and that are configured for the virtual host. The network interface that the virtual host is associated with must also be both up and enabled for hosting. Note the following:	107
3. ClusterPulse narrows the list to those servers without inactive, down, or disabled HP Clustered File System device monitors. If there are no servers that meet this criteria, the virtual host is not made active anywhere.	108
4. If the virtual host is currently active on a server and that virtual host has the NOFAILBACK policy, then this active server is moved to the head of the list of preferred servers to be considered.	108
5. From this list, ClusterPulse tries to find a server with all services up and enabled. If ClusterPulse finds a server meeting these conditions, it will use it, preferring servers earlier in the list of servers configured for the virtual host.	108
6. If there are no servers with completely healthy services, ClusterPulse picks a server that has at least one service up and en...	108
7. The selected server will have one interface that was configured for this virtual host. The virtual host will be active on this interface. If ClusterPulse cannot locate a server meeting these conditions, it does not place the virtual host anywhere.	108
Customize Service and Device Monitors for Failover	109
Specify Failover/Failback Behavior	109
Select a Backup Interface for Failover	109
Specify Failback Behavior of the Virtual Host	110
AUTOFAILBACK	110
NOFAILBACK	110
Failback Policy and Monitor Probe Severity	111
11	113
Configure Service Monitors	113
Overview	113
Service Monitors and Virtual Hosts	113
Service Monitors and Failover	114
Types of Service Monitors	114
FTP Service Monitor	115
HTTP Service Monitor	115
HTTPS Service Monitor	116
SMTP Service Monitor	116
TCP Service Monitor	116
Custom Service Monitor	117
Add or Modify a Service Monitor	117
Advanced Settings for Service Monitors	119
Service Monitor Policy	120
Timeout and Failure Severity	120
Service Priority	121
Probe Type	122
Custom Scripts	122
Scripts	123
Event Severity	124
Script Ordering	125
1. The Stop script is run on all servers where the virtual host should be inactive.	125
2. ClusterPulse waits for all Stop scripts to complete.	125
3. The Start script is run on the server where the virtual host is becoming active.	125
Other Configuration Procedures	126
Delete a Service Monitor	126
Disable a Service Monitor on a Specific Server	126
Enable a Previously Disabled Service Monitor	126
View Service Monitor Errors	127
Clear Service Monitor Errors	127
12	128
Configure Device Monitors	128
Overview	128
Multi-Active Device Monitors	128
DISK Device Monitor	129
GATEWAY Device Monitor	129
Custom Device Monitor	130
Server Assignments	130
Failover	131
Device Monitors and Failover	131
Device Monitor Activeness Policy	131
1. If the device monitor on a specific server is disabled, then the device monitor will not be made active on that server.	131
2. ClusterPulse considers the list of servers that are both up and enabled and that are configured for the device monitor. Note the following:	131
3. If the device monitor is multi-active, it will be active on all servers passing evaluation for steps 1 and 2. If the device m...	132
4. From the list of servers that pass evaluation for steps 1 and 2, ClusterPulse tries to find a server with all services up and...	132
5. If there are no servers with completely healthy services, ClusterPulse picks a server that has at least one service up and en...	132
6. If ClusterPulse cannot locate a server meeting these conditions, it will make the device monitor active on the first server in the list of servers for this device monitor.	132
Add or Modify a Device Monitor	132
Advanced Settings for Device Monitors	134
Probe Severity	135
Custom Scripts	137
Event Severity	138
Script Ordering	139
1. The Stop script is run on all servers where the shared device or virtual host should be inactive.	139
2. ClusterPulse waits for all Stop scripts to complete.	139
3. The Start script is run on the server where the virtual host or shared device is becoming active.	139
Virtual Hosts	140
Servers for Device Monitors	141
Other Configuration Procedures	142
Delete a Device Monitor	142
Disable a Device Monitor	143
Enable a Device Monitor	143
View Device Monitor Errors	143
13	144
Configure Notifiers	144
Overview	144
Add or Modify a Notifier	145
Other Configuration Procedures	146
Delete a Notifier	146
Disable a Notifier	146
Enable a Notifier	147
Test a Notifier	147
Notifier Message Format	147
Sample Notifier Messages	147
A Sample Notifier Script	148
14	149
Test Your Configuration	149
Test SAN Shared Filesystem Operation	149
Test SAN Connectivity and Shared Filesystem Operation	150
1. From the HP CFS Management Console, log into one of the cluster servers.	150
2. Import an unused SAN disk into your cluster configuration.	150
3. Create a PSFS filesystem on an unused partition on this disk.	150
4. Log into each of the servers as Administrator and perform some basic I/O tests to the shared filesystem using a tool such as WinZip. Verify that changes to the filesystem made by each server are visible to all other servers in the cluster.	150
Test Filesystem Failure Recovery	150
1. Configure the cluster with a shared filesystem as described in the previous procedure.	150
2. Pull the LAN network connection(s) from one of the servers. Verify that this server is unable to access the shared filesystem. Verify that the other servers in the cluster are still able to access the shared filesystem.	150
3. Reconnect the LAN network to the server and then reboot it. Verify that the server, upon rebooting, is able to mount the shared filesystem. Verify that all servers are able to access the shared filesystem.	150
4. Pull the SAN network connection(s) from one of the servers. Verify that this server is unable to access the shared filesystem. Verify that the other servers in the cluster are still able to access the shared filesystem.	150
5. Reconnect the SAN network to the server and then reboot it. Verify that the server, upon rebooting, is able to mount the shared filesystem. Verify that all servers are able to access the shared filesystem.	150
6. Power off one of the servers. Verify that the other servers in the cluster are still able to access the shared filesystem.	150
7. Restore the power to the server and then reboot it. Verify that this server, upon rebooting, is able to mount the shared filesystem. Verify that all servers are able to access the shared filesystem.	151
Test Virtual Host Operation and Failover	151
Test Failure and Reintegration of Servers	151
1. From the HP CFS Management Console, log into a backup cluster server.	151
2. Configure the cluster with a single virtual host.	151
3. Validate that all servers are up, that the virtual host is active on the primary server, and that the backup servers are inactive.	151
4. Pull the LAN network connection(s) from the primary server.	151
5. Verify that the Management Console shows that the primary server is down and inactive and that the first backup server is active.	151
6. Reconnect the primary server to the LAN.	151
7. Verify that the primary server re-enters the cluster as the active host and that the first backup server becomes inactive.	151
Test Failure and Reintegration of Service Monitors	151
1. From the HP CFS Management Console, log into a backup server.	151
2. Add a service monitor to the virtual host already defined in the system.	151
3. Verify that all servers are up, that the service you are testing is up, and that the virtual host is active on the primary server and inactive on the backup servers.	152
4. Stop the service you are testing on the primary server (for example, for HTTP, bring down the HTTP process).	152
5. Verify that HP Clustered File System detects the service failure. The virtual host should be inactive on the primary server and active on the first backup server.	152
6. Start the service that you are testing on the primary server.	152
7. Verify that HP Clustered File System detects that the service has become active.	152
8. Verify that the virtual host is active on the primary server and inactive on the backup servers.	152
Test DNS Load-Balancing and Failover	152
Validate Correct Load-Balancing Operation	153
1. Ping www.acmd.com.	153
2. Validate that the returned IP address is 192.168.100.1.	153
3. Ping www.acmd.com.	153
4. Validate that the returned IP address is 192.168.100.2.	153
5. Continue to ping and validate that the opposite IP address is returned by DNS.	153
Validate Load-Balancing When a Server Is Down	153
1. From the HP CFS Management Console, log into one of the servers in the cluster.	153
2. Pull the LAN network connection(s) from a server that you are not logged onto.	153
3. Verify that HP Clustered File System detects that the server is down and that the backup for this virtual host takes over operation from the primary.	153
4. Ping the address www.acmd.com multiple times.	153
5. Verify that all requests are still being returned correctly.	153
6. Restore the LAN network connections.	153
7. Verify that DNS now serves up both IP addresses again and that the ping is returned correctly by both.	154
Test LAN Failover of Administrative Cluster Traffic	154
1. Connect your cluster servers with at least two physically separate LANs. Configure the Linux network software to enable the interfaces to these networks on each of the cluster servers.	154
2. From the HP CFS Management Console, log into one of the cluster servers.	154
3. Observe on the Management Console which of your LANs is currently being used for cluster administrative traffic. Physically disconnect one of the server's LAN connections to this network.	154
4. Observe on the Management Console that HP Clustered File System has noticed the network disconnection and has failed over the administrative cluster traffic to one of the other LANs.	154
5. Reconnect the disconnected server to the LAN. Observe on the Management Console that HP Clustered File System has noticed that network connectivity has been restored for this LAN.	154
15	155
Advanced Topics	155
The Effect of Monitors on Virtual Host Failover	155
Service Monitors	155
Custom Device Monitors	158
Integrate Custom Applications	161
Device Monitor or Service Monitor?	161
Built-In Monitor or User-Defined Monitor?	162
Example of Using Monitors with Applications	162
An Example of Start and Stop Scripts	163
Script Environment Variables	163
Limit the Servers That Can Join a Cluster	164
16	165
SAN Maintenance	165
Server Access to the SAN	165
Membership Partitions	166
Display the Status of SAN Ownership Locks	166
Manage Membership Partitions with mprepair	169
mprepair Utility	170
View Membership Partitions and Their Status	170
Active and Inactive Membership Partitions	171
Sizes for Membership Partitions	172
Export Configuration Changes	172
mprepair Options	172
Change a Host Bus Adapter or Driver	175
1. Stop HP Clustered File System:	175
2. Disable the HP Clustered File System service:	175
3. Remove the psd driver from the driver stack:	175
4. Reboot the server. The server will come up without HP Clustered File System and the psd driver.	175
5. Make the necessary change to the HBA or driver. Reboot the system if the HBA installation prompts you to do so.	175
6. (Optional.) Verify that the new HBA is supported:	175
7. Update the registry:	175
8. Enable HP Clustered File System and the psd driver:	175
9. Reboot the server to return the psd driver to the driver stack.	175
10. When the system is rebooted, HP Clustered File System will still be disabled in the Windows Services Control Panel. Re-enable it for Automatic startup if desired.	175
11. Start HP Clustered File System (or wait until the next reboot).	175
Server Cannot Be Located	176
Online Insertion of New Storage	176
Online Replacement of a FibreChannel Switch	177
Replace a Brocade FC Switch	177
1. Stop HP Clustered File System on any servers that are connected only to the original switch.	177
2. If possible, save the configuration information on the original switch. Use the configUpload command.	177
3. Record the IP address of the original switch. Use the ipAddrShow command.	177
4. Back up the zone configuration information, either from the original switch or from another switch in the fabric. Use the cfgShow command and record its output.	178
5. Connect the power and either the Ethernet or the serial console cable to the new switch.	178
6. Log on to the new switch.	178
7. Disable the switch with the switchDisable command.	178
8. Disable any stale active configuration on the new switch with the cfgDisable command.	178
9. Verify that the Brocade licenses are installed by using the licenseShow command. The new switch should have the same kind of license as the rest of the fabric.	178
10. Clear any stale zone configuration on the new switch with the cfgClear command.	178
11. Save the clean configuration with the cfgSave command.	178
12. Configure the new switch. If you saved the original configuration with the configUpload command, use the configDownload comm...	178
13. Connect the FC connectors to the new switch. Be sure to plug them into the same ports as on the original switch.	178
14. Set the Ethernet IP address on the new switch to the IP address of the original switch. Use the ipAddrSet command.	178
15. Enable the switch using the switchEnable command.	178
Replace a McDATA FC Switch	179
1. Stop HP Clustered File System on any servers that are connected only to the original switch.	179
2. If possible, save configuration information from the original switch. Some items such as the zone configuration are not neede...	179
3. After the original switch has been powered down, power up the new switch and set the IP address to the old switch's address t...	179
4. Connect to the EWS and take the switch offline using the Operations > Switch > Online State tab.	179
5. Make the switch operating mode and domain ID acceptable to the original fabric. This can be done either by consulting the fab...	179
6. Add the private community to the Configure > Management > SNMP tab and ensure that it is write enabled.	180
7. Connect the FC connectors to the new switch. Be sure to plug them into the same ports as on the original switch.	180
8. Bring the switch online.	180
17	181
Other Cluster Maintenance	181
Maintain the HP Clustered File System Event Log	181
Windows Event Viewer	182
HP CFS Management Console	182
View the Event Log	183
Set the Number of Lines to Display on the Server Log Window	183
Audit Administrative Commands	184
Add Your Own Messages to the Event Log	184
Cluster Alerts	185
Check the Server Configuration	185
Disable a Server for Maintenance	186
1. Disable the server. (Choose the server from the Servers window on the HP CFS Management Console, right-click, and select Disable.) This step causes the virtual host to fail over to a backup network interface on another server.	186
2. If you want the virtual host to remain on the backup network interface after the original server is returned to operation but...	186
3. Perform the necessary maintenance on the original server and then reenable it.	186
Troubleshoot Cluster Problems	186
HP Clustered File System Fails to Start	186
The Server Status Is “Down”	187
1. Verify that the server is connected to the network.	187
2. Verify that the network devices and interfaces are properly configured on the server.	187
3. Ensure that the ClusterPulse process is running on the server.	187
4. Verify that the same version of HP Clustered File System is installed on all servers in the cluster.	187
HP Clustered File System Considers a Running Service Down	187
1. Verify that the server is connected to the network.	187
2. Verify that the network devices and interfaces are properly configured on the server.	187
3. Ensure that the ClusterPulse process and the service monitor agent (monitor_agent) are running on the server.	187
A Virtual Host Is Inaccessible	187
HP Clustered File System Exits Immediately	188
Troubleshoot Monitor Problems	188
Monitor Status	188
“Down” Status	188
“Undefined” Status	189
“SYSTEM ERROR” Status	189
“Unknown” Status	189
“Event” Status	189
Clear an Error	190
Monitor Activity	191
“Activity Unknown” Status	192
“Transitioning” Activity	192
HP Clustered File System Network Port Numbers	192
External Network Port Numbers	192
Internal Network Port Numbers	193
A	194
Management Console Icons	194
HP Clustered File System Entities	194
Monitor Probe Status	195
Management Console Alerts	196
B	197
Error and Event Log Messages	197
Management Console Alert Messages	197
ClusterPulse Messages	205
PSFS Filesystem Messages	209
Distributed Lock Manager Messages	209
SANPulse Error Messages	209
SCL Messages	210
Network Interface Messages	210
A Network Interface Is Down or Unavailable	210
Network Interface Requirements Are Not Met	211
IPv-4	211
Port 8940	212
A	213
B	213
C	213
D	213
E	214
F	214
G	215
H	215
L	215
M	215
N	215
O	216
P	216
R	216
S	216
T	217
V	217