Showing posts sorted by relevance for query bonding. Sort by date Show all posts
Showing posts sorted by relevance for query bonding. Sort by date Show all posts

Mar 12, 2013

ADSL Line Bonding - Bonded Broadband

Bonded ADSL is where multiple broadband lines are joined together to form a single larger pipe.

Bonding is not the same as load balancing, which would require a complicated algorithm to keep the lines in balance. A bonded connection operates as one pipe and the data going down that pipe is automatically shared proportionately over the individual ADSL lines.


Mature technology

The industry standard way of achieving this is through the use of MultiLink PPP (ML-PPP). This is a tried and tested technology and has been used by Internet Service Providers for many years. It is the very same technology used to provide ISDN internet connections larger than 64k.


Whereas with ISDN multiple 64k channels could be combined to make a larger (128k or 256k) connection, with DSL we are combining multiple high-speed ADSL or SDSL lines.

Special requirements for bonding ADSL lines


ADSL lines have certain properties that pose particular challenges to when it comes to bonding. Unlike ISDN lines, ADSL lines do not have guaranteed or even predictable levels of bandwidth. Different ADSL lines at the same site can also have varying latency. Naive bonding implementation that do not take account of these factors will be problematic and will provide a poor quality bonded connection. At Netservers we use an enhanced form of MultiLink PPP called "Quantum Bonding". This technology is been created specifically to address the unique challenges of DSL line bonding and is the foundation of our ADSL bonding service.

Required Equipment

Ordinary consumer ADSL routers are not capable of bonding ADSL lines. A more sophisticated router such as Cisco or FireRack is required to perform line bonding.

The FireRack equipment supplied by Netservers is available with 2, 4, 6 and 8 ADSL 2+ interfaces. Cisco routers that take WIC modules can be similarly configured by adding the appropriate number of ADSL2+ WIC cards.

The technique used by Netservers is true bonding of PPPoE or PPPoA DSL connections. Some Virtual Internet Service Providers (VISPs) claim to provide a bonded ADSL service without utilising ML-PPP. Typically the technique that they use is to bond multiple VPN connections together, rather than bonding multiple DSL lines. This is not true line bonding and is a technically inferior solution with a number of disadvantages.

Increased resilience through ADSL bonding

The most obvious benefit of ADSL line bonding is the increase in download and upload bandwidth. Less obvious is increased fault-tolerance and resilience that that bonding provides. The bonding service provided by Netservers will utilise however many lines are available at a given time. If for instance you have a four-line bonded service, and one of those lines fails, your service will continue to operate over the three remaining lines. Naturally you will see a reduction in available bandwidth, but the service as a whole will continue to operate.

Dec 10, 2014

Ethernet bonding with Linux and 802.3ad

Nowadays, most desktop mainboards provide more than one gigabit ethernet port. Connecting them both to the same switch causes most Linux distros by default to get a individual IP on each device and route traffic only on the primary device (based on device metric) or round-robin. A single connection always starts at one IP and so all traffic goes through one device, limiting maximum bandwidth to 1 GBit.

Here comes bonding (sometimes called (port) trunking or link aggregation) to play. It connects two ore more ethernet ports to one virtual port with only one MAC and so mostly one IP address. Wheres earlier only two hosts (with the same OS running) or two switches (from the same vendor) could be connected, nowadays there's a standard protocol which makes it easy: LACP which is part of IEEE 802.3ad. Linux supports difference bonding mechanisms including 802.3ad. To enable bonding at all there are some kernel settings needed:

Device Drivers  --->
[*] Network device support  --->
<*>   Bonding driver support

After compiling and rebooting, we need a userspace tool for configuring the virtual interface. It's called ifenslave and provided with the Linux kernel. You can either compile it by hand

/usr/src/linux/Documentation/networking
gcc -Wall -O -I/usr/src/linux/include ifenslave.c -o ifenslave
cp ifenslave /sbin/ifenslave

or install it by emerge if you run Gentoo Linux:

emerge -va ifenslave

Now we can configure the bonding device, called bond0. Firstofall we need to set the 802.3ad mode and the MII link monitoring frequency by

echo "802.3ad" > /sys/class/net/bond0/bonding/mode
echo 100 >/sys/class/net/bond0/bonding/miimon

Now we can up the device and add some ethernet ports:

ifconfig bond0 up
ifenslave bond0 eth0
ifenslave bond0 eth1

Now bond0 is ready to be used. Run a dhcp client or set an IP by

ifconfig bond0 192.168.1.2 netmask 255.255.255.0

These steps are needed on each reboot. If you're running gentoo, you can use baselayout for this. Add

config_eth0=( "none" )
config_eth1=( "none" )
preup() {
 # Adjusting the bonding mode / MII monitor
 # Possible modes are : 0, 1, 2, 3, 4, 5, 6,
 #     OR
 #   balance-rr, active-backup, balance-xor, broadcast,
 #   802.3ad, balance-tlb, balance-alb
 # MII monitor time interval typically: 100 milliseconds
 if [[ ${IFACE} == "bond0" ]] ; then
  BOND_MODE="802.3ad"
  BOND_MIIMON="100"
  echo ${BOND_MODE} >/sys/class/net/bond0/bonding/mode
  echo ${BOND_MIIMON}  >/sys/class/net/bond0/bonding/miimon
  einfo "Bonding mode is set to ${BOND_MODE} on ${IFACE}"
  einfo "MII monitor interval is set to ${BOND_MIIMON} ms on ${IFACE}"
 else
  einfo "Doing nothing on ${IFACE}"
 fi
 return 0
}
slaves_bond0="eth0 eth1"
config_bond0=( "dhcp" )

