New Technical Resource! Mastering the TNSR® Command Line Interface (CLI)

[mwatch]

In the age of automation, CLI remains crucial for network engineers. TNSR software router offers an industry-standard CLI, making it easy for experienced engineers to configure and troubleshoot.

Here is a new technical resource to help anyone master the TNSR Command Line Interface (CLI).

Read Now: https://www.netgate.com/resources/mastering-the-tnsr-command-line-interface-cli

[michmoor]

@mwatch

There is a configuration database but is there anyway to make the candidate configuration -- the candidate -- until you confirm (commit confirm) changes to make it running?
In Arista this is called 'configure session'. You can have this be your default way of entering the cli until you commit which is flexible.
Juniper has this baked in as part of the configuration process

Having the running configuration be active on any changes is a bit scary.
To me it seems like the bits are there to make this work with the configuration database.

Is there an ability to pipe 'grep' as well? Case insensitive.

show running | grep wan

It seems the matching parameters are case sensitive which isn't great. Junos handles this in the background when you

show configuration | display set | match wan

Lastly, is there a way to 'section; similar to Arista or IOS/NXOS where any line matching what you are looking for will bring up that block of configuration?

show run section bgp

[fractal_boy]

@michmoor no to "commit confirm" of a candidate config. In TNSR CLI when you type exit you commit your change. Please test your changes in a lab environment before running them on production.

Please read the article there is an answer to almost all your questions.
"| match" instead of "| grep". You can match using regex.

show running | match wan

matching parameters is case-sensitive.

regarding the "section" you can do something like this:

show run bgp

to display BGP configuration.