Using the Bootflash or Bootdisk on a Supervisor Engine 720
Using the Bootflash or Bootdisk on a Supervisor Engine 720
All 12.2SX releases support the Supervisor Engine 720 64-MB bootflash device (sup-bootflash:).
Release 12.2(18)SXE5 and rebuilds and Release 12.2(18)SXF and rebuilds support WS-CF-UPG=,
which replaces the bootflash device with a CompactFlash adapter and 512 MB CompactFlash card
(sup-bootdisk:). Refer to this publication:
The Supervisor Engine 720 has two CompactFlash Type II slots. The CompactFlash Type II slots
support CompactFlash Type II Flash PC cards sold by Cisco Systems, Inc. The keywords for the slots on
the active Supervisor Engine 720 are disk0: and disk1:. The keywords for the slots on a redundant
Supervisor Engine 720 are slavedisk0: and slavedisk1:.
Configuring Supervisor Engine 720 Ports
Supervisor Engine 720 port 1 has a small form-factor pluggable (SFP) connector and has no unique
configuration options.
Supervisor Engine 720 port 2 has an RJ-45 connector and an SFP connector (default). To use the RJ-45
connector, you must change the configuration.
To configure port 2 on a Supervisor Engine 720 to use either the RJ-45 connector or the SFP connector,
perform this task:
CommandPurpose
Step 1
Step 2
Router(config)# interface gigabitethernetslot/2
Router(config-if)# media-type {rj45 | sfp}
Router(config-if)# no media-type
This example shows how to configure port 2 on a Supervisor Engine 720 in slot 5 to use the RJ-45
connector:
Configuring and Monitoring the Switch Fabric Functionality
Understanding How the Switch Fabric Functionality Works
These sections describe how the switch fabric functionality works:
• Switch Fabric Functionality Overview, page 4-3
• Forwarding Decisions for Layer 3-Switched Traffic, page 4-3
• Switching Modes, page 4-3
Switch Fabric Functionality Overview
The switch fabric functionality is built into the Supervisor Engine 720 and creates a dedicated
connection between fabric-enabled modules and provides uninterrupted transmission of frames between
these modules. In addition to the direct connection between fabric-enabled modules provided by the
switch fabric funtionality, fabric-enabled modules also have a direct connection to the 32-Gbps
forwarding bus.
Forwarding Decisions for Layer 3-Switched Traffic
Switching Modes
Either a PFC3 or a Distributed Feature Card 3 (DFC3) makes the forwarding decision for Layer
3-switched traffic as follows:
• A PFC3 makes all forwarding decisions for each packet that enters the switch through a module
without a DFC3.
• A DFC3 makes all forwarding decisions for each packet that enters the switch on a DFC3-enabled
module in these situations:
–
If the egress port is on the same module as the ingress port, the DFC3 forwards the packet
locally (the packet never leaves the module).
–
If the egress port is on a different fabric-enabled module, the DFC3 sends the packet to the
egress module, which sends it out the egress port.
–
If the egress port is on a different nonfabric-enabled module, the DFC3 sends the packet to the
Supervisor Engine 720. The Supervisor Engine 720 fabric interface transfers the packet to the
32-Gbps switching bus where it is received by the egress module and is sent out the egress port.
With a Supervisor Engine 720, traffic is forwarded to and from modules in one of the following modes:
• Compact mode—The switch uses this mode for all traffic when only fabric-enabled modules are
installed. In this mode, a compact version of the DBus header is forwarded over the switch fabric
channel, which provides the best possible performance.
• Truncated mode—The switch uses this mode for traffic between fabric-enabled modules when there
are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a
truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel.
• Bus mode (also called flow-through mode)—The switch uses this mode for traffic between
nonfabric-enabled modules and for traffic between a nonfabric-enabled module and a fabric-enabled
module. In this mode, all traffic passes between the local bus and the supervisor engine bus.
Table 4-1 shows the switching modes used with fabric-enabled and nonfabric-enabled modules installed.
When configuring the switching mode, note the following information:
• To allow use of nonfabric-enabled modules or to allow fabric-enabled modules to use bus mode,
enter the fabric switching-mode allow bus-mode command.
• To prevent use of nonfabric-enabled modules or to prevent fabric-enabled modules from using bus
mode, enter the no fabric switching-mode allow bus-mode command.
CautionWhen you enter the no fabric switching-mode allow bus-mode command, power is removed from any
nonfabric-enabled modules installed in the switch.
• To allow fabric-enabled modules to use truncated mode, enter the fabric switching-mode allow
truncated command.
• To prevent fabric-enabled modules from using truncated mode, enter the no fabric switching-mode
allow truncated command.
• To configure how many fabric-enabled modules must be installed before they use truncated mode
instead of bus mode, enter the fabric switching-mode allow truncated threshold number command.
• To return to the default truncated-mode threshold, enter the no fabric switching-mode allow
truncated threshold command.
Monitoring the Switch Fabric Functionality
The switch fabric functionality supports a number of show commands for monitoring purposes. A fully
automated startup sequence brings the module online and runs the connectivity diagnostics on the ports.
This example shows how to display the fabric channel switching mode of all modules:
Router# show fabric switching-mode
Global switching mode is Compact
dCEF mode is not enforced for system to operate
Fabric module is not required for system to operate
Modules are allowed to operate in bus mode
Truncated mode is allowed
Configuring and Monitoring the Switch Fabric Functionality
Router#
Displaying the Fabric Status
To display the fabric status of one or all switching modules, perform this task:
CommandPurpose
Router# show fabric status [slot_number | all]
This example shows how to display the fabric status of all modules:
Router# show fabric status
slot channel speed module fabric
status status
1 0 8G OK OK
5 0 8G OK Up- Timeout
6 0 20G OK Up- BufError
8 0 8G OK OK
8 1 8G OK OK
9 0 8G Down- DDRsync OK
Router#
Displays fabric status.
Chapter 4 Configuring a Supervisor Engine 720
Displaying the Fabric Utilization
To display the fabric utilization of one or all modules, perform this task:
CommandPurpose
Router# show fabric utilization [slot_number | all]
This example shows how to display the fabric utilization of all modules:
Router# show fabric utilization all
Lo% Percentage of Low-priority traffic.
Hi% Percentage of High-priority traffic.