IBM SC30-3681-08 manual Conguring and Monitoring the Config Process, Entering and Exiting Config

Chapter 6. Con®guring and Monitoring the CONFIG Process

This chapter describes the CONFIG process con®guration and operational commands. It includes the following sections:

vªEntering and Exiting CONFIGº

vªCONFIG Commandsº

Entering and Exiting CONFIG

To enter CONFIG from OPCON (*):

1.At the OPCON prompt, enter the status command to ®nd the PID of CONFIG. (See page 9 for a sample output of the status command.)

* status

2.Enter the OPCON talk command and the PID for CONFIG:

*talk 6

The console displays the CONFIG prompt (Config>). Now, you can enter CONFIG commands. If the prompt does not appear, press the Return key again. To exit CONFIG and return to the OPCON prompt (*), enter the intercept character. (The default is Ctrl-P .)

CONFIG Commands

This section describes each of the CONFIG commands. Each command includes a description, syntax requirements, and an example. The CONFIG commands are summarized in Table 4.

After accessing the CONFIG environment, enter the con®guration commands at the Config> prompt.

Table 4. CONFIG Command Summary

Command	Function
? (Help)	Displays all the commands available for this command level or lists the
	options for speci®c commands (if available). See ªGetting Helpº on page
	10.
Add	Adds an interface to the router con®guration, or a user to the router.
Boot	Enters Boot CONFIG command mode.
Change	Changes a user's password or a user's parameter values associated with
	this interface. Also changes a slot/port of an interface.
Clear	Clears con®guration information.
Delete	Deletes an interface from the router con®guration or deletes a con®gured
	user.
Disable	Disables login from a remote console,
Enable	Enables login from a remote console,
Environment	Monitors the operational temperature of the router if it has two service
	ports.
Event	Enters the Event Logging System con®guration environment.
Feature	Provides access to con®guration commands for independent router
	features outside the usual protocol and network interface con®guration
	processes.

© Copyright IBM Corp. 1994, 1998 51