Skip to main content

Configuring the JunOS CLI (Standalone vMX)

Happy 2021!

A lot of the information came from this video by Network Direction. It also showed me how to use these virtual labs. Usually I just showed up, clicked random buttons, and moved onto local .iso because I knew how to get those started.

Use Juniper vLabs for an online lab space to work in.

Let the setup commence, click the arrow, then SSH!

Two modes: Operational, Configuration. 

In Cisco talk, it's the > prompt and the # prompt after you hit config t.

Most prevalent thought: How many Cisco configurations also work here? What context clues can I use to look around? 

Turns out, yes, you can use the ? to figure out where to go next.

The show configuration layout looks kind of like a JSON or Python file, without the double quotes.

Check out show chassis routing-engine: How much of a system's resources are being used, broken down.

The syntax error was from me pressing the spacebar after 'edit protocols' in an attempt to just get to bgp. You can do that, if you start at top:

Notice the edit banner has gone back to [edit] and then [edit protocols bgp]

After editing the name (much more involved than 'hostname R1'), we can compare the actions.

I like how it uses math symbols. Minus is like "Well, no need for you anymore huh".

Pretend you have bare-bones knowledge about CLIs for routers. You can figure out what 'hostname' means.

What would you find easier to get the understanding of: 

copy running-config startup-config (copy run start)


commit and-quit? 

After years of use, I would say the former. For the newcomer, it may still be the former, because context is there.

                                                set address

Easier to write and read. Unless you find it easier to have your subnet masks spelled out. No shaming here. You can also stick the entire command - the interface setting, the number, the IP addressing scheme family, the address itself - all on one line. That's amazing!

This was my first foray into configuring Junos routers, and it was easier and clearer than I thought. Let's try a VLAN. Today's resource comes from MustBeGeek.

I can set them on the vMX router, but I can't actually show them. Am I missing a command somewhere.

I like how if you mistype something, JunOS is quick to say "Nope. Wrong. Try again!"

A unit is a logical interface - What you need to create a VLAN!

It's time for that torrential troublemaker, DNS, using Juniper's own documentation.

It doesn't recognize some commands the documentation lists despite being in the proper drop-down. Again, it stops before I can add a space to continue the command and throws a "?"

Hey, at least that works!

When I was configuring a NAT Pool, I swear it automatically finished the 'match-direction' command in the line. Some of them do get rather lengthy.

Appreciate how it tells you, clearly, what statements you may be missing:

 ## Warning: missing mandatory statement(s): 'translation-type'

So, that's the first look at JunOS CLI! Fun, clear, can't wait to do more.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory