HP ProLiant 4500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 67

Connecting to Shared Resources, Table 2-3, Comparison of Net Use Command Syntax

Get HP ProLiant 4500 PDF manuals and user guides View all HP ProLiant 4500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 67 highlights

2-36 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Connecting to Shared Resources In the traditional, command-driven connection to a shared resource, the user needs to know the server name and the share name. In a clustered environment, the command is changed to reflect the cluster network name and file share that were configured as part of the failover group for that shared directory. Compare the command syntax in Table 2-3 for connecting to a shared resource on a stand-alone server versus a clustered server. Table 2-3 Comparison of Net Use Command Syntax Server Environment Stand-alone server Cluster node Command Syntax Net use J:\\servername\sharename Net use J:\\networkname\fileshare Change client login scripts and profiles so that users connect to resources using the cluster network name and file share. Client/Server Applications Reconfiguration of client applications in a client/server environment may also be required. Some applications, such as many of the popular databases, require the client to specify the IP address of the server that holds the database they want to connect to. The IP addresses may be held in a special configuration program or in a text file. Any references to the server's actual IP addresses must be changed to reflect the new IP Address Resource that has been configured for that application's cluster group. Some databases allow you to specify the IP address of a backup server, which the client database software attempts to use in case the database is not accessible using the first IP address. The backup IP address scheme can be used in a nonclustered environment to assist clients if the primary server fails. This is no longer necessary when using MSCS.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
2-36
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
Connecting to Shared Resources
In the traditional, command-driven connection to a shared resource, the user
needs to know the server name and the share name
.
In a clustered
environment, the command is changed to reflect the cluster network name and
file share that were configured as part of the failover group for that shared
directory.
Compare the command syntax in Table 2-3 for connecting to a shared resource
on a stand-alone server versus a clustered server.
Table 2-3
Comparison of Net Use Command Syntax
Server Environment
Command Syntax
Stand-alone server
Net use J:\\servername\sharename
Cluster node
Net use J:\\networkname\fileshare
Change client login scripts and profiles so that users connect to resources
using the cluster network name and file share.
Client/Server Applications
Reconfiguration of client applications in a client/server environment may also
be required. Some applications, such as many of the popular databases, require
the client to specify the IP address of the server that holds the database they
want to connect to. The IP addresses may be held in a special configuration
program or in a text file. Any references to the server’s actual IP addresses
must be changed to reflect the new IP Address Resource that has been
configured for that application’s cluster group.
Some databases allow you to specify the IP address of a backup server, which
the client database software attempts to use in case the database is not
accessible using the first IP address. The backup IP address scheme can be
used in a nonclustered environment to assist clients if the primary server fails.
This is no longer necessary when using MSCS.