Table Of Contents

debug ipv6 pim df-election

debug ipv6 policy

debug ipv6 pool

debug ipv6 rip

debug ipv6 routing

debug ipv6 static

debug isis spf-events

debug nhrp

debug nhrp condition

debug nhrp error

default (IPv6 OSPF)

default-information originate (IPv6 IS-IS)

default-information originate (IPv6 OSPF)

default-metric (EIGRP)

default-metric (IPv6)

deny (IPv6)

dialer-list protocol

discard-route (IPv6)

distance (IPv6)

distance (IPv6 EIGRP)

distance (IPv6 Mobile)

distance bgp (IPv6)

distribute-list prefix-list (IPv6 EIGRP)

distribute-list prefix-list (IPv6 RIP)

distribute-list prefix-list (IPv6 OSPF)

dns-server (IPv6)

domain-name (IPv6)

enabled

encryption (IKE policy)

eui-interface

evaluate (IPv6)

event-log

explicit-prefix

frame-relay map ipv6

glbp ipv6

group (IKE policy)

hash (IKE policy)

home-address home-network

home-network

host group

hostname

import dns-server

import domain-name

import information refresh

import nis address

import nis domain-name

import nisp address

import nisp domain-name

import sip address

import sip domain-name

import sntp address

information refresh

ip address

ip http server

debug ipv6 pim df-election

To display debug messages for Protocol Independent Multicast (PIM) bidirectional designated forwarder (DF) election message processing, use the debug ipv6 pim df-election command in privileged EXEC mode. To disable debug messages for PIM bidirectional DF election message processing, use the no form of this command.

debug ipv6 pim df-election [interface type number] [rp rp-name | rp-address]

no debug ipv6 pim df-election [interface type number] [rp rp-name | rp-address]

Syntax Description

interface	(Optional) Specifies that debug messages on a specified interface will be displayed.
type number	(Optional) Interface type and number. For more information, use the question mark (?) online help function.
rp	(Optional) Specifies that debug messages on a specified Route Processor (RP) will be displayed.
rp-name	(Optional) The name of the specified RP.
rp-address	(Optional) The IPv6 address of the specified RP.

Command Default

