HP StorageWorks 1606 DCFM Installation, Migration, and Transition Guide - Supp - Page 59

Enterprise trial pre-installation requirements on UNIX systems

Page 59 highlights

Enterprise trial pre-installation requirements on UNIX systems 1 17. Select the Start DCFM Client check box on the Start Server screen. 18. Click Finish. After all of the selected services are started, the Log In dialog box displays. 19. Enter your user name and password. The defaults are Administrator and password, respectively. 20. Click Login. 21. Click OK on the Login Banner. Enterprise trial pre-installation requirements on UNIX systems • To avoid errors, close all instances of the application before beginning the installation or uninstallation procedures. If you still receive error messages after closing the application, enter the following commands: #ps -ef | grep -i "" to list the process IDs #kill -9 "" where is any Management application process • Check for and install the latest Java patches for your operating system. DCFM requires JRE 1.6.0. For the Solaris web site listing patch information, go to http://java.sun.com/javase/downloads/index.jsp. • (Solaris only) To use IPv6 on a server that is IPv4- and IPv6-enabled, complete the following steps. a. Open a command window. b. Type ifconfig inet6 plumb up and press Enter. c. Restart the Management server and client, if running. If the IPv6 address is not configured properly, the client will show a "Server Not Available at port 51511" message even though the server started successfully. • Make sure that an X Server is available for display and is configured to permit X Client applications to display from the host on which they are installing the EFCM Server (typically, this simply requires that the system console be present and running with a logged in user on the X Server-based desktop session, such as KDE, GNOME, and so on). If this is a headless unit with no console, refer to "Headless Pre-Installation Requirements" on page 23. • Make sure that the DISPLAY environment variable is correctly defined in the shell with a valid value (for example, to display to the local console, export DISPLAY=:0.0, or to display to a remote system that has an X Server running, export DISPLAY=:0.0). You may also need to consider a firewall that might block the display to the X Server which listens by default on TCP port 6000 on the remote host. To display to a remote system you need to permit the remote display of the X Server by running command xhost +IP, where IP is the IP address of the DCFM server host from the X-based desktop of the remote system. • Make sure you test the DISPLAY definition by running the command xterm from the same shell from which you run install.bin. A new X terminal window to the destination X Server display should open. DCFM Installation, Migration, and Transition Guide 43 53-1001360-01

  • 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
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254

DCFM Installation, Migration, and Transition Guide
43
53-1001360-01
Enterprise trial pre-installation requirements on UNIX systems
1
17.
Select the
Start DCFM Client
check box on the
Start Server
screen.
18. Click
Finish
.
After all of the selected services are started, the
Log In
dialog box displays.
19.
Enter your user name and password.
The defaults are Administrator and password, respectively.
20. Click
Login
.
21. Click
OK
on the Login Banner.
Enterprise trial pre-installation requirements on UNIX systems
To avoid errors, close all instances of the application before beginning the installation or
uninstallation procedures.
If you still receive error messages after closing the application, enter the following commands:
#ps -ef | grep -i “”
to list the process IDs
#kill -9 “
<Process_ID>
where
<Process_ID>
is any Management application process
Check for and install the latest Java patches for your operating system. DCFM requires
JRE 1.6.0. For the Solaris web site listing patch information, go to
(Solaris only) To use IPv6 on a server that is IPv4- and IPv6-enabled, complete the following
steps.
a.
Open a command window.
b.
Type
ifconfig
<Interface_Name>
inet6 plumb up
and press
Enter
.
c.
Restart the Management server and client, if running.
If the IPv6 address is not configured properly, the client will show a "Server Not Available at
port 51511" message even though the server started successfully.
Make sure that an X Server is available for display and is configured to permit X Client
applications to display from the host on which they are installing the EFCM Server (typically,
this simply requires that the system console be present and running with a logged in user on
the X Server-based desktop session, such as KDE, GNOME, and so on).
If this is a headless unit with no console, refer to “Headless Pre-Installation Requirements” on
page 23.
Make sure that the DISPLAY environment variable is correctly defined in the shell with a valid
value (for example, to display to the local console,
export DISPLAY=:0.0
, or to display to a
remote system that has an X Server running,
export DISPLAY=
<Remote_IP_address>
:0.0
).
You may also need to consider a firewall that might block the display to the X Server which
listens by default on TCP port 6000 on the remote host.
To display to a remote system you need to permit the remote display of the X Server by running
command
xhost +IP
, where IP is the IP address of the DCFM server host from the X-based
desktop of the remote system.
Make sure you test the DISPLAY definition by running the command
xterm
from the same shell
from which you run
install.bin
. A new X terminal window to the destination X Server display
should open.