Cisco WS-C3550-12G User Manual

Download

Page 1

Corporate Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 526-4100

Cisco Catalyst Switch Manager User Guide

Release 3.1

Customer Order Number: OL-4930-01

Page 2

THE SPECIFICATIONS AND INFORMATION REGA RDING THE P RODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE W ITH OUT NOT ICE. A LL 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 RESPONSIBILIT Y FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRA NTY FO R THE A CCOMPA NYING PRODUCT A RE SET FORTH IN T HE INFORM ATION P ACKET 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 DO CUMENT FILES AND SOFTW ARE OF THESE SUPPL IERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM AL L WARRANTIES, EX PRESSED OR IMPLIED, INCLUDING, WITHO UT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICUL AR PURPOSE AND NON INFRINGEMENT OR ARISIN G 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, LOS T PROFITS OR LOSS OR DAMAGE TO DATA ARISIN G OUT OF THE US E OR INABILI TY TO USE THIS MA NUAL, EVEN I F CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SU CH DAMA GES.

Cisco Catalyst Switch Manager User Guide

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website 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. (0402R)

Page 3

iii

Cisco Catalyst Switch Manager User Guide

OL-4930-01

CONTENTS

About this Guide xxi

Document Audience xxii

Document Organization xxiii

Document Conventions xxiv

Related Documentation

While you can access all relate d docum entatio n on the C isco website, URLs which are available at the time of publication are noted in the following lists.

The following Cisco EMF documentation is available for reference:

• Quick Start Guide Cisco EMF Version 3.2 SP7

http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_quick_start09186a00 801a8e01.html

• Cisco Element Management Framework Installation and Administration Guide

Version 3.2 Servic e Pack 7

http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_installation_and_conf iguration_guide_book09186a00801a8e04.html

• Cisco Element Management Framework User Guide Version 3.2 Service Pack 7

http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_user_guide_book091 86a00801a8815.html

• Release Notes for Cisco Element Management Framework v3.2 Service Pack 7

http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/prod_release_note09186a0080 1a7220.html

In addition to this guide, the following Cisco Catalyst Switch Manager documentation is available for reference:

• Cisco Catalyst Switch Manager Installation Guide Version 3.1

• Release Notes for Cisco Catalyst Switch Manager, Version 3.1

Page 26

xxvi

Cisco Catalyst Switch Manager User Guide

OL-4930-01

About this Guide

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-R OM is updated regul arly and may be more current than printed documentation. The CD -R OM package is av ailable as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco do cumentati on in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from

the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by

calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Page 27

xxvii

Cisco Catalyst Switch Manager User Guide

OL-4930-01

About this Guide

Obtaining Documentation

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments to bug-doc@cisco.com. You can submit comments by using the response card (if present) behind the front cover of your

document or by writing to the following address: Cisco Systems

Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883

We appreciate your comments.

Page 28

xxviii

Cisco Catalyst Switch Manager User Guide

OL-4930-01

About this Guide

Obtaining Technical Assistance

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample confi gurations from the Cisco TAC website. Cisco.com register ed users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,

product installation, or basic product configuration. There is little or no impact to your business operations.

• Priority level 3 (P3)—Operational performance of the network is impaired, but most business

operations remain functional. You and Cisco are willing to commit resources during normal b usiness hours to restore service to satisfactory levels.

• Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects

of your business operations are negatively impacted by inadequate performance of Cisc o produc ts. You and Cisco will commit full-time resources during normal business hours to reso lve the situation.

• Priority level 1 (P1)—An ex isting network is “down,” or there is a critical impact to your business

operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Page 29

xxix

Cisco Catalyst Switch Manager User Guide

OL-4930-01

About this Guide

Obtaining Technical Assistance

Cisco TAC Website

The Cisco TAC website provides online documents and to ols to help troubl esh oot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradati on signi f icantly impact s b usi ness operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for e xample, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Page 30

xxx

Cisco Catalyst Switch Manager User Guide

OL-4930-01

About this Guide

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solu tio ns is available from v a rious online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Ci sco Systems, as well as

ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new

and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco quarterly publication that provides the latest networking trends,

technology breakthroughs, and Cis co products an d solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certif ication information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

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

• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet

business strategies for executives. You can access iQ Magazine at this UR L:

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

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering

professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Inte rnet Prot ocol Journal at this UR L:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networking training. Current offerings in network training are

listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

Page 31

CHA P T E R

1-1

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Product Overview

This chapter consists of the following primary sections:

• Cisco Catalyst Switch Manager Software Overview

• Supported Hardware

• Supported Software

The Cisco Catalyst Switch Manager software manages and monitors Catalyst switches using Cisco Element Management Framework (Cisco EMF), version 3.2. The Cisco Catalyst Switch Manager provides standard element management functionality, such as fault, configuration, accounting, performance, and security (FCAPS).

Page 32

1-2

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Cisco Catalyst Switch Manager Software Overview

The Cisco Catalyst Switch Manager software adds custom windows and modeling behavior to the standard Cisco EMF system to provide management of the Catalyst switches.

The Cisco Catalyst Switch Manager helps network administrators manage Catalyst switches by eliminating the need to have Simple Network Management Protocol (SNMP) and a detailed knowledge of the Cisco IOS or Catalyst OS required commands. The Cisco Catalyst Switch Manager also helps simplify the deployment process for the Catalyst switches.

Multiple Element Managers can be installed onto a single Cisco EMF server, which allows multi-device and multi-vendor management from a single system.

Note Refer to the Cisco Element Management Framework User Guide for additional information.

Software Features

The Cisco Catalyst Switch Manager provides the following features:

• Manual predeployment of Catalyst switches and subcomponents in the management system before

actual installation. The system can automatically detect predeployed objects and begin management when they are installed and configured

• Autodiscovery feature that identifies newly installed Catalyst switches and their hardware

configuration

• Access to maps that are automatically created by the management system to show the exact

representation of Catalyst switches components

• SNMP alarms presented as color-coded icons on network maps

• Access to fault, configuration, accounting, performance, and security (FCAPS) functionality

(supported through SNMP and Cisco IOS or Catalyst OS software) through GUIs that you can operate without SNMP or Cisco IOS or Catalyst OS software expertise

• Many operations can be performed to several Catalyst switches, simplifying the management of a

large deployment of multiple switches

• Event browser or performance manager provide historical information analysis

• Configuration of Ethernet, PoS, ATM, and Sonet modules

• Configuration management, including backup and restore operations

• Software-download management

Page 33

1-3

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Hardware

The following table lists hardware supported by the Cisco Catalyst Switch Manager, release 3.1.

Table 1-1 Supported Hardware

Part Number Description

WS-C2950-12 12 port, 10/100 Catalyst Switch, Standard Image only WS-C2950C-24 Fixed 12-port Catalyst 2950 series chassis WS-C2950G-12-E1 Fixed 12-port Catalyst 2950 series chassis WS-C2950G-24-E1 Fixed 24-port Catalyst 2950 series chassis WS-C2950G-24-E1-DC Fixed 24-port Catalyst 2950 series chassis WS-C2950G-48-E1 Fixed 48-port Catalyst 2950 series chassis WS-C2950SX-24 24 10/100 ports w/2 1000BASE-SX ports, Standard Image only WS-C2950T-24 Fixed 24-port Catalyst 2950 series chassis WS-C2970G-24TS 24 Ethernet 10/100/1000 ports and 4 SFP ports WS-C2970G-24T 24 Ethernet 10/100/1000 ports WS-C3550-12T Fixed 12-port Catalyst 3550 series chassis WS-C3550-12G Fixed 12-port Catalyst 3550 series chassis WS-C3550-24-EMI/SMI Fixed 24-port Catalyst 3550 series chassis WS-C3550-24-DC-SMI Fixed 24-port Catalyst 3550 series chassis WS-C3550-48-EMI/SMI Fixed 48-port Catalyst 3550 series chassis WS-C3550-24-FX-SMI Fixed 24-port Catalyst 3550 series chassis WS-C4003 3-slot Catalyst 4000 series chassis WS-C4006-S3-AC/DC 6-slot Catalyst 4000 series chassis WS-C4503 3-slot Catalyst 4500 series chassis WS-C4506 6-slot Catalyst 4500 series chassis WS-C4507R 7-slot Catalyst 4500 series chassis WS-C6006 6-slot Catalyst 6000 series chassis WS-C6009 9-slot Catalyst 6000 series chassis WS-C6506 6-slot Catalyst 6500 series chassis WS-C6509 9-slot Catalyst 6500 series chassis WS-C6509-NEB Vertical 9-slot Catalyst 6500 series chassis WS-C6513 13-slot Catalyst 6500 series chassis WS-CAC-1000W 1000W AC power supply WS-CAC-1300W 1300W AC power supply WS-CAC-2500W 2500W AC power supply WS-CAC-4000W 4000W AC power supply WS-CDC-1300W 1300W DC power supply WS-CDC-2500W 2500W DC power supply

Page 34

1-4

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Hardware

PWR-1900-AC 1900W AC power supply WS-SUP720, SUP720 CEF720 SUP engine- integrated fabric, MSFC3 WS-X6K-SUP1-NOMSFC Supervisor Engine 1 without MSFC WS-X6K-SUP1A-MSFC Supervisor Engine 1A with MSFC WS-X6K-S1A-MSFC2 Supervisor Engine 1A with MSFC2 WS-X6K-S2-MSFC2 Supervisor Engine 2 with MSFC2 WS-X6K-S2U-MSFC2 Supervisor Engine 2 with 256 MB DRAM and MSFC2 WS-X6066-SLB-APC Content Switching Module WS-X6182-2PA FlexWAN Module WS-X6224-100FX-MT 24-port 100FX, MT-RJ WS-X6324-100FX-MM 24-port 100FX, MT-RJ, multimode fiber, 128K per port packet buffers WS-X6324-100FX-SM 24-port 100FX, MT-RJ, single-mode fiber, 128K per port packet buffers WS-X6324-100FX-SM 48-port 10/100TX, RJ-45 WS-X6248-TEL 48-port 10/100TX, RJ-21 WS-X6248A-TEL 48-port 10/100TX, RJ-21, 128K per port packet buffers WS-X6348-RJ-45 48-port 10/100TX, RJ-45, 128K per port packet buffers WS-X6348-RJ45V 48-port 10/100TX, RJ-45, 128K per port packet buf fers with inline po wer WS-X6348-RJ21 48-port 10/100, RJ-21, upgradable to voice WS-X6348-RJ21V 48-port 10/100, RJ-21, inline power WS-X6524-100FX-MM Fabric-enabled 100FX Fast Ethernet Module, multimode fiber, MT-RJ WS-X6548-RJ-21 Fabric-enabled 10/100 Fast Ethernet Modules, RJ-21 WS-X6548-RJ-45 Fabric-enabled 10/100 Fast Ethernet Modules, RJ-45 WS-X6408-GBIC 8-port Gigabit Ethernet WS-X6408A-GBIC 8-port Gigabit Ethernet with enhanced QoS WS-X6416-GBIC 16-port Gigabit Ethernet WS-X6416-GE-MT 16-port Gigabit Ethernet, MT-RJ WS-X6516-GBIC 16-port Gigabit Ethernet, single fabric-enabled connection WS-X6816-GBIC 16-port Gigabit Ethernet, dual fabric-enabled with Distributed

Forwarding, (Req GBICs) WS-X6316-GE-TX 16-port Gigabit Ethernet, RJ-45 WS-X6501-10GEX4 One-port 10GBASE-EX4 Metro Extended Reach 10 Gigabit Ethernet

Module (single-mode fiber) WS-X6502-10GE 1-port 10GBASE-LR Serial 130nm Long Haul 10 Gigabit Ethernet

module (WS-G6488 installed) WS-X6516-GE-TX 16-port Gigabit Ethernet, RJ-45, x-bar WS-X6066-SLB-APC Server Load Balancing Module WS-C6500-SFM Switch Fabric Module

Table 1-1 Supported Hardware (continued)

Part Number Description

Page 35

1-5

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Hardware

WS-6500-SFM2 Switch Fabric Module, version 2 WS-X4448-GB-LX Catalyst 4000 48-Port 1000Base-LX WS-X4448-GB-RJ45 Catalyst 4000 48-Port GE Module, 10/100/1000 Base-T (RJ45) WS-X4148-FE-LX-MT 48 ports 100BASE-LX10 for SMF (Fast Ethernet) WS-X4148-FX-MT Catalyst 4000 FE Switching Module, 48-100FX MMF (MTRJ) WS-X4148-RJ Catalyst 4000 10/100 Auto Module, 48-Ports (RJ-45) WS-X4148-RJ21 Catalyst 4000 10/100 Module, 48-Ports Telco (4xRJ21) WS-X4232-GB-RJ Catalyst 4000 E/FE/GE Module,2- GE(GBIC),32- 10/100 (RJ-45) WS-X4232-L3 Catalyst 4000 E/FE/GE L3 Module, 2-GE(GBIC),32-10/100 WS-X4232-RJ-XX Catalyst 4000 10/100 Module,32-ports(RJ45)+Modular uplinks WS-X4424-GB-RJ45 Catalyst 4000 24-port 10/100/1000 Module (RJ45) WS-X4306-GB Catalyst 4000 Gigabit Ethernet Module, 6-Ports (GBIC) WS-X4412-2GB-T Catalyst 4000,12-port GE 1000T(RJ45)+2GBIC WS-X4418-GB Catalyst 4000 GE Module, Server Switching 18-Ports (GBIC) WS-G5484 1000BASE-SX Short Wavelength GBIC (Multimode only) WS-G5486 1000BASE-LX/LH long haul GBIC (singlemode or multimode) WS-G5487 1000Base-ZX extended reach GBIC (singlemode) WS-G5483 1000BASE-T GBIC OSM-4GE-WAN-GBIC 4-port Gigabit Ethernet Optical Services Module, GBIC OSM-4OC12-POS-MM 4-port OC-12/STM-4 SONET/SDH OSM, MM, with 4 ports of Gigabit

