NetWare Dealing with DBNET6.NLM

(Last modified: 18Aug2003)

This document (10066246) is provided subject to the disclaimer at the end of this document.


NetWare Dealing with DBNET6.NLM


Novell NetWare 6.0

Novell NetWare 5.1

Novell NetWare 4.2

Server Abends



Table of Contents

1.0  Overview
2.0  Loading DBNET
3.0  DBNET Configuration
    3.1  DBNET.CFG File
    3.2  DNS Name Resolution (RESOLV.CFG)
4.0  DBNET Console Commands
5.0  Required Support Modules
6.0  Network Boards Tested with DBNET4
    6.1  LAN Drivers Tested
    6.2  Ethernet
    6.3  Token Ring
7.0  Network Boards Tested with DBNET5:
    7.1  LAN Drivers Tested
    7.2  Ethernet
8.0  Legal Information
    8.1  Disclaimer and Copyright
    8.2  Trademarks

1.0  Overview

    DBNET.NLM creates remote core dumps to assist with
    troubleshooting when a server abends. There are two
    versions of DBNET: one for NetWare v4.11 (DBNET4.NLM),
    and one for NetWare v5.0 (DBNET5.NLM).

2.0  Loading DBNET

    When you load DBNET for the first time, the server
    should be running and the network board drivers with
    TCP/IP bound to them should be loaded.
    When DBNET is loaded for the first time, it tries to
    automatically configure itself by scanning for any
    network boards bound to TCP/IP and then chooses one
    that is on the same network as the default router found
    by TCPIP.NLM.
    If no default router is present, DBNET displays a list
    of boards bound to IP and prompts you for a default
    router (optional). If TCPIP is not loaded, DBNET scans
    all available network boards, displays a list of all
    boards that can support IP, and prompts you for an IP
    address, mask, and default router.  If no boards can be
    found DBNET returns an error message.

    Once DBNET is configured, it saves its configuration
    information into DBNET.CFG on the server's DOS
    partition, then it attempts to execute DBNET.CFG to
    load the debug time network driver.
    After DBNET is configured, the DBNET NLM can be loaded
    from STARTUP.NCF (Currently only DBNET4 can be loaded
    from STARUP.NCF.) or AUTOEXEC.NCF. If any changes to the
    server or the network configuration are made, DBNET
    should be reconfigured by executing the DBCFG console
    command or by editing the DBNET.CFG file manually.
    Note:  The current version of DBNET requires a Pentium
    class processor. The Pentium processors have an
    internal high-speed clock that is used by DBNET to time
    packet timeouts, etc.
    The AMD K5 and K6 processors also support this clock;
    however, the latest version of DBNET has not been
    tested with the AMD processors. Without a high speed
    clock, packet retrying can be slower or erratic.

3.0  DBNET Configuration

 3.1  DBNET.CFG File

      DBNET users the DBNET.CFG configuration file to load
      and configure the debug MLID (LAN driver) for use at
      debug time.
      The DBNET.CFG sections and key words are as follows
      (case sensitive):

       Section '[dbmlid]':

               'addr' - IP address of debug board.
               'mask' - IP network mask.
               'defr' - default IP router.

       Section: [dbmlid]:

               'mlid' - debug LAN module, along with command
                       line options.

       Section [dblsl]


               'min buffers' - minimum LSL buffers to allocate
                   default:  64
                   range:  64 - 256

               'max buffers' - maximum LSL buffers to allocate
                   default: 128
                   range:  128 - 256

               'buffer size' - LSL buffer packets size in bytes
                    default: auto or 4277
                        (53 max MAC header (Token-Ring) 64
                        max IP header +  64 max TCP header
                        + 4096 packet data)
                   range: 572 (min MTU size) - 4277

           For most LAN drivers, this section is not
           required.  DBNET tries configure itself
           automatically. If a board is in use by the
           operating system -- meaning that the driver is
           loaded -- and has been selected by DBNET as the
           debug driver, DBNET sets the debug LSL buffer
           size to the Max Packet Size supported by the
           driver. If no driver can be found, the default
           Max Packet Size of 4277 is used.
           If DBNET is loaded from STARTUP.NCF, you can
           set the Buffer Size parameter to save on memory
           space. The Buffer Size can also be used to
           limit the Max Packet Size sent by the debug

           Some boards might not work with the dynamic LSL
           buffer allocation and you will need to set the
           min buffers parameter to a higher initial
           value. The DBNET command DBSTAT will show the
           debug LSL settings.

      A sample DBNET.CFG configuration file follows:

           mlid=CPQNF3.LAN NAME=CPQ_EII FRAME=Ethernet_II

 3.2  DNS Name Resolution (RESOLV.CFG)

      DBNET reads the DNS file for TCPIP.NLM from
      SYS:\ETC\RESOLV.CFG, for its domain name resolution
      parameters. DBNET looks for the 'domain' and
      'nameserver' lines in RESOLV.CFG.

