Cisco IOS IPv6 Command Reference

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

Command Default

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

Command Modes

Interface configuration

Command History

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.

When the ospfv3 dead-interval command is configured with the process-id argument, it overwrites the ipv6 dead-interval configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

Examples

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

interface ethernet 1

 ipv6 ospf dead-interval 60

Related Commands

ipv6 ospf demand-circuit

To configure Open Shortest Path First version 3 (OSPF) to treat the interface as an OSPFv3 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

Usage Guidelines

When the ospfv3 demand-circuit command is configured with the process-id argument, it overwrites the ipv6 ospf demand-circuit configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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

Related Commands

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

Command Default

Authentication and encryption are not configured on an interface.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ipv6 ospf encryption command is enabled, both authentication and encryption are enabled.

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 version 3 (OSPFv3) 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

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

Usage Guidelines

When the ospfv3 flood-reduction command is configured with the process-id argument, it overwrites the ipv6 ospf flood-reduction configuration if OSPFv3 was attached to the interface using the ipv6 ospf flood-reduction command.

All routers supporting the Open Shortest Path First version 3 (OSPFv3) 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

ipv6 ospf hello-interval

To specify the interval between hello packets that the Cisco IOS software sends on the Open Shortest Path First version 3 (OSPFv3) 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

Command Default

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

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 hello-interval command is configured with the process-id argument, it overwrites the ipv6 ospf hello-interval configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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

ipv6 ospf mtu-ignore

To disable Open Shortest Path First version 3 (OSPFv3) 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

OSPFv3 MTU mismatch detection is enabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 mtu-ignore command is configured with the process-id argument, it overwrites the ipv6 ospf mtu-ignore configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

OSPFv3 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, OSPFv3 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

Related Commands

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

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

Command Default

No configuration is specified.

Command Modes

Interface configuration

Command History

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 Open Shortest Path First version 3 (OSPFv3) 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

Command Default

Default depends on the network type.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 network command is configured with the process-id argument, it overwrites the ipv6 ospf network configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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 OSPFv3 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

OSPFv3 Network as Broadcast Network Example

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

interface serial 0

 ipv6 enable

 ipv6 ospf 1 area 0

 ipv6 ospf network broadcast

 encapsulation frame-relay

OSPFv3 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

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

Command Default

The router priority is 1.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 priority command is configured with the process-id argument, it overwrites the ipv6 ospf priority configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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 version 3 (OSPFv3) 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

ipv6 ospf retransmit-interval

To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the Open Shortest Path First version 3 (OSPFv3) 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

Command Default

The default is 5 seconds.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 retransmit-interval command is configured with the process-id argument, it overwrites the ipv6 ospf retransmit-interval configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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

Related Commands

ipv6 ospf transmit-delay

To set the estimated time required to send a link-state update packet on the Open Shortest Path First version 3 (OSPFv3) 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

Command Default

The default is 1 second.

Command Modes

Interface configuration

Command History

Usage Guidelines

When the ospfv3 transmit-delay command is configured with the process-id argument, it overwrites the ipv6 ospf transmit-delay configuration if OSPFv3 was attached to the interface using the ipv6 ospf area command.

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

Related Commands

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

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

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 [vrf vrf-name] accept-register {list access-list | route-map map-name}

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

Syntax Description

Command Default

All sources are accepted at the RP.

Command Modes

Global configuration

Command History

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 candidate rp

To configure the candidate rendezvous point (RP) to send Protocol Independent Multicast (PIM) RP advertisements to the bootstrap router (BSR), use the ipv6 pim bsr candidate rp command in global configuration mode. To disable PIM RP advertisements to the BSR, use the no form of this command.

ipv6 pim [vrf vrf-name] bsr candidate rp ipv6-address [group-list access-list-name] [priority priority-value] [interval seconds] [scope scope-value] [bidir]

no ipv6 pim [vrf vrf-name] bsr candidate rp ipv6-address [group-list access-list-name] [priority priority-value] [interval seconds] [scope scope-value] [bidir]

Syntax Description

Command Default

Router is not enabled as a candidate RP.
If no scope is configured, all scopes are advertised.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the ipv6 pim bsr candidate rp command to send PIM RP advertisements to the BSR.

The group prefixes defined by the access-list-name argument will also be advertised in association with the RP address. If a group prefix in the access list is denied, it will not be included in the C-RP advertisement.

If the priority priority-value keyword and argument are specified, then the router will announce itself to be a candidate RP with the specified priority.

