Information Technology Reference
In-Depth Information
Table 9-8 outlines the problem that might cause this symptom and describes solutions to that problem.
Table9-8
ARA: Connection Hangs After “Communicating At...” Message
Possible Problems
Solution
MNP4 Link
Request packets
sent by client ARA
stack are responded
to by the serving
modem instead of
the ARA server
1.
Check the version numbers of the ARA software on the
client and the Cisco IOS software on the access server.
If you are using ARA version 1.0 or Cisco IOS software prior
to Release 10.2, it is advisable to upgrade to ARA 2.0 and
Cisco IOS Release 10.2 or later. ARA 2.0 modifies the framing
of MNP4 Link Request packets, allowing them to be passed to
the access server rather than responded to by the serving
modem.
MNP4 Link
Request packets
sent by client ARA
stack are responded
to by the serving
modem instead of
the ARA server
(continued)
2.
If you cannot upgrade your software, try modifying the
behavior of the modem to use a LAPM-to-No Error
Correction fallback instead of a LAPM-to-MNP4-to-No
Error Correction fallback. The modem no longer listens for
and respond to MNP4 messages, allowing MNP4 packets to
reach the access server.
Note:
Many modems cannot be configured in this manner.
3.
If your modem does not use LAPM error correction, it
might be possible to modify
all
ARA client scripts to
extend the 500 ms pause before exiting. Configure an
additional delay that takes into account the behavior of the
serving
modem.
ARA: Cannot Send or Receive Data over ARA Dialin Connection
Symptom:
ARA connections are established, but users cannot send or receive ARA data over the link.