to your /etc/conf.d/net. I found this nice preup part in the Gentoo Wiki Archive.

Now you have to configure the other side of the link. You can either use a Linux box and configure it the same way or a 802.3ad-capable switch. I used an HP Procurve 1800-24G switch. You have to enable LACP on the ports you're connected:


Now everything should work and you can enjoy a 2 GBits (or more) link. Further details can be found in the kernel documentation.

Mar 12, 2013

Jazztel Bonding the new alternative to VDSL

Since the launch by Jazztel of 30/1.5 (now 3) over VDSL, users are away from their central longed for access to this service in order to obtain maximum performance in their lines.

But the strict conditions of employment for VDSL so far have not allowed that dream can become a reality. The only hope for these users on copper pair, almost the majority, and not eligible modalities Cable / FTTH, is that ADSL operators implemented the ADSL bonding as an alternative.

At this point, all plants covered Jazztel VDSL are prepared and ready to start offering turn bonding. As confirmed by the Director of the Division of Residential and CMO Jazztel, Luis del Pozo, in an exclusive interview to bandaancha.eu (and soon to be available on the cover of this page) from the first half of the next 2011, Jazztel plans to launch its marketing Bonding + service, which will offer its existing users synchronization values ​​similar to those enjoyed by lucky customers with coverage for VDSL2.

Bonding +, the alternative to VDSL Jazztel

According to the Well, Jazztel "always attentive to the suggestions of its customers, has decided to launch this new modality, to bring those most affected by the distance factor solution both an economic and high quality. Currently our team technical closely with Huawei technicians, working around the clock for final tuning of Jazztel DSLAM and interesting alternative to offer this in the first third of 2011 "


Recall that the ADSL bonding involves using two lines on copper loop, doubling the theoretical maximum speed of ADSL2 +. This, in addition to the core, and require two physical copper pairs connected to two DSLAM ports, the subscriber must have a router compatible with this standard, from which hang two microfilters, one per line.

Net equipment: Comtrend NexusLink 5631Hg

The company chosen to provide new equipment for customers who sign this new option has been, as it was almost predictable, Comtrend which in turn is working hard to adapt their new NexusLink 5631Hg to the requirements of the operator and the deadlines set by this.


Thus, the new router must support IPv6, be compatible with the standard N and take at least one Gigabit Ethernet port, which lacks elements Based Comtrend model, which itself has two USB port ready to connect external storage devices or usb printer.


Until then, the limited beta tester of this new modality being used to test the latest tuning its predecessor, the NexusLink 5631 , the same team that the British operator BE is provided its users with bonding.

Source photo beusergroup.co.uk / technotes / index.php? xusLink_5631 you ...

Note that although the new method is not intended Bonding + exceed benefits Premium VDSL2 mode, in some lines in tests has achieved up to 40 Mbps in the downstream channel, as we can see here


The price

The trading prices of Jazztel Bonding + are defined yet, but according to the Well, should not exceed the service VDSL, although the cost of keeping the two lines and the launch of the service in the customer's home could reach somewhat expensive product, but, in his own words "along with the usual policy of Jazztel try to strive, as far as possible in the least possible impact these costs to the end user"

Recall that the cost of Jazztel VDSL, right now (final price and without promotions) only exceeds in just 2 € to 20 Mbps service to the operator's intention would then be to not beat this price for users Bonding + hire.

In the coming days we will have more details and information on this interesting scoop that we advance here more summary, on the cover of bandaancha.eu

Jan 16, 2015

Bonding instead of load balancing: Never be offline again!

The philosophy behind Viprinet "Bonding instead of load balancing: Never be offline again!"

Viprinet – Always online, always broadband!

Today, business transactions require enterprises to have an Internet connection with 100% uptime. However, most network solutions dash already against the basics: As soon as an Internet line drops out and mobile radio cells are overbooked, the availability of the connectivity solution decreases significantly. Learn in this video why Viprinet is independent of individual Internet links and can thus help businesses to achieve 100% uptime – at even lower costs.


The data stream from the LAN is encrypted by the Multichannel VPN Router and distributed onto the Internet connections (here: 2x DSL, 1x 3G / UMTS). The encrypted and fragmented data passes the networks of the utilized ISPs and reaches the Multichannel VPN Hub in the data center, which in turn decrypts the data stream and reassembles it correctly. Afterwards, the data stream is forwarded to its actual destination on the Internet. The same goes for the opposite direction: Here, the Hub encrypts the data stream, while the VPN Router decrypts it.

Feel free to visit our downloads section and download our whitepaper on the topic "Always online – wherever and whenever needed", providing detailed information on the Viprinet principle and its possibilities.

We are the bonding inventors!

We've invented the principle enabling the bonding of different WAN technologies. For us, bonding means real aggregation of bandwidth of all WAN media to be bonded.

