Saturday, November 28, 2015

VXLAN simplified - what, why and how ?

What is VXLAN?

  • VXLAN - Virtual eXtensible Local Area Network, is an encapsulation or tunneling method to carry the L2 overlay network traffic on top of L3 networks.
  • VXLAN encapsulates original L2 frames in to a UDP packet (Port 4789).
  • It is developed by VMware, Cisco, Arista and Broadcom.


Why use VXLAN?


Let’s imagine a datacenter network scenario where there is a requirement for a customer or system to have the virtual machines in a single subnet or broadcast domain. The virtual machines are located in different hosts which are separated by racks, datacenters or even geographically and are in separate L3 segments of the network. How do we fulfill the requirement? VXLAN to the rescue.

By virtualizing Layer 2 VXLAN can bridge datacenters without changing address or gateway. A smart guy might ask: “We can do that with OTV, then why VXLAN?” Well, it’s true that they can serve the same purpose, but the difference is the limitation of number of LAN segments which is 4094 (maximum VLANs) in case of OTV. The VXLAN header provides a 24-bit address space called the VNI (VXLAN Network Identifier) to separate out tenant segments, which is 16 million.

How does VXLAN work?


Two major terminology of VXLAN are VTEP and VNI.

VTEP -  VXLAN Tunnel End Point, as the name implies it’s the point where VM traffic is encapsulated or de-encapsulated. This function is performed in the hypervisor or switch.

VNI - Virtual Network Identifier, which is used to identify VXLAN segments. All the hosts configured in a VNI are considered to be in the same broadcast domain and synchronized (Ex. MAC and ARP table).
VXLAN control plane can operate in three modes for traffic replication: Multicast, Unicast and Hybrid

Multicast Mode
  • Multicast mode relies on the capability multicast protocols (IGMP, PIM) of the physical network devices.
  • In this mode a multicast address is associated with each VXLAN segment or VID. Each host hosting the VM related to that segment joints the multicast group.
  • Broadcast, Unknown unicast and Multicast traffic known in short as BUM from the VMs are transmitted using multicast capability of the physical network devices.

Figure: Multicast mode

Unicast Mode
  • In unicast mode a Proxy VTEP referred as UTEP, is elected in each physical network segment to replicated multi destination traffic or BUM.
  • This mode does not need any special configuration or features in the physical network devices.
Figure: Unicast mode

Hybrid Mode
  • Hybrid mode is very similar to the unicast mode, other than multicast capability used only in the physical L2 switches. Multicast routing (PIM) is not required.
  • Multicast is used to replicate BUM traffic in the same physical L2 domain. Unicast is used to replicate BUM traffic between different physical network subnet.
Figure: Hybrid mode


Reference:

Thursday, November 26, 2015

Inter-AS VPWS in Alcatel-Lucent SR


Figure: Network diagram

In this post we will discuss on implementing L2 VPN service in Alcatel-Lucent. The two types of L2 VPN supported in ALU service router are VPWS or VLL and VPS. Different type of VPWS service exists based on network type: epipe, fpipe, apipe, ipipe. In our exercise we will configure epipe (e=ethernet) service.  

The configuration of epipe service is pretty simple in 7750SR. Refer here for service model.
To add a bit complexity, we will try it in an Inter-AS network environment.

The implementation approach in our example here is referred as Model-C. In this model BGP is used for signaling service label and LDP for transport label.

Tuesday, November 17, 2015

ALU 7750 SR L3VPN (VPRN)

MPLS L3 VPN – the Alcatel-Lucent way of implementation



This exercise shows the Alcatel-lucent’s way of implementing MPLS L3 VPN which is named as Virtual Private Routing Network – VPRN. In this technology the PE router keeps separate virtual route-table (VRF) for each customer. VPRN uses two type of MPLS labels: outer label also called transport label, inner label called customer/service label. Customer routes are exchanged between PE using MP-BGP address family VPN-IPv4. PE can run any dynamic or static routing protocol with the CE. Here we used OSPF for PE-CE routing.
Figure: Network diagram


Router
Interface
IP Address
R1
system
50.50.50.1
ToR2 (port 1/1/1)
192.168.12.1
ToR4 (port 1/1/2) (vrf ABC)
10.10.10.1
R2
system
50.50.50.2
ToR1 (port 1/1/1)
192.168.12.2
ToR3 (port 1/1/2)
192.168.23.2
R3
system
50.50.50.3
ToR2 (port 1/1/2)
192.168.23.3
ToR5 (port 1/1/1) (vrf ABC)
20.20.20.1
R4
E0/0
10.10.10.2
Loopback 1
4.4.4.4
R5
E0/0
20.20.20.2
Loopback 1
5.5.5.5
                                                   
Table: Interface details

Monday, November 16, 2015

ALU 7750 SR Service Architecture

Alcatel-Lucent 7750SR Service model

Various service provider VPN technologies (L2 and L3 VPN) are supported in 7750SR. Alcatel-Lucent's view of implementing these technologies are well structured in a model. Here I will describe the components of this model with sample configuration.

Components


  1. Customer: Every service will be associated with a customer ID, which has no real effect on the router functions. Its mainly used for reporting purpose.
  2. Service: Any VPN service (VPWS, VPLS, VPRN) should have an ID and must be associated with a customer.
  3. SAP: Service access point (SAP) is simply the interfaces facing the customer devices
  4. SDP: Service distribution point (SDP) is the logical interface representing the transport tunnel towards other PEs. It actually establishes a T-LDP.


Configuration Example


##### Creation of a customer #####

*A:PE-1# configure service customer 111 create
*A:PE-1>config>service>cust$ description "Customer ABC"
*A:PE-1>config>service>cust$ phone "+1-222-555-6666"
##### Configuration of SDP #####
*A:PE-1# configure service sdp 2 mpls create
*A:PE-1>config>service>sdp$ far-end 10.10.10.2
*A:PE-1>config>service>sdp$ ldp
#### Creation of an epipe/vpws service ####
*A:PE-1# configure service epipe 55 customer 111 create
*A:PE-1>config>service>epipe$ sap 1/1/2 create
*A:PE-1>config>service>epipe>sap$ exit
*A:PE-1>config>service>epipe# spoke-sdp 2:55 create
*A:PE-1>config>service>epipe>spoke-sdp$ exit
*A:PE-1>config>service>sdp$ no shutdown