Debugging for PIM bidirectional DF election message processing is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(7)T	This command was introduced.
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(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 debug ipv6 pim df-election command if traffic is not flowing properly when operating in PIM bidirectional mode or if the show ipv6 pim df and show ipv6 pim df winner commands do not display the expected information.

Examples

The following example shows how to enable debugging for PIM bidirectional DF election message processing on Ethernet interface 1/0 and at 200::1:

Route# debug ipv6 pim df-election interface ethernet 1/0 rp 200::1

Related Commands

Command	Description
ipv6 pim rp-address	Configures the address of a PIM RP for a particular group range.
show ipv6 pim df	Displays the DF-election state of each interface for each RP.
show ipv6 pim df winner	Displays the DF-election winner on each interface for each RP.

debug ipv6 policy

To display IPv6 policy routing packet activity, use the debug ipv6 policy command in user EXEC or privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ipv6 policy [access-list-name]

no debug ipv6 policy [access-list-name]

Syntax Description

access-list-name

(Optional) Name of the IPv6 access list for which to clear the match counters. Names cannot contain a space or quotation mark, or begin with a numeric.

Command Default

IPv6 policy routing packet activity is not displayed.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
12.3(7)T	This command was introduced.
12.2(30)S	This command was integrated into Cisco IOS Release 12.2(30)S.

Usage Guidelines

If no access list is specified using the optional access-list-name argument, information about all policy-matched and policy-routed packets is displayed.

After you configure IPv6 policy routing, use the debug ipv6 policy command to verify that IPv6 policy-based routing (PBR) is policy-routing packets normally. Policy routing looks at various parts of the packet and then routes the packet based on certain user-defined attributes in the packet. The debug ipv6 policy command helps you determine what policy routing is following. It displays information about whether a packet matches the criteria, and if so, the resulting routing information for the packet.

Do not use the debug ipv6 policy command unless you suspect a problem with IPv6 PBR policy routing.

Examples

The following example enables IPv6 policy routing packet activity. The output for this command is self-explanatory:

Router# debug ipv6 policy

00:02:38:IPv6 PBR:Ethernet0/0, matched src 2003::90 dst 2001:1000::1 protocol 58

00:02:38:IPv6 PBR:set nexthop 2003:1::95, interface Ethernet1/0

00:02:38:IPv6 PBR:policy route via Ethernet1/0/2003:1::95

debug ipv6 pool

To enable debugging on IPv6 prefix pools, use the debug ipv6 pool command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug ipv6 pool

no debug ipv6 pool

Syntax Description

This command has no keywords or arguments.

Command Default

No debugging is active.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(13)T	This command was introduced.

Examples

The following example enables debugging for IPv6 prefix pools:

Router# debug ipv6 pool

2w4d: IPv6 Pool: Deleting route/prefix 2001:0DB8::/29 to Virtual-Access1 for cisco

2w4d: IPv6 Pool: Returning cached entry 2001:0DB8::/29 for cisco on Virtual-Access1 to 

pool1

2w4d: IPv6 Pool: Installed route/prefix 2001:0DB8::/29 to Virtual-Access1 for cisco

Related Commands

Command	Description
ipv6 local pool	Configures a local IPv6 prefix pool.
show ipv6 interface	Displays the usability status of interfaces configured for IPv6.
show ipv6 local pool	Displays information about defined IPv6 prefix pools.

debug ipv6 rip

To display debug messages for IPv6 Routing Information Protocol (RIP) routing transactions, use the debug ipv6 rip command in privileged EXEC mode. To disable debug messages for IPv6 RIP routing transactions, use the no form of this command.

debug ipv6 rip [interface-type interface-number]

no debug ipv6 rip [interface-type interface-number]

Syntax Description

interface-type	(Optional) The interface type about which to display debug messages.
interface-number	(Optional) The interface number about which to display debug messages.

Command Default

IPv6 RIP debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(2)T	This command was introduced.
12.0(21)ST	This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S	This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S	This command was integrated into Cisco IOS Release 12.2(14)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

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

---

Note By default, the network server sends the output from debug commands and system error messages to the console. To redirect debug output, use the logging command options within global configuration mode. Destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. For complete information on debug commands and redirecting debug output, refer to the Cisco IOS Debug Command Reference.

---

Using this command without arguments enables IPv6 RIP debugging for RIP packets that are sent and received on all router interfaces. Using this command with arguments enables IPv6 RIP debugging for RIP packets that are sent and received only on the specified interface.

---

Caution Using this command on busy networks seriously degrades the performance of the router.

---

Examples

The following example shows output for the debug ipv6 rip command:

Router# debug ipv6 rip

13:09:10:RIPng:Sending multicast update on Ethernet1/1 for as1_rip

13:09:10:       src=FE80::203:E4FF:FE12:CC1D

13:09:10:       dst=FF02::9 (Ethernet1/1)

13:09:10:       sport=521, dport=521, length=32

13:09:10:       command=2, version=1, mbz=0, #rte=1

13:09:10:       tag=0, metric=1, prefix=::/0

13:09:28:RIPng:response received from FE80::202:FDFF:FE77:1E42 on Ethernet1/1 for as1_rip

13:09:28:       src=FE80::202:FDFF:FE77:1E42 (Ethernet1/1)

13:09:28:       dst=FF02::9

13:09:28:       sport=521, dport=521, length=32

13:09:28:       command=2, version=1, mbz=0, #rte=1

13:09:28:       tag=0, metric=1, prefix=2000:0:0:1:1::/80

The example shows two RIP packets; both are updates, known as "responses" in RIP terminology and indicated by a "command" value of 2. The first is an update sent by this router, and the second is an update received by this router. Multicast update packets are sent to all neighboring IPv6 RIP routers (all routers that are on the same links as the router sending the update, and that have IPv6 RIP enabled). An IPv6 RIP router advertises the contents of its routing table to its neighbors by periodically sending update packets over those interfaces on which IPv6 RIP is configured. An IPv6 router may also send "triggered" updates immediately following a routing table change. In this case the updates only includes the changes to the routing table. An IPv6 RIP router may solicit the contents of the routing table of a neighboring router by sending a Request (command =1) message to the router. The router will respond by sending an update (Response, command=2) containing its routing table. In the example, the received response packet could be a periodic update from the address FE80::202:FDFF:FE77:1E42 or a response to a RIP request message that was previously sent by the local router.

Table 25 describes the significant fields shown in the display.

Table 25 debug ipv6 rip Field Descriptions 

Field	Description
as1_rip	The name of the RIP process that is sending or receiving the update.
src	The address from which the update was originated.
dst	The destination address for the update.
sport, dport	The source and destination ports for the update. (IPv6 RIP uses port 521, as shown in the display.)
command	The command field within the RIP packet. A value of 2 indicates that the RIP packet is a response (update); a value of 1 indicates that the RIP packet is a request.
version	The version of IPv6 RIP being used. The current version is 1.
mbz	There must be a 0 (mbz) field within the RIP packet.
#rte	Indicates the number of routing table entries (RTEs) the RIP packet contains.
tag metric prefix	The tag, metric, and prefix fields are specific to each RTE contained in the update. The tag field is intended to allow for the flagging of IPv6 RIP "internal" and "external" routes. The metric field is the distance metric from the router (sending this update) to the prefix. The prefix field is the IPv6 prefix of the destination being advertised.

Related Commands

Command	Description
debug ipv6 routing	Displays debug messages for IPv6 routing table updates and route cache updates.

debug ipv6 routing

To display debug messages for IPv6 routing table updates and route cache updates, use the debug ipv6 routing command in privileged EXEC mode. To disable debug messages for IPv6 routing table updates and route cache updates, use the no form of this command.

debug ipv6 routing

no debug ipv6 routing

Syntax Description

This command has no arguments or keywords.

Command Default

Debugging for IPv6 routing table updates and route cache updates is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(2)T	This command was introduced.
12.0(21)ST	This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S	This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S	This command was integrated into Cisco IOS Release 12.2(14)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

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

---

Note By default, the network server sends the output from debug commands and system error messages to the console. To redirect debug output, use the logging command options within global configuration mode. Destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. For complete information on debug commands and redirecting debug output, refer to the Cisco IOS Debug Command Reference.

---

Examples

The following example shows output for the debug ipv6 routing command:

Router# debug ipv6 routing

13:18:43:IPv6RT0:Add 2000:0:0:1:1::/80 to table

13:18:43:IPv6RT0:Better next-hop for 2000:0:0:1:1::/80, [120/2]

13:19:09:IPv6RT0:Add 2000:0:0:2::/64 to table

13:19:09:IPv6RT0:Better next-hop for 2000:0:0:2::/64, [20/1]

13:19:09:IPv6RT0:Add 2000:0:0:2:1::/80 to table

13:19:09:IPv6RT0:Better next-hop for 2000:0:0:2:1::/80, [20/1]

13:19:09:IPv6RT0:Add 2000:0:0:4::/64 to table

13:19:09:IPv6RT0:Better next-hop for 2000:0:0:4::/64, [20/1]

13:19:37:IPv6RT0:Add 2000:0:0:6::/64 to table

13:19:37:IPv6RT0:Better next-hop for 2000:0:0:6::/64, [20/2]

The debug ipv6 routing command displays messages whenever the routing table changes. For example, the following message indicates that a route to the prefix 2000:0:0:1:1::/80 was added to the routing table at the time specified in the message.

13:18:43:IPv6RT0:Add 2000:0:0:1:1::/80 to table

The following message indicates that the prefix 2000:0:0:2::/64 was already in the routing table; however, a received advertisement provided a lower cost path to the prefix. Therefore, the routing table was updated with the lower cost path. (The [20/1] in the example is the administrative distance [20] and metric [1] of the better path.)

13:19:09:IPv6RT0:Better next-hop for 2000:0:0:2::/64, [20/1]

Related Commands

Command	Description
debug ipv6 rip	Displays debug messages for IPv6 RIP routing transactions.

debug ipv6 static

To enable Bidirectional Forwarding Detection for IPv6 (BFDv6) debugging, use the debug ipv6 static command in privileged EXEC mode.

debug ipv6 static

Command Default

Debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
Cisco IOS XE Release 2.1	This command was introduced.

Usage Guidelines

Use the debug ipv6 static command to monitor BFDv6 operation.

Examples

The following example enables BFDv6 debugging:

Router# debug ipv6 static

Related Commands

Command	Description
monitor event ipv6 static	Monitors the operation of the IPv6 static and IPv6 static BFDv6 neighbors using event trace.
show ipv6 static	Displays the current contents of the IPv6 routing table.

debug isis spf-events

To display a log of significant events during an Intermediate System-to-Intermediate System (IS-IS) shortest-path first (SPF) computation, use the debug isis spf-events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug isis spf-events

no debug isis spf-events

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0	This command was introduced.
12.2(15)T	Support for IPv6 was added.
12.2(18)S	Support for IPv6 was added.
12.0(26)S	Support for IPv6 was added.
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 displays information about significant events that occur during SPF-related processing.

Examples

The following example displays significant events during an IS-IS SPF computation:

Router# debug isis spf-events

ISIS-Spf:  Compute L2 IPv6 SPT

ISIS-Spf: Move 0000.0000.1111.00-00 to PATHS, metric 0

ISIS-Spf: Add 0000.0000.2222.01-00 to TENT, metric 10

ISIS-Spf: Move 0000.0000.2222.01-00 to PATHS, metric 10

ISIS-Spf: considering adj to 0000.0000.2222 (Ethernet3/1) metric 10, level 2, circuit 3, 
adj 3 

ISIS-Spf:   (accepted)

ISIS-Spf: Add 0000.0000.2222.00-00 to TENT, metric 10

ISIS-Spf:   Next hop 0000.0000.2222 (Ethernet3/1)

ISIS-Spf: Move 0000.0000.2222.00-00 to PATHS, metric 10

ISIS-Spf: Add 0000.0000.2222.02-00 to TENT, metric 20

ISIS-Spf:   Next hop 0000.0000.2222 (Ethernet3/1)

ISIS-Spf: Move 0000.0000.2222.02-00 to PATHS, metric 20

ISIS-Spf: Add 0000.0000.3333.00-00 to TENT, metric 20

ISIS-Spf:   Next hop 0000.0000.2222 (Ethernet3/1)

ISIS-Spf: Move 0000.0000.3333.00-00 to PATHS, metric 20

debug nhrp

To enable Next Hop Resolution Protocol (NHRP) debugging, use the debug nhrp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug nhrp {ipv4 | ipv6} [cache | extension | packet | rate]

no debug nhrp

Syntax Description

ipv4	Specifies the IPv4 overlay address.
ipv6	Specifies the IPv6 overlay address.
cache	(Optional) Specifies NHRP cache operations.
extension	(Optional) Specifies NHRP extension processing.
packet	(Optional) Specifies NHRP activity.
rate	(Optional) Specifies NHRP rate limiting.

(

Command Default

NHRP debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

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

Examples

The following example shows NHRP debugging output for IPv6:

Router# debug nhrp ipv6

Aug  9 13:13:41.486: NHRP: Attempting to send packet via DEST

			- 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32

Aug  9 13:13:41.486: NHRP: Encapsulation succeeded.  

Aug  9 13:13:41.486: NHRP: Tunnel NBMA addr 11.11.11.99

Aug  9 13:13:41.486: NHRP: Send Registration Request via Tunnel0 vrf 0, packet size: 105

Aug  9 13:13:41.486: src: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32, 

	         dst: 2001:0db8:3c4d:0015:0000:0000:1a2f:3d2c/32

Aug  9 13:13:41.486: NHRP: 105 bytes out Tunnel0

Aug  9 13:13:41.486: NHRP: Receive Registration Reply via Tunnel0 vrf 0, packet size: 125

The following example shows NHRP debugging output for IPv4:

Router# debug nhrp ipv4

Aug  9 13:13:41.486: NHRP: Attempting to send packet via DEST 10.1.1.99

Aug  9 13:13:41.486: NHRP: Encapsulation succeeded.  Tunnel IP addr 10.11.11.99

Aug  9 13:13:41.486: NHRP: Send Registration Request via Tunnel0 vrf 0, packet size: 105

Aug  9 13:13:41.486:       src: 10.1.1.11, dst: 10.1.1.99

Aug  9 13:13:41.486: NHRP: 105 bytes out Tunnel0

Aug  9 13:13:41.486: NHRP: Receive Registration Reply via Tunnel0 vrf 0, packet size: 125

Aug  9 13:13:41.486: NHRP: netid_in = 0, to_us = 1

Related Commands

Command	Description
debug dmvpn	Displays DMVPN session debugging information.
debug nhrp error	Displays NHRP error level debugging information.

debug nhrp condition

To enable Next Hop Resolution Protocol (NHRP) conditional debugging, use the debug nhrp condition command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug nhrp condition [peer [nbma | tunnel | ip-address | ipv6-address]] | [interface tunnel number] | [vrf vrf-name]

no debug nhrp condition [peer {nbma | tunnel} ip-address | ipv6-address] | [interface tunnel number] | [vrf vrf-name]

Syntax Description

peer	(Optional) Specifies an NHRP peer.
nbma	(Optional) Specifies mapping nonbroadcast access (NBMA).
tunnel	(Optional) Specifies a tunnel.
ip-address	(Optional) The IPv4 address for the NHRP peer.
ipv6-address	(Optional) The IPv6 address for the NHRP peer.
interface	(Optional) Displays NHRP information based on a specific interface.
tunnel number	(Optional) Specifies the tunnel address for the NHRP peer.
vrf vrf-name	(Optional) Specifies debugging information for sessions related to the specified virtual routing and forwarding (VRF) configuration.

Command Default

Conditional NHRP debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(9)T	This command was introduced.
12.4(20)T	The ipv6-address argument was added.

Examples

The following example shows how to enable conditional NHRP debugging for a specific tunnel:

Router# debug nhrp condition peer tunnel 192.0.2.1

Related Commands

Command	Description
debug dmvpn	Displays DMVPN session debugging information.
debug nhrp error	Displays NHRP error level debugging information.

debug nhrp error

To display Next Hop Resolution Protocol (NHRP) error level debugging information, use the debug nhrp error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug nhrp {ipv4 | ipv6} error

no debug nhrp {ipv4 | ipv6} error

Syntax Description

ipv4	Specifies the IPv6 overlay network.
ipv6	Specifies the IPv6 overlay network.

Command Default

Error level NHRP debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(9)T	This command was introduced.
12.4(20)T	The ipv4 and ipv6 keywords were added.

Examples

The following example shows how to enable error level debugging for IPv4 NHRP:

Router# debug nhrp ipv4 error 

NHRP errors debugging is on

Related Commands

Command	Description
debug dmvpn	Displays DMVPN session debugging information.
debug nhrp condition	Enables NHRP conditional debugging.

default (IPv6 OSPF)

To return a parameter to its default value, use the default command in router configuration mode.

default [area | auto-cost | default-information | default-metric | discard-route | distance | distribute-list | ignore | log-adjacency-changes | maximum-paths | passive-interface | redistribute | router-id | summary-prefix | timers]

Syntax Description

area	(Optional) Open Shortest Path First (OSPF) for IPv6 area parameters.
auto-cost	(Optional) OSPF interface cost according to bandwidth.
default-information	(Optional) Distributes default information.
default-metric	(Optional) Metric for a redistributed route.
discard-route	(Optional) Enables or disables discard-route installation.
distance	(Optional) Administrative distance.
distribute-list	(Optional) Filter networks in routing updates.
ignore	(Optional) Ignores a specific event.
log-adjacency-changes	(Optional) Log changes in the adjacency state.
maximum-paths	(Optional) Forwards packets over multiple paths.
passive-interface	(Optional) Suppresses routing updates on an interface.
redistribute	(Optional) Redistributes IPv6 prefixes from another routing protocol.
router-id	(Optional) Router ID for the specified routing process.
summary-prefix	(Optional) OSPF summary prefix.
timers	(Optional) OSPF timers.

Command Default

This command is disabled by default.

Command Modes

Router configuration

Command History

Release	Modification
12.2(15)T	This command was introduced.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.

Usage Guidelines

The command is removed if it is disabled by default.

Examples

In the following example, OSPF for IPv6 area parameters are reset to the default values:

default timers spf

default-information originate (IPv6 IS-IS)

To inject an IPv6 default route into an Intermediate System-to-Intermediate System (IS-IS) IPv6 routing domain, use the default-information originate command in address family configuration mode. To disable this feature, use the no form of this command.

default-information originate [route-map map-name]

no default-information originate [route-map map-name]

Syntax Description

route-map map-name

(Optional) Route map should be used to advertise the default route conditionally. The map-name argument identifies a configured route map.

Command Default

This feature is disabled.

Command Modes

Address family configuration

Command History

Release	Modification
12.2(8)T	This command was introduced.
12.0(21)ST	This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S	This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S	This command was integrated into Cisco IOS Release 12.2(14)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

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

If a router configured with this command has an IPv6 route to ::/0 in the routing table, IS-IS will originate an advertisement for ::/0 in its link-state packets (LSPs).

Without a route map, the default is advertised only in Level 2 LSPs. For Level 1 routing, there is another mechanism to find the default route, which is for the router to look for the closest Level 1 or Level 2 router. The closest Level 1 or Level 2 router can be found by looking at the attached bit (ATT) in Level 1 LSPs.

A route map can be used for two purposes:

•Make the router generate default in its Level 1 LSPs.

•Advertise ::/0 conditionally.

With a match ipv6 address standard-access-list command, you can specify one or more IPv6 routes that must exist before the router will advertise ::/0.

Examples

The following example shows the IPv6 default route (::/0) being advertised with all other routes in router updates:

Router(config)# router isis area01

Router(config-router)# address-family ipv6

Router(config-router-af)# default-information originate

Related Commands

Command	Description
address-family ipv6 (IS-IS)	Specifies the IPv6 address family and places the router in address family configuration mode.
match ipv6 address	Distributes IPv6 routes that have a prefix permitted by a prefix list.
show isis database	Displays the IS-IS link-state database.

default-information originate (IPv6 OSPF)

To generate a default external route into an Open Shortest Path First (OSPF) for IPv6 routing domain, use the default-information originate command in router configuration mode. To disable this feature, use the no form of this command.

default-information originate [always] metric metric-value [metric-type type-value] [route-map map-name]

no default-information originate [always] metric metric-value [metric-type type-value] [route-map map-name]

Syntax Description

always	(Optional) Always advertises the default route regardless of whether the software has a default route.
metric metric-value	Metric used for generating the default route. If you omit a value and do not specify a value using the default-metric router configuration command, the default metric value is 10. The default metric value range is from 0 to 16777214.
metric-type type-value	(Optional) External link type associated with the default route advertised into the OSPF for IPv6 routing domain. It can be one of the following values: 1—Type 1 external route 2—Type 2 external route The default is type 2 external route.
route-map map-name	(Optional) Routing process will generate the default route if the route map is satisfied.

Command Default

This command is disabled by default.

Command Modes

Router configuration

Command History

Release	Modification
12.2(15)T	This command was introduced.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.

Usage Guidelines

Whenever you use the redistribute or the default-information router configuration command to redistribute routes into an OSPF for IPv6 routing domain, the Cisco IOS software automatically becomes an Autonomous System Boundary Router (ASBR). However, an ASBR does not, by default, generate a default route into the OSPF for IPv6 routing domain. The software still must have a default route for itself before it generates one, except when you have specified the always keyword.

When you use this command for the OSPF for IPv6 process, the default network must reside in the routing table, and you must satisfy the route-map map-name keyword and argument. Use the default-information originate always route-map map-name form of the command when you do not want the dependency on the default network in the routing table.

Examples

The following example specifies a metric of 100 for the default route redistributed into the OSPF for IPv6 routing domain, an external metric type of type 2, and the default route to be always advertised:

default-information originate always metric 100 metric-type 2 

Related Commands

Command	Description
redistribute (IPv6)	Redistributes IPv6 routes from one routing domain into another routing domain.

 

default-metric (EIGRP)

To set metrics for the Enhanced Interior Gateway Routing Protocol (EIGRP), use the default-metric command in router configuration mode. To remove the metric value and restore the default state, use the no form of this command.

default-metric bandwidth delay reliability loading mtu

no default-metric bandwidth delay reliability loading mtu

Syntax Description

bandwidth	Minimum bandwidth of the route in kilobytes per second. It can be from 1 to 4294967295.
delay	Route delay in tens of microseconds. It can be 1 or any positive number that is a multiple of 39.1 nanoseconds.
reliability	Likelihood of successful packet transmission expressed as a number from 0 through 255. The value 255 means 100 percent reliability; 0 means no reliability.
loading	Effective bandwidth of the route expressed as a number from 1 to 255 (255 is 100 percent loading).
mtu	The smallest allowed value for the maximum transmission unit (MTU), expressed in bytes. It can be from 1 to 65535.

Command Default

Only connected routes can be redistributed without a default metric. The metric of redistributed connected routes is set to 0.

Command Modes

Router configuration

Command History

Release	Modification
10.0	This command was introduced.
12.0(22)S	Address family support was added.
12.2(15)T	Address family support was added.
12.2(18)S	Address family support was added.
12.4(6)T	Support for IPv6 was added.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRB	This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

You must use a default metric to redistribute a protocol into EIGRP, unless you use the redistribute command. Automatic metric translations occur between IGRP and EIGRP. You do not need default metrics to redistribute IGRP or EIGRP into itself.

---

Note The default-metric command does not affect EIGRP-to-EIGRP or IGRP-to-EIGRP distribution. To configure EIGRP-to-EIGRP or IGRP-to-EIGRP distribution, use route maps.

---

Metric defaults have been carefully set to work for a wide variety of networks. Take great care when changing these values.

Default metrics are supported only when you are redistributing from IGRP, EIGRP, or static routes.

Examples

The following example shows how the redistributed Routing Information Protocol (RIP) metrics are translated into EIGRP metrics with values as follows: bandwidth = 1000, delay = 100, reliability = 250, loading = 100, and MTU = 1500:

router eigrp 109

 network 172.16.0.0

 redistribute rip

 default-metric 1000 100 250 100 1500

Related Commands

Command	Description
ipv6 router eigrp	Configures the EIGRP IPv6 routing process.
redistribute (IP)	Redistributes routes from one routing domain into another routing domain.
redistribute (IPv6)	Redistributes IPv6 routes from one routing domain into another routing domain.

default-metric (IPv6)

To set default metric values for routes redistributed into the Open Shortest Path First (OSPF) for IPv6 routing protocol, use the default-metric command in router configuration mode. To return to the default state, use the no form of this command.

default-metric metric-value

no default-metric metric-value

Syntax Description

metric-value

Default metric value appropriate for the specified routing protocol. The range is from 1 to 4294967295.

Command Default

Built-in, automatic metric translations, as appropriate for each routing protocol.

Command Modes

Router configuration

Command History

Release	Modification
12.2(15)T	This command was introduced.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.

Usage Guidelines

The default-metric command is used in conjunction with the redistribute router configuration command to cause the current routing protocol to use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, using a default metric provides a reasonable substitute and enables the redistribution to proceed.

Finer control over the metrics of reditributed routes can be gained by using the options to the redistribute command, including route maps.

Examples

The following example shows an OSPF for IPv6 routing protocol redistributing routes from the Routing Information Protocol (RIP) process named process1. All the redistributed routes are advertised with a metric of 10.

ipv6 router ospf 100

 default-metric 10

 redistribute rip process1

Related Commands

Command	Description
redistribute (IPv6)	Redistributes IPv6 routes from one routing domain into another routing domain.

 

deny (IPv6)

To set deny conditions for an IPv6 access list, use the deny command in IPv6 access list configuration mode. To remove the deny conditions, use the no form of this command.

deny protocol {source-ipv6-prefix/prefix-length | any | host source-ipv6-address | auth} [operator [port-number]] {destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address | auth} [operator [port-number]] [dest-option-type [doh-number | doh-type]] [dscp value] [flow-label value] [fragments] [log] [log-input] [mobility] [mobility-type [mh-number | mh-type]] [routing] [routing-type routing-number] [sequence value] [time-range name] [undetermined-transport]

no deny protocol {source-ipv6-prefix/prefix-length | any | host source-ipv6-address | auth} [operator [port-number]] {destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address | auth} [operator [port-number]] [dest-option-type [doh-number | doh-type]] [dscp value] [flow-label value] [fragments] [log] [log-input] [mobility] [mobility-type [mh-number | mh-type]] [routing] [routing-type routing-number] [sequence value] [time-range name] [undetermined-transport]

Internet Control Message Protocol

deny icmp {source-ipv6-prefix/prefix-length | any | host source-ipv6-address | auth} [operator [port-number]] {destination-ipv6-prefix/prefix-length | any | host destination-ipv6-address | auth} [operator [port-number]] [icmp-type [icmp-code] | icmp-message