If the scope keyword is used, the router advertises itself as the C-RP only to the BSR for the specified scope. If the group-list keyword is specified along with the scope, then only prefixes in the access-list-name argument with the same scope as the scope configured will be advertised. If no scope is configured, all scopes are advertised.

Examples

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

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

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

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

Related Commands

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

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

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 [vrf vrf-name] bsr candidate bsr ipv6-address [hash-mask-length] [priority priority-value]

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

Syntax Description

Command Default

Router is not enabled as a BSR.

Command Modes

Global configuration

Command History

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 used.

Examples

The following example configures the router with the IPv6 address 2001:0DB8:3000:3000::42 as the candidate BSR, with a hash mask length of 124 and a priority of 10:

ipv6 pim bsr candidate bsr 2001:0DB8:3000:3000::42 124 priority 10

Related Commands

ipv6 pim bsr candidate rp

To configure the candidate rendezvous point (RP) to send Protocol Independent Multicast (PIM) RP advertisements to the bootstrap router (BSR), use the ipv6 pim bsr candidate rp command in global configuration mode. To disable PIM RP advertisements to the BSR, use the no form of this command.

ipv6 pim [vrf vrf-name] bsr candidate rp ipv6-address [group-list access-list-name] [priority priority-value] [interval seconds] [scope scope-value] [bidir]

no ipv6 pim [vrf vrf-name] bsr candidate rp ipv6-address [group-list access-list-name] [priority priority-value] [interval seconds] [scope scope-value] [bidir]

Syntax Description

Command Default

Router is not enabled as a candidate RP.
If no scope is configured, all scopes are advertised.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the ipv6 pim bsr candidate rp command to send PIM RP advertisements to the BSR.

The group prefixes defined by the access-list-name argument will also be advertised in association with the RP address. If a group prefix in the access list is denied, it will not be included in the C-RP advertisement.

If the priority priority-value keyword and argument are specified, then the router will announce itself to be a candidate RP with the specified priority.

If the scope keyword is used, the router advertises itself as the C-RP only to the BSR for the specified scope. If the group-list keyword is specified along with the scope, then only prefixes in the access-list-name argument with the same scope as the scope configured will be advertised. If no scope is configured, all scopes are advertised.

Examples

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

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

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

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

Related Commands

ipv6 pim dr-priority

To configure the designated router (DR) priority on a Protocol Independent Multicast (PIM) router, use the ipv6 pim dr-priority command in interface configuration mode. To restore the default value, use the no form of this command.

ipv6 pim dr-priority value

no ipv6 pim dr-priority

Syntax Description

Command Default

Default value is 1.

Command Modes

Interface configuration

Command History

Usage Guidelines

The ipv6 pim dr-priority command configures the neighbor priority used for PIM DR election. The router with the highest DR priority on an interface becomes the PIM DR. If several routers have the same priority, then the router with the highest IPv6 address on the interface becomes the DR.

If a router does not include the DR priority option in its hello messages, then the router is considered to be the highest-priority router and becomes the DR. If several routers do not include the DR priority option in their hello messages, then the router with the highest IPv6 address becomes the DR.

Examples

The following example configures the router to use DR priority 3:

Router(config)# interface FastEthernet 1/0

Router(config-if)# ipv6 pim dr-priority 3

Related Commands

ipv6 pim hello-interval

To configure the frequency of Protocol Independent Multicast (PIM) hello messages on an interface, use the ipv6 pim hello-interval command in interface configuration mode. To return to the default interval, use the no form of this command.

ipv6 pim hello-interval seconds

no ipv6 pim hello-interval seconds

Syntax Description

Command Default

Hello messages are sent at 30-second intervals with small random jitter.

Command Modes

Interface configuration

Command History

Usage Guidelines

Periodic hello messages are sent out at 30-second intervals with a small jitter. The ipv6 pim hello-interval command allows users to set a periodic interval.

Examples

The following example sets the PIM hello message interval to 45 seconds:

Router(config)# interface FastEthernet 1/0

Router(config-if)# ipv6 pim hello-interval 45

Related Commands

ipv6 pim join-prune-interval

To configure periodic join and prune announcement intervals for a specified interface, use the ipv6 pim join-prune-interval command in interface configuration mode. To return to the default value, use the no form of the command.

ipv6 pim join-prune-interval seconds

no ipv6 pim join-prune-interval seconds

Syntax Description

Command Default

The default is 60 seconds.

Command Modes

Interface configuration

Command History

Usage Guidelines

Periodic join and prune announcements are sent out at 60-second intervals. The ipv6 pim join-prune-interval command allows users to set a periodic interval.

Examples

