Introduction

Relief workers, soldiers, public safety personnel, and others need the right information, in the right place, at the right time, wherever they are located. Mobile ad hoc networks are emerging to address these needs. The IETF request for comment, RFC RFC5578, defines a PPP-over-Ethernet (PPPoE) based mechanism for integrating IP routers and mobile radios in ad hoc networks, enabling faster convergence, more efficient route selection, and better performance for delaysensitive traffic.

Radio-Aware Routing (RAR) is a mechanism that uses radios to interact with the routing protocol OSPFv3/EIGRP to signal the appearance, disappearance, and link conditions of one-hop routing neighbors.

In large mobile networks, connections to the routing neighbors are often interrupted due to distance and radio obstructions. When these signals do not reach the routing protocols, protocol timers are used to update the status of a neighbor. Routing protocols have lengthy timers, which is not recommended in mobile networks.

The RAR feature is supported on the Cisco ESR6300 Embedded Series Router.

Mobile Ad Hoc Networking (MANET)

Mobile ad hoc networks are emerging as a means for delivering the benefits of IP networking to users operating beyond the reach of a fixed network. In ad hoc networks, mobile nodes associate on an extemporaneous or ad hoc basis. Ad hoc networks have numerous distinguishing characteristics when compared to conventional networking solutions:

• Self-forming — Nodes that come within radio range of each other can establish a network association without any pre-configuration or manual intervention.

• Self-healing — Nodes can join or leave rapidly without affecting operation of the remaining nodes.

• No infrastructure — In an ad hoc network, mobile nodes form their own network, and essentially become their own infrastructure.

• Peer to peer — Traditional networks typically support end systems operating in client-server mode. In an ad hoc network, mobile nodes can communicate and exchange information without prior arrangement and without reliance on centralized resources.

• Predominantly wireless — Historically networks have been mostly wired, and enhanced or extended through wireless access. The ad hoc environment is essentially wireless, but can be extended to support wired resources.

• Highly dynamic — Mobile nodes are in continuous motion and ad hoc networking topologies are constantly changing.

Collectively, these characteristics will enable ad hoc networks to deliver timely information to a new and underserved class of users. Ad hoc networking solutions can be applied to virtually any scenario that involves a cadre of highly mobile users or platforms (which may include stationary devices as well), a strong need to share IP-based information, and an environment in which fixed infrastructure is impractical, impaired, or impossible.

A Real-World Problem Description

Consider the following diagram:

The above network is a voice, video, data network between moving vehicles that consists of both ground and air vehicles, hence the network is mobile and it is a peer to peer mesh that changes as topographical obstructions are encountered. This is where we get the term mobile ad hock network or MANET for short.

In the scenario in the drawing, all 4 trucks always have connectivity with the helicopters that are flying over the same road. The two helicopters always have line of sight and will always have a connection between each other. The trucks may even be able to connect to the other helicopter or a truck on the opposite road when conditions are favorable.

Here we see that the path between trucks 1 and 3 are completely blocked. The path between Truck 2 and 4 is about to be blocked.

Our existing routing protocols such as OSPFv3 and EIGRP need to adjust its path metrics very quickly to maintain a cohesive operational network. The routing protocol also needs a way to get that information from the radios and that requires a radio to router protocol that is delivered by Cisco Radio Aware Routing in the form of two open protocols:

• PPP over Ethernet (PPPoE)

• Dynamic Link Exchange Protocol (DLEP)

Both protocols are discussed later in this document.

Point-to-Point Protocol over Ethernet PPPoE or PPPoE

PPPoE is a well-defined communication mechanism between the client and the server. In the RAR implementation, radio takes the role of the PPPoE client and router takes the role of the PPPoE server. This allows a loose coupling of radio and router, while providing a well-defined and predictable communication mechanism.

As PPPoE is a session or a connection oriented protocol, it extends the point-to-point radio frequency (RF) link from an external radio to an IOS router.

PPPoE Extensions

PPPoE extensions are used when the router communicates with the radio. In the Cisco IOS implementation of PPPoE, each individual session is represented by virtual access interface (connectivity to a radio neighbor) on which, QoS can be applied with these PPPoE extensions.

RFC5578 provides extensions to PPPoE to support credit-based flow control and session-based real time link metrics, which are very useful for connections with variable bandwidth and limited buffering capabilities (such as radio links).

Virtual Multipoint Interface (VMI)

Though PPPoE Extensions provides most of the setup to communicate between a router and a radio, VMI addresses the need to manage and translate events that higher layers (example, routing protocols) consume. In addition, VMI operates in the Bypass mode.

In Bypass mode, every Virtual Access Interface (VAI) representing a radio neighbor is exposed to routing protocols OSPFv3 and EIGRP, so that, the routing protocol directly communicates with the respective VAI for both unicast and multicast routing protocol traffic.

Note	DLEP only supports aggregate mode. The preferred mode for PPPOE is bypass.

In Aggregate mode, VMI is exposed to the routing protocols (OSPF) so that the routing protocols can leverage VMI for their optimum efficiency. When the network neighbors are viewed as a collection of networks on a point-to-multipoint link with broadcast and multicast capability at VMI, VMI helps in aggregating the multiple virtual access interfaces created from PPPoE. VMI presents a single multi access layer 2 broadcast capable interface. The VMI layer re-directs unicast routing protocol traffic to the appropriate P2P link (Virtual-Access interface), and replicates any Multicast/Broadcast traffic that needs to flow. Since the routing protocol communicates to a single interface, the size of the topology database is reduced, without impacting the integrity of the network.

