NCPROUTE is a server that provides an alternative to using the
Network Control Program (NCP) as a static host-independent IP router.
NCPROUTE has the following effects:
- NCP becomes an active RIP router on an IP network.
- NCP becomes responsive to SNMP route table queries.
Notes: - NCPROUTE requires NCP V7R1, or later.
- NCPROUTE requires SNALINK LU0 when using NCP V7R3 or previous.
- SNALINK and IP over CDLC is supported for ESCON, BCCA, and CADS
channels.
- IP over CDLC can be used instead of SNALINK when using NCP V7R4,
or later.
- If using RIP Version 2, NCPROUTE requires NCP V7R6, or later.
Also, the NCP generation definition must have VSUBNETS=YES specified
on the BUILD statement.
- NCP versions V6R1 and V6R2 support static IP routing only. NCP
uses these static route tables to deliver datagrams over connected
IP networks. NCP V7R1 can be specified only as a host-dependent router
and it requires the NCPROUTE server to function as a RIP router.
- If using NCPROUTE with SNALINK, IP over CDLC channels, and OMPROUTE,
you should customize the NCST interface metric on the NCP client side
for the SNALINK NCST connection so the routes will be less preferred.
This causes OMPROUTE to prefer routes from the IP over CDLC interface
over the ones from the SNALINK interface. To customize the interface
metric, see the interface metric option
in Step 8: Configure the NCPROUTE gateways data set (Optional).
Do the same for the SNALINK interface on the MVS™ host side by customizing the metric in the
BSDROUTINGPARMS statement. RIP traffic will be carried over the IP
over CDLC interface, while transport PDUs (for example, Hello, Add
Route Request, Delete Route Request) will be carried over the SNALINK
interface.
- NCPROUTE does not support zero subnets.
NCPROUTE provides dynamic route table updates for one or more NCP
clients that have been generated as IP routers and have NCPROUTE specified
as the NCPROUTE server. NCPROUTE tables are updated periodically in
the NCP client based on updates sent by the NCPROUTE server. These
updates reflect dynamic changes in route states.
An NCPROUTE server
at the host uses the Routing Information Protocol (RIP), described
in RFC 1058 (RIP version 1) and in RFC 1723 (RIP version 2). The same
routing protocols are used by OMPROUTE. NCPROUTE is implemented as
a RIP server operating on an MVS host
connected to a RIP client in the NCP. Together they provide the appearance
to the IP network of an IP router using the RIP protocol. The same
client/server pair also provides SNMP agent support for network management
route table queries. RIP Versions 1 and 2 are currently supported
by NCPROUTE. For a brief description of RIP (Versions 1 and 2), see Routing.