LANChapter04.docx

1、LANChapter04Chapter 4. Configuring the CatalystThis chapter covers the following key topics: Catalyst 5000/6000 CLI Syntax Conventions Provides the standard Cisco representation for interpreting commands administered on Catalyst switches. Catalyst 5000 Configuration Methods Provides information on h

2、ow to operate under the Console, Telnet, and TFTP configuration modes for Catalyst configuration. Using the Catalyst 5000/6000 Command-Line Interface Describes command-line recall, editing, and help for the Catalyst 5000 series. Passwords Provides documentation on how to set, change, and recover pas

3、swords for the Catalyst 5000/6000 series of switches. Configuration File Management Discusses how to store and restore configuration files on flash and TFTP servers for Supervisor I, II, and III modules. Image File Management Describes how to transfer Supervisor I, II, and III module software images

4、. Redundant Supervisor Modules Discusses how to implement redundant Supervisor modules to ensure system operation in the event of a module failover. Configuring Other Catalysts Provides a quick overview of the configuration methods for the 1900/2800 and the 3000 series of Catalyst switches.Users fam

5、iliar with Cisco routers exercise a command line interface (CLI) embedded in the IOS. The CLI characteristics are seen across nearly all of the router product line. However, most Catalysts CLIs differ from those found on Cisco routers. In fact, the Catalyst family has several CLIs based upon the mod

6、el origins. The Catalyst 4000/5000/6000 series differs from the 3000 series, the 1900,2800 and the 8500 series. This chapter compares differences between the router CLI and the Catalyst 4000/5000/6000 family. It also describes the command line interface including aspects like command line recall, co

7、mmand editing, uploading and downloading code images and configuration files. An overview of the menu driven configuration for the other Catalysts is addressed in the last section, Configuring Other Catalysts. Examples of configuring the Catalyst 8500 series are included in Chapter 11, Layer 3 Switc

8、hing. This deals primarily, however, with the XDI interface used by the Catalyst 4000/5000/6000 family.NoteCisco folklore has it that XDI is the name of a UNIX-like kernel purchased for use in equipment that evolved into the Catalyst 4000, 5000, and 6000 products of today. The XDI CLI is often refer

9、red to as CatOS.The Catalyst product family evolution does not have the same roots as the Cisco router products. Ciscos history begins with the development of routers to interconnect networks. As the router family increased, a number of differences between the early models and the later became evide

10、nt. Particularly with the release of 9.1x, the command line interface vastly differed for the IOS. But the IOS essentially retained the same look and feel after that point across all of the router family. Users of the Catalyst on the other hand may encounter multiple CLIs dependent upon the model us

11、ed. This occurs not because Cisco changed its mind on how to present the CLI, but because some of the products were acquired technologies with a previously installed user base. For example, some of the Catalysts such as the 1900 and 2800 came from Grand Junction and have their own configuration meth

12、ods. Some come from Kalpana, such as the Catalyst 3000, and use a different menu structure. Some were developed by Cisco. For example, the 8500 and the 2900XL, and use IOS type configurations. The Catalyst 5000 family originated with Crescendo. When Cisco acquired Crescendo, a significant user base

13、already familiar with the XDI/CatOS configuration modes existed. The Catalyst 5000 and 6000 series use a CLI which differs from all of the others.This chapter provides an overview for configuring the Catalyst 4000/5000/6000 series products. The CLI syntax and conventions are covered, along with comm

14、and recall and editing methods. Methods for storing and retrieving configuration files images are also explained. Finally, configuring and managing redundant supervisor modules in a Catalyst 5500/6000/6500 are discussed.Catalyst 5000/6000 CLI Syntax ConventionsAll well-documented equipment uses a st

15、andard representation for interpreting commands. The Catalyst is no exception. Cisco documents how to interpret the printed commands of its documentation. Table 4-1 summarizes the command syntax conventions used in the Catalyst documentation and in this book.Table4-1. Catalyst Syntax ConventionsComm

16、and PresentationInterpretationBoldfaceCommands and keywords that are entered literally as shown are in boldface.ItalicArguments for which you supply values are in italics. Elements in square brackets are optional.x | y | zAlternative required keywords are grouped in braces and separated by vertical

