Re: Vswitch Question
Jim, I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. That's fine if you need maintenance on your primary OSA, but not when when you want to go to the high availability steady state Ronald van der Laan
Re: Vswitch Question
Thanks Ron, I tried the following which accomplished the objective of getting the vswitch to recognize C000 as the backup: SET VSWITCH name CONNECT Thanks again Jim P. On 8/19/10 3:52 AM, Ronald van der Laan nl50...@gmail.com wrote: Jim, I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. That's fine if you need maintenance on your primary OSA, but not when when you want to go to the high availability steady state Ronald van der Laan
Re: Vswitch Question
On Thursday, 08/19/2010 at 03:52 EDT, Ronald van der Laan nl50...@gmail.com wrote: I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. Sorry, I didn't see this before. You cannot change the active RDEV on a connected VSWITCH. In Jim's case, he wanted to use the *secondary* for something else. To do that SET VSWITCH name RDEV prim_osa You will see the secondary OSA detached from the controller, and it is then available for use. Only use the DETACH command if the VSWITCH becomes unresponsive (in which case you get a snapdump of the system first to go with your PMR). Likewise, never ATTACH an OSA to a VSWITCH controller. If you want to use the *primary* for some other purpose, then you will disrupt the VSWITCH: SET VSWITCH name DISCONNECT SET VSWITCH name RDEV C000 SET VSWITCH name CONNECT To add the former primary OSA back: SET VSWITCH name RDEV C000 prim_osa Of course, prim_osa is now the backup! You could use the disconnect three-step to get it back as the primary, but that's an itch that need not be scratched. (Who cares which one is the backup? It's not like you would use one fast, one slow!) If you want to add and delete OSAs on the fly with no disruption, then you engage link aggregation and define a port group. Alan Altmark z/VM Development IBM Endicott
Re: Vswitch Question
Alan, Great info. Thanks. Jim P. On 8/19/10 9:04 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Thursday, 08/19/2010 at 03:52 EDT, Ronald van der Laan nl50...@gmail.com wrote: I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. Sorry, I didn't see this before. You cannot change the active RDEV on a connected VSWITCH. In Jim's case, he wanted to use the *secondary* for something else. To do that SET VSWITCH name RDEV prim_osa You will see the secondary OSA detached from the controller, and it is then available for use. Only use the DETACH command if the VSWITCH becomes unresponsive (in which case you get a snapdump of the system first to go with your PMR). Likewise, never ATTACH an OSA to a VSWITCH controller. If you want to use the *primary* for some other purpose, then you will disrupt the VSWITCH: SET VSWITCH name DISCONNECT SET VSWITCH name RDEV C000 SET VSWITCH name CONNECT To add the former primary OSA back: SET VSWITCH name RDEV C000 prim_osa Of course, prim_osa is now the backup! You could use the disconnect three-step to get it back as the primary, but that's an itch that need not be scratched. (Who cares which one is the backup? It's not like you would use one fast, one slow!) If you want to add and delete OSAs on the fly with no disruption, then you engage link aggregation and define a port group. Alan Altmark z/VM Development IBM Endicott
VSWITCH Question
We're updating some OSA micro code and I'm trying to determine the most effective way to take the VSWITCH connected to a production OSA offline so the code can update properly. I know that the OSA device has to be vary'd offline, as does the path and CHPID. Is there a way to tell a VSWITCH to shutdown without destroying it? This particular VSWITCH doesn't have a second fail-over address. If I detach the device from the VSWITCH controller, vary the device, path and CHPID offline, will this suffice? Thanks in advance, Dave Keeton
Re: VSWITCH Question
Will work, but would be nicer to it if you did a set vswitch disconnect first. You will lose all connectivity with no backup, but you know that ;) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Keeton Sent: Monday, May 17, 2010 3:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Question We're updating some OSA micro code and I'm trying to determine the most effective way to take the VSWITCH connected to a production OSA offline so the code can update properly. I know that the OSA device has to be vary'd offline, as does the path and CHPID. Is there a way to tell a VSWITCH to shutdown without destroying it? This particular VSWITCH doesn't have a second fail-over address. If I detach the device from the VSWITCH controller, vary the device, path and CHPID offline, will this suffice? Thanks in advance, Dave Keeton
Re: VSWITCH Question
Thank you, Marcy! I appreciate the quick response. Regards, Dave On Mon, 2010-05-17 at 18:32 -0500, Marcy Cortes wrote: Will work, but would be nicer to it if you did a set vswitch disconnect first. You will lose all connectivity with no backup, but you know that ;) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Keeton Sent: Monday, May 17, 2010 3:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Question We're updating some OSA micro code and I'm trying to determine the most effective way to take the VSWITCH connected to a production OSA offline so the code can update properly. I know that the OSA device has to be vary'd offline, as does the path and CHPID. Is there a way to tell a VSWITCH to shutdown without destroying it? This particular VSWITCH doesn't have a second fail-over address. If I detach the device from the VSWITCH controller, vary the device, path and CHPID offline, will this suffice? Thanks in advance, Dave Keeton
Re: OSA VSWITCH QUESTION
Scott, Here the information from my z/Linux ADMIN. Note that the IP's are masked as we cannot send or publicize them Security reasons. Let me know what you think. [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=no BOOTPROTO=static IPADDR=10.15.333.444 MACADDR= MTU=1500 NETMASK=255.255.0.0 NETTYPE=qeth ONBOOT=yes PORTNAME= SUBCHANNELS=0.0.7203,0.0.7204,0.0.7205 TYPE=Ethernet [r...@e49l054p ~]# [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 ARP=no BOOTPROTO=static IPADDR=10.16.333.444 MTU=1500 NETMASK=255.255.0.0 NETTYPE=qeth ONBOOT=yes PORTNAME= SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 TYPE=Ethernet [r...@e49l054p ~]# I think this may be part of it; [r...@e49l054p ~]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=e49l054p GATEWAY=10.15.333.444 Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Scott Rohling Sent: Tuesday, March 16, 2010 4:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: OSA VSWITCH QUESTION Terry - we need to see the ifcfg-eth1 file - and maybe ifcfg-eth0 too to help... I think you'll find them under /etc/sysconfig/network-scripts/ (?) You're showing us the config for what works - but not the config for what doesn't... Scott On Tue, Mar 16, 2010 at 1:29 PM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Error! Filename not specified. Hi I have a dilemma that I hope you can help with: I have cloned a z/VM LPAR and a z/Linux guest from my Production system. I have a VSWITCH set up and a matching NIC def in the Directory for the z/Linux guest. I can display the OSA and see that it is attached to the VSWITCH and I can see that the NIC was configured correctly when the z/Linux guest is logged on. The z/Linux guest is RHEL 5.2. The problem is when the guest initializes we see this message: Bringing up interface eth1: qeth device eth1 does not seem to be present, delaying initialization. When I display the VSWITCH Q VSWITCH DET I expected to see the IP address associated with the network interface show up in the VSWITCH which tells me the we can get to the z/Linux guest but I don't see the IP. Now if we bring the z/Linux guest up in RESCUE mode where it is reading the CONF file where I specifically enter the IP address I can display the VSWITCH and see the IP address associated with the VSWITCH as I expected and we can PING the z/Linux guest and login to it. So what am I doing wrong here? Why on a normal boot can't I see the IP in the VSWITCH and hence login into the z/Linux guest or PING it but when I load it using the CONF file in RESCUE mode I can login to the guest and PING it what am I missing?: CONF FILE: /* configuration information for RESCUE MODE */ HOSTNAME=E49L054P.CMS.HHS.GOV DASD=700,800-831 NETTYPE=qeth SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 PORTNAME= IPADDR=10.16.49.13 NETWORK=10.16.0.0 NETMASK=255.255.0.0 BROADCAST=10.16.255.255 GATEWAY=10.16.0.254 SEARCHDNS=cms.hhs.gov LAYER2=0 DNS=10.15.0.117 MTU=1500 VSWITCH WHEN GUEST is BROUGHT UP NORMALLY(No 10.16.49.13 IP): q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110318 Errors: 0 TX Packets: 357Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99369 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 986Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 89162TX Bytes: 0 Device: 7405 Unit: 002 Role: DATA Port: 0073 Index: 0010 Options: Broadcast Multicast IPv6 IPv4 VLAN VSWITCH DISPLAY AFTER GUEST UP IN RESCUE MODE : q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER
Re: OSA VSWITCH QUESTION
Well - can't help you then with whether correct ip addresses are being used, etc... the main point was to ensure the ifcfg files had the correct values (the same you use with rescue system).But in reading more carefully - I see the problem seems to be that eth1 is not available. So does eth0 work? When you do the rescue system - you are likely using eth0 -- and not eth1. The message seems to indicate that the address for eth1 is not available -- your ifcfg-eth1 files shows 7403-7405 being used. What does a 'vmcp q nic' show? Is there really a 7403-7405 NIC device defined to the guest? Having eth0/eth1 implies you have 2 NICs. It's complaining about eth1 -- so what about eth0? Is that working? Scott On Wed, Mar 17, 2010 at 8:55 AM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Scott, Here the information from my z/Linux ADMIN. Note that the IP’s are masked as we cannot send or publicize them Security reasons. Let me know what you think. [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=no BOOTPROTO=static IPADDR=10.15.333.444 MACADDR= MTU=1500 NETMASK=255.255.0.0 NETTYPE=qeth ONBOOT=yes PORTNAME= SUBCHANNELS=0.0.7203,0.0.7204,0.0.7205 TYPE=Ethernet [r...@e49l054p ~]# [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 ARP=no BOOTPROTO=static IPADDR=10.16.333.444 MTU=1500 NETMASK=255.255.0.0 NETTYPE=qeth ONBOOT=yes PORTNAME= SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 TYPE=Ethernet [r...@e49l054p ~]# I think this may be part of it; [r...@e49l054p ~]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=e49l054p GATEWAY=10.15.333.444 *Thank You,* * * *Terry Martin* *Lockheed Martin - Citic* *z/OS and z/VM Performance Tuning and Operating Systems Support* *Office - 443 348-2102* *Cell - 443 632-4191* *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Scott Rohling *Sent:* Tuesday, March 16, 2010 4:54 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: OSA VSWITCH QUESTION Terry - we need to see the ifcfg-eth1 file - and maybe ifcfg-eth0 too to help... I think you'll find them under /etc/sysconfig/network-scripts/ (?) You're showing us the config for what works - but not the config for what doesn't... Scott On Tue, Mar 16, 2010 at 1:29 PM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: *Error! Filename not specified.* Hi I have a dilemma that I hope you can help with: I have cloned a z/VM LPAR and a z/Linux guest from my Production system. I have a VSWITCH set up and a matching NIC def in the Directory for the z/Linux guest. I can display the OSA and see that it is attached to the VSWITCH and I can see that the NIC was configured correctly when the z/Linux guest is logged on. The z/Linux guest is RHEL 5.2. The problem is when the guest initializes we see this message: Bringing up interface eth1: qeth device eth1 does not seem to be present, delaying initialization. When I display the VSWITCH Q VSWITCH DET I expected to see the IP address associated with the network interface show up in the VSWITCH which tells me the we can get to the z/Linux guest but I don’t see the IP. Now if we bring the z/Linux guest up in RESCUE mode where it is reading the CONF file where I specifically enter the IP address I can display the VSWITCH and see the IP address associated with the VSWITCH as I expected and we can PING the z/Linux guest and login to it. So what am I doing wrong here? Why on a normal boot can’t I see the IP in the VSWITCH and hence login into the z/Linux guest or PING it but when I load it using the CONF file in RESCUE mode I can login to the guest and PING it what am I missing?: CONF FILE: /* configuration information for RESCUE MODE */ HOSTNAME=E49L054P.CMS.HHS.GOV DASD=700,800-831 NETTYPE=qeth SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 PORTNAME= IPADDR=10.16.49.13 NETWORK=10.16.0.0 NETMASK=255.255.0.0 BROADCAST=10.16.255.255 GATEWAY=10.16.0.254 SEARCHDNS=cms.hhs.gov LAYER2=0 DNS=10.15.0.117 MTU=1500 VSWITCH WHEN GUEST is BROUGHT UP NORMALLY(No 10.16.49.13 IP): q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110318 Errors: 0 TX Packets: 357Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99369 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001
Re: OSA VSWITCH QUESTION
Hmm ... well - based on that, I'm not sure what's wrong, but will make these observations: - The only NIC you have defined is 7403-5 ...So you should not expect more than one of the ethx devices to come up. You need to define the devices and couple them to the vswitch's before the devices will be recognized. When you boot normally - you show that none of the devices are present for any of the Linux eth devices. Not just eth1 -- but also eth0 and eth2. - The ifcfg-eth1 file you listed does show 7403-5 being used, so I'm not sure why it's not seeing it. It makes me wonder if we're seeing the right ifcfg-eth1 file -- or if maybe an alias eth1 qeth is needed in modprobe.conf? - The ifcfg-eth0 file shows 7203-5 being used -- these don't appear to be defined to your guest. Any reason why not? - There also seems to be an ifcfg-eth2 based on your error messages.. When you use rescue mode - it only knows about eth0 ... and apparently it's defined correctly (correct device addresses) in the conf file and comes up. Which is why I'm suspecting a problem with the network config files - but your ifcfg-eth1 looks correct - so I'm not sure what's wrong offhand. The only other thing I can think of is that the PROFILE EXEC used when you come up normally does something to the NIC -- but your CP Q NIC seems to show it's there. Is the VSWITCH identically defined on both lpars? (layer3, etc).. Scott On Wed, Mar 17, 2010 at 9:38 AM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Scott, Yes ETH0 is working and being used when we boot in RESCUE mode. When we try to boot normally it is ETH1 that we would use and that is not coming up. So something is different in how we come up normally and with RESCUE mode where we specify the ETH0. Wish I knew what that difference was. It is probably something right under my nose! When booted normally not in RESCUE mode: Bringing up interface eth0: qeth device eth0 does not seem to be present, delay ing initialization. [FAILED] Bringing up interface eth1: qeth device eth1 does not seem to be present, delay ing initialization. [FAILED] Bringing up interface eth2: qeth device eth2 does not seem to be present, delay ing initialization. [FAILED] 00: CP Q NIC 00: Adapter 7403 Type: QDIO Name: UNASSIGNED Devices: 3 00: MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VSE4PS11 When booted in RESCUE mode: eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:10.16.XX.XX Bcast:10.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::200:0:200:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:624 (624.0 B) TX bytes:552 (552.0 B) CP Q NIC Adapter 7403 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VSE4PS11 *Thank You,* * * *Terry Martin* *Lockheed Martin - Citic* *z/OS and z/VM Performance Tuning and Operating Systems Support* *Office - 443 348-2102* *Cell - 443 632-4191* *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Scott Rohling *Sent:* Wednesday, March 17, 2010 11:13 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: OSA VSWITCH QUESTION Well - can't help you then with whether correct ip addresses are being used, etc... the main point was to ensure the ifcfg files had the correct values (the same you use with rescue system).But in reading more carefully - I see the problem seems to be that eth1 is not available. So does eth0 work? When you do the rescue system - you are likely using eth0 -- and not eth1. The message seems to indicate that the address for eth1 is not available -- your ifcfg-eth1 files shows 7403-7405 being used. What does a 'vmcp q nic' show? Is there really a 7403-7405 NIC device defined to the guest? Having eth0/eth1 implies you have 2 NICs. It's complaining about eth1 -- so what about eth0? Is that working? Scott On Wed, Mar 17, 2010 at 8:55 AM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Scott, Here the information from my z/Linux ADMIN. Note that the IP’s are masked as we cannot send or publicize them Security reasons. Let me know what you think. [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=no BOOTPROTO=static IPADDR=10.15.333.444 MACADDR= MTU=1500 NETMASK=255.255.0.0 NETTYPE=qeth ONBOOT=yes PORTNAME= SUBCHANNELS=0.0.7203,0.0.7204,0.0.7205 TYPE=Ethernet [r...@e49l054p ~]# [r...@e49l054p ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 ARP=no BOOTPROTO=static IPADDR=10.16.333.444 MTU=1500 NETMASK
OSA VSWITCH QUESTION
Hi I have a dilemma that I hope you can help with: I have cloned a z/VM LPAR and a z/Linux guest from my Production system. I have a VSWITCH set up and a matching NIC def in the Directory for the z/Linux guest. I can display the OSA and see that it is attached to the VSWITCH and I can see that the NIC was configured correctly when the z/Linux guest is logged on. The z/Linux guest is RHEL 5.2. The problem is when the guest initializes we see this message: Bringing up interface eth1: qeth device eth1 does not seem to be present, delaying initialization. When I display the VSWITCH Q VSWITCH DET I expected to see the IP address associated with the network interface show up in the VSWITCH which tells me the we can get to the z/Linux guest but I don't see the IP. Now if we bring the z/Linux guest up in RESCUE mode where it is reading the CONF file where I specifically enter the IP address I can display the VSWITCH and see the IP address associated with the VSWITCH as I expected and we can PING the z/Linux guest and login to it. So what am I doing wrong here? Why on a normal boot can't I see the IP in the VSWITCH and hence login into the z/Linux guest or PING it but when I load it using the CONF file in RESCUE mode I can login to the guest and PING it what am I missing?: CONF FILE: /* configuration information for RESCUE MODE */ HOSTNAME=E49L054P.CMS.HHS.GOV DASD=700,800-831 NETTYPE=qeth SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 PORTNAME= IPADDR=10.16.49.13 NETWORK=10.16.0.0 NETMASK=255.255.0.0 BROADCAST=10.16.255.255 GATEWAY=10.16.0.254 SEARCHDNS=cms.hhs.gov LAYER2=0 DNS=10.15.0.117 MTU=1500 VSWITCH WHEN GUEST is BROUGHT UP NORMALLY(No 10.16.49.13 IP): q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110318 Errors: 0 TX Packets: 357Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99369 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 986Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 89162TX Bytes: 0 Device: 7405 Unit: 002 Role: DATA Port: 0073 Index: 0010 Options: Broadcast Multicast IPv6 IPv4 VLAN VSWITCH DISPLAY AFTER GUEST UP IN RESCUE MODE : q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110392 Errors: 0 TX Packets: 364Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99921 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 491Discarded: 0 Errors: 0 TX Packets: 7 Discarded: 0 Errors: 0 RX Bytes: 43429TX Bytes: 552 Device: 7405 Unit: 002 Role: DATA Port: 0074 Index: 0011 Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 10.16.49.13 MAC: 02-00-00-00-00-04 FE80::200:0:100:4MAC: 02-00-00-00-00-04 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:4 MAC: 33-33-FF-00-00-04 Local q vswitch vse4ps11 det VSWI TCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxco Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell -
Re: OSA VSWITCH QUESTION
Terry - we need to see the ifcfg-eth1 file - and maybe ifcfg-eth0 too to help... I think you'll find them under /etc/sysconfig/network-scripts/ (?) You're showing us the config for what works - but not the config for what doesn't... Scott On Tue, Mar 16, 2010 at 1:29 PM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Hi I have a dilemma that I hope you can help with: I have cloned a z/VM LPAR and a z/Linux guest from my Production system. I have a VSWITCH set up and a matching NIC def in the Directory for the z/Linux guest. I can display the OSA and see that it is attached to the VSWITCH and I can see that the NIC was configured correctly when the z/Linux guest is logged on. The z/Linux guest is RHEL 5.2. The problem is when the guest initializes we see this message: Bringing up interface eth1: qeth device eth1 does not seem to be present, delaying initialization. When I display the VSWITCH Q VSWITCH DET I expected to see the IP address associated with the network interface show up in the VSWITCH which tells me the we can get to the z/Linux guest but I don’t see the IP. Now if we bring the z/Linux guest up in RESCUE mode where it is reading the CONF file where I specifically enter the IP address I can display the VSWITCH and see the IP address associated with the VSWITCH as I expected and we can PING the z/Linux guest and login to it. So what am I doing wrong here? Why on a normal boot can’t I see the IP in the VSWITCH and hence login into the z/Linux guest or PING it but when I load it using the CONF file in RESCUE mode I can login to the guest and PING it what am I missing?: CONF FILE: /* configuration information for RESCUE MODE */ HOSTNAME=E49L054P.CMS.HHS.GOV DASD=700,800-831 NETTYPE=qeth SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 PORTNAME= IPADDR=10.16.49.13 NETWORK=10.16.0.0 NETMASK=255.255.0.0 BROADCAST=10.16.255.255 GATEWAY=10.16.0.254 SEARCHDNS=cms.hhs.gov LAYER2=0 DNS=10.15.0.117 MTU=1500 VSWITCH WHEN GUEST is BROUGHT UP NORMALLY(No 10.16.49.13 IP): q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110318 Errors: 0 TX Packets: 357Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99369 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 986Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 89162TX Bytes: 0 Device: 7405 Unit: 002 Role: DATA Port: 0073 Index: 0010 Options: Broadcast Multicast IPv6 IPv4 VLAN VSWITCH DISPLAY AFTER GUEST UP IN RESCUE MODE : q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110392 Errors: 0 TX Packets: 364Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99921 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 491Discarded: 0 Errors: 0 TX Packets: 7 Discarded: 0 Errors: 0 RX Bytes: 43429TX Bytes: 552 Device: 7405 Unit: 002 Role: DATA Port: 0074 Index: 0011 Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 10.16.49.13 MAC: 02-00-00-00-00-04 FE80::200:0:100:4MAC: 02-00-00-00-00-04 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:4 MAC: 33-33-FF-00-00-04 Local q vswitch vse4ps11 det VSWI TCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1 Maxco *Thank You,* * * *Terry Martin* *Lockheed Martin - Citic* *z/OS and z/VM Performance Tuning and Operating Systems Support* *Office - 443 348-2102* *Cell - 443 632-4191*
Re: OSA VSWITCH QUESTION
I will work on getting the additional information. Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Scott Rohling Sent: Tuesday, March 16, 2010 4:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: OSA VSWITCH QUESTION Terry - we need to see the ifcfg-eth1 file - and maybe ifcfg-eth0 too to help... I think you'll find them under /etc/sysconfig/network-scripts/ (?) You're showing us the config for what works - but not the config for what doesn't... Scott On Tue, Mar 16, 2010 at 1:29 PM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Error! Filename not specified. Hi I have a dilemma that I hope you can help with: I have cloned a z/VM LPAR and a z/Linux guest from my Production system. I have a VSWITCH set up and a matching NIC def in the Directory for the z/Linux guest. I can display the OSA and see that it is attached to the VSWITCH and I can see that the NIC was configured correctly when the z/Linux guest is logged on. The z/Linux guest is RHEL 5.2. The problem is when the guest initializes we see this message: Bringing up interface eth1: qeth device eth1 does not seem to be present, delaying initialization. When I display the VSWITCH Q VSWITCH DET I expected to see the IP address associated with the network interface show up in the VSWITCH which tells me the we can get to the z/Linux guest but I don't see the IP. Now if we bring the z/Linux guest up in RESCUE mode where it is reading the CONF file where I specifically enter the IP address I can display the VSWITCH and see the IP address associated with the VSWITCH as I expected and we can PING the z/Linux guest and login to it. So what am I doing wrong here? Why on a normal boot can't I see the IP in the VSWITCH and hence login into the z/Linux guest or PING it but when I load it using the CONF file in RESCUE mode I can login to the guest and PING it what am I missing?: CONF FILE: /* configuration information for RESCUE MODE */ HOSTNAME=E49L054P.CMS.HHS.GOV DASD=700,800-831 NETTYPE=qeth SUBCHANNELS=0.0.7403,0.0.7404,0.0.7405 PORTNAME= IPADDR=10.16.49.13 NETWORK=10.16.0.0 NETMASK=255.255.0.0 BROADCAST=10.16.255.255 GATEWAY=10.16.0.254 SEARCHDNS=cms.hhs.gov LAYER2=0 DNS=10.15.0.117 MTU=1500 VSWITCH WHEN GUEST is BROUGHT UP NORMALLY(No 10.16.49.13 IP): q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110318 Errors: 0 TX Packets: 357Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99369 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 986Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 89162TX Bytes: 0 Device: 7405 Unit: 002 Role: DATA Port: 0073 Index: 0010 Options: Broadcast Multicast IPv6 IPv4 VLAN VSWITCH DISPLAY AFTER GUEST UP IN RESCUE MODE : q vswitch vse4ps11 det VSWITCH SYSTEM VSE4PS11 Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-03 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8903 VDEV: 8903 Controller: DTCVSW2 VSWITCH Connection: MAC address: 00-14-5E-B7-D4-94 RX Packets: 380Discarded: 110392 Errors: 0 TX Packets: 364Discarded: 0 Errors: 0 RX Bytes: 31684TX Bytes: 99921 Device: 8903 Unit: 000 Role: DATA Port: 0001 Index: 0001 Adapter Connections: Adapter Owner: E49L054P NIC: 7403 Name: UNASSIGNED RX Packets: 491Discarded: 0 Errors: 0 TX Packets: 7 Discarded: 0 Errors: 0 RX Bytes: 43429TX Bytes: 552 Device: 7405 Unit: 002 Role: DATA Port: 0074 Index: 0011 Options: Broadcast Multicast
Yet another vSwitch question...
How many vSwitch rdevices can a single controller userid control? I had thought it was one, but it appears that they can support more than one... Is there a limit? We were adding a second vSwitch in preparation to convert from fiber OSAs to copper, and I defined two additional controller userids in the CP directory and set them, giving me DTCVSW1-4. I expected the second vSwitch to use 3 and 4, but when I query the vSwitches, both are using 1 and 2: q vswitch VSWITCH SYSTEM VSWC Type: VSWITCH Connected: 1Maxconn: INFINITE PERSISTENT RESTRICTEDPRIROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-15 State: Ready IPTimeout: 5 QueueStorage: 8 RDEV: 8C00 VDEV: 8C00 Controller: DTCVSW1 RDEV: 8D00 VDEV: 8D00 Controller: DTCVSW2 BACKUP VSWITCH SYSTEM VSWG Type: VSWITCH Connected: 36 Maxconn: INFINITE PERSISTENT RESTRICTEDPRIROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Portname: OSASUE2RDEV: 8A00 Controller: DTCVSW1 VDEV: 8A00 RDEV: 8B00 VDEV: 8B00 Controller: DTCVSW2 BACKUP Ready; T=0.01/0.01 09:16:29 So... Is there a limit, and where should I have looked to find it? -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different.
Re: Yet another vSwitch question...
The Vswitch statement supports up to 3 OSA devices for failover. If you're using link aggregation, you can use up to 8; but they are not coded on the Vswitch statement. RPN01 wrote: How many vSwitch rdevices can a single controller userid control? I had thought it was one, but it appears that they can support more than one... Is there a limit? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
Re: Yet another vSwitch question...
On Wednesday, 11/26/2008 at 10:35 EST, RPN01 [EMAIL PROTECTED] wrote: How many vSwitch rdevices can a single controller userid control? I had thought it was one, but it appears that they can support more than one... Is there a limit? There is no [practical] limit. That's why DTCVSW1 and DTCVSW2 are the only controllers you'll need. The 2nd VSWITCH will probably choose DTCVSW2 as primary and DTCVSW1 as backup, as CP will load balance among the eligible controllers. This is why you shouldn't override the default of CONTROLLER * unless directed to by the Support Center. And in that case, having a 3rd controller handy (but typically not logged on) would be a good idea. That way diagnositics can be obtained without disrupting other VSWITCHes. Alan Altmark z/VM Development IBM Endicott
Re: Yet another vSwitch question...
True, but has nothing to do with the question How many OSA addresses can one of the controller userids, such as DTCVSW1 in the installation system, support at one time? -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 11/26/08 9:43 AM, Rich Smrcina [EMAIL PROTECTED] wrote: The Vswitch statement supports up to 3 OSA devices for failover. If you're using link aggregation, you can use up to 8; but they are not coded on the Vswitch statement. RPN01 wrote: How many vSwitch rdevices can a single controller userid control? I had thought it was one, but it appears that they can support more than one... Is there a limit?
VSWITCH question
I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
Re: VSWITCH question
No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
The new VSWITCH is the same subnet and guests should all be able to use the same IP's? Scott Rohling On Tue, Oct 14, 2008 at 5:14 PM, Daniel Allen [EMAIL PROTECTED] wrote: No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
Is the 2nd vswitch up - show us Q VSWITCH 2ndone DETAILS. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Tuesday, October 14, 2008 4:14 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH question No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
An OSA/VSWITCH question
If I have a z/OS 1.4 guest running under z/VM with dedicated OSA addresses, will it work using using VSWITCH ? The z/OS guest uses a port name but the VSWITCH does not. Or does it matter ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: An OSA/VSWITCH question
The VSWITCH does not need a portname -- from reading other posts, there is a caution to make sure you do NOT use the same port name z/OS is using. I see it set to DONTCARE or NOTUSED when I look at various VSWITCH details.. Scott Rohling On Mon, Oct 6, 2008 at 10:26 AM, Daniel Allen [EMAIL PROTECTED] wrote: If I have a z/OS 1.4 guest running under z/VM with dedicated OSA addresses, will it work using using VSWITCH ? The z/OS guest uses a port name but the VSWITCH does not. Or does it matter ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: An OSA/VSWITCH question
Thanks, Scott. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, October 06, 2008 9:40 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: An OSA/VSWITCH question The VSWITCH does not need a portname -- from reading other posts, there is a caution to make sure you do NOT use the same port name z/OS is using. I see it set to DONTCARE or NOTUSED when I look at various VSWITCH details.. Scott Rohling On Mon, Oct 6, 2008 at 10:26 AM, Daniel Allen [EMAIL PROTECTED] wrote: If I have a z/OS 1.4 guest running under z/VM with dedicated OSA addresses, will it work using using VSWITCH ? The z/OS guest uses a port name but the VSWITCH does not. Or does it matter ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
You could also add the SET VSWITCH GRANT statements to AUTOLOG1's profile (prior to RACF/VM or your ESM's autologging, as TCPIP and such should be autologged in AUTOLOG2 profile exec in that case) OR you could add a profile for the GRANT statements via RACF/VM or your ESM if you have one and are really tight on security requirements. Doug -Original Message- From: The IBM z/VM Operating System on behalf of Hodge, Robert L Sent: Fri 16-May-08 18:45 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
Someone commented that it was somewhat clunky, but what we've been doing for the grants is to add two COMMAND statements to each guest's CP Directory entry (actually via an include); the first does the grant for the user, and the second does a couple to connect up the vSwitch, if it isn't already connected. Before this, each new Linux guest had to be added to either the SYSTEM CONFIG (problematic) or AUTOLOG1 (time consuming), and either method allows the person doing it to forget, make a mistake or make some typo in the addition that could cause problems much later during the next IPL, at which time it will take at least a short time to diagnose and repair. Having the whole thing taken care of in one entry in the CP Directory, and included in each guest that needs it, is much less prone to any errors someone (such as me) might tend to make. It's one less thing to remember when creating a new Linux guest. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 5/20/08 10:40 AM, Ponte, Doug [EMAIL PROTECTED] wrote: You could also add the SET VSWITCH GRANT statements to AUTOLOG1's profile (prior to RACF/VM or your ESM's autologging, as TCPIP and such should be autologged in AUTOLOG2 profile exec in that case) OR you could add a profile for the GRANT statements via RACF/VM or your ESM if you have one and are really tight on security requirements. Doug -Original Message- From: The IBM z/VM Operating System on behalf of Hodge, Robert L Sent: Fri 16-May-08 18:45 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
On Tuesday, 05/20/2008 at 02:37 EDT, RPN01 [EMAIL PROTECTED] wrote: Someone commented that it was somewhat clunky, but what we've been doing for the grants is to add two COMMAND statements to each guest's CP Directory entry (actually via an include); the first does the grant for the user, and the second does a couple to connect up the vSwitch, if it isn't already connected. Before this, each new Linux guest had to be added to either the SYSTEM CONFIG (problematic) or AUTOLOG1 (time consuming), and either method allows the person doing it to forget, make a mistake or make some typo in the addition that could cause problems much later during the next IPL, at which time it will take at least a short time to diagnose and repair. Having the whole thing taken care of in one entry in the CP Directory, and included in each guest that needs it, is much less prone to any errors someone (such as me) might tend to make. It's one less thing to remember when creating a new Linux guest. Or the NICDEF plus a single entry in your ESM. RACF has authorization controls for VSWITCHes, Guest LANs, and VLAN IDs. Set it and forget it. Alan Altmark z/VM Development IBM Endicott
VSWITCH question
I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
VSWITCH question
I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: Vswitch Question from newbie
well, you could create a disconnected vswitch for the .5 network, or just a guest lan. The disconnected vswitch (when you define the vswitch don't code any RDEVs) has the advantage that virtual machine membership, and vlan membership should you go that route, is RACF protected. I think with this configuration you've outlined you will need to instruct each linux machine to not allow any traffic from the other interfaces on the .5. But, yeah, this can be done. David Kreuter Mary Elwood wrote: I hate to have to ask this, but we've looked through documentation and from what I've read it doesn't appear this can be done. But since I'm new to z/VM, Linux, and TCPIP I need to ask the question. Below is the scenario We need to know if we can do what we need to do using vswitches. We run z/VM 5.1 with SUSE SLES9. We run on a z990 (2084). On the z990 we have three OSA’s. Two OSA’s will go to a vswitch for the 10.10.8 network and will have three linux images in the network. We will have one OSA that will to go a vswitch for the 10.10.6 network and will have one linux image. We then want to create a vswitch for a 10.10.5 network that would be a private network where all four linux images can communicate. We need the one linux image on the 10.10.6 network to be able to push code changes up to the three linux images on the 10.10.8 network. Is this possible??? The vswitch for the 10.10.5 network has no OSA on purpose. We want the 10.10.5 to be a separate virtual network internet to z/VM only. We can have no outside access to the 10.10.5 network other than the four linux images on the 10.10.8 and the 10.10..6 networks. I hope this is clear. Thank you for your help and patience. Mary Elwood Navy Federal Credit Union Vienna, VA 703-206-4201 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/430 - Release Date: 28/08/2006
Re: Vswitch Question from newbie
At 01:44 PM 8/29/2006, you wrote: On Tuesday, 08/29/2006 at 01:21 AST, Mary Elwood [EMAIL PROTECTED] wrote: As a newbie, I hope you'll take the opportunity to attend the System z9 and zSeries Expo in October in Orlando. Go to http://www.vm.ibm.com/events and click on the link for the Expo. We're providing a lot of education on the VSWITCH and Guest LANs! Mary, IF you cant make it to the Z Expo, please consider the next SHARE which will be in Tampa the week of Feb 11. Plenty of good sessions there including a few by Alan himself. Duane
