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.
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!
It’s been quite a while since my last post and I thought I would post this little snippet of information that I found while deploying the ASR platform into my employers network.
I attended the packet pushers party on Friday 17th and managed to have some of my questions answered during what was a great show.
Over the last few years I have made the transition at the company I work for, from Support Engineer to Network Engineer. In between this I became a Managed Services Engineer dealing with the configuration, installation and maintenance of Cisco 1800 series routers. During this time I decided I would use the knowledge gained in my day job to go on the certification trail. 4 months later I gained my CCNA accreditation and a thirst to obtain more understanding in networking in general.
So I was tasked to provide a failover mechanism for a customer with Juniper equipment without using OSPF.
With the L2 providers we use there is always a link from the CPE to the provider equipment and then it breaks out to their backbone. Now, this means that there could be a break in the provider network and the customer CPE would still see the link as up. We would then be blindly forwarding traffic into a black hole. Continue reading