Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3
CFR Commands: exception core-file -- ip ftp passive

Table Of Contents

exception core-file

exception crashinfo buffersize

exception crashinfo file

exception dump

exception linecard

exception memory

exception protocol

exception region-size

exception spurious-interrupt

exec

exec-banner

exec-character-bits

exec-timeout

execute-on

exit (EXEC)

exit (global)

file prompt

filter-for-history

format

frequency

fsck

full-help

help

history

history size

hold-character

hops-of-statistics-kept

hostname

hours-of-statistics-kept

http-raw-request

insecure

international

ip bootp server

ip director cache refresh

ip director cache size

ip director cache time

ip director default priorities

ip director default weights

ip director dfp security

ip director dfp

ip director drp rttprobe

ip director drp synchronized

ip director host priority

ip director host weights

ip director server availability

ip director server port availability

ip dns server

ip drp domain

ip finger

ip ftp passive


exception core-file

To specify the name of the core dump file, use the exception core-file command in global configuration mode. To return to the default core filename, use the no form of this command.

exception core-file filename

no exception core-file

Syntax Description

filename

Name of the core dump file saved on the server.


Defaults

The core file is named hostname-core, where hostname is the name of the router.

Command Modes

Global configuration

Command History

Release
Modification

10.2

This command was introduced.


Usage Guidelines

If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the router's memory is larger than 16 MB, the whole core file will not be copied to the server. Therefore, use rcp or FTP to dump the core file.


Caution Use the exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

Examples

In the following example, the router is configured to use FTP to dump a core file named dumpfile to the FTP server at 172.17.92.2 when it crashes:

Router(config)# ip ftp username red 
Router(config)# ip ftp password blue 
Router(config)# exception protocol ftp 
Router(config)# exception dump 172.17.92.2 
Router(config)# exception core-file dumpfile 

Related Commands

Command
Description

exception dump

Causes the router to dump a core file to a particular server when the router crashes.

exception memory

Causes the router to create a core dump and reboot when certain memory size parameters are violated.

exception protocol

Configures the protocol used for core dumps.

exception spurious-interrupt

Causes the router to create a core dump and reload after a specified number of spurious interrupts.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the username for FTP connections.


exception crashinfo buffersize

To change the size of the buffer used for crashinfo files, use the exception crashinfo buffersize command in global configuration mode. To revert to the default buffersize, use the no form of this command.

exception crashinfo buffersize kilobytes

no exception crashinfo buffersize kilobytes

Syntax Description

kilobytes

Sets the size of the buffersize to the specified value within the range of 32 to 100 kilobytes. The default is 32KB.


Defaults

Crashinfo buffer is 32KB.

Command Modes

Global configuration

Command History

Release
Modification

12.2(4)T, 12.2(11)

This command was introduced for the Cisco 3600 series only (3620, 2640, and 3660 platforms).

12.2(13)T

This command was implemented in 6400-NSP images.


Usage Guidelines

The crashinfo file saves information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure, and the file is created the next time you boot the Cisco IOS image after the failure (instead of while the system is failing).

Examples

In the following example, the crashinfo buffer is set to 100 KB:

Router(config)# exception crashinfo buffersize 100

Related Commands

Command
Description

exception crashinfo file

Enables the creation of a diagnostic file at the time of unexpected system shutdowns.


exception crashinfo file

To enable the creation of a diagnostic file at the time of unexpected system shutdowns, use the exception crashinfo file command in global configuration mode. To disable the creation of crashinfo files, use the no form of this command.

exception crashinfo file device:filename

no exception crashinfo file device:filename

Syntax Description

device:filename

Specifies the flash device and file name to be used for storing the diagnostic information. The colon is required.


Defaults

Enabled

Command Modes

Global configuration

Command History

Release
Modification

12.2(4)T, 12.2(11)

This command was introduced for the Cisco 3600 series only.

12.2(13)T

This command was implemented in 6400-NSP images.


Usage Guidelines

The "crashinfo" file saves information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure, and the file is created the next time you boot the IOS image after the failure (instead of while the system is failing). The filename will be filename_yyyymmdd-hhmmss, where y is year, m is month, d is date, h is hour, and s is seconds.

Examples

In the following example, a crashinfo file called "crashdata" will be created in the default flash memory device if a system crash occurs:

Router(config)# exception crashinfo file flash:crashinfo 

Related Commands

Command
Description

exception crashinfo buffersize

Changes the size of the crashinfo buffer.


exception dump

To configure the router to dump a core file to a particular server when the router crashes, use the exception dump command in global configuration mode. To disable core dumps, use the no form of this command.

exception dump ip-address

no exception dump

Syntax Description

ip-address

IP address of the server that stores the core dump file.


Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines


Caution Use the exception dump command only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the router's memory is larger than 16 MB, the whole core file will not be copied to the server. Therefore, use rcp or FTP to dump the core file.

The core dump is written to a file named hostname-core on your server, where hostname is the name of the router. You can change the name of the core file by configuring the exception core-file command.

This procedure can fail for certain types of system crashes. However, if successful, the core dump file will be the size of the memory available on the processor (for example, 16 MB for a CSC/4).

Examples

In the following example, a user configures a router to use FTP to dump a core file to the FTP server at 172.17.92.2 when it crashes:

Router(config)# ip ftp username red 
Router(config)# ip ftp password blue 
Router(config)# exception protocol ftp 
Router(config)# exception dump 172.17.92.2 
Router(config)# exception core-file dumpfile 

Related Commands

Command
Description

exception core-file

Specifies the name of the core dump file.

exception memory

Causes the router to create a core dump and reboot when certain memory size parameters are violated.

exception protocol

Configures the protocol used for core dumps.

exception spurious-interrupt

Causes the router to create a core dump and reload after a specified number of spurious interrupts.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the username for FTP connections.

ip rcmd remote-username

Configures the remote username to be used when requesting a remote copy using rcp.


exception linecard

To enable storing of crash information for a line card and optionally specify the type and amount of information stored, use the exception linecard command in global configuration mode. To disable the storing of crash information for the line card, use the no form of this command.

exception linecard {all | slot slot-number} [corefile filename | main-memory size [k | m] | queue-ram size [k | m] | rx-buffer size [k | m] | sqe-register-rx | sqe-register-tx | tx-buffer size [k | m]]

no exception linecard

Syntax Description

all

Stores crash information for all line cards.

slot slot-number

Stores crash information for the line card in the specified slot. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008 router.

corefile filename

(Optional) Stores the crash information in the specified file in NVRAM. The default filename is hostname-core-slot-number (for example, c12012-core-8).

main-memory size

(Optional) Stores the crash information for the main memory on the line card and specifies the size of the crash information. Size of the memory to store is 0 to 268435456.

queue-ram size

(Optional) Stores the crash information for the queue RAM memory on the line card and specifies the size of the crash information. Size of the memory to store can be from 0 to 1048576.

rx-buffer size

tx-buffer size

(Optional) Stores the crash information for the receive and transmit buffer on the line card and specifies the size of the crash information. Size of the memory to store can be from 0 to 67108864.

sqe-register-rx

sqe-register-tx

(Optional) Stores crash information for the receive or transmit silicon queueing engine registers on the line card.

k

m

(Optional) The k option multiplies the specified size by 1K (1024), and the m option multiplies the specified size by 1M (1024*1024).


Defaults

No crash information is stored for the line card.

If enabled with no options, the default is to store 256 MB of main memory.

Command Modes

Global configuration

Command History

Release
Modification

11.2 GS

This command was introduced for Cisco 12000 series Gigabit Switch Routers (GSRs).


Usage Guidelines

Use caution when enabling the exception linecard global configuration command. Enabling all options could cause a large amount (150 to 250 MB) of crash information to be sent to the server.


Caution Use the exception linecard global configuration command only when directed by a technical support representative. Only enable options that the technical support representative requests you to enable. Technical support representatives need to be able to look at the crash information from the line card to troubleshoot serious problems on the line card. The crash information contains all the line card memory information including the main memory and transmit and receive buffer information. .

Examples

In the following example, the user enables the storing of crash information for line card 8. By default, 256 MB of main memory is stored.

Router(config)# exception linecard slot 8 

exception memory

To cause the router to create a core dump and reboot when certain memory size parameters are violated, use the exception memory command in global configuration mode. To disable the rebooting and core dump, use the no form of this command.

exception memory {fragment size | minimum size}

no exception memory {fragment | minimum}

Syntax Description

fragment size

The minimum contiguous block of memory in the free pool, in bytes.

minimum size

The minimum size of the free memory pool, in bytes.


Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines

This command is used to troubleshoot memory leaks.

The size is checked every 60 seconds. If you enter a size that is greater than the free memory, a core dump and router reload is generated after 60 seconds.


Caution Use the exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

The exception dump command must be configured in order to generate a core dump file. If the exception dump command is not configured, the router reloads without generating a core dump.

Examples

In the following example, the user configures the router to monitor the free memory. If the amount of free memory falls below 250,000 bytes, the router will dump the core file and reload.

Router(config)# exception dump 131.108.92.2
Router(config)# exception core-file memory.overrun 
Router(config)# exception memory minimum 250000 

Related Commands

Command
Description

exception core-file

Specifies the name of the core dump file.

exception dump

Configures the router to dump a core file to a particular server when the router crashes.

exception protocol

Configures the protocol used for core dumps.

exception region-size

Specifies the size of the region for the exception-time memory pool.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the username for FTP connections.


exception protocol

To configure the protocol used for core dumps, use the exception protocol command in global configuration mode. To configure the router to use the default protocol, use the no form of this command.

exception protocol {ftp | rcp | tftp}

no exception protocol

Syntax Description

ftp

Uses FTP for core dumps.

rcp

Uses rcp for core dumps.

tftp

Uses TFTP for core dumps. This is the default.


Defaults

TFTP

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines


Caution Use the exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the router's memory is larger than 16 MB, the whole core file will not be copied to the server. Therefore, use rcp or FTP to dump the core file.

Examples

In the following example, the user configures a router to use FTP to dump a core file to the FTP server at 172.17.92.2 when it crashes:

Router(config)# ip ftp username red 
Router(config)# ip ftp password blue 
Router(config)# exception protocol ftp 
Router(config)# exception dump 172.17.92.2 

Related Commands

Command
Description

exception core-file

Specifies the name of the core dump file.

exception dump

Causes the router to dump a core file to a particular server when the router crashes.

exception memory

Causes the router to create a core dump and reboot when certain memory size parameters are violated.

exception spurious-interrupt

Causes the router to create a core dump and reload after a specified number of spurious interrupts.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the username for FTP connections.


exception region-size

To specify the size of the region for the exception-time memory pool, use the exception region-size command in global configuration mode. To use the default region size, use the no form of this command.

exception region-size size

no exception region-size

Syntax Description

size

The size of the region for the exception-time memory pool.


Defaults

16,384 bytes

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines


Caution Use the exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

The exception region-size command is used to define a small amount of memory to serve as a fallback pool when the processor memory pool is marked corrupt. The exception memory command must be used to allocate memory to perform a core dump.

Examples

In the following example, the region size is set at 1024:

Router(config)# exception region-size 1024

Related Commands

Command
Description

exception core-file

Specifies the name of the core dump file.

exception dump

Configures the router to dump a core file to a particular server when the router crashes.

exception memory

Causes the router to create a core dump and reboot when certain memory size parameters are violated.

exception protocol

Configures the protocol used for core dumps.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the username for FTP connections.


exception spurious-interrupt

To configure the router to create a core dump and reload after a specified number of spurious interrupts, use the exception spurious-interrupt command in global configuration mode. To disable the core dump and reload, use the no form of this command.

exception spurious-interrupt [number]

no exception spurious-interrupt

Syntax Description

number

(Optional) A number from 1 to 4294967295 that indicates the maximum number of spurious interrupts to include in the core dump before reloading.


Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

10.3

This command was introduced.


Usage Guidelines


Caution Use the exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel that have access to source code and detailed memory maps.

If you use TFTP to dump the core dump file to a server, the router will only dump the first 16 MB of the file. If the router's memory is larger than 16 MB, the whole core file will not be copied to the server. Therefore, use rcp or FTP to dump the core file.

Examples

In the following example, the user configures a router to create a core dump with a limit of two spurious interrupts:

Router(config)# exception spurious-interrupt 2

Related Commands

Command
Description

exception core-file

Specifies the name of the core dump file.

ip ftp password

Specifies the password to be used for FTP connections.

ip ftp username

Configures the user name for FTP connections.


exec

To allow an EXEC process on a line, use the exec command in line configuration mode. To turn off the EXEC process for the specified line, use the no form of this command.

exec

no exec

Syntax Description

This command has no arguments or keywords.

Defaults

The EXEC processes is enabled on all lines.

Command Modes

Line configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

When you want to allow only an outgoing connection on a line, use the no exec command.

