Re: Linux guest IPv6 address doesn't register on VSWITCH on ifup

Make sure you have PTF UM35894 applied, which added the IPv6 query support in the VSWITCH. There are two things that Linux can do to make its global IPv6 address visible before it starts sending traffic: 1. Respond to an IPv6 neighbor solicitation (NS) message with something called an IPv6

Linux guest IPv6 address doesn't register on VSWITCH on ifup

VSWITCH command to see that the guest has started the interface and registered the IPv4 address. However, the IPv6 address does not get registered until some IPv6 traffic has been passed to the guest. I can force this using either a ping from outside or a ping from the guest to something outside

Re: zVM VSwitch networking

On Friday, 10/09/2020 at 10:37 GMT, "van Sleeuwen, Berry" wrote: > Correct. When a guest connects to another guest on the same vswitch/vlan then > the traffic will not go outside of the LPAR. There is simply no need to go > outside as the two machine can talk to each other

Re: zVM VSwitch networking

, is it a correct assumption ? > > Scenario 1: > 2x zLinux on VSWITCH (option Layer-2), same VLAN, connected to same VSWITCH > (same CHPID) on the same zVM LPAR. Yes, unless OSAs are put into "hairpin" mode, which forces the traffic to go out of the LPAR to the switch,

Re: zVM VSwitch networking

Hi Marius, Correct. When a guest connects to another guest on the same vswitch/vlan then the traffic will not go outside of the LPAR. There is simply no need to go outside as the two machine can talk to each other directly. The same is true for a LAN inside VM. Both give you a virtual network

zVM VSwitch networking

Hello, I have the following network configuration scenarios. In scenario 1 - physical network infrastructure attached to Mainframe is not involved in communication between two zLinux hosts and traffic is handled on zVM level , is it a correct assumption ? Scenario 1: 2x zLinux on VSWITCH (option

Re: Open Vswitch and SLES12 KVM

Hi Folks! The place that Robert pointed it is correct, but to update it we use a script called qeth_configure (I guess it would be similar to chzdev but for SuSE and network only) So the answer was: qeth_configure -l -o "bridge_role=primary" 1 Thank you! Tito On Tue, Dec 12, 2017 at 1:23 PM,

Re: Open Vswitch and SLES12 KVM

SLES 12 SP2 seems to have chzdev. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christian Ehrhardt Sent: Tuesday, December 12, 2017 7:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Open Vswitch and SLES12 KVM On Tue, Dec 12, 2017

Re: Open Vswitch and SLES12 KVM

On Tue, Dec 12, 2017 at 4:05 PM, Robert J Brenneman wrote: > I have the following at the very end of my > /etc/udev/rules.d/51-qeth-0.0.1080.rules I think that is close to where chzdev [1] would place it, but IIRC SLES12 was not yet on chzdev right? If they are I beg your

Re: Open Vswitch and SLES12 KVM

I have the following at the very end of my /etc/udev/rules.d/51-qeth-0.0.1080.rules file: >>> ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.1080", ATTR{layer2}="1" ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.1080", ATTR{buffer_count}="128" ACTION=="add", SUBSYSTEM=="ccwgroup",

Re: Open Vswitch and SLES12 KVM

On Mon, Dec 11, 2017 at 11:37 PM, Tito Garrido <titogarr...@gmail.com> wrote: > Hi Folks, > > What is the recommended setup for open vswitch on SLES 12 on z? > > I can see: > https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_ovs.html > > But it

Open Vswitch and SLES12 KVM

Hi Folks, What is the recommended setup for open vswitch on SLES 12 on z? I can see: https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_ovs.html But it says nothing about BRIDGEPORT. Where should I put OPTIONS="layer2=1 bridge_role=primary Is "OPTIONS" a re

Ethernet/VSwitch woes

On Mon, 13 Nov 2017, Frank M. Ramaekers wrote: > Okay, I have a Fedora release 23 install. Everything work > greatwell that's until I reboot (re-IPL). There is an > inconsistency in the initialization of the Ethernet > interfaces: > 3) Both interfaces come up normally: > ifconfig >

Re: Ethernet/VSwitch woes

AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Ethernet/VSwitch woes On Mon, 13 Nov 2017 14:01:11 + "Frank M. Ramaekers" <framaek...@ailife.com> wrote: > Okay, I have a Fedora release 23 install. Everything work > greatwell that's until I reboot (re-IPL). There is an &

Re: Ethernet/VSwitch woes

On Mon, 13 Nov 2017 14:01:11 + "Frank M. Ramaekers" wrote: > Okay, I have a Fedora release 23 install. Everything work > greatwell that's until I reboot (re-IPL). There is an > inconsistency in the initialization of the Ethernet interfaces: how the interface

Ethernet/VSwitch woes

Okay, I have a Fedora release 23 install. Everything work greatwell that's until I reboot (re-IPL). There is an inconsistency in the initialization of the Ethernet interfaces: 1) Interfaces come up w/o an IP address (see enccw0.0600 and enccw0.0700 ifconfig enccw0.0.0600:

Re: Where to put set vswitches for port based vswitch

>>> On 1/7/2017 at 08:39 AM, "Ambros, Thomas" <thomas_amb...@keybank.com> >>> wrote: > The vswitch itself is defined in System Config but I don't want to code > modifies in there after the vswitch definition because that doesn't seem to > lend its

Where to put set vswitches for port based vswitch

Newbie question. The vswitch itself is defined in System Config but I don't want to code modifies in there after the vswitch definition because that doesn't seem to lend itself to an automated process the way issuing a Dirmaint command does. Is there any reason not to Dirmaint add them

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

ASED) and > he cant send any untagged frames. > I would rather manage a USERBASED VSWITCH with trunks over managing ports > with PORTBASED any day... > It is much easier to make vlan mistakes with PORTBASED... USERBASED is much > more intuitive, easy to manage and easy to view... To

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

