> I wish to test our TCP/IP configuration as second level and then use the > same configuration when we go first level. Our OSA UCBs are: > > F800-F802 > F900-F902 > FC00-FC02 > FD00-FD02 > > What is the best method of adding these UCBs to VMTESTSV?s directory entry > so I can build my second level TCPIP configuration using the real UCBs. I > hope this makes sense.
Get a new small subnet (8 or 16 addresses) from your network guys. Also get the network guys to add routing entries to indicate to your production network that the new segment is reachable via the address of your production VM TCPIP (or use a Linux guest instead; much more powerful, at the expense of more complexity). On 1st level, define a separate VSWITCH for connecting to the 2nd level guest. Use NICDEF in the directory entry for the 2nd level machine to build a virtual OSA at the proper virtual address and couple the virtual NICs to that new VSWITCH. On your first level VM TCPIP, add a new NICDEF and couple it to the new VSWITCH. Configure it with one of the new IP addresses from the new subnet (usually the lowest one). Make certain you IPL CMS first in your 2nd level VM userid. In the PROFILE EXEC for the 2nd level system use SET CPUID to set a different CPU ID than your real one. In the 2nd level system, update SYSTEM NETID on the S disk to have a different nodeID for the CPU id you set in the PROFILE EXEC, and make similar changes in SYSTEM CONFIG on MAINT CF1 and CF2. In the PROFILE TCPIP for the 2nd level system, use the multi-node support to specify config statements based on node id, eg: NORMAL: HOME xxx.x.... LVL2VM: HOME yyy... This whole rigamarole allows you to bring the same system up on 1st level or 2nd level and have it automatically configure different IP addresses, etc to reflect whether it's production or test. The separate subnet is necessary so that IP routing works from the outside while you're running 2nd level. The trick with changing the CPUid also gives you a reminder which system you're on in the bottom right of the screen (helps avoid typing CP SHUTDOWN to the wrong CP...8-)). ---------------------------------------------------------------------- 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