About MANETs

Mobile Ad Hoc Networks (MANETs) for device-to-radio communications address the challenges faced when merging IP routing and mobile radio communications in ad hoc networking applications.

Through the device-to-radio link, the radio can inform the device immediately when a node joins or leaves, and this enables the device to recognize topology changes more quickly than if it had to rely on timers. Without this link-status notification from the radio, the device would likely time out while waiting for traffic. The link-status notification from the radio enables the device to respond faster to network topology changes. Metric information regarding the quality of a link is passed between the device and radio, enabling the device to more intelligently decide on which link to use.

With the link-status signaling provided by the device-to-radio link, applications such as voice and video work better because outages caused by topology changes are reduced or eliminated. Sessions are more stable and remain active longer.

Cross-layer feedback for device-to-radio integration of Radio-Aware Routing (RAR) takes advantage of the functions defined in RFC 5578. The RFC 5578 is an Internet Engineering Task Force (IETF) standard that defines PPP over Ethernet (PPPoE) extensions for Ethernet-based communications between a device and a mobile radio, that operates in a variable-bandwidth environment and has limited buffering capabilities. These extensions provide a PPPoE session-based mechanism for sharing radio network status such as link-quality metrics and establishing flow control between a device and an RAR-compliant radio.

An RAR-compliant radio initiates a Layer 2 PPPoE session with its adjacent device on behalf of every device and radio neighbor discovered in the network. These Layer 2 sessions are the means by which radio network status for each neighbor link is reported to the device. The radio establishes the correspondence between each PPPoE session and each link to a neighbor.

PPPoE Interfaces for Mobile Radio Communications

The Mobile Ad Hoc Network (MANET) implementation uses PPP over Ethernet (PPPoE) sessions to enable intranodal communications between a device 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 (device-to-device). This is duplicated each time a radio establishes a new radio link. The virtual multipoint interface (VMI) on the device can aggregate multiple PPPoE sessions and multiplex them to look like a single interface to the routing processes. Underneath the VMI are virtual access interfaces that are associated with each of the PPP and PPPoE connections.

A PPPoE session is established between a device and a radio on behalf of every other device and 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 device. The figure below shows the PPPoE session exchange between mobile devices and directional radios in a MANET network.

This capability requires that a Radio-Aware Routing (RAR)-compliant radio be connected to a device through Ethernet. The device always considers the Ethernet link to be up. If the radio side of the link goes down, the device waits until a routing update timeout occurs to declare the route down and then updates the routing table. The figure below shows a simple device-to-radio link topology.

Neighbor Up and Down Signaling

Mobile Ad Hoc Networks (MANETs) are highly dynamic environments. Nodes might move into, or out of, radio range at a fast pace. Each time a node joins or leaves, the network topology must be logically reconstructed by the devices. Routing protocols normally use timer-driven hello messages or neighbor timeouts to track topology changes, but MANETs reliance on these mechanisms can result in unacceptably slow convergence.