So, If you make sure you have NATIVE NONE and keep track of your grants (just like PORTBASED) there is no real security concern... The guest is only allowed the vlans you grant it (just like PORTBASED) and he cant send any untagged frames. I would rather manage a USERBASED VSWITCH with trunks

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

nked OSA port. There are NO OSA controls on what LPARs can use what VLANs, so it must be assumed that the host can attach itself to any VLAN authorized for the port. In a VSWITCH, we don't have that problem. However, VLAN IDs can and do change. You don't want a VLAN-aware host to be acci

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

iedziuk > <gpowiedz...@gmail.com> wrote: > > > > 3. Less common, useful in some cases - OSA is plugged into "trunk" port > on > > real switch and in general same as (2). But, when you do grant, you can > say > > that this specific grant should act as "

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

rant should act as "porttype trunk" (and you specify > which vlans are trunked) so VSWITCH instead of removing the vlan tag, > forwards the whole thing to linux guest. So linux guest should be > configured to receive and send tagged frames. As Mark mentioned, during > install

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

2016-04-21 16:29 GMT-04:00 Mark Post <mp...@suse.com>: > >>> On 4/21/2016 at 03:38 PM, Grzegorz Powiedziuk <gpowiedz...@gmail.com> > wrote: > -snip- > > I believe Mark said that having linux to handle vlan tagging is hard. > > > > But what you are

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

>>> On 4/21/2016 at 04:38 PM, Alan Altmark wrote: > On Thursday, 04/21/2016 at 07:39 GMT, Grzegorz Powiedziuk > wrote: >> I believe Mark said that having linux to handle vlan tagging is hard. > > There is nothing difficult about getting Linux to

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

security management. > In your case, you let the vswitch to do vlan tagging and untaging. So > vswitch has to be vlan aware so it can receive and understand tagged frames > from the outside real, switch. > When it receives a tagged frame from the outside world it removes the

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

>>> On 4/21/2016 at 03:38 PM, Grzegorz Powiedziuk <gpowiedz...@gmail.com> >>> wrote: -snip- > I believe Mark said that having linux to handle vlan tagging is hard. > > But what you are trying to do is different. In your case, vswitch is > removing/adding

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

> In this statement does the VLAN AWARE specify TRUNKING to the uplink OSA ? > If not what is the difference between what we coded VLAN 229 and VLAN > AWARE? > > DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN AWARE NATIVE NONE > > Thanks, > Dave > > I believe Mark said that havi

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

AWARE? > > DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN AWARE NATIVE NONE Yes, VLAN AWARE specifies trunking on the uplink. The difference is that you authorized everyone who was not explicitly authorized to a VLAN to use VLAN 229, and I required everyone to have an explicit GRANT. By the

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

between what we coded VLAN 229 and VLAN AWARE? DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN AWARE NATIVE NONE Thanks, Dave From: Dave Myers Sent: Wednesday, April 20, 2016 10:37 PM To: 'linux-390@VM.MARIST.EDU' <linux-390@VM.MARIST.EDU> Subject: RE: Install not working for SLES11 SP4 thru T

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

>>> On 4/20/2016 at 10:28 PM, Dave Myers <dave.my...@siriuscom.com> wrote: > VLAN def in system config is: > define vswitch vsw1 rdev 400.p1 vlan 229 It's been a while since I played with this stuff, but one thing I know for sure: If the Linux guest has to be aware

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

nstall not working for SLES11 SP4 thru TRUNKED VSWITCH On Thursday, 04/21/2016 at 02:29 GMT, Dave Myers <dave.my...@siriuscom.com> wrote: > VLAN def in system config is: > define vswitch vsw1 rdev 400.p1 vlan 229 Gaaack! Please use DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

On Thursday, 04/21/2016 at 02:29 GMT, Dave Myers <dave.my...@siriuscom.com> wrote: > VLAN def in system config is: > define vswitch vsw1 rdev 400.p1 vlan 229 Gaaack! Please use DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN AWARE NATIVE NONE Have your switch admin verify that o

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

SLES11 SP4 thru TRUNKED VSWITCH VLAN def in system config is: define vswitch vsw1 rdev 400.p1 vlan 229 In LNXDFLT profile we have: COMMAND SET VSWITCH VSW1 GRANT VLAN 229 COMMAND DEFINE NIC 300 TYPE QDIO COMMAND COUPLE 300 TO SYSTEM VSW1 When we logon to the guest from which we are exe

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

What does q vswitch show you? Marcy -Original Message- From: Dave Myers [dave.my...@siriuscom.com<mailto:dave.my...@siriuscom.com>] Sent: Wednesday, April 20, 2016 09:29 PM Central Standard Time To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Install not working for SLES

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

VLAN def in system config is: define vswitch vsw1 rdev 400.p1 vlan 229 In LNXDFLT profile we have: COMMAND SET VSWITCH VSW1 GRANT VLAN 229 COMMAND DEFINE NIC 300 TYPE QDIO COMMAND COUPLE 300 TO SYSTEM VSW1 When we logon to the guest from which we are executing the SLES11SP4, we get positive

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

On Thursday, 04/21/2016 at 01:56 GMT, Dave Myers <dave.my...@siriuscom.com> wrote: > The define VSWITCH and the COUPLE both produce no errors. That part looks good. > Yes. We are using this VLAN for some z/OS interfaces, so it is not new. > > The SLES11SP4 EXEC does n

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

The define VSWITCH and the COUPLE both produce no errors. That part looks good. Yes. We are using this VLAN for some z/OS interfaces, so it is not new. The SLES11SP4 EXEC does not show any errors. The only message we get, after a 1-2 minute hang in the SLES11SP4 EXEC is: " unable to

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

Is anything else on your vswitch working or is this a new set up? We run trunked ports and use the vlan on the grant statement with SP4 so that isn't an issue. What messages are you getting?Did you get your default route right? -Original Message- From: Linux on 390 Port

Re: Install not working for SLES11 SP4 thru TRUNKED VSWITCH

What happens when you 'CP COUPLE nicaddress TO SYSTEM vswitchname' from this guests console? If there's an error it may help troubleshoot.. You need to ensure you're connected to the VSWITCH -- does CP Q VSWITCH vswitchname DETAILS show this guest connected? Scott Rohling On Wed, Apr 20, 2016

Install not working for SLES11 SP4 thru TRUNKED VSWITCH

I am trying to install SLES11 SP4 under zVM VSWITCH. The VSWITCH is attached to an OSA that is TRUNKED to a switch port. We defined VLAN ID on the VSWITCH def and also on the GRANT ACCESS statement for the guest. We cannot connect when we run the SLES11SP4 EXEC. Does anyone know

Re: VSWITCH

The 10Gb only have a single port, so if you're using both ports on the 1Gb then you'll need 2 x 10Gb cards. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Wells Sent: 25 March 2016 2:33 PM To: LINUX-390@VM.MARIST.EDU Subject: VSWITCH I

Re: VSWITCH

Tks Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Friday, March 25, 2016 3:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: VSWITCH Nope -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU

Re: VSWITCH

Nope -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Wells Sent: Friday, March 25, 2016 7:33 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] VSWITCH I currently have 1gig OSA's port(2) defined... Do I need to do anything in Config

