Novell Server Consolidation and Migration Toolkit 1.1, Руководство администратора, Страница: 82 / 126

82 Novell Server Consolidation and Migration Toolkit Administration Guide
no
vd
ocx
(E
NU)
9 Decem
ber
200
5
Volume Contents Do Not Display
Problem: No data appears in the Volume object after dropping a container into a volume
that has not been opened.
Action: Map a drive to the volume from the workstation.
“SMDR Not Communicating” or “Error Opening Connection to SMDR” Errors
Possible Cause: The Storage Management Data Requester (SMDR) and Target Service Agent
(TSA) are not loaded on either the source or the destination server, or the
sys:etc/hosts
file does not contain the server IP addresses, or Service
Location Protocol (SLP) is not properly configured.
Action: Check to see if smdr.nlm is running on a NetWare
®
server by entering
m
smdr
at the server console.
To check if the SMDR module is running on an OES Linux server, enter
pgrep smdr
at the shell prompt.
If SMDR is not loaded on the source or destination server, manually load it.
On a NetWare server, enter
load smdr
. On an OES Linux server, enter
/
etc/init.d/novell-smdrd start
.
Action: Check to see if tsafs.nlm is running on a NetWare server by entering
m tsa*
at the server console.
To check if the TSAFS module is running on an OES Linux server, enter
/
opt/novell sms/bin/smsconfig -t
at the shell prompt.
If TSAFS is not loaded on the source or destination server, manually load it.
On a NetWare server, enter
load tsafs
. On an OES Linux server, enter
/
opt/novell/sms/bin/smsconfig -l tsafs
.
Action: On a small network with three or fewer servers, you do not need to configure
SLP. Instead, edit the sys:etc/hosts file on the source server to contain the IP
address and DNS name of the destination server, and vice versa on the
destination server.
After editing the sys:etc/hosts files, you might need to reload
smdr.nlm
and
tsafs.nlm on your NetWare servers.
Action: Enter
display slp services smdr.novell//(svcname-
ws==source_ server_name
) (replace source_server_name with the
name of your source server) at the destination server console.
If it appears there is a problem with SLP, go to Novell’s Knowledgebase (http:/
/support.novell.com/search/kb_index.jsp) and search for SLP-related
configuration information.
“Specified TSA Does Not Exist” Errors When Copying Data from NetWare to OES
Linux
Possible Cause: The SMDR daemon needs to be restarted on the OES Linux server.
Action: Enter
rcnovell-smdrd restart
at the Linux server’s shell prompt.