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: LINUX-390@VM.MARIST.EDU
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:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan 
Altmark
Sent: Monday, December 15, 2014 11:32 PM
To: LINUX-390@VM.MARIST.EDU
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" <raymond....@pseg.com>
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
alan_altm...@us.ibm.com
IBM Endicott

----------------------------------------------------------------------
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
----------------------------------------------------------------------
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 lists...@vm.marist.edu 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/

Reply via email to