Print Download PDF Send Feedback

Previous

Next

IPv6 OSPF

In This Section:

Configuring OSPFv3 with IPv6 VRRP

Configuring IPv6 OSPFv3 - Gaia Portal

Configuring IPv6 OSPFv3 - Gaia Clish (ipv6 ospf)

Monitoring IPv6 OSPFv3

Open Shortest Path First (OSPF) is a link-state routing protocol that calculates forwarding tables in an IP-based internetwork. OSPF is the preferred Interior Gateway Protocol (IGP) for Check Point.

OSPF supports IPv6. OSPF for IPv6 is also referred to as OSPF version 3 (OSPFv3). OSPFv3 is defined in RFC 5340 (which makes RFC 2740 obsolete).

For IPv6, VRRP clusters are supported. ClusterXL clusters are not supported.

The IPv6 address appearing in the source of OSPF packets sent on the interface must be a link-local address, that is, an FE80::/64 address. A link-local address is automatically added to each interface when IPv6 is enabled on Gaia. The addresses are used for next hops, to advertise routes, and to send hello messages. OSPF advertises the IPv6 addresses defined by the user, but OSPF exchanges routes using the FE80 addresses. A /64 address is required by the OSPFv3 protocol. If the peer router does not use an FE80::/64 address, OSPFv3 does not work.

OSPFv2 is used with IPv4. See OSPF.

Configuring OSPFv3 with IPv6 VRRP

To use OSPFv3 with VRRPv3, enable the Virtual Address option on the IPv6 OSPF Interface configuration page. If the configured interface is part of the VRRP master virtual router, OSPFv3 runs on the interface. When you enable this option, OSPFv3 uses the VRRPv3 virtual link-local address for the interface as the source of its control packets. This cannot be the automatically configured link-local address—that is, you must change the link-local address for the interface to something other than the default. You must configure the same link-local address on all the routers in the VRRP group.

VRRP installs the link-local address only on the master, so OSPFv3 runs only on that router. If a failover occurs, VRRPv3 installs the link-local address on the new master and OSPFv3 starts running on that system. Because OSPFv3 runs on one router at a time, there is no synchronization of OSPFv3 state between the VRRP group members.

Configuring IPv6 OSPFv3 - Gaia Portal

OSPFv3 has almost the same configuration parameters as OSPFv2.

To configure IPv6 OSPF:

  1. Enable IPv6. This automatically adds FE80::/64 link local to the interfaces.
  2. Open the Advanced Routing > IPv6 OSPF page of the Portal.
  3. Define IPv6 OSPF Global settings, including the Router ID.
  4. Optional: Define additional IPv6 OSPF areas, in addition to the backbone area.
  5. Optional: For each area, you can add one or more address ranges if you want to reduce the number of routing entries that the area advertises into the backbone.

    Note - To prevent an address range from being advertised into the backbone, select Restrict for the address range

  6. Configure IPv6 OSPF Interfaces.

IPv6 OSPF Global Settings

Configure these IPv6 OSPF global parameters.

Note: Graceful Restart Helper is not supported.

Parameter

Description

Router ID

A number that uniquely defines the router in a routing domain.
Best Practice - Selecting an existing IP address in the unit is recommended because the OSPF Router ID inherently makes it unique. We recommend setting the Router ID rather than relying on the system to pick on based on an IP address. This prevents the router ID from changing if the interface used for the router ID goes down.

  • Range: Dotted-quad.([0-255].[0-255].[0-255].[0-255]). Do not use 0.0.0.0.
  • Default: A non-loopback IPv4 address assigned to the loopback interface, if available. Otherwise the system selects an IPv4 address from the list of active interfaces.

SPF Delay

The time (in seconds) the system waits before recalculating the OSPF routing table after a change in the topology.

  • Default: 2.
  • Range: 1-60.

SPF Hold Time

The minimum time (in seconds) between recalculations of the OSPF routing table.

  • Default:5.
  • Range: 1-60.