17、bars.x | y | zOptional alternative keywords are grouped in brackets and separated by vertical bars.StringA nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.Catalyst 5000 Configuration MethodsWhen you attempt to log in to the Cat

18、alyst, the Catalyst presents you with a password prompt. If you enter the correct password, you enter the Catalysts NORMAL mode. Normal mode equates to a routers User EXEC mode allowing you to view most Catalyst parameters, but not authorizing any configuration changes. To make changes, you must ent

19、er the Catalysts PRIVILEGED mode. The privileged mode functionally equates to the routers PRIVILEGED EXEC mode. In the privileged mode, you can view configuration files and make configuration changes. You enter the Catalysts privileged mode with the enable command. The Catalyst then prompts for a pa

20、ssword.You can access the Catalyst CLI through one of three methods: through the console interface, Telnet, or Trivial File Transfer Protocol (TFTP). The following sections detail each access method.Like a router, commands are additiveadding configuration statements to an existing file does not comp

21、letely overwrite the existing configuration. Suppose you have an existing configuration that assigns ports 2/1-10 to VLAN 5. If you add a configuration that assigns ports 2/1-5 to VLAN 5, but you do nothing to ports 2/6-10, 2/6-10 remain in VLAN 5. The absence of these ports in the new VLAN assignme

22、nt does not remove them from VLAN 5. If, however, the additional configuration includes a line that assigns ports 2/6-10 to VLAN 20, they move VLAN membership.A foolproof way of ensuring that a new configuration completely overwrites an existing file is to enter clear config all (see Example 4-1). I

23、f you clear the configuration from Telnet or TFTP, you do not see this output. You only see this when directly attached to the console. This CLI command returns the Catalyst Supervisor module to its default configuration where all ports belong to VLAN 1, there is no VTP domain (explained in Chapter

24、12, VLAN Trunking Protocol ), and all Spanning Tree parameters back to default values. Note also that entering this command clears the consoles IP address too. You can clear the configuration with any of the access methods, but if you do so while you access the Catalyst through Telnet, you disconnec

25、t from the Catalyst because the Catalyst no longer has an IP address either.Example 4-1 clear config all OutputConsole (enable) clear config Usage: clear config all clear config clear config rmon Console (enable) clear config all This command will clear all configuration in NVRAM. This command will

26、cause ifIndex to be reassigned on the next system startup. Do you want to continue (y/n) n? y . . . System configuration cleared. Use session command to clear ATM or Router specific configurations. Console (enable) From the Supervisor console, or via Telnet, you can clear the Catalyst configuration

27、with the clear config all command. clear config all in Example 4-1 resets the Supervisor module to its defaults. Note that this command does not clear the files for the ATM LANE module, nor for the RSM (or MSM in a Catalyst 6000). This only affects the modules directly configured from the Supervisor

28、 module. To clear the configurations on the ATM or router modules, you need to access the modules with the sessionmodule_number command. This command performs the equivalent of an internal Telnet to the module so that you can make configuration changes. The ATM and router modules use IOS commands to

29、 change, save, and clear configurations.TipConfiguring the Catalyst through the console and through Telnet allows you to enter commands in real time, but only one at a time. Unlike Cisco routers, the Catalyst immediately stores commands in nonvolatile random-access memory (NVRAM) and does not requir

30、e you to perform a copy run start like a router. Any command you type in a Catalyst is immediately remembered, even through a power cycle. This presents a challenge when reversing a series of commands. On a router, you can reverse a series of commands with reload, as long as you didnt write the runn

31、ing configuration into NVRAM.Before making serious changes to a Catalyst, copy the configuration to an electronic notepad. On the Catalyst, use the command set length 0 to terminate the more function, enable screen capture on your device, and enter show config to capture the current configuration. T

32、hen if you do not like the changes you made and cannot easily reverse them, clear config all and replay the captured configuration file to locally restore the starting configuration.Console ConfigurationThe Catalyst 5000 series Supervisor module has one physical console connection. For a Supervisor I or a Supervisor II, the connection is an EIA-232 25-pin connection. For a Supervisor III module, the connection is an RJ-45 connector. Make sure that you know which kind of Supervisor module you are working