AVM NetWAYS/ISDN - CHAPTER 3 - LAN SITE


PRE-CHECK

Before you install NetWAYS/ISDN, the NetWare MultiProtocol Router for ISDN 
must be installed and configured in the LAN. If this requirement is met, you
can begin adding the remote access component to the MPR for ISDN.

INSTALLING NETWAYS/ISDN

	1. Insert your disk NetWare MultiProtocol Router for ISDN Disk in 
	   the disk drive of the router PC.
	2. Type
		load install
	   at the console prompt.
	3. Select Product Options from the Installation Options menu.
	4. Press Insert.
	5. The line you have to enter now depends on the version of the MPR
	   for ISDN you are using:

	   - If you are using a MPR for ISDN v2.0, enter
		A:mpr4isdn.20\<D channel protocol>

	     Example: A:mpr4isdn.20\EURO-D

	     The following D channel protocols are supported:  1TR6, ALINE
	     and EURO-D (DSS-1).  Enter the D channel protocol that is 
	     available at your ISDN access.
	   
	   - If you are using a MPR for ISDN v2.1, enter
			A:mpr4isdn.21\<D channel protocol>

 	     Example: A:mpr4isdn.21\EURO-D

	     The following D channel protocols are currently supported: 
	     1TR6, ALINE, VN3 and DSS-1. Enter the D channel protocol that 
	     is available at your ISDN access.

	6. Follow the instructions on the screen.


CONFIGURING NETWAYS/ISDN

- Installing a Port for NetWAYS/ISDN

Before:	Please make sure that the ISDN Expert Port Configuration of the port 
	or ports of the ISDN controller you want to configure for remote 
	access contains the following values:
	Layer 2 Protocol: X.75 SLP and
	Layer 3 Protocol: Transparent.

Then proceed as follows:
	1. Type
		load inetcfg
	   at the console prompt.
	2. Select LAN And WAN Board Parametersfrom the Internetworking Con-
	   figuration menu.
	3. Press Insert.
	4. Select ISDNWAYS from the Available Drivers menu.
	5. Select Add New LAN Board from the Available Cards For LAN
	   Driver ISDNWAYS menu.
	The LAN Board Configuration menu appears on the screen (fig. 3).
	The next steps will be described below.

- Configuring a Port for NetWAYS/ISDN


	ͻ
	 	    LAN Board Configuration              
	͹
	 Board Name:		NETWAYS-1-1              
	 						 
	 Board Status:		Enabled                  
	 Card Parameters:	board=AVMB1-1; port=1    
	 Frame Type:		Ethernet_II              
	ͼ
		Fig.3: LAN Board Configuration Menu

	1. Enter a name for the NetWAYS/ISDN driver in the Board Name field,
	   for example "NETWAYS-1-1".
	   In the above example, the first -1 stands for AVMB1-1 and the
	   second -1 for port=1, which means that the first port of the ISDN
	   controller "AVMB1-1" is used for transmission.
	2. Accept the default Enabled.
	3. Enter the following three parameters into the field Card Parameters:
	   - board=	The value for board= refers to the name of the ISDN
		        controller, the port or ports of which you want to 
			configure for incoming calls from remote PCs.  Enter
			the name you already assigned to the ISDN controller, 
			for example "board=AVMB1-1".
	   - port=	The value for port= specifies which port of the ISDN 
			controller is to be used.  Possible values are 1 and 2.
	   - node=	The default for node= is automatically set to 1 
			(node=1). This means that you do not have to configure
			this value in the "Card Parameter" field if you want to
			accept the default.  It can be configured otherwise if
			required.  Please note that the value for node= must
			always differ from the value configured for Node
			Address in the NET.CFG file of the remote PC or PCs.
			Otherwise this would lead to IPX address conflicts.
	4. Enter Ethernet_II in the Frame Type field.
	5. Press ESC and save this configuration.

	   The Configured LAN and WAN Boards menu appears on the screen: 
	   The driver "NETWAYS-1-1" is now the driver for the first port of 
	   the AVM ISDN Controller:

	ͻ
		     Configured LAN and WAN Boards            
	͹
	  Board Name	Driver	    Frame Type	     Status   
	  NETWAYS1-1	NETWAYS	    Ethernet_II      Enabled  
	ͼ

		Fig. 4:	Configured LAN and WAN Boards 	Menu

	6. Press ESC to go back to the main menu and go to the following 
	   section.