Default ASE Route Cost

When routes from other protocols are redistributed into OSPF as ASEs, they are assigned this configured cost unless a cost has been specified for the individual route.

  • Range: 1-16777215.
  • Default: 1.

Default ASE Route Type

When routes from other protocols are redistributed into OSPF as ASEs, they are assigned this route type, unless a type has been specified for the individual route. ASEs can either be type 1 or type 2.

  • Type 1: Used for routes imported into OSPF which are from IGPs whose metrics are directly comparable to OSPF metrics. When a routing decision is being made, OSPF adds the internal cost to the AS border router to the external metric.
  • Type 2: Used for routes whose metrics are not comparable to OSPF internal metrics. In this case, only the external OSPF cost is used. In the event of ties, the least cost to an AS border router is used.
  • Range: Type 1, Type 2
  • Default: 1.

 

IPv6 OSPF Areas

Configure these IPv6 OSPF Area parameters.

The Areas section shows the IPv6 OSPF parameters of each area.

Add/Edit Area

Parameter

Description

Area

For the name of the area, choose an IPv4 address (preferred) or an integer.

Use Stub Area Type

A Stub Area is an area in which there are no Autonomous System External (ASE) routes. ASE routes are routes to destinations external to the AS.

Note: The backbone area cannot be a stub area. NSSA Areas are not supported.

  • Range: Selected (Area Type is Stub), Deselected (Area Type is Normal)
  • Default: Deselected

Stub Area Parameters

These parameters show if you define the area as a stub area.

Parameter

Description

Cost for Default Route

The cost for the default route to the stub area.

  • Range: 1-16777215.
  • Default: No default.

Totally Stubby

An area in which there are no ASE routes or summary routes.

  • Default: Areas are not initially totally stubby.

Add/Edit Address Range

Parameter

Description

Address Range

An area can be configured with any number of address ranges. Address ranges are used to reduce the number of routing entries that a given area will emit into the backbone (and hence all) areas.

An address range is defined by a prefix and a mask length. If a given prefix aggregates a number of more specific prefixes within an area, then an address range can be configured and will be the only prefix advertised into the backbone. Be careful when configuring an address range that covers parts of a prefix that are not contained within the area.

Restrict

Prevent an address from being advertised into the backbone.

  • Range: Selected (Restrict), Deselected (Do not restrict)

Add/Edit Stub Network

Parameter

Description

Address Range

OSPF can advertise reachability to prefixes that are not running OSPF by configuring a stub network. The advertised prefix shows as an OSPF internal route and can be filtered at area borders with the OSPF area ranges. The prefix must be directly reachable on the router where the stub network is configured (that is, one of the routers interface addresses must fall in the prefix) in order to be included in the router-LSA. Stub hosts are configured by specifying a mask length of 128.

An address range is defined by a prefix and a mask length. A prefix and mask can be advertised. That can be activated by the local address of a point-to-point interface. To advertise reachability to such an address, enter an IP address for the prefix and a non-zero cost for the prefix.

 

Cost

The cost associated with the stub network. The higher the cost, the less preferred the prefix as an OSPF route.

  • Range: 1-65535
  • Default: 1

IPv6 OSPF Interfaces

To configure an IPv6 OSPF interface:

  1. In the Add/Edit Interface window, assign the appropriate Area to each interface by selecting the OSPF area that this interface participates in.

    The OSPF interface configuration parameters are displayed showing the default settings. If you want to accept the default settings for the interface, no further action is necessary.

  2. (Optional) Change any configuration parameters for the interface.

Note - The hello interval and dead interval must be the same for all routers on the link. Authentication is not supported for IPv6 OSPF interfaces.

Add/Edit Area

Parameter

Description

Interface

The interfaces for OSPF configuration. An interface must have an area associated with it in order to become active in OSPF.

Area

