ty Also, an academic question:
Are the 3 OSA addresses below (9004, 9005, 9006) used for 1 connection (Read/Write/ Data)? Here is our LNX Config file data from LNXMAINT's 191: From RHEL53 VLINUX2 on LNXMAINT’s 191: HOSTNAME="vlinux2.newyorklife.com" DASD="100-101,200" NETTYPE="qeth" IPADDR="172.28.3.136" SUBCHANNELS="0.0.d000,0.0.d001,0.0.d002" PORTNAME="LNXVSW1" BROADCAST="172.28.3.255" NETWORK="172.28.3.0" NETMASK="255.255.255.192" SEARCHDNS="newyorklife.com" GATEWAY="172.28.3.129" DNS="172.28.100.100" MTU="1500" Alan Altmark <alan_altm...@us.ibm.com> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 09/09/2010 10:16 AM Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How Do You Configure a 2nd VSWITCH? On Thursday, 09/09/2010 at 09:42 EDT, George Henke/NYLIC <george_he...@newyorklife.com> wrote: > We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH > controller, DTCVSW2 at OSA 9004. > > We are trying to understand how LNXVSW1 is related to the VSWITCH controller, > DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, for redundancy and > improved throughput. > > We believe it is related through our DEFINE in SYSTEM CONFIG: > > /* vswitch definitions*/ > define vswitch lnxvsw1 portname lnxvsw1 rdev 9004 > /* end of vswitch definition */ Get rid of the PORTNAME LNXVSW1. (Another PORTNAME bites the dust!) > and our subsequent OSA ATTACH of 9004 to DTCVSW2: > > Is this correct? No. You don't ATTACH or DETACH anything; the system handles it. Just DEFINE VSWITCH. > If so, then to configure a second VSWITCH, we should be able to DEFINE a second > VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005 TO DTCVSW1. > > Is this correct? No. Just defines your second (third, fourth, ...) VSWITCH and don't worry about controller selection. The only time to worry about the controller is when the Support Center asks you to do it. Alan Altmark z/VM Development IBM Endicott
