Cisco IE 2000 Software Configuration Guide, Release 15.0(1)EY · Cisco IE 2000 Switch Software Configuration Guide Cisco IOS Release 15.0(1)EY ... LOSS OR DAMAGE TO DATA ARISING OUT

Cisco IE 2000 Switch Software Configuration GuideCisco IOS Release 15.0(1)EYFirst Published: July 2012Last Updated: February 2016

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

© 2012–2016 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/officeshttp://www.cisco.com/go/trademarks

Preface

AudienceThis guide is for the networking professional managing your switch. Before using this guide, you should have experience working with the Cisco IOS software and be familiar with the concepts and terminology of Ethernet and local area networking.

PurposeThis guide provides the information that you need to configure Cisco IOS software features on your switch.

This guide provides procedures for using the commands that have been created or changed for use with the switch. It does not provide detailed information about these commands. For detailed information about these commands, see the Cisco IE 2000 Switch Command Reference for this release.

For information about the standard Cisco IOS commands, see the Cisco IOS 15.0 documentation set available from the Cisco.com home page.

This guide does not provide detailed information on the graphical user interfaces (GUIs) for the embedded Device Manager. However, the concepts in this guide are applicable to the GUI user. For information about Device Manager, see the switch online help.

For documentation updates, see the release notes for this release.

ConventionsThis publication uses these conventions to convey instructions and information:

Command descriptions use these conventions:

• Commands and keywords are in boldface text.

• Arguments for which you supply values are in italic.

• Square brackets ([ ]) mean optional elements.

• Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.

• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional element.

Interactive examples use these conventions:

3Cisco IE 2000 Switch Software Configuration Guide

Preface

• Terminal sessions and system displays are in screen font.

• Information you enter is in boldface screen font.

• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).

Notes, cautions, and timesavers use these conventions and symbols:

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Related PublicationsThese documents provide complete information about the switch and are available from this Cisco.com site:

http://www.cisco.com/go/ie2000_docs

Note Before installing, configuring, or upgrading the switch, see these documents:

• For initial configuration information, see the “Using Express Setup” section in the getting started guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.

• For Device Manager requirements, see the “System Requirements” section in the release notes (not orderable but available on Cisco.com).

• For upgrading information, see the “Downloading Software” section in the release notes.

See these documents for other information about the switch:

• Release Notes

• Software Configuration Guide

• Command Reference

• System Message Guide

• Hardware Installation Guide

• Getting Started Guide

• Regulatory Compliance and Safety Information

• Additional documents such as installation notes and upgrade instructions

• Device Manager online help (available on the switch)

• Network Admission Control Software Configuration Guide


http://www.cisco.com/go/ie2000_docs

Preface

• Compatibility matrix documents are available from this Cisco.com site:http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.


http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.htmlhttp://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Preface


C H A P T E R 1

Configuration Overview

FeaturesYour switch uses the Cisco IOS software licensing (CISL) architecture to support a single universal cryptographic image (supports encryption). This image implements the LAN Base or LAN Lite features depending on your switch model:

• The LAN Base image provides quality of service (QoS), port security, 1588v2 PTP, and static routing features.

• The LAN Lite image provides reduced Layer 2 functionality without the loss of critical security features such as SSH and SNMPv3.

Feature Software LicensingA feature license is supported on a single universal image that implements the LAN Base or LAN Lite features depending on your software license:

• The LAN Base features include quality of service (QoS), port security, PTP, and static routing.

• The LAN Lite features provide Layer 2 functionality without losing critical security features such as SSH and SNMPv3.

Cryptographic functionality is included on the universal image.

These guidelines can help you determine what image is running on your switch:

• Enter the show version privileged EXEC command. The first line of output indicates the image, such as LANBASE.

• Enter the show license privileged EXEC command, to see which is the active image:

Switch# show licenseIndex 1 Feature: lanbase Period left: Life time License Type: Permanent License State: Active, In Use License Priority: Medium License Count: Non-Counted

Index 2 Feature: lanlite Period left: 0 minute 0 second

1-1Cisco IE 2000 Switch Software Configuration Guide

Chapter 1 Configuration OverviewFeature Software Licensing

Ease-of-Deployment and Ease-of-Use Features• Express Setup for quickly configuring a switch for the first time with basic IP information, contact

information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP) information through a browser-based program. For more information about Express Setup, see the getting started guide.

• User-defined and Cisco-default Smartports macros for creating custom switch configurations for simplified deployment across the network.

• A removable SD flash card that stores the Cisco IOS software image and configuration files for the switch. You can replace and upgrade the switch without reconfiguring the software features.

• An embedded Device Manager GUI for configuring and monitoring a single switch through a web browser. For information about launching Device Manager, see the getting started guide. For more information about Device Manager, see the switch online help.

Performance Features• Autosensing of port speed and autonegotiation of duplex mode on all switch ports for optimizing

bandwidth

• Automatic medium-dependent interface crossover (auto-MDIX) capability on 10/100 and 10/100/1000 Mb/s interfaces and on 10/100/1000 BASE-TX SFP module interfaces that enables the interface to automatically detect the required cable connection type (straight-through or crossover) and to configure the connection appropriately

• Support for up to 1546 bytes routed frames, up to 9000 bytes for frames that are bridged in hardware, and up to 2000 bytes for frames that are bridged by software

• IEEE 802.3x flow control on all ports (the switch does not send pause frames)

• Support for up to 6 EtherChannel groups

• Port Aggregation Protocol (PAgP) and Link Aggregation Control Protocol (LACP) for automatic creation of EtherChannel links

• Per-port storm control for preventing broadcast, multicast, and unicast storms

• Port blocking on forwarding unknown Layer 2 unknown unicast, multicast, and bridged broadcast traffic

• Cisco Group Management Protocol (CGMP) server support and Internet Group Management Protocol (IGMP) snooping for IGMP Versions 1, 2, and 3:

– (For CGMP devices) CGMP for limiting multicast traffic to specified end stations and reducing overall network traffic

– (For IGMP devices) IGMP snooping for forwarding multimedia and multicast traffic

• IGMP report suppression for sending only one IGMP report per multicast router query to the multicast devices (supported only for IGMPv1 or IGMPv2 queries)

• IGMP snooping querier support to configure switch to generate periodic IGMP general query messages

• IGMP helper to allow the switch to forward a host request to join a multicast stream to a specific IP destination address

• IGMP filtering for controlling the set of multicast groups to which hosts on a switch port can belong



• IGMP throttling for configuring the action when the maximum number of entries is in the IGMP forwarding table

• IGMP leave timer for configuring the leave latency for the network

• Switch Database Management (SDM) templates for allocating system resources to maximize support for user-selected features

• Cisco IOS IP Service Level Agreements (SLAs), a part of Cisco IOS software that uses active traffic monitoring for measuring network performance

• Configurable small-frame arrival threshold to prevent storm control when small frames (64 bytes or less) arrive on an interface at a specified rate (the threshold)

• FlexLink Multicast Fast Convergence to reduce the multicast traffic convergence time after a FlexLink failure

• RADIUS server load balancing to allow access and authentication requests to be distributed evenly across a server group

• Support for QoS marking of CPU-generated traffic and queue CPU-generated traffic on the egress network ports

Management Options• An embedded Device Manager—Device Manager is a GUI application that is integrated in the

software image. You use it to configure and to monitor a single switch. For information about launching Device Manager, see the getting started guide. For more information about Device Manager, see the switch online help.

