On Tuesday, 11/18/2008 at 03:34 EST, Dresmond McLaurin <[EMAIL PROTECTED]> wrote: > 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
Add a System_Identifier (not System_Identifier_Default) that is pre-defined with the CPU serial number of the DR site. Or reverse it and make ZVMCS3 the default and add a statement to cover your home system. > 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. Having done as described above, you can prefix the VMLAN statement with the system id. E.g. ZVMCS3: VMLAN xxxxx ZVMCS1: VMLAN yyyyy > 3) TCPIP profile needs a different IP address, maskl and Gateway at our > DR site. Use "nodeid TCPIP" instead of PROFILE. The node name comes from SYSTEM NETID S. That, too, is selected by CPU ID. IF there is no matching entry in SYSTEM NETID, the default node name will be the System_Identifer. > 4) If we make any of the changes above on the DR system, they will get > over-written because the DASD replicates constantly. All of the changes above will be in your *production* system and will be replicated. All is geared off of the SYSTEM_IDENTIFIER. Alan Altmark z/VM Development 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
