[an error occurred while processing this directive][an error occurred while processing this directive]

Deleting a Statement from a JUNOS Configuration

To delete a statement or identifier from a JUNOS configuration, use the delete configuration mode command. Deleting a statement or an identifier effectively "unconfigures" the functionality associated with that statement or identifier, returning that functionality to its default condition.

user@host# delete <statement-path> <identifier>

When you delete a statement, the statement and all its subordinate statements and identifiers are removed from the configuration.

For statements that can have more than one identifier, when you delete one identifier, only that identifier is deleted. The other identifiers in the statement remain.

To delete the entire hierarchy starting at the current hierarchy level, do not specify a statement or an identifier in the delete command. When you omit the statement or identifier, you are prompted to confirm the deletion:


user@host# delete
Delete everything under this level? [yes, no] (no)
Possible completions:
no    Don't delete everything under this level
yes   Delete everything under this level
Delete everything under this level? [yes, no] (no) 

Note: You cannot delete multiple statements or identifiers within a hierarchy using a single delete command. You must delete each statement or identifier individually using multiple delete commands. For example, consider the following configuration at the [edit system] hierarchy level:

system {host-name host-211;domain-name domain-122;backup-router;arp;authentication-order [ radius password tacplus ];}

To delete the domain-name, host-name, and backup-router from the configuration, you cannot issue a single delete command:

user@host> delete system hostname host-211 domain-name domain-122 backup-router

You can only delete each statement individually:

user@host delete system host-name host-211

user@host delete system domain-name domain-122

user@host delete system backup-router

Published: 2010-04-27

[an error occurred while processing this directive]