ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaju_5.4.0.1/rzajuwhyconnectionsfail.htm

77 lines
5.0 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Why some LAN connections fail" />
<meta name="abstract" content="Sometimes an incorrectly configured controller description can cause a connection failure." />
<meta name="description" content="Sometimes an incorrectly configured controller description can cause a connection failure." />
<meta name="DC.Relation" scheme="URI" content="rzajutroubleshootingtokenring.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="why_connections_fail" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Why some LAN connections fail</title>
</head>
<body id="why_connections_fail"><a name="why_connections_fail"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Why some LAN connections fail</h1>
<div><p>Sometimes an incorrectly configured controller description can
cause a connection failure.</p>
<p> The cases here involve the incorrect configuration of
the adapter address, source service access point <a href="rzajuhigherlayersoverlanprotocols.htm#higher_layers_over_lan_protocols__ssaps_and_dsaps">(SSAP)</a>, or destination service access point <a href="rzajuhigherlayersoverlanprotocols.htm#higher_layers_over_lan_protocols__ssaps_and_dsaps">(DSAP)</a> parameters. </p>
<p>For more information about how these parameters influence a successful
connection, see <a href="rzajuunderstandingstationids.htm#understanding_station_ids">How
LAN devices identify themselves</a>. For other causes of a connection failure,
see <a href="rzajuunderstandingwhentoconnect.htm#understanding_when_to_connect">Which
device initiates the connection</a>. </p>
<p><strong>The remote system does not connect:</strong></p>
<p>If your controller description uses <a href="rzajudialmode.htm#dial_mode">dial
mode</a>, it is not unusual for the system to receive message CPA58E0 (<tt class="msgph">Controller
not replying</tt>) or CPA57EF (<tt class="msgph">Contact not successful</tt>).
Remote systems or controller descriptions that do not vary on can cause one
of these messages to appear.</p>
<p><strong>Your system does not connect:</strong></p>
<p>If your controller description uses <a href="rzajuanswermode.htm#answer_mode">answer
mode</a>, you might receive the message CPI591A (<tt class="msgph">Controller is online,
varied off, or not recognized by the local system</tt>). There are some
things that can cause this message to appear:</p>
<ul><li>The connection requested by the remote system does not exist on the local
system. The local system searches for this connection (that is indicated by
combining the local adapter address, the DSAP, and the SSAP) in all varied-on
controller descriptions.</li>
<li>The controller description does not refer to the line
description that can answer the call.</li>
</ul>
<p><strong>Solution:</strong></p>
<p>To correct any of the above problems, do one or more of these steps:</p>
<ul><li>On either side of the connection, verify that the controller description
has the correct combination of adapter address, SSAP, and DSAP.</li>
<li>Enter the line description that can accept the call into the Switched
line list field of the controller description. See <a href="rzajuunderstandingconnestablishment.htm#understanding_conn_establishment">Understanding
connection establishment</a> for information about the relationship between
line descriptions and controller descriptions.</li>
<li>Vary on the correct controller description (use the Work with Configuration
Status (WRKCFGSTS) command to vary on the controller).</li>
<li>Verify that the local and remote adapters are wired into the network correctly.</li>
</ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajutroubleshootingtokenring.htm" title="The server has tools to help you locate and resolve errors.">Troubleshoot token ring</a></div>
</div>
</div>
</body>
</html>