Use the VPN-Interface-PPP-Ethernet template for vEdge Cloud and vEdge router devices.
Point-to-Point Protocol (PPP) is a data link protocol used to establish a direct connection between two nodes. PPP properties are associated with a PPPoE-enabled interface on vEdge routers to connect multiple users over an Ethernet link.
To configure PPPoE on vEdge routers using vManage templates:
- Create a VPN-Interface-PPP-Ethernet feature template to configure a PPPoE-enabled interface as described in this article.
- Create a VPN-Interface-PPP feature template to configure PPP parameters for the PPP virtual interface. See the VPN-Interface-PPP help topic
- Optionally, create a VPN feature template to modify the default configuration of VPN 0. See the VPN help topic.
Some versions of the VPN-Interface-PPP-Ethernet feature template include sections for VRRP and ARP. You cannot configure VRRP or ARP on PPPoE-enabled interfaces, so do not use these sections of the template.
Navigate to the Template Screen
- In vManage NMS, select the Configuration ► Templates screen.
- In the Device tab, click Create Template.
- From the Create Template drop-down, select From Feature Template.
- From the Device Model drop-down, select the type of device for which you are creating the template.
- Click the Transport & Management VPN tab located directly beneath the Description field, or scroll to the Transport & Management VPN section.
- Under Additional VPN 0 Templates, located to the right of the screen, click VPN Interface PPP.
- From the VPN Interface PPP Ethernet drop-down, click Create Template. The VPN-Interface-PPP-Ethernet template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining VPN Interface PPP parameters.
When you first open a feature template, for each parameter that has a default value, the scope is set to Default (indicated by a check mark), and the default setting or value is shown. To change the default or to enter a value, click the scope drop-down to the left of the parameter field and select one of the following:
Device Specific (indicated by a host icon)
Use a device-specific value for the parameter. For device-specific parameters, you cannot enter a value in the feature template. You enter the value when you attach a Viptela device to a device template.
When you click Device Specific, the Enter Key box opens. This box displays a key, which is a unique string that identifies the parameter in a CSV file that you create. This file is an Excel spreadsheet that contains one column for each key. The header row contains the key names (one key per column), and each row after that corresponds to a device and defines the values of the keys for that device. You upload the CSV file when you attach a Viptela device to a device template. For more information, see Create a Template Variables Spreadsheet.
To change the default key, type a new string and move the cursor out of the Enter Key box.
Examples of device-specific parameters are system IP address, hostname, GPS location, and site ID.
Global (indicated by a globe icon)
Enter a value for the parameter, and apply that value to all devices.
Examples of parameters that you might apply globally to a group of devices are DNS server, syslog server, and interface MTUs.
Minimum PPPoE-Enabled Interface Configuration
The following parameters are required (unless otherwise indicated) to create a PPPoE-enabled interface on a vEdge router:
|1.||Template Name||Enter a name for the template. It can be up to 128 characters and can contain only alphanumeric characters.|
|2.||Description (Template)||Enter a description for the template. It can be up to 2048 characters and can contain only alphanumeric characters.|
|3.||Shutdown||Click No to enable the PPPoE-enabled interface.|
|4.||Interface Name||Enter the name of the physical interface in VPN 0 to associate with the PPP interface.|
|5.||Description (optional)||Enter a description of the PPPoE-enabled interface.|
Select Dynamic to set the interface as a DHCP client, to allow the interface to receive its IP address from a DHCP server. If you select Dynamic, you can set the DHCP distance to specify the administrative distance of routes learned from a DHCP server. The default DHCP distance is 1.
|7.||IPv4 Address||Enter the IPv4 address of the interface if the interface is not receiving its IP address from a DHCP server.|
|8.||IPv6 Configuration||Configure an IPv6 address for an interface in VPN 0. You can select Dynamic to set the interface as a DHCP client, to allow the interface to receive its IP address from a DHCP server. If you select Dynamic, you can set the DHCP distance to specify the administrative distance of routes learned from a DHCP server. The default administrative distance is 1.|
|9.||IPv6 Address||Enter the IPv6 address of the interface if the interface is not receiving its IP address from a DHCP server.|
|10.||DHCP helper (optional)||
Enter up to four IP addresses for DHCP servers in the network, separated by commas, to have the interface be a DHCP helper. A DHCP helper interface forwards BOOTP (Broadcast) DHCP requests that it receives from the specified DHCP servers.
|11.||Bandwidth Upstream (optional)||For transmitted traffic, set the bandwidth above which to generate notifications.
Range: 1 through (232 / 2) – 1 kbps
|12.||Bandwidth Downstream (optional)||For received traffic, set the bandwidth above which to generate notifications.
Range: 1 through (232 / 2) – 1 kbps
|13.||Save||Click Save to save the feature template.|
vpn 0 interface pppnumber bandwidth-downstream kbps bandwidth-upstream kbps description text dhcp-helper ip-address (ip address ipv4-prefix/length | ip-dhcp-client [dhcp-distance number]) (ipv6 address ipv6-prefix/length | ipv6 dhcp-client [dhcp-distance number] [ dhcp-rapid-commit] [no] shutdown
Apply Access Lists
To configure a shaping rate to a PPPoE-enabled interface and to apply a QoS map, a rewrite rule, access lists, and policers to the interface, select the ACL/QOS tab:
|Shaping Rate||Configure the aggregate traffic transmission rate on the interface to be less than line rate, in kilobits per second (kbps).|
|QoS Map||Specify the name of the QoS map to apply to packets being transmitted out the interface.|
|Rewrite Rule||Click On, and specify the name of the rewrite rule to apply on the interface.|
Click On, and specify the name of the access list to apply to packets being received on the interface.
|Egress ACL||Click On, and specify the name of the access list to apply to packets being transmitted on the interface.|
|Ingress Policer||Click O,n and specify the name of the policer to apply to packets being received on the interface.|
|Egress Policer||Click On, and specify the name of the policer to apply to packets being transmitted on the interface.|
vpn 0 interface pppnumber access-list acl-list (in | out) policer policer-name (in |out) qos-map name rewrite-rule name shaping-rate name
Configure Other Interface Properties
To configure other interface properties, select the Advanced tab:
Choose full or half to specify whether the interface runs in full-duplex or half-duplex mode.
|MAC Address||Specify a MAC address to associate with the interface, in colon-separated hexadecimal notation.|
|IP MTU||Specify the maximum MTU size of packets on the interface.
Range: 576 through 1804
Default: 1500 bytes
|PMTU Discovery||Click On to enable path MTU discovery on the interface. PMTU determines the largest MTU size that the interface supports so that packet fragmentation does not occur.|
Select a setting for bidirectional flow control, which is a mechanism for temporarily stopping the transmission of data on the interface.
|TCP MSS||Specify the maximum segment size (MSS) of TPC SYN packets passing through the vEdge router. By default, the MSS is dynamically adjusted based on the interface or tunnel MTU such that TCP SYN packets are never fragmented.
Range: 552 to 1460 bytes
Specify the speed of the interface, for use when the remote end of the connection does not support autonegotiation.
|Static Ingress QoS||
Specify a queue number to use for incoming traffic.
Specify how long it takes for a dynamically learned ARP entry to time out.
|Autonegotiation||Click Off to turn off autonegotiation. By default, an interface runs in autonegotiation mode.|
|TLOC Extension||Enter the name of a physical interface on the same router that connects to the WAN transport. This configuration then binds this service-side interface to the WAN transport. A second vEdge router at the same site that itself has no direct connection to the WAN (generally because the site has only a single WAN connection) and that connects to this service-side interface is then provided with a connection to the WAN.|
|Power over Ethernet (on vEdge 100m and vEdge 100wm routers)||Click On to enable PoE on the interface.|
vpn 0 interface pppnumber arp-timeout seconds [no] autonegotiate duplex (full | half) flow-control control mac-address mac-address mtu bytes pmtu pppoe-client ppp-interface pppnumber speed speed static-ingress-qos number tcp-mss-adjust bytes tloc-extension interface-name
Complete CLI Configuration Commands for PPPoE-Enabled Interfaces
The following shows all the commands available for PPPoE-enabled interfaces. This is a subset of the commands available for general interfaces. Configure NAT, PMTU, and tunnel interfaces on the PPP virtual interface rather than on the PPPoE-enabled interface.
vpn vpn-id interface interface-name access-list acl-list arp ip ip-address mac mac-address arp-timeout seconds autonegotiate clear-dont-fragment description text duplex (full | half) flow-control (bidirectional | egress | ingress) (ip address prefix/length | ip dhcp-client [dhcp-distance number]) keepalive seconds retries mac-address mac-address mtu bytes policer policer-name pppoe-client ppp-interface name qos-map name rewrite-rule name shaping-rate name shutdown speed speed static-ingress-qos number tcp-mss-adjust bytes tloc-extension interface-name
Introduced in vManage NMS Release 15.3.
In Release 16.3, add support for IPv6.