Navigating

Containers

In the following example, tcp-keepalive and gnmi are containers.

tcp-keepalive {
    admin-state disable
    idle-time 600
    interval 15
    retries 4
}
gnmi {
    admin-state enable
    auto-config-save false
}

Lists

In the following example, the entire set of interfaces is a list.

        group "group-1" {
            connect-retry 600
            keepalive 33
        }
        group "group-2" {
            description "Text description for group-2"
            local-preference 8
        }

List entries

In the following example, group ‟group-2” is identified in this way.

router "Base" {
    bgp {
        group "group-1" {
            connect-retry 600
            keepalive 33
        }
        group "group-2" {
            description "Text description for group-2"
            local-preference 8
        }
    }
}

Keys

In the following example, ‟group-1” and ‟group-2” are unique identifiers.

router "Base" {
    bgp {
        group "group-1" {
            connect-retry 600
            keepalive 33
        }
        group "group-2" {
            description "Text description for group-2"
            local-preference 8
        }
    }
}

Leafs

tcp-keepalive {
    admin-state disable
    idle-time 600
    interval 15
    retries 4
}
gnmi {
    admin-state enable
    auto-config-save false
}

Leaf-list

In the following example, ‟policy” is a leaf-list element.

    policy ["policy-a" "policy-b" "policy-c"]

Leaf-list entries

In the following example, ‟policy-a”, ‟policy-b”, and ‟policy-c” are leaf-list entries.

    policy ["policy-a" "policy-b" "policy-c"]

Elements in the tree structure

In the following example, admin-state (leaf name), enable (enumerated value), and connect-retry (leaf name) are keywords, and ‟800” is a variable parameter.

*[ex:/configure router "Base" bgp]
A:admin@node-2# info
    admin-state enable
    connect-retry 800

tree detail command output

In the following, the bold elements are containers (or container lists) which contain leafs (or leaf-lists).

*[ex:/configure system]
A:admin@node-2# tree detail
+-- alarms
|   +-- admin-state <keyword>
|   +-- apply-groups <reference>
|   +-- apply-groups-exclude <reference>
|   +-- max-cleared <number>
+-- allow-boot-license-violations <boolean>
+-- apply-groups <reference>
+-- apply-groups-exclude <reference>
+-- boot-bad-exec <string>
+-- boot-good-exec <string>
+-- central-frequency-clock
|   +-- apply-groups <reference>
|   +-- apply-groups-exclude <reference>
|   +-- bits
|   |   +-- input
|   |   |   +-- admin-state <keyword>
|   |   +-- interface-type <keyword>
|   |   +-- output
|   |   |   +-- admin-state <keyword>
|   |   |   +-- line-length <keyword>
|   |   |   +-- ql-minimum <keyword>
|   |   |   +-- source <keyword>
|   |   |   +-- squelch <boolean>
|   |   +-- ql-override <keyword>
|   |   +-- ssm-bit <number>
|   +-- ptp
|   |   +-- admin-state <keyword>
|   +-- ql-minimum <keyword>
|   +-- ql-selection <boolean>
|   +-- ref-order
|   |   +-- fifth <keyword>
|   |   +-- first <keyword>
|   |   +-- fourth <keyword>
|   |   +-- second <keyword>
|   |   +-- third <keyword>

---snip---

Explicit configuration workflow

(ro)[/]

(ex)[/configure router "Base" bgp]

Implicit configuration workflow

[ro:/configure]

*[ex:/configure]

Two-line prompt usage

The following examples display the two-line prompt in different modes.

• prompt in operational mode

  [/]
  A:admin@node-2#
  

• prompt in the operational root, with exclusive configuration mode

  (ex)[/]
  A:admin@node-2#
  

• prompt in operational mode show router bgp

  [/show router "Base" bgp]
  A:admin@node-2#
  

• prompt in exclusive configuration mode configure router bgp

  (ex)[/configure router "Base" bgp]
  A:admin@node-2#
  

• prompt in exclusive configuration mode configure router bgp with uncommitted changes

  *(ex)[/configure router "Base" bgp]
  A:admin@node-2#
  

