Use the IPv6_OSPF statement to specify various parameters that apply globally to IPv6 OSPF, either to all interfaces or to the overall IPv6 OSPF autonomous system.
Syntax
>>-IPv6_OSPF--+--------------------+----------------------------> '-RouterID--=--value-' .-Comparison--=--Type2-. .-Demand_Circuit--=--YES---. >--+----------------------+--+--------------------------+-------> '-Comparison--=--value-' '-Demand_Circuit--=--value-' .-DR_Max_Adj_Attempt--=--0-----. .-Instance--=--0-----. >--+------------------------------+--+--------------------+---->< '-DR_Max_Adj_Attempt--=--value-' '-Instance--=--value-'
Parameters
- RouterID
- Every router in an IPv6 OSPF routing domain must be assigned a
unique 32-bit router ID.
The value used for the IPv6 OSPF router ID is chosen as follows:
- If this router ID is configured, the value
configured is used as the IPv6 OSPF router ID.
Rule: The reserved 0.0.0.0 address cannot be used as a router ID.
- If this router ID is not configured and IPv4 OSPF is also active on OMPROUTE, then the IPv4 Router ID value is also be used for IPv6.
Valid values are any 32-bit value, in dotted decimal format (in other words, specified as an IPv4-style IP address).
Restriction: If IPv4 OSPF is NOT active, then RouterID is a required configuration parameter.
- If this router ID is configured, the value
configured is used as the IPv6 OSPF router ID.
- Comparison
- Tells OMPROUTE where external routes fit in the IPv6 OSPF hierarchy.
IPv6 OSPF supports two types of external metrics. Type1 external metrics
are equivalent to the link state metric. Type2 external metrics are
greater than the cost of any path internal to the AS. Use of Type2
external metrics assumes that routing between autonomous systems is
the major cost of routing a packet, and eliminates the need for conversion
of external costs to internal link state metrics. Valid values are
Type1 (or 1) or Type2 (or 2).
For more information about the COMPARISON configuration parameter, see z/OS Communications Server: IP Configuration Guide.
- Demand_Circuit
- Global demand circuit setting. Coding YES enables demand circuits for IPv6 OSPF. Demand circuit parameters can then be coded on the IPv6_OSPF_Interface statement. Valid values are Yes or No.
- DR_Max_Adj_Attempt
- Specifies the maximum number of adjacency attempts to be used
for reporting and controlling futile neighbor state loops. After the
adjacency attempt count for a neighboring designated router reaches
the threshold, an informational message is issued to report the problem.
If a redundant interface is available that can reach the neighbor,
adjacency formation is attempted over that interface. An informational
message is issued to report the interface switch and the adjacency
formation attempt. Valid values are in the range 0 - 100. The value
0 indicates infinite retries.
For information about futile neighbor state loops, see the network design considerations information in z/OS Communications Server: IP Configuration Guide. For the types of interfaces supporting the futile neighbor state loop detection for OSPF, see Interfaces supported by OMPROUTE.
- Instance
- Provides the default instance number for OMPROUTE. OMPROUTE supports only one instance of IPv6 OSPF on a link, and this parameter specifies the default value for all IPv6 OSPF interfaces. This value can be overriden on individual IPv6_OSPF_Interface statements. Valid values are any integer from 0 - 255.