Cisco WS-X6416-GE-MT - Interface Module - Expansion Uživatelský manuál Strana 15

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 51
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 14
White Paper
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 15 of 51
After this point the route processor controls the system. From the software perspective, the route
processor acts as the primary CPU, and the switch processor acts as the secondary CPU. This is
transparent to the user; all configuration commands are entered directly through the route
processor CPU in Cisco IOS Software. Commands entered that affect the switch processor
functionality are passed internally from the route processor to the switch processor.
Unlike the Cisco Catalyst OS, net booting a Cisco IOS Software image from a TFTP server is not
supported because the supervisor image is a bundled image for two processors. The runtime
image location (c6sup<xy>-is-mz-<version>) must be stored on a device local to the switch
processor (sup-bootflash) or the flash card (slot0:, disk0:, disk1:).
Logging into the Switch Processor in Cisco IOS Software
While the command line perspective is from the route processor, you can log into the switch
processor for any Layer 2-specific debugging. You can use the following commands to debug and
to check the switch processor status during runtime. Note that all Layer 2 through Layer 4
configurations are done from the main Cisco IOS Software command line:
Remote login: The remote login command (or remote login switch for the Cisco Catalyst
6500 Series Supervisor Engine 2, Cisco Catalyst 6500 Supervisor Engine 32, and Cisco
Catalyst 6500 Series Supervisor Engine 720) is equivalent to the session command in the
Cisco Catalyst OS. The hostname becomes “hostname–sp”. Use the exit command rather
than Control-C to exit the switch processor.
Remote command: If only one command’s output is needed from the switch processor,
use a remote command <command> (or remote command switch <command> for the
Cisco Catalyst 6500 Series Supervisor Engine 2, Cisco Catalyst 6500 Supervisor Engine
32, and Cisco Catalyst 6500 Series Supervisor Engine 720), as seen below.
Note: There is no help facility (that is, remote command show?) when using the remote
command.
IOS#remote command sw show bootvar
IOS-sp#
BOOT variable = bootflash:c6sup22-psv-mz.121-11b.EX,1
CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x2002
IOS#
Switch Management
Although the direct console cable connection is a useful way for managing a Cisco Catalyst 6500,
other methods of network-based management (such as telnet or SNMP) require a management
interface with which to access the switch. In the Cisco Catalyst OS, two management interfaces,
sc0 and sc1, are available for the system. An IP address and VLAN must be assigned to these
interfaces if both are in use. Any IP-based management of a Cisco Catalyst OS is then directed to
the sc0 or sc1 interface address. With the hybrid OS, the sc0/sc1 interface is used in conjunction
with any Layer 3 VLAN interfaces created for routing functionality.
Zobrazit stránku 14
1 2 ... 10 11 12 13 14 15 16 17 18 19 20 ... 50 51

Komentáře k této Příručce

Žádné komentáře