Comandos ospf

32OSPF Commands

OverviewThis chapter describes Open Shortest Path First (OSPF) router commands.

OSPF is a shortest path first or link‐state protocol. The Matrix X Router supports OSPF Version 2.0, as defined in RFC 2328. OSPF is an interior gateway protocol that distributes routing information between routers in a single autonomous system (AS). OSPF chooses the least‐cost path as the best path. OSPF is suitable for complex networks with a large number of routers because it provides equal‐cost multi‐path routing where packets to a single destination can be sent by more than one interface simultaneously.

In a link‐state protocol, each router maintains a database that describes the entire AS topology, which it builds out of the collected link state advertisements of all routers. Each participating router distributes its local state (that is, the router’s usable interfaces and reachable neighbors) throughout the AS by flooding. Each multi‐access network that has at least two attached routers has a designated router and a backup designated router. The designated router floods a link state advertisement for the multi‐access network and has other special responsibilities. The designated router concept reduces the number of adjacencies required on a multi‐access network.

For information about... Refer to page...

Global Configuration Mode OSPF Command 32-2

Global Commands 32-2

Area Commands 32-32

Default Commands 32-51

Interface Commands 32-57

Querying Commands 32-73

Matrix X Router Command Line Interface Reference Guide 32-1

Global Configuration Mode OSPF Command

Global Configuration Mode OSPF CommandThere is one global configuration mode OSPF command, router ospf.

router ospfThis command acquires configuration mode for an instance in OSPF.

Syntaxrouter ospf instance_id

no router ospf instance_id

Parameters

ModeGlobal Router Configuration.

UsageUse the router ospf command to enter OSPF Router Configuration mode for an OSPF instance. Once in OSPF Router Configuration mode, begin adding or reconfiguring an OSPF instance.

ExampleThis example shows how to acquire OSPF Router Configuration mode for OSPF instance 1 from the switch mode.

matrix-x(switch-su)->routermatrix-x(router-exec)# configmatrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)#

Global CommandsThe global OSPF commands are listed below.

instance_id An integer from 1 to 4294967294 identifying the OSPF instance.

Up to 4 concurrent OSPF instances can be configured.


advertise-subnet 32-3

authentication 32-5

compatible rfc1583 32-7

dead-interval 32-8

distance 32-9

enable 32-10

32-2 OSPF Commands

Global Commands

advertise-subnetThis command determines whether OSPF will, when advertising point‐to‐point interfaces, advertise the network number and netmask instead of a host route to the remote IP network.

Syntaxadvertise-subnet

no advertise-subnet

ParametersNone.

DefaultsDisabled.

ModeOSPF Router Configuration.

hello-interval 32-11

igp-shortcut 32-12

inherit-metric 32-13

multicast-rib 32-14

network 32-15

nssa-inherit-metric 32-16

nssa-stability-interval 32-17

poll-interval 32-18

priority 32-19

redistribute 32-20

redistribute-nssa 32-22

require-vbit 32-23

retransmit-interval 32-24

router id 32-25

timers spf 32-26

trace file 32-27

trace flag 32-29

transmit-delay 32-31



Global Commands

UsageThis command determines whether OSPF will, when advertising point‐to‐point interfaces, advertise the network number and netmask instead of a host route to the remote IP network. Because the netmask is sometimes set improperly on point‐to‐point interfaces, this option is disabled by default. This command can be overridden at the area and interface levels.

ExampleThe following example turns the global advertise‐subnet on, then turns it off for area 1.2.3.4:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# advertise-subnetmatrix-x(config-router-ospf)# no area 1.2.3.4 advertise-subnet

Related Commandsarea advertise-subnet

ip ospf advertise-subnet

32-4 OSPF Commands

Global Commands

authenticationThis command specifies the type of OSPF authentication employed.

Syntaxauthentication {simple key | md5 id_number md5_key [start-generate date_time] [stop-generate date_time] [start-accept date_time] [stop-accept date_time]}

no authentication {simple key | md5 id_number}

Parameters

DefaultsThe default is for no authentication to be explicitly configured.


UsageAuthentication can help to guarantee that routing information is imported only from trusted routers. A variety of authentication schemes can be used, but a single scheme must be configured for each network. The use of different schemes enables some interfaces to use much stricter authentication than others. The two authentication schemes available are simple and MD5.

Use the authentication command to specify the type of global authentication and key values used in OSPF. Use the no form of this command to remove authentication for the area. Authentication is used by OSPF to generate and verify the authentication field in the OSPF header. The global authentication is the default and can be overridden at the area command and interface levels.

simple key Specifies simple (clear password) authentication. The value for key is specified as a one‐ to eight‐character string.

md5 id_number md5_key Specifies the authentication used for specifying MD5 cryptographic authentication.

The value for id_number is an integer ranging from 1 to 255.

The value for md5_key is a character string, ranging from 1 to 16 characters.

start‐generate date_time

stop‐generate date_time

(Optional) Specifies the start and stop times for generating MD5 authentication. The date_time values must be in the format YYYY‐MM‐DD.HH.MM.

Both parameters are optional and you may enter them in any order when specifying multiple commands.

start‐accept date_time

stop‐accept date_time

(Optional) Specifies the start and stop times for accepting MD5 authentication. The date_time values must be in the format YYYY‐MM‐DD.HH.MM.

Both parameters are optional and you may enter them in any order when specifying multiple commands.


Global Commands

When you want to keep certain routers from exchanging OSPF packets, use the simple form of authentication. The interfaces that the packets are to be sent on still need to be trusted, because the key will be placed in the packets and can be seen by anyone with access to the network.

When you do not trust other users of your network, use MD5 authentication. The system works by using shared secret keys. Because the keys are used to sign the packets with an MD5 checksum, they cannot be forged or tampered with. Because the keys are not included in the packet, snooping the key is not possible. Users of the network can still snoop the contents of packets, however, because the packets are not encrypted.

The Matrix X MD5 authentication is compliant with RFC 2328 which uses the MD5 algorithm and an authentication key of up to 16 characters. RFC 2328 allows multiple MD5 keys per interface. Each key has two associated time ranges.

In order to turn off authentication, you must include the authentication type in the no form of the command. For example, if MD5 authentication was configured, then simply specifying no authentication will not work. In addition, you must specify the simple key when turning off simple authentication, and you must specify the MD5 id_number when turning off MD5 authentication.

ExamplesThe following example configures simple authentication in OSPF instance 1.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# authentication simple abc

The following example configures MD5 authentication for OSPF instance 2. The ID for this MD5 configuration is 1, and the key is configured as bar.

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# authentication md5 1 bar

The following example turns off the MD5 authentication that was configured in the previous example. Note that specifying the MD5 key is not required, but specifying the MD5 ID is.

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# no authentication md5 1

The following example configures md5 authentication for OSPF instance 3. MD5 authentication is configured with a start‐generate time set to November 2, 2004 at 9:30 p.m., a stop‐generate time set to November 2, 2004 at 9:45 p.m., a start‐accept time set to December 2, 2004 at 9 p.m. and a stop‐accept time set to December 31, 2004 at 2 p.m.:

matrix-x(router-config)# router ospf 3matrix-x(config-router-ospf)# authentication md5 2 md5 start-generate 2004-11-02.21.30 stop-generate 2004-11-02.21.45 start-accept 2004-12-02.21.00 stop-accept 2004-12-31.22.00

Related Commandsarea authentication

ip ospf authentication

32-6 OSPF Commands

Global Commands

compatible rfc1583This command specifies this Matrix X Router to run in RFC 1583 mode instead of RFC 2328 mode.

Syntaxcompatible rfc1583

no compatible rfc1583

ParametersNone.

DefaultsEnabled.


UsageDo not specify this command if all the routers using an OSPF implementation in your domain are based on RFC 2328 or later. This option should be specified the same way on all routers in the domain. If any router does not have this option, you should always enable this. When disabled, the preference rules for best route election are changed to eliminate certain kinds of possible routing loops.

Use the no form of this command removes the requirement to run in RFC 1583 mode and reverts to RFC 2328.

ExampleThe following example disables RFC 1583 mode for instance 1 of OSPF:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# no compatible rfc1583


Global Commands

dead-intervalThis command specifies the interval that can elapse without receiving a router’s hello packets before the router’s neighbors will declare it down.

Syntaxdead-interval time-seconds

no dead-interval time-seconds

Parameters

Defaults40 seconds.


UsageUse this command to specify the interval that can elapse without receiving a router’s hello packets before the router’s neighbors will declare it down. This value can be overridden at the area and interface levels. Generally, this value should equal four times the HELLO interval. Do not set this value to be less than the HELLO interval or convergence will fail.

Use the no form of this command removes the configured value and returns to its default value of 40 seconds. Specifying a value for time‐seconds in the no form has no effect on configuration.

ExampleThe following example configures a global dead‐interval value of 30. This value is then overridden in area 1.2.3.4 to be 25.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# dead-interval 30matrix-x(config-router-ospf)# area 1.2.3.4 dead-interval 25

Related Commandsarea dead-interval

ip ospf dead-interval

time‐seconds Interval ranging from 1 to 65535 seconds.

32-8 OSPF Commands

Global Commands

distanceThis command specifies how active routes that are learned from OSPF internal reachability will be selected, compared to other protocols.

Syntaxdistance int_value

no distance [int_value]

Parameters

Defaults10.


UsageUse the distance command to specify how active routes that are learned from the OSPF internal reachability (compared to other protocols) will be selected. When a route has been learned from more than one protocol, the active route will be selected from the protocol with the lowest distance. Each protocol has a default distance in this selection.

Use the negative form of this command, no distance, to remove the configured value and return it to its default value of 10.

ExampleThe following example configures the default distance for internal routes to be 100.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# distance ospf 100

int_value The preference for internal routes, ranging from 1 and 255 inclusive.


Global Commands

enableThis command enables an OSPF instance.

Syntaxenable

no enable


DefaultsEnabled.

UsageThe no form of this command disables the instance. If an enabled instance is disabled, then it is stopped, and all running state is deleted but all configuration state is preserved. If a disabled instance is enabled, it will start running again with its preserved configuration state.

ExampleThe following example disables OSPF instance 3:

matrix-x(router-config)# router ospf 3matrix-x(config-router-ospf)# no enable

32-10 OSPF Commands

Global Commands

hello-intervalThis command specifies the interval between hello packets that a peer router sends on an interface.

Syntaxhello-interval time-seconds

no hello-interval [time-seconds]

Parameters

Defaults10 seconds.


UsageUse this command to specify the interval between hello packets that a peer router sends on an interface. Although specified here at the global level, it can be overridden in the area and interface levels.

Use the no form of this command to remove the configured value and return it to the default. Specifying a time‐seconds value in the no form has no effect on the configuration.

ExampleThe following example configures a global hello interval of 15 seconds which is then overridden in the area statement where it is set to 5 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# hello-interval 15matrix-x(config-router-ospf)# area 1.2.3.4 hello-interval 5

Related Commandsarea hello-interval

ip ospf hello-interval

time-seconds The interval between hello packet transmissions a peer router sends on an interface, ranging from 1 to 65535 seconds.


Global Commands

igp-shortcutThis command enables the IGP shortcut feature for OSPF.

Syntaxigp-shortcut

no igp-shortcut


DefaultsDisabled.

UsageThis command enables the IGP shortcut feature for OSPF. When configured, OSPF will consider MPLS tunnels as uni‐directional, directly connected, point‐to‐point links.

The no form of this command disables this feature.

ExamplesThe following command enables the IGP Shortcut feature for OSPF instance 1:

matrix-x(router-config)# router ospf 1matrix-x(router-ospf)# igp-shortcut

The following command disables the IGP Shortcut feature for OSPF instance 1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# no igp-shortcut

32-12 OSPF Commands

Global Commands

inherit-metricThis command configures an OSPF ASE (Autonomous System External) route to inherit the metric of the external route when no metric is specified on the export policy.

Syntaxinherit-metric

no inherit-metric

ParametersNone.

DefaultsDisabled.


UsageUse this command to configure an OSPF ASE route to inherit the metric of the external route when no metric is specified on the export policy. This feature maintains compatibility with all current export functions. A metric specified on the export policy takes precedence.

ExampleThe following example configures ASE routes exported into OSPF to inherit the metric of the external route:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# inherit-metric

Note: The metric specified in the defaults section (default-metric) is used if this command is not specified.


Global Commands

multicast-ribThis command specifies the Routing Information Base (RIB) in which OSPF internal routes are installed.

Syntaxmulticast-rib

no multicast-rib

ParametersNone.

DefaultsDisabled.


UsageUse this command to specify the RIB in which OSPF internal routes are installed. The unicast RIB is required and is the default. In code bases supporting extended RIBs, OSPF routes can be installed in the multicast RIB.

This command has no effect on self‐originated ASE (Autonomous System External) or NSSA routes because they are exported from another protocol.

Use the no form of this command to change the parameter to its default.

ExampleThe following example configures OSPF routes to be installed in the unicast and multicast RIBs:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# multicast-rib

32-14 OSPF Commands

Global Commands

networkThis command defines the interfaces on which OSPF will run and the area ID for those interfaces.

Syntaxnetwork ip_address wildcard-mask area area_id

no network ip_address wildcard-mask area area_id

Parameters

DefaultsThis command is not explicitly configured by default.


UsageUse the network area command to specify interfaces on which OSPF runs and to define the area ID for those interfaces. Use the negative form of this command, no network area, to disable OSPF routing for any specified interfaces.

ExamplesThe following example defines network 192.168.10.5 0.0.0.255 in area 1.2.3.4:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# network 192.168.10.5 0.0.0.255 area 1.2.3.4

The following example disables OSPF routing on interface 102.168.10.10 in area 1.2.3.4:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# no network 192.168.10.10 0.0.0.0 area 1.2.3.4

ip_address A valid IP address.

wildcard‐mask IP‐address‐type mask that includes don’t care bits.

area area_id An ID for an area specified as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone. If you want to associate areas with IP subnets, you can specify a subnet address for this value.


Global Commands

nssa-inherit-metricThis command allows an OSPF NSSA route to inherit the metric of the external route when no metric is specified on the export policy. This feature maintains compatibility with all current export functions. A metric specified on the export policy will take precedence.

Syntaxnssa-inherit-metric

no nssa-inherit-metric

ParametersNone.

DefaultsDisabled.


ExampleThe following example sets NSSA routes exported into OSPF to inherit the metric of the external route:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# nssa-inherit-metric

32-16 OSPF Commands

Global Commands

nssa-stability-intervalThis command sets the interval that an NSSA translator will continue to translate after losing the translator election.

Syntaxnssa-stability-interval time-seconds

no nssa-stability-interval [time-seconds]

Parameters

Defaults40 seconds.

ModeGlobal Configuration.

UsageAn NSSA ABR can translate Type 7 LSAs into Type 5 LSAs. A translator election is run to determine which one ABR for a given NSSA will translate.

When an ABR was a translator and loses this election, it will cease translating after the specified seconds value. This allows newly translated Type 5 LSAs from the new translator to be flooded throughout the domain before the currently translated Type 5 LSAs from this translator are flushed and Type 5 LSAs resulting from direct translation are allowed to age out.

ExampleThe following example sets the nssa‐stability‐interval to 10 seconds:

matrix-x(router-config)# nssa-stability-interval 10

time-seconds A period ranging from 1 to 65535 seconds.


Global Commands

poll-intervalThis command specifies the interval between OSPF packets that the router sends before adjacency is established with a neighbor.

Syntaxpoll-interval time-seconds

no poll-interval [time-seconds]

Parameters

Defaults120 seconds.


UsageUse this command to reduce network overhead in cases where a router may have a neighbor on a given interface at the expense of initial convergence time. The value configured here at the global level can be overridden at the area and interface levels.

Use the no form of this command to reset the specified value to the default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures a global poll interval of 100 seconds. This value is overridden in interface ge.4.2, where it is configured to be 110 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# poll-interval 100matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.4.2matrix-x(config-router-if-ge.4.2)# ip ospf poll-interval 110

Related Commandsarea poll-interval

ip ospf poll-interval


32-18 OSPF Commands

Global Commands

priorityThis command specifies the priority for becoming the Designated Router (DR).

Syntaxpriority level

no priority [level]

Parameters

Defaults1.


UsageUse this command to specify the priority for becoming the DR. When more than one router attached to a network tries to become the DR, the one with the highest priority wins. If competing routes have the same priority, the one with the highest router ID becomes the DR. The router placing second in the election becomes the backup DR. A router with a router priority set to 0 is ineligible to become the DR.

The value specified here at the global level can be overridden at the area and interface levels (area priority and ip ospf priority commands).

Use the no form of this command to reset the specified value to the default. Specifying a value for level in the no form has no effect on the configuration.

ExampleThe following example sets a global priority of 10 which is then overridden in area 1.2.3.4, where it is set to 15:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# priority 10matrix-x(config-router-ospf))# area 1.2.3.4 priority 15

Related Commandsarea priority

ip ospf priority

level A priority number, ranging from 0 to 255, for becoming a DR.


Global Commands

redistributeThis command specifies routes to import into OSPF.

Syntaxredistribute protocol [route-map name] {0-9}

no redistribute protocol [route-map name]

Parameters

DefaultsThe default is to redistribute OSPF and the direct routes associated with the interfaces on which OSPF is running.


UsageUse this command to specify routes to export to OSPF. This command causes routes from the specified protocol to be considered for redistribution into the current protocol. Additionally, if a route map is specified, then routes from the specified protocol matching the named route map will be considered for redistribution into the current protocol.

If the referenced route map has not yet been configured, then an empty route map is created with the specified name.

protocol Protocol name for routes you want to redistribute to the current protocol being configured. Valid choices are: aggregate, bgp, direct, kernel, isis, ospf, ospf‐ase, rip, and static.

route‐map name (Optional) Name of a route map to apply to these routes.

{0-9} Although this command can be given multiple times, it can only be given once to each of the nine configurable protocols. For example, if a redistribute command is given for a protocol and route map, and then given again for the same protocol with a different route map, the second configuration overrides the first.

Note: This is an implicit default and is erased with the first redistribute configuration.

Note: Configuring away from the default removes the implicitly configured default. To export those routes you must go back and specify to redistribute OSPF and direct routes after the first redistribute configuration.

32-20 OSPF Commands

Global Commands

ExamplesIn the following example OSPF instance 2 is configured to redistribute all BGP and RIP routes:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# redistribute bgpx-series(config-router-ospf)# redistribute rip

The following example configures a community set, set1, that permits AS:num 101:102. It then configures an extended community set extset1, that permits Route Target AS:num 201:202.

matrix-x(router-config)# ip community-set set1 permit 101:102matrix-x(router-config)# ip extcommunity-set ext-set1 permit rt 201:202

The two are then added to a community list, called commlist1:

matrix-x(router-config)# ip community-list commlist1 permit set1matrix-x(router-config)# ip community-list commlist1 permit ext-set1

The community list is then applied to a route map called matchcommlist1. If the route map matches BGP Community list commlist1, then the metric for routes is set to 20:

matrix-x(router-config)# route-map match-commlist1matrix-x(config-route-map)# match community commlist1matrix-x(config-route-map)# set metric 20

Finally, route map match‐commlist1 is applied to BGP routes and exported into instance 1 of OSPF:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# redistribute bgp route-map match- commlist1

In the following example, route map abc is configured with the following match criteria:

If a route matches interface ge.1.1 and a pre‐configured BGP Community labeled bgpcomm1, then communities specified in community com‐set‐1 will be added to the route, communities specified in community labeled com‐set‐2 will be deleted from the route, and the route metric set to 50.

matrix-x(router-config)# route-map abcmatrix-x(config-route-map)# match interface ge.1.1matrix-x(config-route-map)# match community-set bgpcomm1matrix-x(config-route-map)# set community-set com-set-1 additivematrix-x(config-route-map)# set community-set com-set-2 deletematrix-x(config-route-map)# set metric 50

This route map is then applied to static routes and exported into OSPF instance 2:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# redistribute static route-map abc


Global Commands

redistribute-nssaThis command specifies routes to export to OSPF NSSA in an OSPF instance.

Syntaxredistribute-nssa protocol [route-map name] {0-9}

no redistribute-nssa protocol [route-map name]

Parameters

DefaultsOSPF does not redistribute any routes into NSSA.


UsageThis command specifies routes to export to OSPF NSSA in an OSPF instance. It causes routes from the specified protocol to be considered for redistribution into OSPF‐NSSA. Also, if a route map is specified, then routes from the specified protocol matching the named route map will be considered for redistribution into OSPF‐NSSA.

If the referenced route map has not yet been configured, then an empty route map is created with the specified name.

ExamplesIn the following example, route map abc is configured to match all IPv4 prefixes (configured in prefix list pl1), to set the exported metric to 1, and to set the NSSA Propagate (P) bit:

matrix-x(router-config)# ip prefix-list pl1 seq 1 permit 0.0.0.0/0 le 32matrix-x(router-config)# route-map abcmatrix-x(config-route-map)# match ip address prefix-list pl1matrix-x(config-route-map)# set metric 1matrix-x(config-route-map)# set propagate

This route map is then applied to static routes and exported into OSPF NSSA:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# redistribute-nssa static route-map abc

protocol Protocol name for routes you want to redistribute to the current protocol being configured. Valid choices are: aggregate, bgp, direct, isis, kernel, ospf, ospf‐ase, rip, and static.

route‐map name Name of a route map to apply to these routes.

{0‐9} Although this command can be given multiple times, it can only be given once to each of the nine configurable protocols. For example, if a redistribute command is given for a protocol and route map, and then given again for the same protocol with a different route map, the second configuration overrides the first.

32-22 OSPF Commands

Global Commands

require-vbitThis command instructs the spf code to require that the vbit be set in the router LSAs of routers that are the end points of virtual links.

Syntaxrequire-vbit

no require-vbit

ParametersNone.

DefaultsDisabled.


UsageWhen this command is not specified, the vbit can be clear, and the virtual link will still be considered. This command is a work around for issues in some OSPF implementations.

ExampleThe following example turns require‐vbit on:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# require-vbit


Global Commands

retransmit-intervalThis command sets the interval between Link State Advertisement (LSA) retransmissions for adjacencies.

Syntaxretransmit-interval time-seconds

no retransmit-interval [time-seconds]

Parameters

Defaults5 seconds.


UsageThis command sets the interval between LSA retransmissions for adjacencies. If a Link State Protocol (LSP) is not acknowledged within the interval specified with this command, it is re‐sent.

This command is specified at the global level and can be overridden in the area and interface levels with the area retransmit‐interval and ip ospf retransmit‐interval commands.

The no form of this command resets the specified value to the default. Specifying a value fortime‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures the global retransmit interval to be 10 seconds. This value is then overridden in area 1.2.3.4, where it is configured to be 15 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# retransmit-interval 10matrix-x(config-router-ospf)# area 1.2.3.4 retransmit-interval 15

Related Commandsarea retransmit-interval

ip ospf retransmit-interval


32-24 OSPF Commands

Global Commands

router idThis command sets the OSPF 32‐bit router ID for the specified instance. The Router ID set by this command is the lowest loopback interface IP address on the Matris X router. If no loopback interfaces are configured, then the lowest interface IP address is chosen. Finally, if no interface IP addresses are configured, the IP address 127.0.0.1 is chosen. Once a Router ID has been selected, it will change only as the result of entering the no router id command or a system reboot.

Syntaxrouter id rid_value

no router id rid_value

Parameters

DefaultsThe globally specified Router ID. If a globally specified Router ID does not exist, then the highest IP address will be used.


UsageIf the Router ID is not specified, then the instance uses the global default router ID.

The no form of this command resets the configured router ID to its default value specified by the globally defined Router ID.

ExampleThe following example configures the OSPF router ID to be 4.3.2.1.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# router id 4.3.2.1

rid_value A 32‐bit address in dotted‐quad notation.


Global Commands

timers spfThis command specifies the minimum period between when OSPF receives a topology change and when it starts the Sender Policy Framework (SPF) computation.

Syntaxtimers spf time-seconds

no timers spf [time-seconds]

Parameters

Defaults5 seconds.


UsageThe no form of this command resets the specified value to its default.

ExampleThe following example configures the SPF timer interval to 15 seconds:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# timers spf 15

time-seconds The minimum interval in seconds between SPF calculations, ranging from 1 to 65535.

32-26 OSPF Commands

Global Commands

trace fileThis command specifies the file to receive tracing information, the size of the file, whether to overwrite existing files, and the maximum number of files allowed.

Syntaxtrace file file_name [max-size file_size[M | m | K | k]] [max-files num_files] [no-timestamp] [noverwrite]

no trace file file_name [max-size file_size[M | m | K | k]] [max-files num_files] [no-timestamp] [overwrite]

Parameters

Defaults• Disabled.

• max-size file_size: Unlimited. The size of a trace file is limited by the file system on which the trace file resides.

• max-files num_files: 4,294,967,295 files.

• no-timestamp: Prepend a timestamp to all lines written to a trace file.

• overwrite: Append to an existing file.


file_name The name of the file to receive the tracing information. Note that the file name is not specified in quotes.

max‐size file_size[M|m|K|k]

(Optional) Maximum file size in bytes (by default) or megabytes or kilobytes, ranging from 10K to 4,095,000,000 bytes. Notice that there is no space between the file_size parameter and the unit type.

M and m both specify megabytes. K and k both specify kilobytes. If no unit type is entered, bytes is assumed.

If no maximum file size is specified, the default is “unlimited.” The size of a trace file is limited by the file system on which the trace file resides.

max‐files num_files (Optional) Maximum number of files allowed in the directory, ranging from 2 to 4,294,967,295.

If no maximum number of files is specified, the default is 4,294,967,295no-timestamp (Optional) A timestamp should not be prepended to all trace lines. The

default is to prepend a timestamp to all lines written to a trace file.overwrite (Optional) Begin tracing by overwriting, or truncating, an existing file.

The default is to append to an existing file.


Global Commands

UsageThis command specifies the file to receive tracing information for all OSPF events. The specific events that are traced are controlled by the trace flag command. The trace file command is also associated with each protocol, so that data pertaining to a single protocol can be written to its own file.

On the Matrix X Router, trace files are stored in the /var/trace directory. When entering a trace file name, specify only the file name, not the complete path. Trace files are not persistent across system reboots.

The no form of this command disables tracing.

Command options are governed by the following rules:

• The max‐size option specifies a maximum size of the trace file which can be specified in megabytes by giving ‘M’ or ‘m’ (without a leading space), or it can be specified in kilobytes by giving ʹKʹ or ʹkʹ. If you specify no units, the size is assumed to be in bytes. When the maximum file size is reached, the file is closed and renamed to fname.0, then fname.1, and so on, until the maximum number of files specified by the max‐files option is reached.

• The max‐files option specifies the maximum number of files allowed in the specified directory with a default of 4,294,967,295 files.

• The no‐timestamp option disables the pre‐pending of a timestamp to all lines written to the trace file.

• The overwrite option specifies whether to start tracing by truncating or appending to an existing file.

These options are not cumulative across multiple commands. Consider the following example:

matrix-x(config-router-ospf)# trace file ospf.log no-timestampmatrix-x(config-router-ospf)# trace file ospf.log max-files 10

The option given in the second command completely replaces that given in the first. In order to specify both no‐timestamp and max‐files 10, they must be entered on the same line as follows:

matrix-x(config-router-ospf)# trace file ospf.log max-files 10 no-timestamp

ExampleIn the following example, OSPF tracing is written to the file /var/trace/ospf.log. The maximum size of the file is configured to be 1024 KB, and the maximum number of files permitted is 4. When the file reaches 1 megabyte in size (the maximum size in this configuration), the file is renamed to ospf.log.0, and ospf.log is re‐created. This continues until four log files exist (the maximum allowed in this configuration). No timestamp will display at the beginning of the trace lines.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# trace file ospf.log max-size 1024k max-files 4 no-timestamp

32-28 OSPF Commands

Global Commands

trace flagThis command sets OSPF‐specific tracing options as well as options common across all protocols. Each flag must reside on its own configuration line, that is, you cannot specify to trace both task and policy packets in the same command.

Syntaxtrace flag {route | normal | state | policy | task | timer | all} |{db | ospf-state | drelect | spf | flood | debug} | {packets | hello | dd | lsr | lsu | lsa [send | receive | send-receive] [detail]}

no trace flag {route | normal | state | policy | task | timer | all} |{db | ospf-state | drelect | spf | flood | debug} | {packets | hello | dd | lsr | lsu | lsa [send | receive | send-receive] [detail]}

Parameters

The following tracing flags are common to all protocols. They cannot be associated with a send, receive, or send‐receive action item. Similarly, you cannot specify to show detailed data when tracing these flags

The following tracing flag is common to all protocols. It cannot be associated with a send, receive, or send‐receive action item. Similarly, you cannot specify showing detailed data when tracing all.

route Trace routing table changes for routes installed by this protocol or peer.

normal Trace normal protocol occurrences. Note: Abnormal protocol occurrences are always traced.

state Trace state machine transition in the protocol.

policy Trace the application of protocol and user‐specified policy to routes being imported or exported.

task Trace system interface and processing associated with this protocol.

timer Trace timer usage by this protocol.

all Turns on all trace flags.

The following OSPF‐specific flags cannot be associated with the send, receive, or send‐receive action items:

db Trace the link‐state database operations.

ospf‐state Trace OSPF state change information.

drelect Trace the Designated Router operations.

spf Trace the Shortest Path First (SPF) calculations.

flood Trace the flooding procedure.

debug Trace OSPF at the debugging level of detail.

The following OSPF‐specific flags can be associated with the send, receive, or send‐receive action items:

packets Trace all OSPF link‐state packets.

hello Trace OSPF hello packets, which are used to determine neighbor reachability.


Global Commands


UsageUse the trace flag command to specify tracing flags for OSPF tracing. Each flag must reside on its own configuration line. For example, you cannot specify to trace both task and policy packets in the same command. On the Matrix X Router, trace files are stored in the /var/trace directory. When entering a trace file name, specify only the file name, not the complete path. Trace files are not persistent across system reboots.

DefaultsNo flags to be explicitly configured.

ExampleIn the following example, trace flags specify that both the sent and received link state request and hello messages are traced in detail. This tracing data will be written to the file /var/trace/ospf.log.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# trace file ospf max-size 1024kmatrix-x(config-router-ospf)# trace flag lsr send-receive detailmatrix-x(config-router-ospf)# trace flag hello send-receive detail

dd Trace OSPF Database Description (DD) packets, which are used in synchronizing OSPF databases.

lsr Trace OSPF link‐state request packets, which are used in synchronizing OSPF databases.

lsu Trace OSPF link‐state update packets, which are used in synchronizing OSPF databases.

lsa Trace OSPF link‐state acknowledgement packets, which are used in synchronizing OSPF databases.

These optional action items specify whether to limit the tracing to packets as follows:

send Optionally specify to limit tracing for packets sent.

receive Optionally specify to limit tracing for packets received.

send‐receive Optionally specify to limit tracing for packets sent and received.

detail Optionally specify to use a more verbose format when displaying information about the contents of packets instead of one or two lines.

32-30 OSPF Commands

Global Commands

transmit-delayThis command specifies the time in seconds required to transmit a link state update.

Syntaxtransmit-delay time-seconds

no transmit-delay [time-seconds]

Parameters

Defaults1 second.


UsageThis command sets the estimated time in seconds required to transmit a link state update. It takes into account transmission and propagation delays and must be greater than 0. The transmit delay is specified here at the global level. It can be overridden at the area and interface levels (area transmit‐delay and ip ospf transmit‐delay) as well as within a virtual link (area virtual‐link).

The no form of this command resets the specified value to the default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures a global transmit delay of 5 seconds. This value is then overridden in area 1.2.3.4 to be 3 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# transmit-delay 5matrix-x(config-router-ospf)# area 1.2.3.4 transmit-delay 3

time-seconds An interval ranging from 1 to 65535 seconds.


Area Commands

Area CommandsThe area commands are listed below.


area advertise-subnet 32-33

area authentication 32-34

area dead-interval 32-36

area hello-interval 32-37

area nssa 32-38

area nssa-range 32-39

area nssa-translate-always 32-40

area poll-interval 32-41

area priority 32-42

area range 32-43

area retransmit-interval 32-44

area stub 32-45

area stubhost 32-46

area stubnetwork 32-47

area transmit-delay 32-48

area virtual-link 32-49

32-32 OSPF Commands

Area Commands

area advertise-subnetThis command specifies whether OSPF will, when advertising point‐to‐point interfaces, advertise the network number and netmask instead of a host route to the remote IP.

Syntaxarea area_id advertise-subnet

no area area_id advertise-subnet

Parameters

DefaultsDisabled.


UsageUse this command to specify whether OSPF will, when advertising point‐to‐point interfaces, advertise the network number and netmask instead of a host route to the remote IP. Because the netmask is sometimes set improperly on point‐to‐point interfaces, this option is disabled by default.

Configuring this command in an area overrides a global advertise‐subnet command. Similarly, this command can be overridden in an interface command.

ExamplesThe following example turns advertise‐subnet on for area 1.2.3.4 and off for interface ge.1.1 in the same area:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 advertise-subnetmatrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# no ip ospf advertise-subnet

Related Commandsadvertise-subnet

ip ospf advertise-subnet

area_id An ID for an area specified as an IP address in dotted‐quad format. A value of 0.0.0.0 means that the area is a backbone.


Area Commands

area authenticationThis command specifies the type of OSPF authentication used and any key values.

Syntaxarea area-id authentication {simple key]} | {md5 id_number md5_key [start-generate date_time] [stop-generate date_time] [start-accept date_time] [stop-accept date_time]}

no area area-id authentication {simple key | md5 id_number}

Parameters

DefaultsNo authentication.


UsageAuthentication can help to guarantee that routing information is imported only from trusted routers. A variety of authentication schemes can be used, but a single scheme must be configured for each network. The use of different schemes enables some interfaces to use much stricter authentication than others. The two authentication schemes available are simple, and MD5.

Authentication is used by OSPF to generate and verify the authentication field in the OSPF header. The area authentication command specifies the type of authentication and key values used in OSPF. The negative form of this command removes authentication for the area.

The global authentication is the default and can be overridden here in the area command. Similarly, this command can be overridden at the interface level.

area-id An ID for OSPF area to be authenticated, expressed as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

simple key Specifies simple (clear password} authentication. The value for key is specified as a one‐ to eight‐character string.

md5 id_number md5_key Specifies the authentication used for specifying MD5 cryptographic authentication. The value for id_number is an number from 1 to 255. The value for md5_key is a one‐ to sixteen‐character string.





(Optional) The start and stop values must be in the format: YYYY‐MM‐DD.HH.MM. Each start and stop value is optional, and order is not important when specifying multiple commands.

32-34 OSPF Commands

Area Commands


When you do not trust other users of your network, use MD5 authentication. The system works by using shared secret keys. Because keys are used to sign the packets with an MD5 checksum, they cannot be forged or tampered with and because they are not included in the packet, snooping the key is not possible. Network users can still snoop the contents of packets, though, because packets are not encrypted.

The Matrix X MD5 authentication is compliant with the specification in OSPF RFC 2328. This specification uses the MD5 algorithm and an authentication key of up to 16 characters. RFC 2328 allows multiple MD5 keys per interface. Each key has two associated time ranges.

In order to turn off authentication, you must include the authentication type in the no form of the command. For example, if MD5 authentication was configured, then simply specifying no area authentication will not work. In addition, you must specify the simple key when turning off simple authentication, and you must specify the MD5 id_number when turning off MD5 authentication.

ExamplesThe following example configures simple authentication in OSPF instance 1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 authentication simple abc

The following example configures MD5 authentication for OSPF area 1.2.3.4. The ID for this MD5 configuration is 1, and the key is configured as bar.

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# area 1.2.3.4 authentication md5 1 bar

The following example turns off the MD5 authentication that was configured in the previous example. Note that you need not specify the MD5 key, but must specify the MD5 ID.

matrix-x(router-config)# router bgp ospf 2matrix-x(config-router-ospf)# no area 1.2.3.4 authentication md5 1

The following example configures MD5 authentication for OSPF instance 3. MD5 authentication is configured with a start‐generate time of January 2, 2005 at 9:30 p.m., a stop‐generate time of January 2, 2005 at 9:45 p.m., a start‐accept time set to January 2, 2005 at 9:00 p.m, and a stop‐accept time set to January 2, 2005 at 10:00 p.m.

matrix-x(router-config)# router ospf 3matrix-x(config-router-ospf)# area 1.1.1.1 authentication md5 2 md5 start-generate 2005-01-02.21.30 stop-generate 2005-01-02.21.45 start-accept 2005-01-02.21.00 stop-accept 2005-01-02.22.00

Related Commandsauthentication

ip ospf authentication


Area Commands

area dead-intervalThis command specifies the interval that can elapse without receiving a router’s hello packets before the router’s neighbors will declare it down.

Syntaxarea area_id dead-interval time-seconds

no area area_id dead-interval [time-seconds]

Parameters


Defaults40 seconds.

UsageUse this command to specify the interval that can elapse without receiving a router’s hello packets before the router’s neighbors will declare it down. It is specified here at the area level, and it can be overridden in the equivalent interface command, ip ospf dead‐interval.

Generally speaking, this value should be equal to four times the HELLO interval. (Refer to the area hello‐interval command.) Do not set this value to less than the HELLO interval because convergence will not occur.

Use the no form of this command to reset the specified value to the default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures a dead‐interval of 80 seconds for area 1.2.3.4, and a dead‐interval of 60 seconds on interface ge.1.1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 dead-interval 80matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf dead-interval 60

Related Commandsdead-interval

ip ospf dead-interval

area_id An ID for an area specified as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

time-seconds An integer ranging from 1 to 65535 seconds.

32-36 OSPF Commands

Area Commands

area hello-intervalThis command specifies the interval between Hello packets that the router sends.

Syntaxarea area_id hello-interval time-seconds

no area area_id hello-interval [time-seconds]

Parameters


Defaults10 seconds.

UsageUse this command to specify the interval between Hello packets that the router sends. It is specified here at the area level, and it can be overridden in the equivalent interface command. (Refer to ip ospf hello‐interval). A general rule for configuring this value is that it should be equal to one fourth the dead interval. (Refer to area dead‐interval.) This value should never be less than the dead interval value.

Use the no form of this command resets the specified value to the default. Specifying a value fortime‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures a hello interval of 20 seconds for area 1.2.3.4, and a hello interval of 15 seconds on interface ge.1.1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 hello-interval 20matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf hello-interval 15

Related Commandshello-interval

ip ospf hello-interval




Area Commands

area nssaThis command configures a Not So Stubby Area (NSSA).

Syntaxarea area-id nssa [metric] [metric-type]

no area area-id nssa

Parameters


DefaultsNon‐stub, non‐NSSA. If area nssa is set, the default metric is 1 and the default metric type is 1.

UsageUse this command to configure an area as a NSSA. External routes that are not imported into an NSSA can be represented by means of a default route. It is used when an OSPF inter‐network is connected to multiple non‐OSPF routing domains.

Using the no form of this command changes the NSSA back to a plain area.

If the router is an ABR and has the highest router ID of all the ABRs in the area, and no other ABR in the area is configured to translate always, it will translate Type 7 LSAs with the P‐bit (set by the propagate flag in an export command) to Type 5 LSAs. When an ABR that was translating loses a translator election, it will cease translating, and after a number of seconds (determined by nssa‐stability‐ interval), it will flush any Type 5 LSAs resulting from aggregation. Any Type 5 LSAs resulting from direct translation of Type 7 LSAs will be allowed to age out.

An ABR will always originate a default route into any attached NSSAs. The metric of this default route can be specified in the command and defaults to 1. If there are any filters for the NSSA, the default will be Type 3 LSA.

ExampleThe following example changes the default metric type to 2:

matrix-x(router-config)# router ospf 1

area_id NSSA area expressed in as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

metric (Optional) The default OSPF metric, ranging from 1 to 65535. If area nssa is configured, then this value defaults to 1.

metric-type (Optional) Specify 1 or 2 as the default metric type. Routes exported from the routing table into OSPF default to becoming Type 1 ASEs. If area nssa is configured, then this value defaults to 1.

Note: NSSA and Stub are mutually exclusive.

32-38 OSPF Commands

Area Commands

matrix-x(config-router-ospf)# area 1.2.3.4 nssa 10 2

area nssa-rangeThis command specifies the network ranges that should be translated into Type 5 LSas from NSSA Type 7 LSAs.

Syntaxarea area_id nssa-range ip_address mask [no-advertise]

no area area_id nssa-range ip_address mask [no-advertise]

Parameters


DefaultsNSSA net ranges are not configured by default.

UsageUse this command to specify the network ranges that should be translated into Type 5 LSas from NSSA Type 7 LSAs. The default behavior is to translate Type 7 LSas that do not fall within a configured net range.

This command is valid only in an NSSA. It will be ignored when configured in a non‐NSSA.

ExampleThe following example configures an NSSA range on address 192.168.110.0 with a mask of 255.255.0.0:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 nssa-range 192.168.110.0 255.255.0.0

area_id An ID for an area specified as IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

ip_address The IPv4 address associated with this range.mask The network mask for the specified IP address.no-advertise (Optional) Sets the address range status to DoNotAdvertise. The Type 3