Ethernet

OSM-4OC12-POS-SI 4-port OC-12/STM-4 SONET/SDH OSM, SM-IR, with 4 ports of

Gigabit Ethernet OSM-4OC12-POS-SI+ Enhanced 4-port OC-12/STM-4 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-4OC12-POS-SL 4-port OC-12/STM-4 SONET/SDH OSM, SM-LR, with 4 ports of

Gigabit Ethernet OSM-1OC48-POS-SS 1-port OC-48/STM-16 SONET/SDH OSM, SM-SR, with 4 ports of

Gigabit Ethernet OSM-1OC48-POS-SS+ Enhanced 1-port OC-48/STM-16 SONET/SDH OSM, SM-SR, w/ 4 GE OSM-1OC48-POS-SI 1-port OC-48/STM-16 SONET/SDH OSM, SM-IR, with 4 ports of

Gigabit Ethernet OSM-1OC48-POS-SI+ Enhanced 1-port OC-48/STM-16 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-4OC3-POS-SI 4-port OC-3/STM-1 SONET/SDH OSM, with 4 GE OSM-4OC3-POS-SI+ Enhanced 4-port OC-3/STM-1 SONET/SDH SM-IR OSM, w/ 4 GE OSM-1OC48-POS-SL+ Enhanced 1-port OC-48/STM-16 SONET/SDH OSM, SM-LR, w/ 4 GE OSM-8OC3-POS-SI+ Enhanced 8-port OC-3/STM-1 SONET/SDH SM-IR OSM, w/ 4 GE OSM-16OC3-POS-SI+ Enhanced 16-port OC-3/STM-1 SONET/SDH OSM, SM-IR, w/ 4 GE

Table 1-1 Supported Hardware (continued)

Part Number Description

Page 36

1-6

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Hardware

OSM-2OC12-POS-MM+ Enhanced 2-port OC-12/STM-4 SONET/SDH OSM, MM, w/ 4 GE OSM-2OC12-POS-SI+ Enhanced 2-port OC-12/STM-4 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-4OC12-POS-SI+ Enhanced 4-port OC-12/STM-4 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-1OC48-POS-SS+ Enhanced 1-port OC-48/STM-16 SONET/SDH OSM, SM-SR, w/ 4 GE OSM-1OC48-POS-SI+ Enhanced 1-port OC-48/STM-16 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-2OC48/1DPT-SS 2-port OC-48/STM-16 POS/DPT OSM, SM-SR, with 4 GE OSM-2OC48/1DPT-SL 2-port OC-48/STM-16 POS/DPT OSM, SM-LR, with 4 GE OSM-2OC48/1DPT-SI 2-port OC-48/STM-16 POS/DPT OSM, SM-IR, with 4 GE OSM-2CHOC12/T3-SI 2-port CHOC-12/CHSTM-4 OSM, to T3/E3, SM-IR, with 4 GE OSM-2CHOC48/T3-SS 2-port CHOC-48/CHSTM-16 OSM, to T3/E3, SM-SR, with 4 GE OSM-1OC48-POS-SL 1-port OC-48/STM-16 SONET/SDH OSM, SM-LR, with 4 ports of

Gigabit Ethernet

OSM-16OC3-POS-MM 16-port OC-3/STM-1 SONET/SDH OSM, MM, with 4 ports of Gigabit

Ethernet

OSM-16OC3-POS-SI 16-port OC-3/STM-1 SONET/SDH OSM, SM-IR, with 4 ports of

Gigabit Ethernet

OSM-16OC3-POS-SL 16-port OC-3/STM-1 SONET/SDH OSM, SM-LR, with 4 ports of

Gigabit Ethernet

OSM-2OC12-POS-MM 2-port OC-12/STM-4 SONET/SDH OSM, MM, with 4 ports of Gigabit

Ethernet OSM-2OC12-POS-MM+ Enhanced 2-port OC-12/STM-4 SONET/SDH OSM, MM, w/ 4 GE OSM-2OC12-POS-SI 2-port OC-12/STM-4 SONET/SDH OSM, SM-IR, with 4 ports of

Gigabit Ethernet OSM-2OC12-POS-SI+ Enhanced 2-port OC-12/STM-4 SONET/SDH OSM, SM-IR, w/ 4 GE OSM-2OC12-POS-SL 2-port OC-12/STM-4 SONET/SDH OSM, SM-LR, with 4 ports of

Gigabit Ethernet OSM-8OC3-POS-MM 8-port OC-3/STM-1 SONET/SDH OSM, MM, with 4 ports of Gigabit

Ethernet OSM-8OC3-POS-SI 8-port OC-3/STM-1 SONET/SDH OSM, SM-IR, with 4 ports of Gigabit

Ethernet OSM-8OC3-POS-SL+ Enhanced 8-port OC-3/STM-1 SONET/SDH SM-LR OSM, w/ 4 GE OSM-8OC3-POS-SL 8-port OC-3/STM-1 SONET/SDH OSM, SM-LR, with 4 ports of Gigabit

Ethernet OSM-1CHOC12/T3-SI 1-port CHOC-12/CHSTM-4 OSM, to T3/E3, SM-IR, with 4 GE OSM-1CHOC48/T3-SS 1-port channelized OC48 OSM, SM-SR, with 4 Gigabit Ethernet OSM-1CHOC48/T3-SI 1-port channelized OC48 OSM, SM-IR, with 4 Gigabit Ethernet OSM-2CHOC48/T3-SS 2-port channelized OC48 OSM, SM-SR, with 4 ports of Gig abit Ethernet OSM-2CHOC48/T3-SI 2-port channelized OC-48 OSM, SM-IR, with 4 po rts of Gigabit Ethernet OSM-4CHOC12/T3-MM 4-port channelized OC-12 OSM, MM, with 4 ports of Gigabit Ethernet

Table 1-1 Supported Hardware (continued)

Part Number Description

Page 37

1-7

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Hardware

OSM-4CHOC12/T3-SI 4-port channelized OC-12 OSM, SI, with 4 ports of Gigabit Ethernet OSM-8CHOC12/T3-MM 8-port channelized OC-12 OSM, MM, with 4 ports of Gigabit Ethernet OSM-8CHOC12/T3-SI 8-port channelized OC-12 OSM, SI, with 4 ports of Gigabit Ethernet PA-2E3 2 Port E3 Serial Port Adapter with E3 DSUs PA-2H 2-Port HSSI Port Adapter PA-2T3 2 Port T3 Serial Port Adapter PA-2T3+ 2 Port T3 Serial Port Adapter Enhanced PA-4T+ 4 Port Serial Port Adapter, Enhanced PA-8T-232 8-Port Serial, 232 Port Adapter PA-8T-V35 8-Port Serial, V.35 Port Adapter PA-8T-X21 8-Port Serial, X.21 Port Adapter PA-A3-E3 1-Port ATM Enhanced E3 Port Adapter PA-A3-OC3MM 1-Port ATM Enhanced OC3c/STM1 Multimode Port Adapter PA-A3-OC3SMI 1-Port ATM Enhanced OC3c/STM1 Singlemode (IR) Port Adapter PA-A3-OC3SML 1-Port ATM Enhanced OC3c/STM1 Singlemode (LR) Port Adapter PA-A3-T3 1-Port ATM Enhanced DS3 Port Adapter PA-E3 1 Port E3 Serial Port Adapter with E3 DSU PA-H 1-Port HSSI Port Adapter PA-MC-2T3+ 2 port multichannel T3 port adapter PA-MC-8E1/120 8 port multichannel E1 port adapter with G.703 120ohm interface PA-MC-8T1 8 port multichannel T1 port adapter with integrated CSU/DSUs PA-MC-E3 1 port Multi-Channel E3 port adapter PA-MC-T3 1 port multichannel T3 port adapter PA-POS-OC3MM 1-Port Packet/SONET OC3c/STM1 Multimode Port Adapter PA-POS-OC 3SMI 1-Port Packet/SONET OC3c/STM1 Singlemode (IR) Port Adapter PA-POS-OC 3SML 1-Port Packet/SONET OC3c/STM 1 Singlemode (LR ) Port Adapte r PA-T3 1 Port T3 Serial Port Adapter PA-T3+ 1 Port T3 Serial Port Adapter Enhanced PA-A3-8E1IMA 8-port ATM Inverse Mux E1 (120 Ohm) Port Adapter PA-MC-4T1 4 port multichannel T1 port adapter with integrated CSU/DSUs GE-WAN2 2-port Gigabit Ethernet

Table 1-1 Supported Hardware (continued)

Part Number Description

Page 38

1-8

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 1 Product Overview

Supported Software

The Cisco Catalyst Switch Manager 3.1 supports the following IOS and Catalyst OS software.

The following Native IOS releases are supported as listed by chassis family:

• Catalyst 2950 series switch—12.1(11)EA1, 12.1(12c)EA1, 12.1(13)EA1, and 12.1(14)EA1

• Catalyst 2970 series switch—12.1(14)EA1

• Catalyst 3550 series switch—12.1(11)EA1, 12.1(12c)EA1, 12.1(12)EA1, 12.1(13)EA1, and

12.1(14)EA1

• Catalyst 4000 series switches:

–

Catalyst 4006 switch—12.1(12c)EW1 and 12.1(13)EW2

–

Catalyst 4503 switch—12.1(13)EW, 12.1(12c)EW1, and 12.1(13)EW2

–

Catalyst 4506 switch—12.1(12c)EW1 and 12.1(13)EW2

• Catalyst 6500 series switch:

–

Catalyst 6509NEB switch—12.1(13)E, 12.1(13)E1, and 12.1(19)E1

–

Catalyst 6513 switch—12.1(13)E, 12.1(13)E4, and 12.1(19)E1

The following Pure Catalyst OS version is supported by the Catalyst 6506 and 6509 switch:

7.2, 7.3, 7.4, 7.5 and 7.5(1), 7.6, and 8.2.

The following table identifies the Hybrid OS combinations supported by device.

Note The above versions of CatOS and IOS have been extensively tested with the Cisco Catalyst Switch

Manager software. Other versions and combinations of CatOS/IOS should interoperate with the manager, although there may be unanticipated incompatibilities or errors.

Table 1-2 Supported Hybrid OS Combinations

Device IOS Version Catalyst OS Version

Catalyst 6006 switch 12.1(12c) 6.3(10)

12.1(12c)E4 6.3(8)

12.1(12c)E4 6.3(9)

12.1(12c)E4 7.5(1)

12.1(12c)E4 7.6(1)

Catalyst 6509 switch 12.1(13)E 7.5(1)

12.1(19)E1 7.6(latest)

Page 39

CHA P T E R

2-1

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Basic Concepts

This chapter describes basic concepts and terminology used in this guide, and consists of the following primary sections:

• Cisco EMF and Cisco Catalyst Switch Manager Software

• Cisco Catalyst Switch Manager Objects and Interfaces

• Containment Views

• Cisco Catalyst Switch Manager Object States

Page 40

2-2

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco EMF and Cisco Catalyst Switch Manager Software

The Cisco Catalyst Switch Manager is the carrier-class element manager for Catalyst switches, which “plugs into” Cisco EMF. The Cisco Catalyst Switch Manager software adds additional windows and a back-end controller process that communicates with the hardware elements (using Cisco EMF) as shown in the following figure.

Figure 2-1 Cisco EMF and Cisco Catalyst Switch Manager Processes

Element Management

An Element Manager is an application that is responsible for providing fault, conf igu ration, accounting, performance and security (FCAPS) management for a particular type of Network Element or family of Network Elements. The Cisco Catalyst Switch Manager software primarily provides fault and performance information. The configuration capabilities are limited, and the accounting information is used for inve ntory purposes. No security information is pro vided b y the Cisco Catal yst Switch Manager.

Element Manager

Windows

C65/76M controller

CEMF

Management

Network

Cisco EM Database

Cisco C65/76M Database

Cisco EM controller

Catalyst 6500

73603

Page 41

2-3

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Objects and Interfaces

The Cisco Catalyst Switch Manager software provides three types of objects:

• Physical—Represents actual components and devices such as the chassis (hardware frame), fans,

power supplies, modules, and ports/interfaces.

• Logical—Represents the nontangible features, such as VLAN configurations, EtherChannels, and

routing protocols.

