Add RIP Interface (ADDRIPIFC)

Where allowed to run: All environments (*ALL)
Threadsafe: No
Parameters
Examples
Error messages

The Add RIP Interface (ADDRIPIFC) command defines a RIP interface that the OMPROUTED server will add into the RIP (Routing Information Protocol) implementation. It sets the different parameters needed for each interface.

With this command IPv4 (RIPv2) and IPv6 (RIPng) Interfaces can be configured.

Restrictions:

Top

Parameters

Keyword Description Choices Notes
IFC Interface identifier Character value, *PPPCNNPRF, *PPP6CNNPRF Required, Positional 1
PPPCNNPRF Connection profile Character value, *NONE Optional
RCVRIP Receive RIP *YES, *NO, *RIP1, *RIP2, *ANY Optional
RCVDYNNET Receive dynamic networks *YES, *NO Optional
RCVDYNSUBN Receive dynamic subnets *YES, *NO Optional
RCVPFXRTE Receive prefix routes *YES, *NO Optional
RCVDYNHOST Receive dynamic hosts *NO, *YES Optional
SNDRIP Send RIP *YES, *NO Optional
SNDONLY Send only Values (up to 3 repetitions): *ALL, *VIRTUAL, *DEFAULT, *DIRECT, *TRIGGERED Optional
SNDDFTRTE Send default routes *NO, *YES Optional
SNDSTTRTE Send static routes *NO, *YES Optional
SNDHOSTRTE Send host routes *NO, *YES Optional
SNDNETRTE Send network routes *YES, *NO Optional
SNDSUBNRTE Send subnet routes *YES, *NO Optional
SNDPFXRTE Send prefix routes *YES, *NO Optional
SNDRVSRTE Send poisoned reverse routes *YES, *NO Optional
SNDRTRARTE Send router advertise routes *YES, *NO Optional
FILTER RIP filter Values (up to 6 repetitions): Element list Optional
Element 1: Destination route Character value
Element 2: Filter type *NOSND, *NORCV, *SND, *SNDCND, *RCV, *RCVCND
Element 3: Subnet mask Character value, *HOST
Element 4: Prefix length 1-128, 128
INMETRIC In metric 1-15, 1 Optional
OUTMETRIC Out metric 0-15, 0 Optional
RIPV2 RIP version 2 *YES, *NO Optional
AUTKEY Authentication key Character value Optional
Top

Interface identifier (IFC)

Specifies the internet address of a configured logical interface in the system. The interface identifier can be an IPv4 or IPv6 address.

This is a required parameter.

*PPPCNNPRF
The point-to-point connection profile specified for the Connection profile (PPPCNNPRF) parameter is used to send and receive RIP routing traffic over an IPv4 point-to- point link.
*PPP6CNNPRF
The point-to-point connection profile specified for the Connection profile (PPPCNNPRF) parameter is used to send and receive RIP routing traffic over an IPv6 point-to-point link.
character-value
Specify the internet address of the RIP interface to add. An IPv4 internet address is specified in the form nnn.nnn.nnn.nnn where nnn is a decimal number between 0 and 255. An IPv6 internet address is specified in the form n:n:n:n:n:n:n:n where n is a hexadecimal number in the range from 0 through X'ffff'. The value "::" indicates that one or more groups of 16 bits are zero.

The interface identifier can also be an alias name of an logical interface.

Top

Connection profile (PPPCNNPRF)

Specifies the profile created for point-to-point connection to a host at the remote end. This profile will be used later when the point-to-point link is being active.

*NONE.
Specifies that this interface will not work over a point-to-point link.
character-value
Specify the connection profile to be used. This profile must have been configured previuosly using Remote Access Services.
Top

Receive RIP (RCVRIP)

Specifies what type of RIP updates are accepted over this interface. Valid values are:

*YES
RIP packets are received over this interface, subject to other filters.

Note: If the RIP version 2 (RIPV2) parameter is set to *YES, then receive only RIP Version 2 updates over this interface. This is the default value. If it is set to *NO, then receive only RIP Version 1 updates over this interface. This note is only valid when IPv4 internet address is specified in the Interface identifier (IFC) parameter.

*NO
No RIP packets are received over this interface, regardless of any other filters.
*RIP1
Accept only RIP version 1 updates over this interface. Only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.
*RIP2
Accept only RIP version 2 updates over this interface. Only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.
*ANY
Accept RIP Version 1 and RIP Version 2 updates over this interface. Only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

