|
|
This chapter describes the major ME1100 Series system administration tasks. For comprehensive documentation of CLI commands, refer to "Command Reference."
This chapter contains:
You can connect to the system in the following ways:
To log into the system, enter a valid username and password at the login prompt. To log out, enter the exit command.
To log into the system, you must enter the username and password for a valid user account.
Each user account has one of two privilege levels---0 or 15. Users with privilege level 15 can use all of the CLI commands. Users with privilege level 0 can use only a subset of the CLI commands, as described in "Command Reference."
When you configure the system using the setup program, you create an administrative user account (with privilege level 15). When you are logged in as an administrative user, you can create, change, and delete other user accounts.
Use the username command to administer user accounts. For more information about the username command, refer to the "username" section.
Enter this command to create a user account named username1 with password password1 and privilege level 0:
# username username1 password password1 privilege level
where username1 is the username, password1 is the account password, and level is the privilege level (0 or 15).
Enter this command to remove the user account:
# no username name
You cannot delete a user account if a user is logged in with that username.
After you create a user account, you can change its properties as described in the following sections.
Level 15 users can change any account password. Level 0 users cannot change account passwords.
To change an account password, enter:
# username username1 password new_password
where username1 is the account name and new_password is the account's new password. The account privilege level does not change.
The rules for changing account privilege levels are:
To change an account privilege level from 0 to 15, enter:
# username username1 password password1 privilege 15
where username1 is the account name, password1 is the account password, and privilege 15 changes the account privilege level to 15. To change the account privilege from 15 to 0, enter the same command, substituting 0 for 15.
Several commands shut down the system. Rebooting the system starts the management services installed on the system, even if they were stopped prior to the reboot.
 |
