Table Of Contents

ipv6 ospf dead-interval

ipv6 ospf demand-circuit

ipv6 ospf encryption

ipv6 ospf flood-reduction

ipv6 ospf hello-interval

ipv6 ospf mtu-ignore

ipv6 ospf name-lookup

ipv6 ospf neighbor

ipv6 ospf network

ipv6 ospf priority

ipv6 ospf retransmit-interval

ipv6 ospf transmit-delay

ipv6 pim

ipv6 pim accept-register

ipv6 pim bsr announced rp

ipv6 pim bsr border

ipv6 pim bsr candidate bsr

ipv6 pim bsr candidate rp

ipv6 pim dr-priority

ipv6 pim hello-interval

ipv6 pim join-prune-interval

ipv6 pim neighbor-filter list

ipv6 pim rp embedded

ipv6 pim rp-address

ipv6 pim spt-threshold infinity

ipv6 policy route-map

ipv6 port-map

ipv6 prefix-list

ipv6 prefix-list sequence-number

ipv6 redirects

ipv6 rip default-information

ipv6 rip enable

ipv6 rip metric-offset

ipv6 rip summary-address

ipv6 route

ipv6 route static bfd

ipv6 router eigrp

ipv6 router isis

ipv6 router nemo

ipv6 router ospf

ipv6 router rip

ipv6 source-route

ipv6 split-horizon eigrp

ipv6 ospf dead-interval

To set the time period for which hello packets must not be seen before neighbors declare the router down, use the ipv6 ospf dead-interval command in interface configuration mode. To return to the default time, use the no form of this command.

ipv6 ospf dead-interval seconds

no ipv6 ospf dead-interval

Syntax Description

seconds

Specifies the interval (in seconds). The value must be the same for all nodes on the network.

Command Default

Four times the interval set by the ipv6 ospf hello-interval command

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

The interval is advertised in router hello packets. This value must be the same for all routers and access servers on a specific network.

Examples

The following example sets the Open Shortest Path First (OSPF) dead interval to 60 seconds:

interface ethernet 1

 ipv6 ospf dead-interval 60

Related Commands

Command	Description
ipv6 ospf hello-interval	Specifies the interval between hello packets that the Cisco IOS software sends on the interface.

ipv6 ospf demand-circuit

To configure Open Shortest Path First (OSPF) to treat the interface as an OSPF demand circuit, use the ipv6 ospf demand-circuit command in interface configuration mode. To remove the demand circuit designation from the interface, use the no form of this command.

ipv6 ospf demand-circuit

no ipv6 ospf demand-circuit

Syntax Description

This command has no arguments or keywords.

Command Default

The circuit is not a demand circuit.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

On point-to-point interfaces, only one end of the demand circuit must be configured with this command. Periodic hello messages are suppressed and periodic refreshes of link-state advertisements (LSAs) do not flood the demand circuit. This command allows the underlying data link layer to be closed when the topology is stable. In point-to-multipoint topology, only the multipoint end must configured with this command.

Examples

The following example sets the configuration for an ISDN on-demand circuit:

interface BRI0

 ipv6 ospf 1 area 1 

 ipv6 ospf demand-circuit

ipv6 ospf encryption

To specify the encryption type for an interface, use the ipv6 ospf encryption command in interface configuration mode. To remove the encryption type from an interface, use the no form of this command.

ipv6 ospf encryption {ipsec spi spi esp encryption-algorithm [[key-encryption-type] key] authentication-algorithm [key-encryption-type] key | null}

no ipv6 ospf encryption ipsec spi spi

Syntax Description

ipsec	IP Security (IPSec).
spi spi	Security policy index (SPI) value. The spi value must be a number from 256 to 4294967295.
esp	Encapsulating security payload (ESP).
encryption-algorithm	Encryption algorithm to be used with ESP. The values can be any of the following: •aes-cdc—Enables AES-CDC encryption. •3des—Enables 3DES encryption. •des—Enables DES encryption. •null—ESP with no encryption.
key-encryption-type	(Optional) One of two values can be entered: •0—The key is not encrypted. •7—The key is encrypted.
key	(Optional) Number used in the calculation of the message digest. The number is 32 hex digits (16 bytes) long. The size of the key depends on the encryption algorithm used. Some algorithms, such as AES-CDC, allow the user to choose the size of the key.
authentication-algorithm	Encryption authentication algorithm to be used. The values can be one of the following: •md5—Enables message digest 5 (MD5). •sha1—Enables SHA-1.
null	Overrides area encryption.

