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

  • 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 40
White Paper
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 41 of 51
In Cisco IOS Software only an interface configuration level command is needed; the global
configurations are made as part of this single macro.
In the examples below, AutoQoS is enabled and is configured to trust all incoming CoS and DSCP
marking. The third example configures port 3/1 for ingress QoS for a Cisco IP phone:
Cisco Catalyst OS Cisco IOS Software
set qos autoqos
set port qos 3/1 autoqos trust cos
set port qos 3/1 autoqos trust dscp
set port qos 3/1 autoqos voip ciscoipphone
Switch(config)#int gi 3/1
Switch(config-if)#switchport
Switch(config-if)#auto qos voip cisco-phone
Note: For further information about AutoQoS macro command inclusion, see
http://www.cisco.com/en/US/partner/products/hw/switches/ps708/products_configuration_guide_ch
apter09186a0080121d11.html#22805.
Switch Port Analyzer (SPAN)
SPAN is a troubleshooting analysis feature used to mirror the traffic coming to and from physical
and logical interfaces on the switch. A SPAN session is an association of a set of SPAN source
ports or VLANs that need to be monitored and a SPAN destination port is where the mirrored
traffic is sent. The SPAN destination port does not belong to any VLAN and does not participate in
spanning tree. Any 10M, 100M, 1G, or 10G port can be configured as a SPAN source or
destination port (including fabric-enabled and DFC-enabled line cards).
SPAN has been implemented differently between the two operating systems. the Cisco Catalyst
OS can support up to two ingress-only or ingress/egress SPAN sessions and four egress-only
SPAN sessions. Cisco IOS Software is slightly different in that it also supports two ingress-only or
ingress/egress SPAN sessions and beginning in Cisco IOS Software release 12.2(33)SXH an
additional fourteen egress only span sessions are supported. In addition, Cisco IOS Software has
the added functionality of allowing the CPU interfaces as SPAN source ports. Using the CPU as a
source port for SPAN sessions provides the ability to baseline CPU bound traffic typers as well as
troubleshoot CPU related issues.
Different SPAN sessions can contain overlapping or distinct sets of source interfaces. Both
switchports and routed ports can be configured as SPAN sources. Different SPAN sessions must
contain distinct, nonoverlapping sets of destination interfaces.
Ingress SPAN (Rx) copies network traffic received by the source ports for analysis at the
destination port. Egress SPAN (Tx) copies network traffic transmitted from the source ports.
Configuration option "both" copies network traffic received and transmitted by the source ports to
the destination port. Cisco IOS Software can monitor 128 Egress or “both” sources and up to 128
ingress ports as source ports.
5
Up to 64 SPAN destination interfaces are supported.
The following example configures ports 5/1-2 as SPAN Sources and port 5/3 as the SPAN
destination.
Cisco Catalyst OS Cisco IOS Software
set span 5/1,5/2 5/3 rx create monitor session 1 source int f5/1—2 rx
monitor session 1 dest int f5/3
5
With Cisco IOS Software Release 12.2(18)SXE and above.
Zobrazit stránku 40
1 2 ... 36 37 38 39 40 41 42 43 44 45 46 ... 50 51

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

Žádné komentáře