Chapter 2. Planning 9
– A Linux SSH client, such as PuTTY (recommended) or TeraTerm
–A VNC viewer
These resources are described in more detail in the chapters that follow.
2.1.3 Networking resources
The following network resources are needed:
A TCP/IP address for z/VM
One TCP/IP address for each Linux virtual server
Associated TCP/IP information:
– DNS host name
– DNS domain
– DNS server TCP/IP address
–TCP/IP gateway
– TCP/IP subnet mask
– TCP/IP broadcast address (usually calculated from address and subnet mask)
– TCP/IP MTU size
The TCP/IP addresses must be routed to the OSA card(s).
2.2 z/VM conventions
It is a best practice to use naming conventions so that you and others can recognize z/VM
resources by their names. This section discusses conventions for DASD volume names and
backup file names.
2.2.1 Volume labeling convention
You should have a convention for labeling DASDs. You might already have a labeling
convention that will largely determine the labels to be given to the DASD used by your z/VM
and Linux LPAR.
Each System z DASD is addressed with a device number consisting of four hexadecimal
digits. Each System z DASD has a six character label. It is convenient to include the four-digit
address in the label so that you can easily tell the address of each DASD from its label. When
followed, this convention guarantees that no two DASDs will have the same label. This can
be an important issue especially when z/OS® has access to the DASD.
Sometimes a DASD is shared among LPARs, in which case your z/VM LPAR can
see a
DASD
owned by other LPARs. In this situation, it is convenient to identify the LPAR that owns
the DASD. Therefore the volume labeling convention used in this book identifies the LPAR
with the first character. That leaves the second character in the label to identify the basic
function of the DASD.
Commenti su questo manuale