• Network element—Represents the entir e Catalyst switch managed through a single SN MP agent and

IOS command-line interface.

Physical Objects

The Cisco Catalyst Switch Manager software models the following physical components:

• Chassis—The hardware frame of the Catalyst switch

• Power supplies—The source of power for the Catalyst switch

• Supervisor Engine modules—Contain the route and switch processors

• Ethernet interfaces—Ports on Ethernet modules and supervisor engine modules

• Ethernet modules—Represent Ethernet, Fast Etherne t, and Gigabit Ethe rnet modu les

• Switch Fabric Modules—Provide connection to the crossbar switching fabric

• FlexWAN modules —Supports up to two port adapters that provide WAN and MAN connections

• Port adapters—The port adapters plug into the FlexWAN module to provide WAN and MAN

connections

• OSM GeWAN modules/interfaces—Modules and associated ports that provide 4 Gigabit Ethernet

WAN connections

• OSM PoS modules/interfaces—Modules and associated ports that provide Packet-over-SONET

(PoS) connection support

• OSM Channelized SONET modules/interfaces—Modules and associated ports that provide

SONET-based channelizing of interface bandwidth, including both PoS and serial subinterfaces

• Content Switching Modules—Defines a virtual server that represents a cluster of real servers

Page 42

2-4

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Objects and Interfaces

These Cisco Catalyst Switch Manager objects have the following hierarchical organization:

• Chassis

–

Power supplies

–

Supervisor engine modules: Ethernet interfaces

–

Ethernet modules: Ethernet interfaces

–

Switch Fabric Modules

–

FlexWAN Modules Port adapters: ATM port adapters ATM SONET interfaces ATM E3 interfaces ATM T3 interfaces

–

OSM GeWAN Modu les OSM GeWAN interfaces

–

OSM PoS Modules Ethernet interfaces OSM PoS interfaces

–

OSM Channelized SONET Modules Ethernet interfaces OSM ChSONET interfaces OSM Serial Subinterfaces OSM PoS Subinterfaces

–

Content Switching Modules

Logical Objects

The Cisco Catalyst Switch Manager models the following logical components:

• Software—Represents the IOS image and configuration file on the Catalyst switch

• EtherChannels—Creates, delete s, and modi fies EtherChannels on the Catal yst switch

• VLAN—Lists, creates, and deletes VLAN interfaces on the Catalyst switch

• Loopback—Used to isolate the fault on an end-to-end circuit

• Syslog—Represents the standard syslog messaging protocol on the Catal yst switc h

• ACL—Represent access control lists, both standard and extended, named and numbered

• NDE—NetFlow Data Export (NDE) makes traf fic stat istics available for analysis b y an external data

collector

• QoS—Enables and manages the global quality of service (QoS) engine.

Page 43

2-5

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Objects and Interfaces

• QoS policy map—Describes the traffic filters applied to enforce QoS parameters on ingress traffic

received on an interface or VLAN.

• EIGRP—Creates, modifies, and deletes Enhanced Interior Gateway Routing Protocol (EIGRP)

instances on the Catalyst switch

• BGP—Creates and modifies Border Gateway Protocol (BGP) routing protocol

• OSPF—Displays the Open Shortest Path First (OSPF) routing protocol information for the

Catalyst switch

• VTP—VLAN Trunking Protocol

• STP—Spanning Tree Protocol

• IS-IS—Creates, modifies, and deletes in termed iate system-to-intermediate system (IS-IS) routing

processes on the Catalyst switch

These components have the following hierarchical organization:

• Software

–

EtherChannels

–

Syslog

–

EIGRP

–

BGP

–

OSPF

–

VTP

–

VLAN

–

STP

–

IS-IS

–

ACL

–

NDE

–

MPLS

–

Loopback

–

QoS QoS policy map

Page 44

2-6

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Objects and Interfaces

Network Element Object

The Network Element object is a logical container representing the entire Catalyst switch managed through the supervisor and/or MSFC SNMP agents and Catalyst OS/IOS command-line interface. This class acts as a container for the physical and logical components of the device. The entire hierarchical structure of the Cisco Catalyst Switch Manager components is as follows:

Network Element

Chassis

Power Supplies Supervisor Modules Ethernet Interfaces Ethernet Modules Ethernet Interfaces Switch Fabric Modules FlexWAN Modules Port Adapter ATM Port Adapter ATM SONET Interfaces ATM E3 Interfaces ATM T3 Interfaces OSM GeWAN Modules OSM GeWAN Interfaces OSM POS Modules Ethernet Interfaces OSM POS Interfaces OSM Channelized SONET Modules Ethernet Interfaces OSM Channelized SONET Interfaces OSM Serial Sub-interfaces OSM POS Sub-interfaces Content Switching Modules

Software

EtherChannels Syslog EIGRP BGP OSPF VTP VLAN STP IS-IS ACL NDE Loopback QoS QoS Policy Map

Page 45

2-7

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Containment Views

The Cisco EMF Map Viewer application uses a concept called containment views to allow logical grouping of monitored objects. Objects being managed by Cisco EMF must be added to one or more containment views. Objects are organized into different views and can exist in multiple views simultaneously by reference. Objects can be in one or more containment views.

When installed, the Cisco Catalyst Switch Manager does not modify the visible containment views and all managed objects will appear in the Physical tree. Note that previous versions of the EMS added three other containment views (Catalyst6000Manager, Catalyst6500Manager and Cisco7600Manager). If these views are present, the version 2.0 or earlier release of the Manager application is still instal led. See the Cisco 6500/760 0 Manager Installation Gu ide for instruction on remo ving the pre vious version of the Manager.

View s are accessible by clicking the Viewer icon on the Cisco EMF launchpad. These views appear in the frame at the left of the window when you op en the Map Viewer window (see the follo wing f ig ure for an example).

Vie ws model hierarchical relationships between objects, both physical and logical. Objects are organized into different views and can exist in multiple views simultaneously by reference. Each object can have a number of parent and child objects. You can access EM objects by navigat ing through one of t he vie ws to find specific objects b y e x panding th e te xt. Cli ck on the p lus sign (+) ne xt to any object to expand the view. A minus sign (–) next to an object indicates there are no more levels to expand; you may, however , click on a minus sign (–) to collapse the view to the level of the specific object as necessary. Each view represents a different way of containing and grouping objects.

The EM adds specific views to the standard views supplied by Cisco EMF. The sta ndard Cisco EMF views are the Physical and Network views.

Note For further information on views, see the Cisco Element Management Framework User Guide Release

3.2.

Figure 2-2 EM Views

The number in parenthesis next to a view indicat es ho w many top–le v el object s are contained withi n the view. Notice that the RME and VLAN–QinQ views do not display a number beside the view name. In addition to the minus sign beside the view n ame, the absence of a number is a indicator that there are no objects beneath it.

Page 46

2-8

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Containment Views

The Views sec tion covers the following areas:

• Network View

• Physical View

• RME View

• Self Management View

• VLAN–QinQ View

You may or may not see all of these views using this EM (exceptions noted). These views all e xist within EMs, however they are not all implemented. If multiple EMs are co–resident, the applicable views are displayed.

Network View

The network view is a standard feature in Cisco EMF that displays all network devices within their relevant networks and subnets. The auto–discovery system of Cisco EMF uses this view to determine which devices exist on the system so that it does not try to disco ver the same de vice multipl e times. This view displays all IP devices under their paren t network (that is, it groups monit ored objects in a network layout). This view provides a logical view of the network structure. Fo r example, devices on the same subnet would be grouped together.

Refer to the Cisco Element Management Framework User Guide for more information.

Physical View

Objects in the Physical view are ordered according to their relative geographical or physical location. The Physical view defines physical containment relationships, meaning that each object is defined according to which object it is contained within. For example, a site is located under the Physical view; a chassis is contained under a site; and sub modules and supporting modules are contained within a chassis.

The Physical view also provides chassis maps, which are gr aphical represen tations o f the ch assis and its contents. You can access management menus on objects within chassis maps. To display a chassis map, simply click on the chassis object for the router you wish to view. Logical connection objects are not apparent under the Physical view.

Page 47

2-9

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Containment Views

Figure 2-3 Physical View Chassis Map

Refer to the Cisco Element Management Framework User Guide for more information.

RME View

All objects managed by the RME server display beneath the RME view. Objects are organized by RME server objects.

Note For more information on RME, refer to the User Guide for Resource Manager Essentials 3.5 at the

following URL:

http://www.cisco.com/en/US/products/sw/ciscowork/ps2073/products_user_guide_book09186a00800c a43b.html

Page 48

2-10

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Containment Views

Self Management View

This view allows you to monitor network elements which are part of the Cisco EMF system. The Self Management view is non–propagating.

VLAN–QinQ View

The VLAN–QinQ view displays the interfaces for which 802.1Q tunneling is enabled. Each such interface is represented as a child of the associated VLAN. The following displays an example of the object hierarchy.

• VLAN-X

–

ChassisX-InterfaceX

–

ChassisY-InterfaceY

• VLAN-Y

–

ChassisX-InterfaceX

–

ChassisY-InterfaceY

Page 49

2-11

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Object States

All Cisco Catalyst Switch Manager objects have states associated with them. Each state corresponds to a specific task that is performed in that state. For example, in the performance state, attributes are being polled at a predefined rate. State changes can be triggered by actions, or selected SNMP traps from the device. The state of an object can change frequently, depending upon what actions are being performed on the object. All objects in Cisco EMF have a state assigned to them, which appears at the bottom left corner of each window for a selected object.

Object states reflect the life cycle of an object. Whatever stage the object is in at any given time displays in the state type. The state of an object can change frequently, depending upon what actions take place on the object. All objects within the EM are in a specific state which appears at the bottom left corner of each FCAPS window. The following figure highlights an object’s state.

Figure 2-4 EM Object States

The two most common object states are Normal and Decommissioned. Some states are inherited by an object’s children. For example, if a chassis is decommissioned, all subchassis objects are also decommissioned. If performance logging is enabled on a module, performance lo gging is enabled on all ports of that module.

The following sections describe the possible states that an object may be in and provides a description of these states.

Decommissioned State

The decommissioned state indicates that an object is not being managed. When an object is initially deployed, it is normally placed into a decommissioned state. The following actions occur on a decommissioned object:

• Active management stops

• All subobjects also are decommissioned

Decommission buttons can be found within certain windo ws, dependent upon the type of object select ed. When an object is decommissioned, the children of that object also change their state to decommissioned. For example, if a module is decommissioned, all interfaces and connections on that module are decommissioned.

Objects can be put into the decommissioned state from any other state.

Page 50

2-12

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Object States

Discovery State

The discovery state is a temporary state that is assigned to certain objects during subchassis discovery. This state applies to the Network Element, Chassis and Software objects. It is used to determine the

physical and logical components on a switch. If successful, an automatic state transition to normal is made. If communication is lost, the object transitions to the discovery lostcomms state. If physical components are detected that do not match the expected types, the objects are transitioned to the mismatched state.

Normal State

The normal state is applicable to all objects, and represents a situation in which an object is regarded as being actively monitored. When an object enters the normal stat e, Cisco EMF performs heartbeat polling on the object every five minutes to check for connectivity or changes to the object.

Lostcomms State

This state applies only to the Network Element object. If communi cation to the Netw ork Element object is lost, it moves into the lostcomms state. Heartbeat polling polls an object every five minutes to verify its existence and current state. Heartbeat polling continues, until the object responds positively to a heartbeat request. When the object can be contacted again, it responds positively to heartbeat requests, and then moves back into the normal state.

Normal Lostcomms State

This state applies all objects except the Netwo rk Element object. This state indicates that communication has been lost to an object that was formerly in the normal state. Two transitions can be made out of this state:

• If communication is restored, the object transitions back to the normal state.

• While this object is still in the normal lostcomms state, if the object is stimulated to activate

performance logging, then the transition is immediately to the perflostcomms state.

Page 51

2-13

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Object States

Performance State

This state applies all physical objects that support Performance Logging. When you enable performance logging on an object in the normal state, the object is moved into the performance state. Specific performance data is collected on the object and can be viewed in the Performance Manager. You can enable performance logging on a global scale or on an individual interface basis. Enabling global performance logging puts all subchassis objects into the performance state.

Performance logging occurs at the specif ied in terval. When you initially enable performance logging or global performance logging on an object, it takes a period of time u p to the leng th of the i nterval for the data to be collected and become visible in Cisco Catal yst Switch Ma nager p erformance menus.

Heartbeat polling is performed on an object in the performance state. If the object moves into the lostcomms state, it is returned to the performance state when the error is corrected. For example, if a module is in the performance state and it fails, it mo ves into t he lostcomms state. When heart beat polling finds the module is back up, it restores the module to the performance state.

There are three transitions out of the performance state:

• If communication to the object is lost while the object is in the performan ce state, the state transition

is into the perflostcomms state.

• To turn off the object’s performance logging, you can send the object the normal stimulus. The

transition is to the normal state.

• If heartbeat polling determines that connectivity is lost or chan ges hav e been made to the object, the

transition is to the discovery state. Once discovery is completed successfully, the object transitions back to the performance state.

Perflostcomms State

This state applies all physical objects that support Performance Logging. This state indicates that communication has been lost to an object that was formerly in the performance state. Two transitions can be made out of this state:

• If communication is restored, the object transitions back to the performance state.

• While this object is still in the perflostcomms state, if the object is stimulated to deactivate

performance logging, then the transition is immediately to the normal lostcomms state.

If communication to an object is lost, it moves into the lostcomms state. In this state, performance polling (if activated) is stopped; however, heartbeat polling continues, until the object responds positively to a heartbeat request. Heartbeat polling polls an object every five minutes to verify its existence and current state. When the object can be contacted again, it responds positively to heartbeat requests, and then moves back into the previously held state.

Discovery Lostcomms State

The discovery lostcomms state applies to Network Element, Software and Chassis objects. This state is similar to the lostcomms state, except that it only occurs during the discovery process. When connectivity is established with the corresponding object in the de vice, the disco v ery is resumed and the object moves out of the discovery lostcomms state.

Page 52

2-14

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 2 Basic Concepts

Cisco Catalyst Switch Manager Object States

Mismatched State

The mismatched state occurs when a mismatch is found between the type of hardware discovered and what is predeployed in Cisco EMF. For example, if a 48-port 10/100TX, RJ-45 module is expected, the module is predeployed in Cisco EMF to prepare for that type of module. However, when the module becomes available and is placed into the chassis, it is not a 48-port 10/100TX, RJ-45 module, but an 8-port Gigabit Ethernet module. After the Cisco Catalyst Switch Manager detects the new module, it finds a mismatch. The module gets placed into the mismatched state and an alarm is raised against the module.

To correct a mismatch problem, the source of the problem must be assessed. If the operator was at fault and predeployed an incorrect module, the operator sh ould delete the predepl oyed module and deplo y the correct module. If the engineer is at fault and inserted the wrong type of module into the chassis, then the module should be removed and replaced.

The mismatched state applies to the following objects:

• Network element

• All modules

• Port Adapters

• Channelized SONET subinterfaces

For the Network Element object, the mismatched state indicates that there is a major difference between the Cisco EMF informatio n and the a ctual Ca talyst switch. This mismatch can be in the major switch series (e.g., 6000, 6500), the specific model of the switch (e.g., 6506, 6509 or 6513) or the type of software installation on the switch (Catalyst OS, Hybrid OS or Native IOS).

Page 53

CHA P T E R

3-1

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Getting Started

This chapter describes the typical tasks encountered when you are first using the Cisco Catalyst Switch Manager. This chapter consists of the following sections:

• Preparing to Use the Cisco Catalyst Switch Manager Software

• Launching Cisco EMF

• Cisco EMF Launchpad

• Quitting a Cisco EMF User Session

Page 54

3-2

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Preparing to Use the Cisco Catalyst Switch Manager Software

The following procedure outlines the general steps involv ed in using the Cisco Catalyst Switch Manager software.

Step 1 Install and start Cisco EMF.

Note For more information on how to install and start Cisco EMF, see the Cisco Element Management

Framework Installation and Administration Guide.

Step 2 Install the Cisco Catalyst Switch Manager software.

Note For more information on how to install the Cisco Catalyst Switch Manager, see the Cisco

Catalyst Switch Manager Installation Guide.

Step 3 Set up the Catalyst switch.

You must configure the C atalyst sw itch to su pport SNMP management before it can be properly managed by Cisco EMF.

Note For more information on configuring the switch, see the “Software Configuration

Requirements” section in the Cisco Catalyst Switch Manager Installation Guide.

Step 4 Start a Cisco EMF session.

Starting a Cisco EMF user session provides access to all Cisco Catalyst Switch Manager functionality. For more information, see the “Launching Cisco EMF” section on page 3-3.

Step 5 Deploy objects.

For more information, see the appropriate deployment section in Chapter 4, “Deploying the Cisco

Catalyst Switch Manager.”

Step 6 Configure and monitor managed objects using object management windows as necessary.

For more information, see the “Working With Object Manage ment Windows” section in Chapter 4,

“Deploying the Cisco Catalyst Switch Manager.”

Page 55

3-3

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Launching Cisco EMF

The Cisco EMF Launchpad application is the main starting point for using Cisco EMF. The Launchpad can be accessed by starting a Cisco EMF user session. Before you can start a Cisco EMF user session, Cisco EMF has to be running. If a message is displayed indicating that Cisco EMF is not running, contact the system administrator.

To start a Cisco EMF user session, do the following:

Step 1 From the command line on the terminal window, type the following:

Cisco EMF_ROOT/bin/Cisco EMF session

Note Replace Cisco EMF_ROOT with the root directory in which Cisco EMF is installed (for example,

/opt/Cisco EMF).

The login window appears as follows.

Figure 3-1 Login Window

Step 2

Enter your user name and password, then click Ok to proceed. When an invalid user name or password is entered, an error is displayed. Click Ok and then enter a valid

user name and password. Three attempts to enter a valid user name and passw or d ar e allowed. If a valid user name and password are not entere d within three attemp ts, the lo gin window closes.

When a valid user name and the password are entered, the session starts and the Cisco EMF Launchpad window appears (see Figure 3-2).

Page 56

3-4

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Cisco EMF Launchpad

The icons which display in the Cisco EMF Manager and Event Manager areas of the Launchpad represent the applications the Cisco EMF installation provides. The follow ing figure displays the Cisco EMF Launchpad and the icons which represent the standard Cisco EMF tools.

Figure 3-2 Cisco EMF Launchpad

Note Additional icons may appear on the Launchpad following some package installations.

The following paragraphs describe each of these tools. For more detailed information on these applications, refer to the Cisco Element Management Framework User Guide.

Event Grps icon - Launches Event Groups Application

PreFilter icon - Launches Pre Filtering Application

Notify icon - Launches Notification Profile Application

Thresholds icon - Launches Thresholding Regimes Application

80864

Viewer icon - Launches MapViewer

Groups icon - Launches the Object Group Manager

Access icon - Launches Access Manager

Events icon - Launches the Query Editor and Event Browser

Discovery icon - Launches Auto Discovery

Page 57

3-5

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Cisco EMF Launchpad

Viewer

The Viewer icon provides access to the Cisco EM F Map Viewer application, which provides complete flexibility in viewing, building, and monitoring a network using graphical representations of Network Elements. The Map Vie wer application is the primary access point for C65/76M management functions.

Groups

The Groups icon provides access to the Cisco EMF Object Group Manager application, which pro vides the opportunity to organize N etwork Elements into obj ect groups. The Object Group Manager allo ws the creation, deletion, and modification of object groups. Object groups can be any combination of objects derived from the Cisco EMF managed object class. Objects can be added manually or on the basis of query criteria.

Access

The Access icon provides access to the Cisco EMF User Access Control application, which is a component of Carrier Class Security and provides system administrators the opportunity to control which features of their system can be accessed by various levels of personnel. This is important for security and efficient and effective network management.

Events

The Events icon provides access to the Event Browser application. In Cisco EMF, when a condition (fault) occurs on a managed object in the network, the system is notified immediately. This notification is shown as an event and can be viewed with the Event Browser. One of the mo st importan t aspects of network service management is the ability to identify events on the system and to take action to resolve them quickly and efficiently. For example, there may be a power supply fault in a chassis which would require an engineer to be sent out to rectify the fault. This fault is critical to the running of the network and would need prompt attention.

Discovery

The Discovery icon provides access to the Cisco EMF Auto Discovery application, which examines the network for IP and SNMP devices and creates a managed object for each new device discovered. Auto Discovery can be opened from the Cisco EMF Launchpad window or from a pop-up menu available on a selected object.

Notify

The Notify icon provides access to the Notification feature. An important aspect of a monitoring system which captures and reacts to events on the network is when and how a network operator is informed of these events. The Cisco EMF Event Manager uses notifications for providing this information. For example, when the temperature of a module rises 10 degrees above normal, an e-mail might be sent to the network operator warning of a potential problem and a minor event might be generated if the temperature does not fall to within 10 degrees of normal within twenty minutes.

Page 58

3-6

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Cisco EMF Launchpad

Notification profiles ar e collections of notificatio ns. Each notification p rofile has a name and description and can be accessed by all Event Manager users. Each profile includes a list of notifications, and is run following a trigger, which might be an event entering an event group, or a threshold breach in a thresholding regime. For example, when the first event is received by an event group, a notification profile may be triggered that caus es a sound to occur , which alerts the operator . As well as audible alerts, a notification can be set up to display on screen, or to trigger an external notification, such as an e-mail.

Thresholds

The Thresholds icon provides access to the Thresholding Regime feature. A Thresholding Regime is a set of threshold conditions for specified object attributes which, when breached, causes one or more notification profiles to be run. The Thresholding Regime defines which attributes should be polled and on what period, and defines the thresholding conditions. The Thresholding Regime specifies object groups that contain the objects whose attributes will be polled.

Event Grps

The Event Grps icon provides access to the Event Groups application, which is used to organize Network Elements into event groups and to vie w the status of these groups as scoreboards. You can create, delete, and modify event groups and scoreboards. Event groups are available to all users.

Event groups can be any combination of objects derived from the Cisco EMF-managed object class. These groups are set up using queries, which can be configured to match given requirements. For example, a network administrator could choose to monitor a particular de vice, specify a time period, and choose to look at events that are warnings or critical. You define a query so that the event group only includes the events that meet the specified criteria.

PreFilter

Filtering events at the point at which they enter the system is known as pre-filtering. When specified pre-filtering criteria is met, events are not available to the EMS. Filtering certain events prevents unnecessary data from being written to the database, improving overall system performance. The Pre Filtering application opens from the Cisco EMF La unchpad.

Event filtering is also a v ai lable in the Ev ent Bro wser an d Even t Group ap plications to d etermines which alarms display to a certain user or participate in a event group.

Page 59

3-7

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Quitting a Cisco EMF User Session

To quit a Cisco EMF user session, follow these steps:

Step 1 In the Launchpad window, do one of the following:

• Click the Quit icon from the tool bar.

• From the File menu, choose Quit.

• Press Ctrl-Q.

A window appears, asking, Do you wish to quit the Cisco EMF Manager System?

Step 2 Click Yes to quit the session. All active applications are closed and the session terminates.

Page 60

3-8

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 3 Getting Started

Quitting a Cisco EMF User Session

Page 61

CHA P T E R

4-1

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Deploying the Cisco Catalyst Switch Manager

This chapter describes how to deplo y objects wit hin the Cisco Catalyst Switch Manager, and consists of the following primary sections:

• Deploying and Commissioning Process Overview

• Deploying Existing Network Objects Using IP Auto Discovery

• Manually Deploying Network Objects

• Predeploying Anticipated Network Objects

• Enabling Communication Between Network Elements and Devices

• Manually Commissioning Network Elements

Deploying and commissioning a Catalyst switch using Cisco EMF is a two-step process:

1. Deploy objects that need to be managed. Cisco Catalyst Switch Manager object s can be depl oyed

manually or discovered automatically.

2. Commission the objects, allowing Cisco EMF to manage them.

The deployment process should be done after you install the Cisco Catalyst Switch Manager software for the first time, or after you install new hardware. Deployment informs the Cisco Catalyst Switch Manager of the presence of supported hardware.

The Cisco Catalyst Switch Manager objects can be automatically discovered or manually deployed. Objects can also be predeployed in Cisco EMF before the actual installation of a Catalyst switch in the field.

Predeployment is the process of reserving a space in Cisco EMF for network equipme nt, wh ich has not yet been physically slotted into the system rack. When an object or device is predeployed, the physical device or object is not present, but Cisco EMF has been preco nfigured to hold an object of similar type. As a result, Cisco Catalyst Switch Manager module objects can be deployed and the Cisco Catalyst Switch Manager will not monitor their status. When a module is then placed in the physical equ ipment, the new module will be automatically detected and management of the module will be automatically started.

A fully deployed Cisco Catalyst Switch Ma nager object in Cisco EMF has the following object hierarchy:

Page 62

4-2

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Container (Site, Bay, etc.)

Network Element

Chassis Power Supplies Supervisor Modules Ethernet Interfaces Ethernet Modules Ethernet Interfaces Switch Fabric Modules FlexWAN Modules Port Adapter ATM Port Adapter ATM SONET Interfaces ATM E3 Interfaces ATM T3 Interfaces OSM GeWAN Modules OSM GeWAN Interfaces OSM PoS Modules Ethernet Interfaces OSM PoS Interfaces OSM Channelized SONET Modules Ethernet Interfaces OSM Channelized SONET Interfaces OSM Serial Sub-interfaces OSM PoS Sub-interfaces Content Switching Modules Software EtherChannels Syslog EIGRP BGP OSPF VTP VLANS VLAN_1-205 VLAN-1 VLAN-2 VLAN-3... VLAN_206-410 VLAN-206 VLAN-207 VLAN-208... VLAN_411-615... VLAN-411 VLAN-412 VLAN-413... STP IS-IS ACL NDE Loopback QoS QoS Policy Map

The top-level Network Element object represents the entire swit ch inclu ding the physical and logical components of the switch. The Chassis object, which is a child of the Network Element object, represents all the physical components of the switch. For example, the chassis frame, power supplies, modules, and ports are all represented under the Chassis object. The Software object, which is a peer of the Chassis object, represents all the logical components of the switch. For example, VLAN configurations, EtherChannels, and routing protocols are represented under the Software object.

Page 63

4-3

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Due to the large number of possible VLAN objects available to a Network Element, the VLANS container may be configured to group VLANs into subsets. These groupings improve system performance during subchassis discovery. By default, VLAN container objects exist as depicted in the previous listing, however, VLAN object configuration may be altered by editing the C6576MCntrllUserData.ini file. Under the VLAN Group area of the file, you may modify the Objects per Group value (default v alue is 20 5) and you may decrease the Maximum VLANs entry (def ault v alue is 4096). The maximum value may not be increased above 4096.

Commissioning is the process that notifies Cisco EMF to begin actively monitoring an object. The following Cisco Catalyst Switch Manager objects can be commissioned and decommissioned by the user:

• Network Element

• Supervisor Module

• Ethernet Module

• Switch Fabric Module

• FlexWAN Module

• Content Switching Module

• Port Adapter

• OSM Module

When applied to these objects, the commissioning process is propagated down to all the object’s children. For example, if the Network Element object is commissioned, all the Cisco Catalyst Switch Manager objects are also commissioned. If only a Supervisor Module object is commissioned, then its Ethernet Interface objects are also commissioned.

When the Network Element object is commissioned, a subchassis discovery is started to determine the contents of the switch. The subchassis discovery task is executed during commissi oning . The discovery task does the following:

• Verifies the predeployed objects.

• If a mismatch between a predeployed object and the discovered object exists, then the predeployed

object is placed in a Mismatched state. For example, if a Supervisor Engine 2 MSFC2 is predeplo yed but a Supervisor Engine 1A MSFC2 is discovered, the Supervisor Module object will be placed in a Mismatched state. If the wrong object was predeployed, delete the object and recommission the Network Element. If the wrong module w as inserted in the switch or router , insert the correct module and recommission the object.

• Checks for switch components that were not predeployed. Any objects that are discovered will be

created and commissioned automatically.

• Automatically creates and commissions the remaining Cisco Catalyst Switch Manager objects.

These objects include the power supply and all of the logical objects.

If objects on the switch are discovered that do not currently exist in Cisco EMF, then these objects are automatically created and populated. For example, an Ethernet module would be automatically populated with the appropriate number of interfaces when it is discovered. If the object already exists in Cisco EMF , then a type match is made against the Cisco EMF object and the one fou nd during discov ery . If a mismatch is found, the object is placed into the Mismatched state and an error is generated. If there is no mismatch, then the object is commissioned successfully and Cisco EMF begins to monitor it.

Page 64

4-4

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

The following figure shows the Cisco EMF Map Viewer application with the Cisco Catalyst Switch Manager software installed. When an object is deployed in Cisco EMF, the objects are automatically added to the Network, Physical, and the appropriate Manager Views. In this example, the Network Element objects are called “may” and “morar,” the Chassis objects are called “may-Chassis” and “morar-Chassis,” and the Software objects are called “may-Software” and “morar-Software.”

Under the Network container, the Network Element objects are labelled by their IP addresses and added to the group representing the subnet that they belong to (192.168.12.0). Under the Physical container, the Network Element and Chassis objects are available.

Figure 4-1 Hierarchical Structure of Deployed and Commissioned Objects

Page 65

4-5

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Deploying and Commissioning Process Overview

There are three methods that enable Cisco EMF to monitor a Catalyst switch:

• IP Auto Discovery

Use this method to deploy a large number o f devices that are currently connected to the network. This method automatically deploys the Network Element and Software objects for each Catalyst switch discovered.

For detailed information, se e the “Deploying Existing Network Objects Using IP Auto Discovery”

section on page 4-6.

• Manual Deployment

Use this method if a small number of devices that are connected to the network need to b e deployed. This method deploys the Network Element and Software objects for the Catalyst switch specified.

For detailed information, see the “M anuall y Deploying N etwork Objects” se ction on page 4- 9.

• Predeployment

Use this method to predeploy a device that is not connected to the network. The following objects can be predeployed:

–

Network Element and Software

–

Chassis

–

Supervisor Modules

–

Ethernet Modules

–

Switch Fabric Modules

–

FlexWAN Modules

–

Port Adapters

–

OSM Modules

For detailed information, see the “Predeploying Anticipated Network Objects” section on

page 4-15.

The remaining Cisco Catalyst Switch Manager objects are automatically discovered when the Network Element object is commissioned.

Page 66

4-6

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Deploying Existing Network Objects Using IP Auto Discovery

The Cisco EMF Auto Discovery application is used to search a n existing network . The network is examined for IP and SNMP devices. An object is created for each ne w device discovered. The Discover Network Devices window is used to perform IP Auto Discovery.

To deploy objects using IP auto discovery, perform the following:

Step 1 Launch the Discover Network Devices window by completing one of the following:

• From the Cisco EMF Launchpad (Figure 3-2), click the Discovery icon.

• From the MapV iewer application, right–click an object and choose Deployment/Auto Discovery...

When first launched, the IP Discovery window resembles the following example:

Figure 4-2 IP Discovery Window

The contents of this window depend on ho w the windo w w as launched. For example, if this windo w w as launched from an object in the Physical containment view, then the Physical Location parameter would be automatically set to the location from which the window was launched, as shown in the preceding figure.

Page 67

4-7

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Deploying Existing Network Objects Using IP Auto Discovery

Step 2 Provide the required information in the displayed fields.

For more information on the Cisco EMF Auto Discovery process, see the “Auto Discovery” chapter of the Cisco Element Management Framework User Guide.

Note When specifying the SNMP community string, use the read-write community string for the switch. If the

read community string is used or appears first in the list of community strings, then that will be the SNMP community string used for both the read and read-write operations by the Cisco Catalyst Switch Manager. As a result, set operations will fail.

After the discovery process is complete, newly discovered objects will be automatically added to the Network and Physical view containers within the Map Viewer application. In the Network view container, the object will be placed under the appropriate subnet. In the Physical view container, discovered objects will be placed in the location based on the value of the Physical Location parameter.

If one of the discovered devices is a Catalyst switch, then a Cisco Catalyst Switch Manager Network Element object will also be added into the Network containers, Physical containers, and the appropriate Manager Views. The Software object is also automatically added to the Manager View. In the fo llowing figure, the Network Element object is labelled “192.168.12.105” and the Software object is labelled “192.168.12.105-Software.”

Figure 4-3 Map Viewer with a Newly Discovered Catalyst Switch

Page 68

4-8

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Deploying Existing Network Objects Using IP Auto Discovery

After the Network Element and Softw are objects ha v e been created by the Auto Discov ery process, their contents need to be determined. This determination is made by commissioning the Network Element object. When the Network Element object is commissioned, it executes a subchassis discovery process that communicates with the switch to automatically determine the contents of the switch.

However, before the Network Element object can be commissioned, additional parameters are required. Specifically, the Telnet and Enable passwords and the SNMP communities are required. These values are established on the Network Eleme nt Managem ent win dow.

For further information on setting these parameters and commissioning the Network Element, see the following sections:

• Enabling Communication Between Network Elements and Devices, page 4-22

• Manually Commissioning Network Elements, page 4-25

Page 69

4-9

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

The manual deployment method is used when discovery of the entire network is not needed and the specific device IP address known. Using manual deployment, you may elect to:

• Automatically commission the deployed switch object within the EMS immediately following

deployment (i.e., the device is connected to the network)

• Deploy the switch object as decommissioned and commission at a later time

• Predeploy the switch object and configure the EMS to automatically commission the switch object

when the device becomes available on the network

Manual deployment is achieved using a wizard. A wizard is simply a series of screens that prompt you for specific data. Depending on the circumstances under which you are performing manual deployment the wizard may vary. Possible variations include:

• Manually Deploying from a Site Object

• Manually Deploying from a Network Element Object

• Manually Deploying Using Quickstart

The following sections describe these deployment wizards.

Manually Deploying from a Site Object

To manually deploy a Catalyst switch from a generic Site object, perform the following:

Step 1 Right-click a generic container object and choose Deployment > CSM/7600 Manager, then choo se one

of the following options:

• Deploy Catalyst 6000 Chassis

• Deploy Catalyst 6500 Chassis

• Deploy Cisco 2950 Chassis

• Deploy Cisco 2970 Chassis

• Deploy Cisco 3550 Chassis

• Deploy Cisco 4000 Chassis

• Deploy Cisco 4500 Chassis

Note The Quickstart manual chassis deployment options available on the Deployment > CCSM

submenu are described in detail in the “Manually Deploying Using Quickstart” section on

page 4-13.

The Deployment Wizard appears, displaying the Deployment Wizard—Templates window. Depending on the Catalyst switch family selected in Step 1 the Deployment W izard—T emplates window

displays different options. The following deployment templates display in the Deployment Wizard—Templates window when the Catalyst 6000 or 6500 chassis deployment option is selected:

• Network Element with IOS instal led (Aut o–disc over Chassis)

• Network Element with IOS installed (Specific Chassis)

• Network Element with IOS/CatOS installed (Auto–discover Chassis)

Page 70

4-10

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

• Network Element with IOS/CatOS installed (Specific Chassis)

• Network Element with CatOS installed (Auto–discover Chassis)

• Network Element with CatOS installed (Specific Chassis)

The following deployment templates display in the De ployment Wizard—Templates window when the Catalyst 2950, 3550, 4000 or 4500 chassis deployment option is selected:

• Network Element (Auto–discover Chassis)

• Network Element (Specific Chassis)

Deployment templates are available for the following types of deployment:

• Auto–discover Chassis—Deploys the Network Element and Software objects within the EMS and

automatically commissions these objects to automatically populate the Network Element object through chassis and subchassis discovery. The discovery process creates objects representing the Chassis and all subchassis elements within the physical switch at the time of discovery.

• Specific Chassis—Deploys the Network Element, Chassis, and Software objects. Used when you

want to perform predeployment operations.

Tip The Specific Chassis option is most commonly used when predeploying network elements. For further

information on predeploying objects, refer to Predeploying Anticipated Network Objects.

Furthermore, deploying a Catalyst 6000 or 6500 chassis through the Deployment Wizard templates provides templates appropriate to the type of software installed on the switch itself:

• IOS—Native IOS–based switch

• IOS/CatOs—Hybrid–based switch where both Native IOS and Catalyst IOS software is utilized

• CatOs—Catalyst IOS–based swit ch

Step 2 Choose the appropriate deployment template option from the list and click Forward.

The Deployment Wizard—Object Parameters window (1) appears. You can deploy multiple switches at a time using the same deployment template. If you opt to deploy more than one switch, the Deployment W izard disp lays each of the resulting screens

for each switch to be deployed.

Step 3 Enter the number of switches that you want to deploy using this templ ate in the provided f ield, then click

Forward. The Deployment Wizard—Object Parameters window (2) appears. Depending on the deployment

template selected in Step 2, the fields on the Deployment Wizard—Object Parameters window (2) vary.

Step 4 Provide data in the Object Parameter fields as applicable per the following descriptions.

• Catalyst Switch Name—Name of the Network Element object to be disp layed in t he Map Viewer

application

• Supervisor IP Address—IP address of the switch

• SNMP V2c Read Community—SNMP v1 read community used by the device

• SNMP V2c Write Community—SNMP v1 write community used by the device

Page 71

4-11

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

Note The SNMP V2c Read and Write Community field labels contain a prefix appropriate to the

deployment template selected in Step 2, IOS or CatOS. Multiple SNMP V2c Read and Write Community fields appear if a Hybrid deployment template was selected in Step 2, IOS and CatOS.

If using a Hybrid deployment template, you must click Forward after providing the SNMP V2c Rea d and Write Community fields. Another Deployment Wizard—Object Parameters (3) window appears with the following fields. Provide inputs accordingly, then click Forward.

• Username—Username ID login for the device

• Password—Corresponding password to the device for the username entered

• EXEC Password—Executive password to the device

Note The Username, Password, and EXEC Password field labels will contain a prefix appropriate to

the deployment template selected in Step 2, IOS or CatOS. Multiple Username, Password, and EXEC Password fiel ds display i f a Hybrid depl oyment template w as selected in Step 2, IOS and CatOS.

Note The Network Element object can be deployed and commissioned without the P assword or EXEC

passwords being set. However, some of the attributes within the EMS will display a value of “ERROR” because these values are retrieved using IOS and/or Catalyst IOS commands.

• Deployment Commissioning Mode—Determines the commissioning action to be taken upon

deployment. Available options are as follows:

–

Decommissioned—Deploys the Chassis object in the decommissioned state (i.e., not commissioned).

–

Commission—Deploys the Chassis object in the commissions state.

–

Auto Commission—Predeploys the Chassis object in the decommissioned state. Upon contact with the device, commissioning automatically begins (i.e., chassis and subchassis discovery initiates).

Step 5 Click Forward.

The Deployment—Wizard Summary window appears. The number of objects to be deployed consists of user selected and automatically added objects. For each