The OSPF area to which the interface belongs. An OSPF area defines a group of routers running OSPF that have the complete topology information of the area. OSPF areas use an area border router to exchange information about routes. Routes for a given area are summarized into the backbone area for distribution into other non-backbone areas. An area border router (ABR) is one that has at least two interfaces in at least two different areas. One of those areas must be the backbone or the router must have a virtual link configured. OSPF forces a hub and spoke topology of areas, with the backbone area always being the hub.

  • Range: All areas currently configured.
  • Default: None.

Hello interval

The time, in seconds, between hello packets that the router sends on the interface. For a given link, this must be the same on all routers or adjacencies will not be created.

  • Range: 1-65535 (seconds).
  • Default: For broadcast interfaces, the default is 10 seconds. For point-to-point interfaces, the default is 30 seconds.

Dead interval

The number of seconds after a router stops receiving hello packets that it declares the neighbor is down. Typically, the value of this field should be four times the size of the hello interval.

For a given link, this field must be the same on all routers or adjacencies will not be created. The value must not be zero.

  • Range: 1-65535 (seconds).
  • Default: For broadcast interfaces, the default is 40 seconds. For point-to-point interfaces, the default is 120 seconds.

Retransmit interval

The number of seconds between LSA retransmissions, for adjacencies belonging to this interface. Also used when retransmitting Database Description and Link State Request Packets. This should be well over the expected round-trip delay between any two routers on the attached network. The setting of this value should be conservative or needless retransmissions will result.

  • Range: 1-65535 (seconds).
  • Default: 5.

OSPF Cost

The weight of a given path in a route. The higher the cost, the less preferred the link. You may explicitly override this setting in route redistribution. To use one interface over another for routing paths, give one a higher cost.

  • Range: 1-65535.
  • Default: 1.

Election Priority

The priority for becoming the designated router (DR) on this link. When two routers attached to a network both attempt to become a designated router, the one with the highest priority wins. If there is currently an elected DR on the link, it will remain the DR regardless of the configured priority. This feature prevents the DR from changing too often. This field is only relevant on a shared-media interface (Ethernet), as a DR is not elected on point-to-point type interfaces. A router with priority 0 is not eligible to become the designated router.

  • Range: 0-255.
  • Default: 1.

Passive

An interface in passive mode does not send hello packets out of the given interface. This means no adjacencies are formed on the link. The purpose of passive mode is to make it possible for the network associated with the interface to be included in the intra-area route calculation. In non passive mode, the network is redistributed into OSPF and is an ASE. In passive mode, all interface configuration information is ignored, with the exception of the associated area and the cost.

  • Default: Not selected.

Virtual Address

Directs OSPFv3 to use the VRRPv3 virtual link-local address as the source of its control packets. When enabled, OSPFv3 runs on the interface only while the local router is the master with respect to a VRRPv3 state machine on the interface.

Note: The VRRPv3 state machine must back-up an IPv6 link-local address that is not auto-configured on the interface.

  • Default: Unselected.

Configuring IPv6 OSPFv3 - Gaia Clish (ipv6 ospf)

The commands for OSPFv3 are similar to those for OSPFv2, except that instead of ospf you type ipv6 ospf3.

To show the configuration, use show ipv6 ospf commands.

To work with OSPFv3, you must enable IPv6 on Gaia. This automatically adds FE80::/64 link local to the interfaces.

When you do initial configuration, set the router ID. Use this command:

set router-id [default | <ip_address>]

Parameter

Description

default

Selects the highest interface address when OSPF is enabled.

<ip_address>

Specifies a specific IP address to assign as the router ID. Do not use 0.0.0.0 as the router ID address. Best Practice - Check Point recommends setting the router ID rather than relying on the default setting. Setting the router ID prevents the ID from changing if the default interface used for the router ID goes down.

The Router ID uniquely identifies the router in the autonomous system. The router ID is used by the BGP and OSPF protocols. We recommend setting the router ID rather than relying on the default setting. This prevents the router ID from changing if the interface used for the router ID goes down. Use an address on a loopback interface that is not the loopback address (127.0.0.1).

