Chapter 2. Planning 9
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 cards.
2.2 z/VM conventions
It is good practice to use naming conventions so that you and others can recognize z/VM
resources by their names. This section discusses such conventions for DASD volume names
and backup file names.
2.2.1 Volume labeling convention
Use a convention for labeling DASD. Your enterprise may already have a labeling convention
which 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 DASD is shared among LPARs, in which case your z/VM LPAR can see DASD
that is owned by other LPARs. In this situation, it is convenient to identify the LPAR that
owns
the DASD. The volume labeling convention used in this book identifies the LPAR using the
first character. That leaves the second character in the label to identify the basic function of
the DASD.
The LPAR used in this book is identified by the character M. The following characters are
used for the types of DASD in the second character of the label:
M Minidisk space (PERM)
P Paging space (PAGE)
S Spool space (SPOL)
T Temporary disk space (TDISK)
V z/VM operating system volumes
Komentarze do niniejszej Instrukcji