summary LSA will not be suppressed, and the component networks will remain hidden from other networks.


Area Commands

area nssa-translate-alwaysThis command allows an Area Border Router (ABR) to always translate Type 7 LSAs into Type 5 LSAs for the specified area.

Syntaxarea area_id nssa-translate-always

no area area_id nssa-translate-always

Parameters


DefaultsDisabled.

UsageUse this command to allow an ABR to always translate Type 7 LSAs into Type 5 LSAs for the specified area. Ordinarily, a translator election is run to determine which on ABR for a given NSSA will translate. But this option allows an ABR to always translate Type 7 LSAs into Type 5 LSAs for the containing area. If an ABR is configured to always translate, then no other ABR will translate unless it is also configured to always translate.

ExampleThe following example configures area 1.2.3.4 to always translate Type 7 LSAs into Type 5 LSAs.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 nssa-translate-always

area_id NSSA area expressed as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

32-40 OSPF Commands

Area Commands

area poll-intervalThis command specifies the interval between OSPF packets that the router sends before adjacency is established with a neighbor.

Syntaxarea area_id poll-interval time-seconds

no area area_id poll-interval [time-seconds]

Parameters



UsageUse this command to specify the interval between OSPF packets that the router sends before adjacency is established with a neighbor. Utilizing this command reduces network overhead in cases where a router may have a neighbor on a given interface at the expense of initial convergence time.

Specifying a poll interval for an area overrides the default configured poll interval. Similarly, an interface‐specific poll interval overrides a value configured here.

Use the no form of this command to reset the configured time‐seconds to the default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExamplesThe following example configures an area poll interval of 100 seconds. This value is overridden in interface ge.1.1, where it is configured to be 110 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 poll-interval 100matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf poll-interval 110

Related Commandspoll-interval

ip ospf poll-interval

area_id An ID for an area specified as an IP address in dotted‐quad format. A value of 0.0.0.0 means that the area is a backbone.

time‐seconds The poll interval, ranging from 1 to 65535 seconds.


Area Commands

area priorityThis command specifies the priority for becoming the Designated Router (DR).

Syntaxarea area_id priority level

no area area_id priority [level]

Parameters


Defaults1.

UsageUse this command to specify the priority for becoming the DR. The priority specified at the area level can be overridden at the interface level. When more than one router attached to a network attempts to become the DR, the one with the highest priority wins. If the competing routers have the same priority, the one with the highest router ID becomes the DR. The router coming in second in the election becomes the backup DR. A router with a priority set to 0 is ineligible to become the DR.

Use the no form of this command to reset the configured value to its default. Specifying a value for level in the no form has no effect on the configuration.

ExampleThe following example configures an area priority of 10. It also sets the priority for interface ge.1.1 to be 5:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 priority 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf priority 5

Related Commandspriority


level A priority number, ranging from 0 to 255, for becoming a DR. A priority of 0 indicates that the router is ineligible to become the DR.

Note: This command applies only to broadcast or NBMA media.

32-42 OSPF Commands

Area Commands

ip ospf priority

area rangeThis command configures the scope of an area on an Area Border Router (ABR).

Syntaxarea area_id range ip_address mask [no-advertise]

no area area_id range ip_address mask [no-advertise]

Parameters

DefaultsNot explicitly configured.


UsageUse this command to define the range of addresses to be used by an ABR when it communicates routes to other areas. Intra‐area LSAs that fall within the specified ranges are not advertised into other areas as inter‐area routes. Instead, the specified ranges are advertised as summary network LSAs.

If no‐advertise is specified, the summary network LSAs and all LSAs within the range are not advertised. Intra‐area LSAs that do not fall into any range are also advertised as summary network LSAs.

On well‐designed networks, this command reduces routing data overhead propagated between areas. The entries in this command can be either networks or subnetwork/mask‐length pairs. Specifying the command on a non‐ABR will have no effect.

Use the no form of this command to remove the configured summarization.

ExampleThe following example configures an area range on address 192.168.0.0 with a mask of 255.255.0.0:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 range 192.168.0.0 255.255.0.0

area_id The area ID, specified as an IP address in dotted‐quad format. A value of 0.0.0.0 means the area is a backbone.

ip_address IPv4 address associated with this range.mask Network mask of the specified IP address.no-advertise Optional. Sets the address range status to DoNotAdvertise. Type 3 summary

LSAs will not be suppressed, and component networks will remain hidden from other networks.


Area Commands

area retransmit-intervalThis command specifies the interval between Link State Advertisement (LSA) retransmissions for adjacencies.

Syntaxarea area_id retransmit-interval time-seconds

no area area_id retransmit-interval [time-seconds]

Parameters


Defaults5 seconds.

UsageUse this command to specify the interval between LSA retransmissions for adjacencies. If a Link State Protocol (LSP) is not acknowledged within the specified period, then it is re‐sent. This setting is another convergence/network traffic trade‐off.

This command overrides the global retransmit interval and can be overridden at the interface level.

Use the no form of this command to reset the specified value to its default. Specifying a value for time‐ seconds in the no form has no effect on the configuration.

ExampleThe following example configures the retransmit interval for area 1.2.3.4 at 10 seconds. This value is then overridden in interface ge.1.1, where it is set to 7 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 retransmit-interval 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf retransmit-interval 7

Related Commandsretransmit-interval

ip ospf retransmit-interval


time-seconds The retransmit interval, ranging from 1 to 65535 seconds.

32-44 OSPF Commands

Area Commands

area stubThis command configures an area as a stub area where there are no Autonomous System External (ASE) or NSSA routes.

Syntaxarea area_id stub [metric]

no area area_id stub [metric]

Parameters


Defaults• No stub areas are explicitly configured.

• Metric: 1

UsageUse this command to configure an area as a stub area. A stub area is one in which there are no ASE or NSSA routes. Each router in the area must specify that the area is a stub, or adjacencies will not form. If a metric is specified, then it is used to inject a default route into the area with the specified value originating from this router. A metric value should only be specified on an ABR. It is possible to use stub on multiple ABRs and give them different metrics.

Use the no form of this command to remove the configured stub area.

ExampleThe following example configures area 4.3.2.1 as a stub area with a metric of 15:

matrix-x(router-config)# router ospfmatrix-x(config-router-ospf)# area 4.3.2.1 stub 15


metric Metric for the stub area, ranging from 1 to 65535. If a stub area is configured, then this value defaults to 1.

Note: NSSA and stub areas are mutually exclusive.


Area Commands

area stubhostThis command specifies directly attached hosts that should be advertised as reachable from the router and the metrics with which they should be advertised.

Syntaxarea area_id stubhost ip_address metric_value

no area area_id stubhost ip_address metric_value

Parameters


Defaults• The area stubhost command is not explicitly configured.

• Metric: 1

UsageUse this command to specify directly attached hosts that should be advertised as reachable from the router and the metrics with which they should be advertised. Point‐to‐point interfaces on which it is not desirable to run OSPF should be specified here. It is also useful to assign an additional address to the loopback interface (one not on the 127 network) and advertise it as a stubhost.

If this address is the same as the router ID, it enables routing to OSPF routers by router ID instead of by interface address. Routing by router ID is more reliable than routing to one of the router’s interface addresses, which may not always be reachable.

Use the no form of this command removes the configured stubhost.

ExampleThe following example configures a single stubhost, 192.1.1.1 with a metric of 2 in area 1.2.3.4:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 stubhost 192.1.1.1 2


ip_addres The address of the host to be advertised.metric_value Metric to be advertised for the host, ranging from 1 to 65535. If a stubhost is

configured, then this value defaults to 1.

Note: This command is identical to area stubnetwork in function except that a 32-bit mask is assumed.

32-46 OSPF Commands

Area Commands

area stubnetworkThis command specifies directly attached networks that should be advertised as reachable from this router and the metrics with which they should be advertised.

Syntaxarea area_id stubnetwork ip_address mask metric

no area area_id stubnetwork ip_address mask metric

Parameters


Defaults• The area stubnetwork command is not explicitly configured.

• Metric: 1

UsageUse this command to specify directly attached networks that should be advertised as reachable from this router and the metrics with which they should be advertised. Interfaces on which it is not desirable to run OSPF should be specified here. No checking is currently done on whether the specified network is actually reachable from this router, so care should be taken.

Use the no form of this command to remove the configured stubnetwork.

ExamplesThe following example configures a single stubnetwork, 192.168.10 with a netmask of 24 in area 1.2.3.4:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# area 1.2.3.4 stubnetwork 192.168.10 255.255.255.0


ip_address The address of the host to be advertised.mask Specifies a mask length for a network prefix.metric Metric for the stubnetwork, ranging from 1 to 65535. If a stubnetwork is

configured, then this value defaults to 1.

Note: This command is identical to area stubhost in function except that a 32-bit mask is not assumed and, therefore, must be configured.


Area Commands

area transmit-delayThis command specifies the interval required to transmit a link state update.

Syntaxarea area_id transmit-delay time-seconds

no area area_id transmit-delay [time-seconds]

Parameters


Defaults1 second.

UsageUse this command to set the estimated interval required to transmit a link state update. This value takes into account transmission and propagation delays and must be greater than 0.

This value overrides the global transmit‐delay value and can be overridden at the interface level.

Use the no form of this command to remove the configured value and return the delay to the default value of 1 second. Specifying a value for time‐seconds in the no form of the command has no effect on the configuration.

ExampleThe following example configures the transmit‐delay for area 1.2.3.4 to 10 seconds. This value is then overridden on interface ge.1.1, where it is configured at 5 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 transmit-delay 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf transmit-delay 5

Related Commandstransmit-delay

ip ospf transmit-delay



32-48 OSPF Commands

Area Commands

area virtual-linkThis command configures a virtual link on the backbone.

Syntaxarea transit_area virtual-link router id [authentication {simple key | md5 id md5key [start-generate date_time] [stop-generate date_time] [start-accept date_time] [stop-accept date_time]}] [hello-interval time-seconds] [retransmit-interval time-seconds] [transmit-delay time-seconds] [dead-interval time-seconds]

no area transit_area virtual-link neighbor-id [authentication {simple key | md5 id md5key}]

Parameters

transit_area An ID, in dotted‐quad format, that sets the area through which the virtual link should exist. This value cannot be 0.0.0.0.

router id The ID of one end of the virtual link.authentication

simple key |

md5 id md5key

(Optional) Sets an authentication type to include on this virtual link.

simple key sets simple (clear password) authentication. The key is as a 1‐8 character string

