Building a Juniper olive lab and playing with it is no different than gathering Cisco OS images and stuffing them into GNS3 or eve-ng. This articles describes some of my ramblings.
Candidate Configuration vs Active configuration in Junos
Let’s check show configuration interfaces on the operational mode:
We have the same output with “show interfaces” under [edit interfaces] level:
Let’s make a little change under interface tap (I added a description ):
Now, if we issue a “show configuration interfaces” again, we’ll have a different output than with “show interfaces”:
It’s because the active configuration and the candidate configuration aren’t the same here. How do we view the difference? “show interfaces | compare rollback 0” which compares the interfaces section between the active and the candidate configurations:
Making Juniper Olive instances talk together
I spent a few hours on this issue. And after consulting with a friend, I figured out that I need TAP interfaces, Bridging and fxp logical interfaces.
So If I want to have 6 Juniper Olives connected in some kind of network, I should have 6 bridged TAP interfaces. The remaining work is to create units under interface fxp0, each unit tagged with a seperate vlan-id.
What if I have Router A connected to Router B and Router C? Router A would have 2 connections. So does it need 2 TAPs?
No. Only one TAP. See TAP interfaces as “pipes”. When bridged, it means routers can communicate. period.
Himawan Nugroho details this issue in one of his blog posts.
Basic ATM Interface Configuration On Juniper JUNOS
I thought ATM interfaces are configured just like any other juniper interface. How stupid I was, LOL. I got this error message on the right.
So JUNOS needs us to specify the ATM PIC type and the VPI/VCI number.
|Configuring the ATM PIC Type|
|Configuring the VPI|
|Configuring the VCI|
|Configuring the IP address|
I chose the VCI number identical to the unit number; it’s just a best-practice. And don’t forget to commit your configuration!
Here is what it would look like:
BGP Traceroute options
Now in normal operation, we should only see keepalives:
Then I issued a clear bgp neighbor and that led to sending Notification messages:
Then we receive the OPEN messages: