Guest

Cisco IOS Software Releases 12.4 Special and Early Deployments

Mobile Ad Hoc Networks for Router-to-Radio Communications

Table Of Contents

Mobile Ad Hoc Networks for Router-to-Radio Communications

Contents

Prerequisites for Mobile Ad Hoc Networks for Router-to-Radio Communications

Restrictions for Mobile Ad Hoc Networks for Router-to-Radio Communications

Information About Mobile Ad Hoc Networks for Router-to-Radio Communications

Benefits of Router-to-Radio Links Using Virtual Multipoint Interfaces with PPPoE in Cisco IOS Software

MANETs for Router-to-Radio Communications

PPPoE Interfaces for Mobile Radio Communications

Virtual Multipoint Interface

Link Quality Metrics Reporting for OSPFv3 and EIGRP with VMI Interfaces

Neighbor Up/Down Signaling for OSFPv3 and EIGRP

PPPoE Credit-based Flow Control

IPv6 Addresses

How to Configure Router-to-Radio Links Using VMI PPPoE

Implementing the VMI Infrastructure Using PPPoE

Implementing the VMI and Configuring the Routing Protocol

Configuration Examples for VMI PPPoE

Basic VMI PPPoE Configuration with EIGRP IPv4: Example

Basic VMI PPPoE Configuration Using EIGRP for IPv6: Example

VMI PPPoE Configuration Using EIGRP for IPv4 and IPv6: Example

VMI PPPoE Configuration for OSPFv3: Example

VMI PPPoE Configuration Using Multiple Virtual Templates: Example

PPPoE Configuration: Example

Configuring Two VMIs: Example

Marking and Queuing Packets over VMI: Example

Additional References

Related Documents

Standards\

MIBs

RFCs

Technical Assistance

Command Reference

debug eigrp notifications

debug vmi

eigrp interface

interface vmi

ipv6 ospf cost

ipv6 ospf network

mode bypass

physical-interface

show ipv6 ospf

show ipv6 ospf interface

show pppoe

show vmi neighbors

Feature Information About the 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: May 17, 2007

Mobile 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. the Cisco solution for MANETs provides capabilities that enable

Optimal route selection based on Layer 2 feedback from the radio network

Faster convergence when nodes join and leave the network

Efficient integration of point-to-point, directional radio topologies with multi hop routing

Flow-controlled communications between each radio and its partner router

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 voice and video work better because outages caused by topology changes are reduced or eliminated. Sessions are more stable and remain active longer.

Key features of Cisco's mobile ad hoc networks for router-to-radio communications include the following:

Link Quality Metrics Reporting

The PPPoE protocol has been extended to enable a router or radio to query or report link-quality metric information. Cisco routers have been enhanced so that OSPFv3 or EIGRP routing protocols can factor link quality metrics into route cost calculations.

Neighbor Up or Down Signaling

Neighbor up or down signaling enables Cisco routers to use link establishment or termination signals from the radio to update routing topology.

PPPoE Credit-based Flow Control

This extension to the PPPoE protocol allows a receiver to control the rate at which a sender can transmit data for each PPPoE session, so that the need for queuing in the radio is minimized.

Virtual Multipoint Interface (VMI)

This Cisco router enhancement maps multiple PPPoE sessions (each representing a point-to-point neighbor connection) into a single broadcast-capable, multi-access interface.

Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the " "Command Reference" section.

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS 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 for Router-to-Radio Communications

Information About Mobile Ad Hoc Networks for Router-to-Radio Communications

How to Configure Router-to-Radio Links Using VMI PPPoE

Configuration Examples for VMI PPPoE

Additional References

Command Reference

Feature Information About the Mobile Ad Hoc Networks for Router-to-Radio Communications

Prerequisites for Mobile Ad Hoc Networks for Router-to-Radio Communications

The features described in this document require one of the following router platforms:

Cisco 2800 Series (2801, 2811, 2821, or 2851)

Cisco 3250 and Cisco 3270

Cisco 3800 Series (3825 or 3845)

To use the PPPoE and virtual multipoint interface (VMI) features described in this document, a radio device that implements the PPPoE functionality enhancements described in the draft RFC 2516 is required. Users can optionally implement draft-bberry-pppoe-credit-06.txt for PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics, but this draft must be implemented if you plan to use VMI features.

Restrictions for Mobile Ad Hoc Networks for Router-to-Radio Communications

VMI on Routed Ports

VMIs can be configured only on routed ports. VMIs are not supported on VLAN or switched ports.

Quality of Service

Of the Quality of Service (QoS) queueing features available from Cisco, only class-based Weighted Fair Queueing (WFQ) is supported on VMIs. The VMI can identify Differentiated Services Code Point (DSCP) values, and perform network-based application recognition (NBAR), but no policing or policy mapping occurs on those matches.

Information About Mobile Ad Hoc Networks for Router-to-Radio Communications

This section describes VMI PPPoE. The following sections are included:

Benefits of Router-to-Radio Links Using Virtual Multipoint Interfaces with PPPoE in Cisco IOS Software

MANETs for Router-to-Radio Communications

IPv6 Addresses

PPPoE Interfaces for Mobile Radio Communications

Link Quality Metrics Reporting for OSPFv3 and EIGRP with VMI Interfaces

Benefits of Router-to-Radio Links Using Virtual Multipoint Interfaces with PPPoE in Cisco IOS Software

As the global leader in mission-critical networking and IP communications, Cisco is uniquely positioned to deliver reliable and efficient converged voice, video, and data solutions to organizations around the world. Benefits of this technology include the following:

Optimal route selection is based on Layer 2 feedback from the radio network.

Efficient integration of point-to-point, directional radio topologies with multi hop routing.

Convergence is faster when nodes join and leave the network because routers are able to respond faster to network topology changes.

Flow-controlled communications between the radio and its partner router enables applications such voice and video to work better because outages caused by moving links are reduced or eliminated. Sessions are more stable and remain active longer.

MANETs for Router-to-Radio Communications

Mobile Ad Hoc Networks (MANETs) enable users deployed in areas with no fixed communications infrastructure to access critical voice, video, and data services. 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 multi-agency 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. MANETs set the stage for more timely information sharing and faster, more effective decision-making.

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. Since 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. Finally, 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 multi-hop, multipoint router environments, as 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

routers and radios can interoperate efficiently, and without impacting operation of the radio network

radio point-to-point and router point-to-multipoint paradigms can be rationalized

radios can report status to routers for each link and each neighbor, and

routers can use this information to optimize routing decisions.

PPPoE Interfaces for Mobile Radio Communications

The Cisco MANET solution employs PPP-over-Ethernet (PPPoE) sessions to enable intra-nodal 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 Virtual Multipoint Interface (VMI) on the router aggregates multiple PPPoE sessions and multiplexes these to look like a single interface to the routing processes. This interface collects the series of PPP/PPPoE connections. Underneath the VMI interface there 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. Figure 1 illustrates 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 assumes that a PPPoE-equipped radio connects to a router using Ethernet. The router always considers the Ethernet link to be up. If the radio side of the link goes down, the router will wait until a routing update time-out has occurred to declare the route down and then update the routing table. Figure 2 illustrates a simple router-to-radio link topology.

Figure 2 Router-to-Radio Link

Routing protocols used for VMI PPPoE are EIGRP (IPv4, IPv6) and OSPFv3 (IPv6).

Virtual Multipoint Interface

The VMI interface 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 interface, VMI replicates the packet and unicasts it 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. On the other hand, the routing processes in Cisco's MANET solution operate most efficiently when viewing the network link as point-to-multipoint, with broadcast capability. For the router, modeling the MANET as a collection of point-to-point nodes would have a dramatic impact on the size of its internal database.

The Virtual Multipoint Interface (VMI) within the router aggregates 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, multi-access, 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 Quality of Service (QoS) queue.

The VMI also relays the link quality metric and neighbor up/down signaling from the radio to the routing protocols. Currently, VMI signals are used by EIGRP (for IPv4 and IPv6 neighbors) and OSPFv3 (for IPv6 neighbors).

Link Quality Metrics Reporting for OSPFv3 and EIGRP with VMI Interfaces

The quality of a radio link has a direct impact on the throughput that can be achieved by router-router traffic. The PPPoE protocol has been extended to provide a process by which a router can request, or a radio can report, link quality metric information. Cisco's OSFPv3 and EIGRP implementations have been enhanced so that 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.

The routing protocols receive raw radio link data, and compute a composite quality metric for each link. In computing these metrics, the following factors may be considered:

Maximum Data Rate - the theoretical maximum data rate of the radio link, in bytes per second

Current Data Rate - the current data rate achieved on the link, in bytes per second

Latency - the transmission delay packets encounter, in milliseconds

Resources - a percentage (0-100) that can represent the remaining amount of a resource (such as battery power)

Relative Link Quality - a numeric value (0-100) representing relative quality, with 100 being the highest quality

Metrics can be weighted during the configuration process to emphasize or de-emphasize particular characteristics. For example, if throughput is a particular concern, the current data rate metric could be weighted so that it is factored more heavily into the composite metric. Similarly, a metric that is of no concern can be omitted from the composite calculation.

Link metrics can change rapidly, often by very small degrees, which could result in a flood of meaningless routing updates. In a worst case scenario, the network would be churning almost continuously as it struggled to react to minor variations in link quality. To alleviate this concern, Cisco provides a tunable dampening mechanism that allows the user 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 OSPF 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.

A tunable hysteresis mechanism allows users to 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 the following characteristics:

Current and Maximum Bandwidth

Latency

Resources

Hysteresis

Individual weights can be deconfigured and all weights can be cleared so that the cost is set back to the default value for the interface type. Based on the routing changes that occur, cost can be determined by the application of these metrics. The following sections provide more details about OSPF and EIGRP metrics:

OSPF Cost Calculation

EIGRP Cost Metrics

VMI Metric to EIGRP Metric Conversion

Dynamic Cost Metric for Interfaces

EIGRP Metric Dampening

OSPF Cost Calculation

Because cost components can change rapidly, it might be necessary to dampen the volume of changes to reduce network-wide churn. The recommended values for S2, S3, and S4 are based on network simulations that may reduce the rate of network changes. The recommended value for S1 is zero to eliminate this variable from the route cost calculation.

The overall link cost is computed using the following formula:

Table 1 defines the symbols used in the OSPF cost calculation.

Table 1 OSPF Cost Calculation Definitions

Cost Component
Component Definition

OC

The "default OSPF Cost". Calculated from reference bandwidth using

reference_bw / (MDR*1000) where reference_bw=10^8

A through D

Various radio-specific data based formula's which produce result in range 0-64k

A

CDR and MDR related formula

(2^16 * (100 - (CDR * 100 / MDR)))/100

B

Resources related formula

((100 - RESOURCES)^3 * 2^16 / 10^6)

C

