Cisco Vdsl2 Ipoe Example

Cisco vdsl2 ipoe example

Use the IPoE template for Cisco IOS XE routers.

You configure IPoE on routers with DSL interfaces, to provide support for service provider digital subscriber line (DSL) functionality.

To configure DSL interfaces on Cisco routers using vManage templates:

  1. Create a VPN Interface DSL IPoE feature template to configure IP-over-Ethernet interface parameters, as described in this article.
  2. Create a VPN feature template to configure VPN parameters.

    Introduction

    See the VPN help topic.

Navigate to the Template Screen and Name the Template

  1. In vManage NMS, select the Configuration ► Templates screen.
  2. In the Device tab, click Create Template.
  3. From the Create Template drop-down, select "From Feature Template."
  4. From the Device Model drop-down, select the type of device for which you are creating the template.
  5. Click the Transport & Management VPN tab located directly beneath the Description field, or scroll to the Transport & Management VPN section.
  6. Under Additional VPN 0 Templates, located to the right of the screen, click VPN Interface DSL IPoE.
  7. From the VPN Interface DSL IPoE drop-down, click Create Template.

    The VPN Interface DSL IPoE template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining IPoE Interface parameters.

  8. In the Template Name field, enter a name for the template.

    The name can be up to 128 characters and can contain only alphanumeric characters.

  9. In the Template Description field, enter a description of the template.

    Cisco vdsl2 ipoe example

    The description can be up to 2048 characters and can contain only alphanumeric characters.

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:

Parameter Scope

Scope Description

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.

Configure IPoE Functionality

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.

Cisco vdsl2 ipoe example

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.

Contact Cisco

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.

Configure IPoE Functionality

To configure basic IPoE functionality, select the Basic Configuration tab and configure the following parameters.

Required parameters are indicated with an asterisk.

Parameter NameDescription
Shutdown*Click No to enable the VDSL controller interface.
Controller VDSL Slot*Enter the slot number of the controller VDSL interface, in the format slot/subslot/port (for example, 0/2/0).
Mode*

Select the operating mode of the VDSL controller from the drop-down:

  • Auto—Default mode.
  • ADSL1—Use ITU G.992.1 Annex A full-rate mode, which provides a downstream rate of 1.3 Mbps and an upstream rate of 1.8 Mbps.
  • ADSL2—Use ITU G.992.3 Annex A, Annex L, and Annex M, which provides a downstream rate of 12 Mbps and an upstream rate of 1.3 Mbps.
  • ADSL2+— Use ITU G.992.5 Annex A and Annex M, which provides a downstream rate of 24 Mbps and an upstream rate of 3.3 Mbps.
  • ANSI—Operating in ADSL2/2+ mode, as defined in ITU G.991.1, G.992.3, and G992.5, Annex A and Annex M, and in VDSL2 mode, as defined in ITU-T G993.2.
  • VDSL2—Operate in VDSL2 mode, as defined in ITU-T G.993.2, which uses frequencies of up to 30 MHz to provide a downstream rate of 200 Mbps and an upstream rate of 100 Mbps..
VDSL Modem ConfigurationEnter a command to send to the DSL modem in the NIM module.

Cisco vdsl2 ipoe example

If the command is valid, it is executed and the results are returned to the vManage NMS. If the command is not valid, it is not executed.

SRA

Click Yes to enable seamless rate adaptation on the interface. SRA adjusts the line rate based on current line conditions.

To save the feature template, click Save.

Configure the Ethernet Interface

To configure an Ethernet interface on the VDSL controller, select the Ethernet tab and configure the following parameters.

You must configure all parameters.

Parameter NameDescription
Ethernet Interface NameEnter a name for the Ethernet interface, in the format subslot/port (for example 2/0).

Cisco vdsl2 ipoe example

You do not need to enter the slot number, because it must always be 0.

VLAN IDEnter the VLAN identifier of the Ethernet interface.
DescriptionEnter a description for the interface.
Dynamic/StaticAssign a dynamic or static IPv4 address to the Ethernet interface.
IPv4 Address

Enter the static IPv4 address of the Ethernet interface.