The Multichannel VPN Router is the core of the Viprinet technology. With this device, several broadband lines can be combined into a single, highly available joint line. Unlike load balancing which can only distribute load to several WAN links, real bonding of all connections available is realized here.

Viprinet can combine all different types of access media, be they ADSL, SDSL, UMTS / HSPA+ / 3G, or LTE / 4G. The LAN sees these connections as one single line providing the accumulated up- and downstream of the different links even for single downloads.

The remote station principle

Viprinet uses an exceptional VPN tunnel technique with a star topology for secure and fast site, facility and vehicle linkage. For this purpose, the integration of two different devices is needed: A Multichannel VPN Router establishes an encrypted VPN tunnel to a single central remote station, the Multichannel VPN Hub, via each Internet line available. These VPN tunnels are then bundled into one tunnel through which the data is then transferred.

The Multichannel VPN Hub is usually located in a highly reliable data center and acts as an exchange: Data targeted at another company site will be forwarded through the respective VPN tunnel; data targeted at the public Internet will be decrypted and forwarded to its destination. The VPN Hub provides secure and quick communication between different Multichannel VPN Routers but it also serves as pivotal exchange point between the encrypted VPN and the public Internet.

Highest reliability and maximum bandwidth

With bonding using the Viprinet principle, a fast virtual WAN connection featuring almost 100 per cent reliability can be established. This reliability even inceases, the more different WAN media are bonded together. The ability to aggregate the bandwidths of all WAN media guarantees maximum transfer rates.​

Wired and wireless bonding: Viprinet's magic

The magic of the Viprinet principle lies in bonding wired WAN media like DSL or cable together with wireless media like UMTS / 3G, HSPA+ or even LTE / 4G. Providers able to bond all these media always offer the optimum mix of cost-effective WAN media ensuring highest bandwidth and reliability. Especially the ability to combine all common 3G and 4G mobile phone technologies like LTE, HSPA+, UMTS and CDMA via bonding with satellite and/or DSL or cable is unique worldwide.

LACP/Etherchannel Algorithms & Linux Bonding Modes

The LACP Mode in Enterasys or the Port-channel mode in Cisco, have their own algorithms for the priority selection for the slave interfaces involved in the bonding.
As I am a Linux Guy I am more familiar with the Bonding in Linux envoirnment.
We can create bonding in the /etc/sysconfig/network/ifcfg-bond0,here we can define the Master Interface with the IP address and then the slave interfaces involved in the bonding process along with the Mode of the Bonding.

The Switch connected for the bonding also has it's own aggregation algorithm present which must match the with the mode set in the server.

There are 7 modes present in the Linux kernel.

Refer to the Bonding Documentation in the Linux Kernel, it will be available at the path
cat /usr/src/linux-2.6.38/Documentation/networking/bonding.txt | less

More verbose information can be found at
http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding

Enterasys :
In Enterasys Switches such as N-series, the LACP Lag output Algorithm can be set for the 3 modes
DIP-SIP - Destination IP address/Source IP Address, slave interfaces are assigned on the basis of Source or Destination IP Addresses.
DA-SA - Destination MAC Addess/Source Mac Address, slave interfaces are assigned on the basis of Source or Destination MAC Addresses.
Round-Robin - Equal distribtution from the first slave to all slaves in round-robin fashion

To check for the LACP algorithm use following on the Enterasys Switch
Matrix N3 Platinum(su)->sh lacp ?
Specifies the lag port(s) to display
outportAlgorithm Shows lacp current ouport algorithm
flowRegeneration Shows lacp flow regeneration state
singleportlag Show single port lag setting
state Show global lag enable state
Matrix N3 Platinum(su)->sh lacp outportAlgorithm
dip-sip
Matrix N3 Platinum(su)->

To set the LACP outputalgorithm to different mode
Matrix N3 Platinum(su)->set lacp outportAlgorithm ?
dip-sip Use sip-dip algorithm for outport determination
da-sa Use da-sa algorithm for outport determination
round-robin Use round-robin algorithm for outport determination
Matrix N3 Platinum(su)->set lacp outportAlgorithm round-robin
Matrix N3 Platinum(su)->

Hence in accordance with the Mode set on the switch we can set the mode in the Linux
After doing this the LAG groups present will use the round-robin algorithm for flow distrbution.
Remember this is the global configuration which will cause change in algorithm of all LAG ports present.
By default the dip-sip algorithm is configured in the Enterasys switches.

Cisco :
On the Cisco Catalyst Switches, the port-channel can be used in LACP mode for the operation.
The default Load-balancing method used is src-mac (Source MAC Address).
Cisco allows us to perform the dry-run of the algoritm implemented using the test command.
I have all interfaces configured in the LACP Mode (Not in PAgP).

To check what is the current algorithm
Cisco#sh etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-mac
EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source MAC address
IPv4: Source MAC address
IPv6: Source MAC address
Cisco#

To test the Etherchannel Algorithm used
Cisco#test etherchannel load-balance interface port-channel 1 mac 00:18:17:F1:F9:C4 E4:9F:16:C5:11:56
Would select Gi1/0/1 of Po1
Cisco#