user selected object (i.e., the number of switch Network Element objects entered in Step 3), there are two automatically added objects, one generic Network Element object and one Software object. These variables directly correlate to the number of objects listed in the deployment summary information.

Step 6 Click Finish to deploy the chassis and close the Deployment Wizard—Summary window if the

deployment summary information is correct. If the Deployment Wizard—Summary information is incorrect, click Cancel to stop deployment and close the Deployment Wizard—Summary window.

The Deployment Wi zard—Summary windo w closes and a Report displays indicating the outcome of the deployment.

Page 72

4-12

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

The deployed Network Element object(s) appear in the left-hand pane of the Map Viewer beneath the generic object from which deployment was initiated and the corresponding icon(s) appear in the right-hand pane of the Map Viewer. The Software and Chassis objects appear beneath the Network Element object in the left-hand pane of the Map Viewer and the corresponding icon(s) appear in the right-hand pane of the Map Viewer.

If you opted to commission the Network Element as part of deployment through t he selected Deployment Commissioning Mode (as described in Step 4), the Network Element objects commissio n and subchassis discovery initiates thereby communicating the switch inventory (or contents of the device) to the EMS. Following subchassis discovery, subchassis objects appear beneath the Chassis obje ct in th e left-han d pane of the Map V ie wer and the corresp onding icon(s) appear in the right-hand pane of the Map Viewer. Additionally, when selected the Chassis object is selected in the left-hand pane of the Map Viewer, the chassis map appears in the right-hand pane of the Map Viewer.

If you opted to deploy the Network El ement b y selecting t he Decommission ed option fro m Deplo yment Commissioning Mode as described in Step 4, the objects deploy in an unmanaged state (e.g., decommissioned). At any time following successful chassis deployment, you may initiate chassis and subchassis discovery by commissioning the chassis. Until you do so, the chassis remains in an unmanaged state (e.g., decommissioned). For further information, see the “Manually Commissioning

Network Elements” section on page 4-25.

If you opted to predeploy the Network Element as an Auto–commissioned object from the Deployment Commissioning Mode field as described in Step 4, the objects deploy in an unmanaged state (e.g., decommissioned). Once the predeployed Network Element is available on the network, the chassis object automatically commission s and init iates subch assis di scovery. Objects appear within the Map View er as previously described.

Manually Deploying from a Network Element Object

Manual deployment from a Network Element Object is only available on the Catalyst 6000 and 6500 family switches. Manual deployment from a Catalyst 2950, 35 50, 4000, and 4500 family switch Network Element is not currently supported by the EMS.

T o manually depl oy a Catalyst swit ch from a previously deployed Network Element object, perform the following:

Step 1 Right-click a Network Element object and choose Deployment > Deploy Chassis.

The Deployment Wizard Object Parameters window appears.

Step 2 Enter data in the displayed Object Parameter fields as applicable per the following descriptions.

• Catalyst Switch Name—Name of the Network Element object to be disp layed in t he Map Viewer

application

• Chassis Type—Indicates the type of device that you want to deploy. Depending on the Network

Element type from which the Deployment Wizard was initiated, the possible options vary. For a Catalyst 6000 family switch options are as follows:

–

wsc6006

–

wsc6009

For a Catalyst 6500 family switch options are as follows:

–

wsc6506

–

wsc6509

Page 73

4-13

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

–

wsc6509NEB

–

wsc6513

Step 3 Click Forward.

The Deployment W izard—Summary windo w closes and the deployed Netw ork Element object(s) appear in the left-hand pane of the Map Viewer beneath the generic object from which deployment was init iated and the corresponding icon(s) appear in the right-hand pane of the Map Viewer. The Software and Chassis objects appear beneath the Network Element object in the left-hand pane of the Map Viewer and the corresponding icon(s) appear in the right-hand pane of the Map Viewer.

Following manual deployment via a Network Element object you must manually configure the SNMP write and read communities and device password through the EM, then commission the object to discover the chassis and subchassis objects.

For detailed instructions on perf orming these tasks, see the “Enabling Communication Between Network

Elements and Devices” section on page 4-22 and the “Manually Commissioning Network Elements” section on page 4-25.

Manually Deploying Using Quickstart

The Quickstart manual deployment method is used when discovery of the entire network is not needed and the specific IP address and type of de vice that is conn ected to the netw ork is k no wn. Th e Quickstart option deploys the Network Element, Chassis, and Software objects, then discovers the device and performs subchassis discovery automatically following deployment in order to determine the contents of the swtich.

To manually deploy a Catalyst switch using Quickstart, perform the following:

Step 1 Right-click a generic container object and choose Deployment > CSM/7600 Manager, then choo se one

of the following options:

• Quickstart Deploy Catalyst 6000 Ch assis

• Quickstart Deploy Catalyst 6500 Ch assis

• Quickstart Deploy Cisco 2950 Chassis

• Quickstart Deploy Cisco 2970 Chassis

• Quickstart Deploy Cisco 3550 Chassis

• Quickstart Deploy Cisco 4000 Chassis

• Quickstart Deploy Cisco 4500 Chassis

Note The manual chassis deployment options other than Quickstart that are available on the

Deployment > CSM/7600 Manager submenu are described in detail in the “Manually Deploying

Network Objects” section on page 4-9.

The Deployment Wizard—Object Parameters window appears.

Step 2 Provide data in the Object Parameter fields as applicable per the following descriptions.

• Catalyst Switch Name—Name of the Network Element object to be disp layed in t he Map Viewer

application

Page 74

4-14

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Deploying Network Objects

• Supervisor IP Address—IP address of the switch

• SNMP V2c Read Community—SNMP v2c read community used by the device

• SNMP V2c Write Community—SNMP v2c write community used by the device

• Username—Username ID login for the device

• Password—Corresponding password to the device for the username entered

• EXEC Password—Executive password to the device

Note The Username, Password, and EXEC Password field labels will contain a prefix appropriate to

the switch selected in Step 1, CatOS/IOS or IOS.

Note The Network Element object can be deployed and commissioned without the P assword or EXEC

passwords being set. However, some of the attributes within the EMS will display a value of “ERROR” because these values are retrieved using IOS and/or Catalyst OS commands.

• OS Deployment Mode—Determines the operating system of the Catalyst 6000 or 65 00 switch to be

deployed. Available options are as follows:

–

Auto Detect—The EMS will automatically determine the appropriate deployment template by contacting the device to determine the supported operating system: Native IOS, Catalyst OS, or Hybrid.

–

Catalyst OS—Deploys the object per the Catalyst OS template.

–

Hybrid—Deploys the object per the Native IOS/Catalyst OS template.

–

Native IOS—Deploys the object per the Native IOS template.

Step 3 Click Forward.

The Deployment—Wizard Summary window appears. The number of objects to be deployed consists of user selected and automatically added objects. The

number of objects listed in the deployment summary information account for one Chassi s object and two automatically added objects, one generic Network Element object and one Software object.

Step 4 Click Finish to deploy the chassis and close the Deployment Wizard—Summary window if the

deployment summary information is correct. If the Deployment Wizard—Summary information is incorrect, click Cancel to stop deployment and close the Deployment Wizard—Summary window.

The Deployment Wizard—Summary window closes and the deployed Network Element object appears in the left-hand pane of the Map V ie wer beneath the generic object from w hich deployment wa s initiated and the corresponding icon(s) appear in the right-hand pane of the Map Viewer. The Software and Chassis objects appear beneath the Network Element object in the left-hand pane of the Map Viewer and the corresponding icon(s) appear in the right-hand pane of the Map Viewer.

Page 75

4-15

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

The predeployment option is used to deploy a Catalyst switch into Cisco EMF before it has been attached to the network. After an object has been predeployed, Cisco EMF keeps the object in a decommissioned state until the device corresponding to the object is added to the network. After the switch is brought on-line, the predeployed object can be configured to automatically commission. The following objects can be predeployed:

• Network Element, Software and Chassis

• Supervisor Modules

• Ethernet Modules

• Switch Fabric Modules

• FlexWAN Modules

• Port Adapter

• Content Switching Module

• EtherChannel Modules

The remaining Cisco Catalyst Switch Manager objects are automatically discovered when you commission the Network Element object.

Predeploying Network Element, Software, and Chassis Objects

To manually predeploy the Network Element, Software, and Chassis Cisco Catalyst Switch Manager objects from various objects within the object hierarchy, proceed as follows.

If deploying from a generic Site container object, perform the following steps:

Step 1 Right-click a generic Site container object, then choose Deployment > CSM/7600 Manager, then

choose one of the following options:

–

Deploy Catalyst 6000 Chassis

–

Deploy Catalyst 6500 Chassis

–

Deploy Cisco 2950 Chassis

–

Deploy Cisco 2970 Chassis

–

Deploy Cisco 3550 Chassis

–

Deploy Cisco 4000 Chassis

–

Deploy Cisco 4500 Chassis The Deployment Wizard appears, displaying the Deployment Wizard—Templates window. Depending on the Catalyst switch family selected in Step 1, the Deployment Wizard—Templates

window displays different options. The following deployment templates display in the Deployment Wizard—Templates window when the Catalyst 6000 or 6500 chassis deployment option is selected:

• Network Element with IOS instal led (Aut o–disc over Chassis)

• Network Element with IOS installed (Specific Chassis)

• Network Element with IOS/CatOS installed (Auto–discover Chassis)

• Network Element with IOS/CatOS installed (Specific Chassis)

Page 76

4-16

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

• Network Element with CatOS installed (Auto–discover Chassis)

• Network Element with CatOS installed (Specific Chassis)

The following deployment templates display in the De ployment Wizard—Templates window when the Catalyst 2950, 2970, 3550, 4000 or 4500 chassis deployment option is selected:

• Network Element (Auto–discover Chassis)

• Network Element (Specific Chassis)

Deployment templates are available for the following types of deployment:

• Auto–discover Chassis—Deploys the Network Element and Software objects within the EMS and

• Specific Chassis—Deploys the Network Element, Chassis, and Software objects. Used when you

want to perform predeployment operations.

Tip The Auto–discover Chassis option is most commo nly used w hen manually depl o yin g netw ork el ements

that are available on the network. For further information on manually deploying objects, refer to the

“Manually Deploying Network Objects” section on page 4-9.

Furthermore, deploying a Catalyst 6000 or 6500 chassis through the Deployment Wizard templates provides templates appropriate to the type of software installed on the switch itself:

• IOS—Native IOS–based switch

• IOS/CatOs—Hybrid–based switch where both Native IOS and Catalyst IOS software is utilized

• CatOs—Catalyst IOS–based swit ch

Step 2 Choose the appropriate Specific Chassis deployment template option from the list, then click Forward.

The Deployment Wizard—Object Parameters window (1) appears. You may predeploy multiple switches at a time using the same deployment template. If you opt to predeploy more than one switches, the Deployment Wizard displays each of the resulting

screens for each switch to be predeployed.

Step 3 Enter the number of switches that you want to predeploy using this template in the provided field, then

click Forward. The Deployment Wizard—Object Parameters window (2) appears. Depending on the deployment

template selected in Step 2, the fields on the Deployment Wizard—Object Parameters window (2) vary.

Step 4 Provide data in the displayed Object Parameter fields as applicable per the following descriptions.

• Catalyst Switch Name—Name of the Network Element object to be disp layed in t he Map Viewer

application

• Supervisor IP Address—IP address of the switch

• SNMP V2c Read Community—SNMP v2c read community used by the device

• SNMP V2c Write Community—SNMP v2c write community used by the device

Page 77

4-17

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

Note The SNMP V2c Read and Write Community field labels will contain a prefix appropriate to t he

deployment template selected in Step 2, IOS or CatOS. Multiple SNMP V2c Read and Write Community fields display if a Hybrid deployment template was selected in Step 2, IOS and CatOS.

Note The Network Element object can be predeployed without the SNMP read/write community

strings being set.

• Username—Username ID login for the device

• Password—Corresponding password to the device for the username entered

• EXEC Password—Executive password to the device

Note The Username, Password, and EXEC Password field labels will contain a prefix appropriate to

the deployment template selected in Step 2, IOS or CatOS. Multiple Username, Password, and EXEC Password fiel ds display i f a Hybrid depl oyment template w as selected in Step 2, IOS and CatOS.

Note The Network Element object can be predeployed without the Password or EXEC passwords

being set.

Step 5 Choose the appropriate Deployment Commissioning Mode option. For predeployment, it is suggested

that you choose the Auto Commission option, b ut the Decommissioned option is an alternati ve selection. The Auto Commission parameter determines the commissioning action to be taken upon deployment.

Available options are as follows:

• Decommissioned—Deploys the Chassis object in the decommissioned state (i.e., not

commissioned).

• Commission—Deploys the Chassis object in the commissions state. This option is used when

deploying objects available on the network.

• Auto Commission—Predeploys the Chassis object in the decommissioned state. Upon contact with

the device, commissioning automatically begins (i.e., chassis and subchassis discovery initiates).

Step 6 Click Forward.

The Deployment—Wizard Summary window appears. The number of objects to be deployed consists of user selected and automatically added objects. For each

