Thank you all for your responses,,, our 1st Q on Linux 390... we will move forward with the System_Identifier construct based on CPUID ... thanks again !
Clovis Pereira <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 11/18/2008 04:14 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: z/VM issues after replicating DASD to DR site Dresmond, you can solve all this questions only with changes into SYSTEM CONFIG. >>> 1) SYSTEM CONFIG has System_Identifer_Default ZVMCS1, we want our DR to >>> be ZVMCS3 Include Serial Number of each CPU to differentiate. Example: SYSTEM_IDENTIFIER_DEFAULT UNDEFND SYSTEM_IDENTIFIER * %%1341 ZVMCS1 SYSTEM_IDENTIFIER * %%0D06 ZVMCS3 >>> 2) I see duplicate MAC addresses on OSA,,, I found the VMLAN MACPREFIX >>> statement, but since it goes in SYSTEM CONFIG, that brings me back to the >>> first issue again. After step 1, prefix each VMLAN card with the Sysid. Example:>> ZVMCS1: VMLAN MACPREFIX 021341 ZVMCS3: VMLAN MACPREFIX 020D06 >>> 3) TCPIP profile needs a different IP address, maskl and Gateway at our >>> DR site. After step 1, TCPIP will use first the "sysid" profile by default. So, create two profiles TCPIP with different names: ZVMCS1 TCPIP, ZVMCS3 TCPIP, When these files exist, PROFILE.TCPIP will not be used by default. >>> 4) If we make any of the changes above on the DR system, they will get >>> over-written because the DASD replicates constantly. Make the changes on your base dasd before the replication. The two VM images can use the same SYSTEM CONFIG. There are other changes possible in this same line. Please, see the manual VM System Planning for details. Good luck. ______________________________________________ Clovis Pereira zVM & zOS Support - SWS Maintenance and Technical Support Services MTS Brazil phone: 55-11-2132-3399 [EMAIL PROTECTED] Dresmond McLaurin <Dresmond.McLauri [EMAIL PROTECTED]> To Sent by: Linux on [email protected] 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject z/VM issues after replicating DASD to DR site 18/11/2008 18:30 Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Hope this email finds you well... We are building zVM/Linux/CCL/IPTG to replace 3746-900's... We IPL'd our DR site remotely yesterday and ran into issues because we replicate mirror images of all DASD to DR site from production site... When z/VM ipls, CP is using the production system and some parameters don't work in DR... For example, 1) SYSTEM CONFIG has System_Identifer_Default ZVMCS1, we want our DR to be ZVMCS3 2) I see duplicate MAC addresses on OSA,,, I found the VMLAN MACPREFIX statement, but since it goes in SYSTEM CONFIG, that brings me back to the first issue again. 3) TCPIP profile needs a different IP address, maskl and Gateway at our DR site. 4) If we make any of the changes above on the DR system, they will get over-written because the DASD replicates constantly. Any guidance is greatly appreciated, thanks.... ---------------------------------------------------------------------- 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 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
<<image/gif>>
<<image/gif>>
<<image/gif>>
