
Installing the Async Gateway
21
Novell Confidential
Manual (ENU) 21 December 2004
Gathering I/O Port Driver Information for NetWare
If you are installing the NetWare
®
Async Gateway, some additional information must be
determined:
Hardware Type:
If you load only one communication port driver, you do not need to define
a hardware type. If you load multiple port drivers, each driver must be identified by a unique
name referred to as a hardware type. The driver must be AIO compliant.
When two or more multiple IO boards are installed, list the hardware number assigned by
Novell to the AIO-compliant driver you have installed. For more information, including
driver names, their hardware type (number), and the number of ports they support, see
Appendix A, “Asynchronous Input/Output Drivers,” on page 101
.
Board Number:
If you load only one communication port driver, you do not need to define
a port number. If you load multiple drivers or add ports, you need a unique board number for
each port definition.
When two or more multiple IO boards are installed, you must provide a memory address
(usually d0000) and a unique port address when you load its driver.
You can obtain this information when you include these parameters on the command line
during loading. The load program displays the board number that it assigns to the IO board.
Use this board number for all the ports you configure for this board. This information is also
available in the Readme file or printed documentation for the IO expansion board.
Port Number:
If you load only one communication port driver, you do not need to define a
port number. If you load a single multiport communication driver (such as aioicomx.nlm), the
first port should be defined as 0. Subsequent ports that you define increase incrementally by
1. Assign one port per modem. Some drivers auto-detect the next available port when they are
loaded, and others do not, so you might have to keep track of the next available port.
If you cannot obtain the hardware type or board number from loading the IO board driver, you can
use aioterm.nlm to obtain it.
Determining Where to Install the Async Gateway Administrator Snap-In to
ConsoleOne
Async Gateway administration is performed through ConsoleOne
®
, version 1.3.6 or later. If
necessary, this can be downloaded from
Novell download site (http://www.novell.com/
downloads)
.
When you install the Async Gateway, the Gateway Administrator snap-in files are copied to a
ConsoleOne location that you specify. The Gateway Administrator snap-in files extend the
functionality of ConsoleOne to let you administer the Async Gateway.
You should install the Gateway Administrator snap-in files wherever the GroupWise
Administrator snap-in files are already installed. Different Gateway Administrator files are
installed depending on whether you are using the GroupWise 6.5 or 7.
x
version of the GroupWise
Administrator snap-ins. You can check the GroupWise Administrator snap-in version in
ConsoleOne. Click Help > About Snap-Ins > GroupWise Administration.
ASYNC CONNECTION AND MODEM WORKSHEET
Under
Item 4: Additional Information for NetWare
, provide the extra information required for the
NetWare Async Gateway.
Содержание GROUPWISE 7 ASYNC GATEWAY - INSTALLATION AND ADMINISTRATION
Страница 4: ...Novell Confidential Manual ENU 21 December 2004...
Страница 108: ...108 GroupWise 7 Async Gateway Installation and Administration Guide Novell Confidential Manual 99a 21 December 2004...
Страница 112: ...112 GroupWise 7 Async Gateway Installation and Administration Guide Novell Confidential Manual 99a 21 December 2004...
Страница 116: ...116 GroupWise 7 Async Gateway Installation and Administration Guide Novell Confidential Manual 99a 21 December 2004...
Страница 128: ...128 GroupWise 7 Async Gateway Installation and Administration Guide Novell Confidential Manual ENU 21 December 2004...