The following example sets the join and prune announcement intervals to 75 seconds:

Router(config)# interface FastEthernet 1/0

Router(config-if)# ipv6 pim join-prune-interval 75

ipv6 pim neighbor-filter list

To filter Protocol Independent Multicast (PIM) neighbor messages from specific IPv6 addresses, use the ipv6 pim neighbor-filter command in the global configuration mode. To return to the router default, use the no form of this command.

ipv6 pim [vrf vrf-name] neighbor-filter list access-list

no ipv6 pim [vrf vrf-name] neighbor-filter list access-list

Syntax Description

Command Default

PIM neighbor messages are not filtered.

Command Modes

Global configuration

Command History

Usage Guidelines

The ipv6 pim neighbor-filter list command is used to prevent unauthorized routers on the LAN from becoming PIM neighbors. Hello messages from addresses specified in this command are ignored.

Examples

The following example causes PIM to ignore all hello messages from IPv6 address FE80::A8BB:CCFF:FE03:7200:

Router(config)# ipv6 pim neighbor-filter list nbr_filter_acl

Router(config)# ipv6 access-list nbr_filter_acl

Router(config-ipv6-acl)# deny ipv6 host FE80::A8BB:CCFF:FE03:7200 any

Router(config-ipv6-acl)# permit any any

ipv6 pim passive

To enable the Protocol Independent Multicast (PIM) passive feature on a specific interface, use the ipv6 pim passive command in interface configuration mode. To disable this feature, use the no form of this command.

ipv6 pim passive

no ipv6 pim passive

Syntax Description

This command has no arguments or keywords.

Command Default

PIM passive mode is not enabled on the router.

Command Modes

Interface configuration (config-if)

Command History

Usage Guidelines

Use the ipv6 pim passive command to configure IPv6 PIM passive mode on an interface.

A PIM passive interface does not send or receive any PIM control messages. However, a PIM passive interface acts as designated router (DR) and designated forwarder (DF)-election winner, and it can accept and forward multicast data.

Examples

The following example configures IPv6 PIM passive mode on an interface:

Router(config)# interface gigabitethernet 1/0/0

Router(config-if)# ipv6 pim passive

Related Commands

ipv6 pim rp embedded

To enable embedded rendezvous point (RP) support in IPv6 Protocol Independent Multicast (PIM), use the ipv6 pim rp-embedded command in global configuration mode. To disable embedded RP support, use the no form of this command.

ipv6 pim [vrf vrf-name] rp embedded

no ipv6 pim [vrf vrf-name] rp embedded

Syntax Description

Command Default

Embedded RP support is enabled by default.

Command Modes

Global configuration

Command History

Usage Guidelines

Because embedded RP support is enabled by default, users will generally use the no form of this command to turn off embedded RP support.

The ipv6 pim rp embedded command applies only to the embedded RP group ranges ff7X::/16 and fffX::/16. When the router is enabled, it parses groups in the embedded RP group ranges ff7X::/16 and fffX::/16, and extracts the RP to be used from the group address.

Examples

The following example disables embedded RP support in IPv6 PIM:

no ipv6 pim rp embedded

ipv6 pim rp-address

To configure the address of a Protocol Independent Multicast (PIM) rendezvous point (RP) for a particular group range, use the ipv6 pim rp-address command in global configuration mode. To remove an RP address, use the no form of this command.

ipv6 pim [vrf vrf-name] rp-address ipv6-address [group-access-list] [bidir]

no ipv6 pim rp-address ipv6-address [group-access-list] [bidir]

Syntax Description

Command Default

No PIM RPs are preconfigured.
Embedded RP support is enabled by default when IPv6 PIM is enabled (where embedded RP support is provided).
Multicast groups operate in PIM sparse mode.

Command Modes

Global configuration

Command History

Usage Guidelines

When PIM is configured in sparse mode, you must choose one or more routers to operate as the RP. An RP is a single common root of a shared distribution tree and is statically configured on each router.

Where embedded RP support is available, only the RP needs to be statically configured as the RP for the embedded RP ranges. No additional configuration is needed on other IPv6 PIM routers. The other routers will discover the RP address from the IPv6 group address. If these routers want to select a static RP instead of the embedded RP, the specific embedded RP group range must be configured in the access list of the static RP.

The RP address is used by first-hop routers to send register packets on behalf of source multicast hosts. The RP address is also used by routers on behalf of multicast hosts that want to become members of a group. These routers send join and prune messages to the RP.

