| |
This topic contains the following sections:
To isolate and resolve problems with NetWare Link/PPP, complete the following steps:
Check the Status option in NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > select a port) to verify that the port is enabled.
For ports configured as ISDN connections, verify that the ISDN address and the ISDN subaddress entered for the interface are correct.
Verify that the Inbound Call Processing option is enabled in NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > Authentication Options).
Verify that the WAN board driver and PPPTSM are loaded by reading the CONSOLE.LOG file. You can also enter modules at the console prompt. The system returns the names of modules that are loaded.
Verify that the desired protocols are bound to the WAN interface by entering CONFIG at the server prompt.
Use MONITOR to verify that LCP and the appropriate NCP (IPCP, IPXCP, ATCP, or BRIDGECP) are running. Select the appropriate interface under LAN/WAN Information and look under the custom statistics to verify that the desired NCP is in state 9 (Open).
Verify your software configuration with back-to-back testing, as described in Back-to-Back Testing in the Overview documentation. If the test is successful, the interfaces are ready for use.
Verify that the hardware is set up properly, as described in Verify the Proper Setup of Connecting Hardware.
Verify that the modem is set up properly for initialization, as described in Verify that the Modem is Set Up Properly for Initialization.
Verify that the modem initialized properly, as described in Verify that the Modem Initialized Properly.
This section lists checkpoints for the hardware required for both on-demand connections (modems) and permanent connections (crossover cables, modem eliminators, or leased lines).
To verify connections that use modems, complete the following steps:
Verify that the modem is receiving power.
Check the phone cables.
Check the cables to the WAN board.
To verify connections that use permanent links connected by crossover cables, modem eliminators, or leased lines, complete the following steps:
Verify that both Data Set Ready (DSR) and Data Carrier Detect (DCD) signals are active.
There might be lights for these signals on the devices indicating that the signals are active. If the signals are active, go to Step 6 . Otherwise, continue with the next step.
Load MONITOR at the NetWare console.
Select the LAN/WAN Information option and select the appropriate WAN port.
This unique address is displayed in the window that appears after the interface is selected in MONITOR. To determine the node address that is assigned to a specific port, enter CONFIG at the NetWare console and look at the node address listed below the desired port. The LSL board number, which is the first four digits of the node number, can also be used to identify the port.
Check that the DCE Signal - DSR statistic is in state 1 and the DCE Signal - DCD option is in state 0 before the call is initiated.
After the call is made, DCD should be in state 1.
For synchronous ports, verify that a clock is supplied.
Crossover cables used with synchronous ports require that the transmit clock is generated internally. Typically, the transmit clocks for modems, DSU/CSUs, and modem eliminators are supplied by the DCE device.
Verify that the PPP port is not connected to an X.25 or frame relay network access point.
In such a case, the driver is functional, but PPP receives invalid frames. PPP discards these frames, and the frames sent by PPP are also discarded by the switch.
Verify that the crossover cable cross-connects the signals, as described in Back-to-Back Testing in the Overview documentation.
To verify connections for outgoing calls that use permanent links connected by crossover cables, modem eliminators, or leased lines, complete the following steps:
Load NIASCFG to verify that the WAN call destination record has the correct phone number (parameter path: Select Configure NIAS > Protocols and Routing > WAN Call Directory > Selected LAN/WAN Driver).
Calls going through a PBX might require a 9 dialed first.
For calls dialed from a phone line within the same PBX, verify whether only the extension is required.
For a call made in Data Terminal Ready (DTR) Dialed mode (the modem dials the preconfigured number), pulse dialing is generally required.
Usually, an internal PBX does not support pulse dialing. If this is the case, use an outside line.
For calls dialed from an external line to an extension on an internal PBX, verify that the extension can be reached without the intervention of an operator.
If you are using AT commands and your modem is not DTR controlled, you must specify the type of modem attached to the port in the Modem/DCE Device field when you configure a port through NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces). This option selects a modem initialization script that is stored as an .MDC file in the SYS:SYSTEM\ directory. For information on these files and the modem vendors to which they correspond, refer to Table 15 .
These initialization scripts are sent to the corresponding modem under the following circumstances:
For an initialization script to work, several elements must be set up properly. To verify the modem setup, complete the following steps:
Verify that the correct cables are attached to the modem.
Specify the correct modem in the Modem/DCE Device type (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > a specific PPP interface > Modem/DCE type).
If you specify the wrong modem or neglect to specify a modem, it is very unlikely that the modem will initialize correctly. Look on the front of the modem or underneath for the model number. If there is no exact match, select a simpler modem from the same manufacturer.
If you have a modem that is not supported in the list of modems in the Modem/DCE Device types, try Hayes compatible for a short-term solution. Also, refer to the WWW location
http://support.novell.com.
In the long term, it is better to create your own modem script. Refer to Create or Change a Modem Script for details.
Verify that the interface speed configured in NIASCFG is accepted by the modem (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > a specific PPP interface > Interface Speed).
Use the highest interface speed your modem supports without excessive CRC errors. Refer to the modem manual to determine the supported interface speeds. Often this information is difficult to find; therefore, experimenting with different values might be the easiest way to determine the supported interface speeds. Follow the instructions in Verify Your Interface Speed.
For a port using the WHSMAIO (WAN HSMTM [Hardware Specific ModuleTM ] Asynchronous Input/Output) driver, verify that the Interface Speed option is set to a speed that the board's UART is capable of handling.
For example, if you are using AIOCOMX, one of the last lines displayed during initialization states the speed, in bps, that is acceptable to the UART. For the 16450 UART, this rate is 2,400 bps. Therefore, if you use an interface speed greater than 2,400 with a 16450 UART, the WHSMAIO driver does not load. To determine which UART is in your PC, enter LOAD AIOCOMX at the console. If AIOCOMX is already loaded, enter UNLOAD AIOCOMX at the console prompt and then load it again.
If the modem does not initialize properly after you have completed this procedure, the initialization script might be the source of the problem and you must create your own script. Refer to Create or Change a Modem Script for details.
To verify that you are using the correct interface speed, complete the following steps:
Change the interface speed in NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > a specific PPP interface > Interface Speed).
Restart the server or issue the REINITIALIZE SYSTEM command from the console or NIASCFG.
Watch the initialization in PPPTRACE to verify that the interface speed is acceptable.
If the modem replies OK after the issuance of each AT command from PPP, the speed is probably correct.
If you are still uncertain about the interface speed, or if the modem replied OK after a large group of AT commands, decrease the interface speed and repeat Step 2 and Step 3 . Keep the following points in mind:
Most modems require that the interface speed be the same on both ends of the connection.
Some modems (those without automatic speed buffering or connect speed functionality) require that the Interface Speed option be the same as the connect speed. To check the connect speed, watch in PPPTRACE as a connection is made. This speed can change between (or during) calls, according to the quality of the phone lines.
If you are using a high-speed WAN board (such as Synchronous/+ or NW2000) and the modem accepts only a low interface speed (4,800 or lower), the performance is poor. The best solution is to use a faster modem. However, even with fast modems, bad phone lines cause low connect speeds.
To verify that the modem initialized properly, complete the following steps:
Verify that the AA light on the front panel of the modem is on.
This is generally, but not always, an indication that the initialization script worked. Most, but not all, modems have this light. If this light is on, the initialization script probably worked and the modem should function properly.
The first commands sent by the router are a <CR> and +++ATE1H0. DTR is then toggled on the modem. After the +++ATE1H0 command, the modem should issue the response <CR><LF> OK<CR><LF> or OK<CR><LF> .
Verify that the modem issued the OK response.
If this OK response is not sent by the modem and the modem has been set up properly, as described in Verify that the Modem is Set Up Properly for Initialization the modem might be the source of the problem.
If you have another modem of the same type, try using it. If it works, then the first modem was faulty. You can also use a communications package to check whether the modem is functional.
If the modem returns OK to the +++ATE1H0 command at a given interface speed, you must verify that the commands sent to the modem are understood by the modem.
When a line of commands is sent, there should be a response for every few lines sent.
If there is no response, the interface speed might be too high. If there is still no response at the lowest interface speed, recheck the modem setup. If you cannot resolve the problem, try a different modem.
If you see a receive line that has an ERROR response, one of the settings in that line is not understood by the modem. Here is an example:
snd ATE0N1Q0V1X4&C1&D2&Q5&U0&K0&L0&R0rcv ERROR
To correct this error, refer to the modem manual to find out which command is not supported by the modem. In the previous example, the &U0 command was not in the manual and was not supported by this modem. In some cases, an update from the manufacturer might be required to support this parameter. Decide whether you want to get an update or omit the parameter and continue. If you choose to omit the parameter, follow the instructions described in Create or Change a Modem Script.
The routing software requires that the modem raise a DSR signal.
If the modem does not raise this signal, the initialization script appears to finish successfully, but any calls originated from this interface go into an Out-Queued state in CALLMGR and are never made. You can simulate a DSR signal by setting the Simulate DSR option in NIASCFG to Yes (parameter path: Select Configure NIAS > Protocols and Routing > Network Interfaces > Physical Options). Alternatively, you can use the AT&S0 command to force the modem to raise DSR. However, this command is not supported by all modems. To send this command to the modem, follow these instructions:
When you configure a port through the Network Interfaces option in NIASCFG, you must specify the type of modem attached to the port in the Modem/DCE Device field. This option selects a modem initialization script that is stored as an .MDC file in the SYS:SYSTEM\ directory. Table 15 lists the modem script files in this directory.
Table 15. Modem Script Files
You can use the new Windows-based modem script tool WMDMMGR to edit these script files or to create new modem scripts.
The following is an example of an error resulting from the execution of a sample modem script.
snd ATE0N1Q0V1X4&C1&D2&Q5&U0&K0&L0&R0rcv ERROR
In this example, the &U0 command is not supported by the modem; therefore, the following steps must be completed to correct the script:
Copy the modem script from SYS:SYSTEM to another location to make modifications.
Start the Windows-based program WMDMMGR.
Select File > Open, then select the modem script file containing the modem definition.
Select the modem script containing the &UO command and make modifications.
Select File > Save, then copy the updated file back to SYS:SYSTEM.
Enter REINITIALIZE SYSTEM to reload the new script.
Try to initialize the modem again with PPPCON, then use PPPTRACE to determine whether the new script worked.
| |