GLOBAL_OPTIONS statement

Use the GLOBAL_OPTIONS statement to configure miscellaneous options to OMPROUTE which apply to OSPF, RIP, or neither.

Syntax

Read syntax diagramSkip visual syntax diagram
                   .-Ignore_Undefined_Interfaces=NO----.   
>>-Global_Options--+-----------------------------------+-------><
                   '-Ignore_Undefined_Interfaces=value-'   

Parameters

Ignore_Undefined_Interfaces
Instructs OMPROUTE on how to handle stack interfaces that are not configured by way of OSPF_INTERFACE, RIP_INTERFACE, IPV6_RIP_INTERFACE, IPV6_OSPF_INTERFACE, INTERFACE, or IPV6_INTERFACE statements, either explicit or wildcard. NO indicates that OMPROUTE configures such interfaces with default values (including setting the MTU size to 576 and using the class mask as the subnet mask and overriding stack definition values with these default values for IPv4 interfaces), and possibly advertises these interfaces to the rest of the network if OSPF settings or RIP filters permit it.

Result: By definition, the network class masks that are used for undefined IPv4 interfaces if GLOBAL_OPTIONS Ignore_Undefined_Interfaces=NO is coded, or the GLOBAL_OPTIONS statement is not coded, (thereby taking the default of NO) are as follows:

  • Class A: 255.0.0.0
  • Class B: 255.255.0.0
  • Class C: 255.255.255.0

A YES value indicates that OMPROUTE ignores these interfaces, does not configure them, and does not advertise them under any circumstances. IF YES is coded, OMPROUTE does not advertise these interfaces or their attached subnets or prefixes, and it does not update any stack definition values. Static routes coded in the TCP/IP profile over interfaces that are ignored by OMPROUTE are still advertised by OMPROUTE into OSPF, RIP, or both if appropriate filters and settings permit the advertisement of static routes.

Guideline: Code YES to get additional reconfiguration capability. You can use OMPROUTE reconfiguration to add a definition for an interface that has been defined to the stack but is ignored by OMPROUTE. However, OMPROUTE does not associate the interface with the new definition until it has been deleted from the stack and re-added.