4.0  DBNET Console Commands

    DBHELP                  Displays DBNET console commands.
    DBCONFIG                Configures debug network.
                            This command is executed the first
                            time DBNET loads to set up DBNET.CFG
                            on the NetWare DOS partition.
                            Whenever there is a change to the
                            network boards loaded by the OS or
                            changes to the TCP/IP address
                            assigned to those boards, DBCFG
                            shoud be executed manually to
                            reconfigure DBNET.CFG.  DBNET.CFG
                            can also be edited manually (see
                            section 3.0 DBNET Configuration).
    DBSTART                 Starts debug network.
    DBSTOP                  Stops debug network.
    DBMODULES               Displays debug network modules.
    DBSTAT <IP|LSL|MLID>    Displays debug network statistics.

5.0  Required Support Modules

    New versions of DIAG411.NLM (v1.42) and DIAG500.NLM
    (v1.22), which are included with DBNET, allow for core
    dumps over a network device. The new DIAG detects if
    DBNET is loaded and present a new core dump option
    "NETWORK" when using the .C command in  the OS
    debugger.  DIAG also allows the "NETWORK" device and
    destination host IP address to be specified on its
    command line:
    LOAD DIAGxxx -d NETWORK -h
    When DIAG is loaded in this manner, its AUTODUMP option
    is enabled, allowing a core dump to be started
    automatically as the server traps or abends. After the
    core dump completes, the server will either restart or
    reboot itself, depending on how the Auto Restart After
    Abend parameter is set.  DIAG can be loaded either
    before or after DBNET.NLM
    DBNET also needs a core dump receiver. IMGHOST receives
    the core dump from DBNET. IMGHOST has two executable
    the server. IMGHOST.EXE is a Win32 console application
    which will run on Windows NT or Windows 95/98.
    The latest Winsock for NetWare 4.11 and a newer
    WSPIP.NLM for both NetWare 4.11 and 5.0 have also been
    included with DBNETx. IMGHOST.NLM/EXE requires Winsock.
    The NetWare 4.11 version is found in INSOCK.EXE.
    WS2_32.NLM (Winsock) also requires LOCNLM32.NLM to be
    loaded. Winsock is included with NetWare 5.

    The newer WSPIP.NLM module is included in NetWare 5
    Support Pack 3. WSPIP.NLM fixes the problem with the IP
    address in IMGHOST.NLM showing The IMGHOST.EXE
    still has this problem with the Win32 Winsock library.

