The shutdown command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the
no shutdown command.
The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
The no form of the command puts an entity into the administratively enabled state.
[no
] ospf
ospf-instance [instance-id] [router-id]
The no form of the command to reverts to the default value.
ospf3 [instance-id] [router-id]
The no form of the command deletes the OSPFv3 protocol instance, removing all associated configuration parameters.
instance-id — Specify the instance ID for the OSPFv3 instance being created or modified. The instance ID must match the specified range based on the address family. For ipv6-unicast, the instance id must be between 0 and 31. For ipv4-unicast the instance id must be between 64-95.
[no
] asbr
[trace-path
domain-id]
The no form of the command removes the ASBR status and withdraws the routes redistributed from the Routing Table Manager into this instance of OSPF from the link state database.
no asbr — The router is not an ASBR.
The no form of the command enables the post-RFC1583 method of summary and external route calculation.
compatible-rfc1583 — RFC1583 compliance is enabled.
The no form of this command restores the default settings and re-enables IGP-LDP synchronization on all interfaces participating in the OSPF or IS-IS routing protocol and for which the ldp-sync-timer is configured.
export policy-name [policy-name…]
The no form of the command removes all policies from the configuration.
no export — No export route policies specified.
The no form of the command removes the parameters from the configuration.
The limit value specifies the maximum number of non-default AS-external-LSA entries that can be stored in the link-state database (LSDB). Placing a limit on the non-default AS-external-LSAs in the LSDB protects the router from receiving an excessive number of external routes that consume excessive memory or CPU resources. If the number of routes reach or exceed the
limit, the table is in an overflow state.
When in an overflow state, the router will not originate any new AS-external-LSAs. In fact, it withdraws all the self-originated non-default external LSAs.
The interval specifies the amount of time to wait after an overflow state before regenerating and processing non-default AS-external-LSAs. The waiting period acts like a dampening period preventing the router from continuously running Shortest Path First (SPF) calculations caused by the excessive number of non-default AS-external LSAs.
The external-db-overflow must be set identically on all routers attached to any regular OSPF area. OSPF stub areas and not-so-stubby areas (NSSAs) are excluded.
The no form of the command disables limiting the number of non-default AS-external-LSA entries.
no external-db-overflow — No limit on non-default AS-external-LSA entries.
The no form of the command reverts to the default value.
external-preference 150 — OSPF external routes have a default preference of 150.
The no form of the command disables graceful restart and removes all graceful restart configurations in the OSPF instance.
When graceful-restart is enabled, the router can be a helper (meaning that the router is helping a neighbor to restart) or be a restarting router or both. The
router supports only helper mode. This facilitates the graceful restart of neighbors but will not act as a restarting router (meaning that the
routerwill not help the neighbors to restart).
The no helper-disable command enables helper support and is the default when graceful-restart is enabled.
import policy-name [policy-name...(up to 5 max)]
[no
] loopfree-alternate [remote-lfa [max-pq-cost
value]]
The user enables the remote LFA next-hop calculation by the IGP LFA SPF by appending the remote-lfa option. When this option is enabled in an IGP instance, SPF performs the remote LFA additional computation following the regular LFA next-hop calculation when the latter resulted in no protection for one or more prefixes which are resolved to a given interface.
If the user excluded the interface from LFA using the command loopfree-alternate-exclude, the LFA policy, if applied to the interface, has no effect.
The no form deletes the mapping of a route next-hop policy template to an OSPF or IS-IS interface.
The default action of the loopfree-alternate-exclude command, when not explicitly specified by the user in the prefix policy, is a “reject”. Thus, regardless if the user did or did not explicitly add the statement “default-action reject” to the prefix policy, a prefix that did not match any entry in the policy will be accepted into LFA SPF.
The no form deletes the exclude prefix policy.
The no form of the command disables the submission of routes into the multicast RTM.
If the overload command is encountered during the execution of an
overload-on-boot command then this command takes precedence. This could occur as a result of a saved configuration file where both parameters are saved. When the file is saved by the system the
overload-on-boot command is saved after the
overload command.
However, when
overload-on-boot is configured under OSPF with no timeout value configured, the router will remain in overload state indefinitely after a reboot.
Use the no form of this command to return to the default. When the
no overload command is executed, the overload state is terminated regardless of the reason the protocol entered overload state.
[no
] overload-include-ext-2
[no
] overload-include-stub
The no overload command does not affect the
overload-on-boot function.
The no form of the command removes the overload-on-boot functionality from the configuration.
The no form of the command reverts to the default value.
preference 10 — OSPF internal routes have a preference of 10.
The default reference-bandwidth is
100,000,000 Kbps or 100 Gbps, so the default auto-cost metrics for various link speeds are as as follows:
The reference-bandwidth command assigns a default cost to the interface based on the interface speed. To override this default cost on a particular interface, use the
metric metric command in the
config>router>ospf>area>interface ip-int-name context.
The no form of the command reverts the reference-bandwidth to the default value.
reference-bandwidth 100000000 — Reference bandwidth of 100 Gbps.
The no form of
rib-priority command disables RIB prioritization at the associated level.
rtr-adv-lsa-limit limit [log-only] [threshold
percent] [overload-timeout {
seconds | forever}]
The no form of the command removes the rtr-adv-lsa-limit.
The default value for the base instance is inherited from the configuration in the config>router context. If the router ID in the t
config>router context is not configured, the following applies:
This is a required command when configuring multiple instances and the instance being configured is not the base instance.
To force the new router ID to be used, issue the shutdown and
no shutdown commands for the instance, or reboot the entire router.
The no form of the command to reverts to the default value.
The no form of this command, disables this capability.
This command instructs IS-IS or OSPF to include RSVP LSPs originating on this node and terminating on the router-id of a remote node as direct links with a metric equal to the operational metric provided by MPLS. Note that Dijkstra will always use the IGP metric to build the SPF tree and the LSP metric value does not update the SPF tree calculation. During the IP reach to determine the reachability of nodes and prefixes, LSPs are then overlaid and the LSP metric is used to determine the subset of paths which are equal lowest cost to reach a node or a prefix. If the user enabled the
relative-metric option for this LSP, IGP will apply the shortest IGP cost between the endpoints of the LSP plus the value of the offset, instead of the LSP operational metric, when computing the cost of a prefix which is resolved to the LSP.
When rsvp-shortcut is enabled at the IGP instance level, all RSVP LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in configure>router>mpls>lsp>to, corresponds to a router-id of a remote node. RSVP LSPs with a destination corresponding to an interface address or any other loopback interface address of a remote node are automatically not considered by IS-IS or OSPF. The user can, however, exclude a specific RSVP LSP from being used as a shortcut for resolving IGP routes by entering the
config>router>mpls>lsp>no igp-shortcut command.
This feature provides IGP with the capability to populate the multicast RTM with the prefix IP next-hop when both the rsvp-shortcut and the
multicast-import options are enabled in IGP. The unicast RTM can still make use of the tunnel next-hop for the same prefix. This change is made possible with the enhancement by which SPF keeps track of both the direct first hop and the tunneled first hop of a node which is added to the Dijkstra tree.
The no form of this command disables the resolution of IGP routes using RSVP shortcuts.
There are two mutually exclusive modes of operation for the prefix SID range on the router. In the global mode of operation, the user configures the global value and this IGP instance will assume the start label value is the lowest label value in the SRGB and the prefix SID index range size equal to the range size of the SRGB. Once one IGP instance selected the global option for the prefix SID range, all IGP instances on the system will be restricted to do the same. The user must shutdown the segment routing context and delete the
prefix-sid-range command in all IGP instances in order to change the SRGB. Once the SRGB is changed, the user must re-enter the
prefix-sid-range command again. The SRGB range change will be failed if an already allocated SID index/label goes out of range.
Cfg_SR_MTU is the MTU configured by the user for all SR tunnels within a given IGP instance using the above CLI. If no value was configured by the user, the SR tunnel MTU will be fully determined by the IGP interface calculation explained next.
IGP_Tunnel_MTU is the minimum of the IS-IS or OSPF interface MTU among all the ECMP paths or among the primary and LFA backup paths of this SR tunnel.
The parameters (link,
area, and
as) control the scope of the capabilies advertisements.
The no form of the command disables the the super-backbone functionality.
The no incremental-spf-wait form of the command resets the timer value back to the default value.
It is recommended that the neighbors configured (lsa-generate)
lsa-second-wait interval is equal or greater then the
lsa-arrival timer configured here.
Use the no form of this command to return to the default.
lsa-generate max-lsa-wait [lsa-initial-wait [lsa-second-wait]]
Configuring the lsa-arrival interval to equal or less than the
lsa-second-wait interval configured in the
lsa-generate command is recommended.
Use the no form of this command to return to the default.
The no redistribute-delay form of the command resets the timer value back to the default value.
spf-wait max-spf-wait [
spf-initial-wait [
spf-second-wait]]
This command defines the maximum interval between two consecutive SPF calculations in milliseconds. Timers that determine when to initiate the first, second, and subsequent SPF calculations after a topology change occurs can be controlled with this command. Subsequent SPF runs (if required) will occur at exponentially increasing intervals of the spf-second-wait interval. For example, if the
spf-second-wait interval is 1000, then the next SPF will run after 2000 milliseconds, and then next SPF will run after 4000 milliseconds, etc., until it reaches the
spf-wait value. The SPF interval will stay at the
spf-wait value until there are no more SPF runs scheduled in that interval. After a full interval without any SPF runs, the SPF interval will drop back to
spf-initial-wait.
Use the no form of this command to return to the default.
The no form of the command disables traffic engineered route calculations.
no traffic-engineering — Traffic engineered route calculations is disabled.
[no
] unicast-import-disable
This command creates the context to configure an OSPF or OSPF3 area.
An area is a collection of network segments within an AS that have been administratively grouped together. The area ID can be specified in dotted decimal notation or as a 32-bit decimal integer.
The no form of the command deletes the specified area from the configuration. Deleting the area also removes the OSPF configuration of all the interfaces, virtual-links, and address-ranges etc., that are currently assigned to this area.
no area — No OSPF areas are defined.
area-range ip-prefix/
mask [advertise
| not-advertise
]
The no form of the command deletes the range (non) advertisement.
no area-range — No range of addresses are defined.
In the NSSA context, the
option specifies that the range applies to external routes (via type-7 LSAs) learned within the NSSA when the routes are advertised to other areas as type-5 LSAs.
area-range ipv6-prefix/prefix-length [advertise
| not-advertise
]
The no form of the command deletes the range (non) advertisement.
no area-range — No range of addresses are defined.
In the NSSA context, the
option specifies that the range applies to external routes (via type-7 LSAs) learned within the NSSA when the routes are advertised to other areas as type-5 LSAs.
The no form of this command removes this option.
The no form of the command reverts to the default value.
[no
] loopfree-alternate-exclude
The no form of this command re-instates the default value for this command.
The no form of this command disables OSPF LSA filtering (normal operation).
This command creates the context to configure an OSPF or OSPF3 Not So Stubby Area (NSSA) and adds/removes the NSSA designation from the area.
The no form of the command removes the NSSA designation and configuration context from the area.
no nssa — The OSPF or OSPF3 area is not an NSSA.
The no form of the command disables origination of a default route.
no originate-default-route — A default route is not originated.
[no
] redistribute-external
NSSA or Not So Stubby Areas are similar to stub areas in that no external routes are imported into the area from other OSPF or OSPF3 areas. The major difference between a stub area and an NSSA is that the NSSA has the capability to flood external routes that it learns (providing it is an ASBR) throughout its area and via an Area Border Router to the entire OSPF or OSPF3 domain.
The no form of the command disables the default behavior to automatically redistribute external routes into the NSSA area from the NSSA ABR.
redistribute-external — External routes are redistributed into the NSSA.
This command enables access to the context to configure an OSPF or OSPF3 stub area and adds/removes the stub designation from the area.
The no form of the command removes the stub designation and configuration context from the area.
no stub — The area is not configured as a stub area.
The no form of the command disables sending summary route advertisements and, for stub areas, only the default route is advertised by the ABR.
summaries — Summary routes are advertised by the ABR into the stub area or NSSA.
The no form of the command disables advertising point-to-point interfaces as subnet routes meaning they are advertised as host routes.
advertise-subnet — Advertises point-to-point interfaces as subnet routes.
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.
The no form of the command removes the authentication.
no authentication — No authentication is defined.
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.
The no form of the command removes the authentication key.
no authentication-key — No authentication key is defined.
Both simple password and
message-digest authentication are supported.
The no form of the command disables authentication on the interface.
no authentication — No authentication is enabled on an interface.
[no
] bfd-enable
[remain-down-on-failure
]
The no form of this command removes BFD from the associated IGP protocol adjacency.
The no form of the command reverts to the default value.
If the dead-interval configured applies to an interface, then all nodes on the subnet must have the same dead interval.
If the dead-interval configured applies to a virtual link, then the interval on both termination points of the virtual link must have the same dead interval.
Reducing the interval, in combination with an appropriate reduction in the associated dead-interval, allows for faster detection of link and/or router failures at the cost of higher processing costs.
The no form of this command reverts to the default value.
hello-interval 10 — A 10-second hello interval.
If the hello-interval configured applies to an interface, then all nodes on the subnet must have the same hello interval.
If the hello-interval configured applies to a virtual link, then the interval on both termination points of the virtual link must have the same hello interval.
[no
] interface
ip-int-name [secondary]
The no form of the 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 — No OSPF interfaces are defined.
The no form of the command reverts to the default value.
point-to-point if the physical interface is SONET.
broadcast if the physical interface is Ethernet or unknown.
The no form of the command removes the message digest key identified by the
key-id.
The keyid is expressed as a decimal integer.
The MD5 key. The key can be any alphanumeric string up to 16 characters in length.
The no form of the 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 — The metric is based on
reference-bandwidth setting and the link speed.
config>port>ethernet
config>port>sonet-sdh>path
config>port>tdm>t3-e3
config>port>tdm>t1-e1>channel-group
Use the no form of this command to revert to default.
no mtu — Uses the value derived from the MTU configured in the
config>port context.
By default, only interface addresses that are configured for OSPF will be advertised as OSPF interfaces. The passive parameter allows an interface to be advertised as an OSPF interface without running the OSPF protocol.
The no form of the command removes the passive property from the OSPF interface.
Service interfaces defined in config>router>service-prefix are passive.
The no form of the command reverts the interface priority to the default value.
The no form of this command reverts to the default interval.
The no form of
rib-priority command disables RIB prioritization at the associated level.
The no form of this command reverts to the default delay time
[no
] virtual-link
router-id transit-area area-id
The router-id specified in this command must be associated with the virtual neighbor. The transit area cannot be a stub area or a Not So Stubby Area (NSSA).
The no form of the command deletes the virtual link. (
Default: none specified)
