VDSL2 Interfaces on NFX350 Devices
VDSL Interface Overview
Very-high-bit-rate digital subscriber line (VDSL) technology is part of the xDSL family of modem technologies that provide faster data transmission over a single flat untwisted or twisted pair of copper wires. The VDSL lines connect service provider networks and customer sites to provide high bandwidth applications (triple-play services) such as high-speed Internet access, telephone services like VoIP, high-definition TV (HDTV), and interactive gaming services over a single connection.
VDSL2 is an enhancement to G.993.1 (VDSL) and permits the transmission of asymmetric (half-duplex) and symmetric (full-duplex) aggregate data rates up to 100 Mbps on short copper loops using a bandwidth up to 17 MHz. The VDSL2 technology is based on the ITU-T G.993.2 (VDSL2) standard, which is the International Telecommunication Union standard describing a data transmission method for VDSL2 transceivers.
The VDSL2 uses discrete multitone (DMT) modulation. DMT is a method of separating a digital subscriber line signal so that the usable frequency range is separated into 256 frequency bands (or channels) of 4.3125 KHz each. The DMT uses the Fast Fourier Transform (FFT) algorithm for demodulation or modulation for increased speed.
VDSL2 interface supports Packet Transfer Mode (PTM). The PTM mode transports packets (IP, PPP, Ethernet, MPLS, and so on) over DSL links as an alternative to using Asynchronous Transfer Mode (ATM). PTM is based on the Ethernet in the First Mile (EFM) IEEE802.3ah standard.
VDSL2 provides backward compatibility with ADSL2 and ADSL2+ because this technology is based on both the VDSL1-DMT and ADSL2/ADSL2+ recommendations.
VDSL2 Vectoring Overview
Vectoring is a transmission method that employs the coordination of line signals that reduce crosstalk levels and improve performance. It is based on the concept of noise cancellation, like noise-cancelling headphones. The ITU-T G.993.5 standard, "Self-FEXT Cancellation (Vectoring) for Use with VDSL2 Transceivers,” also known as G.vector, describes vectoring for VDSL2.
The scope of Recommendation ITU-T G.993.5 is specifically limited to the self-FEXT (far-end crosstalk) cancellation in the downstream and upstream directions. The FEXT generated by a group of near-end transceivers and interfering with the far-end transceivers of that same group is canceled. This cancellation takes place between VDSL2 transceivers, not necessarily of the same profile.
VDSL2 Network Deployment Topology
In standard telephone cables of copper wires, voice signals use only a fraction of the available bandwidth. Like any other DSL technology, the VDSL2 technology utilizes the remaining capacity to carry the data and multimedia on the wire without interrupting the line's ability to carry voice signals.
This example depicts the typical VDSL2 network topology deployed using NFX device.
A VDSL2 link between network devices is set up as follows:
Connect an end-user device such as a LAN, hub, or PC through an Ethernet interface to the customer premises equipment (CPE) (for example, an NFX device).
Connect the CPE to a DSLAM.
The VDSL2 interface uses either Gigabit Ethernet or fiber as second mile to connect to the Broadband Remote Access Server (B-RAS) as shown in Figure 1.
The ADSL interface uses either Gigabit Ethernet (in case of IP DSLAM] as the “second mile” to connect to the B-RAS or OC3/DS3 ATM as the second mile to connect the B-RAS as shown in Figure 2.
Note:The VDSL2 technology is backward compatible with ADSL2 and ADSL2+. VDSL2 provides an ADSL2 and ADSL2+ interface in an ATM DSLAM topology and provides a VDSL2 interface in an IP or VDSL DSLAM topology.
The DSLAM accepts connections from many customers and aggregates them to a single, high-capacity connection to the Internet.
Figure 1 shows a typical VDSL2 network topology.

Figure 2 shows a backward-compatible ADSL topology using ATM DSLAM.