• implicit configuration workflow prompt for a session in private configuration mode, with a present working context of configure router bgp with uncommitted changes in the private candidate datastore, and the baseline datastore out-of-date

  !*[pr:/configure router "Base" bgp]
  A:admin@node-2#
  

Help displayed from the operational root level

[/]
A:admin@node-2# ?

 admin                 + Enter the administrative context for system operations
 bof                   + Enter the bof context
 clear                 + Clear statistics or reset operational state
 configure             + Enter the configuration context
 debug                 + Enter the debug context
 environment           + Configure the environment settings for this session
 file                  + Perform file operations
 li                    + Enter the lawful intercept context
 monitor               + Show operational information at an interval
 password              - Change the local user or an administrative password
 show                  + Show operational information
 state                 + Show state information
 tools                 + Enter the tools context for troubleshooting

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 edit-config           - Enter a configuration context
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 info                  - Show the information under the present working context
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 pyexec                - Execute a Python application
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

Help displayed in exclusive configuration mode

? help output lists additional commands available in exclusive configuration mode. The ? help is context-sensitive.

(ex)[/]
A:admin@node-2# ?

 admin                 + Enter the administrative context for system operations
 clear                 + Clear statistics or reset operational state
 configure             + Enter the configuration context
 environment           + Configure the environment settings for this session
 file                  + Perform file operations
 monitor               + Show operational information at an interval
 password              - Change the local user or an administrative password
 show                  + Show operational information
 state                 + Show state information
 tools                 + Enter the tools context for troubleshooting

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 edit-config           - Enter a configuration context
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 info                  - Show the information under the present working context
 insert                - Insert an element into a user-ordered list
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 pyexec                - Execute a Python application
 quit-config           - Exit the candidate configuration mode
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

 Configuration commands:
 annotate              - Annotate a configuration element with a comment
 commit                - Commit the candidate configuration
 compare               - Compare changes between datastores
 copy                  - Copy a configuration element to another
 discard               - Discard changes in the candidate datastore
 rename                - Rename a list element
 update                - Update the candidate baseline
 validate              - Validate changes in the candidate datastore

Help results depend on cursor position

The help results may depend on the cursor position. The following example shows the router command syntax, followed by available commands after entering the router context.

[ex:/configure]
A:admin@node-2# router?

 router [[router-name] <string>]

 [router-name]         - Administrative router name

 aggregates            + Enter the aggregates context
 allow-icmp-redirect   - Allow ICMP redirects on the management interface
 allow-icmp6-redirect  - Allow IPv6 ICMP redirects on the management interface
 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 autonomous-system     - AS number advertised to peers for this router
 bfd                   + Enter the bfd context
 bgp                   + Enable the bgp context
 bier                  + Enable the bier context
 class-forwarding      - Allow class-based forwarding over IGP shortcuts
 confederation         + Enter the confederation context
 description           - Text description
 dhcp-server           + Enter the dhcp-server context
 dns                   + Enter the dns context
 ecmp                  - Maximum equal-cost routes for routing table instance
 
---snip---

? output with more detail

In the following ? output, similar information is shown, with more details provided for configuring the router command, including the allowable string length and default value for the command.

[ex:/configure]
A:admin@node-2# router ?

 router [[router-name] <string>]

 [[router-name] <string>]
 <string> - <1..64 characters>
 Default  - "Base"

    Administrative router name

 aggregates            + Enter the aggregates context
 allow-icmp-redirect   - Allow ICMP redirects on the management interface
 allow-icmp6-redirect  - Allow IPv6 ICMP redirects on the management interface
 apply-groups          - Apply a configuration group at this level
 apply-groups-exclude  - Exclude a configuration group at this level
 autonomous-system     - AS number advertised to peers for this router
 bfd                   + Enter the bfd context
 bgp                   + Enable the bgp context
 bier                  + Enable the bier context
 class-forwarding      - Allow class-based forwarding over IGP shortcuts
 confederation         + Enter the confederation context
 description           - Text description
 dhcp-server           + Enter the dhcp-server context
 dns                   + Enter the dns context
 ecmp                  - Maximum equal-cost routes for routing table instance
 
 ---snip---

