Tag Archives: VPN

MPLS VPN – option C – using bgp label exchange with cisco and Junos -part 1

Leave a reply

It has been a while since I have done any labs after getting a new job. This time, I will be building a NNI option C using both Cisco IOS and Juniper MX. The reason I write this is because I do not find many resources on the internet about the inter AS connection using 2 different software at the same time. Hope this can be useful for anyone who is having the same struggle as i do.
(the AS# below are randomly picked!!)
lab-testing-mpls
Based on the lab diagram (dont feel like copping it up), as the internal VPN service is already running and the intra AS is running OSPF and LDP for MPLS, I will be connecting AS5052 (the green aren in middle) and AS7077 (the orange area at the bottom) together over NNIs to extend the MPLS VPN services.
Continue reading →

Cisco ASA – Site to Site IPSec VPN with dynamic IP address

2 Replies

Setting up a policy based site to site IPSec VPN tunnel with static IP address is quite stright forward in Cisco ASA, but what if one of the end point is using dymanic IP address?
In this lab, I will be using 2 virtual ASA (9.6(2)) to create a site to site IPSec VPN tunnel, as well as setting up Cisco VPN client in one of the ASA with static IP address.
The ASA-F14 is the one with static IP address, and the ASA-F16 is using dynamic IP address.
20161221-mpls-2vrfs
Continue reading →

Traffic Engineering – MPLS

Leave a reply

This time we will handle the basic traffic engineering within a MPLS network. This technique allows network admin to manipulate the traffic and fully utilize the subscribed bandwidth or circuits.
Traffic engineering within a MPLS network can be more accurate and convenience than in a typical TCP/IP network, because TE are happened at the MPLS level only, which would not affect the base of the whole network topology. If manipulate traffic at the IP level, everything running on top of IP level will be affected.
The network topology for this testing is listed below.
20160123-00-topo
Continue reading →

Playing with Multicast – Part 4 – NV-MVPN on Junos

2 Replies

It sure has been some times since the last multicast post. This time, we will put the lab into a higher level, and will be running the multicast on the MPLS VPN platform. Since this post is focusing on MCast only, the configuration for MPLS network will not be described with my detail. So let s dig in.
20160117-LAB-NGMVPN-topo
Continue reading →

Playing with Multicast – Part 1.

Leave a reply

It really has been a long time since my previous post. I have recently received a project that deal with multicast, a old technology that is really new to me.
I have been googling around for resources and references, and there are indeed a lot of results that mostly focus on theory. Therefore, I decided to contribute some of my hands on experiences for anyone who is building a similar lab as I do.
My lab builds from simple to complex (the difficulty is really based on my own experience only.) It starts from a playing multicast at a local area network and up to a MPLS VPN network.
Part 1 of the multicast post starts with 1x receiver and 1x sender in a local area network.
Part 2 of the multicast post is describes the lab with a router and one for each sender and receiver.

Playing with Multicast – Part 2.


Part 3 of the multicast post is describes the lab with 3 routers and one for each sender and receiver.
(still organizing the information)
Part 4 of the multicast post is putting the lab from part 2 onto a MPLS VPN platform.
(still organizing the information)
Long story short, I will go straight to the part one deployment. The lab is simple; There is only 1 sender and 1 receiver within the same broadcast domain.
TOPOLOGY:
MCast-topo-local
The Sender is an Ubuntu 14.04 32bit with updated components as of 2015 Dec,02. The receiver is a Win XP 32bit machine. Both of them are equipped with 512Mb of ram and 20G of hdd. Both machines are installed with VLC as for sending and receiving. There is a Junos device as their gateway, but it can be ignored for this lab since it does not have any PIM nor IGMP configured. Continue reading →