T – W Commands

terminal

To set the number of lines, and the width of the lines, displayed in the terminal window, use the terminal command.

terminal { length lines| width characters}

Syntax Description

length lines

The number of lines displayed in the terminal window. Valid values range from 0 to 511 lines. Enter 0 to eliminate pausing.

width characters

The number of characters per line displayed in the terminal window. Valid values range from 24 to 511 characters.

Command Modes

Any command mode

Command History

Release

Modification

1.1(1)

Command added.

Usage Guidelines

Use this command to set the number of lines, and the number of characters per line, to be displayed in the terminal window.

Examples

This example shows how to set the number of lines displayed in the terminal window to 12: 

FP9300-A# terminal length 12
FP9300-A *# commit-buffer
FP9300-A#

Related Commands

Command

Description

set cli

Specifies whether command output lines wrap or truncate, whether table headers are displayed, and whether commas or spaces are used to separate fields in command output tables.

top

To enter root (EXEC) from any mode, use the top command.

top

Syntax Description

This command has no arguments or keywords.

Command Modes

Any command mode

Command History

Release

Modification

1.1(1)

Command added.

Examples

This example shows how to enter root from any mode: 

FP9300-A /system/services # top
                                       
FP9300-A#

Related Commands

Command

Description

up

Moves up one mode.

traceroute (connect local-mgmt)

To trace the route to another device on the network using its host name or IPv4 address, use the traceroute command.

traceroute { hostname| IPv4_address} [ source header_IP]

Syntax Description

hostname| IPv4_address

The host name or IP address of the network device to be contacted. The maximum number of characters allowed for the host name is 510.

source header_IP

(Optional) Use this keyword to specify the device IP address to be included in the packet headers.

Command Modes

connect local-mgmt

Command History

Release

Modification

1.1(1)

Command added.

Usage Guidelines

Use this command to trace the route of IP packets to a network host.

If you do not specify the source IP address to be included in the packet headers, the management port address is used.

Examples

This example shows how to connect to the local management CLI and then trace the route to another device on the network: 

firepower# connect local-mgmt
firepower(local-mgmt)# traceroute 198.51.100.10
traceroute to 198.51.100.10 (198.51.100.10), 30 hops max, 40 byte packets
 1  198.51.100.57 (198.51.100.57)  0.640 ms  0.737 ms  0.686 ms
 2  net1-gw1-13.cisco.com (198.51.100.101)  2.050 ms  2.038 ms  2.028 ms
 3  net1-sec-gw2.cisco.com (198.51.100.201)  0.540 ms  0.591 ms  0.577 ms
 4  net1-fp9300-19.cisco.com (198.51.100.108)  0.336 ms  0.267 ms  0.289 ms

firepower(local-mgmt)#

Related Commands

Command

Description

ping

Pings the device at a specified destination (IPv4 address).

traceroute6 (connect local-mgmt)

To trace the route to another device on the network using its host name or IPv6 address, use the traceroute6 command.

traceroute6 { hostname| ipv6_address} [ source header_ip]

Syntax Description

hostname| ipv6_address

The host name or IPv6 address of the network device to be contacted. The maximum number of characters allowed for the host name is 510.

source header_ip

(Optional) Use this keyword to specify the device IP address to be included in the packet headers.

Command Modes

connect local-mgmt

Command History

Release

Modification

1.1(1)

Command added.

Usage Guidelines

Use this command to trace the route of IP packets to a network host.

If you do not specify the source IP address to be included in the packet headers, the management port address is used.

Examples

This example shows how to connect to the local management CLI and then trace the route to another device on the network: 

firepower# connect local-mgmt
firepower(local-mgmt)# traceroute 2001:DB8:1::1
traceroute to 2001:DB8:1::1 (2001:DB8:1::1), 30 hops max, 40 byte packets
 1  2001:DB8:1::4 (2001:DB8:1::4)  0.640 ms  0.737 ms  0.686 ms
 2  net1-gw1-13.cisco.com (2001:DB8:1::6)  2.050 ms  2.038 ms  2.028 ms
 3  net1-sec-gw2.cisco.com (2001:DB8:1::8)  0.540 ms  0.591 ms  0.577 ms
 4  net1-fp9300-19.cisco.com (2001:DB8:1::7)  0.336 ms  0.267 ms  0.289 ms

firepower(local-mgmt)#

Related Commands

Command

Description

ping6

Pings the device at a specified destination (IPv6 address).

up

To move up one level in the command-mode hierarchy, use the up command.

up

Syntax Description

This command has no arguments or keywords.

Command Modes

Any command mode

Command History

Release

Modification

1.1(1)

Command added.

Examples

This example shows how to move up one mode: 

FP9300-A /org/service-profile # up                                  
FP9300-A /org #

Related Commands

Command

Description

exit

Exits the current CLI session and disconnects from the device, or exits from a connected object mode and returns to the root (EXEC) level.

top

Enters root (EXEC) from any mode.

verify platform-pack

To manually verify the integrity of a downloaded FXOS platform bundle, use the verify platform-pack command.

verify platform-pack version version_number

Syntax Description

version version_number

Specifies the version number of the platform package to verify.

Command Modes

Firmware mode

Command History

Release

Modification

1.1(1)

Command added.

Usage Guidelines

The integrity of the image is automatically verified when a new image is downloaded to the Firepower 4100/9300 chassis; use this command to later manually verify the integrity of a downloaded image.

You can use the show validate-task or the show validation package command to determine the desired package version number.

You also can use the show validate-task command to monitor the verification process. The output display does not refresh automatically, so you may have to enter the command multiple times.

Examples

This example shows how to verify a specific platform package: 

FP9300-A# scope firmware
FP9300-A /firmware # show validation package 
Firmware Package 2.2(2.19):
    Validation Time Stamp: 2017-10-26T14:34:24.925
    Pack Name: fxos-k9.2.2.2.19.SPA
    Validation State: None
    Overall Status Code: Ok

Firmware Package 2.3(1.51):
    Validation Time Stamp: 2017-10-25T16:53:30.914
    Pack Name: fxos-k9.2.3.1.51.SPA
    Validation State: None
    Overall Status Code: Ok
FP9300-A /firmware # verify platform-pack version 2.3(1.51)
The currently installed FXOS platform software package is 2.3(1.51)
All the Security Modules will be installed with these software components:
    Security Module Adapter  4.0(1.67)
    Security Module BIOS     FXOSSM2.1.3.1.13.0927171811
    Security Module FXOS     2.3(1.50)

INFO: There is no service impact to install this FXOS platform software 2.3(1.51)


Verifying FXOS platform software package 2.3(1.51). Verification could take several minutes.
Do you want to proceed? (yes/no) [yes]:

Related Commands

Command

Description

download image

Downloads an FXOS software image to the Firepower 4100/9300 chassis.

show validate-task

Displays the status of the image verification process.

where

To determine where you are in the CLI command hierarchy, use the where command.

where

Syntax Description

This command has no arguments or keywords.

Command Modes

Any command mode

Command History

Release

Modification

1.1(1)

Command added.

Examples

This example shows how to determine where you are in the CLI: 

FP9300-A /org/service-profile # where
Mode: /org/service-profile
Mode Data:
       scope org
       enter org org10                                       
       enter service-profile sp10 instance  
FP9300-A /org/service-profile #

Related Commands

Command

Description

top

Moves to top (EXEC) level from any mode.

up

Moves up one mode.