Pages

5.18.2017

BIRD Route Server Install | BGP Peer with Juniper MX

I was recently faced with a challenge whereby I needed to inject 30,000 BGP routes into a test environment for a DOCSIS 3.1 POC. Typically I would use IXIA to form the BGP session and inject the routes. However, all 5 IXIA testers were in use thus I needed a quick alternative. 

I was already aware of BIRD and it's use as a route server in a number of IXP environments so figured it would be a good fit. The following steps detail how to install BIRD on Ubuntu and how to instantiate a BGP session with a Juniper MX router. 

For more info on BIRD check here

Topology:


Filter ISIS Interface Routes Using JUNOS Policy

In this article, I'm going to explain how to use JUNOS policy to filter ISIS interface routes. We will look exclusively at export filtering. Import route policy is not allowed when using a link-state protocol such as ISIS or OSPF. This is because all nodes much synchronise their link-state database and import policy may alter this required behavior. The main use case whereby export route filtering can be useful is to reduce the size of your link-state database by filtering interface routes. Large deployments can see many thousands of IGP prefixes. ISIS does not rely on IP for transport thus we can safely filter these. Quite often only certain prefixes are actually required to be exchanged via an IGP such as loopbacks for PE reachability. In this example we will filter interface routes from the ISIS process and verify loopback reachability still exists. 

Topology:


5.02.2017

EVPN-VXLAN Inter-Tenant Routing on Juniper QFX / MX



I've recently started working on a project focused on EVPN-VXLAN based on Juniper technology. I figured I'd take the opportunity to share some experiences specifically around inter-VXLAN routing. Inter-VXLAN routing can be useful when passing traffic between different tenants. For example, you may have a shared-services tenant that needs to be accessed by a number of different customer tenants whilst not allowing reachability between customer tenants. By enabling inter-VXLAN routing on the MX we can use various route-leaking techniques and policy to provide a technical point of control.

To read the article then please head over to the iNET ZERO blog