OES 2 includes a new version of the Response File Generator that runs from the YaST Administrator Settings tool on Linux. This NetWare Response File Utility is automatically installed on every OES 2 Linux server. Because of the many improvements that have been made in this wizard, it is recommended that you use this method to create response files for NetWare 6.5 SP8 servers.
If you have not already done so, install the OES 2 add-on product on a SLES 10 SP1 server. For more information, see Installing OES 2 SP2
in the OES 2 SP2: Installation Guide.
To start the utility, click > > > .
Select the hardware type of the server you are creating the response file for:
Select to create a response file for use when installing virtualized NetWare 6.5 SP8 as a guest operating system on a Xen-based host server.
Select to create a response file for use when installing physical NetWare 6.5 SP8 on standard server hardware.
Select the type of installation for the response file:
New Server: Select this option to create a response file for a new NetWare 6.5 SP8 server installation.
Server Upgrade: Select this option to create a response file to be used when performing an upgrade of a NetWare server. (This option is included for compatibility with previous versions of NetWare and should not be selected for an NetWare 6.5 SP8 server. In-place and remote server upgrades are no longer supported in NetWare 6.5 SP8.)
Factory Install - Image: Select this option to create a response file to be used when performing the first phase of a factory installation of a NetWare server.
Factory Install - Configure: Select this option to create a response file to be used for the second phase of a factory installation of a NetWare server.
IMPORTANT:You must use a response file for both phases of a factory installation. You cannot use a response file for the image phase and then answer the installation prompts manually for the configuration phase.
(Optional) Select an existing response file to use as a template for the one you are creating.
Use a response file template: Select this option if you have previously created a response file that you want to use as the template for the new one.
Response file template: Browse to and select the existing response file you want to use as the template.
NOTE:Use only a response file created with the NetWare Response File Utility as a template. Do not use response files created with the Response File Generator in Deployment Manager for previous versions of NetWare.
Click .
To create a complete response file, you must click each of the headings on the Response File Generator page and specify the required information. Many of the sections have default settings that you can accept for most server installations. The color of the headings changes from red to blue after you have made the settings for each section.
NOTE:Depending on the selections you made on the previous screen and the settings you select as you go through the Response File Generator, you might not see all of the headings detailed in this section.
Click the heading on the Response File Generator page.
On the Source Properties page, select the of the NetWare 6.5 installation files.
Select if you want to facilitate the automated installation or upgrade of NetWare servers by copying the NetWare installation files from the NetWare 6.5 CDs or DVD to a remote “source” server. The files can then be accessed from this source server instead of from a local CD/DVD drive or hard disk.
Select if you want to use the NetWare installation CDs or DVD as the source or copy their contents to the local hard disk drive.
HINT:You can also use an .iso file as a local storage source.
(Conditional) If you selected as the location type, specify the following information:
Server Name: The name of the source server containing the installation files.
Server IP Address: The IP address of the source server.
Source Location Path: The path to the folder where you copied the NetWare installation files; for example, vol1:nw65inst.
Click .
(Conditional) If you selected to install from a remote NetWare server in Step 2, click the heading on the Response File Generator page and specify the following eDirectory information to enable the NetWare install program to authenticate to the tree and access the source installation files:
Tree Name: The name of the eDirectory tree in which the source server’s Server object exists.
Context for Server Object: The full path of the source server object in the eDirectory tree. For example, if the source server object is in an Organizational Unit (OU) named Sales under the Organization (O) named Example, the context would be denoted as OU=Sales.O=Example or Sales.Example.
User Name: The Common Name (CN) of the user to use when logging in to the tree. This should be a user with the necessary rights to install a server object into the tree.
User Context: The full eDirectory context for the User object.
Password/Retype Password: Type the user’s password in both of the password fields to verify accuracy.
Click .
Click the heading on the Response File Generator page.
The destination server is the new server for new server and factory installations, or the server to be upgraded for upgrades.
Specify the following information:
Server Name: For new servers and factory installations, specify a valid NetWare server name. The server name must be unique from all other servers in the eDirectory tree. The name can be between 2 and 47 alphanumeric characters and can contain underscores ( _ ) and hyphens (-), but no spaces ( ). The first character cannot be a period (.).
IMPORTANT:The server name must be different from the name that you plan to use for the eDirectory tree.
Server IP Address: If you are creating a response file for a new server or server upgrade, type the IP address of the server in the field.
Click .
Click the heading on the Response File Generator page.
If the server is to be installed into a new eDirectory tree, select the check box. Otherwise, leave the check box deselected to install the server into an existing tree.
Specify the following information:
Tree Name: The name of the eDirectory tree where you want the server’s Server object to be created
Context for Server Object: The full path of the Server object in the eDirectory tree. For example, a NetWare server might be installed in an Organizational Unit (OU) named Sales under the Organization (O) named Org. The context would be denoted as OU=Sales.O=Org or Sales.Org.
Replica Server IP Address: The IP address of a server holding an eDirectory replica (for existing tree installations only).
Admin Name: The Common Name (CN) of the Admin user with rights to install servers in the tree.
Admin Context: The full eDirectory context for the Admin user object.
Password/Retype Password: Type the user’s password in both of the password fields to verify accuracy.
Click .
Click the heading on the Response File Generator page.
NetWare servers must have a valid license in order to function. During the NetWare installation, the NICI keys (*.nfk files) are read and used to create a license object in the eDirectory tree.
Specify the following information for your server:
NDS License Context: Specify the container in eDirectory where you want the NetWare license object to be created. Normally this is created at the Organization (O) level so that the license information can flow down to the entire tree.
Install without Licenses: Although the server can be installed without a license, an unlicensed server allows only two user connections and is not fully functional. If you select this option, you can use the Novell iManager utility to install the necessary licenses after the installation. See Section 4.25.2, Installing NetWare Licenses for instructions.
If no valid license file can be found when the response file installation is run, the install assumes licenses will be installed later and continues with the installation.
Click .
Click the Protocols heading on the Response File Generator page.
NetWare 6.5 SP8 provides support for the Internet Protocol (IP) and the Internetwork Packet Exchange (IPX™) protocol. Both protocols can be assigned to a single network board, which allows the server to communicate using both IP and IPX.
The IP protocol is selected by default and cannot be deselected. The IPX protocol is optional.
Specify the IP protocol information for the server:
IP Address: Specify the IP address for the server. (In most cases, the IP address is automatically entered in this field based on the address you specified for the destination server.)
An IP address identifies each device on the network. The address consists of 32 bits, which are represented as decimal values separated by periods, such as 123.45.67.89. If your server connects to the Internet, you must obtain a unique IP address. For information on receiving an IP address, contact your Internet service provider (ISP).
Subnet Mask: Specify the subnet mask (typically 255.255.255.0).
A subnet mask lets you break up your network into smaller networks. Your network might have too many nodes or be too geographically diverse to manage as a single network. Dividing your network into smaller networks lets the network routers filter and reduce the network activity seen by any of the nodes. However, dividing your network and using several network addresses might not be appropriate on a large network that needs to appear to network administrators as a single network.
Router (Gateway): Specify the address of the router that connects two different environments, such as a LAN and the Internet.
You can specify a specific router (gateway) address, or you can rely on the network to automatically find the nearest router. If you specify the address, remember that the router must exist on the network segment.
(Optional) To enable IPX support on the server, select the check box and specify the following information:
IPX Frame Types: The basic installation selects the default IPX frame type for your network. You can add support for additional frame types by clicking the radio button for the desired frame types.
Each frame type that is used on the network is treated as a logical network segment and requires its own IPX network address, even though each frame type is using the same network board and physical cable segment.
Server ID: Specify a hexadecimal number, one to eight digits (1 to FFFFFFFE), that identifies the server in IPX communications.
Click .
Click the heading on the Response File Generator page.
The NetWare installation program supports multiple languages. If the server you are creating the response file for requires support for a language other than United States English, you can select the language and code page settings here.
For each setting, click the down-arrow to select the desired setting from a drop-down list:
Language: Select English, German, Italian, Spanish, French, Portuguese, or Russian.
Country Code: Select the code for the country where the server will be installed.
Code Page: Select 437 for United States English or 850 for Multilingual.
Keyboard Code: Select the language of the keyboard to be used with the server.
Click .
Server Location Protocol (SLP) enables client applications to dynamically discover services in TCP/IP networks. Without SLP, network resources must be manually configured or specified in a separate configuration file. Networks with no more than three servers do not need SLP.
Click the heading on the Response File Generator page.
Specify the SLP settings for the server:
Do Not Install SLP: Select this option if you do not want to install SLP.
DA Server IP Address: Specify the IP addresses of the Directory Agents (DAs) on your netowrk. You can specifyup to three IP addresses for Directory Agents.
SLP Scope List: Specify the scopes a DA must support. Use commas to separate each scope. For example, net.slp.useScopes = myScope1, myScope2, myScope3.
Configure Server as Directory Agent (DA): If you do not have any DAs configured on your netowrk or you want to add another one, you can configure this server to be a DA by selecting this option.
Enable Multicast Routing on This Server: Select this option if you need multicast routing.
Click .
Click on the Response File Generator page.
Specify the Domain Name Service (DNS) configuration information for your server:
Host Name: This is the simple, readable name that matches this NetWare 6.5 server’s name (or the name you have bound to the network board, such as “server1”).
Domain: The hierarchical name that represents the DNS naming scheme of your network, such as example.com.
Name Server IP Address: Specify the IP address of up to three existing DNS servers that maintain the list containing this server’s simple, readable name and IP address.
Verify the DNS Information: Select this option if you want the NetWare Install program to verify the DNS information for you.
Click .
Click on the Response File Generator page.
In the field, select the time zone the server will reside in from the list provided.
Each time zone region displays the standard time offset from GMT, which is the difference, in number of hours, between Greenwich Mean Time (GMT) and the time zone being selected. GMT is equivalent to Coordinated Universal Time (UTC).
Select if you want the server to automatically adjust its clock for Daylight Saving Time.
Click .
Time synchronization is a critical function for servers in an eDirectory tree. The reported time must be synchronized across the network in order to provide expiration dates and time stamps to establish the order of events taking place in eDirectory.
Click the heading on the Response File Generator page.
Specify the time server protocol the server should use:
NTPv3: Select this option to use Network Time Protocol for synchronizing time on your network. (The xntpd.nlm that provides NTP time packets is also capable of providing Timesync packets for servers that require them, such as NetWare 5.0 and 4.2 servers.)
TimeSync: Select this option to use the legacy time synchronization mechanism built in to NetWare. (The timesync.nlm that provides Timesync packets is also capable of providing NTP packets for interoperability with other time servers.)
Specify the type of time server you want the server to be.
The NetWare time synchronization scheme distinguishes four types of time servers. Three of these provide network time: Single Reference, Reference, and Primary. All other servers are called Secondary time servers because they receive their time from the time providers.
Single: The first server is a network is automatically designated as a Single Reference time server. It provides time to the entire network.
Reference: A network usually has only one Reference time server. It provides a network time for all Primary time servers to migrate to. It is used on larger networks where Primary time servers are required. If more than one Reference time server exists, each must be synchronized to the same external time source, such as an atomic clock.
Primary: A Primary time server is responsible for determining and setting the network time. It polls other primary and reference servers to determine the “average network time.” The average network time is then distributed to other requesting servers.
Secondary: By default, all servers except the first server are designated as Secondary time servers. Secondary time servers rely on other sources such as a Single Reference time server to provide them with the network time. A Secondary time server can get the network time from another Secondary time server or from a Single Reference, Reference, or Primary time server.
NOTE:If the network has fewer than 30 servers, use the default installation settings of a Single Reference time server (the first server installed in the tree) and Secondary time servers (all subsequent servers installed in the tree). If the network has more than 30 servers, you might need to customize the environment by using different types of time servers.
(Optional) If you selected TimeSync as the time server protocol, you can configure up to three Timesync time sources by selecting and specifying the IP addresses of the time sources in the Time Source fields.
If a configured time source uses NTP, select the check box to the right of the time source.
Click .
Click the heading on the Response File Generator page.
Specify the settings for various aspects of the server installation:
Automatic Install Reboot: Select whether you want the server to automatically reboot after the install is complete. The default is Yes.
NOTE:Be sure to remove all floppy disks and bootable CDs from the destination server before the reboot.
Unsupported Drivers: Select whether you want the NetWare install program to use untested LAN and disk drivers if no certified drivers can be found. The default is No.
Driver Install Type: Select whether you want the NetWare install to auto-load the drivers (Default) or to stop at the driver selection screens (Manual).
Server Up On Reboot: Select whether you want the server to come up after the system is rebooted. The default is Yes.
(Optional) If you want to specify non-default server SET parameters during the installation, click > . Type the new SET parameter, then click .
If you need to remove a SET parameter from the list, select it and click .
After you have finished adding SET parameters, click .
Click .
Click the heading on the Response File Generator page.
In the field, specify the size for the server’s FAT (DOS) boot partition, in megabytes.
The default of 500 MB is sufficient for most NetWare servers.
In the Sys Volume Size field, specify the size for the server’s sys: volume.
The default setting is 9500 MB (approximately 9.5 GB) for the NetWare system and product files, but you can specify a larger size if you plan to store additional data on the sys: volume.
IMPORTANT:In NetWare 6.5 SP6 and earlier, the default size for the sys: volume was 4 GB (4000 MB). Starting in NetWare 6.5 SP8, that default size is no longer large enough to accommodate server installations that include iManager, Apache, and Tomcat. If you are installing a server without iManager, Apache, and Tomcat, you can decrease the size of the sys: volume if disk space is limited.
Click .
Click the heading on the Response File Generator page.
This page lists the patterns available for installation with NetWare 6.5 SP8. A pattern defines a special-purpose server that can be configured during the NetWare installation.
Select the pattern you want for the server being installed.
Selecting the button next to the name of the pattern displays a description of that pattern in the description window.
Click .
(Conditional) If you chose the Customized NetWare Server pattern, click the heading to see a list of the components available for installation with NetWare 6.5 SP8.
Select the products you want to install on the server.
To view a description of a component, click the component’s name. A description is displayed in the description box.
Selecting a box adds the component to the list of products and services to install. Deselecting a box removes the component from the list of products and services to be installed.
To select all available components to install, select . To deselect all components, select .
Click .
Click the heading on the Response File Generator page.
Select the Novell Modular Authentication Service (NMAS™) login methods to install on the server. The defaults are Challenge Response and NDS.
To view a description of a method, click the method’s name. A description is displayed in the description box.
To select all available methods to install, select . To deselect all methods, select .
Click .
Depending on the components you selected for a Customized Server, the Response File Generator page can include some or all of these additional headings:
DNS/DHCP Configuration
iFolder Server Configuration
MySQL Configuration
exteNd Application Server Configuration
NetStorage Configuration
Refer to the online help to configure the settings for these components.
When you have finished making all the settings for the response file (all headings are displayed as blue instead of red), click .
Specify the following information to save the response file.
Response file name: Specify a name for this response file. The default name is netware.rsp.
Save Directory: Browse to or specify the location on the local file system where you want to save the response file. Be sure to specify a valid path ending with a forward slash (/) character.
The NetWare license files should be saved in this same location.
NOTE:You can extract the NetWare license files from the .iso image file by using the Nautilus file browser. Open the image file and wait for the browser to scan the image. When the Archive Manager window appears, select the .nfk and .nlf files in the /license directory and click the icon. Select the destination folder and click the button. The license files are saved to the specified location in a /license directory. If necessary, copy them to the directory where you saved the response file.
(Optional - Virtual Hardware Type only) Select if you want YaST to automatically launch the VM Creation Wizard and begin the process of creating a virtual machine and installing the virtualized NetWare server using this response file.
Also specify the following:
Custom VM name: The default name for the virtual machine you are creating a response file for is the server name. If you want, you can change it to a custom name that is more descriptive.
Installation Source Location: Browse to and select the location of the installation source (DVD, .iso image, or NFS mount).
Installation Destination Location: (Factory Installations only) Browse to or specify the path to the server image that you previously created and now want to configure. The default location is /var/lib/xen/images/vmname.
Click to exit the NetWare Response File Utility.
If you selected the option to start the VM Creation Wizard, the wizard automatically launches and uses the settings in the response file to install the virtual NetWare server. In most cases, no further input is required from the installer.