Re: Defining second OSA port on the chpid on SLES10 SP3
>>> On 3/9/2011 at 06:27 PM, Alan Altmark wrote: > I'm expressing my ignorance now. I thought that the startup scripts that > read config files and construct the ifconfig commands were provided by the > distro and are not part of Linux, per se. That's true. (Of course, "not part of Linux" is everything except the kernel, but I know what you meant.) > If that's the case, then IBM > would not document the existence or format of those files. But, it appears the Device Drivers manual does, for some items. Go figure. Look for instances of /etc/sysconfig/ to find them. > And the generic Device Drivers manual says that the udev rules are > distro-specific. So are you saying that the network config files of the > SLES 10 era replaced by new udev rules in SLES 11? And that, unlike days > of yore, you use some new utility or YaST to manipulate the udev rules? Not the network configuration files, but the hardware ones. The network configuration files are still there, and have the same content as before (I believe). The hardware configuration files are gone as of SLES11. Look under /etc/sysconfig/hardware/ to see. Even in SLES10, YaST was the official method to manage hardware configuration files. The replacement for all those is udev. There are some tools that get shipped as part of the s390-tools package to manipulate System z specific hardware, along with other things such as shutdown actions, etc. The _documented_ method to do hardware configuration on SLES is via YaST. The adventurous can use additional commands such as qeth_configure, dasd_configure, zfcp_host_configure, zfcp_disk_configure, etc. Those are mainly intended to be used by YaST and other SUSE-supplied tools. They _can_ be used by sysadmins, and I have in the past recommended that they do so in a number of cases. I caution that there are no man pages for those, just usage notes in /usr/share/doc/packages/s390-tools/README.SUSE. Many of these commands existed in SLES10. They've been updated to work with udev in SLES11, and to handle the changed/increased functionality of the device drivers in that version. 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: Defining second OSA port on the chpid on SLES10 SP3
On Wednesday, 03/09/2011 at 06:12 EST, Mark Post wrote: > >>> On 3/9/2011 at 06:02 PM, Alan Altmark wrote: > > Strange. Then what would be the equivalent for SLES 11? Doesn't changing > > it create a compatibility/upgrade problem? > > That would be a udev rule under /etc/udev/rules.d/. You _really_ don't want > people editing those by hand. > > > I just find it strange the SOME of the parms are documented, but not all. > > Red Hat has the same issue. > > Send an email to linux...@de.ibm.com with your comments. :) They write the > Device Drivers manual. I'm expressing my ignorance now. I thought that the startup scripts that read config files and construct the ifconfig commands were provided by the distro and are not part of Linux, per se. If that's the case, then IBM would not document the existence or format of those files. And the generic Device Drivers manual says that the udev rules are distro-specific. So are you saying that the network config files of the SLES 10 era replaced by new udev rules in SLES 11? And that, unlike days of yore, you use some new utility or YaST to manipulate the udev rules? Alan Altmark z/VM and Linux on System z 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: Defining second OSA port on the chpid on SLES10 SP3
Ok - I thought this was a distro specific issue -- RHEL and SLES use entirely different files to configure network devices ... I just thought the end result was supposed to be what is documented in Device Drivers (a resulting /sys setting...). I thought RHEL and SLES made up the configuration options used to get there? No? Scott Rohling p.s. To me - this is a configuration file -- and anything that might be in it should be documented . Things like QDIO architecture are a different fruit. In this case - being able to know how to specify the portname doesn't seem like something you want to hide. On Wed, Mar 9, 2011 at 4:14 PM, Mark Post wrote: > >>> On 3/9/2011 at 06:06 PM, Scott Rohling > wrote: > > It seems the goal 'would' be to document 'every last thing that can be > put > > in those files' to me as well.. Why code for it if you're not going to > > document it? 'Mystery features' and 'hacks' are for games ;-) > > I don't know. Why doesn't IBM document every last machine instruction, > diagnose code, the QDIO architecture, etc.? Some things you just want > people to use the documented interfaces for, and let the tools handle > things. Based on the number of service requests I've had to handle for > people that didn't want to use the tools, but didn't spend the time to > really understand the internals, that's not an entirely ludicrous > philosophy. Personally, I would prefer to see it all documented, but I'm > not in charge. > > > 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: Defining second OSA port on the chpid on SLES10 SP3
>>> On 3/9/2011 at 06:06 PM, Scott Rohling wrote: > It seems the goal 'would' be to document 'every last thing that can be put > in those files' to me as well.. Why code for it if you're not going to > document it? 'Mystery features' and 'hacks' are for games ;-) I don't know. Why doesn't IBM document every last machine instruction, diagnose code, the QDIO architecture, etc.? Some things you just want people to use the documented interfaces for, and let the tools handle things. Based on the number of service requests I've had to handle for people that didn't want to use the tools, but didn't spend the time to really understand the internals, that's not an entirely ludicrous philosophy. Personally, I would prefer to see it all documented, but I'm not in charge. 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: Defining second OSA port on the chpid on SLES10 SP3
>>> On 3/9/2011 at 06:02 PM, Alan Altmark wrote: > Strange. Then what would be the equivalent for SLES 11? Doesn't changing > it create a compatibility/upgrade problem? That would be a udev rule under /etc/udev/rules.d/. You _really_ don't want people editing those by hand. > I just find it strange the SOME of the parms are documented, but not all. > Red Hat has the same issue. Send an email to linux...@de.ibm.com with your comments. :) They write the Device Drivers manual. 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: Defining second OSA port on the chpid on SLES10 SP3
It seems the goal 'would' be to document 'every last thing that can be put in those files' to me as well.. Why code for it if you're not going to document it? 'Mystery features' and 'hacks' are for games ;-) Scott Rohling On Wed, Mar 9, 2011 at 4:02 PM, Alan Altmark wrote: > On Wednesday, 03/09/2011 at 05:40 EST, Mark Post wrote: > > >>> On 3/9/2011 at 12:17 PM, Alan Altmark > wrote: > > >> Try QETH_PORTNO. > > > > > > Mark, where is this mechanism documented? The Device Driver book > (even > > > for SLES 11) does not refer to such. > > > > It's not that I know of. Since this is a parm that was only used in > SLES10, it > > wouldn't be in the distribution-specific Device Drivers and Commands > books, > > which started with SLES11. > > Strange. Then what would be the equivalent for SLES 11? Doesn't changing > it create a compatibility/upgrade problem? > > > I think this is a case of "If you're technical enough to not use YaST > and > > instead edit hardware configuration files directly, you should be able > to look > > at the skeleton config files and startup scripts to figure it out." I > don't > > think we've ever documented every last thing that can be put into those > files, > > but I could be wrong. > > I just find it strange the SOME of the parms are documented, but not all. > Red Hat has the same issue. > > Alan Altmark > > z/VM and Linux on System z 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/ > -- 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: Defining second OSA port on the chpid on SLES10 SP3
On Wednesday, 03/09/2011 at 05:40 EST, Mark Post wrote: > >>> On 3/9/2011 at 12:17 PM, Alan Altmark wrote: > >> Try QETH_PORTNO. > > > > Mark, where is this mechanism documented? The Device Driver book (even > > for SLES 11) does not refer to such. > > It's not that I know of. Since this is a parm that was only used in SLES10, it > wouldn't be in the distribution-specific Device Drivers and Commands books, > which started with SLES11. Strange. Then what would be the equivalent for SLES 11? Doesn't changing it create a compatibility/upgrade problem? > I think this is a case of "If you're technical enough to not use YaST and > instead edit hardware configuration files directly, you should be able to look > at the skeleton config files and startup scripts to figure it out." I don't > think we've ever documented every last thing that can be put into those files, > but I could be wrong. I just find it strange the SOME of the parms are documented, but not all. Red Hat has the same issue. Alan Altmark z/VM and Linux on System z 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: Defining second OSA port on the chpid on SLES10 SP3
>>> On 3/9/2011 at 12:17 PM, Alan Altmark wrote: >> Try QETH_PORTNO. > > Mark, where is this mechanism documented? The Device Driver book (even > for SLES 11) does not refer to such. It's not that I know of. Since this is a parm that was only used in SLES10, it wouldn't be in the distribution-specific Device Drivers and Commands books, which started with SLES11. > Is it the same on Red Hat? I doubt it, since it was a variable used in one of the scripts SUSE wrote, but I haven't checked. > I have > the vague impression that attributes that are specific to a particular > device driver are named _, but that's purely > speculative. (I can't find a reference for that, either.) > > Or is this simply a case of "everyone knows that". :-) I think this is a case of "If you're technical enough to not use YaST and instead edit hardware configuration files directly, you should be able to look at the skeleton config files and startup scripts to figure it out." I don't think we've ever documented every last thing that can be put into those files, but I could be wrong. 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: Defining second OSA port on the chpid on SLES10 SP3
I did a google search for QETH_PORTNO in PDF files only. The only hits were from Debian. ;-) Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Alan Altmark/Endicott/IBM@IBMUS To: LINUX-390@vm.marist.edu Date: 03/09/2011 09:19 AM Subject:Re: Defining second OSA port on the chpid on SLES10 SP3 Sent by:Linux on 390 Port On Tuesday, 03/08/2011 at 11:06 EST, Mark Post wrote: > >>> On 3/8/2011 at 09:08 PM, Chuck Tribolet wrote: > > PORTNO=1 > > ETHTOOL_OPTIONS='' > > LLADDR='' > > MTU='' > > NAME='' > > REMOTE_IPADDR='' > > USERCONTROL='no' > > > > What am I missing? > > Try QETH_PORTNO. Mark, where is this mechanism documented? The Device Driver book (even for SLES 11) does not refer to such. Is it the same on Red Hat? I have the vague impression that attributes that are specific to a particular device driver are named _, but that's purely speculative. (I can't find a reference for that, either.) Or is this simply a case of "everyone knows that". :-) Alan Altmark z/VM and Linux on System z 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/ -- 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: Defining second OSA port on the chpid on SLES10 SP3
On Tuesday, 03/08/2011 at 11:06 EST, Mark Post wrote: > >>> On 3/8/2011 at 09:08 PM, Chuck Tribolet wrote: > > PORTNO=1 > > ETHTOOL_OPTIONS='' > > LLADDR='' > > MTU='' > > NAME='' > > REMOTE_IPADDR='' > > USERCONTROL='no' > > > > What am I missing? > > Try QETH_PORTNO. Mark, where is this mechanism documented? The Device Driver book (even for SLES 11) does not refer to such. Is it the same on Red Hat? I have the vague impression that attributes that are specific to a particular device driver are named _, but that's purely speculative. (I can't find a reference for that, either.) Or is this simply a case of "everyone knows that". :-) Alan Altmark z/VM and Linux on System z 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: Defining second OSA port on the chpid on SLES10 SP3
QETH_PORTNO=1 in /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.1200 was the trick. Chuck Tribolet trib...@almaden.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Chuck Tribolet/Almaden/IBM To: linux-...@www2.marist.edu Date: 03/08/2011 06:08 PM Subject:Defining second OSA port on the chpid on SLES10 SP3 I'm trying to use the second port on an OSA Express3 card under SLES10 SP3. It keeps coming up trying to talk to the first port (portno 0). I know the HW is good because it will work if I do: ifdown eth0 echo 0 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/online echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/portno echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/online ifup eth0 but that goes away when I reboot zLinux. It's not persistent. Here's /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.1200 BOOTPROTO='static' UNIQUE='' STARTMODE='auto' IPADDR='9.30.163.167' IPADDR_IPV6='fec8::9:30:163:167/64' NETMASK='255.255.255.128' NETWORK='' BROADCAST='' _nm_name='qeth-bus-ccw-0.0.1200' PORTNO=1 ETHTOOL_OPTIONS='' LLADDR='' MTU='' NAME='' REMOTE_IPADDR='' USERCONTROL='no' What am I missing? 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: Defining second OSA port on the chpid on SLES10 SP3
>>> On 3/8/2011 at 09:08 PM, Chuck Tribolet wrote: > PORTNO=1 > ETHTOOL_OPTIONS='' > LLADDR='' > MTU='' > NAME='' > REMOTE_IPADDR='' > USERCONTROL='no' > > What am I missing? Try QETH_PORTNO. 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/
Defining second OSA port on the chpid on SLES10 SP3
I'm trying to use the second port on an OSA Express3 card under SLES10 SP3. It keeps coming up trying to talk to the first port (portno 0). I know the HW is good because it will work if I do: ifdown eth0 echo 0 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/online echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/portno echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.1200/online ifup eth0 but that goes away when I reboot zLinux. It's not persistent. Here's /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.1200 BOOTPROTO='static' UNIQUE='' STARTMODE='auto' IPADDR='9.30.163.167' IPADDR_IPV6='fec8::9:30:163:167/64' NETMASK='255.255.255.128' NETWORK='' BROADCAST='' _nm_name='qeth-bus-ccw-0.0.1200' PORTNO=1 ETHTOOL_OPTIONS='' LLADDR='' MTU='' NAME='' REMOTE_IPADDR='' USERCONTROL='no' What am I missing? 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/