In IP based we can use the IP address to test the etherchannel.
To see the Ether-channel algorithm present
Cisco(config)#port-channel load-balance ?
dst-ip Dst IP Addr
dst-mac Dst Mac Addr
src-dst-ip Src XOR Dst IP Addr
src-dst-mac Src XOR Dst Mac Addr
src-ip Src IP Addr
src-mac Src Mac Addr
Cisco(config)#port-channel load-balance

Here we can see that there is the src-dst-ip & src-dst-mac which are used for inducing additional randomization using the XOR logical operation present.

Hence the load-balancing can be done using the Destination IP address or Source IP address, same goes for the MAC addresses.

To set the New Algorithm
Cisco(config)#port-channel load-balance dst-mac
Cisco(config)#

Now the Load-balancing will happen through the Destination-Mac Address.I will do some more research on this and update the post.

Dec 10, 2014

Interface Bonding 802.3ad (LACP) with Mikrotik and Cisco

Bonding (also called port trunking or link aggregation) can be configured quite easily on RouterOS-Based devices.

Having 2 NICs (ether1 and ether2) in each router (Router1 and Router2), it is possible to get maximum data rate between 2 routers, by aggregating port bandwidth.

To add a bonding interface on Router1 and Router2:

/interface bonding add slaves=ether1,ether2

(bonding interface needs a couple of seconds to get connectivity with its peer)

Link Monitoring:
Currently bonding in RouterOS supports two schemes for monitoring a link state of slave devices: MII and ARP monitoring. It is not possible to use both methods at a time due to restrictions in the bonding driver.

ARP Monitoring:
ARP monitoring sends ARP queries and uses the response as an indication that the link is operational. This also gives assurance that traffic is actually flowing over the links. If balance-rr and balance-xor modes are set, then the switch should be configured to evenly distribute packets across all links. Otherwise all replies from the ARP targets will be received on the same link which could cause other links to fail. ARP monitoring is enabled by setting three properties link-monitoring, arp-ip-targets and arp-interval. Meaning of each option is described later in this article. It is possible to specify multiple ARP targets that can be useful in a High Availability setups. If only one target is set, the target itself may go down. Having an additional targets increases the reliability of the ARP monitoring.

MII Monitoring:
MII monitoring monitors only the state of the local interface. In RouterOS it is possible to configure MII monitoring in two ways:

MII Type 1: device driver determines whether link is up or down. If device driver does not support this option then link will appear as always up.
MII Type 2: deprecated calling sequences within the kernel are used to determine if link is up. This method is less efficient but can be used on all devices. This mode should be set only if MII type 1 is not supported.

Main disadvantage is that MII monitoring can’t tell if the link actually can pass the packets or not even if the link is detected as up.

MII monitoring is configured setting desired link-monitoring mode and mii-interval.

Configuration Example: 802.3ad (LACP) with Cisco Catalyst GigabitEthernet Connection.

/inteface bonding add slaves=ether1,ether2 \
   mode=802.3ad lacp-rate=30secs \
   link-monitoring=mii-type1 \
   transmit-hash-policy=layer-2-and-3


Other part configuration (assuming the aggregation switch is a Cisco device, usable in EtherChannel / L3 environment):

!
interface range GigabitEthernet 0/1-2
   channel-protocol lacp
   channel-group 1 mode active
!
interface PortChannel 1
   no switchport
   ip address XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX
!

Or for EtherChannel / L2 environment:

!
interface range GigabitEthernet 0/1-2
   channel-protocol lacp
   channel-group 1 mode active
!
interface PortChannel 1
   switchport
   switchport mode access
   swichport access vlan XX
!

Dec 4, 2014

ZyXEL P-663H-51 ADSL2+ 4-port Bonding Gateway Review

ZyXEL's New P-663H-51 ADSL 2/2+ modem / router supports speeds of up to 48mbps downstream and 4mbps upstream, and includes four 10/100 Ethernet LAN ports. It also provides TR069 protocol for remote management, SPI firewall and DOS protection for security, and advanced QoS and multicasting features for triple play services.

Features at a Glance
  • ADSL2/2+, Annex L and Annex M
  • 2 ADSL2+ port bonding
  • Stateful Packet Inspection
  • Anti Denial-of-Service attack and port scanning
  • IGMP proxy/snooping for IP multicast
  • Port-based VLAN to support triple-play services
ZyXEL's P-663H-51 is an all-in-one ADSL2+ gateway for Home, SOHO and SMB applications. Featuring two ADSL2+ WAN ports and four 10/100Mbps Ethernet LAN ports, the P663H-51 provides SPI (Stateful Packet Inspection), anti-DOS (Denial of Service) and many Firewall security features to protect against network intrusion and attacks.

In addition, advanced features such as IP multicasting, IGMP proxy/snooping, fast leave and IP QoS fulfill the need of triple-play services, while the G.bond-based port bonding feature groups the 2 ADSL2+ physical ports into a logical link. The link not only provides VDSL-equivalent bandwidth with much longer loop length, its load-balance feature between the two ports also makes P-663H-51 the best choice for business and high-end market applications.

ZyXEL P-663H-51 Features

Higher-speed Broadband Access

The ZyXEL P-663H-51 has two ADSL2/2+ WAN ports. With the ATM-based multi-paired bonding feature, the two ports can be grouped into a logical link boasting the bandwidth twice as fast as a single ADSL2/2+ port, and the bit rates of each individual port can be freely and independently changed by their respective PHY layer. If one of the member ports fails, the conveyed traffic will be moved to the other port. When the failed port recovers, it will seamlessly return to the logical link and share the transmission/reception of the upper-layer traffic.

