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)
or
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.
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.
Comments
Post a Comment