Download PDF - IBM Redbooks

4. Establish the NFS environment and access to the z/OS shared libraries.
5. Load the installation media to the installation space, and mount the file system.
6. Define the user IDs and credentials.
Continue with the SAP installation.
Hints and tips for network preparations
SAP systems consist of many components that require communication setup in a particular
way, depending on the selected platforms, server configurations, and corporate networking
standards. SAP and IBM provide detailed information about how to lay out the network in the
following documents:
► Installation Guides - SAP NetWeaver 7.3
► Business Continuity for SAP on IBM System z, SC33-8206-04
► SAP on DB2 UDB on DB2 for z/OS and OS/390: Connectivity Guide, SC33-7965
► SAP Note 1263782 about HiperSockets recommendations
This section provides several networking hints and tips for the following tasks:
► Preparing the network for the zEnterprise System
► Setting up near continuous availability of System z
► Setting up the network for z/VM
► Setting up the network for Linux on System z
Hints for preparing the network for the zEnterprise System
Use the fastest database-to-application server connection available. A low latency network
connection generally experiences small delay times, which is good for response time. Use the
following hints to assist you in preparing the network for the zEnterprise System:
► If you use HiperSockets to connect to a z/VM LPAR and Linux on System z application
server, use the following settings:
– Use 8992 MTU in the TCP/IP Profile (see SAP Note 1263782).
– Use 16K MFS in the IOCDS definition.
– Set up one LAN CHPID for the initial installation, but plan for multiple LANs for the
longer term, a minimum of two CHIPs (up to 16 can be defined).
► Use OSA-2 or OSA-3 adapters at a minimum, or use OSA-4 when available:
– Configure two or more ports on separate OSA cards for HA.
– Define TCP/IP Jumbo Frames (MTU=8992) if possible.
► For a static only network, define all static subnet routes in TCP/IP (ROUTE statement).
► The OSPF Routing Protocol (omproute address space) for dynamic routing offers the
following advantages:
– Selects shortest route in event of network connection failure
– Performs fast updates of routing tables.
– Permits a higher degree of availability by using alternative routing.
► For IP address conventions, consider the following suggestions:
– For database servers, use addresses ending in even numbers.
– For application servers, use addresses ending in odd numbers.
Appendix B. Planning, preparing, and implementing the SAP landscape 187