Note - In a cluster, you must select a router ID and make sure that it is the same on all cluster members.

  • Range: Dotted-quad.([0-255].[0-255].[0-255].[0-255]). Do not use 0.0.0.0
  • Default: The interface address of one of the local interfaces.

 

IPv6 OSPF Global Settings

set ipv6 ospf3 
   default-ase-cost <1-16777215>
   default-ase-type <1 | 2>
   spf-delay <1-60> | default
   spf-holdtime <1-60> | default

Note: The graceful-restart-helper parameter is not supported.


Parameter

Description

default-ase-cost <1-16777215>

When routes from other protocols are redistributed into OSPF as ASEs, they are assigned this configured cost unless a cost has been specified for the individual route.

  • Default: 1
default-ase-type <1|2>

When routes from other protocols are redistributed into OSPF as ASEs, they are assigned this route type, unless a type has been specified for the individual route. ASEs can either be type 1 or type 2.

  • Type 1: Used for routes imported into OSPF which are from IGPs whose metrics are directly comparable to OSPF metrics. When a routing decision is being made, OSPF adds the internal cost to the AS border router to the external metric.
  • Type 2: Used for routes whose metrics are not comparable to OSPF internal metrics. In this case, only the external OSPF cost is used. In the event of ties, the least cost to an AS border router is used.
  • Default: 1.
spf-delay <1-60>

The time (in seconds) the system waits before recalculating the OSPF routing table after a change in the topology.

  • Default: 2.
spf-holdtime <1-60>

The minimum time (in seconds) between recalculations of the OSPF routing table.

  • Default:5.

IPv6 OSPF Areas

Use the following commands to configure OSPFv3 (IPv6 OSPF) areas, including the backbone and stub areas.

NSSA is not available for OSPFv3

set ipv6 ospf3 area ospf_area <on | off>
set ipv6 ospf3 area ospf_area
   stub <on | off>
   stub default-cost <1-677215>
   stub summary <on | off>
   range VALUE <on | off>
   range VALUE restrict VALUE
   stub-network VALUE <on | off>
   stub-network VALUE stub-network-cost <1-65535>

Parameter

Description

ospf_area <on | off>

For the name of the area, choose an IPv4 address (preferred) or an integer.

stub <on | off>

A Stub Area is an area in which there are no Autonomous System External (ASE) routes. ASE routes are routes to destinations external to the AS.

Note: The backbone area cannot be a stub area. NSSA Areas are not supported.

Default: Off

stub default-cost <1-677215>

The cost for the default route to the stub area.

Default: No default.

stub summary <on | off>

An area in which there are no ASE routes or summary routes.

Default: Off

range VALUE <off | on>

An area can be configured with any number of address ranges. Address ranges are used to reduce the number of routing entries that a given area will emit into the backbone (and hence all) areas.

An address range is defined by a prefix and a mask length. If a given prefix aggregates a number of more specific prefixes within an area, then an address range can be configured and will be the only prefix advertised into the backbone. Be careful when configuring an address range that covers parts of a prefix that are not contained within the area.

range VALUE restrict <on | off>

Prevent an address from being advertised into the backbone.

stub-network VALUE <on | off>

OSPF can advertise reachability to prefixes that are not running OSPF by configuring a stub network. The advertised prefix shows as an OSPF internal route and can be filtered at area borders with the OSPF area ranges. The prefix must be directly reachable on the router where the stub network is configured (that is, one of the routers interface addresses must fall in the prefix) in order to be included in the router-LSA. Stub hosts are configured by specifying a mask length of 128.

An address range is defined by a prefix and a mask length. A prefix and mask can be advertised. That can be activated by the local address of a point-to-point interface. To advertise reachability to such an address, enter an IP address for the prefix and a non-zero cost for the prefix.

 

stub-network VALUE stub-network-cost <1-65535>

The cost associated with the stub network. The higher the cost, the less preferred the prefix as an OSPF route.

Default: 1