Command Default

Authentication and encryption are not configured on an interface.

Command Modes

Interface configuration

Command History

Release	Modification
12.4(9)T	This command was introduced.

Usage Guidelines

When the ipv6 ospf encryption command is enabled, both authentication and encryption are enabled. However, when you use an encryption command such as area encryption, you may not also use an authentication command (such as area authentication or area virtual-link authentication) at the same time.

The user needs to ensure that the same policy (the SPI and the key) is configured on all of the interfaces on the link. SPI values may automatically be used by other client applications, such as tunnels.

The policy database is common to all client applications on a box. This means that two IPSec clients, such as Open Shortest Path First (OSPF) and a tunnel, cannot use the same SPI. Additionally, an SPI can be used only in one policy.

The null keyword is used to override existing area encryption. If area encryption is not configured, then it is not necessary to configure the interface with the ipv6 ospf encryption null command.

Examples

The following example specifies the encryption type for Ethernet interface 0/0. The IPSec SPI value is 1001, ESP is used with no encryption, and the authentication algorithm is SHA-1.

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 ospf encryption ipsec spi 1001 esp null sha1 
123456789A123456789B123456789C123456789D 

Related Commands

Command	Description
area authentication	Enables authentication for an OSPF area.
area encryption	Enables encryption for an OSPF area.
area virtual-link authentication	Enables authentication for virtual links in an OSPF area.
ipv6 ospf authentication	Specifies the authentication type for an interface.

ipv6 ospf flood-reduction

To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the ipv6 ospf flood-reduction command in interface configuration mode. To disable this feature, use the no form of this command.

ipv6 ospf flood-reduction

no ipv6 ospf flood-reduction

Syntax Description

This command has no arguments or keywords.

Command Default

This command is disabled.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

All routers supporting the Open Shortest Path First (OSPF) demand circuit are compatible and can interact with routers supporting flooding reduction.

Examples

The following example suppresses the flooding of unnecessary LSAs on serial interface 0:

interface serial 0

 ipv6 ospf flood-reduction

Related Commands

Command	Description
show ipv6 ospf interface	Displays OSPF-related interface information.
show ipv6 ospf neighbor	Displays OSPF-neighbor information on a per-interface basis.

ipv6 ospf hello-interval

To specify the interval between hello packets that the Cisco IOS software sends on the interface, use the ipv6 ospf hello-interval command in interface configuration mode. To return to the default time, use the no form of this command.

ipv6 ospf hello-interval seconds

no ipv6 ospf hello-interval

Syntax Description

seconds

Specifies the interval (in seconds). The value must be the same for all nodes on a specific network.

Command Default

The default interval is 10 seconds when using Ethernet and 30 seconds when using nonbroadcast.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

This value is advertised in the hello packets. The shorter the hello interval, the earlier topological changes will be detected, but more routing traffic will ensue. This value must be the same for all routers and access servers on a specific network.

Examples

The following example sets the interval between hello packets to 15 seconds:

interface ethernet 1

 ipv6 ospf hello-interval 15

Related Commands

Command	Description
ipv6 ospf dead-interval	Sets the time period for which hello packets must not have been seen before neighbors declare the router down.

ipv6 ospf mtu-ignore

To disable Open Shortest Path First (OSPF) maximum transmission unit (MTU) mismatch detection on receiving database descriptor (DBD) packets, use the ipv6 ospf mtu-ignore command in interface configuration mode. To reset to default, use the no form of this command.

ipv6 ospf mtu-ignore

no ipv6 ospf mtu-ignore

Syntax Description

This command has no arguments or keywords.

Command Default

OSPF MTU mismatch detection is enabled.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

