Re: Defining VSWITCH difficulties
On Friday, 08/27/2010 at 02:53 EDT, Sterling James wrote: > It is needed if you share an OSA port with zOS. Sorry, Jim, but it isn't. If you don't specify the port name, no check is made. If you specify it, it must match. If you have evidence to the contrary, please call it in. Alan Altmark z/VM Development IBM Endicott
Re: Defining VSWITCH difficulties
No it's not. I share my OSA with z/OS. z/OS needs a portname, z/VM does not. On Fri, Aug 27, 2010 at 2:53 PM, Sterling James wrote: > It is needed if you share an OSA port with zOS. > > > > From: Mike Walter To: IBMVM@LISTSERV.UARK.EDU > Date: 08/27/2010 01:46 PM Subject: Re: Defining VSWITCH difficulties Sent > by: The IBM z/VM Operating System > -- > > > > > Um, uh... then why not simply remove the PORT argument from the z/VM > manuals and from the command syntax itself - issuing an error message > (unsupported operand) when it is specified? > I'll submit an RCF if it will help with that part. :-) > > That would not help the issue with Linux guests, but there would be one > less bullet in the chamber, no? > > Respectfully, > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > *"Alan Altmark" * > > Sent by: "The IBM z/VM Operating System" > > 08/27/2010 01:38 PM > Please respond to > "The IBM z/VM Operating System" > > >To > IBMVM@LISTSERV.UARK.EDU > cc > Subject > Re: Defining VSWITCH difficulties > > > > > > > On Friday, 08/27/2010 at 12:26 EDT, George Henke/NYLIC > wrote: > > 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or > incorrect > > required port name > > 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: > > > > The VSWITCH expects, requires a port name for 181D. > > > > Either the Portname or the Port number which defaulted to P0 is wrong. > > > > You can specify port number as 181d.Px > > > > You may want to try a QUERY VSWITCH RDEV 181D for more information. > > I've been harping on this since port names became optional in October 2003 > (7 years ago!): DO NOT SPECIFY A PORT *NAME* in Linux or z/VM IP or > VSWITCH configurations! > > Yes, they are required in z/OS, but that's a z/OS Comm Server issue. > > Alan Altmark > z/VM Development > IBM Endicott > > -- > > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. > > - Please consider the environment > before printing this email and any attachments. This e-mail and any > attachments are intended only for the individual or company to which it is > addressed and may contain information which is privileged, confidential and > prohibited from disclosure or unauthorized use under applicable law. If you > are not the intended recipient of this e-mail, you are hereby notified that > any use, dissemination, or copying of this e-mail or the information > contained in this e-mail is strictly prohibited by the sender. If you have > received this transmission in error, please return the material received to > the sender and delete all copies from your system. > > -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: Defining VSWITCH difficulties
> I've been harping on this since port names became optional in October 2003 > (7 years ago!): DO NOT SPECIFY A PORT *NAME* in Linux or z/VM IP or > VSWITCH configurations! > > Yes, they are required in z/OS, but that's a z/OS Comm Server issue. > > Alan Altmark > z/VM Development > IBM Endicott How 'bout continuing to syntax-check the command (simply for compatability) but no-op'ing the PORTNAME function? Mark Wheeler UnitedHealth Group
Re: Defining VSWITCH difficulties
On Friday, 08/27/2010 at 02:47 EDT, Mike Walter wrote: > Um, uh... then why not simply remove the PORT argument from the z/VM manuals > and from the command syntax itself - issuing an error message (unsupported > operand) when it is specified? > I'll submit an RCF if it will help with that part. :-) > > That would not help the issue with Linux guests, but there would be one less > bullet in the chamber, no? Don't think we haven't considered it! :-) We don't do it, though, because it would create an incompatibility and people would complain. For most of you, it's not broken, so we're inclined not to fix it in a way that would create breakage. If you want to submit an RCF that the pubs need to be clear on the lack of need to specify these options, that would be good. There are probably some people using the port name to help them ensure they are sharing ports with hosts that they *think* they're sharing with. They would get really annoyed. (Every time we assume no one is doing something, we're always wrong.) Alan Altmark z/VM Development IBM Endicott
Re: Defining VSWITCH difficulties
It is needed if you share an OSA port with zOS. From: Mike Walter To: IBMVM@LISTSERV.UARK.EDU Date: 08/27/2010 01:46 PM Subject: Re: Defining VSWITCH difficulties Sent by: The IBM z/VM Operating System Um, uh... then why not simply remove the PORT argument from the z/VM manuals and from the command syntax itself - issuing an error message (unsupported operand) when it is specified? I'll submit an RCF if it will help with that part. :-) That would not help the issue with Linux guests, but there would be one less bullet in the chamber, no? Respectfully, Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Alan Altmark" Sent by: "The IBM z/VM Operating System" 08/27/2010 01:38 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Defining VSWITCH difficulties On Friday, 08/27/2010 at 12:26 EDT, George Henke/NYLIC wrote: > 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect > required port name > 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: > > The VSWITCH expects, requires a port name for 181D. > > Either the Portname or the Port number which defaulted to P0 is wrong. > > You can specify port number as 181d.Px > > You may want to try a QUERY VSWITCH RDEV 181D for more information. I've been harping on this since port names became optional in October 2003 (7 years ago!): DO NOT SPECIFY A PORT *NAME* in Linux or z/VM IP or VSWITCH configurations! Yes, they are required in z/OS, but that's a z/OS Comm Server issue. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. - Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.
Re: Defining VSWITCH difficulties
Um, uh... then why not simply remove the PORT argument from the z/VM manuals and from the command syntax itself - issuing an error message (unsupported operand) when it is specified? I'll submit an RCF if it will help with that part. :-) That would not help the issue with Linux guests, but there would be one less bullet in the chamber, no? Respectfully, Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Alan Altmark" Sent by: "The IBM z/VM Operating System" 08/27/2010 01:38 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Defining VSWITCH difficulties On Friday, 08/27/2010 at 12:26 EDT, George Henke/NYLIC wrote: > 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect > required port name > 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: > > The VSWITCH expects, requires a port name for 181D. > > Either the Portname or the Port number which defaulted to P0 is wrong. > > You can specify port number as 181d.Px > > You may want to try a QUERY VSWITCH RDEV 181D for more information. I've been harping on this since port names became optional in October 2003 (7 years ago!): DO NOT SPECIFY A PORT *NAME* in Linux or z/VM IP or VSWITCH configurations! Yes, they are required in z/OS, but that's a z/OS Comm Server issue. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Defining VSWITCH difficulties
On Friday, 08/27/2010 at 12:26 EDT, George Henke/NYLIC wrote: > 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect > required port name > 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: > > The VSWITCH expects, requires a port name for 181D. > > Either the Portname or the Port number which defaulted to P0 is wrong. > > You can specify port number as 181d.Px > > You may want to try a QUERY VSWITCH RDEV 181D for more information. I've been harping on this since port names became optional in October 2003 (7 years ago!): DO NOT SPECIFY A PORT *NAME* in Linux or z/VM IP or VSWITCH configurations! Yes, they are required in z/OS, but that's a z/OS Comm Server issue. Alan Altmark z/VM Development IBM Endicott
Re: Defining VSWITCH difficulties
Yeah, much better. Thanks all! Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 10:32 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Yeah, drop it. If you do use it, it has to match what the other users of that port are using. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 8:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn&#
Re: Defining VSWITCH difficulties
09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: The VSWITCH expects, requires a port name for 181D. Either the Portname or the Port number which defaulted to P0 is wrong. You can specify port number as 181d.Px You may want to try a QUERY VSWITCH RDEV 181D for more information. "Martin, Terry R. (CMS/CTR) (CTR)" Sent by: The IBM z/VM Operating System 08/27/2010 11:35 AM Please respond to The IBM z/VM Operating System To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Defining VSWITCH difficulties Issue a DET VSWITCH vswitchname – this will destroy it and you can than re-define it. BTW, are you sure that that the OSA 181D is really PORT 0 and not PORT 1? Once you get it set up you can add it to the guest with COUPLE command. 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 Frank M. Ramaekers Sent: Friday, August 27, 2010 11:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Not yet, have to figure out how to delete this partially defined one, since there doesn’t appear to be a “DELETE VSWITCH” (at least in the manual I’m looking at). Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties We don’t specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don’t understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I’m attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don’t see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware
Re: Defining VSWITCH difficulties
Is it me or doesn't ATTACH and DETACH or DEFINE and DELETE make more sense?Kinda odd that they paired DEFINE with DETACH. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Detach vswitch switchname Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 11:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Not yet, have to figure out how to delete this partially defined one, since there doesn't appear to be a "DELETE VSWITCH" (at least in the manual I'm looking at). Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 12
Re: Defining VSWITCH difficulties
Issue a DET VSWITCH vswitchname - this will destroy it and you can than re-define it. BTW, are you sure that that the OSA 181D is really PORT 0 and not PORT 1? Once you get it set up you can add it to the guest with COUPLE command. 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 Frank M. Ramaekers Sent: Friday, August 27, 2010 11:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Not yet, have to figure out how to delete this partially defined one, since there doesn't appear to be a "DELETE VSWITCH" (at least in the manual I'm looking at). Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to De
Re: Defining VSWITCH difficulties
Yeah, drop it. If you do use it, it has to match what the other users of that port are using. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 8:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please des
Re: Defining VSWITCH difficulties
Detach vswitch switchname Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 11:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Not yet, have to figure out how to delete this partially defined one, since there doesn't appear to be a "DELETE VSWITCH" (at least in the manual I'm looking at). Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f
Re: Defining VSWITCH difficulties
Not yet, have to figure out how to delete this partially defined one, since there doesn't appear to be a "DELETE VSWITCH" (at least in the manual I'm looking at). Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Friday, August 27, 2010 10:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-664
Re: Defining VSWITCH difficulties
We don't specify portnames when we define our vswitches. Have you tried defining your vswitch without specifying portnames? Jim Hughes 603-271-5586 "It is fun to do the impossible." From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immedi
Re: Defining VSWITCH difficulties
Okay, but I don't understand this either? * 08/27/10 * 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT181DDEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 09:26:39 DTCOSD310E VSWITCH-OSD device VSWAILT181DDEV: Missing or incorrect required port name 09:26:39 DTCOSD082E VSWITCH-OSD shutting down: 09:26:39 DTCPRI385IDevice VSWAILT181DDEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Inoperative 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 181D Port Number: 0 OSA 181D DETACHED DTCVSW2 181D BY DTCVSW2 OSA 181E DETACHED DTCVSW2 181E BY DTCVSW2 OSA 181F DETACHED DTCVSW2 181F BY DTCVSW2 09:26:39 DTCOSD361I VSWITCH-OSD link removed for VSWAILT181DDEV 09:26:39 DTCOSD360I VSWITCH-OSD link added for VSWAILT1200DEV 09:26:39 DTCOSD080I VSWITCH-OSD initializing: 09:26:39 DTCPRI385I Device VSWAILT1200DEV: 09:26:39 DTCPRI386I Type: VSWITCH-OSD, Status: Not started 09:26:39 DTCPRI387I Envelope queue size: 0 09:26:39 DTCPRI497I Address: 1200 Port Number: 0 09:26:39 DTCQDI001I QDIO device VSWAILT1200DEV device number 1200: 09:26:39 DTCQDI007I Enabled for QDIO data transfers 09:26:39 DTCOSD238I ToOsd: IPv4 multicast support enabled for VSWAILT1200DEV 09:26:39 DTCOSD319I ProcessSetArpCache: Supported for device VSWAILT1200DEV 09:26:39 DTCOSD341I Obtained MAC address 00145EB77AC5 for device VSWAILT1200DEV 09:26:39 DTCOSD238I ToOsd: IPv6 multicast support enabled for VSWAILT1200DEV Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Friday, August 27, 2010 9:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Defining VSWITCH difficulties Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: Defining VSWITCH difficulties
Any additional messages on DTCVSW2's console? From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Frank M. Ramaekers Sent: Friday, August 27, 2010 7:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Defining VSWITCH difficulties I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Defining VSWITCH difficulties
I'm attempting to define a new VSWITCH: define vswitch vswailt rdev 181d 1200 portname osa181d osa1200 VSWITCH SYSTEM VSWAILT is created Ready; T=0.01/0.01 09:26:39 HCPSWU2832E Connection 181D.P00 for VSWITCH SYSTEM VSWAILT is not active. HCPSWU2832E Device is detached from DTCVSW2. HCPSWU2830I VSWITCH SYSTEM VSWAILT status is ready. HCPSWU2830I DTCVSW2 is VSWITCH controller for device 1200.P00. But, I don't see what the problem is with 181D (through 181F): q vswitch VSWITCH SYSTEM VSWAILT Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware MAC address: 02-00-01-00-00-0D State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Portname: OSA181DRDEV: 181D.P00 Controller: NONE Error: Detached Portname: OSA1200RDEV: 1200.P00 Controller: DTCVSW2 VDEV: 1200 : : q paths 181d Device 181D, Status ONLINE CHPIDs to Device 181D (PIM) : 90 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 09:30:21 cp q 181d-181f OSA 181D FREE, OSA 181E FREE, OSA 181F FREE Ready; T=0.01/0.01 09:38:15 The error message HCPSWU2832E doesn't give me much to go on. Any ideas? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
