|
|
This appendix provides a CLI-based setup procedure for a standalone switch. Before connecting the switch to a power source, review the safety warnings in "Switch Installation."
For an unconfigured switch, you can access the CLI either through Express Setup or through the console port. These sections describe each method:
Express Setup is supported on switches running Cisco IOS Release 12.1(14)EA1 or later. If you are installing an unconfigured switch, refer to the Cisco IOS release label on the rear panel of the switch to determine the software release.
 |
Note For switches running releases earlier than Cisco IOS Release 12.1(14)EA1, go to the "Accessing the CLI Through the Console Port" section. |
You can access the CLI on an unconfigured switch by placing the switch in Express Setup mode and then by connecting a switch Ethernet port to the Ethernet port of your PC or workstation. To put the switch into Express Setup mode, follow the steps described in "Using Express Setup," for powering on the switch and using Express Setup.
After the switch is in Express Setup mode, open a Telnet session to the switch by entering the IP address 10.0.0.1. Enter the setup user EXEC command. See these sections in this chapter to then configure the switch by using the CLI:
After you have entered the configuration information for the switch, save it to Flash memory by using the write memory privileged EXEC command.
|
Note While in Express Setup mode, the IP address 10.0.0.1 is active until you enter the write memory command. You lose the Telnet connection after entering the write memory command. |
For more information about using the CLI, refer to the switch command reference for this release.
You can access the CLI on a configured or unconfigured switch by connecting the console port of the switch to the serial port on your PC or workstation and accessing the switch through a terminal-emulation session. To access the switch through the console port, follow these steps:
Follow these steps to connect the PC or terminal to the switch console port:
Step 2 Attach the DB-9 female DTE of the adapter cable to the PC serial port, or attach an appropriate adapter to the terminal.
Before you power on the switch, start the terminal emulation session so that you can see the output display from the POST.
The terminal-emulation software—frequently a PC application such as Hyperterminal or ProcommPlus—makes communication between the switch and your PC or terminal possible.
Follow these steps to start a terminal-emulation session:
Step 2 Configure the baud rate and character format of the PC or terminal to match these console port default characteristics:
Complete these steps to power on the switch:
Step 2 Connect the other end of the power cable to a grounded AC outlet.
As the switch powers on, it begins POST, a series of tests that run automatically to ensure that the switch functions properly. If POST fails, see the "Understanding POST Results" section to determine a course of action.
If you started the terminal emulation program before you powered on your switch, the PC or terminal displays the bootloader sequence. You need to press Enter to display the setup program prompt. See these sections to then configure the switch by using the CLI:
To set up the switch, you must assign an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also required if you plan to use the CMS to configure and manage the switch.
You will need this information from your network administrator before you complete the setup program:
Follow these steps to complete the setup program and to create an initial configuration for the switch:
Step 2 Enter a host name for the switch, and press Return.
On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.
Step 3 Enter an enable secret password, and press Return.
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces. The secret password is encrypted and the enable password is in plain text.
Step 4 Enter an enable password, and press Return.
Step 5 Enter a virtual terminal (Telnet) password, and press Return.
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.
Step 6 (Optional) Configure SNMP by responding to the prompts. You can also configure SNMP later through the CLI or CMS interface. To configure SNMP later, enter no.
Step 7 Enter the interface name (physical interface or VLAN name) of the interface that connects to the management network, and press Return. For this release, always use vlan1 as that interface.
Step 8 Configure the interface by entering the switch IP address and subnet mask and pressing Return. (The IP address and subnet masks shown here are examples.)
Step 9 Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.
If you enter N, the switch appears as a candidate switch in the CMS. You can configure the switch as a command switch later through the CLI or CMS interface. To configure it later, enter no.
You have now completed the initial configuration of the switch, and the switch displays its initial configuration. This is an example of the output that appears:
Step 10 These choices appear:
Make your selection, and press Return.
After you complete the setup program, the switch can run the default configuration that you created. If you want to change this configuration or want to perform other management tasks, use one of these tools:
To use the CLI, enter commands at the Switch> prompt through the console port or through the network by using Telnet. For configuration information, refer to the switch software configuration guide or the switch command reference.
To use CMS, refer to the software configuration guide.
Posted: Mon Feb 9 09:04:38 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
