Marco,

It sounds like the hipersockets connection has not been made visible to the 
Linux guest in the z/VM directory.  Please verify with your z/VM administrator 
that the hipersockets connection has been defined (and that there is some other 
guest on that same hipersocket connection so you can test the communications).  
If the hipersocket link has been defined to your virtual machine, it might be 
blocked and you'll need to use cio_ignore to make it visible.

Thanks,

Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)

-----Original Message-----
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of Marco Banuelos
Sent: Tuesday, February 5, 2019 3:01 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Problem with Hipersockets z13 SUSE 12 Sp4

Hi all,

I'm experiencing some problems with SLES 12 SP4 running on z/vm 7.1, I made a 
SLES 12 SP4 installation and I configured with OSA network, now the customer 
want's to switch from OSA to Hipersocket and the HiperSocket network it's not 
showed on the SLES 12 SP4 vm, I rebooted the vm, I tried to install manually 
the driver, but it's not working.

Does anyone experienced this issue?

Thank you.
Best Regards.



Marco Antonio Bañuelos Hernández
Ingeniero de Pre-venta
marco.banue...@suse.com

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&amp;data=02%7C01%7CSam.Cohen%40LRS.COM%7C86fbdccec46b47f09c3608d68bcdeb80%7C62af9ccc42164ae2a1d306614c59c315%7C0%7C1%7C636850113886160721&amp;sdata=z69SCdWJ5rYYzKdUzDn9tmHcW1E9I72WUSYgX0mUXvY%3D&amp;reserved=0

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to