z/OS Communications Server: SNA Network Implementation Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


EE reliability and strategy

z/OS Communications Server: SNA Network Implementation Guide
SC27-3672-01

Because EE relies on IP network strategy and integrity, effective IP network design is essential to ensure successful EE implementation. The robustness of EE depends on the stability of your IP network configuration, just as any mission-critical TCP application does. With a stable IP network configuration in place, EE ensures the availability of SNA applications.

In planning your EE environment, discuss your configuration with the WAN environment architect to determine whether VPN or your firewall will be affected. You should also communicate with those responsible for MVS™, because EE can affect the way OSA, OSAE, or CIP are defined.

Base a well-designed IP Infrastructure on the following considerations:
  • The dynamic routing update protocols being used (such as OSPF, RIP, RIPV2, EIGRP, and so on)
  • Use of a private intranet in contrast to the public Internet
  • The type of network interfaces used, and MTU size
  • The IP security mechanisms (NAT, IPSec, firewall)
  • The quality of service (QoS) for the WAN

Figure 1 shows the differences between a SNA network and EE using an IP network.

Figure 1. Comparison between an EE network and a SNA network
Diagram that shows the difference between an EE network and a SNA network.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014