Novell is now a part of Micro Focus

Automating NetWare 5 Server Installations, Sending a CoreDump to a Remote TCP/IP Host

Articles and Tips: tip

Paul Thompson
Novell, inc.

01 Feb 2001


If you are going to install multiple NetWare 5 servers with the same or similar configuration, you might consider using the NetWare 5 Response File to automate the server installations. This file can feed some or all configuration parameters to the installation program.

A response file is automatically created when you install a NetWare 5 server. After you install your first server, you can then use the response file created during that installation as input for subsequent NetWare 5 installations. The installation program reads the values specified in the response file and uses them instead of the default values; it then moves from installation screen to installation screen with minimum user input. The file is called RESPONSE.NI and is located in the SYS:\NI\DATA directory.

Using the RESPONSE.NI File To use the RESPONSE.NI file, perform the following steps:

Copy the RESPONSE.NI file from the original server either to a diskette or to another drive that's accessible by the server on which you are installing NetWare 5. Start the installation process, and in the Install Options window, press F3. Now enter the full path to the response file.

The installation program will now use the response file's values for the remainder of the installation. You can also manually add, remove or change values in the response file by editing it in a text editor, such as Microsoft's Notepad.

Sending a CoreDump to a Remote TCP/IP Host DBNET5.NLM (included with NW5SP3 in the \TOOLS\DBNET directory) allows you to create a coredump on a remote host, rather than on the local DOS partition, through the use of TCP/IP. Usually, DBNET5.NLM is loaded in the STARTUP.NCF or the AUTOEXEC.NCF files and works to present a new coredump destination option, "network," when using the .C command in the OS debugger of the abended server.

Its MLID configuration (which NIC's have IP bound, default router, etc.) is stored on the DOS partition in DBNET.CFG for use at debug time. You can also configure DBNET.CFG manually or with the DBCONFIG command (once DBNET.NLM is loaded).

The DBNET.NLM comes with a number of commands that you might find useful:

  • DBSTART Starts debug network

  • DBSTOP Stops debug network

  • DBMODULES Displays debug network modules

  • DBSTAT <IP|LSL|MLID> Displays debug network statistics

  • DBSTART Starts debug network

  • DBSTOP Stops debug network

  • DBMODULES Displays debug network modules

  • DBSTAT <IP|LSL|MLID> Displays debug network statistics

  • DBHELP Displays DBNET console commands

The host that wished to receive the coredump from DBNET needs to be running an agent called IMGHOST, which comes in two executable forms:

  • IMGHOST.NLM runs on a NW server

  • IMGHOST.EXE runs WinNT or Win95/98 (Win32 console application)

You can use DBNET in combination with DIAG500.NLM, which you can configure to automatically send a coredump at abend time by using the following command:

load diag500 -d network -h <destination_IP_address>

* Originally published in Novell AppNotes


Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Micro Focus