Compliant all standard ADSL2/ADSL2+ features

In addition to delivering increased data rates over greater distance than the basic ADSL2/ADSL2+, the P663H-51 also supports traditional ADSL2+ standards, such as Annex L, Annex M, DELT, SRA and dying gasp functions.

Robust, State-of-the-Art IP Security

The ZyXEL Prestige 663H-51 provides state-of-the-art standard Firewall features including, Stateful Packet Inspection, anti-DoS (Denial of Service) and IP/MAC address spoofing protection for basic defense against hackers, network intruders and other hazardous threats.

Sophisticated QoS for Triple-Play Services

The P-663H-51 comes with complete integrated ATM and Ethernet QoS mechanisms, as well as various IP QoS features (Packet classification/Rate Limitation/Queue Scheduling). The seamless QoS-mapping not only allows consistent and appropriate traffic treatment of packets, but also enables fulfillment of triple-play services. The IGMP proxy/snooping and fast leave (v1, v2) features also supports IP multicasting services.



ADSL Layer Features
  • ADSL2/2+, Annex L and Annex M
  • Support DELT (dual ended loop test)
  • Seamless Rate adaptation (SRA)
  • Dying Gasp
ATM Layer Features
  • Multiple PVC support
  • RFC1483/2684 multiple protocol over AAL5
RFC2516 PPPoE
  • VC and LLC Multiplexing
  • Traffic Shaping UBR, CBR, VBR-nrt
  • OAM F4/F5 end-to-end loopback
  • ATM-based Multi-Pair Bonding (G.998.1) support
Security Features
  • Three level management login
  • WAN & LAN Service access control
  • Service access control based on source IP address
  • Anti-Denial of Service, SYNC flooding, IP Smurfing, Ping of Death, Fraggle,Teardrop, LandAnti-port scanning
TCP/IP/port/Interface filtering rules, Protect against IP and MAC address spoofing
  • Stateful Packet Inspection
Logging Features
  • User selectable levels
  • Local display and/or send to remote syslog server
  • ADSL up/down, PPP up/down
  • Intrusion alert
  • Primary DNS server status monitor
  • XML config file failures
Network Protocols
  • IP routing
TCP, UDP, ICMP, ARP
    • VPN (IPSec, PPTP, L2TP) pass-through *
    • DHCP Server/Relay/Client
    • RADIUS client
    • DNS rely/proxy
    • Dynamic DNS
    • RIP/RIP v2 routing functions
    • NAT/PAT/NAPT
    • IGMP Proxy/snooping and fast leave (v1, v2 and v3)
    • IP QoS
    • UPnP IGD 1.0
Ethernet L2 Features
    • Default Bridging for user traffic
    • ARP
    • 802.1Q Tag-Based VLAN
    • 802.1P CoS with priority queuing
Hardware Specifications
    • Power input & Power consumption
12VDC (1.5A), 15 watt
      • Power Adaptor Input 100~ 240VAC, 0.5A, 50~60Hz, 40~60VA, Output 12VDC, 1.5A, 18W
      • LAN 4-Port RJ-45 connectors for 10/100Mbps with Auto MDI/MDIX. Support both Half and Full Duplex
      • ADSL one RJ-11 connector for 2 ADSL2+ ports
Physical Specifications
      • Dimension
205(W)x 145(D)x 32(H)mm
Environmental Specification
        • Temperature Operating 0 ~ 40, Storage -30 ~ 60
        • Humidity Operating 20 ~ 85% (non-condensing), Storage 10 ~ 95% (non-condensing)
Certification
        • RoHS & WEEE
        • Safety
- UL1950 - CSA C22.2 No. 950
        • EMC - FCC Part 15 & Part 68Class B

The ZyXEL P-663H-51 ADSL2+ 4-port Bonding Gateway review can be read on this forum.

Feb 2, 2011

Opening the Door to In-Building Copper Network Upgrades

Many communication services providers have made the decision to deploy fiber-to-the-building (FTTB) networks to multi-dwelling-units (MDUs). This hybrid approach, in which the existing in-building copper network remains active, can be a cost-effective and viable approach for delivering the high-speed services subscribers demand while keeping costs in check.

Yet, providers must ask themselves: Will this strategy work 5 years from now? What about 10 or 20 years down the road?

Enhanced services are in their infancy in terms of adoption and development. Social networking, cloud computing, high-speed file transfers, and streaming audio and video will continue to change the way bandwidth is used.

Copper has so far proven its ability to support high-speed services. Many providers, both large and small, have successfully deployed broadband over Last Mile copper networks. However, providers must prepare those networks for the future.

Below are 6 steps to upgrade your in-building copper networks to meet the ever-increasing demand for enhanced services.

Step 1. Improve performance and density of in-building entrance terminals (IBETs).

Network reliability is more important than ever because degradation of the network is more noticeable than ever. Higher bandwidth services operate at higher frequency electrical signals in the copper network. These higher frequency signals are more prone to imperfections in the legacy network, which can manifest in higher crosstalk, higher signal loss, and unbalance. Today, with multiple channels of HD video and high-speed Internet, and higher subscriber expectations, those imperfections are unacceptable. Pixelation or delays during a favorite TV show leads to angry customers.