configuration commands in read-only configuration mode

 compare               - Compare changes between datastores
 validate              - Validate changes in the candidate datastore

configuration commands in exclusive configuration mode

 annotate              - Annotate a configuration element with a comment
 commit                - Commit the candidate configuration
 compare               - Compare changes between datastores
 copy                  - Copy a configuration element to another
 discard               - Discard changes in the candidate configuration
 load                  - Load contents into the candidate configuration
 rename                - Rename a list element
 replace               - Match and replace values in the candidate configuration
 rollback              - Roll back to a previous configuration
 update                - Update the candidate baseline
 validate              - Validate changes in the candidate configuration

[ex:/configure system security aaa remote-servers]
A:admin@node-2# tree
+-- apply-groups
+-- apply-groups-exclude
+-- ldap
|   +-- admin-state
|   +-- apply-groups
|   +-- apply-groups-exclude
|   +-- public-key-authentication
|   +-- route-preference
|   +-- server
|   |   +-- address
|   |   |   +-- apply-groups
|   |   |   +-- apply-groups-exclude
|   |   |   +-- port
|   |   +-- admin-state
|   |   +-- apply-groups
|   |   +-- apply-groups-exclude
|   |   +-- bind-authentication
|   |   |   +-- password
|   |   |   +-- root-dn
|   |   +-- search
|   |   |   +-- base-dn
|   |   +-- server-name
|   |   +-- tls-profile
|   +-- server-retry
|   +-- server-timeout
|   +-- use-default-template

---snip---

Displaying commands using Tab

[ex:/configure log]
A:admin@node-2# Press Tab

 accounting-policy        app-route-notifications  apply-groups
 apply-groups-exclude     event-damping            event-handling
 event-trigger            file                     filter
 foo                      log-events               log-id
 route-preference         services-all-events      snmp-trap-group
 syslog                   throttle-rate

 back                     delete                   edit-config
 enable                   exec                     exit
 history                  info                     insert
 logout                   oam                      ping
 pwc                      pyexec                   ssh
 telnet                   top                      traceroute
 tree

 annotate                 commit                   compare
 copy                     discard                  rename
 update                   validate

[ex:/configure log]
A:admin@node-2# event-damping Press Tab
 
 <event-damping>
 false
 true

 accounting-policy        app-route-notifications  apply-groups
 apply-groups-exclude     event-handling           event-trigger
 file                     filter                   log-events
 log-id                   route-preference         services-all-events
 snmp-trap-group          syslog                   throttle-rate

 delete                   insert

The ? help displays similar information but only displays global or configuration commands at the operational root or at the root of a command context.

Global commands displayed at the environment root context

[/environment]
A:admin@node-2# ?

 command-completion    + Enter the command-completion context
 console               + Enter the console context
 message-severity-     + Enter the message-severity-level context
  level
 more                  - Prompt to continue or stop when output text fills page
 progress-indicator    + Enter the progress-indicator context
 prompt                + Enter the prompt context
 time-display          - Time zone displayed before the prompt
 time-format           - Time format to display date and time

 Global commands:
 back                  - Move back one or more levels
 delete                - Delete an element
 edit-config           - Enter a candidate configuration mode
 enable                - Enable administrative mode
 exec                  - Execute commands from a file
 exit                  - Return to the previous context or to operational root
 history               - Show the command history
 info                  - Show the information under the present working context
 logout                - Exit the CLI session
 oam                   - Perform OAM tests
 ping                  - Ping an IP address or DNS name
 pwc                   - Show the present working context
 pyexec                - Execute a Python application
 ssh                   - SSH to an IP address or DNS name
 telnet                - Telnet to an IP address or DNS name
 top                   - Move to the top level of the context
 traceroute            - Show the route taken to an IP address or DNS name
 tree                  - Show the command tree under the present working context

Global commands available in the context

The global commands are not displayed in the environment prompt context, for example, although these commands are still available in the context.