If the optional group-access-list argument is not specified, the RP is applied to the entire routable IPv6 multicast group range, excluding SSM, which ranges from FFX[3-f]::/8 to FF3X::/96. If the group-access-list argument is specified, the IPv6 address is the RP address for the group range specified in the group-access-list argument.

You can configure Cisco IOS software to use a single RP for more than one group. The conditions specified by the access list determine which groups the RP can be used for. If no access list is configured, the RP is used for all groups.

A PIM router can use multiple RPs, but only one per group.

Examples

The following example shows how to set the PIM RP address to 2001::10:10 for all multicast groups:

Router(config)# ipv6 pim rp-address 2001::10:10

The following example sets the PIM RP address to 2001::10:10 for the multicast group FF04::/64 only:

Router(config)# ipv6 access-list acc-grp-1

Router(config-ipv6-acl)# permit ipv6 any ff04::/64

Router(config)# ipv6 pim rp-address 2001::10:10 acc-grp-1

The following example shows how to configure a group access list that permits the embedded RP ranges derived from the IPv6 RP address 2001:0DB8:2::2:

Router(config)# ipv6 pim rp-address 2001:0DB8:2::2 embd-ranges

Router(config)# ipv6 access-list embd-ranges

Router(config-ipv6-acl)# permit ipv6 any ff73:240:2:2:2::/96

Router(config-ipv6-acl)# permit ipv6 any ff74:240:2:2:2::/96

Router(config-ipv6-acl)# permit ipv6 any ff75:240:2:2:2::/96

Router(config-ipv6-acl)# permit ipv6 any ff76:240:2:2:2::/96

Router(config-ipv6-acl)# permit ipv6 any ff77:240:2:2:2::/96

Router(config-ipv6-acl)# permit ipv6 any ff78:240:2:2:2::/96

The following example shows how to enable the address 100::1 as the bidirectional RP for the entries multicast range FF::/8:

ipv6 pim rp-address 100::1 bidir

In the following example, the IPv6 address 200::1 is enabled as the bidirectional RP for the ranges permitted by the access list named bidir-grps. The ranges permitted by this list are ff05::/16 and ff06::/16.

Router(config)# ipv6 access-list bidir-grps

Router(config-ipv6-acl)# permit ipv6 any ff05::/16

Router(config-ipv6-acl)# permit ipv6 any ff06::/16

Router(config-ipv6-acl)# exit

Router(config)# ipv6 pim rp-address 200::1 bidir-grps bidir

Related Commands

ipv6 pim spt-threshold infinity

To configure when a Protocol Independent Multicast (PIM) leaf router joins the shortest path tree (SPT) for the specified groups, use the ipv6 pim spt-threshold infinity command in global configuration mode. To restore the default value, use the no form of this command.

ipv6 pim [vrf vrf-name] spt-threshold infinity [group-list access-list-name]

no ipv6 pim spt-threshold infinity

Syntax Description

Command Default

When this command is not used, the PIM leaf router joins the SPT immediately after the first packet arrives from a new source. Once the router has joined the SPT, configuring the ipv6 pim spt-threshold infinity command will not cause it to switch to the shared tree.

Command Modes

Global configuration

Command History

Usage Guidelines

Using the ipv6 pim spt-threshold infinity command enables all sources for the specified groups to use the shared tree. The group-list keyword indicates to which groups the SPT threshold applies.

The access-list-name argument refers to an IPv6 access list. When the access-list-name argument is specified with a value of 0, or the group-list keyword is not used, the SPT threshold applies to all groups. The default setting (that is, when this command is not enabled) is to join the SPT immediately after the first packet arrives from a new source.

Examples

The following example configures a PIM last-hop router to stay on the shared tree and not switch to the SPT for the group range ff04::/64.:

Router(config)# ipv6 access-list acc-grp-1

Router(config-ipv6-acl)# permit ipv6 any FF04::/64

Router(config-ipv6-acl)# exit

Router(config)# ipv6 pim spt-threshold infinity group-list acc-grp-1

ipv6 policy route-map

To configure IPv6 policy-based routing (PBR) on an interface, use the ipv6 policy route-map command in interface configuration mode. To disable PBR on an interface, use the no form of this command.

ipv6 policy route-map route-map-name

no ipv6 policy route-map route-map-name

Syntax Description

Command Default

Policy routing does not occur on the interface.

Command Modes

Interface configuration

Command History

Usage Guidelines

You could enable PBR if you want your packets to take a route other than the obvious shortest path.

The ipv6 policy route-map command identifies a route map to use for policy-based routing. The route-map commands each have a list of match and set commands associated with them. The match commands specify the match criteria—the conditions under which PBR is allowed for the interface. The set commands specify the set actions—the particular PBR actions to perform if the criteria enforced by the match commands are met. The no ipv6 policy route-map command deletes the pointer to the route map.

