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.
The description command associates a text string with a configuration context to help identify the context in the configuration file.
The no form of the command removes any description string from the context.
The no form of the command disables the limit of multicast routes within a VRF context. Issue the
no form of the command only when the VPRN instance is shutdown.
The no form of the command disables the IGMP instance. To start or suspend execution of IGMP without affecting the configuration, use the
no shutdown command.
The no form of the command removes the IP address.
The no form of the command deletes the IGMP interface. The
shutdown command in the
config>router>igmp>interface context can be used to disable an interface without removing the configuration for the interface.
no interface — No interfaces are defined.
The no form of the command disables the IGMP router alert check option.
This command applies the referenced IGMP policy (filter) to a subscriber or a group-interface. An IGMP filter is also known as a black/white list and it is defined under the
configure>router>policy-options.
The no form of the command removes the policy association from the IGMP instance.
no import — No import policy specified.
The no form of the command removes the IP address.
The no form of the command disables the command.
The no form of the command disables the command.
The no form of the command reverts to the default.
The source command is mutually exclusive with the specification of individual sources for the same group.
Use the no form of the command to remove the source from the configuration.
Use the no form of the command to remove the starg entry from the configuration.
The no form of the command removes the source from the configuration.
The no form of the command removes the starg entry from the configuration.
Interface names are case-sensitive and must be unique within the group of defined IP interfaces defined for config router interface,
config service ies interface, and
config service ies subscriber-interface group-interface. Interface names must not be in the dotted decimal notation of an IP address. For example, the name “1.1.1.1” is not allowed, but “int-1.1.1.1” is allowed. Show commands for router interfaces use either the interface names or the IP addresses. Ambiguity can exist if an IP address is used as an IP address and an interface name. Duplicate interface names can exist in different router instances, although this is not recommended because it may be confusing.
The no form of the command removes the IP interface and all the associated configurations.
If the ip-int-name already exists, the context is changed to maintain that IP interface. If
ip-int-name does not exist, the interface is created and the context is changed to that interface for further command processing.
The apply-to command is first saved in the PIM configuration structure. Then, all subsequent commands either create new structures or modify the defaults as created by the apply-to command.
The no form of the command removes the assert-period from the configuration.
The no form of this command removes BFD from the associated IGP protocol adjacency.
The no form of the command disables SPT switchover for default MDT. On disable, PIM instance resets all MDTs and reinitiate setup.
The no form of the command removes the policy association from the instance.
no import join-policy
no import register-policy
The no form of the command disables the multicast balancing.
This command is mutually exclusive with the mc-ecmp-balance command in the same context.
The no form of the command disables the hash-based multicast balancing of traffic over ECMP links.
The no version of this command disables MoFRR for PIM interfaces.
The no form of this command reverts to the default value of the hello-interval.
The hello-multiplier in conjunction with the
hello-interval determines the holdtime for a PIM neighbor.
When the improved-assert command is enabled, the PIM assert process is done entirely in the control plane. The advantages are that it eliminates duplicate traffic forwarding to the LAN. It also improves performance since it removes the required interaction between the control and data planes.
NOTE: improved-assert is still fully interoperable with the draft-ietf-pim-sm-v2-new-xx, Protocol Independent Multicast - Sparse Mode (PIM-SM): Revised, and RFC 2362,
Protocol Independent Multicast-Sparse Mode (PIM-SM), implementations. However, there may be conformance tests that may fail if the tests expect control-data plane interaction in determining the assert winner. Disabling the
improved-assert command when performing conformance tests is recommended.
This command configures the option to join the P2MP LDP tree towards the multicast source. If p2mp-ldp-tree-join is enabled, a PIM multicast join received on an interface is processed to join the P2MP LDP LSP, using the in-band signaled P2MP tree for the same multicast flow. LDP P2MP tree is set up towards the multicast source. The route to the multicast node source is looked up from the RTM. The next-hop address for the route to source is set as the root of LDP P2MP tree.
The no form of the command disables joining the P2MP LDP tree for IPv4 or IPv6 or for both (if both or none is specified).
The no form of the command restores the default values.
This command configures the bootstrap priority of the router. The RP is sometimes called the bootstrap router. The priority determines if the router is eligible to be a bootstrap router. In the case of a tie, the router with the highest IP address is elected to be the bootstrap router.
By enabling sticky-dr on this interface, it will continue to act as the DR for the LAN even after the old DR comes back up.
The no form of the command disables sticky-dr operation on this interface.
This command enables the context to configure rendezvous point (RP) parameters. The address of the root of the group’s shared multicast distribution tree is known as its RP. Packets received from a source upstream and join messages from downstream routers rendezvous at this router.
The no form of the command removes the anycast instance from the configuration.
The no form of the command disables auto RP.
The no form of the command removes an entry from the list.
Entries can be created or destroyed. If no IP addresses are configured in the config>router>pim>rp>static>address context, then the multicast group to RP mapping is derived from the RP-set messages received from the Bootstrap Router.
The detailed protocol specification is defined in RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. This RFC describes a multicast address allocation policy in which the address of the RP is encoded in the IPv6 multicast group address, and specifies a PIM-SM group-to-RP mapping to use the encoding, leveraging, and extending unicast-prefix-based addressing. This mechanism not only provides a simple solution for IPv6 inter-domain ASM but can be used as a simple solution for IPv6 intra-domain ASM with scoped multicast addresses as well. It can also be used as an automatic RP discovery mechanism in those deployment scenarios that would have previously used the Bootstrap Router protocol (BSR).
The no form of the command disables embedded RP.
This command configures the address ranges of the multicast groups for this router. When there are parameters present, the command configures the SSM group ranges for IPv6 addresses and netmasks.
The no form of the command removes the group-prefix from the configuration.
When the infinity keyword is specified, no switchover will occur at any time, regardless of the traffic level is detected. The threshold, in kilobits per second (KBPS), value is 4294967295.