Note: If RIP2 authentication is required and this value is set, unauthenticated RIP1 packets are received over this interface. Also, if RIP2 authentication is not required, authenticated RIP2 packets are not being received over this interface, regardless of the value of the RIP version 2 (RIPV2) parameter.

Top

Receive dynamic networks (RCVDYNNET)

Specifies whether or not to learn routes for networks over this interface. If this is not set, only nets explicitly allowed using the Add RIP Accepted Route (ADDRIPACP) command are accepted on this interface. This parameter is only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Receives dynamic network routes.
*NO
Does not receive dynamic network routes.
Top

Receive dynamic subnets (RCVDYNSUBN)

Specifies whether or not to learn routes for subnets over this interface. If this is not set, only subnets explicitly allowed using the Add RIP Accepted Route (ADDRIPACP) command are accepted on this interface. This parameter is only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Receives dynamic subnet routes.
*NO
Does not receive dynamic subnet routes.
Top

Receive prefix routes (RCVPFXRTE)

Specifies whether or not to learn routes for prefixes over this interface. If this is not set, only prefixes explicitly allowed using the Add RIP Accepted Route (ADDRIPACP) command are accepted on this interface. This parameter is only valid if an IPv6 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Receives dynamic prefix routes
*NO
Does not receive dynamic prefix routes.
Top

Receive dynamic hosts (RCVDYNHOST)

Specifies whether or not to learn routes for hosts over this interface. If this is not set, only hosts explicitly allowed using the Add RIP Accepted Route (ADDRIPACP) command are accepted on this interface.

*NO
Does not receive dynamic host routes.
*YES
Receives dynamic host routes
Top

Send RIP (SNDRIP)

Determines whether or not RIP advertisements are sent over this interface.

*YES
Sends RIP advertisements.
*NO
Does not send RIP advertisements.
Top

Send only (SNDONLY)

Specifies send restrictions.

Single values

*ALL
Specifies no send restrictions.

Other values (up to 3 repetitions)

*VIRTUAL
Sends virtual IP addresses.
*DEFAULT
Sends the default route.
*DIRECT
Sends direct routes.
*TRIGGERED
Only sends routes when requested or when route becomes inactive (metric 16).
Top

Send default routes (SNDDFTRTE)

Advertise the default route (destination 0.0.0.0 for IPv4 or destination/prefix len ::/0 for IPv6), if it is available, in RIP responses sent from this IP source address.

Note: If *DEFAULT is set on the Send only (SNDONLY) parameter, the Send default routes (SNDDFTRTE) parameter is ignored and is set to *YES.

*NO
Does not send default routes.
*YES
Sends default routes.
Top

Send static routes (SNDSTTRTE)

Advertise static and direct routes in RIP responses sent from this IP source address. Split horizon is applied; that is, static routes configured over an interface are not included in RIP responses sent from that interface.

*NO
Does not send static routes.
*YES
Sends static routes.
Top

Send host routes (SNDHOSTRTE)

Advertise host routes in RIP responses sent from this IP source address. In this context, a host route is one with a subnet mask of 255.255.255.255 (IPv4) or a prefix length of 128 (IPv6).

*NO
Does not send host routes.
*YES
Sends host routes.
Top

Send network routes (SNDNETRTE)

Advertise all network level routes in RIP responses sent from this IP address. This parameter is only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Sends network routes.
*NO
Does not send network routes.
Top

Send subnet routes (SNDSUBNRTE)

Advertise appropriate subnet-level routes in RIP responses sent from this IP address. This parameter is only valid if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

In this context an appropriate subnet is one that meets RFC 1058 subnet advertisement constraints as follows:

*YES
Sends subnet routes.
*NO
Does not send subnet routes.
Top

Send prefix routes (SNDPFXRTE)

Advertise all prefix routes in IPv6 RIP responses sent from this IP address. This parameter is only valid if an IPv6 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Sends prefix routes.
*NO
Does not send prefix routes.
Top

Send poisoned reverse routes (SNDRVSRTE)

Advertise poisoned reverse routes over the interface corresponding to the next hop. A poison reverse route is one with an infinite metric (16). If *NO is specified, OMPROUTED still uses split horizon.

*YES
Sends poisoned reverse routes.
*NO
Does not send poisoned reverse routes.
Top