Policy-based routing can be performed on any match criteria that can be defined in an IPv6 access list.

Examples

In the following example, a route map named pbr-dest-1 is created and configured, specifying packet match criteria and desired policy-route action. Then, PBR is enabled on Ethernet interface 0/0:

ipv6 access-list match-dest-1

  permit ipv6 any 2001:1760::/32

route-map pbr-dest-1 permit 10

  match ipv6 address match-dest-1

  set interface Ethernet0/0

interface Ethernet0/0

  ipv6 policy-route-map pbr-dest-1

Related Commands

ipv6 port-map

To establish port-to-application mapping (PAM) for the system, use the ipv6 port-map command in global configuration mode. To delete user-defined PAM entries, use the no form of this command.

ipv6 port-map {application port port-num [list acl-name]}

no ipv6 port-map {application port port-num [list acl-name]}

Syntax Description

Command Default

None

Command Modes

Global configuration

Command History

Usage Guidelines

The ipv6 port-map command associates TCP or User Datagram Protocol (UDP) port numbers with applications or services, establishing a table of default port mapping information at the firewall. This information is used to support network environments that run services using ports that are different from the registered or well-known ports associated with a service or application.

The port mapping information in the PAM table is of one of three types:

•System-defined

•User-defined

•Host-specific

System-Defined Port Mapping

Initially, PAM creates a set of system-defined entries in the mapping table using well-known or registered port mapping information set up during the system start-up. The Cisco IOS Firewall Context-Based Access Control feature requires the system-defined mapping information to function properly. System-defined mapping information cannot be deleted or changed; that is, you cannot map HTTP services to port 21 (FTP) or FTP services to port 80 (HTTP).

Table 32 lists the default system-defined services and applications in the PAM table.

Note You can override the system-defined entries for a specific host or subnet using the list keyword in the ipv6 port-map command.

User-Defined Port Mapping

Network applications that use non-standard ports require user-defined entries in the mapping table. Use the ipv6 port-map command to create default user-defined entries in the PAM table.

To map a range of port numbers with a service or application, you must create a separate entry for each port number.

Note If you try to map an application to a system-defined port, a message appears warning you of a mapping conflict.

Use the no form of the ipv6 port-map command to delete user-defined entries from the PAM table.

To overwrite an existing user-defined port mapping, use the ipv6 port-map command to associate another service or application with the specific port.

Host-Specific Port Mapping

User-defined entries in the mapping table can include host-specific mapping information, which establishes port mapping information for specific hosts or subnets. In some environments, it might be necessary to override the default port mapping information for a specific host or subnet, including a system-defined default port mapping information. Use the list keyword for the ipv6 port-map command to specify an ACL for a host or subnet that uses PAM.

Note If the host-specific port mapping information is the same as existing system-defined or user-defined default entries, host-specific port changes have no effect.

Examples

The following user-defined port-mapping configuration map port 8080 to the HTTP application:

ipv6 port-map http port 8080

Host-specific port-mapping configuration maps port 2121 to the FTP application from a particular set of host. First, the user needs to create a permit IPv6 access list for the allowed host(s). In the following example, packets from the hosts in the 2001:0DB8:1:7 subset destined for port 2121 will be mapped to the FTP application:

Router(config)# ipv6 access-list ftp-host

Router(config-ipv6-acl)# permit 2001:0DB8:1:7::/64 any

The port-map configuration is then configured as follows:

Router(config)# ipv6 port-map ftp port 2121 list ftp-host 

Related Commands

ipv6 prefix-list

To create an entry in an IPv6 prefix list, use the ipv6 prefix-list command in global configuration mode. To delete the entry, use the no form of this command.

ipv6 prefix-list list-name [seq seq-number] {deny ipv6-prefix/prefix-length | permit ipv6-prefix/prefix-length | description text} [ge ge-value] [le le-value]

no ipv6 prefix-list list-name

Syntax Description

Command Default

No prefix list is created.

Command Modes

Global configuration

Command History

Usage Guidelines

The ipv6 prefix-list command is similar to the ip prefix-list command, except that it is IPv6-specific.

To suppress networks from being advertised in updates, use the distribute-list out command.

The sequence number of a prefix list entry determines the order of the entries in the list. The router compares network addresses to the prefix list entries. The router begins the comparison at the top of the prefix list, with the entry having the lowest sequence number.

