authentication [inbound sa-name outbound sa-name]
authentication bidirectional sa-name
no authentication
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link>if
Supported on all 7210 SAS platforms as described in this document
This command configures the password used by the OSPF3 interface or virtual link to send and receive OSPF3 protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for correct protocol communication.
By default, no authentication key is configured.
The no form of this command removes the authentication.
no authentication
Specifies the inbound sa-name for OSPF3 authentication, up to 32 characters.
Specifies the outbound sa-name for OSPF3 authentication, up to 32 characters.
Specifies bidirectional OSPF3 authentication, up to 32 characters.
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>ospf>area>interface
config>router>ospf>area>virtual-link>if
Supported on all 7210 SAS platforms as described in this document
This command configures the password used by the OSPF interface or virtual-link to send and receive OSPF protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for correct protocol communication. If the authentication-type is configured as password, this key must be configured.
By default, no authentication key is configured.
The no form of this command removes the authentication key.
no authentication-key
Specifies the authentication key. The key can be any combination of ASCII characters up to 8 characters (unencrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
Keyword that specifies the hash key. The key can be any combination of ASCII characters up to 22 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
Keyword that specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
Keyword that specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
authentication-type {password | message-digest}
no authentication-type
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command enables authentication and specifies the type of authentication to be used on the OSPF interface.
Both simple password and message-digest authentication are supported.
By default, authentication is not enabled on an interface.
The no form of this command disables authentication on the interface.
no authentication
Keyword that enables simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
Keyword that enables message digest MD5 authentication in accordance with RFC1321. If this option is configured, at least one message-digest-key must be configured.
[no] bfd-enable [remain-down-on-failure]
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command enables the use of bidirectional forwarding (BFD) to control the state of the associated protocol interface. By enabling BFD on a specific protocol interface, the state of the protocol interface is tied to the state of the BFD session between the local node and the remote node. The parameters used for the BFD are set using the BFD command under the IP interface.
BFD is not supported for IPv6 interfaces.
For more information about the protocols and platforms that support BFD, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
The no form of this command removes BFD from the associated IGP protocol adjacency.
no bfd-enable
Keyword that forces adjacency down on BFD failure.
dead-interval seconds
no dead-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command configures the time, in seconds, that OSPF waits before declaring a neighbor router down. If no Hello packets are received from a neighbor for the duration of the dead interval, the router is assumed to be down. The minimum interval must be two times the Hello interval.
The no form of this command reverts to the default value.
dead-interval 40
If the configured dead-interval value applies to an interface, all nodes on the subnet must have the same dead interval.
If the configured dead-interval value applies to a virtual link, the interval on both termination points of the virtual link must have the same dead interval.
Specifies the dead interval, in seconds.
[no] export policy-name [policy-name...up to 5 max]
config>router>ospf
Supported on all 7210 SAS platforms as described in this document
This command configures export routing policies that determine the routes exported from the routing table to OSPF.
If no export policy is defined, non OSPF routes are not exported from the routing table manager to IS-IS.
If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered overrides the previous command. A maximum of five policy names can be specified.
If an aggregate command is also configured in the config>router context, the aggregation is applied before the export policy is applied.
Routing policies are created in the config>router>policy-options context.
The no form of this command removes the specified policy-name or all policies from the configuration if no policy-name is specified.
no export
Specifies the export policy name.
export-limit number [log percentage]
no export-limit
config>router>ospf
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum number of routes (prefixes) that can be exported into OSPF from the route table.
The no form of this command removes the parameters from the configuration.
no export-limit
Specifies the maximum number of routes (prefixes) that can be exported into OSPF from the route table.
Specifies the percentage of the export-limit at which a warning log message and SNMP notification would be sent.
hello-interval seconds
no hello-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command configures the interval between OSPF hellos issued on the interface or virtual link.
The hello interval, in combination with the dead-interval, is used to establish and maintain the adjacency. Use this parameter to edit the frequency that hello packets are sent.
Reducing the interval, in combination with an appropriate reduction in the associated dead-interval, allows for faster detection of link or router failures at the cost of higher processing.
The no form of this command reverts to the default value.
hello-interval 10
If the configured hello-interval value applies to an interface, all nodes on the subnet must have the same hello interval.
If the configured hello-interval value applies to a virtual link, the interval on both termination points of the virtual link must have the same hello interval.
Specifies the hello interval, in seconds, expressed as a decimal integer.
[no] interface ip-int-name [secondary]
config>router>ospf>area
config>router>ospf3>area
Supported on all 7210 SAS platforms as described in this document
This command configures an OSPF interface.
By default, interfaces are not activated in any interior gateway protocol, such as OSPF, unless explicitly configured.
The no form of this command deletes the OSPF interface configuration for this interface. The shutdown command in the config>router>ospf>interface context can be used to disable an interface without removing the configuration for the interface.
no interface
Specifies the IP interface name. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. Interface names can be any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
If the IP interface name does not exist or does not have an IP address configured, an error message is returned.
If the IP interface exists in a different area, it is moved to this area.
The IPv6 address is not present for OSPF on the node. It is supported only for OSPF3.
Keyword that allows multiple secondary adjacencies to be established over a single IP interface.
interface-type {broadcast | point-to-point}
no interface-type
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the interface type to be either broadcast or point-to-point.
Use this command to set the interface type of an Ethernet link to point-to-point to avoid having to carry the broadcast adjacency maintenance overhead of the Ethernet link, provided the link is used as a point-to-point.
If the interface type is not known at the time the interface is added to OSPF and subsequently the IP interface is bound (or moved) to a different interface type, this command must be entered manually.
The no form of this command reverts to the default value.
interface-type broadcast — if the physical interface is Ethernet or unknown
A virtual link is always regarded as a point-to-point interface and not configurable.
Keyword that configures the interface to maintain this link as a broadcast network. To significantly improve adjacency forming and network convergence, a network should be configured as point-to-point if only two routers are connected, even if the network is a broadcast media, such as Ethernet.
Keyword that configures the interface to maintain this link as a point-to-point link.
message-digest-key key-id md5 [key | hash-key] [hash| hash2]
no message-digest-key key-id
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command configures a message digest key when MD5 authentication is enabled on the interface. Multiple message digest keys can be configured.
The no form of this command removes the message digest key identified by the key-id value.
Specifies the key ID, expressed as a decimal integer.
Specifies the MD5 key. The key can be any alphanumeric string up to 16 characters.
Specifies the MD5 hash key. The key can be any combination of ASCII characters, up to 32 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
Keyword that specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.
Keyword that specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
metric metric
no metric
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command configures an explicit route cost metric for the OSPF interface that overrides the metrics calculated based on the speed of the underlying link.
The no form of this command deletes the manually configured interface metric, so the interface uses the computed metric based on the reference-bandwidth command setting and the speed of the underlying link.
no metric
Specifies the metric to be applied to the interface, expressed as a decimal integer.
mtu bytes
no mtu
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the OSPF packet size used on this interface. If this parameter is not configured, OSPF derives the MTU value from the MTU configured (default or explicitly) in the config>port>ethernet context.
If this parameter is configured, the smaller value between the value configured here and the MTU configured (default or explicitly) in any of the previous contexts is used.
To determine the actual packet size, add 14 bytes for an Ethernet packet and 18 bytes for a tagged Ethernet packet to the size of the OSPF (IP) packet MTU configured in this command.
The no form of this command reverts to the default value.
no mtu
Specifies the MTU to be used by OSPF for this logical interface, in bytes.
node-sid index value
node-sid label value
no node-sid
config>router>ospf>area>interface
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE
This command assigns a node SID index or label value to the prefix representing the primary address of an IPv4 network interface of the loopback type. Only a single node SID can be assigned to an interface. The secondary address of an IPv4 interface cannot be assigned a node SID index and does not inherit the SID of the primary IPv4 address.
This command fails if the network interface is not of type loopback or if the interface is defined in an IES or a VPRN context. Also, assigning the same SID index or label value to the same interface in two different IGP instances is not allowed within the same node.
The value of the label or index SID is taken from the range configured for this IGP instance. When using the global mode of operation, a new segment routing module checks that the same index or label value cannot be assigned to more than one loopback interface address. When using the per-instance mode of operation, this check is not required because the index and label ranges of the various IGP instance are not allowed to overlap.
The no form of this command reverts to the default value.
no node-sid
Specifies the node SID index or label value.
[no] passive
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command adds the passive property to the OSPF interface where passive interfaces are advertised as OSPF interfaces but do not run the OSPF protocol.
By default, only interface addresses that are configured for OSPF are advertised as OSPF interfaces. The passive command allows an interface to be advertised as an OSPF interface without running the OSPF protocol.
While in passive mode, the interface ignores ingress OSPF protocol packets and does not transmit OSPF protocol packets.
By default, service interfaces defined in the config>router>service-prefix context are passive. All other interfaces are not passive.
The no form of this command removes the passive property from the OSPF interface.
priority number
no priority
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the priority of the OSPF interface that is used in an election of the designated router on the subnet.
This parameter is used only if the interface is of type broadcast. The router with the highest priority interface becomes the designated router. A router with priority 0 is not eligible to be the designated router (DR) or backup designated router (BDR).
The no form of this command reverts to the default value.
priority 1
Specifies the interface priority, expressed as a decimal integer. A value of 0 indicates the router is not eligible to be the DR or BDR on the interface subnet.
retransmit-interval seconds
no retransmit-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command specifies the length of time, in seconds, that OSPF waits before retransmitting an unacknowledged link state advertisement (LSA) to an OSPF neighbor.
The value should be longer than the expected round trip delay between any two routers on the attached network. When the retransmit-interval expires and no acknowledgment has been received, the LSA is retransmitted.
The no form of this command reverts to the default value.
retransmit-interval 5
Specifies the retransmit interval, in seconds, expressed as a decimal integer.
transit-delay seconds
no transit-delay
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
config>router>ospf3>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command configures the estimated time, in seconds, to transmit an LSA on the interface or virtual link.
The no form of this command reverts to the default value.
transit-delay 1
Specifies the transit delay, in seconds, expressed as a decimal integer.
[no] virtual-link router-id transit-area area-id
config>router>ospf>area
config>router>ospf3>area
Supported on all 7210 SAS platforms as described in this document
This command configures a virtual link to connect area border routers to the backbone via a virtual link.
The backbone area (area 0.0.0.0) must be contiguous and all other areas must be connected to the backbone area. If it is not practical to connect an area to the backbone (see area 0.0.0.2 in the following figure), the area border routers (routers 1 and 2 in the following figure) must be connected using a virtual link. The two area border routers form a point-to-point-like adjacency across the transit area. (area 0.0.0.1 in the following figure). A virtual link can be configured only while in the area 0.0.0.0 context.
The router-id specified in this command must be associated with the virtual neighbor. The transit area cannot be a stub area or an NSSA.
The no form of this command deletes the virtual link.
Specifies the router ID of the virtual neighbor, in IP address dotted decimal notation.
Specifies the area ID that identifies the transit area that links the backbone area with the area that has no physical connection with the backbone.
The OSPF backbone area, area 0.0.0.0, must be contiguous and all other areas must be connected to the backbone area. The backbone distributes routing information between areas. If it is not practical to connect an area to the backbone, the area border routers (such as routers Y and Z) must be connected using a virtual link. The two area border routers form a point-to-point-like adjacency across the transit area (area 0.0.0.4).