Re: hipersockets on a VM layer 2 vswitch
Yes but the layer 2 vswitch is running on z/VM ver. 5.4. Does this mean we will need to set up a layer 2 hipersocket on the z/OS side as well? Thank you Mark, yes we are running z/OS ver. 1.10 on the LPAR running the TSMTCS app. Russell -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Jacobs Sent: Wednesday, February 03, 2010 4:32 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: hipersockets on a VM layer 2 vswitch That lpar is running zOS 1.10. Mark Jacobs -Original Message- From: The IBM z/VM Operating System on behalf of David Boyes Sent: Wed 2/3/2010 4:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: hipersockets on a VM layer 2 vswitch You need a very modern z/OS for layer 2 connections to work. You don't say what level of z.OS, but I think it has to be minimum 1.10 if not 1.11. On 2/3/10 2:54 PM, russell.gendr...@custserv.com russell.gendr...@custserv.com wrote: Greetings, We currently have multiple Linux guest running on z/VM on both a layer 3 tcp/ip vswitch as well as a layer 2 vswitch. On one particular z/VM we have a hipersocket link to a z/OS system for using the TSMTCS backup application. Currently only the layer 3 guests use the hipersockets. We tried to define the hipersocket link on the z/OS system To a layer 2 Linux guest but there is no connection for some reason. Has anyone else tried this and if so were you successful? Thanks Russell Gendreau Time Customer Service, Inc. 813-554-2064
hipersockets on a VM layer 2 vswitch
Greetings, We currently have multiple Linux guest running on z/VM on both a layer 3 tcp/ip vswitch as well as a layer 2 vswitch. On one particular z/VM we have a hipersocket link to a z/OS system for using the TSMTCS backup application. Currently only the layer 3 guests use the hipersockets. We tried to define the hipersocket link on the z/OS system To a layer 2 Linux guest but there is no connection for some reason. Has anyone else tried this and if so were you successful? Thanks Russell Gendreau Time Customer Service, Inc. 813-554-2064
Re: hipersockets on a VM layer 2 vswitch
You need a very modern z/OS for layer 2 connections to work. You don’t say what level of z.OS, but I think it has to be minimum 1.10 if not 1.11. On 2/3/10 2:54 PM, russell.gendr...@custserv.com russell.gendr...@custserv.com wrote: Greetings, We currently have multiple Linux guest running on z/VM on both a layer 3 tcp/ip vswitch as well as a layer 2 vswitch. On one particular z/VM we have a hipersocket link to a z/OS system for using the TSMTCS backup application. Currently only the layer 3 guests use the hipersockets. We tried to define the hipersocket link on the z/OS system To a layer 2 Linux guest but there is no connection for some reason. Has anyone else tried this and if so were you successful? Thanks Russell Gendreau Time Customer Service, Inc. 813-554-2064
Re: hipersockets on a VM layer 2 vswitch
That lpar is running zOS 1.10. Mark Jacobs -Original Message- From: The IBM z/VM Operating System on behalf of David Boyes Sent: Wed 2/3/2010 4:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: hipersockets on a VM layer 2 vswitch You need a very modern z/OS for layer 2 connections to work. You don't say what level of z.OS, but I think it has to be minimum 1.10 if not 1.11. On 2/3/10 2:54 PM, russell.gendr...@custserv.com russell.gendr...@custserv.com wrote: Greetings, We currently have multiple Linux guest running on z/VM on both a layer 3 tcp/ip vswitch as well as a layer 2 vswitch. On one particular z/VM we have a hipersocket link to a z/OS system for using the TSMTCS backup application. Currently only the layer 3 guests use the hipersockets. We tried to define the hipersocket link on the z/OS system To a layer 2 Linux guest but there is no connection for some reason. Has anyone else tried this and if so were you successful? Thanks Russell Gendreau Time Customer Service, Inc. 813-554-2064
Layer 2 VSWITCH
Howdy; I am trying to test migration from Layer 3 VSWITCH to Layer 2 with z/VM 5.2. I am not having any luck defining a layer 2 VSWITCH and am unsure what I could be doing wrong. I get the following errors: define vswitch vlinux1 rdev f912 fd12 ethernet portname osadxvm1 osadxvm2 VSWITCH SYSTEM VLINUX1 is created Ready; HCPSWU2830I VSWITCH SYSTEM VLINUX1 status is devices attached. HCPSWU2830I DTCVSW1 is VSWITCH controller. HCPSWU2830I VSWITCH SYSTEM VLINUX1 status is devices attached. HCPSWU2830I DTCVSW1 is VSWITCH controller. HCPSWU2832E The connection for VSWITCH SYSTEM VLINUX1 is not active. HCPSWU2832E None of the RDEVs are available working QDIO OSA Express devices. HCPSWU2832E The connection for VSWITCH SYSTEM VLINUX1 is not active. HCPSWU2832E None of the RDEVs are available working QDIO OSA Express devices. q lan vlinux1 details VSWITCH SYSTEM VLINUX1 Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Unaware State: Disconnected QueueStorage: 8 Portname: OSADXVM1 RDEV: F912 Controller: NONE Error: No Layer 2 Portname: OSADXVM2 RDEV: FD12 Controller: NONE Error: No Layer 2 Ready; I can re-define it as a layer 3 VSWITCH and it works fine. detach vswitch vlinux1 VSWITCH SYSTEM VLINUX1 is destroyed Ready; define vswitch vlinux1 rdev f912 fd12 portname osadxvm1 osadxvm2 VSWITCH SYSTEM VLINUX1 is created Ready; HCPSWU2830I VSWITCH SYSTEM VLINUX1 status is ready. HCPSWU2830I DTCVSW1 is VSWITCH controller. q lan vlinux1 details VSWITCH SYSTEM VLINUX1 Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDNONROUTER Accounting: OFF VLAN Unaware State: Ready IPTimeout: 5 QueueStorage: 8 Portname: OSADXVM1 RDEV: F912 Controller: DTCVSW1 VDEV: F912 Portname: OSADXVM2 RDEV: FD12 Controller: DTCVSW2 VDEV: FD12 BACKUP Ready; What am I missing? Thanks; ok r.
Re: Layer 2 VSWITCH
Raymond, q lan vlinux1 details VSWITCH SYSTEM VLINUX1 Type: VSWITCH Connected: 0Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Unaware State: Disconnected QueueStorage: 8 Portname: OSADXVM1 RDEV: F912 Controller: NONE Error: No Layer 2 Portname: OSADXVM2 RDEV: FD12 Controller: NONE Error: No Layer 2 Ready; The No Layer 2 in the Error: field means the devices you're trying to use do not support layer 2 mode. Regards, Miguel Delapaz z/VM TCP/IP Development