Table Of Contents
Basic System Management Commands
absolute
alias
buffers
buffers huge size
calendar set
clock calendar-valid
clock read-calendar
clock set
clock summer-time
clock timezone
clock update-calendar
downward-compatible-config
hostname
ip bootp server
ip finger
ip telnet source-interface
ip tftp source-interface
load-interval
ntp access-group
ntp authenticate
ntp authentication-key
ntp broadcast
ntp broadcast client
ntp broadcastdelay
ntp clock-period
ntp disable
ntp master
ntp max-associations
ntp peer
ntp server
ntp source
ntp trusted-key
ntp update-calendar
periodic
process-max-time
prompt
scheduler allocate
scheduler interval
service decimal-tty
service exec-wait
service finger
service hide-telnet-address
service nagle
service prompt config
service tcp-small-servers
service telnet-zero-idle
service udp-small-servers
show aliases
show buffers
show calendar
show clock
show idb
show ntp associations
show ntp status
show registry
show sntp
sntp broadcast client
sntp server
time-range
Basic System Management Commands
This chapter describes the commands used to perform basic system management tasks in Cisco IOS Release 12.1. Basic system management tasks include naming the router, enabling basic services, and configuring the Network Time Protocol (NTP).
For basic system management configuration tasks and examples, refer to the "Performing Basic System Management" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.1.
absolute
To specify an absolute time when a time range is in effect, use the absolute time-range configuration command. To remove the time limitation, use the no form of this command.
absolute [start time date] [end time date]
no absolute
Syntax Description
start time date
|
(Optional) Absolute time and date that the associated permit or deny statement starts going into effect. The time is expressed in a 24-hour clock, in the form of hours:minutes. For example, 8:00 is 8:00 am and 20:00 is 8:00 pm. The date is expressed in the format day month year. The minimum start is 00:00 1 January 1993. If no start time and date are specified, the permit or deny statement is in effect immediately.
|
end time date
|
(Optional) Absolute time and date that the associated permit or deny statement is no longer in effect. Same time and date format as described for the start. The end time and date must be after the start time and date. The maximum end time is 23:59 31 December 2035. If no end time and date are specified, the permit or deny statement is in effect indefinitely.
|
Defaults
There is no absolute time when the time range is in effect.
Command Modes
Time-range configuration
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
Usage Guidelines
For Cisco IOS Release 12.1, IP and IPX extended access lists are the only functions that can use time ranges. For further information on using these functions, see the Cisco IOS 12.1 IP and IP Routing and the Cisco IOS 12.1 AppleTalk and Novell IPX publications.
The absolute command is one way to specify when a time range is in effect. Another way is to specify a periodic length of time with the periodic command. Use either of these commands after the time-range command, which enables time-range configuration mode and specifies a name for the time range. Only one absolute entry is allowed per time-range command.
If a time-range command has both absolute and periodic values specified, then the periodic items are evaluated only after the absolute start time is reached, and are not further evaluated after the absolute end time is reached.
Note
All time specifications are taken as local time. To ensure that the time range entries take effect at the desired times, the system clock should be synchronized. Use NTP or the hardware calendar to synchronize the clock. For more information, refer to the "Performing Basic System Management" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide.
Examples
The following example configures an access list named northeast, which references a time range named xyz. The access list and time range together permit traffic on Ethernet interface 0 starting at noon on January 1, 2001 and going forever.
absolute start 12:00 1 January 2001
ip access-list extended northeast
permit ip any any time-range xyz
ip access-group northeast in
The following example permits UDP traffic until noon on December 31, 2000. After that time, UDP traffic is no longer allowed out Ethernet interface 0.
absolute end 12:00 31 December 2000
ip access-list extended northeast
permit udp any any time-range abc
ip access-group northeast out
The following example permits UDP traffic out Ethernet interface 0 on weekends only, from 8:00 a.m. on January 1, 1999 to 6:00 p.m. on December 31, 2001:
absolute start 8:00 1 January 1999 end 18:00 31 December 2001
periodic weekends 00:00 to 23:59
ip access-list extended northeast
permit udp any any time-range test
ip access-group northeast out
Related Commands
Command
|
Description
|
deny
|
Sets conditions under which a packet does not pass a named access list.
|
periodic
|
Specifies a recurring (weekly) start and end time for a time-range.
|
permit
|
Sets conditions under which a packet passes a named access list.
|
time-range
|
Enables time-range configuration mode and names a time-range definition.
|
alias
To create a command alias, use the alias global configuration command. Use the no form of this command to delete all aliases in a command mode or to delete a specific alias, and to revert to the original command syntax.
alias mode alias-name alias-command-line
no alias mode [alias-name]
Syntax Description
mode
|
Command mode of the original and alias commands. See Table 104 for a list of options for this argument.
|
alias-name
|
Command alias.
|
alias-command-line
|
Original command syntax.
|
Defaults
Default aliases are in EXEC mode as follows:
Command Alias
|
Original Command
|
h
|
help
|
lo
|
logout
|
p
|
ping
|
r
|
resume
|
s
|
show
|
w
|
where
|
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
You can use simple words or abbreviations as aliases. The aliases in the "Defaults" section are predefined. They can be turned off using the no alias command.
Table 104 shows the acceptable options for the mode argument in the alias global configuration command.
Table 104 mode Argument Options
Argument Options
|
Mode
|
configuration
|
Global configuration
|
controller
|
Controller configuration
|
exec
|
EXEC
|
hub
|
Hub configuration
|
interface
|
Interface configuration
|
ipx-router
|
IPX router configuration
|
line
|
Line configuration
|
map-class
|
Map class configuration
|
map-list
|
Map list configuration
|
route-map
|
Route map configuration
|
router
|
Router configuration
|
See the summary of command modes in the "Using the Command-Line Interface" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide for more information about command modes.
When you use online help, command aliases are indicated by an asterisk (*), as follows:
*lo=logout lock login logout
When you use online help, aliases that contain spaces (for example, telnet device.cisco.com 25) are displayed as follows:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# alias exec device-mail telnet device.cisco.com 25
*device-mail="telnet device.cisco.com 25"
When you use online help, the alias is expanded and replaced with the original command, as shown in the following example with the td alias:
Router(config)# alias exec td trace device
*td="trace device" telnet terminal test tn3270
To list only commands and omit aliases, begin your input line with a space. In the following example, the alias td is not shown, because there is a space before the t? command line.
telnet terminal test tn3270 trace
As with commands, you can use online help to display the arguments and keywords that can follow a command alias. In the following example, the alias td is created to represent the command telnet device. The /debug and /line switches can be added to telnet device to modify the command:
Router(config)# alias exec td telnet device
/debug Enable telnet debugging mode
/line Enable telnet line mode
You must enter the complete syntax for the alias command. Partial syntax for aliases are not accepted. In the following example, the parser does not recognize the command t as indicating the alias td.
Examples
The following example creates the alias fixmyrt for the IP route198.92.116.16:
alias exec fixmyrt clear ip route 198.92.116.16
Related Commands
Command
|
Description
|
show aliases
|
Displays all alias commands.
|
buffers
To make adjustments to initial buffer pool settings and to the limits at which temporary buffers are created and destroyed, use the buffers global configuration command. Use the no form of this command to return the buffers to their default size.
buffers {small | middle | big | verybig | large | huge | type number} {permanent | max-free
| min-free | initial} number
no buffers {small | middle | big | verybig | large | huge | type number} {permanent | max-free
| min-free | initial} number
Syntax Description
small
|
Buffer size of this public buffer pool is 104 bytes.
|
middle
|
Buffer size of this public buffer pool is 600 bytes.
|
big
|
Buffer size of this public buffer pool is 1524 bytes.
|
verybig
|
Buffer size of this public buffer pool is 4520 bytes.
|
large
|
Buffer size of this public buffer pool is 5024 bytes.
|
huge
|
Default buffer size of this public buffer pool is 18024 bytes. This value can be configured with the buffers huge size command.
|
type number
|
Interface type and interface number of the interface buffer pool. The type value cannot be fddi.
|
permanent
|
Number of permanent buffers that the system tries to create and keep. Permanent buffers are normally not trimmed by the system.
|
max-free
|
Maximum number of free or unallocated buffers in a buffer pool. A maximum of 20,480 small buffers can be constructed in the pool.
|
min-free
|
Minimum number of free or unallocated buffers in a buffer pool.
|
initial
|
Number of additional temporary buffers that are to be allocated when the system is reloaded. This keyword can be used to ensure that the system has necessary buffers immediately after reloading in a high-traffic environment.
|
number
|
Number of buffers to be allocated.
|
Defaults
The default number of buffers in a pool is determined by the hardware configuration and can be displayed with the EXEC show buffers command.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Normally you need not adjust these parameters; do so only after consulting with technical support personnel. Improper settings can adversely impact system performance.
You cannot configure FDDI buffers.
Examples
Examples of Public Buffer Pool Tuning
The following example keeps at least 50 small buffers free in the system:
buffers small min-free 50
The following example increases the permanent buffer pool allocation for big buffers to 200:
buffers big permanent 200
Example of Interface Buffer Pool Tuning
A general guideline is to display buffers with the show buffers command, observe which buffer pool is depleted, and increase that one.
The following example increases the permanent Ethernet 0 interface buffer pool on a Cisco 4000 is 96 because the Ethernet 0 buffer pool is depleted:
buffers ethernet 0 permanent 96
Related Commands
Command
|
Description
|
load-interval
|
Changes the length of time for which data is used to compute load statistics.
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
buffers huge size
To dynamically resize all huge buffers to the value you specify, use the buffers huge size global configuration command. Use the no form of this command to restore the default buffer values.
buffers huge size number
no buffers huge size number
Syntax Description
number
|
Huge buffer size, in bytes.
|
Defaults
18024 bytes
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Use only after consulting with technical support personnel. The buffer size cannot be lowered below the default.
Examples
The following example resizes huge buffers to 20000 bytes:
Related Commands
Command
|
Description
|
buffers
|
Makes adjustments to initial buffer pool settings and to the limits at which temporary buffers are created and destroyed.
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
calendar set
To set the system calendar, use one of the formats of the calendar set EXEC command.
calendar set hh:mm:ss day month year
calendar set hh:mm:ss month day year
Syntax Description
hh:mm:ss
|
Current time in hours (military format), minutes, and seconds.
|
day
|
Current day (by date) in the month.
|
month
|
Current month (by name).
|
year
|
Current year (no abbreviation).
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Some platforms have a calendar which is separate from the system clock. This calendar runs continuously, even if the router is powered off or rebooted. After you set the calendar, the system clock will be automatically set from the calendar when the system is restarted or when the clock read-calendar EXEC command is issued. The time specified in this command is relative to the configured time zone.
Examples
The following example manually sets the system calendar to 1:32 p.m. on July 23, 1997:
calendar set 13:32:00 23 July 1997
Related Commands
clock calendar-valid
To configure a router as a time source for a network based on its calendar, use the clock calendar-valid global configuration command. Use the no form of this command to specify that the calendar is not an authoritative time source.
clock calendar-valid
no clock calendar-valid
Syntax Description
This command has no arguments or keywords.
Defaults
The router is not configured as a time source.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Some platforms have a calendar which is separate from the system clock. This calendar runs continuously, even if the router is powered off or rebooted. If you have no outside time source available on your network, use this command to make the calendar an authoritative time source.
Examples
The following example configures a router as the time source for a network based on its calendar:
Related Commands
Command
|
Description
|
ntp master
|
Configures the Cisco IOS software as an NTP master clock to which peers synchronize themselves when an external NTP source is not available.
|
vines time use-system
|
Sets VINES network time based on the internal time.
|
clock read-calendar
To manually read the calendar into the system clock, use the clock read-calendar EXEC command.
clock read-calendar
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Some platforms have a calendar which is separate from the system clock. This calendar runs continuously, even if the router is powered off or rebooted. When the router is rebooted, the calendar is automatically read into the system clock. However, you may use this command to manually read the calendar setting into the system clock. This command is useful if the calendar set command has been used to change the setting of the calendar.
Examples
The following example configures the system clock to set its date and time by the calendar setting:
Related Commands
clock set
To manually set the system clock, use one of the formats of the clock set command in privileged EXEC mode.
clock set hh:mm:ss day month year
clock set hh:mm:ss month day year
Syntax Description
hh:mm:ss
|
Current time in hours (military format), minutes, and seconds.
|
day
|
Current day (by date) in the month.
|
month
|
Current month (by name).
|
year
|
Current year (no abbreviation).
|
Command Modes
Privileged EXEC mode
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Generally, if the system is synchronized by a valid outside timing mechanism, such as an NTP or VINES clock source, or if you have a router with calendar capability, you do not need to set the system clock. Use this command if no other time sources are available. The time specified in this command is relative to the configured time zone.
Examples
The following example manually sets the system clock to 1:32 p.m. on July 23, 1997:
clock set 13:32:00 23 July 1997
Related Commands
clock summer-time
To configure the system to automatically switch to summer time (daylight savings time), use one of the formats of the clock summer-time global configuration command. Use the no form of this command to configure the Cisco IOS software not to automatically switch to summer time.
clock summer-time zone recurring [week day month hh:mm week day month hh:mm [offset]]
clock summer-time zone date date month year hh:mm date month year hh:mm [offset]
clock summer-time zone date month date year hh:mm month date year hh:mm [offset]
no clock summer-time
Syntax Description
zone
|
Name of the time zone (for example, "PDT" for Pacific Daylight Time) to be displayed when summer time is in effect.
|
recurring
|
Indicates that summer time should start and end on the corresponding specified days every year.
|
date
|
Indicates that summer time should start on the first specific date listed in the command and end on the second specific date in the command.
|
week
|
(Optional) Week of the month (1 to 5 or last).
|
day
|
(Optional) Day of the week (Sunday, Monday,...).
|
date
|
Date of the month (1 to 31).
|
month
|
(Optional) Month (January, February,...).
|
year
|
Year (1993 to 2035).
|
hh:mm
|
(Optional) Time (military format) in hours and minutes.
|
offset
|
(Optional) Number of minutes to add during summer time (default is 60).
|
Defaults
Summer time is disabled. If clock summer-time zone recurring is specified without parameters, the summer time rules default to United States rules. Default of offset is 60.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Use this command if you want to automatically switch to summer time (for display purposes only). Use the recurring form of the command if the local summer time rules are of this form. Use the date form to specify a start and end date for summer time if you cannot use the first form.
In both forms of the command, the first part of the command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the Southern Hemisphere.
Examples
The following example specifies that summer time starts on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00:
clock summer-time PDT recurring 1 Sunday April 2:00 last Sunday October 2:00
If you live in a place where summer time does not follow the pattern in the first example, you could set it to start on October 12, 1997 at 02:00, and end on April 26, 1998 at 02:00, with the following example:
clock summer-time date 12 October 1997 2:00 26 April 1998 2:00
Related Commands
clock timezone
To set the time zone for display purposes, use the clock timezone global configuration command. To set the time to Coordinated Universal Time (UTC), use the no form of this command.
clock timezone zone hours-offset [minutes-offset]
no clock timezone
Syntax Description
zone
|
Name of the time zone to be displayed when standard time is in effect.
|
hours-offset
|
Hours difference from UTC.
|
minutes-offset
|
(Optional) Minutes difference from UTC.
|
Defaults
UTC
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The system internally keeps time in UTC, so this command is used only for display purposes and when the time is manually set.
Table 105 lists common time zone acronyms used for the zone argument.
Table 105 Common Time Zone Acronyms
Acronym
|
Time Zone Name and UTC Offset
|
Europe
|
|
GMT
|
Greenwich Mean Time, as UTC
|
BST
|
British Summer Time, as UTC +1 hour
|
IST
|
Irish Summer Time, as UTC +1 hour
|
WET
|
Western Europe Time, as UTC
|
WEST
|
Western Europe Summer Time, as UTC +1 hour
|
CET
|
Central Europe Time, as UTC +1
|
CEST
|
Central Europe Summer Time, as UTC +2
|
EET
|
Eastern Europe Time, as UTC +2
|
EEST
|
Eastern Europe Summer Time, as UTC +3
|
MSK
|
Moscow Time, as UTC +3
|
MSD
|
Moscow Summer Time, as UTC +4
|
US and Canada
|
|
AST
|
Atlantic Standard Time, as UTC -4 hours
|
ADT
|
Atlantic Daylight Time, as UTC -3 hours
|
ET
|
Eastern Time, either as EST or EDT, depending on place and time of year
|
EST
|
Eastern Standard Time, as UTC -5 hours
|
EDT
|
Eastern Daylight Saving Time, as UTC -4 hours
|
CT
|
Central Time, either as CST or CDT, depending on place and time of year
|
CST
|
Central Standard Time, as UTC -6 hours
|
CDT
|
Central Daylight Saving Time, as UTC -5 hours
|
MT
|
Mountain Time, either as MST or MDT, depending on place and time of year
|
MST
|
Mountain Standard Time, as UTC -7 hours
|
MDT
|
Mountain Daylight Saving Time, as UTC -6 hours
|
PT
|
Pacific Time, either as PST or PDT, depending on place and time of year e.g. Los Angeles
|
PST
|
Pacific Standard Time, as UTC -8 hours
|
PDT
|
Pacific Daylight Saving Time, as UTC -7 hours
|
HST
|
Hawaiian Standard Time, as UTC -10 hours
|
AKST
|
Alaska Standard Time, as UTC -9 hours
|
AKDT
|
Alaska Standard Daylight Saving Time, as UTC -8 hours
|
Australia
|
|
WST
|
Western Standard Time, as UTC +8 hours e.g. Perth
|
CST
|
Central Standard Time, as UTC +9.5 hours e.g. Darwin
|
EST
|
Eastern Standard/Summer Time, as UTC +10 hours (+11 hours during summer time) e.g. Canberra
|
Table 106 lists an alternative method for referring to time zones, in which single letters are used to refer to the time zone difference from UTC. Using this method, the letter Z is used to indicate the zero meridian, equivalent to UTC, and the letter J (Juliet) is used to refer to the local time zone. Using this method, the International Date Line is between time zones M and Y.
Table 106 Single Letter Time Zone Designators
Letter Designator
|
Word Designator
|
Difference from UTC
|
Y
|
Yankee
|
UTC - 12 hours
|
X
|
Xray
|
UTC - 11 hours
|
W
|
Whiskey
|
UTC - 10 hours
|
V
|
Victor
|
UTC - 9 hours
|
U
|
Uniform
|
UTC - 8 hours
|
T
|
Tango
|
UTC - 7 hours
|
S
|
Sierra
|
UTC - 6 hours
|
R
|
Romeo
|
UTC - 5 hours
|
Q
|
Quebec
|
UTC - 4 hours
|
P
|
Papa
|
UTC - 3 hours
|
O
|
Oscar
|
UTC - 2 hours
|
N
|
November
|
UTC - 1 hour
|
Z
|
Zulu
|
same as UTC
|
A
|
Alpha
|
UTC + 1 hour
|
B
|
Bravo
|
UTC + 2 hours
|
C
|
Charlie
|
UTC + 3 hours
|
D
|
Delta
|
UTC + 4 hours
|
E
|
Echo
|
UTC + 5 hours
|
F
|
Foxtrot
|
UTC + 6 hours
|
G
|
Golf
|
UTC + 7 hours
|
H
|
Hotel
|
UTC + 8 hours
|
I
|
India
|
UTC + 9 hours
|
K
|
Kilo
|
UTC + 10 hours
|
L
|
Lima
|
UTC + 11 hours
|
M
|
Mike
|
UTC + 12 hours
|
Examples
The following example sets the timezone to Pacific Standard Time (PST), which is 8 hours behind UTC:
The following example sets the timezone to Atlantic Time (AT) for Newfoundland, Canada, which is 3.5 hours behind UTC:
Related Commands
Command
|
Description
|
calendar set
|
Sets the system calendar.
|
clock set
|
Manually set the system clock.
|
clock summer-time
|
Configures the system to automatically switch to summer time (daylight savings time).
|
show clock
|
Displays the system clock.
|
clock update-calendar
To set the calendar from the system clock, use the clock update-calendar EXEC command.
clock update-calendar
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Some platforms have a calendar which is separate from the system clock. This calendar runs continuously, even if the router is powered off or rebooted.
If the system clock and calendar are not synchronized, and the system clock is more accurate, use this command to update the calendar to the correct date and time.
Examples
The following example copies the current time from the system clock to the calendar:
Related Commands
downward-compatible-config
To generate a configuration that is compatible with an earlier Cisco IOS release, use the downward-compatible-config global configuration command. To remove this feature, use the no form of this command.
downward-compatible-config version
no downward-compatible-config
Syntax Description
version
|
Cisco IOS Release number, not earlier than 10.2.
|
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
In Cisco IOS Release 10.3, IP access lists changed format. Use this command to regenerate a configuration in a format prior to Release 10.3 if you are going to downgrade from a Release 10.3 or later to an earlier release. The earliest release this command accepts is 10.2.
When this command is configured, the router attempts to generate a configuration that is compatible with the specified version. Currently, this command affects only IP access lists.
Under some circumstances, the software might not be able to generate a fully backward-compatible configuration. In such a case, the software issues a warning message.
Examples
The following example generates a configuration file compatible with Cisco IOS Release 10.2:
downward-compatible-config 10.2
Related Commands
Command
|
Description
|
access-list (extended)
|
Provides extended access lists that allow more detailed access lists.
|
access-list (standard)
|
Defines a standard XNS access list.
|
hostname
To specify or modify the host name for the network server, use the hostname global configuration command. The host name is used in prompts and default configuration filenames. The setup command facility also prompts for a host name at startup.
hostname name
Syntax Description
name
|
New host name for the network server.
|
Defaults
The factory-assigned default host name is router.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The order of display at startup is banner message-of-the-day (MOTD), then login and password prompts, then EXEC banner.
Do not expect case to be preserved. Upper- and lowercase characters look the same to many internet software applications (often under the assumption that the application is doing you a favor). It may seem appropriate to capitalize a name the same way you might do in English, but conventions dictate that computer names appear all lowercase. For more information, refer to RFC 1178, Choosing a Name for Your Computer.
The name must also follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. Names must be 63 characters or fewer. For more information, refer to RFC 1035, Domain Names—Implementation and Specification.
Examples
The following example changes the host name to sandbox:
Related Commands
Command
|
Description
|
setup
|
Enables you to make major enhancements to your configurations, for example, adding a protocol suit, making major addressing scheme changes, or configuring newly installed interfaces.
|
ip bootp server
To access the BOOTP service available from hosts on the network, use the ip bootp server global configuration command. Use the no form of the command to disable these services.
ip bootp server
no ip bootp server
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
By default, the BOOTP server is enabled.
The integrated Dynamic Host Configuration Protocol (DHCP) server was introduced in Cisco IOS Release 12.0(1)T. Because DHCP is interoperable with BOOTP, both of these services share the "well-known" UDP server port of 67 (per RFC 951, RFC 1534, and RFC 2131). If both the BOOTP server and DHCP server are disabled, and a helper address is not configured, "ICMP port unreachable" messages will be sent in response to incoming requests on port 67, and the original incoming packet will be discarded.
Examples
In the following example, BOOTP and DHCP services are disabled on the router:
Router(config)# no ip bootp server
Router(config)# no service dhcp
Related Commands
Command
|
Description
|
service dhcp
|
Enables the integrated Dynamic Host Configuration Protocol (DHCP) server and relay agent.
|
ip finger
To configure a system to accept Finger protocol requests (defined in RFC 742), use the ip finger global configuration command. To disable this service, use the no form of this command.
ip finger [rfc-compliant]
no ip finger
Syntax Description
rfc-compliant
|
(Optional) Configures the system to wait for "Return" or "/W" input when processing Finger requests. This keyword should not be used for those systems.
|
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
12.1
|
The rfc-compliant keyword was introduced.
|
Usage Guidelines
The Finger service allows remote users to view the output equivalent to the show users [wide] command.
When ip finger is configured, the router will respond to a telnet a.b.c.d finger command from a remote host by immediately displaying the output of the