Send router advertise routes (SNDRTRARTE)

Advertise router advertisement routes in IPv6 RIP responses sent from this IP source address. These are routes that have been learned by the stack using IPv6 Router Discovery and that OMPROUTED has learned from the stack. Split horizon is applied; that is, router advertisement routes learned over an interface are not included in IPv6 RIP responses sent from that interface. This parameter is only valid if an IPv6 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Sends router advertise routes.
*NO
Does not send router advertise routes.
Top

RIP filter (FILTER)

Specifies up to six filters on a RIP Interface. When specified on the RIP Interface, the filter parameter applies only to the corresponding RIP interface. The Filter can also be set stand-alone in the OMPROUTED configuration file (nosend and noreceive only) to apply to all configured RIP interfaces. The Add RIP Filter (ADDRIPFLT) command is used for that purpose.

RIP Filters can be configured to OMPROUTED such that certain RIP routing information will not be sent out to other routers and/or accepted from other routers. By using filters, an installation can limit the amount of RIP routing information sent into the network and/or the amount of RIP routing information maintained by OMPROUTED. In addition, filters can be used to hide destination addresses from portions of the network.

In order to add an IPv4 RIP filter to this RIP interface, the Destination route, the Filter type and the Subnet mask elements are required. The Prefix length element would be ignored for IPv4 routes. However, in order to add an IPv6 RIP filter, the Destination route, the Filter type and the Prefix length elements are required. The Subnet mask element would be ignored for IPv6 routes.

Single values

*NONE
No extra filters will be applied to this RIP interface.

Element 1: Destination route

The Destination route element specifies the route in network, subnetwork, or host format in dotted decimal form for IPv4 or the route in colon-hexadecimal format for IPv6. Alternatively, wildcards (*IPV4 or *IPV6), which matches any destination, can be set to filter out all routes sent or received over an interface. The use of the wildcards is also referred to as a blackhole filter. This should be used in conjunction with either additional send or receive filters to allow only certain routes to be received; or advertised over an interface or set of interfaces. The address can be an IPv4 or IPv6 address.

character-value
An IPv4 internet address is specified in the form nnn.nnn.nnn.nnn where nnn is a decimal number between 0 and 255. An IPv6 internet address is specified in the form n:n:n:n:n:n:n:n where n is a hexadecimal number in the range from 0 through X'ffff'. The value "::" indicates that one or more groups of 16 bits are zero.

Element 2: Filter type

The filter type can be any of the following values:

*NOSND
Specifies that routes matching the Destination route element and subnet mask (IPv4) / prefix length (IPv6) are not going to be sent over this RIP interface. This option serves as a RIP output filter.
*NORCV
Specifies that routes matching the Destination route element and subnet mask (IPv4) / prefix length (IPv6) are going to be ignored in messages received over this RIP interface. This option serves as a RIP input filter.
*SND
Specifies that routes matching the Destination route element and subnet mask (IPv4) / prefix length (IPv6) are going to be sent over only this RIP interface (or any other RIP interface with an equivalent filter). This option serves as an RIP output filter and can be used for inbound and outbound traffic splitting.
*SNDCND
Specifies that routes matching the .Destination route element and subnet mask (IPv4) / prefix length (IPv6) are going to be sent over only this interface, when this interface is active (or any other active RIP interface with an equivalent filter). If this interface is inactive, the routes can be sent over other interfaces. This option serves as an RIP output filter and can be used for inbound and outbound traffic splitting.
*RCV
Specifies that routes matching the Destination route element and subnet mask (IPv4) / prefix length (IPv6) are going to be received over only this interface (or any other RIP interface with an equivalent filter). If received over other RIP interfaces, the routes are discarded. This option serves as an RIP input filter.
*RCVCND
Specifies that routes matching the Destination route element and subnet mask (IPv4) / prefix length (IPv6) are going to be received over only this interface when this interface is active (or any other active RIP interface with an equivalent filter). If this interface is inactive, the routes can be received over all other active RIP interfaces. This option serves as an RIP input filter.

Element 3: Subnet mask

Specifies the subnet mask with respect to the network range specified for the Destination route element. If this value is not set, the default subnet mask is 255.255.255.255 (*HOST), meaning apply the filter to the Destination route element as was set. Setting the subnet mask has no meaning and is not valid, if the Destination route element is set as a wildcard (*IPV4) for a blackhole filter. Subnet mask is ignored for IPv6 destination routes.