The no exec command allows you to disable the EXEC process for connections which may attempt to send unsolicited data to the router. (For example, the control port of a rack of modems attached to an auxiliary port of router.) When certain types of data are sent to a line connection, an EXEC process can start, which makes the line unavailable.

When a user tries to Telnet to a line with the EXEC process disabled, the user will get no response when attempting to log on.

Examples

The following example disables the EXEC process on line 7.

Router(config)# line 7 
Router(config-line)# no exec 

exec-banner

To reenable the display of EXEC and message-of-the-day (MOTD) banners on the specified line or lines, use the exec-banner command in line configuration mode. To suppress the banners on the specified line or lines, use the no form of this command.

exec-banner

no exec-banner

Syntax Description

This command has no arguments or keywords.

Defaults

Enabled on all lines

Command Modes

Line configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

This command determines whether the router will display the EXEC banner and the message-of-the-day (MOTD) banner when an EXEC session is created. These banners are defined with the banner exec and banner motd global configuration commands. By default, these banner are enabled on all lines. Disable the EXEC and MOTD banners using the no exec-banner command.

This command has no effect on the incoming banner, which is controlled by the banner incoming command.

The MOTD banners can also be disabled by the no motd-banner line configuration command, which disables MOTD banners on a line. If the no exec-banner command is configured on a line, the MOTD banner will be disabled regardless of whether the motd-banner command is enabled or disabled. Table 24 summarizes the effects of the exec-banner command and the motd-banner command.

Table 24 Banners Displayed Based On exec-banner and motd-banner Combinations

 
exec-banner (default)
no exec-banner
motd-banner (default)

MOTD banner

EXEC banner

None

no motd-banner

EXEC banner

None


For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner command or no motd-banner command is configured. Table 25 summarizes the effects of the exec-banner command and the motd-banner command for reverse Telnet connections.

Table 25 Banners Displayed Based On exec-banner and motd-banner Combinations
for Reverse Telnet Sessions to Async Lines 

 
exec-banner (default)
no exec-banner
motd-banner (default)

MOTD banner

Incoming banner

Incoming banner

no motd-banner

Incoming banner

Incoming banner


Examples

The following example suppresses the EXEC and MOTD banners on virtual terminal lines 0 to 4:

Router(config)# line vty 0 4 
Router(config-line)# no exec-banner 

Related Commands

Command
Description

banner exec

Defines and enables a customized banner to be displayed whenever the EXEC process is initiated.

banner incoming

Defines and enables a customized message to be displayed when there is an incoming connection to a terminal line from a host on the network.

banner motd

Defines and enables a customized message-of-the-day banner.

motd-banner

Controls (enables or disables) the display of message-of-the-day banners on a specified line or lines.


exec-character-bits

To configure the character widths of EXEC and configuration command characters, use the exec-character-bits command in line configuration mode. To restore the default value, use the no form of this command.

exec-character-bits {7 | 8}

no exec-character-bits

Syntax Description

7

Selects the 7-bit character set. This is the default.

8

Selects the full 8-bit character set for use of international and graphical characters in banner messages, prompts, and so on.


Defaults

7-bit ASCII character set

Command Modes

Line configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

Setting the EXEC character width to 8 allows you to use special graphical and international characters in banners, prompts, and so on. However, setting the EXEC character width to 8 bits can cause failures. If a user on a terminal that is sending parity enters the help command, an "unrecognized command" message appears because the system is reading all 8 bits, and the eighth bit is not needed for the help command.


Note If you are using the autoselect function, set the activation character to the default (Return) and the value for exec-character-bits to 7. If you change these defaults, the application will not recognize the activation request.


Examples

The following example enables full 8-bit international character sets, except for the console, which is an ASCII terminal. It illustrates use of the default-value exec-character-bits global configuration command and the exec-character-bits line configuration command.

Router(config)# default-value exec-character-bits 8
Router(config)# line 0
Router(config-line)# exec-character-bits 7

Related Commands

Command
Description

default-value exec-character-bits

Defines the EXEC character width for either 7 bits or 8 bits.

default-value special-character-bits

Configures the flow control default value from a 7-bit width to an 8-bit width.

length

Sets the terminal screen length.

terminal exec-character-bits

Locally changes the ASCII character set used in EXEC and configuration command characters for the current session.

terminal special-character-bits

Changes the ASCII character widths to accept special characters for the current terminal line and session.


exec-timeout

