- Preface
- Product Overview
- Using the Command Line
- Configuring the Interfaces
- IP Mobility
- Introduction to Radio Aware Routing and MANET
- Understanding and Configuring DLEP
- Configuring R2CP
- Configuring PPPoE
- OSPFv3 Address Families
- Configuring OSPFv3 for a MANET
- Configuring EIGRP in a MANET
- Understanding and Configuring IP Multiplexing
- Zeroization
- Command Reference
- System Message Overview
- Technical Support Reference
- Debug Commands
- List of Commands
- Commands
- access-list
- clear dlep client
- clear dlep counters
- clear dlep neighbor
- clear ospfv3
- clear pppoe relay context
- clear vmi counters
- destination
- eigrp interface
- flowcontrol send
- holdtime
- interface vmi
- ip dlep set heartbeat-threshold
- ip dlep set nbr-activity-timeout
- ip dlep set nbr-down-ack-timeout
- ip dlep set peer-terminate-ack-timeout
- ip dlep vtemplate
- ip mux
- ip mux cache
- ip mux policy
- ip mux profile
- ip mux udpport
- ip r2cp heartbeat-threshold
- ip r2cp node-terminate-ack-threshold
- ip r2cp node-terminate-ack-timeout
- ip r2cp port
- ip r2cp session-activity-timeout
- ip r2cp session-terminate-ack-threshold
- ip r2cp session-terminate-ack-timeout
- ip r2cp virtual-template
- manet cache
- manet hello unicast
- manet peering selective
- manet willingness
- matchdscp
- maxlength
- mode
- mtu
- ospfv3 area
- ospfv3 cost dynamic
- ospfv3 cost dynamic default
- ospfv3 cost dynamic hysteresis
- ospfv3 cost dynamic weight
- ospfv3 dead-interval
- ospfv3 hello-interval
- ospfv3 manet peering cost
- ospfv3 manet peering link-metrics
- ospfv3 network
- outdscp
- physical-interface
- router ospfv3
- service declassify
- show declassify
- show dlep clients
- show dlep config
- show dlep counters
- show dlep neighbors
- show ip eigrp neighbors
- show ip mux
- show ip mux cache
- show ip mux interface
- show ip mux profile
- show ip redirects
- show ipv6 eigrp neighbors
- show ospfv3
- show ospfv3 database
- show ospfv3 flood-list
- show ospfv3 interface
- show ospfv3 neighbor
- show ospfv3 neighbor manet
- show ospfv3 promiscuous acknowledgments
- show pppoe
- show pppoe derived
- show pppoe session
- show r2cp clients
- show r2cp config
- show r2cp neighbors
- show vmi counters
- show vmi neighbors
- shutdown
- singlepacket
- source
- summary-prefix (OSPFv3)
- timers manet
- timers throttle spf
- ttl
Command Reference
This appendix provides command reference documentation in the following major sections:
Debug Commands
You can search for debug commands from privileged EXEC mode.
Do not use debug commands unless a Cisco Support engineer instructs you to do so.
This example shows how to display debug commands for Dynamic Link Exchange Protocol (DLEP):
List of Commands
This section lists the mobility commands modified or introduced in this Configuration Guide:
- access-list
- clear dlep client
- clear dlep counters
- clear dlep neighbor
- clear ospfv3
- clear pppoe relay context
- clear vmi counters
- destination
- eigrp interface
- flowcontrol send
- holdtime
- interface vmi
- ip dlep set heartbeat-threshold
- List of CommandsList of Commandsip dlep set nbr-activity-timeout
- ip dlep set nbr-down-ack-timeout
- ip dlep set peer-terminate-ack-timeout
- ip dlep vtemplate
- ip mux
- ip mux cache
- ip mux policy
- ip mux profile
- ip mux udpport
- ip r2cp heartbeat-threshold
- ip r2cp node-terminate-ack-threshold
- ip r2cp node-terminate-ack-timeout
- ip r2cp port
- ip r2cp session-activity-timeout
- ip r2cp session-terminate-ack-threshold
- ip r2cp session-terminate-ack-timeout
- ip r2cp virtual-template
- manet cache
- manet hello unicast
- manet peering selective
- manet willingness
- matchdscp
- maxlength
- mode
- mtu
- ospfv3 area
- ospfv3 cost dynamic
- ospfv3 cost dynamic default
- ospfv3 cost dynamic hysteresis
- ospfv3 cost dynamic weight
- ospfv3 dead-interval
- ospfv3 hello-interval
- ospfv3 manet peering cost
- ospfv3 manet peering link-metrics
- ospfv3 network
- outdscp
- physical-interface
- router ospfv3
- service declassify
- show declassify
- show dlep clients
- show dlep config
- show dlep counters
- show ip eigrp neighbors
- show ip mux
- show ip mux cache
- show ip mux interface
- show ip mux profile
- show ip redirects
- show ipv6 eigrp neighbors
- show ospfv3
- show ospfv3 database
- show ospfv3 flood-list
- show ospfv3 interface
- show ospfv3 neighbor
- show ospfv3 neighbor manet
- show ospfv3 promiscuous acknowledgments
- show pppoe
- show pppoe derived
- show pppoe session
- show r2cp clients
- show r2cp config
- show r2cp neighbors
- show vmi counters
- show vmi neighbors
- shutdown
- singlepacket
- source
- summary-prefix (OSPFv3)
- timers manet
- timers throttle spf
- ttl
Commands
The following section provides the complete reference pages for all commands listed in this appendix.
access-list
To assign an existing access list to the IP multiplex profile, enter the access-list command. To clear the access list associated with the IP multiplex profile, use the no form of the command.
access-list {{1-199} |{1300-2699} | name}
Syntax Description
Standard access list number to use with the IP multiplex profile. |
|
Extended access list number to use with the IP multiplex profile. |
|
Command Modes
IP multiplexing profile configuration (config-ipmux-profile)
IPv6 multiplexing profile configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
You must configure an access list for IP multiplexing to work. The access list identifies the traffic to be considered for multiplexing. If you do not configure an access list, then no packets are queued for multiplexing.
If you enter the access-list command again, then the new access list writes over the previously entered access list.You must enter the shutdown and no shutdown commands to make the new access list take effect.
Create an ACL list using the ip access-list or ipv6 access-list command. When you configure an ACL to use with IP multiplexing, filter only traffic based on destination address, destination port, and protocol type. If you configure an ACL with other filter characteristics, unexpected or undesirable multiplexing decisions may occur. If you change an ACL associated with an IP Multiplexing profile, you will be prompted to issue a shutdown/no shutdown to the profile before the new access-list filters take effect.
If you delete an ACL from the profile, IP multiplexing will not send superframes, however it will still accept superframes.
Examples
The following example shows how to configure the ACL routeRTP-SJ as the active ACL to filter packets for IP multiplexing.
clear dlep client
To clear a router-to-radio peer association, use the clear dlep client command in privileged EXEC mode.
clear dlep client [ interface ] [ peer-id ]
Syntax Description
Peer ID with valid range from 1 to 2147483647. Clears a specific router-to-radio peer association (client) identified in the output of the show dlep clients command. |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to clear a router-to-radio peer association.
The following example clears a router-to-radio peer association on the fa0/1 interface (with a peer ID value of 11):
Related Commands
|
|
|
|---|---|
clear dlep counters
To clear DLEP counters, use the clear dlep counters command in privileged EXEC mode.
clear dlep counters [ interface ]
Syntax Description
Command Default
If no arguments are specified, all counters on all VMI interfaces with DLEP configured are cleared.
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to clear counters on one DLEP interface:
Router# clear dlep counters gigabitEthernet 0/1.5
clear dlep neighbor
To clear a neighbor session, use the clear dlep neighbor command in privileged EXEC mode.
clear dlep neighbor [ interface ] [ session-id ]
Syntax Description
Session ID with valid range from 1 to 2147483647 Clears a neighbor session with a specific neighbor identified in the output of the show dlep neighbors command |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to clear the neighbor session on the specified interface.
Examples
The following example clears a DLEP neighbor session on a specific FastEthernet interface—where the interface is fa0/1 and the session ID is 11:
Related Commands
|
|
|
|---|---|
clear ospfv3
To clear redistribution by the IPv4 OSPFv3 routing process, use the clear ospfv3 command in privileged EXEC mode.
clear ospfv3 [ process-id ] { counters [ neighbor [ neighbor-interface ] [ neighbor-id ] | force-spf | process | redistribution | traffic [ interface-id ]]}
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the process-id argument to clear only one OSPF process. If process-id is not specified, all OSPF processes are cleared.
Examples
The following example clears all OSPFv3 processes:
The following example clears the OSPFv3 counters for neighbor s19/0.
The following example now shows that there have been 0 state changes since using the clear ospfv3 counters neighbor s19/0 command:
The following example shows the clear ospfv3 force-spf command:
The following example clears all OSPF processes:
The following example clears all OSPF processes for neighbors:
The following example shows the clear ospfv3 redistribution command:
The following example shows the clear ospfv3 traffic command:
Related Commands
|
|
|
|---|---|
Displays OSPF neighbor information on a per-interface basis. |
clear pppoe relay context
To clear the PPP over Ethernet (PPPoE) relay context created for relaying PPPoE Active Discovery (PAD) messages, use the clear pppoe relay context command in privileged EXEC mode.
clear pppoe relay context {all | id session-id}
Syntax Description
Clears a specific context identified in the output of the show pppoe relay context all command. |
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(28)SB. |
Usage Guidelines
Use this command to clear relay contexts created for relaying PAD messages.
Examples
The following example clears all PPPoE relay contexts created for relaying PAD messages:
Related Commands
|
|
|
|---|---|
Displays PPPoE relay contexts created for relaying PAD messages. |
|
clear vmi counters
To clear VMI counters, use the clear vmi counters command in privileged EXEC mode.
clear vmi counters [ vmi-interface ]
Syntax Description
Command Default
If no VMI interfaces are specified, counters on all VMI interfaces are cleared.
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to clear counters on VMI 1:
destination
To specify the IPv4 or IPv6 destination address for the remote endpoint of the IP multiplexing path, enter the destination command. To clear the destination address, use the no form of the command.
destination {ip_addr | ipv6_addr}
Syntax Description
IPv4 address for the destination remote endpoint of the IP multiplexing path. |
|
IPv6 address for the destination remote endpoint of the IP multiplexing path. |
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
You must configure a destination address for the profile in order to use it. If you attempt to issue a no shutdown command when no destination address is configured, you will be prompted to configure a destination address. If a profile is active, you must issue a shutdown command before changing the destination address.
An incoming superframe must match its source and destination addresses to the destination and source addresses, respectively, in the multiplexing profile in order for the superframe to be demultiplexed. If either address does not match, the superframe is ignored.
If you enter the destination command again, then the new address overwrites the previously entered address.
Examples
The following example shows how to configure the IPv6 address FE80::A8BB:CCFF:FE01:5700 as the destination address for superframe packets.
eigrp interface
To set a threshold value to minimize hysteresis in a router-to-radio configuration, use the eigrp interface command in interface-configuration mode. To reset the hysteresis threshold to the default value, use the no form of this command.
eigrp vmi-interface-number interface [ dampening-change value ] [ dampening-interval value ]
no eigrp vmi-interface-number interface [ dampening-change value ] [ dampening-interval value ]
Syntax Description
Command Default
Default for change-based dampening is 50 percent of the computed metric.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.4(15)T. |
Usage Guidelines
This command advertises routing changes for Enhanced Interior Gateway Routing Protocol (EIGRP) traffic only.
The REPLY sent to any QUERY always contains the latest metric information. Exceptions that result in an immediate UPDATE being sent include the following replies:
- A down interface
- A down route
- Any change in metric which results in the router selecting a new next hop
The default value for the change tolerance will be 50 percent of the computed metric. It can be configured in a range of 0 to 100 percent. If the metric change of the interface is not greater (or less) than the current metric plus or minus the specified amount, the change will not result in a routing change, and no update will be sent to other adjacencies.
The default value for the update intervals is 30 seconds. It can be configured in the range from 0 to 64535 seconds. If this option is specified, changes in routes learned though this interface, or in the interface metrics, will not be advertised to adjacencies until the specified interval is met. When the timer expires, any changes detected in any routes learned through the interface, or the metric reported by the interfaces will be sent out.
Examples
Change-based Dampening Example
The following example sets the threshold to 50 percent tolerance routing updates involving VMI interfaces and peers:
Interval-based Dampening Example
The following example sets the interval to 30 seconds at which updates occur for topology changes that affect VMI interfaces and peers:
Related Commands
|
|
|
|---|---|
Sets a threshold value to minimize hysteresis in a router-to-radio configuration. |
|
Creates a VMI that can be configured and applied dynamically. |
flowcontrol send
To enable transmit flow control on an interface, use the flowcontrol send command in interface-configuration mode. To disable transmit flow control, use the no form of this command.
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Examples
The following example shows how to enable transmit flow control on interface FastEthernet 0/0:
holdtime
To specify the amount of time, in milliseconds, that a multiplex profile waits to fill the superframe before sending a partial superframe with currently queued packets, enter the holdtime command. To reset the holdtime to 20 milliseconds, use the no form of the command.
Syntax Description
Amount of time that a multiplex profile waits before sending a partial superframe. Valid values range from 20 to 250 milliseconds. |
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not enter a holdtime, the profile waits the default value of 20 milliseconds before sending a partial superframe.
Examples
The following example shows how to configure the hold time to 150 milliseconds before the profile forwards a partial superframe.
interface vmi
To create a Virtual Multipoint Interface (VMI) for dynamic configuration and application, use the interface vmi command in global-configuration mode. To remove a VMI interface, use the no form of this command.
interface vmi interface-number
no interface vmi interface-number
Syntax Description
Number assigned to the VMI. The value range for VMI interface numbers is from 1 to 2147483647. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.4(15)T. |
Usage Guidelines
VMI Interface Aggregation Point
The VMI interface acts as an aggregation point for multiple PPPoE connections from one or more radios over one or more physical interfaces.
OSPFv3 and EIGRP Route Advertisements
All OSPFv3, EIGRPv4, and EIGRPv6 route advertisements that are received over the PPPoE connections are reported to the routing protocol as coming from a single interface, thus simplifying the routing protocol topology table and providing scalability benefits of each of the routing protocols.
Examples
The following example shows how to create a VMI interface:
Related Commands
|
|
|
|---|---|
Sets a threshold value to minimize hysteresis in a router-to-radio configuration. |
|
Creates a physical subinterface to be associated with the VMIs on a router. |
ip dlep set heartbeat-threshold
To set the maximum number of consecutively missed heartbeats allowed on the DLEP router-to-radio association, use the ip dlep set heartbeat-threshold command in interface-configuration mode.
ip dlep set heartbeat-threshold count
Syntax Description
Maximum number of missed heartbeats allowed. The valid range is from 2 to 8. |
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip dlep set heartbeat-threshold command to set the maximum number of consecutively missed heartbeats allowed on the DLEP router-to-radio association before declaring a failed association.
Examples
The following example sets the DLEP heartbeat threshold to 4:
ip dlep set nbr-activity-timeout
To set the maximum time allowed for inactivity before ending a neighbor session, use the ip dlep set nbr-activity-timeout command in interface-configuration mode. To reset the timeout to the default value, use the no form of this command.
ip dlep set nbr-activity-timeout seconds
no ip dlep set nbr-activity-timeout seconds
Syntax Description
Command Default
The default neighbor-activity timeout is 0 (the timer is disabled).
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip dlep set nbr-activity-timeout command to set the maximum number of seconds before a neighbor session-timer determines a neighbor session is stale.
Examples
The following example sets the neighbor-activity timeout to 2 seconds:
ip dlep set nbr-down-ack-timeout
To set the maximum number of seconds allowed for neighbor sessioning against a lost neighbor-down acknowledgement, use the ip dlep set nbr-down-ack-timeout command in interface-configuration mode. To reset the timeout to the default value, use the no form of this command.
ip dlep set nbr-down-ack-timeout seconds
no ip dlep set nbr-down-ack-timeout seconds
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip dlep set nbr-down-ack-timeout command to set the maximum number of seconds allowed for neighbor sessioning against a lost neighbor-down acknowledgement.
Examples
The following example sets the neighbor-down-ack timeout to 12 seconds:
ip dlep set peer-terminate-ack-timeout
To set the maximum number of seconds allowed for neighbor sessioning against a lost peer-terminate-acknowledgement, use ip dlep set peer-terminate-ack-timeout command in interface-configuration mode. To reset the timeout to the default value, use the no form of this command.
ip dlep set peer-terminate-ack-timeout seconds
no ip dlep set peer-terminate-ack-timeout seconds
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip dlep set nbr-down-ack-timeout command to set the maximum number of seconds allowed for neighbor sessioning against a lost peer-terminate-acknowledgement.
Examples
The following example sets the neighbor-down ack timeout to 12 seconds:
ip dlep vtemplate
To initiate DLEP on the interface (and set the virtual-template interface number), use the ip dlep vtemplate command in interface-configuration mode. To disable DLEP on the interface, use the no form of this command.
ip dlep vtemplate number [port number]
no ip dlep vtemplate number [port number]
Syntax Description
(Optional) Keyword and port number to designate the port used for the virtual-template interface. The port number valid range is from 1 to 65534. |
Command Default
If you do not specify a port number, the default port number used is 55555.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ip dlep vtemplate command to specify a virtual-template interface number for DLEP. When assigning this number, you are initiating DLEP on the interface.
To change the virtual-template interface number for DLEP, you must enter the no version of the last ip dlep vtemplate command you entered before entering the new ip dlep vtemplate command.
Examples
The following example shows how to set the DLEP virtual-template interface number to 88:
The following example shows how to set the DLEP virtual-template interface number to 88 and then change it to 96:
ip mux
To enable IP multiplexing on an interface enter the ip mux command. To disable IP multiplexing on an interface use the no form of the command.
Syntax Description
To enable IP multiplexing on an interface enter the ip mux command. |
|
To disable IP multiplexing on an interface use the no form of the command. |
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
IP multiplexing must be enabled on the interface for the interface to receive or send IP multiplexing superframes.
Examples
The following example shows how to configure IP multiplexing in IPv6 on interface FastEthernet 0/1.
ip mux cache
To set the IP multiplex cache size in bytes, enter the ip mux cache command.
Syntax Description
Maximum cache size in bytes. Valid values range from 1000000 to 4294967295. |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not enter a cache size, the IP multiplexing packet handler defaults to 1,000,000 bytes. A 1,000,000 byte cache contains 11363 entries.
Examples
The following example shows how to configure the IP multiplexing cache size to 5,000,000.
ip mux policy
To create an IP multiplexing DSCP policy with a specified name and enter IP multiplexing policy mode, enter the ip mux policy command. To delete the IP multiplexing policy, use the no form of this command.
{ip | ipv6} mux policy policy_name
[no] {ip | ipv6} mux policy policy_name
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can specify up to three policies in addition to the default policy.
Examples
The following example shows how to configure an IPv6 multiplexing DSCP policy with the name routeRTP-SJ and enter IPv6 multiplexing policy configuration mode.
ip mux profile
To create an IP multiplexing profile with a specified name and enter IP multiplexing profile mode, enter the ip mux profile command. To delete the IP multiplexing profile, use the no form of this command.
{ip | ipv6} mux profile profile_name
[no] {ip | ipv6} mux profile profile_name
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
There is no default profile. You can specify up to 500 profiles.
Examples
The following example shows how to configure an IPv6 multiplexing profile with the name routeRTP-SJ and enter IPv6 multiplexing profile configuration mode.
ip mux udpport
To specify a destination UDP port to use for multiplexed packets, enter the ip mux udpport command.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not enter a port number, the system uses the default port 6682.
Examples
The following example shows how to configure the UDP port or IP multiplexing packets to 5000.
ip r2cp heartbeat-threshold
To set the maximum number of missed R2CP heartbeat messages allowed before declaring the router-to-radio association failed, use the ip r2cp heartbeat-threshold command in interface-configuration mode.
ip r2cp heartbeat-threshold count
Syntax Description
The number of missed R2CP heartbeats allowed before declaring a failed association between the router and locally attached radio. |
|
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp heartbeat-threshold command to set the R2CP heartbeat threshold. This heartbeat threshold is the number of consecutively missed R2CP heartbeats allowed before declaring the router-to-radio association failed.
Examples
The following example sets the R2CP heartbeat threshold to 3:
ip r2cp node-terminate-ack-threshold
To set the R2CP node-terminate acknowledgement threshold, use the ip r2cp node-terminate-ack-threshold command in interface-configuration mode. To reset the default-node terminate acknowledgement threshold to the default value, use the no form of this command.
ip r2cp node-terminate-ack-threshold value
no ip r2cp node-terminate-ack-threshold value
Syntax Description
The number of missed and/or lost R2CP node acknowledgements allowed before declaring the terminate effort complete. |
|
Command Default
The default R2CP node-terminate acknowledgement threshold is 3.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp node-terminate-ack-threshold command to set the number of missed and/or lost R2CP node acknowledgements allowed before declaring the terminate effort complete.
Examples
The following example sets the R2CP node-terminate-ack-threshold to 2:
Related Commands
|
|
|
|---|---|
Sets the number of milliseconds the client waits for the node-terminate acknowledgment. |
ip r2cp node-terminate-ack-timeout
To set the R2CP node-terminate acknowledgement timeout, use the ip r2cp node-terminate-ack-timeout command in interface-configuration mode. To reset the R2CP node-terminate acknowledgement timeout to the default value, use the no form of this command.
ip r2cp node-terminate-ack-timeout milliseconds
no ip r2cp node-terminate-ack-timeout milliseconds
Syntax Description
The maximum number of milliseconds allowed by R2CP when waiting for the node-terminate acknowledgement. |
|
Command Default
The default node-terminate acknowledgement timeout is 1000 milliseconds.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp node-terminate ack-timeout command to set the maximum number of milliseconds the client can wait for a node-terminate acknowledgement.
Examples
The following example sets the node-terminate acknowledgement timeout to 2200 milliseconds for R2CP:
Related Commands
|
|
|
|---|---|
Sets the number of missed and/or lost node acknowledgements allowed by R2CP before declaring the terminate effort complete. |
ip r2cp port
To specify a port for R2CP, use the ip r2cp port command in interface-configuration mode. To reset the R2CP port number to the default value, use the no form of this command.
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example sets the R2CP port to 5858:
ip r2cp session-activity-timeout
To configure the R2CP neighbor session-activity timeout, use the ip r2cp session-activity-timeout command in interface-configuration mode. To reset the neighbor session-terminate activity timeout to the default value, use the no form of this command.
ip r2cp session-activity-timeout seconds
no ip r2cp session-activity-timeout seconds
Syntax Description
The valid range for R2CP neighbor session-activity timeout is from 0 to 4 seconds. |
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp session-activity-timeout command to set the maximum number of seconds before a neighbor session-timer determines a neighbor session is stale.
Examples
The following example sets the neighbor-session activity timeout for R2CP to 2 seconds:
ip r2cp session-terminate-ack-threshold
To set the R2CP neighbor session-terminate acknowledgement threshold, use the ip r2cp session-terminate-ack-threshold command in interface-configuration mode. To reset the R2CP neighbor session terminate-acknowledgement threshold to the default value, use the no form of this command.
ip r2cp session-terminate-ack-threshold value
no ip r2cp session-terminate-ack-threshold value
Syntax Description
The number of missed and/or lost R2CP neighbor session acknowledgements allowed before declaring the terminate effort complete. |
|
Command Default
The default neighbor session-terminate acknowledgement threshold is 3.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp session-terminate-acknowledgement-threshold command to set the number of missed and/or lost R2CP neighbor session acknowledgements allowed before declaring the terminate effort complete.
Examples
The following example sets the R2CP neighbor session-terminate acknowledgement threshold to 4:
Related Commands
|
|
|
|---|---|
Sets the amount of time the client waits for the neighbor session terminate acknowledgment in milliseconds. |
ip r2cp session-terminate-ack-timeout
To set the maximum number of milliseconds allowed on the R2CP interface before sending a neighbor session terminate-acknowledgement, use the ip r2cp session-terminate-ack-timeout command in interface-configuration mode. To reset the timeout to the default value, use the no form of this command.
ip r2cp node-terminate-ack-timeout milliseconds
no ip r2cp node-terminate-ack-timeout milliseconds
Syntax Description
The time duration allowed by R2CP when waiting for the neighbor session-terminate acknowledgement. |
|
Command Default
The neighbor session terminate-acknowledgement timeout default is 1000 milliseconds.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp session-terminate-ack-timeout command to set the amount of time the client waits for the node terminate acknowledgement to occur in milliseconds.
Examples
The following example sets the neighbor session terminate-acknowledgement timeout to 2400 milliseconds for R2CP:
Related Commands
|
|
|
|---|---|
Sets the number of missed and/or lost session acknowledgements allowed by R2CP before declaring the terminate effort complete. |
ip r2cp virtual-template
To set a virtual-template access number for R2CP, use the ip r2cp virtual-template command in interface-configuration mode. To free a virtual template from R2CP, use the no form of this command.
ip r2cp virtual-template number
no ip r2cp virtual-template number
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the ip r2cp virtual-template command to specify a virtual-template access number for R2CP. When creating a virtual-access interface, R2CP requires this access number for virtual-template selection.
Examples
The following example sets the R2CP virtual-template access number to 224:
manet cache
To configure the number of MANET cached LSA updates and acknowledgments, use the manet cache command in router-configuration mode. To restore the default values, use the no form of this command.
manet cache { update update-value | acknowledgment ack-value }
no manet cache { update | acknowledgment }
Syntax Description
Defaults
Command Modes
Router configuration (config-router)
Command History
|
|
|
|---|---|
When you set the cache size, the router keeps a larger number of temp LSAs and ACKs. If the cache fills up before the timers expire, the LSAs and ACKs are deleted from the cache. In some cases, the deleted ACKs can cause the router to flood 1-hop neighbors because the router no longer knows about the deleted ACKs.
If you increase the size of the cache, you might prevent non-primary relay routes from flooding in the case when ACKs were deleted because the cache became full before the ACK timer expired. Increasing the cache size reduces the amount of memory available for the cache storage.
Before you decide to increase the cache size, ensure that the free memory is not reduced to levels that can affect basic route processing.
Assessing How Cache Size Affects Performance
It is difficult to assess the number of times that flooding occurs because LSAs and ACKs have been deleted before the ACK timer expired. Use the show ospfv3 command to compare the current and maximum cache values. Over time, if the two values are very close, it indicates that the cache is filling up faster than the timer expiration is occurring. In that case, increasing the cache size may be helpful.
Examples
The following example uses cache size for the LSA update and LSA ACKs. The manet cache update command optimizes the exchange of the LS database while forming adjacencies with new neighbors in the radio environment. The result is minimized OSPF control traffic and reduced use of radio bandwidth. The ACK cache size improves the dynamic relaying of the LSA update information:
The lines that begin with "LSA cache Disabled" and "ACK cache Disabled" contain the cache size information.
Related Commands
|
|
|
|---|---|
manet hello unicast
To configure whether MANET hello requests and responses are sent as unicast packets or multicast packets use the manet hello unicast command in router-configuration mode. To return to multicast MANET hello requests, use the no form of this command.
Syntax Description
Configures manet hello requests and responses to send in unicast. |
Command Default
Command Modes
Router configuration (config-rtr)
Command History
|
|
|
|---|---|
Usage Guidelines
For broadcast radios, multicast mode typically provides improved performance with reduced bandwidth utilization. For point-to-point radios, unicast mode typically provides improved performance and reduced bandwidth utilization.
Note For optimal performance, configure all nodes consistently.
Examples
The following example shows how to configure the manet hello unicast command.
manet peering selective
To enable selective peering on a per-area or per-interface basis and configure the maximum number of redundant paths to each neighbor, use the manet peering selective command in router-configuration mode. To disable selective MANET peering, use the no form of this command.
manet peering selective [redundancy redundancy-count ] [ per-interface ]
Syntax Description
Command Modes
Router configuration (config-rtr)
Command History
|
|
|
|---|---|
Usage Guidelines
Selective peering will only be enabled for instances of the OSPF process for which the corresponding interface have been configured with the ospfv3 network manet command.
Examples
The following example shows how to enable manet selective peering per interface with a redundancy of 10.
manet willingness
To configure the overlapping relay willingness value on a MANET router, use the manet willingness command in router-configuration mode. To disable a willingness value, use the no form of this command which restores the default willingness value of 128.
Syntax Description
Defaults
Command Modes
Router configuration (config-rtr)
Command History
|
|
|
|---|---|
Usage Guidelines
Willingness is a one-octet unsigned integer describing the willingness of the sender to act as an active overlapping relay for its peers. A willingness value of 100 is less willing to become a relay than a value of 128.
A willingness value of 0 means that the router will NEVER be chosen as an active relay by its peers. A willingness value of 255 means that the router will ALWAYS be chosen as an active relay by its peers.
Examples
The following example shows how to controls the willingness of the router to be an active relay for the MANET network:
Related Commands
|
|
|
|---|---|
matchdscp
To specify a DSCP value used to match IP multiplexed packets for the policy, enter the matchdscp command.
Syntax Description
Command Modes
IP multiplexing policy configuration (config-ipmux-policy)
IPv6 multiplexing policy configuration (config-ipmux-policy-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
Make sure that the DSCP values do not overlap between policies. If the DSCP values do overlap, then the first policy to match the DSCP value from the top of the list is selected.
Examples
The following example shows how to configure the DSCP value to 45 in the IPv6 Multiplexing policy routeRTP-SJ.
maxlength
To specify the largest packet size that the multiplex profile can hold for multiplexing, enter the maxlength command. To reset the policy to multiplex any packet that fits in the superframe, use the no form of the command.
Syntax Description
Maximum packet size in bytes. Valid values range from 64 to 1472 bytes |
Command Default
By default, the policy multiplexes any packet that fits into the superframe.
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify a maximum packet size for multiplexing, the maximum packet size will default to the configured MTU size minus the length of the superframe header (28 bytes for IPv4, 48 bytes for IPv6).
Examples
The following example shows how to configure the maximum packet size that can go into the IP multiplexing profile routeRTP-SJ to 1472 bytes.
mode
To enable VMI to support multicast traffic, use the mode command in interface-configuration mode. To return the interface to the default mode (aggregate), use the no form of this command.
Syntax Description
Keyword to set the mode to aggregate. All virtual-access interfaces created by PPPoE neighbor sessions are logically aggregated under the VMI. |
|
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.4(15)T to support multicast traffic on Virtual Multipoint Interfaces (VMIs). |
Usage Guidelines
Use this command to support multicast traffic in router-to-radio configurations.
Aggregate mode is the default mode for VMI, where VMI aggregates all virtual-access interfaces logically. To enable VMI to forward packets to the correct virtual-access interface, you must define applications such as EIGRP and OSPFv3 (all applications above Layer 2) on VMI.
Using bypass mode is recommended for multicast applications.
In bypass mode, the virtual-access interfaces are directly exposed to applications running above Layer2. In bypass mode, definition of a VMI is still required because the VMI continues to manage presentation of cross-layer signals such as neighbor up, neighbor down, and metrics. However, applications will still be aware on the actual underlying virtual-access interfaces and send packets to them directly.
Using bypass mode can cause databases in the applications to be larger because knowledge of more interfaces are required for normal operation.
After you enter the mode command, Cisco recommends that you copy the running configuration to NVRAM because the default mode of operation for VMI is to logically aggregate the virtual-access interfaces.
Examples
The following examples set the interface mode to bypass:
The following example shows how to enable Multicast Support on a VMI Interface:
Note Enabling Multicast on VMI interfaces includes changing the VMI interface to bypass mode and enabling "ip pim" on the virtual-template interface.
Related Commands
|
|
|
|---|---|
mtu
To specify the maximum transmission unit (MTU) size for an outbound superframe, enter the mtu command. To reset the MTU to 1500 bytes, use the no form of the command.
Syntax Description
MTU size of the outbound superframe in bytes. Valid values range from 256 to 1500 bytes |
Command Default
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify an MTU size, the IP multiplex packet handler uses the default value of 1500 bytes.
For each new packet being added to the superframe, the IP multiplex packet handler checks the byte count of the multiplex queue. If the queue byte count and the superframe header length exceeds the configured MTU size, it builds a superframe from the previous packets and the new packet becomes the first packet of the next superframe.
If you enter the mtu command again, then the MTU size overwrites the previously entered size.
The superframe size specified in the mtu command includes the IP frame header for the superframe of 48 bytes for IPv4 and 28 bytes for IPv4 packets. Therefore an IPv6 mtu configured to 1400 bytes will accept 1352 bytes of data before sending a full superframe. An IPv4 mtu configured to 1400 bytes will accept 1372 bytes of data before sending a full superframe.
Examples
The following example shows how to configure the MTU size for IP multiplexing profile routeRTP-SJ to 1000 bytes.
ospfv3 area
To attach an interface to a specific OSPFv3 area and enable routing of IPv6 network traffic using IPv4 or IPv6 addresses, use the ospfv3 area command in interface-configuration mode. To detach the interface from the OSPFv3 area, use the no form of this command.
ospfv3 process-id area area-number {ipv4 | ipv6} [instance instance-number]
no ospfv3 [ process-id ] area area-number {ipv4 | ipv6} instance instance-number
Syntax Description
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
You must enter this command to attach an interface to a specific OSPFv3 process and instance. After you have attached an interface to a specific OSPFv3 process and interface, you can enter other OSPFv3 characteristics.
An interface can only support one IPv4 address family process and one IPv6 address family process at the same time.
Examples
The following example shows a typical configuration with both IPv6 and IPv4 routing in OSPF that use the default instance numbers.
ospfv3 cost dynamic
To specify that the OSPF cost associated with a path on an interface is dynamic, use the ospfv3 cost dynamic command in interface-configuration mode.
ospfv3 [ process-id ] cost dynamic
Syntax Descriptionz
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here may be assigned administratively when OSPF routing is enabled.The range is 1 to 65535. |
Command Default
By default, MANET interfaces are set to use dynamic costs. Non-MANET networks are set to use static costs.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
To reset the OSPF cost associated with an interface to a static cost, enter the OSPFv3 cost command.
When the network type is set to MANET, the OSPF cost associated with an interface automatically sets to dynamic. All other network types, keep the interface cost, and you must enter the ospfv3 cost dynamic command to change the cost to dynamic.
Examples
The following example shows how to configure the OSPFv3 instance 4 to use dynamic costing for the OSPF interface:
Related Commands
|
|
|
|---|---|
Configure default metric value to use until metric information is received from the radio. |
|
Amount of impact a link metric change has on the dynamic cost. |
|
ospfv3 cost dynamic default
To specify that the OSPF interface cost associated as dynamic, but use a static value until link metric data arrive, use the ospfv3 cost dynamic default command in interface-configuration mode. To reset the interface cost, use the no form of this command.
ospfv3 [ process-id ] cost dynamic default interface-cost
no ospfv3 [ process-id ] cost dynamic default
Syntax Descriptionz
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
For a MANET interface, if you do not specify a default dynamic cost, OSPF uses the interface cost until it receives link metric data.
Examples
The following example shows how to configure the OSPFv3 instance 4 to use 30 as the default cost until link metric data arrive for dynamic costing:
Related Commands
|
|
|
|---|---|
Amount of impact a link metric change has on the dynamic cost. |
|
ospfv3 cost dynamic hysteresis
To enable cost dynamic hysteresis, use the ospfv3 cost dynamic hysteresis command in interface-configuration mode. To disable cost dynamic hysteresis use the no form of this command.
ospfv3 [ process-id ] cost dynamic hysteresis [threshold threshold_value | percent percent_value]
no ospfv3 [ process-id ] cost dynamic hysteresis [threshold threshold_value | percent percent_value]
Syntax Description
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to dampen the frequency of OSPFv3 route cost changes due to small changes in link metrics. The threshold option specifies the magnitude of change in cost before OSPFv3 is notified. The percent option specifies the change relative to the original cost necessary before OSPFv3 is notified.
The n o ospfv3 cost dynamic hysteresis command disables cost dynamic hysteresis. The no ospfv3 cost dynamic hysteresis command with the threshold or percent keywords leaves hysteresis enabled and returns the type and value to their defaults.
If hysteresis is enabled without a mode, the default mode is threshold and the default threshold-value is 10.
The higher the threshold or percent value is set, the larger the change in link quality required to change OSPF route costs.
Examples
The following example sets the cost dynamic hysteresis to 10 percent for OSPFv3 process 4:
Related Commands
|
|
|
|---|---|
Configure default metric value to use until metric information is received from the radio. |
|
Amount of impact a link metric change has on the dynamic cost. |
|
ospfv3 cost dynamic weight
When dynamic cost is configured, OSPF route cost is calculated from a set of link metrics. To change how each link metric affects route cost, use the ospfv3 cost dynamic weight command in interface-configuration mode. The no version of this command sets the weight to the default weight for the specified metric.
ospfv3 process-id cost dynamic weight [threshold threshold_value | percent percent_value]
no ospfv3 process-id cost dynamic weight [threshold threshold_value | percent percent_value]
Syntax Description
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The default weight for throughput, resources, latency, and L 2-factor is 100%.
The higher the threshold or percent value is set, the larger the change in link quality required to change OSPF route costs.
Examples
The following example sets the cost dynamic weight for latency to 20%:
Related Commands
|
|
|
|---|---|
Configure default metric value to use until metric information is received from the radio. |
|
Displays information on the OSPFv3 interfaces including weights. |
|
ospfv3 dead-interval
To set the time period for which hello packets must not be seen before neighbors declare the router down, use the ospfv3 dead-interval command in interface-configuration mode. To return to the default time, use the no form of this command.
ospfv3 [ process-id ] dead-interval seconds
no ospfv3 [ process-id ] dead-interval
Syntax Description
Command Default
The default interval is four times the interval set by the ospfv3 hello-interval command.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
If no hello-interval is specified, the default dead-interval is 120 second for MANETs and 40 seconds for all other network types.
The interval is advertised in router hello packets. This value must be the same for all routers and access servers on a specific network.
Examples
The following example sets the OSPF dead interval to 60 seconds for OSPFv3 process 6:
Related Commands
ospfv3 hello-interval
To specify the interval between hello packets that the Cisco IOS software sends on the interface where the OSPFv3 address family is defined, use the ospfv3 hello-interval command in interface-configuration mode. To return to the default time, use the no form of this command.
ospfv3 [ process-id ] hello-interval seconds
no ospfv3 [ process-id ] hello-interval
Syntax Description
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
This value is advertised in the hello packets. The smaller the hello interval, the faster 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 for OSPFv3 process 4:
Related Commands
ospfv3 manet peering cost
Use selective peering to minimize the full neighbor adjacencies in a MANET. To set a minimum cost change threshold necessary before a new neighbor is considered for selective peering, use the ospfv3 manet peering cost command in interface-configuration mode. To exclude cost considerations from the selective peering decision, use the no form of this command.
ospfv3 [ process-id ] manet peering cost {threshold threshold_value | percent percent_value}
no ospfv3 [ process-id ] manet peering cost
Syntax Description
Command Default
The default MANET peering cost is 0. No incremental improvement in route cost is required to consider selective peering with a new neighbor.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
When selective peering is configured at a given redundancy level, the first 50% of redundant paths do not consider the cost change threshold associated with this command. This allows a minimum OSPFv3 topology to be established in high cost networks.
For example, if you configure selective peering to have a redundancy level of 3 (a total of four paths allowed), the first two neighbors are considered for selective peering, regardless of the neighbor cost. Only the subsequent paths are held to the relative cost change requirements.
Examples
The following example shows how to set the MANET peering cost threshold to 3000.
Related Commands
ospfv3 manet peering link-metrics
To configure and OSPFv3 process to wait for link metrics from a neighbor before attempting selective peering with that neighbor, use the ospfv3 manet peering link-metrics command in interface-configuration mode. The threshold value specifies a minimum incremental improvement over the existing OSPFv3 route cost before attempting selective peering. The no version of the command disables the requirement to wait for link metrics before attempting selective peering.
ospfv3 [ process-id ] manet peering link-metrics threshold
no ospfv3 [ process-id ] manet peering link-metrics
Syntax Description
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
By default, selective peering does not require initial link metrics. If you enter this command without a specified threshold, the default threshold is 0.
Examples
The following example shows how to set the peering link metrics threshold to 3000 for OSPFv3 process 4.
Related Commands
|
|
|
|---|---|
Enable selective peering on a per-area or per-interface basis and configure the maximum number of redundant paths to each neighbor. |
ospfv3 network
To configure the OSPFv3 network type to a type other than the default for a given medium, use the ospfv3 network command in interface-configuration mode. To return to the default value, use the no form of this command.
ospfv3 [ process-id ] network { broadcast | non-broadcast | { point-to-multipoint [ non-broadcast ] | point-to-point | manet}
no ospfv3 [ process-id ] network
Syntax Description
Defaults
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the ospfv3 network manet command to enable relaying and caching of LSA updates and LSA ACKs on the MANET interface. This will result in a reduction of OSPF traffic and save radio bandwidth
By default, selective peering is disabled on MANET interfaces.
By default, the OSPFv3 dynamic cost timer is enabled for the MANET network type, as well as caching of LSAs and LSA ACKs received on the MANET interface. The following default values are applied for cache and timers:
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 non-broadcast multiaccess 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 non-broadcast assumes that there are virtual circuits from every router to every router or fully meshed network. There are other configurations where this assumption is not true, for example, a partially meshed network. In these cases, you can configure the OSPF network type as a point-to-multipoint network. Routing between two routers that are not directly connected will go through the router that has virtual circuits to both routers. You need not configure neighbors when using this feature.
If this command is issued on an interface that does not allow it, this command will be ignored.
OSPF has two features related to point-to-multipoint networks. One feature applies to broadcast networks; the other feature applies to non-broadcast networks:
Related Commands
|
|
|
|---|---|
Configure default metric value to use until metric information is received from the radio. |
|
Amount of impact a link metric change has on the dynamic cost. |
outdscp
To specify a DSCP value used for the outbound IP multiplexed superframe for the policy, enter the outdscp command.
Syntax Description
Command Modes
IP multiplexing policy configuration (config-ipmux-policy)
IPv6 multiplexing policy configuration (config-ipmux-policy-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not enter a value for outdscp, superframes are sent with the DSCP bit set as 0.
Examples
The following example shows how to configure the DSCP value to 10 for the outbound multiplexed superframe in the IPv6 Multiplexing policy routeRTP-SJ.
physical-interface
To associate physical interfaces with the VMI on a router, use the physical-interface command command in interface-configuration mode. To remove the interface associated interface, use the no form of this command.
physical-interface interface-type / slot
Syntax Description
Specifies the type of interface or subinterface; value can be Ethernet, Fast Ethernet, or Gigabit Ethernet. |
|
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.4(15)T to support VMIs in Mobile Ad Hoc Router-to-Radio Networks. |
Usage Guidelines
Use the physical-interface command to create a physical subinterface.
Only one physical interface can be assigned to a VMI interface. Because a very high number of VMI interfaces can be used, assign a new VMI for each physical interface.
Examples
The following examples shows how to configure the physical interface for vmi1 to FastEthernet0/1.
Related Commands
|
|
|
|---|---|
router ospfv3
To enter router configuration mode and enable an OSPFv3 routing process to route IPv6 or IPv4 address-family traffic in IPv6 networks, use the router ospfv3 command in global configuration mode. To terminate an OSPFv3 routing process, use the no form of this command.
Syntax Description
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here may be assigned administratively when OSPF routing is enabled.The range is 1 to 65535. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You can specify multiple IP OSPFv3 routing processes in each router.The router ospfv3 command must be followed by the address-family command for routing of IPv6 traffic to occur.
Each OSPFv3 routing process must have a unique router ID. If a router ID is not configured manually (using the router-id A.B.C.D command), Cisco IOS attempts to auto-generate a router ID for this process from the IPv4 address of a configured interface. If Cisco IOS cannot generate a unique router-id, the OSPFv3 process remains inactive.
When you use the no form of the global router ospfv3 process-id command, the associated interface configuration ospfv3 process-id command is automatically removed from your configuration.
Examples
The following example configures an OSPF routing process and assign a process number of 4:
Related Commands
|
|
|
|---|---|
Defines the interfaces on which OSPFv3 runs and defines the area ID for those interfaces. |
service declassify
To enable the declassification (zeroization) function, enter the service declassify command. Use the no form of the command to disable the declassification process.
service declassify {erase-flash | erase-nvram | erase-all | erase-default} [trigger GPIO pin-number]
[no] service declassify {erase-flash | erase-nvram | erase-all | erase-default} [trigger GPIO pin-number]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5921 ESR does not support this comand.
The network interfaces are shut down when declassification starts.
The output that appears on the console when declassification starts depends on which options have been configured. It is not possible to document exactly what appears on the screen, because of the complex interactions between the declassification process and the logging process during declassification.
You can use the trigger GPIO keyword after any of the other keywords for this command to start the declassification monitoring processing at the specified pin-number. By default the Cisco 5930 ESR starts the declassification monitoring process at GPIO pin 4.
Examples
The following examples show the console output when declassification is invoked.
If you enter the
service declassify erase-all command, the Flash file system is erased and the Cisco 5930 Flash file system will no longer have a bootable Cisco IOS image. You must initiate error recovery action in order to have a bootable Cisco IOS image.
The startup configuration file is also erased; the router boots from the factory default configuration the next time it is booted.
The output from the service declassify erase-all command resembles the following:
service declassify erase-flash
When you enter the
service declassify erase-flash command, the flash file system is erased and there will not be a bootable image for the router in the Flash file system. Error recovery actions must be initiated to load a bootable image.
The startup configuration file is not erased if you enter the service declassify erase-flash command. When the Cisco 5930 ESR is booted, it uses the startup configuration file in NVRAM.
The output from the service declassify erase-flash command resembles the following:
service declassify erase-nvram
Note If you enter the service declassify erase-nvram command, the flash file system is not erased. The bootable image in the Flash file system remains and the Cisco 5930 ESR can be booted. The startup configuration file is erased; because the router has no configuration file, it boots from the default configuration.
The output fromthe service declassify erase-nvram command resembles the following:
service declassify erase-default
If you enter the service declassify erase-default command, neither the flash file system or NVRAM are erased. The declassification process quickly reaches a state in which the cisco IOS logging process is not operative and the common command output is not seen.
Even though this declassification process shutsdown interfaces, no messages display indication this.
The output fromthe service declassify erase-default command resembles the following:
Related Commands
|
|
|
|---|---|
show declassify
To display the state of the zeroization (declassify) function (enabled, in progress, and so forth) and the sequence of declassification steps that will be performed, use the show declassify command in global configuration mode.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5921 ESR does not support this comand.
The output for the show declassify command indicates the following things:
- If zeroization (declassification) is enabled
- If zeroization (declassification) is in progress,
- The General Purpose Input/Output (GPIO) pin used as a trigger
- Any optional behaviors that are enabled
The output also shows all actions that will be performed when declassification is initiated.
Examples
The following example shows output for the show declassify command:
Table A-1 describes the common fields in the show declassify command output.
Related Commands
|
|
|
|---|---|
show dlep clients
To display router-to-radio peer associations, use the show dlep clients command in privileged EXEC mode.
show dlep clients [ interface ] [ peer-id ]
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show dlep clients command to display router-to-radio peer associations.
Examples
The following example shows how to display router-to-radio peer associations on all interfaces:
Related Commands
|
|
|
|---|---|
show dlep config
To display the DLEP server configuration, use the show dlep config command in privileged EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show dlep config command to display the DLEP server configuration.
Display DLEP server configuration example
The following example shows how to display the DLEP server configuration:
Related Commands
|
|
|
|---|---|
show dlep counters
To display DLEP counters, use the show dlep counters command in privileged EXEC mode.
show dlep counters [ vmi-interface ]
Syntax Description
Command Default
If no arguments are specified, counters on all VMI interfaces with DLEP configured are displayed.
Command Modes
Command History
|
|
|
|---|---|
Examples
The following is example output from the show dlep counters command used to display input and output DLEP counts on the gigabitEthernet interface:
Table A-2 describes the significant count definitions in the show dlep counters command display.
show dlep neighbors
To display neighbor sessions on the specified interface, use the show dlep neighbors command in privileged EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show dlep neighbors command to display the established neighbor sessions.
The following example shows how to display the established neighbor sessions on all interfaces:
Related Commands
|
|
|
|---|---|
show ip eigrp neighbors
To display neighbors discovered by Enhanced Interior Gateway Routing Protocol (EIGRP), use the show ip eigrp neighbors command in EXEC mode.
show ip eigrp neighbors [interface-type | as-number | static | detail]
Syntax Description
(Optional) Keyword to display detailed neighbor information. |
Command Modes
Command History
|
|
|
|---|---|
Support for NSF restart operations was integrated into the output. |
|
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
Use the show ip eigrp neighbors command to determine when neighbors become active and inactive. The show ip eigrp neighbors command is also useful for debugging certain types of transport problems.
Examples
The following is example output from the show ip eigrp neighbors command:
show ip mux
To display configured IP multiplexing statistics, use the show ip mux command in user EXEC or privileged EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to display IP multiplex statistics.
Table A-3 describes the significant fields of the show ip mux command output.
show ip mux cache
To display cache statistics, use the show ip mux cache command in user EXEC or privileged EXEC mode.
show {ip | ipv6} mux cache [profile profile_name | nomux | stale]
Syntax Description
Keyword and profile name to show IP multiplex cache contents by profile |
|
Keyword to display IP multiplex cache of do not multiplex entries |
|
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to display the cache statistics.
Table A-4 describes the significant fields of the show ip mux cache command output.
The following example shows how to display the cache statistics for do-not-multiplex entries:
The following example shows how to display the cache statistics for stale entries:
The following example shows how to display the cache statistics for the IP multiplexing profile r1.
show ip mux interface
To display configured IP multiplexing statistics for an interface, use the show ip mux interface command in user EXEC or privileged EXEC mode.
show {ip | ipv6} mux interface interface_type
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify an interface type, the show ip mux interface commands displays statistics for all interfaces with IP multiplexing configured.
Examples
The following example shows how to display IP multiplex statistics for Ethernet 0/1.
Table A-5 describes the significant fields of the show ip mux interface command output.
show ip mux profile
To display cache statistics for a specific IP multiplexing profile, use the show ip mux cache profile command in user EXEC or privileged EXEC mode.
show {ip | ipv6} mux profile profile_name
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify a profile_name, the this command displays the statistics for all configured profiles.
Examples
The following example shows how to display the cache statistics for the IPv6 profile r1v6.
Table A-6 describes the significant fields of the show ipv6 mux profile command output.
show ip redirects
To display the address of a default gateway (router) and the address of hosts for which an ICMP redirect message has been received, use the show ip redirects command in user EXEC or privileged EXEC mode.
Command Modes
Command History
Usage Guidelines
This command displays the default router (gateway) as configured by the ip default-gateway command.
The ip mtu command enables the router to send ICMP redirect messages.
Examples
The following is example output from the show ip redirects command:
Related Commands
show ipv6 eigrp neighbors
To display the neighbors discovered by EIGRP for IPv6, use the show ipv6 eigrp neighbors command in user EXEC or privileged EXEC mode.
show ipv6 eigrp neighbors [interface-type | as-number | static | detail]
Syntax Description
(Optional) Keyword to display detailed neighbor information. |
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
This command was integrated into Cisco IOS Release 12.2(33)SXH. |
Usage Guidelines
Use the show ipv6 eigrp neighbors command to determine when neighbors become active and inactive. It is also useful for debugging certain types of transport problems.
Examples
The following is example output from the show ipv6 eigrp neighbors command:
show ospfv3
To display information about one or more OSPFv3 routing processes, use the show ospfv3 command in user EXEC or privileged EXEC mode.
Syntax Description
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here may be assigned administratively when OSPF routing is enabled.The range is 1 to 65535. |
Command Modes
Command History
|
|
|
|---|---|
The syntax for the command changed from show IPv6 OSPF to show ospfv3. This output for this command was expanded to include IPv4 and IPv6 address family information. |
Examples
The following is example output from the show ospfv3 command:
show ospfv3 database
To display the contents of the OSPFv3 Link State Advertisement (LSA) database, or selective parts thereof, use the show ospfv3 database command in privileged EXEC mode. The various forms of this command deliver information about different OSPF LSAs.
show ospfv3 [ process-id ] [ area-id ] database
show ospfv3 [ process-id ] [ area-id ] database [ adv-router [ router-id ]]
show ospfv3 [ process-id ] [ area-id ] database [ database-summary ]
show ospfv3 [ process-id ] [ area-id ] database [ external [ link-state-id ] [ adv-router | internal | self-originate ] [ ipv6-address ]]
show ospfv3 [ process-id ] [ area-id ] database [ inter-area prefix [ link-state-id ] [ adv-router | internal | self-originate ] | [ ipv6-address ]]
show ospfv3 [ process-id ] [ area-id ] database [ inter-area router [ link-state-id ] [ adv-router | internal | self-originate ] | [ destination-router-id ]]
show ospfv3 [ process-id ] [ area-id ] database [ link ] [ link-state-id ] [ adv-router | internal | self-originate ] [ interface [ interface-name ]]
show ospfv3 [ process-id ] [ area-id ] database [ network ] [ link-state-id ] [ adv-router | internal | self-originate ]
show ospfv3 [ process-id ] [ area-id ] database [ nssa-external [ link-state-id ] [ adv-router | internal | self-originate ] | [ ipv6-address ]]
show ospfv3 [ process-id ] [ area-id ] database [ prefix ] [ link-state-id ] [ adv-router | internal | self-originate ] [ router | network ]
show ospfv3 [ process-id ] [ area-id ] database [ promiscuous ]
show ospfv3 [ process-id ] [ area-id ] database [ router ] [ adv-router | internal | self-originate ] [ link-state-id ]
show ospfv3 [ process-id ] [ area-id ] database [ self-originate ] [ link-state-id ]
Syntax Description
Command Modes
Command History
Usage Guidelines
The adv-router keyword requires a router ID. The self-originate keyword displays only those LSAs that originated from the local router. Both of these keywords can be appended to all other keywords used with the show ospfv3 database command to provide more detailed information.
Examples
The following is example output from the show ospfv3 database command when no arguments or keywords are used:
Table A-7 describes the significant fields shown in the display.
|
|
|
|---|---|
show ospfv3 flood-list
To display a list of OSPFv3 LSAs waiting to be flooded over an interface, use the s how ospfv3 flood-list command in user EXEC or privileged EXEC mode.
show ospfv3 [ process-id ] flood-list interface- type interface-number
Syntax Description
(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here may be assigned administratively when OSPF routing is enabled.The range is 1 to 65535. |
|
Command Modes
Command History
Usage Guidelines
Examples
The following is example output from the show ospfv3 flood-list command:
Table A-8 describes the significant fields shown in the display.
|
|
|
|---|---|
Identification of the router for which information is displayed. |
|
show ospfv3 interface
To display OSPF-related interface information, use the show ospfv3 interface command in privileged EXEC mode.
show ospfv3 [ process-id ] interface [ interface - type interface-number ] [ brief ]
Syntax Description
Command Modes
Command History
Examples
The following is example output from the show ospfv3 interface command:
Table A-9 describes the significant fields shown in the display.
show ospfv3 neighbor
To display OSPF neighbor information on a per-interface basis, use the show ospfv3 neighbor command in privileged EXEC mode.
The show ospfv3 neighbor command without the process-id displays OSPFv3 neighbor information for both IPv4 and IPv6 address families for all OSPFv3 processes.
show ospfv3 [ process-id ] neighbor [interface- type interface-number ] [ neighbor-id ] [ detail ]
Syntax Description
Command Modes
Command History
Examples
The following is example output from the show ospfv3 neighbor command:
The following is example output from the show ospfv3 neighbor command with the detail keyword:
Table A-10 describes the significant fields shown in the display.
show ospfv3 neighbor manet
To display OSPF neighbor information, use the show ospfv3 neighbor manet command in privileged EXEC mode.
The show ospfv3 neighbor manet command displays manet neighbor information.
show ospfv3 [ process-id ] [ area-id ] neighbor manet
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This output for this command was expanded to include IPv4 and IPv6 address family information. |
Examples
The following is example output from the show ospfv3 neighbor manet command:
show ospfv3 promiscuous acknowledgments
To display the cache of temporary acknowledgments, use the show ospfv3 promiscuous acknowledgments command in privileged EXEC mode.
show ospfv3 [ process-id ] promiscuous acknowledgments [ detail ]
Syntax Description
Command Modes
Command History
Examples
The following is example output from the show ospfv3 promiscuous acknowledgments command using the detail keyword. It The shows that the cache of temporary acknowledgements is not allocated for the router.
Related Commands
|
|
|
|---|---|
Displays lists of information related to the OSPF database for a specific router. |
show pppoe
To display information about active PPPoE neighbor sessions, use the show pppoe command in privileged EXEC mode.
show pppoe {derived group | relay [context all] | session [all | interface | packets] | summary | throttled mac}
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.3(4)T and was enhanced to display information about relayed PPPoE Active Discovery (PAD) messages. |
Examples
The following example shows output for the show pppoe session command:
Table A-11 describes the significant fields shown in the display.
show pppoe derived
To display the cached PPPoE configuration that is derived from the subscriber profile for a specified PPPoE profile, use the show pppoe derived command in privileged EXEC mode.
show pppoe derived group group-name
Syntax Description
PPPoE profile for which the cached PPPoE configuration displays. |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A subscriber profile can be configured locally on the router or remotely on a AAA server. The PPPoE configuration that is derived from a subscriber profile is cached locally under the PPPoE profile. Use the show pppoe derived command to display the cached PPPoE configuration that is derived from the subscriber profile for a specified PPPoE profile.
A subscriber profile contains a list of PPPoE service names. The PPPoE server will advertise the service names that are listed in the subscriber profile to each PPPoE client connection that uses the configured PPPoE profile. A subscriber profile is assigned to a PPPoE profile by using the service profile command in BBA group configuration mode.
Examples
The following example shows the PPPoE configuration for PPPoE profile that is derived from subscriber profile. The services are advertised to each PPPoE client connection that uses PPPoE profile.
Related Commands
show pppoe session
To display information about currently active PPPoE neighbor sessions, use the show pppoe session command in privileged EXEC mode.
show pppoe session [ all | packets ]
Syntax Description
(Optional) Keyword to display detailed information about the PPPoE neighbor session. |
|
(Optional) Keyword to display packet statistics for the PPPoE neighbor session. |
Command Modes
Command History
Examples
Single Neighbor Session: Example
The following is example output from the show pppoe session command:
Table A-12 describes the significant fields shown in the displays.
|
|
|
|---|---|
Displays the state of the neighbor session, which will be one of the following: |
|
Related Commands
|
|
|
|---|---|
Clears PPPoE relay contexts created for relaying PAD messages. |
|
Displays PPPoE relay contexts created for relaying PAD messages. |
show r2cp clients
To display R2CP clients, use the show r2cp clients command in privileged EXEC mode.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the show r2cp clients command to exchange metric information with the radio—either for all radio clients on all interfaces or for one radio client on a specific interface.
Examples
Show all radio clients on all interfaces example
The following example shows how to display all radio clients on all interfaces:
Show all radio clients on all interfaces example
Related Commands
show r2cp config
To display R2CP configuration, use the show r2cp config command in privileged EXEC mode.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
Use the show r2cp config command to display router configuration details for the R2CP interface.
These details include the following components:
Examples
Display R2CP router configuration details example
The following example shows how to display configuration details for the R2CP interface:
Related Commands
|
|
|
|---|---|
Displays radio client information for one or more clients on the R2CP interface. |
|
Displays neighbors on an R2CP interface radio capabilities from a Layer 3, next-hop perspective. |
show r2cp neighbors
To show neighbors for R2CP, including two radio neighbor sessions, use the show r2cp neighbors command in privileged EXEC mode.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The Cisco 5930 ESR does not support this comand.
View neighbors on an R2CP interface to display information about the neighbor with which the radio can talk from a Layer 3, next-hop perspective. The show r2cp neighbors command output allows you to get metric data associated with a next-hop, so you can better understand the paths that the traffic is taking.
Examples
The following example shows metric data for R2CP neighbor sessions:
Related Commands
|
|
|
|---|---|
show vmi counters
The show vmi counters command in privileged EXEC mode displays input and output counts.
show vmi counters [ vmi-interface ]
Syntax Description
Command Default
If no VMI interface is specified, counters for all VMI interfaces are displayed.
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to display the VMI input and output counts for DLEP:
The following example shows vmi counts for DLEP.
Table A-14 describes the count definitions in the show vmi counters command display.
show vmi neighbors
To display information about neighbor connections to the VMI, use the show vmi neighbors command in privileged EXEC mode.
show vmi neighbors [ detail ] [ vmi-interface ]
Syntax Description
(Optional) Keyword to display details about the VMI neighbors. |
|
Command Default
If no arguments are specified, information about all neighbors for all VMI interfaces displays.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.4(15)T. |
Usage Guidelines
The show vmi neighbors command provides a list of devices that have been dynamically discovered by the connected radio devices in a router-to-radio network, and for which connectivity has been achieved through PPPoE and the radio network.
Examples
The following is example output from the show vmi neighbors command used to display dynamically created neighbors on a VMI interface:
Table A-14 describes the significant fields shown in the show vmi neighbors command display.
show vmi neighbors command with detail keyword: Example
The following example shows the details about the known VMI neighbors:
Table A-15 describes the significant fields shown in the show vmi neighbors detail command display.
Related Commands
|
|
|
|---|---|
Creates a virtual multipoint interface (VMI) that can be configured and applied dynamically. |
shutdown
To deactivate an IP multiplexing profile, enter the shutdown command. To activate an IP multiplexing profile, use the no form of the command.
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
You must enter the no shutdown command to activate an IP multiplexing profile so that the IP multiplexing packet handler processes packets for IP multiplexing. A disabled multiplexing profile cannot send superframes, but will accept incoming superframes which match its configured source and destination addresses.
If you want to change the ACL associated with the profile, or edit the ACL associated with the profile, you must enter the shutdown command. After you have changed either the access-list or the ACL associated with the profile, you then enter the no shutdown command to clear the IP multiplexing cache and use the new information.
A multiplexing profile must have both a source and destination address configured in order to be activated.
Examples
The following example shows how to activate the IP multiplexing profile routeRTP-SJ.
singlepacket
Interesting data packets are always transmitted inside a superframe, even if there is only one packet to transmit when the hold timer expires. If you want the IP multiplexing packet handler not to create single packet superframes, enter the no singlepacket command. If you want to send single packet superframes, enter the singlepacket command.
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
By default the IP multiplexing packet handler creates single packet superframes.
Single packet multiplexing applies to all hold queues for a given IP multiplexing profile.
Examples
The following example shows how to configure single packet superframes for IP multiplexing profile routeRTP-SJ.
source
To specify the IPv4 or IPv6 source address for the local endpoint of the IP multiplexing path, enter the source command. To clear the source address, use the no form of the command.
source {ip_addr | ipv6_addr | interface interface_type}
Syntax Description
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
You must configure a source address for the profile in order to use it. If you attempt to issue a no shutdown command when no source address is configured, you will be prompted to configure a source address. If a profile is active, you must issue a shutdown command before changing the source address.
If you enter the source command again, then the new address overwrites the previously entered address.
An incoming superframe must match its source and destination addresses to the destination and source addresses, respectively, in the multiplexing profile in order for the superframe to be demultiplexed. If either address does not match, the superframe is ignored.
Examples
The following example shows how to configure the IPv6 address FE80::A8BB:CCFF:FE01:5700 as the source address for superframe packets.
summary-prefix (OSPFv3)
To configure an IPv6 summary prefix, use the summary-prefix command in router address-family configuration mode. To restore the default, use the no form of this command.
summary-prefix prefix [ not-advertise | tag tag-value ]
no summary-prefix prefix [ not-advertise | tag tag-value ]
Syntax Description
Command Default
Command Modes
Router address family configuration (config-rtr-af)
Command History
Usage Guidelines
The summary-prefix command can be used to summarize routers redistributed from other routing protocols. Multiple groups of addresses can be summarized. The metric used to advertise the summary is the smallest metric of all the more specific routes. This command helps reduce the size of the routing table.
Examples
In the following example, the summary prefix FEC0::/24 includes addresses FEC0::/1 through FEC0::/24. Only the address FEC0::/24 is advertised in an external LSA.
timers manet
To configure MANET timer parameters, use the timers manet command in router-configuration mode. To restore the timer default values, use the no form of this command.
timers manet { ackwait ackwait-value | peering peering-value | pushback pushback-value }
no timers manet { ackwait ackwait-value | peering peering-value | pushback pushback-value }
Syntax Description
Command Modes
Router configuration (config-rtr)
Command History
|
|
|
|---|---|
Usage Guidelines
Non-active relays do not immediately start helping with flooding. Timers can be configured to delay Non-active relays until the active relay finishes its procedure. The timers manet command is used to configure these timers.
Peering Timers on MANET Interfaces
When selective peering is enabled, this timer determines how long the OSPFv3 process waits between selective peering decisions. Use the peering keyword to specify how long the router waits between selective peering decisions.
Acknowledgements on MANET Interfaces
When sending acknowledgments on a MANET interface, a small delay is configured in order to accumulate as many acknowledgments as possible into a single ACK message to reduce the number of messages being sent. Use the ackwait ackwait-value keyword and argument to set the acknowledgment wait timer.
Pushback Timers on MANET Interfaces
Use the pushback keyword to help prevent multiple non-primary relays from flooding at the same time. If a relay has already seen all of the acknowledgements from the nodes for which it is going to relay, it will cancel the pushback timer.
The default value for the pushback timer is 50 percent of the retransmit timer value.
Examples
The following example shows how to set the MANET pushback timer to 50,000 milliseconds, the MANET acknowledgement timer to 1001 milliseconds, and the MANET peering timer to 1000 seconds:
Related Commands
timers throttle spf
To turn on Open Shortest Path First (OSPF) for IPv6 shortest path first (SPF) throttling, use the timers throttle spf command in router-configuration mode. To turn off SPF throttling, use the no form of this command.
timers throttle spf delay next-delay holdtime
Syntax Description
Command Default
Command Modes
Router configuration (config-rtr)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(28)SB. |
|
This command was integrated into Cisco IOS Release 12.4(24)GC. |
Usage Guidelines
The first wait interval between SPF calculations is the amount of time in milliseconds specified by the delay argument.
Use the next-delay argument to set the delay between the first and second SPF calculations.
Each consecutive wait interval is two times the current hold level in milliseconds until the wait time reaches the maximum time in milliseconds as specified by the holdtime argument. Subsequent wait times remain at the maximum until the values are reset or an LSA is received between SPF calculations.
When you configure an OSPFv3 network manet for any interface attached to the OSPFv3 process, the default values for the delay, next-delay, and hold time are reduced to 1000 milliseconds, 1000 milliseconds, and 2000 milliseconds respectively.
Examples
The following example shows a router with the delay and next-delay interval values configured at 40 milliseconds, and the holdtime value to 50 milliseconds :
Related Commands
|
|
|
|---|---|
Displays general information about OSPF for IPv6 routing processes. |
ttl
To insert into the superframe header the time-to-live (TTL) value for outbound superframes, enter the ttl command. To reset the TTL to 64 hops, use the no form of this command.
Syntax Description
Number of hops equivalent to the TTL value inserted into the IP header of the outbound superframe. Valid values range from 1 to 255 hops. |
Command Modes
IP multiplexing configuration (config-ipmux-profile)
IPv6 multiplexing configuration (config-ipmux-profile-v6)
Command History
|
|
|
|---|---|
Usage Guidelines
If you do not specify an TTL, the IP multiplex packet handler uses the default value of 64 hops.
If you enter the ttl command again, then the new TTL value overwrites the previously entered size.
Examples
The following example shows how to configure the TTL size for IP multiplexing profile routeRTP-SJ to 255 hops.
Feedback