6.0  Network Boards Tested with DBNET4
 6.1  LAN Drivers Tested

      MSM.NLM, v3.17, 1 July 1996
      ETHERTSM, v3.11, 3 July 1996
      TOKENTSM, v3.11, 3 July 1996
      NBI.NLM, v1.44, 2 July 1996
 6.2  Ethernet

      Novell NE2000, ISA (NE2000.LAN, v3.62, 5 July 1996)
      Compaq NetFlex-3, 10/100, PCI (CPQNF3.LAN, v2.41, 9
      April 1998)
      3Com 509 Etherlink ISA, PCI (3C5X9.LAN, v4.20j, 21
      Nov 1997)
      3Com 905B TX, 10/100, PCI (3C90X.LAN, v3.10, 26 May
      Intel E100B, 82557-Based, 10/100, PCI (E100B, v1.47,
      20 June 1996)
      SMC Ether Power II 9432TX, 10/100, PCI (SMC9432.LAN,
      v1.02, 10 Apr 1997;
      SMCPWR2.LAN, v1.06, 13 May 1998)
 6.3  Token Ring

      IBM Token Ring Shared RAM, ISA (TOKEN.LAN, v4.08, 22
      Oct 1997)
         - Won't initialize board (does not work well with polling)
      IBM Token Ring (Cricket Stick), PCI (IBMTRPO, v2.17,
      6 May 1998)
         - Needs to have Min Buffers parameter set to 40 in the LSL
           section of DBNET.CFG
         - Sometimes the board would not initialize in the debugger,
           and the core dump would need to be started again.
      IBM Streamer, PCI (IBMMPCO, v2.08, 23 June 1997)
      Madge Smart PCI Ringnode (CMDGODI.LAN, v2.09, 27 Feb
         - Works as dedicated board (DBNET.CFG will need to be
           edited). When using an OS board, sometimes the adapter would
           initialize, but would not send packets, even though it could
           receive them.
      Olicom OC-3137, PCI/II (OCTOK162.LAN, v4.11, 11 Nov
      Thomas Conrad TC4048, PCI (CPQTRPCI.LAN, v2.08, 11
      May 1998)

7.0  Network Boards Tested with DBNET5:
 7.1  LAN Drivers Tested

      MSM.NLM, v3.94, 1 March 1999 (NW5 SP2)
      ETHERTSM, v3.80, 1 March 1999 (NW5 SP2)
      TOKENTSM, v3.77, 5 March 1999 (NW5 SP2)
      NBI.NLM, v2.25, 30 Sept 1998 (NW5 SP2)

      The NetWare 5 Support Pack 2 version of the MSM,
      TSM, and HSM modules also work with with DBNET on
      NetWare 4.11.
 7.2  Ethernet

      Compaq NetFlex-3, 10/100, PCI (CPQNF3.LAN, v2.42, 10
      June 1998)
      Intel E100B, 82557-Based, 10/100, PCI (E100B, v4.39,
      12 January 1999)
      3Com 905B TX, 10/100, PCI (3C90X.LAN, v4.00, 14 Aug
      CNEAMD.LAN, 10/100, PCI, v1.39, 23 Jan 1998

8.0  Legal Information
 8.1  Disclaimer and Copyright

      Novell, Inc. makes no representations or warranties
      with respect to the contents or use of this
      documentation, and specifically disclaims any
      express or implied warranties of merchantability or
      fitness for any particular purpose. Further, Novell,
      Inc. reserves the right to revise this publication
      and to make changes to its content, at any time,
      without obligation to notify any person or entity of
      such revisions or changes.

      Further, Novell, Inc. makes no representations or
      warranties with respect to any software, and
      specifically disclaims any express or implied
      warranties of merchantability or fitness for any
      particular purpose. Further, Novell, Inc. reserves
      the right to make changes to any and all parts of
      Novell software, at any time, without any obligation
      to notify any person or entity of such changes.

      Copyright (C) 1999 Novell, Inc. All rights reserved.
      No part of this publication may be reproduced,
      photocopied, stored on a retrieval system, or
      transmitted without the express written consent of
      the publisher.
 8.2  Trademarks

      Novell and  NetWare, are registered trademarks of
      Novell, Inc. in the United States and other

      NE2000 and NetWare Loadable Module and NLM are
      trademarks of Novell, Inc.

      All third-party trademarks are the property of their
      respective owners.


For additional information on NetWare 6, please see the following solution.  TID #10064501 - NetWare 6 Readme Addendum


Document Title: NetWare Dealing with DBNET6.NLM
Document ID: 10066246
Solution ID: NOVL64141
Creation Date: 20Nov2001
Modified Date: 18Aug2003
Novell Product Class:NetWare


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.