Caution The system will not operate when it is shut down or is not configured, which can cause serious errors to occur in applications that are using it. |
To shut down the system before powering it off, enter the shutdown command. If you power off the system without entering this command you might disable the system.
To reboot the system, enter the reload command. The login prompt appears when the reboot is complete.
To erase the system configuration and reboot the system, enter the erase config command. After the system reboots you must reconfigure the system using the setup program, as described in the "Configuring the System Using the Setup Program" section.
For more information about these commands, refer to:
The system uses Coordinated Universal Time (UTC) for keeping and displaying the time and date. To display the system time, enter:
# show clock
For more information about the show clock command, refer to the "show clock" section.
You can set and maintain the system date and time using either of two methods:
NTP is the recommended method for configuring time and date on the system. If your network uses NTP to set the date and time on devices, enter the following command to designate an NTP server for the system to use to set the system clock:
# ntp server ip-address
where ip-address is the IP address of an NTP server.
For more information, refer to the "ntp server" section.
If you disable NTP, set the system clock to UTC manually as described in the "Setting Date and Time Manually" section.
|
Caution If you do not set the system clock manually after disabling NTP, the system clock might become inaccurate when the system is rebooted. |
If your network does not use NTP to set the system time on devices and the time is not set correctly, set the date and time to UTC manually by entering:
# clock set hh:mm:ss month day year
where hh:mm:ss is the current time (for example, 13:32:00), month is the current month (for example, January, February), day is the day of the month (for example, 1 to 31), and year is the current year (for example, 2000).
For more information, refer to the "clock" section.
|
Caution You must set the clock to UTC for the system to interact correctly with applications that use it. |
You configure the Ethernet 0 interface when you initially configure the system. If you need to change the interface configuration, use the interface command. For instructions, refer to the "interface" section.
The Ethernet 1 interface is not used.
Register the system in DNS, using the system hostname as its DNS name.
|
Caution If you do not register the system in DNS using the system hostname as its DNS name, network connectivity problems can occur. |
You configure the system to use a DNS server when you initially configure the system. If you need to change the DNS configuration, use the ip name-server command. For information about this command, refer to the "ip name-server" section.
To configure a default domain name, use the ip domain-name command. For information about this command, refer to the "ip domain-name" section.
You can optionally configure the system to be manageable by SNMP. You can configure the following SNMP parameters:
| SNMP Parameter | Description | For More Information |
|---|---|---|
Community | Community strings that allow access to SNMP on system | |
Contact | String that identifies a contact person for system | |
Location | String that identifies system location | |
Name | String that identifies system name |
By itself, the system cannot perform any network management tasks. External management applications use the system to collect and aggregate management data from network devices. To accomplish this, these management applications install management services on the system. Refer to your management application documentation to determine how to install its management services on the system.
The system allows you to administer all the installed management services at once. All commands that affect management services affect all of them at once; the logs that collect services information collect information about all of them.
Management services are restarted automatically when you reboot.
You can stop and restart the management services if the system is not responding correctly to a management application. This should cause the services to reset and function properly again.
To stop management services, enter:
# services stop
To start management services, enter:
# services start
For more information about the services command, refer to the "services" section.
You can remove the management services from the system. You should do this only after you have stopped using the system to collect management data for any applications that were using it.
|
Caution Removing management services stops the system from interacting with management applications that use it, causing serious errors in the applications. |
To remove the management services from the system, enter:
# erase services
This command stops the management services before removing them and erases the logs that collect management services information.
System services (services built into the system) are not removed. Only management services installed by external applications are removed.
The following commands display information about the system:
| Command | Description | For More Information |
|---|---|---|
Display messages logged during last system boot. | ||
Display system date and time. | ||
Display system configuration. | ||
Display information about system network interfaces | ||
Display information about processes running on the system. | ||
show servicesconsole | Display services console. | |
show serviceslog | Display log information about management services activity on system. | |
Display syslog information. | ||
Display information necessary for TAC to assist you. | ||
Display information about current software on the system. |
To view system health statistics, connect to the system using a web browser to verify HTTP connectivity:
For example, if the system IP address is 10.1.58.5, enter the URL http://10.1.58.5 in a web browser.
A login dialog box appears.
Step 2 Enter the username and password you created during setup in the login dialog box.
The system home page appears, displaying the system health statistics described in Table 4-1 and support information:
| Statistic | Description |
|---|---|
Last Boot: | Date of last system boot, in UTC |
Current Time: | Current time, in UTC |
CPU (5sec): | CPU utilization |
RAM Used: | Memory utilization |
Virtual Memory Used: | Virtual memory utilization |
Disk Used: | Disk utilization |
The ME1100 Series has an operating system image and a default system configuration (hereafter collectively called the maintenance image) stored in Flash memory. You can use it to boot the system to perform some system administration tasks and disaster recovery.
You can run only the following commands while the system is running from the maintenance image: reload, erase config, and fsck.
For information about these commands, refer to "Command Reference."
While the maintenance image is running, you can do the following tasks, which you cannot do when the system is booted from the disk:
As a security measure, you can boot from the maintenance image only while connected to the system console.
To boot the system from the maintenance image, follow these steps while connected to the system console:
The following prompt appears during system boot:
Hit <ESC> to enter configuration mode
Step 2 Press Escape while the prompt is displayed:
The following prompt appears:
Current Boot Device: SCSI Hard Disk
1-Change boot order to BootFlash
2-Exit without saving changes
3-Save changes and exit
Step 3 Enter 1.
The following prompt appears:
Current Boot Device:BootFlash
1-Change boot order to SCSI hard disk
2-Exit without saving changes
3-Save changes and exit
Step 4 Enter 3.
The system boots from the maintenance image and automatically logs you in without entering a username or password.
Step 5 When you complete the necessary tasks, reboot the system by entering the reload command and allow the system to boot from the disk (the default boot order).
Refer to the "reload" section for more information about the reload command.
 |
Note If you enter the erase config command, the system reboots automatically, but you must reconfigure it with the setup program. Refer to the "hostname" section for more information. |
If you cannot log in to the system because you cannot remember the administrator account names or passwords, you can recover by booting from the maintenance image, erasing the existing configuration from Flash memory, and reconfiguring the system using the setup program.
|
Caution To reconfigure the system after initial configuration, you must erase the existing configuration. The system will not respond to requests from applications until you reconfigure it. |
To recover from losing all administrator passwords:
Step 2 Enter the erase config command to erase the system configuration. The system reboots.
Step 3 Allow the system to boot from disk (the default boot order).
Step 4 Configure the system from the setup program, as described in the "Configuring the System Using the Setup Program" section.
Step 5 After the system reboots, log in as the user you created during setup.
While the system is running from the maintenance image, you can maintain the disk filesystem with the fsck command.
To maintain the disk filesystem using the fsck command:
Step 2 Enter the fsck command.
The fsck command checks and repairs the filesystem. It might prompt you for confirmation before making certain repairs.
When the command prompt appears, the command is done.
Step 3 Enter the reload command to reboot the system.
Step 4 Allow the system to boot from the disk (the default).
Posted: Mon Jun 19 00:29:58 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.