• Network Assistant—Network Assistant is a network management application that can be downloaded from Cisco.com. You use it to manage a single switch, a cluster of switches, or a community of devices. For more information about Network Assistant, see Getting Started with Cisco Network Assistant, available on Cisco.com.

• CLI—The Cisco IOS software supports desktop- and multilayer-switching features. You can access the CLI either by connecting your management station directly to the switch console port or by using Telnet from a remote management station. For more information about the CLI, see Chapter 2, “Using the Command-Line Interface.”

• SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS) and HP OpenView. You can manage from an SNMP-compatible management station that is running platforms such as HP OpenView or SunNet Manager. The switch supports a comprehensive set of MIB extensions and four remote monitoring (RMON) groups. For more information about using SNMP, see Chapter 36, “Configuring SNMP.”

• Cisco IOS Configuration Engine (previously known as the Cisco IOS CNS agent)—Configuration service automates the deployment and management of network devices and services. You can automate initial configurations and configuration updates by generating switch-specific configuration changes, sending them to the switch, executing the configuration change, and logging the results.

For more information about CNS, see Chapter 5, “Configuring Cisco IOS Configuration Engine.”



Industrial Application• CIP—Common Industrial Protocol (CIP) is a peer-to-peer application protocol that provides

application level connections between the switch and industrial devices such as I/O controllers, sensors, relays, and so forth.You can manage the switch using CIP-based management tools, such as RSLogix. For more information about the CIP commands that the switch supports, see the command reference.

• Profinet Version 2—Support for PROFINET IO, a modular communication framework for distributed automation applications. The switch provides a PROFINET management connection to the I/O controllers.

Manageability Features• CNS embedded agents for automating switch management, configuration storage, and delivery.

• DHCP for automating configuration of switch information (such as IP address, default gateway, hostname, and Domain Name System [DNS] and TFTP server names).

• DHCP relay for forwarding User Datagram Protocol (UDP) broadcasts, including IP address requests, from DHCP clients.

• DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts.

• DHCP-based autoconfiguration and image update to download a specified configuration of a new image to a large number of switches.

• DHCPv6 bulk-lease query to support new bulk lease query type (as defined in RFC5460).

• DHCPv6 Relay Source Configuration feature to configure a source address for DHCPv6 relay agent.

• DHCP server port-based address allocation for the preassignment of an IP address to a switch port.

• Directed unicast requests to a DNS server for identifying a switch through its IP address and its corresponding hostname and to a TFTP server for administering software upgrades from a TFTP server.

• Address Resolution Protocol (ARP) for identifying a switch through its IP address and its corresponding MAC address.

• Unicast MAC address filtering to drop packets with specific source or destination MAC addresses.

• Configurable MAC address scaling that allows disabling MAC address learning on a VLAN to limit the size of the MAC address table.

• Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping between the switch and other Cisco devices on the network.

• Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for interoperability with third-party IP phones.

• LLDP media extensions (LLDP-MED) location TLV that provides location information from the switch to the endpoint device.

• Network Time Protocol (NTP) for providing a consistent time stamp to all switches from an external source.

• Network Time Protocol version 4 (NTPv4) to support both IPv4 and IPv6 and compatibility with NTPv3.

• Precision Time Protocol (PTP) as defined in the IEEE 1588 standard to synchronize with nanosecond accuracy the real-time clocks of the devices in a network.



– PTP enhancement to support PTP messages on the expansion module ports.

• Cisco IOS File System (IFS) for providing a single interface to all file systems that the switch uses.

• Support for the SSM PIM protocol to optimize multicast applications, such as video.

• Configuration logging to log and to view changes to the switch configuration.

• Unique device identifier to provide product identification information through a show inventory user EXEC command display.

• In-band management access through Device Manager over a Netscape Navigator or Microsoft Internet Explorer browser session.

• In-band management access for up to 16 simultaneous Telnet connections for multiple CLI-based sessions over the network.

• In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections for multiple CLI-based sessions over the network.

• In-band management access through SNMP Versions 1, 2c, and 3 get and set requests.

• Out-of-band management access through the switch console port to a directly attached terminal or to a remote terminal through a serial connection or a modem.

• Secure Copy Protocol (SCP) feature to provide a secure and authenticated method for copying switch configuration or switch image files (requires the cryptographic version of the software).

• Configuration replacement and rollback to replace the running configuration on a switch with any saved Cisco IOS configuration file.

• The HTTP client in Cisco IOS can send requests to both IPv4 and IPv6 HTTP server, and the HTTP server in Cisco IOS can service HTTP requests from both IPv4 and IPv6 HTTP clients.

• Simple Network and Management Protocol (SNMP) can be configured over IPv6 transport so that an IPv6 host can send SNMP queries and receive SNMP notifications from a device running IPv6.

• IPv6 stateless autoconfiguration to manage link, subnet, and site addressing changes, such as management of host and mobile IP addresses.

• Disabling MAC address learning on a VLAN.

• DHCP server port-based address allocation for the preassignment of an IP address to a switch port.

• CPU utilization threshold trap monitors CPU utilization.

• LLDP-MED network-policy profile time, length, value (TLV) for creating a profile for voice and voice-signaling by specifying the values for VLAN, class of service (CoS), differentiated services code point (DSCP), and tagging mode.

• Support for including a hostname in the option 12 field of DHCPDISCOVER packets. This provides identical configuration files to be sent by using the DHCP protocol.

• DHCP Snooping enhancement to support the selection of a fixed string-based format for the circuit-id sub-option of the Option 82 DHCP field.

• Support for PROFINET IO, a modular communication framework for distributed automation applications. The switch provides a PROFINET management connection to the I/O controllers.

Availability and Redundancy Features• UniDirectional Link Detection (UDLD) and aggressive UDLD for detecting and disabling

unidirectional links on fiber-optic interfaces caused by incorrect fiber-optic wiring or port faults



• IEEE 802.1D Spanning Tree Protocol (STP) for redundant backbone connections and loop-free networks. STP has these features:

– Up to 128 spanning-tree instances supported

– Per-VLAN spanning-tree plus (PVST+) for load balancing across VLANs

– Rapid PVST+ for load balancing across VLANs and providing rapid convergence of spanning-tree instances

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) for grouping VLANs into a spanning-tree instance and for providing multiple forwarding paths for data traffic and load balancing and rapid per-VLAN Spanning-Tree plus (rapid-PVST+) based on the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) for rapid convergence of the spanning tree by immediately changing root and designated ports to the forwarding state

• Optional spanning-tree features available in PVST+, rapid-PVST+, and MSTP mode:

– Port Fast for eliminating the forwarding delay by enabling a port to immediately change from the blocking state to the forwarding state

– BPDU guard for shutting down Port Fast-enabled ports that receive bridge protocol data units (BPDUs)

– BPDU filtering for preventing a Port Fast-enabled port from sending or receiving BPDUs

– Root guard for preventing switches outside the network core from becoming the spanning-tree root

– Loop guard for preventing alternate or root ports from becoming designated ports because of a failure that leads to a unidirectional link

• FlexLink Layer 2 interfaces to back up one another as an alternative to STP for basic link redundancy (requires the LAN Base image)

• Link-state tracking to mirror the state of the ports that carry upstream traffic from connected hosts and servers, and to allow the failover of the server traffic to an operational link on another Cisco Ethernet switch.

VLAN Features• Support for up to 255 VLANs for assigning users to VLANs associated with appropriate network

resources, traffic patterns, and bandwidth.

• Support for VLAN IDs in the 1 to 4096 range as allowed by the IEEE 802.1Q standard.