VSWITCH

I currently have 1gig OSA's port(2) defined... Do I need to do anything in Config of VSWITCH if I swap out 1Gig for a 10Gig ? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which

Re: Ethernet on VSwitch

> From:Mark Post <mp...@suse.com> > To:LINUX-390@VM.MARIST.EDU, > Date:08/03/2016 21:55 > Subject: Re: Ethernet on VSwitch > Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU> > >>> On 3/8/2016 at 02:09 PM, "

Re: Ethernet on VSwitch

t/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Frank M. Ramaekers Sent: den 8 mars 2016 8:10 To: LINUX-390@VM.MARIST.EDU Subject: Ethernet on VSwitch I'm wondering why it was assumed that these adapters should use the (almost)

Re: Ethernet on VSwitch

speeds: > > There's a feature request from IBM for SLES12 SP2 that involves a qeth driver > update to more accurately report data to the ethtool command. For a virtual NIC on a VSWITCH, z/VM will respond to the qdio driver's qeth_query_card_info() call with "10Gb fibre running full dup

Re: Ethernet on VSwitch

>>> On 3/8/2016 at 02:09 PM, "Frank M. Ramaekers" >>> wrote: > I'm wondering why it was assumed that these adapters should use the > (almost) slowest speeds: There's a feature request from IBM for SLES12 SP2 that involves a qeth driver update to more accurately report

Ethernet on VSwitch

