Beruflich Dokumente
Kultur Dokumente
V100R001C01SPC600
Issue
06
Date
2013-01-24
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website:
http://enterprise.huawei.com
Issue 06 (2013-01-24)
Contents
Contents
1 Installing the eSpace Local Maintenance Terminal ............................................................... 1
1.1 Installing the LMT ........................................................................................................................................... 1
1.1.1 Installation Preparations .......................................................................................................................... 1
1.1.2 Installing the LMT Server ....................................................................................................................... 8
1.1.3 Installing the LMT Client...................................................................................................................... 13
1.2 Uninstalling the LMT ..................................................................................................................................... 14
Issue 06 (2013-01-24)
ii
Issue 06 (2013-01-24)
Requirement
Operating
System
Component
Requirement
You are advised to install the server on a host running the Windows
Server 2008 R2 or Linux SuSE 11 64-bit SP1 operating system.
Client
CPU
Memory
2 GB or more
Hard disk
80 GB or more
Operating
System
Windows XP or Windows 7
CPU
Memory
2 GB or more
Hard disk
80 GB or more
Display
Others
Prerequisites
You have learned about the device version. To obtain the device version, connect the device to
the LMT through the serial port (Logging In to the eSpace U1910 Using the CLI) and run the
show version command.
Client: LMTClient.rar
Server
Before installing the LMT, refer to Table 1-2 to understand the installation package structure.
Table 1-2 Structure of the installation package
Home Directory
Subdirectory
Description
Server
Server suse
Issue 06 (2013-01-24)
Home Directory
Subdirectory
Description
system.
Currently, only the 64-bit SuSE operating
system is supported.
Server win
Client
2.
The file signature verification tool can be executed only in Windows Vista and Windows Server
2008 or higher.
The libeay32.dll file delivered with the file signature verification tool is a file required to run the
tool.
Double-click FileIntegrityVerify.exe.
The File Integrity Verify Tool window is displayed.
3.
Select the path for storing the LMT installation package, and click Verify.
If "Success" is displayed for all items, the integrity of the installation package is
successfully verified.
If "Failure" or "No Sign Data" is displayed for any item, the verification failed.
Obtain the LMT installation package of the correct version again.
If the file to be checked is not in the Windows operating system, copy the file to the Windows
operating system before using the tool to check the integrity of the file.
Issue 06 (2013-01-24)
Windows operating system: You are advised to deploy the LMT server and the LMTclient on the
same PC.
SuSE operating system: You are advised to deploy the LMT server and the LMT client on the same
network segment.
Policy
Example
LMT server
Windows:
192.169.103.187
192.169.103.187
LMT client
SuSE: 192.169.103.92
Context
The LMT client and the LMT server for SuSE do not require installation. Therefore, you only
need to check whether the LMT server is already installed in the Windows operating system.
Procedure
Step 1 Choose Start > All programs to check whether the LMTServer items exist.
Step 2 Choose Start > All Programs > LMTServer to start the LMT server.
Step 3 View the LMT server title bar
.
If the version displayed is different from the version that needs to be installed, uninstall the
software. For details, see 1.2 Uninstalling the LMT.
----End
Prerequisites
The installation package LMTServer_suse11.zip has been obtained and stored in
D:\Server_suse on the local PC.
Issue 06 (2013-01-24)
Procedure
Step 1 Log in to the server as the root user.
Step 2 Run the mkdir Server_suse command to create a folder.
Run the ls command. The following information shown in Figure 1-1 is displayed.
Figure 1-1 Creating the Server_suse folder
1.
2.
Run the vi /etc/vsftpd.conf command to set the following parameters in the vsftpd
configuration file:
Run the service vsftpd status command to check the vsftpd operating status.
linux-w098:/ # service vsftpd status
Checking for service vsftpd
running
done
done
If unused is displayed, run the service vsftpd start command to start the vsftpd
service.
linux-w098:/ # service vsftpd start
Starting vsftpd
done
Step 4 On the local PC where the installation package is stored, upload the installation package to the
Server_suse folder on the server in binary mode.
To use FTP to upload the installation package, proceed as follows:
1.
2.
In the command-line interface that is displayed, run the ftp 192.169.103.92 command.
The following information is displayed.
C:\Documents and Settings\Administrator>ftp 192.169.103.92 //192.169.103.92 is
the server IP address.
Issue 06 (2013-01-24)
Connected to 192.169.103.96.
220 (vsFTPd 2.0.7)
User (192.169.103.92:(none)):
3.
If the root user cannot log in to the server, modify the permissions for the root user on the server.
Run the vi /etc/ftpusers command, and delete root in the file or prefix it with a number sign (#).
4.
Run the bin command to switch to the binary mode for uploading the installation
package.
ftp> bin
200 Switching to Binary mode.
5.
Run the cd /Server_suse command to access the destination path for uploading the
installation package:
ftp> cd /Server_suse
250 Directory successfully changed.
6.
Run the lcd d:\Server_suse command to access the source installation package:
ftp> lcd d:\Server_suse
Local directory now D:\Server_suse.
7.
8.
Run the bye command to exit the FTP service after the upload is complete.
----End
Context
When you install LMT, the following ports need to be used:
Issue 06 (2013-01-24)
If port 8877 is used by other applications, another idle port can be chosen.
TFTP port: 69
Before you install the LMT, disable the firewall and ensure that the preceding ports are not
used.
The following describes how to check whether the port is used and how to handle the used
situation in Windows and Linux operating systems.
Procedure
1.
2.
In the command-line interface that is displayed, run the netstat -aon | findstr port
command to display the port information, as shown in Figure 1-2. If the port is used,
proceed to Step 3. If the port is unused, skip Step 3.
3.
If the port is used, run the tasklist | findstr Process ID (PID) command to display the
information about the software that is using the port, as shown in Figure 1-2.
If the information about the server port, Telnet port or TFTP port is not displayed, it indicates that the
port is not used.
4.
Log in to the server as the root user and run the lsof -i: PortID command.
If the port information is not displayed, it indicates that the port is not occupied.
If the information similar to the following is displayed, disable the related software.
For example, if the port 8877 is used by the LMTServer as shown in Figure 1-3,
disable the LMTServer to release the port.
----End
Issue 06 (2013-01-24)
Prerequisites
You have obtained the LMT installation package for Windows at
http://enterprise.huawei.com.
There is at least 3 GB of available disk space.
Procedure
Step 1 Double-click LMTServerSetUp.exe in the LMT server folder.
The dialog box for selecting the installation language is displayed. In the dialog box, select
English.
Step 2 Click OK.
The Welcome to the LMTServer Setup Wizard dialog box is displayed, as shown in Figure
1-4.
Figure 1-4 Welcome to the LMTServer Setup Wizard dialog box
Issue 06 (2013-01-24)
Step 4 You are advised to use the default installation path C:\Program Files\LMTServer. You can
click Browse... to choose another installation path, and click Next.
The Select Additional Tasks dialog box is displayed, as shown in Figure 1-6.
Issue 06 (2013-01-24)
Step 5 No shortcut is created by default. You can select any shortcuts as required, and click Next.
The Ready to Install dialog box is displayed, as shown in Figure 1-7.
Figure 1-7 Ready to Install dialog box
Issue 06 (2013-01-24)
10
Step 6 Verify that the installation path is correct, and click Install.
A dialog box shown in Figure 1-8 is displayed after the installation is complete.
Figure 1-8 Completing the LMTServer Setup Wizard dialog box
Issue 06 (2013-01-24)
11
Before using the port, verify that the port is not used. For details, see Checking Whether the Port Is
Used.
1.
2.
Use the Notepad to open the configuration.properties file, and locate the following
information: channel.client.bin.port = 8877.
3.
Change 8877 to the customized port in the preceding information, and save the settings.
4.
----End
Prerequisites
You have obtained the LMT installation package for SuSE at http://enterprise.huawei.com.
There is at least 3 GB of available disk space.
Procedure
Step 1 Log in to the server as the root user.
The topic assumes that the installation package is stored in Server_suse, for example,
Server_suse/LMTServer_suse11.zip.
Step 2 Run the cd /Server_suse command to access the Server_suse folder.
Step 3 Run the unzip LMTServer_suse11.zip command to decompress the installation package.
After decompression, a folder named LMTServer_suse11 is generated, where the
LMTServer is stored. The installation is complete.
If the LMTServer_suse11 folder already exists before decompression, run the rm -rf
LMTServer_suse11 command to delete the folder before running the unzip
LMTServer_suse11.zip command.
----End
Follow-up Procedure
After the installation is complete, perform the following steps to start the LMT server.
1.
Run the chmod -R 777 LMTServer_suse11 command to change the permissions of the
LMTServer_suse11 folder for the root user.
Run the ls -al command to view the changed permissions. If drwxrwxrwx is displayed,
the change is successful, as shown in Figure 1-10.
Issue 06 (2013-01-24)
12
2.
3.
Installation Steps
This topic describes the installation steps of the LMT client.
Context
The LMT client does not require installation. Double-click LMTClient.exe in the
LMTClient folder to start the LMT client.
The default server port is 8877.
If a customized port is set when installing the LMT server, modify the connection port for the LMT
client. For details, see Procedure.
Procedure
Step 1 Open the LMTClient\Config folder.
Step 2 Use the Notepad to open the loginConfig.cfg file.
Step 3 Change the port in bold in the following information to the customized server port.
{'pwd': '', 'user_name': u'admin', 'port': u'8877', 'server_ip': u'192.169.103.187'}
Step 4 Save the settings and double-click LMTClient.exe to start the LMT client.
----End
Issue 06 (2013-01-24)
13
Installation Verification
If the LMT client can connect to the LMT server, the LMT installation is successful.
Result
If the workspace page shown in Figure 1-12 is displayed after the LMT client starts, the LMT
client connects to the server successfully.
Figure 1-12 LMT workspace page
The default user name and password for login are admin and huawei123.
Context
The LMT client and the LMT server for SuSE do not require installation. To uninstall the
software, you only need to delete software directories.
To uninstall the LMT server in the Windows operating system, proceed as follows:
Procedure
Step 1 Choose Start > All programs > LMTServer > Uninstall LMTServer. The Uninstall dialog
box is displayed.
Step 2 Click Yes to start the uninstallation. The LMTServer Uninstall dialog box is displayed.
Step 3 Click Yes to confirm the uninstallation.
Step 4 After the uninstallation is complete, the message is displayed, indicating that the LMT server
is uninstalled successfully.
----End
Issue 06 (2013-01-24)
14
Issue 06 (2013-01-24)
15
Procedure
Step 1 Choose Start > Computer.
Step 2 Right-click the disk where the NFS server is to be installed (for example, disk E). Choose
Properties from the shortcut menu that is displayed.
Step 3 In the Properties dialog box that is displayed, check the disk's file system, as shown in Figure
2-1.
To ensure that Universal Access Platform can normally record and play voices, New
Technology File System (NTFS) must be used. If the file system is not NTFS, reinstall the
operating system.
Figure 2-1 Properties dialog box
----End
Procedure
Step 1 Log in to the file server as the administrator user.
Step 2 Choose Start > Administrative Tools > Server Manager.
The Server Manager window is displayed.
Step 3 Add the Services for Network File System Tools feature.
1.
In the Server Manager window, select Features from the navigation tree.
Details about features are displayed in the right area, as shown in Figure 2-2.
Issue 06 (2013-01-24)
16
2.
3.
Choose Remote Server Administration Tools > Role Administration Tools > File
Services Tools, and select the Services for Network File System Tools check box, as
shown in Figure 2-3.
4.
Click Next.
The Confirm Installation Selections dialog box is displayed.
5.
Issue 06 (2013-01-24)
17
6.
Click Close.
Issue 06 (2013-01-24)
18
If File Services is not displayed in the Roles Summary area, File Services is not
installed. Go to Step 5.
If File Services is displayed in the Roles Summary area, File Services is installed. Go
to Step 6.
Step 5 Install File Services and Services for Network File System.
1.
2.
Click Next.
The Select Server Roles dialog box is displayed.
3.
Issue 06 (2013-01-24)
19
4.
Click Next.
The File Services dialog box is displayed.
5.
Click Next.
The Select Role Services dialog box is displayed.
6.
Issue 06 (2013-01-24)
In the Role Services list box, select the File Server and Services for Network File
System check boxes, as shown in Figure 2-7.
20
7.
Click Next.
The Confirm Installation Selections dialog box is displayed.
8.
Issue 06 (2013-01-24)
21
9.
Click Close.
2.
Issue 06 (2013-01-24)
In the Role Services list box, select the Services for Network File System check box,
as shown in Figure 2-9.
22
3.
Click Next.
The Confirm Installation Selections dialog box is displayed.
4.
Issue 06 (2013-01-24)
23
5.
Click Close.
----End
Procedure
Step 1 Choose Start > Administrative Tools > Server Manager.
The Server Manager window is displayed.
Step 2 In the Server Manager window, select Roles from the navigation tree.
Details about roles are displayed in the right area, as shown in Figure 2-11.
Issue 06 (2013-01-24)
24
Issue 06 (2013-01-24)
25
Step 5 Select the Active Directory Lightweight Directory Services check box.
The message "Add features required for Active Directory Lightweight Directory Services?" is
displayed, as shown in Figure 2-13.
Figure 2-13 Adding a feature
Step 6 Click Add Required Features. The Select Server Roles dialog box is displayed.
In the Select Server Roles dialog box, the Active Directory Lightweight Directory Services
check box is selected.
Step 7 Click Next.
The Active Directory Lightweight Directory Services dialog box is displayed.
Step 8 Click Next.
Issue 06 (2013-01-24)
26
----End
Prerequisites
The name of the computer where the file server is installed has been obtained. To obtain the
computer name, proceed as follows: Right-click Computer on the desktop, or choose Start >
Computer and right-click in the blank area. Choose Properties from the shortcut menu.
Issue 06 (2013-01-24)
27
Click the Computer Name tab in the System Properties dialog box and find the computer
name. Assume that the computer name is Win-DRTVNVDH67M.
Procedure
Step 1 Choose Start > Administrative Tools > Active Directory Lightweight Directory Services
Setup Wizard.
The Welcome to the Active Directory Lightweight Directory Services Setup Wizard
dialog box is displayed.
Step 2 Click Next.
The Setup Options dialog box is displayed, as shown in Figure 2-15.
Figure 2-15 Setup Options dialog box
Issue 06 (2013-01-24)
28
Step 4 Enter the instance name (for example, nfsinstance) in the Instance name text box, and click
Next.
The Ports dialog box is displayed, as shown in Figure 2-17.
Issue 06 (2013-01-24)
29
Step 5 Retain the default values for LDAP port number and SSL port number. Click Next.
The Application Directory Partition dialog box is displayed, as shown in Figure 2-18.
Issue 06 (2013-01-24)
30
Record the setting of LDAP port number, which will be used for subsequent configuration tasks (for
example, Extending the AD LDS Schema).
2.
Issue 06 (2013-01-24)
31
Step 8 Set Data files and Data recovery files to a folder where you want to store the AD
LDS-related files, and click Next.
The Service Account Selection dialog box is displayed, as shown in Figure 2-20.
Issue 06 (2013-01-24)
32
Issue 06 (2013-01-24)
33
Issue 06 (2013-01-24)
34
Step 12 Select the MS-InetOrgPerson.LDF and MS-User.LDF check boxes, and click Next.
The Ready to Install dialog box is displayed.
Step 13 Click Next to install the AD LDS instance.
When the installation is complete, the Installing AD LDS dialog box is displayed.
Step 14 Click Finish.
Step 15 Verify that the new AD LDS instance nfsinstance exists.
1.
2.
Issue 06 (2013-01-24)
35
If the AD LDS instance nfsinstance exists, the installation is successful. If the instance
does not exist, reinstall the AD LDS instance.
3.
Click
On the displayed Uninstall or change a program page, double-click the AD LDS instance to be
deleted and perform operations as prompted.
----End
Procedure
Step 1 Click Start, right-click Command Prompt, and choose Run as administrator from the
shortcut menu.
The Administrator: Command Prompt window is displayed.
Step 2 Run the following commands to import the MS-AdamSchemaW2K8.LDF file:
cd C:\WINDOWS\ADAM
ldifde -i -u -f MS-AdamSchemaW2K8.LDF -s localhost:389 -c "CN=Configuration,DC=X"
#configurationNamingContext
Issue 06 (2013-01-24)
36
In this example, the AD LDS instance uses the default LDAP port number 389. This port number is set
in Figure 2-17 in Installing AD LDS Instances. Except port number 389, you are not allowed to modify
"CN=Configuration,DC=X" or #configurationNamingContext in the command.
Procedure
Step 1 Choose Start > Administrative Tools > ADSI Edit.
The ADSI Edit window is displayed, as shown in Figure 2-26.
Figure 2-26 ADSI Edit window
Issue 06 (2013-01-24)
37
Step 2 In the navigation tree, right-click ADSI Edit, and choose Connect to from the shortcut menu.
The Connection Settings dialog box is displayed.
1.
In the Connection Point area, click Select a well known Naming Context, and select
Configuration from the drop-down list box.
2.
In the Computer area, click Select or type a domain or server: (Server | Domain
[:port]), and enter localhost:389 in the text box, as shown in Figure 2-27.
In this example, the AD LDS instance uses the default LDAP port number 389. This port number is set
in Figure 2-17 in Installing AD LDS Instances.
3.
Step 3 In the navigation tree, choose Configuration > CN=Configuration > CN=Sites >
CN=Default-First-Site-Name > CN=Servers > CN=Computer name $ AD LDS instance
name > CN=NTDS Settings, as shown in Figure 2-28.
Issue 06 (2013-01-24)
38
Step 4 Right-click CN=NTDS Settings, and choose Properties from the shortcut menu.
The CN=NTDS Settings Properties dialog box is displayed, as shown in Figure 2-29.
Figure 2-29 CN=NTDS Settings Properties dialog box
Issue 06 (2013-01-24)
39
----End
Procedure
Step 1 Click Start, right-click Command Prompt, and choose Run as administrator from the
shortcut menu.
The Administrator: Command Prompt window is displayed.
Step 2 Run the following commands to enable the Active Directory plug-in schmmgmt.dll:
cd C:\WINDOWS\ADAM
regsvr32 schmmgmt.dll
displayed. Click OK.
exit
Issue 06 (2013-01-24)
40
Step 7 Click OK. The Console1 window is displayed, as shown in Figure 2-33.
Issue 06 (2013-01-24)
41
Step 8 Right-click Active Directory Schema, and choose Change Active Directory Domain
Controller from the shortcut menu.
The Change Directory Server dialog box is displayed, as shown in Figure 2-34.
Figure 2-34 Change Directory Server dialog box
Step 9 In the Change to area, modify <Type a Directory Server name[:port] here> to the server
name and port number, such as localhost:389.
Step 10 Select localhost:389, and click OK.
In this example, the AD LDS instance uses the default LDAP port number 389. This port
number is set in Figure 2-17 in Installing AD LDS Instances.
Step 11 (Optional) Perform the following operations if Active Directory Schema fails to be expanded
in the Console1 window:
1.
Issue 06 (2013-01-24)
42
2.
Set File Name to the name of the management console file, such as nfsmmc, and click
Save.
3.
Click
4.
Choose Start > Run, enter mmc in Open, and click OK.
5.
6.
Step 12 Add the gidNumber and uidNumber schema objects to the user class.
1.
Choose Active Directory Schema > Classes, right-click user, and choose Properties
from the shortcut menu.
The User Properties dialog box is displayed, as shown in Figure 2-37.
Issue 06 (2013-01-24)
43
2.
Click the Attributes tab, and click Add on the Attributes tab page.
The Select Schema Object dialog box is displayed, as shown in Figure 2-38.
Issue 06 (2013-01-24)
44
3.
4.
5.
6.
Issue 06 (2013-01-24)
Click Continue running and ignore errors with this snap-in for the rest of the
session., and click OK.
45
7.
Verify that the gidNumber and uidNumber schema objects are added to the user class
successfully.
Before viewing the result, you are advised to click or drag the scroll bars in the navigation
tree and the right pane. If you do not do this, the console window may exit abnormally.
When you click user in the navigation tree, gidNumber and uidNumber are displayed in the
right pane, as shown in Figure 2-40, which indicates that the schema objects are added
successfully. If they do not exist, add them again.
Figure 2-40 Verifying the result
Choose Active Directory Schema > Classes, right-click group, and choose Properties
from the shortcut menu.
The Group Properties dialog box is displayed, as shown in Figure 2-41.
Issue 06 (2013-01-24)
46
2.
Click the Attributes tab, and click Add on the Attributes tab page.
The Select Schema Object dialog box is displayed, as shown in Figure 2-42.
Issue 06 (2013-01-24)
47
3.
4.
Click OK.
5.
Verify that the gidNumber schema object is added to the group class successfully.
When you click group in the navigation tree, gidNumber is displayed in the right pane,
as shown in Figure 2-43, which indicates that the schema object is added successfully. If
the schema object does not exist, add it again.
48
----End
Step 2 In the navigation tree, right-click ADSI Edit, and choose Connect to from the shortcut menu.
The Connection Settings dialog box is displayed.
1.
In the Connection Point area, click Select a well known Naming Context, and select
Default naming context from the drop-down list box.
2.
In the Computer area, click Select or type a domain or server: (Server | Domain
[:port]), and enter localhost:389 in the text box, as shown in Figure 2-45.
In this example, the AD LDS instance uses the default LDAP port number 389. This port number is set
in Figure 2-17 in Installing AD LDS Instances.
Issue 06 (2013-01-24)
49
3.
Step 3 In the navigation tree, click Default naming context and click
nodes, as shown in Figure 2-46.
to expand lower-level
Issue 06 (2013-01-24)
50
Step 5 In the Select a class list box, select container, and click Next.
The dialog box for setting the attribute value is displayed, as shown in Figure 2-48.
Issue 06 (2013-01-24)
51
Step 6 In the Value text box, enter Users, and click Next.
The value is the name of the container that stores user account mappings.
Step 7 Click Finish.
----End
Issue 06 (2013-01-24)
52
Step 3 In the Create Object dialog box, select user, and click Next.
The dialog box for setting the attribute value is displayed, as shown in Figure 2-50.
Issue 06 (2013-01-24)
53
Step 4 In the Value text box, enter the user name administrator, and click Next.
The user name is not associated with the Windows or UNIX user, and can be a random entry.
Step 5 Click More Attributes, and set uidNumber, gidNumber, sAMAccountName for this user
account.
The uidNumber and gidNumber attributes indicate the user ID (UID) and group ID (GID) of the UNIX
user who is being mapped. The sAMAccountName value must match the name of a local user on the
Windows-based computer that is running Server for NFS. If uidNumber and gidNumber are not
displayed after you click More Attributes, restart the ADSI editor.
1.
Issue 06 (2013-01-24)
In the Select a property to view drop-down list box, select uidNumber. In the
Attribute Values area, set Edit Attribute to 65534, as shown in Figure 2-51.
54
If gidNumber and uidNumber are not displayed in the Select a property to view drop-down list box,
delete the CN=Users container and delete the default naming context that is created. Then refer to
Updating the Active Directory Schema to verify that the gidNumber and uidNumber schema objects
are added.
2.
Click Set.
3.
gidNumber: 65533
sAMAccountName: Administrator
4.
Issue 06 (2013-01-24)
55
Step 3 In the Select a class list box, select group, and click Next.
The dialog box for setting the attribute value is displayed, as shown in Figure 2-53.
Issue 06 (2013-01-24)
56
Step 4 In the Value text box, enter the group object name Administrators, and click Next.
Ensure that the group object name matches the name of the group account for which group account
mapping is desired.
Step 5 Click More Attributes, and set gidNumber and sAMAccountName for the group object
Administrators.
The gidNumber attribute is the GID of the UNIX group that is being mapped. The sAMAccountName
value must match the name of a local group on the Windows-based computer that is running Server for
NFS. If gidNumber and sAMAccountName are not displayed after you click More Attributes, restart
the ADSI editor.
1.
Issue 06 (2013-01-24)
In the Select a property to view drop-down list box, select gidNumber. In the
Attribute Values area, set Edit Attribute to 65533, as shown in Figure 2-54.
57
2.
Click Set.
3.
4.
Procedure
Step 1 Click Start, right-click Command Prompt, and choose Run as administrator from the
shortcut menu.
The Administrator: Command Prompt window is displayed.
Step 2 Run the following commands to grant read permission on AD LDS objects to the everyone
user group:
cd C:\WINDOWS\ADAM
dsacls "\\localhost:389\CN=nfsinstance,DC=Win-DRTVNVDH67M" /G everyone:GR /I:T
Issue 06 (2013-01-24)
58
//Note: (1) nfsinstance: AD LDS instance name. (2) Win-DRTVNVDH67M: computer name. (3)
389: LDAP port number, which is set in Figure 2-17 during the AD LDS instance installation.
For details about the AD LDS instance installation, see Installing AD LDS Instances.
The information shown in Figure 2-55 indicates that read permission is successfully granted.
Figure 2-55 Granting read permission
Procedure
Step 1 Click Start, right-click Command Prompt, and choose Run as administrator from the
shortcut menu.
The Administrator: Command Prompt window is displayed.
Step 2 Run the nfsadmin mapping config adlookup=yes addomain=localhost:389 command to
configure the mapping source.
The configuration result is displayed, as shown in Figure 2-56.
Issue 06 (2013-01-24)
59
If the message "Failed to update the settings." is displayed, install Windows patches and run this
command again. For details on how to install Windows patches, see
http://support.microsoft.com/kb/2222746.
In this example, the AD LDS instance uses the default LDAP port number 389. This port number is set
in Figure 2-17 in Installing AD LDS Instances.
Context
Performing NFS sharing for D:\fileserver on the NFS server is used as an example in this
topic.
Procedure
Step 1 Choose Start > Computer.
The Computer window is displayed.
Step 2 Create a fileserver folder in Local Disk (D:).
Step 3 Right-click fileserver, and choose Properties from the shortcut menu.
The fileserver Properties dialog box is displayed, as shown in Figure 2-57.
Issue 06 (2013-01-24)
60
Step 4 Click the NFS Sharing tab, and click Manage NFS Sharing on the NFS Sharing tab page.
The NFS Advanced Sharing dialog box is displayed.
Step 5 Set NFS sharing parameters and permissions.
1.
2.
Click Permissions.
The NFS Share Permissions dialog box is displayed, as shown in Figure 2-59.
Issue 06 (2013-01-24)
61
a.
b.
c.
3.
Click Apply, and click OK. The fileserver Properties dialog box is displayed.
4.
Click Close.
Step 6 Right-click fileserver, and choose Share with > Specific people from the shortcut menu.
The File Sharing dialog box is displayed, as shown in Figure 2-60.
Figure 2-60 File Sharing dialog box
Step 7 In Choose people to share with, enter Everyone, and click Add.
Step 8 In the list box, click Everyone, and choose Read/Write from the shortcut menu.
Issue 06 (2013-01-24)
62
Procedure
1.
Double-click My Computer.
2.
Select the drive to be checked, right-click the selected drive, and choose Properties from
the shortcut menu.
In the displayed Properties dialog box, check the file type of the drive, as shown
inFigure 2-61.
Issue 06 (2013-01-24)
63
1.
2.
3.
Decompress the package to any path of the local disk. After decompression, passwd and
group files are generated.
To prevent that the passwd and group files from being accidentally deleted, create a new
folder, for example, D:\passwd_group to save the files.
----End
Issue 06 (2013-01-24)
64
Procedure
Step 1 Download Windows Services for UNIX Version 3.5 on the official network of Microsoft to
the local disk, for example, D:\.
Step 2 Double-click Windows Service for UNIX 3.5_en.exe. The dialog box shown in Figure 2-62
is displayed. Click Unzip to extract files.
Figure 2-62 Winzip Self-Extractor-Windows Service for UNIX 3.5_en.exe dialog box
Issue 06 (2013-01-24)
65
The method of selecting the installation item is as follows: click the option and choose Entire feature
(including all subfeatures if any) will be installed on local hard drive from the shortcut menu.
Issue 06 (2013-01-24)
66
The method of unselecting the installation item is as follows: click the option and choose Entire feature
will not be available from the shortcut menu.
Step 11 Click Next until the User Name Mapping page is displayed.
Step 12 Click Local User Name Mapping Server, and then click Password and group files. Click
Next.
Step 13 Enter the paths where the passwd and group files are located in the Password file path and
name and Group file path and name text boxes, as shown in Figure 2-66. Then click Next.
Figure 2-66 User Name Mapping
Step 14 Select the installation path. The default path is C:\SFU. Click Next to wait for the installation.
Step 15 Click Finish.
----End
Procedure
Step 1 Choose Start > Programs > Services for UNIX Administration. The Services for UNIX
Administration page is displayed.
Step 2 Double-click User Name Mapping, as shown in Figure 2-67.
Issue 06 (2013-01-24)
67
Step 3 Click Maps. The Maps page is displayed, as shown in Figure 2-68.
Figure 2-68 Maps
2.
Click List Windows Users and select Administrator in Windows Users, as shown in
Figure 2-69.
Issue 06 (2013-01-24)
68
3.
Click List UNIX Users and select nobody for Administrator in UNIX Users.
4.
Click Add.
5.
2.
Click List Windows Groups and select Administrator in Windows Groups, as shown
in Figure 2-70.
3.
Click List UNIX Groups and select nobody for Administrator in UNIX Groups.
4.
Click Add.
5.
Procedure
Step 1 Create a shared folder. The shared folder name is fileserver.
Step 2 Right-click fileserver and choose Properties from the shortcut menu that is displayed.
Step 3 Click the NFS Sharing tab in the displayed dialog box.
Step 4 Set parameters on the NFS Sharing tab page, as shown in Figure 2-71.
Issue 06 (2013-01-24)
69
The parameters on the NFS Sharing tab page are described as follows:
Anonymous UID/GID: indicates the anonymous UID or GID, which is used for NFS
connection authentication.
When the NFS is used for voice recording and playing services, setting the value of Anonymous
UID/GID is optional. By default, the system sets the values of Anonymous UID and Anonymous GID
to 65534 and 65533.
Step 5 Click Permissions and grant read and write permissions to the shared folder, as shown in
Figure 2-72.
Issue 06 (2013-01-24)
70
Procedure
Step 1 Insert the installation CD-ROM of the operating system into the CD-ROM drive.
Step 2 Enter yast2 in the command line window to enter the YaST control center.
Step 3 Click Network Services and double-click NFS Server on the displayed page.
A dialog box shown in Figure 2-73 is displayed.
Issue 06 (2013-01-24)
71
Issue 06 (2013-01-24)
72
Procedure
Step 1 Log in as the root user.
Step 2 Disable the firewall.
1.
2.
Select Security and Users in the left area. Click the Firewal in the right area.
3.
Select the Start-Up. Select the When Booting and Stop Firewall Now.
4.
2.
//Open the exports file in /etc and make the file editable.
Issue 06 (2013-01-24)
73
If the NFS service is in running state, it indicates that the NFS service is started normally, as
shown in Figure 2-76.
Figure 2-76 Checking the NFS service status
----End
Procedure
1.
2.
Choose Service.
3.
4.
Issue 06 (2013-01-24)
74
5.
Click Save.
6.
See LMT-based Login and Configuration to run the config add nfs type <mrs> nfsno<0-3>
nfsip <A.B.C.D> remotedir /<string> localdir <string> [backupip <A.B.C.D>]
command.
----End
Procedure
1.
Run the show nfs type mrs command on the U1910 to view the NFS status. For details
on how to run the command, see LMT-based Login and Configuration.
If STATUS is Connect as shown in Figure 2-78, the NFS is installed successfully.
Issue 06 (2013-01-24)
75
----End
Issue 06 (2013-01-24)
76