OSPF checks whether neighbors are using the same MTU on a common interface. This check is performed when neighbors exchange DBD packets. If the receiving MTU in the DBD packet is higher then the IP MTU configured on the incoming interface, OSPF adjacency will not be established.

Examples

The following example disables MTU mismatch detection on receiving DBD packets:

interface serial 0/0

 ipv6 ospf mtu-ignore

ipv6 ospf name-lookup

To display Open Shortest Path First (OSPF) router IDs as Domain Naming System (DNS) names, use the ipv6 ospf name-lookup command in global configuration mode. To stop displaying OSPF router IDs as DNS names, use the no form of this command.

ipv6 ospf name-lookup

no ipv6 ospf name-lookup

Syntax Description

This command has no arguments or keywords.

Command Default

This command is disabled by default

Command Modes

Global configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

This command makes it easier to identify a router because the router is displayed by name rather than by its router ID or neighbor ID.

Examples

The following example configures OSPF to look up DNS names for use in all OSPF show EXEC command displays:

ipv6 ospf name-lookup

ipv6 ospf neighbor

To configure Open Shortest Path First (OSPF) routers interconnecting to nonbroadcast networks, use the ipv6 ospf neighbor command in interface configuration mode. To remove a configuration, use the no form of this command.

ipv6 ospf neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out]

no ipv6 ospf neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out]

Syntax Description

ipv6-address	Link-local IPv6 address of the neighbor. This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
priority number	(Optional) A number that indicates the router priority value of the nonbroadcast neighbor associated with the IPv6 prefix specified. The default is 0.
poll-interval seconds	(Optional) A number value that represents the poll interval time (in seconds). RFC 2328 recommends that this value be much larger than the hello interval. The default is 120 seconds (2 minutes). This keyword does not apply to point-to-multipoint interfaces.
cost number	(Optional) Assigns a cost to the neighbor, in the form of an integer from 1 to 65535. Neighbors with no specific cost configured will assume the cost of the interface, based on the ipv6 ospf cost command.
database-filter all out	(Optional) Filters outgoing link-state advertisements (LSAs) to an OSPF neighbor.

Command Default

No configuration is specified.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

X.25 and Frame Relay provide an optional broadcast capability that can be configured in the map to allow OSPF to run as a broadcast network. At the OSPF level you can configure the router as a broadcast network.

One neighbor entry must be included in the Cisco IOS software configuration for each known nonbroadcast network neighbor. The neighbor address must be a link-local address of the neighbor.

If a neighboring router has become inactive (hello packets have not been seen for the Router Dead Interval period), hello packets may need to be sent to the dead neighbor. These hello packets will be sent at a reduced rate called Poll Interval.

When the router first starts up, it sends only hello packets to those routers with nonzero priority, that is, routers that are eligible to become designated routers (DRs) and backup designated routers (BDRs). After the DR and BDR are selected, the DR and BDR will then start sending hello packets to all neighbors in order to form adjacencies.

The priority keyword does not apply to point-to-multipoint interfaces. For point-to-multipoint interfaces, the cost keyword and the number argument are the only options that are applicable. The cost keyword does not apply to nonbroadcast multiaccess (NBMA) networks.

Examples

The following example configures an OSPF neighboring router:

ipv6 ospf neighbor FE80::A8BB:CCFF:FE00:C01

ipv6 ospf network

To configure the OSPF network type to a type other than the default for a given medium, use the ipv6 ospf network command in interface configuration mode. To return to the default type, use the no form of this command.

ipv6 ospf network {broadcast | non-broadcast | {point-to-multipoint [non-broadcast] | point-to-point}}

no ipv6 ospf network

Syntax Description

broadcast	Sets the network type to broadcast.
non-broadcast	Sets the network type to nonbroadcast multiaccess (NBMA).
point-to-multipoint [non-broadcast]	Sets the network type to point-to-multipoint. The optional non-broadcast keyword sets the point-to-multipoint network to be nonbroadcast. If you use the non-broadcast keyword, the neighbor command is required.
point-to-point	Sets the network type to point-to-point.