Latency as reported by the radio (already in the 0-64K range when reported (LATENCY)

D

RLF related formula

((100 - RLF) * 2^16)/100

S1 through S4

Scalar weighting factors input from CLI. These scalars scale DOWN the values as computed by A-D.

The value of 0 disables and value of 100 enables full 0-64k range for one component.


While each network might have unique characteristics that require different settings to optimize actual network performance, these are recommended values intended as a starting point for optimizing a OSPFv3 network. Table 2 lists the recommended value settings for OSPF cost metrics.

Table 2 Recommended Value Settings for OSPF Cost Metrics

Setting
Metric Description
Default Value
Recommended Value

S1

ipv6 ospf dynamic weight throughout

100

0

S2

ipv6 ospf dynamic weight resources

100

29

S3

ipv6 ospf dynamic weight latency

100

29

S4

ipv6 ospf dynamic weight L2 factor

100

29


Using this formula, the default path costs were calculated as noted in the following list. If these values do not suit your network, you can use your own method of calculating path costs.

56-kbps serial link—Default cost is 1785.

64-kbps serial link—Default cost is 1562.

T1 (1.544-Mbps serial link)—Default cost is 64.

E1 (2.048-Mbps serial link)—Default cost is 48.

4-Mbps Token Ring—Default cost is 25.

Ethernet—Default cost is 10.

16-Mbps Token Ring—Default cost is 6.

FDDI—Default cost is 1.

X25—Default cost is 5208.

Asynchronous—Default cost is 10,000.

ATM— Default cost is 1.

To illustrate these settings, the following example shows how OSPF cost metrics might be defined for a VMI interface:

interface vmi1
 ipv6 ospf cost dynamic weight throughput 0
 ipv6 ospf cost dynamic weight resources 29
 ipv6 ospf cost dynamic weight latency 29
 ipv6 ospf cost dynamic weight L2-factor 29

EIGRP Cost Metrics

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. Exceptions which will result in immediate update being sent:

A down interface

A down route

Any change in metric which results in the router selecting a new next hop

EIGRP uses the metric weights along with a set of vector metrics to compute the composite metric for local RIB installation and route selections. The EIGRP composite metric is calculated using the formula:

EIGRP Metric = 256*((K1*Bw) + (K2*Bw)/(256-Load) + (K3*Delay)*(K5/(Reliability + K4)))

Table 3 lists the EIGRP vector metrics and their descriptions.

Table 3 EIFRP Vector Metrics

Vector Metric
Description

bandwidth

Minimum bandwidth of the route in kilobits per second. It can be 0 or any positive integer.

delay

Route delay in tens of microseconds. It can be 0 or any positive number that is a multiple of 39.1 nanoseconds.

delay reliability

Likelihood of successful packet transmission expressed as a number between 0 and 255. The value 255 means 100 percent reliability; 0 means no reliability.

load

Effective load of the route expressed as a number from 0 to 255 (255 is 100 percent loading).

mtu

Minimum maximum transmission unit (MTU) size of the route in bytes. It can be 0 or any positive integer.


EIGRP monitors metric weights on an interface to allow for the tuning of EIGRP metric calculations and indicate type of service (TOS). Table 4 lists the K-values and their default.

Table 4 EIGRP K-Value Defaults 

Setting
Default Value

K1

1

K2

0

K3

1

K4

0

K5

0


Most configurations use the first two metrics -delay and bandwidth, with bandwidth taking precedence. The default formula of 256*(BW +Delay) is the EIGRP metric.


Note You can change the weights (as with IGRP), but these weights must be the same on all the routers.


For example, look at an IGRP link whose bandwidth to a particular destination is 128k and the delay is 84000 microseconds.

Using the cut-down formula, the EIGRP metric calculation would simplify to 256*(BW + Delay), resulting in the following value:

Metric = 256*(10^7/128 + 84000/10)= 256*86525 = 22150400

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 L2 to L3. Table 5 lists the EIGRP metrics and their significance.

Table 5 EIGRP Metrics

Metric
EIGRP
Significance

current data rate

unsigned interval

Snapshot value of bytes per second rate on the link

max data rate

unsigned interval

Bytes per second maximum rate on link

latency

unsigned interval

Average delay on the link, specified in ms

resources

unsigned interval

A representation of resources indicating a percentage (0-100), such as, battery power. Harris implementation always reports 100

relative link quality

unsigned interval

opaque number (0-100) representing radio's view of link quality 0 represents the worst possible link, 100 represents the best.


These EIGRP metric values map to the basic EIGRP interface parameters as indicated in Table 6

Table 6 EIGRP Mapping of Metrics for VMI Interfaces

VMI Metric
EIGRP Metric
Mapping

current data rate

Bandwidth

Used directly and is converted to Kbits.

relative link quality resources

Reliability

Calculated according to the following formula:

if resources < 30%

(255 * ((relative link quality + resources)/2) / 100

else

(255 * relative link quality) / 100

max data rate

relative link quality

Delay

Calculated according to the following formula:

calc_delay(maximum_data_rate) * relative link quality / 100) / USEC_TO_MSEC

load

Load

Calculated according to the following formula:

255 - ((255 * load) / 100)



Note If the current data rate = 0; then (current data rate / max data rate) is defined to be 1.


Dynamic Cost Metric for Interfaces

The dynamic cost metric used for interfaces is computed based on the Layer 2 (L2) feedback to Layer 3 (L3). The dynamic cost is calculated using the following formula:

L2L3API

Where the metric calculations are

S1 = ipv6 ospf dynamic weight throughput
S2 = ipv6 ospf dynamic weight resources
S3 = ipv6 ospf dynamic weight latency
S4 = ipv6 ospf dynamic weight L2 factor
OC = standard cost of a non-VMI route

Throughput = (current-data-rate)/(maximum-data-rate)

Router-dynamic cost= OC + (S1) + (S2) + (S3) + (S4)

For a dynamic cost to have the same cost as a default cost, all parameters must equal zero.

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 in conjunction with the throughput, resources, latency, or L2-factor keyword. Each of these weights has a default value of 100% 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 Open Shortest Path First (OSPF) cost.

Because cost components can change rapidly, you may need to dampen the amount of changes in order 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

EIGRP Metric Dampening

Because metric components could be changing rapidly, the frequency of the changes can have an impact on the network. Frequent changes require 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

a down interface

a down route

any change in a metric which results in the router selecting a new nexthop

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, will not be 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, will not be 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, which have outstanding changes to report, will be sent out. If a route changes, such that the final metric of the route matches the last updated metric, no update will be sent.

Neighbor Up/Down Signaling for OSFPv3 and EIGRP

MANETs are highly dynamic environments. Nodes may move into, or out of, radio range at a fast pace. Each time a node joins or leaves, of course, 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 for MANETs reliance on these mechanisms can result in unacceptably slow convergence.

This 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 will immediately sense the loss and establish 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 reduces routing delays and prevents applications from timing out; enables network-based applications and information to be delivered reliably and quickly over directional radio links; provides faster convergence and optimal route selection so that delay-sensitive traffic such as voice and video are not disrupted; and reduces impact on radio equipment by minimizing the need for internal queuing/buffering; also provides consistent Quality of Service for networks with multiple radios.

The messaging allows for flexible rerouting when necessary because of

Noise on the Radio links

Fading of the Radio links

Congestion of the Radio links

Radio link power fade

Utilization of the Radio

Figure 3 illustrates the signaling sequence that occurs when radio links go up and down.

Figure 3 Up and Down Signaling Sequence

PPPoE Credit-based 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 may vary due to location changes or environmental conditions, and many radio transmission systems have limited buffering capabilities. To minimize the need for packet queuing in the radio, Cisco has implemented extensions to the PPPoE protocol that enable the router to control traffic buffering in congestion situations. Implementing flow-control on these router-to-radio sessions also will allow use of quality of service features such as fair queuing.

The solution utilizes a credit-granting mechanism documented in an IETF informational draft. 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 has been 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 have been granted. Credits can be added incrementally over the course of a session.

IPv6 Addresses

You can configure VMI interfaces 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 ipv6-address argument in the ipv6 address command must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.

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 or later releases, Cisco IOS Release 12.0(21)ST, and Cisco IOS Release 12.0(22)S or 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 command-line interface (CLI) displays the following error message when multiple IPv6 addresses within the same prefix on an interface are configured as:

Prefix <prefix-number> already assigned to <interface-type>

For additional information about IPv6 addressing, see Implementing IPv6 Addressing in the Cisco IOS IPv6 Configuration Guide at the following URL:

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a00806f3a6a.html

How to Configure Router-to-Radio Links Using VMI PPPoE

This section identifies the tasks that will be used to configure VMI PPPoE. Configuring the VMI PPPoE involves implementing the infrastructure, establishing the IPv4 and IPv6 addressing schemes, and configuring the routing environment. This document contains configuration guidelines only for configuration of PPPoE as it relates to VMIs. For details about configuring PPPoE, refer to the Cisco IOS Broadband and DSL Configuration Guide. For details about PPPoE commands, refer to the Cisco IOS Broadband and DSL Command Reference.

The following sections are included:

Implementing the VMI Infrastructure Using PPPoE

Configuration Examples for VMI PPPoE

Implementing the VMI Infrastructure Using PPPoE

The PPPoE protocol provides the transport for the mobile network. The following tasks are required to configure PPPoE to support the VMI.

Creating a Subscriber Profile for PPPoE Service Selection (Required)

Configuring the PPPoE Profile for PPPoE Service Selection (Required)

Configuring PPPoE on an Ethernet Interface (Required)

Creating a Subscriber Profile for PPPoE Service Selection

Perform this task to configure a subscriber profile for PPPoE service selection.

SUMMARY STEPS

1. enable

2. configure terminal

3. subscriber profile profile-name

4. pppoe service manet_radio

5. subscriber authorization enable

6. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

subscriber profile profile-name

Example:

Router(config)# subscriber profile manet

Enters Subscriber Profile configuration mode.

Step 4 

pppoe service manet_radio

Example:

Router(config-sss-profile)# pppoe service manet_radio

Adds a PPPoE MANET radio service name to a subscriber profile to enable the use of the VMI interface.

Step 5 

subscriber authorization enable

Example:

Router(config-sss-profile)# subscriber authorization enable

Enable Subscriber Service Switch type authorization. This command is required when VPDN is not used.

Step 6 

exit

Example:

Router(config-sss-profile)# exit

Returns to global configuration mode.

What to Do Next

After you have defined the PPPoE subscriber profile and service, you must apply the definitions to a BBA group

Configuring the PPPoE Profile for PPPoE Service Selection

Perform this task to associate a subscriber profile with 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. enable

2. configure terminal

3. bba-group pppoe {group-name | global}

4. virtual-template template-number

5. service profile subscriber-profile-name [refresh minutes]

6. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

bba-group pppoe {group-name | global}


Example:

Router(config)# bba-group pppoe group1

Defines a PPPoE profile and enters BBA group configuration mode.

The global keyword creates a profile that will serve as the default profile for any PPPoE port that is not assigned a specific profile.

Step 4 

virtual-template template-number

Example:

Router(config-bba-group)# virtual-template 1

Specifies which virtual template will be used to clone virtual access interfaces for all PPPoE ports that use this PPPoE profile.

Step 5 

service profile subscriber-profile-name [refresh minutes]

Example:

Router(config-bba-group)# service profile subscriber-group1

Assigns a subscriber profile to a PPPoE profile.

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.

The PPPoE configuration that is derived from the subscriber gold_isp_A under the PPPoE profile. Use the service profile command with the refresh keyword and the minutes argument to cause the cached PPPoE configuration to be timed out after a specified number of minutes.

Step 6 

end

Example:

Router(config-bba-group)# end

(Optional) Returns to privileged EXEC mode.

Troubleshooting Tips

Use the show pppoe session and debug pppoe commands to troubleshoot PPPoE sessions.

Configuring PPPoE on an Ethernet Interface

Perform this task to assign a PPPoE profile to an Ethernet interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface fastethernet slot/port

4. pppoe enable [group group-name]

5. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface fastethernet slot/port

Example:

Router(config)# interface fastethernet 1/0

Specifies a Fast Ethernet interface and enters interface configuration mode. Ethernet, Fast Ethernet, and Gigabit Ethernet can be used.

Step 4 

pppoe enable [group group-name]

Example:

Router(config-if)# pppoe enable group bba1

Enables PPPoE sessions on an Ethernet interface or subinterface.

Note If a PPPoE profile is not assigned to the interface by using the group group-name option, the interface will use the global PPPoE profile.

Step 5 

end

Example:

Router(config-if)# end

(Optional) Exits the configuration mode and returns to privileged EXEC mode.

Implementing the VMI and Configuring the Routing Protocol

The configuration guidelines in this section are all optional, depending on the method and routing protocol that you choose to support the VMI interface.

Creating and Configuring a Virtual Template for VMI PPPoE

Creating and Configuring a VMI Interface for EIGRP IPv4 (Optional)

Creating and Configuring a VMI interface for EIGRP IPv6 (Optional)

Creating and Configuring a VMI Interface for OSPFv3

Verifying the OSPF Cost Dynamic for a VMI Interface

Verifying the VMI Configuration

Creating and Configuring a Virtual Template for VMI PPPoE

To create and configure a virtual template, use the following commands beginning in global configuration mode. 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.

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. As an example, consider the following configuration:

subscriber authorization enable 
!
subscriber profile one 
pppoe service manet_radio_over_x_band 
! 
! 
subscriber profile two 
pppoe service manet_radio_over_c_band 
! 
! 
! 
bba-group pppoe one 
virtual-template 1 
service profile one
! 
! 
bba-group pppoe two 
virtual-template 2 
service profile two

! 
! 
interface Virtual-Template1 
. 
. 
. 
! 
!
interface Virtual-Template2 
. 
. 
. 

Using this configuration, any PPPoE request for a session (presentation of a PPPoE Active Discovery Initiate, or PADI packet) with the service name of "manet_radio_over_x_band" would use Virtual-Template1 as the interface to be cloned. Conversely, any PADI presented by the radio with the service name of "manet_radio_over_c_band" would use Virtual-Template2.


Note All service names used for MANET implementations must begin with the string "manet_radio".


SUMMARY STEPS

1. enable

2. configure terminal

3. interface virtual-template number

4. ip unnumbered interface-type interface-number
or
ipv6 enable
or both if both IPv4 and IPv6 are used.

DETAILED STEPS

 
Command
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface virtual-template number

Example:
Router(config)# interface virtual-template number

Creates a virtual template, and enters interface configuration mode.

Step 4 

ip unnumbered interface-type interface-number
or
ipv6 enable
or both if both IPv4 and IPv6 are used.



Example:
Router(config-if)# ip unnumbered vmi1

Enables IP processing of IPv4 on an interface without assigning an explicit IP address to the interface.

If you are using IPv6, enter the ipv6 enable command to enable IPv6 processing on the interface.

If you are using both IPv6 and IPv4, include both commands.

Where To Go Next

Refer to the "Virtual Interface Template Service" chapter in the Cisco IOS Dial Solutions Configuration Guide for additional information about configuring the virtual templates

Creating and Configuring a VMI Interface for EIGRP IPv4

Perform this task to create the VMI interface and associate it with the Ethernet interface on which PPPoE is enabled. When you create a VMI interface, assign the IPv6 or IPv4 address to that VMI interface definition. Do not assign any addresses to the corresponding physical interface.

The radio alerts the router with PADT messages that the layer-2 radio frequency (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.


Note This configuration includes Quality of Service (QoS) fair queueing and 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.


SUMMARY STEPS

1. enable

2. configure terminal

3. ip routing

4. no virtual-template subinterface

5. policy-map fair-queue

6. class class-default

7. fair-queue

8. interface virtual-template 1

9. ip unnumbered vmi1

10. service-policy output fair-queue

11. no keepalive

12. interface vmi interface-number

13. ip address address mask

14. no ip redirects

15. no ip split-horizon eigrp autonomous-system-number

16. physical-interface interface-type/slot

17. exit

18. router eigrp autonomous-system-number

19. network network-number ip-mask

20. redistribute connected

21. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

ip routing

Example:

Router# ip routing

Enables IP routing on the router.

Step 4 

no virtual template subinterface

Example:

Router# no virtual template subinterface

Disables the virtual template on the subinterface.

Step 5 

policy-map [type {stack | access-control | port-filter | queue-threshold | logging log-policy}] policy-map-name

Example:

Router(config-pmap)# policy map fair queue

Enters policy map configuration mode and creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

Step 6 

class class-default

Example:

Router(config-pmap)# class class-default

Specifies the name of the class whose policy you want to create or change or specifies the default class (commonly known as the class-default class) before you configure its policy.

Step 7 

fair-queue

Example:

Router(config-pmap)# fair-queue

Enables weighted fair queueing (WFQ) on the interface

Step 8 

interface virtual-template number

Example:

Router(config-if)# interface virtual-template 1

Enters interface configuration mode and creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.

Step 9 

ip unnumbered interface-type interface-number

Example:
Router(config-if)# ip unnumbered vmi1

Enables IP processing of IPv4 on a serial interface without assigning an explicit IP address to the interface

Step 10 

service-policy output fair-queue output fair-queue

Example:

Router(config-if)# 

Attaches a policy map to an input interface or virtual circuit (VC) or an output interface or VC, to be used as the service policy for that interface or VC.

Step 11 

no keepalive

Example:

Router(config-if)# no keepalive

Turns off PPP keepalive messages to the interface.

Step 12 

interface type interface-number

Example:

Router(config-if)# interface vmi interface-number

Specifies the number of the VMI interface.

Step 13 

ip address address mask

Example:

Router(config-if)# ip address address mask

Specifies the IP address of the VMI interface.

Step 14 

no ip redirect

Example:

Router(config)# no ip redirect

Disables the sending of Internet Control Message Protocol (ICMP) redirect messages if the Cisco IOS software is forced to resend a packet through the same interface on which it was received.

Step 15 

no ip split-horizon eigrp autonomous-system-number

Example:

Router(config)# service-policy output fair-queue no ip split-horizon eigrp 101

Disables the split horizon mechanism for the specified session.

Step 16 

physical-interface interface-type/slot

Example:

Router(config-if)#  physical-interface FE/0

Creates the physical subinterface to be associated with the VMI interfaces on the router.

Step 17 

exit


Example:

Router(config-if)#  exit

Leaves (exits) the active session (logs off the device) or exits a command mode to the next higher mode. This command can be used in any EXEC mode (such as User EXEC mode or Privileged EXEC mode) to exit from the EXEC process.

Step 18 

router eigrp autonomous-system-number

Example:

Router(config)# router eigrp 100

Enables EIGRP routing on the router and identifies the autonomous system number.

Step 19 

network network-number ip-mask

Example:

Router(config)# network 10.1.1.0 0.0.0.255

Identifies the EIGRP network.

Step 20 

redistribute connected

Example:

Router(config)# redistribute connected

Redistributes routes from one routing domain into another routing domain.

Step 21 

end

Example:

Router(config)# end

(Optional) Exits the configuration mode and returns to privileged EXEC mode.

Creating and Configuring a VMI interface for EIGRP IPv6

Perform this task to create the VMI interface and associate it with the Ethernet interface on which PPPoE is enabled. When you create a VMI interface, assign the IPv6 address to that VMI interface definition. Do not assign any addresses to the corresponding physical interface.

The radio alerts the router with PADT messages that the layer-2 radio frequency (RF) connection is no longer alive. If you turn off the PPP keepalive messages, it can 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.


Note This configuration includes Quality of Service (QoS) fair queueing and 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.


SUMMARY STEPS

1. enable

2. configure terminal

3. ipv6 unicast-routing

4. ipv6 cef

5. policy-map fair-queue

6. class class-default

7. fair-queue

8. interface virtual-template 1

9. ipv6 enable

10. no keepalive

11. service-policy output fair-queue

12. interface vmi interface-number

13. no keepalive

14. ipv6 address address/prefix-length

15. ipv6 enable

16. ipv6 eigrp as-number

17. no ipv6 redirects

18. no ipv6 split-horizon eigrp as-number

19. physical-interface interface-type/slot

20. ipv6 router eigrp

21. no shutdown

22. redistribute connected

23. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

ipv6 unicast-routing

Example:

Router# ipv6 unicst-routing

Enables IPv6 unicast routing.

Step 4 

ipv6 cef

Example:

Router# ipv6 cef

Enables IPv6 CEF on the router.

Step 5 

policy-map [type {stack | access-control | port-filter | queue-threshold | logging log-policy}] policy-map-name

Example:

Router(config-pmap)# policy map fair queue

Enters policy map configuration mode and creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

Step 6 

class class-default

Example:

Router(config-pmap)# class class-default

Specifies the name of the class whose policy you want to create or change or specifies the default class (commonly known as the class-default class) before you configure its policy.

Step 7 

fair-queue

Example:

Router(config-pmap)# fair-queue

Enables weighted fair queueing (WFQ) on the interface

Step 8 

interface virtual-template number

Example:

Router(config-if)# interface virtual-template 1

Enters interface configuration mode and creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.

Step 9 

ipv6 enable

Example:

Router(config-if)# ipv6 enable

Enables IPv6 routing on the virtual template.

Step 10 

no keepalive

Example:

Router(config-if)# no keepalive

Turns off PPP keepalive messages to the virtual template.

Step 11 

service-po.icy output fair-queue output fair-queue

Example:

Router(config-if)# 

Attaches a policy map to an input interface or virtual circuit (VC) or an output interface or VC, to be used as the service policy for that interface or VC.

Step 12 

interface type number

Example:

Router(config)# interface vmi1

Creates a VMI interface.

Step 13 

no keepalive

Example:

Router(config-if)# no keepalive

Turns off PPP keepalive messages to the VMI interface.

Step 14 

ipv6 address address/prefix

Example:

Router(config-if)#

Specifies the IPv6 address for the interface.

Step 15 

ipv6 enable

Example:

Router(config-if)# ipv6 enable

Enables IPv6 routing on the interface.

Step 16 

ipv6 eigrp as-number

Example:

Router(config-if)# ipv6 eigrp 1

Enables Enhanced Interior Gateway Routing Protocol (EIGRP) for IPv6 on a specified interface and specifies the Autonomous System (AS) number.

Step 17 

no ipv6 redirect

Example:

Router(config-if)# no ipv6 redirect

Disables the sending of Internet Control Message Protocol (ICMP) IPv6 redirect messages if Cisco IOS software is forced to resend a packet through the same interface on which the packet was received

Step 18 

no ipv6 split-horizon eigrp as_number

Example:

Router(config-if)# no ipv6 split-horizon eigrp 100

Disables the split horizon for EIGRP IPv6. Associates this command with a specific EIGRP AS.

Step 19 

physical-interface interface-type/slot

Example:

Router(config-if)# physical-interface FE/0

Creates the physical subinterface to be associated with the VMI interfaces on the router.

Step 20 

ipv6 router eigrp as-number

Example:

Router(config-if)# ipv6 router eigrp 100

Places the router in router configuration mode, creates an Enhanced Interior Gateway Routing Protocol (EIGRP) routing process in IPv6, and allows you to enter additional commands to configure this process.

Step 21 

no shutdown

Example:

Router(config-if)# no shutdown

Restarts a disabled interface or prevents the interface from being shut down.

Step 22 

redistribute connected


Example:

Router(config-if)# redistribute connected

Allows the target protocol to redistribute routes learned by the source protocol and connected prefixes on those interfaces over which the source protocol is running. Redistributes IPv6 routes from one routing domain into another routing domain.

Step 23 

end

Example:

Router(config-if)# end

(Optional) Exits the configuration mode and returns to privileged EXEC mode.

Creating and Configuring a VMI Interface for OSPFv3

Perform this task to create the VMI interface and associate it with the Ethernet interface on which PPPoE is enabled. When you create a VMI interface, assign the IPv6 or IPv4 address to that VMI interface definition. Do not assign any addresses to the corresponding physical interface.

Cisco recommends that IPv6 global addresses not be assigned to VMI for OSPFv3 to decrease convergence times. Instead, OSPFv3 will use the IPv6 Link Local address to form a neighbor relationship. Additionally, you should decrease the OSPF SPF change and hold timers to 1 second each. Doing so will decrease convergence times at a cost of increased activity on the link.

The radio alerts the router with PADT messages that the layer-2 radio frequency (RF) connection is no longer alive. If you turn off the PPP keepalive messages, it can make CPU usage more efficient and help to avoid the potential for the router to terminate the connection if PPP keepalives are missed over a lossy RF link.


Note This configuration includes Quality of Service (QoS) fair queueing and 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.


SUMMARY STEPS

1. enable

2. configure terminal

3. ipv6 unicast-routing

4. ipv6 cef

5. ipv6 enable

6. policy-map fair-queue

7. class class-default

8. fair-queue

9. interface virtual-template 1

10. no keepalive

11. service-policy output fair-queue

12. interface vmi interface-number

13. no keepalive

14. ipv6 enable

15. ipv6 ospf 1 area 0

16. ipv6 ospf network point-to-multipoint

17. ipv6 ospf cost hysterisys 1000

18. ipv6 ospf cost dynamic weight throughput percent

19. ipv6 ospf cost dynamic weight resources percent

20. ipv6 ospf cost dynamic weight latency percent

21. ipv6 ospf cost dynamic weight L2-factor percent

22. ipv6 ospf process-id area area-id [instance instance-id]

23. physical-interface interface-type/slot

24. ipv6 router ospf1

25. router-id ip-address

26. redistribute connected metric type 1

27. timers spf spf-delay spf-hold

28. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

ipv6 unicast-routing

Example:

Router(config)# ipv6 unicst-routing

Enables IPv6 unicast routing.

Step 4 

ipv6 cef

Example:

Router(config)# ipv6 cef

Enables IPv6 CEF on the router.

Step 5 

policy-map [type {stack | access-control | port-filter | queue-threshold | logging log-policy}] policy-map-name

Example:

Router(config-pmap)# policy map fair queue

Enters policy map configuration mode and creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.

Step 6 

class class-default

Example:

Router(config-pmap)# class class-default

Specifies the name of the class whose policy you want to create or change or specifies the default class (commonly known as the class-default class) before you configure its policy.

Step 7 

fair-queue

Example:

Router(config-pmap)# fair-queue

Enables weighted fair queueing (WFQ) on the interface

Step 8 

interface virtual-template number

Example:

Router(config-if)# interface virtual-template 1

Enters interface configuration mode and creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.

Step 9 

no keepalive

Example:

Router(config-if)# no keepalive

Turns off PPP keepalive messages.

Step 10 

service-po.icy output fair-queue output fair-queue

Example:

Router(config-if)# service-policy output fair-queue

Attaches a policy map to an input interface or virtual circuit (VC) or an output interface or VC, to be used as the service policy for that interface or VC.

Step 11 

ipv6 enable

Example:

Router(config-if)# ipv6enable

Enables IPv6 routing on the virtual template.

Step 12 

interface type number

Example:

Router(config-if)# interface vmi1

Creates a VMI interface.

Step 13 

no keepalive

Example:

Router(config-if)# no keepalive

Turns off PPP keepalive messages to the VMI interface.

Step 14 

ipv6 enable

Example:

Router(config-if)# ip address fastethernet 0/0

Enables IPv6 routing on the VMI interface.

Step 15 

ipv6 ospf session area area

Example:

Router(config-if)# ipv6 ospf enable

Enables IPv6 OSPF routing on the interface.

Step 16 

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

Example:

Router(config-if)# ipv6 ospf network point-to-multipoint

Specifies the OSPF network type.

Step 17 

ipv6 ospf cost hysterisis

Example:

ipv6 ospf cost dynamic hysteresis threshold 1000

Sets the hysterisis tolerance for the interface.

Step 18 

ipv6 ospf cost dynamic

Example:

Router(config-if)# ipv6 ospf cost dynamic weight throughput 0

Sets the metric for the throughput threshold.

Step 19 

ipv6 ospf cost dynamic

Example:

Router(config-if)# ipv6 ospf cost dynamic weight resources 29

Sets the metric for the resource factor.

Step 20 

ipv6 ospf cost dynamic

Example:

Router(config-if)# ipv6 ospf cost dynamic weight latency 29

Sets the threshold for the latency factor.

Step 21 

ipv6 ospf cost {number | dynamic}

Example:

Router(config-if)# ipv6 ospf cost dynamic weight L2-factor 29

Sets the metric for the Layer 2 -to- Layer 3 delay factor.

Step 22 

ipv6 ospf process-id area area-id [instance instance-id]

Example:

Router(config-if)# ipv6 ospf 1 area 0

Enables OSPF for IPv6 on an interface.

Step 23 

physical-interface interface-type/slot

Example:

Router(config-if)# physical-interface FE/0

Creates the physical subinterface to be associated with the VMI interfaces on the router.

Step 24 

ipv6 router ospf process-id

Example:

Router(config-if)# ipv6 router ospf1

Enables OSPF for IPv6 router configuration mode.

Step 25 

router-id ip-address

Example:

Router(config-if)# router-id 10.1.1.1

Identifies a specific router rather than allowing the dynamic assignment of the router to occur.

Step 26 

redistribute connected metric-type {internal | external}

Example:

Router(config-if)# redistribute connected metric-type internal

Redistributes IPv6 routes from one routing domain into another routing domain. Allows the target protocol to redistribute routes learned by the source protocol and connected prefixes on those interfaces over which the source protocol is running.

Step 27 

timers spf spf-delay spf-hold

Example:

Router(config-if)#timers spf 1 1

Specifies the spf delay time and maximum hold time in milliseconds to delay the calculations for Value ranges for these arguments is 1 to 600,000 milliseconds.

The OSPF Shortest Path First Throttling feature makes it possible to configure SPF scheduling in millisecond intervals and to potentially delay shortest path first (SPF) calculations during network instability. SPF is scheduled to calculate the Shortest Path Tree (SPT) when there is a change in topology

Step 28 

end

Example:

Router(config-if)# end

(Optional) Exits the configuration mode and returns to privileged EXEC mode.

Verifying the OSPF Cost Dynamic for a VMI Interface

The following shows a sample output display when the OSPF cost dynamic is configured on a VMI.

Router1# show ipv6 ospf interface serial2/0

Serial2/0 is up, line protocol is up
   Link Local Address FE80::A8BB:CCFF:FE00:100, Interface ID 10
   Area 1, Process ID 1, Instance ID 0, Router ID 200.1.1.1
   Network Type POINT_TO_MULTIPOINT, Cost: 64 (dynamic), Cost Hysteresis: 200
   Cost Weights: Throughput 100, Resources 20, Latency 80, L2-factor 100
   Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
   Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
     Hello due in 00:00:19
   Index 1/2/3, flood queue length 0
   Next 0x0(0)/0x0(0)/0x0(0)
   Last flood scan length is 0, maximum is 0
   Last flood scan time is 0 msec, maximum is 0 msec
   Neighbor Count is 0, Adjacent neighbor count is 0
   Suppress hello for 0 neighbor(s)

Verifying the VMI Configuration

Possible commands to use in verifying the configuration include:

show pppoe session all

show interface vmi

show vmi neighbors

show vmi neighbors detail

show ip eigrp interfaces

show ip eigrp neighbors

show ipv6 eigrp interfaces

show ipv6 eigrp neighbors

show ipv6 ospf interface

Configuration Examples for VMI PPPoE

Basic VMI PPPoE Configuration with EIGRP IPv4: Example

Basic VMI PPPoE Configuration with EIGRP IPv4: Example

Basic VMI PPPoE Configuration Using EIGRP for IPv6: Example

VMI PPPoE Configuration Using EIGRP for IPv4 and IPv6: Example

VMI PPPoE Configuration for OSPFv3: Example

VMI PPPoE Configuration Using Multiple Virtual Templates: Example

VMI PPPoE Configuration Using Multiple Virtual Templates: Example

PPPoE Configuration: Example

Configuring Two VMIs: Example

Marking and Queuing Packets over VMI: Example

Basic VMI PPPoE Configuration with EIGRP IPv4: Example

This example illustrates the simplest configuration using EIGRP as the routing protocol. This configuration includes one VMI interface.

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname host1
!
logging buffered 3000000
no logging console
enable password test
!
no aaa new-model
clock timezone EST -5
ip cef
!
no ip domain lookup
subscriber authorization enable
!
subscriber profile host1
 pppoe service manet_radio
!
subscriber profile test
 pppoe service manet_radio
!
!
multilink bundle-name authenticated
no virtual-template subinterface
!
archive
 log config
!
policy-map FQ
 class class-default
  fair-queue
!
bba-group pppoe test
 virtual-template 1
 service profile test
!
bba-group pppoe VMI1
 virtual-template 1
 service profile host1
!
!
interface Loopback1
 ip address 10.9.1.1 255.255.255.0
 no ip proxy-arp
 load-interval 30
!
interface FastEthernet0/0
 no ip address
 no ip mroute-cache
 load-interval 30
 speed 100
 full-duplex
 pppoe enable group VMI1
!
interface Serial1/0
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/1
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
!
interface Serial1/2
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/3
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface FastEthernet2/0
 switchport access vlan 2
 duplex full
 speed 100
!
interface FastEthernet2/1
 switchport access vlan 503
 load-interval 30
 duplex full
 speed 100
!
interface FastEthernet2/2
 shutdown
!
interface FastEthernet2/3
 shutdown
!
interface Virtual-Template1
 ip unnumbered vmi1
 load-interval 30
 no keepalive
 service-policy output FQ
!
interface Vlan1
 no ip address
 no ip mroute-cache
 shutdown
!
interface Vlan2
 ip address 10.15.60.144 255.255.255.0
 no ip mroute-cache
 load-interval 30
!
interface Vlan503
 ip address 10.2.2.2 255.255.255.0
 load-interval 30
!
interface vmi1
 ip address 10.3.3.1 255.255.255.0
 no ip redirects
 no ip split-horizon eigrp 1
 load-interval 30
 eigrp 1 interface dampening-change 50
 physical-interface FastEthernet0/0
!
router eigrp 1
 redistribute connected
 network 10.2.0.0 0.0.255.255
 network 10.3.0.0 0.0.255.255
 auto-summary
!
no ip http server
no ip http secure-server
!
control-plane
!
!
line con 0
 exec-timeout 0 0
 stopbits 1
line aux 0
line vty 0 4
 login
!
end

Basic VMI PPPoE Configuration Using EIGRP for IPv6: Example

This example shows the basic requirements for configuring a VMI interface that uses EIGRP for IPv6 as the routing protocol. It includes one VMI interface.

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname host1
!
logging buffered 3000000
no logging console
enable password lab
!
no aaa new-model
clock timezone EST -5
ip cef
!
!
!
!
no ip domain lookup
ipv6 unicast-routing
ipv6 cef
subscriber authorization enable
!
subscriber profile host1
 pppoe service manet_radio
!
subscriber profile test
 pppoe service manet_radio
!
!
multilink bundle-name authenticated
no virtual-template subinterface
!
!
!
!
archive
 log config
!
!
policy-map FQ
 class class-default
  fair-queue
!
!
!
!
!
bba-group pppoe test
 virtual-template 1
 service profile test
!
bba-group pppoe VMI1
 virtual-template 1
 service profile host1
!
!
!
interface Loopback1
 ip address 10.9.1.1 255.255.255.0
 no ip proxy-arp
 load-interval 30
 ipv6 address 2001:0DB1:1::1/64
 ipv6 enable
 ipv6 eigrp 1
!
interface FastEthernet0/0
 no ip address
 no ip mroute-cache
 load-interval 30
 speed 100
 full-duplex
 pppoe enable group VMI1
!
interface Serial1/0
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/1
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/2
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/3
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface FastEthernet2/0
 switchport access vlan 2
 duplex full
 speed 100
!
interface FastEthernet2/1
 switchport access vlan 503
 load-interval 30
 duplex full
 speed 100
!
interface FastEthernet2/2
 shutdown
!
interface FastEthernet2/3
 shutdown
!
interface Virtual-Template1
 no ip address
 load-interval 30
 ipv6 enable
 no keepalive
 service-policy output FQ
!
interface Vlan1
 no ip address
 no ip mroute-cache
 shutdown
!
interface Vlan2
 ip address 10.15.60.144 255.255.255.0
 no ip mroute-cache
 load-interval 30
!
interface Vlan503
 ip address 10.2.2.2 255.255.255.0
 load-interval 30
 ipv6 address 2001:0DB1:8::1/64
 ipv6 enable
 ipv6 eigrp 1
!
interface vmi1
 no ip address
 load-interval 30
 ipv6 enable
 no ipv6 redirects
 ipv6 eigrp 1
 no ipv6 split-horizon eigrp 1
 physical-interface FastEthernet0/0
!
no ip http server
no ip http secure-server
!
ipv6 router eigrp 1
 router-id 10.9.1.1
 no shutdown
 redistribute connected
!
control-plane
!
line con 0
 exec-timeout 0 0
 stopbits 1
line aux 0
line vty 0 4
 login
!
end

VMI PPPoE Configuration Using EIGRP for IPv4 and IPv6: Example

The following examples shows 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.

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname host1
!
logging buffered 3000000
no logging console
enable password lab
!
no aaa new-model
clock timezone EST -5
ip cef
!
no ip domain lookup
ipv6 unicast-routing
ipv6 cef
subscriber authorization enable
!
subscriber profile host1
 pppoe service manet_radio
!
subscriber profile test
 pppoe service manet_radio
!
!
multilink bundle-name authenticated
no virtual-template subinterface
!
archive
 log config
!
policy-map FQ
 class class-default
  fair-queue
!
bba-group pppoe test
 virtual-template 1
 service profile test
!
bba-group pppoe VMI1
 virtual-template 1
 service profile host1
!
!
interface Loopback1
 ip address 10.9.1.1 255.255.255.0
 no ip proxy-arp
 load-interval 30
 ipv6 address 2001:0DB1:1::1/64
 ipv6 enable
 ipv6 eigrp 1
!
interface FastEthernet0/0
 no ip address
 no ip mroute-cache
 load-interval 30
 speed 100
 full-duplex
 pppoe enable group VMI1
!
interface Serial1/0
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/1
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/2
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface Serial1/3
 no ip address
 no ip mroute-cache
 shutdown
 clock rate 2000000
!
interface FastEthernet2/0
 switchport access vlan 2
 duplex full
 speed 100
!
interface FastEthernet2/1
 switchport access vlan 503
 load-interval 30
 duplex full
 speed 100
!
interface FastEthernet2/2
 shutdown
!
interface FastEthernet2/3
 shutdown
!
interface Virtual-Template1
 ip unnumbered vmi1
 load-interval 30
 ipv6 enable
 no keepalive
 service-policy output FQ
!
interface Vlan1
 no ip address
 no ip mroute-cache
 shutdown
!
interface Vlan2
 ip address 10.15.60.144 255.255.255.0
 no ip mroute-cache
 load-interval 30
!
interface Vlan503
 ip address 10.2.2.2 255.255.255.0
 load-interval 30
 ipv6 address 2001:0DB1:8::1/64
 ipv6 enable
 ipv6 eigrp 1
!
interface vmi1
 ip address 10.3.3.1 255.255.255.0
 no ip redirects
 no ip split-horizon eigrp 1
 load-interval 30
 ipv6 address 2001:0DB1:2::1/64
 ipv6 enable
 no ipv6 redirects
 ipv6 eigrp 1
 no ipv6 split-horizon eigrp 1
 eigrp 1 interface dampening-interval 30
 physical-interface FastEthernet0/0
!
router eigrp 1
 redistribute connected
 network 10.2.0.0 0.0.255.255
 network 10.3.0.0 0.0.255.255
 auto-summary
!
!
!
no ip http server
no ip http secure-server
!
ipv6 router eigrp 1
 router-id 10.9.1.1
 no shutdown
 redistribute connected
!
control-plane
!
!
line con 0
 exec-timeout 0 0
 stopbits 1
line aux 0
line vty 0 4
 login
!
end

VMI PPPoE Configuration for OSPFv3: Example

The following example shows how to configure VMI PPPoE using OSPFv3 as the routing protocol. This configuration includes three VMI interfaces.

Building configuration...

Current configuration : 3568 bytes
!
! Last configuration change at 00:03:01 EST Thu Jan 1 2004
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname host2
!
boot-start-marker
boot system flash:c3270-adventerprisek9-mz.124-11.3.PI6b
boot-end-marker
!
logging buffered 3000000
no logging console
enable password lab
!
no aaa new-model
clock timezone EST -5
!
!
ip cef
!
!
no ip domain lookup
ipv6 unicast-routing
ipv6 cef
subscriber authorization enable
!
subscriber profile host2
 pppoe service manet_radio
!
!
multilink bundle-name authenticated
no virtual-template subinterface
!
policy-map FQ
 class class-default
  fair-queue
!
bba-group pppoe VMI1
 virtual-template 1
 service profile host2
!
bba-group pppoe VMI2
 virtual-template 2
 service profile host2
!
bba-group pppoe VMI3
 virtual-template 3
 service profile host2
!
!
interface Loopback1
 ip address 10.16.1.1 255.255.255.0
 no ip proxy-arp
 load-interval 30
 ipv6 address 2001:0DB1:1::1/64
 ipv6 enable
 ipv6 ospf 1 area 0
!
interface FastEthernet0/0
 no ip address
 load-interval 30
 duplex full
 speed 100
 pppoe enable group VMI3
!
interface GigabitEthernet0/0
 no ip address
 load-interval 30
 duplex full
 speed 100
 pppoe enable group VMI1
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface GigabitEthernet0/1
 no ip address
 load-interval 30
 duplex full
 speed 100
 pppoe enable group VMI2
!
interface Serial1/0
 no ip address
 shutdown
!
interface Serial1/1
 no ip address
 shutdown
!
interface Serial1/2
 no ip address
 shutdown
 clock rate 2000000
!
interface Serial1/3
 no ip address
 shutdown
 clock rate 2000000
!
interface FastEthernet2/0
 switchport access vlan 2
 duplex full
 speed 100
!
interface FastEthernet2/1
 switchport access vlan 503
 load-interval 30
 duplex full
 speed 100
!
interface FastEthernet2/2
 shutdown
!
interface FastEthernet2/3
 shutdown
!
interface Virtual-Template1
 no ip address
 load-interval 30
 ipv6 enable
 no keepalive
 service-policy output FQ
!
interface Virtual-Template2
 no ip address
 load-interval 30
 ipv6 enable
 no keepalive
 service-policy output FQ
!
interface Virtual-Template3
 no ip address
 load-interval 30
 ipv6 enable
 no keepalive
 service-policy output FQ
!
interface Vlan1
 no ip address
 shutdown
!
interface Vlan2
 ip address 10.15.60.146 255.255.255.0
 load-interval 30
!
interface Vlan503
 ip address 10.2.2.2 255.255.255.0
 load-interval 30
 ipv6 address 2001:0DB1:8::1/64
 ipv6 enable
 ipv6 ospf 1 area 0
!
interface vmi1
 no ip address
 load-interval 30
 ipv6 address 2001:0DB1:2::1/64
 ipv6 enable
 ipv6 ospf network point-to-multipoint
 ipv6 ospf cost dynamic hysteresis threshold 1000
 ipv6 ospf cost dynamic weight throughput 0
 ipv6 ospf cost dynamic weight resources 29
 ipv6 ospf cost dynamic weight latency 29
 ipv6 ospf cost dynamic weight L2-factor 29
 ipv6 ospf 1 area 0
 physical-interface GigabitEthernet0/0
!
interface vmi2
 no ip address
 load-interval 30
 ipv6 address 2001:0DB1:3::1/64
 ipv6 enable
 ipv6 ospf network point-to-multipoint
 ipv6 ospf cost dynamic hysteresis threshold 1000
 ipv6 ospf cost dynamic weight throughput 0
 ipv6 ospf cost dynamic weight resources 29
 ipv6 ospf cost dynamic weight latency 29
 ipv6 ospf cost dynamic weight L2-factor 29
 ipv6 ospf 1 area 0
 physical-interface GigabitEthernet0/1
!
interface vmi3
 no ip address
 load-interval 30
 ipv6 address 2001:0DB1:4::1/64
 ipv6 enable
 ipv6 ospf network point-to-multipoint
 ipv6 ospf cost dynamic hysteresis threshold 1000
 ipv6 ospf cost dynamic weight throughput 0
 ipv6 ospf cost dynamic weight resources 29
 ipv6 ospf cost dynamic weight latency 29
 ipv6 ospf cost dynamic weight L2-factor 29
 ipv6 ospf 1 area 0
 physical-interface FastEthernet0/0
!
!
!
no ip http server
no ip http secure-server
!
ipv6 router ospf 1
 router-id 10.16.1.1
 log-adjacency-changes
 redistribute connected metric-type 1
 timers spf 1 1

!
!
!
!
!
control-plane
!
!
line con 0
 exec-timeout 0 0
line aux 0
line vty 0 4
 login
!
end

end

VMI PPPoE Configuration Using Multiple Virtual Templates: Example

The following example shows how to configure VMI using multiple virtual templates. This example shows two VMIs, each with a different service name.

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname router1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
clock timezone EST -5
ip cef
no ip domain lookup
!
!
subscriber authorization enable
!
subscriber profile router1_ground
 pppoe service manet_radio_ground
!
subscriber profile router1_satellite
 pppoe service manet_radio_satellite
!
ipv6 unicast-routing
policy-map fair -
 class class-default
  fair-queue
!
!
!
bba-group pppoe router1_ground
 virtual-template 1
 service profile router1_ground
!
bba-group pppoe router1_satellite
 virtual-template 2
 service profile router1_satellite
 service-policy output fair-queue
!
!
interface Ethernet0/0
 pppoe enable group router1_ground
!
interface Ethernet0/1
 pppoe enable group router1_satellite
!
interface Ethernet0/2
 no ip address
 shutdown
!
interface Ethernet0/3
 no ip address
 shutdown
!
interface Ethernet1/0
 no ip address
 shutdown
!
interface Ethernet1/1
 no ip address
 shutdown
!
interface Ethernet1/2
 no ip address
 shutdown
!
interface Ethernet1/3
 no ip address
 shutdown
!
interface Serial2/0
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/3
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/0
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/3
 no ip address
 shutdown
 serial restart-delay 0
!
interface Virtual-Template1
 ip unnumbered vmi1
 load-interval 30
 no peer default ip address
 no keepalive
 fair-queue
!
interface Virtual-Template2
 ip unnumbered vmi1
 load-interval 30
 no peer default ip address
 no keepalive
 fair-queue
!
interface vmi1
 description ground connection
 ip address 10.2.2.1 255.255.255.0
 physical-interface Ethernet0/0
!
interface vmi2
 description satellite connection
 ip address 10.2.3.1 255.255.255.0
 physical-interface Ethernet0/1
!
router eigrp 1
 network 10.2.2.0 0.0.0.255
 network 10.2.3.0 0.0.0.255
 auto-summary
!
!
no ip http server
!
!
!
!
!
control-plane
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
 login
!
end

PPPoE Configuration: Example

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 FastEthernet 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 list1
  pppoe service service1
  subscriber authorization enable

!
bba-group pppoe bba1
  virtual-template 1
  service profile list1
!
interface FastEthernet0/1
  no ip address
  pppoe enable group bba1
!
interface Virtual-Template 1
  no ip address
  no peer default ip-address
!
interface vmi 1
  no ip address
  physical-interface FastEthernet0/1

Configuring Two VMIs: Example

The following example shows a configuration that includes two VMIs, each having different service names.

version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname router1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
clock timezone EST -5
ip cef
no ip domain lookup
!
!
subscriber authorization enable
!
subscriber profile router1_ground
 pppoe service manet_radio_ground
!
subscriber profile router1_satellite
 pppoe service manet_radio_satellite
!
ipv6 unicast-routing
!
!
!
bba-group pppoe router1_ground
 virtual-template 1
 service profile router1_ground
!
bba-group pppoe router1_satellite
 virtual-template 2
 service profile router1_satellite
!
!
interface Ethernet0/0
 pppoe enable group router1_ground
!
interface Ethernet0/1
 pppoe enable group router1_satellite
!
interface Ethernet0/2
 no ip address
 shutdown
!
interface Ethernet0/3
 no ip address
 shutdown
!
interface Ethernet1/0
 no ip address
 shutdown
!
interface Ethernet1/1
 no ip address
 shutdown
!
interface Ethernet1/2
 no ip address
 shutdown
!
interface Ethernet1/3
 no ip address
 shutdown
!
interface Serial2/0
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial2/3
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/0
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/1
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/2
 no ip address
 shutdown
 serial restart-delay 0
!
interface Serial3/3
 no ip address
 shutdown
 serial restart-delay 0
!
interface Virtual-Template1
 ip unnumbered vmi1
 load-interval 30
 no peer default ip address
 no keepalive
 fair-queue
!
interface Virtual-Template2
 ip unnumbered vmi2
 load-interval 30
 no peer default ip address
 no keepalive
 fair-queue
!
interface vmi1
 description ground connection
 ip address 2.2.2.1 255.255.255.0
 physical-interface Ethernet0/0
!
interface vmi2
 description satellite connection
 ip address 2.2.3.1 255.255.255.0
 physical-interface Ethernet0/1
!
router eigrp 1
 network 2.2.2.0 0.0.0.255
 network 2.2.3.0 0.0.0.255
 auto-summary
!
!
no ip http server
!
!
!
!
!
control-plane
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
 login
!
end

Marking and Queuing Packets over VMI: Example

This configuration example includes QoS features in use with a VMI. Packets are marked either outbound or inbound over the VMI according to a policy map defined on the interface. This configuration differs slightly from standard QoS configurations because it requires that two different policies be applied to two different interfaces.

You apply the fair queue policy to the virtual template to define the queueing mechanism. To mark packets, you create a another policy and apply it to VMI to mark the traffic. The two policy maps work in tandem to provide the QoS support on the radio interface


Note Packets will not be marked if you use the standard fair queue class or use hierarchical policy maps applied to the virtual templates.


The examples that follow show the device configurations that support the marking and queueing on a VMI.

Output Configuration of VMI and Policy Map Configured on Router 1


!
!
!
class-map match-all udp-traffic
 match access-group 100
!
!
policy-map FQ
 class class-default
  fair-queue
policy-map my-marker
 class udp-traffic
  set dscp af41
!
!
interface Virtual-Template1
.
.
.
 service-policy output FQ
!
!
interface vmi1
.
.
.
 service-policy output my-marker
.
.
.
!
access-list 100 permit udp any any
!

Input Configuration for VMI and Policy Map configured on Router 2


!
!
!
class-map match-all udp-traffic
 match access-group 100
!
!
policy-map FQ
 class class-default
  fair-queue
policy-map my-marker
 class udp-traffic
  set dscp ef
!
interface Virtual-Template1
...
 service-policy output FQ
!
interface vmi1
...
 service-policy input my-marker
!
access-list 100 permit udp any any
!

This display is output from the show policy-map command for the VMI and policy map configured on on Router 1.


Router1# show policy-map int vmi1

 vmi1
  Service-policy output: my-marker
    Class-map: udp-traffic (match-all)
      5937331 packets, 6234197550 bytes
      30 second offered rate 840000 bps, drop rate 0 bps
      Match: access-group 100
      QoS Set
        dscp af41
          Packets marked 5937331
    Class-map: class-default (match-any)
      12829 packets, 769740 bytes
      30 second offered rate 0 bps, drop rate 0 bps
      Match: any
!
!
!

This display is output from the show policy-map command for the VMI and policy map configured on on Router 2.

Router2# show policy-map int vmi1
 vmi1
  Service-policy input: my-marker
    Class-map: udp-traffic (match-all)
      5971417 packets, 6150560540 bytes
      30 second offered rate 824000 bps, drop rate 0 bps
      Match: access-group 100
      QoS Set
        dscp ef
          Packets marked 5971418
    Class-map: class-default (match-any)
      26167 packets, 1623087 bytes
      30 second offered rate 0 bps, drop rate 0 bps
      Match: any


Additional References

The following sections provide references related to <<Feature>>.

Related Documents

Related Topic
Document Title

EIGRP

Cisco IOS IP Routing Protocols Configuration Guide and Cisco IOS IP Routing Protocols Command Reference

OSPF

Cisco IOS IP Routing Protocols Configuration Guide and Cisco IOS IP Routing Protocols Command Reference

PPPoE

Cisco IOS Dial Solutions Configuration Guide and Cisco IOS Dial Solutions Command Reference

IPv6

Cisco IOS IPv6 Configuration Guide and Cisco IOS IPv6 Command Reference

IPv6 Addressing

"Implementing IPv6 Addressing and Basic Connectivity" in the Cisco IOS IPv6 Configuration Guide

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a00806f3a6a.html


Standards

Standard
Title

Draft

IETF drafts:

- draft-bberry-pppoe-credit-06.txt for PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics


\

MIBs

MIB
MIB Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs


RFCs

RFC
Title

None

-


Technical Assistance

Description
Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport


Command Reference

This section documents new and modified commands.

debug eigrp notifications

debug vmi

interface vmi

interface vmi

ipv6 ospf cost

ipv6 ospf network

mode bypass

physical-interface

show ipv6 ospf

show ipv6 ospf interface

show pppoe

show vmi neighbors

debug eigrp notifications

To debug notifications sent from the L2L3 API interface, use the debug eigrp notifications command in privileged EXEC mode. To turn off debugging, use the no form of this command.

debug eigrp notifications {rib | interface}

Syntax Description

rib

Captures notifications from the routing information base (RIB)

interface

Captures notifications from the interface.


Command Default

Debugging of EIGRP notifications for the L2L3 API interface is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.4(15)XF

This command was introduced.


Usage Guidelines

Consult Cisco technical support before using this command.


Caution Use of debug commands can have severe performance penalties and should be used with extreme caution. For this reason, Cisco recommends that you contact Cisco technical support before enabling a debug command.

Examples

The following example displays information about the L2L3 API Interface:

Router# debug eigrp notifications rib

debug vmi

To display debugging output for virtual multipoint interfaces (VMIs), use the debug vmi command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug vmi {error | multicast | neighbor | packet | pppoe}

no debug vmi {error | multicast | neighbor | packet | pppoe}

Syntax Description

error

Displays errors received on the interface.

multicast

Displays information about multicast packets going in or out on the interface.

neighbor

Displays information about neighbor relationships causing the VMI interface to go up or down.

packet

Displays information about packets going in or out on the VMI interface.

pppoe

Displays information about the flows between PPPoE and the VMI interface that trigger the creation of a neighbor relationship.


Command Default

Debugging is disabled by default.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.4(15)XF

This command was introduced to support Mobile Adhoc Networking.


Examples

The following is sample output from the debug vmi command when the VMI interface is working correctly:

Router# debug vmi neighbor

Jan  6 07:01:54.601: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Jan  6 07:01:54.605: vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.2
Jan  6 07:01:54.605: vmi_create_neighbor:  V4--  nbr=0, key=::4.3.3.2
Jan  6 07:01:54.605: vmi_create_neighbor:  V6--  nbr=0, key=::
Jan  6 07:01:54.605: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0
Jan  6 07:01:54.605: vmi_nbr_add: Begin. nbr=8381D104 nbr->IPv6linkPtr = 0, 
nbr->IPv4linkPtr = 0
Jan  6 07:01:54.605: VMI:  Begin dump of Neighbor RBTree
Jan  6 07:01:54.605: VMI: vmiLink_t(838368E0),key=::10.3.3.2,V4
Jan  6 07:01:54.605: VMI: nbr addresses: ::  10.3.3.2
Jan  6 07:01:54.605:      mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE
Jan  6 07:01:54.605: VMI: NO L2 STRUCT FOUND
Jan  6 07:01:54.605: VMI:  End dump of Neighbor RBTree
Jan  6 07:01:54.609: vmi1 new nbr ::/10.3.3.2
Jan  6 07:01:54.609: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state 
to up
Jan  6 07:01:54.609: vmi_create_route_tbl_entry: Interface up on vmi1
Jan  6 07:01:54.609: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2
Jan  6 07:01:54.609: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2
Jan  6 07:01:54.617: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is up: new 
adjacency
Jan  6 07:01:55.601: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, 
changed state to up

The following is sample output from the debug vmi command for a periodic status update:

Router# debug vmi neighbor

Jan  6 07:02:24.609: vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.2
Jan  6 07:02:24.609:   cur_tx_bytes = 776, old_tx_bytes = 0, tx_delta = 776
Jan  6 07:02:24.609:   msec_clock_diff = 30004, clock_diff = 30, rate = 102400000
Jan  6 07:02:24.609:   max_traffic = 2207566340

The following is sample output from the debug vmi command when the loss of a neighbor is reported:

Router# debug vmi neighbor

Jan  6 07:02:33.781: vmi_destroy_neighbor: Delete route 10.3.3.2 returned RC_IPROUTEDEL_DB
Jan  6 07:02:33.781: vmi_destroy_neighbor: VMI_IPV4 nbr=8381D104
Jan  6 07:02:33.781: vmi_nbr_delete: deleting V4 linkPtr=838368E0, nbr=8381D104
Jan  6 07:02:33.781: vmiFreeNeighbor: Freeing nbr=8381D104
Jan  6 07:02:33.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state 
to down
Jan  6 07:02:33.781: vmi_hwif_goingdown: called for vmi1
Jan  6 07:02:33.781: vmi_hwif_goingdown: No corresponding VMI interface found for  vmi1
Jan  6 07:02:33.785: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is down: 
igrp2 peer state - DOWN
Jan  6 07:02:33.793: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Jan  6 07:02:34.793: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, 
changed state to down
Jan  6 07:02:35.785: %LINK-5-CHANGED: Interface vmi1, changed state to administratively 
down


The following example shows the status of a VMI peer relationship:

Router# debug vmi neighbor

Jan  6 07:03:37.737: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Jan  6 07:03:37.769: vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.1
Jan  6 07:03:37.769: vmi_create_neighbor:  V4--  nbr=0, key=::10.3.3.1
Jan  6 07:03:37.769: vmi_create_neighbor:  V6--  nbr=0, key=::
Jan  6 07:03:37.769: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0
Jan  6 07:03:37.769: vmi_nbr_add: Begin. nbr=7004A304 nbr->IPv6linkPtr = 0, 
nbr->IPv4linkPtr = 0
Jan  6 07:03:37.769: VMI:  Begin dump of Neighbor RBTree
Jan  6 07:03:37.769: VMI: vmiLink_t(70EF96A8),key=::10.3.3.1,V4
Jan  6 07:03:37.769: VMI: nbr addresses: ::  10.3.3.1
Jan  6 07:03:37.769:      mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE
Jan  6 07:03:37.769: VMI: NO L2 STRUCT FOUND
Jan  6 07:03:37.769: VMI:  End dump of Neighbor RBTree
Jan  6 07:03:37.769: vmi1 new nbr ::/10.3.3.1
Jan  6 07:03:37.769: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state 
to up
Jan  6 07:03:37.769: vmi_create_route_tbl_entry: Interface up on vmi1
Jan  6 07:03:37.769: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1
Jan  6 07:03:37.769: vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1
Jan  6 07:03:37.781: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is up: new 
adjacency
Jan  6 07:03:38.737: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, 
changed state to up
Jan  6 07:04:07.769: vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.1
Jan  6 07:04:07.769:   cur_tx_bytes = 640, old_tx_bytes = 0, tx_delta = 640
Jan  6 07:04:07.769:   msec_clock_diff = 30000, clock_diff = 30, rate = 102400000
Jan  6 07:04:07.769:   max_traffic = 57600

Jan  6 07:04:16.953: vmi_destroy_neighbor: Delete route 10.3.3.1 returned RC_IPROUTEDEL_DB
Jan  6 07:04:16.953: vmi_destroy_neighbor: VMI_IPV4 nbr=7004A304
Jan  6 07:04:16.953: vmi_nbr_delete: deleting V4 linkPtr=70EF96A8, nbr=7004A304
Jan  6 07:04:16.953: vmiFreeNeighbor: Freeing nbr=7004A304
Jan  6 07:04:16.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state 
to down
Jan  6 07:04:16.957: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is down: 
igrp2 peer state - DOWN
Jan  6 07:04:16.961: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Jan  6 07:04:17.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, 
changed state to down

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

vmi-interface-number

The number assigned to the VMI interface.

dampening-change value

(Optional) Value used to minimize the effect of frequent routing changes in router-to-radio configurations. Percent interface metric must change to cause update. Value range is 1to 100.

dampening-interval value

(Optional) Specifies the time interval in seconds to check the interface metrics at which advertising of routing changes occurs. The default value is 30 seconds. Value range is 1to 65535


Command Default

Default for change-based dampening is 50 percent of the computed metric.

Default for interval-based dampening is 30 seconds.

Command Modes

Interface configuration

Command History

Release
Modification

12.4(15)XF

This command was introduced.


Usage Guidelines

This command advertises routing changes for EIGRP traffic only.

The REPLY sent to any QUERY will always contain the latest metric information. Exceptions which will result in immediate UPDATE being sent:

A down interface

A down route

Any change in metric which results in the router selecting a new next hop

Change-based Dampening

The default value for the change tolerance will be 50% of the computed metric. It can be configured in the range from 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.

Interval-based Dampening

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:

interface vmi1
 ip address 10.2.2.1 255.255.255.0
 ipv6 address 2001:0DB1:2::1/96
 ipv6 enable
 eigrp 1 interface dampening-change 50
 physical-interface Ethernet0/0

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:

interface vmi1
 ip address 10.2.2.1 255.255.255.0
 ipv6 address 2001:0DB1:2::1/96
 ipv6 enable
 eigrp 1 interface dampening-interval 30
 physical-interface Ethernet0/0

interface vmi

To create a virtual multipoint interface (VMI) that can be configured and applied dynamically, use the interface vmi command in global configuration mode. Use the no form of this command to remove a VMI interface.

interface vmi interface-number

no interface vmi

Syntax Description

interface-number

Number assigned to the VMI. The value range for VMI interface numbers is from 1 to 2147483647


Command Default

No virtual template number is defined.

Command Modes

Global configuration

Command History

Release
Modification

12.4(15)XF

This command was introduced.


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:

interface vmi 1
  ip address 10.2.1.1 255.255.255.0
  no ip redirects
  no ip split-horizon eigrp 1
  load-interval 30
  ipv6 address 2001:0DB8:1:1:FFFF:FFFF:FFFF:FFFE/64 
  ipv6 enable
  no ipv6 redirects
  ipv6 eigrp 1
  no ipv6 split-horizon eigrp 1
  physical-interface GigabitEthernet 0/0
end

ipv6 ospf cost

To explicitly specify the cost of sending a packet on an interface, use the ipv6 ospf cost command in interface configuration mode. To reset the interface cost to the default value, use the no form of this command.

ipv6 ospf cost interface-cost | dynamic [weight {throughput percent | resources percent | latency percent | L2-factor percent] | [hysteresis [threshold threshold-value]]

no ipv6 ospf cost

Syntax Description

interface-cost

Unsigned integer value expressed as the link-state metric. It can be a value in the range from 1 to 65535.

dynamic

Default value on VMI interfaces.

weight

(Optional) Amount of impact a variable has on the dynamic cost.

throughput percent

Throughput weight of the Layer 2 link, expressed as a percentage. The percent value can be in the range from 0 to 100. The default value is 100.

resources percent

Resources weight (such as battery life) of the router at the Layer 2 link, expressed as a percentage. The percent value can be in the range from 0 to 100. The default value is 100.

latency percent

Latency weight of the Layer 2 link, expressed as a percentage. The percent value can be in the range from 0 to 100. The default value is 100.

L2-factor percent

Quality weight of the Layer 2 link expressed as a percentage. The percent value can be in the range from 0 to 100. The default value is 100.

hysteresis

(Optional) Value used to dampen cost changes.

threshold threshold-value

(Optional) Cost change threshold at which hysteresis will be implemented. The threshold range is from 0 to 64k, and the default threshold value is 10k.


Command Default

Default cost is based on the bandwidth.

Default cost on VMI interfaces is dynamic.

Command Modes

Interface configuration

Command History

Release
Modification

12.0(24)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(15)XF

The following keywords and arguments were added to support Virtual Multipoint Interfaces (VMI) and Mobile Adhoc Networking:

dynamic argument

weight, throughput percent, resources percent, latency percent, and L2-factor percent keywords and arguments

hysteresis and threshold keywords and the threshold-value argument


Usage Guidelines

You can set the metric manually using the ipv6 ospf cost command, if you need to change the default. Using the bandwidth command changes the link cost as long as the ipv6 ospf cost command is not used.

The link-state metric is advertised as the link cost in the router link advertisement.

Dynamic Cost Metric for Interfaces

The dynamic cost metric used for interfaces is computed based on the Layer 2 (L2) feedback to Layer 3 (L3).

In general, the path cost is calculated using the following formula:

Using this formula, the default path costs were calculated as noted in the following list. If these values do not suit your network, you can use your own method of calculating path costs.

56-kbps serial link—Default cost is 1785.

64-kbps serial link—Default cost is 1562.

T1 (1.544-Mbps serial link)—Default cost is 64.

E1 (2.048-Mbps serial link)—Default cost is 48.

4-Mbps Token Ring—Default cost is 25.

Ethernet—Default cost is 10.

16-Mbps Token Ring—Default cost is 6.

FDDI—Default cost is 1.

X25—Default cost is 5208.

Asynchronous—Default cost is 10,000.

ATM— Default cost is 1.The dynamic cost is calculated using the following formula:

L2L3API

Where the metric calculations are

S1 = ipv6 ospf dynamic weight throughput
S2 = ipv6 ospf dynamic weight resources
S3 = ipv6 ospf dynamic weight latency
S4 = ipv6 ospf dynamic weight L2 factor
OC = standard cost of a non-VMI route

Throughput = (current-data-rate)/(maximum-data-rate)

Router-dynamic cost= OC + (S1) + (S2) + (S3) + (S4)

For a dynamic cost to have the same cost as a default cost, all parameters must equal zero.

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 in conjunction with the throughput, resources, latency, or L2-factor keyword. Each of these weights has a default value of 100% 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 Open Shortest Path First (OSPF) cost.

Because cost components can change rapidly, you may need to dampen the amount of changes in order 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.

Examples

The following example sets the interface cost value to 65:

ipv6 ospf cost 65

The following example sets the interface cost value for a VMI interface:

interface vmi 0
ipv6 ospf cost dynamic hysteresis threshold 30
ipv6 ospf cost dynamic weight throughput 75
ipv6 ospf cost dynamic weight resources 70
ipv6 ospf cost dynamic weight latency 80
ipv6 ospf cost dynamic weight L2-factor 10


ipv6 ospf network

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

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

no ipv6 ospf network

Syntax Description

broadcast

Sets the network type to broadcast.

non-broadcast

Sets the network type to nonbroadcast multiaccess (NBMA).

point-to-multipoint [non-broadcast]

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

point-to-point

Sets the network type to point-to-point.


Command Default

Default depends on the network type.

Command Modes

Interface configuration

Command History

Release
Modification

12.0(24)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(15)XF

The point-to-multipint keyword was added to support the Virtual Multipoint Interfaces (VMI) and Mobile Adhoc Networking.


Usage Guidelines

NBMA Networks

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

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

Point-to-Multipoint Networks

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

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

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

Examples

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

interface serial 0
 ipv6 enable
 ipv6 ospf 1 area 0
 ipv6 ospf network broadcast
 encapsulation frame-relay

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

interface serial 0
 ipv6 enable
 ipv6 ospf 1 area 0
 encapsulation frame-relay
 ipv6 ospf cost 100
 ipv6 ospf network point-to-multipoint
 frame-relay map ipv6 2001:0DB1::A8BB:CCFF:FE00:C01 broadcast
 frame-relay map ipv6 2001:0DB1B:CCFF:FE00:C02 broadcast
 frame-relay local-dlci 200
 ipv6 ospf neighbor 2001:0DB1B:CCFF:FE00:C01
 ipv6 ospf neighbor2001:0DB1B:CCFF:FE00:C02

Related Commands

Command
Description

frame-relay map

Defines mapping between a destination protocol address and the DLCI used to connect to the destination address.

ipv6 ospf neighbor

Configures OSPF routers interconnecting to nonbroadcast networks.

x25 map

Sets up the LAN protocols-to-remote host mapping.


mode bypass

To enable Virtual Multipoint Interfaces (VMI) to support multicast traffic, use the mode bypass command in interface configuration mode. To return the interface to the default mode of aggregate, use the no form of this command.

mode [aggregate | bypass]

no mode bypass

Syntax Description

aggregate

Sets the mode to aggregate. All virtual-access interfaces created by PPPoE sessions are logically aggregated under the VMI.

bypass

Sets the mode to bypass.


Command Default

No mode

Command Modes

Interface configuration

Command History

Release
Modification

12.4(15)XF

This command was introduced to support multicast traffic on Virtual Multipoint Interfaces (VMIs).


Usage Guidelines

Use the mode bypass command when you need to support multicast traffic in router-to-radio configurations..

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.

Bypass Mode

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 will continue 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 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.

Examples

The following example sets the interface mode to bypass:

Router# enable
Router# configure terminal
Router(config)# interface vmi1
Router(config-if)# mode bypass

Related Commands

Command
Description

interface vmi

Creates a VMI interface.


physical-interface

To create a physical subinterface to be associated with the Virtual Multipoint Interfaces (VMI) on a router, use the physical-interface command in interface configuration mode. To return the interface to the default mode of synchronous, use the no form of this command.

physical-interface interface-type/slot

no physical-interface

Syntax Description

interface-type

Specifies the type of interface or subinterface; value can be Ethernet, Fast Ethernet, or Gigabit Ethernet.

slot

Indicates the slot in which the interface is present.


Command Default

No physical interface exists until created

Command Modes

Interface configuration

Command History

Release
Modification

12.4(15)XF

This command was introduced to support Virtual Multipoint Interfaces (VMIs).


Usage Guidelines

Use the physical-interface command to create a physical subinterface.

Only one physical interface can be assigned to a VMI interface. Because there is very high number of VMI interfaces that can be used, assign a new VMI for each physical interface.

Examples

The following example shows how to change a low-speed serial interface from synchronous to asynchronous mode:

Router(config)# interface vmi1
Router(config-if)# physical-interface fe0/1

Related Commands

Command
Description

interface vmi

Creates a VMI interface.


show ipv6 ospf

To display general information about Open Shortest Path First (OSPF) routing processes, use the show ipv6 ospf command in user EXEC or privileged EXEC mode.

show ipv6 ospf [process-id] [area-id]

Syntax Description

process-id

(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here is the number assigned administratively when the OSPF routing process is enabled.

area-id

(Optional) Displays information about a specified area only.


Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

12.0(24)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.3(4)T

Command output is changed when authentication is enabled.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(25)SG

This command was integrated into Cisco IOS Release 12.2(25)SG.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(9)T

Command output was updated to display OSPF for IPv6 encryption information.

12.4(15)XF

Command output was modified to include VMI PPPoE process-level values.


Examples

show ipv6 ospf Output Example

The following is sample output from the show ipv6 ospf command:

Router# show ipv6 ospf

Routing Process "ospfv3 1" with ID 10.10.10.1
 SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
 Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
 LSA group pacing timer 240 secs
 Interface flood pacing timer 33 msecs
 Retransmission pacing timer 66 msecs
 Number of external LSA 0. Checksum Sum 0x000000
 Number of areas in this router is 1. 1 normal 0 stub 0 nssa
    Area BACKBONE(0)
        Number of interfaces in this area is 1
        MD5 Authentication, SPI 1000
        SPF algorithm executed 2 times
        Number of LSA 5. Checksum Sum 0x02A005
        Number of DCbitless LSA 0
        Number of indication LSA 0
        Number of DoNotAge LSA 0
        Flood list length 0

Table 7 describes the significant fields shown in the display.

Table 7 show ipv6 ospf Field Descriptions 

Field
Description

Routing process "ospfv3 1" with ID 10.10.10.1

Process ID and OSPF router ID.

LSA group pacing timer

Configured LSA group pacing timer (in seconds).

Interface flood pacing timer

Configured LSA flood pacing timer (in milliseconds).

Retransmission pacing timer

Configured LSA retransmission pacing timer (in milliseconds).

Number of areas

Number of areas in router, area addresses, and so on.


show ipv6 ospf With Area Encryption Example

The following sample output shows the show ipv6 ospf command with area encryption information:

Router# show ipv6 ospf 

Routing Process "ospfv3 1" with ID 10.0.0.1 
It is an area border router 
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs 
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs 
LSA group pacing timer 240 secs 
Interface flood pacing timer 33 msecs 
Retransmission pacing timer 66 msecs 
Number of external LSA 0. Checksum Sum 0x000000 
Number of areas in this router is 2. 2 normal 0 stub 0 nssa 
Reference bandwidth unit is 100 mbps 
    Area BACKBONE(0) 
        Number of interfaces in this area is 2 
        SPF algorithm executed 3 times 
        Number of LSA 31. Checksum Sum 0x107493 
        Number of DCbitless LSA 0 
        Number of indication LSA 0 
        Number of DoNotAge LSA 20 
        Flood list length 0 
    Area 1 
        Number of interfaces in this area is 2 
        NULL Encryption SHA-1 Auth, SPI 1001 
        SPF algorithm executed 7 times 
        Number of LSA 20. Checksum Sum 0x095E6A 
        Number of DCbitless LSA 0 
        Number of indication LSA 0 
        Number of DoNotAge LSA 0 
        Flood list length 0 

Table 8 describes the significant fields shown in the display.

Table 8 show ipv6 ospf with Area Encryption Information Field Descriptions 

Field
Description

Area 1

Subsequent fields describe area 1.

NULL Encryption SHA-1 Auth, SPI 1001

Displays the encryption algorithm (in this case, null, meaning no encryption algorithm is used), the authentication algorithm (SHA-1), and the security policy index (SPI) value value (1001).


show ipv6 ospf interface

To display Open Shortest Path First (OSPF)-related interface information, use the show ipv6 ospf interface command in user EXEC or privileged mode.

show ipv6 ospf [process-id] [area-id] interface [interface-type interface-number] [brief]

Syntax Description

process-id

(Optional) Internal identification. It is locally assigned and can be any positive integer. The number used here is the number assigned administratively when the OSPF routing process is enabled.

area-id

(Optional) Displays information about a specified area only.

interface-type interface-number

(Optional) Interface type and number.

brief

(Optional) Displays brief overview information for OSPF interfaces, states, addresses and masks, and areas on the router.


Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

12.0(24)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S.

12.3(4)T

Command output is changed when authentication is enabled.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(25)SG

This command was integrated into Cisco IOS Release 12.2(25)SG.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.4(9)T

Command output is changed when encryption is enabled.

12.2(33)SRB

The brief keyword was added.

12.4(15)XF

Output displays were modified so that VMI PPPoE interface-based local state values are displayed in the command output when a VMI interface is specified.


Examples

show ipv6 ospf interface Standard Output Example

The following is sample output from the show ipv6 ospf interface command:

Router# show ipv6 ospf interface

ATM3/0 is up, line protocol is up 
  Link Local Address 2001:0DB1:205:5FFF:FED3:5808, Interface ID 13
  Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3
  Network Type POINT_TO_POINT, Cost: 1
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:06
  Index 1/2/2, flood queue length 0
  Next 0x0(0)/0x0(0)/0x0(0)
  Last flood scan length is 12, maximum is 12
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1 
    Adjacent with neighbor 172.16.4.4
  Suppress hello for 0 neighbor(s)
FastEthernet0/0 is up, line protocol is up 
  Link Local Address 2001:0DB1:205:5FFF:FED3:5808, Interface ID 3
  Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3
  Network Type BROADCAST, Cost: 1
  Transmit Delay is 1 sec, State BDR, Priority 1 
  Designated Router (ID) 172.16.6.6, local address 2001:0DB1:205:5FFF:FED3:6408
  Backup Designated router (ID) 172.16.3.3, local address 2001:0DB1:205:5FFF:FED3:5808
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:05
  Index 1/1/1, flood queue length 0
  Next 0x0(0)/0x0(0)/0x0(0)
  Last flood scan length is 12, maximum is 12
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1 
    Adjacent with neighbor 172.16.6.6  (Designated Router)
  Suppress hello for 0 neighbor(s)

Table 9 describes the significant fields shown in the display.

Table 9 show ipv6 ospf interface Field Descriptions 

Field
Description

ATM3/0

Status of the physical link and operational status of protocol.

Link Local Address

Interface IPv6 address.

Area 1, Process ID 1, Instance ID 0, Router ID 172.16.3.3

The area ID, process ID, instance ID, and router ID of the area from which this route is learned.

Network Type POINT_TO_POINT, Cost: 1

Network type and link-state cost.

Transmit Delay

Transmit delay, interface state, and router priority.

Designated Router

Designated router ID and respective interface IP address.

Backup Designated router

Backup designated router ID and respective interface IP address.

Timer intervals configured

Configuration of timer intervals.

Hello

Number of seconds until the next hello packet is sent out this interface.

Neighbor Count

Count of network neighbors and list of adjacent neighbors.


Cisco IOS Release 12.2(33)SRB Example

The following is sample output of the show ipv6 ospf interface command when the brief keyword is entered.

Router# show ipv6 ospf interface brief 

Interface    PID   Area            Intf ID    Cost  State Nbrs F/C
VL0          6     0               21         65535 DOWN  0/0
Se3/0        6     0               14         64    P2P   0/0
Lo1          6     0               20         1     LOOP  0/0
Se2/0        6     6               10         62    P2P   0/0
Tu0          1000  0               19         11111 DOWN  0/0

OSPF with Authenticaion on the Interface Example

The following is sample output from the show ipv6 ospf interface command with authentication enabled on the interface:

Router# show ipv6 ospf interface

Ethernet0/0 is up, line protocol is up
  Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
  Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
  Network Type BROADCAST, Cost:10
  MD5 Authentication SPI 500, secure socket state UP (errors:0)
  Transmit Delay is 1 sec, State BDR, Priority 1
  Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
  Backup Designated router (ID) 10.10.10.1, local address
2001:0DB1:A8BB:CCFF:FE00:6E00
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:01
  Index 1/1/1, flood queue length 0
  Next 0x0(0)/0x0(0)/0x0(0)
  Last flood scan length is 1, maximum is 1
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 10.11.11.1  (Designated Router)
  Suppress hello for 0 neighbor(s)

OSPF with Null Authenticaion Example

The following is sample output from the show ipv6 ospf interface command with null authentication configured on the interface:

Router# show ipv6 ospf interface

Ethernet0/0 is up, line protocol is up
  Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
  Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
  Network Type BROADCAST, Cost:10
  Authentication NULL
  Transmit Delay is 1 sec, State BDR, Priority 1
  Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
  Backup Designated router (ID) 10.10.10.1, local address
2001:0DB1:A8BB:CCFF:FE00:6E00
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:03
  Index 1/1/1, flood queue length 0
  Next 0x0(0)/0x0(0)/0x0(0)
  Last flood scan length is 1, maximum is 1
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 10.11.11.1  (Designated Router)
  Suppress hello for 0 neighbor(s)

OSPF with Authentication for The Area Example

The following is sample output from the show ipv6 ospf interface command with authentication configured for the area:

Router# show ipv6 ospf interface

Ethernet0/0 is up, line protocol is up
  Link Local Address 2001:0DB1:A8BB:CCFF:FE00:6E00, Interface ID 2
  Area 0, Process ID 1, Instance ID 0, Router ID 10.10.10.1
  Network Type BROADCAST, Cost:10
  MD5 Authentication (Area) SPI 1000, secure socket state UP (errors:0)
  Transmit Delay is 1 sec, State BDR, Priority 1
  Designated Router (ID) 10.11.11.1, local address 2001:0DB1:A8BB:CCFF:FE00:6F00
  Backup Designated router (ID) 10.10.10.1, local address
FE80::A8BB:CCFF:FE00:6E00
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:03
  Index 1/1/1, flood queue length 0
  Next 0x0(0)/0x0(0)/0x0(0)
  Last flood scan length is 1, maximum is 1
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 10.11.11.1  (Designated Router)
  Suppress hello for 0 neighbor(s)

OSPF with Dynamic Cost Example

The following display shows sample output from the show ipv6 ospf interface command when the OSPF cost dynamic is configured.

Router1# show ipv6 ospf interface serial2/0

Serial2/0 is up, line protocol is up
   Link Local Address 2001:0DB1:A8BB:CCFF:FE00:100, Interface ID 10
   Area 1, Process ID 1, Instance ID 0, Router ID 172.1.1.1
   Network Type POINT_TO_MULTIPOINT, Cost: 64 (dynamic), Cost Hysteresis: 200
   Cost Weights: Throughput 100, Resources 20, Latency 80, L2-factor 100
   Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
   Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
     Hello due in 00:00:19
   Index 1/2/3, flood queue length 0
   Next 0x0(0)/0x0(0)/0x0(0)
   Last flood scan length is 0, maximum is 0
   Last flood scan time is 0 msec, maximum is 0 msec
   Neighbor Count is 0, Adjacent neighbor count is 0
   Suppress hello for 0 neighbor(s)

show pppoe

Use the show pppoe command to display information about currently active PPPoE sessions.

show pppoe {session | all | derived | packets | relay}

Syntax Description

all

Shows detailed information about the PPPoE session.

derived

Displays information about the cached PPPoE configuration.

relay

Displays PPPoE relay information.

packets

Displays packet statistics for the PPPoe session.

session

Displays summary information about PPPoE sessions.


Command DefaultDefault

None.

Command Modes

User EXEC

Command History

Release
Modification

12.0(24)S

This command was introduced.

12.3(4)T

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.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and support was added for the Cisco 7200, 7301, 7600, and Cisco 10000 series platforms.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2 and the output following the use of the all keyword was modified to indicate if a session is Interworking Functionality (IWF)-specific or if the tag ppp-max-payload tag is in the discovery frame and accepted.

12.4(15)XF

The output was modified to display Virtual Multipoint Interface (VMI) and PPPoE process-level values.


Examples

PPPoE Session Examples

The following example shows output for the show pppoe session command:
Router# show pppoe session 
1 session  in LOCALLY_TERMINATED (PTA) State
     1 session  total

Uniq ID  PPPoE  RemMAC          Port                    VT  VA         State
           SID  LocMAC                                      VA-st
     84     79  0014.a922.b941  Fa0/0                    1  Vi3        PTA
                000a.8a8e.75f8                              UP

The following is sample output from the show pppoe session command:

Router# show pppoe session

     1 session  in FORWARDED (FWDED) State
     1 session  total

Uniq ID
PPPoE 
SID
RemMAC
Port
VT
VA
State
LocMAC
VA-st
26
19
0001.96da.a2c0
Et0/0.1
5
N/A
RELFWD
000c.8670.1006
VLAN:3434

PPPoE Session with IWF and ppp-max-payload Tag Example

The following is sample output from the show pppoe session command when there is an IWF session and the ppp-max-payload tag is accepted in the discovery frame (available in Cisco IOS Release 12.2(31)SB2):

Router# show pppoe session   

     1 session  in LOCALLY_TERMINATED (PTA) State
     1 session  total.  1 session of it is IWF type

Uniq ID
PPPoE 
SID
RemMAC
Port
VT
VA
State
LocMAC
VA-st
Type
26
21
0001.c9f2.a81e
Et1/2
1
Vi2.1
PTA
0006.52a4.901e
UP
IWF


Router# show pppoe session all

Total PPPoE sessions 1


session id: 21
local MAC address: 0006.52a4.901e, remote MAC address: 0001.c9f2.a81e
virtual access interface: Vi2.1, outgoing interface: Et1/2, IWF
PPP-Max-Payload tag: 1500
    15942 packets sent, 15924 received
    224561 bytes sent, 222948 received

Table 10 describes the significant fields shown in the displays.

Table 10 show pppoe session Field Descriptions 

Field
Description

Uniq ID

Unique identifier for the PPPoE session.

PPPoE SID

PPPoE session identifier.

RemMAC

Remote MAC address.

Port

Port type and number.

VT

Virtual-template interface.

VA

Virtual access interface.

State

Displays the state of the session, which will be one of the following:

FORWARDED

FORWARDING

LCP_NEGOTIATION

LOCALLY_TERMINATED

PPP_START

PTA_BINDING

RELFWD (a PPPoE session was forwarded for which the Active discovery messages were relayed)

SHUTTING_DOWN

VACCESS_REQUESTED

LocMAC

Local MAC address.


PPPoE Session Including Credit Flow Statistics Example

The following example shows the output from the show pppoe session all command. This version of the display includes PPPoE credit flow statistics for the session.

Router# show pppoe session all 

Total PPPoE sessions 1 
session id: 1 
local MAC address: aabb.cc00.0100, remote MAC address: aabb.cc00.0200 
virtual access interface: Vi2, outgoing interface: Et0/0 
17 packets sent, 24 received 
1459 bytes sent, 2561 received 
PPPoE Flow Control Stats 
Local Credits: 65504 Peer Credits: 65478 
Credit Grant Threshold: 28000 Max Credits per grant: 65534 
PADG Seq Num: 7 PADG Timer index: 0 
PADG last rcvd Seq Num: 7 
PADG last nonzero Seq Num: 0 
PADG last nonzero rcvd amount: 0 
PADG Timers: [0]-1000 [1]-2000 [2]-3000 [3]-4000 
PADG xmit: 7 rcvd: 7 
PADC xmit: 7 rcvd: 7 
PADQ xmit: 0 rcvd: 0

Related Commands

Command
Description

clear pppoe relay context

Clears PPPoE relay contexts created for relaying PAD messages.

show pppoe relay context all

Displays PPPoE relay contexts created for relaying PAD messages.


show vmi neighbors

To display information about neighbor connections to the Virtual Multipoint Interface (VMI ), use the show vmi neighbors command in User EXEC mode.

show vmi neighbors [detail] [vmi-interface]

Syntax Description

detail

(Optional) Displays details about the VMI neighbors.

vmi-interface

(Optional) Number of the VMI interface


Command Default

If no arguments are specified, information about all neighbors for all VMI interfaces is displayed.

Command Modes

User EXEC

Command History

Release
Modification

12.4(15)XF

This command was introduced.


Usage Guidelines

If no arguments are specified, information about all neighbors for all VMI interfaces is displayed.

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 sample output from the show vmi neighbors command used to display dynamically created neighbors on a VMI interface.

Router# show vmi neighbors vmi1

1 vmi1 Neighbors

           IPV6       IPV4                      Transmit    Receive
Interface  Address    Address       Uptime      Packets     Packets
vmi1       ::         10.3.3.2      00:02:11    0000000008  0000000073

Table 11 describes the significant fields shown in the show vmi neighbors command display.

Table 11 show vmi neighbors Field Descriptions 

Field
Description

Interface

The interface number.

IPv6 Address

IPv6 address of the neighbor.

IPv4 Address

IPv4 address of the neighbor.

Uptime

How long the interface has been up. Time shown in hh:mm:ss format.

Transmit Packets

Number of packets transmitted from the interface during the monitored up time.

Received Packets

Number of packets received on the interface during the monitored up time.


show vmi neighbors command with detail keyword: Example

The following example shows the details about the known VMI neighbors.

Router# show vmi neighbors detail 

1 vmi1 Neighbors

vmi1   IPV6 Address=::
       IPV4 Address=10.3.3.2, Uptime=00:02:16
       Output pkts=8, Input pkts=75
       No Session Metrics have been received for this neighbor.
       Transport PPPoE, Session ID=79
       INTERFACE STATS:
          VMI Interface=vmi1,
             Input qcount=0, drops=0, Output qcount=0, drops=0
          V-Access intf=Virtual-Access3,
             Input qcount=0, drops=0, Output qcount=0, drops=0
          Physical intf=FastEthernet0/0,
             Input qcount=0, drops=0, Output qcount=0, drops=0

PPPoE Flow Control Stats
 Local Credits: 65442   Peer Credits: 65443
 Credit Grant Threshold: 28000    Max Credits per grant: 65534
 PADG Seq Num: 133     PADG Timer index: 0
 PADG last rcvd Seq Num: 133
 PADG last nonzero Seq Num: 0
 PADG last nonzero rcvd amount: 0
 PADG Timers:    [0]-1000    [1]-2000    [2]-3000    [3]-4000
 PADG xmit: 133  rcvd: 133
 PADC xmit: 133  rcvd: 133
 PADQ xmit: 0  rcvd: 0


Table 12 describes the significant fields shown in the show vmi neighbors detail command display.

Table 12 show vmi neighbors detail Field Descriptions 

Field
Description

Interface

The interface number.

IPv6 Address

IPv6 address of the neighbor.

IPv4 Address

IPv4 address of the neighbor.

Uptime

How long the interface has been up. Time shown in hh:mm:ss format.

Output pkts

Number of outgoing packets during the recorded up time.

Input pkts

Number of incoming packets during the recorded up time.

Transmitted packets

Number of packets transmitted from the interface.

Received Packets

Number of packets received on the interface.

Transport

The routing protocol, in this case-PPPoE.

Session ID

The identifier of the VMI session.

INTERFACE STATS

A series of statistics collected on the interface and shows for each of the VMI interface, virtual access interface, and the physical interface. For each interface, statistics are displayed indicating the number of packets in the input and output queues and the number of packets dropped from each queue.

PPPoE Flow Control Stats

The statistics collected for PPPoE credit flow.

Local Credits: The amount of credits belonging to this node.
Peer Credits: The amount of credits belonging to the peer.
Credit Grant Threshold: The number of credits below which the peer needs to dip before this node sends an inband or out-of-band grant.
Max Credits per grant: 65534
PADG Seq Num: 133
PADG Timer index: 0
PADG last rcvd Seq Num: 133
PADG last nonzero Seq Num: 0
PADG last nonzero rcvd amount: 0
PADG Timers: [0]-1000 [1]-2000 [2]-3000 [3]-4000
PADG xmit: numberic rcvd: numeric
PADC xmit: 133 rcvd: 133
PADQ xmit
: 0 rcvd: 0


Feature Information About the Mobile Ad Hoc Networks for Router-to-Radio Communications

Table 13 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.3(14)T or a later release appear in the table., page 43

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS 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 13 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.


Table 13 Feature Information for Mobil Ad Hoc Networks for Router-to-Radio Communications

Feature Name
Releases
Feature Information

PPPoE Support for Credit Flow and Metrics on Router-to-Radio Links Feature

12.4(15)XF

Credit-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:

PPPoE Interfaces for Mobile Radio Communications

PPPoE Credit-based Flow Control

Configuration Examples for VMI PPPoE

OSPFv3 Dynamic Interface Cost Support

12.4(15)XF

OSPFv3 Dynamic Interface Cost Support provides enhancements to the OSPFv3 cost metric for supporting Mobile Adhoc Networking.

The following section provides information about this feature;

OSPF Cost Calculation

EIGRP L2/L3 API and Tunable Metric for Mobile Adhoc Networks

12.4(15)XF

EIGRP 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 L2L3 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 section provides information about this feature:

Link Quality Metrics Reporting for OSPFv3 and EIGRP with VMI Interfaces

Basic VMI PPPoE Configuration Using EIGRP for IPv6: Example

VMI PPPoE Configuration Using EIGRP for IPv4 and IPv6: Example