proxmox-mirrors/mirror_frr
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_frr synced 2025-08-08 16:42:32 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: fixup basic.rst

Browse Source 
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
This commit is contained in:
Quentin Young 2017-12-22 16:19:33 -05:00
parent 2dd0a0ed1d
commit 8d2098618c
No known key found for this signature in database
GPG Key ID: DAF48E0F57E0834F
1 changed files with 225 additions and 321 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

546
doc/user/basic.rst
View File

@ -6,11 +6,15 @@ Basic commands
There are five routing daemons in use, and there is one manager daemon. There are five routing daemons in use, and there is one manager daemon.
These daemons may be located on separate machines from the manager These daemons may be located on separate machines from the manager
daemon. Each of these daemons will listen on a particular port for daemon. Each of these daemons will listen on a particular port for
incoming VTY connections. The routing daemons are: incoming VTY connections. The routing daemons are:
* *ripd*, *ripngd*, *ospfd*, *ospf6d*, *bgpd* - *ripd*
* *zebra* - *ripngd*
- *ospfd*
- *ospf6d*
- *bgpd*
- *zebra*
The following sections discuss commands common to all the routing The following sections discuss commands common to all the routing
daemons. daemons.
@ -38,12 +42,12 @@ Config files are generally found in:
* :file:`@value{INSTALL_PREFIX_ETC}`/\*.conf * :file:`@value{INSTALL_PREFIX_ETC}`/\*.conf
Each of the daemons has its own Each of the daemons has its own
config file. For example, zebra's default config file name is: config file. For example, zebra's default config file name is:
* :file:`@value{INSTALL_PREFIX_ETC`/zebra.conf} * :file:`@value{INSTALL_PREFIX_ETC`/zebra.conf}
The daemon name plus :file:`.conf` is the default config file name. You The daemon name plus :file:`.conf` is the default config file name. You
can specify a config file using the @kbd{-f} or @kbd{--config-file} can specify a config file using the :kbd:`-f` or :kbd:`--config-file`
options when starting the daemon. options when starting the daemon.
.. _Basic_Config_Commands: .. _Basic_Config_Commands:
@ -51,220 +55,189 @@ options when starting the daemon.
Basic Config Commands Basic Config Commands
--------------------- ---------------------
.. index:: Command {hostname `hostname`} {} .. index:: hostname HOSTNAME
Command {hostname `hostname`} {} ``hostname HOSTNAME``
Set hostname of the router. Set hostname of the router.
.. index:: Command {password `password`} {} .. index:: password PASSWORD
Command {password `password`} {} ``password PASSWORD``
Set password for vty interface. If there is no password, a vty won't Set password for vty interface. If there is no password, a vty won't
accept connections. accept connections.
.. index:: Command {enable password `password`} {} .. index:: enable password PASSWORD
Command {enable password `password`} {} ``enable password PASSWORD``
Set enable password. Set enable password.
.. index:: Command {log trap `level`} {} .. index::
single: no log trap [LEVEL]
single: log trap LEVEL
Command {log trap `level`} {} ``[no] log trap LEVEL``
.. index:: Command {no log trap} {} These commands are deprecated and are present only for historical
compatibility. The log trap command sets the current logging level for all
enabled logging destinations, and it sets the default for all future logging
commands that do not specify a level. The normal default logging level is
debugging. The ``no`` form of the command resets the default level for future
logging commands to debugging, but it does not change the logging level of
existing logging destinations.
Command {no log trap} {} .. index::
These commands are deprecated and are present only for historical compatibility. single: no log stdout [LEVEL]
The log trap command sets the current logging level for all enabled single: log stdout [LEVEL]
logging destinations, and it sets the default for all future logging commands
that do not specify a level. The normal default
logging level is debugging. The `no` form of the command resets
the default level for future logging commands to debugging, but it does
not change the logging level of existing logging destinations.
.. index:: Command {log stdout} {} ``[no] log stdout LEVEL``
Enable logging output to stdout. If the optional second argument specifying
the logging level is not present, the default logging level (typically
debugging, but can be changed using the deprecated ``log trap`` command) will
be used. The ``no`` form of the command disables logging to stdout. The
``LEVEL`` argument must have one of these values: emergencies, alerts,
critical, errors, warnings, notifications, informational, or debugging. Note
that the existing code logs its most important messages with severity
``errors``.
Command {log stdout} {} .. index::
.. index:: Command {log stdout `level`} {} single: no log file [FILENAME [LEVEL]]
single: log file FILENAME [LEVEL]
Command {log stdout `level`} {} ``[no] log file [FILENAME [LEVEL]]``
.. index:: Command {no log stdout} {} If you want to log into a file, please specify ``filename`` as
in this example: ::
Command {no log stdout} {} log file /var/log/frr/bgpd.log informational
Enable logging output to stdout.
If the optional second argument specifying the
logging level is not present, the default logging level (typically debugging,
but can be changed using the deprecated `log trap` command) will be used.
The `no` form of the command disables logging to stdout.
The `level` argument must have one of these values:
emergencies, alerts, critical, errors, warnings, notifications, informational, or debugging. Note that the existing code logs its most important messages
with severity `errors`.
.. index:: Command {log file `filename`} {} If the optional second argument specifying the logging level is not present,
the default logging level (typically debugging, but can be changed using the
deprecated ``log trap`` command) will be used. The ``no`` form of the command
disables logging to a file. *Note:* if you do not configure any file logging,
and a daemon crashes due to a signal or an assertion failure, it will attempt
to save the crash information in a file named /var/tmp/frr.<daemon
name>.crashlog. For security reasons, this will not happen if the file exists
already, so it is important to delete the file after reporting the crash
information.
Command {log file `filename`} {} .. index::
.. index:: Command {log file `filename` `level`} {} single: no log syslog [LEVEL]
single: log syslog [LEVEL]
Command {log file `filename` `level`} {} ``[no] log syslog [LEVEL]``
.. index:: Command {no log file} {} Enable logging output to syslog. If the optional second argument specifying
the logging level is not present, the default logging level (typically
debugging, but can be changed using the deprecated ``log trap`` command) will
be used. The ``no`` form of the command disables logging to syslog.
Command {no log file} {} .. index::
If you want to log into a file, please specify `filename` as single: no log monitor [LEVEL]
in this example:: single: log monitor [LEVEL]
log file /var/log/frr/bgpd.log informational ``[no] log monitor [LEVEL]``
Enable logging output to vty terminals that have enabled logging using the
If the optional second argument specifying the ``terminal monitor`` command. By default, monitor logging is enabled at the
logging level is not present, the default logging level (typically debugging, debugging level, but this command (or the deprecated ``log trap`` command) can
but can be changed using the deprecated `log trap` command) will be used. be used to change the monitor logging level. If the optional second argument
The `no` form of the command disables logging to a file. specifying the logging level is not present, the default logging level
(typically debugging, but can be changed using the deprecated ``log trap``
command) will be used. The ``no`` form of the command disables logging to
terminal monitors.
Note: if you do not configure any file logging, and a daemon crashes due .. index::
to a signal or an assertion failure, it will attempt to save the crash single: no log facility [FACILITY]
information in a file named /var/tmp/frr.<daemon name>.crashlog. single: log facility [FACILITY]
For security reasons, this will not happen if the file exists already, so
it is important to delete the file after reporting the crash information.
.. index:: Command {log syslog} {} ``[no] log facility [FACILITY]``
This command changes the facility used in syslog messages. The default
facility is ``daemon``. The ``no`` form of the command resets
the facility to the default ``daemon`` facility.
Command {log syslog} {} .. index::
.. index:: Command {log syslog `level`} {} single: no log record-priority
single: log record-priority
Command {log syslog `level`} {} ``[no] log record-priority``
.. index:: Command {no log syslog} {} To include the severity in all messages logged to a file, to stdout, or to
a terminal monitor (i.e. anything except syslog),
use the ``log record-priority`` global configuration command.
To disable this option, use the ``no`` form of the command. By default,
the severity level is not included in logged messages. Note: some
versions of syslogd (including Solaris) can be configured to include
the facility and level in the messages emitted.
Command {no log syslog} {} .. index::
Enable logging output to syslog. single: log timestamp precision <0-6>
If the optional second argument specifying the single: [no] log timestamp precision <0-6>
logging level is not present, the default logging level (typically debugging,
but can be changed using the deprecated `log trap` command) will be used.
The `no` form of the command disables logging to syslog.
.. index:: Command {log monitor} {} ``[no] log timestamp precision [<0-6>]``
This command sets the precision of log message timestamps to the given number
Command {log monitor} {} of digits after the decimal point. Currently, the value must be in the range
.. index:: Command {log monitor `level`} {} 0 to 6 (i.e. the maximum precision is microseconds). To restore the default
behavior (1-second accuracy), use the ``no`` form of the command, or set the
Command {log monitor `level`} {} precision explicitly to 0.
.. index:: Command {no log monitor} {}
Command {no log monitor} {}
Enable logging output to vty terminals that have enabled logging
using the `terminal monitor` command.
By default, monitor logging is enabled at the debugging level, but this
command (or the deprecated `log trap` command) can be used to change
the monitor logging level.
If the optional second argument specifying the
logging level is not present, the default logging level (typically debugging,
but can be changed using the deprecated `log trap` command) will be used.
The `no` form of the command disables logging to terminal monitors.
.. index:: Command {log facility `facility`} {}
Command {log facility `facility`} {}
.. index:: Command {no log facility} {}
Command {no log facility} {}
This command changes the facility used in syslog messages. The default
facility is `daemon`. The `no` form of the command resets
the facility to the default `daemon` facility.
.. index:: Command {log record-priority} {}
Command {log record-priority} {}
.. index:: Command {no log record-priority} {}
Command {no log record-priority} {}
To include the severity in all messages logged to a file, to stdout, or to
a terminal monitor (i.e. anything except syslog),
use the `log record-priority` global configuration command.
To disable this option, use the `no` form of the command. By default,
the severity level is not included in logged messages. Note: some
versions of syslogd (including Solaris) can be configured to include
the facility and level in the messages emitted.
.. index:: Command {log timestamp precision `<0-6>`} {}
Command {log timestamp precision `<0-6>`} {}
.. index:: Command {no log timestamp precision} {}
Command {no log timestamp precision} {}
This command sets the precision of log message timestamps to the
given number of digits after the decimal point. Currently,
the value must be in the range 0 to 6 (i.e. the maximum precision
is microseconds).
To restore the default behavior (1-second accuracy), use the
`no` form of the command, or set the precision explicitly to 0.
:: ::
@group log timestamp precision 3
log timestamp precision 3
@end group
In this example, the precision is set to provide timestamps with In this example, the precision is set to provide timestamps with
millisecond accuracy. millisecond accuracy.
.. index:: Command {log commands} {} .. index:: log commands
Command {log commands} {} ``log commands``
This command enables the logging of all commands typed by a user to This command enables the logging of all commands typed by a user to
all enabled log destinations. The note that logging includes full all enabled log destinations. The note that logging includes full
command lines, including passwords. Once set, command logging can only command lines, including passwords. Once set, command logging can only
be turned off by restarting the daemon. be turned off by restarting the daemon.
.. index:: Command {service password-encryption} {} .. index:: service password-encryption
Command {service password-encryption} {} ``service password-encryption``
Encrypt password. Encrypt password.
.. index:: Command {service advanced-vty} {} .. index:: service advanced-vty
Command {service advanced-vty} {} ``service advanced-vty``
Enable advanced mode VTY. Enable advanced mode VTY.
.. index:: Command {service terminal-length `<0-512>`} {} .. index:: service terminal-length <0-512>
Command {service terminal-length `<0-512>`} {} ``service terminal-length <0-512>``
Set system wide line configuration. This configuration command applies Set system wide line configuration. This configuration command applies
to all VTY interfaces. to all VTY interfaces.
.. index:: Command {line vty} {} .. index:: line vty
Command {line vty} {} ``line vty``
Enter vty configuration mode. Enter vty configuration mode.
.. index:: Command {banner motd default} {} .. index:: banner motd default
Command {banner motd default} {} ``banner motd default``
Set default motd string. Set default motd string.
.. index:: Command {no banner motd} {} .. index:: no banner motd
Command {no banner motd} {} ``no banner motd``
No motd banner string will be printed. No motd banner string will be printed.
.. index:: {Line Command} {exec-timeout `minute`} {} .. index:: exec-timeout MINUTE [SECOND]
{Line Command} {exec-timeout `minute`} {} ``exec-timeout MINUTE [SECOND]``
.. index:: {Line Command} {exec-timeout `minute` `second`} {} Set VTY connection timeout value. When only one argument is specified
it is used for timeout value in minutes. Optional second argument is
used for timeout value in seconds. Default timeout value is 10 minutes.
When timeout value is zero, it means no timeout.
{Line Command} {exec-timeout `minute` `second`} {} .. index:: no exec-timeout
Set VTY connection timeout value. When only one argument is specified
it is used for timeout value in minutes. Optional second argument is
used for timeout value in seconds. Default timeout value is 10 minutes.
When timeout value is zero, it means no timeout.
.. index:: {Line Command} {no exec-timeout} {} ``no exec-timeout``
Do not perform timeout at all. This command is as same as *exec-timeout 0 0*.
{Line Command} {no exec-timeout} {} .. index:: access-class ACCESS-LIST
Do not perform timeout at all. This command is as same as
*exec-timeout 0 0*.
.. index:: {Line Command} {access-class `access-list`} {} ``access-class ACCESS-LIST``
Restrict vty connections with an access list.
{Line Command} {access-class `access-list`} {}
Restrict vty connections with an access list.
.. _Sample_Config_File: .. _Sample_Config_File:
@ -275,7 +248,6 @@ Below is a sample configuration file for the zebra daemon.
:: ::
@group
! !
! Zebra configuration file ! Zebra configuration file
! !
@ -286,17 +258,15 @@ Below is a sample configuration file for the zebra daemon.
log stdout log stdout
! !
! !
@end group
'!' and '#' are comment characters. If the first character of the word
'!' and '#' are comment characters. If the first character of the word
is one of the comment characters then from the rest of the line forward is one of the comment characters then from the rest of the line forward
will be ignored as a comment. will be ignored as a comment.
:: ::
password zebra!password password zebra!password
If a comment character is not the first character of the word, it's a If a comment character is not the first character of the word, it's a
normal character. So in the above example '!' will not be regarded as a normal character. So in the above example '!' will not be regarded as a
@ -307,52 +277,52 @@ comment and the password is set to 'zebra!password'.
Terminal Mode Commands Terminal Mode Commands
====================== ======================
.. index:: Command {write terminal} {} .. index:: write terminal
Command {write terminal} {} ``write terminal``
Displays the current configuration to the vty interface. Displays the current configuration to the vty interface.
.. index:: Command {write file} {} .. index:: write file
Command {write file} {} ``write file``
Write current configuration to configuration file. Write current configuration to configuration file.
.. index:: Command {configure terminal} {} .. index:: configure terminal
Command {configure terminal} {} ``configure terminal``
Change to configuration mode. This command is the first step to Change to configuration mode. This command is the first step to
configuration. configuration.
.. index:: Command {terminal length `<0-512>`} {} .. index:: terminal length <0-512>
Command {terminal length `<0-512>`} {} ``terminal length <0-512>``
Set terminal display length to `<0-512>`. If length is 0, no Set terminal display length to ``<0-512>``. If length is 0, no
display control is performed. display control is performed.
.. index:: Command {who} {} .. index:: who
Command {who} {} ``who``
Show a list of currently connected vty sessions. Show a list of currently connected vty sessions.
.. index:: Command {list} {} .. index:: list
Command {list} {} ``list``
List all available commands. List all available commands.
.. index:: Command {show version} {} .. index:: show version
Command {show version} {} ``show version``
Show the current version of @value{PACKAGE_NAME} and its build host information. Show the current version of @value{PACKAGE_NAME} and its build host information.
.. index:: Command {show logging} {} .. index:: show logging
Command {show logging} {} ``show logging``
Shows the current configuration of the logging system. This includes Shows the current configuration of the logging system. This includes
the status of all logging destinations. the status of all logging destinations.
.. index:: Command {logmsg `level` `message`} {} .. index:: logmsg LEVEL MESSAGE
Command {logmsg `level` `message`} {} ``logmsg LEVEL MESSAGE``
Send a message to all logging destinations that are enabled for messages Send a message to all logging destinations that are enabled for messages
of the given severity. of the given severity.
@ -364,64 +334,46 @@ Common Invocation Options
These options apply to all @value{PACKAGE_NAME} daemons. These options apply to all @value{PACKAGE_NAME} daemons.
``-d, --daemon``
*-d*
*--daemon*
Runs in daemon mode. Runs in daemon mode.
*-f `file`* ``-f file, --config_file=FILE``
*--config_file=`file`*
Set configuration file name. Set configuration file name.
*-h* ``-h, --help``
*--help*
Display this help and exit. Display this help and exit.
*-i `file`* ``-i file, --pid_file=file``
*--pid_file=`file`*
Upon startup the process identifier of the daemon is written to a file, Upon startup the process identifier of the daemon is written to a file,
typically in :file:`/var/run`. This file can be used by the init system typically in :file:`/var/run`. This file can be used by the init system
to implement commands such as *.../init.d/zebra status*, to implement commands such as ``.../init.d/zebra status``,
*.../init.d/zebra restart* or @command{.../init.d/zebra ``.../init.d/zebra restart`` or ``.../init.d/zebra stop``.
stop}.
The file name is an run-time option rather than a configure-time option The file name is an run-time option rather than a configure-time option
so that multiple routing daemons can be run simultaneously. This is so that multiple routing daemons can be run simultaneously. This is
useful when using @value{PACKAGE_NAME} to implement a routing looking glass. One useful when using @value{PACKAGE_NAME} to implement a routing looking glass. One
machine can be used to collect differing routing views from differing machine can be used to collect differing routing views from differing
points in the network. points in the network.
*-A `address`* ``-A address, --vty_addr=address``
*--vty_addr=`address`*
Set the VTY local address to bind to. If set, the VTY socket will only Set the VTY local address to bind to. If set, the VTY socket will only
be bound to this address. be bound to this address.
*-P `port`* ``-P port, --vty_port=port``
*--vty_port=`port`*
Set the VTY TCP port number. If set to 0 then the TCP VTY sockets will not Set the VTY TCP port number. If set to 0 then the TCP VTY sockets will not
be opened. be opened.
*-u `user`* ``-u user, --vty_addr=user``
*--vty_addr=`user`*
Set the user and group to run as. Set the user and group to run as.
*-v* ``-v, --version``
*--version*
Print program version. Print program version.
@ -430,21 +382,18 @@ These options apply to all @value{PACKAGE_NAME} daemons.
Loadable Module Support Loadable Module Support
======================= =======================
FRR supports loading extension modules at startup. Loading, reloading or FRR supports loading extension modules at startup. Loading, reloading or
unloading modules at runtime is not supported (yet). To load a module, use unloading modules at runtime is not supported (yet). To load a module, use
the following command line option at daemon startup: the following command line option at daemon startup:
``-M module:options, --module module:options``
*-M `module:options`* Load the specified module, optionally passing options to it. If the module
*--module `module:options`*
Load the specified module, optionally passing options to it. If the module
name contains a slash (/), it is assumed to be a full pathname to a file to name contains a slash (/), it is assumed to be a full pathname to a file to
be loaded. If it does not contain a slash, the be loaded. If it does not contain a slash, the
`@value{INSTALL_PREFIX_MODULES`} directory is searched for a module of `@value{INSTALL_PREFIX_MODULES`} directory is searched for a module of
the given name; first with the daemon name prepended (e.g. `zebra_mod` the given name; first with the daemon name prepended (e.g. ``zebra_mod``
for `mod`), then without the daemon name prepended. for ``mod``), then without the daemon name prepended.
This option is available on all daemons, though some daemons may not have This option is available on all daemons, though some daemons may not have
any modules available to be loaded. any modules available to be loaded.
@ -453,23 +402,23 @@ The SNMP Module
--------------- ---------------
If SNMP is enabled during compile-time and installed as part of the package, If SNMP is enabled during compile-time and installed as part of the package,
the `snmp` module can be loaded for the *zebra*, the ``snmp`` module can be loaded for the *zebra*, *bgpd*, *ospfd*, *ospf6d*
*bgpd*, *ospfd*, *ospf6d* and *ripd* daemons. and *ripd* daemons.
The module ignores any options passed to it. Refer to :ref:`SNMP_Support` The module ignores any options passed to it. Refer to :ref:`SNMP_Support`
for information on its usage. for information on its usage.
The FPM Module The FPM Module
-------------- --------------
If FPM is enabled during compile-time and installed as part of the package, If FPM is enabled during compile-time and installed as part of the package,
the `fpm` module can be loaded for the *zebra* daemon. This the ``fpm`` module can be loaded for the *zebra* daemon. This
provides the Forwarding Plane Manager ("FPM") API. provides the Forwarding Plane Manager ("FPM") API.
The module expects its argument to be either `netlink` or The module expects its argument to be either ``netlink`` or
`protobuf`, specifying the encapsulation to use. `netlink` is the ``protobuf``, specifying the encapsulation to use. `netlink` is the
default, and `protobuf` may not be available if the module was built default, and `protobuf` may not be available if the module was built
without protobuf support. Refer to :ref:`zebra_FIB_push_interface` for more without protobuf support. Refer to :ref:`zebra_FIB_push_interface` for more
information. information.
.. _Virtual_Terminal_Interfaces: .. _Virtual_Terminal_Interfaces:
@ -485,15 +434,14 @@ interface (CLI) for user interaction with the routing daemon.
VTY Overview VTY Overview
------------ ------------
VTY stands for Virtual TeletYpe interface. It means you can connect to VTY stands for Virtual TeletYpe interface. It means you can connect to
the daemon via the telnet protocol. the daemon via the telnet protocol.
To enable a VTY interface, you have to setup a VTY password. If there To enable a VTY interface, you have to setup a VTY password. If there
is no VTY password, one cannot connect to the VTY interface at all. is no VTY password, one cannot connect to the VTY interface at all.
:: ::
@group
% telnet localhost 2601 % telnet localhost 2601
Trying 127.0.0.1... Trying 127.0.0.1...
Connected to localhost. Connected to localhost.
@ -506,12 +454,13 @@ is no VTY password, one cannot connect to the VTY interface at all.
Password: XXXXX Password: XXXXX
Router> ? Router> ?
enable Turn on privileged commands enable . . . Turn on privileged commands
exit Exit current mode and down to previous mode exit . . . Exit current mode and down to previous mode
help Description of the interactive help system help . . . Description of the interactive help system
list Print command list list . . . Print command list
show Show running system information show . . . Show system inform
who Display who is on a vty
wh. . . Display who is on a vty
Router> enable Router> enable
Password: XXXXX Password: XXXXX
Router# configure terminal Router# configure terminal
@ -519,10 +468,9 @@ is no VTY password, one cannot connect to the VTY interface at all.
Router(config-if)# ip address 10.0.0.1/8 Router(config-if)# ip address 10.0.0.1/8
Router(config-if)# ^Z Router(config-if)# ^Z
Router# Router#
@end group
'?' is very useful for looking up commands.
:kbd:`?` is very useful for looking up commands.
.. _VTY_Modes: .. _VTY_Modes:
@ -572,41 +520,22 @@ CLI Movement Commands
These commands are used for moving the CLI cursor. The :kbd:`C` character These commands are used for moving the CLI cursor. The :kbd:`C` character
means press the Control Key. means press the Control Key.
:kbd:`C-f` / :kbd:`LEFT`
*C-f*
*:kbd:`RIGHT`*
@kindex C-f
@kindex :kbd:`RIGHT`
Move forward one character. Move forward one character.
:kbd:`C-b` / :kbd:`RIGHT`
*C-b*
*:kbd:`LEFT`*
@kindex C-b
@kindex :kbd:`LEFT`
Move backward one character. Move backward one character.
:kbd:`M-f`
*M-f*
@kindex M-f
Move forward one word. Move forward one word.
:kbd:`M-b`
*M-b*
@kindex M-b
Move backward one word. Move backward one word.
:kbd:`C-a`
*C-a*
@kindex C-a
Move to the beginning of the line. Move to the beginning of the line.
:kbd:`C-e`
*C-e*
@kindex C-e
Move to the end of the line. Move to the end of the line.
@ -619,42 +548,31 @@ These commands are used for editing text on a line. The :kbd:`C`
character means press the Control Key. character means press the Control Key.
:kbd:`C-h` / :kbd:`DEL`
*C-h*
*:kbd:`DEL`*
@kindex C-h
@kindex :kbd:`DEL`
Delete the character before point. Delete the character before point.
*C-d* :kbd:`C-d`
@kindex C-d
Delete the character after point. Delete the character after point.
*M-d* :kbd:`M-d`
@kindex M-d
Forward kill word. Forward kill word.
*C-w* :kbd:`C-w`
@kindex C-w
Backward kill word. Backward kill word.
*C-k* :kbd:`C-k`
@kindex C-k
Kill to the end of the line. Kill to the end of the line.
*C-u* :kbd:`C-u`
@kindex C-u
Kill line from the beginning, erasing input. Kill line from the beginning, erasing input.
*C-t* :kbd:`C-t`
@kindex C-t
Transpose character. Transpose character.
@ -665,42 +583,28 @@ There are several additional CLI commands for command line completions,
insta-help, and VTY session management. insta-help, and VTY session management.
:kbd:`C-c`
*C-c*
@kindex C-c
Interrupt current input and moves to the next line. Interrupt current input and moves to the next line.
*C-z* :kbd:`C-z`
@kindex C-z
End current configuration session and move to top node. End current configuration session and move to top node.
*C-n* :kbd:`C-n` / :kbd:`DOWN`
*:kbd:`DOWN`*
@kindex C-n
@kindex :kbd:`DOWN`
Move down to next line in the history buffer. Move down to next line in the history buffer.
*C-p* :kbd:`C-p` / :kbd:`UP`
*:kbd:`UP`*
@kindex C-p
@kindex :kbd:`UP`
Move up to previous line in the history buffer. Move up to previous line in the history buffer.
*TAB* :kbd:`TAB`
@kindex :kbd:`TAB`
Use command line completion by typing :kbd:`TAB`. Use command line completion by typing :kbd:`TAB`.
*?* :kbd:`?`
@kindex :kbd:`?`
You can use command line help by typing `help` at the beginning of You can use command line help by typing `help` at the beginning of
the line. Typing @kbd{?} at any point in the line will show possible the line. Typing :kbd:`?` at any point in the line will show possible
completions. completions.