Re: hipersockets

On Friday, 11/20/2015 at 02:02 GMT, David Kreuter wrote: > Another advantage is that it uses only one hipersocket triplet whereas > dedicated hipersocket will end up using one triplet per Linux virtual. > You can even use the same hiper triplet on each LPAR. > There is

Re: hipersockets

Gregory: It does help. As a VSWITCH it can be protected by RACF hence the VLANs can be RACF protected too. Another advantage is that it uses only one hipersocket triplet whereas dedicated hipersocket will end up using one triplet per Linux virtual. You can even use the same hiper triplet on each

Re: hipersockets

ohhh I see what you are saying (I think so). I was thinking about standard usage of vswitch bridge so a scenario where all guests have real dedicated hipersockets and vswitch has one of these hipersockets as well. This gives hipersocket virtual machines a way to talk to each other (via

Re: hipersockets

Thanks Alan. HiperSocket VSWITCH Bridge will not help when it comes to isolation, right? Vswitch simply acts as a bridge for hipersocket network using using one of the real hipersocket devices as one of its own interfaces (bridge port). Via this bridge Hipersocket network gets access to external

Available now: Linux on z Systems publications for Red Hat Enterprise Linux 7.2

This document describes the device drivers available to Red Hat Enterprise Linux 7.2 for the control of z Systems devices and attachments. It also provides information on commands and parameters relevant to configuring Linux on z Systems. This document describes tools for obtaining dumps

2015-11-19 Documentation for RHEL 7.2 available on developerWorks

Please refer to http://www.ibm.com/developerworks/linux/linux390/whatsnew.html for new documentation for RHEL 7.2 * end of message Mit freundlichen Grüßen / Kind regards Gerhard Hiller Software Management and