• VLAN Query Protocol (VQP) for dynamic VLAN membership.

• IEEE 802.1Q trunking encapsulation on all ports for network moves, adds, and changes; management and control of broadcast and multicast traffic; and network security by establishing VLAN groups for high-security users and network resources.

• Dynamic Trunking Protocol (DTP) for negotiating trunking on a link between two devices and for negotiating the type of trunking encapsulation (IEEE 802.1Q) to be used.

• VLAN Trunking Protocol (VTP) and VTP pruning for reducing network traffic by restricting flooded traffic to links destined for stations receiving the traffic.

• Voice VLAN for creating subnets for voice traffic from Cisco IP phones.



• VLAN 1 minimization for reducing the risk of spanning-tree loops or storms by allowing VLAN 1 to be disabled on any individual VLAN trunk link. With this feature enabled, no user traffic is sent or received on the trunk. The switch CPU continues to send and receive control protocol frames.

• VLAN FlexLink load balancing to provide Layer 2 redundancy without requiring Spanning Tree Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic based on VLAN.

• Support for 802.1x authentication with restricted VLANs (also known as authentication failed VLANs).

• Support for VTP version 3 that includes support for configuring extended range VLANs (VLANs 1006 to 4096) in any VTP mode, enhanced authentication (hidden or secret passwords), propagation of other databases in addition to VTP, VTP primary and secondary servers, and the option to turn VTP on or off by port.

Security Features• IP Service Level Agreements (IP SLAs) support to measure network performance by using active

traffic monitoring

• IP SLAs EOT to use the output from IP SLAs tracking operations triggered by an action such as latency, jitter, or packet loss for a standby router failover takeover (requires the LAN Base image)

• Web authentication to allow a supplicant (client) that does not support IEEE 802.1x functionality to be authenticated using a web browser

• Local web authentication banner so that a custom banner or an image file can be displayed at a web authentication login screen

• MAC authentication bypass (MAB) aging timer to detect inactive hosts that have authenticated after they have authenticated by using MAB

• Password-protected access (read-only and read-write access) to management interfaces (Device Manager, Network Assistant, and the CLI) for protection against unauthorized configuration changes

• Multilevel security for a choice of security level, notification, and resulting actions

• Static MAC addressing for ensuring security

• Protected port option for restricting the forwarding of traffic to designated ports on the same switch

• Port security option for limiting and identifying MAC addresses of the stations allowed to access the port

• VLAN-aware port security option to shut down the VLAN on the port when a violation occurs, instead of shutting down the entire port

• Port security aging to set the aging time for secure addresses on a port

• Protocol storm protection to control the rate of incoming protocol traffic to a switch by dropping packets that exceed a specified ingress rate

• BPDU guard for shutting down a Port Fast-configured port when an invalid configuration occurs

• Standard and extended IP access control lists (ACLs) for defining security policies in both directions on routed interfaces (router ACLs) and VLANs and inbound on Layer 2 interfaces (port ACLs)

• Extended MAC access control lists for defining security policies in the inbound direction on Layer 2 interfaces

• Source and destination MAC-based ACLs for filtering non-IP traffic



• DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers

• IP source guard to restrict traffic on nonrouted interfaces by filtering traffic based on the DHCP snooping database and IP source bindings

• Dynamic ARP inspection to prevent malicious attacks on the switch by not relaying invalid ARP requests and responses to other ports in the same VLAN

• Layer 2 protocol tunneling bypass feature to provide interoperability with third-party vendors

• IEEE 802.1x port-based authentication to prevent unauthorized devices (clients) from gaining access to the network. These features are supported:

– Multidomain authentication (MDA) to allow both a data device and a voice device, such as an IP phone (Cisco or non-Cisco), to independently authenticate on the same IEEE 802.1x-enabled switch port

– Dynamic voice virtual LAN (VLAN) for MDA to allow a dynamic voice VLAN on an MDA-enabled port

– VLAN assignment for restricting 802.1x-authenticated users to a specified VLAN

– Port security for controlling access to 802.1x ports

– Voice VLAN to permit a Cisco IP Phone to access the voice VLAN regardless of the authorized or unauthorized state of the port

– IP phone detection enhancement to detect and recognize a Cisco IP phone

– Guest VLAN to provide limited services to non-802.1x-compliant users

– Restricted VLAN to provide limited services to users who are 802.1x compliant, but do not have the credentials to authenticate via the standard 802.1x processes

– 802.1x accounting to track network usage

– 802.1x with wake-on-LAN to allow dormant PCs to be powered on based on the receipt of a specific Ethernet frame

– 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802.1x on the switch

– Voice-aware 802.1x security to apply traffic violation actions only on the VLAN on which a security violation occurs

– MAC authentication bypass to authorize clients based on the client MAC address

– Network Edge Access Topology (NEAT) with 802.1X switch supplicant, host authorization with CISP, and auto enable to authenticate a switch outside a wiring closet as a supplicant to another switch

– IEEE 802.1x with open access to allow a host to access the network before being authenticated

– IEEE 802.1x authentication with downloadable ACLs and redirect URLs to allow per-user ACL downloads from a Cisco Secure ACS server to an authenticated switch

– Flexible-authentication sequencing to configure the order of the authentication methods that a port tries when authenticating a new host

– Multiple-user authentication to allow more than one host to authenticate on an 802.1x-enabled port

• Network Admission Control (NAC) features:

– NAC Layer 2 802.1x validation of the antivirus condition or posture of endpoint systems or clients before granting the devices network access



For information about configuring NAC Layer 2 802.1x validation, see the “Configuring NAC Layer 2 802.1x Validation” section on page 13-46

– NAC Layer 2 IP validation of the posture of endpoint systems or clients before granting the devices network access

For information about configuring NAC Layer 2 IP validation, see the Network Admission Control Software Configuration Guide

– IEEE 802.1x inaccessible authentication bypass

For information about configuring this feature, see the “Configuring Inaccessible Authentication Bypass” section on page 13-44

– Authentication, authorization, and accounting (AAA) down policy for a NAC Layer 2 IP validation of a host if the AAA server is not available when the posture validation occurs

For information about this feature, see the Network Admission Control Software Configuration Guide.

• TACACS+, a proprietary feature for managing network security through a TACACS server

• RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users through AAA services

• Enhancements to RADIUS, TACACS+, and SSH to function over IPv6

• Kerberos security system to authenticate requests for network resources by using a trusted third party (requires the cryptographic versions of the software)

• Secure Socket Layer (SSL) Version 3.0 support for the HTTP 1.1 server authentication, encryption, and message integrity and HTTP client authentication to allow secure HTTP communications (requires the cryptographic version of the software)

• Voice-aware IEEE 802.1x and MAC authentication bypass (MAB) security violation to shut down only the data VLAN on a port when a security violation occurs

• Support for IP source guard on static hosts

• RADIUS change of authorization (CoA) to change the attributes of a certain session after it is authenticated. When there is a change in policy for a user or user group in AAA, administrators can send the RADIUS CoA packets from the AAA server, such as Cisco Secure ACS to reinitialize authentication, and apply to the new policies.

• IEEE 802.1x User Distribution to allow deployments with multiple VLANs (for a group of users) to improve scalability of the network by load balancing users across different VLANs. Authorized users are assigned to the least populated VLAN in the group, assigned by RADIUS server.

• Support for critical VLAN with multiple-host authentication so that when a port is configured for multi-authentication, and an AAA server becomes unreachable, the port is placed in a critical VLAN in order to still permit access to critical resources

• Customizable web authentication enhancement to allow the creation of user-defined login, success, failure and expire web pages for local web authentication

• Support for Network Edge Access Topology (NEAT) to change the port host mode and to apply a standard port configuration on the authenticator switch port

• VLAN-ID based MAC authentication to use the combined VLAN and MAC address information for user authentication to prevent network access from unauthorized VLANs

• MAC move to allow hosts (including the hosts connected behind an IP phone) to move across ports within the same switch without any restrictions to enable mobility. With MAC move, the switch treats the reappearance of the same MAC address on another port in the same way as a completely new MAC address.



• Support for 3DES and AES with version 3 of the Simple Network Management Protocol (SNMPv3). This release adds support for the 168-bit Triple Data Encryption Standard (3DES) and the 128-bit, 192-bit, and 256-bit Advanced Encryption Standard (AES) encryption algorithms to SNMPv3.

QoS and CoS Features

Note These features require the LAN Base image.

• Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying traffic and configuring egress queues

• Automatic quality of service (QoS) Voice over IP (VoIP) enhancement for port-based trust of DSCP and priority queuing for egress traffic

• Classification

– IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS marking priorities on a per-port basis for protecting the performance of mission-critical applications

– IP ToS/DSCP and IEEE 802.1p CoS marking based on flow-based packet classification (classification based on information in the MAC, IP, and TCP/UDP headers) for high-performance quality of service at the network edge, allowing for differentiated service levels for different types of network traffic and for prioritizing mission-critical traffic in the network

– Trusted port states (CoS, DSCP, and IP precedence) within a QoS domain and with a port bordering another QoS domain

– Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value received, and ensuring port security

• Policing

– Traffic-policing policies on the switch port for managing how much of the port bandwidth should be allocated to a specific traffic flow.

– Aggregate policing for policing traffic flows in aggregate to restrict specific applications or traffic flows to metered, predefined rates.

• Out-of-profile

– Out-of-profile markdown for packets that exceed bandwidth utilization limits

• Ingress queueing and scheduling

– Two configurable ingress queues for user traffic (one queue can be the priority queue)

– Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications

– Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are sent to the ring (sharing is the only supported mode on ingress queues)

• Egress queues and scheduling

– Four egress queues per port.

– WTD as the congestion-avoidance mechanism for managing the queue lengths and providing drop precedences for different traffic classifications.


Chapter 1 Configuration OverviewDefault Settings After Initial Switch Configuration

– SRR as the scheduling service for specifying the rate at which packets are dequeued to the egress interface (shaping or sharing is supported on egress queues). Shaped egress queues are guaranteed but limited to using a share of port bandwidth. Shared egress queues are also guaranteed a configured share of bandwidth, but can use more than the guarantee if other queues become empty and do not use their share of the bandwidth.

Monitoring Features• EOT and IP SLAs EOT static route support identify when a preconfigured static route or a DHCP

route goes down

• MAC address notification traps and RADIUS accounting for tracking users on a network by storing the MAC addresses that the switch has learned or removed

• Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) for traffic monitoring on any port or VLAN (RSPAN requires LAN Base image)

• SPAN and RSPAN support of Intrusion Detection Systems (IDS) to monitor, repel, and report network security violations (RSPAN requires LAN Base image)

• Four groups (history, statistics, alarms, and events) of embedded RMON agents for network monitoring and traffic analysis

• Syslog facility for logging system messages about authentication or authorization errors, resource issues, and time-out events

• Layer 2 traceroute to identify the physical path that a packet takes from a source device to a destination device

• Time Domain Reflector (TDR) to diagnose and resolve cabling problems on 10/100 and 10/100/1000 copper Ethernet ports

• SFP module diagnostic management interface to monitor physical or operational status of an SFP module

• Facilities for processing alarms related to temperature, power-supply conditions, and the status of the Ethernet ports

• Alarm relay contacts that can be used for an external relay system

• Digital optical monitoring (DOM) to check status of X2 small form-factor pluggable (SFP) modules

Default Settings After Initial Switch ConfigurationThe switch is designed for plug-and-play operation, requiring only that you assign basic IP information to the switch and connect it to the other devices in your network. If you have specific network needs, you can change the interface-specific and system-wide settings.

Note For information about assigning an IP address by using the browser-based Express Setup program, see the getting started guide. For information about assigning an IP address by using the CLI-based setup program, see the hardware installation guide.



If you do not configure the switch at all, the switch operates with these default settings:

• Default switch IP address, subnet mask, and default gateway is 0.0.0.0. For more information, see Chapter 4, “Performing Switch Setup Configuration,” and Chapter 25, “Configuring DHCP.”

• Default domain name is not configured. For more information, see Chapter 4, “Performing Switch Setup Configuration.”

• DHCP client is enabled, the DHCP server is enabled (only if the device acting as a DHCP server is configured and is enabled), and the DHCP relay agent is enabled (only if the device is acting as a DHCP relay agent is configured and is enabled). For more information, see Chapter 4, “Performing Switch Setup Configuration,” and Chapter 25, “Configuring DHCP.”

• Switch cluster is disabled. For more information about switch clusters, see Chapter 6, “Configuring Switch Clusters.”

• No passwords are defined. For more information, see Chapter 7, “Performing Switch Administration.”

• System name and prompt is Switch. For more information, see Chapter 7, “Performing Switch Administration.”

• NTP is enabled. For more information, see Chapter 7, “Performing Switch Administration.”

• DNS is enabled. For more information, see Chapter 7, “Performing Switch Administration.”

• TACACS+ is disabled. For more information, see Chapter 12, “Configuring Switch-Based Authentication.”

• RADIUS is disabled. For more information, see Chapter 12, “Configuring Switch-Based Authentication.”

• The standard HTTP server and Secure Socket Layer (SSL) HTTPS server are both enabled. For more information, see Chapter 12, “Configuring Switch-Based Authentication.”

• IEEE 802.1x is disabled. For more information, see Chapter 13, “Configuring IEEE 802.1x Port-Based Authentication.”

• Port parameters

– Operating mode is Layer 2 (switch port). For more information, see Chapter 15, “Configuring Interface Characteristics.”

– Interface speed and duplex mode is autonegotiate. For more information, see Chapter 15, “Configuring Interface Characteristics.”

– Auto-MDIX is enabled. For more information, see Chapter 15, “Configuring Interface Characteristics.”

– Flow control is off. For more information, see Chapter 15, “Configuring Interface Characteristics.”

• VLANs

– Default VLAN is VLAN 1. For more information, see Chapter 17, “Configuring VLANs.”

– VLAN trunking setting is dynamic auto (DTP). For more information, see Chapter 17, “Configuring VLANs.”

– Trunk encapsulation is negotiate. For more information, see Chapter 17, “Configuring VLANs.”

– VTP mode is server. For more information, see Chapter 18, “Configuring VTP.”

– VTP version is Version 1. For more information, see Chapter 18, “Configuring VTP.”

– Voice VLAN is disabled. For more information, see Chapter 19, “Configuring Voice VLAN.”

• STP, PVST+ is enabled on VLAN 1. For more information, see Chapter 20, “Configuring STP.”



• MSTP is disabled. For more information, see Chapter 21, “Configuring MSTP.”

• Optional spanning-tree features are disabled. For more information, see Chapter 22, “Configuring Optional Spanning-Tree Features.”

• FlexLinks are not configured. For more information, see Chapter 24, “Configuring FlexLinks and the MAC Address-Table Move Update.”

• DHCP snooping is disabled. The DHCP snooping information option is enabled. For more information, see Chapter 25, “Configuring DHCP.”

• IP source guard is disabled. For more information, see Chapter 25, “Configuring DHCP.”

• DHCP server port-based address allocation is disabled. For more information, see Chapter 25, “Configuring DHCP.”

• Dynamic ARP inspection is disabled on all VLANs. For more information, see Chapter 26, “Configuring Dynamic ARP Inspection.”

• IGMP snooping is enabled. No IGMP filters are applied. For more information, see Chapter 28, “Configuring IGMP Snooping and MVR.”

• IGMP throttling setting is deny. For more information, see Chapter 28, “Configuring IGMP Snooping and MVR.”

• The IGMP snooping querier feature is disabled. For more information, see Chapter 28, “Configuring IGMP Snooping and MVR.”

• MVR is disabled. For more information, see Chapter 28, “Configuring IGMP Snooping and MVR.”

• Port-based traffic

– Broadcast, multicast, and unicast storm control is disabled. For more information, see Chapter 29, “Configuring Port-Based Traffic Control.”

– No protected ports are defined. For more information, see Chapter 29, “Configuring Port-Based Traffic Control.”

– Unicast and multicast traffic flooding is not blocked. For more information, see Chapter 29, “Configuring Port-Based Traffic Control.”

– No secure ports are configured. For more information, see Chapter 29, “Configuring Port-Based Traffic Control.”

• CDP is enabled. For more information, see Chapter 32, “Configuring CDP.”

• UDLD is disabled. For more information, see Chapter 33, “Configuring UDLD.”

• SPAN and RSPAN are disabled. For more information, see Chapter 30, “Configuring SPAN and RSPAN.”

• RMON is disabled. For more information, see Chapter 34, “Configuring RMON.”

• Syslog messages are enabled and appear on the console. For more information, see Chapter 35, “Configuring System Message Logging.”

• SNMP is enabled (Version 1). For more information, see Chapter 36, “Configuring SNMP.”

• No ACLs are configured. For more information, see Chapter 37, “Configuring Network Security with ACLs.”

• QoS is disabled. For more information, see Chapter 38, “Configuring QoS.”

• No EtherChannels are configured. For more information, see Chapter 40, “Configuring EtherChannels.”

• IP unicast routing is disabled. For more information, see Chapter 41, “Configuring Static IP Unicast Routing.”


Chapter 1 Configuration OverviewNetwork Configuration Examples

Network Configuration ExamplesThis section provides network configuration concepts and includes examples of using the switch to create dedicated network segments and interconnecting the segments through Fast Ethernet and Gigabit Ethernet connections.

• Design Concepts for Using the Switch, page 1-14

• Ethernet-to-the-Factory Architecture, page 1-15

Design Concepts for Using the SwitchAs your network users compete for network bandwidth, it takes longer to send and receive data. When you configure your network, consider the bandwidth required by your network users and the relative priority of the network applications that they use.

Table 1-1 describes what can cause network performance to degrade and how you can configure your network to increase the bandwidth available to your network users.

Bandwidth alone is not the only consideration when designing your network. As your network traffic profiles evolve, consider providing network services that can support applications for voice and data integration, multimedia integration, application prioritization, and security. Table 1-2 describes some network demands and how you can meet them.

Table 1-1 Increasing Network Performance

Network Demands Suggested Design Methods

Too many users on a single network segment and a growing number of users accessing the Internet

• Create smaller network segments so that fewer users share the bandwidth, and use VLANs and IP subnets to place the network resources in the same logical network as the users who access those resources most.

• Use full-duplex operation between the switch and its connected workstations.

• Increased power of new PCs, workstations, and servers

• High bandwidth demand from networked applications (such as e-mail with large attached files) and from bandwidth-intensive applications (such as multimedia)

• Connect global resources, such as servers and routers to which the network users require equal access, directly to the high-speed switch ports so that they have their own high-speed segment.

• Use the EtherChannel feature between the switch and its connected servers and routers.



Ethernet-to-the-Factory ArchitectureThis section is an overview of the Ethernet-to-the-Factory (EttF) architecture that provides network and security services to the devices and applications in automation and control systems. It then integrates those into the wider enterprise network.

EttF architecture applies to many types of manufacturing environments, but it must be tailored to the industry type, the manufacturing type, and the production-facility size. Deployments can range from small networks (less than 50 devices), to medium-sized networks (less than 200 devices), and to large networks (up to and more than 1000 devices).

Within the EttF architecture are conceptual structures called zones that separate the various functions, from the highest-level enterprise switches and processes to the smallest devices that control more detailed processes and devices on the factory floor. See Figure 1-1.

For more information about EttF architecture, see this URL:

http://www.cisco.com/web/strategy/manufacturing/ettf_overview.html

Enterprise Zone

The enterprise zone comprises the centralized IT systems and functions. Wired and wireless access is available to enterprise network services, such as enterprise resource management, business-to-business, and business-to-customer services.The basic business administration tasks, such as site business planning and logistics, are performed here and rely on standard IT services. Guest access systems are often located here, although it is not uncommon to find them in lower levels of the framework to gain flexibility that might be difficult to achieve at the enterprise level.

Table 1-2 Providing Network Services

Network Demands Suggested Design Methods

Efficient bandwidth usage for multimedia applications and guaranteed bandwidth for critical applications

• Use IGMP snooping to efficiently forward multimedia and multicast traffic.

• Use other QoS mechanisms such as packet classification, marking, scheduling, and congestion avoidance to classify traffic with the appropriate priority level, which provides maximum flexibility and support for mission-critical, unicast, and multicast and multimedia applications.

• Use MVR to continuously send multicast streams in a multicast VLAN but to isolate the streams from subscriber VLANs for bandwidth and security reasons.

High demand on network redundancy and availability to provide always on mission-critical applications

• Use VLAN trunks and BackboneFast for traffic-load balancing on the uplink ports so that the uplink port with a lower relative port cost is selected to carry the VLAN traffic.

An evolving demand for IP telephony • Use QoS to prioritize applications such as IP telephony during congestion and to help control both delay and jitter within the network.

• Use switches that support at least two queues per port to prioritize voice and data traffic as either high- or low-priority, based on IEEE 802.1p/Q. The switch supports at least four queues per port.

• Use voice VLAN IDs (VVIDs) to provide separate VLANs for voice traffic.


http://www.cisco.com/web/strategy/manufacturing/ettf_overview.html


Demilitarized Zone

The demilitarized zone (DMZ) provides a buffer for sharing of data and services between the enterprise and manufacturing zones. The DMZ maintains availability, addresses security vulnerabilities, and abiding by regulatory compliance mandates. The DMZ provides segmentation of organizational control, for example, between the IT and production organizations. Different policies for each organization can be applied and contained. For example, the production organization might apply security policies to the manufacturing zone that are different than those applied to the IT organization.

Manufacturing Zone

The manufacturing zone comprises the cell networks and site-level activities. All the systems, devices, and controllers that monitor the plant operations are in this zone. The cell zone is a functional area within a production facility.

The cell zone is a set of devices, controllers, and so on, that provide the real-time control of a functional aspect of the automation process. They are all in real-time communication with each other. This zone requires clear isolation and protection from the other levels of plant or enterprise operations.



Figure 1-1 shows the EttF architecture.

Figure 1-1 Ethernet-to-the-Factory Architecture

LAN

GE Link forFailover

Detection

Servers

Managementtools

Servers

Catalyst3750 switch

Catalyst3750 switchstack

Catalyst4500 switch

2043

22



Topology Options

Topology design starts with considering how devices are connected to the network. The cell network also requires physical topologies that meet the physical constraints of the production floor. This section provides guidelines for topology designs and describes the trunk-drop, ring, and redundant-star topologies.

• Physical layout—The layout of the production environment drives the topology design. For example, a trunk-drop or ring topology is a good choice for a long conveyor-belt system, but a redundant-star configuration is not a good choice.

• Real-time communications—Latency and jitter are primarily caused by the amount of traffic and number of hops a packet must make to reach its destination. The amount of traffic in a Layer 2 network is driven by various factors, but the number of devices is important. Follow these guidelines for real-time communications:

– The amount of latency introduced per Layer 2 hop should be considered. For instance, there is a higher latency with 100 Mb interfaces than there is with 1 Gigabit interfaces.

– Bandwidth should not consistently exceed 50 percent of the interface capacity on any switch.

– The CPU should not consistently exceed 50 to 70 percent utilization. Above this level, the switch might not properly process control packets and might behave abnormally.

These are the key connectivity considerations:

• Devices are connected to a switch through a single network connection or an IP-enabled I/O block or linking device if they do not support Ethernet. Most devices have no or limited failover capabilities and therefore cannot effectively use redundant network connections.

• Redundant connections can be used in certain industries and applications, such as process-related industries that are applied to critical infrastructure.

Cell Network—Trunk-Drop Topology

Switches are connected to each other to form a chain of switches in a trunk-drop topology (also known as a cascaded topology). See Figure 1-2.

• The connection between the Layer 3 switch and the first Layer 2 switch is very susceptible to oversubscription, which can degrade network performance.

• There is no redundancy to the loss of a connection.



Figure 1-2 Cell Network–Trunk-Drop Topology

Cell Network—Ring Topology

A ring topology is similar to a trunk-drop topology except that the last switch in the chain is connected to the Layer 3 switch that forms a network ring. If a connection is lost in a ring, each switch maintains connectivity to the other switches. See Figure 1-3.

• The network can only recover from the loss of a single connection.

• It is more difficult to implement because it requires additional protocol implementation and Rapid Spanning Tree Protocol (RSTP).

• Although better than the trunk-drop, the top of the ring (connections to the Layer 3 switches) can become a bottleneck and is susceptible to oversubscription, which can degrade network performance.

2851

92

HumanMachineInterface

(HMI)

IE2000

Controllers

Cell Zone

Catalyst 3750Stackwise

SwitchStack

Controllers, Drives,and Remote I/Os



Figure 1-3 Cell Network–Ring Topology

Cell Network—Redundant-Star Topology

In a redundant-star topology, every Layer 2 access switch has dual connections to a Layer 3 distribution switch. Devices are connected to the Layer 2 switches. See Figure 1-4.

• Any Layer 2 switch is always only two hops to another Layer 2 switch.

• In the Layer 2 network, each switch has dual connections to the Layer 3 devices.

• The Layer 2 network is maintained even if multiple connections are lost.

2851

92


(HMI)

IE2000

Controllers

Cell Zone


SwitchStack

Controllers, Drives,and Remote I/Os


Chapter 1 Configuration OverviewWhere to Go Next

Figure 1-4 Cell Network–Redundant Star Topology

Where to Go NextBefore configuring the switch, review these sections for startup information:

• Chapter 2, “Using the Command-Line Interface”

• Chapter 4, “Performing Switch Setup Configuration”

To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator:http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

2851

94


(HMI)

IE2000

Cell Zone


SwitchStack

Controllers, Drives,and Remote I/O


http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

Chapter 1 Configuration OverviewWhere to Go Next


C H A P T E R 2

Using the Command-Line Interface

Information About Using the Command-Line Interface This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your switch.

Command ModesThe Cisco IOS user interface is divided into many different modes. The commands available to you depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a list of commands available for each command mode.

When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC commands are one-time commands, such as show commands, which show the current configuration status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved when the switch reboots.

To have access to all commands, you must enter privileged EXEC mode. You must enter a password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC command or enter global configuration mode.

Using the configuration modes (global, interface, and line), you can make changes to the running configuration. If you save the configuration, these commands are stored and used when the switch reboots. To access the various configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and line configuration mode.


Chapter 2 Using the Command-Line InterfaceInformation About Using the Command-Line Interface

Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode, and how to exit the mode. The examples in the table use the hostname Switch.

Table 2-1 Command Mode Summary

Mode Access Method Prompt Exit Method About This Mode

User EXEC Begin a session with your switch.

Switch> Enter logout or quit.

Use this mode to

• Change terminal settings.

• Perform basic tests.

• Display system information.

Privileged EXEC While in user EXEC mode, enter the enable command.

Switch# Enter disable to exit.

Use this mode to verify commands that you have entered. Use a password to protect access to this mode.

Global configuration While in privileged EXEC mode, enter the configure command.

Switch(config)# To exit to privileged EXEC mode, enter exit or end, or press Ctrl-Z.

Use this mode to configure parameters that apply to the entire switch.

Config-vlan While in global configuration mode, enter the vlan vlan-id command.

Switch(config-vlan)# To exit to global configuration mode, enter the exit command.

To return to privileged EXEC mode, press Ctrl-Z or enter end.

Use this mode to configure VLAN parameters. When VTP mode is transparent, you can create extended-range VLANs (VLAN IDs greater than 1005) and save configurations in the switch startup configuration file.

VLAN configuration While in privileged EXEC mode, enter the vlan database command.

Switch(vlan)# To exit to privileged EXEC mode, enter exit.

Use this mode to configure VLAN parameters for VLANs 1 to 1005 in the VLAN database.



For more detailed information on the command modes, see the command reference guide for this release.

Help SystemYou can enter a question mark (?) at the system prompt to display a list of commands available for each command mode. You can also obtain a list of associated keywords and arguments for any command, as shown in Table 2-2.

Interface configuration

While in global configuration mode, enter the interface command (with a specific interface).

Switch(config-if)# To exit to global configuration mode, enter exit.


Use this mode to configure parameters for the Ethernet ports.

For information about defining interfaces, see the “Using Interface Configuration Mode” section on page 15-6.

To configure multiple interfaces with the same parameters, see the “Configuring a Range of Interfaces” section on page 15-13.

Line configuration While in global configuration mode, specify a line with the line vty or line console command.

Switch(config-line)# To exit to global configuration mode, enter exit.


Use this mode to configure parameters for the terminal line.

Table 2-1 Command Mode Summary (continued)

Mode Access Method Prompt Exit Method About This Mode

Table 2-2 Help Summary

Command Purpose

help Obtain a brief description of the help system in any command mode.

abbreviated-command-entry? Obtain a list of commands that begin with a particular character string.

For example:

Switch# di?dir disable disconnect

abbreviated-command-entry Complete a partial command name.

For example:

Switch# sh confSwitch# show configuration



Understanding Abbreviated CommandsYou need to enter only enough characters for the switch to recognize the command as unique.

This example shows how to enter the show configuration privileged EXEC command in an abbreviated form:

Switch# show conf

No and default Forms of CommandsAlmost every configuration command also has a no form. In general, use the no form to disable a feature or function or reverse the action of a command. For example, the no shutdown interface configuration command reverses the shutdown of an interface. Use the command without the keyword no to reenable a disabled feature or to enable a feature that is disabled by default.

