ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajy_5.4.0.1/rzajyphysicalnetworkproblems.htm

85 lines
5.0 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="Physical network problems" />
<meta name="DC.Relation" scheme="URI" content="rzajytroubleshootingethernet.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="rzajyphysicalnetworkproblems" />
<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>Physical network problems</title>
</head>
<body id="rzajyphysicalnetworkproblems"><a name="rzajyphysicalnetworkproblems"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Physical network problems</h1>
<div><div class="section"><p>If your adapter card cannot make a connection to the network,
and the Product Activity Log points to a physical network problem, check the
following problem areas:</p>
</div>
<div class="section"><h4 class="sectiontitle">Cabling problems</h4><div class="p"> <ul><li>Check that your cable type is appropriate for the line speed you are using.
For example, category 3 cable cannot be used for 100 Mbps.</li>
<li>Is the cable wired correctly?</li>
<li>Do all cables, patch cables, and patch panels between the <span class="keyword">iSeries™</span> and
the network, switch or hub support your line speed? For example, if the line
speed is configured at 100 Mbps, the cable must be category 5 to support the
speed.</li>
</ul>
</div>
</div>
<div class="section"><h4 class="sectiontitle">Possible solutions</h4><ul><li>If the cables have been excessively bent or stretched, the wiring inside
the cable might have been untwisted, damaged, or even broken. Try reseating
the cable or temporarily replacing it with a functional one.</li>
<li>Make sure that you are not using crossover cable.</li>
<li>Route the cable away from electrically noisy devices, such as fluorescent
lights, printers, copiers, or electric motors. These items can cause interference
with data transmissions.</li>
<li>Try plugging the cable into a different switch or hub port.</li>
<li>Check that the switch or hub has the latest software from the vendor.</li>
<li>You might want to add lightning protection to your network cabling and
switch or hub power lines, if you live in a lightning prone area. A direct
strike can cause a large power surge, which can severely damage your networking
equipment and cabling.</li>
</ul>
</div>
<div class="section"><h4 class="sectiontitle">Configuration problem checks and solutions</h4><ul><li>Check that the line speed and duplex mode chosen in CRTLINETH are the
same as the parameters programmed into the switch or hub port. One frequent
cause of problems is a duplex or line speed mismatch <div class="note"><span class="notetitle">Note:</span> To use the *AUTO
configuration for line speed or duplex mode, you must configure both of the
parameters to *AUTO. Do not use line speed and duplex configurations of 10/AUTO,
100/AUTO, AUTO/Half, or AUTO/Full. These configurations might work, but you
will have frequently unsuccessful and incorrect connections. </div>
</li>
<li>Try varying the line off and then on again with *RESET. Do not use *RESET
if an MFIOP is the IOP! This might shut down the entire machine
because other devices that share the MFIOP will not be able to access the
line.</li>
<li>If you suspect the adapter might be faulty, run VFYCMN with an external
wrap plug attached. If this test is passed, the adapter card is not likely
to be the problem.</li>
<li>Connect a LAN analyzer to verify that the actual line speed and duplex
mode being used on the link between the <span class="keyword">iSeries</span> and
the hub or switch is accurate.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajytroubleshootingethernet.htm" title="Having problems with your server and connections? Get tips on why connections might fail, why frames are dropped, or why PCs cannot connect to your system.">Troubleshoot Ethernet</a></div>
</div>
</div>
</body>
</html>