So LinkedIn told me it was my 3 year workiversary the other day. 3 whole years since starting with Fluency Communications and building out their National Next Gen Network.
When I first joined the company, the network was ran on 3 Vyatta boxes and a few 100M circuits. From there we started the upgrade process to Juniper MX5 routers and some 1G links.
What made the MX platform stand out for us was the following:-
- Stability of Junos OS
- Rich feature set
- Built in scripting tools (Netconf/SLAX)
We required to have a box that would scale not only in performance but features. The MX5 can be easily unlocked from a 20G line rate box up to an MX10 giving 40G line rate performance with a simple license install (and further if you want). For us, EVPN is looking like a no brainer upgrade from VPLS with its control plane learning and mac learning/filtering with the use of policies. Sometimes it seems the possibilities are endless!
We have now outgrown the MX5/10 as our core router and we are now in receipt of some shiny MX480 routers (see below picture). We have also taken the decision to go single vendor, which up until the last year or so I always had an inherent distrust of but seeing the flexibility of the MX platform has removed that mental stumbling block and we are now using the MX104 at our access edge for customer connections rather than our previous vendor.
This allows us to look at things like Junos Space,Network Director and Connectivity Services Director to allow us to build service templates that will allow us to provision complex customer solutions and the click of a button rather than jumping onto several boxes and sitting at the cli for 20-30mins. This frees up my time to start looking at the next core network upgrade!
Have a great Christmas and a fantastic New Year!
P.S. Here’s a pic of our little MX evolution. From bottom to top – MX5, MX10, MX104 and an MX480!
So i have been using Juniper MX routers for some years now (mainly MX80’s) and have configured CoS in reasonably basic forms to suit $dayjob’s needs (mainly 4 queues).
It turns out that even though the MX routers support 8 queues in the basic line cards, by default it starts with 4 :s
Would it not be easier to enable all 8 to start with?
This blog is cross posted from my original blog found here
Below is a list of the 5 network things I am looking forward to in 2015 (in no particular order).
Having used MTR on my mac and on Linux system I was always frustrated with the lack of this option from the Junos CLI. You have always been able to start a shell and run MTR as below:-
nick@ScoobyDoo> start shell
% mtr 188.8.131.52
Although it’s super handy, the inconvenience of starting the shell can be a PITA.
I thought i would have to live with this until I found the following:-
nick@ScoobyDoo> traceroute monitor 184.108.40.206
No. I wasn’t meaning that!
I have spent the last few days trying to get an ME-3600 to play nicely with an SRX for VPLS.
Now, I have to admit that I love most Juniper products with the exception of the J-series and have spent a fair amount of time on the Juniper certification trail.
You may think that this leads me to be slightly biased when reviewing a book about a Juniper product but it does not.
As you may have already realised I am always looking for ways to speed up my day to day tasks.
Every few days I check my BGP peering to see if there are any sessions down and then give the peers the obligatory nudge to reset a session.
Normally I run ‘ show bgp sum | i Active’ or Idle/Open which gives me a list of peers that are not in an ‘established’ state. This means running a seperate command for each Active/Idle/Open session.
Thats far too much like hard work so i started to see what other option were available after the | . One of them is utility egrep! So, after 7 mins of trying to run commands and finally realising I have to escape the | i have came up with the below:-
show bgp summary | utility egrep ‘Idle| Active| Open’
Hope it helps you save some time!