VDSL2 Interface Support on NFX350 Devices
The VDSL2 interface is supported on the NFX Series devices listed in Table 1. (Platform support depends on the Junos OS release in your installation.)
Features |
POTS |
---|---|
Devices |
CPE-SFP-VDSL2 |
Supported annex operating modes |
Annex A and Annex B* |
Supported Bandplans |
Annex A 998 Annex B 997 and 998 |
Supported standards |
ITU-T G.993.2 and ITU-T G.993.5 (VDSL2) |
Used in |
North American network implementations |
ADSL backward compatibility |
G 992.3 (ADSL2) G 992.5 (ADSL2+) |
Only one CPE-SFP-VDSL2 device is supported at a time.
VDSL2 Interface Compatibility with ADSL Interfaces
VDSL2 interfaces on NFX Series devices are backward compatible with most ADSL2 and ADSL2+ interface standards. The VDSL2 interface uses Ethernet in the First Mile (EFM) mode or Packet Transfer Mode (PTM) and uses the named interface ge-0/0/10 and ge-0/0/11.
The VDSL2 interface has backward compatibility with ADSL2 and ADSL2+.
It requires around 60 seconds to switch from VDSL2 to ADSL2 and ADSL2+ or from ADSL2 and ADSL2+ to VDSL2 operating modes.
VDSL2 Interfaces Supported Profiles
A profile is a table that contains a list of pre-configured VDSL2 settings. Table 2 lists the different profiles supported on the VDSL2 interfaces and their properties.
Profiles |
Data Rate |
---|---|
8a |
50 |
8b |
50 |
8c |
50 |
8d |
50 |
12a |
68 |
12b |
68 |
17a |
100 |
Auto |
Negotiated (based on operating mode) |
Example: Configuring VDSL SFP Interface on NFX350 Devices
Requirements
This example uses the following hardware and software components:
NFX350 device running Junos OS Release 20.2R1.
Overview
In this example, you are configuring VDSL SFP interface on an NFX350 device with the following configurations:
Physical interface - ge-0/0/11
VDSL SFP options - profile auto and carrier auto
To configure VDSL SFP interface on NFX250 devices, you must configure JDM, vSRX Virtual Firewall, and vJunos0.
Ensure that connectivity to the host is not lost during the configuration process.
Configuration
Procedure
Step-by-Step Procedure
To configure VDSL SFP interfaces on NFX350 devices:
Connect to the host.
user@host> configure [edit] user@host#
Configure virtual interfaces:
user@host# set vmhost virtualization-options interfaces ge-1/0/3 user@host# set vmhost virtualization-options interfaces ge-1/0/4 user@host# commit
Create VLANs using VLAN IDs:
user@host# set vlans vlan100 vlan-id 100 user@host# set vlans vlan101 vlan-id 101 user@host# set vlans vlan200 vlan-id 200 user@host# set vlans vlan50 vlan-id 50
Configure interfaces:
user@host# set interfaces sxe-0/0/0 unit 0 family ethernet-switching interface-mode trunk user@host# set interfaces sxe-0/0/0 unit 0 family ethernet-switching vlan members vlan50 user@host# set interfaces sxe-0/0/0 unit 0 family ethernet-switching vlan members vlan100 user@host# set interfaces sxe-0/0/0 unit 0 family ethernet-switching vlan members vlan101 user@host# set interfaces sxe-0/0/0 unit 0 family ethernet-switching vlan members vlan200 user@host# set interfaces ge-0/0/11 native-vlan-id 50 user@host# set interfaces ge-0/0/11 dsl-sfp-options vdsl-options profile auto user@host# set interfaces ge-0/0/11 dsl-sfp-options vdsl-options carrier auto user@host# set interfaces ge-0/0/11 unit 0 family ethernet-switching interface-mode trunk user@host# set interfaces ge-0/0/11 unit 0 family ethernet-switching vlan members vlan50 user@host# set interfaces ge-0/0/11 unit 0 family ethernet-switching vlan members vlan101 user@host# set interfaces ge-1/0/3 vlan-tagging user@host# set interfaces ge-1/0/3 unit 0 vlan-id 50 user@host# set interfaces ge-1/0/3 unit 0 family inet address 130.1.1.11/24 user@host# set interfaces ge-1/0/3 unit 0 family inet6 address 2001::1/64
Commit the configuration.
user@host# commit and-quit user@host> exit