Command Default

Default depends on the network type.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(15)XF	The point-to-multipint keyword was added to support the Virtual Multipoint Interfaces (VMI) and Mobile Adhoc Networking.
12.4(15)T	This command was integrated into Cisco IOS 12.4(15)T.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

NBMA Networks

Using this feature, you can configure broadcast networks as NBMA networks when, for example, routers in your network do not support multicast addressing. You can also configure NBMA networks (such as X.25, Frame Relay, and Switched Multimegabit Data Service [SMDS]) as broadcast networks. This feature saves you from needing to configure neighbors.

Configuring NBMA networks as either broadcast or nonbroadcast assumes that there are virtual circuits from every router to every router or fully meshed networks. However, the assumption is not true for other configurations, such as for a partially meshed network. In these cases, you can configure the OSPF network type as a point-to-multipoint network. Routing between two routers that are not directly connected will go through the router that has virtual circuits to both routers. You need not configure neighbors when using this feature.

Point-to-Multipoint Networks

OSPFv3 for IPv6 has two features related to point-to-multipoint networks. One feature applies to broadcast networks; the other feature applies to nonbroadcast networks:

•On point-to-multipoint, broadcast networks, you can use the neighbor command, and you must specify a cost to that neighbor.

•On point-to-multipoint, nonbroadcast networks, you must use the neighbor command to identify neighbors. Assigning a cost to a neighbor is optional.

Examples

OSPF Network as Broadcast Network Example

The following example sets your OSPF network as a broadcast network:

interface serial 0

 ipv6 enable

 ipv6 ospf 1 area 0

 ipv6 ospf network broadcast

 encapsulation frame-relay

OSPF Point-to-Multipoint Network with Broadcast Example

The following example illustrates a point-to-multipoint network with broadcast:

interface serial 0

 ipv6 enable

 ipv6 ospf 1 area 0

 encapsulation frame-relay

 ipv6 ospf cost 100

 ipv6 ospf network point-to-multipoint

 frame-relay map ipv6 2001:0DB1::A8BB:CCFF:FE00:C01 broadcast

 frame-relay map ipv6 2001:0DB1B:CCFF:FE00:C02 broadcast

 frame-relay local-dlci 200

 ipv6 ospf neighbor 2001:0DB1B:CCFF:FE00:C01

 ipv6 ospf neighbor2001:0DB1B:CCFF:FE00:C02

Related Commands

Command	Description
frame-relay map	Defines mapping between a destination protocol address and the DLCI used to connect to the destination address.
ipv6 ospf neighbor	Configures OSPF routers interconnecting to nonbroadcast networks.
x25 map	Sets up the LAN protocols-to-remote host mapping.

ipv6 ospf priority

To set the router priority, which helps determine the designated router for this network, use the ipv6 ospf priority command in interface configuration mode. To return to the default value, use the no form of this command.

ipv6 ospf priority number-value

no ipv6 ospf priority number-value

Syntax Description

number-value

A number value that specifies the priority of the router. The range is from 0 to 255.

Command Default

The router priority is 1.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

When two routers attached to a network both attempt to become the designated router, the one with the higher router priority takes precedence. If there is a tie, the router with the higher router ID takes precedence. A router with a router priority set to zero is ineligible to become the designated router or backup designated router. Router priority is configured only for interfaces to multiaccess networks (in other words, not to point-to-point networks).

This priority value is used when you configure Open Shortest Path First (OSPF) for nonbroadcast networks using the ipv6 ospf neighbor command.

Examples

The following example sets the router priority value to 4:

interface ethernet 0

 ipv6 ospf priority 4

Related Commands

Command	Description
ipv6 ospf network	Configures the OSPF network type to a type other than the default for a given medium.
ipv6 ospf neighbor	Configures OSPF routers interconnecting to nonbroadcast networks.

ipv6 ospf retransmit-interval

To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the interface, use the ipv6 ospf retransmit-interval command in interface configuration mode. To return to the default value, use the no form of this command.

ipv6 ospf retransmit-interval seconds

no ipv6 ospf retransmit-interval

Syntax Description