DHCP Helper

Enter up to eight 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.

To save the feature template, click Save.

​Create a Tunnel Interface

On IOS XE routers, you can configure up to four tunnel interfaces.

Cisco RV134W VDSL2 Wireless-AC VPN Router

This means that each router can have up to four TLOCs.

For the control plane to establish itself so that the overlay network can function, you must configure WAN transport interfaces in VPN 0.

To configure a tunnel interface for the multilink interface, select the Tunnel Interface tab and configure the following parameters:

Parameter NameDescription
Tunnel InterfaceClick On to create a tunnel interface.
ColorSelect a color for the TLOC.
Control ConnectionIf the router has multiple TLOCs, click No to have the tunnel not establish a TLOC.

The default is On, which establishes a control connection for the TLOC.

Maximum Control Connections

Specify the maximum number of vSmart controllers that the WAN tunnel interface can connect to.

To have the tunnel establish no control connections, set the number to 0.

Range: 0 through 8
Default: 2

vBond As STUN ServerClick On to enable Session Traversal Utilities for NAT (STUN) to allow the tunnel interface to discover its public IP address and port number when the router is located behind a NAT.
Exclude Controller Group ListSet the vSmart controllers that the tunnel interface is not allowed to connect to.
Range: 0 through 100
vManage Connection PreferenceSet the preference for using a tunnel interface to exchange control traffic with the vManage NMS.
Range: 0 through 8
Default: 5
Port HopClick On to enable port hopping, or click Off to disable it.

When a router is behind a NAT, port hopping rotates through a pool of preselected OMP port numbers (called base ports) to establish DTLS connections with other routers when a connection attempt is unsuccessful.

Cisco ASA + PPPoE using a BT Infinity VDSL connection

The default base ports are 12346, 12366, 12386, 12406, and 12426. To modify the base ports, set a port offset value.
Default: Enabled

Low-Bandwidth LinkSelect to characterize the tunnel interface as a low-bandwidth link.
Allow ServiceSelect On or Off for each service to allow or disallow the service on the interface.

To configure additional tunnel interface parameters, click Advanced Options and configure the following parameters:

Parameter NameDescription
GRE

Use GRE encapsulation on the tunnel interface.

By default, GRE is disabled.

If you select both IPsec and GRE encapsulations, two TLOCs are created for the tunnel interface that have the same IP addresses and colors, but that differ by their encapsulation.

IPsec

Use IPsec encapsulation on the tunnel interface.

Best online trading platform for occasional tradesuk

By default, IPsec is enabled.

If you select both IPsec and GRE encapsulations, two TLOCs are created for the tunnel interface that have the same IP addresses and colors, but that differ by their encapsulation.

IPsec Preference

Specify a preference value for directing traffic to the tunnel.

A higher value is preferred over a lower value.

Range: 0 through 4294967295
Default: 0

IPsec Weight

Enter a weight to use to balance traffic across multiple TLOCs.

Your Answer

A higher value sends more traffic to the tunnel.

Range: 1 through 255
Default: 1

Carrier

Select the carrier name or private network identifier to associate with the tunnel.

Values: carrier1, carrier2, carrier3, carrier4, carrier5, carrier6, carrier7, carrier8, default
Default: default

Bind Loopback TunnelEnter the name of a physical interface to bind to a loopback interface.
Last-Resort CircuitSelect to use the tunnel interface as the circuit of last resort.
NAT Refresh IntervalEnter the interval between NAT refresh packets sent on a DTLS or TLS WAN transport connection.
Range: 1 through 60 seconds
Default: 5 seconds
Hello IntervalEnter the interval between Hello packets sent on a DTLS or TLS WAN transport connection.
Range: 100 through 10000 milliseconds
Default: 1000 milliseconds (1 second)
Hello Tolerance

Enter the time to wait for a Hello packet on a DTLS or TLS WAN transport connection before declaring that transport tunnel to be down.

Range: 12 through 60 seconds
Default: 12 seconds

Configure the Interface as a NAT Device

To configure an interface to act as a NAT device for applications such as port forwarding, select the NAT tab, click On and configure the following parameters:

Parameter NameDescription
NATClick On to have the interface act as a NAT device.
Refresh Mode

Select how NAT mappings are refreshed, either outbound or bidirectional (outbound and inbound).
Default: Outbound

UDP Timeout

Specify when NAT translations over UDP sessions time out.
Range: 1 through 65536 minutes
Default: 1 minutes

TCP Timeout

Specify when NAT translations over TCP sessions time out.
Range: 1 through 65536 minutes
Default: 60 minutes (1 hour)

Block ICMP

Select On to block inbound ICMP error messages.

By default, a router acting as a NAT device receives these error messages.
Default: Off

Respond to PingSelect On to have the router respond to ping requests to the NAT interface's IP address that are received from the public side of the connection.

To create a port forwarding rule, click Add New Port Forwarding Rule and configure the following parameters.

Indicator stochastic oscillator divergence forex factory

You can define up to 128 port-forwarding rules to allow requests from an external network to reach devices on the internal network.

Parameter NameDescription
Port Start Range

Enter a port number to define the port or first port in the range of interest.
Range: 0 through 65535

Port End RangeEnter the same port number to apply port forwarding to a single port, or enter a larger number to apply it to a range of ports.
Range: 0 through 65535
ProtocolSelect the protocol to which to apply the port-forwarding rule, either TCP or UDP.

To match the same ports for both TCP and UDP traffic, configure two rules.

VPNSpecify the private VPN in which the internal server resides. This VPN is one of the VPN identifiers in the overlay network.
Range: 0 through 65530
Private IPSpecify the IP address of the internal server to which to direct traffic that matches the port-forwarding rule.

To save a port forwarding rule, click Add.

To save the feature template, click Save.

Apply Access Lists

To apply a rewrite rule, access lists, and policers to a router interface, select the ACL tab and configure the following parameters:

Parameter NameDescription
Shaping rate

Configure the aggreate traffic transmission rate on the interface to be less than line rate, in kilobits per second (kbps).

QoS mapSpecify the name of the QoS map to apply to packets being transmitted out the interface.
Rewrite RuleClick On, and specify the name of the rewrite rule to apply on the interface.
Ingress ACL – IPv4

Click On, and specify the name of the access list to apply to IPv4 packets being received on the interface.

Egress ACL – IPv4Click On, and specify the name of the access list to apply to IPv4 packets being transmitted on the interface.
Ingress ACL – IPv6

Click On, and specify the name of the access list to apply to IPv6 packets being received on the interface.

Egress ACL – IPv6Click On, and specify the name of the access list to apply to IPv6 packets being transmitted on the interface.
Ingress PolicerClick On, and specify the name of the policer to apply to packets being received on the interface.
Egress PolicerClick On, and specify the name of the policer to apply to packets being transmitted on the interface.

To save the feature template, click Save.

Configure Other Interface Properties​

To configure other interface properties, select the Advanced tab and configure the following properties:

Parameter NameDescription
Bandwidth UpstreamFor transmitted traffic, set the bandwidth above which to generate notifications.
Range: 1 through (232 / 2) – 1 kbps
Bandwidth DownstreamFor received traffic, set the bandwidth above which to generate notifications.
Range: 1 through (232 / 2) – 1 kbps
IP MTUSpecify the maximum MTU size of packets on the interface.
Range: 576 through 1804
Default: 1500 bytes
TCP MSSSpecify the maximum segment size (MSS) of TPC SYN packets passing through the router.

Navigate to the Template Screen and Name the Template

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
Default: None

TLOC Extension

Enter the name of the physical interface on the same router that connects to the WAN transport circuit. This configuration then binds this service-side interface to the WAN transport.

A second 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.

TrackerEnter the name of a tracker to track the status of transport interfaces that connect to the internet.
IP Directed-BroadcastEnables translation of a directed broadcast to physical broadcasts.

An IP directed broadcast is an IP packet whose destination address is a valid broadcast address for some IP subnet but which originates from a node that is not itself part of that destination subnet.

To save the feature template, click Save.

Release Information

Introduced in vManage NMS in Release 18.4.1.