For the benefit of the rest of the list; Alan's suggestion to enable faked frame headers solved the problem I was having.
Unfortunately, a second problem surfaced immediately. The VSWITCH would give me an error when the DHCP client received its lease: HCPSWU2833E Error 'E00A'X adding IP address 192.54.6.16 for VSWITCH SYSTEM VLINUX1. HCPSWU2833E IP address is already in use on the LAN. There is no other machine (real or virtual) on the network with this address. I could have ignored the message except that the DHCP client will then only respond to other machines on the VSWITCH. It will not communicate with the router on the subnet (nor consequently with any machine outside of the subnet). I left the user logged off overnight; when I logged it on this morning it started up, received its DHCP lease without triggering the VSWITCH error, and was communicating normally on the network, with both other VSWITCH users and with the rest of the world. As soon as I rebooted it, I began to receive the VSWITCH errors again. After asking Dr Google, I found that I needed to add the line "ARP='no'" to /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.a001 (our NIC dev) for an IP VSWITCH. We've been using IP VSWITCH without DHCP for about a year, and why we never ran into this problem before, I couldn't exactly say. http://www.vm.ibm.com/virtualnetwork/hintarp.html IBM: z/VM Virtual Networking Hints and Tips - Error x0002, xE00A We've been using IP VSWITCH without DHCP for about a year, and why we never ran into this problem before, I couldn't exactly say. As of right now it looks a lot like we have what we need for a successful DHCP implementation. Thanks, everybody. ok r. -----Original Message----- From: Alan Altmark [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 3:18 PM To: [email protected] Subject: Re: DHCP over VSWITCH? On Thursday, 08/24/2006 at 01:33 MST, "Stricklin, Raymond J" <[EMAIL PROTECTED]> wrote: > > I am trying to set up DHCP for linux users on our VSWITCH. > > > > Right now I have two linux users, both on VSWITCH. One is the DHCP > > server (SLES9 SP2 with ISC dhcpd), and one is the DHCP client > > (SLES10 with dhcpcd). > > > > The client sends its VM user name as its DHCP client identifier; the > > server assigns a fixed address using that instead of the ethernet > > MAC address, as our VSWITCH is running in layer 3. Easiest is to change to use a Layer 2 VSWITCH (TYPE ETHERNET). To use DHCP with Layer 3, you have to get the device driver to generate fake ethernet frame headers. E.g. For NIC A000 on SLES9: /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.a000: CCW_CHAN_IDS='0.0.a000 0.0.a001 0.0.a002' CCW_CHAN_MODE='OSAPORT' CCW_CHAN_NUM='3' MODULE='qeth' MODULE_OPTIONS='' SCRIPTDOWN='hwdown-ccw' SCRIPTUP='hwup-ccw' SCRIPTUP_ccw='hwup-ccw' SCRIPTUP_ccwgroup='hwup-qeth' STARTMODE='auto' QETH_OPTIONS='fake_ll=1' <---- look here! Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