- Binding Protocols to NetWAYS/ISDN

After the port has been configured for remote PC access, you have to bind 
the protocol or protocols you want to use for communication between the 
remote PC and the LAN to the configured NetWAYS/ISDN driver.
The binding of protocols to a configured NetWAYS/ISDN driver is shown for 
the IPX protocol

Note: If you wish to use TCP/IP in addition to IPX, both protocols have to
      be bound to the respective board (NETWAYS-1-1, etc.).


Examples for IPX and TCP/IP are given in Appendix A of the NetWAYS/ISDN manual,
section "Protocol Bindings".

Proceed as follows:
	1. Select Protocol Attachment To Board.
	2. Press Insert.
	3. Select IPX from the displayed options.
	4. Select NETWAYS-1-1 from the boards shown on the screen.
	5. Enter a unique network number into the field IPX Network Number 
	   e.g. "1000".
Important: To avoid IPX address conflicts, the IPX Network Number used here 
	   must be unique; i.e. it must neither be used in the pool of 
	   Network Numbers for WAN Links nor as an Internal Network Number 
	   in your LAN.
	   Please note further that you allocate a unique network number to 
	   each NetWAYS/ISDN driver you configure.


	6. Press ESC and save the configuration.
	7. The configuration is complete when all ports have been configured
	   and all protocols you want to use (IPX and/or TCP/IP) have been
	   bound to NetWAYS/ISDN.
	   If you only want to configure one port for incoming calls from
	   remote PCs and only want to use the IPX protocol, the configuration
	   is complete.  Go to step 8.
	   If you want to configure more than one port for incoming calls 
	   from remote PCs, follow the above instructions for each of the
	   ports.  Then go to step 8.

Note: Please note that all ports configured for NetWAYS/ISDN as described 
      above can only be used for remote PC access via ISDN.
      Remote access and wide area connections cannot be managed simultaneously.
      If a port configured for NetWAYS/ISDN is to be used again for wide 
      area connections, you have to select the NetWAYS/ISDN driver from the 
      list "Configured LAN and WAN boards" and change the Board Status from 
      Enabled to Disabled.  The corresponding port of the ISDN controller 
      is now ready to manage wide area connections again.


	8. Leave the NetWare environment and start the server or router again.  NetWAYS/ISDN is now installed on the server and is ready to receive calls from remote PCs.

Important: Please note that every time you change or extend the configuration 
 	   of NetWAYS/ISDN, the file server or router PC must be rebooted.  
	   This is true for changes or extensions of the port configuration 
	   as well as for changes in protocol binding to NetWAYS/ISDN drivers.


OTHER CONFIGURATION POSSIBILITIES

- Call Acceptance

This parameter may be configured in the ISDN Expert Port Configuration and 
specifies for each port of an ISDN controller whether an ISDN specific 
security check with automatic call back is carried through or not.  Thus 
you may specify whether each remote PC is allowed to access this port or 
whether only those users are allowed access who have their own ISDN Call 
Destination entry in the WAN Call Directory.

If you configured the port of an ISDN adapter for remote access with Net-
WAYS/ISDN, the remote access connections are treated like the WAN connections 
before.

If you selected Accept All Numbers, all remote PCs are allowed access.

If you configured Accept Only Registered Numbers, only those remote PCs 
listed in the WAN Call Directory are allowed to access the LAN.  If a remote 
client wants to access this port, the MPR for ISDN will check the incoming 
number and automatically call back the remote PC.

For information on how to make an ISDN Call Destination entry see the 
NetWare MultiProtocol Router for ISDN Supervisor's Guide, p. 2-15.

Important: Never configure "Automatically" for "Connect To Destination" 
	   in an ISDN Call Destination entry for a remote PC.  The MPR for
	   ISDN of the LAN would then permanently try to establish a connection
	   to the remote PC, which may lead to very high ISDN connection
	   charges.

Please pay attention to the configuration examples in Appendix A of this manual.

Note: The entries Inactivity Timeout, Disconnect Timeout, Channel-On-Demand 
      and Bundling are ignored in the ISDN Call Destination Configuration.
      When the MPR for ISDN deactivates an ISDN connection physically or 
      physically and logically (Inactivity Timeout, Disconnect Timeout), it 
      accepts the corresponding values set in the NET.CFG file on the remote 
      PC. 














Copyright AVM GmbH, 1994