IPv4 dynamic routing using OMPROUTE

Daemon is a UNIX term for a background server process, and daemons are used for dynamic routing. For z/OS® Communications Server IP, there is a multiprotocol routing daemon available. For IPv4, OMPROUTE supports the RIP Version 1, RIP Version 2, and OSPF routing protocols. You can send RIP Version 1 or RIP Version 2, but not both at the same time on a single interface. However, you can configure a RIP interface to receive both versions.

Guideline: If OROUTED was used in a prior release and the RIP protocol is still the preferred dynamic routing method in your host configuration, use OMPROUTE to provide RIP support.

For IPv4, OMPROUTE implements the OSPF protocol described in RFC 1583 (OSPF Version 2), the OSPF subagent protocol described in RFC 1850 (OSPF Version 2 Management Information Base), and the RIP protocols described in RFC 1058 (Routing Information Protocol) and in RFC 1723 (RIP Version 2 - Carrying Additional Information). It provides an alternative to the static TCP/IP gateway definitions. The MVS™ host running with OMPROUTE becomes an active OSPF or RIP router in an IP network. Either or both of these routing protocols can be used to dynamically maintain the host routing table. For example, OMPROUTE can detect when a route is created, is temporarily unavailable, or if a more efficient route exists. If both OSPF and RIP protocols are used simultaneously, OSPF routes are preferred over RIP routes to the same destination.

Tip: You can use the IBM® Health Checker for z/OS to check whether the total number of indirect routes in a TCP/IP stack routing table exceeds a maximum threshold. When this threshold is exceeded, OMPROUTE and the TCP/IP stack can experience high CPU consumption from routing changes. For more information about IBM Health Checker for z/OS, see z/OS Communications Server: IP Diagnosis Guide and IBM Health Checker for z/OS: User's Guide.