Configuration commands can also have a default form. The default form of a command returns the command setting to its default. Most commands are disabled by default, so the default form is the same as the no form. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default command enables the command and sets variables to their default values.

? List all commands available for a particular command mode.

For example:

Switch> ?

command ? List the associated keywords for a command.

For example:

Switch> show ?

command keyword ? List the associated arguments for a keyword.

For example:

Switch(config)# cdp holdtime ? Length of time (in sec) that receiver must keep this packet

Table 2-2 Help Summary (continued)

Command Purpose


Chapter 2 Using the Command-Line InterfaceCLI Error Messages

CLI Error MessagesTable 2-3 lists some error messages that you might encounter while using the CLI to configure your switch.

Configuration LoggingYou can log and view changes to the switch configuration. You can use the Configuration Change Logging and Notification feature to track changes on a per-session and per-user basis. The logger tracks each configuration command that is applied, the user who entered the command, the time that the command was entered, and the parser return code for the command. This feature includes a mechanism for asynchronous notification to registered applications whenever the configuration changes. You can choose to have the notifications sent to the syslog.

Note Only CLI or HTTP changes are logged.

Table 2-3 Common CLI Error Messages

Error Message Meaning How to Get Help

% Ambiguous command: "show con"

You did not enter enough characters for your switch to recognize the command.

Reenter the command followed by a question mark (?) with a space between the command and the question mark.

The possible keywords that you can enter with the command appear.

% Incomplete command. You did not enter all the keywords or values required by this command.

Reenter the command followed by a question mark (?) with a space between the command and the question mark.


% Invalid input detected at ‘^’ marker.

You entered the command incorrectly. The caret (^) marks the point of the error.

Enter a question mark (?) to display all the commands that are available in this command mode.



Chapter 2 Using the Command-Line InterfaceHow to Use the CLI to Configure Features

How to Use the CLI to Configure Features

Configuring the Command HistoryThe software provides a history or record of commands that you have entered. The command history feature is particularly useful for recalling long or complex commands or entries, including access lists. You can customize this feature to suit your needs as described in these sections:

• Changing the Command History Buffer Size, page 2-6 (optional)

• Recalling Commands, page 2-6 (optional)

• Disabling the Command History Feature, page 2-7 (optional)

Changing the Command History Buffer Size

By default, the switch records ten command lines in its history buffer. You can alter this number for a current terminal session or for all sessions on a particular line. These procedures are optional.

Beginning in privileged EXEC mode, enter this command to change the number of command lines that the switch records during the current terminal session:

Switch# terminal history [size number-of-lines]

The range is from 0 to 256.

Beginning in line configuration mode, enter this command to configure the number of command lines the switch records for all sessions on a particular line:

Switch(config-line)# history [size number-of-lines]

The range is from 0 to 256.

Recalling Commands

To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions are optional.

Table 2-4 Recalling Commands

Action1

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.

Result

Press Ctrl-P or the up arrow key. Recall commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands.

Press Ctrl-N or the down arrow key. Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively more recent commands.

show history While in privileged EXEC mode, list the last several commands that you just entered. The number of commands that appear is controlled by the setting of the terminal history global configuration command and the history line configuration command.



Disabling the Command History Feature

The command history feature is automatically enabled. You can disable it for the current terminal session or for the command line. These procedures are optional.

To disable the feature during the current terminal session, enter the terminal no history privileged EXEC command.

To disable command history for the line, enter the no history line configuration command.

Using Editing FeaturesThis section describes the editing features that can help you manipulate the command line. It contains these sections:

• Enabling and Disabling Editing Features, page 2-7 (optional)

• Editing Commands Through Keystrokes, page 2-7 (optional)

• Editing Command Lines That Wrap, page 2-9 (optional)

Enabling and Disabling Editing Features

Although enhanced editing mode is automatically enabled, you can disable it, reenable it, or configure a specific line to have enhanced editing. These procedures are optional.

To globally disable enhanced editing mode, enter this command in line configuration mode:

Switch (config-line)# no editing

To reenable the enhanced editing mode for the current terminal session, enter this command in privileged EXEC mode:

Switch# terminal editing

To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration mode:

Switch(config-line)# editing

Editing Commands Through Keystrokes

Table 2-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.

Table 2-5 Editing Commands through Keystrokes

Capability Keystroke1 Purpose

Move around the command line to make changes or corrections.

Press Ctrl-B, or press the left arrow key.

Move the cursor back one character.



Press Ctrl-F, or press the right arrow key.

Move the cursor forward one character.

Press Ctrl-A. Move the cursor to the beginning of the command line.

Press Ctrl-E. Move the cursor to the end of the command line.

Press Esc B. Move the cursor back one word.

Press Esc F. Move the cursor forward one word.

Press Ctrl-T. Transpose the character to the left of the cursor with the character located at the cursor.

Recall commands from the buffer and paste them in the command line. The switch provides a buffer with the last ten items that you deleted.

Press Ctrl-Y. Recall the most recent entry in the buffer.

Press Esc Y. Recall the next buffer entry.

The buffer contains only the last 10 items that you have deleted or cut. If you press Esc Y more than ten times, you cycle to the first buffer entry.

Delete entries if you make a mistake or change your mind.

Press the Delete or Backspace key.

Erase the character to the left of the cursor.

Press Ctrl-D. Delete the character at the cursor.

Press Ctrl-K. Delete all characters from the cursor to the end of the command line.

Press Ctrl-U or Ctrl-X. Delete all characters from the cursor to the beginning of the command line.

Press Ctrl-W. Delete the word to the left of the cursor.

Press Esc D. Delete from the cursor to the end of the word.

Capitalize or lowercase words or capitalize a set of letters.

Press Esc C. Capitalize at the cursor.

Press Esc L. Change the word at the cursor to lowercase.

Press Esc U. Capitalize letters from the cursor to the end of the word.

Designate a particular keystroke as an executable command, perhaps as a shortcut.

Press Ctrl-V or Esc Q.

Table 2-5 Editing Commands through Keystrokes (continued)




Editing Command Lines That Wrap

You can use a wraparound feature for commands that extend beyond a single line on the screen. When the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the first ten characters of the line, but you can scroll back and check the syntax at the beginning of the command. The keystroke actions are optional.

To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You can also press Ctrl-A to immediately move to the beginning of the line.

The arrow keys function only on ANSI-compatible terminals such as VT100s.

In this example, the access-list global configuration command entry extends beyond one line. When the cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line, the line is again shifted ten spaces to the left.

Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1Switch(config)# $ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25Switch(config)# $t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eqSwitch(config)# $108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45

After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been scrolled to the right:

Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$

The software assumes you have a terminal screen that is 80 columns wide. If you have a different width, use the terminal width privileged EXEC command to set the width of your terminal.

Use line wrapping with the command history feature to recall and modify previous complex command entries. For information about recalling previous command entries, see the “Editing Commands Through Keystrokes” section on page 2-7.

Scroll down a line or screen on displays that are longer than the terminal screen can display.

Note The More prompt is used for any output that has more lines than can be displayed on the terminal screen, including show command output. You can use the Return and Space bar keystrokes whenever you see the More prompt.

Press the Return key. Scroll down one line.

Press the Space bar. Scroll down one screen.

Redisplay the current command line if the switch suddenly sends a message to your screen.

Press Ctrl-L or Ctrl-R. Redisplay the current command line.

1. The arrow keys function only on ANSI-compatible terminals such as VT100s.

Table 2-5 Editing Commands through Keystrokes (continued)




