86 lines
5.2 KiB
HTML
86 lines
5.2 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Virtual Ethernet problems with IXS and IXA attached servers</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="rzahqtroubleshootveconn"></a>
|
||
|
|
<h3 id="rzahqtroubleshootveconn">Virtual Ethernet problems with IXS and IXA attached servers</h3>
|
||
|
|
<p>For the purposes of this section, the virtual Ethernet point to point LAN
|
||
|
|
and the virtual Ethernet ports 0-9 are all considered virtual Ethernet adapters
|
||
|
|
or virtual Ethernet ports.</p>
|
||
|
|
<p>There are two kinds of virtual Ethernet device drivers, virtual Ethernet
|
||
|
|
Adapter (VE) and a virtual Ethernet Data Transport (DT).</p>
|
||
|
|
<ul>
|
||
|
|
<li>The virtual Ethernet Adapter corresponds to the driver that appears as
|
||
|
|
the adapter, called 'virtual' because no NIC hardware is associated with
|
||
|
|
it.</li>
|
||
|
|
<li>The virtual Ethernet Data Transport is the driver that provides a connection
|
||
|
|
to the system bus connecting all the virtual Ethernet networks.</li></ul>
|
||
|
|
<p>When a VE port cannot communicate across the system bus, it reports that
|
||
|
|
the cable for the port is unplugged (cable disconnected). This is an important
|
||
|
|
concept for troubleshooting virtual Ethernet errors.</p>
|
||
|
|
<p>The virtual Ethernet Ports under Windows are automatically installed and
|
||
|
|
uninstalled by the virtual Ethernet Utility (VEU). The utility receives signaling
|
||
|
|
through a configuration file from the NWSD. For example, when a user creates
|
||
|
|
a Line Description under the NWSD for a given virtual Ethernet Port the VEU
|
||
|
|
installs the corresponding VE port. Rebooting the Windows server configures
|
||
|
|
the VE port address.</p>
|
||
|
|
<p>The following virtual Ethernet components use the listed driver.</p>
|
||
|
|
<ul>
|
||
|
|
<li>virtual Ethernet Adapter: qvndvemp.sys</li>
|
||
|
|
<li>virtual Ethernet Data Transport: qvndvedt.sys</li>
|
||
|
|
<li>virtual Ethernet Install Utility: qvndveu.exe</li></ul>
|
||
|
|
<p>Troubleshooting virtual Ethernet problems</p>
|
||
|
|
<p>When the communication between any VE ports is not functioning, you need
|
||
|
|
to perform two general tasks to troubleshoot the problem.</p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Determine the status of the VE ports.</li>
|
||
|
|
<li>Match the observed results to the following troubleshooting cases.</li></ol>
|
||
|
|
<p><span class="bold">Determine VE port status</span></p>
|
||
|
|
<p>To determine the status of the VE ports.</p>
|
||
|
|
<ul>
|
||
|
|
<li>Use the iSeries console to determine if a line description for the VE
|
||
|
|
port is created under the NWSD.</li>
|
||
|
|
<li>Use the Windows console to open the <span class="bold">Network and Dial
|
||
|
|
Up Connections</span> folder and determine if the VE port icon is present.</li></ul>
|
||
|
|
<p><span class="bold">Match port status with troubleshooting cases</span></p>
|
||
|
|
<p>Match results of your determination of the status of the VE ports to one
|
||
|
|
of the following troubleshooting cases.</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="iconyeslineyes.htm#iconyeslineyes">Both line description and icon are present</a>.</li>
|
||
|
|
<li><a href="iconnolineyes.htm#iconnolineyes">Line description is present and icon is missing</a>.</li>
|
||
|
|
<li><a href="iconyeslineno.htm#iconyeslineno">Line description is missing and icon is present</a>.</li>
|
||
|
|
<li><a href="iconnolineno.htm#iconnolineno">Both line description and icon are missing</a>.</li></ul>
|
||
|
|
<p>In each case, you must first verify the i5/OS side then verify the Windows
|
||
|
|
side. To verify the Windows side, you may need to open the Event Log and
|
||
|
|
the Device Manager.</p>
|
||
|
|
<ul>
|
||
|
|
<li>To open the Event Log, from the Windows <span class="bold">Start</span> menu,
|
||
|
|
select <span class="bold">Programs</span>, then <span class="bold">Administrative
|
||
|
|
Tools</span>, then <span class="bold">Event Viewer</span>.</li>
|
||
|
|
<li>To open the Device Manager, from the Windows <span class="bold">Start</span> menu,
|
||
|
|
select <span class="bold">Settings</span>, then <span class="bold">Control Panel</span>, then <span class="bold">Administrative Tools</span>, then <span class="bold">Computer Management</span>, then <span class="bold">Device Manager</span>.</li></ul>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|