Configuring the Management Interface and Security
This module describes how to configure the physical management interfaces (ports) as well as the various management interface applications, such as SNMP, SSH, and TACACS+. It also explains how to configure users, passwords, IP configuration, clock and time zone, and domain name settings.
•About Management Interface and Security
•Configuring the Management Port
•How to Enter Management Interface Configuration Mode
•Configuring the Management Port Physical Parameters
•Configuring the Available Interfaces
•Configuring and Managing the SNMP Interface
•IP Configuration
•Configuring and Managing the SNMP Interface
•Configuring Time Clocks and Time Zone
•Domain Name Server (DNS) Settings
About Management Interface and Security
The Service Control Module is equipped with an RJ-45 management (MNG) port. This Gigabit Ethernet port provides access from a remote management console to the SCE platform via a LAN.
Perform the following tasks to configure the management interface and management interface security:
•Configure the management port:
–Physical parameters
•Configure management interface security
–Configure the permitted and not-permitted IP addresses
Configuring the Management Port
Perform the following tasks to configure the management port:
•Configure the IP address and subnet mask
•Configure physical parameters:
–Speed
–Duplex
Step 1 Cable the management port, connecting it to the remote management console via the LAN.
Step 2 Configure the management port physical parameters. (See Configuring the Management Port Physical Parameters.)
How to Enter Management Interface Configuration Mode
interface Mng The GBE management interface is configured as follows:
•mode: Gigabit Ethernet Interface configuration mode
•interface designation: 1/1
Step 1 Type configure and press Enter.
Enters Global Configuration mode.
The command prompt changes to SCE(config)#.
Step 2 Type interface GigabitEthernet 1/1 and press Enter.
Enters GigabitEthernet Interface Configuration mode.
The command prompt changes to SCE(config-if)#
Configuring the Management Port Physical Parameters
This is a Gigabit Ethernet interface and is used for management operations and for transmitting RDRs, which are the output of traffic analysis and management operations.
•Setting the IP Address and Subnet Mask of the Management Interface
•Configuring the Management Interface Speed and Duplex Parameters
•How to Monitor the Management Interface
Setting the IP Address and Subnet Mask of the Management Interface
The user must define the IP address of the management interface.
Options
The following options are available:
•IP address — The IP address of the management interface.
•subnet mask — subnet mask of the management interface.
Changing the IP address of the management interface via telnet will result in loss of the telnet connection and inability to reconnect with the interface.
Step 1 From the SCE(config if)# prompt, type ip address ip-address subnet-mask and press Enter.
The command might fail if there is a routing table entry that is not part of the new subnet defined by the new IP address and subnet mask.
Note Changing the IP address of the management interface via telnet will result in loss of the telnet connection and inability to reconnect with the interface.
Note After changing the IP address, you must reload the SCE platform so that the change will take effect properly in all internal and external components of the SCE platform. (See Rebooting and Shutting Down the SCE Platform, page 3-14.)
Setting the IP Address and Subnet Mask of the Management Interface: Example
The following example shows how to set the IP address of the SCE platform to 10.1.1.1 and the subnet mask to 255.255.0.0.
SCE(config if)#ip address 10.1.1.1 255.255.0.0
Configuring the Management Interface Speed and Duplex Parameters
This section presents sample procedures that describe how to configure the speed and the duplex of the Management Interface.
Both these parameters must be configured separately for each port.
•Interface State Relationship to Speed and Duplex
•How to Configure the Speed of the Management Interface
•How to Configure the Duplex Operation of the Management Interface
Interface State Relationship to Speed and Duplex
The following table summarizes the relationship between the interface state and speed and duplex.
Note•It is not possible to set one parameter to "Auto" and to specify the other parameter. If either speed or duplex is set to "Auto", then both parameters will behave as if set to "Auto".
•Due to the nature of the interface, 1000Mbps operation is only available when auto-negotiation is enabled.
Table 5-1 Interface State Relationship to Speed and Duplex
|
|
Actual FE Interface State
|
Auto |
Auto |
Auto negotiation |
Auto |
Full/Half |
Auto negotiation |
10/100 |
Auto |
Auto negotiation |
10 |
Full |
10 Mbps and full duplex |
10 |
Half |
10 Mbps and half duplex |
100 |
Full |
100 Mbps and full duplex |
100 |
Half |
100 Mbps and half duplex |
How to Configure the Speed of the Management Interface
Options
The following options are available:
•speed — speed in Mbps of the currently selected management port (0/1 or 0/2):
–10
–100
–auto (default) — auto-negotiation (do not force speed on the link)
If the duplex parameter is configured to auto, changing the speed parameter has no effect (see ).
Step 1 From the SCE(config if)# prompt, type speed 10|100|auto and press Enter.
Specify the desired speed option.
Configuring the Speed of the Management Interface: Example
The following example shows how to use this command to configure the Management port to 100 Mbps speed.
How to Configure the Duplex Operation of the Management Interface
Options
The following options are available:
•duplex — duplex operation of the management port (1/1):
–full
–half
–auto (default) — auto-negotiation (do not force duplex on the link)
If the speed parameter is configured to auto, changing the duplex parameter has no effect (see ).
Step 1 From the SCE(config-if)# prompt, type duplex auto|full|half and press Enter.
Specify the desired duplex option.
Configuring the Duplex Operation of the Management Interface: Example
The following example shows how to use this command to configure the management port to half duplex mode.
SCE(config-if)#duplex half
How to Monitor the Management Interface
Use this command to display the following information for the management interface.
•autonegotiation
•IP address
•active port
Step 1 From the SCE# prompt, type show GigabitEthernet interface Mng 1/1 [auto-negotiate|ip address] and press Enter.
Displays the GBE management interface configuration. If no option is specified, all management interface information is displayed.
Configuring 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 SCE platform and the external components of the system.
•TACACS+ Authentication, Authorization, and Accounting
•Configuring Access Control Lists (ACLs)
•Managing the Telnet Interface
•Configuring the SSH Server
•Enabling the SNMP Interface
TACACS+ Authentication, Authorization, and Accounting
•Information About TACACS+ Authentication, Authorization, and Accounting
•How to Configure the SCE Platform TACACS+ Client
•How to Manage the User Database
•Configuring AAA Login Authentication
•Configuring AAA Privilege Level Authorization Methods
•Configuring AAA Accounting
•Monitoring TACACS+ Servers
•Monitoring TACACS+ Users
Information About TACACS+ Authentication, Authorization, and Accounting
•TACACS+ Authentication, Authorization, and Accounting
•Login Authentication
•Accounting
•Privilege Level Authorization
•General AAA Fallback and Recovery Mechanism
•About Configuring TACACS+
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 SCE platform, providing a secure means of managing the SCE platform, as the authentication server will authenticate each user. This then centralizes the authentication database, making it easier for the customers to manage the SCE platform.
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
•Privilege level authorization
•Accounting
Login Authentication
The SCE platform 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 SCE platform user log and the telnet session is terminated (unless the user is connected to the console port.)
The SCE platform will eventually receive one of the following responses from the TACACS+ server:
•ACCEPT - The user is authenticated and service may begin.
•REJECT - The user has failed to authenticate. The user may be denied further access, or will be prompted to retry the login sequence depending on the TACACS+ server.
•ERROR - An error occurred at some time during authentication. This can be either at the server or in the network connection between the server and the SCE platform. If an ERROR response is received, the SCE platform will try to use an alternative method\server for authenticating the user.
•CONTINUE - The user is prompted for additional authentication information.
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:
•Each executed command (the command must be a valid one) will be logged using the TACACS+ accounting mechanism (including login and exit commands).
•The command is logged both before and after it is successfully executed.
•Each accounting message contains the following:
–User name
–Current time
–Action performed
–Command privilege level
TACACS+ accounting is in addition to normal local accounting using the SCE platform 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 SCE platform 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 SCE platform sends an authentication request to the TACACS+ server specifying the requested privilege level. The SCE platform grants the requested privilege level only after the TACACS+ server does the following:
•Authenticates the " enable " command password
•Verifies that the user has sufficient privileges to enter the requested privilege level.
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 SCE platform uses a fall-back mechanism to maintain service availability in case of an error.
The AAA methods available are:
•TACACS+ - AAA is performed by the use of a TACACS+ server, allows authentication, authorization and accounting.
•Local - AAA is performed by the use of a local database, allows authentication and authorization.
•Enable - AAA is performed by the use of user configured passwords, allows authentication and authorization.
•None - no authentication\authorization\accounting is performed.
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:
•TACACS+
•Local
•Enable
•None
Note Important: If the server goes to AAA fault, the SCE platform will not be accessible until one of the AAA methods is restored. In order to prevent this, it is advisable to use the "none" method as the last AAA method. If the SCE platform becomes un-accessible, the shell function "AAA_MethodsReset" will allow the user to delete the current AAA method settings and set the AAA method used to "Enable".
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 TACACS+ servers.
Configure the remote servers for the protocols. Keep in mind the following guidelines
–Configure the encryption key that the server and client will use.
–The maximal user privilege level and enable password (password used when executing the enable command) should be provided.
–The configuration should always include the root user, giving it the privilege level of 15.
–Viewer (privilege level 5) and superuser (privilege level 10) user IDs should be established at this time also.
1. For complete details on server configuration, refer to the appropriate configuration guide for the particular TACACS+ server that you will be using.
2. Configure the SCE client to work with TACACS+ server:
–hostname of the server
–port number
–shared encryption key (the configured encryption key must match the encryption key configured on the server in order for the client and server to communicate.)
3. (Optional) Configure the local database, if used.
–add new users
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 SCE platform in case of TACACS+ server failure.
Note If TACACS+ is used as the login method, the TACACS+ username is used automatically in the enable command. Therefore, it is important to configure the same usernames in both TACACS+ and the local database so that the enable command can recognize this username.
–specify the password
–define the privilege level
4. Configure the authentication methods on the SCE platform.
–login authentication methods
–privilege level authorization methods
5. Review the configuration.
Use the " show running-config " command to view the configuration.
How to Configure the SCE Platform TACACS+ Client
•Configuring the SCE Platform TACACS+ Client
•How to Add a New TACACS+ Server Host
•How to Remove a TACACS+ Server Host
•How to Configure the Global Default Key
•How to Configure the Global Default Timeout
Configuring the SCE Platform TACACS+ Client
The user must configure the remote servers for the TACACS+ protocol. Then the SCE platform TACACS+ client must be configured to work with the TACACS+ servers. The following information must be configured:
•TACACS+ server hosts definition — a maximum of three servers is supported.
For each sever host, the following information can be configured:
–hostname (required)
–port
–encryption key
–timeout interval
•Default encryption key (optional) — A global default encryption key may be defined. This key is defined as the key for any server host for which a key is not explicitly configured when the server host is defined.
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.
•Default timeout interval (optional) — A global default timeout interval may be defined. This timeout interval is defined as the timeout interval for any server host for which a timeout interval is not explicitly configured when the server host is defined.
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 SCE platform TACACS+ client are explained in the following sections:
•How to Add a New TACACS+ Server Host
•How to Remove a TACACS+ Server Host
•How to Configure the Global Default Key
•How to Configure the Global Default Timeout
How to Add a New TACACS+ Server Host
Use this command to define a new TACACS+ server host that is available to the SCE platform TACACS+ client.
The Service Control solution supports a maximum of three TACACS+ server hosts.
Options
The following options are available:
•host-name — name of the server
•port number — TACACS+ port number
–Default = 49
•timeout interval — time in seconds that the server waits for a reply from the server host before timing out
–Default = 5 seconds or user-configured global default timeout interval (see How to Define the Global Default Timeout.)
•key-string — encryption key that the server and client will use when communicating with each other. Make sure that the specified key is actually configured on the TACACS+ server host.
–Default = no key or user-configured global default key (see How to Define a Global Default Key.)
Step 1 From the SCE(config)# prompt, type tacacs-server host host-name [port portnumber] [timeout timeout-interval] [key key-string] and press Enter.
How to Remove a TACACS+ Server Host
Options
The following options are available:
•host-name — name of the server to be deleted
Step 1 From the SCE(config)# prompt, type no tacacs-server host host-name and press Enter.
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:
•key-string — default encryption key that all TACACS+ servers and clients will use when communicating with each other. Make sure that the specified key is actually configured on the TACACS+ server hosts.
–Default = no encryption
How to Define a Global Default Key
Step 1 From the SCE(config)# prompt, type tacacs-serverkey key-string and press Enter.
How to Clear the Global Default Key
Step 1 From the SCE(config)# prompt, type no tacacs-server key and press Enter.
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:
•timeout interval — default time in seconds that the server waits for a reply from the server host before timing out.
–Default = 5 seconds
How to Define the Global Default Timeout
Step 1 From the SCE(config)# prompt, type tacacs-server timeout timeout-interval and press Enter.
How to Clear the Global Default Timeout
Step 1 From the SCE(config)# prompt, type no tacacs-server timeout and press Enter.
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:
•Username
•Password — may configured as encrypted or unencrypted
•Privilege level
The procedures for managing the local user database are explained in the following sections:
•How to Add a New User to the Local Database
•How to Define the User Privilege Level
•How to Add a New User with Privilege Level and Password
•How to Delete a User
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
•How to Add a User with a Clear Text Password
•How to Add a User with No Password
•How to Add a User with an MD5 Encrypted Password Entered in Clear Text
•How to Add a User with an MD5 Encrypted Password Entered as an MD5 Encrypted String
Options
The password is defined with the username. There are several password options:
•No password — Use the nopassword keyword.
•Password — Password is saved in clear text format in the local list.
Use the password parameter.
•Encrypted password — Password is saved in encrypted (MD5) form in the local list. Use the secret keyword.
Password may be defined by either of the following methods:
–Specify a clear text password, which is saved in MD5 encrypted form
–Specify an MD5 encryption string, which is saved as the user MD5-encrypted secret password
The following options are available:
•name — name of the user to be added
•password — a clear text password. May be saved in the local list in either of two formats:
–as clear text
–in MD5 encrypted form if the secret keyword is used
•encrypted-secret — an MD5 encryption string password
The following keywords are available:
•nopassword — There is no password associated with this user
•secret — the password is saved in MD5 encrypted form. Use with either of the following keywords to indicate the format of the password as entered in the command:
–0 — use with the password option to specify a clear text password that will be saved in MD5 encrypted form
–5 — use with the encrypted-secret option to specify an MD5 encryption string that will be saved as the user MD5-encrypted secret password
How to Add a User with a Clear Text Password
Step 1 From the SCE(config)# prompt, type username name password password and press Enter.
How to Add a User with No Password
Step 1 From the SCE(config)# prompt, type username name nopassword and press Enter.
How to Add a User with an MD5 Encrypted Password Entered in Clear Text
Step 1 From the SCE(config)# prompt, type username name secret 0 password and press Enter.
How to Add a User with an MD5 Encrypted Password Entered as an MD5 Encrypted String
Step 1 From the SCE(config)# prompt, type username name secret 5 encrypted-secret and press Enter.
How to Define the User Privilege Level
•About the User Privilege Level
•Options
About the User Privilege Level
Privilege level authorization in the SCE platform 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 SCE platform sends an authentication request to the TACACS+ server specifying the requested privilege level. The SCE platform 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:
•name — name of the user whose privilege level is set
•level — the privilege level permitted to the specified user. These levels correspond to the CLI authorization levels, which are entered via the enable command:
–0 — User
–10 — Admin
–15 (default) — Root
Step 1 From the SCE(config)# prompt, type username name privilege level and press Enter.
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 In the config files ( running config and startup config ), this command will appear as two separate commands.
•Options
•How to Add a User with a Privilege Level and a Clear Text Password
•How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered in Clear Text
•How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered as an MD5 Encrypted String
Options
The following options are available:
•name — name of the user whose privilege level is set
•level — the privilege level permitted to the specified user. These levels correspond to the CLI authorization levels, which are entered via the enable command:
–0 — User
–10 — Admin
–15 (default) — Root
•password — a clear text password. May be saved in the local list in either of two formats:
–as clear text I
–n MD5 encrypted form if the secret keyword is used
•encrypted-secret — an MD5 encryption string password
The following keywords are available:
•secret — the password is saved in MD5 encrypted form. Use with either of the following keywords to indicate the format of the password as entered in the command:
–0 — use with the password option to specify a clear text password that will be saved in MD5 encrypted form
–5 = use with the encrypted-secret option to specify an MD5 encryption string that will be saved as the user MD5-encrypted secret password
How to Add a User with a Privilege Level and a Clear Text Password
Step 1 From the SCE(config)# prompt, type username
name privilege level password password and press Enter.
How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered in Clear Text
Step 1 From the SCE(config)# prompt, type username name privilege level secret 0 password and press Enter.
How to Add a User with a Privilege Level and an MD5 Encrypted Password Entered as an MD5 Encrypted String
Step 1 From the SCE(config)# prompt, type username name privilege level secret 5 encrypted-secret and press Enter.
How to Delete a User
Options
The following options are available:
•name — name of the user to be deleted
Step 1 From the SCE(config)# prompt, type no username name and press Enter.
Configuring AAA Login Authentication
There are two features to be configured for login authentication:
•Maximum number of permitted Telnet login attempts
•The authentication methods used at login (see General AAA Fallback and Recovery Mechanism.)
The procedures for configuring login authentication are explained in the following sections:
•Configuring Maximum Login Attempts
•How to Configure the Login Authentication Methods
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:
•number-of-attempts — The maximum number of login attempts that will be permitted before the telnet session is terminated.
This is relevant only for Telnet sessions. From the local console, the number of re-tries is unlimited.
–Default = three
Step 1 From the SCE(config)# prompt, type aaa authentication attempts login number-of-attempts and press Enter.
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
•How to Specify the Login Authentication Methods
•How to Delete the Login Authentication Methods List
Options
The following options are available:
•method — the login authentication methods to be used. You may specify up to four different methods, in the order in which they are to be used.
–group TACACS+ — Use TACACS+ authentication.
–local — Use the local username database for authentication
–enable (default) — Use the " enable " password for authentication
–none — Use no authentication.
How to Specify the Login Authentication Methods
Step 1 From the SCE(config)# prompt, type aaa authentication login default method1 [method2...] and press Enter.
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 From the SCE(config)# prompt, type no aaa authentication login default and press Enter.
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.
Configuring AAA Privilege Level Authorization Methods
•Options
•How to Specify AAA Privilege Level Authorization Methods
•How to Delete the AAA Privilege Level Authorization Methods List
Options
The following options are available:
•method — the login authorization methods to be used. You may specify up to four different methods, in the order in which they are to be used.
–group TACACS+ — Use TACACS+ authorization.
–local — Use the local username database for authorization
–enable (default) — Use the " enable " password for authorization
–none — Use no authorization.
How to Specify AAA Privilege Level Authorization Methods
Step 1 From the SCE(config)# prompt, type aaa authentication enable default method1 [method2...] and press Enter.
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 From the SCE(config)# prompt, type no aaa authentication enable default and press Enter.
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.
Configuring AAA Accounting
Use this command to enable or disable TACACS+ accounting.
•About AAA Accounting
•Options
•How to Enable AAA Accounting
•How to Disable AAA Accounting
About AAA Accounting
If TACACS+ accounting is enabled, the SCE platform sends an 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:
•level — The privilege level for which to enable the TACACS+ accounting
How to Enable AAA Accounting
Step 1 From the SCE(config)# prompt, type aaa authentication accounting commands level default stop-start group tacacs+ and press Enter.
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 From the SCE(config)# prompt, type aaa authentication accounting commands level default and press Enter.
Monitoring TACACS+ Servers
Use these commands to display statistics for the TACACS+ servers.
•How to Display Statistics for TACACS+ Servers
•How to Display Statistics, Keys and Timeouts for TACACS+ Servers
How to Display Statistics for TACACS+ Servers
Step 1 From the SCE# prompt, type show tacacs and press Enter.
How to Display Statistics, Keys and Timeouts for TACACS+ Servers
Step 1 From the SCE# prompt, type show tacacs all and press Enter.
Note 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.
Monitoring TACACS+ Users
Use this command to display the users in the local database, including passwords.
Step 1 From the SCE# prompt, type show users and press Enter.
Note 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.
Configuring Access Control Lists (ACLs)
•About Access Control Lists
•Options
•How to Add Entries to an ACL
•How to Remove an ACL
•How to Enable an ACL
About Access Control Lists
The SCE platform can be configured with Access Control Lists (ACLs), which are used to globally permit or deny incoming connections on the management interface. An access list is an ordered list of entries, each consisting of an IP address and an optional wildcard "mask" defining an IP address range, and a permit/deny field.
The order of the entries in the list is important. The default action of the first entry that matches the connection is used. If no entry in the Access List matches the connection, or if the Access List is empty, the default action is deny.
Configuration of system access is done in two stages:
1. Creating an access list. ( How to Add Entries to an ACL).
2. Enabling the access list. (See How to Enable an ACL.)
Creating an access list is done entry by entry, from the first to the last.
When the system checks for an IP address on an access list, the system checks each line in the access list for the IP address, starting at the first entry and moving towards the last entry. The first match that is detected (that is, the IP address being checked is found within the IP address range defined by the entry) determines the result, according to the permit/deny flag in the matched entry. If no matching entry is found in the access list, access is denied.
You can create up to 99 access lists.
An ACL is enabled by the ip access-class command. If an ACL is enabled, when a request comes in, the SCE platform first checks if there is permission for access from that IP address. If not, the SCE does not respond to the request. The basic IP interface is low-level, blocking the IP packets before they reach the interfaces.
If no ACL is enabled, access is permitted from all IP addresses.
Note The SCE Platform will respond to ping commands only from IP addresses that are allowed access. Pings from a non-authorized address will not receive a response from the SCE platform, as ping uses ICMP protocol.
Options
The following options are available:
•number — the ID number assigned to the Access Control List
•ip-address — the IP address of the interface to be permitted or denied. Enter in x.x.x.x format.
•ip-address/mask — configures a range of addresses in the format x.x.x.x y.y.y.y where x.x.x.x specifies the prefix bits common to all IP addresses in the range, and y.y.y.y is a wildcard-bits mask specifying the bits that are ignored. In this notation, `0' means bits to ignore.
The following keywords are available:
•permit — the specified IP addresses have permission to access the SCE platform.
•deny — the specified IP addresses are denied access to the SCE platform.
How to Add Entries to an ACL
Step 1 Type configure and press Enter.
Enables Global Configuration mode.
Step 2 Enter the desired IP address or addresses.
•To configure one IP address type:
access-list number permit|deny ip-address and press Enter.
•To configure more than one IP address type:
access-list number permit|deny ip-address/mask and press Enter.
When you add a new entry to an ACL, it is always added to the end of the list.
Adding Entries to an ACL: Example
The following example adds an entry to the access list number 1, that permits access only to IP addresses in the range of 10.1.1.0-10.1.1.255.
SCE(config)#access-list 1 permit 10.1.1.0 0.0.0.255
How to Remove an ACL
Use this command to remove an ACL with all its entries.
Step 1 From the SCE(config)# prompt, type no access-list number and press Enter.
Removes the specified ACL with all its entries.
How to Enable an ACL
An ACL permits or denies all traffic to the SCE platform.
Step 1 From the SCE(config)# prompt, type ip access-class number and press Enter.
Applies the specified ACL to all traffic attempting to access the SCE platform.
Managing the Telnet Interface
•About the Telnet Interface
•How to Prevent Telnet Access
•How to Configure the Telnet Timeout
About the Telnet Interface
This section discusses the Telnet interface of the SCE platform. A Telnet session is the most common way to connect to the SCE platform CLI interface.
You can set the following parameters for the Telnet interface:
•Enable/disable the interface
•Timeout for Telnet sessions, that is, if there is no activity on the session, how long the SCE platform waits before automatically cutting off the Telnet connection.
The following commands are relevant to Telnet interface:
•line vty
•[no] access list
•[no] service telnetd
•[no] timeout
•show line vty timeout
How to Prevent Telnet Access
Use this command to disable access by Telnet altogether.
Step 1 From the SCE(config)# prompt, type no service telnetd and press Enter.
Current Telnet sessions are not disconnected, but no new Telnet sessions are allowed.
How to Configure the Telnet Timeout
The SCE platform supports timeout of inactive Telnet sessions.
Options
The following options are available:
•timeout — The length of time in minutes before an inactive Telnet session will be timed-out.
–Default — 30 minutes
Step 1 From the SCE(config-line)# prompt, type timeout timeout , and press Enter.
Configuring the SSH Server
•The SSH Server
•Key Management
•Managing the SSH Server
•How to Monitor the Status of the SSH Server
The SSH Server
A shortcoming of the standard telnet protocol is that it transfers password and data over the net unencrypted, thus compromising security. Where security is a concern, using a Secure Shell (SSH) server rather than telnet is recommended.
An SSH server is similar to a telnet server, but it uses cryptographic techniques that allow it to communicate with any SSH client over an insecure network in a manner which ensures the privacy of the communication. CLI commands are executed over SSH in exactly the same manner as over telnet.
The SSH server supports both the SSH-1 and SSH-2 protocols.
Key Management
Each SSH server should define a set of keys (DSA2, RSA2 and RSA1) to be used when communicating with various clients. The key sets are pairs of public and private keys. The server publishes the public key while keeping the private key in non-volatile memory, never transmitting it to SSH clients.
Note The keys are kept on the tffs0 file system, which means that a person with knowledge of the `enable' password can access both the private and public keys.
The SSH server implementation provides protection against eavesdroppers who can monitor the management communication channels of the SCE platform, but it does not provide protection against a user with knowledge of the `enable' password.
Key management is performed by the user via a special CLI command. A set of keys must be generated at least once before enabling the SSH server.
Size of the encryption key is always 2048 bits.
Managing the SSH Server
•How to Monitor the Status of the SSH Server
Use these commands to manage the SSH server. These commands do the following:
•Generate an SSH key set
•Enable/disable the SSH server
•Enable/disable SSHv1. (Disabling SSHv1 allows you to run SSHv2 only.)
•Delete existing SSH keys
How to Generate a Set of SSH Keys
Remember that you must generate a set of SSH keys before you enable the SSH server.
Step 1 From the SCE(config)# prompt, type ip ssh key generate and press Enter.
Generates a new SSH key set and immediately saves it to non-volatile memory. (Key set is not part of the configuration file). Key size is always 2048 bits.
How to Enable the SSH Server
Step 1 From the SCE(config)# prompt, type ip ssh and press Enter.
How to Disable the SSH Server
Step 1 From the SCE(config)# prompt, type no ip ssh and press Enter.
How to Run Only SSHv2
Step 1 From the SCE(config)# prompt, type ip ssh and press Enter.
Step 2 From the SCE(config)# prompt, type no ip ssh sshv1 and press Enter
To re-enable SSHv1, use the command ip ssh SSHv1.
How to Delete the Existing SSH Keys
Step 1 From the SCE(config)# prompt, type ip ssh key remove and press Enter.
Removes the existing SSH key set from non-volatile memory.
If the SSH server is currently enabled, it will continue to run, since it only reads the keys from non-volatile memory when it is started. However, if the startup-configuration specifies that the SSH server is enabled, the SCE platform will not be able to start the SSH server on startup if the keys have been deleted. To avoid this situation, after executing this command, always do one of the following before the SCE platform is restarted (using reload ):
•Generate a new set of keys.
•Disable the SSH server and save the configuration.
How to Monitor the Status of the SSH Server
Use this command to monitor the status of the SSH sever, including current SSH sessions.
Step 1 From the SCE> prompt, type show ip ssh and press Enter.
This is a User Exec command. Make sure that you are in User Exec command mode by exiting any other modes.
Enabling the SNMP Interface
Use this command to explicitly enable the SNMP interface.
The SNMP interface is implicitly enabled when any snmp-server command is executed to configure any SNMP parameter. For more information on configuring and managing the SNMP parameters, including hosts, communities, contact, location, and trap destination hosts, see Configuring and Managing the SNMP Interface.
•How to Enable the SNMP Interface
•How to Disable the SNMP Interface
How to Enable the SNMP Interface
You must define at least one community string to allow SNMP access. For complete information on community strings see Configuring SNMP Community Strings.
Step 1 From the SCE(config)# prompt, type snmp-server enable and press Enter.
How to Disable the SNMP Interface
Step 1 From the SCE(config)# prompt, type no snmp-server and press Enter.
Configuring and Managing the SNMP Interface
•About the SNMP Interface
•Configuring SNMP Community Strings
•How to Configure SNMP Notifications
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.
•SNMP Protocol
•Security Considerations
•About CLI
•About MIBs
•Configuration via SNMP
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.
SCE platform supports the original SNMP protocol (also known as SNMPv1), and a newer version called Community-based SNMPv2 (also known as SNMPv2C).
•SNMPv1 — is the first version of the Simple Network Management Protocol, as defined in RFCs 1155 and 1157, and is a full Internet standard. SNMPv1 uses a community-based form of security.
•SNMPv2c — is the revised protocol, which includes improvements to SNMPv1 in the areas of protocol packet types, transport mappings, and MIB structure elements but using the existing SNMPv1 administration structure. It is defined in RFC 1901, RFC 1905, and RFC 1906.
SCE platform 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 SCE platform:
Table 5-2 Request Types
|
|
|
Set Request |
Writes new data to one or more of the objects managed by an agent. |
Set operations immediately affect the SCE platform running-config but do not affect the startup config |
Get Request |
Requests the value of one or more of the objects managed by an agent. |
|
Get Next Request |
Requests the Object Identifier(s) and value(s) of the next object(s) managed by an agent. |
|
Get Response |
Contains the data returned by an agent. |
|
Trap |
Sends an unsolicited notification from an agent to a manager, indicating that an event or error has occurred on the agent system |
SCE platform may be configured to send either SNMPv1 or SNMPv2 style traps. |
Get Bulk Request |
Retrieves large amounts of object information in a single Request / response transaction. GetBulk behaves as if many iterations of GetNext request/responses were issued, except that they are all performed in a single request/response. |
This is newly defined SNMPv2c message. |
Security Considerations
By default, the SNMP agent is disabled for both read and write operations. When enabled, SNMP is supported over the management port only (in-band management is not supported).
In addition, the SCE platform supports the option to configure community of managers for read-write accessibility or for read-only accessibility.
About CLI
•CLI
•CLI Commands for Configuring SNMP
•CLI Commands for Monitoring SNMP
CLI
The SCE platform 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 disabled 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.
•snmp-server enable
•no snmp-server
•[no] snmp-server community [all]
•[no | default] snmp-server enable traps
•[no] snmp-server host [all]
•[no] snmp-server contact
•[no] snmp-server location
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:
•show snmp (available when SNMP agent is disabled)
•show snmp community
•show snmp contact
•show snmp enabled
•show snmp host
•show snmp location
•show snmp MIB (available when SNMP agent enabled and community was set)
•show snmp traps
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.
For further information concerning MIBs used by the Cisco SCE8000 platform, see the Cisco Service Control MIBs, page A-1
Configuration via SNMP
SCE platform 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 enterprise MIB objects.
It should be noted also that the SCE platform 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.
Configuring SNMP Community Strings
•How to Define a Community String
•How to Remove a Community String
•How to Display the Configured 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:
•SNMP Get , Get-next , and Get-bulk requests are valid if the community string in the request matches the read-only community.
•SNMP Get , Get-next , Get-bulk and Set requests are valid if the community string in the request matches the agent's read-write community.
How to Define a Community String
Options
The following options are available:
•community-string — a security string that identifies a community of managers who are permitted to access the SNMP server
The following keywords are available:
•ro — read only (default accessibility)
•rw — read and write
Step 1 From the SCE(config)# prompt, type snmp-server community community-string ro|rw and press Enter.
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.
Since read-only is the default, it does not need to be defined explicitly.
SCE(config)#snmp-server community mycommunity
How to Remove a Community String
Step 1 From the SCE(config)# prompt, type no snmp-server community community-string and press Enter.
Removing a Community String: Example
The following example shows how to remove a community string called "mycommunity".
SCE(config)#no snmp-server community mycommunity
How to Display the Configured Community Strings
Step 1 From the SCE> prompt, type show snmp-server community community-string and press Enter.
Displaying the Configured Community Strings: Example
The following example shows how to display the configured SNMP communities.
SCE>show snmp community
Community: public, Access Authorization: RO, Access List Index: 1
SCE>
How to Configure SNMP Notifications
Use these commands to configure:
•The destinations that will receive SNMP notifications (hosts)
•Which types of notifications will be sent (traps)
•About SNMP Notifications
•How to Define SNMP Hosts
About SNMP Notifications
Notifications are unsolicited messages that are generated by the SNMP agent that resides inside the SCE platform 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 SCE platform is not configured to send any SNMP notifications. You must define the Network Management System to which the SCE platform 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 SCE platform, an SNMP notification is sent from the SCE platform to the list of IP addresses that you define.
SCE platform supports two general categories of notifications according to the configurations per MIBs. (add here link to the support list --TBD)
SCE platform supports two general categories of notifications:
•Standard SNMP notifications - As defined in RFC1157 and using the conventions defined in RFC1215.
•Proprietary service control enterprise notifications - As defined in the service control proprietary MIB (See Table A-22 on page A-22).
After a host or hosts are configured to receive notifications, by default, the SCE platform sends to the host or hosts all the notifications supported by the SCE platform except for the AuthenticationFailure notification. The SCE platform provides the option to enable or disable the sending of this notification, as well as some of the SCE enterprise notifications, explicitly.
SCE platform can be configured to generate either SNMPv1 style or SNMPv2c style notifications. By default, the SCE platforms sends SNMPv1 notifications.
Following are some sample procedures illustrating how to do the following:
•Configure hosts (NMS) to which the SNMP agent should send notifications
•Remove/disable a host (NMS) from receiving notifications
•Enable the SNMP agent to send authentication-failure notifications
•Enable the SNMP agent to send enterprise notifications
•Reset all notifications to the default setting
How to Define SNMP Hosts
Use this command to define the hosts that will receive notifications from the SCE platform.
•Options
•How to Configure the SCE Platform to Send Notifications to a Host (NMS)
•How to Configure the SCE Platform to Stop Sending Notifications to a Host
•How to Configure SNMP Traps
Options
The following options are available:
•ip-address — the IP address of the SNMP server host
•community-string — a security string that identifies a community of managers who are permitted to access the SNMP server
•version — SNMP version running in the system. Can be set to 1 or 2c.
–Default — 1 (SNMPv1)
How to Configure the SCE Platform to Send Notifications to a Host (NMS)
Step 1 At the SCE(config)# prompt, type snmp-server host ip-address community-string and press Enter.
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 SCE Platform to Send Notifications to Multiple Hosts: Example
The following example shows how to configure the SCE platform to send SNMPv1 notifications to several hosts.
SCE(config)#snmp-server host 10.10.10.10 mycommunity
SCE(config)#snmp-server host 20.20.20.20 mycommunity
SCE(config)#snmp-server host 30.30.30.30 mycommunity
SCE(config)#snmp-server host 40.40.40.40 mycommunity
How to Configure the SCE Platform to Stop Sending Notifications to a Host
Step 1 At the SCE(config)# prompt, type no snmp-server host ip-address and press Enter.
Configuring the SCE Platform 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".
SCE(config)#no snmp-server host 192.168.0.83
How to Configure SNMP Traps
Use this command to configure the notifications that will be sent to the defined host.
•Options
•How to Enable the SNMP Server to Send Authentication Failure Notifications
•How to Enable the SNMP Server to Send All Enterprise Notifications
•How to Enable the SNMP Server to Send a specific Enterprise Notification
•How to Restore All Notifications to the Default Status
Options
The following options are available:
•snmp — optional parameter that specifies that all or specific snmp traps should be enabled or disabled.
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 .
•enterprise — optional parameter that specifies that all or specific enterprise traps should be enabled or disabled.
By default, enterprise traps are enabled.
•enterprise trap name — optional parameter that specifies a specific snmp trap that should be enabled or disabled.
Values: attack, chassis, link-bypass, logger, operational-status, port-operational-status, pull-request-failure, RDR-formatter, session, SNTP, subscriber, system-reset, telnet, vas-traffic-forwarding
Use these parameters as follows:
•To enable/disable all traps of one type: Specify only snmp or enterprise .
•To enable/disable only one specific trap: Specify snmp or enterprise with the additional trap name parameter naming the desired trap.
•To enable/disable all traps: Do not specify either snmp or enterprise .
How to Enable the SNMP Server to Send Authentication Failure Notifications
Step 1 At the SCE(config)# prompt, type snmp-server enable traps snmp authentication and press Enter.
How to Enable the SNMP Server to Send All Enterprise Notifications
Step 1 At the SCE(config)# prompt, type snmp-server enable traps enterprise and press Enter.
How to Enable the SNMP Server to Send a specific Enterprise Notification
Step 1 At the SCE(config)# prompt, type snmp-server enable traps enterprise [attack|chassis|link-bypass|logger|operational-status|port-operational-status|pull-request-failure|RDR-formatter|session| SNTP|subscriber|system-reset|telnet|vas-traffic-forwarding] and press Enter.
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.
SCE(config)#snmp-server enable traps enterprise logger
How to Restore All Notifications to the Default Status
Step 1 At the SCE(config)# prompt, type default snmp-server enable traps and press Enter.
Resets all notifications supported by the SCE platform to their default status.
IP Configuration
•Configuring the IP Routing Table
•IP Advertising
•How to Configure the IP Address of the Management Interface
Configuring the IP Routing Table
•About the IP Routing Table
•How to Configure the Default Gateway
•How to Add an Entry to the IP Routing Table
•How to Display the IP Routing Table
About the IP Routing Table
For handling IP packets on the out-of-band MNG port, the SCE platform maintains a static routing table. When a packet is sent, the system checks the routing table for proper routing, and forwards the packet accordingly. In cases where the SCE platform cannot determine where to route a packet, it sends the packet to the default gateway.
SCE platform supports the configuration of the default gateway as the default next hop router, as well as the configuration of the routing table to provide different next hop routers for different subnets (for maximum configuration of 10 subnets).
The following sections illustrate how to use CLI commands to configure various parameters.
The following commands are relevant to IP routing tables:
•ip default-gateway
•ip route prefix mask next-hop
•no ip route all
•no ip route prefix mask
•show ip route
•show ip route prefix
•show ip route prefix mask
How to Configure the Default Gateway
Options
The following option is available:
•ip-address—the IP address of the default gateway.
Step 1 From the SCE(config)# prompt, type ip default-gateway ip-address, and press Enter.
Configuring the Default Gateway: Example
The following example shows how to set the default gateway IP of the SCE platform to 10.1.1.1.
SCE(config)#ip default-gateway 10.1.1.1
How to Add an Entry to the IP Routing Table
Options
The following options are available:
•prefix — IP address of the routing entry, in dotted notation.
•mask — The relevant subnet mask, in dotted notation
•next-hop — The IP address of the next hop in the route, in dotted notation.
Must be within the MNG interface subnet.
Step 1 From the SCE(config)# prompt, type ip route
prefix mask next-hop, and press Enter.
Adds the specified IP routing entry to the routing table.
How to Add an Entry to the IP Routing Table: Example
The following example shows how to set the router 10.1.1.250 as the next hop to subnet 10.2.0.0.
SCE(config)#ip route 10.2.0.0 255.255.0.0 10.1.1.250
How to Display the IP Routing Table
•How to Display the Entire IP Routing Table
•How to Display the IP Routing Table for a Specified Subnet
How to Display the Entire IP Routing Table
Step 1 From the SCE# prompt, type show ip route and press Enter.
Displays the entire routing table and the destination of last resort (default-gateway)
Displaying the Entire IP Routing Table: Example
This example shows how to display the routing table.
SCE#show ip route
gateway of last resort is 10.1.1.1
| prefix | mask | next hop |
|-----------------|------------------|-----------------|
| 10.2.0.0 | 255.255.0.0 | 10.1.1.250 |
| 10.3.0.0 | 255.255.0.0 | 10.1.1.253 |
| 198.0.0.0 | 255.0.0.0 | 10.1.1.251 |
| 10.1.60.0 | 255.255.255.0 | 10.1.1.5 |
How to Display the IP Routing Table for a Specified Subnet
Options
The following options are available:
•prefix — IP address of the routing entry, in dotted notation.
•mask — The relevant subnet mask, in dotted notation
Step 1 From the SCE# prompt, type show ip route prefix mask and press Enter.
Displays the routing table for the specified subnet (prefix/mask).
Displaying the IP Routing Table for a Specified Subnet: Example
This example shows how to display the routing table for a specified subnet.
SCE#show ip route 10.1.60.0 255.255.255.0
| prefix | mask | next hop |
|-----------------|-----------------|-----------------|
| 10.1.60.0 | 255.255.255.0 | 10.1.1.5 |
sce#
IP Advertising
•Configuring IP Advertising
•How to Display the Current IP Advertising Configuration
IP advertising is the act of periodically sending ping requests to a configured address at configured intervals. This maintains the SCE platform 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:
•[no] ip advertising
•ip advertising destination
•ip advertising interval
•default ip advertising destination
•default ip advertising interval
•show ip advertising
•show ip advertising destination
•show ip advertising interval
Configuring 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:
•interval — The time interval between pings in seconds.
default interval = 300 seconds
•destination — The IP address of the destination for the ping requests
default destination = 127.0.0.1
How to Enable IP Advertising
Step 1 From the SCE(config)# prompt, type ip advertising and press Enter.
Enables IP advertising.
How to Configure the IP Advertising Destination
Step 1 From the SCE(config)# prompt, type ip advertising destination destination, and press Enter.
Configures the destination for the IP advertising pings.
How to Configure the IP Advertising Interval
Step 1 From the SCE(config)# prompt, type ip advertising interval interval, and press Enter.
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.
SCE(config)#ip advertising destination 10.1.1.1
SCE(config)#ip advertising interval 240
How to Display the Current IP Advertising Configuration
Step 1 From the SCE# prompt, type show ip advertising and press Enter.
Displays the status of IP advertising (enabled or disabled), the configured destination, and the configured interval
How to Configure the IP Address of the Management Interface
The user must define the IP address of the management interface.
Note Changing the IP address of the management interface via telnet will result in loss of the telnet connection and inability to reconnect with the interface.
Note After changing the IP address, you must reload the SCE platform (see Rebooting and Shutting Down the SCE Platform, page 3-14) so that the change will take effect properly in all internal and external components of the SCE platform.
Options
The following options are available:
•ip-address — The IP address of the management interface. If both management ports are connected, so that a backup management link is available, this IP address will be act as a virtual IP address for the currently active management port, regardless of which physical port is currently active.
•subnet mask — subnet mask of the management interface.
Step 1 Connect the SCE platform directly to a local console.
Establishes contact with the SCE platform that is not dependent on the configured IP address.
Step 2 From the SCE(config if)# prompt, type ip address ip-address subnet-mask and press Enter.
Configures a new IP address for the management interface
The command might fail if there is a routing table entry that is not part of the new subnet defined by the new IP address and subnet mask..
Configuring the IP Address of the Management Interface: Example
The following example shows how to set the IP address of the SCE platform to 10.1.1.1 and the subnet mask to 255.255.0.0.
SCE(config if)#ip address 10.1.1.1 255.255.0.0
Configuring Time Clocks and Time Zone
•Displaying the System Time
•Displaying the Calendar Time
•Setting the System Clock
•Setting the Calendar
•Setting the Time Zone
•Removing the Current Time Zone Setting
•Configuring Daylight Saving Time
The SCE platform 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 SCE platform does not track Daylight Saving Time automatically, so you must update the time zone when the time changes bi-annually.
The SCE platform has the following two time sources:
•A real-time clock, called the calendar, that continuously keeps track of the time, even when the SCE platform is not powered up. When the SCE platform reboots, the calendar time is used to set the system clock. The calendar is not used for time tracking during system operation.
•A system clock, which creates all the time stamps during normal operation. This clock clears if the system shuts down. During a system boot, the clock is initialized to show the time indicated by the calendar.
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.
Displaying the System Time
Step 1 From the SCE(config)# prompt, type show clock and press Enter.
Displaying the System Time: Example
The following example shows the current system clock.
SCE#show clock
12:50:03 UTC MON November 13 2001
sce#
Displaying the Calendar Time
Step 1 From the SCE(config)# prompt, type show calendar and press Enter.
Displaying the Calendar Time: Example
The following example shows the current system calendar.
SCE#show calendar
12:50:03 UTC MON May 11 2007
sce#
Setting the System Clock
Options
The following option is available:
•time-date the time and date you want to set, in the following format:
hh:mm:ss day month year
Step 1 From the SCE# prompt, type clock set time-date and press Enter.
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.
SCE#clock set 10:20:00 13 may 2007
SCE#clock update-calendar
SCE#show clock
10:21:10 UTC THU May 13 2007
Setting the Calendar
The calendar is a system clock that continues functioning even when the system shuts down.
Options
The following option is available:
•time-date —the time and date you want to set, in the following format:
hh:mm:ss day month year
Step 1 From the SCE# prompt, type calendar set time-date and press Enter.
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 From the SCE# prompt, type clock read-calendar and press Enter.
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.
SCE#calendar set 10:20:00 13 may 20017
SCE#clock read-calendar
SCE#show calendar
10:21:06 UTC THU May 13 2007
Setting the Time Zone
Options
The following options are available:
•zone — The name of the time zone to be displayed.
default = GMT
•hours — The hours offset from UTC. This must be an integer in the range -23 to 23.
default = 0
•minutes — The minutes offset from UTC. This must be an integer in the range of 0 to 59. Use this parameter to specify an additional offset in minutes when the offset is not measured in whole hours.
default = 0
Step 1 From the SCE(config)# prompt, type clock timezone zone hours minutes and press Enter.
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.
SCE(config)#clock timezone PST -10
SCE(config)#
Removing the Current Time Zone Setting
Step 1 From the SCE(config)# prompt, type no clock timezone and press Enter.
Removes the timezone configuration and resets the timezone to the default value (UTC).
Configuring Daylight Saving Time
The SCE platform 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
•Guidelines
•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
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:
•recurring — If daylight saving time always begins and ends on the same day every year, (as in the United States), the clock summer-time recurring command is used. The beginning and ending days for daylight saving time can be configured once, and the system will automatically perform the switch every year.
•not recurring — If the start and end of daylight saving time is different every year, (as in Israel), the clock summer-time command is used. In this case, the transitions must be configured every year for that particular year. (
Note The "year" is not necessarily a calendar year. If the transition days are determined in the fall, the transitions for that fall and the next spring may be configured.
The day on which the transition takes place may be defined in several ways:
•Specific date — For example, March 29, 2004. A specific date, including the year, is defined for a not recurring configuration.
•First/last occurrence of a day of the week in a specified month — For example, the last Sunday in March. This is used for a recurring configuration.
•Day of the week in a specific week in a specified month — For example, Sunday of the fourth week of March. (This would be different from the last Sunday of the month whenever there were five Sundays in the month). This is used for a recurring configuration.
The following options are available:
•zone — the time zone code for daylight saving time
•week (recurring only)— the week of the month on which daylight saving begins (week1) and ends (week2)
•day (recurring only) — the day of the week on which daylight savings begin (day1) and ends (day2)
•date (non-recurring only) — the date of the month on which daylight saving begins (date1) and ends (date2)
•month — the month in which daylight saving begins (month1) and ends (month2)
•year (non-recurring only) — the year in which daylight saving begins (year1) and ends (year2)
•offset — the difference in minutes between standard time and daylight saving time.
Default = 60 minutes
Guidelines
General guidelines for configuring daylight saving time transitions:
•Specify the time zone code for daylight saving time.
•recurring — specify a day of the month (week#|first|last/day of the week/month).
•not recurring — specify a date (month/day of the month/year).
•Define two days:
–Day1 = beginning of daylight saving time.
–Day2 = end of daylight saving time.
•In the Southern hemisphere, month2 must be before month1, as daylight saving time begins in the fall and ends in the spring.
•Specify the exact time that the transition should occur (24 hour clock).
–Time of transition into daylight saving time — according to local standard time.
–Time of transition out of daylight saving time — according to local daylight savings time.
•For the clock summer-time recurring command, the default values are the United States transition rules:
–Daylight saving time begins: 2:00 (AM) on the second Sunday of March.
–Daylight saving time ends: 2:00 (AM) on the first Sunday of November.
How to Define Recurring Daylight Saving Time Transitions
Step 1 From the SCE(config)# prompt, type clock summer-time zone recurring [week1 day1 month1 time1 week2 day2 month2 time2 [ offset ]] and press Enter.
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:
•Daylight saving time begins — 0:00 on the last Sunday of March.
•Daylight saving time ends — 23:59 on the Saturday of fourth week of November.
•Offset = 1 hour (default.
SCE(config)# clock summer-time DST recurring last Sunday March 00:00 4 Saturday November
23:59
How to Define Non-Recurring Daylight Saving Time Transitions
Step 1 From the SCE(config)# prompt, type clock summer-time zone [ date1 month1 year1 time1 date2 month2 year2 time2 [ offset ]] and press Enter.
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:
•Daylight saving time begins — 0:00 on April 16, 2004.
•Daylight saving time ends — 23:59 October 23, 2004.
•Offset = 1 hour (default)
SCE(config)# clock summer-time DST April 16 2004 00:00 October 23 2004 23:59
How to Cancel the Daylight Saving Time Configuration
Step 1 From the SCE(config)# prompt, type no clock summer-time and press Enter.
Removes all daylight saving configuration.
How to Display the Current Daylight Saving Time Configuration
Step 1 From the SCE# prompt, type show timezone and press Enter.
Displays the current time zone and daylight saving time configuration.
Domain Name Server (DNS) Settings
•Configuring DNS Lookup
•Configuring Name Servers
•How to Add a Host to the Host Table
•How to Display Current DNS Settings
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. If the name is in a dotted decimal notation (that is, in the format x.x.x.x), it is directly translated to an IP address it represents.
2. If the name does not contain the dot character (.), the system looks it up in the IP Host table. If the name is found on the table, it is mapped to the corresponding IP address. The IP host table can be configured using the command ip host.
3. If the name does not contain the dot (.) character, and the domain name function is enabled (See the ip domain-lookup command), and a default domain name is specified (See the ip domain-name command), the default domain name is appended to the given name to form a fully qualified host name. This, in turn, is used to perform a DNS query translating the name to an IP address.
4. Otherwise, if the domain name function is enabled, the name is considered to be fully qualified, and is used to perform a DNS query translating the name to an IP address.
The following commands are relevant to DNS settings:
•ip name-server
•ip domain-name
•no ip domain-name
•ip domain-lookup
•show hosts
Configuring DNS Lookup
How to Enable DNS Lookup
Step 1 From the SCE(config)# prompt, type ip domain-lookup and press Enter.
Enables DNS lookup.
How to Disable DNS Lookup
Step 1 From the SCE(config)# prompt, type no ip domain-lookup and press Enter.
Configuring Name Servers
•Options
•How to Define Domain Name Servers
•How to Remove a Domain Name Server
•How to Remove All Domain Name Servers
Options
The following options are available:
•server-ip-address — The IP address of the domain name server. You can define more than one DNS server (server-ip-address1, server-ip-address2, server-ip-address3)
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 From the SCE(config)# prompt, type ip name-server server-address1 [server-address2 [server-address3]] and press Enter.
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.
SCE(config)#ip name-server 10.1.1.60 10.1.1.61
How to Remove a Domain Name Server
Step 1 From the SCE(config)# prompt, type no ip name-server server-address1 [server-address2 [server-address3]] and press Enter.
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.
SCE(config)#no ip name-server 10.1.1.60 10.1.1.61
How to Remove All Domain Name Servers
Step 1 From the SCE(config)# prompt, type no ip name-server and press Enter.
Removes all configured DNS servers.
How to Add a Host to the Host Table
Options
The following options are available:
•hostname — The name of the host.
•ip-address — The IP address of the host
Step 1 From the SCE(config)# prompt, type ip host hostname ip-address and press Enter.
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.
SCE(config)#ip host PC85 10.1.1.61
The following example shows how to remove a hostname together with all its IP mappings.
SCE(config)#no ip host PC85
How to Display Current DNS Settings
Step 1 From the SCE# prompt, type show hosts and press Enter.
Displays current DNS settings.
Displaying Current DNS Settings: Example
The following example shows how to display current DNS information.
SCE#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
sce#