-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Link detected: yes (Neither has native OSA, so I don't know if this is just a VSwitch thing

Max NFS speed via vswitch and 10GBit adapter ?

Hi, we are trying to bump up the speed doing file transfers via a vswitch connected to a 10Gbit OSA. There seems to be a lot of parameters having a significant impact on speed here. It's for getting best speed for a TSM Server backing up its own db2 database That lives on std eckd disk onto nfs

DTCOSD089E VSWITCH channel errors

from the DTCVSW1 console log: DTCOSD089E VSWITCH-OSD device XCATVSW28403DEV: Channel error on 8404 It was working beautifully until this :( Oddly, the basic IP stack access via TN3270 etc. works fine, only the VSWITCHes seem to have trouble. I've had to set them to "disconnect" to avo

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

>>> On 9/25/2015 at 02:41 PM, Offer Baruch <offerbar...@gmail.com> wrote: > Not sure if i understand your question but yes i am sure. > When using a layer2 vswitch you have to specify the layer2 option on > znetconf/qeth_configure and on your ifcfg file or your NIC will s

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

Mark, you are correct. "Vlan aware" does not require layer 2. I don't think it has been said in this thread, but don't use the PORTTYPE option at all on the Define VSWITCH. Let it default to "access" and define the virtual NIC connection type for each user (which is just

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

The guest being unaware says nothing about the real connection to the OSA card. If the osa is connected to a trunk port and the vlan is tagged, then the vswitch must be set to layer2 and vlan aware to strip the vlan tag and forward the data to the guest as if it is a regular access port without

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

I have not tested that... So VLAN AWARE should be sufficient even if the vswitch is defined as layer3... correct? On Sep 25, 2015 10:30 PM, "Offer Baruch" <offerbar...@gmail.com> wrote: > The guest being unaware says nothing about the real connection to the OSA > card. I

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

>>> On 9/25/2015 at 03:30 PM, Offer Baruch <offerbar...@gmail.com> wrote: > The guest being unaware says nothing about the real connection to the OSA > card. If the osa is connected to a trunk port and the vlan is tagged, then > the vswitch must be set to layer2 and vlan

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

>>> On 9/25/2015 at 03:38 PM, Offer Baruch <offerbar...@gmail.com> wrote: > I have not tested that... So VLAN AWARE should be sufficient even if the > vswitch is defined as layer3... correct? I don't have the ability to create VLANs in the network, so I can'

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

>>> On 9/23/2015 at 11:46 PM, Offer Baruch <offerbar...@gmail.com> wrote: > There is no problem connecting the guest in access mode while your vswitch > is in trunk mode... > All you have to change from a regular layer 3 vswitch is the layer2=1flag > on the interface.

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

Not sure if i understand your question but yes i am sure. When using a layer2 vswitch you have to specify the layer2 option on znetconf/qeth_configure and on your ifcfg file or your NIC will simply won't get online. Happens all the time. Offer Baruch On Sep 25, 2015 9:32 PM, "Mark Post

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

@VM.MARIST.EDU Subject: Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux NTAC:Missing Hi, Are you sure you want your linux guests in trunk mode as well? It is 2 different things to configure your vswitch as trunk and the guest in trunk. There is no problem connecting the guest in access mode

Re: Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

Hi, Are you sure you want your linux guests in trunk mode as well? It is 2 different things to configure your vswitch as trunk and the guest in trunk. There is no problem connecting the guest in access mode while your vswitch is in trunk mode... All you have to change from a regular layer 3

Vswitch-Trunk mode-Ethernet-Vlan Aware and zLinux

NTAC:3NS-20 I am trying to configure a new Vswitch that I've not had experience with previously. My current vswitch is an access IP VLAN UNAWARE connection. I had little issue configuring z/VM's TCPIP stack or zLinux instances to use it. Now we are attempting to switch to a vswtich

Re: Strange vswitch problem

On Wed, Jan 28, 2015 at 12:21 AM, Offer Baruch offerbar...@gmail.com wrote: Hi Can you also attach the output of q vswitch vswitch_name access for this vswitch? q vswitch RHTS1 access VSWITCH SYSTEM RHTS1Type: QDIOConnected: 42 Maxconn: INFINITE PERSISTENT RESTRICTED

Re: Strange vswitch problem

Mark, Currently using autolog to via profile exec to authorize users to the VSWITCH CP SET VSWITCH test1 GRANT user vlan I have NICDEF in my user direct adding the nics like below 02272 NICDEF 8000 TYPE QDIO LAN SYSTEM TEST1 MACID 11 02273 NICDEF 8003 TYPE QDIO LAN SYSTEM TEST2 On Wed

Re: Strange vswitch problem

On Wed, 2015-01-28 at 09:50 -0500, Andrew Lemay wrote: What I don't get is my configs are the same for all 42 guests. But this one keeps showing up on guest LAN [root@test-09 ~]# dmesg | grep qeth qeth: loading core functions qeth: register layer 2 discipline qeth 0.0.8000: MAC address

Re: Strange vswitch problem

On Wed, Jan 28, 2015 at 10:36 AM, Ursula Braun ubr...@linux.vnet.ibm.com wrote: On Wed, 2015-01-28 at 09:50 -0500, Andrew Lemay wrote: What I don't get is my configs are the same for all 42 guests. But this one keeps showing up on guest LAN [root@test-09 ~]# dmesg | grep qeth qeth:

Re: Strange vswitch problem

On 1/28/2015 at 08:38 AM, Andrew Lemay and...@lemay.org wrote: I can ping it from my networks after revoking access to the vswitch and re granting access to the vswitch. In your CP directory, are you using a NICDEF statement and a COMMAND statement to grant authorization to the VSWITCH

Re: Strange vswitch problem

0.0.8000: Device is a Guest LAN QDIO card (level: V614) qeth 0.0.8000: MAC address 11:11:11:11:11:11 successfully registered on device eth0 And the port name seems to be set now. q vswitch test1 USErid test-09 VSWITCH SYSTEM test1Type: QDIOConnected: 46 Maxconn: INFINITE PERSISTENT

Strange vswitch problem

Hello, I have about 40 guests attached to a single vswitch and all but one are having a problem. test-09 keeps coming up as UNASSIGNED. This is z/VM V6.1.0 Has anyone ever seen this before? Adapter Owner: test-09 NIC: 8000.P00 Name: UNASSIGNED Type: QDIO 00: Porttype: Access 00

Re: Strange vswitch problem

Hi Can you also attach the output of q vswitch vswitch_name access for this vswitch? Did you recently ipled your z/vm? Do you get any error messages on the guest console after logging in (that is piwer on the guest)? Thanks Offer Baruch On Jan 28, 2015 1:56 AM, Andrew Lemay and...@lemay.org

Re: VSWITCH for z/vm tcpip

grant tcpip access to the vswitch set vswitch vsw1 grant tcpip - also add that to system profile to make it persistent - if you use RACF/VM, you will have to set permissions there - after logging on tcpip, you can have a look at the vswitch to see if the connection is ok: CP Q VSWITCH VSW1

Re: VSWITCH for z/vm tcpip

OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 IUCV *VSWITCH MSGLIMIT 65535 NICDEF F800 TYPE QDIO LAN SYSTEM VSW1 NICDEF F900 TYPE QDIO LAN SYSTEM VSW1 NICDEF FC00 TYPE QDIO LAN SYSTEM VSW1

Re: VSWITCH for z/vm tcpip

ON @@member4name USING SUBCONFIG TCPIP-4 OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 IUCV *VSWITCH MSGLIMIT 65535 NICDEF F800 TYPE QDIO LAN SYSTEM VSW1 NICDEF F900 TYPE QDIO LAN SYSTEM VSW1 NICDEF

Re: VSWITCH for z/vm tcpip

You can't have NICDEF's using a VSWITCH with TCPIP and ATTACH: statements in the DTCPARMS file NICDEFS are used to connect a virtual device to the user and couple it to the VSWITCH. The VSWITCH is the only one that touches the Real devices not TCPIP in this case. ATTACH: is used when you want

Re: VSWITCH for z/vm tcpip

why you configured two IP addresses from the same subnets? If that really is needed, I probably would setup two different TCPIP machines. The point of using a VSWITCH is to let it handle the physical OSAs and any failover. The guest needs only one interface per VLAN per VSWITCH that it is using

Re: VSWITCH for z/vm tcpip - Q on 2nd OSA definition

On 1/20/2015 at 11:48 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: My configuration is a bit different and I have a second VSWITCH specifying OSA address 0A0 but is not defined in my TCPIP configuration. Or TCPIP's directory statement. It is defined in SYSTEM CONFIG

Re: VSWITCH for z/vm tcpip - Q on 2nd OSA definition

My configuration is a bit different and I have a second VSWITCH specifying OSA address 0A0 but is not defined in my TCPIP configuration. Or TCPIP's directory statement. It is defined in SYSTEM CONFIG and in Autolog1 profile exec. 0A0 is not the Primary OSA so maybe that's

Re: VSWITCH for z/vm tcpip

ok---it is working after I added the ATTACH but I gather this is F800(example) is running through OSA only not the VSWITCH.. I did find where the old 5.4 had the NICDEF in the USER DIRECT file The Cook book I am looking at has the steps to set the OSA addr to the VSWITCH BUT questions it shows

Re: VSWITCH for z/vm tcpip

On Monday, 01/19/2015 at 11:19 EST, Ron Wells ron.we...@springleaf.com wrote: ok---it is working after I added the ATTACH but I gather this is F800(example) is running through OSA only not the VSWITCH.. I did find where the old 5.4 had the NICDEF in the USER DIRECT file The Cook book I am

Re: VSWITCH for z/vm tcpip

attached to the TCP/IP stack. But you've probably already fixed that. The reason to attach the z/VM TCP/IP stack to the VSWITCH is to leverage the HA qualities of the VSWITCH with its ability to fail over to a second OSA card. Alan is right - if you're going to do this, the better model is to put

Fw: VSWITCH for z/vm tcpip

? - Forwarded by Ron Wells/AGFS/AGFin on 01/19/2015 10:36 AM - From: Ron Wells ron.we...@springleaf.com To: LINUX-390@VM.MARIST.EDU Date: 01/19/2015 10:19 AM Subject:Re: VSWITCH for z/vm tcpip Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU ok---it is working after I added

Re: VSWITCH for z/vm tcpip

IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 IUCV *VSWITCH MSGLIMIT 65535 NICDEF F800 TYPE QDIO LAN SYSTEM VSW1 added these NICDEF F900 TYPE QDIO LAN SYSTEM VSW1 NICDEF FC00 TYPE QDIO LAN SYSTEM VSW1 NICDEF FD00 TYPE QDIO LAN SYSTEM VSW1 SUBCONFIG TCPIP-1 LINK TCPMAINT

Re: VSWITCH for z/vm tcpip

.. BUT... q vswitch display shows following differences and do not understand why... RDEV: F804.P00 VDEV: F804 Controller DTCPVSW2 old display from 5.4 system RDEV: F804.P00 VDEV: 0600??? the difference is 0600 vs F804 do not know why/reason From: Scott Rohling scott.rohl...@gmail.com

Re: VSWITCH for z/vm tcpip

was not in setup once I put that ATTACH inplace it came up.. BUT... q vswitch display shows following differences and do not understand why... RDEV: F804.P00 VDEV: F804 Controller DTCPVSW2 old display from 5.4 system RDEV: F804.P00 VDEV: 0600??? the difference is 0600 vs F804 do not know why

Re: VSWITCH for z/vm tcpip

Subject:Re: VSWITCH for z/vm tcpip Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU On Friday, 01/16/2015 at 09:49 EST, Ron Wells ron.we...@springleaf.com wrote: Found the following that was incorrect...or modified from original 5.4 setup..person that set this up no longer here

Re: VSWITCH for z/vm tcpip

to see what device numbers you require. If you want TCPIP to use a VSWITCH, you will need NICDEFs to provide the connection to the VSWITCH, or you could use a :vnic. tag in SYSTEM DTCPARMS. If it's using device number F800, then you can have a NICDEF F800 to replace the OSA. You only need F800-F803

Re: VSWITCH for z/vm tcpip

03:39 PM Subject: Re: VSWITCH for z/vm tcpip Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU We finishe installing and migrating files from z/VM 5.4 to z/VM 6.3 System itself comes up...TCPIP not working compared old tcpip and vswitch file/parms..all seems to be the same.. When

Re: VSWITCH for z/vm tcpip

We finishe installing and migrating files from z/VM 5.4 to z/VM 6.3 System itself comes up...TCPIP not working compared old tcpip and vswitch file/parms..all seems to be the same.. When display addr of OSA's and Hipersocket used..they show as if not defined

Re: VSWITCH for z/vm tcpip

Are you autologging your controllers? -- Mike Harding z/VM System Support Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 01/15/2015 01:25:48 PM: From: Ron Wells ron.we...@springleaf.com To: LINUX-390@VM.MARIST.EDU Date: 01/15/2015 03:39 PM Subject: Re: VSWITCH for z/vm tcpip Sent

Re: Arp cache in a VSWITCH ??

to a vswitch using layer 2, problem goes away. So we have added a new setup of vswitches using layer 2, and changes the servers when we need to or can now, one by one. Tore Agblad System programmer, Volvo IT certified IT Architect Volvo Information

Re: Arp cache in a VSWITCH ??

[mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: den 5 november 2012 17:00 To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? On 11/5/2012 at 10:17 AM, Dean, David (I/S) david_d...@bcbst.com wrote: Mark, these all say DOS format, I have done vi:set fileformat=unix

Re: Arp cache in a VSWITCH ??

. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, November 02, 2012 3:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? On 11/2/2012 at 10:49 AM, Dean, David (I/S) david_d...@bcbst.com wrote: I am having

Re: Arp cache in a VSWITCH ??

: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dennis Musselwhite Sent: den 1 november 2012 15:33 To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? As Marcy Cortes suggested, a duplicate IP address is one possible explanation. If you had a duplicate *inside* your

Re: Arp cache in a VSWITCH ??

On 11/5/2012 at 10:17 AM, Dean, David (I/S) david_d...@bcbst.com wrote: Mark, these all say DOS format, I have done vi:set fileformat=unix on install-sh and a makefiledirs but now it is giving me this Am I missing something simple? Perhaps. I'm not sure what you're doing, but I

Re: Arp cache in a VSWITCH ??

E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: den 1 november 2012 01:01 To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? On 10/31/2012

Re: Arp cache in a VSWITCH ??

: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: den 2 november 2012 20:21 To: LINUX-390@VM.MARIST.EDU Subject: Re: Arp cache in a VSWITCH ?? On 11/2/2012 at 10:49 AM

Re: Arp cache in a VSWITCH ??

cache in a VSWITCH ?? If it is installed, mtr is traceroute on steriods. HTH., Peter Peter Linnell SUSE Linux Technical Specialist Tel: 1-415-308-3037 -- For LINUX-390 subscribe / signoff / archive access instructions

Re: Arp cache in a VSWITCH ??

in a VSWITCH ?? Hi, Marcy. The main MTR web site is: http://www.bitwizard.nl/mtr/ but there does not appear to be a pre-built binary for s390x. Let me see if I can't built it here on my SLES 112 SP2 guest. Have a good one, too. DJ On 11/01/2012 04:02 PM, Marcy Cortes wrote: Sounds

Re: Arp cache in a VSWITCH ??

On 11/2/2012 at 10:49 AM, Dean, David (I/S) david_d...@bcbst.com wrote: I am having a problem compiling it (suse 11.2). if you get a working copy, I would like one too. Make use of the work others have done. Download the SRPM from

  1   2   3   4   5   6   7   8   >