Using Console RedirectionDell™ PowerVault™ 715N NAS Systems Administrator's Guide
Installing Multilanguage User Interface
(MUI) Support
Installing and Configuring Support for Other Languages
Microsoft Directory Synchronization Services
This section includes descriptions of advanced features that cannot be performed from the Dell™ PowerVault™ NAS Manager menus.
To perform the procedures in this section, you must use the Terminal Services Advanced Client. To access the Terminal Services Advanced Client, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
 |
NOTE: The default administrator user name is administrator and the default password is powervault. |
Console redirection allows you to view the NAS system's power-on self-test (POST) and change BIOS settings from a client system. Console redirection redirects keyboard input and text output through the serial port. Graphic output is not redirected. This section describes the simplest connection possible: connecting to a system with a serial cable.
To use console redirection, you must have the following:
|
NOTE: Console redirection is enabled by default in the NAS system BIOS. |
|
NOTE: You can use clients running operating systems other than Windows 2000 for console redirection. However, this section provides information for setting up console redirection only on a Windows 2000 client system. For console redirection information on other operating systems, see the operating system documentation. |
To set up console redirection on a Windows 2000 client system to manage your NAS system, perform the following steps:
See "Shutting Down the NAS System" in "NAS Manager."
The COM port used on your client system is typically labeled COM1 or COM2.
You can now use your client system to manage your NAS system. If you need to configure your BIOS settings, see "Entering the BIOS Setup Utility" in your User's Guide.
Because of ANSI limitations, not all keys can be used with console redirection. Table 7-1 shows the keystroke combinations used for the version of Windows on your client system.
|
Normal Keys (As They Appear on the Keyboard) |
Keys Used for |
Keys Used for All Other Windows Operating Systems |
|---|---|---|
Home | <Esc><h> | <Esc><h> |
End | <Esc><k> | <Esc><k> |
Insert | <Esc><+> | <Esc><+> |
Delete | <Esc><-> | <Esc><-> |
Page Up | < Esc><?> | <Page Up> |
Page Down | <Esc></> | <Page Down> |
F1 | <Esc><1> | <F1> |
F2 | <Esc><2> | <F2> |
F3 | <Esc><3> | <F3> |
F4 | <Esc><4> | <F4> |
F5 | <Esc><5> | <Esc><5> |
F6 | <Esc><6> | <Esc><6> |
F7 | <Esc><7> | <Esc><7> |
F8 | <Esc><8> | <Esc><8> |
F9 | <Esc><9> | <Esc><9> |
F10 | <Esc><0> | <Esc><0> |
F11 | <Esc><!> | <Esc><!> |
F12 | <Esc><@> | <Esc><@> |
Up arrow | <Esc><w> | Up arrow |
Right arrow | <Esc><a> | Right arrow |
Left arrow | <Esc><d> | Left arrow |
Down arrow | <Esc><x> | Down arrow |
<Ctrl><Alt><Delete> | <Esc><Shift><r> <Esc><r> <Esc><Shift><r> OR <Esc><Shift><b> | <Esc><Shift><r> <Esc><r> <Esc><Shift><r> OR <Esc><Shift><b> |
|
NOTE: Installing the MUI for your language automatically installs the appropriate language locale. |
The PowerVault 715N NAS system allows you to change languages for its Microsoft Windows Powered operating system's user interface. The MUI allows the PowerVault 715N to display Windows Powered operating systems menus, dialogs, and help files in multiple languages. The supported MUI languages are simplified Chinese, traditional Chinese, Dutch, English, French, German, Italian, Japanese, Korean, Spanish, and Swedish. You must install a language MUI from the Multilingual Support CD before it can be used on the system. When you receive a PowerVault 715N NAS system from Dell, the root directory of drive C includes a localization directory, which contains all of the files included in the Multilingual Support CD. If you have performed the reinstallation procedure, this directory does not exist, and you must install a language MUI from the Multilingual Support CD.
|
NOTE: Installing and configuring the operating system MUI does not affect the language used by the NAS Manager. |
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
After a MUI language has been installed, you can apply it to any user by performing the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
The default administrator user name is administrator and the default password is powervault.
|
NOTE: Install additional language locales only if your preferred language is not available with MUI support or you need additional locale support. |
The Windows Powered operating system that comes installed on the PowerVault 715N can be configured to support reading and writing documents in a number of languages. To install the software required to support a specific language, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: For more information, see the Microsoft Windows Powered operating system's online help. |
Network adapter teaming allows the system to use the combined throughput of multiple network ports in parallel to increase performance or to provide fault tolerance. Network adapter teaming on your NAS system supports the following technologies:
|
NOTE: When creating or removing teams, the IP address of the NAS system's LAN connections changes. To prevent disconnecting from the NAS system during team configuration, use a serial connection when creating or removing teams. See "Configuring Your System Using a Serial Connection" in "Initial Configuration" before configuring your teams. |
Adaptive Load Balancing (ALB) is a simple and efficient method for increasing the NAS system's network transmission throughput. The ALB software continuously analyzes transmission loading on each adapter and balances the load across the teamed ports as needed. Adapter teams configured for ALB also provide the benefits of adapter fault tolerance. To use ALB, the Ethernet ports on the NAS system must be linked to the same Ethernet switch.
Adapter Fault Tolerance (AFT) provides the safety of an additional backup link between the NAS system and the hub or switch. If a hub, switch port, cable, or Ethernet port fails, you can maintain uninterrupted network performance. AFT is implemented with a primary adapter and a backup, or secondary, adapter. If the link to the primary adapter fails, the link to the secondary adapter automatically takes over.
Link aggregation is a performance technology developed by Intel and others to increase a system's network throughput. Unlike ALB, link aggregation can be configured to increase both transmission and reception channels between your system and switch. Link aggregation works only with compatible Intel switches. To use link aggregation, the Ethernet ports of the NAS system must be linked to the same Intel Ethernet switch.
Fast EtherChannel (FEC) is a performance technology developed by Cisco Systems to increase a system's network throughput. Unlike ALB, FEC can be configured to increase both transmission and reception channels between your NAS system and switch. FEC works only with compatible Cisco switches. To use FEC, the Ethernet ports of the NAS system must be linked to the same Cisco FEC-compatible switch.
IEEE 802.3ad is a performance technology standard that increases a system's network throughput. IEEE 802.3ad is similar to the FEC standard developed by Cisco. However, whereas FEC works only with FEC-compatible Cisco switches, IEEE 802.3ad works with all switches that support IEEE 802.3ad. To use IEEE 802.3ad, the Ethernet ports of the NAS system must be linked to the same IEEE 802.3ad switch.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Network Teaming utility, Intel PROSet II, displays.
The Teaming Wizard displays.
The types of team include Adapter Fault Tolerance, Adaptive Load Balancing, Fast EtherChannel*/Link Aggregation, and IEEE 802.3ad.
|
NOTE: Broadcom NICs cannot be selected. |
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Network Teaming utility, Intel PROSet II, displays.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Network Teaming utility, Intel PROSet II, displays.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Network Teaming utility, Intel PROSet II, displays.
The types of team include Fault Tolerance, Load Balancing, Fast EtherChannel*/Link Aggregation, and IEEE 802.3ad.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Broadcom Advanced Server Control Suite window displays.
The types of team include Start Load Balance and Fail Over, FEC/GEC, and Link Aggregation (IEEE 802.3ad).
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Broadcom Advanced Server Control Suite window displays.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
The Broadcom Advanced Server Control Suite window displays.
The types of team include Start Load Balance and Fail Over, FEC/GEC, and Link Aggregation (IEEE 802.3ad).
Services for UNIX (SFU) provides the tools needed to integrate UNIX and Windows networks by leveraging existing UNIX network resources and expertise. SFU includes more than 60 of the most common UNIX command line utilities to provide a familiar environment for UNIX users and administrators.
Server for NFS allows you to leverage your existing UNIX network resources for UNIX clients.
SFU provides important tools to enhance and simplify the administration of your network.
SFU provides a robust Server for NFS that can be used to provide disk resources from systems running Windows NT and Windows 2000 to any system on your network that supports NFS. To administer Server for NFS, set the following options from the SFU MMC console:
Table 7-2 lists UNIX utilities provided with SFU.
|
Category |
Utility |
|---|---|
File and directory utilities | basename, cp, diff, dirname, dos2unix, find, ln, ls, mkdir, mount, mv, paste, pwd, rm, rmdir, sdiff, split, tee, touch, uniq, uudecode, uuencode, umount |
Text utilities | cat, cut, grep, egrep, fgrep, head, more, printf, sed, sort, tail, tr, vi, wc |
Programming utilities | perl, od, sh, strings |
Security utilities | chmod, chown, su |
Process and general utilities | cron, crontab, date, du, kill, nice, printenv, ps, rcmd, renice, sleep, atr, top, uname, wait, which, xargs |
The Telnet server works optimally for most installations. It accepts logins from a variety of clients, including the Telnet clients shipped with Windows 2000, Windows NT, Windows 95, and Windows 98, as well as a variety of character mode terminal clients from virtually any operating system. In addition, it can be configured to meet specific site requirements such as improving security, simplifying logins, and supporting stream or console mode.
The SFU Telnet server supports Windows NT LAN Manager (NTLM) for authentication of client logins. NTLM allows users to be automatically authenticated to the Telnet server based on their Windows NT login. This makes using Telnet completely transparent to users, while ensuring that clear text passwords do not pass over the network. However, NTLM must be supported on the client side of the login as well.
When users are logged in to a system that is using NTLM login, they are restricted to local drives on that system. If they need to map network resources, they can do so by explicitly mapping with full credentials.
The Telnet server is administered using the SFU MMC snap-in or the tnadmin program.
The following options are available:
SFU UNIX includes a single MMC for managing all of SFU. The MMC provides a cohesive management interface that allows you to administer all systems on the network from any console. Further, since SFU supports the Windows Management Interface (WMI), management can be scripted from the command line.
You can access the MMC Console by selecting Computer Management under System Management on the Advanced Administration Menu. See "Using the PowerVault Advanced Administration Menu" in "NAS Manager."
SFU includes ActiveState's ActivePerl 5.6, a full-featured port of Perl 5.6 and Perl Script to Windows Powered operating systems. Among other improvements, ActivePerl 5.6 includes support for fork() emulation at the interpreter level, improving the portability of scripts and modules. ActivePerl also provides full support for the Windows Script Host, making ActivePerl an excellent tool for system administration tasks.
User Name Mapping provides mapping of names between the UNIX and Windows environments. You can configure User Name Mapping from the SFU MMC Console or by using the NAS Manager to configure properties for the NFS Sharing Protocol. With User Name Mapping, you can create simple maps between Windows Powered user accounts and corresponding UNIX accounts. You can also use the Advanced Map feature to map accounts with dissimilar names. Given that UNIX user names are case-sensitive, while Windows Powered operating system names are not, the use of User Name Mapping can greatly simplify maintaining and managing accounts in the two environments. User Name Mapping uses Network Information Service (NIS) or local Personal Computer Network File System (PCNFS) user and group files to authenticate users. Also, User Name Mapping supports bidirectional one-to-many mapping, allowing you to map a single UNIX or Windows Powered operating system account to multiple accounts in the other environment. For example, you can map more than one administrative account in a Windows Powered operating system to the UNIX root account.
To create user and group name maps, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
To configure the type of server to be used to access UNIX user and group names, perform the following steps:
|
NOTE: The UNIX password file and group file formats must conform to the UNIX standard for these files. |
To define simple maps in SFU, select the Simple Maps check box, and then perform the following steps:
If you are defining explicit maps, you create user and group maps individually. To create explicit maps, perform the following steps:
This action refreshes your UNIX users or groups selection.
For UNIX and Windows NT User Name Mapping, an NIS Server must already exist in the UNIX environment or UNIX user and group files must exist on the PowerVault NAS system. User Name Mapping associates UNIX users and groups to Windows NT users and groups. You can use two types of maps, simple and explicit. Simple maps define a one-to-one relationship between the same user names and groups. Explicit maps define a relationship between dissimilar user names and groups.
In the workgroup scenario, you configure User Name Mapping locally on the PowerVault 715N system. All maps are contained on this system.
In the domain scenario, you configure NFS Authentication on all domain controllers. The NT Authentication Service installation program must be installed on the domain controller and available in the DomainUtils share on the NAS system.
To install the NT Authentication Service on a domain controller, perform the following steps:
Although Windows and UNIX file systems do not allow certain characters in filenames, the characters that are prohibited by each operating system are not the same. For example, a valid Windows filename can not contain a colon (:), but a UNIX filename can. If a UNIX user attempts to create a file in an NFS share and that file contains an illegal character in its name, the attempt will fail.
You can use filename character translation to replace characters that are not allowed in a file system by mapping them to characters that are valid. To enable filename character translation, create a text file that maps Windows to UNIX characters, and then modify the registry entry that specifies the path and name of the translation file.
The filename character translation text file is a list of mapped characters in the following format, such as the following:
0xnn : 0xnn [ ; comment ]
where nn is the hexadecimal value of the character
The entry for a map from the UNIX character ":" to the Windows character "-" in the filename character translation text is as follows:
0x3a : 0x2d ; Map ':' (0x3a) to '-' (0x2d)
To map the character combination "()" to the character "^", add the following entry:
0x28 0x29 : 0x5e ; Map '()' to '^'
To specify the path and name of the filename character translation text file for Server for NFS to use, modify the following registry key to contain the path and filename of the character translation file:
HKLM\SOFTWARE\Microsoft\Server for NFS\CurrentVersion\Mapping\CharacterTranslation
File Server for Macintosh (FSM) provides the tools needed to integrate Macintosh and Windows networks by leveraging existing Macintosh network resource and expertise. FSM is disabled by default on the NAS system. See "Enabling the AppleTalk Protocol" for information about enabling FSM.
The AppleTalk protocol is disabled on the NAS system by default. You must enable the AppleTalk protocol for Macintosh clients to access the NAS system.
To enable the AppleTalk protocol, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
FSM can bind to only one network adapter. By default, it is bound to the embedded 10/100TX Network Adapter. To change the binding in systems with multiple network adapters, the AppleTalk protocol properties for the network adapter to be used by AppleTalk must be modified to accept inbound connections.
To modify the AppleTalk protocol adapter binding for filers with multiple network adapters, perform the following steps from the NAS Manager:
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The AppleTalk protocol must bind to an adapter that is enabled, regardless of whether the File Server for Macintosh is disabled. |
A user authentication map (UAM) is a software program that prompts users for an account name and password before they log in to a server. The Macintosh Chooser has a standard UAM built in that uses the clear-text password or Apple's RandNum Exchange method of security.
Microsoft Authentication offers an additional level of security because the password is used as a key to encrypt a random number. If the system administrator has determined that encryption is an important security measure, you may be asked to use Microsoft Authentication in addition to Microsoft UAM authentication.
To use Microsoft UAM 5.01, you must have a Macintosh client running AppleShare Client 3.8 or newer or the Mac operating system (OS) 8.5 or newer operating system. If you do not meet the minimum requirements, the Microsoft UAM Installer installs the old Microsoft UAM 1.0 module. If you upgrade your system software, you need to run the Microsoft UAM Installer again.
Log in to the Microsoft UAM Volume on the system to access the MS UAM file, and then drag this file to the AppleShare Folder in your System folder.
To access the Microsoft Authentication files on the system, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The password can be no longer than eight characters. Passwords longer than eight characters cannot be used when mapping an Apple share without a UAM. |
Ask your system administrator if you are not sure of the zone.
To install the authentication files on the Macintosh workstation, perform the following steps:
The installer reports whether the installation succeeded.
If the installation succeeded, Macintosh users of this workstation are offered Microsoft Authentication when they connect to the system.
If File Services for Macintosh cannot establish communications to the local RPC service, you may need to restart the Workstation Service.
To restart the Workstation Service, perform the following steps:
See "Logging in to the NAS Manager."
|
NOTE: The default administrative user name is administrator and the default password is powervault. |
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
Services for NetWare (SFN) are compatible with Novell NetWare Bindery service for authentication and file access using the internetwork packet exchange/sequenced packet exchange (IPX/SPX) network protocol. Services for NetWare are disabled by default. See "Enabling Services For NetWare."
The NetWare protocol is disabled on the NAS system by default. You must enable the NetWare protocol for NetWare clients to access the NAS system.
To enable the NetWare protocol, perform the following steps:
See "Logging in to the NAS Manager" in "NAS Manager."
To configure this protocol, you need the internal network number, the frame type, and the network number.
Internal network numbers are used for internal routing and are generally needed only for servers. You should not need to change this option on your system.
Frame types define the packet formats that are used by different networks. It is important that all systems in a network have the same frame type so that they can communicate with the rest of the network.
When you are configuring your system, it attempts to automatically detect the frame type for the client. In most cases, this is successful. However, occasionally the automatic detection feature selects an inappropriate frame type, usually because more than one frame type exists on the network. If this happens, you should manually set the frame type to match the one specified on your NetWare server. Note that if more than one frame type exists, you should select the one that is detected first. For example, if the frame types Ethernet 802.2 and Ethernet 802.3 are bound to the same segment, then configure frame type Ethernet 802.2. The order of detection is Ethernet 802.2, Ethernet 802.3, Ethernet II, and then Ethernet SNAP.
By default, the IPX protocol is configured on the NAS system to automatically detect frame types. To use the IPX protocol, you must change your NAS system's IPX properties to manually detect frame types.
To configure the IPX protocol to manually detect frame types, perform the following steps:
See "Logging in to the NAS Manager."
|
NOTE: The default administrative user name is administrator and the default password is powervault. |
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
The IPX protocol is now configured on the NAS system to manually detect frame types.
Microsoft Directory Synchronization Services (MSDSS) allows you to synchronize a wide variety of data stored in the Active Directory service with Novell Directory Service (NDS) and NetWare 3.x binderies.
MSDSS is a highly flexible service that helps Novell users to perform the following tasks:
MSDSS supports two-way synchronization with NDS and one-way synchronization with NetWare 3.x binderies to provide a complete directory interoperability solution. MSDSS also supports password synchronization and provides a directory migration service.
MSDSS allows NetWare users to deploy Active Directory without having to replace existing directories or bear the cost of managing two separate directories. As a result, users have the flexibility to:
MSDSS is easy to use and makes synchronization and Active Directory setup easy through its management interface. It is fully featured to allow users a choice of management, synchronization, and migration options.
MSDSS supports all major NetWare platforms and most Novell directories and binderies, and it includes support for IPX/SPX and TCP/IP network protocols.
To implement MSDSS, you must install the Windows 2000 Server operating system and the MSDSS software (available on the Microsoft Services for NetWare Version 5 CD) on at least one system. In Windows 2000, when you promote a system running Windows 2000 Server to an Active Directory server, it becomes a domain controller. You use this domain controller to configure Active Directory, install MSDSS, and then import information from the existing NetWare environment.
The larger the environment, the more new servers you need. If you are planning to have more than one domain, then you need new hardware for the first domain controller in each domain.
You must also install Novell Client Access software on the MSDSS server or servers. MSDSS uses Novell Client Access to authenticate and to access NDS. While accessing NDS, it authenticates, but does not use a license. MSDSS also uses Novell Client Access to map one directory's contents to another, taking into account the fact that the object classes in Novell's NDS or bindery directories are different from Active Directory object classes. Novell Client Access is also required to use the File Migration utility to migrate files.
You can install Novell Client Access in four modes: IP only, IPX only, IP and IPX combined, and IP with IPX Compatibility Mode. Most NetWare environments still use IPX. MSDSS works in all the modes because it uses Novell Client Access to access the lower layers.
If you are migrating NDS, you can import the user and group information from one NDS server to the MSDSS server because you have one user database per tree. You can then migrate the file system. Remember that each Novell server has its own file system, which is not replicated to other servers (whereas NDS is replicated to other servers). After the files are migrated, you can uninstall NDS from the server to provide more space for the Windows 2000 Server operating system.
The next two sections describe the procedures for implementing MSDSS in a smaller (local area network [LAN] only) or larger (wide area network [WAN]) network. You need to adapt the guidelines to suit your environment and goals.
A small company with a LAN-based and uncomplicated network is often a likely candidate for a quick migration. After doing all the preparations described in the previous section, perform the following steps (adjusted, if necessary, to your situation):
|
NOTE: To access MSDSS software, map a network drive to \\Dellxxxxxxx\DomainUtils, where xxxxxxx is the system's service tag number. For example, if your service tag number is 1234567, type DELL1234567. You can find the service tag number on the top cover of your NAS system. |
You must also run the File Migration utility.
When you are performing a migration, this page does not include the option to actually perform an initial reverse synchronization, but it is the page where you specify which password option you want to use.
After the user accounts are migrated, you can migrate the file system (migrating the users before the files allows you to migrate file-system permissions). Follow the instructions in the Help printout, "To migrate files." The prompts guide you through the following steps:
The NDS Modify option converts, by default, to Read because it does not have an equivalent NFTS right. You might want to click the Write check box to allow read/write access.
If the NDS or Bindery volume you selected in the source tree displays Unavailable, then you are not currently logged in to that tree or Bindery server. Log in, and then press <F5> after reselecting the volume to view the directories within the displayed volume.
The utility scans all source volumes and counts and displays the number of directories and files in each. It ensures that proper access has been given to each source volume, directory, and file. If any errors occur, the utility displays them under NetWare scan logs and Windows scan logs, respectively. You can select a number of acceptable errors; if this number is exceeded, the process aborts, allowing you to return to previous steps to correct the errors.
Manually migrate (or use third-party utilities to migrate) object security permissions and system accounts, printer objects, application objects, and other objects that MSDSS does not migrate from Bindery or NDS to Active Directory. (MSDSS migrates NetWare user accounts, groups, and distribution lists for Bindery and NDS, and, for NDS only, MSDSS also migrates NDS organizational units and organizations.)
You must configure the desktops to join the Windows 2000 domain.
Be sure that the users know how to handle their password the first time they log in (for possible password options, see "MSDSS Password Management" in "MSDSS Deployment: Understanding Synchronization and Migration)" at www.microsoft.com.
An organization large enough to have WAN links probably selects to synchronize its networks temporarily while performing a gradual migration over time (up to 3 months for a large network), or it prefers to use synchronization to establish a mixed Novell/Windows 2000 network on a long-term basis. If you plan a staged migration, one-way synchronization is often the appropriate choice.
After doing all the preparation described above, perform the following steps (adjusted, if necessary, to your situation):
|
NOTE: To access MSDSS software, map a network drive to \\Dellxxxxxxx\DomainUtils, where xxxxxxx is the system's service tag number. For example, if your service tag number is 1234567, type DELL1234567. You can find the service tag number on the top cover of your NAS system. |
MSDSS does not support custom object mapping for Bindery.
For more information, see the Novell website at support.novell.com/servlet/Knowledgebase and the Windows 2000 website at www.microsoft.com/windows2000.
This section explains how secure sockets layers (SSL) are used in the NAS system. It also explains how to use your own certificate, if you have one, and how to regenerate your certificate.
Certificates contain information that is used to establish system identities over a network. This identification process is called authentication. Although authentication is similar to conventional forms of identification, certificates enable Web servers and users to authenticate each other before establishing a connection to create more secure communications. Certificates also contain encryption values, or keys, that are used in establishing an SSL connection between the client and server. Information, such as a credit card number, sent over this connection is encrypted so that it cannot be intercepted and used by unauthorized parties.
Two types of certificates are used in SSL. Each type has its own format and purpose. Client certificates contain personal information about the clients requesting access to your site, which allows you to positively identify them before allowing them access to the site. Server certificates contain information about the server, which allows the client to positively identify the server before sharing sensitive information.
To activate your Web server's SSL 3.0 security features, you must obtain and install a valid server certificate. Server certificates are digital identifications containing information about your Web server and the organization sponsoring the server's Web content. A server certificate enables users to authenticate your server, check the validity of Web content, and establish a secure connection. The server certificate also contains a public key, which is used in creating a secure connection between the client and server.
The success of a server certificate as a means of identification depends on whether the user trusts the validity of information contained in the certificate. For example, a user logging on to your company's website might be hesitant to provide credit card information, despite having viewed the contents of your company's server certificate. This might be especially true if your company is new and not well known.
For this reason, certificates are sometimes issued and endorsed by a mutually trusted, third-party organization, called a certification authority. The certification authority's primary responsibility is confirming the identity of those seeking a certificate, thus ensuring the validity of the identification information contained in the certificate.
Alternatively, depending on your organization's relationship with its website users, you can issue your own server certificates. For example, in the case of a large corporate intranet handling employee payroll and benefits information, corporate management might decide to maintain a certificate server and assume responsibility for validating identification information and issuing server certificates. For more information, see "Obtaining a Server Certificate From a Certification Authority."
By default, the PowerVault 715N has a self-generated and self-signed certificate. The configured SSL port is 1279.
|
NOTE: For non-SSL communication, use port 1278. This port is not a secure port and all text is sent in plain text over the network. |
If a certification authority is present in the network, the administrator can choose to change the default PowerVault 715N certificate. The administrator must use the wizards to first request a certificate and then apply it to the NAS system.
|
NOTE: If you are replacing your current server certificate, the Internet Information Server (IIS) continues to use the old certificate until the new request has been completed. |
Find a certification authority that provides services that meet your business needs, and then request a server certificate.
|
NOTE: For the latest list of certification authorities supporting IIS, see the Microsoft Security website. In the By Category list, select Certification Authority Services. |
To obtain a server certificate, perform the following steps:
See "Logging in to the NAS Manager."
|
NOTE: The default administrative user name is administrator and the default password is powervault. |
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
The certification authority processes the request and sends you the certificate.
|
NOTE: Some certification authorities require you to prove your identity before processing your request or issuing you a certificate. |
For more information about SSL, see the Internet Information Server online help.
Your NAS system uses the simple network management protocol (SNMP), which is a set of protocols used by systems to provide information to a central management information database. The NAS Manager provides a method for configuring the community and agent properties.
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: The default administrator user name is administrator and the default password is powervault. |
|
NOTE: If the Advanced Administration Menu does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS system. |
Select this option if you want a trap message sent when authentication fails.
|
NOTE: You can make changes to an entry by clicking the entry and then clicking Edit. You can delete a selected entry by clicking Remove. |
|
NOTE: If you remove all the community names, including the default name Public, SNMP does not respond to any community names presented. You can add additional community and host names as necessary. |
|
NOTE: If you change existing SNMP settings, your changes take effect immediately. You do not need to restart the SNMP service for your settings to take effect. If you are configuring SNMP for the first time, you must restart SNMP before the settings take effect. |
See "Logging in to the NAS Manager" in "NAS Manager."
|
NOTE: If you change existing SNMP settings, your changes take effect immediately. You do not need to restart the SNMP service for your settings to take effect. If you are configuring SNMP for the first time, you must restart SNMP before the settings take effect. |