If multiple entries of a prefix list match a prefix, the entry with the lowest sequence number is considered the real match. Once a match or deny occurs, the router does not go through the rest of the prefix list. For efficiency, you may want to put the most common permits or denies near the top of the list, using the seq-number argument.

The show ipv6 prefix-list command displays the sequence numbers of entries.

IPv6 prefix lists are used to specify certain prefixes or a range of prefixes that must be matched before a permit or deny statement can be applied. Two operand keywords can be used to designate a range of prefix lengths to be matched. A prefix length of less than, or equal to, a value is configured with the le keyword. A prefix length greater than, or equal to, a value is specified using the ge keyword. The ge and le keywords can be used to specify the range of the prefix length to be matched in more detail than the usual ipv6-prefix/prefix-length argument. For a candidate prefix to match against a prefix list entry three conditions can exist:

•the candidate prefix must match the specified prefix list and prefix length entry

•the value of the optional le keyword specifies the range of allowed prefix lengths from the prefix-length argument up to, and including, the value of the le keyword

•the value of the optional ge keyword specifies the range of allowed prefix lengths from the value of the ge keyword up to, and including, 128.

Note Note that the first condition must match before the other conditions take effect.

An exact match is assumed when the ge or le keywords are not specified. If only one keyword operand is specified then the condition for that keyword is applied, and the other condition is not applied. The prefix-length value must be less than the ge value. The ge value must be less than, or equal to, the le value. The le value must be less than or equal to 128.

Every IPv6 prefix list, including prefix lists that do not have any permit and deny condition statements, has an implicit deny any any statement as its last match condition.

Examples

The following example denies all routes with a prefix of ::/0.

Router(config)# ipv6 prefix-list abc deny ::/0

The following example permits the prefix 2002::/16:

Router(config)# ipv6 prefix-list abc permit 2002::/16

The following example shows how to specify a group of prefixes to accept any prefixes from prefix 5F00::/48 up to and including prefix 5F00::/64.

Router(config)# ipv6 prefix-list abc permit 5F00::/48 le 64

The following example denies prefix lengths greater than 64 bits in routes that have the prefix 2001:0DB8::/64.

Router(config)# ipv6 prefix-list abc permit 2001:0DB8::/64 le 128

The following example permits mask lengths from 32 to 64 bits in all address space.

Router(config)# ipv6 prefix-list abc permit ::/0 ge 32 le 64

The following example denies mask lengths greater than 32 bits in all address space.

Router(config)# ipv6 prefix-list abc deny ::/0 ge 32

The following example denies all routes with a prefix of 2002::/128.

Router(config)# ipv6 prefix-list abc deny 2002::/128 

The following example permits all routes with a prefix of ::/0.

Router(config)# ipv6 prefix-list abc permit ::/0

Related Commands

ipv6 prefix-list sequence-number

To enable the generation of sequence numbers for entries in an IPv6 prefix list, use the ipv6 prefix-list sequence-number command in global configuration mode. To disable the generation of sequence numbers, use the no form of this command.

ipv6 prefix-list sequence-number

no ipv6 prefix-list sequence-number

Syntax Description

This command has no arguments or keywords.

Command Default

Sequence numbers are automatically generated for entries in an IPv6 prefix list.

Command Modes

Global configuration

Command History

Usage Guidelines

To suppress sequence numbers use the no ipv6 prefix-list sequence-number command. If you disable the generation of sequence numbers in an IPv6 prefix list, you must specify the sequence number for each entry using the seq-number argument of the ipv6 prefix-list command.

The show ipv6 prefix-list command displays the sequence numbers of entries.

Examples

The following example shows the automatic sequence number generation for entries in an IPv6 prefix list being disabled:

Router(config)# no ipv6 prefix-list sequence-number

Related Commands

ipv6 redirects

To enable the sending of Internet Control Message Protocol (ICMP) IPv6 redirect messages if Cisco IOS software is forced to resend a packet through the same interface on which the packet was received, use the ipv6 redirects command in interface configuration mode. To disable the sending of redirect messages, use the no form of this command.

ipv6 redirects

no ipv6 redirects

Syntax Description

This command has no arguments or keywords.

Command Default

The sending of ICMP IPv6 redirect messages is enabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

The rate at which the router generates all IPv6 ICMP error messages can be limited by using the ipv6 icmp error-interval command.

Examples

The following example disables the sending of ICMP IPv6 redirect messages on Ethernet interface 0 and reenables the messages on Ethernet interface 1:

Router(config)# interface ethernet 0

Router(config-if)# no ipv6 redirects

Router(config)# interface ethernet 1

Router(config-if)# ipv6 redirects