To set the interval that the EXEC command interpreter waits until user input is detected, use the exec-timeout command in line configuration mode. To remove the timeout definition, use the no form of this command.

exec-timeout minutes [seconds]

no exec-timeout

Syntax Description

minutes

Integer that specifies the number of minutes. The default is 10 minutes.

seconds

(Optional) Additional time intervals in seconds.


Defaults

10 minutes

Command Modes

Line configuration

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

If no input is detected during the interval, the EXEC facility resumes the current connection. If no connections exist, the EXEC facility returns the terminal to the idle state and disconnects the incoming session.

To specify no timeout, enter the exec-timeout 0 0 command.

Examples

The following example sets a time interval of 2 minutes, 30 seconds:

Router(config)# line console
Router(config-line)# exec-timeout 2 30 

The following example sets a time interval of 10 seconds:

Router(config)# line console 
Router(config-line)# exec-timeout 0 10 

execute-on

To execute commands on a line card, use the execute-on command in privileged EXEC mode.

execute-on {slot slot-number | all | master} command

Syntax Description

slot slot-number

Executes the command on the line card in the specified slot. Slot numbers can be chosen from the following ranges:

Cisco 12012 router: 0 to 11

Cisco 12008 access server: 0 to 7

Cisco AS5800 access server: 0 to 13

all

Executes the command on all line cards.

master

(AS5800 only) Executes the designated command on a Dial Shelf Controller (DSC). Do not use this option; it is used for technical support troubleshooting only.

command

Cisco IOS command to remotely execute on the line card.


Command Modes

Privileged EXEC

Command History

Release
Modification

11.2 GS

This command was introduced to support Cisco 12000 series Gigabit Switch Routers.

11.3(2)AA

This command was implemented in images for the Cisco AS5800 series.


Usage Guidelines

Use this command to execute a command on one or all line cards to monitor and maintain information on one or more line cards (for example, a line card in a specified slot on a dial shelf). This allows you to issue commands remotely; that is, to issue commands without needing to log in to the line card directly. The all form of the command allows you to issue commands to all the line cards without having to log in to each in turn.

Though this command does not have a no form, note that it is possible to use the no form of the remotely executed commands used in this command.


Tips This command is useful when used with show EXEC commands (such as show version), because you can verify and troubleshoot the features found only on a specific line card. Please note, however, that because not all statistics are maintained on the line cards, the output from some of the show commands might not be consistent.


Cisco 12000 GSR Guidelines and Restrictions

You can use the execute-on privileged EXEC command only from Cisco IOS software running on the GRP card.


Timesaver Though you can use the attach privileged EXEC command to execute commands on a specific line card, using the execute-on slot command saves you some steps. For example, first you must use the attach command to connect to the Cisco IOS software running on the line card. Next you must issue the command. Finally you must disconnect from the line card to return to the Cisco IOS software running on the GRP card. With the execute-on slot command, you can perform three steps with one command. In addition, the execute-on all command allows you to perform the same command on all line cards simultaneously.


Cisco AS5800 Guidelines and Restrictions

The purpose of the command is to conveniently enable certain commands to be remotely executed on the dial shelf cards from the router without connecting to each line card. This is the recommended procedure, because it avoids the possibility of adversely affecting a good configuration of a line card in the process. The execute-on command does not give access to every Cisco IOS command available on the Cisco AS5800 access server. In general, the purpose of the execute-on command is to provide access to statistical reports from line cards without directly connecting to the dial shelf line cards.


Caution Do not use this command to change configurations on dial shelf cards, because such changes will not be reflected in the router shelf.

Using this command makes it possible to accumulate inputs for inclusion in the show tech-support command.

The master form of the command can run a designated command remotely on the router from the DSC card. However, using the console on the DSC is not recommended. It is used for technical support troubleshooting only.

The show tech-support command for each dial shelf card is bundled into the router shelf's show tech-support command via the execute-on facility.

The execute-on command also support interactive commands such as the following:

router: execute-on slave slot slot ping

The execute-on command has the same limitations and restrictions as a vty telnet client has; that is, it cannot reload DSC using the following command:

router: execute-on slave slot slot reload

You can use the execute-on command to enable remote execution of the commands included in the following partial list:

debug dsc clock

show context

show diag

show environment

show dsc clock

show dsi

show dsip

show tech-support

Examples

In the following example, the user executes the show controllers command on the line card in slot 4 of a Cisco 12000 series GSR:

Router# execute-on slot 4 show controllers

