Re: Hipersockets broke Ethernet?
We had this same problem 2 years ago. This is what we did to solve it: Be sure to place the hipersocket address first in the home list before any SOURCEVIPA addresses in PROFILE TCPIP fm. Do this in z/VM and in z/OS both. Kyle Stewart -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Chase, John Sent: Wednesday, February 27, 2013 1:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets broke Ethernet? -Original Message- From: Chase, John [ snip ] Now, what's missing from this file that is present in the same file on our golden image is the statement: OPTIONS=layer2=0 portno=0 I don't know why that statement is missing, unless our network guy deleted it from the penguin that doesn't talk while he was trying to figure out Hipersockets. I also notice the golden copy has BOOTPROTO=static instead of none. I'll set both back to golden and see what happens. And that fixed that problem. We now have both interfaces working, but the hipersockets network appears to be one-way at the moment: We can ping z/OS from Linux, but cannot ping Linux from z/OS. I don't believe that side of the question belongs on this forum, but if somebody wants to respond off-list, please do. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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/ == THIS ELECTRONIC MESSAGE, INCLUDING ANY ACCOMPANYING DOCUMENTS, IS CONFIDENTIAL and may contain information that is privileged and exempt from disclosure under applicable law. If you are neither the intended recipient nor responsible for delivering the message to the intended recipient, please note that any dissemination, distribution, copying or the taking of any action in reliance upon the message is strictly prohibited. If you have received this communication in error, please notify the sender immediately. Thank you. -- 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: Hipersockets broke Ethernet?
Be sure to place the hipersocket address first in the home list before any SOURCEVIPA addresses in PROFILE TCPIP fm. Do this in z/VM and in z/OS both. Kyle Stewart -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Chase, John Sent: Wednesday, February 27, 2013 1:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets broke Ethernet? -Original Message- From: Chase, John [ snip ] Now, what's missing from this file that is present in the same file on our golden image is the statement: OPTIONS=layer2=0 portno=0 I don't know why that statement is missing, unless our network guy deleted it from the penguin that doesn't talk while he was trying to figure out Hipersockets. I also notice the golden copy has BOOTPROTO=static instead of none. I'll set both back to golden and see what happens. And that fixed that problem. We now have both interfaces working, but the hipersockets network appears to be one-way at the moment: We can ping z/OS from Linux, but cannot ping Linux from z/OS. I don't believe that side of the question belongs on this forum, but if somebody wants to respond off-list, please do. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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/ == THIS ELECTRONIC MESSAGE, INCLUDING ANY ACCOMPANYING DOCUMENTS, IS CONFIDENTIAL and may contain information that is privileged and exempt from disclosure under applicable law. If you are neither the intended recipient nor responsible for delivering the message to the intended recipient, please note that any dissemination, distribution, copying or the taking of any action in reliance upon the message is strictly prohibited. If you have received this communication in error, please notify the sender immediately. Thank you. -- 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: Hipersockets broke Ethernet?
-Original Message- From: Chase, John [ snip ] Now, what's missing from this file that is present in the same file on our golden image is the statement: OPTIONS=layer2=0 portno=0 I don't know why that statement is missing, unless our network guy deleted it from the penguin that doesn't talk while he was trying to figure out Hipersockets. I also notice the golden copy has BOOTPROTO=static instead of none. I'll set both back to golden and see what happens. And that fixed that problem. We now have both interfaces working, but the hipersockets network appears to be one-way at the moment: We can ping z/OS from Linux, but cannot ping Linux from z/OS. I don't believe that side of the question belongs on this forum, but if somebody wants to respond off-list, please do. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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: Hipersockets broke Ethernet?
On 2/26/2013 at 04:48 PM, Chase, John jch...@ussco.com wrote: How do we configure Linux so that both interfaces (eth0 and hsi0) are configured at startup time? Look at /etc/sysconfig/network-scripts/ifcfg-eth0 to see what is in there for ONBOOT. For the interface to be started automatically, it should be set to yes. 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: Hipersockets broke Ethernet?
-Original Message- From: Linux on 390 Port On Behalf Of Mark Post On 2/26/2013 at 04:48 PM, Chase, John jch...@ussco.com wrote: How do we configure Linux so that both interfaces (eth0 and hsi0) are configured at startup time? Look at /etc/sysconfig/network-scripts/ifcfg-eth0 to see what is in there for ONBOOT. For the interface to be started automatically, it should be set to yes. Thanks. Checked; it's set to yes. Tried an interactive IPL and startup of the Linux vm, and saw some error messages that indicate we've got some misteaks [sic] in the definitions of the hipersockets virtual devices (but after the guest is started, ifconfig shows only the hipersockets interface as active). Here's the VM logon of the guest: LOGON AT 15:40:29 CST TUESDAY 02/26/13 Command complete NIC 0600 is created; devices 0600-0602 defined NIC 0600 is connected to VSWITCH SYSTEM VMBSW1 HCPNIC2781E NIC 7000 not created; network devices 7000-7002 could not be defined z/VM V6.2.02013-02-04 13:33 Vdevs 7000-7002 are for the hipersockets interface. The NIC at vaddr 600 is the Ethernet interface that previously worked just fine. Here's the part of the Linux console log pertaining to qeth: qeth: loading core functions vmur: z/VM virtual unit record device driver loaded. NET: Registered protocol family 10 lo: Disabled Privacy Extensions qeth: register layer 3 discipline qdio: 0.0.7002 HS on SC 2 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA:RW AO qeth: register layer 2 discipline qeth 0.0.0600: The qeth device is not configured for the OSI layer required by z /VM qeth 0.0.0600: The qeth device driver failed to recover an error on the device qeth: irb : 00 c2 60 17 0d b9 30 38 0e 00 10 00 00 80 00 00 ..`...08... . qeth: irb 0010: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... . qeth: sense data : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth 0.0.0600: The qeth device driver failed to recover an error on the device qeth 0.0.7000: Device is a HiperSockets card (level: HSGR) with link type HiperSockets. qeth 0.0.7000: Hardware IP fragmentation not supported on hsi0 qeth 0.0.7000: Inbound source MAC-address not supported on hsi0 qeth 0.0.7000: VLAN enabled qeth 0.0.7000: Multicast enabled qeth 0.0.7000: IPV6 enabled qeth 0.0.7000: Broadcast enabled qeth 0.0.7000: Using SW checksumming on hsi0. qeth 0.0.7000: Outbound TSO not supported on hsi0 [ OK ] Setting hostname redacted: [ OK ] Bringing up interface eth0: WARNING: /etc/modprobe.conf line 1: ignoring bad li ne starting with 'hsi0' WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: /etc/modprobe.conf line 1: ignoring bad line starting with 'hsi0' WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Device eth0 does not seem to be present, delaying initialization. [FAILED] Bringing up interface hsi0: [ OK ] The modprobe.conf file was created by a colleague, and contains one line: 'hsi0 alias qeth' (without the apostrophes). That's all the diagnostics I have at the moment. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing
Re: Hipersockets broke Ethernet?
On 2/26/2013 at 06:08 PM, Chase, John jch...@ussco.com wrote: -snip- Tried an interactive IPL and startup of the Linux vm, and saw some error messages that indicate we've got some misteaks [sic] in the definitions of the hipersockets virtual devices (but after the guest is started, ifconfig shows only the hipersockets interface as active). Here's the VM logon of the guest: LOGON AT 15:40:29 CST TUESDAY 02/26/13 Command complete NIC 0600 is created; devices 0600-0602 defined NIC 0600 is connected to VSWITCH SYSTEM VMBSW1 HCPNIC2781E NIC 7000 not created; network devices 7000-7002 could not be defined z/VM V6.2.02013-02-04 13:33 Vdevs 7000-7002 are for the hipersockets interface. The NIC at vaddr 600 is the Ethernet interface that previously worked just fine. Here's the part of the Linux console log pertaining to qeth: qeth: loading core functions vmur: z/VM virtual unit record device driver loaded. NET: Registered protocol family 10 lo: Disabled Privacy Extensions qeth: register layer 3 discipline This line, and the line 2 down is interesting. It looks like the NIC is trying to be both Layer 3 and Layer 2. Which is it _supposed_ to be? qdio: 0.0.7002 HS on SC 2 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA:RW AO qeth: register layer 2 discipline What all does the ifcfg-eth0 file have in it? qeth 0.0.0600: The qeth device is not configured for the OSI layer required by z /VM qeth 0.0.0600: The qeth device driver failed to recover an error on the device qeth: irb : 00 c2 60 17 0d b9 30 38 0e 00 10 00 00 80 00 00 ..`...08... . qeth: irb 0010: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... . qeth: sense data : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth 0.0.0600: The qeth device driver failed to recover an error on the device 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: Hipersockets broke Ethernet?
How are 7000-7002 defined? Seeing the directory entry would be useful too. An error is happening before the ipl moment. David Kreuter Original message From: Mark Post mp...@suse.com Date: To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets broke Ethernet? On 2/26/2013 at 06:08 PM, Chase, John jch...@ussco.com wrote: -snip- Tried an interactive IPL and startup of the Linux vm, and saw some error messages that indicate we've got some misteaks [sic] in the definitions of the hipersockets virtual devices (but after the guest is started, ifconfig shows only the hipersockets interface as active). Here's the VM logon of the guest: LOGON AT 15:40:29 CST TUESDAY 02/26/13 Command complete NIC 0600 is created; devices 0600-0602 defined NIC 0600 is connected to VSWITCH SYSTEM VMBSW1 HCPNIC2781E NIC 7000 not created; network devices 7000-7002 could not be defined z/VM V6.2.0 2013-02-04 13:33 Vdevs 7000-7002 are for the hipersockets interface. The NIC at vaddr 600 is the Ethernet interface that previously worked just fine. Here's the part of the Linux console log pertaining to qeth: qeth: loading core functions vmur: z/VM virtual unit record device driver loaded. NET: Registered protocol family 10 lo: Disabled Privacy Extensions qeth: register layer 3 discipline This line, and the line 2 down is interesting. It looks like the NIC is trying to be both Layer 3 and Layer 2. Which is it _supposed_ to be? qdio: 0.0.7002 HS on SC 2 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA:RW AO qeth: register layer 2 discipline What all does the ifcfg-eth0 file have in it? qeth 0.0.0600: The qeth device is not configured for the OSI layer required by z /VM qeth 0.0.0600: The qeth device driver failed to recover an error on the device qeth: irb : 00 c2 60 17 0d b9 30 38 0e 00 10 00 00 80 00 00 ..`...08... . qeth: irb 0010: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... . qeth: sense data : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth 0.0.0600: The qeth device driver failed to recover an error on the device 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: Hipersockets broke Ethernet?
-Original Message- From: Linux on 390 Port On Behalf Of Mark Post On 2/26/2013 at 06:08 PM, Chase, John jch...@ussco.com wrote: -snip- qeth: register layer 3 discipline This line, and the line 2 down is interesting. It looks like the NIC is trying to be both Layer 3 and Layer 2. Which is it _supposed_ to be? I believe it's supposed to be Layer 2; connects to a vswitch. qdio: 0.0.7002 HS on SC 2 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA:RW AO qeth: register layer 2 discipline What all does the ifcfg-eth0 file have in it? [root@myPenguin ~]# cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none DNS1=10.1.4.73 DOMAIN=ourshop.com GATEWAY=10.1.1.1 IPADDR=10.1.1.36 MTU=1500 NETMASK=255.255.255.192 NETTYPE=qeth NM_CONTROLLED=yes ONBOOT=yes PORTNAME=DONTCARE SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet UUID=646a685e-75d1-4ef4-bc5e-7482b66a7981 IPV6INIT=no USERCTL=no [root@myPenguin ~]# Now, what's missing from this file that is present in the same file on our golden image is the statement: OPTIONS=layer2=0 portno=0 I don't know why that statement is missing, unless our network guy deleted it from the penguin that doesn't talk while he was trying to figure out Hipersockets. I also notice the golden copy has BOOTPROTO=static instead of none. I'll set both back to golden and see what happens. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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: Hipersockets broke Ethernet?
RHEL has an error where if you use system-config-network on a layer 2 interface it forgets that it was layer 2. Reported a year ago as Bug 809534 - system-config-network ignores option field. No fix. Did you use system-config-network? Lee On 2/26/2013 6:30 PM, Chase, John wrote: -Original Message- From: Linux on 390 Port On Behalf Of Mark Post On 2/26/2013 at 06:08 PM, Chase, John jch...@ussco.com wrote: -snip- qeth: register layer 3 discipline This line, and the line 2 down is interesting. It looks like the NIC is trying to be both Layer 3 and Layer 2. Which is it _supposed_ to be? I believe it's supposed to be Layer 2; connects to a vswitch. qdio: 0.0.7002 HS on SC 2 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA:RW AO qeth: register layer 2 discipline What all does the ifcfg-eth0 file have in it? [root@myPenguin ~]# cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none DNS1=10.1.4.73 DOMAIN=ourshop.com GATEWAY=10.1.1.1 IPADDR=10.1.1.36 MTU=1500 NETMASK=255.255.255.192 NETTYPE=qeth NM_CONTROLLED=yes ONBOOT=yes PORTNAME=DONTCARE SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet UUID=646a685e-75d1-4ef4-bc5e-7482b66a7981 IPV6INIT=no USERCTL=no [root@myPenguin ~]# Now, what's missing from this file that is present in the same file on our golden image is the statement: OPTIONS=layer2=0 portno=0 I don't know why that statement is missing, unless our network guy deleted it from the penguin that doesn't talk while he was trying to figure out Hipersockets. I also notice the golden copy has BOOTPROTO=static instead of none. I'll set both back to golden and see what happens. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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/ -- Lee Stewart, Senior SE Sirius Computer Solutions Phone: (303) 996-7122 Email: lee.stew...@siriuscom.com Web: www.siriuscom.com -- 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: Hipersockets broke Ethernet?
-Original Message- From: Linux on 390 Port On Behalf Of Lee Stewart RHEL has an error where if you use system-config-network on a layer 2 interface it forgets that it was layer 2. Reported a year ago as Bug 809534 - system-config-network ignores option field. No fix. Did you use system-config-network? We did not see a directory or file with that exact name, so I'll guess we did not. One file named network, in /etc/sysconfig, contains only three lines: NETWORKING=yes HOSTAME=myPenguin.ussco.com GATEWAY=10.1.1.1 The ifcfg-eth0 cited earlier lives in /etc/sysconfig/network-scripts. In case I forgot to mention it, we're working with RHEL 6.3. -jc- [ snip ] ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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/