To verify whether the sending of IPv6 redirect messages is enabled or disabled on an interface, enter the show ipv6 interface command:

Router# show ipv6 interface

Ethernet0 is up, line protocol is up

  IPv6 is stalled, link-local address is FE80::1 

  Global unicast address(es):

    2000::1, subnet is 2000::/64

    3000::1, subnet is 3000::/64

  Joined group address(es):

    FF02::1

    FF02::2

    FF02::1:FF00:1

  MTU is 1500 bytes

  ICMP error messages limited to one every 100 milliseconds

  ICMP redirects are disabled

  ND DAD is enabled, number of DAD attempts: 1

  ND reachable time is 30000 milliseconds

  ND advertised reachable time is 0 milliseconds

  ND advertised retransmit interval is 0 milliseconds

  ND router advertisements are sent every 200 seconds

  ND router advertisements live for 1800 seconds

  Hosts use stateless autoconfig for addresses.

Ethernet1 is up, line protocol is up

  IPv6 is stalled, link-local address is FE80::2

  Global unicast address(es):

    2000::2, subnet is 2000::/64 

    3000::3, subnet is 3000::/64 

  Joined group address(es):

    FF02::1

    FF02::2

    FF02::1:FF00:1

  MTU is 1500 bytes

  ICMP error messages limited to one every 100 milliseconds

  ICMP redirects are enabled

  ND DAD is disabled, number of DAD attempts: 0

  ND reachable time is 30000 milliseconds

  ND advertised reachable time is 0 milliseconds

  ND advertised retransmit interval is 0 milliseconds

  ND router advertisements are sent every 200 seconds

  ND router advertisements live for 1800 seconds

  Hosts use stateless autoconfig for addresses.

Related Commands

ipv6 rip default-information

To originate a default IPv6 route into the Routing Information Protocol (RIP), use the ipv6 rip default-information command in interface configuration mode. To remove the default IPv6 RIP route, use the no form of this command.

ipv6 rip name default-information {only | originate} [metric metric-value]

no ipv6 rip name default-information

Syntax Description

Command Default

Metric value is 1.

Command Modes

Interface configuration

Command History

Usage Guidelines

The ipv6 rip default-information command is similar to the default-information originate (RIP) command, except that it is IPv6-specific.

Originating a default IPv6 route into RIP also forces the advertisement of the route in router updates sent on the interface. The advertisement of the route occurs regardless of whether the route is present in the IPv6 routing table.

The metric metric-value keyword and argument allow more flexibility in topologies with multiple RIP routers on a LAN. For example, a user may want to configure one of many routers on a LAN as the preferred default router, so that all default route traffic will transit this router. This function can be achieved by configuring the preferred router to advertise a default route with a lower metric than the other routers on the network.

Note To avoid routing loops after the IPv6 default route (::/0) is originated into a specified RIP routing process, the routing process ignores all default route information received in subsequent IPv6 RIP update messages.

Examples

The following example originates a default IPv6 route into RIP on Ethernet interface 0/0 and advertises only the default route in router updates sent on the interface:

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 rip cisco default-information only

The following example originates a default IPv6 route into RIP on Ethernet interface 0/0 and advertises the default route with all other routes in router updates sent on the interface:

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 rip cisco default-information originate

Related Commands

ipv6 rip enable

To enable an IPv6 Routing Information Protocol (RIP) routing process on an interface, use the ipv6 rip enable command in interface configuration mode. To disable an IPv6 RIP routing process on an interface, use the no form of this command.

ipv6 rip name enable

no ipv6 rip name

Syntax Description

Command Default

An IPv6 RIP routing process is not defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

The ipv6 rip enable interface configuration command is used to enable IPv6 RIP explicitly on required interfaces. In IPv4, the network network-number router configuration command is used to implicitly specify the interfaces on which to run IPv4 RIP.

Examples

The following example enables the IPv6 RIP routing process named cisco on Ethernet interface 0/0:

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 rip cisco enable

Related Commands

ipv6 rip metric-offset

To set the IPv6 Routing Information Protocol (RIP) metric for an interface, use the ipv6 rip metric-offset command in interface configuration mode. To return the metric to its default value, use the no form of this command.

ipv6 rip word metric-offset value

no ipv6 rip word metric-offset

Syntax Description

Command Default

The default metric value is 1.

Command Modes

Interface configuration

Command History

Usage Guidelines

When an IPv6 RIP route is received, the interface metric value set by the ipv6 rip metric-offset command is added before the route is inserted into the routing table. Therefore, increasing the IPv6 RIP metric value of an interface increases the metric value of IPv6 RIP routes received over the interface.

