지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault 13.0.1 - Installation Guide

Introduction Deploying NetVault Reviewing pre-installation requirements Installing NetVault Reviewing post-installation requirements Upgrading NetVault Licensing NetVault Removing NetVault Troubleshooting

Linux

On Linux OS, verify that the following shared C libraries are available on the server and client systems:

•
libc.so.6
•
libdl.so.2

These libraries provide the standard library functions, including the “system calls” functions.

On systems that do not have these packages, NetVault does not start after installation. In this scenario, run the following command from the NetVault installation directory (/usr/netvault/, by default) to obtain a list of NetVault dependencies and to determine any missing ones.

find ./|grep -v -E "pgAdmin3|stackbuilder|postgresql|lib/libssl|replaced/"|xargs file|egrep 'shared object|executable'|cut -d: -f1|xargs ldd 2>/dev/null|egrep -v '^\.'|perl -pe 's/ *\(.*$//'|sort -u|grep "not found"|grep -v -E "PIC"

The missing dependencies are reported as “Not Found.”

The required files are available as RPM packages. You can install them using the RPM utility. For more information, see the man page for the rpm command. You can also use the configuration tool YaST (Yet another Setup Tool) to locate and install the packages. Once the tool finds the package containing the required file, select the Install command from the Package menu to install the file. For more information about YaST, see the user’s guide for this tool.

RHEL 5.x

Create the following symbolic links:

•
NetVault Server (Hybrid and Pure x86-64):
•
# ln -s /usr/netvault/dynlib/oca-libs/lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.1.0.0
•
NetVault Client (Hybrid x86-32):
•
# ln -s /lib/libssl.so.0.9.7a /lib/libssl.so.0.9.7
•
# ln -s /lib/libcrypto.so.0.9.7a /lib/libcrypto.so.0.9.7
•
NetVault Client (Hybrid x86-64):
•
# ln -s /lib/libssl.so.0.9.7a /lib/libssl.so.0.9.7
•
# ln -s /lib/libcrypto.so.0.9.7a /lib/libcrypto.so.0.9.7
•
# ln -s /lib64/libssl.so.0.9.7a /lib64/libssl.so.0.9.7
•
# ln -s /lib64/libcrypto.so.0.9.7a /lib64/libcrypto.so.0.9.7
•
# ln -s /usr/netvault/dynlib/oca-libs/lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.1.0.0
•
NetVault Client (Pure x86-64):
•
# ln -s /lib64/libssl.so.0.9.7a /lib64/libssl.so.0.9.7
•
# ln -s /lib64/libcrypto.so.0.9.7a /lib64/libcrypto.so.0.9.7
•
# ln -s /usr/netvault/dynlib/oca-libs/lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.1.0.0

Solaris 10 (SPARC and x86-64)

On Solaris 10, you must configure or use the sgen driver utility to add the client-attached library devices to the NetVault Server.

 
* 
NOTE: These steps are not required if the Solaris 10 client does not control a device.
To configure the sgen driver on Solaris 10 Clients:
1
Log on to the machine to which the device is directly attached, and start a terminal session. To verify that the OS recognizes the device, type:
cfgadm -al
cfgadm -al -o show_FCP_dev XX:WWN
cfgadm -o force_update -c unconfigure/configure XX or XX:WWN or XX:WWN:LUN
2
Navigate to the following directory:
/kernel/drv/
3
Open the file sgen.conf for editing. Verify that the sgen driver is configured to attach to the target device. The “sgen” line of this file should look similar to the following:
name="sgen" parent="fp" target=0 lun=0;
Note the following:
•
Fiber Channel devices must be bound with “WWN” entries. Therefore, the “sgen” line should look something like the following example:
name="sgen" parent="fp" target=0 lun=0
fc-port-wwn="1000000cc4c8m0";
•
Editing the sgen.conf file may require that you reboot the target system.
4
Validate that the sgen driver has successfully created the necessary device files by:
•
Step 1: Checking to ensure that the “/devices” directory exists:
/devices/pci@7c,0/pci1022,7458@2/pci1077,1401/fp@0, 0/sgen@w1000000cc4c8m0
•
Step 2: Checking to ensure that the “/dev/scsi/changer” directory contains the appropriate files and these files have been properly associated to the target device:
/dev/scsi/changer/c2t1000000cc4c8m0d0
5
Create a symbolic link in the /dev directory for the NetVault device file associated with the hardware path used in the /dev/scsi/changer directory:
ln -s /devices/pci@7c,0/pci1022,7458@2/pci1077, 1401/fp@0,0/sgen@w1000000cc4c8m0 /dev/nv0
6
Validate that the symbolic link was successfully created, and that it has the correct permissions, by issuing the following command from the prompt:
/dev/nv0 -> pci@7c,0/pci1022,7458@2/pci1077,1401/fp@0, 0/sgen@w1000000cc4c8m0,0:changer

Solaris 11 (SPARC and x86-64)

On Solaris 11, the OS does not correctly update the machine configuration to attach the library arm to the sgen driver after NetVault updates the sgen.conf file. You can use the following procedure to update the machine configuration.

 
* 
NOTE: The exact steps may vary slightly depending on your machine settings.

For more information, see the Oracle Solaris Administration Guide.

To correctly update the machine configuration:
1
Log on to the Solaris machine as root, and start a terminal session. Verify that the device is present:
cfgadm -al
Verify that the driver aliases are okay.
2
Create a copy of the driver_aliases file. Remove the sgen driver and install it again:
 
* 
NOTE: : You may have to copy /kernel/drv/sgen.conf to /etc/drivers/drv.
cd /etc
cp driver_aliases driver_aliases.BKP
rem_drv sgen
add_drv -m '* 0666 bin bin' -i ‘”scsiclass,08” “scsa,0.8.bmpt”’ sgen
3
Verify that the driver is configured:
cd /etc
grep sgen driver_aliases
If the output of the grep command shows that the aliases “scsiclass,08” and “scsa,0.8.bmpt” are assigned to the sgen driver, the driver is properly configured.
sgen "scsiclass,08"
sgen "scsa,0.8.bmpt"
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택