The connectivity or cross-connect solution chosen for the in-building entrance terminal (IBET) directly affects the quality of service to subscribers. Contact integrity provided by the connector is critical to ensure reliable service, not only at the time of installation, but over the life of the connector.

Replacing a building’s aging 66 blocks with VDSL-compatible and Category 5 (CAT5)-compliant blocks can help achieve network reliability. Choosing a gel-filled, easy-to-install, insulation displacement contact (IDC) block, goes even further to protect reliability. Gel encapsulation helps protect the connection against moisture and corrosion, preserving a high-integrity, reliable connection for long-term broadband performance. The ideal IDC block could be installed without stripping wires or using tools, helping reduce the risk of it being installed incorrectly. It would also be able to be re-opened for visual validation of the IDC connection.

Where space is a concern, consider equipment that will increase density in the IBET. A typical indoor building entrance terminal today is configured with the terminal blocks installed along with separate 5-pin protective devices that shield equipment from transient voltage and current surges. Copper cables connect the individual subscriber blocks with the protection devices.

Recently, 3M introduced an innovative terminal block design (3M™ Quick Connect System 2814) that integrates the protection into the block. (It is currently deployed in other regions of the world and is anticipated to be release in the U.S. later this year.) (See Figure 1.) With the block, the entrance terminal holds just 1 device per subscriber instead of 2, essentially doubling density. Now, a 50-pair box can hold 100 pairs, allowing for more subscribers or additional services. The dual-purpose block also supports better signal integrity by eliminating the connection point between the terminal block and the protection device, where signal can degrade, potentially interfering with service.

Step 2. Optimize POTS splitter management for better service quality and greater efficiencies.

FTTB/VDSL2 applications with a remote DSLAM at the premises commonly require the installation of 2 sets of DSL-dedicated terminal blocks and equipment cables to and from the DSLAM at the building’s main distribution frame (MDF). To provide DSL service to a customer, 2 jumpers -- POTS IN and DSL OUT -- will run between the existing MDF and the DSL terminal blocks (See Figure 1.)


Figure 1. FTTB/VDSL2 applications with a remote DSLAM at the premises commonly require the installation of 2 sets of DSL-dedicated terminal blocks.

For larger, non-”pizza box” remote DSLAM applications (typically 50 or more subscribers), it is possible to achieve a higher density infrastructure with lower installation costs by using a VDSL2-ready block with integrated POTS splitters with just 1 equipment cable between the DSLAM and the MDF.

Besides creating such a high-density system, a well-designed integrated splitter block can also help deliver enhanced VDSL2 service. Individual wire guide channels can help maintain the wire pairs’ tight twist up to the base of the block’s Insulation Displacement Contacts (IDC). Sustaining the twist throughout the cable length reduces the potential for crosstalk and supports VDSL signal integrity. POTS splitters mounting on the block’s rear side will reduce the chance of accidental disconnections.

VDSL2 POTS splitters need to be fully compliant with the requirements of ANSI T1.413-1998 Issue 2 Annex E, ITU-T G.993.2 and designed to include robust ring trip protection with full compliance to the Broadband Forum TR 127 Issue 2 to support quality multimedia transmission.

Step 3. Provision a DSLAM port to every living unit.

For larger deployments where a high subscribership rate is expected, pre-deploying a DSLAM port to every living unit can reduce installation costs down the road. By using a VDSL2-ready block with integrated POTS splitters, a DSLAM port can be assigned up front to each living unit. To activate DSL, the technician skips the step of removing the POTS jumper and installing 2 new jumpers because it’s already done. The technician simply connects the already-installed jumpers to the splitter block.

Providers have shied away from taking this tact, and rightly so. Assigning each living unit with a DSLAM port requires a big initial investment in materials and labor. However, in buildings where DSL service is typically high, such as high-end apartments or college dorms, pre-deployment helps make activation easier and is cost-effective over time.

Step 4. Upgrade your copper cable to at least CAT5e.

The conduit that carries signal from the building entrance terminal to the individual subscriber is obviously an essential part of the in-building network.

Category 3 (CAT3) cable is primarily used for POTS wiring and still widely deployed today. CAT3 cable can support low-speed data applications with frequency transmissions up to 16 MHz and data transfer rates up to 10 Mbps. That simply won’t cut it for high-speed services available today and in the future. When deploying DSL, CAT3 should be replaced with a higher performing cable (i.e., CAT5 Enhanced [CAT5e] or better).

CAT5e cable is specified for transmission frequencies up to 100 MHz and can support data rates up to 1 Gbps, providing optimal performance for all data and phone systems.

CAT6 marks the next step up from CAT5e and carries a higher price tag. CAT6 cable raised the bar for operating frequencies to 250 MHz and can support data rates up to 10 Gbps.

The newest cable specification, CAT7 cable, is now also available, although it has not yet been widely adopted except for some government and manufacturing applications. It can achieve 600 MHz and 10 Gbps.