Use the ipv6 rip metric-offset command to influence which routes are used, as you prefer. The IPv6 RIP metric is in hop count.

Examples

The following example configures a metric increment of 10 for the RIP routing process named cisco on Ethernet interface 0/0:

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 rip cisco metric-offset 10

Related Commands

ipv6 rip summary-address

To configure IPv6 Routing Information Protocol (RIP) to advertise summarized IPv6 addresses on an interface and to specify the IPv6 prefix that identifies the routes to be summarized, use the ipv6 rip summary-address command in interface configuration mode. To stop the advertising of the summarized IPv6 addresses, use the no form of this command.

ipv6 rip word summary-address ipv6-prefix/prefix-length

no ipv6 rip word summary-address

Syntax Description

Command Default

No default behavior or values.

Command Modes

Interface configuration

Command History

Usage Guidelines

The ipv6 rip summary-address command is similar to the ip summary-address rip command, except that it is IPv6-specific.

Use the ipv6 rip summary-address command to force IPv6 RIP to advertise specific networks on specific interfaces (assuming that routes to those networks exist).

If the first bits of the prefix length for a route match the value specified for the ipv6-prefix argument, the prefix specified in the ipv6-prefix argument is advertised instead of the route. As a result, multiple routes can be replaced by a single route whose metric is the lowest metric of the multiple routes.

Examples

In the following example, the IPv6 address 2001:0DB8:0:1:260:3EFF:FE11:6770 that is assigned to Ethernet interface 0/0 with an IPv6 prefix length of 64 bits is summarized as IPv6 prefix 2001:0DB8::/35 for the IPv6 RIP routing process named cisco:

Router(config)# interface ethernet 0/0

Router(config-if)# ipv6 address 2001:0DB8:0:1:260:3EFF:FE11:6770 /64

Router(config-if)# ipv6 rip cisco summary-address 2001:0DB8::/35

Note A route advertisement that is suppressed as a result of split horizon is not considered by RIP when RIP is deciding whether to advertise a summary route.

Related Commands

ipv6 route

To establish static IPv6 routes, use the ipv6 route command in global configuration mode. To remove a previously configured static route, use the no form of this command.

ipv6 route [vrf vrf-name] ipv6-prefix/prefix-length {ipv6-address | interface-type interface-number [ipv6-address]} [nexthop-vrf [vrf-name1 | default]] [administrative-distance] [administrative-multicast-distance | unicast | multicast] [next-hop-address] [tag tag] [name name]

no ipv6 route [vrf vrf-name] ipv6-prefix/prefix-length {ipv6-address | interface-type interface-number [ipv6-address]} [nexthop-vrf [vrf-name1 | default]] [administrative-distance] [administrative-multicast-distance | unicast | multicast] [next-hop-address] [tag tag] [name route-name]

Syntax Description

Command Default

No static routes are established.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the ipv6 route command to implement static multicast routes in IPv6. For a static multicast route, the IPv6 address of the next-hop router must be provided. The administrative-multicast-distance argument determines the distance that will be used when selecting this route for RPF. When the unicast keyword is used, this route will not be used in multicast RPF selection.

When the ipv6 route command is used with the multicast keyword, the route will not be populated in the unicast RIB. When the optional administrative-multicast-distance argument is not specified, the multicast RPF administrative distance defaults to the same value as that determined by the administrative-distance argument.

Examples

The following example shows a static route that applies to unicast routing only:

ipv6 route 2001::/64 5::5 100 unicast 

The following example shows a static route used only for multicast RPF selection:

ipv6 route 2001::/64 7::7 100 multicast

The following example shows a static route used for both unicast routing and multicast RPF selection:

ipv6 route 2001::/64 6::6 100

The following example shows a static route used for both unicast routing and multicast RPF selection, but with different administrative distances:

ipv6 route 10::/64 7::7 100 200

The following example configures a static route for use in VPN for IPv6:

ipv6 route vrf red 4004::/64 pos 1/0 

The following example configures a static default route within a VRF. Use of the global keyword in this static route provides access to the Internet:

ipv6 route vrf red ::0/0 7007::1 global

Related Commands

ipv6 route static bfd

To specify static route Bidirectional Forwarding Detection for IPv6 (BFDv6) neighbors, use the ipv6 route static bfd command in global configuration mode. To remove a static route BFD neighbor, use the no form of this command.

ipv6 route static bfd [vrf vrf-name] interface-type interface-number ipv6-address [unassociated]

no ipv6 route static bfd

Syntax Description