Searching and Filtering Output of show and more CommandsYou can search and filter the output for show and more commands. This is useful when you need to sort through large amounts of output or if you want to exclude output that you do not need to see. Using these commands is optional.

To use this functionality, enter a show or more command followed by the pipe character (|), one of the keywords begin, include, or exclude, and an expression that you want to search for or filter out:

command | {begin | include | exclude} regular-expression

Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output are not displayed, but the lines that contain Output appear.

This example shows how to include in the output display only lines where the expression protocol appears:

Switch# show interfaces | include protocolVlan1 is up, line protocol is upVlan10 is up, line protocol is down

Accessing the CLIYou can access the CLI through a console connection, through Telnet, or by using the browser.

Accessing the CLI through a Console Connection or through Telnet

Before you can access the CLI, you must connect a terminal or PC to the switch console port and power on the switch, as described in the getting started guide that shipped with your switch. Then, to understand the boot process and the options available for assigning IP information, see Chapter 4, “Performing Switch Setup Configuration.”

If your switch is already configured, you can access the CLI through a local console connection or through a remote Telnet session, but your switch must first be configured for this type of access. For more information, see the “Setting a Telnet Password for a Terminal Line” section on page 12-28.

You can use one of these methods to establish a connection with the switch:

• Connect the switch console port to a management station or dial-up modem. For information about connecting to the console port, see the Hardware Installation Guide.

• Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management station. The switch must have network connectivity with the Telnet or SSH client, and the switch must have an enable secret password configured.

For information about configuring the switch for Telnet access, see the “Setting a Telnet Password for a Terminal Line” section on page 12-28. The switch supports up to 16 simultaneous Telnet sessions. Changes made by one Telnet user are reflected in all other Telnet sessions.

For information about configuring the switch for SSH, see the “Configuring the SSH Server” section on page 12-40. The switch supports up to five simultaneous secure SSH sessions.

After you connect through the console port, through a Telnet session or through an SSH session, the user EXEC prompt appears on the management station.


C H A P T E R 3

Configuring Switch Alarms

Finding Feature Information Your software release may not support all the features documented in this chapter. For the latest feature information and caveats, see the release notes for your platform and software release.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Information About Switch Alarms The switch software monitors switch conditions on a per-port or a switch basis. If the conditions present on the switch or a port do not match the set parameters, the switch software triggers an alarm or a system message. By default, the switch software sends the system messages to a system message logging facility, or a syslog facility. You can also configure the switch to send Simple Network Management Protocol (SNMP) traps to an SNMP server. You can configure the switch to trigger an external alarm device by using the alarm relay.


http://www.cisco.com/go/cfnhttp://www.cisco.com/go/cfn

Chapter 3 Configuring Switch AlarmsInformation About Switch Alarms

Global Status Monitoring AlarmsThe switch processes alarms related to temperature and power supply conditions, referred to as global or facility alarms.

FCS Error Hysteresis ThresholdThe Ethernet standard calls for a maximum bit-error rate of 10-8. The bit error-rate range is from 10-6 to 10-11. The bit error-rate input to the switch is a positive exponent. If you want to configure the bit error-rate of 10-9, enter the value 9 for the exponent. By default, the FCS bit error-rate is 10-8.

You can set the FCS error hysteresis threshold to prevent the toggle of the alarm when the actual bit-error rate fluctuates near the configured rate. The hysteresis threshold is defined as the ratio between the alarm clear threshold to the alarm set threshold, expressed as a percentage value.

For example, if the FCS bit error-rate alarm value is configured to 10–8, that value is the alarm set threshold. To set the alarm clear threshold at 5*10-10, the hysteresis, value h, is determined as follows:

h = alarm clear threshold / alarm set threshold

h = 5*10-10 / 10-8 = 5*10-2 = 0.05 = 5 percent

The FCS hysteresis threshold is applied to all ports on the switch. The allowable range is from 1 to 10 percent. The default value is 10 percent. See the “Configuring the FCS Bit Error Rate Alarm” section on page 3-7 for more information.

Port Status Monitoring AlarmsThe switch can also monitor the status of the Ethernet ports and generate alarm messages based on the alarms listed in Table 3-2. To save user time and effort, it supports changeable alarm configurations by using alarm profiles. You can create a number of profiles and assign one of these profiles to each Ethernet port.

Table 3-1 Global Status Monitoring Alarms

Alarm Description

Power supply alarm By default, the switch monitors a single power supply. If you configure a dual power supply, an alarm triggers if one power supply fails. You can configure the power supply alarm to be connected to the hardware relays. For more information, see the “Configuring the Power Supply Alarms” section on page 3-6.

Temperature alarms The switch contains one temperature sensor with a primary and secondary temperature setting. The sensor monitors the environmental conditions inside the switch.

The primary and secondary temperature alarms can be set as follows:

• The primary alarm is enabled automatically to trigger both at a low temperature, –4°F (–20°C) and a high temperature, 203°F (95°C). It cannot be disabled. By default, the primary temperature alarm is associated with the major relay.

• The secondary alarm triggers when the system temperature is higher or lower than the configured high and low temperature thresholds. The secondary alarm is disabled by default.

For more information, see the “Configuring the Switch Temperature Alarms” section on page 3-6.

SD-Card By default the alarm is disabled.


Chapter 3 Configuring Switch AlarmsInformation About Switch Alarms

Alarm profiles provide a mechanism for you to enable or disable alarm conditions for a port and associate the alarm conditions with one or both alarm relays. You can also use alarm profiles to set alarm conditions to send alarm traps to an SNMP server and system messages to a syslog server. The alarm profile defaultPort is applied to all interfaces in the factory configuration (by default).

Note You can associate multiple alarms to one relay or one alarm to both relays.

Table 3-2 lists the port status monitoring alarms and their descriptions and functions. Each fault condition is assigned a severity level based on the Cisco IOS System Error Message Severity Level.

Triggering Alarm OptionsThe switch supports these methods for triggering alarms:

• Configurable Relay

The switch is equipped with one independent alarm relay that can be triggered by alarms for global, port status and SD flash card conditions. You can configure the relay to send a fault signal to an external alarm device, such as a bell, light, or other signaling device. You can associate any alarm condition with the alarm relay. Each fault condition is assigned a severity level based on the Cisco IOS System Error Message Severity Level.

See the “Configuring the Power Supply Alarms” section on page 3-6 for more information on configuring the relay.

• SNMP Traps

SNMP is an application-layer protocol that provides a message format for communication between managers and agents. The SNMP system consists of an SNMP manager, an SNMP agent, and a management information base (MIB).

Table 3-2 Port Status Monitoring Alarms

Alarm List ID Alarm Description

1 Link Fault alarm The switch generates a link fault alarm when problems with a port physical layer cause unreliable data transmission. A typical link fault condition is loss of signal or clock. The link fault alarm is cleared automatically when the link fault condition is cleared. The severity for this alarm is error condition, level 3.

2 Port not Forwarding alarm The switch generates a port not-forwarding alarm when a port is not forwarding packets. This alarm is cleared automatically when the port begins to forward packets. The severity for this alarm is warning, level 4.

3 Port not Operating alarm The switch generates a port not-operating alarm when a port fails during the startup self-test. When triggered, the port not-operating alarm is only cleared when the switc

Documents

Cisco IE 2000 Software Configuration Guide, Release 15.0(1)EY · Cisco IE 2000 Switch Software Configuration Guide Cisco IOS Release 15.0(1)EY ... LOSS OR DAMAGE TO DATA ARISING OUT