The difference is in the twist. Generally speaking, the tighter the wire pairs within the cable are twisted together, the better the signal integrity. When wires are laid side-by-side, the electromagnetic signal traveling through can jump from one wire to the other. The resulting crosstalk interferes with the signal, causing data errors, service interruptions and unhappy subscribers. At low frequencies, crosstalk usually doesn’t cause many problems. But at high frequencies, crosstalk can degrade the signal enough to interfere with service. Twisting the wires together has a canceling effect on crosstalk. The more twists per inch of wire, the better the cancellation effect.

For instance, CAT3 cable wires are twisted 3 to 4 times per foot of cable. CAT5e cable contains 3 to 4 twists per inch of cable, 12 times the twist of CAT3, leading to significantly better signal integrity (and happier subscribers).

Step 5. Train technicians to inspect for proper bonding and grounding.

As building communications closets become crowded with more and more equipment, proper bonding and grounding becomes increasingly important to ensure safety of people, property and the network. Proper bonding and grounding ensures that foreign voltage safely drains to the earth ground. Poor bonding and grounding can lead to service outages, damaged equipment, and, worst of all, the possible injury or death of a person.

Most operators have their own procedures for bonding and grounding based on industry guidelines. Still, due to lack of training and oversight, it is not uncommon to find improperly grounded telecom equipment in the field. To avoid dangerous situations, communications providers should properly train technicians on proper bonding and grounding, and continually stress its importance.

Before installing service, technicians should make sure that the building developer has provided a proper ground source. The utility/communications room should be equipped with a copper-clad, fire-rated multi-grounded neutral (MGN) conductor source that is #6 American Wire Gauge (AWG) or larger, and in good condition. The ground wire should be installed as straight as possible or make sweeping bends. (See Figure 2.) Tight bends or kinks increase the risk of foreign voltage jumping off the conductor and energizing surrounding metal. If the ground wire does not meet these minimum requirements, technicians should report the situation to their supervisor and delay installation until the grounding components are brought up to standard.


Figure 2. Ground wire should be installed as straight as possible and ensure the building developer has provided a proper ground source.

The MGN ground wire source should be connected to a bus bar. Telecom equipment on the wall is also connected to the bus bar to create a path to ground. If the bus bar is full, the technician should install an additional bar (or ask the building manager to do so) and strap the 2 bus bars together. The bonding conductor for passive equipment should be jacketed, fire-rated #6 AWG or larger. Active equipment should be bonded using, at minimum, #2 AWG tinned copper conductor. Again, bends should be sweeping and not tight or kinked.

Of note, some technicians may believe that because the building terminal cabinet contains protection coils, it is safe from foreign voltage regardless of the ground wire. However, if the building terminal is not properly bonded to ground, the metal cabinet protection may prove ineffective.

Step 6. Ensure a multiple-free network.

In-building copper networks should be multiple-free to ensure high-quality service now and in the future. That means each subscriber has a dedicated pair leading from the cross-connect cabinet to the building terminal to the living unit.

Many older networks were built in a bridge-tap configuration in which multiple living units are connected to a single pair running all the way from the cross-connect cabinet. Cable counts in multiple make it easier and less costly to add new subscribers, and it may have worked just fine for POTS; however, it doesn’t work for broadband. Each tap siphons off signal strength, leaving subscribers downstream with degraded service. Imagine a garden hose with holes punctured in it every few feet. By the time you get to the end of the hose, not much water is coming out. That’s essentially how it works with bridge tapping.

New networks should be designed multiple-free and old systems reconfigured to prevent bridge tapping. One possible way to ensure a multiple-free network is to choose a cross-connect block that does not allow bridge tapping. - source

Jan 16, 2013

Ericsson tests 500-Mbps VDSL2 technology


Line bonding, noise cancellation solutions could enable high-speed broadband access, mobile backhaul over copper lines.

Ericsson on Monday announced it has successfully tested high-speed VDSL2 technology at speeds of over 500 megabits per second.

The Swedish equipment vendor achieved the high data transfer rates over twisted copper pairs using new line bonding and crosstalk cancellation technology, which it calls 'vectorised' VDSL2.

Six lines were bonded in order to reach speeds above 500 Mbps at 500 metres. Crosstalk cancellation technology reduces the effects of noise from other copper pairs in the same cable bundle, enabling Ericsson to extend the capacity and reach of the signal to more people.

The company said standards for VDSL2 line bonding are already available, while standardisation of vectoring is expected by the end of 2009.

VDSL2 enables operators to offer access to the latest high-speed broadband services using their existing copper lines.

"With this technology, operators can enhance fibre access deployments with copper access in the last mile and thereby maximise the reuse of existing infrastructure," the vendor said in a statement.

"It also proves Ericsson's abilities to provide future mobile backhauling, which will enable quick and cost-effective introduction of Long Term Evolution (LTE) solutions," said Hakan Eriksson, CTO of Ericsson.

Ericsson said VDSL2 will allow a larger number of consumers to access demanding services including HDTV and video-on-demand (VoD) via their broadband connection.

Eriksson said the demonstration confirms Ericsson's "commitment to the continued research and development of DSL technology to improve operators' business with new access solutions." - source

Sep 22, 2013

How-To Bond 2 or more NICs together on MS Windows

Teaming or Link Aggregation is likewise the term used for Bonding 2 or more network interface controller (NIC) card on Microsoft Windows such as XP, Server 2003, Vista and 7 that creates a new "virtual" interface which has the total speed of both cards together. Take note the Bonding should not be confused with interface "bridging".

