Re: Another Layer 2 question.
On Tue, 2011-06-28 at 11:08 -0700, Chuck Tribolet wrote: I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Chuck, does your ifcfg-eth file for the VSWITCH NIC contain an LLADDR-definition? If yes, please remove it. VSWITCH NICs should always use the zVM-chosen MAC-address, which may change after LOGOFF/LOGON. Bugzilla 658708 is open to address this issue. Regards, Ursula Braun IBM Germany, Linux on System z development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
It did not contain an LLADDR definition. And I'm up via a Layer 3 VSWITCH, which suits me fine (less tweaking of Linux). Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Ursula Braun ubr...@linux.vnet.ibm.com To: LINUX-390@vm.marist.edu Date: 06/29/2011 12:58 AM Subject:Re: Another Layer 2 question. Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On Tue, 2011-06-28 at 11:08 -0700, Chuck Tribolet wrote: I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Chuck, does your ifcfg-eth file for the VSWITCH NIC contain an LLADDR-definition? If yes, please remove it. VSWITCH NICs should always use the zVM-chosen MAC-address, which may change after LOGOFF/LOGON. Bugzilla 658708 is open to address this issue. Regards, Ursula Braun IBM Germany, Linux on System z development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
On Mon, 2011-06-27 at 14:25 -0500, Dave Jones wrote: Here is what is in the ifcfg-eth0 file: # IBM QETH DEVICE=eth0 BOOTPROTO=static VSWITCH=1 OPTION=(layer2=1) IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ehternet ONBOOT=yes HWADDR=02:00:00:00:00:07 SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Dave, I would change 3 things in your ifcfg-eth0 file: 1. Remove HWADDR and VSWITCH 2. typo:TYPE=Ethernet 3. Specify the layer2 option with this syntax: OPTIONS='layer2=1' resulting in: # IBM QETH DEVICE=eth0 BOOTPROTO=static OPTIONS='layer2=1' IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ethernet ONBOOT=yes SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Does this config file help? Regards, Ursula Braun, IBM Germany, Linux on System z Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
Hi, Ursula. Yes, that fixed the problem; many thanks! I didn't need the HWADDR and VSWITCH settings and I specified the OPTIONS statement incorrectly (it's OPTIONS and not just OPTION). Have a good one. DJ On 06/28/2011 03:24 AM, Ursula Braun wrote: On Mon, 2011-06-27 at 14:25 -0500, Dave Jones wrote: Here is what is in the ifcfg-eth0 file: # IBM QETH DEVICE=eth0 BOOTPROTO=static VSWITCH=1 OPTION=(layer2=1) IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ehternet ONBOOT=yes HWADDR=02:00:00:00:00:07 SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Dave, I would change 3 things in your ifcfg-eth0 file: 1. Remove HWADDR and VSWITCH 2. typo: TYPE=Ethernet 3. Specify the layer2 option with this syntax: OPTIONS='layer2=1' resulting in: # IBM QETH DEVICE=eth0 BOOTPROTO=static OPTIONS='layer2=1' IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ethernet ONBOOT=yes SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Does this config file help? Regards, Ursula Braun, IBM Germany, Linux on System z Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Another Layer 2 question.
I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
Give us a hint :-) Scott Rohling On Tue, Jun 28, 2011 at 12:08 PM, Chuck Tribolet trib...@almaden.ibm.comwrote: I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
On 6/28/2011 at 02:08 PM, Chuck Tribolet trib...@almaden.ibm.com wrote: I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Assuming the NIC is at virtual address 700, then these two commands should do the trick: qeth_configure 0.0.0700 0.0.0701 0.0.0702 0 qeth_configure -l 0.0.0700 0.0.0701 0.0.0702 1 Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
First command runs with no output. Second command returns: LNXEC602: qeth_configure -l 0.0.1200 0.0.1201 0.0.1202 1 LNXEC602: (Layer2) LNXEC602: Could not set device 0.0.1200 online LNXEC602: lnxec602:~ # My virtual OSA address is 1200/1201/1202 Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 06/28/2011 11:39 AM Subject:Re: Another Layer 2 question. Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 6/28/2011 at 02:08 PM, Chuck Tribolet trib...@almaden.ibm.com wrote: I've got a similar problem to Dave Jones, converting from real OSA ports to a Layer 2 VSWITCH. I've successfully done SLES 10 and RHEL 5, but I'm having trouble with a SLES 11 system on the same VSWITCH. What do I need to change there? Assuming the NIC is at virtual address 700, then these two commands should do the trick: qeth_configure 0.0.0700 0.0.0701 0.0.0702 0 qeth_configure -l 0.0.0700 0.0.0701 0.0.0702 1 Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
On 6/28/2011 at 03:00 PM, Chuck Tribolet trib...@almaden.ibm.com wrote: First command runs with no output. Second command returns: LNXEC602: qeth_configure -l 0.0.1200 0.0.1201 0.0.1202 1 LNXEC602: (Layer2) LNXEC602: Could not set device 0.0.1200 online LNXEC602: lnxec602:~ # My virtual OSA address is 1200/1201/1202 Is it actually coupled to a Layer 2 VSWITCH? vmcp q nic vmcp q vswitch Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
cpsendx 602 cp q osa LNXEC602: OSA 1200 ON NIC 1200 UNIT 000 SUBCHANNEL = LNXEC602: 1200 DEVTYPE OSA CHPID 02 OSD LNXEC602: 1200 MAC 02-00-00-00-00-79 CURRENT LNXEC602: 1200 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE LNXEC602: OSA 1201 ON NIC 1200 UNIT 001 SUBCHANNEL = 0001 LNXEC602: 1201 DEVTYPE OSA CHPID 02 OSD LNXEC602: 1201 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE LNXEC602: OSA 1202 ON NIC 1200 UNIT 002 SUBCHANNEL = 0002 LNXEC602: 1202 DEVTYPE OSA CHPID 02 OSD LNXEC602: 1202 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE Ready; T=0.01/0.01 12:46:24 cpsendx 602 cp q nic LNXEC602: Adapter 1200.P00 Type: QDIO Name: UNASSIGNED Devices: 3 LNXEC602: MAC: 02-00-00-00-00-79 VSWITCH: SYSTEM LNXVSW2 Ready; T=0.01/0.01 12:46:42 cpsendx 602 cp q vswitch LNXEC602: VSWITCH SYSTEM LNXVSW2 Type: VSWITCH Connected: 4Maxconn: INFINIT E LNXEC602: PERSISTENT RESTRICTEDETHERNET Accounting: OFF LNXEC602: VLAN Unaware LNXEC602: MAC address: 02-00-00-00-00-03 LNXEC602: State: Ready LNXEC602: IPTimeout: 5 QueueStorage: 8 LNXEC602: Isolation Status: OFF LNXEC602: RDEV: 10F6.P00 VDEV: 10F6 Controller: LNXVSW2 Ready; T=0.01/0.01 12:46:56 It's acting like it does when I forget to add the DEDICATE cards for a real OSA card, that is, Linux thinks the device is just not there. But CP seems to think it is. Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 06/28/2011 12:10 PM Subject:Re: Another Layer 2 question. Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 6/28/2011 at 03:00 PM, Chuck Tribolet trib...@almaden.ibm.com wrote: First command runs with no output. Second command returns: LNXEC602: qeth_configure -l 0.0.1200 0.0.1201 0.0.1202 1 LNXEC602: (Layer2) LNXEC602: Could not set device 0.0.1200 online LNXEC602: lnxec602:~ # My virtual OSA address is 1200/1201/1202 Is it actually coupled to a Layer 2 VSWITCH? vmcp q nic vmcp q vswitch Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Another Layer 2 question.
On 6/28/2011 at 03:49 PM, Chuck Tribolet trib...@almaden.ibm.com wrote: cpsendx 602 cp q osa I don't think this is relevant, but it doesn't hurt (unless the guest has class B in which case it might cause some confusion). -snip- cpsendx 602 cp q nic LNXEC602: Adapter 1200.P00 Type: QDIO Name: UNASSIGNED Devices: 3 LNXEC602: MAC: 02-00-00-00-00-79 VSWITCH: SYSTEM LNXVSW2 OK, that looks good. cpsendx 602 cp q vswitch LNXEC602: VSWITCH SYSTEM LNXVSW2 Type: VSWITCH Connected: 4Maxconn: INFINIT E LNXEC602: PERSISTENT RESTRICTEDETHERNET Accounting: OFF As does that. It's acting like it does when I forget to add the DEDICATE cards for a real OSA card, that is, Linux thinks the device is just not there. But CP seems to think it is. What does ls /sys/bus/ccw/devices/ show you? You're going to have to run that from the z/VM console while signed in to Linux. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Layer 2 question
Hi, gang. I've have been tasked with changing the network configuration for a RedHat EL 5.6 s390x guest from employing layer 3 (tcpip) connectivity to a vswitch, to using layer 2 (ethernet) on another vswitch. I've updated the ifcfg-eth0 configuration file with the proper parameters (I think), but a boot time Linux complains that: Device eth0 has different MAC address than expected and doesn't bring up the interface. I can configure eth0 manually by creating the device in /sys/bus/ccwgroup/drivers/qeth with: echo 0.0.0110,0.0.0101,0.0.0102 group and then echo 1 0.0.0100/layer2 echo 1 0.0.0100/online Here is what is in the ifcfg-eth0 file: # IBM QETH DEVICE=eth0 BOOTPROTO=static VSWITCH=1 OPTION=(layer2=1) IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ehternet ONBOOT=yes HWADDR=02:00:00:00:00:07 SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Thanks and have a good one. -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
On 6/27/2011 at 03:25 PM, Dave Jones d...@vsoft-software.com wrote: HWADDR=02:00:00:00:00:07 I would try removing this from the ifcfg-eth0 file. There's usually not a good reason for a guest to be setting (or expecting) a particular MAC address for it's virtual NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
Hi, Mark. I've tried it without the HWADDR value and now the error is eth0 does not seem to be present. Thanks. DJ On 06/27/2011 02:32 PM, Mark Post wrote: On 6/27/2011 at 03:25 PM, Dave Jones d...@vsoft-software.com wrote: HWADDR=02:00:00:00:00:07 I would try removing this from the ifcfg-eth0 file. There's usually not a good reason for a guest to be setting (or expecting) a particular MAC address for it's virtual NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
You need to either remove the specification of the MAC in ifcfg-eth0 -- or specify it in the z/VM directory entry for the guest so that it matches. It's likely best to just remove it and let it default unless you have a real need to specify it. Scott Rohling On Mon, Jun 27, 2011 at 1:25 PM, Dave Jones d...@vsoft-software.com wrote: Hi, gang. I've have been tasked with changing the network configuration for a RedHat EL 5.6 s390x guest from employing layer 3 (tcpip) connectivity to a vswitch, to using layer 2 (ethernet) on another vswitch. I've updated the ifcfg-eth0 configuration file with the proper parameters (I think), but a boot time Linux complains that: Device eth0 has different MAC address than expected and doesn't bring up the interface. I can configure eth0 manually by creating the device in /sys/bus/ccwgroup/drivers/qeth with: echo 0.0.0110,0.0.0101,0.0.0102 group and then echo 1 0.0.0100/layer2 echo 1 0.0.0100/online Here is what is in the ifcfg-eth0 file: # IBM QETH DEVICE=eth0 BOOTPROTO=static VSWITCH=1 OPTION=(layer2=1) IPADDR=xxx.yyy.www.zzz NETMASK=255.255.255.0 NETTYPE=qeth TYPE=Ehternet ONBOOT=yes HWADDR=02:00:00:00:00:07 SUBCHANNELS=0.0.0100,0.0.0101,0.0.0102 Thanks and have a good one. -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
On 6/27/2011 at 03:41 PM, Dave Jones d...@vsoft-software.com wrote: I've tried it without the HWADDR value and now the error is eth0 does not seem to be present. Rats. Is there a file for the NIC in /etc/sysconfig/hardware? If so, is there any sort of MAC specification in there? I would really hate to think you have to hard-code a MAC in that version. That would mean having to set it in USER DIRECT for each guest that uses a Layer 2 NIC, or have some sort of startup logic that figures out what it is and updates ifcfg-eth0 each boot. Blech. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
On Monday, 06/27/2011 at 03:53 EDT, Mark Post mp...@novell.com wrote: On 6/27/2011 at 03:41 PM, Dave Jones d...@vsoft-software.com wrote: I've tried it without the HWADDR value and now the error is eth0 does not seem to be present. Rats. Is there a file for the NIC in /etc/sysconfig/hardware? If so, is there any sort of MAC specification in there? I would really hate to think you have to hard-code a MAC in that version. That would mean having to set it in USER DIRECT for each guest that uses a Layer 2 NIC, or have some sort of startup logic that figures out what it is and updates ifcfg-eth0 each boot. Blech. HWADDR is required for native LPAR configurations in order to set the virtual MAC address in the OSA. For guests, I thought changes had been made so that, if no HWADDR was supplied, the driver would query the current value and use that on the set vmac function. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
Drop the TYPE= and VSWITCH= as well as HWADDR= .. Scott Rohling On Mon, Jun 27, 2011 at 1:41 PM, Dave Jones d...@vsoft-software.com wrote: Hi, Mark. I've tried it without the HWADDR value and now the error is eth0 does not seem to be present. Thanks. DJ On 06/27/2011 02:32 PM, Mark Post wrote: On 6/27/2011 at 03:25 PM, Dave Jones d...@vsoft-software.com wrote: HWADDR=02:00:00:00:00:07 I would try removing this from the ifcfg-eth0 file. There's usually not a good reason for a guest to be setting (or expecting) a particular MAC address for it's virtual NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Layer 2 question
Hi, Scott. Removing the VSWITCH=1 and TYPE=Ethernet values from ifcfg-eth0 does not help matters at allI still receive the eth0 device is not present Thanks, though. DJ On 06/27/2011 02:51 PM, Scott Rohling wrote: Drop the TYPE= and VSWITCH= as well as HWADDR= .. Scott Rohling On Mon, Jun 27, 2011 at 1:41 PM, Dave Jones d...@vsoft-software.com wrote: Hi, Mark. I've tried it without the HWADDR value and now the error is eth0 does not seem to be present. Thanks. DJ On 06/27/2011 02:32 PM, Mark Post wrote: On 6/27/2011 at 03:25 PM, Dave Jones d...@vsoft-software.com wrote: HWADDR=02:00:00:00:00:07 I would try removing this from the ifcfg-eth0 file. There's usually not a good reason for a guest to be setting (or expecting) a particular MAC address for it's virtual NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