*HOST
The subnet mask value used will be 255.255.255.255.
character-value
Specify the mask for the network subnet field and host address field of the internet address that defines a subnetwork. The subnet mask is in the form nnn.nnn.nnn.nnn, where nnn is a decimal number ranging from 0 through 255. The subnet mask must mask off all bits of the network class's network ID portion of the internet address.

For example, 255.255.255.0 could define a subnet mask for an interface with a Class B internet address. In this example, the first two octets must be 1 bits because these octets define the network ID portion of the Class B internet address. The third octet of this subnet mask defines the actual subnet mask ID portion of the interface's internet address. It is also all 1 bits. This leaves the fourth octet to define the host ID portion of the interface's internet address.

Element 4: Prefix length

Specifies how much of the leftmost portion of an IPv6 address is the subnet prefix. If not set, the default prefix length is 128, meaning apply the filter to the Destination route element as was set. Setting the prefix length has no meaning and is not valid if the Destination route element is set as a wildcard (*IPV6) for a blackhole filter. The prefix length is ignored for IPv4 destination routes.

128
The default is 128, which means the Destination route element specified is a host address.
1-128
Specify the number of bits of the IPv6 internet address to use as the subnet prefix.
Top

In metric (INMETRIC)

Specifies the value of the metric to be added to RIP routes received over this interface prior to installation in the routing table.

1
The default is 1.
1-15
Specify the value of the metric.
Top

Out metric (OUTMETRIC)

Specifies the value of the metric to be added to RIP routes advertised over this interface.

0
The default is 0.
0-15
Specify the value of the metric.
Top

RIP version 2 (RIPV2)

Enables RIP version 2 packets to be sent on this link. Valid values are *YES or *NO. If *YES, all RIP packets sent on this link are RIPv2. If *NO, all RIP packets sent on this link are RIPv1. See the Receive RIP (RCVRIP) parameter description above for information about configuring the level of RIP packets that can be received on this link. This parameter is ignored if an IPv6 internet address was specified in the Interface identifier (IFC) parameter.

*YES
Sends RIP version 2 packets.
*NO
Sends RIP version 1 packets.
Top

Authentication key (AUTKEY)

RIP version 2 authentication key. Only used for RIP version 2 packets. Setting this key does not prevent reception of unauthenticated RIPv1 packets. To ensure that only authenticated RIP packets can be received over this interface, set the Receive RIP (RCVRIP) parameter to *RIP2 in addition to this parameter. Valid values are any alphanumeric string up to 16 characters in length coded within double quotation marks, or any hexadecimal string which begins with 0x. This parameter is only valid for RIPv2 if an IPv4 internet address was specified in the Interface identifier (IFC) parameter.

Note: - If the value is entered in characters (rather than the hexadecimal string), that value is case sensitive. - If an authentication key is not provided, authenticated RIP version 2 packets are not received, even if the Receive RIP (RCVRIP) parameter is set to *ANY.

character-value
Specify the authentication key for this interface. This value must be the same in all routers that are attached to a common network. This parameter is ignored for RIPng (IPv6).
Top

Examples

Example 1:Adding an IPv4 RIP Interface

ADDRIPIFC   IFC('9.67.107.7')

This command adds an IPv4 RIP interface. The referenced logical interface must exist on the system. Use the NETSTAT *IFC command to verify that the logical interface exists.

Example 2:Adding a RIPng Interface

ADDRIPIFC   IFC('1000::5678:9abc:def')

This command adds a RIPng interface (IPv6 based). The referenced logical interface must exist on the system. Use the NETSTAT *IFC command and press F20 (Work with IPv6 interfaces) to verify that the logical interface exists.

Top

Error messages

*ESCAPE Messages

TCP8050
*IOSYSCFG authority required to use &1.
TCP6581
Interface with address &1 does not exist.
TCP6582
Interface with address &1 already exists in the RIP configuration file.
TCP6583
Value for parameter &1 not valid.
TCP6584
Internet address &1 not valid for parameter &2.
TCP6585
Interface with alias name &1 already exists in the RIP configuration file.
TCP6586
Interface with alias name &1 does not exist.
TCP6589
Internet address version 6 &1 not valid for parameter &2.
TCP9999
Internal system error in program &1.
Top