The neighbor up/down signaling capability provides faster network convergence by using link-status signals generated by the radio. The radio notifies the device each time a link to another neighbor is established or terminated by the creation and termination of PPP over Ethernet (PPPoE) sessions. In the device, the routing protocols (Open Shortest Path First version 3 [OSPFv3] or Enhanced Interior Gateway Routing Protocol [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 device immediately senses the loss and establishes a new route to the vehicle through neighbors that are not blocked. This high-speed network convergence is essential for minimizing dropped voice calls and disruptions to video sessions.

When virtual multipoint interfaces (VMIs) with PPPoE are used and a partner node has left or a new one has joined, the radio informs the device immediately of the topology change. Upon receiving the signal, the device immediately declares the change and updates the routing tables. The signaling capability provides these advantages:

• 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

• Reduces impact on radio equipment by minimizing the need for internal queueing and buffering

• Provides consistent quality of service for networks with multiple radios

The messaging allows for flexible rerouting when necessary because of these factors:

• Fading of the radio links

• Congestion of the radio links

• Radio link power fade

• Utilization of the radio

The figure below shows the signaling sequence that occurs when radio links go up and down:

PPPoE Credit-based and Metric-based Scaling and Flow Control

Each radio initiates a PPP over Ethernet (PPPoE) session with its local device 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 (device-to-device). This process is duplicated each time a radio establishes a new link.

The carrying capacity of each radio link might vary due to location changes or environmental conditions, and many radio transmission systems have limited buffering capabilities. To minimize the need for packet queueing in the radio, PPPoE protocol extensions enable the device to control traffic buffering in congestion situations. Implementing flow-control on these device-to-radio sessions allows use of quality of service (QoS) features such as fair queueing.

The flow-control solution utilizes a credit-granting mechanism documented in RFC 5578. When the PPPoE session is established, the radio can request a flow-controlled session. If the device acknowledges the request, all subsequent traffic must be flow controlled. If a flow-control session is requested and cannot be supported by the device, the session is terminated. Typically, both the radio and the device initially grant credits during session discovery. Once a device exhausts its credits, it must stop sending until additional credits are granted. Credits can be added incrementally over the course of a session.

Metrics scaling is used with high-performance radios that require high-speed links. The radio can express the maximum and current data rates with different scaler values. Credit scaling allows a radio to change the default credit grant (or scaling factor) of 64 bytes to its default value. You can display the maximum and current data rates and the scalar value set by the radio in the show vmi neighbor detail command output.

DLEP QoS Example

The following figure shows an example topology for DLEP with QoS.

Based on above figure, the QoS policy is applied to egress of Virtual-Template attached to WAN interface Gi0/0/0.

UUT1 Running Configuration

UUT1# show running-config
Building configuration...

Current configuration : 7773 bytes
!
!
version 17.8
service timestamps debug datetime msec
service timestamps log datetime msec
service call-home
platform qfp utilization monitor load 80
platform punt-keepalive disable-kernel-core
!
hostname UUT1
!
boot-start-marker
boot system bootflash:/c6300-universalk9.SSA.bin
!
ipv6 unicast-routing
!
class-map match-any CMAP_VIDEO
 match dscp 33 
 match dscp 35 
 match dscp 37 
 match dscp 39 
 match dscp af41 
class-map match-any CMAP_VOICE
 match dscp 41 
 match dscp 43 
 match dscp 45 
 match dscp 47 
 match dscp 49 
class-map match-any CMAP_DATA
 match dscp 9 
 match dscp 11 
 match dscp 13 
 match dscp 15 
 match dscp af11 
!
policy-map Queue_Map
 class CMAP_VOICE
  bandwidth percent 40 
  set dscp af11
 class CMAP_VIDEO
  bandwidth percent 50 
 class CMAP_DATA
  bandwidth percent 10 
  set dscp af23
!
interface Loopback1
 ip address 1.1.1.1 255.255.255.255
 ipv6 enable
 ospfv3 1 ipv4 area 0
!
interface GigabitEthernet0/0/0
 ip address 10.0.0.1 255.255.255.0
 ip dlep vtemplate 1 port 11113 tcp port 11114 client ip 10.0.0.3 port 11115
 negotiation auto
 ipv6 address 1000::1/64
 ipv6 enable
!
interface GigabitEthernet0/0/1
 no ip address
 shutdown
 negotiation auto
!
interface GigabitEthernet0/1/0
 switchport access vlan 30
!
interface GigabitEthernet0/1/1
!
interface GigabitEthernet0/1/2
!
interface GigabitEthernet0/1/3
!
interface Virtual-Template1
 ip unnumbered GigabitEthernet0/0/0
 ipv6 enable
 service-policy output Queue_Map
!
interface Vlan1
 no ip address
!
interface Vlan30
 ip address 192.168.10.1 255.255.255.0
 ipv6 address 1010::1/64
 ipv6 enable
 ospfv3 1 ipv6 area 0
!
interface Async0/2/0
 no ip address
 encapsulation scada
!
interface vmi1
 ip unnumbered GigabitEthernet0/0/0
 ipv6 address FE80::7E31:EFF:FE85:1E78 link-local
 ipv6 enable
 ospfv3 1 ipv4 area 0
 physical-interface GigabitEthernet0/0/0
!
router ospfv3 1
 !
 router-id 1.1.1.1 
 address-family ipv4 unicast
 exit-address-family
!
end
UUT1#

Validation for DLEP QoS

For the above example, where QoS policy is applied to Virtual-Template1, data packets are flowing through Virtual-Access2 interface which is created when DLEP neighbors came up.

Note	The CLI show policy-map interface Virtual-Template1 will not show the stats.

UUT1#show policy-map interface Virtual-Template 1
 Virtual-Template1 

  Service-policy output: Queue_Map

Service policy content is displayed for cloned interfaces only such as virtual access and sessions.

See the output for Virtual-Access 2:

UUT1#show policy-map interface Virtual-Access 2
 Virtual-Access2 
  Service-policy output: Queue_Map

    Class-map: CMAP_VOICE (match-any)  
      0 packets, 0 bytes
      5 minute offered rate 0000 bps, drop rate 0000 bps
      Match:  dscp 41 
      Match:  dscp 43 
      Match:  dscp 45 
      Match:  dscp 47 
      Match:  dscp 49 
      Queueing
      queue limit 208 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 0/0
      bandwidth 40% (400000 kbps)
      QoS Set
        dscp af11
          Marker statistics: Disabled

    Class-map: CMAP_VIDEO (match-any)  
      0 packets, 0 bytes
      5 minute offered rate 0000 bps, drop rate 0000 bps
      Match:  dscp 33 
      Match:  dscp 35 
      Match:  dscp 37 
      Match:  dscp 39 
      Match:  dscp af41 (34)
      Queueing
      queue limit 208 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 0/0
      bandwidth 50% (500000 kbps)

    Class-map: CMAP_DATA (match-any)  
      0 packets, 0 bytes
      5 minute offered rate 0000 bps, drop rate 0000 bps
      Match:  dscp 9 
      Match:  dscp 11 
      Match:  dscp 13 
      Match:  dscp 15 
      Match:  dscp af11 (10)
      Queueing
      queue limit 208 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 1024337/34827458
      bandwidth 10% (100000 kbps)
      QoS Set
        dscp af23
          Marker statistics: Disabled

    Class-map: class-default (match-any)  
      0 packets, 0 bytes
      5 minute offered rate 0000 bps, drop rate 0000 bps
      Match: any 
      
      queue limit 208 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 0/0

Configuring DLEP on Physical Interface

Navigate to Configuration > Interface > Ethernet. Select the interface to configure and then apply the DLEP Virtual Template. Click on Update & Apply to Device.

Configuring DLEP on the Sub-Interface

Navigate to Configuration > Interface > Ethernet. Select the sub-interface to configure and then apply the DLEP Virtual Template. Click on Update & Apply to Device.

Configuring the Virtual-Template

Navigate to Configuration > Interface > Logical. Select the Virtual-Template tab. From here you can Add, Edit, or Delete interfaces.

Add/Edit the Virtual-Template

Select Add. The Add Virtual Interface window appears.

Click on Apply to Device.

Configuring the VMI

Navigate to Configuration > Interface > Logical. Select the VMI tab. From here you can Add, Edit, or Delete interfaces.

Add/Edit the VMI

Select Add. The Add VMI window appears.

Click on Apply to Device.

Monitoring DLEP

Navigate to Monitoring > General > DLEP. There are two tabs available for monitoring Neighbors or Clients. The Neighbors tab will display information equivalent to the CLI show dlep neighbors. The Clients tab will display information equivalent to the CLI show dlep clients.

DLEP Neighbors

Under the Neighbors tab, select the interface.

Open the interface to view the details.

DLEP Clients

The Clients tab works in the same manner as the Interface tab. Select the interface and open it to view the details.

DLEP Configuration

Router# show dlep config ?
  GigabitEthernet  GigabitEthernet IEEE 802.3z
  |                Output modifiers
  <cr>             <cr>

Router# show dlep config g0/0/1
DLEP Configuration for GigabitEthernet0/0/1

DLEP Peer Description - 
DLEP Version = RFC 8175
DLEP Server IP=10.0.0.1:11117
DLEPv27 TCP Port = 11118
Virtual template=2
Timers (all values are in seconds):
Missed heartbeat threshold=2, Peer Terminate ACK timeout=10
Dlepv27 Applicable configs(in seconds):
Heartbeat interval=5, Discovery interval =5, Session Ack timeout=10
Neighbor activity timeout=0, Neighbor Down ACK timeout=10

DLEP Clients

Router# show dlep clients ?
  GigabitEthernet  GigabitEthernet IEEE 802.3z
  |                Output modifiers
  <cr>             <cr>

Router# show dlep clients
DLEP Clients for all interfaces:



DLEP Clients for Interface GigabitEthernet0/0/1
DLEP Server IP=10.0.0.1:11117 Sock=0 --> Local Router IP address


DLEP Client IP=10.0.0.2:859 TCP Socket fd=1 --> Directly connected Radio to the router
Peer ID=2, Virtual template=2
Description: DLEP_RadioSIM2
Peer Timers (all values in milliseconds):
  Heartbeat=5000, Dead Interval=10000, Terminate ACK=20000
Neighbor Timers (all values in seconds):
  Activity timeout=0, Neighbor Down ACK=10

Supported Metrics:
  Link RLQ RX Metric : 100
  Link RLQ TX Metric : 100
  Link Resources Metric : 100
  Link MTU Metric : 100
  Link Latency Metric : 250 microseconds
  Link CDR RX Metric : 100000000 bps
  Link CDR TX Metric : 100000000 bps
  Link MDR RX Metric : 100000000 bps
  Link MDR TX Metric : 100000000 bps
Router#

DLEP Neighbor

Router# show dlep neighbor ?
  GigabitEthernet  GigabitEthernet IEEE 802.3z
  |                Output modifiers
  <cr>             <cr>

Router# show dlep neighbor
DLEP Neighbors for all interfaces:

DLEP Neighbors for Interface GigabitEthernet0/0/1
DLEP Server IP=10.0.0.1:11117 Sock=0   ---> Local Router IP address

SID=2151  MAC_Address=a453.0e94.f861 
  Addresses:
  IPv4 : 16.0.0.1           ---> Mac-Address and IPv4 address of neighbor's end-point device
Supported Metrics:
  RLQ RX Metric : 100
  RLQ TX Metric : 100
  Resources Metric : 100
  MTU Metric : 1500
  Latency Metric : 250 microseconds
  CDR RX Metric : 100000000 bps
  CDR TX Metric : 100000000 bps
  MDR RX Metric : 100000000 bps
  MDR TX Metric : 100000000 bps

DLEP Counters

Router# show dlep counters ?
  GigabitEthernet  GigabitEthernet IEEE 802.3z
  |                Output modifiers
  <cr>             <cr>

UUT1# show dlep counters
DLEP Counters for GigabitEthernet0/0/1

Last Clear Time = 

DLEP Version = RFC 8175
DLEP Server IP=10.0.0.1:11117
DLEPv5 TCP Port = 11118

Peer Counters:
RX Peer Discovery     0      TX Peer Offer             0     
 RX Peer Offer         0      TX Peer Discovery         0     
 RX Peer Init          0      TX Peer Init Ack          0     
 RX Peer Init Ack      1      TX Peer Init              1     
 RX Heartbeat          41     TX Heartbeat              41    
 RX Peer Terminate     0      TX Peer Terminate Ack     0     
 RX Peer Terminate Ack 0      TX Peer Terminate         0     

Neighbor Counters:
RX Neighbor Up        1      TX Neighbor Up Ack        1     
 RX Metric             0     
 RX Neighbor Down      0      TX Neighbor Down Ack      0     
 RX Neighbor Down Ack  0      TX Neighbor Down          1     

Exception Counters:
RX Invalid Message    0      RX Unknown Message        0     
 Pre-Existing Neighbor 0      Neighbor Resource Error   1     
 Neighbor Not Found    0      Neighbor Msg Peer Not Up  0     

Timer Counters:
Peer Heartbeat Timer         41    
 Peer Terminate Ack Timer     0     
 Neighbor Terminate Ack Timer 0     
 Neighbor Activity Timer      0     
 Radio Connect Timer          5     

Single Timer Wheel "Manet Infra Wheel"
  Granularity      = 250 msec
  Wheel size       = 4096
  Spoke index      = 3730
  Tick count       = 3423890
  Flags            = 0x00
  Active timers    = 1
  High water mark  = 1
  Started timers   = 171177
  Restarted timers = 2
  Cancelled timers = 5
  Expired timers   = 171169
  Long timers      = 0
  Long timer revs  = 0
  Timer suspends   = 0

Scenario 1 : DLEP client is not reachable

In this scenario, the router is not running in discovery mode, and the client/radio attributes have been explicitly configured.

Router# show dlep clients

DLEP Clients for all interfaces:


DLEP Clients for Interface GigabitEthernet0/0/1
DLEP Server IP=14.0.0.3:11117 Sock=-1

Router#show dlep config
DLEP Configuration for GigabitEthernet0/0/1

DLEP Peer Description - 
DLEP Version = RFC 8175
DLEP Server IP=14.0.0.3:11117
DLEPv27 TCP Port = 11118
 Virtual template=2
 Timers (all values are in seconds):
 Missed heartbeat threshold=2, Peer Terminate ACK timeout=10
 Dlepv27 Applicable configs(in seconds):
 Heartbeat interval=60, Discovery interval =5, Session Ack timeout=10
 Neighbor activity timeout=0, Neighbor Down ACK timeout=10

Router#show run int g0/0/1
Building configuration...

Current configuration : 245 bytes
!
interface GigabitEthernet0/0/1
 ip address 14.0.0.3 255.255.255.0
 ip dlep set peer-heartbeat-interval 60
 ip dlep vtemplate 2 port 11117 tcp port 11118 client ip 14.0.0.6 port 859
 negotiation auto
 ipv6 address 1111::1/120
 ipv6 enable
end

Router#show ip arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.199.184.2            9   0013.5f22.0b4a  ARPA   GigabitEthernet0/0/0
Internet  10.199.184.3            8   0018.7414.4e80  ARPA   GigabitEthernet0/0/0
Internet  10.199.184.19           -   a453.0e94.f638  ARPA   GigabitEthernet0/0/0
Internet  14.0.0.2                4   000c.297a.6b3d  ARPA   GigabitEthernet0/0/1
Internet  14.0.0.3                -   a453.0e94.f639  ARPA   GigabitEthernet0/0/1
Internet  14.0.0.6                0   Incomplete      ARPA   

Router#ping 14.0.0.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 14.0.0.6, timeout is 2 seconds:
...
Success rate is 0 percent (0/3)

Router#show run int g0/0/1
Building configuration...

Current configuration : 245 bytes
!
interface GigabitEthernet0/0/1
 ip address 14.0.0.3 255.255.255.0
 ip dlep set peer-heartbeat-interval 60
 ip dlep vtemplate 2 port 11117 tcp port 11118 client ip 14.0.0.6 port 859
 negotiation auto
 ipv6 address 1111::1/120
 ipv6 enable
end

Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int g0/0/1
Router(config-if)#no ip dlep vtemplate 2 port 11117 tcp port 11118 client ip 14.0.0.6 port 859
Router(config-if)# ip dlep set peer-heartbeat-interval 60
Router(config-if)#ip dlep vtemplate 2 port 11117 tcp port 11118 client ip 14.0.0.6 port 859
Router(config-if)#^Z
Router#
*Feb 18 19:43:48.951: %SYS-5-CONFIG_I: Configured from console by console

Router#show dlep counters
DLEP Counters for GigabitEthernet0/0/1

Last Clear Time = 

DLEP Version = RFC 8175
DLEP Server IP=14.0.0.3:11117
DLEPv5 TCP Port = 11118

Peer Counters:
 RX Peer Discovery     0      TX Peer Offer             0     
 RX Peer Offer         0      TX Peer Discovery         0     
 RX Peer Init          0      TX Peer Init Ack          0     
 RX Peer Init Ack      1      TX Peer Init              1     
 RX Heartbeat          0      TX Heartbeat              0     
 RX Peer Terminate     0      TX Peer Terminate Ack     0     
 RX Peer Terminate Ack 0      TX Peer Terminate         0     

Neighbor Counters:
 RX Neighbor Up        0      TX Neighbor Up Ack        0     
 RX Metric             0     
 RX Neighbor Down      0      TX Neighbor Down Ack      0     
 RX Neighbor Down Ack  0      TX Neighbor Down          0     

Exception Counters:
 RX Invalid Message    0      RX Unknown Message        0     
 Pre-Existing Neighbor 0      Neighbor Resource Error   0     
 Neighbor Not Found    0      Neighbor Msg Peer Not Up  0     

Timer Counters:
 Peer Heartbeat Timer         0     
 Peer Terminate Ack Timer     0     
 Neighbor Terminate Ack Timer 0     
 Neighbor Activity Timer      0     
 Radio Connect Timer          1     

Single Timer Wheel "Manet Infra Wheel"
  Granularity      = 250 msec
  Wheel size       = 4096
  Spoke index      = 1710
  Tick count       = 9902
  Flags            = 0x00
  Active timers    = 1
  High water mark  = 1
  Started timers   = 95
  Restarted timers = 4
  Cancelled timers = 4
  Expired timers   = 86
  Long timers      = 0
  Long timer revs  = 0
  Timer suspends   = 0

Router#
Router#show dlep clients 

DLEP Clients for all interfaces:

DLEP Clients for Interface GigabitEthernet0/0/1
DLEP Server IP=14.0.0.3:11117 Sock=0


DLEP Client IP=14.0.0.2:859 TCP Socket fd=1
 Peer ID=3, Virtual template=2
 Description: DLEP_RadioSIM2
 Peer Timers (all values in milliseconds):
  Heartbeat=60000, Dead Interval=120000, Terminate ACK=240000
 Neighbor Timers (all values in seconds):
  Activity timeout=0, Neighbor Down ACK=10

 Supported Metrics:
  Link RLQ RX Metric : 100
  Link RLQ TX Metric : 100
  Link Resources Metric : 100
  Link MTU Metric : 100
  Link Latency Metric : 250 microseconds
  Link CDR RX Metric : 100000000 bps
  Link CDR TX Metric : 100000000 bps
  Link MDR RX Metric : 100000000 bps
  Link MDR TX Metric : 100000000 bps

Scenario 2: DLEP session keeps timing out

In this scenario, the router is running in discovery mode.

Router#show dlep clients 

DLEP Clients for all interfaces:



DLEP Clients for Interface GigabitEthernet0/0/1
DLEP Server IP=14.0.0.3:55555 Sock=0


DLEP Client IP=14.0.0.2:859 TCP Socket fd=1
 Peer ID=13, Virtual template=2
 Description: DLEP_RadioSIM2
 Peer Timers (all values in milliseconds):
  Heartbeat=5000, Dead Interval=10000, Terminate ACK=20000
 Neighbor Timers (all values in seconds):
  Activity timeout=0, Neighbor Down ACK=10

 Supported Metrics:
  Link RLQ RX Metric : 100
  Link RLQ TX Metric : 100
  Link Resources Metric : 100
  Link MTU Metric : 100
  Link Latency Metric : 250 microseconds
  Link CDR RX Metric : 100000000 bps
  Link CDR TX Metric : 100000000 bps
  Link MDR RX Metric : 100000000 bps
  Link MDR TX Metric : 100000000 bps
Router#

*Feb 18 20:01:32.577: %SYS-5-CONFIG_P: Configured programmatically by process Manet Infra Background from console as console
*Feb 18 20:01:32.580: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up
*Feb 18 20:01:32.584: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up
*Feb 18 20:01:32.625: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi2, changed state to up
Router#
Router#
*Feb 18 20:01:44.864: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi2, changed state to down
*Feb 18 20:01:44.873: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down
*Feb 18 20:01:44.878: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down
*Feb 18 20:01:44.889: %SYS-5-CONFIG_P: Configured programmatically by process VTEMPLATE Background Mgr from console as console

debug dlep server
debug dlep timer detail
debug dlep client error
debug dlep client infra
debug dlep client packet detail
debug dlep client state

*Feb 18 20:14:59.553: dlepv27_encoder_signal_packet_start DLEP_SIGNAL_PEER_DISCOVERY(1)
*Feb 18 20:14:59.553: dlepv27_encoder_signal_packet_end tlv block size=0 packet length=8
*Feb 18 20:15:04.609: dlepv27_encoder_signal_packet_start DLEP_SIGNAL_PEER_DISCOVERY(1)
*Feb 18 20:15:04.609: dlepv27_encoder_signal_packet_end tlv block size=0 packet length=8
*Feb 18 20:15:04.611: dlepv27_decoder_signal_packet DLEP_SIGNAL_PEER_OFFER(2) data length 30
*Feb 18 20:15:04.611: dlepv27_decoder_peer_type_tlv DLEP_TLV_PEER_TYPE   flag - 0
dlepv27_decoder_parse_tlv_block last tlv 4; current block_len 11; next tlv 2 
IPv4 Addr 14.0.0.2dlepv27_decoder_ipv4_conn_point_tlv DLEP_TLV_IPv4_CONN_POINT 
dlepv27_decoder_parse_tlv_block last tlv 2; current block_len 0; 
*Feb 18 20:15:04.611: 
*Feb 18 20:15:04.611: dlepv27_decoder_packet rc(RC_DLEP_OK-0) state 0 signal 1 packet_len 38
*Feb 18 20:15:09.648: %DLEP_MSG-4-CONNECT_ERROR: TCP connect to Radio 14.0.0.2 failed via Gi0/0/1. Error code: Resource temporarily unavailable 

*Feb 18 20:15:09.648: dlepv27_encoder_msg_packet_start DLEP_MSG_SESSION_INITIALIZATION(1)
*Feb 18 20:15:09.648: dlepv27_encoder_msg_packet_end tlv block size=13 packet length=17
*Feb 18 20:15:09.649:   Adding Peer for address 14.0.0.2(859), peer_id=22
*Feb 18 20:15:09.649: MANET_Infra: insert s=FFFF771137A8, type=2 (client insert)
*Feb 18 20:15:09.650: MANET Infra: Insert=FFFF745209B0 successful (client insert)
*Feb 18 20:15:09.650: MANET_Infra: insert s=FFFF771137A8, type=1 (client insert)
*Feb 18 20:15:09.650: MANET Infra: Insert=FFFF64C3CEE8 successful (client insert)
*Feb 18 20:15:09.650:  -0 Allocated peer context at 0xFFFF771137A8
*Feb 18 20:15:09.650: dlepv27_decoder_msg_packet DLEP_MSG_SESSION_INITIALIZATION_ACK(2) data length 132 
dlepv27_decoder_status_tlv DLEP_TLV_STATUS  status_code=0 desc ()
dlepv27_decoder_parse_tlv_block last tlv 1; current block_len 127; next tlv 4 

*Feb 18 20:15:09.650: dlepv27_decoder_peer_type_tlv DLEP_TLV_PEER_TYPE   flag - 0
dlepv27_decoder_parse_tlv_block last tlv 4; current block_len 108; next tlv 5 
dlepv27_decoder_heartbeat_interval_tlv DLEP_TLV_HEARTBEAT_INTERVAL  heartbeat=60000 
dlepv27_decoder_parse_tlv_block last tlv 5; current block_len 100; next tlv 12 

*Feb 18 20:15:09.650: dlepv27_decoder_latency_data_rate_value DLEP_TLV_LINK_MDR_METRIC_RX  value=100000000 
dlepv27_decoder_parse_tlv_block last tlv 12; current block_len 88; next tlv 13 

*Feb 18 20:15:09.650: dlepv27_decoder_latency_data_rate_value DLEP_TLV_LINK_MDR_METRIC_TX  value=100000000 
dlepv27_decoder_parse_tlv_block last tlv 13; current block_len 76; next tlv 14 

*Feb 18 20:15:09.650: dlepv27_decoder_latency_data_rate_value DLEP_TLV_LINK_CDR_METRIC_RX  value=100000000 
dlepv27_decoder_parse_tlv_block last tlv 14; current block_len 64; next tlv 15 

*Feb 18 20:15:09.650: dlepv27_decoder_latency_data_rate_value DLEP_TLV_LINK_CDR_METRIC_TX  value=100000000 
dlepv27_decoder_parse_tlv_block last tlv 15; current block_len 52; next tlv 16 

*Feb 18 20:15:09.650: dlepv27_decoder_latency_data_rate_value DLEP_TLV_LINK_LATENCY_METRIC  value=250 
dlepv27_decoder_parse_tlv_block last tlv 16; current block_len 40; next tlv 18 
dlepv27_decoder_rlq_resource_value DLEP_TLV_LINK_RLQ_METRIC_RX  value=100 
dlepv27_decoder_parse_tlv_block last tlv 18; current block_len 35; next tlv 19 
dlepv27_decoder_rlq_resource_value DLEP_TLV_LINK_RLQ_METRIC_TX  value=100 
dlepv27_decoder_parse_tlv_block last tlv 19; current block_len 30; next tlv 17 
dlepv27_decoder_rlq_resource_value DLEP_TLV_LINK_RESOURCES  value=100 
dlepv27_decoder_parse_tlv_block last tlv 17; current block_len 25; next tlv 20 
dlepv27_decoder_mtu_tlv DLEP_TLV_LINK_MTU  mtu=100 
dlepv27_decoder_parse_tlv_block last tlv 20; current block_len 19; next tlv 8 
IPv4 Addr 14.0.0.2dlepv27_decoder_ipv4_address_tlv DLEP_TLV_IPV4_ADDRESS  operation=1 
dlepv27_decoder_parse_tlv_block last tlv 8; current block_len 10; next tlv 10 
IPv4 Subnet Addr 255.255.255.0dlepv27_decoder_ipv4_address_subnet_tlv DLEP_TLV_IPV4_ATTACHED_SUBNET  operation=1 mask=24 
dlepv27_decoder_parse_tlv_block last tlv 10; current block_len 0; 
*Feb 18 20:15:09.651: 
*Feb 18 20:15:09.651: dlepv27_decoder_packet rc(RC_DLEP_OK-0) state 1 signal 0 packet_len 136
Router#

*Feb 18 20:15:14.569: dlepv27_decoder_msg_packet DLEP_MSG_PEER_HEARTBEAT(16) data length 0 

*Feb 18 20:15:14.569:  -curr_state Dlep In-Session State normalized_event=Dlep Peer Heartbeat Event  p2peer=0xFFFF771137A8  peer_id=22  p2neighbor=0x0
*Feb 18 20:15:14.569: dlepv27_decoder_packet rc(RC_DLEP_OK-0) state 2 signal 0 packet_len 4
Router#
*Feb 18 20:15:19.569: dlepv27_decoder_msg_packet DLEP_MSG_PEER_HEARTBEAT(16) data length 0 

*Feb 18 20:15:19.569:  -curr_state Dlep In-Session State normalized_event=Dlep Peer Heartbeat Event  p2peer=0xFFFF771137A8  peer_id=22  p2neighbor=0x0
*Feb 18 20:15:19.569: dlepv27_decoder_packet rc(RC_DLEP_OK-0) state 2 signal 0 packet_len 4
Router#

*Feb 18 20:15:24.569: dlepv27_decoder_msg_packet DLEP_MSG_SESSION_TERM(5) data length 5 
dlepv27_decoder_status_tlv DLEP_TLV_STATUS  status_code=0 desc ()
dlepv27_decoder_parse_tlv_block last tlv 1; current block_len 0; 
*Feb 18 20:15:24.569: 
*Feb 18 20:15:24.569:  -curr_state Dlep In-Session State normalized_event=Dlep Peer Term Event  p2peer=0xFFFF771137A8  peer_id=22  p2neighbor=0x0
*Feb 18 20:15:24.569:  -curr_state Dlep Terminating State normalized_event=Dlep Peer Term ACK Event  p2peer=0xFFFF771137A8  peer_id=22  p2neighbor=0x0
*Feb 18 20:15:24.569: dlepv27_encoder_msg_packet_start DLEP_MSG_SESSION_TERM_ACK(6)
*Feb 18 20:15:24.569: dlepv27_encoder_msg_packet_end tlv block size=12 packet length=16
*Feb 18 20:15:24.570:  -curr_state Dlep Session Reset State normalized_event=Dlep Peer sessoin reset Event  p2peer=0xFFFF771137A8  peer_id=22  p2neighbor=0x0
*Feb 18 20:15:24.570:  -0 Restart all peers on IDB GigabitEthernet0/0/1
*Feb 18 20:15:24.570: dlepv27_decoder_packet rc(RC_DLEP_OK-0) state 2 signal 0 packet_len 9

Router#show dlep config 
DLEP Configuration for GigabitEthernet0/0/1

DLEP Peer Description - 
DLEP Version = RFC 8175
DLEP Server IP=14.0.0.3:55555
DLEPv27 TCP Port = 55556
 Virtual template=2
 Timers (all values are in seconds):
 Missed heartbeat threshold=2, Peer Terminate ACK timeout=10
 Dlepv27 Applicable configs(in seconds):
 Heartbeat interval=5, Discovery interval =5, Session Ack timeout=10
 Neighbor activity timeout=0, Neighbor Down ACK timeout=10

Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int g0/0/1
Router(config-if)#no ip dlep
Router(config-if)#no ip dlep vtemplate
Router(config-if)#no ip dlep vtemplate 2
Router(config-if)#ip dlep set peer-heartbeat-interval 60
Router(config-if)# ip dlep vtemplate 2
Router(config-if)#^Z

Router#show dlep clients

DLEP Clients for all interfaces:


DLEP Clients for Interface GigabitEthernet0/0/1
DLEP Server IP=14.0.0.3:55555 Sock=0


DLEP Client IP=14.0.0.2:859 TCP Socket fd=1
 Peer ID=51, Virtual template=2
 Description: DLEP_RadioSIM2
 Peer Timers (all values in milliseconds):
  Heartbeat=60000, Dead Interval=120000, Terminate ACK=240000
 Neighbor Timers (all values in seconds):
  Activity timeout=0, Neighbor Down ACK=10

 Supported Metrics:
  Link RLQ RX Metric : 100
  Link RLQ TX Metric : 100
  Link Resources Metric : 100
  Link MTU Metric : 100
  Link Latency Metric : 250 microseconds
  Link CDR RX Metric : 100000000 bps
  Link CDR TX Metric : 100000000 bps
  Link MDR RX Metric : 100000000 bps
  Link MDR TX Metric : 100000000 bps
Router#
*Feb 18 20:38:03.708: %SYS-5-CONFIG_P: Configured programmatically by process Manet Infra Background from console as console
*Feb 18 20:38:03.712: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up
*Feb 18 20:38:03.716: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up
*Feb 18 20:38:03.722: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi2, changed state to up

DLEP

debug dlep server detail
debug dlep timer detail
debug dlep neighbor error
debug dlep neighbor infrastructure detail
debug dlep neighbor infrastructure error
debug dlep neighbor metrics
debug dlep neighbor state
debug dlep neighbor all
debug dlep client error
debug dlep client infrastructure
debug dlep client packet dump
debug dlep client packet detail
debug dlep client state

VMI

debug vmi bma
debug vmi packet
debug vmi error
debug vmi multicast 
debug vmi neighbor
debug vmi registries 

Virtual Template

debug vtemplate cloning
debug vtemplate error
debug vtemplate  event
debug vtemplate subinterface

PPPOE

debug pppoe errors
debug pppoe events
debug pppoe packets
debug pppoe data

SSS

debug sss error
debug sss event