|
|
This chapter describes how to perform various administrative tasks on the Catalyst 6000 family switches.
This chapter consists of these sections:
The system name on the switch is a user-configurable string used to identify the device. The default configuration has no system name configured.
If you do not manually configure a system name, the system name is obtained through the Domain Name System (DNS) if you configure the switch as follows:
If the DNS lookup is successful, the DNS host name of the switch is configured as the system name of the switch and is saved in NVRAM (the domain name is removed).
If you have not configured a system prompt, the first 20 characters of the system name are used as the system prompt (a greater-than symbol [>] is appended). The prompt is updated whenever the system name changes, unless you manually configure the prompt using the set prompt command.
The switch performs a DNS lookup for the system name whenever one of the following occurs:
If the system name is user configured, no DNS lookup is performed.
These sections describe how to statically configure the system name and prompt:
To configure a static system name, perform this task in privileged mode:
| Task | Command |
|---|---|
Statically set the system name. | set system name name_string |
This example shows how to configure the system name on the switch:
Console> (enable) set system name Catalyst 6000 System name set. Catalyst 6000> (enable)
To configure a static system prompt, perform this task in privileged mode:
| Task | Command |
|---|---|
Statically set the system prompt. | set prompt prompt_string |
This example shows how to configure the system prompt on the switch:
Console> (enable) set prompt Catalyst6509> Catalyst6509> (enable)
To clear the system name, perform this task in privileged mode:
| Task | Command |
|---|---|
Clear the system name. | set system name |
This example shows how to clear the system name:
Console> (enable) set system name System name cleared. Console> (enable)
You can set the system contact and location to help you with resource management tasks.
To set the system contact and location, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Set the system contact. | set system contact [contact_string] |
Step 2 Set the system location. | set system location [location_string] |
Step 3 Verify the global system information. | show system |
This example shows how to set the system contact and location and verify the configuration:
Catalyst 6000> (enable) set system contact sysadmin@corp.com System contact set. Catalyst 6000> (enable) set system location Sunnyvale CA System location set. Catalyst 6000> (enable) show system PS1-Status PS2-Status Fan-Status Temp-Alarm Sys-Status Uptime d,h:m:s Logout ---------- ---------- ---------- ---------- ---------- -------------- --------- ok none ok off ok 0,04:04:07 20 min PS1-Type PS2-Type Modem Baud Traffic Peak Peak-Time ---------- ---------- ------- ----- ------- ---- ------------------------- other none disable 9600 0% 0% Tue Jun 23 1998, 16:51:36 System Name System Location System Contact ------------------------ ------------------------ ------------------------ Catalyst 6000 Sunnyvale CA sysadmin@corp.com Catalyst 6000> (enable)
To set the system clock, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Set the system clock. | set time [day_of_week] [mm/dd/yy] [hh:mm:ss] |
Step 2 Display the current date and time. | show time |
This example shows how to set the system clock and display the current date and time:
Console> (enable) set time Mon 06/15/98 12:30:00 Mon Jun 15 1998, 12:30:00 Console> (enable) show time Mon Jun 15 1998, 12:30:02 Console> (enable)
You can create a single or multiline message banner that appears on the screen when someone logs in to the switch. The first character following the motd keyword is used to delimit the beginning and end of the banner text. Characters following the ending delimiter are discarded. After entering the ending delimiter, press Return. The banner must be fewer than 3070 characters.
To configure a login banner, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Enter the message of the day. | set banner motd c message_of_the_day c |
Step 2 Display the login banner by logging out and logging back into the switch. |
|
This example shows how to configure the login banner on the switch using the # symbol as the beginning and ending delimiter:
Console> (enable) set banner motd # Welcome to the Catalyst 6000 Switch! Unauthorized access prohibited. Contact sysadmin@corp.com for access. # MOTD banner set Console> (enable)
To clear the login banner, perform this task in privileged mode:
| Task | Command |
|---|---|
Clear the message of the day. | set banner motd cc |
This example shows how to clear the login banner:
Console> (enable) set banner motd ## MOTD banner cleared Console> (enable)
You can use the set alias command to define command aliases (shorthand versions of commands) for frequently used or long and complex commands. Command aliases can save you time and can help prevent typing errors when you are configuring or monitoring the switch.
The name argument defines the command alias. The command and parameter arguments define the command to enter when the command alias is entered at the command line.
To define a command alias on the switch, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Define a command alias on the switch. | set alias name command [parameter] [parameter] |
Step 2 Verify the currently defined command aliases. | show alias [name] |
This example shows how to define two command aliases, sm8 and sp8. sm8 issues the show module 8 command, and sp8 issues the show port 8 command. This example also shows how to verify the currently defined command aliases and what happens when you enter the command aliases at the command line:
Console> (enable) set alias sm8 show module 8 Command alias added. Console> (enable) set alias sp8 show port 8 Command alias added. Console> (enable) show alias sm8 show module 8 sp8 show port 8 Console> (enable) sm8 Mod Module-Name Ports Module-Type Model Serial-Num Status --- ------------------- ----- --------------------- --------- --------- ------- 8 2 DS3 Dual PHY ATM WS-X5166 007243262 ok Mod MAC-Address(es) Hw Fw Sw --- -------------------------------------- ------ ---------- ----------------- 8 00-60-2f-45-26-2f 2.0 1.3 51.1(103) Console> (enable) sp8 Port Name Status Vlan Level Duplex Speed Type ----- ------------------ ---------- ---------- ------ ------ ----- ------------ 8/1 notconnect trunk normal full 45 DS3 ATM 8/2 notconnect trunk normal full 45 DS3 ATM Port ifIndex ----- ------- 8/1 285 8/2 286 Use 'session' command to see ATM counters. Last-Time-Cleared -------------------------- Thu Sep 10 1998, 16:56:08 Console> (enable)
You can use the set ip alias command to define textual aliases for IP addresses. IP aliases can make it easier to refer to other network devices when using ping, telnet, and other commands, even when DNS is not enabled.
The name argument defines the IP alias. The ip_addr argument defines the IP address to which the name refers.
To define an IP alias on the switch, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Define an IP alias on the switch. | set ip alias name ip_addr |
Step 2 Verify the currently defined IP aliases. | show ip alias [name] |
This example shows how to define two IP aliases, sparc and cat6509. sparc refers to IP address 172.20.52.3, and cat6509 refers to IP address 172.20.52.71. This example also shows how to verify the currently defined IP aliases and what happens when you use the IP aliases with the ping command:
Console> (enable) set ip alias sparc 172.20.52.3 IP alias added. Console> (enable) set ip alias cat6509 172.20.52.71 IP alias added. Console> (enable) show ip alias default 0.0.0.0 sparc 172.20.52.3 cat6509 172.20.52.71 Console> (enable) ping sparc sparc is alive Console> (enable) ping cat6509 cat6509 is alive Console> (enable)
In some situations, you might need to add a static routing table entry for one or more destination networks. Static route entries consist of the destination IP network address, the IP address of the next hop router, and the metric (hop count) for the route.
The destination IP network address can be variably subnetted to support Classless Interdomain Routing (CIDR). You can specify the subnet mask (netmask) for a destination network using the number of subnet bits or using the subnet mask in dotted decimal format. If no subnet mask is specified, the default (classful) mask is used.
The switch forwards IP traffic generated by the switch using the longest address match in the IP routing table. The switch does not use the IP routing table to forward traffic from connected devices, only IP traffic generated by the switch itself (for example, Telnet, TFTP, and ping).
To configure a static route, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Configure a static route to the remote network. | set ip route destination[/netmask] gateway [metric] |
Step 2 Verify that the static route appears correctly in the IP routing table. | show ip route |
This example shows how to configure a static route on the switch and how to verify that the route is configured properly in the routing table:
Console> (enable) set ip route 172.16.16.0/20 172.20.52.127 Route added. Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled The primary gateway: 172.20.52.121 Destination Gateway RouteMask Flags Use Interface --------------- --------------- ---------- ----- -------- --------- 172.16.16.0 172.20.52.127 0xfffff000 UG 0 sc0 default 172.20.52.121 0x0 UG 0 sc0 172.20.52.120 172.20.52.124 0xfffffff8 U 1 sc0 default default 0xff000000 UH 0 sl0 Console> (enable)
To enable your Catalyst LAN switch to communicate with devices that do not respond to ARP requests, you can configure a static or permanent ARP entry that maps the IP addresses of those devices to their MAC addresses. You can configure an Address Resolution Protocol (ARP) entry so that it does not age out by configuring it as either static or permanent. When you configure a static ARP entry using the set arp static command, the entry is removed from the ARP cache after a system reset. When you configure a permanent ARP by using the set arp permanent command, the ARP entry is retained even after a system reset.
Because most hosts support dynamic resolution, you usually do not need to specify static or permanent ARP cache entries. When a device does not respond to ARP requests, you can configure an ARP entry to be statically or permanently entered into the ARP cache so that those devices can still be reached.
To configure a static or permanent ARP entry, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Configure a static or permanent ARP entry. | set arp [dynamic | permanent | static] {ip_addr hw_addr} |
Step 2 (Optional) Specify the ARP aging time. | set arp agingtime seconds |
Step 3 Verify the ARP configuration. | show arp |
This example shows how to define a static ARP entry:
Console> (enable) set arp static 20.1.1.1 00-80-1c-93-80-40
Static ARP entry added as
20.1.1.1 at 00-80-1c-93-80-40 on vlan 1
Console> (enable)
This example shows how to define a permanent ARP entry:
Console> (enable) set arp permanent 10.1.1.1 00-80-1c-93-80-60
Permanent ARP entry added as
10.1.1.1 at 00-80-1c-93-80-60 on vlan 1
Console> (enable)
This example sets the ARP aging time:
Console> (enable)set arp agingtime 300ARP aging time set to 300 seconds.Console> (enable)
This example shows how to display the ARP cache:
Console> (enable) show arp ARP Aging time = 300 sec + - Permanent Arp Entries * - Static Arp Entries + 10.1.1.1 at 00-80-1c-93-80-60 on vlan 1 172.20.52.1 at 00-60-5c-86-5b-28 port 8/1 on vlan 1 * 20.1.1.1 at 00-80-1c-93-80-40 port 8/1 on vlan 1 Console> (enable)
To clear ARP entries, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Clear a dynamic, static or permanent ARP entry. | clear arp [dynamic | permanent | static] {ip_addr hw_addr} |
Step 2 Verify the ARP configuration. | show arp |
This example clears all permanent ARP entries and verifies the configuration:
Console> (enable)clear arp permanentPermanent ARP entries cleared.Console> (enable)Console> (enable) show arp ARP Aging time = 300 sec + - Permanent Arp Entries * - Static Arp Entries 172.20.52.1 at 00-60-5c-86-5b-28 port 8/1 on vlan 1 * 20.1.1.1 at 00-80-1c-93-80-40 port 8/1 on vlan 1 Console> (enable)
These sections describe how to schedule a system reset:
You can use the schedule reset command to schedule a system to reset at a future time. This feature allows you to upgrade software during business hours and schedule the system upgrade after business hours to avoid a major impact on users.
You can also use the schedule reset feature when trying out new features on a switch. To avoid misconfiguration or the possibility of losing network connectivity to the device, you can set up the startup configuration feature and schedule a reset to occur in 30 minutes. You can then change the configuration, and if connectivity is lost, the system will reset in 30 minutes and return to the previous configuration.
You can specify an absolute time and date at which the reset should take place, using the reset at command. Entering the month and day argument with this command is optional. If you do not specify the month and day, the reset will take place on the current day if the time specified is later than the current time. If the time scheduled for reset is earlier than the current time, the reset will take place on the following day.
To schedule a reset at a specific time, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Schedule the reset time at a specific time. | reset [mindown] at {hh:mm} [mm/dd] [reason] |
Step 2 Verify the scheduled reset. | show reset |
This example shows how to schedule a reset at a specific time:
Console> (enable)reset at 20:00Reset scheduled at 20:00:00, Wed Aug 18 1999.Proceed with scheduled reset? (y/n) [n]?yReset scheduled for 20:00:00, Wed Aug 18 1999 (in 0 day 5 hours 40 minutes).Console> (enable)
This example shows how to schedule a reset at a specific time and include a reason for the reset:
Console> (enable)reset at 23:00 8/18 Software upgrade to 5.3(1).Reset scheduled at 23:00:00, Wed Aug 18 1999.Reset reason: Software upgrade to 5.3(1).Proceed with scheduled reset? (y/n) [n]?yReset scheduled for 23:00:00, Wed Aug 18 1999 (in 0 day 8 hours 39 minutes).Console> (enable)
This example shows how to schedule a reset with a minimum down time:
Console> (enable)reset mindown at 23:00 8/18 Software upgrade to 5.3(1).Reset scheduled at 23:00:00, Wed Aug 18 1999.Reset reason: Software upgrade to 5.3(1).Proceed with scheduled reset? (y/n) [n]?yReset mindown scheduled for 23:00:00, Wed Aug 18 1999 (in 0 day 8 hours 39 minutes).Console> (enable)
You can schedule a reset within a specified time with the reset in command. For instance, if the current system time is 9:00 a.m. and reset is scheduled in one hour, the scheduled reset will take place at 10:00 a.m. If you or NTP advances the system clock to 10:00 a.m., the reset will take place at 11:00 a.m. If the clock is advanced ahead of the scheduled reset time, the reset will take place 5 minutes after the current time.
To schedule a reset within a specified time, peform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Schedule the reset time within a specific amount of time. | reset [mindown] in [hh] {mm} [reason] |
Step 2 Verify the scheduled reset. | show reset |
This example shows how to schedule a reset in a specified time:
Console> (enable)reset in 5:20 Configuration updateReset scheduled in 5 hours 20 minutes.Reset reason: Configuration updateProceed with scheduled reset? (y/n) [n]?yReset scheduled for 19:56:01, Wed Aug 18 1999 (in 5 hours 20 minutes).Reset reason: Configuration updateConsole> (enable)
This section describes power management in the Catalyst 6000 family switches and includes the following information:
The Catalyst 6000 family modules have different power requirements and, depending upon the wattage of the power supply, certain switch configurations might require more power than a single power supply can provide. Although the power management feature allows you to power all installed modules with two power supplies, redundancy is not supported in this configuration. Redundant and nonredundant power configurations are discussed in the following sections.
To determine the power requirements for your system, see the "Determining System Power Requirements" section.
Use the set power redundancy enable | disable command to enable or disable redundancy (redundancy is enabled by default). With redundancy enabled and two power supplies of equal wattage installed, the total power drawn from both supplies is at no time greater than the capability of one supply. If one supply malfunctions, the other supply can take over the entire system load. When you install and turn on two power supplies of equal wattage, each concurrently provides approximately half of the required power to the system. Load sharing and redundancy are enabled automatically; no software configuration is required.
With redundancy enabled, if you power up the system with two power supplies of unequal wattage, both power supplies will come online but a syslog message is displayed indicating that the lower wattage power supply will be disabled. In the event of the active power supply failing, the lower wattage power supply that was disabled will come online and, if necessary, modules will be powered down to accomodate the lower wattage power supply.
In a nonredundant configuration, the power available to the system is the combined power capability of both power supplies. The system powers up as many modules as the combined capacity allows. However, if one supply should fail and there is not enough power for all previously powered up modules, the system will power down some modules. These modules are marked as power-deny in the show module Status field.
You can change the configuration of the power supplies to redundant or nonredundant at any time. If you switch from a redundant to nonredundant configuration, both power supplies are enabled (even one that was disabled because it was of a lower wattage than the other power supply). Conversely, if you change from a nonredundant to a redundant configuration, both power supplies are initially enabled, and if they are of the same wattage, will remain enabled. If they are of different wattage, a syslog message is displayed and the lower wattage supply is disabled.
Table 14-1 describes how the system responds to changes in the power supply configuration.
| Configuration Change | Effect |
|---|---|
Redundant to nonredundant |
|
Nonredundant to redundant |
|
Equal wattage power supply is inserted with redundancy enabled |
|
Equal wattage power supply is inserted with redundancy disabled |
|
Higher wattage power supply is inserted with redundancy enabled |
|
Lower wattage power supply is inserted with redundancy enabled |
|
Higher or lower wattage power supply is inserted with redundancy disabled |
|
Power supply is removed with redundancy enabled |
|
Power supply is removed with redundancy disabled |
|
System is booted with power supplies of different wattage installed and redundancy enabled |
|
System is booted with power supplies of equal or different wattage installed and redundancy disabled |
|
You can power down a properly working module from the command-line interface (CLI) using the set module power down mod_num command. The module is marked as power-down in the show module Status field. Use the set module power up mod_num command to check if adequate power is available in the system to turn the power on for a module that was previously powered down. If there is not enough power available, the module status changes from power-down to power-deny.
This section describes how to determine the system power requirements for six- and nine-slot chassis. Use the following information to determine your system power requirements:
| Module | Power Requirement |
|---|---|
Supervisor engines (WS-X6K-SUP1A-2GE) (WS-X6K-SUP1-2GE) | 1.70A |
Supervisor engine (WS-X6K-SUP1A-PFC) | 2.50A |
Supervisor engine (WS-X6K-SUP1A-MSFC) | 3.30A |
Multilayer Switching Module (WS-X6302-MSM) | 5.20A |
24-Port 10BaseFL (WS-X6024-10FL-MT) | 1.52A |
24-Port 100FX (WS-X6224-100FX-MT) | 1.90A |
48-Port 10/100TX (WS-X6248-RJ-45) | 2.69A |
8-Port Gigabit Ethernet (WS-X6408-GBIC, WS-X6408A-GBIC) | 2.00A |
16-Port Gigabit Ethernet (WS-X6416-GBIC) | 2.81A |
16-Port Gigabit Ethernet (WS-X6416-GE-MT) | 2.50A |
1-Port OC-12 ATM (WS-X6101-OC12-MMF) | 2.10A |
Total power available with the 1300W power supply is 27.46A. Total power available with the 1000W power supply is 21.40A. | |
Environmental monitoring of chassis components provides early warning indications of possible component failure to ensure safe and reliable system operation and avoid network interruptions. This section describes the monitoring of these critical system components, enabling you to identify and rapidly correct hardware-related problems in your system.
The following sections describe these environmental monitors: CLI commands and LED indications.
This section describes the show test and show environment CLI commands.
Use the show test [mod_num] command to display the errors reported from the diagnostic tests. If you do not specify a module number, test statistics are given for the general system as well as for the module in slot 1. If there are no errors, PASS is displayed in the Line Card Status field.
Refer to the show test command description in the Catalyst 6000 Family Command Reference publication for a sample screen display and descriptions of the output fields.
Use the show environment [temperature | all | power] command to display system status information. Keyword descriptions follow:
When the system has an alarm (major or minor), indicating an overtemperature condition, the alarm is not canceled or any action taken (such as module reset or shutdown) for 5 minutes. If the temperature falls 5°C (41°F) below the alarm threshold during this period, the alarm is canceled.
Table 14-3 lists the environmental indicators for the supervisor engine and switching modules.
| Component | Alarm Type | LED Indication | Action |
|---|---|---|---|
Supervisor engine temperature sensor exceeds major threshold1 | Major | syslog message and SNMP trap generated. If redundancy, system switches to redundant supervisor engine and the active supervisor engine shuts down. If there is no redundancy and the overtemperature condition is not corrected, the system shuts down after 5 minutes. | |
Supervisor engine temperature sensor exceeds minor threshold | Minor | STATUS LED orange | syslog message and SNMP trap generated. Monitor the condition. |
Redundant supervisor engine temperature sensor exceeds major or minor threshold | Major
| STATUS LED red
| syslog message and SNMP trap generated. If major alarm and the overtemperature condition is not corrected, the system shuts down after 5 minutes. If minor alarm, monitor the condition. |
Switching module temperature sensor exceeds major threshold | Major | STATUS LED red | syslog message and SNMP trap generated. Power down the module4. |
Switching module temperature sensor exceeds minor threshold | Minor | STATUS LED orange | syslog message and SNMP trap generated. Monitor the condition. |
| 1Temperature sensors monitor key supervisor engine components including daughter cards. 2A STATUS LED is located on the supervisor engine front panel and all module front panels. 3The STATUS LED is red on the failed supervisor engine. If there is no redundant supervisor, the SYSTEM LED is red also. 4See the "Power Management" section for instructions. |
Posted: Mon Feb 21 16:27:36 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.