seconds

Time (in seconds) between retransmissions. It must be greater than the expected round-trip delay between any two routers on the attached network. The range is from 1 to 65535 seconds. The default is 5 seconds.

Command Default

The default is 5 seconds.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

When a router sends an LSA to its neighbor, it keeps the LSA until it receives back the acknowledgment message. If the router receives no acknowledgment, it will resend the LSA.

The setting of this parameter should be conservative, or needless retransmission will result. The value should be larger for serial lines and virtual links.

Examples

The following example sets the retransmit interval value to 8 seconds:

interface ethernet 2

 ipv6 ospf retransmit-interval 8

ipv6 ospf transmit-delay

To set the estimated time required to send a link-state update packet on the interface, use the ip ospf transmit-delay command in interface configuration mode. To return to the default value, use the no form of this command.

ipv6 ospf transmit-delay seconds

no ipv6 ospf transmit-delay

Syntax Description

seconds

Time (in seconds) required to send a link-state update. The range is from 1 to 65535 seconds. The default is 1 second.

Command Default

The default is 1 second.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(24)S	This command was introduced.
12.2(15)T	This command was integrated into Cisco IOS Release 12.2(15)T.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

Link-state advertisements (LSAs) in the update packet must have their ages incremented by the amount specified in the seconds argument before transmission. The value assigned should take into account the transmission and propagation delays for the interface.

If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. This setting has more significance on very low-speed links.

Examples

The following example sets the retransmit delay value to 3 seconds:

interface ethernet 0

 ipv6 ospf transmit-delay 3

ipv6 pim

To reenable IPv6 Protocol Independent Multicast (PIM) on a specified interface, use the ipv6 pim command in interface configuration mode. To disable PIM on a specified interface, use the no form of the command.

ipv6 pim

no ipv6 pim

Syntax Description

This command has no arguments or keywords.

Command Default

PIM is automatically enabled on every interface.

Command Modes

Interface configuration

Command History

Release	Modification
12.3(2)T	This command was introduced.
12.2(18)S	This command was integrated into Cisco IOS Release 12.2(18)S.
12.0(26)S	This command was integrated into Cisco IOS Release 12.0(26)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG	This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

After a user has enabled the ipv6 multicast-routing command, PIM is enabled to run on every interface. Because PIM is enabled on every interface by default, use the no form of the ipv6 pim command to disable PIM on a specified interface. When PIM is disabled on an interface, it does not react to any host membership notifications from the Multicast Listener Discovery (MLD) protocol.

Examples

The following example turns off PIM on Fast Ethernet interface 1/0:

Router(config)# interface FastEthernet 1/0

Router(config-if)# no ipv6 pim 

Related Commands

Command	Description
ipv6 multicast-routing	Enables multicast routing using PIM and MLD on all IPv6-enabled interfaces of the router and enables multicast forwarding.

ipv6 pim accept-register

To accept or reject registers at the rendezvous point (RP), use the ipv6 pim accept-register command in global configuration mode. To return to the default value, use the no form of this command.

ipv6 pim accept-register {list access-list | route-map map-name}

no ipv6 pim accept-register {list access-list | route-map map-name}

Syntax Description

list access-list	Defines the access list name.
route-map map-name	Defines the route map.

Command Default

All sources are accepted at the RP.

Command Modes

Global configuration

Command History

Release	Modification
12.0(26)S	This command was introduced.
12.3(4)T	This command was integrated into Cisco IOS Release 12.3(4)T.
12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG	This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

Use the ipv6 pim accept-register command to configure a named access list or route map with match attributes. When the permit conditions as defined by the access-list and map-name arguments are met, the register message is accepted. Otherwise, the register message is not accepted, and an immediate register-stop message is returned to the encapsulating designated router.

Examples

The following example shows how to filter on all sources that do not have a local multicast Border Gateway Protocol (BGP) prefix:

ipv6 pim accept-register route-map reg-filter

route-map reg-filter permit 20

 match as-path 101

ip as-path access-list 101 permit

ipv6 pim bsr announced rp

