NetWare(R) MultiProtocol Router(TM) 3.0 README.TXT

Please make note of the following items:

- When configuring asynchronous PPP links using the  WHSMAIO driver, ensure 
  that the systems on each side of the asynchronous PPP link are configured
  to use the same asynchronous character maps (ACCMs).

- If you want to allow IBM's LAN Network Manager to manage the Source Route
  Bridge in NetWare MultiProtocol Router 3.0, you must use the latest version
  of LLC8022.NLM. This file is available on the NetWire(R) electronic bulletin
  board. See the text file, MPR.TXT in Library 8, for the location of
  this NLM(TM) file. 

  To access the NLM, do the following:

  1. Copy the NLM from NetWire to the SYS:SYSTEM directory on the server 
     that will be managed by IBM's LAN Network Manager.
  2. Load INETCFG and enable the LAN Network Management feature in the
     Source Route Bridge option.

- The IPX Protocol option in INETCFG includes the Set Get Nearest Server
  parameter. Configuring this parameter inserts the Set Get Nearest Server
  command in the INETCFG database. By default, this parameter is set to
  ON. 

  If your AUTOEXEC.NCF file currently contains a Set Get Nearest Server
  line, running INETCFG will cause a different Set Get Nearest Server line to
  be added to the INETCFG database. This line might conflict with the one in 
  your AUTOEXEC.NCF file. To resolve this, delete the Set Get Nearest Server 
  line from the AUTOEXEC.NCF file and use INETCFG to set the parameter to
  the desired value.

- Before unloading AURP, use Call Manager to delete any IP calls not in the
  In-Connected or Out-Connected state.

- When INETCFG transfers LOAD and BIND commands from the AUTOEXEC.NCF
  file, it does not transfer the LOAD BOOTPFWD line. The BOOTPFWD.NLM
  shipped with NetWare MultiProtocol Router 3.0 has a new command line that 
  must be configured through INETCFG. Delete the LOAD BOOTPFWD command from 
  the AUTOEXEC.NCF file and use INETCFG to configure BootP Fowarding. 
  BootP Forwarding is configured in TCP/IP Protocol Configuration under 
  Expert Configuration Options.  

- When configuring a PPP on-demand connection, make sure that
  
  + The value configured for the Remote System ID matches the server
    name of the remote system
  + The value configured for the Local System ID matches the server 
    name of the local system 

- If you are using more than one X.25 permanent virtual circuit (PVC) 
  and experience connection problems, then do the following:
  
  1. At the NetWare system console prompt, type "load x25con" and navigate 
     the menus to reach the "Active VC Summary" menu. Select the suspect PVC
     and verify that traffic exchange is occurring. If it is NOT, then 
     continue with Step 2. Otherwise, check the configuration and/or refer 
     to the NetWare MultiProtocol Router 3.0 System Messages and 
     Troubleshooting Guide.
  2. At the NetWare system console prompt, type "load callmgr" and inspect 
     the initial screen (the WAN call status screen).
  3. Select the problem WAN Call Destination, press <Del> to delete 
     the connection, and then press <Ins> to reestablish the connection, 
     choosing the same WAN Call Destination and protocol used previously.
  4. If connection problems persist, complete the following steps below 
     to update your X.25 software.

  The latest version of X25TSM.NLM is available on the NetWire electronic 
  bulletin board. See the text file, MPR.TXT in Library 8, for the location 
  of this NLM. 

  To access the NLM, do the following:

  1. Copy the NLM from NetWire to the SYS:SYSTEM directory. 
  2. Bring down and restart the server to load the latest NLM.

