
12-4 SAN Installation and Troubleshooting Guide
NOTE: The NetWare configuration specified in Figure 2-2 requires that a LUN is bound
on an SP in order for the Data Managed Node for Netware to communicate with the
SP. If there are no LUNs bound, then a Windows NT or Windows 2000 system
attached directly to the SP is required to configure and initialize a LUN. Following this,
the Windows NT or Windows 2000 server can be removed and management can
occur through the NetWare server.
,QVWDOOLQJDQG&RQILJXULQJ'DWD0DQDJHG1RGHIRU
1HW:DUH
To install and configure the Data Managed Node for NetWare, perform the following
steps.
NOTE: Because long filename support may not have been enabled on the NetWare
server, the agent installation uses the 8.3 file format.
1. If a previous version of Managed Node is running, it must be stopped and unin-
stalled using the uninstall commands in the next section.
2. On a client system running Microsoft Windows or DOS, insert the Managed
Node installation CD in the CD-ROM drive.
3. On the client system, map drive letter H to the sys volume on your NetWare
server.
4. At the DOS prompt of the client system, change the directory to the drive con-
taining the installation CD and run the install script by typing LQVWDOO GULYH!,
where drive is the remote drive corresponding to the sys volume on the NetWare
server.
For example,LQVWDOO+ would create h:\dell\om with the appropriate agent
and command line interface (CLI) directories under it.
5. Edit the sys:\etc\hosts file by adding the Internet Protocol (IP) address of the
server, followed by localhost.
For example, type
ORFDOKRVW.
6. If you do not wish to maintain individual host files, edit the sys:\resolve.cfg file
by adding the IP addresses and names of your domain name system (DNS)
servers.
127,&(7KHDJHQWZLOOQRWVWDUWVXFFHVVIXOO\LIWKH'16VHUYHULVGRZQ
DQGVWDUWXSRIWKHDJHQWFRXOGFDXVHXQSUHGLFWDEOHVHUYHUEHKDYLRU