To announce scope-to-rendezvous point (RP) mappings directly from the bootstrap router (BSR) instead of learning them from candidate RPs, use the ipv6 pim bsr announced rp command in global configuration mode. To reset the command to the default values, use the no form of this command.

ipv6 pim bsr announced rp ipv6-address [group-list access-list-name] [priority priority-value] [bidir] [scope scope-value]

no ipv6 pim bsr announced rp

Syntax Description

ipv6-address	The IPv6 address of each RP to be announced, configured on the BSR. This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
group-list	(Optional) List of group prefixes to be associated with the configured RP and added to the BSR RP cache. The group prefixes defined by the access-list-name argument are added to the BSR RP cache. If a group prefix in the access list is denied, however, it is not included in the RP cache.
access-list-name	(Optional) Name of the IPv6 access list containing group prefixes that will be added to the BSR RP cache. Names cannot contain a space or quotation mark, or begin with a numeral.
priority	(Optional) Priority of the RP to be announced.
priority-value	(Optional) Integer from 0 through 192. The RP with the larger priority is preferred. If the priority values are the same, the router with the larger IPv6 address is the RP. The default value is 192 and is not NVgened.
bidir	(Optional) RP is advertised as the C-RP for the group-list access-list-name keyword and argument in the bidirectional range.
scope	(Optional) If the scope keyword is used, the command will have an effect only if it is configured on the BSR with the same scope. The RP is associated with groups ranges belonging to the configured scope.
scope-value	(Optional) Integer from 3 through 15.

Command Default

Scope-to-RP mappings are not announced directly from the BSR.

Command Modes

Global configuration

Command History

Release	Modification
12.4(2)T	This command was introduced.

Usage Guidelines

IPv6 BSR routers can be statically configured to announce scope-to-RP mappings directly instead of learning them from candidate-RP messages. A user might want to configure a BSR router to announce scope-to-RP mappings so that an RP that does not support BSR is imported into the BSR. Enabling this feature also allows an RP positioned outside the enterprise's BSR domain to be learned by configuring the known remote RP on the local candidate BSR routers.

Announcing RP mappings statically from the BSR without having to listen to candidate RP messages is useful in several cases:

•If the RP address never changes because there is only a single RP or the group range uses an anycast RP, it may be less complex to configure the RP address announcement statically on the candidate BSRs.

•If the RP address is a virtual RP address (possible with bidirectional Protocol Independent Multicast [PIM]), it cannot be learned by the BSR from a candidate RP itself. Instead, it must be configured as an announced RP on the candidate BSRs.

•If an RP itself does not support BSR, the ipv6 pim bsr announced rp command allows the RP to be imported into the BSR.

•If an RP is positioned outside an enterprise's BSR domain (which is limited by the ipv6 pim bsr border command), then it cannot be learned because the messages from the remote BSR are filtered. Instead, the RP can be learned by configuring the known remote RP using the ipv6 pim bsr announced rp command on the local candidate BSR routers.

The group prefixes defined by the access-list-name argument are also added to the BSR RP cache. If a group prefix in the access list is denied, however, it is not included in the RP cache.

If the priority priority-value keyword and argument are used, then the announced RP (A-RP) is added as a candidate RP with the specified priority. The default for the priority-value argument is 192, and it is not NVgened. If the scope scope-value keyword and argument are specified, then the RP will be added as C-RP only on the elected BSR for the specified scope.

If the bidir keyword is used, the group range is used for bidirectional shared-tree forwarding; otherwise, it is used for sparse mode forwarding. A single ipv6-address argument can be configured to be the RP for either bidir or sparse mode for a group access list. However, this argument should be used only if consistent RP selection is possible throughout the network.

The announced BSR mappings are announced only by the currently elected BSR.

The announced BSR mappings are always included in the BSR messages and are not suppressed by other received candidate-RP announcements.

You can use unicast PIM or BSR message filtering on the BSR to inhibit learning unwanted dynamic candidate-RP mappings.

Examples

The following example configures the IPv6 address 2001:0DB8:3000:3000::42 to be advertised in the BSM as the candidate RP, with a priority of 0:

Router(config)# ipv6 pim bsr announced rp 2001:0DB8:3000:3000::42 priority 0

The following example configures the IPv6 address 2001:0DB8:1:1:1 to be advertised in the BSM as the candidate RP for scope 6 for the group ranges specified in the access list named list1:

Router(config)# ipv6 pim bsr announced rp 2001:0DB8:1:1:1 group-list list1 scope 6

Related Commands

Command	Description
ipv6 pim bsr border	Configures a border for all BSMs of any scope on a specified interface.
ipv6 pim bsr candidate bsr	Configures a router to be a candidate BSR.
ipv6 pim bsr candidate rp	Configures the candidate RP to send PIM RP advertisements to the BSR.

ipv6 pim bsr border

To configure a border for all bootstrap message (BSMs) of any scope on a specified interface, use the ipv6 pim bsr border command in interface configuration mode. To remove the border, use the no form of this command.

ipv6 pim bsr border

no ipv6 pim bsr border

Syntax Description

This command has no argument or keywords.

Command Default

No border is configured.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(28)S	This command was introduced.

12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.
12.3(11)T	This command was integrated into Cisco IOS Release 12.3(11)T.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG	This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

The ipv6 pim bsr border command is used to configure a border to all global and scoped BSMs. The command filters incoming or outgoing BSMs, preventing the BSMs from being forwarded or accepted on the interface on which the ipv6 pim bsr border command is configured.

Examples

The following example configures a BSR border on Ethernet interface 1/0:

Router(config)# interface Ethernet1/0

 Router(config-if)# ipv6 pim bsr border

 Router(config-if)# end

Router# show running-config interface e1/0

 Building configuration...

 Current configuration :206 bytes

 !

 interface Ethernet1/0

 ipv6 address 2:2:2::2/64

 ipv6 enable

 ipv6 rip test enable

 ipv6 pim bsr border

 no cdp enable

 end

Related Commands

Command	Description
ipv6 pim bsr candidate bsr	Configures a router as a candidate BSR.
ipv6 pim bsr candidate rp	Sends PIM RP advertisements to the BSR.

ipv6 pim bsr candidate bsr

To configure a router to be a candidate bootstrap router (BSR), use the ipv6 pim bsr candidate bsr command in global configuration mode. To remove this router as a candidate BSR, use the no form of this command.

ipv6 pim bsr candidate bsr ipv6-address [hash-mask-length] [priority priority-value]

no ipv6 pim bsr candidate bsr ipv6-address [hash-mask-length] [priority priority-value]

Syntax Description

ipv6-address	The IPv6 address of the router to be configured as a candidate BSR. This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
hash-mask-length	(Optional) The length (in bits) of the mask to use in the BSR hash function. The default value is 126.
priority	(Optional) Priority of the candidate BSR.
priority-value	(Optional) Integer from 0 through 192. The BSR with the larger priority is preferred. If the priority values are the same, the router with the larger IPv6 address is the BSR. The default value is 0.
scope	(Optional) BSR will originate bootstrap messages (BSMs), including the group range associated with the scope, and accept candidate RP (C-RP) announcements only if they are for groups that belong to the given scope.

Command Default

Router is not enabled as a BSR.

Command Modes

Global configuration

Command History

Release	Modification
12.0(28)S	This command was introduced.
12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.
12.3(11)T	This command was integrated into Cisco IOS Release 12.3(11)T.
12.4	The scope keyword and scope-value argument are no longer available in syntax.
12.4(2)T	This command was integrated into Cisco IOS Release 12.4(2)T.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(25)SG	This command was integrated into Cisco IOS Release 12.2(25)SG.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH	This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

The ipv6 pim bsr candidate bsr command is used to configure a router as a candidate BSR. When a router is configured, it will participate in BSR election. If elected BSR, this router will periodically originate BSR messages advertising the group-to-RP mappings it has learned through candidate-RP-advertisement messages.

If the scope keyword is enabled, the BSR will originate BSMs, including the group range associated with the scope, and accept C-RP announcements only if they are for groups that belong to the given scope. If no scope is configured, all scopes are