-
Cisco IOS IP Mobility Configuration Guide, Release 12.4T
-
Part 1: Mobile IP
-
Configuring Mobile IP
-
Mobile IP MIB Support for SNMP
-
Mobile IP—NAT Detect
-
Mobile IP—Support for Foreign Agent Reverse Tunneling
-
Mobile IP—Challenge/Response Extensions
-
Mobile IP—Generic NAI Support and Home Address Allocation
-
Mobile IP Home Agent Policy Routing
-
Mobile IP—Home Agent Accounting
-
Mobile IP Dynamic Security Association and Key Distribution
-
Mobile IP—Support for RFC 3519 NAT Traversal
-
-
Part 2: Mobile Networks
-
Cisco Mobile Networks
-
Cisco Mobile Networks—Asymmetric Link
-
Cisco Mobile Networks—Static Collocated Care-of Address
-
Cisco Mobile Networks—Priority HA Assignment
-
Cisco Mobile Networks—Tunnel Templates for Multicast
-
Mobile Networks Dynamic Collocated Care-of Address
-
Mobile Networks Deployment MIB
-
Mobile IP—Foreign Agent Local Routing to Mobile Networks
-
Mobile IP—Generic Routing Encapsulation for Cisco Mobile Networks
-
Mobile IP Support for RFC 3519 NAT Traversal on the Mobile Router
-
Mobile IP— Policy and Application-Based Routing for MR Multipath
-
Mobile Router DHCP Support for Dynamic CCoA and Foreign Agent Processing
-
Mobile Ad Hoc Networks for Router-to-Radio Communications
-
-
Part 1: Mobile IP
Table Of Contents
Mobile Ad Hoc Networks for Router-to-Radio Communications
Prerequisites for Mobile Ad Hoc Networks
Restrictions for Mobile Ad Hoc Networks
Information About Mobile Ad Hoc Networks
PPPoE Interfaces for Mobile Radio Communications
Multicast Routing in NBMA Mode
Restrictions for IPv6 Addressing
Link-Quality Metrics Reporting for OSPFv3 and EIGRP
EIGRP Cost Metrics for VMI Interfaces
VMI Metric to EIGRP Metric Conversion
EIGRP Metric Dampening for VMI Interfaces
Neighbor Up and Down Signaling for OSFPv3 and EIGRP
PPPoE Credit-based and Metric-based Scaling and Flow Control
How to Configure Router-to-Radio Links
Configuring a Subscriber Profile for PPPoE Service Selection
Assigning the Subscriber Profile to a PPPoE Profile
Enabling PPPoE Sessions on an Interface
Creating a Virtual Template for IPv4 and IPv6
Creating a VMI Interface for EIGRP IPv4
Creating a VMI Interface for EIGRP IPv6
Setting the EIGRP Change-based Dampening Interval Using Classic-Style Configuration
Setting the EIGRP Change-based Dampening Interval Using Named-Style Configuration
Setting the EIGRP Interval-based Dampening Interval Using Classic-Style Configuration
Setting the EIGRP Interval-based Dampening Interval Using Named-Style Configuration
Enabling Bypass Mode for Multicast Applications
Verifying the VMI Configuration
Configuration Examples for VMI PPPoE
Example: Basic VMI PPPoE Configuration with EIGRP IPv4
Example: Basic VMI PPPoE Configuration with EIGRP for IPv6
Example: VMI PPPoE Configuration with EIGRP for IPv4 and IPv6
Example: EIGRP Change-based Dampening for VMI Interfaces
Example: EIGRP Interval-based Dampening for VMI Interfaces
Example: VMI Configuration Using Multiple Virtual Templates
Examples: IP Address Coordination for the VMI in Aggregate Mode
Examples: Enabling Multicast Support with Bypass or Aggregate Mode
Example: Bypass Mode on VMI Interfaces for Multicast Traffic
Example: OSPFv3 for IPv6 Multicast Traffic Using Bypass Mode
Example: EIGRP for IPv4 Using Bypass Mode
Example: EIGRP for IPv6 Using Bypass Mode
Example: EIGRP with IPv4 and IPv6 Traffic Using Bypass Mode
Example: OSPFv3 for Multicast Traffic Using Aggregate Mode
Example: Configuring Two VMIs and Two Virtual Templates
Examples: QoS Configuration for VMI
Feature Information for Mobile Ad Hoc Networks for Router-to-Radio Communications
Mobile Ad Hoc Networks for Router-to-Radio Communications
First Published: May 17, 2007
Last Updated: July 22, 2011Mobile Ad Hoc Networks (MANET) for router-to-radio communications address the challenges faced when merging IP routing and mobile radio communications in ad hoc networking applications.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Mobile Ad Hoc Networks for Router-to-Radio Communications" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Mobile Ad Hoc Networks
•
•
•
•
•
Prerequisites for Mobile Ad Hoc Networks
To use the PPP over Ethernet (PPPoE) and virtual multipoint interface (VMI) features described in this document, a radio device that implements the PPPoE functionality enhancements described in the RFC 2516 and RFC 5578 is required.
Open Shortest Path First (OSPF) enhancements are not tied to the PPPoE/VMI implementations, and do not require such radio devices.
Restrictions for Mobile Ad Hoc Networks
VMIs can be configured on routed ports on VLAN interfaces.
Information About Mobile Ad Hoc Networks
•
•
•
•
•
•
About MANETs
MANETs for router-to-radio communications address the challenges faced when merging IP routing and mobile radio communications in ad hoc networking applications:
•
•
•
•
Through the router-to-radio link, the radio can inform the router immediately when a node joins or leaves, and this enables the router to recognize topology changes more quickly than if it had to rely on timers. Without this link-status notification from the radio, the router would likely time out while waiting for traffic. The link-status notification from the radio enables the router to respond faster to network topology changes. Metric information regarding the quality of a link is passed between the router and radio, enabling the router to more intelligently decide on which link to use.
With the link-status signaling provided by the router-to-radio link, applications such as voice and video work better because outages caused by topology changes are reduced or eliminated. Sessions are more stable and remain active longer.
Cross-layer feedback for router-to-radio integration of Radio-Aware Routing (RAR) takes advantage of the functions defined in RFC 5578. The RFC 5578 is an Internet Engineering Task Force (IETF) standard that defines PPPoE extensions for Ethernet-based communications between a router and a device, such as a mobile radio, that operates in a variable-bandwidth environment and has limited buffering capabilities. These extensions provide a PPPoE session-based mechanism for sharing radio network status such as link-quality metrics and establishing flow control between a router and an RAR-compliant radio.
An RAR-compliant radio initiates a Layer 2 PPPoE session with its adjacent router on behalf of every router and radio neighbor discovered in the network. These Layer 2 sessions are the means by which radio network status for each neighbor link is reported to the router. The radio establishes the correspondence between each PPPoE session and each link to a neighbor.
Routing Challenges for MANETs
MANETs enable users deployed in areas with no fixed communications infrastructure to access critical voice, video, and data services. For example, soldiers in the field can employ unified communications, multimedia applications, and real-time information dissemination to improve situational awareness and respond quickly to changing battlefield conditions. Disaster managers can use video conferences, database access, and collaborative tools to coordinate multiagency responses within an Incident Command System (ICS) framework. For event planners and trade show managers, MANETs represent a cost-effective way to accommodate mobile end users on a short-term basis.
In MANET environments, highly mobile nodes communicate with each other across bandwidth-constrained radio links. An individual node includes both a radio and a network router, with the two devices interconnected over an Ethernet. Because these nodes can rapidly join or leave the network, MANET routing topologies are highly dynamic. Fast convergence in a MANET becomes a challenge because the state of a node can change well before the event is detected by the normal timing mechanisms of the routing protocol.
Radio link quality in a MANET can vary dramatically because it can be affected by a variety of factors such as noise, fading, interference, and power fluctuation. As a result, avoiding congestion and determining optimal routing paths also pose significant challenges for the router network.
Directional radios that operate on a narrow beam tend to model the network as a series of physical point-to-point connections with neighbor nodes. This point-to-point model does not translate gracefully to multihop, multipoint router environments because it increases the size of each router's topology database and reduces routing efficiency.
Effective networking in a MANET environment therefore requires mechanisms by which
•
•
•
•
PPPoE Interfaces for Mobile Radio Communications
The MANET implementation uses PPPoE sessions to enable intranodal communications between a router and its partner radio. Each radio initiates the PPPoE session as soon as the radio establishes a radio link to another radio. After the PPPoE sessions are active, a PPP session is established end-to-end (router-to-router). This is duplicated each time a radio establishes a new radio link. The VMI on the router can aggregate multiple PPPoE sessions and multiplex them to look like a single interface to the routing processes. Underneath the VMI interface are virtual access interfaces that are associated with each of the PPP/PPPoE connections.
A PPPoE session is established between a router and a radio on behalf of every other router/radio neighbor located in the MANET. These Layer 2 sessions are the means by which radio network status gets reported to the Layer 3 processes in the router. The figure below shows the PPPoE session exchange between mobile routers and directional radios in a MANET network.
Figure 1 PPPoE Session Exchange Between Mobile Routers and Directional Radios
This capability requires that an RAR-compliant radio be connected to a router through Ethernet. The router always considers the Ethernet link to be up. If the radio side of the link goes down, the router waits until a routing update timeout occurs to declare the route down and then updates the routing table. The figure below shows a simple router-to-radio link topology.
The routing protocols optimized for VMI PPPoE are Enhanced Interior Gateway Routing Protocol (EIGRP) (IPv4, IPv6) and OSPFv3 (IPv4, IPv6).
Figure 2 Router-to-Radio Link
Virtual Multipoint Interface
The VMI provides services that map outgoing packets to the appropriate PPPoE sessions based on the next-hop forwarding address for that packet. The VMI interface also provides a broadcast service that emulates a set of point-to-point connections as a point-to-multipoint interface with broadcast ability. When a packet with a multicast address is forwarded through the VMI in aggregate mode, VMI replicates the packet and sends it through the virtual access interfaces to each of its neighbors.
Directional radios are frequently used in applications that require greater bandwidth, increased power-to-transmission range, or reduced probability of detection. These radios operate in a point-to-point mode and generally have no broadcast capability. However, the routing processes in MANET operate most efficiently because the network link is treated as point-to-multipoint, with broadcast capability. For the router, modeling the MANET as a collection of point-to-point nodes has a dramatic impact on the size of its internal database.
The VMI within the router can aggregate all of the per-neighbor PPPoE sessions from the radio Ethernet connection. The VMI maps the sessions to appear to Layer 3 routing protocols and applications as a single point-to-multipoint, multiaccess, broadcast-capable network. However, the VMI preserves the integrity of the PPPoE sessions on the radio side so that each point-to-point connection can have its own QoS queue.
The VMI also relays the link-quality metric and neighbor up/down signaling from the radio to the routing protocols. The VMI signals are used by EIGRP (for IPv4 and IPv6 neighbors) and OSPFv3 (for IPv6 neighbors).
Multicast Support for VMIs
By default, VMI operates in aggregate mode, which means that all of the virtual-access interfaces created by PPPoE sessions are aggregated logically under the configured VMI. Applications above Layer 2, such as EIGRP and OSPFv3, should be defined only on the VMI interface. Packets sent to the VMI interface are forwarded to the correct virtual access interface. When VMI interfaces are in aggregate mode, they operate in nonbroadcast multiple access (NBMA) mode. Multicast traffic is forwarded only to the NBMA neighbors where a listener for that group is present.
Note
If you are running multicast applications that require the virtual access interfaces to be exposed to applications above Layer 2 directly, you can configure the VMI to operate in bypass mode. Most multicast applications require that the virtual access interfaces be exposed directly to the routing protocols to ensure that the multicast Reverse Path Forwarding (RPF) can operate as expected. When you use the bypass mode, you must define a VMI to handle presentation of cross-layer signals such as, neighbor up, neighbor down, and metrics. Applications are aware of the actual underlying virtual access interfaces and send packets to them directly. Additional information is required on the virtual template configuration.
For configuration information, see these sections:
•
•
VMI QoS
In Cisco IOS Release 15.2(1)T and later releases, VMI supports full modular QoS CLI (MQC) configurations, which includes remarking, shaping, and policing. For details, see the MQC information in the Quality of Service Solutions Configuration Guide. For configuration examples, see the "Examples: QoS Configuration for VMI" section.
Note
Multicast Routing in NBMA Mode
Multicast is defined as a network group membership spanning the entire network. Usually, multicast is unidirectional from a source to a group of receivers. In both IPv4 and IPv6 architectures, a portion of the address space is reserved for multicast groups and group addresses are requested to and assigned by Internet Assigned Numbers Authority (IANA). See Table 1 for IPv4 examples.
NBMA mode is achieved on a VMI aggregate interface. When operating in multicast NBMA mode, only the virtual interfaces that are part of the multicast tree receive multicast traffic.
IPv6 Address Support on VMIs
You can configure VMIs with IPv6 addresses only, IPv4 addresses only, or both IPv4 and IPv6 addresses.
IPv6 addresses are assigned to individual router interfaces and enable the forwarding of IPv6 traffic globally on the router. By default, IPv6 addresses are not configured and IPv6 routing is disabled.
Note
The /prefix-length argument in the ipv6 address command is a decimal value that indicates how many of the high-order contiguous bits of the address comprise the prefix (the network portion of the address) A slash mark must precede the decimal value.
Restrictions for IPv6 Addressing
In Cisco IOS Release 12.2(4)T and later releases, Cisco IOS Release 12.0(21)ST, and Cisco IOS Release 12.0(22)S and later releases, the ipv6 address or ipv6 address eui-64 command can be used to configure multiple IPv6 global addresses within the same prefix on an interface. Multiple IPv6 link-local addresses on an interface are not supported.
Prior to Cisco IOS Releases 12.2(4)T, 12.0(21)ST, and 12.0(22)S, the Cisco IOS CLI displays the following error message when multiple IPv6 addresses within the same prefix on an interface are configured:
Prefix <prefix-number> already assigned to <interface-type>For additional information about IPv6 addressing, see the "Implementing IPv6 Addressing" section in the Cisco IOS IPv6 Configuration Guide.
OSPFv3 Address Families
In Cisco IOS Release 15.2(1)T and later releases, the OSPFv3 address family feature is implemented according to RFC 5838 and enables the concurrent routing of IPv4 and IPv6 prefixes.
When this feature is enabled with the OSPFv3 MANET feature, IPv6 packets are routed in mobile environments over OSPFv3 using IPv4 or IPv6 addresses.
For configuration details, see the Cisco IOS IPv6 Configuration Guide.
Link-Quality Metrics Reporting for OSPFv3 and EIGRP
The quality of a radio link has a direct impact on the throughput that can be achieved by router-to-router traffic. The PPPoE protocol provides a process by which a router can request, or a radio can report, link-quality metric information. With the Cisco OSFPv3 and EIGRP implementations, the route cost to a neighbor is dynamically updated based on metrics reported by the radio, thus allowing the best route to be chosen within a given set of radio links and reducing the effect of frequent routing changes.
The routing protocols receive raw radio-link data and compute a composite quality metric for each link In computing these metrics, you should consider these factors:
•
•
•
•
•
You can weight metrics during the configuration process to emphasize or deemphasize particular characteristics. For example, if throughput is a particular concern, you can weight the throughput metric so that it is factored more heavily into the composite route cost. Similarly, a metric of no concern can be omitted from the composite calculation
Link metrics can change rapidly, often by very small degrees, which can result in a flood of meaningless routing updates. In a worst-case scenario, the network could churn almost continuously as it struggles to react to minor variations in link quality. To alleviate this concern, Cisco provides a tunable dampening mechanism that allows you to configure threshold values. Any metric change that falls below the threshold is ignored. The quality of a connection to a neighbor varies, based on various characteristics of the interface when OSPFv3 or EIGRP is used as the routing protocol. The routing protocol receives dynamic raw radio-link characteristics and computes a composite metric that is used to reduce the effect of frequent routing changes.
By using the tunable hysteresis mechanism, you can adjust the threshold to the routing changes that occur when the router receives a signal that a new peer has been discovered or that an existing peer is unreachable. The tunable metric is weighted and is adjusted dynamically to account for these characteristics:
•
•
•
•
You can deconfigure individual weights, and you can clear all weights so that the cost returns to the default value for the interface type. Based on the routing changes that occur, you can determine the cost by applying these metrics.
EIGRP Cost Metrics for VMI Interfaces
When EIGRP is used as the routing protocol, metrics allow EIGRP to respond to routing changes. The link-state metric is advertised as the link cost in the router link advertisement. The reply sent to any routing query will always contain the latest metric information. The exceptions that result in an immediate update being sent are:
•
•
•
EIGRP receives dynamic raw radio-link characteristics and computes a composite EIGRP metric based on a proprietary formula. To avoid churn in the network as a result of the change in the link characteristics, EIGRP uses a tunable dampening mechanism.
EIGRP uses the metric weights along with a set of vector metrics to compute the composite metric for local routing information base (RIB) installation and route selections. The EIGRP composite metric is calculated using the formula:
metric = [K1 * BW + (K2 * BW) / (256 - Load) + K3 * Delay] * [K5 / (Reliability + K4)]
If K5 = 0, the formula reduces to metric = [K1 * BW + (K2 * BW)/(256 - Load) + K3 * Delay]
Note
Table 2 lists the EIGRP vector metrics and their descriptions.
EIGRP monitors metric weights on an interface to allow for the tuning of EIGRP metric calculations and indicate the type of service (ToS). Table 3 lists the K-values and their default.
Most configurations use the first two metrics—delay and bandwidth. The default formula of (BW + Delay) is the EIGRP metric. The bandwidth for the formula is scaled and inverted by this formula:
(10^7/minimum BW in kilobits per second)
You can change the weights, but these weights must be the same on all the routers.
For example, look at an EIGRP link where the bandwidth to a particular destination is 128k and the Relative Link Quality (RLQ) is 50 percent.
BW = (256 * 10000000) / 128 = 20000000
Delay = (((10000000000 / 128) * 100) / (50 * 1000)) * 256 = (40000000 / 10) = 4000000
Using the cut-down formula, the EIGRP metric calculation would simplify to 256*(BW + Delay), resulting in the following value:
Metric = (BW + Delay) = 20000000 + 4000000 = 240000000
VMI Metric to EIGRP Metric Conversion
The quality of connection to a VMI neighbor will vary based on various characteristics computed dynamically based on the feedback from Layer 2 to Layer 3. Table 4 lists the EIGRP metrics and their significance.
Table 5 shows how these EIGRP vector metric values map to the basic EIGRP interface parameters.
EIGRP Metric Dampening for VMI Interfaces
Rapid changes in metric components can affect the network by requiring that prefixes learned though the VMI interface be updated and sent to all adjacencies. This update can result in further updates and, in a worst-case scenario, cause network-wide churn. To prevent such effects, metrics can be dampened, or thresholds set, so that any change that does not exceed the dampening threshold is ignored.
Network changes that cause an immediate update include
•
•
•
Dampening the metric changes can be configured based on change or time intervals.
If the dampening method is change-based, changes in routes learned though a specific interface, or in the metrics for a specific interface, are not advertised to adjacencies until the computed metric changes from the last advertised value significantly enough to cause an update to be sent.
If this dampening method is interval-based, changes in routes learned though a specific interface, or in the metrics for a specific interface, are not advertised to adjacencies until the specified interval is met, unless the change results in a new route path selection.
When the timer expires, any routes that have outstanding changes to report are sent. If a route changes, such that the final metric of the route matches the last updated metric, no update is sent.
Each Layer 2 feedback can contribute a cost in the range of 0 to 65535. To tune down this cost range, use the optional weight keyword with the throughput, resources, latency, or L2-factor keyword. Each of these weights has a default value of 100 percent and can be configured in the range from 0 to 100. When 0 is configured for a specific weight, that weight does not contribute to the OSPF cost.
Because cost components can change rapidly, you might need to dampen the number of changes to reduce network-wide churn. Use the optional hysteresis keyword with the threshold threshold-value keyword and argument to set a cost change threshold. Any cost change below this threshold is ignored.
Neighbor Up and Down Signaling for OSFPv3 and EIGRP
MANETs are highly dynamic environments. Nodes might move into, or out of, radio range at a fast pace. Each time a node joins or leaves, the network topology must be logically reconstructed by the routers. Routing protocols normally use timer-driven hello messages or neighbor timeouts to track topology changes, but MANETs reliance on these mechanisms can result in unacceptably slow convergence.
The neighbor up/down signaling capability provides faster network convergence by using link-status signals generated by the radio. The radio notifies the router each time a link to another neighbor is established or terminated by the creation and termination of PPPoE sessions. In the router, the routing protocols (OSPFv3 or EIGRP) respond immediately to these signals by expediting formation of a new adjacency (for a new neighbor) or tearing down an existing adjacency (if a neighbor is lost). For example, if a vehicle drives behind a building and loses its connection, the router immediately senses the loss and establishes a new route to the vehicle through neighbors that are not blocked. This high-speed network convergence is essential for minimizing dropped voice calls and disruptions to video sessions.
When VMI with PPPoE is used and a partner node has left or a new one has joined, the radio informs the router immediately of the topology change. Upon receiving the signal, the router immediately declares the change and updates the routing tables. The signaling capability provides these advantages:
•
•
•
•
•
The messaging allows for flexible rerouting when necessary because of these factors:
•
•
•
•
•
The figure below shows the signaling sequence that occurs when radio links go up and down.
Figure 3 Up and Down Signaling Sequence
PPPoE Credit-based and Metric-based Scaling and Flow Control
Each radio initiates a PPPoE session with its local router as soon as the radio establishes a link to another radio. Once the PPPoE sessions are active for each node, a PPP session is then established end-to-end (router-to-router). This process is duplicated each time a radio establishes a new link.
The carrying capacity of each radio link might vary due to location changes or environmental conditions, and many radio transmission systems have limited buffering capabilities. To minimize the need for packet queueing in the radio, PPPoE protocol extensions enable the router to control traffic buffering in congestion situations. Implementing flow-control on these router-to-radio sessions also will allow use of QoS features such as fair queueing.
The flow-control solution utilizes a credit-granting mechanism documented in RFC 5578. When the PPPoE session is established, the radio can request a flow-controlled session. If the router acknowledges the request, all subsequent traffic must be flow controlled. If a flow-control session is requested and cannot be supported by the router, the session is terminated. Typically, both the radio and the router initially grant credits during session discovery. Once a device exhausts its credits, it must stop sending until additional credits are granted. Credits can be added incrementally over the course of a session.
Metrics scaling is used with high-performance radios that require high-speed links. The radio can express the maximum and current data rates with different scaler values. Credit scaling allows a radio to change the default credit grant (or scaling factor) of 64 bytes to its default value. You can display the maximum and current data rates and the scalar value set by the radio in the show vmi neighbor detail command output.
How to Configure Router-to-Radio Links
This document contains configuration guidelines only for configuration of PPPoE as it relates to VMIs. For details about configuring PPPoE, see the Cisco IOS Broadband and DSL Configuration Guide. For details about PPPoE commands, see the Cisco IOS Broadband and DSL Command Reference.
This section contains the following tasks:
•
•
•
•
•
•
•
•
•
•
•
•
Configuring a Subscriber Profile for PPPoE Service Selection
For VMI to work, you must configure a subscriber profile for PPPoE service selection.In this section, you configure the PPPoE service name, which is used by RAR-compliant radio PPPoE clients to connect to the Cisco IOS PPPoE server.
All PPPoE service names used for MANET implementations must begin with manet_radio for use with VMI and RFC5578 features. Example service names are manet_radio and manet_radio_satellite.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Assigning the Subscriber Profile to a PPPoE Profile
Perform this required task to assign a subscriber profile to a PPPoE profile. In this configuration, the BBA group name should match the subscriber profile name previously defined in the subscriber profile. In this case, the profile name used as the service name is manet_radio.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Troubleshooting Tips
Use the show pppoe session and debug pppoe commands to troubleshoot PPPoE sessions.
Enabling PPPoE Sessions on an Interface
Perform this required task to enable PPPoE sessions on an interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Creating a Virtual Template for IPv4 and IPv6
Perform this optional task to create a virtual template for IPv4 and IPv6. You use the virtual template interface to dynamically clone configurations for each virtual access interface created for a VMI neighbor.
Prerequisites
Cisco recommends that, when using the virtual template, you turn off the PPP keepalive messages to make CPU usage more efficient and to help avoid the potential for the router to terminate the connection if PPP keepalive packets are missed over a lossy radio frequency (RF) link.
SUMMARY STEPS
1.
2.
3.
4.
Perform steps 6, 7, and 8 if you are using IPv6.
If you are using both, perform steps 5, 6, 7, and 8.
5.
6.
7.
8.
DETAILED STEPS
Where to Do Next
For additional information about configuring the virtual templates, see the "Virtual Template Interface Service" chapter in the Cisco IOS Dial Solutions Configuration Guide.
Creating a VMI Interface for EIGRP IPv4
Perform this optional task to create the VMI interface for EIGRP IPv4 and associate it with the interface on which PPPoE is enabled.
Prerequisites
When you create a VMI interface, assign the IPv4 address to that VMI interface definition.
The radio alerts the router with PADT messages that the Layer-2 RF connection is no longer alive. Cisco recommends that you turn off the PPP keepalive messages to make CPU usage more efficient and to help avoid the potential for the router to terminate the connection if PPP keepalive packets are missed over a lossy RF link.
This configuration includes QoS fair queueing and a service policy applied to the VMI interface. Make certain that any fair queueing left over from any previous configurations is removed before applying the new policy map to the virtual template in the VMI configuration.
Restrictions
Do not assign any addresses to the corresponding physical interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
DETAILED STEPS
Creating a VMI Interface for EIGRP IPv6
Perform this optional task to create the VMI interface for EIGRP IPv6 and associate it with the interface on which PPPoE is enabled.
Prerequisites
When you create a VMI interface, assign the IPv6 address to that VMI interface definition.
The radio alerts the router with PADT messages that the Layer-2 RF connection is no longer alive. Cisco recommends that if you turn off the PPP keepalive messages to make CPU usage more efficient and help to avoid the potential for the router to terminate the connection if PPP keepalive packets are missed over a lossy RF link.
This configuration includes QoS fair queueing and a service policy applied to the VMI interface. Make certain that any fair queueing left over from any previous configurations is removed before applying the new policy map to the virtual template in the VMI configuration.
Restrictions
Do not assign any addresses to the corresponding physical interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
DETAILED STEPS
Setting the EIGRP Change-based Dampening Interval Using Classic-Style Configuration
Perform this optional task to set the EIGRP change-based dampening interval for VMI interfaces using classic-style configuration. Configuring the router eigrp command with the autonomous-system-number argument creates an EIGRP configuration referred to as autonomous system (AS) configuration. An EIGRP AS configuration creates an EIGRP routing instance that can be used for tagging routing information.
You can configure this feature with either an IPv4 or an IPv6 address, or you can use both. If you are using both IPv4 and IPv6, complete the entire configuration.
This configuration sets the threshold to 50 percent tolerance for routing updates involving VMI interfaces and peers.
Prerequisites
Complete the virtual template and the appropriate PPPoE configurations before performing this task.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Setting the EIGRP Change-based Dampening Interval Using Named-Style Configuration
Perform this optional task to set the EIGRP change-based dampening interval for VMI interfaces using named-style configuration. Configuring the router eigrp command with the virtual-instance-name argument creates an EIGRP configuration referred to as an EIGRP named configuration. An EIGRP named configuration does not create an EIGRP routing instance by itself. EIGRP named configuration is a base configuration that is required to define address-family configurations under it that are used for routing.
You can configure this feature with either an IPv4 or an IPv6 address, or you can use both. If you are using both IPv4 and IPv6, then complete the entire configuration.
This configuration sets the threshold to 50 percent tolerance for routing updates involving VMI interfaces and peers.
Prerequisites
Complete the virtual template and the appropriate PPPoE configurations before performing this task.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
Setting the EIGRP Interval-based Dampening Interval Using Classic-Style Configuration
Perform this optional task to set an EIGRP interval-based dampening interval for VMI interfaces using classic-style configuration. Configuring the router eigrp command with the autonomous-system-number argument creates an EIGRP configuration referred to as autonomous system (AS) configuration. An EIGRP AS configuration creates an EIGRP routing instance that can be used for tagging routing information.
This configuration sets the interval to 30 seconds at which updates occur for topology changes that affect VMI interfaces and peers.
Prerequisites
Complete the virtual template and the appropriate PPPoE configurations before performing this task.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Setting the EIGRP Interval-based Dampening Interval Using Named-Style Configuration
Perform this optional task to set an EIGRP interval-based dampening interval for VMI interfaces using named-style configuration. Configuring the router eigrp command with the virtual-instance-name argument creates an EIGRP configuration referred to as an EIGRP named configuration. An EIGRP named configuration does not create an EIGRP routing instance by itself. EIGRP named configuration is a base configuration that is required to define address-family configurations under it that are used for routing.
This configuration sets the interval to 30 seconds at which updates occur for topology changes that affect VMI interfaces and peers.
Prerequisites
Complete the virtual template and the appropriate PPPoE configurations before performing this task.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
Enabling Bypass Mode for Multicast Applications
Perform this optional task to enable bypass mode on a VMI interface and override the default aggregation that occurs on VMI interfaces. Bypass mode is recommended for multicast applications.
Prerequisites
Configure the virtual template and the appropriate PPPoE sessions for the VMI interface before performing this task.
Restrictions
Using bypass mode can cause databases in the applications to be larger because knowledge of more interfaces is required for normal operation.
After you enter the mode bypass 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.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Verifying the VMI Configuration
You can use these commands to verify the VMI configuration:
•
•
•
•
•
•
•
•
•
Configuration Examples for VMI PPPoE
•
•
•
•
•
•
•
•
•
•
Example: Basic VMI PPPoE Configuration with EIGRP IPv4
The following example shows the basic VMI PPPoE configuration with EIGRP IPv4 as the routing protocol. This configuration includes one VMI interface.
service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname host1!logging buffered 3000000no logging consoleenable password test!no aaa new-modelclock timezone EST -5ip cef!no ip domain lookupsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!subscriber profile testpppoe service manet_radio!!multilink bundle-name authenticatedno virtual-template subinterface!archivelog config!policy-map FQclass class-defaultfair-queue!bba-group pppoe testvirtual-template 1service profile test!bba-group pppoe VMI1virtual-template 1service profile host1!!interface Loopback1ip address 209.165.200.225 255.255.255.224no ip proxy-arpload-interval 30!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1ip unnumbered vmi1load-interval 30no keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2ip address 209.165.200.226 255.255.255.224no ip mroute-cacheload-interval 30!interface Vlan503ip address 209.165.200.226 255.255.255.224load-interval 30!interface vmi1ip address 209.165.200.226 255.255.255.224no ip redirectsno ip split-horizon eigrp 1load-interval 30dampening-change 50physical-interface FastEthernet0/0!router eigrp 1redistribute connectednetwork 209.165.200.226 255.255.255.224network 209.165.200.227 255.255.255.224auto-summary!no ip http serverno ip http secure-server!control-plane!!line con 0exec-timeout 0 0stopbits 1line aux 0line vty 0 4login!endExample: Basic VMI PPPoE Configuration with EIGRP for IPv6
The following example shows the basic requirements for configuring a VMI interface that uses EIGRP for IPv6 as the routing protocol. It includes one VMI interface.
service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname host1!logging buffered 3000000no logging consoleenable password lab!no aaa new-modelclock timezone EST -5ip cef!!!!no ip domain lookupipv6 unicast-routingipv6 cefsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!subscriber profile testpppoe service manet_radio!!multilink bundle-name authenticatedno virtual-template subinterface!!!!archivelog config!!policy-map FQclass class-defaultfair-queue!!!!!bba-group pppoe testvirtual-template 1service profile test!bba-group pppoe VMI1virtual-template 1service profile host1!!!interface Loopback1ip address 209.165.200.226 255.255.255.224no ip proxy-arpload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1no ip addressload-interval 30ipv6 enableno keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2ip address 209.165.200.225 255.255.255.224no ip mroute-cacheload-interval 30!interface Vlan503ip address 209.165.200.225 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface vmi1no ip addressload-interval 30ipv6 enableno ipv6 redirectsipv6 eigrp 1no ipv6 split-horizon eigrp 1physical-interface FastEthernet0/0!no ip http serverno ip http secure-server!ipv6 router eigrp 1router-id 10.9.1.1no shutdownredistribute connected!control-plane!line con 0exec-timeout 0 0stopbits 1line aux 0line vty 0 4login!endExample: VMI PPPoE Configuration with EIGRP for IPv4 and IPv6
The following examples show how to configure VMI PPPoE using EIGRP as the IP routing protocol when you have both IPv4 and IPv6 addresses configured on the interface. This configuration includes one VMI interface. Though EIGRP allows you to use the same AS number on an IPv4 EIGRP process and on an IPv6 process, we recommend using a unique AS number for each process for clarity.
service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname host1!logging buffered 3000000no logging consoleenable password lab!no aaa new-modelclock timezone EST -5ip cef!no ip domain lookupipv6 unicast-routingipv6 cefsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!subscriber profile testpppoe service manet_radio!!multilink bundle-name authenticatedno virtual-template subinterface!archivelog config!policy-map FQclass class-defaultfair-queue!bba-group pppoe testvirtual-template 1service profile test!bba-group pppoe VMI1virtual-template 1service profile host1!!interface Loopback1ip address 209.165.200.225 255.255.255.224no ip proxy-arpload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1ip unnumbered vmi1load-interval 30ipv6 enableno keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2ip address 209.165.200.225 255.255.255.224no ip mroute-cacheload-interval 30!interface Vlan503ip address 209.165.200.225 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface vmi1ip address 209.165.200.225 255.255.255.224no ip redirectsno ip split-horizon eigrp 1load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableno ipv6 redirectsipv6 eigrp 1no ipv6 split-horizon eigrp 10dampening-interval 30physical-interface FastEthernet0/0!router eigrp 1redistribute connectednetwork 209.165.200.225 255.255.255.224network 209.165.200.226 255.255.255.224auto-summary!!!no ip http serverno ip http secure-server!ipv6 router eigrp 1router-id 10.9.1.1no shutdownredistribute connected!control-plane!!line con 0exec-timeout 0 0stopbits 1line aux 0line vty 0 4login!endExample: EIGRP Change-based Dampening for VMI Interfaces
The following example configures EIGRP address-family Ethernet interface 0/0 to limit the metric change frequency to no more than one change in a 45-second interval:
Router(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 5400Router(config-router-af)# af-interface ethernet0/0Router(config-router-af-interface)# dampening-interval 45Example: EIGRP Interval-based Dampening for VMI Interfaces
The following example configures EIGRP address-family Ethernet interface 0/0 to limit the metric change frequency to no more than one change in a 45-second interval:
Router(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 5400Router(config-router-af)# af-interface ethernet0/0Example: VMI Configuration Using Multiple Virtual Templates
The following example shows how to configure VMI using multiple virtual templates. This example shows two VMIs, each with a different service name.
!service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname router1!boot-start-markerboot-end-marker!!no aaa new-model!resource policy!clock timezone EST -5ip cefno ip domain lookup!!subscriber authorization enable!subscriber profile router1_groundpppoe service manet_radio_ground!subscriber profile router1_satellitepppoe service manet_radio_satellite!ipv6 unicast-routingpolicy-map FQclass class-defaultfair-queue!!!bba-group pppoe router1_groundvirtual-template 1service profile router1_ground!bba-group pppoe router1_satellitevirtual-template 2service profile router1_satellite!!interface Ethernet0/0pppoe enable group router1_ground!interface Ethernet0/1pppoe enable group router1_satellite!interface Ethernet0/2no ip addressshutdown!interface Ethernet0/3no ip addressshutdown!interface Ethernet1/0no ip addressshutdown!interface Ethernet1/1no ip addressshutdown!interface Ethernet1/2no ip addressshutdown!interface Ethernet1/3no ip addressshutdown!interface Serial2/0no ip addressshutdownserial restart-delay 0!interface Serial2/1no ip addressshutdownserial restart-delay 0!interface Serial2/2no ip addressshutdownserial restart-delay 0!interface Serial2/3no ip addressshutdownserial restart-delay 0!interface Serial3/0no ip addressshutdownserial restart-delay 0!interface Serial3/1no ip addressshutdownserial restart-delay 0!interface Serial3/2no ip addressshutdownserial restart-delay 0!interface Serial3/3no ip addressshutdownserial restart-delay 0!interface Virtual-Template1ip unnumbered vmi1load-interval 30no peer default ip addressno keepaliveservice-policy output FQ!interface Virtual-Template2ip unnumbered vmi1load-interval 30no peer default ip addressno keepaliveservice-policy output FQ!interface vmi1description ground connectionip address 209.165.200.225 255.255.255.224physical-interface Ethernet0/0!interface vmi2description satellite connectionip address 209.165.200.225 255.255.255.224physical-interface Ethernet0/1!router eigrp 1network 209.165.200.225 255.255.255.224network 209.165.200.227 255.255.255.224auto-summary!!no ip http server!!!!!control-plane!!line con 0exec-timeout 0 0logging synchronousline aux 0line vty 0 4login!endExamples: IP Address Coordination for the VMI in Aggregate Mode
The default mode for operation of the VMI is aggregate mode. In aggregate mode, all of the virtual access interfaces created by PPPoE sessions are logically aggregated under the VMI. As such, applications above Layer 2, such as EIGRP and OSPFv3, should be defined on the VMI interface only. Packets sent to the VMI will be correctly forwarded to the correct virtual access interface.
The next examples show the IP address coordination needed between the virtual-template configuration and the VMI configuration.
The following example shows the configuration of VMI in aggregate mode using IPv4 as the routing protocol:
!interface Virtual-Template1ip unnumbered vmi1service-policy output FQ!interface vmi1ip address 2.2.2.1 255.255.255.0physical-interface FastEthernet0/0!The following example shows the configuration of VMI in aggregate mode using IPv4 and IPv6 as the routing protocols:
interface Virtual-Template1ip unnumbered vmi1ipv6 enableservice-policy output FQ!interface vmi1ip address 2.2.2.1 255.255.255.0ipv6 enablephysical-interface FastEthernet0/0!The following example shows the configuration of VMI in aggregate mode using IPv6 as the routing protocol:
interface Virtual-Template1ipv6 enableservice-policy output FQ!interface vmi1ipv6 enablephysical-interface FastEthernet0/0!Examples: Enabling Multicast Support with Bypass or Aggregate Mode
Note
Example: Bypass Mode on VMI Interfaces for Multicast Traffic
The following example shows how to enable multicast on VMI interfaces. The example includes changing the VMI interface to bypass mode and enabling PIM sparse mode on the virtual-template interface:
Router# enableRouter# configure terminal!Router(config)# interface Virtual-Template1Router(config-if)# ip address 209.165.200.227 255.255.255.224Router(config-if)# load-interval 30Router(config-if)# no keepaliveRouter(config-if)# ip pim sparse-dense-modeRouter(config-if)# service-policy output FQ!!Router(config)# interface vmi1Router(config-if)# ip address 10.3.9.1 255.255.255.0Router(config-if)# load-interval 30Router(config-if)# physical-interface FastEthernet0/0Router(config-if)# mode bypass!Router(config)# endExample: OSPFv3 for IPv6 Multicast Traffic Using Bypass Mode
hostname host1!enableconfigure terminal!no aaa new-modelclock timezone EST -5!!!ip cefno ip domain lookupipv6 unicast-routingipv6 cefsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!multilink bundle-name authenticatedno virtual-template subinterface!!archivelog config!policy-map FQclass class-defaultfair-queue!bba-group pppoe VMI1virtual-template 1service profile host1!interface Loopback1no ip addressload-interval 30ipv6 address 2001:0DB1::1/64ipv6 enable!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexipv6 enablepppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1no ip addressload-interval 30ipv6 address 2001:0DB8::/32ipv6 enable!ipv6 ospf network point-to-multipointipv6 ospf cost dynamicipv6 ospf 1 area 0no keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2no ip addressno ip mroute-cacheload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 ospf 1 area 0!interface Vlan503load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 ospf 1 area 0!interface vmi1no ip addressload-interval 30ipv6 enablephysical-interface FastEthernet0/0mode bypass!!no ip http serverno ip http secure-server!ipv6 router ospf 1log-adjacency-changesredistribute connected metric-type 1!!!control-plane!!line con 0exec-timeout 0 0stopbits 1line aux 0line vty 0 4login!endExample: EIGRP for IPv4 Using Bypass Mode
The following example shows how to configure EIGRP for IPv4 using bypass mode. In this example, the IP address of the VMI1 interface needs to be defined, but it will not be routable because the VMI interface will be configured as down/down:
hostname host1!no aaa new-modelclock timezone EST -5ip cef!no ip domain lookupsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!!multilink bundle-name authenticatedno virtual-template subinterface!archivelog config!policy-map FQclass class-defaultfair-queue!!!bba-group pppoe VMI1virtual-template 1service profile host1!!interface Loopback1ip address 209.165.200.225 255.255.255.224load-interval 30!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1ip address 209.165.200.225 255.255.255.224load-interval 30no keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2ip address 209.165.200.225 255.255.255.224no ip mroute-cacheload-interval 30!interface Vlan503ip address 209.165.200.225 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enable!interface vmi1ip address 209.165.200.226 255.255.255.224load-interval 30physical-interface FastEthernet0/0mode bypass!router eigrp 1redistribute connectednetwork 209.165.200.225 255.255.255.224network 209.165.200.226 255.255.255.224Example: EIGRP for IPv6 Using Bypass Mode
The following example shows how to configure EIGRP for IPv6 using bypass mode:
!ip cef!!!no ip domain lookupipv6 unicast-routingipv6 cefsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!multilink bundle-name authenticatedno virtual-template subinterface!!!archivelog config!!policy-map FQclass class-defaultfair-queue!!!bba-group pppoe VMI1virtual-template 1service profile host1!!interface Loopback1load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1no ip addressload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1no keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2no ip addressno ip mroute-cacheload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface Vlan503no ip addressload-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface vmi1no ip addressload-interval 30ipv6 enablephysical-interface FastEthernet0/0mode bypass!!no ip http serverno ip http secure-server!ipv6 router eigrp 1no shutdownredistribute connected!!!Example: EIGRP with IPv4 and IPv6 Traffic Using Bypass Mode
The following example shows how to configure EIGRP with IPv4 and IPv6 using bypass mode:
!hostname host1!enableconfigure terminalip cefno ip domain lookupipv6 unicast-routingipv6 cefsubscriber authorization enable!subscriber profile host1pppoe service manet_radio!multilink bundle-name authenticatedno virtual-template subinterface!archivelog config!!policy-map FQclass class-defaultfair-queue!bba-group pppoe VMI1virtual-template 1service profile host1!!interface Loopback1ip address 209.165.200.225 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface FastEthernet0/0no ip addressno ip mroute-cacheload-interval 30speed 100full-duplexpppoe enable group VMI1!interface Serial1/0no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/1no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/2no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface Serial1/3no ip addressno ip mroute-cacheshutdownclock rate 2000000!interface FastEthernet2/0switchport access vlan 2duplex fullspeed 100!interface FastEthernet2/1switchport access vlan 503load-interval 30duplex fullspeed 100!interface FastEthernet2/2shutdown!interface FastEthernet2/3shutdown!interface Virtual-Template1ip address 209.165.200.225 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1no keepaliveservice-policy output FQ!interface Vlan1no ip addressno ip mroute-cacheshutdown!interface Vlan2ip address 209.165.200.226 255.255.255.224no ip mroute-cacheload-interval 30!interface Vlan503ip address 209.165.200.226 255.255.255.224load-interval 30ipv6 address 2001:0DB8::/32ipv6 enableipv6 eigrp 1!interface vmi1ip address 209.165.200.226 255.255.255.224load-interval 30ipv6 enablephysical-interface FastEthernet0/0mode bypass!router eigrp 1redistribute connectednetwork 209.165.200.226 255.255.255.224network 209.165.200.227 255.255.255.224auto-summary!!no ip http serverno ip http secure-server!ipv6 router eigrp 1eigrp router-id 10.9.1.1no shutdownredistribute connected!!!endExample: OSPFv3 for Multicast Traffic Using Aggregate Mode
In this example, multicast is configured as an NBMA network. To configure multicast, the ip multicast-routing global configuration command is required. To configure VMI aggregate mode for multicast, you must configure the VMI with the ip pim nbma-mode command. The following example shows the VMI on an OSPF network:
!service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname mcrtr4!boot-start-markerboot-end-marker!logging message-counter sysloglogging buffered 51200 warnings!no aaa new-model!ip source-route!!ip cef!!ip domain name yourdomain.comip multicast-routingip multicast cache-headersno ipv6 cefsubscriber authorization enable!subscriber profile chanpppoe service manet_radio!!multilink bundle-name authenticated!username lab privilege 15 secret 5 $1$v1bl$B5KD7o3jVKYqfoKoS0FUJ1!!!archivelog confighidekeys!!!!!bba-group pppoe chanvirtual-template 1service profile chan!!interface Loopback0ip address 15.15.15.15 255.255.255.255ip broadcast-address 0.0.0.0!interface FastEthernet0/0description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0/0$ip address 1.1.1.2 255.255.255.0ip broadcast-address 0.0.0.0ip pim sparse-modeip igmp version 3duplex autospeed auto!interface FastEthernet0/1no ip addressip broadcast-address 0.0.0.0duplex autospeed autopppoe enable group chan!interface FastEthernet0/0/0!interface FastEthernet0/0/1!interface FastEthernet0/0/2!interface FastEthernet0/0/3interface FastEthernet0/1/0no ip addressip broadcast-address 0.0.0.0duplex autospeed auto!interface Virtual-Template1ip unnumbered vmi1no peer default ip addressfair-queue!interface Vlan1ip address 10.15.60.53 255.255.255.0!interface vmi1ip address 2.2.2.2 255.255.255.0ip pim nbma-modeip pim sparse-modeip ospf network point-to-multipointload-interval 30physical-interface FastEthernet0/1!router ospfv3 1log-adjacency-changesredistribute connected subnetsredistribute staticnetwork 1.1.1.0 0.0.0.255 area 0network 2.2.2.0 0.0.0.255 area 0!ip forward-protocol ndip http serverip http access-class 23ip http authentication localip http secure-serverip http timeout-policy idle 60 life 86400 requests 10000!!ip pim rp-address 16.16.16.16ip pim register-source vmi1!access-list 23 permit 10.10.10.0 0.0.0.7access-list 110 permit ip any any!!!!control-plane!!!!mgcp fax t38 ecm!!line con 0exec-timeout 0 0login localline aux 0line vty 0 4access-class 23 inprivilege level 15login localtransport input telnet sshline vty 5 15access-class 23 inprivilege level 15login localtransport input telnet ssh!exception data-corruption buffer truncatescheduler allocate 20000 1000endExample: PPPoE Configuration
In the following example, the subscriber profile uses a predefined string manet_radio to determine whether an inbound PPPoE session is coming from a device that supports VMI. All IP definitions are configured on the VMI interface rather than on the Fast Ethernet or virtual-template interfaces; when those interfaces are configured, do not specify either an IP address or an IPv6 address.
No IP address is specified, and IPv6 is enabled by default on the VMI interface:
subscriber profile list1pppoe service manet_radiosubscriber authorization enable!bba-group pppoe bba1virtual-template 1service profile list1!interface FastEthernet0/1no ip addresspppoe enable group bba1!interface Virtual-Template 1no ip addressno peer default ip-address!interface vmi 1no ip addressphysical-interface FastEthernet0/1Example: Configuring Two VMIs and Two Virtual Templates
The following example shows a configuration that includes two VMIs, two virtual templates, and two service names. You can configure multiple virtual template interfaces for your VMI PPPoE connections. The selection of which virtual template to use is predicated on the service name sent by the radio during PPPoE session establishment.
In this example, any PPPoE request for a session (presentation of a PPPoE Active Discovery Initiate [PADI] packet) with the service name of "manet_radio_ground" uses Virtual-Template1 as the interface to be cloned. Conversely, any PADI presented by the radio with the service name of "manet_radio_satellite" uses Virtual-Template2.
!service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname router1!boot-start-markerboot-end-marker!!no aaa new-model!resource policy!clock timezone EST -5ip cefno ip domain lookup!!subscriber authorization enable!subscriber profile router1_groundpppoe service manet_radio_ground!subscriber profile router1_satellitepppoe service manet_radio_satellite!ipv6 unicast-routingpolicy-map FQclass class-defaultfair-queue!!!bba-group pppoe router1_groundvirtual-template 1service profile router1_ground!bba-group pppoe router1_satellitevirtual-template 2service profile router1_satellite!!interface Ethernet0/0pppoe enable group router1_ground!interface Ethernet0/1pppoe enable group router1_satellite!interface Ethernet0/2no ip addressshutdown!interface Ethernet0/3no ip addressshutdown!interface Ethernet1/0no ip addressshutdown!interface Ethernet1/1no ip addressshutdown!interface Ethernet1/2no ip addressshutdown!interface Ethernet1/3no ip addressshutdown!interface Serial2/0no ip addressshutdownserial restart-delay 0!interface Serial2/1no ip addressshutdownserial restart-delay 0!interface Serial2/2no ip addressshutdownserial restart-delay 0!interface Serial2/3no ip addressshutdownserial restart-delay 0!interface Serial3/0no ip addressshutdownserial restart-delay 0!interface Serial3/1no ip addressshutdownserial restart-delay 0!interface Serial3/2no ip addressshutdownserial restart-delay 0!interface Serial3/3no ip addressshutdownserial restart-delay 0!interface Virtual-Template1ip unnumbered vmi1load-interval 30no peer default ip addressno keepaliveservice-policy output FQ!interface Virtual-Template2ip unnumbered vmi2load-interval 30no peer default ip addressno keepaliveservice-policy output FQ!interface vmi1description ground connectionip address 209.165.200.226 255.255.255.224physical-interface Ethernet0/0!interface vmi2description satellite connectionip address 209.165.200.227 255.255.255.224physical-interface Ethernet0/1!router eigrp 1network 209.165.200.226 255.255.255.224network 209.165.200.227 255.255.255.224auto-summary!!no ip http server!!!!!control-plane!!line con 0exec-timeout 0 0logging synchronousline aux 0line vty 0 4login!endExamples: QoS Configuration for VMI
VMI supports full modular QoS CLI (MQC) configurations, which includes remarking, shaping, and policing. For details, see the MQC information in the Quality of Service Solutions Configuration Guide.
Note
This example shows a configuration for QoS features:
class-map match-any chatmatch dscp af11class-map match-any voicematch dscp efclass-map match-any af23match dscp af23class-map match-any af31match dscp af31class-map match-any af33match dscp af33class-map match-any af42match dscp af42policy-map multiple_sessionsclass chatbandwidth 50class voicebandwidth 100class af23bandwidth 150class af31bandwidth 200class af33bandwidth 250class af42bandwidth 300interface virtual-template 1service-policy output multiple_sessionsThis exaample shows the configuration for shaping:
class-map match-any chatmatch dscp af11class-map match-any voicematch dscp efpolicy-map shape_childclass chatbandwidth 200class voicepriority 100policy-map shape_parentclass class-defaultshape average 400000service-policy shape_childThis example shows the configuration for assigning the policy to the VMI interface:
interface vmi1service-policy output shape_parentThis example shows the configuration for policing actions:
class-map match-any af12match dscp af12class-map match-any af41match dscp af41policy-map policeclass af12police 1000000 conform-action set-dscp-transmit af31 exceed-action set-dscp-transmit af23 violate-action set-dscp-transmit af23class af41police 1000000 conform-action transmit exceed-action drop violate-action dropThis example shows the configuration for assigning the policy tothe virtual template interface:
interface virtual-template 1service-policy output policeAdditional References
Related Documents
Standards
No new or modified standards are supported, and support for existing standards has not been modified.
—
MIBs
RFCs
Technical Assistance
Feature Information for Mobile Ad Hoc Networks for Router-to-Radio Communications
Table 6 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 6 Feature Information for Mobile Ad Hoc Networks for Router-to-Radio Communications
EIGRP L2/L3 API and Tunable Metric for Mobile Ad Hoc Networks
12.4(15)XF
12.4(15)T
15.0(1)MEIGRP uses dynamic raw radio link characteristics (current and maximum bandwidth, latency, and resources) to compute a composite EIGRP metric. A tunable hysteresis mechanism helps to avoid churn in the network as a result of the change in the link characteristics.
In addition to the link characteristics, the L2/L3 API provides an indication when a new adjacency is discovered, or an existing unreachable adjacency is again reachable. When EIGRP receives the adjacency signals, it responds with an immediate Hello out the specified interface to expedite the discovery of the EIGRP peer.
The following sections provide information about this feature:
•
•
•
The following commands were introduced or modified: dampening-change, dampening-interval, debug eigrp notifications, debug vmi.
Multicast for Virtual Multipoint Interfaces
15.1(3)T
The Multicast for Virtual Multipoint Interfaces feature enables multicast support for RFC 5578-compliant Radio Aware Routing.
The following sections provide information about this feature:
•
•
•
•
No new or modified commands were introduced with this feature.
OSPFv3 Dynamic Interface Cost Support
12.4(15)XF
12.4(15)T 15.0(1)MOSPFv3 Dynamic Interface Cost Support provides enhancements to the OSPFv3 cost metric for supporting Mobile Ad Hoc Networking.
The following commands were introduced or modified: debug ipv6 ospf l2api, ipv6 ospf cost, test ospfv3 interface.
PPPoE Support for Credit Flow and Metrics on Router-to-Radio Links Feature
12.4(15)XF
12.4(15)T
15.0(1)MCredit-based flow control provides in-band and out-of-band credit grants in each direction. Link Quality Metrics are used to report link performance statistics that are then used to influence routing.
The following sections provide information about this feature:
•
•
•
The following commands were introduced or modified: show pppoe session, show vmi neighbors.
Radio Aware Routing RFC 5578
15.1(3)T
Radio Aware Routing incorporates RFC 5578 updates for interfacing Cisco routers to high-performance radios through PPPoE.
The following section provides information about this feature:
The following commands were introduced or modified: show vmi neighbors.
VMI QoS
15..2(1)T
VMI supports full modular QoS CLI (MQC) configurations, which includes remarking, shaping, and policing. The following section provides information about this feature:
•
No commands were introduced or modified.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2007-2011 Cisco Systems, Inc. All rights reserved.
