CLIENT KIT README FOR SNMP (05/11/94)
To print this file to a local printer,
1. Insert the workstation diskette containing this file into
drive A: (or B:).
2. At the DOS prompt, type "A:" (or "B:") and press <Enter>.
3. At the DOS prompt, type "COPY READVLM.TXT PRN" and press
<Enter>.
NOTE: If you have a postscript printer, import this file into
a word processing application and print from the application.
------------------------------------------------------------------
CONTENTS
This document contains the following topics about SNMP on the
NetWare Client for DOS and MS Windows:
1.0 Introduction to Desktop SNMP
2.0 Components of Desktop SNMP
3.0 Enabling Desktop SNMP Services
3.1 Prerequisites
3.2 Procedure
3.3 Sample configuration file (HRMIB.INI) for HRMIB.EXE
3.4 Sample NET.CFG File for Desktop SNMP Services
4.0 Conventional Memory Usage
5.0 Unloading the Desktop SNMP Software
6.0 Where to Go from Here
1.0 Introduction to Desktop SNMP
Simple Network Management Protocol (SNMP) is an
industry-standard protocol for communication between a network
management console and the network devices that the console is
to monitor. This chapter explains how to enable desktop SNMP
services on your computer, and how to modify the NET.CFG file
to implement additional SNMP options.
The chapter is primarily for supervisors of networks in which
an SNMP-based network management system is implemented.
The Desktop SNMP agent provided with the NetWare Client
Kit 1.1, allows you to manage your NetWare clients from
Novell's NMS (NetWare Management System) and other
industry-standard SNMP management consoles.
2.0 Components of Desktop SNMP
The NetWare Client Kit 1.1 includes the following components
for the Desktop SNMP agent:
HRMIB.EXE - the Host Resources manager, which collects
information about a computer that is
running DOS on the network.
HRMIB.INI - the configuration file for the HRMIB.EXE
file.
WSSNMP.VLM - Desktop SNMP module, which includes support
for MIB-II System and SNMP groups
WSREG.VLM - MIB registration module
WSASN1.VLM - ASN.1 translation module
WSTRAP.VLM - Trap module
MIB2IF.VLM - MIB-II interface groups support
MIB2PROT.VLM - MIB-II support for the TCP/IP groups
STPUDP.COM - Transport provider module for UDP/IP
STPIPX.COM - Transport provider for IPX
These files are copied the client directory on your
computer (default is C:\NWCLIENT.)
NOTE: Refer to the documentation provided with the SNMP
management software for information on specific configurations
for the management software.
3.0 Enabling Desktop SNMP Services
You can set up Desktop SNMP on your client to act as an
SNMP agent for any SNMP-based management consoles.
3.1 Prerequisites
To set up Desktop SNMP Agent services on your client, you will
need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Modify the NET.CFG file to reflect the presence of
Desktop SNMP .VLM files, and then set the required .VLM
file options in the NET.CFG file. See section "IV,"
"Sample NET.CFG File for Desktop SNMP Services" in this
file.
þ Set the "TRAP TARGET" address of the NetWare Services
Management (NSM) consoles or other SNMP-based managers in
the NET.CFG file. See section "IV," "Sample NET.CFG File
for Desktop SNMP Services" in this file.
þ Modify the STARTNET.BAT file to load either STPIPX.COM or
STPUDP.COM.
þ Load the NetWare client software by running the
STARTNET.BAT file in the client directory.
NOTE: You must have either IPX or IP transport installed
on your system. IPX transport (IPXODI) is provided by the
NetWare DOS requester provided in the NetWare Client
Kit 1.1. IP transport for UDP/IP is provided by LAN
Workplace for DOS 4.1 (LAN Workplace). You can use both
types of transport on a single client.
3.2 Procedures
By default, desktop SNMP services are not enabled when you
install the NetWare client. To enable desktop SNMP services,
do the following:
1. Ensure that the Desktop SNMP files are copied to the
client directory (default is C:\NWCLIENT).
2. Modify the NET.CFG file to load the Desktop SNMP .VLM
file suite.
IMPORTANT: When the Desktop SNMP .VLM file suite is
loaded, the WSSNMP.VLM must be loaded first. The
WSTRAP.VLM and WSREG.VLM files must be loaded prior to
loading the WSASN1.VLM file.
To load the Desktop SNMP .VLM file suite, modify the
NET.CFG file on your client in either of the following
two ways:
a. To load Desktop SNMP in addition to the NetWare
DOS Requester software, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
b. To load only Desktop SNMP, without the NetWare
DOS Requester modules, add the following lines to
the NET.CFG file under the "NetWare DOS Requester"
section:
USE DEFAULTS = OFF
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
3. Modify client configuration files for setting up
Desktop SNMP. See "Desktop SNMP Option" in Appendix B of
"Workstation for DOS and MS Windows" for information and
details on how to set up and configure your client for
the following Desktop SNMP parameters:
þ Transport providers
þ MIB-II support
þ Community names
þ Asynchronous timeout
4. Modify the C:\NWCLIENT\STARTNET.BAT file to load the
Desktop SNMP transport files. Add the following commands
in the STARTNET.BAT after the line which loads the
VLM.EXE file.
If you are using IPX transport, add the following
line by typing:
STPIPX
If you are using UDP/IP transport, add the following
line by typing:
STPUDP
NOTE: You can add both commands if your client uses
both IPX and UDP/IP transport.
NOTE: If you are running LAN Workplace, make sure you are
do not load the SNMP.EXE file, provided with the LAN
Workplace package. The installation program for LAN
Workplace creates a file called "LANWP.BAT" that loads
the LAN Workplace software. Check this file for a line
reading "SNMP." It should be listed directly following
the line "TCPIP." If the SNMP line is present, delete it
or comment it out.
5. Use DOS SET command at the system prompt or in a batch
file to set the correct time zone for your area, as
follows:
SET TZ = time_zone
Refer to your DOS manual for the exact syntax for your
particular time zone.
If the time zone is not set in your computer's
environment, traps for SNMP may report an incorrect time.
6. Reboot your computer. The VLM manager will load the
Desktop SNMP .VLM file suite along with any other .VLM
files your client is configured to load.
The Desktop SNMP workstation support includes the
HRMIB.EXE and HRMIB.INI files. These files enable the console
to view data collected at each Desktop SNMP workstation. The
files are located in the client directory (default is
C:\NWCLIENT).
To enable the SNMP console to view data about a Desktop SNMP
workstation, you will need to perform the following tasks:
þ Install the NetWare Client 1.1 on your client computer.
þ Load the HRMIB.EXE software on the client you want data
collected from.
1. Ensure that the HRMIB.EXE and HRMIB.INI files exist
in your client directory (default is C:\NWCLIENT).
2. Load the HRMIB.EXE file by typing
HRMIB.EXE
NOTE: Ensure that the DOS SNMP Agent software is set up
and loaded on your client before loading the HRMIB.EXE
file.
3. Configuring the HRMIB.INI File
The Host Resources MIB does not return information about
devices attached to the host computers, such as printers,
modems, and tape drives. If the network management
console is to view details of such devices, you must
list them in the HRMIB.INI file.
The HRMIB.INI file is located in the directory to which
you installed the NetWare client (C:\NWCLIENT by default)
on your computer. Use a ASCII text editor to enter a
short description of each device. For example:
3.3 Sample configuration file (HRMIB.INI) for HRMIB.EXE
# List of all printers connected to host
[printers]
HP LaserJet IIIp on LPT1:
NEC P20 on LPT2:
# List of all modems connected to host
[modems]
Hayes Optima 144 on COM1:
# List of all tape drives connected to host
[tapes]
Colorado DJ10
HP 35480A SCSI DAT (4-8 GB)
# other devices obtained via DOS APIs
3.4 Sample NET.CFG File for Desktop SNMP Services
A sample of the NET.CFG for SNMP agent services is as follows:
Link Driver NE2000
PORT 300
INT 3
FRAME Ethernet_802.2
MEM D0000
NetWare DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = MIB2PROT.VLM
Desktop SNMP
enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Suzanne Morley x893"
sysLocation = "Building 2"
sysContact = "suzanne@acompany.com"
snmpEnableAuthenTraps = on
Transport Provider IPX
trap target = ab123456:0123456789ab
trap target = cd654321:ba9876543210
Transport Provider UDP
trap target = 999.88.77.66
trap target = 888.11.22.33
4.0 Conventional Memory Usage
If you are willing to trade conventional memory for
performance, you can load one or more Desktop SNMP .VLM files
in conventional memory.
To load all .VLM files in conventional memory, use the VLM /MC
switch when running the VLM manager.
To load a Desktop SNMP .VLM files in conventional memory,
place lines of the following form in the NET.CFG file:
Netware DOS Requester
VLM = vlm_name.VLM
LOAD LOW vlm_name = ON
For example, to load Desktop SNMP while loading the WSASN1.VLM
and WSREG.VLM files in conventional memory, place the
following lines in the NET.CFG file:
Netware DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
Load low WSREG = ON
Load low WSASN1 = ON
5.0 Unloading the Desktop SNMP Software
The following commands, issued in the order given, unload
Desktop SNMP.
NOTE: The VLM -u command unloads all VLM files, not just
Desktop SNMP.
1. Unload STPUDP if UDP/IP support has been loaded:
STPUDP -u
2. Unload STPIPX if IPX support has been loaded:
STPIPX -u
3. Unload all VLM files:
VLM -u
IMPORTANT: Always unload the modules in reverse order from the
order in which you loaded them. For example, if you loaded the
VLM manager followed by STPUDP and then STPIPX, you must
unload them as follows:
STPIPX -u
STPUDP -u
VLM -u
Unloading the modules in any order other than reverse order
causes an error.
6.0 Where to Go from Here
After you have completed the initial configuration of the
desktop SNMP agent, you can further modify the Desktop SNMP
options in the NET.CFG file to meet your specific network
requirements. Refer to"Using the Desktop SNMP NET.CFG Option
for DOS and MS Windows Workstations" in the following section
for a description of these modifications.
7.0 Using the Desktop SNMP NET.CFG Option for DOS and MS Windows
Workstations
Use this option to manage MIB-II support and communities for
SNMP desktops on NetWare and Personal NetWare networks. For
transport providers used with SNMP desktops, see "Using the
Transport Provider IPX | UDP NET.CFG Option for DOS and MS
Windows Workstations."
Available Parameters and Settings for the Desktop SNMP Option
This option has the following parameters and settings:
asynchronous timeout=number
monitor community=["name | public | private"]
control community=["name | public | private"]
trap community=["name | public | private"]
enable monitor community=[specified | any | off |
omitted]
enable control community=[specified | any | off |
omitted]
enable trap community=[specified | off | omitted]
sysname="name"
syslocation="location"
syscontact="contact"
snmpenableauthentraps=[on | off]
Asynchronous Timeout
ASYNCHRONOUS TIMEOUT number
Use this parameter and setting to monitor and control your
SNMP connections.
When an SNMP manager requests information from a managed
object, the desktop SNMP waits a set amount of time before
attempting to cancel requests it has made against managed
objects.
Syntax asynchronous timeout=number
Default 20
Examples For example, to have Desktop SNMP wait 35
system ticks (approximately 2 seconds) before
attempting to cancel a request, you would place
the following lines in your NET.CFG file:
desktop snmp
asynchronous timeout=35
The timeout number is in ticks (18.21 ticks per second on IBM
PCs and compatibles).
Community Names
Desktop SNMP provides default community names for the monitor
(read-only) and control (read/write) communities, as well as
a default community used for traps. Desktop SNMP and other
SNMP entities use these names for access control. The
community name contained in a request message from an SNMP
management station must match the name expected by Desktop
SNMP. Examples of NET.CFG Files Using the Community Name and
Types" for examples of complete files.
If Desktop SNMP receives a request protocol data unit (PDU)
whose community name is not authorized, it does not respond to
the request. For example, suppose the control community name
is "Secret," and Desktop SNMP receives a SETRequest PDU with
a community name of "Public." Desktop SNMP discards the
SETRequest UDP and does not respond to the UDP. However,
Desktop SNMP does send an authentication trap to the trap
targets if snmpEnableAuthenTraps is ON.
A community name can be any arbitrary, case-sensitive ASCII
string up to 32 characters in length. It can include any
characters except space, tab, open square bracket ( [ ), equal
sign ( = ), colon ( : ), semicolon ( ; ), double quotation
mark ( " ), or number sign ( # ). Community name strings are
case-sensitive. Always enclose the community name string in
double quotation marks.
In the Desktop SNMP section of the NET.CFG file, you can
define three communities, as described in the following table:
Desktop SNMP Option Parameters for Community Names
Parameter Explanation
monitor community Describes the read-only community
(the community that is allowed to do
GET and GET NEXT operations). The
default value is "Public." When the
monitor community is disabled, all
read access is disabled.
control community Describes the read/write community
(the community that is allowed to do
SET operations). Any community name
established for read/write access is
also valid for read-only access. The
default value is "Public." When the
control community is disabled, all
write access is disabled.
trap community Describes the community name used for
traps. The default value is "Public."
When the trap community name is
disabled, Desktop SNMP does not send
traps.
MONITOR COMMUNITY ["name | public | private"]
Use this parameter and setting to specify the monitor
community name.
Syntax monitor community=["name | public | private"]
Default public
Examples To specify the monitor community as "Private,"
you would place the following lines in your
NET.CFG file:
desktop snmp
monitor community="private"
CONTROL COMMUNITY ["name | public | private"]
Use this parameter and setting to specify the control
community name.
Syntax control community=["name | public | private"]
Default public
Examples To specify the control community as "secret,"
you would place the following lines in your
NET.CFG file:
desktop snmp
control community="secret"
TRAP COMMUNITY ["name | public | private"]
Use this parameter and setting to specify the trap community
name.
Syntax trap community=["name | public | private"]
Default public
Examples To specify the trap community as "AgentTrap,"
you would place the following lines in your
NET.CFG file:
desktop snmp
trap community="AgentTrap"
Community Types
Community types can also be disabled. When a community type is
disabled, no management entity can access information for that
community. For example, if you disable the control community,
no one can use Desktop SNMP to do SET operations against the
data it manages. "Examples of NET.CFG Files Using the
Community Name and Types" for examples of complete files.
Desktop SNMP reads the community definition as follows,
depending on the Enable CommunityType Community line:
Desktop SNMP Option Settings for the
Community Type Parameters
Setting Explanation
Omitted If "Enable Community" is set to
"Omitted" for a community type,
Desktop SNMP defaults to "Specified"
for that community and looks for a
line defining a CommunityName for the
community. If no CommunityName is
specified, Desktop SNMP defaults to
public.
Off If "Enable Community" is set to "Off"
for a community type, access for that
community is disabled. The line
defining the CommunityName can be
omitted. If the line is present,
Desktop SNMP ignores it.
Any If "Enable Community" is set to "Any"
for a community type, any community
string can be used to gain access.
The line defining the communityName
can be omitted. If it is present,
Desktop SNMP ignores it.
For trap community strings, the "Any"
option is not applicable. If you
specify "Enable Trap Community Any,"
Desktop SNMP interprets the line as
if the community type were specified.
Specified If "Enable Community" is set to
"Specified" for a community type,
Desktop SNMP uses the only the
specified CommunityName for that
community type. If none is specified,
Desktop SNMP defaults to "Public."
ENABLE MONITOR COMMUNITY [specified | any | off | omitted]
Use this parameter and setting to enable the settings for the
monitor community.
Syntax enable monitor community=[specified | any | off
| omitted]
Default specified
Examples To enable the monitor community as "Private"
only, you would place the following lines in
your NET.CFG file:
desktop snmp
enable monitor community=specified
ENABLE CONTROL COMMUNITY [specified | any | off | omitted]
Use this parameter and setting to enable the settings for the
control community.
Syntax enable control community=[specified | any | off
| omitted]
Default specified
Examples To enable full access to the control community
"Secret," you would place the following lines
in your NET.CFG file:
desktop snmp
enable control community=any
ENABLE TRAP COMMUNITY [specified | off | omitted]
Use this parameter and setting to enable the settings for the
trap community.
Syntax enable trap community=[specified | off |
omitted]
Default specified
Examples To disable the trap community name "AgentTrap,"
you would place the following lines in your
NET.CFG file:
desktop snmp
enable trap community=off
Examples of NET.CFG Files Using the Community Name and Types
To use the default trap community, allow any community name to
be used for read access, but set the read/write community name
to secret, place the following lines in NET.CFG:
desktop snmp
enable monitor community=any
enable control community=specified
control community="Secret"
To disable all traps and use the default values for the
monitor and control communities, place the following lines in
NET.CFG:
desktop snmp
able trap community=off
To specify a NULL string for the control community and use the
default values for the monitor and trap communities, place the
following lines in NET.CFG:
desktop snmp
enable control community=specified
control community=""
Setting a NULL string is the same as setting the Enable
Community line to Off.
To allow only the private community to have access, and set
the community name for traps to "AgentTrap," place the
following lines in NET.CFG:
desktop snmp
enable monitor community=specified
monitor community="private"
enable control community=specified
control community="private"
enable trap community=specified
trap community="agenttrap"
To temporarily allow any community name to have read-only
access in the previous example, modify the lines in NET.CFG as
follows:
desktop snmp
enable monitor community=any
monitor community="private"
enable control community=specified
control community="private"
enable trap community=specified
trap community="agenttrap"
Desktop SNMP ignores the Monitor Community="private" line
until you reset the Enable Monitor Community line to
Specified. This allows you to temporarily change the setting
to Any or Off without deleting the specific community name.
MIB-II Support
Desktop SNMP automatically supports three MIB-II groups:
System and SNMP Groups
Interfaces Group
TCP/IP Groups (all other groups except the EGP and
transmission groups, which are not supported by Desktop SNMP)
System and SNMP Group
Desktop SNMP automatically supports two MIB-II groups, system
and SNMP. These groups provide SNMP management stations with
information about your workstation and about Desktop SNMP.
You can define some parameters for your workstation
environment in the NET.CFG file (or other defined
configuration file). The following table explains these
parameters.
Desktop SNMP Option Parameters
Parameter Explanation
sysname Use your user or login name, or your
TCP/IP hostname, if one is assigned.
syslocation Use the physical location of where your
workstation is located.
syscontact Use the real name of the person who should
be contacted if your workstation needs
maintenance.
snmpEnableAuthenTrap The final setting, snmpEnableAuthenTraps,
defaults to OFF. When set to ON, it
instructs Desktop SNMP to send a trap
message if someone without proper access
tries to use SNMP to get or change
information that SNMP manages.
Each of these parameters is optional and can be used in groups
or separately. The first three parameters define information
that can be retrieved by SNMP management stations or reported
in SNMP traps.
Always enclose the Name, Location, or Contact information
in quotation marks.
Following is an example:
desktop snmp
sysname="Suzanne Morley x893"
syslocation="Building 2"
syscontact="suzanne@acompany.com"
snmpenableauthentraps=on
SYSNAME "name"
Use this parameter and setting to inform the SNMP manager of
your username.
Syntax sysname="number"
Default None
Examples To notify the SNMP manager of your username
"Suzanne," you would place the following lines
in your NET.CFG file:
desktop snmp
sysname="Suzanne"
SYSLOCATION "location"
Use this parameter and setting to inform the SNMP manager of
the physical location of you workstation.
Syntax syslocation="location"
Default None
Examples To notify the SNMP manager that your
workstation is in "Building 2," you
would place the following lines in your NET.CFG
file:
desktop snmp
syslocation="Building 2"
SYSCONTACT "contact"
Use this parameter and setting to inform the SNMP manager of
your workstation's system administrator.
Syntax syscontact="contact"
Default None
Examples To notify the SNMP manager that the name of
your workstation's system administrator is "Bob
Jones" at extension "x324," you would place the
following lines in your NET.CFG file:
desktop snmp
syscontact="Bob Jones x324"
SNMPENABLEAUTHENTRAP [on | off]
Use this parameter and setting to instruct the Desktop SNMP to
send a trap message if someone without proper access tries to
use SNMP to get or change information that Desktop SNMP
manages.
Syntax snmpenableauthentrap=[on | off]
Default Off
Examples To increase security on your workstation,
enable the Desktop SNMP to send a trap message
to the manager by placing the following lines
in your NET.CFG file:
desktop snmp
snmpenableauthentrap=on
Interface Group
Desktop SNMP provides a separate VLM file, MIB2IF.VLM, that
supports the interfaces group. This group provides information
about your network connection, such as the number of packets
transmitted and received and whether it is ethernet or token
ring.
Add the following line to the Netware DOS Requester section of
NET.CFG:
netware dos requester
vlm=mib2if.vlm
Always place the MIB2IF.VLM line after the lines that load the
Desktop SNMP VLM suite.
TCP/IP Group
Desktop SNMP also provides a separate VLM file that supports
the remainder of MIB-II. MIB2PROT.VLM provides MIB-II support
for the TCP/IP groups (all groups except interface, system,
and SNMP, which are supported by other VLM files, and EGP and
transmission, which are not supported). Load this VLM when you
are using the TCP/IP stack from LAN WorkPlaceø.
Always place the MIB2PROT.VLM line after the lines that load
the Desktop SNMP VLM suite.
Example of NET.CFG File Including Each Group Support
On a workstation where the NetWare DOS Requester and
comprehensive MIB-II support are both loaded, the entire
Netware DOS Requester and Desktop SNMP sections of NET.CFG
might read as follows:
netware dos requester
vlm=wssnmp.vlm
vlm=wstrap.vlm
vlm=wsreg.vlm
vlm=wsasn1.vlm
vlm=mib2if.vlm
vlm=mib2prot.vlm
desktop snmp
sysname="Suzanne Morley x893"
syslocation="Building 2"
syscontact="Suzanne@acompany.com"
snmpenableauthentraps=on
Using the Transport Provider IPX | UDP NET.CFG Option for DOS and
MS Windows Workstations
The Desktop SNMP transport providers, STPIPX.COM and STPUDP.COM,
read the configuration file to discover trap targets on NetWare
networks. You can specify a separate configuration file for each
transport provider when you load it. The following sections
describe trap target configuration and configuration file
specification.
Use this option to specify the trap target address for your SNMP
desktops. This option has the following parameter and setting:
transport provider ipx | udp
trap target=ipxaddress | ipaddress
TRAP TARGET ipxaddress | ipaddress
Trap targets define the addresses to which SNMP sends SNMP traps.
To receive traps sent by Desktop SNMP, make sure your management
station address is listed in the IPX (for IPX transport) or UDP
(for UDP/IP transport) section of the configuration file read by
the transport providers.
Configuration File
The transport providers read trap targets from the
configuration file. You can name a specific configuration
file, other than NET.CFG, for the transport providers,
STPUDP.COM and STPIPX.COM. (This configuration file should
match the one given in the VLM = command line.) To do this,
load them with the /c option in your STARTNET.BAT file, as
follows:
STPIPX [/c=[path]configurationFile.CFG]
STPUDP [/c=[path]configurationFile.CFG]
The /c option is also available when you load VLM.EXE.
When you specify the configurationFile.CFG without the path,
the transport provider searches starting at the current
directory.
When you do not use the /c option, the transport provider uses
the same configuration file used by the link support layer
module, LSL.COM. This is usually NET.CFG, unless a different
file is specified using the /c option when LSL is loaded.
For example, to load STPIPX with the SNMPNET.CFG configuration
file, use the following command:
STPIPX /c=SNMPNET.CFG
A trap target configuration for a machine using both IPX and
UDP/IP transport is shown in the following example:
transport provider IPX
trap target=ab123456:0123456789ab
trap target=cd654321:ba9876543210
transport provider UDP
trap target=999.88.77.66
trap target=888.11.22.33
By default, no trap targets are defined. If you do not configure at
least one trap target, Desktop SNMP does not send traps.
Syntax trap target=[IPXAddress | IPAddress]
Replace IPXAddress and IPAddress with the
management station address for IPX transport or
for UDP/IP transport.
Default None
Example To set your workstation for a management
station of "ab123456:0123456789ab," you would
place the following lines in your NET.CFG file:
transport provider ipx
trap target=ab123456:0123456789ab
------------------------------------------------------------------
DISCLAIMER
Novell, Inc., makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.
Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of recreating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you.
Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at
the discretion of Novell.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.