-
Cisco Network Module Enhanced Application Performance Assurance User Guide
-
About this Guide
-
General Overview
-
Getting Started with Application Performance Assurance
-
Command Line Interface
-
Operations
-
Utilities
-
Configuring Security
-
Configuring the Line Interface
-
Failure Recovery
-
Raw Data Formatting: The RDR Formatter
-
Managing Users
-
Monitoring NME-APA Module Utilization
-
MIB Reference
-
Table Of Contents
About Management Interface and Security
How to Configure the Available Interfaces
How to Configure TACACS+ Authentication, Authorization, and Accounting
Information About TACACS+ Authentication, Authorization, and Accounting
How to Configure the NME-APA Module TACACS+ Client
How to Manage the User Database
How to Configure AAA Login Authentication
How to Configure AAA Privilege Level Authorization Methods
How to Configure AAA Accounting
How to Monitor TACACS+ Servers
How to Configure the Telnet Interface
How to Configure the Telnet Timeout
How to Enable the SNMP Interface
How to Disable the SNMP Interface
How to Configure and Manage the SNMP Interface
Information About the SNMP Interface
How to Configure SNMP Community Strings
Configuring SNMP Community Strings
How to Define a Community String
How to Remove a Community String
How to Display the Configured Community Strings
How to Configure SNMP Notifications
How to Configure IP Advertising
How to Display the Current IP Advertising Configuration
How to Configure Time Clocks and Time Zone
About Time Clocks and Time Zone
How to Display the System Time
Displaying the System Time: Example
How to Display the Calendar Time
Displaying the Calendar Time: Example
Setting the System Clock: Example
Setting the Time Zone: Example
How to Remove the Current Time Zone Setting
How to Configure Daylight Saving Time
How to Define Recurring Daylight Saving Time Transitions
How to Define Non-Recurring Daylight Saving Time Transitions
How to Cancel the Daylight Saving Time Configuration
How to Display the Current Daylight Saving Time Configuration
How to Enable the SNTP Multicast Client
How to Disable the SNTP Multicast Client
How to Enable the SNTP Unicast Client
Enabling SNTP Unicast Client: Example
How to Disable the SNTP Unicast Client
How to Disable the SNTP Unicast Client and Remove All Servers
How to Define the SNTP Unicast Update Interval
Defining the SNTP Unicast Update Interval: Example
How to Display SNTP Information
Displaying SNTP Information: Example
How to Configure Domain Name Server (DNS) Settings
How to Define Domain Name Servers
How to Remove a Domain Name Server
How to Remove All Domain Name Servers
How to Add a Host to the Host Table
Adding Hosts to Removing them from the Host Table: Examples
How to Display Current DNS Settings
Displaying Current DNS Settings: Example
Configuring Security
This module describes the various management interface applications, such as SNMP and TACACS+. It also explains how to configure users, clock and time zone, and domain name settings.
•
About Management Interface and Security
•
•
•
•
About Management Interface and Security
The internal interface between the Router and the NME-APA module is used as the in-band management port. The configuration of the in-band management port is done through the IOS CLI. All the management communication goes through this interface.
The external port on the NME-APA module is not used.
In addition to the Layer 1 security of a backup management link, the NME-APA module provides a further management interface security feature; an IP filter that monitors for various types of TCP/IP attacks. This filter can be configured with thresholds rates both for defining an attack and defining the end of an attack.
A number of other features and interfaces are configured via the ISR:
•
•
How to Configure the Available Interfaces
The system allows you to configure the Telnet and SNMP interfaces according to the manner in which you are planning to manage the NME-APA module and the external components of the system.
•
•
How to Configure TACACS+ Authentication, Authorization, and Accounting
•
•
•
•
•
•
•
Information About TACACS+ Authentication, Authorization, and Accounting
•
•
•
TACACS+ Authentication, Authorization, and Accounting
TACACS+ is a security application that provides centralized authentication of users attempting to gain access to a network element. The implementation of TACACS+ protocol allows customers to configure one or more authentication servers for the NME-APA module, providing a secure means of managing the NME-APA module, as the authentication server will authenticate each user. This then centralizes the authentication database, making it easier for the customers to manage the NME-APA module.
TACACS+ services are maintained in a database on a TACACS+ server running, typically, on a UNIX or Windows NT workstation. You must have access to and must configure a TACACS+ server before the configured TACACS+ features on your network element are available.
The TACACS+ protocol provides authentication between the network element and the TACACS+ ACS, and it can also ensure confidentiality, if a key is configured, by encrypting all protocol exchanges between a network element and a TACACS+ server.
The TACACS+ protocol provides the following three features:
•
•
•
Login Authentication
The NME-APA module uses the TACACS+ ASCII authentication message for CLI, Telnet and SSH access.
TACACS+ allows an arbitrary conversation to be held between the server and the user until the server receives enough information to authenticate the user. This is usually done by prompting for a username and password combination.
The login and password prompts may be provided by the TACACS+ server, or if the TACACS+ server does not provide the prompts, then the local prompts will be used.
The user log in information (user name and password) is transmitted to the TACACS+ server for authentication. If the TACACS+ server indicates that the user is not authenticated, the user will be re-prompted for the user name and password. The user is re-prompted a user-configurable number of times, after which the failed login attempt is recorded in the NME-APA module user log and the telnet session is terminated (unless the user is connected to the console port.)
The NME-APA module will eventually receive one of the following responses from the TACACS+ server:
•
•
•
•
If the server is unavailable, the next authentication method is attempted, as explained in General AAA Fallback and Recovery Mechanism.
Accounting
The TACACS+ accounting supports the following functionality:
•
•
•
–
–
–
–
TACACS+ accounting is in addition to normal local accounting using the NME-APA module dbg log.
Privilege Level Authorization
After a successful login the user is granted a default privilege level of 0, giving the user the ability to execute a limited number of commands. Changing privilege level is done by executing the "enable" command. This command initiates the privilege level authorization mechanism.
Privilege level authorization in the NME-APA module is accomplished by the use of an "enable" command authentication request. When a user requests an authorization for a specified privilege level, by using the "enable" command, the NME-APA module sends an authentication request to the TACACS+ server specifying the requested privilege level. The NME-APA module grants the requested privilege level only after the TACACS+ server does the following:
•
•
Once the user privilege level has been determined, the user is granted access to a specified set of commands according to the level granted.
As with login authentication, if the server is unavailable, the next authentication method is attempted, as explained in General AAA Fallback and Recovery Mechanism.
General AAA Fallback and Recovery Mechanism
The NME-APA module uses a fall-back mechanism to maintain service availability in case of an error.
The NME-APA module uses a fall-back mechanism to maintain service availability in case of an error.
The AAA methods available are:
•
•
•
•
In the current implementation the order of the methods used isn't configurable but the customer can choose which of the methods are used. The current order is
•
•
•
•
Note
About Configuring TACACS+
The following is a summary of the procedure for configuring TACACS+. All steps are explained in detail in the remainder of this section.
1.
Configure the remote servers for the protocols. Keep in mind the following guidelines
–
–
–
–
2.
3.
–
–
–
4.
–
If the local database and TACACS+ are both configured, it is recommended to configure the same user names in both TACACS+ and the local database. This will allow the users to access the NME-APA module in case of TACACS+ server failure.
Note
–
–
5.
–
–
6.
Use the show running-config command to view the configuration.
How to Configure the NME-APA Module TACACS+ Client
•
•
•
•
•
Configuring the NME-APA Module TACACS+ Client
The user must configure the remote servers for the TACACS+ protocol. Then the NME-APA module TACACS+ client must be configured to work with the TACACS+ servers. The following information must be configured:
•
For each sever host, the following information can be configured:
–
–
–
–
•
If the default encryption key is not configured, a default of no key is assigned to any server for which a key is not explicitly configured.
•
If the default timeout interval is not configured, a default of five seconds is assigned to any server for which a timeout interval is not explicitly configured.
The procedures for configuring the NME-APA module TACACS+ client are explained in the following sections:
•
•
•
•
How to Add a new TACACS+ Server Host
Use this command to define a new TACACS+ server host that is available to the NME-APA module TACACS+ client.
The Service Control solution supports a maximum of three TACACS+ server hosts.
Options
The following options are available:
•
•
–
•
–
•
–
Step 1
How to Remove a TACACS+ Server Host
Options
The following options are available:
•
Step 1
How to Configure the Global Default Key
Use this command to define the global default key for the TACACS+ server hosts. This default key can be overridden for a specific TACACS+ server host by explicitly configuring a different key for that TACACS+ server host.
•
•
Options
The following options are available:
•
–
How to Define a Global Default Key
Step 1
How to Clear the Global Default Key
Step 1
No global default key is defined. Each TACACS+ server host may still have a specific key defined. However, any server host that does not have a key explicitly defined (uses the global default key) is now configured to use no key.
How to Configure the Global Default Timeout
Use this command to define the global default timeout interval for the TACACS+ server hosts. This default timeout interval can be overridden for a specific TACACS+ server host by explicitly configuring a different timeout interval for that TACACS+ server host.
•
•
Options
The following options are available:
•
–
How to Define the Global Default Timeout
Step 1
How to Clear the Global Default Timeout
Step 1
No global default timeout interval is defined. Each TACACS+ server host may still have a specific timeout interval defined. However, any server host that does not have a timeout interval explicitly defined (uses the global default timeout interval) is now configured to a five second timeout interval.
How to Manage the User Database
TACACS+ maintains a local user database. Up to 100 users can be configured in this local database, which includes the following information for all users:
•
•
•
The procedures for managing the local user database are explained in the following sections:
•
•
•
How to Add a New User to the Local Database
Use these commands to add a new user to the local database. Up to 100 users may be defined.
•
•
•
•
Options
The password is defined with the username. There are several password options:
•
•
Use the password parameter.
•
Password may be defined by either of the following methods:
–
–
The following options are available:
•
•
–
–
•
The following keywords are available:
•
•
–
–
How to Add a User with a Clear Text Password
Step 1
How to Add a User with No Password
Step 1
How to Add a User with an MD5 Encrypted Password Entered in Clear Text
Step 1
How to Add a User with an MD5 Encrypted Password Entered as an MD5 Encrypted String
Step 1
How to Define the User Privilege Level
•
About the User Privilege Level
Privilege level authorization in the NME-APA module is accomplished by the use of an "enable" command authentication request. When a user requests an authorization for a specified privilege level, by using the "enable" command, the NME-APA module sends an authentication request to the TACACS+ server specifying the requested privilege level. The NME-APA module grants the requested privilege level only after the TACACS+ server authenticates the "enable" command password and verifies that the user has sufficient privileges the enter the requested privilege level.
Options
The following options are available:
•
•
–
–
–
Step 1
How to Add a New User with Privilege Level and Password
Use these commands to define a new user, including password and privilege level, in a single command.
Note
•
•
Options
The following options are available:
•
•
–
–
–
•
–
–
•
The following keywords are available:
•
–
–
How to Add a User with a Privilege Level and a Clear Text Password
Step 1
How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered in Clear Text
Step 1
How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered as an MD5 Encrypted String
Step 1
How to Delete a User
Options
The following options are available:
•
Step 1
How to Configure AAA Login Authentication
There are two features to be configured for login authentication:
•
•
The procedures for configuring login authentication are explained in the following sections:
•
•
Configuring Maximum Login Attempts
Use this command to set the maximum number of login attempts that will be permitted before the session is terminated.
Options
The following options are available:
•
This is relevant only for Telnet sessions. From the local console, the number of re-tries is unlimited.
–
Step 1
How to Configure the Login Authentication Methods
You can configure "backup" login authentication methods to be used if failure of the primary login authentication method (see General AAA Fallback and Recovery Mechanism ).
Use this command to specify which login authentication methods are to be used, and in what order of preference.
•
•
Options
The following options are available:
•
–
–
–
–
How to Specify the Login Authentication Methods
Step 1
You may list a maximum of four methods; all four methods explained above. List them in the order of priority.
How to Delete the Login Authentication Methods List
Step 1
If the login authentication methods list is deleted, the default login authentication method only (enable password) will be used. TACACS+ authentication will not be used.
How to Configure AAA Privilege Level Authorization Methods
•
•
Options
The following options are available:
•
–
–
–
–
How to Specify AAA Privilege Level Authorization Methods
Step 1
You may list a maximum of four methods; all four methods explained above. List them in the order of priority.
How to Delete the AAA Privilege Level Authorization Methods List
Step 1
If the privilege level authorization methods list is deleted, the default login authentication method only (enable password) will be used. TACACS+ authentication will not be used.
How to Configure AAA Accounting
Use this command to enable or disable TACACS+ accounting.
•
About AAA Accounting
If TACACS+ accounting is enabled, the NME-APA module sendsan accounting message to the TACACS+ server after every command execution. The accounting message is logged in the TACACS+ server for the use of the network administrator.
By default, TACACS+ accounting is disabled.
Options
The following options are available:
•
How to Enable AAA Accounting
Step 1
The start-stop keyword (required) indicates that the accounting message is sent at the beginning and the end (if the command was successfully executed) of the execution of a CLI command.
How to Disable AAA Accounting
Step 1
How to Monitor TACACS+ Servers
Use these commands to display statistics for the TACACS+ servers.
•
•
How to Display Statistics for TACACS+ Servers
Step 1
How to Display Statistics, Keys and Timeouts for TACACS+ Servers
Step 1
Note that, although most show commands are accessible to viewer level users, the ' all ' option is available only at the admin level. Use the command ' enable 10 ' to access the admin level.
How to Monitor TACACS+ Users
Use this command to display the users in the local database, including passwords.
Step 1
Note that, although most show commands are accessible to viewer level users, this command is available only at the admin level. Use the command ' enable 10 ' to access the admin level.
How to Configure the Telnet Interface
•
About the Telnet Interface
This section discusses the Telnet interface of the NME-APA module. A Telnet session is the most common way to connect to the NME-APA module CLI interface.
You can set the following parameters for the Telnet interface:
•
•
The following commands are relevant to Telnet interface:
•
•
•
•
How to Prevent Telnet Access
Use this command to disable access by Telnet altogether.
Step 1
Current Telnet sessions are not disconnected, but no new Telnet sessions are allowed.
How to Configure the Telnet Timeout
The NME-APA module supports timeout of inactive Telnet sessions.
Options
The following options are available:
•
–
Step 1
Enabling the SNMP Interface
Use this command to enable the SNMP interface. For more information on configuring and managing the SNMP parameters, including hosts, communities, contact, location, and trap destination hosts, see How to Configure and Manage the SNMP Interface.
•
•
How to Enable the SNMP Interface
Options
The following options are available:
•
Step 1
You must define at least one community string to allow SNMP access. For complete information on community strings see How to Configure SNMP Community Strings.
How to Disable the SNMP Interface
Step 1
How to Configure and Manage the SNMP Interface
•
•
•
Information About the SNMP Interface
This section explains how to configure the SNMP agent parameters. It also provides a brief overview of SNMP notifications and the supported MIBs, and explains the order in which the MIB must be loaded.
The SNMP Interface
The NME-APA module operating system includes a Simple Network Management Protocol (SNMP) agent that supports the following:
•
•
SNMP Protocol
SNMP (Simple Network Management Protocol) is a set of protocols for managing complex networks. SNMP works by sending messages, called protocol data units (PDUs), to different parts of a network. SNMP-compliant devices, called agents, store data about themselves in Management Information Bases (MIBs) and return this data to the SNMP requesters.
NME-APA module supports the original SNMP protocol (also known as SNMPv1), and a newer version called Community-based SNMPv2 (also known as SNMPv2C).
•
•
NME-APA module implementation of SNMP supports all MIB II variables, as described in RFC 1213, and defines the SNMP traps using the guidelines described in RFC 1215.
The SNMPv1 and SNMPv2C specifications define the following basic operations that are supported by NME-APA module:
Security Considerations
By default, the SNMP agent is enabled with community set to Public, Read-only
In addition, the NME-APA module supports the option to configure community of managers for read-write accessibility or for read-only accessibility.
Information About CLI
•
•
•
CLI
The NME-APA module supports the CLI commands that control the operation of the SNMP agent. All the SNMP commands are available in Admin authorization level. The SNMP agent is enabled by default and any SNMP configuration command enables the SNMP agent (except where there is an explicit disable command).
CLI Commands for Configuring SNMP
Following is a list of CLI commands available for configuring SNMP. These are Global Configuration mode commands.
•
•
•
•
•
•
•
•
CLI Commands for Monitoring SNMP
Following is a list of CLI commands available for monitoring SNMP. These are Viewer mode commands, and are available when the SNMP agent is enabled:
•
•
•
•
•
•
•
•
Information About MIBs
•
MIBs
MIBs (Management Information Bases) are databases of objects that can be monitored by a network management system (NMS). SNMP uses standardized MIB formats that allow any SNMP tools to monitor any device defined by a MIB.
The NME-APA module supports the following MIBs:
•
–
–
•
MIB Data Objects
The data objects that make up the MIB may be identified in two ways:
•
OIDs are written in dotted format such as: 1.3.6.1.4.1.5655.4.1.10.1
•
For instance: "ifTable" stands for the OID of the MIB-II interface table.
Information About MIB-II
MIB-II
NME-APA module fully supports MIB-II (RFC1213), including the following groups
•
•
•
•
IF-MIB
The MIB-II standard has been extended by several different MIBs. The SCOS supports the IF-MIB, defined in RFC-2233.
The IF-MIB defines the following four tables:
These are the details of specific objects in this MIB:
Information About ENTITY-MIB
ENTITY-MIB
The Entity-MIB contains five groups of MIB objects:
•
•
•
•
•
The SCOS implements only the physical and the general groups of the Entity-MIB, since the other groups are not relevant to the NME-APA module.
For full details about all the MIBs used by the NME-APA module, see the Cisco NME-APA MIB Reference Guide .
Configuration via SNMP
NME-APA module supports a limited set of variables that may be configured via SNMP (read-write variables). Setting a variable via SNMP (as via the CLI) takes effect immediately and affects only the running-configuration. To make this configuration stored for next reboots (startup-configuration) the user must specify it explicitly via CLI or via SNMP using the Cisco MIB.
It should be noted also that the NME-APA module takes the approach of a single configuration database with multiple interfaces that may change this database. Therefore, executing the copy running-config startup-config command via CLI or SNMP makes permanent all the changes made by either SNMP or CLI.
How to Configure SNMP Community Strings
•
•
•
•
Configuring SNMP Community Strings
To enable SNMP management, you must configure SNMP community strings to define the relationship between the SNMP manager and the agent.
After receiving an SNMP request, the SNMP agent compares the community string in the request to the community strings that are configured for the agent. The requests are valid under the following circumstances:
•
•
How to Define a Community String
•
Options
The following options are available:
•
The following keywords are available:
•
•
Step 1
Repeat the command as necessary to define all community strings.
Defining a Community String: Example
This example shows how to configure a community string called "mycommunity" with read-only rights and access list number "1".
Since read-only is the default, it does not need to be defined explicitly.
NME-APA(config)#snmp-server community mycommunity 1How to Remove a Community String
Step 1
Removing a Community String: Example
The following example shows how to remove a community string called "mycommunity".
NME-APA(config)#no snmp-server community mycommunityHow to Display the Configured Community Strings
Step 1
Displaying the Configured Community Strings: Example
The following example shows how to display the configured SNMP communities.
NME-APA>show snmp community Community: public, Access Authorization: RO, Access List Index: 1 NME-APA>How to Configure SNMP Notifications
Use these commands to configure:
•
•
About SNMP Notifications
Notifications are unsolicited messages that are generated by the SNMP agent that resides inside the NME-APA module when an event occurs. When the Network Management System receives the notification message, it can take suitable actions, such as logging the occurrence or ignoring the signal.
By default, the NME-APA module is not configured to send any SNMP notifications. You must define the Network Management System to which the NME-APA module should send notifications. (See the table below, Configurable Notifications, for a list of configurable notifications). Whenever one of the events that trigger notifications occurs in the NME-APA module, an SNMP notification is sent from the NME-APA module to the list of IP addresses that you define.
NME-APA module supports two general categories of notifications:
•
•
After a host or hosts are configured to receive notifications, by default, the NME-APA module sends to the host or hosts all the notifications supported by the NME-APA module except for the AuthenticationFailure notification. The NME-APA module provides the option to enable or disable the sending of this notification, as well as some of the NME-APA enterprise notifications, explicitly.
NME-APA module can be configured to generate either SNMPv1 style or SNMPv2c style notifications. By default, the NME-APA modules sends SNMPv1 notifications.
Following are some sample procedures illustrating how to do the following:
•
•
•
•
•
How to Define SNMP Hosts
Use this command to define the hosts that will receive notifications from the NME-APA module.
•
•
Options
The following options are available:
•
•
•
–
How to Configure the NME-APA Module to Send Notifications to a Host (NMS)
Step 1
If the version is not specified, SNMPv1 is assumed.
Only one host can be specified per command. To define multiple hosts, execute one command for each host.
Configuring the NME-APA Module to Send Notifications to Multiple Hosts: Example
The following example shows how to configure the NME-APA module to send SNMPv1 notifications to several hosts.
NME-APA(config)#snmp-server host 10.10.10.10 mycommunity NME-APA(config)#snmp-server host 20.20.20.20 mycommunity NME-APA(config)#snmp-server host 30.30.30.30 mycommunity NME-APA(config)#snmp-server host 40.40.40.40 mycommunityHow to Configure the NME-APA Module to Stop Sending Notifications to a Host
Step 1
Configuring the NME-APA Module to Stop Sending Notifications to a Host: Example
The following example shows how to remove the host with the IP Address: "192.168.0.83".
NME-APA(config)#no snmp-server host 192.168.0.83How to Configure SNMP Traps
Use this command to configure the notifications that will be sent to the defined host.
•
•
•
•
Options
The following options are available:
•
By default, snmp traps are disabled.
snmp trap name —Optional parameter that specifies a specific snmp trap that should be enabled or disabled.
Currently the only accepted value for this parameter is Authentication .
•
By default, enterprise traps are enabled.
•
Values: attack, chassis, link-bypass, logger, operational-status, port-operational-status, pull-request-failure, RDR-formatter, session, SNTP, user, system-reset, telnet, vas-traffic-forwarding
Use these parameters as follows:
•
•
•
How to Enable the SNMP Server to Send Authentication Failure Notifications
Step 1
How to Enable the SNMP Server to Send All Enterprise Notifications
Step 1
How to Enable the SNMP Server to Send a specific Enterprise Notification
Step 1
Specify the desired enterprise trap type.
Enabling the SNMP Server to Send a Specific Enterprise Notification: Example
The following example shows how to configure the SNMP server to send the logger enterprise notification only.
NME-APA(config)#snmp-server enable traps enterprise loggerHow to Restore All Notifications to the Default Status
Step 1
Resets all notifications supported by the NME-APA module to their default status.
IP Configuration
IP Advertising
•
•
About IP Advertising
IP advertising is the act of periodically sending ping requests to a configured address at configured intervals. This maintains the NME-APA module IP/MAC addresses in the memory of adaptive network elements, such as switches, even during a long period of inactivity.
The following commands are relevant to IP advertising:
•
•
•
•
•
•
•
•
How to Configure IP Advertising
To configure IP advertising, you must first enable IP advertising. You may then specify a destination address to which the ping request is to be sent and/or the frequency of the ping requests (interval). If no destination or interval is explicitly configured, the default values are assumed.
•
•
•
Options
The following options are available in the IP advertising commands:
•
default interval = 300 seconds
•
default destination = 127.0.0.1
How to Enable IP Advertising
Step 1
Enables IP advertising.
How to Configure the IP Advertising Destination
Step 1
Configures the destination for the IP advertising pings.
How to Configure the IP Advertising Interval
Step 1
Configures the frequency of the IP advertising pings.
Configuring IP Advertising: Example
The following example shows how to configure IP advertising, specifying 10.1.1.1 as the destination and an interval of 240 seconds.
NME-APA(config)#ip advertising destination 10.1.1.1 interval 240How to Display the Current IP Advertising Configuration
Step 1
Displays the status of IP advertising (enabled or disabled), the configured destination, and the configured interval
How to Configure Time Clocks and Time Zone
•
•
•
•
•
About Time Clocks and Time Zone
The NME-APA module has three types of time settings, which can be configured: the clock, the calendar, and the time zone. It is important to synchronize the clock and calendar to the local time, and to set the time zone properly. The NME-APA module does not track Daylight Saving Time automatically, so you must update the time zone when the time changes bi-annually.
The NME-APA module has the following two time sources:
•
•
It does not matter which clock you set first, as long as you use the clock and calendar read commands to ensure they are synchronized.
The time zone settings are important because they allow the system to communicate properly with other systems in other time zones. The system is configured based on Coordinated Universal Time (UTC), which is standard in the industry for coordination with other manufacturers' hardware and software. For example, Pacific Standard Time would be written as PST-10, meaning that the name of the time zone is PST, which is 10 hours behind Universal Time.
When setting and showing the time, the time is always typed or displayed according to the local time zone configured.
How to Display the System Time
Step 1
Displaying the System Time: Example
The following example shows the current system clock.
NME-APA#show clock 12:50:03 UTC MON November 13 2001 NME-APA#How to Display the Calendar Time
Step 1
Displaying the Calendar Time: Example
The following example shows the current system calendar.
NME-APA#show calendar 12:50:03 UTC MON May 11 2007 NME-APA#How to Set the System Clock
•
Options
The following option is available:
•
hh:mm:ss day month year
Step 1
Sets the system clock to the specified time and date.
Setting the System Clock: Example
The following example shows how to set the clock to 20 minutes past 10 AM, May 13, 2007, updates the calendar and then displays the time.
NME-APA#clock set 10:20:00 13 may 2007 NME-APA#clock update-calendar NME-APA#show clock 10:21:10 UTC THU May 13 2007How to Set the Calendar
The calendar is a system clock that continues functioning even when the system shuts down.
•
Options
The following option is available:
•
hh:mm:ss day month year
Step 1
Sets the system calendar to the specified time and date.
The time specified in this command is relative to the configured time zone.
Step 2
Synchronizes the system clock with the calendar time you just set .
Setting the Calendar: Example
The following example shows that the calendar is set to 10:20 AM, May 13, 2007. The clock is then synchronized with the calendar setting.
NME-APA#calendar set 10:20:00 13 may 20017 NME-APA#clock read-calendar NME-APA#show calendar 10:21:06 UTC THU May 13 2007How to Set the Time Zone
•
Options
The following options are available:
•
default = GMT
•
default = 0
•
default = 0
Step 1
Sets the timezone to the specified timezone name with the configured offset in hours and minutes.
Setting the Time Zone: Example
The following example shows how to set the time zone to Pacific Standard Time with an offset of 10 hours behind UTC.
NME-APA(config)#clock timezone PST -10 NME-APA(config)#How to Remove the Current Time Zone Setting
Step 1
Removes the timezone configuration and resets the timezone to the default value (UTC).
How to Configure Daylight Saving Time
The NME-APA module can be configured to automatically switch to daylight saving time on a specified date, and also to switch back to standard time. In addition, the time zone code can be configured to vary with daylight saving time if required. (For instance, in the eastern United States, standard time is designated EST, and daylight saving time is designated EDT).
•
•
•
•
Options
The transition times into and out of daylight saving time may be configured in one of two ways, depending on how the dates for the beginning and end of daylight saving time are determined for the particular location:
•
•
The day on which the transition takes place may be defined in several ways:
•
•
•
The following options are available:
•
•
•
•
•
•
•
Default = 60 minutes
Guidelines
General guidelines for configuring daylight saving time transitions:
•
•
•
•
–
–
•
•
–
–
•
–
–
How to Define Recurring Daylight Saving Time Transitions
Step 1
Configures daylight saving time to start and stop on the specified days every year.
Defining Recurring Daylight Saving Time Transitions: Example
The following example shows how to configure recurring daylight saving time for a time zone designated "DST" as follows:
•
•
•
NME-APA(config)# clock summer-time DST recurring last Sunday March 00:00 4 Saturday November 23:59How to Define Non-Recurring Daylight Saving Time Transitions
Step 1
Enables privileged EXEC mode.
Defining Non-Recurring Daylight Saving Time Transitions: Example
The following example shows how to configure non-recurring daylight saving time for a time zone designated "DST" as follows:
•
•
•
NME-APA(config)# clock summer-time DST April 16 2004 00:00 October 23 2004 23:59How to Cancel the Daylight Saving Time Configuration
Step 1
Removes all daylight saving configuration.
How to Display the Current Daylight Saving Time Configuration
Step 1
Displays the current time zone and daylight saving time configuration.
How to Configure SNTP
•
•
•
•
•
•
About SNTP
The Simple Network Timing Protocol (SNTP) is a simple solution to the problem of synchronizing the clocks in the various elements of the network. SNTP provides access to a time source via the network. The system clock and calendar are then set in accordance with this external source.
There are two options for the SNTP client. These functions are independent, and the system employ either one or both.
•
•
Note
The following commands are relevant to SNTP configuration:
•
•
•
•
•
How to Enable the SNTP Multicast Client
Step 1
Enables the SNTP multicast client. It will accept time updates from any broadcast server.
How to Disable the SNTP Multicast Client
Step 1
Disables the SNTP multicast client. It will not accept any broadcast time updates.
How to Enable the SNTP Unicast Client
•
Options
The following option is available:
•
Step 1
Defines the SNTP unicast server so that SNTP client is able to query that server.
Enabling SNTP Unicast Client: Example
The following example shows how to enable an SNTP server at IP address 128.182.58.100.
NME-APA(config)# sntp server 128.182.58.100How to Disable the SNTP Unicast Client
•
•
How to Disable the SNTP Unicast Client and Remove All Servers
Step 1
Removes all SNTP unicast servers, preventing unicast SNTP query.
How to Remove One SNTP Server
Options
The following option is available:
•
Step 1
Removes the specified SNTP unicast server .
How to Define the SNTP Unicast Update Interval
•
Options
The following option is available:
•
default interval = 900 seconds
Step 1
Enables privileged EXEC mode.
•
Defining the SNTP Unicast Update Interval: Example
The following example shows how to set the SNTP update interval for 100 seconds.
NME-APA(config)# sntp update-interval 100How to Display SNTP Information
Step 1
Displays the configuration of both the SNTP unicast client and the SNTP multicast client.
Displaying SNTP Information: Example
This example illustrates how to use this command.
NME-APA# show sntp SNTP broadcast client: disabled last update time: not available SNTP unicast client: enabled SNTP unicast server: 128.182.58.100 last update time: Feb 10 2002, 14:06:41 update interval: 100 secondsHow to Configure Domain Name Server (DNS) Settings
•
•
•
About Domain Name Servers
When a name of a host is given as a parameter to a CLI command that expects a host name or an IP address, the system translates the name to an IP address according to the following:
1.
2.
3.
4.
The following commands are relevant to DNS settings:
•
•
•
•
•
How to Configure DNS Lookup
How to Enable DNS Lookup
Step 1
Enables DNS lookup.
How to Disable DNS Lookup
Step 1
How to Configure Name Servers
•
•
•
Options
The following options are available:
•
How to Define Domain Name Servers
Use this command to specify the address of one or more name servers to use for name and address resolution.
Step 1
Defines the servers at the specified addresses as domain name servers.
Defining Domain Name Servers: Example
The following example shows how to configure the two name server (DNS) IP addresses.
NME-APA(config)#ip name-server 10.1.1.60 10.1.1.61How to Remove a Domain Name Server
Step 1
Removes the specified server from the DNS list.
Removing a Domain Name Server: Example
The following example shows how to remove name server (DNS) IP addresses.
NME-APA(config)#no ip name-server 10.1.1.60 10.1.1.61How to Remove All Domain Name Servers
Step 1
Removes all configured DNS servers.
How to Add a Host to the Host Table
•
Options
The following options are available:
•
•
Step 1
Adds the specified host to the host table.
Adding Hosts to Removing them from the Host Table: Examples
The following example shows how to add a host to the host table.
NME-APA(config)#ip host PC85 10.1.1.61The following example shows how to remove a hostname together with all its IP mappings.
NME-APA(config)#no ip host PC85How to Display Current DNS Settings
Step 1
Displays current DNS settings.
Displaying Current DNS Settings: Example
The following example shows how to display current DNS information.
NME-APA#show hosts Default domain is Cisco.com Name/address lookup uses domain service Name servers are 10.1.1.60, 10.1.1.61 Host Address ---- ------- PC85 10.1.1.61 NME-APA#