Step 7 Click Finish to deploy the chassis and close the Deployment Wizard—Summary window if the

deployment summary information is correct. If the Deployment Wizard—Summary information is incorrect, click Cancel to stop deployment and close the Deployment Wizard—Summary window.

Page 78

4-18

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

The Deployment W izard—Summary windo w closes and the deployed Netw ork Element object(s) appear in the left-hand pane of the Map V ie wer beneath the generic object from w hich deployment wa s initiated and the corresponding icon(s) appear in the right-hand pane of the Map Viewer. The Software and Chassis objects appear beneath the Network Element object in the left-hand pane of the Map Viewer and the corresponding icon(s) appear in the right-hand pane of the Map Viewer. The objects deploy in an unmanaged state (e.g., decommissioned).

Once the predeployed Network Element is available on the network, the chassis object automatically commissions and initiates subchassis discovery. Subchassis objects appear within the Map Viewer beneath the Chassis object.

Figure 4-4 Predeployed Catalyst 6509 Chassis Object

After predeploying a Network Element , you may predeploy subchassis modul es, as the following section describes.

If you predeployed the Netwo rk Element with the Auto Commission mode, upon contact with the de vice, the commissioning process automatically begins.

If you predeployed the Network Element to the Decommissioned state, you may manually initiate discovery and subchassis discovery to determine the contents of the switch. For instructions on performing this task, see the “Manually Commissioning Network Elements” section on page 4-25.

Page 79

4-19

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

Note If predeployment was performed without setting the SNMP read/write community strings and/or the

device password, you must establish these parameters prior to commissioning. For instructions, see the

“Enabling Communication Between Network Elements and Devices” section on page 4-22.

Predeploying Subchassis Modules

Following the predeployment of a Catalyst switch Network Element, you may predeploy the modules within the chassis. The following subchassis objects can be predeployed:

• Supervisor Modules

• Ethernet Modules

• Switch Fabric Modules

• FlexWAN Modules

• Port Adapters

• Optical Services Modules

• Content Switching Module

Tip Supporting modules, such as AC or DC power supplies, are automatically added through subchassis

discovery. You cannot manual ly deploy these objects.

To predeploy a subchassis module, perform the following:

Step 1 Launch the Deployment Wizard by performing one of the following:

• Right-click a chassis object, then choose Deployment. Then choose from one of the following

options:

–

Deploy Supervisor/Control Module(s)—Subchassis object predeployment templates for

Supervisor, Switch Fabric, FlexWan, and Content Switching module types.

–

Deploy Ethernet Module(s)—Subchassis object predeployment templates for standard

Ethernet, Fast Ethernet and Gigabit Ethernet module types.

–

Optical Service Module(s)—Subchassis object predeployment templates for Optical Servic e

Modules types.

• Right-click a FlexWan subchassis module object, then choose Deployment > Deploy Port

Adapter(s).

Note To predeploy a port adapter, the FlexWAN module must first be deployed

The Deployment Wizard appears, displaying the Deployment Wizard—Object Parameters (1) window.

Step 2 Enter the number of modules that you want to predeploy using this template in the provided field, then

click Forward.

Page 80

4-20

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

Note When predeploying Content Switch Modules, this value cannot be greater than 1 for IOS

12.1(8a)E3 and earlier and no greater than 11 for IOS 12.1(8a)EX and later.

Note When predeploying Port Adapter subchassis objects using the corresponding deployment

template, this value cannot be greater than 2. If it is, an error messag e wi ll be displayed and the Forward button will not work.

The Deployment Wizard—Object Parameters (2) window appears for each module to be predeploy according the entry provided in Step 2. Depending on the deployment template launched in Step 1, the fields on the Deployment Wizard—Object Parameters window (2) vary.

Step 3 Provide data in the displayed Object Parameter fields as applicable per the following descriptions.

• Name—Name given to the module

• Type—Type of module or port adapter to be predeployed. Depending on the deployment template

launched in Step 1, options are as follows:

• Chassis Slot Number—The slot in which the subchassis module is to be predeployed. This field is

not available on the Port Adapter submodule deployment template.

Note If you enter a chassis slot number that is already occupied, an error message displays and the

Forward button will not work.

• FlexWan Bay Number—The FlexWAN bay in which the port adapter is to be deployed. The port

adapter can be deployed in bays 0 and/or 1. This field is not available on the Supervisor/Control, Ethernet, or OSM module deployment templates.

Note V alid FlexWAN bay numbers are 0 or 1. If you enter any other number , an error message displays

and the Forward button will not work.

Step 4 Click Forward.

The Deployment Wizard—Summary window displays.

Step 5 Click Finish to predeploy the module and close the Deployment Wizard—Summary window if the

predeployment summary information is correct. If the Deployment Wizard—Summary information is incorrect, click Cancel to stop predeployment and close the Deployment Wizard—Summary window.

The Deployment Wi zard—Summary window closes and the deployed Module or Port Adapter object(s) appear in the left-hand pane of the Map Viewer beneath the chassis or FlexWAN object from which deployment was initiated and the correspo nding icon(s) appear in the right-hand pane of the Map V ie wer . The objects predeploy in an unmanaged state (e.g., decommissioned).

Once the predeployed Network Element, of whi ch the pr edeploy ed Module or Port Adapter is p art of, is available on the network the chassis object automatically commissions and initiates subchassis discovery. Subchassis objects appear within the Ma p Viewer beneath the appropriate object and appear in the Chassis Map.

Page 81

4-21

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Predeploying Anticipated Network Objects

Commissioning Predeployed Objects

Predeployed objects may be commissioned manually or aut omatically , depending on the selections m ade from the Deployment W izard object parameters. Object deplo yed with the Auto Commission setting are discovered when a coldStart SNMP trap that is issued from the switch is received by the Cisco EMF server. Receipt of this trap initiates subchassis discovery of the predeployed Network Element, commissioning discovered subobjects.

For the automatic commissioning to work, the switch or router must be configured to send SNMP traps and the Cisco EMF server host must be in the trap client list.

If the coldStart trap is not received by the Cisco EMF server when the switch is first brought on-line, then the predeployed Network Element object needs to be commissioned manually by opening the Network Element window and selecting the Commission button. For further information, see the

“Manually Commissioning Network Elem ents” sect ion on pa ge 4-25.

Page 82

4-22

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Enabling Communication Between Network Elements and Devices

Before commissioning, a communication must be established with the deployed Network Element if it was deployed under one of the following circumstances:

• IP Auto Discovery

• Predeployment

• Manual Deployment to the decommissioned state where the SNMP read/write community strings

and device passwords were not identified

Note If the SNMP read/write community strings and device passwords were identified during the manual

deployment process but the Network Element is in the decommissioned state, the basis for communication with the device is established through the Deployment Wizard but the Network Element object must be commissioned. For instructions on commissioning a Network Element, see the “Manually

Commissioning Network Elements” section on page 4-25.

To enable communication between the Network Element and the device, perform the following:

Step 1 Launch the Network Element Management window by performing one of the following:

• Right–click a Site object within the Network or Physical containment views, then choose

CSM/7600 Manager > NE Config/Mgmt.

• Right–click a Network Element object within the Network or Physical containment views, then

choose NE Config/Mgmt.

The Network Element Management window appears.

Page 83

4-23

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Enabling Communication Between Network Elements and Devices

Figure 4-5 Network Element Management window

Step 2 Specify the passwords and SNMP communities as follows:

a. Select the Configuration tab on the Network Element Management window. b. In the CLI Passwords section, specify the Telnet Password and Enable Password parameters as

follows:

–

Telnet Password—Password used to connect to the switch using the Telnet protocol.

–

Enable Password—Password used to enter the enable mode on the switch.

All values entered in these text fields will be displayed as “*”.

Step 3 Specify the SNMP read and write community strings as follows:

a. Select the SNMP Access tab on the Network Element Management window. b. Enter the correct SNMP read/write community strings as follows:

–

SNMP Version—The version of the SNMP agent running on the switch. The version is one of

these values: SNMPv1, SNMPv2c, or SNMPv3.

The SNMPv3 value is not supported by the Catalyst switches.

–

SNMP v2c Read Community—The v2c community string used to read data from the agent.

–

SNMP v2c Write Community—The v2c community string used to write data to the agent.

Page 84

4-24

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Enabling Communication Between Network Elements and Devices

Note It is possible for the read and read-write community strings are specified as public and private.

If “private” is specified in the IP Discovery window (see Figure 4-2), that value displays on the SNMP Access tab of the Network Element Management window. The community string used in the IP Discovery window should be the read-write SNMP community.

Step 4 Save the entered data by choosing File > Save or clicking the Save icon in the window tool bar as

required.

Step 5 Close the window choosing File > Close or clicking the Close icon in the window tool bar as required.

The window closes.

Page 85

4-25

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Commissioning Network Elements

After the Network Element and Software objects are created using the Deployment Wizard, the type of switch and its contents need to be determined. This determinat ion is made by commissioning the Chassis object. When the Network Element object is commissioned, it executes a subchassis discovery process that communicates with the switch to automatically determine the contents of the switch.

Prior to manually commissioning a Network Element, ensure that the EMS and the device are setup to communicate. For instructions, see the “Enabling Communication Between Network Elements and

Devices” section on page 4-22.

To commission the Network Element object, perform the following:

Step 1 Launch the Network Element Management window by performing one of the following:

• Right–click a Site object within the Network or Physical containment views, then choose

CSM/7600 Manager > NE Config/Mgmt.

• Right–click a Network Element object within the Network or Physical containment views, then

choose NE Config/Mgmt.

The Network Element Management window appears.

Figure 4-6 Network Element Management window

Page 86

4-26

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Commissioning Network Elements

Step 2 From the Configuration tab on the Network Element Management window , click th e Commission button

to start the subchassis discovery process. Subchassis discovery allows the Cisco Catalyst Switch Manager to determine which modules are

installed on the switch and also allows Cisco EMF to start monitoring the switch.

Note Commissioning may take a few minutes.

After the Network Element object is commissioned, the Ph y sical view will resemble the example in the following figure.

Figure 4-7 Commissioned Catalyst 6006 Switch

If there is installed hardware that is not supported by Cisco Ca talyst Switch Man ager, the modu le image will contain a “?” in the graphical display.

If an error is encountered when the object is commissioned, the Network Element object might go into the Mismatched or Lostcomms state and an alarm would be raised.

The Network Element is placed in the Mismatched state if the IP address specified during the Deployment Wizard does not correspond to the device type that was deployed. If this occurs, the Network Element object must be deleted from Cisco EMF and redeployed with the correct IP address or type.

Page 87

4-27

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Manually Commissioning Network Elements

The Network Element is placed in the Lostcomms state if the SNMP read community string specified in the Deployment Wizard is incorrect. If this occurs,

1. Open the Network Element window (displaying the Configuration tab).

2. Decommission the Network Element object by clicking Decommission on the Configuration tab.

3. Select the SNMP tab, then enter the correct SNMP read community.

4. Select the Configuration tab, then recommission the Network Element object by clicking

Commission.

Step 3 Close the window choosing File > Close or clicking the Close icon in the window tool bar as required .

The window closes.

Page 88

4-28

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 4 Deploying the Cisco Catalyst Switch Manager

Working With Object Management Windows

The following sections provide helpful information in regards to launching and using the windows provided in Cisco Catalyst Switch Manager.

Launching Object Management Windows

After all the objects in the network element are in the normal state, windows can be opened to perform management operations on the network element.

To launch the management window of a Cisco Catalyst Switch Manager object, right click its parent object in the Map Viewer application or the object itself in the containment view. Select the option to open the object’s window from the pop-up menu. For descriptions of the object hierarchies, refer to the

Cisco Catalyst Switch Manager Objects and Interfaces section in Chapter 2, “Basic Concepts.”

Tips for Working with Object Management Windows

• Perform management functions on multiple objects within the chassis

Although you cannot launch windows when multiple objects are selected, you can select multiple objects within the list boxes which appear on the left–hand side of most object management windows simultaneously in order to invoke system actions such as configuration or performance logging.

To select a contiguous block of objects, click on the first object; then, without releasing the mouse button, drag to the last desired entry and release. A su bsequent click anywhere on the window deselects all previous selections. T o extend a current ly selected block of chassis, press the Shift key and click on the entry at the end of the group to be added. To add a non–contiguous entry to the selection group, hold down the Ctrl (Control) key and click on the entry to be added.

When selecting multiple entries in a parenting object list box, for example multiple modules on an interface–level window, all applicable interface objects of the selected module s appear in the Interfaces list. The attributes of last object selected in a list box on the left–hand side of a window display in the tabs and areas to the right.

Note that some windows do not support the multiple select feature when unique data entry is required or when system impacts can occur.

• Bring open windows to the front of the display from the Window menu

Handy when you have se veral windo ws open at one time, you can use the W ind ow menu on an open window to bring another open window to the front of the display (i.e., in–front of the other open windows) no matter how many windows are covering it.

• Initiate window navigation from a list box on the left–hand side of an open window

Rather than right–clicking on an object within the Map Viewer, you can right–click objects that display in the list boxes which appear on the left–hand side of the object management windows.