md5 id md5_key sets the authentication used for specifying MD5 cryptography.The value for id is an integer ranging from 1 to 255. The value for md5_key is a 1 to 16 character string.





(Optional) Specifies start and stop dates for MD5 cryptographic authentication. Start and stop values must be in the format: YYYY‐MM‐DD.HH.MM. Each start and stop value is optional, and order is not important when specifying multiple commands.

hello‐intervaltime‐seconds

(Optional) Sets the interval between hello packets that the software sends on an interface, ranging from 1 to 65535 seconds. This value must be an unsigned integer and must be the same for all routers and access servers attached to a common network.

retransmit‐intervaltime‐seconds

(Optional) Sets the interval between link state advertisement (LSA) retransmissions for adjacencies belonging on the interface, ranging from 1 to 65535 seconds. This value must be an integer and must be greater than the expected round‐trip delay.

transmit‐delaytime‐seconds

(Optional) Sets the interval required to send a link state update packet on the port, ranging from 1 to 65535 seconds. This value must be an integer greater than 0. LSAs in the update packet have their age incremented by this amount before transmission.

dead‐intervaltime‐seconds

(Optional) Sets the interval that Hello packets are sent before a neighbor declares the router down, ranging from 1 to 65535 seconds. The default value is four times the hello‐interval, or 40 seconds. If this value is configured less than the hello‐interval, convergence will not occur. This value must be the same for all routers and access servers attached to a common network.


Area Commands


Defaults• No virtual links are explicitly configured.

• Hello‐interval: 10 seconds

• Retransmit‐interval: 5 seconds

• Transmit‐delay: 1 second

• Dead‐interval: 40 seconds

UsageVirtual links are used to establish or increase connectivity of the backbone area. The transit_area sets the area through which the virtual link should exist. The neighbor‐id represents one end of the virtual link. In addition, all standard interface parameters can optionally be specified on a virtual link.

Use the no form of this command to remove the configured virtual link. The transit_area and neighbor‐id parameters are the minimum required in the negative form of this command to remove the entire virtual link.

ExampleThe following example configures a virtual link in transit area 1.1.1.1 with a neighbor ID of 1.2.2.1, a hello interval of 20 seconds, and a retransmit interval of 20 seconds:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.1.1.1 virtual-link 1.2.2.1 hello-interval 20 retransmit-interval 20

32-50 OSPF Commands

Default Commands

Default CommandsThe commands to configure default OSPF parameters are listed below.

default-metricThis command specifies the default ASE export metric.

Syntaxdefault-metric metric_value

no default-metric [metric_value]

Parameters


Defaults1.

UsageUse this command to specify the default ASE export metric. It is used when exporting a non‐OSPF route from the routing table into OSPF as an ASE route. The default‐metric command can be explicitly overridden in export policy.

Use the no form of this command to reset the configured value to its default. Specifying a value for metric_value in the no form has no effect on the configuration.

ExampleThe following example configures a default metric of 5 for instance 1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# default-metric 5


default-metric 32-51

default-nssa-metric 32-52

default-nssa-type 32-53

default-preference 32-54

default-tag 32-55

default-type 32-56

metric_value An integer assigned to exported reachability, ranging from 1 to 65535.


Default Commands

default-nssa-metricThis command specifies the default cost when exporting non‐OSPF routes from the routing table into OSPF NSSA.

Syntaxdefault-nssa-metric metric_value

no default-nssa-metric [metric_value]

Parameters

Defaults1.


UsageUse this command to configure the default metric on originated NSSA routes for an OSPF instance. This command can be explicitly overridden in export policy.

Use the no form of this command to reset the configured value to its default. Specifying a value for metric_value in the no form has no effect on the configuration.

ExampleThe following example configures the default NSSA metric for OSPF instance 1 to be 4:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# default-nssa-metric 4

metric_value An integer assigned to exported reachability, ranging from 1 to 65535.

32-52 OSPF Commands

Default Commands

default-nssa-typeThis command changes the default type of routes exported from the routing table into OSPF NSSA.

Syntaxdefault-nssa-type 1 | 2

no default-nssa-type [1 | 2]

Parameters

Defaults2.


UsageUse this command to set the default NSSA metric type to either 1 or 2. Routes exported from the routing table into OSPF default to becoming type 1 NSSAs. This default can be explicitly changed here and overridden in export policy.

Use the no form of this command to reset the configured value to its default value. Specifying type 1 or 2 in the no form has no effect on the configuration.

ExampleThe following example changes the default NSSA Type to 2:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# default-nssa-type 2

1 | 2 Sets the default metric type to 1 or 2.


Default Commands

default-preferenceThis command specifies the way that active routes learned from the OSPF Autonomous System External (ASE) will be selected, compared to other routes.

Syntaxdefault-preference pref

no default-preference [pref]

Parameters

Defaults150.


UsageWhen a route has been learned from more than one protocol, the active route will be selected from the protocol with the lowest preference. Each protocol has a default preference in this selection.

use the no form of this command to reset the configured value to the default preference, 150. Specifying a value for pref in the no form has no effect on the configuration.

ExampleThe following example configures the OSPF default preference value to be 100:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf)# default-preference 100

pref Integer ranging from 1 to 255.

32-54 OSPF Commands

Default Commands

default-tagThis command propagates data from an exterior gateway protocol (such as BGP) through OSPF.

Syntaxdefault-tag tag_value

no default-tag [tag_value]

Parameters

Defaults0.


UsageOSPF ASE routes contain a 32‐bit tag field that is not used by the OSPF protocol but can be used when exporting to protocols other than OSPF. The command sets the tag, which can be overridden in export policy.

Use the no form of this command to reset the configured value to the default tag value. Specifying a value for tag_value in the no form has no effect on the configuration.

ExampleThe following example configures the default tag value to be 10:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# default-tag 10

tag_value A 32‐bit value for the tag, ranging from 0 to 2,147,483,647.


Default Commands

default-typeThis command changes the default type of routes exported from the routing table into OSPF Autonomous System External (ASE).

Syntaxdefault-type 1 | 2

no default-type [1 | 2]

Parameters

Defaults2.


UsageRoutes exported from the routing table into OSPF default to becoming type 2 ASEs. This default can be explicitly changed here and overridden in export policy.

Use the no form of this command to reset the configured value to its default. Specifying 1 or 2 as the type in the no form has no effect on the configuration.

ExampleThe following example changes the default metric type to 1:

matrix-x(router-config)# router ospf 2matrix-x(config-router-ospf))# default-type 1

1 | 2 Sets the default metric type to 1 or 2.

32-56 OSPF Commands

Interface Commands

Interface CommandsIt is suggested that users of OSPF should configure interface parameters using a physical interface name, such as ge.4.2. Using a physical interface name provides the clearest, least ambiguous way of configuring these parameters. Using a logical address, such as 192.168.10.1, can lead to undesirable results.

The commands to configure OSPF parameters at the interface level are listed below.


ip ospf advertise-subnet 32-58

ip ospf allow-all 32-59

ip ospf authentication 32-60

ip ospf cost 32-62

ip ospf dead-interval 32-63

ip ospf enable 32-64

ip ospf hello-interval 32-64

ip ospf neighbor 32-65

ip ospf network 32-66

ip ospf no-multicast 32-67

ip ospf passive-interface 32-68

ip ospf poll-interval 32-69

ip ospf priority 32-70

ip ospf retransmit-interval 32-71

ip ospf transmit-delay 32-72

ip ospf transmit-delay 32-72


Interface Commands

ip ospf advertise-subnetThis command specifies whether OSPF will, when advertising point‐to‐point interfaces, advertises the network number and netmask of the point‐to‐point interface instead of a host route to the remote IP.

Syntaxip ospf advertise-subnet

no ip ospf advertise-subnet

ParametersNone.

DefaultsDisabled.

ModeRouter Interface Configuration.

UsageBecause the netmask is sometimes set improperly on point‐to‐point interfaces, this option is disabled by default.

ExamplesThe following example turns advertise‐subnet on for interface ge.1.1:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf advertise-subnet

32-58 OSPF Commands

Interface Commands

ip ospf allow-allThis command permits packets from all routers.

Syntaxip ospf allow-all

no ip ospf allow-all

ParametersNone.

DefaultsDisabled.


UsageUse this command to specify to allow packets from all routers, including those not specified in the ip ospf neighbor command.

ExampleThe following example specifies that interface ge.1.1 will allow packets from all routers:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf allow-all


Interface Commands

ip ospf authenticationThis command specifies the type of authentication and key values for an interface.

Syntaxip ospf authentication {simple key | md5 id_number md5_key [start-generate date_time] [stop-generate date_time] [start-accept date_time] [stop-accept date_time]}

no ip ospf authentication {simple key | md5 id_number}

Parameters

DefaultsAuthentication is not explicitly configured.


UsageAuthentication can help guarantee that routing information is imported only from trusted routers. A variety of authentication schemes can be used, but a single scheme must be configured for each network. The use of different schemes enables some interfaces to use much stricter authentication than others. The two authentication schemes available are simple and MD5.

The command specifies the type of authentication and key values used on an interface. This is used by OSPF authentication to generate and verify the authentication field in the OSPF header. If configured, the area authentication (specified with the area authentication command) is the default unless it is configured here at the interface level.


When you do not trust other users of your network, use MD5 authentication. The system works by using shared secret keys. Because the keys are used to sign the packets with an MD5 checksum, they cannot be forged or tampered with. Because the keys are not included in the packet, snooping the key is not possible. Users of the network can still snoop the contents of packets, however, because the packets are not encrypted.

simple key Specifies simple (clear password) authentication. The value for key is specified as a one‐ to eight‐character string.

md5 id_number md5_key Specifies the authentication used for specifying MD5 cryptographic authentication. The value for id_number ranges from 1 to 255. The value for md5_key is a 1‐ to 16‐character string.





(Optional) Specify start and stop dates for MD5 authentication. Start and stop values must be in the format: YYYY‐MM‐DD.HH.MM. Each start and stop value is optional, and their order is not important when specifying multiple commands.

32-60 OSPF Commands

Interface Commands

The Matrix X MD5 authentication is compliant with the specification in OSPF RFC 2328. This specification uses the MD5 algorithm and an authentication key of up to 16 characters. RFC 2328 allows multiple MD5 keys per interface. Each key has two associated time ranges.

In order to turn off authentication, you must include the authentication type in the no form of the command. For example, if MD5 authentication was configured, then simply specifying no ip ospf authentication will not work. In addition, you must specify the simple key when turning off simple authentication, and you must specify the MD5 id_number when turning off MD5 authentication.

