Re: OSA/Express Assistance
Dave, after reboot your OSA interfaces can be 'dead', because 1. problem in OSA-device configuration 2. just a missing gateway After reboot invoke from the HMC-console lsqeth -p to check if OSA-devices are available and route to check if the default gateway is defined. And what is contained in /etc/sysconfig/network/route ? Ursula 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
Re: OSA/Express Assistance
Thanks Ron, I have the integrated ascii console working now. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ron Foster at Baldor-IS rfos...@baldor.com 7/21/2009 11:29 AM Dave, The HMC ASCII Console is enabled inside of Linux with the following in /etc/inittab. The mingetty line comes commented out. # # z900 LPAR SE/HMC VT220/Linux console - uncomment to enable getty on it: # 2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 linux Then once you have done a telinitq or rebooted and gotten all the way up. You click on ASCII Console instead of operating system messages. You get a blank screen. Then position you cursor on the screen and press enter. You should get a login prompt. Ron David Stuart wrote: Hi Ron, I am using the HMC, Operating System Messages, which limits what you can do. I'll check out the ascii console. Yes, I have two ports. I have two OSA/Express cards in the System. One port on each card is ethernet, the other is OSA-ICC. The ethernet ports on both cards are shared across all LPARs. I wish the HMC Op Sys Msgs allowed you to cut and paste... Let me see if I can get the ascii console working, and check on the files you were asking about. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ron Foster at Baldor-IS rfos...@baldor.com 7/21/2009 6:32 AM David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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
Re: OSA/Express Assistance
Dave, you can try to setup a qeth device manually at your HMC console using these steps: 1. Check with lscss, if the subchannel triplet (0.0., 0.0.xxxy, 0.0.xxxz) of your OSA-device is available. 2. Define the ccwgroup device with: echo 0.0.,0.0.xxxy,0.0.xxxz /sys/bus/ccwgroup/drivers/qeth/group 3. Bring the device online: echo 1 /sys/bus/ccwgroup/devices/0.0./online 4. Activate the network interface: ifconfig eth0 ip.ad.dr.es netmask aa.bb.cc.dd Now you should be able to connect from your PC. Then you should check the SLES10 configuration files: /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0. /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0. Regards, Ursula 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
Re: OSA/Express Assistance
On Wed, Jul 22, 2009 at 10:19 AM, Ursula Braunubr...@linux.vnet.ibm.com wrote: 4. Activate the network interface: ifconfig eth0 ip.ad.dr.es netmask aa.bb.cc.dd Don't forget the default route if your PC is not on the same subnet as the Linux guest (in most real world situations it is not) route add default gw Rob -- 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
Re: OSA/Express Assistance
Thanks Ursula, I managed to get one of the connections back up and working. The echo in step 2 failed with a message -bash: echo: write error: Invalid argument. But I went ahead with step 3, echo 1 ... /online, and then step 4, ifconfig eth0, and then added the default route as suggested by Rob, and now I can connect up again! I still need to go look at the config files, but at least I can, now. Not being all that familiar with linux, or having the time to work with it and really learn it, I have a tendency to use Yast(2). However, I apparently shouldn't use Network Manager... Thanks to all, for the suggestions. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ursula Braun ubr...@linux.vnet.ibm.com 7/22/2009 1:19 AM Dave, you can try to setup a qeth device manually at your HMC console using these steps: 1. Check with lscss, if the subchannel triplet (0.0., 0.0.xxxy, 0.0.xxxz) of your OSA-device is available. 2. Define the ccwgroup device with: echo 0.0.,0.0.xxxy,0.0.xxxz /sys/bus/ccwgroup/drivers/qeth/group 3. Bring the device online: echo 1 /sys/bus/ccwgroup/devices/0.0./online 4. Activate the network interface: ifconfig eth0 ip.ad.dr.es netmask aa.bb.cc.dd Now you should be able to connect from your PC. Then you should check the SLES10 configuration files: /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0. /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0. Regards, Ursula 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 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
Re: OSA/Express Assistance
Ursula, The config files you pointed out exist for both OSA ports. But I am not sure what should be in them. Besides the ip address and netmask. I have pasted the files for one of the OSA interfaces below. Sorry for my ignorance, but what am I looking for? What should be in the config file? Thanks, Dave ftpgalileo:~ # cat /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.0510 STARTMODE='auto' MODULE='qeth' MODULE_OPTIONS='' MODULE_UNLOAD='yes' SCRIPTUP='hwup-ccw' SCRIPTUP_ccw='hwup-ccw' SCRIPTUP_ccwgroup='hwup-qeth' SCRIPTDOWN='hwdown-ccw' CCW_CHAN_IDS='0.0.0510 0.0.0511 0.0.0512' CCW_CHAN_NUM='3' CCW_CHAN_MODE='' QETH_LAYER2_SUPPORT='0' LCS_LANCMD_TIMEOUT='' QETH_IPA_TAKEOVER='0' QETH_OPTIONS='' ftpgalileo:~ # cat /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0510 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='157.145.4.159' LLADDR='' MTU='' NAME='IBM OSA Express Network card (0.0.0510)' NETMASK='255.255.252.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='Wo7R.FOqOuhDmSR4' USERCONTROL='no' _nm_name='qeth-bus-ccw-0.0.0510' PREFIXLEN='' Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ursula Braun ubr...@linux.vnet.ibm.com 7/22/2009 1:19 AM Dave, snip. Now you should be able to connect from your PC. Then you should check the SLES10 configuration files: /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0. /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0. Regards, Ursula 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 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
Re: OSA/Express Assistance
On 7/22/2009 at 11:48 AM, David Stuart david.stu...@ventura.org wrote: -snip- Not being all that familiar with linux, or having the time to work with it and really learn it, I have a tendency to use Yast(2). However, I apparently shouldn't use Network Manager... Absolutely. As it is currently designed, Network Manager will only allow one network interface to be active at a time. The intent is that it will be used on things like laptops that have both Ethernet and wireless NICs, and cables get plugged and unplugged, etc. It's not the default on server installs for obvious reasons, but is still made available because a number of people do install SLES on such devices. 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
Re: OSA/Express Assistance
On 7/22/2009 at 12:22 PM, David Stuart david.stu...@ventura.org wrote: Ursula, The config files you pointed out exist for both OSA ports. But I am not sure what should be in them. Besides the ip address and netmask. I have pasted the files for one of the OSA interfaces below. Sorry for my ignorance, but what am I looking for? What should be in the config file? Both of those look fine. By any chance did you try rebooting the system after your network dropped? 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
Re: OSA/Express Assistance
Hi Mark, Yes, I did. After the problem originally occurred. Both OSA interfaces were 'dead'. And I tried again after I reviewed the interface files after going through Ursula's procedures. After reboot, both were 'dead' again. I had to go through Ursula's procedures again to get it back. Right now, only one OSA interface is 'active', meaning that I can connect to it and it will answer a ping. The other is non-responsive. I'm not sure where to go next. When I look at the Network Device through Yast, everything looks correct. But there is something somewhere. I just haven't found it yet. Not knowing where to look, or what to look for, doesn't help much, either. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Mark Post mp...@novell.com 7/22/2009 9:34 AM On 7/22/2009 at 12:22 PM, David Stuart david.stu...@ventura.org wrote: Ursula, The config files you pointed out exist for both OSA ports. But I am not sure what should be in them. Besides the ip address and netmask. I have pasted the files for one of the OSA interfaces below. Sorry for my ignorance, but what am I looking for? What should be in the config file? Both of those look fine. By any chance did you try rebooting the system after your network dropped? 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 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
Re: OSA/Express Assistance
On 7/22/2009 at 12:44 PM, David Stuart david.stu...@ventura.org wrote: Hi Mark, Yes, I did. After the problem originally occurred. Both OSA interfaces were 'dead'. Have you gone back into YaST to switch from Network Manager to traditional mode? 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
Re: OSA/Express Assistance
Mark, I think so. Now when I go in to Yast, Network Devices, Network Card, it shows Traditional Method with ifup as the management selection. If I look at the interfaces through there, they look correct. However, I can only seem to get one interface active at any given time. And it's not always, the same one. Usually, but... Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Mark Post mp...@novell.com 7/22/2009 9:57 AM On 7/22/2009 at 12:44 PM, David Stuart david.stu...@ventura.org wrote: Hi Mark, Yes, I did. After the problem originally occurred. Both OSA interfaces were 'dead'. Have you gone back into YaST to switch from Network Manager to traditional mode? 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 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
Re: OSA/Express Assistance
David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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
Re: OSA/Express Assistance
You may need to POR the system to reset the osa. I don't know of any other way to bring it back if they are as dead as you say. Saying that and looking at what you've done I would have to take a WAG that here is a less invasive way to bring them back. I am not familiar with native Linux and the operation of it,but do you have an HMC from which you reboot/ipl from? You should be able to go to it and activate the osa cards. Good Luck Mace --- On Tue, 7/21/09, Ron Foster at Baldor-IS rfos...@baldor.com wrote: From: Ron Foster at Baldor-IS rfos...@baldor.com Subject: Re: OSA/Express Assistance To: LINUX-390@VM.MARIST.EDU Date: Tuesday, July 21, 2009, 9:32 AM David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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 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
Re: OSA/Express Assistance
Hi Ron, I am using the HMC, Operating System Messages, which limits what you can do. I'll check out the ascii console. Yes, I have two ports. I have two OSA/Express cards in the System. One port on each card is ethernet, the other is OSA-ICC. The ethernet ports on both cards are shared across all LPARs. I wish the HMC Op Sys Msgs allowed you to cut and paste... Let me see if I can get the ascii console working, and check on the files you were asking about. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ron Foster at Baldor-IS rfos...@baldor.com 7/21/2009 6:32 AM David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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 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
Re: OSA/Express Assistance
Mace, Oh, I hope a POR isn't required. The OSA/Express cards are shared across multiple LPARs... Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org LJ Mace ljmace1...@yahoo.com 7/21/2009 7:25 AM You may need to POR the system to reset the osa. I don't know of any other way to bring it back if they are as dead as you say. Saying that and looking at what you've done I would have to take a WAG that here is a less invasive way to bring them back. I am not familiar with native Linux and the operation of it,but do you have an HMC from which you reboot/ipl from? You should be able to go to it and activate the osa cards. Good Luck Mace --- On Tue, 7/21/09, Ron Foster at Baldor-IS rfos...@baldor.com wrote: From: Ron Foster at Baldor-IS rfos...@baldor.com Subject: Re: OSA/Express Assistance To: LINUX-390@VM.MARIST.EDU Date: Tuesday, July 21, 2009, 9:32 AM David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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 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 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
Re: OSA/Express Assistance
On 7/21/2009 at 2:08 PM, David Stuart david.stu...@ventura.org wrote: Mace, Oh, I hope a POR isn't required. The OSA/Express cards are shared across multiple LPARs... I doubt very much that a POR will be needed. What does ifconfig -a and lsqeth show you? 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
Re: OSA/Express Assistance
Dave, The HMC ASCII Console is enabled inside of Linux with the following in /etc/inittab. The mingetty line comes commented out. # # z900 LPAR SE/HMC VT220/Linux console - uncomment to enable getty on it: # 2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 linux Then once you have done a telinitq or rebooted and gotten all the way up. You click on ASCII Console instead of operating system messages. You get a blank screen. Then position you cursor on the screen and press enter. You should get a login prompt. Ron David Stuart wrote: Hi Ron, I am using the HMC, Operating System Messages, which limits what you can do. I'll check out the ascii console. Yes, I have two ports. I have two OSA/Express cards in the System. One port on each card is ethernet, the other is OSA-ICC. The ethernet ports on both cards are shared across all LPARs. I wish the HMC Op Sys Msgs allowed you to cut and paste... Let me see if I can get the ascii console working, and check on the files you were asking about. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.org Ron Foster at Baldor-IS rfos...@baldor.com 7/21/2009 6:32 AM David, When you say, you have to connect to the system via the HMC, are you talking about the operating systems messages interface or the ASCII console interface? You say both ports. This implies more than one interface. What is your default route set to in /etc/sysconfig/network/routes? Is it set to one of the active interfaces? When you say you are getting martian messages, could you elaborate? Could it be that the firewall got turned on? The interface might be up, but the firewall is disallowing all traffic. Also, there is some sort of OSA support tool that our zOS guy uses. He can go look at the OSA and the what LPARS are attached to an OSA and what addresses they are using. The people who know how to use this tool are out today at a meeting. Do you all have someone who can look at the OSA with this tool and find out if the Linux LPAR is really attached and what address it is using. In my limited experience running Linux in LPARS, there are only a few files that have to be right to get the network up. /etc/sysconfig/network/persistentnetworkname (in our case) ifcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/hardware/hardware name (in our case) hwcfg-qeth-bus-ccw-0.0.a100 /etc/sysconfig/network/routes And possibly /etc/hosts Also, if you all are a member of SHARE, there was a presentation some time back that included some tips on how to get the network up when it does not want to come up. If you do not have ascii console mode running, it might be worthwhile to use google to find this presentation. (A lot of the presentations are on the linuxvm.org website.) If I remember correctly, the presenter said that by using a few echo commands to the right places, you could get a network up. I never tried it though. Ron David Stuart wrote: Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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 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 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 LINUX-390 subscribe / signoff / archive access
Re: OSA/Express Assistance
I have reset OSA ports by using the OSA Advanced Facilities dialog in the HMC. It takes about 15 minutes for the port to actually reset after you hit enter though. IBM Hardware Support walked me through it the first time and warned me to be patient for the actual reset. The HMC Operations Guide has the path to this function. Craig Moody System Z Technical Specialist Levi, Ray and Shoup, Inc 2401 West Monroe St Springfield, Il 62704 217 793-3800 x1813 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Tuesday, July 21, 2009 1:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: OSA/Express Assistance On 7/21/2009 at 2:08 PM, David Stuart david.stu...@ventura.org wrote: Mace, Oh, I hope a POR isn't required. The OSA/Express cards are shared across multiple LPARs... I doubt very much that a POR will be needed. What does ifconfig -a and lsqeth show you? 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 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
Re: OSA/Express Assistance
On 7/21/2009 at 2:32 PM, Moody, Craig craig.mo...@lrs.com wrote: I have reset OSA ports by using the OSA Advanced Facilities dialog in the HMC. I really don't think that will be needed either. Everything so far just points to messed up configuration files. 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
OSA/Express Assistance
Afternoon, set Newbie Alert I am not all that experienced with Linux, and I haven't worked with it for a while, and I have proceeded to shot myself in the foot. Maybe both feet. Sles 10 SP 2 running 'native' in an LPAR (no, no z/VM (yeah, I know!)) - Using Yast Network Manager, I have managed to disable both OSA/Express ports, and I have been unable to get them back, so far. Reboot(s) have been unsuccessful in restoring my OSA ports. The ports are running QDIO mode. A ping from my PC times out. An ifstatus eth0 shows it to be active. But I can't seem to connect to it. I have to connect to the System through the HMC. But the rest of what I need to do to get things back active are off in the far hazy, recesses of my mind, such as it is... Ideas and suggestions greatly appreciated. Also, I am having a large number of 'martian' messages, displaying all kinds of header information. None of which makes any sense to me. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 david.stu...@ventura.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