• Active versus Inactive attributes on object management windows

Although all fields available on each EM windo w are described in this guide, some fi elds may appear in faded gray text rather than black text. Active attributes appear in black text and allow text insertion or selection. Fields or buttons which appear in gray text are inactive. Inactive parameters are not currently supported by the Cisco Catalyst Switch Manager, but the associated data may be set or viewed through the related IOS CLI commands.

Page 89

CHA P T E R

5-1

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Network Element Management

This chapter describes how to manage chassis using the Cisco Catalyst Switch Manager, and consi sts of the following primary sections:

• Chassis Layer2/Layer3 Management Window

• Network Element Management Window

• MAC Address Query Window

Page 90

5-2

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Chassis Layer2/Layer3 Management Window

The Chassis Layer2/Layer3 Management window provides capabilities to enable or disable Cisco discovery, unidirectional, LAN and IP routing protocols on the network element.

To launch the Chassis Layer2/Layer3 Management window, perform one of the following:

• Right–click a Site object within the Network or Physical containment views, then choose

CSM/7600 Manager > Chassis Mgmt–IP.

• Right–click a Network Element object within the Network or Physical containment views, then

choose Chassis Mgmt–IP.

The following figure is an example of the Chassis Layer2/Layer3 Management window.

Figure 5-1 Chassis Layer2/Layer3 Management Window

The Chassis Layer2/Layer3 Management window includes the following areas:

• Layer 2 Configuration

• Layer 3 Configuration

Page 91

5-3

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Chassis Layer2/Layer3 Management Window

Layer 2 Configuration

The Layer 2 Configuration area provides the following information:

• CDP—Displays the Cisco Discovery Protocol (CDP) global status on the n etwork element , enabled

or disabled.

• UDLP—Displays the UniDirectional Link Detection Protocol (UDLP) global status on the network

element: enabled, aggressive, or disabled. The “aggressive” option is not applicable for CatOS.

• 802.1x—Displays the 802.1x Port Based Authentication global status on the network element,

enabled or disabled.

Note Dot1x cannot be enabled if dynamic mode is enabled on one or more ports.

Layer 3 Configuration

The Layer 3 Configuration area provides the following information:

• IP CEF—Displays the status of the IP CEF routing on the network element, enabled or disabled.

This feature cannot be disabled on Cisco 3950, 4000, 4500, 6000, 6500, and 7600 series devices.

• IP Multicast—Displays the status of the IP Multicast routing on the network element, enabled or

disabled.

Page 92

5-4

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

The Network Element Management window provides monitoring and mana gement i nformation fo r properties related to the Catalyst switch. These properties include the Telnet and Enable passwords, global performance logging, and SNMP properties for the entire switch.

To launch the Network Element Management window, perform one of the following:

• Right–click a Site object within the Network or Physical containment views, then choose

CSM/7600 Manager > NE Config/Mgmt.

• Right–click a Network Element object within the Network or Physical containment views, then

choose NE Config/Mgmt.

The following figure is an example of the Network Element Management window.

Figure 5-2 Network Element Management Window

The Network Element object list (left-hand side of the window) allows multiple objects to be selected, so that configuration changes can be applied to multiple Network Element objects at the same time.

The following tabs are available on the Network Element Management window:

• Configuration Tab

• System Information Tab

Page 93

5-5

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

• SNMP Access Tab

• SNMP Trap Tab

• Device Management Tab

• Additional Notes Tab

Configuration Tab

The following areas are available on the Configuration tab of the Network Element Management window:

• System

• IP Address

• Operating System

• IOS Session

• Cat OS Session

• Reset System

• Actions

System

The System area provides the following information:

• System Name—Fully qualified name of the switch or router.

IP Address

The IP Address area provides the following information:

• Supervisor—IP address used to access the switch or router.

• MSFC—IP address of the management agent on the MSFC daughter card (only in Hybrid OS).

Operating System

The Operating System area provides the following information:

• Expected OS Type—This attribute is used by a client that initiates a deploym ent context to indicate

the type of operating system expected on a managed device. This can only be changed when the device is decommissioned. Values are:

–

Catalyst OS Only

–

Hybrid OS

–

Native OS

• Active OS Type—The operating system type detected on the managed device.

Page 94

5-6

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

IOS Session

Note The attributes within this area are inactive for Catalyst OS devices.

The IOS Session area provides the following information:

• Username—User name to establish an IOS management session with the device over telnet.

• Password—Password to establish an IOS management session with the device over telnet.

• EXEC Password—Password to enter privileged EXEC mode.

Cat OS Session

Note The attributes within this area are inactive for IOS devices.

The Cat OS Session area provides the following information:

• Same As IOS?—If enabled, the IOS telnet username and password are automatically used to connect

to the Supervisor module over CatOS in Hybrid OS configurations. If this attribute is set to ‘No’ the Username, Password, and EXEC Password fields in the Cat OS

Session area become active.

• Username—User name to establish a CatOS management session with the device over telnet.

• Password—Password to establish a CatOS management session with the device over telnet.

• EXEC Password—Password to enter privileged EXEC mode in a CatOS session.

Note If the above passwords are incorrect, some window va l u e s m a y r e p o r t a s E R ROR .

Reset System

The Reset System area provides the following information:

• Last Restart Reason—Text message displaying why the switch or router was restarted.

• Reset—Button used to reset the switch or router. This action power cycles the switch or router. If

clicked, a pop-up is displayed asking if you really want to reset the switch or router.

Note The Last Restart Reason has no value in a pure CatOS installation.

Note Only users with administrative privileges can use the Reset button.

Note Any changes to the running conf i gurat ion wil l be saved automatically when the switch or router

is reset using the Reset button.

Page 95

5-7

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

Actions

The Actions area provides the following information:

• Commission— Commissions the object manually. Y ou can commissio n the object only if t he object

is in a decommissioned state. Clicking this b utto n forces a subchassis disco v ery to be e x ecuted, and propagates the commissioned status to all subobjects.

• Decommission—Decommissions the object manually and propagates the decommissioned status to

all subobjects. In the decommissioned state, the properties of the object are not monitored. As a result, data displayed in the configuration window is not guaranteed to be current.

System Information Tab

The System Information tab of the Network Element Management window provides the following information:

• System Up Time—The duration of time indicating how long the system has been running. This

attribute is read-only.

• System Services—List of OSI layers supported by the switch or router. This attribute is read-only.

• System Location—Displays the location of the switch or router.

• System Contact—Displays the name of the person who is the contact for this switch/router.

• System Description—A multiline text description of the switch/router. This attribute is read-only.

• Cisco Contact Information—Details on how to contact Cisco Systems. This attribute is read-only

and has no value in a pure CatOS installation.

SNMP Access Tab

The following areas are available on the SNMP Access tab of the Network Element Management window:

• IOS SNMP

• Cat OS SNMP

IOS SNMP

Note The attributes within this area are inactive for Catalyst OS devices.

The IOS SNMP area provides the following information:

• SNMP v2c Read Community—The v2c community string used to read data from the agent.

• SNMP v2c Write Community—The v2c community string used to write data from the agent.

• Last Authentication Failure Address—The IP address of the last host that caused an SNMP

authentication failure to occur.

Note The Last Authentication Failure Address has no value in a pure CatOS installation.

Page 96

5-8

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

Cat OS SNMP

Note The attributes within this area are inactive for IOS devices.

The Cat OS SNMP area provides the following information:

• Same As IOS?—If enabled, the IOS SNMP version and communities will be used to access the

SNMP Agent on the Supervisor module in Hybrid OS configurations. If this attribute is set to ‘No’ the SNMP Read Community and SNMP Write Community fields in

the Cat OS SNMP area become active.

• SNMP v2c Read Community—The v2c community string used to read data from the agent.

• SNMP v2c Write Community—The v2c community string used to write data to the agent.

SNMP Trap Tab

The following areas are available on the Configuration tab of the Network Element Management window:

• Tra p Generat i on

• SNMP Trap

Trap Generation

The Trap Generation area provides the following information:

• SNMP Trap Status—Indicates the level at which SNMP traps are enabled. The level is one of these

values:

–

disabled

–

layer2Only—SNMP traps are enabled on the datalink layer only.

–

layer3Only—SNMP traps are enabled on the network layer only.

–

layer2And3—SNMP traps are enabled on the datalink and network layers.

• Enable—Enables all SNMP trap generation from the swit ch or rout er.

• Disable—Disables all SNMP trap generation from the switch or router.

SNMP Trap

The SNMP Trap area provides the following information:

• Trap Client IP Table—IP address table to which SNMP traps generated by the switch or router are

sent.

–

Trap Client IP—The IP address to which SNMP traps are sent.

–

Client Community—The community string used within the SNMP trap.

–

SNMP Version—Version of the SNMP protocol used by Cisco EMF to communicate with the managed device. This field has the following value: snmpv2c.

Page 97

5-9

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

–

Notification Layer - Indicates the level at which the SNMP trap client is defined. The level is

one of these values:

•layer2Only—SNMP trap client is defined on the datalink layer only.

•layer3Only—SNMP trap client is defined on the network layer only.

•layer2And3—SNMP trap client is defined on the datalink and network layers.

Note The IP address of the Cisco EMF server host should be in this list at all times. If it is not, then

Cisco EMF will not receive any traps from the switch or router, which might result in an event being reported in an untimely fash ion or an event being missed.

• Configure—Launches the Chassis Management - Configure SNMP Trap Client window for

modifying the Trap Client list.

Figure 5-3 Chassis Management—Configure SNMP Trap Client Window

The SNMP Trap Client Configure window provides the following:

–

SNMP Trap Client Address—The IP address to which SNMP traps are sent.

–

SNMP Trap Client Community String—The community string used within the SNMP trap.

–

SNMP Version—The SNMP version running on the device, snmpv1c or snmpv2.

–

Add Client—Adds a client to the client list.

–

Remove Client—Removes the client from the client list.

Note An error is reported if a nonexistent client is removed or if an existing client is added.

Page 98

5-10

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

Network Element Management Window

Device Management Tab

The Device Management tab of the Network Element Management window consists of a single area, Write Config to Flash. The Write Config to Flash area provides a single button:

• Write Mem—Changes to the running config are saved to the startup config. In the future, when the

startup config is accessed, it will contain the most recent running config written to memory.

Additional Notes Tab

The Additional Notes tab of the Network Element Management window contains the Notes area which is a text box that allows you to type in additional notes. For example, this information can include text indicating why global performance logging is turned on.

Page 99

5-11

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

MAC Address Query Window

MAC Addresses are used within a network to iden tify specific ports on an interface. Other de vices in the network use MAC addresses to locate ports in order to create and update routing tables and data structures. The MAC Address Query window allows you to query a Network Element for a MAC address.

The query results of a Network Element based on a MAC address display in an Action Report window, indicating data similar to a “show mac address table address xxxx.xxxx.xxxx” command.

Note MAC address queries may require extensive lengths of time to complete depending on the inventory of

the Network Element object being queried.

To launch the MAC Address Query window, perform one of the following:

• Right–click a Site object within the Network or Physical containment views, then choose

CSM/7600 Manager > NE MAC Address Query.

• Right–click a Network Element object within the Network or Physical containment views, then

choose NE MAC Address Query.

The following figure is an example of the MAC Address Query window.

Figure 5-4 MAC Address Query Window

Page 100

5-12

Cisco Catalyst Switch Manager User Guide

OL-4930-01

Chapter 5 Network Element Management

MAC Address Query Window

The following areas are available on the MAC Address Query window:

• Network Element

• MAC Address Query

Network Element

The Network Element area consist s of a l isti ng o f al l netw ork elements available via the selected object.

MAC Address Query

The MAC Address Query area provides the following:

• MAC Address—Indicates the MAC address to be queried. The MAC address should be entered in

xxxx.xxxx.xxxx format where x may be 1 through 9, A through Z, or a through z.

• Query—Searches the selected Network Element for the entered MAC address.

T o query a MAC address for a Network Element, enter the MAC addr ess in the correspondi ng f ield then click Query. An Action Report window displays indicating the results. An example of a report follows.

Chassis: ems6513a show mac-address-table address: 0006.524B.6A0A Codes: *-primary entry vlan mac address type learn qos ports

-+-----+--------------+-------+------+----+------+ Supervisor: * --- 006.524b.6a0a static No --- Router * --- 006.524b.6a0a static No --- Router * 613 006.524b.6a0a static No --- Router * 333 006.524b.6a0a static No --- Router * 652 006.524b.6a0a static No --- Router * 701 006.524b.6a0a static No --- Router * 700 006.524b.6a0a static No --- Router * 678 006.524b.6a0a static No --- Router * 677 006.524b.6a0a static No --- Router * 908 006.524b.6a0a static No --- Router * 904 006.524b.6a0a static No --- Router * 907 006.524b.6a0a static No --- Router * 906 006.524b.6a0a static No --- Router * 710 006.524b.6a0a static No --- Router * --- 006.524b.6a0a static No --- Router * 999 006.524b.6a0a static No --- Router * 201 006.524b.6a0a static No --- Router

--------------------------------------------------

If a MAC address is not found, a message displays in the table area of the report indicating no results found.