========= Line Card (Slot 4) =======

Interface POS0
Hardware is BFLC POS
lcpos_instance struct   6033A6E0
RX POS ASIC addr space  12000000
TX POS ASIC addr space  12000100
SUNI framer addr space  12000400
SUNI rsop intr status   00
CRC16 enabled, HDLC enc, int clock
no loop

Interface POS1
Hardware is BFLC POS
lcpos_instance struct   6033CEC0
RX POS ASIC addr space  12000000
TX POS ASIC addr space  12000100
SUNI framer addr space  12000600
SUNI rsop intr status   00
CRC32 enabled, HDLC enc, int clock
no loop

Interface POS2
Hardware is BFLC POS
lcpos_instance struct   6033F6A0
RX POS ASIC addr space  12000000
TX POS ASIC addr space  12000100
SUNI framer addr space  12000800
SUNI rsop intr status   00
CRC32 enabled, HDLC enc, int clock
no loop

Interface POS3
Hardware is BFLC POS
lcpos_instance struct   60341E80
RX POS ASIC addr space  12000000
TX POS ASIC addr space  12000100
SUNI framer addr space  12000A00
SUNI rsop intr status   00
CRC32 enabled, HDLC enc, ext clock
no loop
Router# 

Related Commands

Command
Description

attach

Connects you to a specific line card for the purpose of executing commands using the Cisco IOS software image on that line card.


exit (EXEC)

To close an active terminal session by logging off the router, use the exit command in EXEC mode.

exit

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

Use the exit command in EXEC mode to exit the active session (log off the device). This command can be used in any EXEC mode (such as User EXEC mode or Privileged EXEC mode) to exit from the EXEC process.

Examples

In the following example, the exit (global) command is used to move from global configuration mode to privileged EXEC mode, the disable command is used to move from privileged EXEC mode to user EXEC mode, and the exit (EXEC) command is used to log off (exit the active session):

Router(config)# exit
Router# disable
Router> exit

Related Commands

Command
Description

disconnect

Disconnects a line.

end

Ends your configuration session by exiting to EXEC mode.

exit (global)

Exits from the current configuration mode to the next highest configuration mode.

logout

Closes your connection to the device (equivilant to the exit command).


exit (global)

To exit any configuration mode to the next highest mode in the CLI mode hierarchy, use the exit command in any configuration mode.

exit

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

All configuration modes

Command History

Release
Modification

10.0

This command was introduced.


Usage Guidelines

The exit command is used in the Cisco IOS CLI to exit from the current command mode to the next highest command mode in the CLI mode hierarchy.

For example, use the exit command in global configuration mode to return to privileged EXEC mode. Use the exit command in interface, line, or router configuration mode to return to global configuration mode. Use the exit command in subinterface configuration mode to return to interface configuration mode. At the highest level, EXEC mode, the exit command will exit the EXEC mode and disconnect from the router interface (see the description of the exit (EXEC) command for details).

Examples

The following example shows how to exit from the subinterface configuration mode and to return to the interface configuration mode:

Router(config-subif)# exit
Router(config-if)#

The following example displays an exit from the interface configuration mode to return to 
the global configuration mode:

Router(config-if)# exit
Router(config)#

Related Commands

Command
Description

disconnect

Disconnects a line.

end

Ends your configuration session by exiting to privileged EXEC mode.

exit (EXEC)

Closes the active terminal session by logging off the router.


file prompt

To specify the level of prompting, use the file prompt command in global configuration mode.

file prompt [alert | noisy | quiet]

Syntax Description

alert

(Optional) Prompts only for destructive file operations. This is the default.

noisy

(Optional) Confirms all file operation parameters.

quiet

(Optional) Seldom prompts for file operations.


Defaults

alert

Command Modes

Global configuration

Command History

Release
Modification

11.0

This command was introduced.


Usage Guidelines

Use this command to change the amount of confirmation needed for different file operations.

This command affects only prompts for confirmation of operations. The router will always prompt for missing information.

Examples

The following example configures confirmation prompting for all file operations:

Router(config)# file prompt noisy 

filter-for-history

To define the type of information kept in the history table for an Service Assurance Agent (SAA) operation, use the filter-for-history command in SAA RTR configuration mode. To return to the default value, use the no form of this command.

filter-for-history {none | all | overThreshold | failures}

no filter-for-history {none | all | overThreshold | failures}

Syntax Description

<