What makes this a Layer-3 VSWITCH vs a Layer-2?
Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: > > No problem. > > Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I > wished to move this to a > layer-3 VSWITCH for redundancy purposes. (Much of the following was > derived from the IBM > Redbook "Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN > Features of z/VM 4.4") > > > 1)Define the VSWITCH > a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 > b.-and- add the same statement to `SYSTEM CONFIG´file > (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) > 2)Granting access to the VSWITCH > a.set vswitch vswitchname grant userid > b.-and- add Modify VSwitch vswitchnameGRAnt userid to `SYSTEM CONFIG´ > c.- or - add the set vswitch command in the AUTOLOG1 startup > 3)Defining the simulated NICs > a.for userid cmd define nic ccuu4 qdio > b.-and- add to the directory for userid: > NICDEF ccuu4 TYPE QDIO DEVICES 3 > (a above can be skipped, but the userid would have to be logged off then > on) > 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname > (This will need to be performed each time the virtual machine is logged > on.) > > (Don´t think I missed anything) > > > Frank M. > Ramaekers Jr. > > > > > > From: The IBM z/VM Operating System [mailto:[email protected]] On > Behalf Of > Billy Bingham > Sent: Tuesday, August 31, 2010 7:51 AM > To: [email protected] > Subject: Re: VSWITCH defined VSE TCP/IP fails > > > Frank, > > Would you be willing to share the steps you used to create the VSWITCH? > > > Thanks, > > Billy > > On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: > > > > >Thanks, that helps....the difference between an upCOUPLEd and a > COUPLEd > >VSWITCH: > > > >UnCOUPLEd: > >AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: > >8992 > > > >COUPLEd (and not yet initialized): > >AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT > > > >...and initialized: > >* cp q v nic aa0 > >details > >AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: > >3 > >AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM > >VSWAILT > >AR 0015 RX Packets: 49 Discarded: 0 Errors: > >0 > >AR 0015 TX Packets: 42 Discarded: 0 Errors: > >0 > >AR 0015 RX Bytes: 2450 TX Bytes: > >2884 > >AR 0015 Connection Name: Session > >Established > >AR 0015 Device: 0AA0 Unit: 000 Role: CTL- > >READ > >AR 0015 Device: 0AA1 Unit: 001 Role: CTL- > >WRITE > >AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 > >Index: > >0065 > > > >AR 0015 Options: > >IPv4 > >AR 0015 Unicast IP Addresses: > > > >AR 0015 10.1.20.2MAC: 02-00-01-00-00- > >0E > >AR 0015 1I40I READY > > > > > >Thanks Alan! > > > > > >Frank M. Ramaekers Jr. > > > > > > > >-----Original Message----- > >From: The IBM z/VM Operating System > [mailto:[email protected]] On > >Behalf Of Alan Altmark > >Sent: Friday, August 27, 2010 3:33 PM > >To: [email protected] > >Subject: Re: VSWITCH defined VSE TCP/IP fails > > > >On Friday, 08/27/2010 at 04:28 EDT, "Frank M. Ramaekers" > ><[email protected]> wrote: > >> * cp q v nic aa0 details > >> > >> AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 > >> AR 0015 MAC: 02-00-01-00-00-0ELAN: * None > > > >And there you have it. The adapter is not COUPLED, as indicated by > the > >"* > >None". An uncoupled NIC is the equivalent of an unplugged ethernet > >cable. > > > >Alan Altmark > >z/VM Development > >IBM Endicott > > > >_____________________________________________________ This message > >contains information which is privileged and confidential and is solely > >for the use of the intended recipient. If you are not the intended > > recipient, be aware that any review, disclosure, copying, > distribution, > >or use of the contents of this message is strictly prohibited. If you > >have received this in error, please destroy it immediately and notify > us > >at [email protected]. > > > > _____________________________________________________ This message > contains information which is privileged and confidential and is solely > for the use of the intended recipient. If you are not the intended > recipient, be aware that any review, disclosure, copying, distribution, > or use of the contents of this message is strictly prohibited. If you > have received this in error, please destroy it immediately and notify us > at [email protected].