[/environment prompt]
A:admin@node-2# ?

 context               - Show the current command context in the prompt
 newline               - Add a new line before every prompt line
 timestamp             - Show the timestamp before the first prompt line
 uncommitted-changes-  - Show an asterisk (*) when uncommitted changes exist
  indicator

[/environment prompt]
A:admin@node-2# info detail
    context true
    newline true
    timestamp false
    uncommitted-changes-indicator true

(ex)[/environment command-completion]
A:admin@node-2# info detail
    enter true
    space true
    tab true

A warning message is displayed when a session reaches one-half the value of the idle timeout, and another message is displayed when the idle timeout expires and the user is logged out.

[/]
A:admin@node-2# show users
===============================================================================
User                             Type      Login time           Idle time
  Session ID   (Router instance)
               From
===============================================================================
                                 Console         --             0d 21:44:02 --
  6            (--)
               --
admin                            SSHv2     16FEB2021 20:42:15   0d 00:00:04 --
  12           (management)
               192.168.144.97
admin                            SSHv2     16FEB2021 19:49:45   0d 00:00:00 --
 #11           (management)
               192.168.144.97
-------------------------------------------------------------------------------
Number of users: 2
'#' indicates the current active session
===============================================================================

--(more)--(p%)--(lines b-e/t)--

where

• p - indicates the position percentage in the output
• b - indicates the beginning line of the output on the screen
• e - indicates the ending line of the output on the screen
• t - indicates the total lines in the output

--(more)--(5%)--(lines 1-29/527)—

If the command output is still being generated, a question mark ("?") is displayed after the total lines and a warning indicates that the search is incomplete. These indicators are removed when the command output completes.

--(more)--(0%)--(lines 1-29/49833?)--(warning: search will be incomplete)--

The pager supports a high number of output lines. If the command output exceeds the pager memory, an asterisk (*) is displayed after the total lines and a warning indicates that the search is incomplete.

--(more)--(0%)--(lines 3578-3607/93151747*)--(warning: search will be incomplete)--

Searching with a string

The following string search matches any string containing "mda".

/mda

Searching with a regular expression

The following regular expression search matches the neighbor with the IP address that ends with 42 (neighbor "10.81.192.42").

/nei.*42

See Using regular expressions for more information about using regular expressions. The regular expression is highlighted until it is valid. Highlighting occurs when delimiters such as () and [] are unmatched, or when an asterisk (*) or question mark (?) is entered without a preceding expression.

MD-CLI path format

[ex:/configure card 1 mda 1]
A:admin@node-2# pwc
Present Working Context:
  configure
  card 1
  mda 1

Information displayed for a specified CLI path

[ex:/configure]
A:admin@node-2# info candidate detail units /configure system
 ## apply-groups
 ## apply-groups-exclude
 ## contact
    name "node-2"
 ## location
    icmp-vse false
    selective-fib false
 ## coordinates
 ## clli-code
    ospf-dynamic-hostnames false

---snip---

A configuration lock from either implicit or explicit configuration mode is required to display paths for a configuration region.

The state branch does not have a lock and can always be specified.

state branch

[ex:/configure]
A:admin@node-2# info detail /state system
    oper-name "node-2"
    base-mac-address aa:bb:cc:00:00:00
    platform "7750 SR-12"
    chassis-topology standalone
    crypto-module-version "SRCM 3.1"
 ## fabric-speed
    temperature-status ok
    fp-generation-fp2 false
    fp-generation-fp3 false
    fp-generation-fp4 false
    fp-generation-fp5 false
    system-profile none
    active-cpm-slot "A"

info command with a state path

The following example shows the use of the info command with a state path from operational mode.

[/]
A:admin@node-2# info /state system
    oper-name "node-2"
    base-mac-address aa:bb:cc:00:00:00
    platform "7750 SR-12"
    chassis-topology standalone
    crypto-module-version "SRCM 3.1"
    temperature-status ok
    fp-generation-fp2 false
    fp-generation-fp3 false
    fp-generation-fp4 false
    fp-generation-fp5 false
    system-profile none
    active-cpm-slot "A"

