ScreenOS Cookbook

Chapter 1. ScreenOS CLI, Architecture, and Troubleshooting

1.0. Introduction

If you’re a network professional with network OS experience, ScreenOS has a fairly straightforward CLI to get used to. With that being said, it is important to lay the groundwork for how to move around the CLI and understand the troubleshooting capabilities within ScreenOS so that you are prepared to use the information in this book.

Each vendor produces and maintains its own device OS and defines the main keywords used to perform various configuration and information management functions. The keywords in ScreenOS provide the flexibility and structure required to manage the firewall via the CLI. They are:

• get

• set/unset

• save

• clear

• exec

• delete

• regex support

You can see these upon successful login to the firewall by issuing the “next option” command, better known as ?, at the prompt:

	Login: netscreen
	Password: <netscreen>

	top-ssg140->  ?
	clear clear           dynamic system info
	delete                delete persistent info in flash
	exec                  exec system commands
	exit                  exit command console
	get                   get system information
	mtrace                multicast traceroute from source to destination
	ping                  ping other host
	reset                 reset system
	save                  save command
	set                   configure system parameters
	trace-route           trace route
	unset                 unconfigure system parameters
	top-ssg140->

Unlike some other network OSs, there is a single level of access in ScreenOS, based on the permissions associated with the login credentials. ScreenOS provides the ? as a helper. You can find the same information ...