IPv6 OSPF Interfaces

Note - The hello interval and dead interval must be the same for all routers on the link. Authentication is not supported for IPv6 OSPF interfaces.

set ipv6 ospf3 interface <interface_name>
   area <ospf_area> <on|off> 
   cost <1-65535>
   dead-interval <1-65535>
   hello-interval <1-65535>
   passive <on | off>
   priority <0-255>
   retransmit-interval <1-65535>
   virtual-address <on|off>

Parameter

Description

interface <interface_name>

The interfaces for OSPF configuration. An interface must have an area associated with it in order to become active in OSPF.

area <ospf_area> <off | on>

The OSPF area to which the interface belongs. An OSPF area defines a group of routers running OSPF that have the complete topology information of the area. OSPF areas use an area border router to exchange information about routes. Routes for a given area are summarized into the backbone area for distribution into other non-backbone areas. An area border router (ABR) is one that has at least two interfaces in at least two different areas. One of those areas must be the backbone or the router must have a virtual link configured. OSPF forces a hub and spoke topology of areas, with the backbone area always being the hub.

For the name of the area, choose an IPv4 address (preferred) or an integer.

  • Range: All areas currently configured.
  • Default: None.

cost <1-65535>

The weight of a given path in a route. The higher the cost, the less preferred the link. You may explicitly override this setting in route redistribution. To use one interface over another for routing paths, give one a higher cost.

  • Default: 1.

dead-interval <1-65535>

The number of seconds after a router stops receiving hello packets that it declares the neighbor is down. Typically, the value of this field should be four times the size of the hello interval.

For a given link, this field must be the same on all routers or adjacencies will not be created. The value must not be zero.

  • Default: For broadcast interfaces, the default is 40 seconds. For point-to-point interfaces, the default is 120 seconds.

hello-interval <1-65535>

The time, in seconds, between hello packets that the router sends on the interface. For a given link, this must be the same on all routers or adjacencies will not be created.

  • Default: For broadcast interfaces, the default is 10 seconds. For point-to-point interfaces, the default is 30 seconds.
passive <on | off>

An interface in passive mode does not send hello packets out of the given interface. This means no adjacencies are formed on the link. The purpose of passive mode is to make it possible for the network associated with the interface to be included in the intra-area route calculation. In non passive mode, the network is redistributed into OSPF and is an ASE. In passive mode, all interface configuration information is ignored, with the exception of the associated area and the cost.

  • Default: Off

priority <0-255>

The priority for becoming the designated router (DR) on this link. When two routers attached to a network both attempt to become a designated router, the one with the highest priority wins. If there is currently an elected DR on the link, it will remain the DR regardless of the configured priority. This feature prevents the DR from changing too often. This field is only relevant on a shared-media interface (Ethernet), as a DR is not elected on point-to-point type interfaces. A router with priority 0 is not eligible to become the designated router.

  • Default: 1.

retransmit-interval <1-65535>

The number of seconds between LSA retransmissions, for adjacencies belonging to this interface. Also used when retransmitting Database Description and Link State Request Packets. This should be well over the expected round-trip delay between any two routers on the attached network. The setting of this value should be conservative or needless retransmissions will result.

  • Default: 5.

virtual-address <on | off>

Directs OSPFv3 to use the VRRPv3 virtual link-local address as the source of its control packets. When enabled, OSPFv3 runs on the interface only while the local router is the master with respect to a VRRPv3 state machine on the interface.

Note: The VRRPv3 state machine must back-up an IPv6 link-local address that is not auto-configured on the interface.

  • Default: Off.

IPv6 OSPF Configuration Examples


Note - If OSPF is used without the virtual-address option in a VRRP cluster, you must make sure that each router selects a different router-id. To see and correct the router-id:

show router-id
set router-id <ipv4-address>

Example of OSPFv3 configuration:

set ipv6 ospf3 interface eth1 area backbone on

To change default OSPFv3 parameters:

set ipv6 ospf3 interface eth1 cost 2
set ipv6 ospf3 interface eth1 priority 2
set ipv6 ospf3 interface eth1 hello-interval 20
set ipv6 ospf3 interface eth1 dead-interval 80
set ipv6 ospf3 interface eth1 retransmit-interval 20

To configure OSPFv3 to run on the VRRP Virtual Address:

set ipv6 ospf3 interface eth1 virtual-address on

Monitoring IPv6 OSPFv3

You can monitor IPv6 OSPF in the Gaia Portal and in the Gaia Clish.

Monitoring IPv6 OSPF - Gaia Portal

  1. From the Navigation Tree, go to the Advanced Routing > IPv6 OSPF page.
  2. Click the Monitoring tab.

Monitoring IPv6 OSPF - Gaia Clish

To monitor and troubleshoot the IPv6 OSPFv3, run this command:

show ipv6 ospf3
border-routers
database
area {backbone | <area_id>}
areas [detailed]
checksum
database-summary
detailed
external-lsa [detailed]
inter-area-prefix-lsa [detailed]
inter-area-router-lsa [detailed]
intra-area-prefix-lsa [detailed]
link-lsa [detailed]
network-lsa [detailed]
router-lsa [detailed]
type {1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9}
errors {dd | hello | ip | lsack | lsr | lsu | protocol}
events
interface <interface_name> [detailed | stats]
interfaces [detailed | stats]
neighbor <neighbor_IP> [detailed]
neighbors [detailed]
packets
routemap
summary

Where:

Parameter

Description

border-routers

Shows the state of each area border router:

  • Router ID
  • OSPF area
  • Associated route cost

database

area {backbone | <area_id>}

areas [detailed]

checksum

database-summary

detailed

external-lsa [detailed]

inter-area-prefix-lsa [detailed]

inter-area-router-lsa [detailed]

intra-area-prefix-lsa [detailed]

link-lsa [detailed]

network-lsa [detailed]

router-lsa [detailed]

type {1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9}

Show the OSPF database information:

  • area {backbone | <area_id>} - Router-link state, network-link state, AS-border-router-link state, AS- external-link state, and summary-link state statistics for the specified OSPF area; for each interface in this OSPF area, shows the checksum, sequence number, and link count
  • areas [detailed] - Router-link state, network-link state, AS-border-router-link state, AS- external-link state, and summary-link state statistics for each OSPF area; for each OSPF interface, shows the checksum, sequence number, and link count
  • checksum - Checksum sum for each OSPF interface
  • database-summary - Summary of all types of LSAs
  • detailed - Detailed statistics on all types of LSAs
  • external-lsa [detailed] - Type 5 (AS-external) LSA statistics for each OSPF area
  • inter-area-prefix-lsa [detailed] - Type 3 (Summary) LSA statistics for each OSPF area (OSPFv3 only)
  • inter-area-router-lsa [detailed] - Type 4 (ASBR) LSA statistics for each OSPF area (OSPFv3 only)
  • intra-area-prefix-lsa [detailed] - Type 9 (Intra-Area Prefix) LSA statistics for each OSPF area (OSPFv3 only)
  • link-lsa [detailed] - Type 8 (Link) LSA statistics for each OSPF area (OSPFv3 only)
  • network-lsa [detailed] - Type 2 (Network) LSA statistics for each OSPF area
  • router-lsa [detailed] - Type 1 (Router) LSA statistics for each OSPF area
  • nssa-external-lsa [detailed] - Type 7 (NSSA) LSA statistics for each OSPF area (OSPFv2 only)
  • opaque-lsa [detailed] - Opaque LSA statistics for each OSPF area (OSPFv2 only)
  • summary-lsa [detailed] - Summary of all LSAs for each OSPF area (OSPFv2 only)
  • type {1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9} - LSA statistics for each type of LSA:
    • 1 - Router LSA
    • 2 - Network LSA
    • 3 - Summary LSA in OSPFv2, Inter-Area Prefix LSA in OSPFv3
    • 4 - Summary ASBR LSA in OSPFv2, Inter-Area Router LSA in OSPFv3
    • 5 - External LSA in OSPFv2, AS-External LSA in OSPFv3
    • 7 - NSSA LSA in OSPFv2 only, not supported in OSPFv3
    • 8 - Link LSA in OSPFv3 only, not supported in OSPFv2
    • 9 - Intra-Area Prefix LSA in OSPFv3 only, not supported in OSPFv2

errors {dd | hello | ip | lsack | lsr | lsu | protocol}

Number of error messages sent, per type:

  • dd - Database description error messages
  • hello - Hello error messages
  • ip - IP error messages
  • lsack - Link-state acknowledgment error messages
  • lsr - Link-state request error messages
  • lsu - Link-state update error messages
  • protocol - Protocol error messages

events

Number of these types of events:

  • Interface down
  • Interface up
  • Virtual interface down
  • Virtual interface up
  • Designated Router (DR) elections
  • Router ID (RID) changes
  • Area border router (ABR) changes
  • AS border router (ASBR) changes
  • RFC1583 changes
  • LSA self-advertisement messages

interface <interface_name> [detailed | stats]

Shows OSPF information for the specified interface:

  • <interface_name> - interface name
    • IP address
    • Area ID
    • State
    • Number of logged errors (NC)
    • DR Interface IP address
    • BDR Interface IP address
  • detailed
    • IP Address
    • Area
    • Router ID
    • Network type
    • Cost
    • Authentication type
    • Error count
    • Event count
    • Transmit delay
    • State
    • Priority
    • Designated Router (DR) ID and interface IP address
    • Backup Designated Router (BDR) ID and interface IP address
    • Hello, Dead, Wait, and Retransmit timers (in seconds)
    • Next Hello timer
    • Neighbor count
    • Count of lost 2-way connections with neighbors
  • stats
    • Total Errors
    • Hello Interval Mismatch
    • External Option Error
    • Delayed Ack Count
    • Dead Interval Mismatch
    • Lost Neighbor Count
    • Authentication Errors
    • Duplicate Router ID
    • Neighbor Errors
    • Newer Self LSA Count
    • Neighbor Count

interfaces [detailed | stats]

Shows OSPF information for all interfaces:

  • Without command options
    • IP address
    • Area ID
    • State
    • Number of logged errors (NC)
    • DR Interface IP address
    • BDR Interface IP address
  • detailed
    • IP Address
    • Area
    • Router ID
    • Network type
    • Cost
    • Authentication type
    • Error count
    • Event count
    • Transmit delay
    • State
    • Priority
    • Designated Router (DR) ID and interface IP address
    • Backup Designated Router (BDR) ID and interface IP address
    • Hello, Dead, Wait, and Retransmit timers (in seconds)
    • Next Hello timer
    • Neighbor count
    • Count of lost 2-way connections with neighbors
  • stats -
    • Total Errors
    • Hello Interval Mismatch
    • External Option Error
    • Delayed Ack Count
    • Dead Interval Mismatch
    • Lost Neighbor Count
    • Authentication Errors
    • Duplicate Router ID
    • Neighbor Errors
    • Newer Self LSA Count
    • Neighbor Count

neighbor <neighbor_IP> [detailed]

Shows OSPF information for the specified OSPF neighbor:

  • Priority
  • State
  • Number of logged errors

neighbors [detailed]

Shows OSPF information for each OSPF neighbor:

  • IP address
  • Priority
  • State
  • Number of logged errors

packets

Shows the number of received (Rx) and transmitted (Tx) OSPF packets:

  • Hello Rx
  • Hello Tx
  • Link State Update Rx
  • Link State Update Tx
  • Link State Ack Rx
  • Link State Ack Tx
  • Link State Request Rx
  • Link State Request Tx

routemap

Shows OSPF Import Policy and Export Policy.

summary

Shows detailed OSPF configuration.