135 lines
9.9 KiB
HTML
135 lines
9.9 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 iSCSI 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>
|
||
|
|
|
||
|
|
<img src="delta.gif" alt="Start of change" /><img src="delta.gif" alt="Start of change" />
|
||
|
|
<a name="rzahqvirtethproblemsoniscsi"></a>
|
||
|
|
<h4 id="rzahqvirtethproblemsoniscsi">Virtual Ethernet problems with iSCSI attached servers</h4>
|
||
|
|
<p>To see information about the connections available to the Windows TCP/IP
|
||
|
|
stack, enter<span class="bold"> ipconfig /all</span> at a Windows command prompt.
|
||
|
|
You should see information about the following things:</p>
|
||
|
|
<ul>
|
||
|
|
<li>External network adapters</li>
|
||
|
|
<li>The LAN interfaces for the iSCSI HBA ports</li>
|
||
|
|
<li>Virtual Ethernet adapters for your iSeries™ server</li></ul>
|
||
|
|
<p>Match the results of the ipconfig command with one of the following troubleshooting
|
||
|
|
cases and perform the actions suggested for that case until the problem is
|
||
|
|
resolved.</p>
|
||
|
|
<p><span class="bold">A configured LAN IP address is missing in ipconfig</span></p>
|
||
|
|
<p>This case applies if an internet address for a LAN interface in the i5/OS
|
||
|
|
remote configuration does not match an IP address that ipconfig shows for
|
||
|
|
any iSCSI HBA. To display the remote system configuration, see <a href="rzahqdisiplayremotesysconfig.htm#rzahqdisiplayremotesysconfig">Display remote system configuration properties</a>.</p>
|
||
|
|
<ul>
|
||
|
|
<li>Examine the ipconfig results to find the physical addresses (MAC addresses)
|
||
|
|
of the iSCSI HBAs. If a physical address displayed by ipconfig is different
|
||
|
|
than the adapter address for the LAN interface in the i5/OS remote system
|
||
|
|
configuration, do the following steps.
|
||
|
|
<ol type="1">
|
||
|
|
<li>Shut down the server from the Windows console.</li>
|
||
|
|
<li>Vary off the NWSD from i5/OS. See <a href="rzahqstartnstop.htm#rzahqstartnstop">Start and stop an integrated server</a>.</li>
|
||
|
|
<li>Change the adapter address for the LAN interface in the remote system
|
||
|
|
configuration.</li>
|
||
|
|
<li>Using i5/OS, start (vary on) the NWSD. See <a href="rzahqstartnstop.htm#rzahqstartnstop">Start and stop an integrated server</a>.</li></ol></li>
|
||
|
|
<li>Open <span class="bold">Control Panel</span>, then <span class="bold">Administrative
|
||
|
|
Tools</span>, then <span class="bold">Services</span>. Ensure that <span class="bold">iSeries Shutdown Manager</span> is in the list of services and has a status
|
||
|
|
of <span class="bold">Started</span>. This service automatically assigns LAN
|
||
|
|
IP interface information from the i5/OS remote system configuration to ports
|
||
|
|
having the configured MAC addresses.</li>
|
||
|
|
<li>Look in the <span class="bold">Application event log</span> in Windows for
|
||
|
|
events with a source of <span class="bold">iSeries Shutdown Manager</span>.</li>
|
||
|
|
<li>Close any network properties window having <span class="bold">General</span>, <span class="bold">Authentication</span>, and <span class="bold">Advanced</span> tabs
|
||
|
|
because this type of window locks resources required for assigning an IP address.
|
||
|
|
If you close this type of window, wait 30 seconds for iSeries Shutdown Manager
|
||
|
|
to assign the missing IP address, and enter <span class="bold">ipconfig /all</span> again.</li>
|
||
|
|
<li>If none of the ipconfig results describe an installed iSCSI HBA, open
|
||
|
|
Device Manager in Windows and ensure that the network driver for the iSCSI
|
||
|
|
HBA is installed and enabled. If the driver has a yellow '!' or
|
||
|
|
is grayed out, look in the System event log in Windows for events with a source
|
||
|
|
of QL40xx and ensure that the iSCSI HBA is not disabled by the system BIOS
|
||
|
|
setup menu.</li></ul>
|
||
|
|
<p><span class="bold">Ipconfig shows a configured iSCSI HBA connection in media
|
||
|
|
disconnected state</span></p>
|
||
|
|
<p>This case applies if ipconfig shows an iSCSI HBA connection that is in
|
||
|
|
media disconnected state and has a physical address that matches an adapter
|
||
|
|
address in the i5/OS remote system configuration.</p>
|
||
|
|
<ul>
|
||
|
|
<li>Ensure that the physical network is properly connected, and that devices
|
||
|
|
in the network, such as switches, are functioning at the physical link to
|
||
|
|
the hosted system's iSCSI HBA.</li></ul>
|
||
|
|
<p><span class="bold">Ipconfig shows an IBM iSeries Virtual Ethernet connection
|
||
|
|
in media disconnected state </span></p>
|
||
|
|
<ul>
|
||
|
|
<li>Virtual Ethernet requires a working iSCSI network, so iSCSI HBA problems
|
||
|
|
must be resolved first. Ensure that ipconfig shows the LAN addresses in the
|
||
|
|
i5/OS remote system configuration before proceeding.</li>
|
||
|
|
<li>Ensure that the physical network is properly connected, and that devices
|
||
|
|
in the network, such as switches, are functioning beyond the physical link
|
||
|
|
to the hosted system's iSCSI HBA.</li>
|
||
|
|
<li>Ensure that requirements defined in <a href="rzahqnciscinetwork.htm#rzahqnciscinetwork">iSCSI network</a> are
|
||
|
|
satisfied.</li>
|
||
|
|
<li>Open <span class="bold">Control Panel</span>, then <span class="bold">Administrative
|
||
|
|
Tools</span>, then <span class="bold">Services</span>. Ensure that <span class="bold">iSeries Manager</span>,<span class="bold"> iSeries Shutdown Manager</span>, and <span class="bold">iSeries Virtual Ethernet Manager</span> are in the list of services
|
||
|
|
and have a status of <span class="bold">Started</span>.</li>
|
||
|
|
<li>Look in the <span class="bold">Application</span> event log in Windows for
|
||
|
|
events with a source of <span class="bold">iSeries Virtual Ethernet Manager</span>.</li>
|
||
|
|
<li>If a firewall or a similar packet filtering function is involved, see <a href="rzahqconffirewall.htm#rzahqconffirewall">Configure a firewall</a>. LAN IP interfaces in the i5/OS remote system
|
||
|
|
configuration can be affected by firewall software running in Windows.</li>
|
||
|
|
<li>If your NWSD uses IPSec rules other than *NONE, see the <a href="http://www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html" target="_blank">iSCSI troubleshooting </a> web page
|
||
|
|
<img src="www.gif" alt="Link outside the Information Center." />
|
||
|
|
<br />(www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html).</li></ul>
|
||
|
|
<p><span class="bold">Ipconfig shows an IBM iSeries Virtual Ethernet connection
|
||
|
|
with an incorrect IP address</span></p>
|
||
|
|
<ul>
|
||
|
|
<li>Manually configure the IP address in Windows. For point to point virtual
|
||
|
|
Ethernet, see <a href="rzahqipcpi.htm#rzahqipcpi">Point to point virtual Ethernet IP address conflicts</a>. For other virtual Ethernet networks,
|
||
|
|
only steps 1 - 5 of this procedure apply.</li></ul>
|
||
|
|
<p><span class="bold">'Virtual Ethernet x' is configured in i5/OS and 'IBM
|
||
|
|
iSeries Virtual Ethernet x' is missing in ipconfig</span></p>
|
||
|
|
<ul>
|
||
|
|
<li>In i5/OS, verify that the line description exists for the virtual Ethernet
|
||
|
|
of interest. For point to point virtual Ethernet, see <a href="rzahqpointtopointveth.htm#rzahqpointtopointveth">Explore point to point virtual Ethernet networks</a>.</li>
|
||
|
|
<li>Open <span class="bold">Control Panel</span>, then <span class="bold">Administrative
|
||
|
|
Tools</span>, then <span class="bold">Services</span>. Ensure that <span class="bold">iSeries Virtual Ethernet Manager</span> is in the list of services and has a
|
||
|
|
status of <span class="bold">Started</span>. This service automatically creates
|
||
|
|
and removes IBM iSeries Virtual Ethernet adapters to match the line description
|
||
|
|
configuration in i5/OS.</li>
|
||
|
|
<li>Ensure that the system is not set to block installation of unsigned drivers.
|
||
|
|
For details, see steps 1-4 of <a href="rzahqtroubleshootlandrvs01.htm#rzahqtroubleshootlandrvs01">Begin the LAN driver installation or update</a>.
|
||
|
|
If you change the setting from <span class="bold">Block</span>, restart the <span class="bold"> iSeries Virtual Ethernet Manager</span> service, wait 30 seconds
|
||
|
|
and enter <span class="bold">ipconfig /all</span> again.</li>
|
||
|
|
<li>Open <span class="bold">Device Manager</span> in Windows and ensure that the
|
||
|
|
network driver for the IBM iSeries Virtual Ethernet adapter of interest is
|
||
|
|
installed and enabled. If a yellow '!' is shown near the driver,
|
||
|
|
look in the <span class="bold">System</span> event log in Windows for events with
|
||
|
|
a source of <span class="bold">Qvndvimp</span>.</li></ul>
|
||
|
|
<p><span class="bold">Ipconfig results look OK but large transfers fail</span></p>
|
||
|
|
<ul>
|
||
|
|
<li>Ensure that the IBM iSeries Virtual Ethernet adapters and the 'LAN'
|
||
|
|
side of iSCSI HBA ports are not configured to use a larger maximum transmission
|
||
|
|
unit than the iSCSI network supports. For example, not all switches support
|
||
|
|
9000 byte jumbo frames. Check the specifications of your network equipment.
|
||
|
|
For more information, see <a href="rzahqiscsimtucons.htm#rzahqiscsimtucons">Maximum transmission unit (MTU) considerations</a>.</li></ul><img src="deltaend.gif" alt="End of change" /><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|