Ospfv3 Timers; Ospfv3 Configuration Example - Extreme Networks ExtremeWare XOS Guide Manual

OSPFv3 Configuration Example

The cost metric is inserted for all RIPng, static, and direct routes injected into OSPFv3. If the cost metric
is set to 0, the cost is inserted from the route. The tag value is used only by special routing applications.
Use 0 if you do not have specific requirements for using a tag. (The tag value in this instance has no
relationship with IEEE 802.1Q VLAN tagging.)
The same cost, type, and tag values can be inserted for all the export routes, or policies can be used for
selective insertion. When a policy is associated with the export command, the policy is applied on every
exported route. The exported routes can also be filtered using policies.
Verify the configuration using the command:
show ospfv3 {domain <domainName>}

OSPFv3 Timers

Configuring OSPFv3 timers on a per area basis is a shortcut to applying the timers to each VLAN in the
area at the time of configuration. If you add more VLANs to the area, you must configure the timers for
the new VLANs explicitly. Use the command:
configure ospfv3 {domain <domainName>} [vlan <vlan-name> | tunnel <tunnel-name> |
[vlan | tunnel] all] timer {retransmit-interval} <retransmit-interval> {transit-delay}
<transit-delay> {hello-interval} <hello-interval> {dead-interval} <dead-interval>
OSPFv3 Configuration Example
Figure 75 is an example of an autonomous system using OSPFv3 routers. The details of this network
follow.
563
ExtremeWare XOS 11.3 Concepts Guide