Mark, I am still a z/VM learner. Based on your comments, my PROFILE LNXDFLT for TCPMAINT should be changed from
LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR LINK LNXMAINT 0192 0191 RR LINK TCPMAINT 0592 0592 RR To LINK MAINT 0190 0190 R LINK MAINT 019D 019D R LINK MAINT 019E 019E R LINK LNXMAINT 0192 0191 R LINK TCPMAINT 0592 0592 R Shouldn't it? Thanks, Ray -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Pace Sent: Friday, December 19, 2014 3:15 PM To: [email protected] Subject: Re: Problem to test relocating a Linux image to another z/VM - Device 0592 Email sent from outside of PSEG. Use caution before using links/attachments. As part of my linux PROFILE EXEC - if it is going to IPL linux it runs an exec that detaches all disks that do not belong to that linux guest, in my case, all R/O disks. On Fri, Dec 19, 2014 at 1:55 PM, Cohen, Sam <[email protected]> wrote: > Ray, > > You should detach the CMS-oriented disks from your Linux guest before > booting the Linux kernel. Your kernel should only have disks attached > that Linux will actually use. Having disks attached/linked that are > dedicated to one particular z/VM image will prevent relocation. > > Thanks, > > > Sam Cohen > Levi, Ray & Shoup, Inc. > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Chu, Raymond > Sent: Friday, December 19, 2014 11:36 AM > To: [email protected] > Subject: Re: Problem to test relocating a Linux image to another z/VM > - Device 0592 > > Hi Alan and all, > > The EQID on VSWITCH was fixed. When I ran the following: > > vmreloc test Lnx004 zvm2 > HCPRLH1940E LNX004 is not relocatable for the following reason (s): > HCPRLI1996I LNX004: Virtual machine device 0592 is a link to a local > minidisk > > Below is the definition for LNXDFLT profile for Linux images and > TCPMAINT > > IDENTITY TCPMAINT PASSWORD 32M 64M ABCG > INCLUDE TCPCMSU > BUILD ON ZVM1 USING SUBCONFIG TCPMNT-1 BUILD ON ZVM2 USING SUBCONFIG > TCPMNT-2 BUILD ON ZVM3 USING SUBCONFIG TCPMNT-3 BUILD ON ZVM4 USING > SUBCONFIG TCPMNT-4 > > SUBCONFIG TCPMNT-1 > LINK 6VMTCP30 491 491 RR > LINK 6VMTCP30 492 492 RR > MDISK 591 3390 8558 122 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN > MDISK 592 3390 8680 140 XX12B4 MR ALL WTCPMAIN MTCPMAIN > MDISK 198 3390 8820 009 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN MDISK > 191 3390 8829 007 XX12B4 MR RTCPMAIN WTCPMAIN MTCPMAIN > > SUBCONFIG TCPMNT-2 > LINK 6VMTCP30 491 491 RR > LINK 6VMTCP30 492 492 RR > MDISK 591 3390 8558 122 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN > MDISK 592 3390 8680 140 XX1395 MR ALL WTCPMAIN MTCPMAIN > MDISK 198 3390 8820 009 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN MDISK > 191 3390 8829 007 XX1395 MR RTCPMAIN WTCPMAIN MTCPMAIN > > SUBCONFIG TCPMNT-3 > LINK 6VMTCP30 491 491 RR > LINK 6VMTCP30 492 492 RR > MDISK 591 3390 8558 122 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN > MDISK 592 3390 8680 140 XX1A06 MR ALL WTCPMAIN MTCPMAIN > MDISK 198 3390 8820 009 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN MDISK > 191 > 3390 8829 007 XX1A06 MR RTCPMAIN WTCPMAIN MTCPMAIN > > SUBCONFIG TCPMNT-4 > LINK 6VMTCP30 491 491 RR > LINK 6VMTCP30 492 492 RR > MDISK 591 3390 8558 122 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN > MDISK 592 3390 8680 140 XX139F MR ALL WTCPMAIN MTCPMAIN > MDISK 198 3390 8820 009 XX139F MR RTCPMAIN WTCPMAIN MTCPMAIN MDISK > 191 > 3390 8829 007 VX139F MR RTCPMAIN WTCPMAIN MTCPMAIN > * > > PROFILE LNXDFLT > COMMAND SET VSWITCH PASSWORD GRANT &USERID > COMMAND DEFINE NIC 600 TYPE QDIO > COMMAND COUPLE 600 TO SYSTEM VSWPSEG1 > * > COMMAND SET VSWITCH VSWPSEG2 GRANT &USERID > COMMAND DEFINE NIC 700 TYPE QDIO > COMMAND COUPLE 700 TO SYSTEM VSWPSEG2 > * > CPU 00 BASE > CPU 1 > IPL CMS > MACHINE ESA 10 > IUCV ALLOW > OPTION CHPIDV ONE > CONSOLE 009 3215 T > SPOOL 000C 2540 READER * > SPOOL 000D 2540 PUNCH A > SPOOL 000E 1403 A > LINK MAINT 0190 0190 RR > LINK MAINT 019D 019D RR > LINK MAINT 019E 019E RR > LINK LNXMAINT 0192 0191 RR > LINK TCPMAINT 0592 0592 RR > > > USER LNX004 PASSWORD 512M 1G G > INCLUDE LNXDFLT > COMMAND DEFINE STORAGE 256M STANDBY 768M OPTION LNKNOPAS APPLMON > MDISK 0100 3390 0001 5008 XX1185 MR PASSWORD PASSWORD PASSWORD > MDISK 0101 3390 5009 5008 XX1185 MR PASSWORD PASSWORD PASSWORD > > As you can see the profile for LNXDFLT has a statement " LINK TCPMAINT > 0592 0592 RR". When I first tested the first zLinux image, it > complained about the vdisk 592. I realized that this statement > existed in z/VM V6.1 so I added the statement and the first zLinux > image came up and so were other zLinux images. > > At z/VM V6.3, when I attempted the LGR function, it complained about it. > Believe the statement is no longer applicable and need to code to > address to the "IDENTITY TCPMAINT" statement instead. However I do not > what the coding is like. Please advise. > > Thanks, > Ray > > -----Original Message----- > From: Chu, Raymond > Sent: Wednesday, December 17, 2014 4:26 PM > To: 'Linux on 390 Port' > Subject: RE: Problem to test relocating a Linux image to another z/VM > > I add the "rdev 0E1C EQ myEQID TYPE OSA" like this to SYSTEM CONFIG > and reIPLed. It worked > > > -----Original Message----- > From: Chu, Raymond > Sent: Wednesday, December 17, 2014 3:48 PM > To: 'Linux on 390 Port' > Subject: RE: Problem to test relocating a Linux image to another z/VM > > Never mind. Please ignore the previous email. It is not even a > communication controller and it is a special device. > > > -----Original Message----- > From: Chu, Raymond > Sent: Wednesday, December 17, 2014 2:44 PM > To: [email protected] > Subject: RE: Problem to test relocating a Linux image to another z/VM > > Alan, > > Understood that the EQID must be assigned to the VSWITCHes. I searched > the "define vswitch" command and did not have a parameter for EQID. > > I ran the command "q controller" command and it showed the follows: > > q controller > > Controller DTCVSW2 Available: YES VDEV Range: 0600-F000 Level 630 > Capability: IP ETHERNET VLAN_ARP GVRP LINKAGG ISOLATION > NO_ENSEMBLE NO_INMN BRIDGE_CAPABLE VEPA > SYSTEM VSWPSEG1 Active Controller: * RDEV: 0E1C > SYSTEM VSWPSEG2 Active Controller: * RDEV: 0F5F > > Controller DTCVSW1 Available: YES VDEV Range: 0600-F000 Level 630 > Capability: IP ETHERNET VLAN_ARP GVRP LINKAGG ISOLATION > NO_ENSEMBLE NO_INMN BRIDGE_CAPABLE VEPA > SYSTEM VSWPSEG1 Backup Controller: * RDEV: 0F5C > SYSTEM VSWPSEG2 Backup Controller: * RDEV: 0E1F > > Those VSWITCHes are within the Communication Controllers There is a > "set rdev" command for communication controllers as follows: > > -Set--RDEVice--+-rdev--------+--+------------+--TYpe----------> > '-rdev1-rdev2-' +-EQid--eqid-+ > '-NOEQid-----' > > .-SET_ADDRess--4-. > >--+-+-BSC_ADAPTer---+--+----------------+-+------------------->< > | +-IBM1_ADAPTer--+ '-SET_ADDRess--n-' | > | '-TELE2_ADAPTer-' | > '-3705----------------------------------' > > Therefore, I can do the following: > > set rdev 0E1C EQID myEQID > > However the Type parameter is mandatory. > > Could you let me know what it should be? > > Thanks, > Ray > > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Alan Altmark > Sent: Monday, December 15, 2014 11:32 PM > To: [email protected] > Subject: Re: Problem to test relocating a Linux image to another z/VM > > Email sent from outside of PSEG. Use caution before using > links/attachments. > > > On Monday, 12/15/2014 at 10:19 EST, "Chu, Raymond" > <[email protected]> > wrote: > > Hi, > > > > I had a chance to first test LGR function. This is what I had when I > > ran > the > > vmrelocate test command > > > > vmrelocate test seal005 airforce > > > > HCPRLH1940E SEAL005 is not relocatable for the following reason(s): > > HCPRLI1996I SEAL005: Virtual machine device 0592 is a link to a > > local > minidisk > > HCPRLI1982I SEAL005: Source system simulated network device 0600 is > coupled to > > a VSWITCH without an assigned EQID > > HCPRLI1982I SEAL005: Source system simulated network device 0700 is > coupled to > > a VSWITCH without an assigned EQID > > > > The VSWITCH definition in system config do not have definition for > > eqid > and do > > not how to set it. > > HELP HCP1928I gives you the information you need. You don't actually > assign the EQID to VSWITCH, but to the RDEVs that it is using as uplinks. > Your VSWITCHes are using devices E1C-E21 and 5FC-601 on all 4 LPARs, > but your RDEVICE statements aren't setting the EQID on those devices. > > For example, note here than you are assigning an EQID to E10-E12 and > F50-F52, but you aren't using those devices in the DEFINE VSWITCH. > > > NAVY: BEGIN > > rdev 0E10-0E12 eqid PSEGzVM type osa rdev 0F50-0F52 eqid PSEGzVM > > type osa vmlan macprefix 02000B vmlan MACIDRANGE SYSTEM > > 000001-0FFFFF USER 0F0001-0FFFFF vmlan limit transient 0 > > NAVY: END > : > > define vswitch VSWPSEG1 rdev 0E1C 0F5C ethernet define vswitch > > VSWPSEG2 rdev 0F5F 0E1F ethernet > > Alan Altmark > > Senior Managing z/VM and Linux Consultant Lab Services System z > Delivery Practice IBM Systems & Technology Group > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > [email protected] > IBM Endicott > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > > -----------------------------------------The information contained in > this e-mail, including any attachment(s), is intended solely for use > by the named addressee(s). If you are not the intended recipient, or > a person designated as responsible for delivering such messages to the > intended recipient, you are not authorized to disclose, copy, > distribute or retain this message, in whole or in part, without > written authorization from PSEG. This e-mail may contain proprietary, > confidential or privileged information. If you have received this > message in error, please notify the sender immediately. This notice is > included in all e-mail messages leaving PSEG. Thank you for your cooperation. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ----------------------------------------- The information contained in this e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, or a person designated as responsible for delivering such messages to the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, in whole or in part, without written authorization from PSEG. This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. This notice is included in all e-mail messages leaving PSEG. Thank you for your cooperation.
