Re: Start networkadapter without reboot
On Fri, 2012-06-15 at 14:54 +, van Sleeuwen, Berry wrote: Hi Scott, Yes it is. I've found some more information when looking through the /sys/ directory. The state for this device is in HARDSETUP. nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/state HARDSETUP Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). Berry. Hi Berry, correct, state HARDSETUP should be a temporary state during online setting for a qeth device only. If the device stays in state HARDSETUP something unexpected occurred. To understand the reason, the trace file /sys/kernel/debugfs/qeth_setup/hex_ascii should be checked by a qeth expert. It's a wrap around buffer; thus it needs to be saved immediately after the problem shows up. 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/
Re: Start networkadapter without reboot
Hi Ursula, Thank's for your update. I found the file at: nlzlx204:~ # ll /sys/kernel/debug/s390dbf/qdio_setup/ total 0 --w--- 1 root root 0 Apr 5 11:30 flush -r 1 root root 0 Apr 5 11:30 hex_ascii -rw--- 1 root root 0 Apr 5 11:30 level -rw--- 1 root root 0 Apr 5 11:30 pages nlzlx204:~ # Obviously it hadn't been saved at the time of this problem. Regards, Berry. correct, state HARDSETUP should be a temporary state during online setting for a qeth device only. If the device stays in state HARDSETUP something unexpected occurred. To understand the reason, the trace file /sys/kernel/debugfs/qeth_setup/hex_ascii should be checked by a qeth expert. It's a wrap around buffer; thus it needs to be saved immediately after the problem shows up. 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: Start networkadapter without reboot
Ursula Braun writes: correct, state HARDSETUP should be a temporary state during online setting for a qeth device only. If the device stays in state HARDSETUP something unexpected occurred. To understand the reason, the trace file /sys/kernel/debugfs/qeth_setup/hex_ascii should be checked by a qeth expert. It's a wrap around buffer; thus it needs to be saved immediately after the problem shows up. I can reproduce this easily on SLES11SP1 kernel 2.6.32.12-0.7-default (not up to date on service at all). I'll send you a transcript. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK -- 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: Start networkadapter without reboot
On Mon, 2012-06-18 at 10:15 +0100, Malcolm Beattie wrote: Ursula Braun writes: correct, state HARDSETUP should be a temporary state during online setting for a qeth device only. If the device stays in state HARDSETUP something unexpected occurred. To understand the reason, the trace file /sys/kernel/debugfs/qeth_setup/hex_ascii should be checked by a qeth expert. It's a wrap around buffer; thus it needs to be saved immediately after the problem shows up. I can reproduce this easily on SLES11SP1 kernel 2.6.32.12-0.7-default (not up to date on service at all). I'll send you a transcript. Malcolm, looking through your transcript, I find the definition of the NIC (vmcp def nic 800 type qdio), but I do not see a vmcp couple command to bind the created NIC to a VSWITCH or GuestLAN. This would explain the failing STARTLAN command for this qeth device. Try to insert a vmcp couple command between vmcp def nic... and znetconf -a ... . 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/
Re: Start networkadapter without reboot
Ursula Braun writes: looking through your transcript, I find the definition of the NIC (vmcp def nic 800 type qdio), but I do not see a vmcp couple command to bind the created NIC to a VSWITCH or GuestLAN. This would explain the failing STARTLAN command for this qeth device. I intentionally didn't bother with a COUPLE since I was trying to reproduce Berry's problem and also expecting the vNIC to act like a normal NIC and let me configure it and even ifconfig it up before plugging it into a switch. I'd thought that that used to work but maybe not. Would it be considered a bug or an unimplemented feature that it doesn't act that way? Actually, even when I then couple it to a VSWITCH, the state remains in HARDSETUP (even after I do an echo 1 recover too) and an ifup eth1 still fails. That makes it even more unlike a normal NIC and seems very inconvenient. I'll send you the trace for that too in case that part is unexpected. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK -- 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: Start networkadapter without reboot
On Mon, 2012-06-18 at 11:36 +0100, Malcolm Beattie wrote: I intentionally didn't bother with a COUPLE since I was trying to reproduce Berry's problem and also expecting the vNIC to act like a normal NIC and let me configure it and even ifconfig it up before plugging it into a switch. I'd thought that that used to work but maybe not. Would it be considered a bug or an unimplemented feature that it doesn't act that way? Actually, even when I then couple it to a VSWITCH, the state remains in HARDSETUP (even after I do an echo 1 recover too) and an ifup eth1 still fails. That makes it even more unlike a normal NIC and seems very inconvenient. I'll send you the trace for that too in case that part is unexpected. --Malcolm Malcolm, tried to recreate your problem with my available upstream kernel. But my qeth device stayed in state SOFTSETUP after znetconf. Further analysis showed that you need to upgrade to a kernel level of at least 2.6.32.29-0.3.1 (bugzilla 68725) to see this behavior. 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/
Start networkadapter without reboot
Hi All, In a SLES11 SP1 guest I try to activate the second network adapter but it fails. The guest is cloned from a default system where both networks are configured. But this guest has started with only eth0. The nic eth1 was not available during boot. Probably it will start when rebooted but can I active a nic afterwards without a reboot (preferably without rcnetwork restart)? Running ifup I get: nlzlx204:~ # ifup eth1 eth1 name: OSA Express Network card (0.0.0f10) RTNETLINK answers: Cannot assign requested address Cannot enable interface eth1. interface eth1 is not up But the adapter looks like to be online: nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/if_name eth1 nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/online 1 Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven * +31 (0)6 22564276 [Description: atos] [Description: cid:325312309@02022011-28C8] 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/ inline: image001.jpginline: image002.jpg
Re: Start networkadapter without reboot
If you are using VSWITCH's to attach the guest nics -- is this guest authorized for both? Scott Rohling On Fri, Jun 15, 2012 at 5:27 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Hi All, In a SLES11 SP1 guest I try to activate the second network adapter but it fails. The guest is cloned from a default system where both networks are configured. But this guest has started with only eth0. The nic eth1 was not available during boot. Probably it will start when rebooted but can I active a nic afterwards without a reboot (preferably without rcnetwork restart)? Running ifup I get: nlzlx204:~ # ifup eth1 eth1 name: OSA Express Network card (0.0.0f10) RTNETLINK answers: Cannot assign requested address Cannot enable interface eth1. interface eth1 is not up But the adapter looks like to be online: nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/if_name eth1 nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/online 1 Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven * +31 (0)6 22564276 [Description: atos] [Description: cid:325312309@02022011-28C8 ] 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/ -- 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: Start networkadapter without reboot
Hi Scott, Yes it is. I've found some more information when looking through the /sys/ directory. The state for this device is in HARDSETUP. nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/state HARDSETUP Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). Berry. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent: vrijdag 15 juni 2012 15:47 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot If you are using VSWITCH's to attach the guest nics -- is this guest authorized for both? Scott Rohling On Fri, Jun 15, 2012 at 5:27 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Hi All, In a SLES11 SP1 guest I try to activate the second network adapter but it fails. The guest is cloned from a default system where both networks are configured. But this guest has started with only eth0. The nic eth1 was not available during boot. Probably it will start when rebooted but can I active a nic afterwards without a reboot (preferably without rcnetwork restart)? Running ifup I get: nlzlx204:~ # ifup eth1 eth1 name: OSA Express Network card (0.0.0f10) RTNETLINK answers: Cannot assign requested address Cannot enable interface eth1. interface eth1 is not up But the adapter looks like to be online: nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/if_name eth1 nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/online 1 Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven * +31 (0)6 22564276 [Description: atos] [Description: cid:325312309@02022011-28C8 ] 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/ -- 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/ Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit
Re: Start networkadapter without reboot
On 6/15/2012 at 10:54 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). You can try using qeth_configure to take the NIC offline and bring it back online to see if that helps: If this is a Layer 2 VSWITCH, use the -l switch on the command: qeth_configure 0.0.0f10 0.0.0f11 0.0.0f12 0 qeth_configure 0.0.0f10 0.0.0f11 0.0.0f12 1 ifup eth1 Beyond that, is this SP1 system current on maintenance? I don't recall running into this problem, and I've done a lot of dynamic NIC defines and detaches, etc. 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: Start networkadapter without reboot
van Sleeuwen, Berry writes: I've found some more information when looking through the /sys/ directory. The state for this device is in HARDSETUP. nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/state HARDSETUP Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). Try # echo 1 recover You may need to take the device offline first (echo 0 online) and then bring it back again after the recovery attempt (echo 1 online). --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK -- 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: Start networkadapter without reboot
Sigh, why didn't I think of that. Eventhough I couldn't write to recover (yes, I am root here) the echo offline and echo online did the trick. nlzlx204:~ # echo 1 /sys/devices/qeth/0.0.0f10/recover -bash: echo: write error: Operation not permitted Thanks Malcolm. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Malcolm Beattie Sent: vrijdag 15 juni 2012 17:47 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot van Sleeuwen, Berry writes: I've found some more information when looking through the /sys/ directory. The state for this device is in HARDSETUP. nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/state HARDSETUP Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0..7). Try # echo 1 recover You may need to take the device offline first (echo 0 online) and then bring it back again after the recovery attempt (echo 1 online). --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK -- 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/ 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: Start networkadapter without reboot
Hi Mark, No, not the most current level. It's the base install of SLES11 SP1 without additional service. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: vrijdag 15 juni 2012 17:39 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot On 6/15/2012 at 10:54 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). You can try using qeth_configure to take the NIC offline and bring it back online to see if that helps: If this is a Layer 2 VSWITCH, use the -l switch on the command: qeth_configure 0.0.0f10 0.0.0f11 0.0.0f12 0 qeth_configure 0.0.0f10 0.0.0f11 0.0.0f12 1 ifup eth1 Beyond that, is this SP1 system current on maintenance? I don't recall running into this problem, and I've done a lot of dynamic NIC defines and detaches, etc. 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/ 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: Start networkadapter without reboot
I just noticed this in your original post: RTNETLINK answers: Cannot assign requested address What does your ifcfg-eth1 look like? - is it possible the IP address you're using is not valid? You said this was a clone, so just checking network interfaces were updated correctly. I also wonder how this shows us on z/VM with a Q VSWITCH DETAILS -- does it show connected for this 2nd NIC? What does a 'vmcp q nic' show? Are addresses attached to the vswitch? (sort of the same as above).. Scott Rohling On Fri, Jun 15, 2012 at 7:54 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Hi Scott, Yes it is. I've found some more information when looking through the /sys/ directory. The state for this device is in HARDSETUP. nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/state HARDSETUP Searching for this I've found some information in patch reports, for instance at git390.marist.edu and kerneltrap.org. This status is a result of a boot without the actual device available. Indeed, what we have here now. When the cable is plugged (or the vswitch connected) the state should switch to SOFTSETUP or eventualy even to UP. But it doesn't. Would it be possible to get it to UP dynamically or is this a bug that can be resolved with a reboot or network restart only? (kernel level is at 2.6.32.12-0.7). Berry. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent: vrijdag 15 juni 2012 15:47 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot If you are using VSWITCH's to attach the guest nics -- is this guest authorized for both? Scott Rohling On Fri, Jun 15, 2012 at 5:27 AM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Hi All, In a SLES11 SP1 guest I try to activate the second network adapter but it fails. The guest is cloned from a default system where both networks are configured. But this guest has started with only eth0. The nic eth1 was not available during boot. Probably it will start when rebooted but can I active a nic afterwards without a reboot (preferably without rcnetwork restart)? Running ifup I get: nlzlx204:~ # ifup eth1 eth1 name: OSA Express Network card (0.0.0f10) RTNETLINK answers: Cannot assign requested address Cannot enable interface eth1. interface eth1 is not up But the adapter looks like to be online: nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/if_name eth1 nlzlx204:~ # cat /sys/devices/qeth/0.0.0f10/online 1 Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven * +31 (0)6 22564276 [Description: atos] [Description: cid:325312309@02022011-28C8 ] 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
Re: Start networkadapter without reboot
On 6/15/2012 at 12:00 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Sigh, why didn't I think of that. Eventhough I couldn't write to recover (yes, I am root here) the echo offline and echo online did the trick. nlzlx204:~ # echo 1 /sys/devices/qeth/0.0.0f10/recover -bash: echo: write error: Operation not permitted Did you take it offline before trying the recover? Most of the writable values in devices will reject being modified if the device is already online. 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: Start networkadapter without reboot
Hi Mark, Yes I did: nlzlx204:~ # echo 0 /sys/devices/qeth/0.0.0f10/online You have new mail in /var/spool/mail/root nlzlx204:~ # echo 1 /sys/devices/qeth/0.0.0f10/recover -bash: echo: write error: Operation not permitted nlzlx204:~ # echo 1 /sys/devices/qeth/0.0.0f10/online nlzlx204:~ # ll /sys/devices/qeth/0.0.0f10/ snip --w--- 1 root root 4096 Jun 15 17:55 recover snip Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: vrijdag 15 juni 2012 18:08 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot On 6/15/2012 at 12:00 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Sigh, why didn't I think of that. Eventhough I couldn't write to recover (yes, I am root here) the echo offline and echo online did the trick. nlzlx204:~ # echo 1 /sys/devices/qeth/0.0.0f10/recover -bash: echo: write error: Operation not permitted Did you take it offline before trying the recover? Most of the writable values in devices will reject being modified if the device is already online. 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/ 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: Start networkadapter without reboot
Hi Scott, Obviously I did change the IP adresses after the clone. It's part of the clone scripts. I guess the message appears because of the fact that the address cannot be assigned to eth1 just because eth1 isn't activated at that time. Yes, the guest is connected to the vswitch and has the correct configuration. The config normally is controlled by the included profile in the directory. But in this case the guest was started first without the second nic since we didn't need backup at that time. Now the customer wants to test backup so we had to add the nic before we go into production. So I defined the nic dynamically and coupled it to TSM1. As mentioned, normally this would automatically activate the network (you're in luck, somebody has plugged in the cableetc). As for the queries: nlzlx204:~ # vmcp q v nic Adapter 0F00.P00 Type: QDIO Name: devclaw Devices: 3 MAC: 02-00-12-00-00-04 VSWITCH: SYSTEM OSNLINUX Adapter 0F10.P00 Type: QDIO Name: devclaw Devices: 3 MAC: 02-00-12-00-00-05 VSWITCH: SYSTEM TSM1 Query vswitch user nlzln204: snip Adapter Connections: Adapter Owner: NLZLN204 NIC: 0F10.P00 Name: devclaw Porttype: Access RX Packets: 3 Discarded: 0 Errors: 0 TX Packets: 9 Discarded: 0 Errors: 0 RX Bytes: 252 TX Bytes: 744 Device: 0F12 Unit: 002 Role: DATA vPort: 0065 Index: 0065 VLAN: IPv4 0760 Assigned by system VLAN: IPv6 0760 Assigned by system Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 192.168.54.204 MAC: 02-00-12-00-00-05 FE80::200:1200:100:5 MAC: 02-00-12-00-00-05 Local Multicast IP Addresses: 224.0.0.1MAC: 01-00-5E-00-00-01 FF02::1 MAC: 33-33-00-00-00-01 Local FF02::1:FF00:5 MAC: 33-33-FF-00-00-05 Local Obviously, since after a toggle of the nic the network is available, it now shows an IP address. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent: vrijdag 15 juni 2012 18:05 To: LINUX-390@VM.MARIST.EDU Subject: Re: Start networkadapter without reboot I just noticed this in your original post: RTNETLINK answers: Cannot assign requested address What does your ifcfg-eth1 look like? - is it possible the IP address you're using is not valid? You said this was a clone, so just checking network interfaces were updated correctly. I also wonder how this shows us on z/VM with a Q VSWITCH DETAILS -- does it show connected for this 2nd NIC? What does a 'vmcp q nic' show? Are addresses attached to the vswitch? (sort of the same as above).. Scott Rohling 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: Start networkadapter without reboot
On 6/15/2012 at 03:27 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net wrote: Hi Mark, Yes I did: Huh, go figure. It turns out in this case that the NIC has to be online, not offline, for the echo 1 recover to work. (I was just looking through a presentation by Dr. Stefan Reimbold of IBM in Boeblingen that showed this.) 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/
