authentication bidirectional sa-name
authentication [inbound sa-name outbound sa-name]
no authentication
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 an interface with a static security association (SA) used to authenticate OSPFv3 packets.
The no form of this command removes the SA name from the configuration.
no authentication
Specifies the IPSec SA name, up to 32 characters, used for transmitting and receiving OSPFv3 packets.
Specifies the IPSec SA name, up to 32 characters, used for receiving OSPFv3 packets.
Specifies the IPSec SA name, up to 32 characters, used for transmitting OSPFv3 packets.
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>ospf>area>interface
config>router>ospf3>area>virtual-link
Supported on all 7210 SAS platforms as described in this document
This command configures the password used by the OSPF or OSPFv3 interface or virtual-link to send and receive OSPF or OSPFv3 protocol packets on the interface when simple password authentication is configured.
All neighboring routers must use the same type of authentication and password for proper 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 (‟ ”).
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.
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.
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>ospf3>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 or OSPFv3 interface.
Both 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 to enable simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
Keyword to enable 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
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 OSPF interface. By enabling BFD on an OSPF interface, the state of the interface is tied to the state of the BFD session between the local node and the remote node.
The optional remain-down-on-failure parameter can be specified on OSPF interfaces that are enabled for BFD to keep OSPF from reaching the full state if the BFD session to that neighbor cannot be established. This option is disabled by default and should be used only if there is a chance that unicast packets might be discarded while multicast packets are forwarded.
The no form of this command removes BFD from the associated OSPF adjacency.
no bfd-enable
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 or OSPFv3 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 dead-interval configured applies to an interface, all nodes on the subnet must have the same dead interval.
If the dead-interval configured 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, expressed as a decimal integer.
[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 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. Up to five policy-name arguments can be specified.
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 or OSPFv3 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 costs.
The no form of this command reverts to the default value.
hello-interval 10
If the hello-interval configured applies to an interface, all nodes on the subnet must have the same hello interval.
If the hello-interval configured 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 or OSPFv3 interface.
By default, interfaces are not activated in any interior gateway protocol, such as OSPF or OSPFv3, 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 the config>router>interface command. 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 quotess.
If the IP interface name does not exist or does not have an IP address configured, an error message will be returned.
If the IP interface exists in a different area it will be moved to this area.
Keyword to enable 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 or OSPFv3, 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 to configure 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 to configure the interface to maintain this link as a point-to-point link.
[no] loopfree-alternate-exclude
config>router>ospf>area>interface
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command instructs IGP to exclude a specific interface or all interfaces that are participating in a specific IS-IS level or OSPF area in the SPF LFA computation. This reduces LFA SPF calculation where it is not needed.
When an interface is excluded from the LFA SPF in IS-IS, it is excluded in both level 1 and level 2. When it is excluded from the LFA SPF in OSPF, it is excluded in all areas. However, the loopfree-alternate-exclude command can only be executed under the area in which the specified interface is primary. If the command is enabled, the interface is excluded in that area and in all other areas where the interface is secondary. If the user attempts to apply it to an area where the interface is secondary, the command will fail.
The no form of this command reinstates the default value.
no loopfree-alternate-exclude
message-digest-key keyid md5 [key | hash-key] [hash| hash2]
no message-digest-key keyid
config>router>ospf>area>interface
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.
no message-digest-key
Specifies the message digest key, 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.
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.
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 or OSPFv3 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 or OSPFv3 interface MTU value used when negotiating an OSPF or OSPFv3 adjacency.
The operational OSPF or OSPFv3 MTU value is calculated as follows.
If this command is not configured, the OSPF or OSPFv3 interface operational MTU derives the MTU value from the IP interface MTU (which is derived from the port MTU); for example, port MTU minus 14 bytes for a null-encapsulated Ethernet port for OSPF (not OSPFv3). If the derived MTU value is less than 576 bytes, the OSPF interface operational MTU is set to 576 bytes. If a lower interface MTU is required, it must be explicitly configured using this command.
If this command is configured for OSPF (not OSPFv3):
if the OSPF interface MTU is less than 576 bytes, it becomes the operational OSPF MTU, regardless of the port MTU value
if the OSPF interface MTU is equal to or greater than 576 bytes, and the derived interface MTU is less than 576 bytes, the operational OSPF MTU is set to 576 bytes
if the OSPF interface MTU is equal to or greater than 576 bytes, and the derived interface MTU is greater than 576 bytes, the operational OSPF MTU is set to the lesser of the values configured with this command and the derived MTU
The port MTU must be set to 512 bytes or higher, because OSPF cannot support port MTU values lower than 512 bytes.
If this command is configured for OSPFv3:
the operational OSPFv3 MTU is set to the lesser of the values configured with this command and the derived MTU
this applies only when the port MTU is set to 1280 bytes or higher, because OSPFv3 cannot support port MTU values less than 1280 bytes
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 or OSPFv3 (IP) packet MTU configured with this command.
If this command is configured to a value less than the interface or port MTU value, the OSPF or OSPFv3 MTU value will be used to transmit OSPF packets.
The no form of this command uses the value derived from the MTU configured in the config>port context.
no mtu
Specifies the MTU to be used by OSPF or OSPFv3 for this logical interface, in byte.
node-sid index value
node-sid label value
no node-sid
config>router>ospf>area>interface
Supported on all 7210 SAS platforms as described in this document
This command assigns a node SID index or label value to the prefix representing the primary address of an IPv4 network interface of type loopback. 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 or OSPFv3 interface where passive interfaces are advertised as OSPF or OSPFv3 interfaces but do not run the OSPF or OSPFv3 protocol.
By default, only interface addresses that are configured for OSPF or OSPFv3 will be advertised as OSPF or OSPFv3 interfaces. The passive parameter allows an interface to be advertised as an OSPF or OSPFv3 interface without running the OSPF or OSPFv3 protocol.
While in passive mode, the interface will ignore ingress OSPF or OSPFv3 protocol packets and not transmit any OSPF or OSPFv3 protocol packets.
The no form of this command removes the passive property from the OSPF or OSPFv3 interface.
no passive
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 or OSPFv3 interface that is used in an election of the designated router on the subnet.
This parameter is only used 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 or backup designated touter.
The no form of this command reverts the interface priority to the default value.
priority 1
Specifies the interface priority, expressed as a decimal integer.
retransmit-interval seconds
no retransmit-interval
config>router>ospf>area>interface
config>router>ospf>area>virtual-link
config>router>ospf3>area>interface
Supported on all 7210 SAS platforms as described in this document
This command specifies the length of time that OSPF or OSPFv3 will wait 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 acknowledgement has been received, the LSA will be retransmitted.
The no form of this command reverts to the default interval.
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, that it takes to transmit an LSA on the interface or virtual link.
The no form of this command reverts to the default delay time
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 through 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, the area border routers must be connected via a virtual link. The two area border routers will form a point-to-point like adjacency across the transit area. A virtual link can only be configured 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 a NSSA.
The no form of this command deletes the virtual link.
no virtual-link
Specifies the router ID of the virtual neighbor in IP address dotted decimal notation.
Specifies the area ID specified identifies the transit area that links the backbone area to the area that has no physical connection with the backbone, expressed in dotted decimal notation or as a 32-bit decimal integer.