ExamplesThe following example configures the area authentication to be the simple keyword abc. This authentication is then overridden for interface ge.1.1 to be bar.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 authentication simple abcmatrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip authentication simple bar

The following example configures MD5 authentication for interface ge.1.1. The ID for this MD5 configuration is 1, and the key is configured as bar.

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf authentication md5 1 bar

The following example turns off the MD5 authentication that was in the earlier example. Note that specifying the MD5 key is not required, but specifying the MD5 ID is.

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# no ip ospf authentication md5 1

The following example configures MD5 authentication for interface ge.1.1. MD5 is configured with a start‐generate time set to January 2, 2005 at 21:30 hours, a stop‐generate time set to January 2, 2005 at 21:45 hours, a start‐accept time set to January 2, 2005 at 21:00 hours, and a stop‐accept time set to January 2, 2005 at 22:00 hours.

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf authentication md5 2 md5 start-generate 2005-01-02.21.30 stop-generate 2005-01-02.21.45 start-accept 2005-01-02.21.00 stop-accept 2005-01-02.22.00

Related Commandsauthentication

area authentication


Interface Commands

ip ospf costThis command specifies the cost for a route to transit an interface.

Syntaxip ospf cost cost_value

no ip ospf cost [cost_value]

Parameters


Defaults10.

UsageUse this command to specify the cost for a route to transit the interface. Essentially, this is the cost for the Matrix X Router to reach another device from this interface. The command can be explicitly overridden in export policy.

Use the no form of this command to remove the configured cost and return it to its default of 1. Specifying a value for cost_value in the no form has no effect on the configuration.

ExampleThe following example configures the cost for interface ge.1.1 to be 15:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf cost 15

cost_value The cost associated with this interface, ranging from 1 to 65535.

32-62 OSPF Commands

Interface Commands

ip ospf dead-intervalThis command specifies the interval that may elapse on this interface without receiving a router’s hello packets before the router’s neighbors will declare it down.

Syntaxip ospf dead-interval time-seconds

no ip ospf dead-interval [time-seconds]

Parameters

DefaultsIf ip ospf dead‐interval is not specified, the interval defaults to the value specified in area dead‐interval, then to the value specified by the global dead‐interval command. If neither of these is specified, the value is 40 seconds


UsageUse this command to specify the interval that may elapse on this interface without receiving a router’s hello packets before the router’s neighbors will declare it down. The command specified here at the interface level overrides a dead‐interval configured at the area and global levels.

A general rule for configuring this value is that it should be equal to four times the HELLO interval. (See the ip ospf hello‐interval command.) Do not set this value to less than the HELLO interval because convergence will not occur.

Use the no form of this command to reset the configured value to its default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExamplesThe following example configures a dead‐interval of 80 seconds in area 1.2.3.4, and a dead‐interval of 60 seconds on interface ge.1.1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 dead-interval 80matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf dead-interval 60

Related Commandsdead-interval

area dead-interval

time-seconds Interval ranging from 1 to 65535 seconds.


Interface Commands

ip ospf enableThis command enables OSPF on an interface.

Syntaxip ospf enable

no ip ospf enable

ParametersNone.

DefaultsEnabled.


ExampleThe following example disables interface ge.1.1:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# no ip ospf enable

ip ospf hello-intervalThis command specifies the interval between hello packets that the router sends on the interface.

Syntaxip ospf hello-interval time-seconds

no ip ospf hello-interval [time-seconds]

Parameters

DefaultsIf ip ospf hello‐interval is not specified, it defaults to the value specified in area hello‐interval, then to the value specified with the global hello‐interval command. If neither the area nor global hello interval is specified, the default is 10 seconds.



32-64 OSPF Commands

Interface Commands

UsageUse this command to specify the interval between hello packets that the router sends on the interface. The command overrides the interval configured in the equivalent global and area commands. (See the hello‐interval and area hello‐interval commands.)

A general rule for configuring this value is that it should be equal to one‐fourth the dead interval. (See the ip ospf dead‐interval command.) This value should never be less than the dead interval value.

Use the no form of this command to reset the configured time‐seconds value to the default. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures a hello interval of 20 seconds in area 1.2.3.4, and a hello interval of 15 seconds on interface ge.1.1:

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 hello-interval 20matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf hello-interval 15

Related Commandshello-interval

area hello-interval

ip ospf neighborThis command specifies neighboring routers, and specifies whether those routers are eligible to become the Designated Router (DR).

Syntaxip ospf neighbor ip_address [eligible]

no ip ospf neighbor ip_address [eligible]

Parameters


DefaultsOSPF neighbors are not explicitly configured by default.

ip_address A valid IPv4 address specified in dotted‐quad notation.eligible (Optional) Specifies whether the indicated address is eligible to become the DR.


Interface Commands

UsageBy definition it is impossible to send broadcast or multicast packets to discover OSPF neighbors on a non‐broadcast medium, so all neighbors must be configured. The host address list includes one or more neighbors. The eligible option is used to indicate an address’s eligibility to become a DR. Refer to RFC‐2328 for more information.

Use the no form of this command to remove the configured neighbors.

ExampleThe following example specifies that host 10.1.1.1 is eligible to become a DR:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf neighbor 10.1.1.1 eligible

ip ospf networkThis command specifies a either a non broadcast interface on an Non‐Broadcast Multiple Access (NBMA) medium or a point‐to‐multipoint interface.

Syntaxip ospf network {point-to-multipoint | nonbroadcast}

no ip ospf network {point-to-multipoint | nonbroadcast}

Parameters

DefaultsThe default mode is broadcast/point‐to‐point. Therefore, this command is not explicitly configured by default.


UsageBecause an OSPF broadcast medium must support IP multicasting, a broadcast‐capable medium that does not support IP multicasting must be configured as a non broadcast interface. This includes the loopback interface on many operating systems.

ExampleThe following example configures interface lo1 as a non‐broadcast interface:

matrix-x(router-config)# interface lo1matrix-x(router-config-if)# ip ospf network nonbroadcast

point-to-multipoint A non broadcast interface on an NBMA medium.nonbroadcast A point‐to‐multipoint interface.

32-66 OSPF Commands

Interface Commands

ip ospf no-multicastThis command disables multicast on a specified interface.

Syntaxip ospf no-multicast

no ip ospf no-multicast

ParametersNone.

DefaultsBy default, interfaces are multicast interfaces.


UsageThe no form of this command re‐enables multicast on an interface.

ExampleThe following example disables multicast on interface ge.1.1:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf no-multicast


Interface Commands

ip ospf passive-interfaceThis command disables reception and transmission on an interface.

Syntaxip ospf passive-interface

no ip ospf passive-interface

ParametersNone.

DefaultsBy default, reception and transmission are enabled on an interface.


UsageUse this command to disable reception and transmission on an interface. This is used, for example, when this is the only router on the network. This has the effect of originating a stub link to his interface into the domain.

OSPF passive‐interface is not used to learn other routers’ announcements, which is the way passive works in RIP. If your host is connected to a single network on which there are multiple routers, use Router Discovery combined with ICMP redirects to learn a default route and the best route. If your host is connected directly to multiple networks, this method might produce the best routes.

Use the no form of this command to re‐enable reception and transmission on the interface.

ExampleThe following example specifies that the device should not send or receive packets on interface ge.1.1:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf passive-interface

32-68 OSPF Commands

Interface Commands

ip ospf poll-intervalThis command specifies the interval between OSPF packets that the router sends before adjacency is established with a neighbor.

Syntaxip ospf poll-interval time-seconds

no ip ospf poll-interval [time-seconds]

Parameters



UsageUse this command to specify the interval between OSPF packets that the router sends before adjacency is established with a neighbor. This command reduces network overhead in cases where a router may have a neighbor on a given interface at the expense of initial convergence time.

Use the no form of this command to reset the configured value to its default value. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExamplesThe following configures the poll‐interval for interface ge.1.1 to be 100 seconds:

matrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf poll-interval 100

Related Commandspoll-interval

area poll-interval

time-seconds Integer ranging from 1 to 65535 seconds.


Interface Commands

ip ospf priorityThis command specifies the priority for becoming the Designated Router (DR).

Syntaxip ospf priority level

no ip ospf priority [level]

Parameters

DefaultsIf the ip ospf priority command is not specified, then this value defaults to the configured area or global value, respectively. If neither of those values is configured, then this value defaults to 1.


UsageUse this command to specify the priority for becoming the DR. This priority overrides any value configured at the global or area levels. (See the priority and area priority commands.) When more than one router attached to a network attempts to become the DR, the one with the highest priority wins. If the competing routers have the same priority, the one with the highest router ID becomes the DR. The router coming in second in the election becomes the backup DR. A router with a priority set to 0 is ineligible to become the DR.

Use the no form of this command to remove the configured priority. Specifying a value for level in the no form has no effect on the configuration.

ExamplesThe following example configures an area priority of 10 and the priority for interface ge.1.1 to be 5.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 priority 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf priority 5

Related Commandspriority

area priority

level Priority number ranging from 0 to 255, for becoming a DR. A value of 0 indicates that the router is ineligible to become a DR.

Note: This command applies only to broadcast or NBMA media.

32-70 OSPF Commands

Interface Commands

ip ospf retransmit-intervalThis command specifies the interval between Link State Advertisement (LSA) retransmissions for adjacencies.

Syntaxip ospf retransmit-interval time-seconds

no ip ospf retransmit-interval [time-seconds]

Parameters

DefaultsIf the ip ospf priority command is not specified, then this value defaults to the configured area or global value, respectively. If neither of these values is configured, then this value defaults to 5 seconds.


UsageUse this command to specify the interval between LSA retransmissions for adjacencies. If a Link State Protocol (LSP) is not acknowledged within the number of seconds specified here, it is re‐sent.

This command overrides any configured in the global or area levels. (See the retransmit‐interval and area retransmit‐interval commands.)

Use the no form of this command to remove the configured retransmit value. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures the retransmit interval for area 1.2.3.4 to be 10 seconds. This value is then overridden in interface ge.1.1, where it is configured to be 7 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 retransmit-interval 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf retransmit-interval 7

Related Commandsretransmit-interval

area retransmit-interval



Interface Commands

ip ospf transmit-delayThis command specifies the interval required to transmit a link state update.

Syntaxip ospf transmit-delay time-seconds

no ip ospf transmit-delay [time-seconds]

Parameters

DefaultsIf this command is not specified, then the transmit delay value defaults to the configured area or global value, respectively. If neither of those is configured, then this value defaults to 1 second.


