Re: Arp cache in a VSWITCH ??
I got it from the mtr website, unpacked it and run ./configure and make and make install worked out of the gz :-) Just some warnings 'no gtk+ avail, will run without it' Did it in a SLES11 SP1. /Tore Tore Agblad System programmer, Volvo IT certified IT Architect Volvo Information Technology IMO Mainframe Databases & zOpen Gothenburg Dept. DE56430 SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: den 5 november 2012 17:00 To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? >>> On 11/5/2012 at 10:17 AM, "Dean, David (I/S)" wrote: > Mark, these all say DOS format, I have done vi:set fileformat=unix on > install-sh and a makefiledirs but now it is giving me this > > Am I missing something simple? Perhaps. I'm not sure what you're doing, but I expected you to do something like this: rpm -ivh mtr-0.82-5.1.2.src.rpm cd /usr/src/packages/SPECS/ rpmbuild -ba mtr.spec 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: CCL OSA device not activated
Hi Ursula, At first I've copied the rule from the vswitch connection and configured the udev rule according to the configuration we had on the SLES9 machine, including the portno and layer2 rules. When that didn't work I did try to configure with yast, but that didn't work either, basically with the same error: "stderr":"/sbin/qeth_configure: line 280: echo: write error: Input/output error\n", "stdout":"Could not set device 0.0.efac online\n"] Regards, Berry. > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Ursula Braun > Sent: dinsdag 6 november 2012 10:40 > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CCL OSA device not activated > > now I recognize my first hint has been useless for you - sorry. Your problem > is specific to OSN. OSN-devices are special OSA-devices which offer just a > few writable sysfs-attributes (buffer_count and recover). > Thus it does not make sense to have definitions for portname, portno, and > layer2 in a udev-rule for an OSN-device. I assume your udev-rule has been > created by yast - correct? > > Regards, Ursula Braun, IBM Germany Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Nederland B.V. group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. Atos Nederland B.V. / Utrecht KvK Utrecht 30132762 -- 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: CCL OSA device not activated
On Thu, 2012-11-01 at 09:57 +, van Sleeuwen, Berry wrote: > I tried to activate with these commands, as well as with znetconf but that > was still not successful. After installing the most recent patches, the > kernel is now on 2.6.32.59, the ccwgroup device 0.0.efac is activated during > boot. Since it's now active we can test the new CCL once again. > > The funny thing is we are upgrading, from SLES9 to SLES11, just to have a > supported version before we migrate to a new CPU. But indeed, the installed > SLES11 level was not the most recent. > > Since it's an OSN it must be layer2. Even more so, files portname, portno and > layer2 are not available in /sys/bus/ccwgroup/drivers/qeth/0.0.efac/. But it > looks like that's the same in SLES9. During boot there is no comment about > that on SLES9, on SLES11 udev complains about these rules. > Berry, now I recognize my first hint has been useless for you - sorry. Your problem is specific to OSN. OSN-devices are special OSA-devices which offer just a few writable sysfs-attributes (buffer_count and recover). Thus it does not make sense to have definitions for portname, portno, and layer2 in a udev-rule for an OSN-device. I assume your udev-rule has been created by yast - correct? Regards, Ursula Braun, IBM Germany -- 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/
