Page 75 of 130
2.7.1 Loop Bonding
It is the logical bond between two VDSL2 signals or VDSL ports.
•
Based upon the ITU-T Recommendation G.998.2 Ethernet-based multi-pair bonding.
•
Not restricted to VDSL2 technology.
•
Some companies only bonds to VDSL2 ports.
•
VDSL2 Bonding = loop bonding.
Regardless of where the DSLAM is located, the network requirements are the same.
The primary network requirements for loop bonded installs are:
•
Requires two VDSL2 locations within a single DSLAM at the C.O.
•
Connected via two copper pairs to the customer's residence.
•
VDSL2 signals combined into a modem with a bonding capacity of two telephone signals.
•
Actiontec Gateway V2000H.
•
Bandwidth management is controlled by the modem
•
Both loops must meet minimum requirements.
•
Works even if line performance is not identical.
•
Important to groom both lines for optimal performance.
•
Certain line impairments cannot be repaired equally.
Figure 83: CO to Customer premises
Examples:
ingress, cross talk, impulse noise
The primary network requirements for loop:
•
Two VDSL connections be on the same card in a DSLAM.
•
If possible, the two pairs of cables should be within the same 25-pair binder.
•
The QOS will always be applied to the VDSL master port, which should always be connected to the
first/primary line.
The distinction is there to tell you which of the two has the bridge port assigned to it (and thus can’t be
removed). Yes the master port technically has the bridge port (and thus at the ERX the service profile)
attached to it, but at the DSLAM everything references the bonded
group
, not either port, when it comes to
the overall service. It just so happens the group is named after the primary port. Therefore, QoS is applied