UsageUse this command to specify the interval required to transmit a link state update. The command takes into account transmission and propagation delays and must be greater than 0. It also overrides any given value at the global or area levels (the transmit‐delay and area transmit‐delay commands).

Use the no form of this command to remove the configured time‐seconds value. Specifying a value for time‐seconds in the no form has no effect on the configuration.

ExampleThe following example configures the transmit‐delay for area 1.2.3.4 to be 10 seconds. This value is then overridden on interface ge.1.1, where it is configured to be 5 seconds.

matrix-x(router-config)# router ospf 1matrix-x(config-router-ospf)# area 1.2.3.4 transmit-delay 10matrix-x(config-router-ospf)# exitmatrix-x(router-config)# interface ge.1.1matrix-x(router-config-if-ge.1.1)# ip ospf transmit-delay 5

Related Commandstransmit-delay

area transmit-delay


32-72 OSPF Commands

Querying Commands

Querying CommandsThe commands to display OSPF information are listed below.

show ip ospfThis command displays information about a single OSPF instance or all OSPF instances.

Syntaxshow ip ospf [instance_id]

Parameters

ModeRouter privileged execution matrix-x(router-exec)#

Router global configuration: matrix-x(router-config)#

Router interface configuration: matrix-x(router-config-if-xx.x.x)#

UsageThis query has two forms. If the query is issued without an instance ID, then information about all OSPF instances displays. If the query is issued with a specific instance ID, the output will contain data pertaining only to that referenced instance.

ExampleThe following example is a request for information relating to OSPF instance 2:


show ip ospf 32-73

show ip ospf border-routers 32-74

show ip ospf database 32-75

show ip ospf flood-list 32-76

show ip ospf interface 32-77

show ip ospf neighbor 32-78

show ip ospf request-list 32-79

show ip ospf retransmission-list 32-80

show ip ospf summary-address 32-81

show ip ospf virtual-links 32-82

instance_id (Optional) Specifies to return information for a specific instance, ranging from 1 to 4294967294. If no instance ID is entered, the command displays information about all OSPF instances.


Querying Commands

matrix-x(router-config)# show ip ospf 2-----------------------Routing Process "ospf 1" with ID 1.1.1.1 Supports opaque LSA It is an autonomous system boundary router and is an area border router Hold time between two SPFs is 5 Minimum LSA interval 5. Minimum LSA arrival 1 Number of external LSA 0. Checksum sum 0 Number of opaque AS LSA 0, Checksum sum 0 Number of areas in this router is 2. 1 normal 0 stub 1 nssa Area 0.0.0.0 Number of interface in this area is 1 It is a normal area Number of LSA 4 Checksum sum 0 Number of opaque LSA 0 Checksum sum 0 Area ranges are Area 10.10.10.10 Number of interface in this area is 1 It is a nssa area Number of LSA 3 Checksum sum 0 Number of opaque LSA 0 Checksum sum 0

Area range is 192.10.0.0/24

show ip ospf border-routersThis command displays the Autonomous System (AS) and Area Border Routers (ABRs) for all OSPF instances.

Syntaxshow ip ospf border-routers

ParametersNone.




ExampleThe following example is a request for border router data:

matrix-x(router-config)# show ip ospf border-routers

32-74 OSPF Commands

Querying Commands

OSPF Routing TableRoute 192.168.10.1 area 0.0.0.1 ABR

show ip ospf databaseThis command displays information contained within the OSPF Link State Database(s).

Syntaxshow ip ospf database [instance_id [area_id]]

show ip ospf database external [instance_id]

show ip ospf database type-11-opaque [instance_id]

Parameters




UsageThis query can be narrowed to search a specific database, based on the instance ID, the area ID, whether to search the external database or the type‐11‐opaque database.

ExampleThe following example displays a request for all OSPF database data:

matrix-x(router-config)# show ip ospf databaseOSPF Router Instance 1

Router Link States (Area 0.0.0.1)

Link ID ADV RTR Seq No Age Checksum Link ct192.168.10.0 192.168.1.8 0x80000003 0 0xBEEF 1192.168.11.0 192.168.2.4 0x80000003 0 0xBEED 2

instance_id (Optional) Indicates to return information for a specific instance, ranging from 1 to 4294967294.

area_id (Optional) If an instance ID is specified for a database, you can also optionally specify an area to be associated with this query.

external Search the external database.type-11-opaque Search the type‐11‐opaque database.


Querying Commands

show ip ospf flood-listThis command displays a list of OSPF Link State Advertisements (LSAs) waiting to be flooded over an interface.

Syntaxshow ip ospf flood-list [interface-type] [interface-number]

Parameters

ModePrivileged EXEC: matrix‐x(router‐exec)#

ExampleThe following example is a request for flood list information on Ethernet interface number 1:

matrix-x(router)# show ip ospf flood-list ethernet 1

Interface ge.1.1, Queue length 5Link state flooding due in 10 msec

Type LS ID ADV RTR Seq No Age Checksum 5 192.168.10.0 192.168.10.5 0x80000003 0 0xBEEF 5 192.168.11.0 192.168.10.5 0x80000003 0 0xBEEF 5 192.168.12.0 192.168.10.5 0x80000003 0 0xBEEF

interface-type Optionally enter a specific interface type over which LSAs are flooded.interface-number Optionally enter the interface number of which the LSAs are flooded.

32-76 OSPF Commands

Querying Commands

show ip ospf interfaceThis command displays information about a single or all interfaces running OSPF.

Syntaxshow ip ospf interface [ipv4-address | interface-name]

Parameters




UsageThis query has two forms. If the query is issued without arguments, then information on about all interfaces over which OSPF is running displays. Or, the query can be issued with a specific interface, in which case the reply will contain data pertaining only to that referenced interface.

Note that if interfaces are added to the set of interfaces over which OSPF is running after this query has been issued but before the query is finished, it is not guaranteed that the new interfaces will be reported. Similarly, if OSPF is de‐configured on an interface after the query has been issued but before the query is finished, then the interface may or may not be reported.

ExampleThe following example returns OSPF information for interface ge.1.1:

matrix-x(router-config)# show ip ospf interface ge.1.1

OSPF Router Instance 1

ge.4.1 is up, line protocol is upInternet Address 192.168.10.1/24, Area 0.0.0.1Router ID 192.168.10.5, Network Type BROADCAST, Cost: 10Transmit Delay is 1 sec, state WAITING, Priority 1Designated Router is 192.168.10.5 (this router)No Backup Designated router for this networkTimer intervals configured, Hello 20, Dead, 120, Wait 30, Retransmit 5Hello due in 0:00:05Neighbor Count is 0, Adjacent neighbor count is 0

ipv4‐address | interface‐name

Optionally specify either a valid IPv4 address in dotted‐quad notation or a physical interface name.


Querying Commands

show ip ospf neighborThis command displays information about a single or all OSPF neighbors.

Syntaxshow ip ospf neighbor [neighbor]

Parameters




ExampleThe following example returns OSPF information for neighbor ID 2.2.2.2:

matrix-x(router-config)# show ip ospf neighbor 2.2.2.2Routing Process "ospf 1": Neighbor 0.0.103.12, interface address 192.0.0.2 In area 0.0.0.2 interface "ge.1.1" Neighbor priority is 1, state is "Full", 7 state changes DR is 192.0.0.2 BDR is 192.0.0.1 Options is 0x2 Dead timer is due in 4 seconds

neighbor Optionally specify either a valid IPv4 address in dotted‐quad notation or a physical interface name for the OSPF neighbor on which to query information.

32-78 OSPF Commands

Querying Commands

show ip ospf request-listThis command displays a list of all LSAs requested by a router.

Syntaxshow ip ospf request-list [neighbor | interface | interface_neighbor]

Parameters




ExampleThe following example displays a list of LSAs requested by the router for interface ge.1.1:

matrix-x(router-config)# show ip ospf request-list ge.1.1OSPF Instance 1Neighbor 192.168.10.5, interface ge.1.1 address 192.168.10.1

Type LS ID ADV RTR Seq No Age Checksum 1 192.168.10.9 192.168.10.9 0x80000001 35 0xBEEF

neighbor (Optional) Specifies to display a list of all LSAs requested by the router from this neighbor.

interface (Optional) Specifies to display a list of all LSAs requested by the router form this interface.

interface_neighbor (Optional) Specifies to display a list of all LSAs requested from this neighbor on this interface


Querying Commands

show ip ospf retransmission-listThis command displays a list of all LSAs waiting to be re‐sent.

Syntaxshow ip ospf retransmission-list [neighbor | interface | interface_neighbor]

Parameters




ExampleThe following example displays retransmission list information for interface ge.1.1:

matrix-x(router-config)# show ip ospf retransmission-list ge.1.1

OSPF Instance 1Neighbor 192.168.10.5, interface ge.1.1 address 192.168.10.1LSA retransmission due in 3000 msec, Queue length is 3

Type LS ID ADV RTR Seq No Age Checksum1 192.168.10.9 192.168.10.9 0x80000001 35 0xBEEF

neighbor (Optional) Specifies to display a list of all LSAs requested by the router from this neighbor.

interface (Optional) Specifies to display a list of all LSAs requested by the router from this interface.

interface_neighbor (Optional) Specifies to display a list of all LSAs requested from this neighbor on this interface

32-80 OSPF Commands

Querying Commands

show ip ospf summary-addressThis command displays summary address redistribution information, for one or all OSPF instances.

Syntaxshow ip ospf summary-address [instance_id]

Parameters

DefaultsIf instance_id is not specified, information for all instances is displayed.




ExampleThe following example returns summary address information for OSPF instance 1:

matrix-x(router-config)# show ip ospf summary-address 1

OSPF Router Instance 1

instance_id (Optional) Specifies the OSPF instance for which to display information. If no instance_id is specified, information for all instances is displayed. An integer from 1 to 4294967294.


Querying Commands

show ip ospf virtual-linksThis command displays information about configured OSPF virtual links for a single instance or for all OSPF instances.

Syntaxshow ip ospf virtual-links




ExampleThe following example queries virtual link information.

matrix-x(router-config)# show ip ospf virtual-links

Virtual Link to router 192.168.101.2 is upTransit area 0.0.0.1 via interface ge.1.1Link Cost is 5Adjacency State is FULLTimer intervals configured, Hello 20, Dead 120, Wait 30 Retransmit 5Hello due in 0:00:05

32-82 OSPF Commands

Comandos ospf

Education

Transcript of Comandos ospf