The actual speed gain depends and is apparent when copying files to more than 1 client at the same time. In any case, if your network infrastructure supports it, it is always a good practice.

In order to achieve this you will need two (2) things:
  1. A computer with 2 or more interfaces of the same manufacturer with drivers supporting teaming (most manufacturers do)
  2. A switch that supports Link Aggregation (e.g. CISCO SRW series)
First install the latest NIC drivers (also download advanced & utility drivers if availiable)
  • Intel - Download Drivers that include Intel® PROSet utility for Teaming & Vlan HERE
  • Realtek - Download latest drivers HERE
  • Marvell Yukon - Download Drivers & Network Control Utility HERE
Open the switch's Web interface or Configuration utility and navigate to teaming options. Option may vary depending on the manufacturer, so consult the user manual and search for teaming, bonding and link aggregation

Create a new Team and assign 2 or more switch ports to the Team, depending on your network interface controller (NIC) card, also enable LACP.


Next, go to control panel >network connections and right click >properties on one of the network adapters.

Create a new Team and select "IEEE 802.3ad Link Aggregation" as Teaming Protocol. Add the rest of the NIC to the team. A new Network card should appear in network connections. Any IPs should now be assigned to this interface.

Connect the NICs to the appropriate Ethernet ports.

You should now have a working NIC Team!

Dec 10, 2014

EtherChannel vs LACP vs PAgP

What is EtherChannel?

EtherChannel links formed when two or more links budled together for the purposes of aggregating available bandwidth and providing a measure of physical redundancy. Without EtherChannel, only one link will be available while the rest of the links will be disabled by STP, to prevent loop.
p/s# Etherchannel is a term normally used by Cisco, other vendors might calling this with a different term such as port trunking, trunking (do not confuse with cisco’s trunk port definition), bonding, teaming, aggregation etc.


What is LACP

Standards-based negotiation protocol, known as IEEE 802.1ax Link Aggregation Control Protocol, is simply a way to dynamically build an EtherChannel. Essentially, the “active” end of the LACP group sends out special frames advertising the ability and desire to form an EtherChannel. It’s possible, and quite common, that both ends are set to an “active” state (versus a passive state). Once these frames are exchanged, and if the ports on both side agree that they support the requirements, LACP will form an EtherChannel.

What is PAgP

Cisco’s proprietary negotiation protocol before LACP is introduced and endorsed by IEEE. EtherChannel technology was invented in the early 1990s. They were later acquired by Cisco Systems in 1994. In 2000 the IEEE passed 802.3ad (LACP) which is an open standard version of EtherChannel.

EtherChannel Negotiation

An EtherChannel can be established using one of three mechanisms:
  • PAgP - Cisco’s proprietary negotiation protocol
  • LACP (IEEE 802.3ad) – Standards-based negotiation protocol
  • Static Persistence (“On”) – No negotiation protocol is used

Any of these three mechanisms will suffice for most scenarios, however the choice does deserve some consideration. PAgP, while perfectly able, should probably be disqualified as a legacy proprietary protocol unless you have a specific need for it (such as ancient hardware). That leaves LACP and “on“, both of which have a specific benefit.

PAgP/LACP Advantages over Static

a) Prevent Network Error

LACP helps protect against switching loops caused by misconfiguration; when enabled, an EtherChannel will only be formed after successful negotiation between its two ends. However, this negotiation introduces an overhead and delay in initialization. Statically configuring an EtherChannel (“on”) imposes no delay yet can cause serious problems if not properly configured at both ends.

b) Hot-Standby Ports

If you add more than the supported number of ports to an LACP port channel, it has the ability to place these extra ports into a hot-standby mode. If a failure occurs on an active port, the hot-standby port can replace it.

c) Failover

If there is a dumb device sitting in between the two end points of an EtherChannel, such as a media converter, and a single link fails, LACP will adapt by no longer sending traffic down this dead link. Static doesn’t monitor this. This is not typically the case for most vSphere environments I’ve seen, but it may be of an advantage in some scenarios.

d) Configuration Confirmation

LACP won’t form if there is an issue with either end or a problem with configuration. This helps ensure things are working properly. Static will form without any verification, so you have to make sure things are good to go.

To configure an EtherChannel using LACP negotiation, each side must be set to either active or passive; only interfaces configured in active mode will attempt to negotiate an EtherChannel. Passive interfaces merely respond to LACP requests. PAgP behaves the same, but its two modes are refered to as desirable and auto.


3750X(config-if)#channel-group 1 mode ?
  active     Enable LACP unconditionally
  auto       Enable PAgP only if a PAgP device is detected
  desirable  Enable PAgP unconditionally
  on         Enable Etherchannel only
  passive    Enable LACP only if a LACP device is detected

Conclusion

Etherchannel/port trunking/link bundling/bonding/teaming is to combine multiple network interface.
PAgP/LACP is just a protocol to form the etherchannel link. You can have etherchannel without protocol, but not advisable.

Sources:

http://en.wikipedia.org/wiki/EtherChannel
http://packetlife.net/blog/2010/jan/18/etherchannel-considerations/
http://wahlnetwork.com/2012/05/09/demystifying-lacp-vs-static-etherchannel-for-vsphere/