Establishing a configuration lock

In the next example, to use the info command in a state context to a configuration region, a configuration lock must be established.

[/state system]
A:admin@node-2# info /configure system
                      ^^^^^^^^^
MINOR: MGMT_CORE #2203: Invalid element - currently not allowed

[/state system]
A:admin@node-2# edit-config read-only
INFO: CLI #2066: Entering read-only configuration mode

(ro)[/state system]
A:admin@node-2# info /configure system
    name "node-2"
    management-interface {
        configuration-mode mixed
        snmp {
            admin-state disable
        }

---snip---

Supported commands with a CLI path parameter

(ex)[/state router "Base" bgp]
A:admin@node-2# info /state router bgp statistics routes-per-family ipv4
    remote-routes 45
    remote-active-routes 6
    backup-routes 0

*(ex)[/state router "Base" bgp]
A:admin@node-2# compare /configure system
-   name "test1"
+   name "test"

(ex)[/configure router "Base" bgp]
A:admin@node-2# discard /configure system

(ex)[/configure router "Base"]
A:admin@node-2# tree bgp group "mesh" add-paths ipv4
+-- receive
+-- send

[/]
A:admin@node-2# admin show configuration /configure router isis interface "system"
    passive true

(ex)[/configure policy-options]
A:admin@node-2# copy policy-statement "mytest" to /configure policy-options policy-statement "my_new_policy"

(ex)[/configure router "Base" bgp]
A:admin@node-2# rename /configure policy-options policy-statement "mytest" to "another_new_policy" 

Show the context-aware history

The history command output in this example shows configuration mode and configuration commands in the first output but does not in the second output in operational mode.

[ex:/configure router "Base" interface "NEW INTERFACE"]
A:admin@node-2# history

     1 10:30 show version
     2 10:30 ping 192.168.0.10 count 1
     3 10:30 info state system bootup last-boot-config-version
     4 10:31 configure exclusive
     5 10:31 router interface "NEW INTERFACE"
     6 10:31 commit
     7 10:31 history

[ex:/configure router "Base" interface "NEW INTERFACE"]
A:admin@node-2# exit all

[/]
A:admin@node-2# history

     1 10:30 show version
     2 10:30 ping 192.168.0.10 count 1
     3 10:30 info state system bootup last-boot-config-version
     4 10:31 configure exclusive
     7 10:31 history
     8 10:31 exit all
     9 10:32 history

Show all commands in the history

The history all command shows all commands in the history, regardless of the current mode. This example shows configuration mode and configuration commands in operational mode.

[/]
A:admin@node-2# history all

     1 10:30 show version
     2 10:30 ping 192.168.0.10 count 1
     3 10:30 info state system bootup last-boot-config-version
     4 10:31 configure exclusive
     5 10:31 router interface "NEW INTERFACE"
     6 10:31 commit
     7 10:31 history
     8 10:31 exit all
     9 10:32 history all

Show commands in the history

To show the history without the entry numbers and execution times for copying and pasting, use the history commands-only command.

[/]
A:admin@node-2# history commands-only

show version
ping 192.168.0.10 count 1
info state system bootup last-boot-config-version
configure exclusive
history
exit all
history commands-only

Recall by entry number

[/]
A:admin@node-2# !2

[/]
A:admin@node-2# ping 192.168.0.10 count 1
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=121 time=1.58ms.

---- 192.168.0.10 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.58ms, avg = 1.58ms, max = 1.58ms, stddev = 0.000ms

Recall by search string

[/]
A:admin@node-2# !192

[/]
A:admin@node-2# ping 192.168.0.10 count 1
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=121 time=1.39ms.

---- 192.168.0.10 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.39ms, avg = 1.39ms, max = 1.39ms, stddev = 0.000ms

[/]
A:admin@node-2# !ping

[/]
A:admin@node-2# ping 192.168.0.10 count 1
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=121 time=1.27ms.

---- 192.168.0.10 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.27ms, avg = 1.27ms, max = 1.27ms, stddev = 0.000ms

Recall previous command

[/]
A:admin@node-2# !!

[/]
A:admin@node-2# ping 192.168.0.10 count 1
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=121 time=1.29ms.

---- 192.168.0.10 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.29ms, avg = 1.29ms, max = 1.29ms, stddev = 0.000ms

Substitute previous element

[/]
A:admin@node-2# ping 192.168.0.10
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=114 time=120ms.
64 bytes from 192.168.0.10: icmp_seq=2 ttl=114 time=120ms.
64 bytes from 192.168.0.10: icmp_seq=3 ttl=114 time=120ms.
64 bytes from 192.168.0.10: icmp_seq=4 ttl=114 time=120ms.
64 bytes from 192.168.0.10: icmp_seq=5 ttl=114 time=120ms.

---- 192.168.0.10 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 120ms, avg = 120ms, max = 120ms, stddev = 0.091ms

[/]
A:admin@node-2# traceroute !$

[/]
A:admin@node-2# traceroute 192.168.0.10
traceroute to 135.92.55.3, 30 hops max, 40 byte packets
  1  10.0.0.1 (10.0.0.1)    0.948 ms  0.754 ms  0.825 ms
  2  192.168.0.10 (192.168.0.10)    1.14 ms  1.08 ms  9.92 ms

Recall and enter additional elements

Additional elements can be entered after recalled commands to add to the command line. ? help and Tab command completion are supported after recalled commands. In this example, the previous ping command is recalled and size 1500 is added.

[/]
A:admin@cses-V93# !ping size 1500 

[/]
A:admin@node-2# ping 192.168.0.10 count 1 size 1500
PING 192.168.0.10 1500 data bytes
1508 bytes from 192.168.0.10: icmp_seq=1 ttl=63 time=3.30ms.

---- 135.92.55.3 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 3.30ms, avg = 3.30ms, max = 3.30ms, stddev = 0.000ms

The history can be displayed to edit the command before execution by entering ! (exclamation mark) followed by an entry number, a string search, or ! for the previous command followed by :p. Esc+. substitutes the last element that was entered in the previous command. The following history is used at the beginning of each of these examples, and the ☐ character indicates the cursor position after the command is displayed.

[/]
A:admin@node-2# history

     1 10:30 show version
     2 10:30 ping 192.168.0.10 count 1

Display entry number

[/]
A:admin@node-2# !2:p

[/]
A:admin@node-2# ping 192.168.0.10 count 1☐

Display entry with string search

[/]
A:admin@node-2# !192:p

[/]
A:admin@node-2# ping 192.168.0.10 count 1☐

[/]
A:admin@node-2# !ping:p

[/]
A:admin@node-2# ping 192.168.0.10 count 1☐

Display previous command

[/]
A:admin@node-2# !!:p

[/]
A:admin@node-2# ping 192.168.0.10 count 1☐

Display last element

[/]
A:admin@node-2# traceroute 192.168.0.10☐  Esc+. was entered and "192.168.0.10" is displayed

The history can be searched backward interactively with a string search when Ctrl-R is entered. Additional Ctrl-R keystrokes search backward again, and (wrapped) is displayed when the search wraps. Pressing Enter exits search and executes the command, and Ctrl-C exits search without execution. The following history is used at the beginning of the following example.

[/]
A:admin@node-2# history

     1 10:30 show version
     2 10:30 ping 192.168.0.10 count 1

Backward search

[/]
History search '':  Entering Ctrl-R displays the search prompt 

[/]
History search 'pi': ping 192.168.0.10 count 1  Entering "pi" displays the first match

[/]
History search 'pi' (wrapped): ping 192.168.0.10 count 1  Entering Ctrl-R again indicates the search wrapped

[/]
A:admin@node-2# ping 192.168.0.10 count 1  Enter exits search and executes the command
PING 192.168.0.10 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=1 ttl=121 time=1.29ms.

---- 192.168.0.10 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.29ms, avg = 1.29ms, max = 1.29ms, stddev = 0.000ms