Cisco WAN Manager Installation Guide for Solaris 7 · Upgrading Existing Switch Software to 9.3.30 11-4 ... The Cisco WAN Manager Installation Guide for Solaris 7 is intended to provide

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

800 553-NETS (6387)Fax: 408 526-4100

Cisco WAN Manager Installation Guide for Solaris 7Release 11July 2003

Customer Order Number: DOC-7813567=Text Part Number: 78-13567-01

http://www.cisco.com

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

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

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

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

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

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, 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 U.S. and certain other countries.

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

Cisco WAN Manager Installation Guide for Solaris 7, Release 11.Copyright © 2003 Cisco Systems, Inc.All rights reserved.

iiiCisco WAN Manager Installation Guide for Solaris 7

Release 11, Part Number 78-13567-01 Rev. G0, October 2003

C O N T E N T S

About This Guide ix

Objectives ix

Audience ix

Document Organization ix

Related Documentation x

Cisco WAN Manager Release 11 x

Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 xi

Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 xii

Cisco MGX 8950 Multiservice Switch Release 3 xiv

SES PNNI Controller Release 3 xv

Cisco MGX 8830 Multiservice Switch Release 3 xv

Cisco WAN Switching Software Release 9.3 xvi

Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1 xvii

Cisco MGX 8250 Edge Concentrator Switch Release 1 xviii

Cisco MGX 8230 Edge Concentrator Switch Release 1 xix

Document Conventions xx

Obtaining Documentation xxi

World Wide Web xxi

Documentation CD-ROM xxi

Ordering Documentation xxii

Documentation Feedback xxii

Obtaining Technical Assistance xxii

Cisco.com xxii

Technical Assistance Center xxiii

C H A P T E R 1 Introduction 1-1

CWM Configurations 1-2

Upgrade Limitations 1-3

CiscoView Guidelines 1-3

Installation or Upgrade Sequences 1-4

C H A P T E R 2 Preparing for CWM Installation 2-1

CWM Server Prerequisite Checklist 2-1

CWM Server Workstation Requirements 2-2

Contents

ivCisco WAN Manager Installation Guide for Solaris 7


Hardware Requirements 2-3

Software Requirements 2-3

CWM Standalone Statistics Collector 2-4



CWM Client System Requirements 2-5



Solaris Operating System 2.7 Installation 2-6

Preparing the Disk 2-6

Solaris 2.7 Initial Configuration 2-7

Disk Partitioning Requirements 2-9

Partitioning Two 9-GB Disks 2-9

Partitioning an 18-GB Disk 2-10

Installing Solaris on the Newly-Partitioned Disk 2-11

Installing Solaris 2.7 Patches 2-12

First Time Login to Solaris 2-12

CiscoView 5.4 Considerations 2-13

Installation of Netscape Communicator 2-13

HP OpenView 6.2 Installation 2-15

Obtaining HP OpenView Software 2-15

Installing HP OpenView Software 2-15

Setting Up CWM to HP OpenView Communication 2-15

Check the /etc/services File 2-16

Starting HP OpenView 2-16

Wingz Version 2.5.1 Installation 2-16

C H A P T E R 3 Installing CWM Server Software 3-1

Installing CWM Software 3-1

Post Installation Tasks 3-14

First Time Login as User svplus 3-14

Checking the CWM Server File System 3-15

C H A P T E R 4 Upgrading CWM Software 4-1

Upgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release 4-1

Upgrading to the CWM 11 Software from Release 10.4 or 10.5.10 with Multiple CWM Gateways 4-14

Initial Conditions before Upgrade 4-14

Upgrade Procedure 4-15

Contents

vCisco WAN Manager Installation Guide for Solaris 7


Post Installation Tasks 4-17


Checking the CWM Server File System 4-18

C H A P T E R 5 CiscoView, Netscape, and the Java Plug-in 5-1

Installing the Java Plug-in 1.3.1 on Solaris 5-1

Uninstall of the Java Plug-in 5-2

Standalone Installation of CiscoView 5-2

Uninstall CiscoView 5-4

Uninstallation of Netscape Communicator 5-4

C H A P T E R 6 Installing CWM SNMP Service Agent Software 6-1

Installing SNMP Service Agent Software 6-1

Configuration 6-7

Agent Configuration 6-7

Service Agent Configuration 6-7

C H A P T E R 7 Installing CWM Client 7-1

Overview of CWM Client 7-1

Setting Up a Windows Based CWM Client 7-2

Hardware 7-2

Software 7-2

Web Browser 7-3

Installing Java Tools 7-4

Setting Up a Solaris Based CWM Client 7-7

Hardware 7-7

Software 7-7

Web Browser 7-8

Installing Java Tools 7-9

Installing Java Web Start 7-12

Launching CWM Client 7-13

Web Browser Method 7-13

Java Web Start Application Manager Method 7-14

Desktop Shortcut Method 7-15

C H A P T E R 8 Installing Standalone Statistics Collection Manager Software 8-1

Installing CWM Statistics Collection Manager Standalone 8-2


Contents

viCisco WAN Manager Installation Guide for Solaris 7


C H A P T E R 9 Upgrading Standalone Statistics Collection Manager Software 9-1

Upgrading CWM Statistics Collection Manager Standalone Software 9-2

Upgrading to the SCMSA 11 Software from Release 10.x with Multiple CWM Gateways 9-10

Initial Conditions before Upgrade 9-10

Upgrade Procedure 9-11


C H A P T E R 10 Configuration 10-1

Configuring Topology Discovery 10-1

Configuring AutoRoute Topology 10-1

Configuring PNNI Topology 10-2

Configuring Hybrid Topology 10-3

Configuring Standalone Nodes 10-3

Checking the CWM Workstation File System 10-4

Modifying the SNMP Community String 10-11

Modifying the svplus.conf File 10-11

Modifying the process.conf File 10-12

Setting Up the IP Address on an Cisco MGX 8850, Release 2 Switch 10-12

Setting Up ATM WAN Connections 10-13

Configuring the Switch 10-14

Configuring the Router 10-16

cnflan 10-18

cnfnwip 10-20

cnfstatmast 10-21

Configuring PNNI using CiscoView 10-22

Getting Started 10-22

PNNI Configuration 10-22

PNNI Configuration Categories 10-24

C H A P T E R 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN Manager 11-1

Migration Process Overview 11-1

Upgrade Cisco WAN Manager from 10.x to 11. 11-1

Preparing To Upgrade Cisco BPX Switch Software From 9.2.34 to 9.3.30 11-1

Gracefully Upgrading the BCC Card Pair on the BPX node 11-3

Gracefully Upgrading the Rest of the Cards on the BPX Node 11-3

Upgrading Existing Switch Software to 9.3.30 11-4

Upgrading the MGX 8850 from Release 2 to Release 2.1 Software 11-5

XPVC Creation Overview 11-6

Contents

viiCisco WAN Manager Installation Guide for Solaris 7


XPVC as a Migration Connection 11-10

XPVC/XPVP Provisioning and Management 11-11

Connection Creation for XPVC/XPVPs 11-12

Creating an XPVC 11-12

XPVC Preferred Table Configurator 11-12

CWM-XPVC-CLI 11-13

Adding an XPVC 11-13

Deleting an XPVC 11-16

XPVC Provisioning via Service Agent 11-18

Location of ConnProxy Scripts 11-18

Displaying XPVC Status 11-25

Displaying Information on a Specified XPVC Segment 11-27

XPVC End-to-end Test Delay 11-29

A P P E N D I X A Statistics Collection Manager Configuration A-1

Description of Modules A-1

SCM Control Server A-2

SCM Collection Server A-2

SCM Parser Server A-2

SCM Installation Options A-2

ScmProxy A-4

Setting Up the SCM Configurations A-5

SCM Redundancy A-6

A P P E N D I X B IP Reachability B-1

Overview B-1

General Guidelines B-2

AutoRoute Networks B-2

PNNI Networks B-4

I N D E X

Contents

viiiCisco WAN Manager Installation Guide for Solaris 7


ixCisco WAN Manager Installation Guide for Solaris 7


About This Guide

This guide provides information about how to install Cisco WAN Manager (CWM) Release 11 software on a Sun workstation running the Solaris 2.7 operating system (also known as Solaris 7). Instructions for installing the Cisco WAN Manager client on a Windows system is also covered.

ObjectivesThe Cisco WAN Manager Installation Guide for Solaris 7 is intended to provide information on how to install and configure the CWM Release 11 product.

AudienceThe Cisco WAN Manager Installation Guide for Solaris 7 is intended for experienced UNIX users who are involved with the installation and configuration of the CWM Release 11 product.

Document OrganizationThis installation guide has the following chapters and appendices:

• Chapter 1—Introduction

• Chapter 2—Preparing for CWM Installation

• Chapter 3—Installing CWM Server Software

• Chapter 4—Upgrading CWM Software

• Chapter 5—CiscoView, Netscape and the Java Plug-in

• Chapter 6—Installing CWM SNMP Service Agent Software

• Chapter 7—Installing CWM Client

• Chapter 8—Installing Statistics Collection Manager Software

• Chapter 9—Upgrading Statistics Collection Manager Software

• Chapter 10—Configuration

• Chapter 11—Migration from Automatic Routing Management to PNNI Using Cisco WAN Manager

xCisco WAN Manager Installation Guide for Solaris 7


About This GuideRelated Documentation

• Appendix A—Statistics Collection Manager Configuration

• Appendix B—IP Reachability

Related DocumentationThe following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.

Cisco WAN Manager Release 11The product documentation for the Cisco WAN Manager (CWM) network management system for Release 11 is listed in Table 1.

Table 1 Cisco WAN Manager Release 11 Documentation

Title Description

Cisco WAN Manager Installation Guide for Solaris 7, Release 11

DOC-7813567=

Provides procedures for installing Release 11 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 7 platform.

Cisco WAN Manager Installation Guide for Solaris 8, Release 11

DOC-7814230=

Provides procedures for installing Release 11 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 8 platform.

Cisco WAN Manager User’s Guide, Release 11

DOC-7813568=

Describes how to use the CWM Release 11 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.

Cisco WAN Manager SNMP Service Agent, Release 11

DOC-7813569=

Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM that is used for managing Cisco WAN switches using SNMP.

Cisco WAN Manager Database Interface Guide, Release 11

DOC-7813542=

Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.

Table 2 WAN CiscoView Release 3 Documentation

Title Description

WAN CiscoView Release 3 for the MGX 8220 Edge Concentrator, Release 5

DOC-7812768=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco MGX 8220 Edge Concentrator.

WAN CiscoView Release 3 for the MGX 8850 Edge Switch, Release 1

DOC-7811242=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco MGX 8850 Edge Switch.

xiCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 The product documentation for installing and operating the Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 is listed in Table 3.

WAN CiscoView Release 3 for the MGX 8250 Edge Concentrator, Release 1

DOC-7811241=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco MGX 8250 Edge Concentrator.

WAN CiscoView Release 3 for the MGX 8230 Multiservice Gateway, Release 1

DOC-7810926=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco MGX 8230 Multiservice Gateway.

WAN CiscoView for Release 2 of the MGX 8850

DOC-7810349=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco MGX 8850 switch.

WAN CiscoView Release 3 for IGX 8400 Switches

DOC-78111243=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco IGX 8400 switch.

WAN CiscoView Release 3 for BPX 8600 Switches

DOC-7811244=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco BPX 8600 switch.

WAN CiscoView Release 3 for the BPX SES PNNI Controller

DOC-7812303=

Provides instructions for using this network management software application that allows you to perform minor configuration and troubleshooting tasks for element management of the Cisco BPX SES1 PNNI2 Controller.

1. SES = Service Expansion Shelf Private Network-to-Network Interface

2. PNNI = Private Network-to-Network Interface

Table 2 WAN CiscoView Release 3 Documentation (continued)

Title Description

Table 3 Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Documentation

Title Description

Cisco MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide, Release 3

DOC-7814250=

Describes how to install the Cisco MGX 8850 switch. This guide explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both broadband and narrowband service modules.

Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Command Reference, Release 3

DOC-7814789=

Describes the PXM commands that are available on the CLI1 of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.

xiiCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3The product documentation for installing and operating the Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 is listed in Table 4.

Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3

DOC-7814788=

Describes how to configure the Cisco MGX 8850 (PXM45) and the Cisco MGX 8950 switches with a PXM45 controller to operate as ATM edge or core switches. This guide also provides some operation and maintenance procedures.

Cisco SNMP Reference for MGX 8850 (PXM45 and PXM1E), MGX 8950, and MGX 8830, Release 3

DOC-7814747=

Provides information on all supported MIB2 objects, support restrictions, and traps for AXSM, AXSM-E, SRM-3T3, SRME, FRSM12, PXM45, PXM1E, RPM-PR, and RPM-XF.

Cisco Frame Relay Software Configuration Guide and Command Reference for the MGX 8850 FRSM12 Card, Release 3

DOC-7810327=

Describes how to use the high-speed Frame Relay (FRSM-12-T3E3) commands that are available in the CLI of the Cisco MGX 8850 (PXM45) switch.

Cisco AXSM Software Configuration Guide and Command Reference for MGX 8850 (PXM45) and MGX 8950, Release 3

DOC-7814257=

This guide explains how to configure the AXSM cards for operation and contains a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.

Cisco MGX and SES PNNI Network Planning Guide

DOC-7813543=

Provides guidelines for planning a PNNI network that uses the Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and the Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 Series Switch requires an SES3 for PNNI route processing.

Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 3

OL-2768-01 (online only)

Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 Release 3 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.

Cisco VISM Installation and Configuration Guide, Release 3.0


Describes how to install and configure VISM4 in the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides troubleshooting, maintenance, cable and connector specifications, and Cisco CLI command configuration information.

Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches

DOC-7814790=

Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.

1. CLI = command line interface

2. MIB = Management Information Base

3. SES = Service Expansion Shelf

4. VISM = Voice Interworking Service Module

Table 3 Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Documentation (continued)

Title Description

xiiiCisco WAN Manager Installation Guide for Solaris 7



Table 4 Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 Documentation

Title Description

Cisco MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide, Release 3

DOC-7814250=

Describes how to install the Cisco MGX 8850 routing switch. This documentation explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both broadband and narrowband service modules.

Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3

DOC-7814248=

Describes how to configure the Cisco MGX 8850 (PXM1E) and the Cisco MGX 8830 switches with PXM1E controller cards to operate as ATM edge switches. This guide also provides some operation and maintenance procedures.


DOC-7814789=

Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.


DOC-7814747=

Provides information on all supported MIB objects, support restrictions, and traps for AXSM, AXSM-E, SRM-3T3, SRME, FRSM12, PXM45, PXM1E, RPM-PR, and RPM-XF.

Cisco Frame Relay Software Configuration Guide and Command Reference for MGX Switches (PXM1E)

DOC-7814255=

Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides command descriptions for all FRSM commands.

Cisco AUSM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3

DOC-7814254=

Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides command descriptions for all AUSM commands.

Cisco CESM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3

DOC-7814256=

Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides command descriptions for all CESM commands.


DOC-7813543=

Provides guidelines for planning a PNNI network that uses Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 Series Switch requires an SES for PNNI route processing.



Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 Release 3 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.

xivCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8950 Multiservice Switch Release 3The product documentation for installing and operating the Cisco MGX 8950 Multiservice Switch Release 3 is listed in Table 5.



Describes how to install and configure VISM in the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides troubleshooting, maintenance, cable and connector specifications, and Cisco CLI command configuration information.


DOC-7814790=


Table 4 Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 Documentation (continued)

Title Description

Table 5 Cisco MGX 8950 Multiservice Switch Release 3 Documentation

Title Description

Cisco MGX 8950 Hardware Installation Guide, Release 3

DOC-7814147=

Describes how to install the Cisco MGX 8950 core switch. This documentation explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8950 switch uses a PXM45/B controller card and provides support for broadband service modules.


DOC-7814789=


Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3

DOC-7814788=

Describes how to configure the Cisco MGX 8850 (PXM45) and the Cisco MGX 8950 switches with a PXM45 controller to operate as ATM edge or core switches. This guide also provides some operation and maintenance procedures.

Cisco AXSM Software Configuration Guide and Command Reference for MGX 8850 (PXM45) and MGX 8950, Release 3

DOC-7814257=

This guide explains how to configure the AXSM cards for operation and contains a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.


DOC-7814747=



DOC-7813543=

Provides guidelines for planning a PNNI network that uses the Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and the Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 Series Switch requires an SES for PNNI route processing.

xvCisco WAN Manager Installation Guide for Solaris 7



SES PNNI Controller Release 3 The product documentation for installing and operating the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller Release 3 is listed in Table 6.

Cisco MGX 8830 Multiservice Switch Release 3The product documentation for installing and operating the Cisco MGX 8830 Multiservice Switch Release 3 is listed in Table 7.



Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 switch Release 3. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.


DOC-7814790=


Table 5 Cisco MGX 8950 Multiservice Switch Release 3 Documentation (continued)

Title Description

Table 6 SES PNNI Controller Release 3 Documentation

Title Description

Cisco SES PNNI Controller Software Configuration Guide, Release 3

DOC-7814258=

Describes how to configure, operate, and maintain the SES PNNI Controller.

Cisco SES PNNI Controller Command Reference, Release 3

DOC-7814260=

Provides a description of the commands used to configure and operate the SES PNNI Controller.


DOC-7813543=

Provides guidelines for planning a PNNI network that uses the Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and the Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 Series Switch requires an SES for PNNI route processing.

xviCisco WAN Manager Installation Guide for Solaris 7



Cisco WAN Switching Software Release 9.3The product documentation for installing and operating the Cisco WAN Switching Software Release 9.3 is listed in Table 8.

Table 7 Cisco MGX 8830 Multiservice Switch Release 3 Documentation

Title Description

Cisco MGX 8830 Hardware Installation Guide, Release 3

DOC-7814547=

Describes how to install the Cisco MGX 8830 edge switch. This documentation explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8830 switch uses a PXM1E controller card and provides PNNI support for narrowband service modules.

Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3

DOC-7814248=

Describes how to configure the Cisco MGX 8850 (PXM1E) and the Cisco MGX 8830 switches with PXM1E controller cards to operate as ATM edge switches. This guide also provides some operation and maintenance procedures.


DOC-7814789=



DOC-7814747=


Cisco AUSM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3

DOC-7814254=

Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides command descriptions for all AUSM commands.

Cisco CESM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3

DOC-7814256=

Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides command descriptions for all CESM commands.

Cisco Frame Relay Software Configuration Guide and Command Reference for MGX Switches (PXM1E)

DOC-7814255=

Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides command descriptions for all FRSM commands.





DOC-7814790=


xviiCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1The product documentation for installing and operating the Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1 is listed in Table 9.

Table 8 Cisco WAN Switching Software Release 9.3 Documentation

Title Description

Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30

DOC-7812907=

Provides a general description and technical details of the Cisco BPX broadband switch.

Cisco WAN Switching Command Reference, Release 9.3.30

DOC-7812906=

Provides detailed information on the general command line interface commands.

Cisco IGX 8400 Series Installation Guide, Release 9.3.30


Provides hardware installation and basic configuration information for Cisco IGX 8400 Series Switches that are running Switch Software Release 9.3.30 or earlier.

Cisco IGX 8400 Series Provisioning Guide, Release 9.3.30


Provides information for configuration and provisioning of selected services for the Cisco IGX 8400 Series Switches that are running Switch Software Release 9.3.30 or earlier.

9.3.42 Version Software Release Notes Cisco WAN Switching System Software


Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.

Cisco IGX 8400 Series Regulatory Compliance and Safety Information

DOC-7813227=

Provides regulatory compliance, product warnings, and safety recommendations for the Cisco IGX 8400 Series Switch.

Table 9 Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1 Documentation

Title Description

Cisco MGX 8850 Multiservice Switch Installation and Configuration, Release 1.1.3

DOC-7811223=

Provides installation instructions for the Cisco MGX 8850 (PXM1) Edge Concentrator Switch.

Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3

DOC-7811210=

Provides detailed information on the general command line for the Cisco MGX 8850 (PXM1) Edge Concentrator Switch.

Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3

DOC-7811240=

Provides error message descriptions and recovery procedures.

Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3


Provides a technical description of the system components and functionality of the Cisco MGX 8850 (PXM1) Edge Concentrator Switch from a technical perspective.

xviiiCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8250 Edge Concentrator Switch Release 1The documentation for installing and operating the Cisco MGX 8250 Edge Concentrator Switch Release 1 is listed in Table 10.

Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1

DOC-7812278=

Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B and RPM-PR) in the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.




Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1) Software Version 1.2.11



Table 9 Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1 Documentation (continued)

Title Description

Table 10 Cisco MGX 8250 Edge Concentrator Switch Release 1 Documentation

Title Description

Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3

DOC-7811217=

Provides installation instructions for the Cisco MGX 8250 Edge Concentrator Switch.

Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3

DOC-7811212=


Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3

DOC-7811216=


Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3

DOC-7811576=

Describes the system components and functionality of the Cisco MGX 8250 Edge Concentrator Switch from a technical perspective.


DOC-7812278=


xixCisco WAN Manager Installation Guide for Solaris 7



Cisco MGX 8230 Edge Concentrator Switch Release 1The documentation for installing and operating the Cisco MGX 8230 Edge Concentrator Switch Release 1 is listed in Table 11.




Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PSM1) Software Version 1.2.11



Table 10 Cisco MGX 8250 Edge Concentrator Switch Release 1 Documentation (continued)

Title Description

Table 11 Cisco MGX 8230 Edge Concentrator Switch Release 1 Documentation

Title Description

Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3

DOC-7811215=

Provides installation instructions for the Cisco MGX 8230 Edge Concentrator Switch.

Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3

DOC-7811211=


Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3

DOC-78112113=


Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3

DOC-7812899=

Provides a technical description of the system components and functionality of the Cisco MGX 8230 Edge Concentrator Switch from a technical perspective.


DOC-7812278=





Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PSM1) Software Version 1,2.11



xxCisco WAN Manager Installation Guide for Solaris 7


About This GuideDocument Conventions

Document ConventionsThis document uses the following conventions and terminology:

• pointer—indicates where the mouse action is to occur

• select—push and hold the left mouse button

• release—let up on a mouse button to initiate an action

• click—select and release a mouse button without moving the pointer

• double-click—click a mouse button twice quickly without moving the pointer

• drag—move the pointer by sliding the mouse with one or more buttons selected

CWM software supports a three-button mouse. The buttons have the following configurations:

• left button—selects objects and activates controls

• middle button—adjusts a selected group of objects, adds, or deselects a part of the group

• right button—displays and selects options from menus

Users can customize these buttons in an alternative manner.

In situations that allow the user to select more than one item from a list simultaneously, the following actions are supported:

• To select a single item in a list, click on the entry. To deselect a single item, click a second time on the previously selected entry.

• To select a contiguous block of items, click on the first entry; without releasing the mouse button, drag to the last desired entry and release. A subsequent click anywhere on the screen deselects all previous selections.

• To add an item to a selected group, press Shift and click on the entry at the end of the group to be added.

• To add a non-contiguous entry to the selection group, press Ctrl and click on the entry.

The following elements are in boldface:

• menu names

• buttons

• drop-down lists

• keyboard names

Words and characters that are displayed in terminal sessions and on-screen are printed in screen font.

When set off from the main text, words and characters that the user enters are printed in boldface screen font.

Word or character strings enclosed in angle brackets < > indicate that users substitute their own character string for the example presented in the text. When referenced in body text, the word is in boldface (not screen font). See the following examples:

• login: root—Enter the string root at the login prompt.

• password: <rootpassword>—Enter the password in place of the character string <rootpassword>.

Command descriptions use the following conventions:

• Commands and keywords are in boldface.

• Arguments that require values are in italic.

xxiCisco WAN Manager Installation Guide for Solaris 7


About This GuideObtaining Documentation

• Required command arguments are inside angle brackets < >.

• Optional command arguments are in square brackets [ ].

• Alternative keywords are separated by vertical bars ( | ).

Examples use the following conventions:

• Terminal sessions and system displays are in screen font.

• Information users enter is in boldface screen font.

• Non-printing characters, such as passwords, are in angle brackets < >.

• Default responses to system prompts are in square brackets [ ].

Tips, Notes, and cautions use the following conventions and symbols:

Tip Means the following information will help you solve a problem. The tips information mightnot be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

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

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

Obtaining DocumentationThe following sections provide sources for obtaining documentation from Cisco Systems.

World Wide WebYou can access the most current Cisco documentation on the World Wide Web at the following sites:

• http://www.cisco.com

• http://www-china.cisco.com

• http://www-europe.cisco.com

Documentation CD-ROMCisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

xxiiCisco WAN Manager Installation Guide for Solaris 7


About This GuideObtaining Technical Assistance

Ordering DocumentationCisco documentation is available in the following ways:

• Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation FeedbackIf you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to [email protected].

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.Document Resource Connection170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceCisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.comCisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

xxiiiCisco WAN Manager Installation Guide for Solaris 7



Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance CenterThe Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

• P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

• P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

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

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

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

P1 and P2 level problems are defined as follows:

• P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

• P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

xxivCisco WAN Manager Installation Guide for Solaris 7



C H A P T E R

1-1Cisco WAN Manager Installation Guide for Solaris 7


1Introduction

This chapter provides an introduction to Cisco WAN Manager (CWM) Release 11 and provides an overview of the CWM 11 installation and upgrade processes.

CWM is a set of programs that can be installed on a variety of platforms to manage networks that include Cisco nodes. Cisco CWM can be installed as a CWM server, a CWM client, and a standalone CWM statistics collector.

In an operational CWM network management system there must be at least one CWM server. There may be none, one, or several CWM clients and standalone CWM statistics collectors.

The CWM Release 11 comprises a set of software components. Some are Cisco products and some are third party products. Some are provided as part of the CWM package and some the user must obtain from third party sources.

The following table lists the components that make up the CWM 11 package. Note that CiscoView (CV) Release5.4 is one of the components and is normally installed as part of the CWM server install process.

Table 1-1 CWM Components

CWM Component Source

Solaris 2.7 Sun Microsystems

Solaris 2.7 patches Sun Microsystems

Netscape Communicator 4.76 Supplied on the Cisco CWM Rel. 11 CD-ROMs

Java Web Start Supplied on the Cisco CWM Rel. 11 CD-ROMs

Java Runtime Environment (JRE) 1.3 Supplied on the Cisco CWM Rel. 11 CD-ROMs

Java Plug-in 1.3.1 Supplied on the Cisco CWM Rel. 11 CD-ROMs

Informix Wingz 2.5.5 Supplied on the Cisco CWM Rel. 11 CD-ROMs

CWM Server Supplied on the Cisco CWM Rel. 11 CD-ROMs

CWM Client Supplied on the Cisco CWM Rel. 11 CD-ROMs

CiscoView 5.4 Supplied on the Cisco CWM Rel. 11 CD-ROMs

CWM SNMP Service Agent Optional package available at an additional charge (on a separate CD-ROM).



Chapter 1 Introduction

Note The basic CWM product is distributed as a two CD-ROM set.CD-ROM #1 contains the CWM server installation package.CD-ROM #2 contains Netscape Communicator, Adobe Acrobat, JRE 1.3.1, Java Plug-in 1.3.1, Java Webstart, documentation and the gzip utility

The CWM SNMP Service Agent and the SCMSA are each distributed on their own CD-ROMs

CWM ConfigurationsThe installation and upgrade processes permit the user to install these components in various combinations according to the user’s starting and ending CWM configurations. These two parameters determine which programs or components need to be installed or upgraded and in which sequence.

Table 1-2. provides a summary of the installation or upgrade process for each of the starting and ending configuration combinations.

HP OpenView 6.2 Hewlett-Packard (HP). HP OpenView is used in conjunction with the SNMP Service Agent for viewing the Event Log. It is not required for any other CWM procedures.

Statistics Collection Manager, Standalone (SCMSA)

Optional package available at an additional charge (on a separate CD-ROM).

Table 1-1 CWM Components (continued)

CWM Component Source

Table 1-2 Starting Configurations

Starting Configuration

Ending Configuration Installation/Upgrade Summary

Existing CWM 10.x server workstation

CWM 11 server workstation

The existing database is automatically preserved through the upgrade. Requires CWM 11 server and the CWM SNMP Service Agent (if used) to be installed. CiscoView requires that Netscape Communicator, the Java Plug-in, and certain Solaris patches be installed.

If the CWM SNMP Service Agent is installed, install HPOV 6.2. HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log.

From scratch using a new workstation

CWM 11 server workstation

A new workstation, probably received from Sun Microsystems with Solaris 8 or Solaris 9 already installed. Needs everything to be installed including Solaris 2.7, Informix Wingz and the appropriate CWM/CV modules. CiscoView requires that Netscape Communicator, the Java Plug-in, and certain Solaris patches be installed.

If the CWM SNMP Service Agent is installed, install HPOV 6.2. HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log.




Upgrade LimitationsCWM release 11 can be upgraded from CWM Release 10.4 (with Patch 2) or CWM Release 10.5.10 (with Patch 1) only. CWM Release 11 cannot be upgraded from any earlier release of CWM. Users of earlier CWM releases must upgrade by first upgrading to either 10.4 (Patch2) or 10.5.10 (Patch 1) and then upgrade to CWM 11.

CiscoView GuidelinesCiscoView 5.4 can be run in either a CWM server or a CWM client. For normal installation, CiscoView is installed as part of the CWM server installation and no separate CiscoView installation program is required. Once installed in the CWM server, it can be launched in the server or downloaded and launched in a client.

However, there may instances where CiscoView becomes corrupted or where a newer version is required and the user does not want to re-install the CWM server. For such an instance a standalone CiscoView installation program is included in the CWM package (see Chapter 5 for details).

CiscoView 5.4 running in a CWM server requires the installation of the following additional programs.

• Netscape Communicator 4.76 and its associated Solaris patches

• Java 1.3.1 Plug-in

The CWM client is supported both on a Solaris based machine and a Windows based machine.

In both cases CiscoView 5.4 requires the installation of the Java Plugin 1.3.1 in addition to

• Netscape Communicator 4.76 and its associated patches (Solaris version only).

• Sun Micosystems Java Web Start.

• Java Runtime Environment (JRE) 1.3.1.

Solaris based workstation

Solaris client workstation

Needs an Internet browser, a Java runtime environment, and Java Web Start. CWM Client is downloaded and launched from the CWM host using Java Web Start.

Windows based workstation

PC client workstation

Needs an Internet browser, a Jave Runtime Environment, and Java Web Start. CWM Client is downloaded and launched from the CWM host using Java Web Start.

Solaris based workstation

Statistics Collection Manager, Standalone

Requires the installation of Solaris 2.7 and the Statistics Collection Manager, Standalone.

Table 1-2 Starting Configurations (continued)

Starting Configuration

Ending Configuration Installation/Upgrade Summary




Installation or Upgrade SequencesThis section describes the sequence of operations for the various CWM installations and upgrades

CWM Server

Table 1-3 shows the sequence of operations that should be followed when performing a CWM 11 server installation or upgrade.

Table 1-3 CWM Server Sequence of Operations

Operation Notes

Install Solaris 2.7 Required if Solaris 2.7 is not installed in the starting configuration

Install Solaris patches required for CWM and CiscoView

The patch numbers and details of how to obtain them are included in the CWM 11 release notes.

Install Netscape Communicator 4.75

Required only if the workstation is to run CWM server or a CWM client. Not required for a Statistics Collection Manager, Standalone workstation.

Install Wingz 2.5.5 Required if the workstation is to run CWM server. Not required for a Statistics Collection Manager, Standalone workstation

Install or upgrade CWM server or client

This process also installs the web based version of CWM client, Java Web Start, JRE 1.2.2, and CiscoView.

Install CWM SNMP Service Agent

If required must be installed on a CWM server workstation with HP OpenView 6.2. It is used for flow through provisioning of PNNI SPVC supported by both Cisco BPX SES and Cisco MGX 8850 Release 2 networks. Not required for a Standalone Statistics Collection Manager workstation.

Install HP OpenView 6.2 HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log. It is not required for any other CWM procedures. Not required for a Statistics Collection Manager, Standalone workstation.

Install CiscoView 5.4 CiscoView is part of the CWM install procedure for both client and server workstations. Not required for a Statistics Collection Manager, Standalone workstation.

Install Java Plug-in 1.3.1 This operation is required everywhere CiscoView 5.4 is to be run (both client and server workstations). The installation is requested by Netscape Communicator and is performed when CiscoView is launched for the first time. Not required for a Statistics Collection Manager, Standalone workstation.




CWM Client

Table 1-4 shows the sequence of operations that should be followed when performing a CWM 11 client installation or upgrade.

Statistics Collection Manager, Standalone

Table 1-5 shows the sequence of operations that should be followed when performing a Statistics Collection Manager, Standalone (SCMSA) installation or upgrade.

Table 1-4 CWM Client Sequence of Operations

Operation Notes

Install operating system Solaris 2.7 on a Sun Microsystem machine

Microsoft Windows 2000 on a PC machine

Install web browser Netscape Communicator (for Solaris)

Netscape Communicator Internet Explorer (for PC)

Download Java Web Start, JRE 1.3.1, Java Plug-in 1.3.1

Downloaded from the CWM host machine using the web browser

Launch CWM 11 client Performed using the web browser and Java Web Start

Table 1-5 SCMSA Sequence of Operations

Operation Notes

Install Solaris 2.7 Required if Solaris 2.7 is not installed in the starting configuration

Install SCMSA —




C H A P T E R



2Preparing for CWM Installation

This chapter describes those items that should be checked and/or taken care of before Cisco WAN Manager (CWM) can be installed. This includes such items as checking that the hardware is sufficient for the installation, that the correct version of Solaris is installed and so on.

Specifically this chapter contains the following sections:

CWM Server Prerequisite Checklist It also provides information that the user will need prior to beginning the installation of Release 11 of CWM.

The section lists information that is required during the CWM server software installation. The following information is required:

Section Description

CWM Server Prerequisite Checklist

Provides you with details about how to gather the information you will require during the installation of the software.

CWM Server Workstation Requirements

Lists minimum workstation requirements to install and achieve the desired performance.

CWM Standalone Statistics Collector Requirements

Lists the minimum hardware and software requirements to install and operate the Standalone Statistics Collector.

CWM Client System Requirements

Lists the minimum hardware and software requirements to install and operate the CWM Client

Solaris Operating System 2.7 Installation

Lists pre-installation tasks, describes the installation and disk partitioning processes.

Disk Partitioning Provides details of the required disk partition sizes.

Installing Solaris 2.7 patches Lists the required Solaris patches and how to install them.

CiscoView 5.4 Considerations Provides the installation process for the CiscoView prerequisites (Netscape Communicator 4.75 and Java Plug-in 1.3.1).

Installing HP OpenView 6.2 Provides installation and setup procedures. HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log. It is not required for any other CWM procedures.

Installing Wingz Version 2.5.1 Provides installation and setup procedures.



Chapter 2 Preparing for CWM InstallationCWM Server Workstation Requirements

• Workstation hostname

• Root password

• IP Address and subnet address

• Connection method (direct, hub, or router)

Some of this information can be gathered by issuing commands at the existing network management system (NMS) workstation. If there is no existing NMS workstation, gather this information from another source.

Note Prerequisites for CWM client and SCMSA workstations are provided in Chapters 7 and 8 respectively.

CWM Server Workstation RequirementsThe following tables show the CWM Server hardware and software requirements

Table 2-1 Gathering Required Information

Command Comment

host% hostname Obtains workstation’s hostname

Note Hostnames for CWM workstations must begin with an alpha character and may contain only alpha and numeric characters. Do not use a hostname that contains any other characters such as a dash (-) or other special characters.

host% more /etc/defaultrouter Record the information if it exists

host% more /etc/hosts Record the addresses and hostnames

host% more /usr/users/svplus/config.sv

If upgrading, record the gateway node

host% netstat -rn Displays information about static routes

host% more /etc/rc2.d/S72inetsvc

Record the static routes (lines listed under /usr/sbin...224.0.0.0...).

host% more /etc/netmasks Record the IP addresses and subnet masks

host% more /etc/resolv.conf Record this information required for Netscape domain



Chapter 2 Preparing for CWM InstallationCWM Server Workstation Requirements

Hardware RequirementsFour types of machines are supported for CWM Release 11 servers. They are low-end, mid-range, high-end, and carrier grade platforms. Table 2-2 describes the configuration for each platform.

Note The minimum CPU speed requirement for all platforms is 300 MHz. The newer versions of the Sun Ultra 10 have a 450-MHz processor. All platforms require a 24-bit graphics card.

Rebooting the system displays the workstation type, amount of memory, and CPU speed.

The format command enables you to determine information about the disk drives on your workstation. Select a disk from the list of those available, and enter the verify command to determine the current partitioning of each disk.

Software RequirementsThe CWM 11 Server must be run on a Sun workstation with the following software:

Table 2-2 CWM Server Platform Requirements

Type Low End Mid Range High End Carrier Grade

Example Machine Type

Ultra 60 Ultra 60 Enterprise 450 Enterprise 4500

CPU’s 1 2 4 16

RAM 1 GB 2 GB 4 GB 8 GB

Minimum Disk Drives 18 GB 18 GB 36 GB 36 GB

Swap Space 4 GB 8 GB 16 GB 16 GB

Number of Connections

Up to 5,000 100,000 200,000 Up to 1,000,000

Number of Nodes Up to 20 200 1000 2000

Number of Desktops 1 1 12 12

Number of Clients 5 10 20 100

Table 2-3 Required Software

Software Comments

Sun Solaris 2.7 operating system Purchased separately from another vendor

Solaris 2.7 patches See the CWM 11 release notes for the most up-to-date list of required patches

Wingz 2.5.1 CD-ROM provided in the Cisco CWM package

Cisco WAN Manager 11 CD-ROM provided in the Cisco CWM package. Also included on this CD-ROM are CiscoView 5.4, Informix 9.2, Orbix, and the Java Development Kit (JDK).



Chapter 2 Preparing for CWM InstallationCWM Standalone Statistics Collector

CWM Standalone Statistics CollectorThe following tables show the CWM Standalone Statistics Collector hardware and software requirements

Hardware RequirementsFour types of machines are supported for CWM 11 statistic collectors. They are low-end, mid-range, high-end, and carrier grade platforms. Table 2-5 describes the configuration for each platform.

Note All platforms require a 24-bit graphics card and Ethernet connectivity to the CWM host.

Netscape Communicator 4.75 Required to run CiscoView 54. Provided in the Cisco CWM 11 package.

Java 1.3.1 Plug-in Required to run CiscoView 5.4. Provided in the Cisco CWM 11 package

Table 2-3 Required Software

Software Comments

Table 2-4 Optional Software

Software Comments

CWM Release 11 SNMP Service Agent

An optional package (on a separate CD) available at an additional charge. While the CWM Release 11 SNMP Service Agent software is not required to run CWM Release 11, it is used for flow through provisioning of PNNI SPVC supported by both Cisco BPX SES and Cisco MGX 8850 Release 2 networks.

HPOV 6.2 Purchased separately from another vendor. HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log. It is not required for any other CWM procedures.

Table 2-5 CWM Standalone Statistics Collector Platform Requirements

Type Low End High End

Machine Type Ultra 60 Enterprise 450

CPU’s 1 2

RAM 1 GB 2 GB

Disk Drives 18 GB 18 GB

Swap Space 1 GB 4 GB

Number of Connections

100,000 250,000



Chapter 2 Preparing for CWM InstallationCWM Client System Requirements

Software RequirementsThe CWM Release 11 Standalone Statistics Collector must be run on a machine with the following software

• Solaris 2.7 or Solaris 8

CWM Client System RequirementsThe following sections list the CWM Client hardware and software requirements

Hardware RequirementsCWM Client is supported on both a Windows based system and a Solaris based system.

Windows Based System

The following hardware is required for a Windows based CWM Client.

• Intel Pentium III (or compatible) processor with a clock speed of at least 200 Mhz

• 256 Mbytes of RAM

• 50 Mbytes of free disk space

• Ethernet connectivity to a CWM host machine

Solaris Based System

The following hardware is required for a Solaris based CWM Client.

• Sun Ultra 5 with 1 CPU or better

• 128 Mbytes RAM

• 50 Mbytes Disk Free

• Ethernet connectivity to a CWM host machine

Software RequirementsThe software requirements for CWM Client are as follows.

Windows Based System

The following software is required for a Windows based CWM Client.

• MicroSoft Windows 2000 or Windows NT 4.0operating system

• IP connectivity to a CWM host machine

• Windows versions of:

– Netscape Communicator browser version 4.75 or later



Chapter 2 Preparing for CWM InstallationSolaris Operating System 2.7 Installation

– Sun Microsystems Webstart version 1.01 or later

– Sun Microsystems JRE version 1.2.2

– Sun Microsystems Java 2 plug in 1.3.1

Solaris Based System

The following software is required for a Windows Solaris CWM Client.

• Solaris 2.7 or 2.8

• IP connectivity to CWM host machine

• Solaris versions of:

– Netscape Communicator browser version 4.75 or later

– Sun Microsystems Webstart version 1.01 or later

– Sun Microsystems JRE version 1.2.2

– Sun Microsystems Java 2 plug in 1.3.1

Solaris Operating System 2.7 Installation The following procedure need only be performed if Solaris 2.7 is not already installed on the intended CWM workstation.

Note A CWM server requires Solaris 2.7, a CWM client and a CWM standalone statistics collector require Solaris 2.7 or Solaris 8.

For more details on the process, refer to the documentation you received from Sun Microsystems for Solaris 7 (also known as Solaris 2.7) installation instructions.

Preparing the DiskPerform the following steps to prepare the disk for Solaris installation.

Step 1 Login to the system as the root user.

Step 2 Use the sync command to line up all the cylinders and the halt command to halt the system. As user root, type the following commands:

# sync ;sync ;halt

The system displays the ok prompt.

ok

Step 3 If Step 2 fails, as a last resort, depress the stop key and the a key simultaneously.




Solaris 2.7 Initial ConfigurationPerform the following steps to configure the installation process.

Step 1 Insert the Solaris 2.7 CD.

Step 2 At the ok prompt, enter the following command to boot the Solaris 2.7 CD:

ok boot cdrom

The installation process for Solaris 2.7 is straightforward and consists mainly of answering a series of questions as they are displayed on the screen.

Step 3 The Set Language and Locale dialog box is the first to be displayed. Select the following values in the Set Language and Locale dialog box:

Language EnglishLocale USA English (ASCII only)

Step 4 Left-click on Continue to accept your chosen values and move to the next screen.

The Solaris Installation Program banner displays.

Step 5 Read the information displayed and left-click on Continue.

The Identify This System dialog box displays.

Step 6 Read the information displayed and left-click on Continue.

The Host Name dialog box displays.

Step 7 Enter the hostname and left-click on Continue.

Note Do not begin the host name with a number or use a “-” sign in the name.

The Network Connectivity dialog box displays.

Step 8 Read the information displayed, select Yes at the Networked prompt, and left-click on Continue.

At this point, the process may prompt you for the Primary Network Interface.

Step 9 Read the information displayed, enter hme0 at the Pri Network Interface prompt, and left-click on Continue.

The IP Address dialog box displays.

Step 10 Read the information displayed, enter the IP address of the CWM workstation at the IP Address prompt, and left-click on Continue.

The Confirm Information dialog box displays. This dialog box contains all the choices you made in Steps 3 through 9.

Step 11 Carefully examine the information displayed. If you are satisfied with the information displayed, left-click on Continue.

If any values need to be changed, left-click on Change and repeat steps 3 through 10 entering any information that needs to be changed. The Confirm Information dialog box is displayed again, left-click on Continue if the information is correct or, if not, click Change and repeat the process.

The Name Service dialog box displays.

Step 12 Read the information displayed, normally, for a CWM workstation, select None at the Name Service prompt, and left-click on Continue.




Another Confirm Information dialog box displays. This dialog box contains the choice you made for Name Service in Step 12.

Examine the information displayed. If you are satisfied with the information displayed, left-click on Continue. If the Name Service needs to be changed, left-click on Change and repeat step 12 entering the correct value. The Confirm Information dialog box is displayed again. If you are satisfied with the information now displayed, left-click on Continue or, if not, click on Change and repeat the process.

At this point, the Subnets dialog box displays.

Step 13 Read the information displayed. Enter Yes at the Force Subnet Mask Choice prompt, and left-click on Continue.

The Netmask dialog box displays.

Step 14 Read the information displayed. Normally, for a CWM workstation, type in 255.255.255.0 at the Netmask prompt, and left-click on Continue.

The Time Zone dialog box displays.

Step 15 Read the information displayed. Select Geographic Region and left-click on the Set button.

The Geographic Region dialog box displays.

Step 16 Select the appropriate Geographic Region and Time Zone, and left-click on Continue.

The Date and Time dialog box displays.

Step 17 Read the information displayed, enter today’s date and the current time at the Date and Time prompt, and left-click on Continue.

Another Confirm Information dialog box displays. This dialog box contains the choices you made in Steps 13 through 17.

Note An alternative to the Geographic Region option in Step 15 is to select the Greenwich Mean Time (GMT) option. This option causes the timestamp of local messages and messages from the network to be consistent.

Step 18 Carefully examine the information displayed. If you are satisfied with the information displayed, left-click on Continue.

If any values need to be changed, left-click on Change. The Subnets dialog box displays. Re-do Steps 13 through 17, correcting any values. Once have reentered the corrected values, the Confirm Information dialog box displays, with the revised values you just entered. If you are satisfied with the information now displayed, left-click on Continue.

At this point, the first Solaris Interactive Install dialog box displays.

Step 19 Read the information displayed on the Solaris Interactive Install display, and left-click on Continue.

At this point, the second Solaris Interactive Install dialog box displays.

Step 20 Read the information displayed on the second Solaris Interactive Install display, enter Initial at the Initial Install or Upgrade prompt, and left-click on Continue.

The Allocate Client Services? dialog box displays.

Step 21 Read the information displayed, and left-click on Continue.

The Select Languages? dialog box displays.

Step 22 Read the information displayed, and left-click on Continue.

The Select Software dialog box displays.



Chapter 2 Preparing for CWM InstallationDisk Partitioning Requirements

Step 23 Read the information displayed, select Entire Distribution, and left-click on Continue.

Note Do NOT choose Entire Distribution plus OEM. Leave default for 64-bit support.

The Select Disks dialog box displays. At least two 9.1-GB disk should be displayed.

Step 24 Read the information displayed.

Step 25 Add the appropriate disk or disks (for multiple hard drives) by moving them to the Selected column, and left-click on Continue.

The Preserve Data? dialog box displays.

Step 26 Read the information displayed. Choose the default (Not Preserving data), and left-click on Continue.

The Automatically Layout File Systems? dialog box displays.

Step 27 Read the information displayed, select Manual Layout, and left-click on Continue.

The File System and Disk Layout dialog box displays.

Step 28 Read the information displayed, confirm that it is correct, and left-click on Customize…

Step 29 Proceed to the next section to partition your hard drives.

Disk Partitioning RequirementsSufficient disk space and proper disk partitioning are essential to achieving the best performance from CWM and your network management workstation. The Solaris 2.7 installation procedure continues from Step 29 with a series of screens which lead the user through the partitioning process.

Note The minimum disk space requirement for Release 11 of CWM is two, 9-GB disk drives.

Partitioning Two 9-GB DisksThis section describes how to partition a CWM workstation that has two 9-GB disk drives. When you come to the Solaris disk partition screens make sure that both disks are in selected column on the screen before you start the partitioning. Partition the first disk drive as shown in Table 2-6. Partition the second disk drive as shown in Table 2-7.

Table 2-6 Partitioning the First 9-GB Disk

Slice Partition Space Comments

s0 / 1500 MB Root partition, allocate this partition third.

s1 swap 2048 MB Swap partition, allocate this partition second, allows for 1024 MB memory, allocate double the amount of RAM for swap.

s2 <overlap> 8692 MB Total amount of space on the disk; do not attempt to modify.

s3 /opt 2000 MB Allocate this partition fourth.



Chapter 2 Preparing for CWM InstallationDisk Partitioning Requirements

Note The total space should equal the space shown in s2.

Note The total space should equal the space shown in s2.

Partitioning an 18-GB Disk

This section describes how to partition a CWM workstation that has an 18-GB disk drive. When you install Solaris, partition the disk drive as shown in Table 2-8.

s4 /var 1044 MB Variable partition that occupies the remainder of the disk; allocate this partition last.

s5

s6 /usr/users 2000 MB Must be at least 2000 MB; allocate this partition first.

s7

Table 2-7 Partitioning the Second 9-GB Disk


s0 swap 2048 MB Allocate this partition first, allows for 1024 MB memory, allocate double the amount of RAM for swap.

s1


s3 /spare 4649 MB Allocate this partition last, This partition can be used for customer use or can be used for multiple 2 GB Informix raw partitions.

s4

s5

s6

s7 1995 MB Allocate this partition second. Informix raw DB (maximum 1.995 GB, minimum 1 GB).

Table 2-6 Partitioning the First 9-GB Disk (continued)


Table 2-8 Partitioning an 18-GB Disk


s0 / 1995 MB Allocate this partition third, allows for patch downloads, etc.

s1 swap 4096 MB Allocate this partition second, allows for 2048 MB memory, allocate double the amount of RAM for swap.




Chapter 2 Preparing for CWM InstallationInstalling Solaris on the Newly-Partitioned Disk

Note If two Informix raw databases are needed, then make s6 <blank>….1995 MB.)

Installing Solaris on the Newly-Partitioned Disk

Step 1 After you have completed partitioning your disk (or disks), the Solaris installation process will prompt you to set up the file system:

The File System and Disk Layout dialog box displays.

Step 2 Read the information displayed, confirm that it is correct, and left-click on Continue.

The Mount Remote File Systems? dialog box displays.

Step 3 Read the information displayed, confirm that it is correct, and left-click on Continue to accept the default. Do not select Remote Mounts.

Step 4 The Profile screen displays. Choose Begin Installation

The Solaris installation process now asks you what kind of action it should take after installing the files:

AutoReboot/manualReboot

Step 5 Choose AutoReboot.

Note This part of the process (downloading the files) may take up to 1 hour. There is no input required.

Step 6 The Solaris installation process now displays the Set Password screen.

Step 7 Choose the option to set the root password after autoreboot.

After auto reboot set root’s password.

Step 8 The Solaris installation process prompts you to setup autoshutdown:

Shut down after 30 min?

Step 9 Choose No.

s3 /opt 3000 MB Allocate this partition fourth. Used for HPOV.

s4 /var 1611 MB Remainder of disk; allocate this partition last

s5 /usr/users 3000 MB Must be at least 2000 MB; allocate this partition first

s6 /spare 1995 MB Allocate this partition sixth, /spare or optional second informix raw DB

s7 1995 MB Allocate this partition fifth, informix raw DB (maximum 1.995 GB, minimum 1 GB)

Table 2-8 Partitioning an 18-GB Disk




Chapter 2 Preparing for CWM InstallationInstalling Solaris 2.7 Patches

Step 10 The Solaris installation process prompts you to setup multiple confirmation:

Ask again?

Step 11 Choose No

Installing Solaris 2.7 PatchesSolaris patches 106300-09, 106327-12, 106541-19, 106950-18, 106980-18, 107078-10, 107081-11, 107153-01, 107544-03, 107607-01, 107636-03, 108376-03, 109104-01, 110881-01, and 111980-01 must be installed before CWM 11 and CiscoView can be launched.

Consult the CWM release notes, they may contain a more up-to-date list of patches.

You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command. Patches can be obtained from SunService (if the user has a SunSpectrum contract) or from the SunSolve Recommended and Security Patches web site.

Patches are available to Sun Microsystems customers over the World Wide Web at this URL:www.sunsolve.sun.COM/pub-cgi/show.pl?target=home

If the search facility on the SunSolve site is used, search for the search ID number and do not include the two-digit patch version number. Patches with the highest version numbers should be used.

Note If the CWM workstation is behind a corporate firewall, it may not be possible to connect to the Internet. In this case the workstation should be removed and set to a location where an Internet connection can be made. After the patches have been downloaded, the workstation can again be located behind the firewall again.

Step 1 At the Sun Microsystems web site, click on Patch Finder.

Step 2 Under “Recommended and Security Patches” click on 7 (nn.nM), [where nn.n is a size in Mbytes,for example 7 (48.9M)].

Step 3 Download the file. The file downloads under the filename of 7_recommended.zip.

Step 4 Unzip the file on the workstation and in the newly created 7_recommended directory, enter the install cluster command.

Step 5 Install individual patches by entering the patchadd command.

First Time Login to SolarisAfter installing the Sun Solaris 2.7 operating system, perform the following steps:

Step 1 Log in to the workstation as user root. Using the Solaris Login interface, select CDE.

Step 2 Close the File Manager and Help windows, leaving only the CDE menu bar.

Step 3 Right click on the blank screen. Highlight Tools, then Terminal.



Chapter 2 Preparing for CWM InstallationCiscoView 5.4 Considerations

Move this terminal window to the upper right corner of the screen.

Step 4 Right click on the blank screen select Hosts, then select Terminal Console.

Lower the height to display four lines and move this window so that it rests above the CDE menu bar. This window provides a display of workstation system messages.

Step 5 Left-click the CDE icon labeled TTT.

The Style Manager window is displayed.

Step 6 Left-click on Screen. Click screen saver on and screen lock off. Click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes. Click OK.

Step 7 Click on Backdrop and select GrayDk, click Apply.

Do the same to all four screens, labeled One, Two, Three, and Four in the CDE icon bar. In screen Four click OK and return to screen One. This helps to conserve workstation resources.

Step 8 Click the CDE icon labeled TTT. Click Startup in the Style Manager. Click Set Home Session and click OK.

The next login session will use this same screen configuration. Click OK and close the Style Manager.

Step 9 Type eject in the Terminal Window to remove the Solaris 2.7 CD, if necessary.

CiscoView 5.4 ConsiderationsInstallation of CiscoView is simply clicking Yes to one of the CWM server screens when asked during the installation process. A standalone procedure for installing CiscoView is also available that can be used to re-install CiscoView without re-installing CWM.

Note Instructions for the standalone installation of CiscoView and for uninstalling CiscoView are included in Chapter 5.

Netscape Communicator should be installed at this point in the process. It must be installed before CWM and CiscoView are installed.

Installation of Netscape CommunicatorThe Sun Microsystems Netscape Communicator for the Solaris package (version 4.76) is included on the Cisco-provided CWM CD-ROM#2 under the filename of NSCPcom.sparc.tar.gz

Netscape Communicator should be installed before the installation of CWM and CiscoView. Netscape Communicator requires:

• 20Mbytes of free disk space

• The basic Solaris software end-user cluster (SUNWCuser) be installed.

Install Netscape Communicator using the following steps.

Step 1 Log in to the CWM workstation as user root.



Chapter 2 Preparing for CWM InstallationCiscoView 5.4 Considerations

Step 2 Insert the Cisco WAN Manager Release 11 CD-ROM # 2 into the CD-ROM drive.

Step 3 The NSCPcom.sparc.tar.gz file is located on the CD-ROM in the tools directory. You can check that it is present by changing to the tools directory and listing the files as in the following commands.

# cd /cdrom/cdrom0/110tools# ls

Note The 110 tools directory on the CD#2 also contains a copy of Adobe Acrobat Reader under the filename of sunsparc-rs-405.tar.gz. This software can be used for viewing documentation in the pdf format.

Step 4 Copy the Netscape file to the workstation hard drive.

cp /cdrom/cdrom0/110tools/NSCPcom.sparc.tar.gz /tmp

Step 5 Copy the gzip utility to the workstation hard drive.

cp /cdrom/cdrom0/110tools/gzip /tmp

Step 6 Change to the tmp directory.

cd /tmp

Step 7 Change the permission of the copied gzip file so that it can be executed.

chmod 555 /tmp gzip

Step 8 Unzip the file the Netscape Communicator file.

./gzip -d /tmp/NSCPcom.sparc.tar.gz

Note The gzip utility is a compression software tool that compresses files and assigns them the.gz suffix. Use gzip -d to decompress .gz files. In addition to being provided on CD#2, installing CWM automatically installs gzip in the usr/users/svplus/tools folder and its path is defined in the users account.

Step 9 Untar the file.

tar xvf /tmp/NSCPcom.sparc.tar

Step 10 If not already logged in as root, log in now.

myhhost% suPassword:#

Step 11 Install Netscape Communicator

pkgadd -d /tmp NSCPcom

This command installs the Netscape Communicator package in the /opt/NSCPcom directory.

Step 12 Add the /opt/NSCPcom directory to the PATH variable.

setemv PATH $PATH’:/opt/NSCPcom’

Note The instructions for uninstalling Netscape Communicator are included in Chapter 5.



Chapter 2 Preparing for CWM InstallationHP OpenView 6.2 Installation

HP OpenView 6.2 Installation HP OpenView is used in conjunction with the SNMP Service Agent and for viewing the Event Log. It is not required for any other CWM procedures. Before installing the HP OpenView 6.2 software, ensure that the Solaris 2.7 operating system software is installed.

Obtaining HP OpenView SoftwareYou can purchase the HP OpenView software via FTP (or by ordering the CD) from the Hewlett Packard external website at the following URL.

http://openview.hp.com/products/nnm/

Installing HP OpenView SoftwareTo install the HP OpenView software, complete the following steps:

Step 1 Insert the HP Openview CD-ROM into the CD-ROM drive.

Step 2 Enter the following commands:

# cd /cdrom/cdrom0# ls

Step 3 Check for the install file. Begin the install process by entering the following command:

# ./install

Step 4 Reply to the following questions that will be displayed during the installation process:

Install man pages? y

Install on line manuals n

Discover network? y

snmp string default gateway? s

display interface? n

Web browser? s

continue? y

No further interaction is required. You should see the Install Successful!! message.

Setting Up CWM to HP OpenView CommunicationAll the libraries in HP OpenView are shared libraries. In order to get CWM and ovw communicating properly, you need to configure the LD_LIBRARY_PATH with the following commands:

If you are using the Korn shell, enter the following commands as root:

# LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/OV/lib# export LD_LIBRARY_PATH



Chapter 2 Preparing for CWM InstallationWingz Version 2.5.1 Installation

If you are using the C shell, enter the following command as root:

# setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/opt/OV/lib

Check the /etc/services FileExamine the /etc/services file, and check to see if an entry exists for snmp 8161/udp. Enter the following command:

# more /etc/services

If an entry exists for snmp 8161/udp, change it to the following value:

snmp 161/udp

Note To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.

If you changed the /etc/services file, you must reboot the CWM workstation for the changes to take effect. Enter the following command:

# sync ;sync ;reboot

Starting HP OpenViewTo start HP OpenView, you must have installed the CWM software and the optional CWM SNMP Service Agent software (see Chapters 3 and 6 for details). Complete the following steps to start HP OpenView.

Step 1 Open a terminal window as user svplus.

Step 2 Enter the following command:

hostname% ovw &

Step 3 When the root map is displayed, double-click on the StrataCom icon.

Step 4 Drag the nodes from the holding area to the map.

Step 5 Minimize the root map, move the Event Categories window to the lower left of the screen.

Step 6 To download from the HPOV StrataCom map, choose node > StrataCom > Image Download.

Step 7 Locate the image and highlight it. Click Download. The results of the action are displayed.

Wingz Version 2.5.1 Installation Solaris 2.7 should be installed before installing the Wingz package. If you are installing the optional HP OpenView package, install it before installing the Wingz package.

Step 1 Log in as root.

Step 2 Insert the Wingz 2.5.1 CD into the drive.




Step 3 Access the CD by entering the following commands:

# cd /cdrom/cdrom0#./Install.sh

The following prompts appear:

Appear to be using Solaris 2.7 (5.7)Install product for platform?

Step 4 Enter y to begin installing the product from the CD.

Step 5 Choose the appropriate Wingz product to install. A menu of installation choices appears as well as the following prompt:

Choose product

Step 6 Select Item 2, Wingz for Solaris 2.7 by entering 2.

The installation process prompts you to confirm your choice:

Install Wingz for Solaris 2.7 (5.7)

This is the correct product, so enter y to confirm use of Solaris 2.7.

Step 7 The next step is to choose the appropriate Wingz package to install. A menu of installation choices appears as well as the following prompt:

Choose package

Step 8 Select Item 1, Install All (install the entire Wingz package for Solaris 2.7) by entering 1.

Step 9 The next step is to choose a path on the workstation disk in which to install the files. The installation process prompts you to enter a path by displaying the following prompt:

To be installed in

Step 10 The path is /usr/users/Wingz. Enter /usr/users/Wingz at the prompt:

The installation process prompts you to confirm the path you entered:

/usr/users/Wingz?

This is the correct path. Enter y to confirm that the path is /usr/users/Wingz.

Step 11 After the Wingz files are copied from the CD to the /usr/users/Wingz path on the workstation hard disk, the Wingz software needs to be branded (basically licensing the software for your use).

Branding consists of the following steps.

a. The installation process prompts you to enter the Wingz serial number:

Enter serial number>

b. Enter the serial number (obtained from the paper shipped with Wingz 2.5.1).

c. Next, the installation process prompts you to enter the Wingz license key:

Enter key>

d. Enter the Wingz license key (obtained from the paper shipped with Wingz 2.5.1).

e. Next, the installation process prompts you to enter the Wingz product number:

Enter Product Number>

f. Enter the Wingz product number (obtained from the paper shipped with Wingz 2.5.1).




g. Once the correct branding numbers are entered, the installation process displays the following confirmation message:

Brand successful.

At this point, the installation process returns to the package menu. The installation of Wingz 2.5.1 is complete.

Step 12 Select Item 6 for Exit (exit the Wingz package menu and return to the Solaris 2.7 Unix prompt) by entering 6.

Step 13 Exit the install process. Eject the CD by entering the following commands:

# cd /# eject

C H A P T E R



3Installing CWM Server Software

This chapter provides a step-by-step procedure to install the CWM Release 11 and CiscoView Release 5.4 software on a CWM server workstation. The CWM Release 11 software installation process uses InstallShield to simplify the process.

Before installing the CWM Release 11 software on the CWM workstation, the following software should have already been installed (in the following order):

• Solaris 2.7 Operating System

• Solaris patches (see the release notes for the latest list of patches)

• Netscape Communicator 4.76 or later (for CiscoView 5.4)

• HPOV 6.2

• Wingz 2.51

Refer to Chapter 2 for instructions on installing these products.

Installing CWM Software To install the CWM Release 11 software, perform the following steps:

Note The windows in this section reflect a single disk install. Areas where choices differ for a multi-disk install are called out in the procedure.

Step 1 Login to the CWM workstation as user root.

Step 2 Insert the Cisco WAN Manager Release 11 CDROM #1 into the CDROM drive.



Step 4 Check for the InstallCWM.sh file, begin the install process by entering the following command:

# ./InstallCWM.sh

The installation classes are loaded (a process that takes several minutes). The CWM Installation Welcome window is displayed, as shown in Figure 3-1.



Chapter 3 Installing CWM Server SoftwareInstalling CWM Software

Figure 3-1 CWM Installation Welcome Window

Step 5 Click Next on the Welcome window to continue.

The README Information window, Figure 3-2, is displayed.




Figure 3-2 CWM Installation README Information Window

Step 6 After reading the information presented on the information window, click Next.

The Information about the Upgrade Procedure window is displayed, as shown in Figure 3-3.




Figure 3-3 Information About the Upgrading Procedure Window

Step 7 At the Information About the Upgrading Procedure window, accept the default No and click Next.

The Auto-Partition Disks window is displayed, as shown in Figure 3-4.

Figure 3-4 Auto-Partition Window




Step 8 At the Auto-Partition Disks window, accept the default No and click Next.

The Meta Devices window is displayed, as shown in Figure 3-5.

Figure 3-5 Meta Devices Window

Step 9 At the Meta Devices window, unless you have meta devices to configure, accept the default No and click Next.

Note A meta device is a virtual device created by concatenating or striping disk partitions (usually to improve performance).

The Multiple Disk Configuration for Informix window is displayed, as shown in Figure 3-6.

Figure 3-6 Multiple Disk Configuration for Informix Window




Step 10 At the Multiple Disk Configuration for Informix window, if you have one disk accept the default No and click Next. If you have two disks, click on the Yes radio button and then click Next to continue.

The Select the Raw Partition for CWM Database window is displayed, as shown in Figure 3-7.

Figure 3-7 Select the Raw Partition for CWM Database Window

Step 11 Select the partition to be used for the database.

In this release of CWM, the database name cannot be changed, accept the default name of stratacom.

Note If you have multiple hard disks configured, more partitions will be displayed than those shown in Figure 3-7.

A small window is displayed warning the user that the selected partition must be at least 1 GByte in size (see Figure 3-8).

Figure 3-8 Minimum Space Warning

Step 12 Check the size of the partition, if the size is not large enough click Cancel, change the partition size and restart the installation process. If the size is large enough, click OK and then click Next in the main window.

When Next has been clicked, the CWM FTP Information window is displayed as shown in Figure 3-9.




Figure 3-9 CWM FTP Information Window

Step 13 At the CWM FTP Information window, enter the user name (default "svplus") and the password of the user on the machine.

Note In this release, the user name of "svplus" must be used and cannot be changed.

After entering the FTP user name and password, click Next.

The Choose Destination Directory window is displayed, as shown in Figure 3-10.

Figure 3-10 Choose Destination Directory Window




Accept the default destination directory of usr/users/svplus and click Next.

Although the destination directory is editable, this release supports only the default directory.

The Install Orbix window is displayed, as shown in Figure 3-11.

Figure 3-11 Install Orbix Window

Orbix is the software component that provides the communication capability between CWM gateways.

Step 14 At the Install Orbix window, accept the default Yes and click Next.

The Enter Domain Name window is displayed as shown in Figure 3-12.

Note This domain name is for database purposes only and has nothing to do with DNS.




Figure 3-12 Enter the Domain Name Window

Step 15 At the Enter the Domain Name window, enter the domain configured for the workstation.

This information allows the CWM client workstations access to the database. Also ensure that the workstation and the domain is reachable. You can enter the ping command to test this.

The only reason to leave the Domain Name field empty (or blank) would be for a standalone CWM server never to have client workstations.

After entering the domain name, click Next. The Install CiscoView window is displayed, as shown in Figure 3-13.

Figure 3-13 Install CiscoView Window




Note Remember that certain Solaris patches are required for CiscoView 5.4, see Chapter 2 and the CWM Release 11 release notes for the latest details.

Step 16 Either select Yes to install CiscoView or select No if CiscoView is not to be installed. Click Next.If Yes is selected, the Enter CiscoView home window is displayed as shown in Figure 3-14.

Caution Do not install CiscoView over a previously installed CiscoView, this action will cause two versions of CiscoView to exist and the system will not operate properly.If CiscoView is installed (from a previous installation) either select No and Continue or go back, uninstall CiscoView, restart the install process, and select Yes at the CiscoView window.

Figure 3-14 Enter CiscoView Home Window

Step 17 At the Enter CiscoView Home window, either click Install to accept the default directory (/opt) or enter a new directory name and then click Install.

The software installation process begins. This process will take from 30 to 60 minutes depending on the speed and resources of the CWM workstation. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 3-15.

A small log window is also displayed showing entries to the install log as they are entered.




Figure 3-15 Installation Progress Indicator (extracting files)

If the CWM system was installed previously, a message appears telling the user that files already exist and permission is requested to overwrite the files with new files. This message is shown in Figure 3-16. Click Yes to All.

Figure 3-16 Copy Files Message

After extracting the necessary CWM program files, the window refreshes and the installation process begins creating and configuring the database. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the database creation process, as shown in Figure 3-17.




Figure 3-17 Installation Progress Indicator (database creation)

An Install Log window is also displayed (see Figure 3-18).

Figure 3-18 Install Log

A dialog box displays informing you that the installation is complete, as shown in Figure 3-19.




Figure 3-19 Installation Complete Window

Step 18 Click Finish on the dialog box.

The software installation process is completed. The Install Shield window closes.

The first time (and only the first) that CWM is installed, the system will display a message stating that the kernel has been changed. Click OK to reboot the system

The reboot sequence aligns the cylinders of your hard disks and gracefully shuts down the Solaris operating system.

Step 19 At this point, you can push the CDROM eject button on the CDROM drive to eject the installation CD.

Note When CWM is installed, the tasks can be checked by displaying the contents of the InstallShield.log file under usr/users/svplus/log. This log displays the installation tasks that were completed and lists any errors encountered during the installation.



Chapter 3 Installing CWM Server SoftwarePost Installation Tasks

Post Installation TasksAfter the CWM installation is complete the following configuration tasks should be completed.

If you haven’t already done so eject the CWM CD-ROM by entering the eject command in the terminal window.

First Time Login as User svplusAfter completing the CWM Release 11 software installation, perform the following steps when you log in to CWM as user svplus.

Step 1 Log in to the workstation as user svplus using the Solaris Login interface.

Step 2 Select CDE.


Step 4 Right-click on the blank screen, select Tools, select Terminal.


Step 5 Right click on blank screen select Hosts, select Terminal Console.




Step 7 Left click on the Screen, click screen saver on and screen lock off. Click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK.

Step 8 Click on Backdrop and select GrayDk. Click Apply.

Do the same to all four screens,. They are labeled One, Two, Three and Four in the CDE icon bar. In Four click OK and return to screen One. This action helps to conserve workstation resources.

Step 9 Click on the CDE icon labeled TTT. Click Startup > Set Home Session > OK.

The next login session will come up using this same screen configuration. Click OK and close the Style Manager.

Step 10 Place the cursor in the terminal window. Enter vi to edit the network.conf file.

% cd /usr/users/svplus/config% vi network.conf

Step 11 Modify the network.conf file depending on your network requirements.

Note When using the vi Editor, remember to write your changes before quitting: press Esc, colon (:), then wq!




Checking the CWM Server File SystemAt the CWM workstation, log in as user root, and examine the following files.

• /etc/hosts

• /etc/netmasks

• /etc/rs2.d/S72inetsvc

• /etc/defaultrouter

• /usr/users/svplus/.cshrc

• /usr/users/svplus/network.conf

• /usr/users/svplus/config/CWMGateway.conf

• /system

• /etc/system

Note The IP addresses shown are examples. Use addresses relevant to your network.

/etc/hosts

Examine the /etc/hosts file and check that the file contains a nodename and IP address for all nodes. The IP address should be one that CWM can use for network discovery (see following paragraphs). Enter the correct nodenames and addresses for any missing nodes.

To view the /etc/hosts file, enter the following command:

host% more /etc/hosts

Use vi Editor to enter items into the file.

IPX and MGX (Rel 1.x, 2.0 and up to 2.1.60) Nodes

For each node:

Enter the ATM0 or NWIP address and the node name.

Enter the LnPci0 or LANIP address and the nodename followed by an identifier such as -l, or -lan).

Example:

172.70.207.9mgx1192.0.0.9mgx1-l

MGX (Rel 2.1.70 and above) Nodes

For each node:

Enter the IP address used in option 8 of the cnfndparms command. This address can be displayed at the node by entering the dspndparms command.

Example:

172.70.209.9mgx4




BPX Nodes

For each node:

Enter the node’s IP address and the node name.

Example:

192.0.0.8bpx1

Example Host File

As an example, a hosts file might look like the following example:

# MGX Rel 1, 2.0, up to 2.1.60 nodes172.70.207.9mgx1192.0.0.9mgx1-l172.70.207.6mgx2192.0.0.6mgx2-l172.70.207.4mgx3192.0.0.4mgx3-l##MGX Rel 2.1.70 and up nodes172.70.209.9mgx4172.70.209.8mgx5172.70.209.7mgx6172.70.209.6mgx7##BPX nodes192.0.0.8bpx1192.0.0.9bpx2192.0.0.10bpx3

/etc/netmasks

Examine the /etc/netmasks file for all subnet and netmask entries. To view the /etc/netmasks file, enter the following command:

host% more /etc/netmasks

/etc/rc2.d/S72inetsvc

Examine the /etc/rc2.d/S72inetsvc file to ensure that the IP relay address points to the gateway node. To view the /etc/rc2.d/S72inetsvc file, enter the following command:


Use the vi Editor to open the S72inetsvc file and find the following line:

/usr/sbin/route add -interface -netmask “224.0.0.0” “224.0.0.0” “$mcastif”)&

Add the following line directly below that line

/usr/sbin/route add net 10.10.10.0 209.165.200.225 1 (use your site’s valid IP addresses)

Note When using the vi editor, remember to write your changes before quitting: press Esc, colon (:), then wq!




/etc/defaultrouter

Examine the /etc/defaultrouter file. To view the /etc/defaultrouter file, enter the following command:

host% more /etc/defaultrouter

Note If this file does not exist, use the vi Editor to create a new file with the name defaultrouter.

If the router IP address is not currently in the file, use the vi Editor to add a line containing the IP address of the default router to which the CWM workstation is attached.


usr/users/svplus/.cshrc

Use the vi editor to modify .cshrc as follows:

vi usr/users/svplus/.cshrc

Change the line:setenv PATH$ORBIXROOT/bin:$PATH tosetenv PATH$ORBIXROOT/bin:/opt/NSCPcom:$PATH

Add the following lines to the end of the file.

setenv PATH “netscape path”:$PATHsetenv MOZILLA_HOME “netscape path”Exit vi.

svplus/config/network.conf file

The network.conf file is located in the /usr/users/svplus/config directory.

The user should modify this file to specify networks parameters for each network to be discovered and managed.This file can describe multiple networks where each network can be any one of the following types.

• AutoRoute

• PNNI

• Hybrid (consisting of AutoRoute and PNNI segments)

For each network specified in the network.conf file, its entry consists of the following fields.

• NETWORK (this must be the first field)

• NETWORK ID

• GATEWAYS

• DISCOVERY PROTOCOL

• IP REACHABILITY FLAG




• OPTIONS

NETWORK

The NETWORK field has the following format.

NETWORK: <Network Name>

When describing a network’s parameters, NETWORK must be the first parameter.

The Network name cannot have more than 10 characters and cannot contain a space.

Note Long network names are truncated to 10 characters and invalid names are ignored.

NETWORK ID

The NETWORK ID field has the following format.

NETWORK_ID: <Network ID>

Network ID is optional. If it is specified, the Network ID must be a unique numeric value in the range in [1, 32000].

Note After Network ID is modified, a CWM cold start is needed.

GATEWAYS

The GATEWAYS field has the following formats.

GATEWAYS: <Gateway Name(s)> (used for AutoRoute and PNNI).

AR-GATEWAYS: <Gateway Name> (used for AutoRoute segments in a Hybrid network type).

PNNI-GATEWAYS: <Gateway Name(s)> (used for PNNI segments in a Hybrid network type).

The user should enter the name(s) of any gateways that CWM is to use for network discovery.

The rules for gateways parameters depend upon the network type.

AutoRoute

Use the GATEWAYS: <Gateway Name> format and specify one (and only one) network node to be used as the AutoRoute gateway.

PNNI

Use the GATEWAYS: <Gateway Name> format and specify one or more network nodes to be used as PNNI gateways. If more than one gateway is specified for the network, the names should be separated by commas.

Hybrid

This field is used to specify which gateways should be used for the AutoRoute and PNNI segments of the network.

Use the PNNI-GATEWAYS: <Gateway Names> format to specify one or more network nodes to be used as PNNI gateways. If more than one gateway is specified for the PNNI segment, the names should be separated by commas.

Use the AR-GATEWAYS: <Gateway Names> format and specify one (and only one) network node to be used as an AutoRoute gateway.




Note If either AR-GATEWAYS or PNNI-GATEWAYS is specified for the network, the other gateway entry (PNNI-GATEWAYS or AR-GATEWAYS as the case may be) can be omitted. However, specifying both types of gateway speeds up the discovery process and is recommended.

.DISCOVERY PROTOCOL

This field is used to specify the network type and has the following format.

DISCOVERY PROTOCOL: <Protocol Name>

The Protocol Name can be either AUTOROUTE or PNNI or HYBRID.

AUTOROUTE is used to discover Auto Route networks .

PNNI is used for ILMI or PNNI discovery of PNNI networks.

HYBRID is used to discover networks that contain both AutoRoute and PNNI segments.

IP REACHABILITY FLAG

The IP REACHABILITY FLAG field is used to specify which IP address method is to be used for managing network nodes. This field is used for AutoRoute networks and Hybrid AutoRoute segments only. It is ignored for PNNI networks or segments.The IP REACHABILITY FLAG field has the following format.

IP REACHABILITY FLAG:<Ip Flag>

IP Flag can be set to NWIP_ON or NWIP_OFF or LANIP.

NWIP_ON — All the routing nodes in the network are managed using their nw ip addresses.

NWIP_OFF — All the routing nodes in the network are managed through the Gateway. The Gateway then routes packets to the individual routing nodes on the corresponding routing trunks.

LANIP — All the nodes in the network are managed using Lan IP. The AUTOROUTE Gateway node is always managed using the LAN IP. By specifying “LANIP”, all management traffic (including link0/link1, snmp and tftp) is sent to each node (routing node or feeders) using their Lan IP addresses.

If NWIP is set to ON or OFF, management messages use the managed network for delivery and are therefore considered to be in-band. A setting of LAN IP, on the other hand, uses a separate LAN (or LAN emulation) network for message delivery and is therefore considered to be out-of-band.

OPTIONAL

The OPTIONAL field is used to specify a number of options associated with the IP REACHABILITY FLAG and has the following format.

OPTIONAL: “List of Parameters for Auto Route Networks”

This field is mandatory for AutoRoute networks and AutoRoute segments in Hybrid networks. If this field is not specified, Auto Route networks and segments WILL NOT be discovered

OPTIONAL does not apply for PNNI networks and is ignored.

The OPTIONAL field has five sub-fields (options) as follows:

• TIMEOUT

• RETRANSMIT

• THROTTLE




• ACKNOWLEDGE

• BLOCKSIZE

TIMEOUT

Link timeout value. The amount of time to wait before resending a message to an Cisco IGX 8400 and Cisco BPX 8600 when a response is not received. Default value is 7.

RETRANSMIT

Link retry count. The number of times CWM will retransmit a message before it declares the link down. Default value is 6.

THROTTLE

Download throttling timeout value. Default value is 0

ACKNOWLEDGE

ACK timeout value used during the download process. When an acknowledgment to a configuration message sent to an Cisco IGX 8400, or Cisco BPX 8600 is not received within this time period, the message is sent again. Default value is 30.

BLOCKSIZE

Block size used for an Cisco IGX 8400, or Cisco BPX 8600 configuration upload. Default value is 1024.

Note In this release the default values must not be changed.

Network.conf Examples

1. Discover an AutoRoute Network

NETWORK:Network1

GATEWAYS:B8650_SJ

DISCOVERY PROTOCOL:AUTOROUTE

IP REACHABILITY FLAG:NWIP_ON

OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

2. Discover a PNNI network

NETWORK:Network2

GATEWAYS:M8850_LA

DISCOVERY PROTOCOL:PNNI

Note PNNI networks do not need IP REACHABILITY and OPTIONAL parameter

3. Discover a HYBRID Network

#NETWORK:Network3

#PNNI-GATEWAYS:M8850_LA, M8850_CH




#AR-GATEWAYS:B8650_LA

#DISCOVERY PROTOCOL:HYBRID

#IP REACHABILITY FLAG:NWIP_ON

#OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

CWM Gateway Configuration File

If the upgraded CWM workstation is part of a multiple CWM gateway configuration, check the CWMGateway.conf file and ensure that the DomainGatewayList contains all the stations in the Gateway domain.

For example:

host% cd usr/users/svplus/confighost% more CWMGateway.conf

Check the DomainGatewayList portion of this file.

## Default: DomainGatewayList## Usage: DomainGateWayList tmonda dilbag sgharatDomainGatewayList CWM1 CWM2 CWM3

In this example, CWM1, CWM2, and CWM3 are the names of the CWM gateways.

/system

Change directory to /system and enter the ls command. Check to see that all required HPOV PSOV_XXXXX patches have been installed.

# cd /system# ls

/etc/system

Check to see that the CWM installation process added the semaphores required for Solaris and HP OpenView operability

(set semsys:seminfo_semmsl=30).

forceload: sys/shmsysforceload: sys/semsysset semsys:seminfo_semaem=16384set semsys:seminfo_semmap=66set semsys:seminfo_semmni=4096set semsys:seminfo_semmns=4096set semsys:seminfo_semmnu=4096set semsys:seminfo_semume=64set semsys:seminfo_semvmx=32767set semsys:seminfo_semmsl=30set shmsys:shminfo_shmmax=268435456set shmsys:shminfo_shmmin=100set shmsys:shminfo_shmmni=100set shmsys:shminfo_shmseg=100




Reboot the Workstation

After completing the configuration, reboot the workstation.


C H A P T E R



4Upgrading CWM Software

This chapter provides step-by-step procedures to upgrade your CWM server workstation software. The software upgrade process of CWM Release 11 uses InstallShield to simplify the process.

This chapter describes the following two upgrade scenarios:

• Upgrading to the latest release of CWM Release 11 Software from an earlier 10 release.

• Upgrading to the latest release of CWM Release 11 Software from an earlier 10 release with multiple CWM gateways.

Note You can upgrade your software to the CWM Release 11 release only if your workstation is currently running CWM 10.4 with patch 2, or CWM 10.5.10 with patch 1 software.

Caution Service Class Template (SCT) configurations are not preserved during the CWM 10.x to 11 upgrade process.

Upgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release

To upgrade to the CWM Release 11 from releases 10.4, or 10.5 complete the following steps:

Step 1 Ensure that the requisite Solaris 2.7 patches are installed. See Chapter 1 and release notes for details.

Step 2 Log in as user svplus.

Step 3 Stop the CWM core processes.

Step 4 Log in to the CWM workstation as user root

Step 5 Insert the Cisco WAN Manager Release 11 CD#1 into the CDROM drive.



Step 7 Check for the InstallCWM.sh file and begin the install process by entering the following command:

# ./InstallCWM.sh



Chapter 4 Upgrading CWM SoftwareUpgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release

The CWM Installation Welcome window is displayed, as shown in Figure 4-1.

Figure 4-1 CWM Installation Welcome Window

Step 8 Click Next on the welcome window to continue.

The README Information window is displayed (see Figure 4-2).




Figure 4-2 CWM Installation README Information Window

Step 9 After reading the information presented on the README Information window, click Next.

The Information About the Upgrading Procedure window is displayed, as shown in Figure 4-3.




Figure 4-3 Information About the Upgrading Procedure Window

Step 10 At the Information About the Upgrade Procedure window, select Yes and click Next.

Figure 4-4 Upgrade Information

Step 11 When the Upgrade Information window is displayed, click OK

The CWM role in the CWM domain for CWM CWM Communication window is displayed, as shown in Figure 4-5. This window is displayed only if upgrading from 10.4 or 10.5.10, otherwise it is skipped.




Figure 4-5 CWM role in the CWM domain for CWM CWM Communication Window

Step 12 Select either Primary or Secondary for the CWM station being upgraded.

If Secondary is selected, the window is refreshed and the user is requested to enter the name of the Primary station as shown in Figure 4-6. This window is displayed only if upgrading from 10.4, otherwise it is skipped.

Figure 4-6 CWM role in the CWM domain for CWM CWM Communication Window 2

Step 13 Enter the name of the primary CWM machine.

Step 14 Click Next.

The Auto-Partition Disks window is shown in Figure 4-7.




Figure 4-7 Auto-Partition Disks Window

Step 15 At the Auto-Partition window, accept the default No and click Next.

The Meta Devices window is displayed, as shown in Figure 4-8.


Step 16 At the Meta Devices window, accept the default No and click Next.







Step 17 At the Multiple Disk Configuration for Informix window, accept the default No if you have one disk, click on Yes If you have two disks. Click Next to continue.

The Select the Raw Partition for CWM Database window is displayed, as shown in Figure 4-10.

Figure 4-10 Select the Raw Partition for CWM Database

Step 18 In the Select the Raw Partition for CWM Database window, accept the default name of stratacom, by clicking Next. In this release of CWM, the partition cannot be changed

Note If you have multiple hard disks configured, more partitions may be displayed than those shown in Figure 4-10.

A small window is displayed warning the user that the selected partition must be at least 1 GBytes in size (see Figure 4-11).




Figure 4-11 Minimum Space Warning

Step 19 Check the size of the partition, if the size is not large enough click Cancel, change the partition size and restart the installation process. If the size is large enough, click OK and then click Next in the main window.

When Next has been clicked, the CWM FTP Information window is displayed as shown in Figure 4-12.

Figure 4-12 CWM FTP Information Window

Step 20 At the CWM FTP Information window, enter the user name (default “svplus”) and the password of the user on the machine.

After entering the FTP user name and password, click Install.

The Choose Destination Directory window is displayed, as shown in Figure 4-13.

Note This window may or may not be displayed depending upon whether a suitable destination directory already exists.





Step 21 If this window is displayed, click Next.

In this release of CWM, the destination directory cannot be changed.





The Enter Domain Name window is displayed as shown in Figure 4-15.





Step 23 At the Enter the Domain Name window, enter the domain configured for the workstation.

This information allows the CWM client workstations access to the database. Also ensure that the workstation and the domain is reachable. You can enter the ping command to test this.

The only reason to leave the Domain Name field empty (or blank) would be for a standalone CWM server that would never have client workstations.

Step 24 After entering the domain name, click Next.

The Install CiscoView window is displayed, as shown in Figure 4-16.

Figure 4-16 Install CiscoView Window




Note The requested patches for CiscoView (106327-05, 106980-10, 107081-11, 107636-03, and 108376-03) should be installed after installing Solaris 2.7.

Patches are available to Sun Microsystems customers over the World Wide Web at this URL.

www.sunsolve.sun.com.

You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command.

Either select Yes to install CiscoView or No if CiscoView is not to be installed, and then click Next.

If Yes is selected, the CiscoView home window is displayed as shown in Figure 3-14.

Caution Do not install CiscoView over a previously installed CiscoView, this action will cause two versions of CiscoView to exist and the system will not operate properly.If CiscoView is installed (from a previous installation) either select No and Continue or go back, uninstall CiscoView, restart the install process, and select Yes at the CiscoView window.

Figure 4-17 Enter CiscoView Home Window

Step 25 At the Enter CiscoView Home window, either click Install to accept the default directory (/opt) or enter a new directory name and click Install.




The software installation process begins. This process takes from 30 to 60 minutes depending on the speed and resources of the CWM workstation. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 4-18.

A small log window is also displayed showing entries to the install log as they are entered.


If the CWM system was installed previously, a message appears telling the user that files already exist and requesting permission to overwrite the files with new files. This message is shown in Figure 4-19. Click Yes to All.

Figure 4-19 Copy Files Message

After extracting the necessary CWM program files, the window refreshes, and the installation process begins creating and configuring the database. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the database creation process, as shown in Figure 4-20.





An Install Log window is also displayed (see Figure 4-21)

Figure 4-21 Install Log




Chapter 4 Upgrading CWM SoftwareUpgrading to the CWM 11 Software from Release 10.4 or 10.5.10 with Multiple CWM Gateways



Doing so ends the software installation process is completed. The Install Shield window closes.

Step 27 At this point, you can push the CD-ROM eject button on the CD-ROM drive to eject the installation CD.

The first time (and only the first) that CWM is installed, the system will display a message stating that the kernel has been changed. Click OK to reboot the system

The reboot sequence aligns the cylinders of your hard disks, gracefully shuts down, and restarts the Solaris operating system.

When the upgrade is finished, the contents of the scmtemplate table are stored in /usr/users/svplus/SAVE/ under the filename scmtemplate.

Upgrading to the CWM 11 Software from Release 10.4 or 10.5.10 with Multiple CWM Gateways

When upgrading from a network in which there are multiple CWM gateways, a special sequence of steps needs to be followed. This procedure ensures that, at all times, there is one and only one master CWM in a CWM domain and that the integrity of the network configuration and user data files is maintained.

Initial Conditions before UpgradeConsider an example network that has three Release 10.5.10 CWM gateways (named A, B, and C), all in the same domain. The gateways consist of one master and two secondaries. All gateways are up and running, all are synced with the network configuration and user data.




Note Although this example uses a network with three CWM stations, the same procedure can be extended to a network using any number of stations. The same procedure is also used if the three CWM stations are running CWM 10.4

In release 10.4, 10.5, and 11, the first CWM station to be started is automatically assigned the role of primary station. The second station to be started becomes a secondary station with priority 1. Subsequent stations also become secondary stations with priorities of 2, 3, and so on. To ensure such a primary/secondary arrangement, the DomainGatewayList field in the CWMGateway.conf file for all three CWM stations must list all CWM gateways.

As shown in Figure 4-23, CWMA station is primary and stations CWMB and CWMC are secondary with priorities of 1 and 2 respectively. The CWMGateway.conf field for all three gateways contains the following entry:

DomainGatewayList CWMA CWMB CWMC

Figure 4-23 Initial State of CWM Gateways

Upgrade ProcedureThe following steps upgrade the stations, one by one, to Release 11.

Step 1 Stop the CWM core process for CWMA

This action causes CWMB to assume the role of primary and CWMC the role of secondary priority 1.

Step 2 Use InstallCWM.sh to upgrade CWMA to release 11 as described in the previous section. Use the Primary/Secondary select window to select CWMA as primary.

Step 3 Start the CWM core process for CWMA.

CWMA starts as primary but in a different gateway domain.

The new states of the three CWM stations are shown in Figure 4-24.

Figure 4-24 State of CWM Gateways after Step 3

Step 4 Stop the CWM core process for CWMB

This action causes CWMC to assume the role of primary.

Step 5 Use InstallCWM.sh to upgrade CWMB to release 11.

CWMA 10.5.10Primary

DomainGatewayList = A,B,C

CWMB 10.5.10Secondary Pri 1


CWMC 10.5.10Secondary Pri 2


CWMA 11Primary

DomainGatewayList = A

CWMB 10.5.10Primary


CWMC 10.5.10Secondary Pri 1





When requested, use the Primary/Secondary select window to select CWMB as secondary and CWMA as primary.

Step 6 Start the CWM core process for CWMB.

CWMB starts as secondary priority 1 in the same domain as CWMA.



Step 7 Stop the CWM core process for CWMC.

Step 8 Use InstallCWM.sh to upgrade CWMC to release 11.

When requested, use the Primary/Secondary select window to select CWMC as secondary and CWMA as primary.

Step 9 Start the CWM core process for CWMC.

CWMC starts as secondary priority 2 in the same domain as CWMA and CWMB.



Step 10 At this point, all three gateways are operating in the initial state except that they have all been upgraded to Release 11.

The user must now update the DomainGatewayList in the CWMGateway.conf file for all three gateways to include CWMA, CWMB, and CWMC. In this way the gateways will be part of the same gateway domain when their cores are next restarted.

CWMA 11Primary


CWMB 11Secondary Pri 1

DomainGatewayList = A,B

CWMC 10.5.10Primary


CWMA 11Primary


CWMB 11Secondary Pri 1

DomainGatewayList = A,B

CWMC 11Secondary Pri 2

DomainGatewayList = A,C



Chapter 4 Upgrading CWM SoftwarePost Installation Tasks

Post Installation TasksAfter the CWM installation is complete the following configuration tasks should be completed.

If you haven’t already done so, eject the CWM CD-ROM by entering the eject command in the terminal window.

First Time Login as User svplusAfter completing the CWM Release 11 software installation, perform the following steps when you log in to CWM as user svplus.


Step 2 Select CDE.


Step 4 Right-click on the blank screen, select Tools, select Terminal.


Step 5 Right click on blank screen select Hosts, select Terminal Console.




Step 7 Left click on the Screen, click screen saver on and screen lock off. Click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK.


Do the same to all four screens,. They are labeled One, Two, Three and Four in the CDE icon bar. In Four click OK and return to screen One. This action helps to conserve workstation resources.

Step 9 Click on the CDE icon labeled TTT. Click Startup > Set Home Session > OK.


Step 10 Place the cursor in the terminal window. Enter the vi Editor to edit the network.conf file.

% cd /usr/users/svplus/config% vi network.conf

Step 11 Modify the network.conf file depending on your network requirements.

Note When using the vi Editor, remember to write your changes before quitting: press Esc, colon (:), then wq!




Checking the CWM Server File SystemAt the CWM workstation, log in as user root, and examine the following files.

• /etc/hosts

• /etc/netmasks






• /system

• /etc/system


/etc/hosts






For each node:



Example:

172.70.207.9mgx1192.0.0.9mgx1-l


For each node:


Example:

172.70.209.9mgx4




BPX Nodes

For each node:


Example:

192.0.0.8bpx1

Example Host File



/etc/netmasks














/etc/defaultrouter















• AutoRoute

• PNNI




• NETWORK ID

• GATEWAYS






• OPTIONS

NETWORK






NETWORK ID





GATEWAYS







AutoRoute


PNNI


Hybrid








.DISCOVERY PROTOCOL















OPTIONAL






• TIMEOUT

• RETRANSMIT

• THROTTLE




• ACKNOWLEDGE

• BLOCKSIZE

TIMEOUT


RETRANSMIT


THROTTLE


ACKNOWLEDGE


BLOCKSIZE





NETWORK:Network1

GATEWAYS:B8650_SJ





NETWORK:Network2

GATEWAYS:M8850_LA




#NETWORK:Network3











For example:





/system


# cd /system# ls

/etc/system













C H A P T E R



5CiscoView, Netscape, and the Java Plug-in

CiscoView 5.3 can be installed either during the CWM server Installation procedure (see Chapter 3 for details) or independently using a standalone Cisco provided script. Once installed, CiscoView 5.3 can be launched from CWM 11 provided the Java Plug-in 1.3.1 has been installed. Details of how CiscoView 5.3 can be launched from within CWM 11 are described in the Cisco WAN Manager User’s Guide, Release 11.

This chapter describes how to:

• install Java Plug-in

• install CiscoView 5.3 using the standalone method

• uninstall CiscoView 5.3

• uninstall the Java Plug-in

• uninstall Netscape Communicator

Note Solaris patches 106327-12, 107081-11, 107636-03, and 108376-03 must be installed before CiscoView can be launched.

Installing the Java Plug-in 1.3.1 on SolarisRunning CiscoView 5.3 from Netscape Communicator requires that a Java 1.3.1 Plug-in be installed.

The Java Plug-in is included in CDROM #2 and should be installed using the following procedure.

Step 1 Log in to the CWM workstation as user root, and insert the Cisco WAN Manager Release 11 CD-ROM # 2 into the CD-ROM drive.

Step 2 The j2re-1_3_03-solsparc.sh file is a script for installing the Java Plug-in and is located on the CD-ROM in the tools directory. You can check that it is present by changing to the tools directory and listing the files as in the following commands.


Step 3 Copy the script file to a directory on the workstation hard drive (for example, /opt).

cp /cdrom/cdrom0/110tools/j2re-1_3_03-solsparc.sh /opt

Step 4 Change to the directory containing the script file (for example, /opt).



Chapter 5 CiscoView, Netscape, and the Java Plug-inUninstall of the Java Plug-in

cd /opt

Step 5 Run the script file

sh j2re-1_3_03-solsparc.sh

Running the script creates a directory named j2re-1_3_03 that contains the Java Plug-in modules. This directory is placed in the directory that the user selected in step 3

Step 6 Start the vi Editor to open the .cshrc file in the /usr/users/svplus directory.

Step 7 Add the following line to the .cshrc file (instead of opt, use the directory selected in step 3).

setenv NPX_PLUGIN_PATH /opt/j2re1_3_03/plugin/sparc/ns4

Step 8 Close the vi Editor, saving the changes.

Note If you upgrade or downgrade your Java Plug-in, you should delete the following files before starting netscape:

$HOME/.netscape/cert7.db$HOME/.netscape/key3.db

Uninstall of the Java Plug-inThe following steps uninstall the Java Plug-in.

Note Do not uninstall the Java Plug-in if it is required by any of your applications.

Step 1 Log in as root.

Step 2 Navigate to the /usr/j2se directory

Step 3 Type the following command:

# ./pam.sh

Step 4 Select option 2. This will uninstall the Java Plug-in.

Standalone Installation of CiscoViewCiscoView 5.3 can be installed independently of CWM by using a Cisco provided script. This installation procedure and script are intended primarily for users who suspect that the installed CiscoView is corrupted or who installed CWM without CiscoView and want to install CiscoView later. The script installs a package of 18 programs. To execute the script, perform the following steps.



Chapter 5 CiscoView, Netscape, and the Java Plug-inUninstall CiscoView

Caution Do not install CiscoView over a previously installed CiscoView, this will cause two versions of CiscoView to exist and the system will not operate properly. If CiscoView has already been installed, uninstall CiscoView and then use the standalone CiscoView installation procedure.

Step 1 Insert CD#1 into the CD drive.

Step 2 From root, enter the following commands:

# cd/cdrom/cdrom0/# ./ciscoview/setupCv.sh -q <install directory>

in this release, the install directory is /opt/CSCOpx, thus:

# cd/cdrom/cdrom0/# ./ciscoview/setupCv.sh -q /opt/CSCOpx

These commands cause the setupCv.sh script to start execution and install CiscoView in the CSCOpx directory.

If an error occurs during the installation process, details can be found by checking the log file at /var/tmp/ciscoinstall.log.

Uninstall CiscoViewCisco View can be uninstalled using a Cisco provided uninstall script.

Caution The uninstall script MUST be used to remove the product. If you try to remove CiscoView or any of the packages manually, you can damage your system.

Step 1 As root, enter the following commands to start the uninstall script.

# cd /

# /opt/CSCOpx/bin/uninstall.sh

/opt/CSCOpx is the default installation directory.

Note When you remove CiscoView, the uninstall script removes changes made to the /etc/services file. The /etc directory still contains all system file changes.

Uninstall messages are written to the /var/tmp/ciscouninstall.log file.

Step 2 At the prompt, enter q to quit.

When the uninstall script is complete, a message displays:

All files were deleted successfully.

Step 3 Check /etc/syslog.conf for syslog changes.



Chapter 5 CiscoView, Netscape, and the Java Plug-inUninstallation of Netscape Communicator

Step 4 Check /etc/services to ensure that port assignments for the CiscoView applications have been removed.

Uninstallation of Netscape CommunicatorThe following steps uninstall Netscape Communicator.

Step 1 Log in as root

Step 2 Type the following command:

pkgrm NSCPcom

This will remove Netscape Communicator.

C H A P T E R



6Installing CWM SNMP Service Agent Software

This chapter provides step-by-step procedures to install the CWM Release 11 SNMP Service Agent software. The CWM SNMP Service Agent software installation uses InstallShield to simplify the process. Before installing the CWM SNMP Service Agent software on the CWM workstation, the following software should have been installed (in the following order):


• Solaris patches (see the release notes for the latest list of patches)

• Netscape Communicator 4.75 (if required)

• HPOV 6.2

• Wingz 2.5.1

• CWM Release 11 software (including CiscoView 5.4)

Refer to Chapter 2 for instructions on installing these products.

Note The CWM Release 11 SNMP Service Agent software is an optional package available at an additional charge. While the CWM Release 11 SNMP Service Agent software is not required to run CWM Release 11, it can be added to provide flow through provisioning and fault management capabilities to upper layer OSS.

Installing SNMP Service Agent SoftwareTo install the CWM Release 11 SNMP Service Agent software, complete the following steps:


Step 2 Insert the CWM Release 11 SNMP Service Agent CD-ROM into the CDROM drive.



Step 4 Check for the InstallAgent.sh file and begin the install process by entering the following command:

# ./InstallAgent.sh

After a few moments, the SNMP Service Agent Welcome window is displayed (See Figure 6-1).



Chapter 6 Installing CWM SNMP Service Agent SoftwareInstalling SNMP Service Agent Software

Figure 6-1 CWM SNMP Service Agent Installation Welcome Window


The Choose Destination Directory window, Figure 6-2, is displayed.




Figure 6-2 CWM SNMP Service Agent Choose Destination Directory Window

Note The default Primary Destination Directory displayed when the Choose Destination Directory window opens is /usr/users/svplus. If this directory exists, you must install the SNMP Service agent here.

The Browse.. button will only be effective if you installed the CWM server files in a directory other than /usr/users/svplus. If you attempt to change directories on a system where /usr/users/svplus exists, the system responds with the message “Destination dir cannot be changed.”

Step 6 After confirming the destination directory, click Install.

The software installation process begins. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 6-3.




Figure 6-3 CWM SNMP Service Agent Installation Progress Indicator (extracting files)

Note The SNMP Service Agent installation process may find files that already exist on your CWM workstation. When this occurs, a dialog will display asking if it is OK to overwrite this file, as shown in Figure 6-4. When this occurs, reply Yes to All.

Figure 6-4 Copy Files Window

After extracting the necessary SNMP Service Agent files, the window refreshes, and the installation process begins configuring the SNMP Service Agent files (ConnProxy, LineProxy, CardProxy, DiagProxy, and PortProxy). The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the SNMP Service Agent configuration process, as shown in Figure 6-5.




Figure 6-5 CWM SNMP Service Agent Installation Progress Indicator (Service Agent configuration)

When completed, a final window displays indicating that the installation is completed. This window is shown in Figure 6-6.




Figure 6-6 CWM SNMP Service Agent Installation Complete Window

Step 7 Click Finish to end the installation.

Doing so ends the software installation process, the Install Shield window closes.



Chapter 6 Installing CWM SNMP Service Agent SoftwareConfiguration

ConfigurationBoth the SNMP Agent and SNMP Service Agent have configuration files, as described in the following subsections.

Agent ConfigurationThe SNMP Agent configuration file (SNMPAgent.conf) is located in the /us/users/svplus/config directory.

The UDP port used for SNMP Requests can be configured in this file.

Port 8161 is the default UDP port. It may be changed to match your system’s requirements.

After changing the UDP port, you must send a SIGHUP to the SNMP Agent process to force it to read the configuration file again.

Service Agent ConfigurationThe SNMP Service Agent configuration file (snmpd.cnf) is located in the /usr/users/svplus/config directory.

The SNMP community strings are configured in this file. As community strings are used as an index in the Node and Event MIBs, RtmProxy does not require this configuration file. Only ConnProxy (connGroup MIB), and PortProxy (portGroup MIB) use these community strings for authentication.

The Service Agent defaults are GET = public and SET = private.

The Service Agent reads the configuration file only at startup. When you change the configuration file, you must restart the Service Agent (that is, ConnProxy and PortProxy) to obtain the new configuration information.

For more information on configuring and using the SNMP Service Agent software, refer to the Cisco WAN Manager SNMP Service Agent, Release 11.

Syntax: TRANSPORT special SNMP

OVER UDP SOCKET

AT PORT 8161

Syntax: GET_COMMUNITY public

SET_COMMUNITY private



Chapter 6 Installing CWM SNMP Service Agent SoftwareConfiguration

C H A P T E R



7Installing CWM Client

This chapter provides an introduction to CWM Client in CWM Release 11 and describes the installation and launch processes.

Overview of CWM ClientCWM Client is a software component of CWM that permits the user to access and use the features of a CWM server workstation from a network connected client system.

CWM Client is a Java based software package that is designed to run on either a Sun Solaris or a Windows 2000 based client machine under Sun Microsystem’s Java Web Start utility.

Note In release 11 the installation and launching procedures are much different from those in earlier versions of CWM. In earlier versions, the client software was installed directly onto the client machine using a special installation program.

CWM Client Release 11 software is distributed on the CWM server CD-ROMs and is installed on the CWM server workstation as part of the normal CWM server installation process.

The process of launching the client software in the client machine consists of first downloading it to the client machine and then starting the client program. This process is managed from the client machine using a web browser, Java runtime environment (JRE) 1.3.1 software, and Sun Microsystem’s Java Web Start tool all of which must have been installed in the client machine. In addition, launching CiscoView in the client machine requires the Java Plug-in 1.3.1 to be installed. However, this is a component of JRE 1.3.1 and is installed along with the JRE.

On the client machine, the user can download CWM Client and start the program using any of three methods.

1. Start the web browser, connect to the CWM server, and click the displayed icon for CWM or one its applications. This method must be used the first time that CWM is downloaded and launched.

2. Start Java Web Start and click the CWM Client icon.

3. Click a CWM Client shortcut icon on the client desktop.

Note The second and third methods listed above cannot be used to download the Client for the first time. However, they can be used for subsequent downloads and launches.

Each of these methods produces the same results.



Chapter 7 Installing CWM ClientSetting Up a Windows Based CWM Client

Note The Java Web Start installation registers the file extension.jnlp and the MIME type application/x-java-jnlp-file with the operating system, so that Java Web Start will be launched from the browser when a link to a JNLP file is activated. In a Windows based machine, the installer also installs shortcuts to the Application Manager on the desktop and in the Windows Start menu.

If Netscape 6/6.01 is being used as the network browser, set up the Java Web Start MIME type (JNLP) in the Edit->Preferences->Navigator->Helper Applications section. The file extension is jnlp and the MIME Type is application/x-java-jnlp-file. It should be handled by the javaws executable file in your Java Web Start directory.

If the CWM Client software has previously been downloaded and cached, Java Web Start contacts the CWM server and checks to see if a newer version of the CWM Client software exists. If there is a newer version it is downloaded, cached, and launched otherwise the current version is launched.

Setting Up a Windows Based CWM ClientThis section describes the hardware, software, and web browser requirements for a Windows based CWM client.

HardwareThe minimum hardware requirements to run CWM Client release 11 on a Microsoft Windows based PC are as follows:

• Intel Pentium III (or compatible) processor with a clock speed of at least 200 Mhz



• Ethernet connectivity to a CWM server machine

Software The software requirements to run CWM Client release 11 on a Microsoft Windows based PC are as follows:

• MicroSoft Windows 2000 operating system

• IP connectivity to a CWM server machine

• Netscape Communicator browser version 4.75 or later

• Sun Microsystems Java Web Start version 1.01 or later

• Sun Microsystems JRE version 1.3.1 (Windows version)

• Sun Microsystems Java Plug-in 1.3.1 (Windows version, used for CiscoView)




Web BrowserEither Microsoft Internet Explorer or Netscape Communicator can be used on a PC based client.

Microsoft Internet Explorer is included in the Windows software and unless removed will always be installed in a Windows system.

If the user prefers Netscape Communicator, and it is not already installed, it can be downloaded over the Internet. Using Internet Explorer to access Netscape Communicator, go to the following URL:

www.netscape.com

Click the download button at the top of the page. Then follow the download and install instructions.

The browser requires that the it’s path be set using the following procedure:

Step 1 Locate the appropriate browser executable file (netscape.exe for Netscape Communicator and IEXPLORE.EXE for Internet Explorer). Note its path. The default paths for these files are:

• C:\Program Files\Netscape\Communicator\Program

• C:\Program Files\Internet Explorer

Step 2 On the desktop, right click on the My Computer icon and select Properties.

Step 3 Click on the Advanced tab and then click on the Environment Variables button.

Step 4 On the Variable Value line, append a semicolon ; , followed by the path noted in Step 1.

For example, if using Netscape Communicator, append,

;C:\Program Files\Netscape\Communicator\Program

Step 5 Click on OK.

Making Netscape Communicator the Default Browser

For users that prefer Netscape Navigator, use the following procedure to change the default browser from Internet Explorer to Netscape Navigator.

Step 1 Quit Netscape Navigator.

Step 2 Start Internet Explorer.

Step 3 Click on Tools -> Internet Options -> Programs, then unselect the "Internet Explorer should check to see wheter it is the default" box. (Versions other than 5.5 may have different menus).

Step 4 Exit Internet Explorer.

Step 5 Click on the Windows Start button -> Search -> For Files or Folders.

Step 6 Find the file named 'prefs.js', typically under Documents and Settings\All Users\Application Data\Netscape\Users\default\. Note: there may be several copies of this file if the workstation has multiple users and / or multiple versions of Netscape installed.

Step 7 Using Windows Explorer rename prefs.js to prefs.sav.js.

Step 8 Start Netscape Navigator.

Step 9 When Netscape Navigator asks if it should be the default browser, answer 'Yes'.

Step 10 Exit Netscape Navigator.




Step 11 Remove the new prefs.js and rename the prefs.sav.js to prefs.js.

Installing Java ToolsThe following Java tools are required to run CWM client:

• Java Web Start

• Java Runtime Environment (JRE) version 1.3.1

• Java plug-in 1.3.1 (required to launch CiscoView).

These tools are included in the CWM Server CD-ROMs and are stored in the CWM server machine automatically when the CWM server software is installed. These programs are then available for downloading to the CWM client machine.

Step 1 Ensure that the web browser is installed and running on the client machine.

Step 2 Connect to the CWM server machine using its workstation name followed by :1551 (for example http://cwmhost:1551 or http://cwmhost.company.com:1551).

1551 is the software port number for the CWM Client web page

The CWM server machine displays the CWM Client Launcher web page as shown in Figure 7-1. This page is made up of three panes. The top right pane shows the CWM logo, the top left pane shows a list of CWM applications, and the bottom pane contains the CWM Client Help Page link used to install the Java tools.




Figure 7-1 CWM Web Page

Step 3 Click on the CWM Client Help Page link at the bottom pane of the page. The resulting window is shown in Figure 7-2.

This page contains a table of links to download Java Web Start and JRE 1.3 for both Solaris and Windows. It also contains installation instructions for installing the Java tools.




Figure 7-2 Client Help Page

Note The JRE tool should be installed first.

Step 4 Click on the appropriate Jave runtime link (In the Solaris column or the Windows column depending upon the type of client machine being used.)

The download program displays a window requesting the user to specify where the download is to be saved. Note a convenient location and the name of the downloaded file (for example, the Windows JRE filename is Java Runtime 1.3.1 Win.exe).

Step 5 Browse to the selected location on the window and click Save.

A progress bar is displayed and the program is downloaded.

Step 6 Using Solaris or Windows on the client machine, browse to the selected location and double click on the downloaded program.

A software license agreement window is displayed.

Step 7 Click Yes on the license agreement window. A window requesting the destination for the JRE is displayed as shown in Figure 7-3.



Chapter 7 Installing CWM ClientSetting Up a Solaris Based CWM Client

Figure 7-3 Choose Destination Location Window

Accept the default destination by clicking Next. A progress bar is displayed while the JRE is installed.

Setting Up a Solaris Based CWM ClientThis section describes the hardware, software, and web browser requirements for a Solaris based CWM client.

HardwareThe minimum hardware requirement s to run CWM Client Release 11 on a Sun Solaris based system are as follows.

• Sun Ultra 5 with SCSI controller with a clock speed of at least 300 Mhz



• Ethernet connectivity to a CWM server machine

Software The software requirement s to run CWM Client Release 11 on a Sun Solaris based system are as follows.

• Solaris version 2.7 or 8

• IP connectivity to a CWM server machine

• Netscape Communicator browser version 4.75 or later

• Sun Microsystems Java Web Start version 1.0.1 or later

• Sun Microsystems JRE version 1.3.1 (Solaris version)

• Sun Microsystems Java Plug-in 1.3.1 (Solaris version used for CiscoView)




Web BrowserThe Solaris version of Netscape Communicator is used on a Solaris based client.

The Sun Microsystems Netscape Communicator for the Solaris package (version 4.76) is included on the Cisco-provided CWM Server CD #2 under the file name of NSCPcom.sparc.tar.gz

Install Netscape Communicator using the following steps.


Step 2 Insert the CWM server 11 CD #2 into the CD-ROM drive.

Step 3 The NSCPcom.sparc.tar.gz file is located on the CD-ROM in the 110tools directory. You can check that it is present by changing to the tools directory and listing the files by entering the following commands.


Step 4 Copy the Netscape file to the workstation hard drive.

cp /cdrom/cdrom0/110tools/NSCPcom.sparc.tar.gz /tmp

Step 5 Copy the gzip utility to the workstation hard drive.

cp /cdrom/cdrom0/110tools/gzip /tmp

Note If the CWM CD-ROMs are not available at the site of the client machine, the CD-ROM should be inserted in the CWM server machine and the NSCPcom.sparc.tar.gz and the gzip files FTP’d to the /tmp directory in the client machine. This method has the same effect as performing Steps 1–4

Step 6 Change to the tmp directory

cd /tmp

Step 7 Change the permission of the copied gzip file so that it can be executed.

chmod 555 /tmp gzip

Step 8 Unzip the Netscape Communicator file.

./gzip -d /tmp/NSCPcom.sparc.tar.gz

Step 9 Untar the file.

tar xvf /tmp/NSCPcom.sparc.tar

Step 10 Install Netscape Communicator

pkgadd -d /tmp NSCPcom

The pkgadd command installs the Netscape Communicator package in the /opt/NSCPcom directory.

Step 11 Add the /opt/NSCPcom directory to the PATH variable.




Installing Java ToolsThe following Java tools are required to run CWM client:

• Java Web Start

• Java Runtime Environment (JRE) version 1.3.1

• Java plug-in 1.3.1 (required to launch CiscoView).

These tools are included in the CWM Server CD-ROMs and are stored in the CWM server machine automatically when the CWM server software is installed. These programs are then available for downloading to the CWM client machine.

Step 1 Ensure that the web browser is installed and running on the client machine.



The CWM server machine displays the CWM Client Launcher web page as shown in Figure 7-4. This page is made up of three panes. The top right pane shows the CWM logo, the top left pane shows a list of CWM applications, and the bottom pane contains the CWM Client Help Page link used to install the Java tools.





Step 3 Click on the CWM Client Help Page link at the bottom pane of the page. The resulting window is shown in Figure 7-5.

This page contains a table of links to download Java Web Start and JRE 1.3 for both Solaris and Windows. It also contains installation instructions for installing the Java tools.




Figure 7-5 Client Help Page

Note The JRE tool should be installed before Java Web Start.

Step 4 Click on the appropriate Jave runtime link (In the Solaris column or the Windows column depending upon the type of client machine being used.)

Note To avoid mime type problems with downloading, right click the download link and choose "Save Link/Target As...".

The download program displays a window requesting the user to specify where the download is to be saved. Save the downloaded file in the /tmp directory.

Log in as root and type these commands:

# cd /usr# chmod +x /tmp/j2re-1_3_1-solsparc.sh# /tmp/jr2-i_3_1-solsparc.sh

Step 5 A software license agreement window is displayed. Click Yes on the license agreement window.

The JRE 1.3/1 is now installed in the /usr directory.



Chapter 7 Installing CWM ClientInstalling Java Web Start

Installing Java Web StartWhen JRE 1.3.1 has been downloaded and installed, Java Web Start should be installed using the following procedure. This procedure is applicable to both Solaris and Windows based clients.

Step 1 Return to the CWM Help Page and click on the appropriate Java Web Start link (Solaris or Windows column).

The download program displays a window requesting the user to specify where the download is to be saved. Note a convenient location and the name of the downloaded file (for example, the Windows filename is Java Web Start 1.0.1Win.exe).

Step 2 Browse to the selected location on the window and click Save.

A progress bar is displayed and the program is downloaded.

Step 3 Using Solaris or Windows on the client machine, browse to the selected location and double click on the downloaded program.

A software license agreement window is displayed.

Step 4 Click Yes on the license agreement window.

A window requesting the destination for the Java Web Start is displayed as shown in Figure 7-6.

Figure 7-6 Java Web Start Setup: Installation Directory Window

Step 5 Accept the default destination by clicking Next.

A progress bar is displayed while the Java Web Start is installed.

Configuring Java Plug-in 1.3.1

With the completion of step 5 above, JRE 1.3.1 and Java Web Start have been downloaded and installed. As part of the JRE 1.3.1 installation process, the Java Plug-in 1.3.1 (required by CiscoView) has also been installed.

On Windows based clients, no further action is required and CiscoView can be launched from within CWM client.



Chapter 7 Installing CWM ClientLaunching CWM Client

On Solaris based clients, the path to the plug-in has to be set in the .cshrc file. Set the path using the following procedure.

Step 1 Start an editor and open the .cshrc file in the /usr/users/svplus directory.

Step 2 Add the following line to the .cshrc file.

setenv NPX_PLUGIN_PATH /usr/j2re1_3_1/plugin/sparc/ns4

Step 3 Save the changes.

Step 4 Close the editor

.

Note Executing the source .cshrc command will cause the PATH change to take effect immediately.

Launching CWM ClientThis section describes the methods by which the user can launch CWM Client.

When the client machine is running Solaris or Windows 2000 and the network browser and Java tools have been installed, there are several methods available for launching the Cisco CWM Client.

The first time (but only the first time) that CWM Client is to be launched, the user must start the web browser and connect to the CWM Server to display the CWM Client Launch page. The client can then be launched by clicking on the appropriate part of the page.

After the client has been launched for the first time, subsequent launches can be performed either through the web browser (described above), through the Java Web Start Manager or through a CWM application desktop shortcut icon.

In each case the CWM Client is launched. The software is downloaded or not from the CWM server depending upon whether it is resident in the client machine. Any local copy of CWM Client is checked at the server to see if it is the latest version. If it is not, the most current version is downloaded and launched. This feature ensures that if a later version CWM Client is installed on the CWM server, it will automatically be available at the client machine.

Web Browser MethodTo launch CWM Client using the web browser, perform the following steps.

Step 1 Check that the web browser is installed and running on the client machine.



Step 3 The CWM server machine displays its web page as shown in Figure 7-7.





Step 4 To launch CWM, click on the Cisco WAN Manager picture in the top right pane. To launch a specific CWM application, click on one of the menu items in the top left pane.

Java Web Start Application Manager MethodTo use the Java Web Start Application Manager, first start the Application Manager either by clicking the Java Web Start icon on the desktop or selecting Java Web Start in the Windows Start Menu.

Figure 7-8 shows an example of the Java Web Start Application Manager window.




Figure 7-8 Java Web Start Application Manager Window

Click on the appropriate icon to launch the desired application. Only applications that have previously been downloaded (by another method) will show up in this window. Make sure that the text above the icons says Downloaded Applications. If it does not use the View menu to select Downloaded Applications.

Desktop Shortcut MethodIf the same CWM application is launched two times, Java Web Start will ask the user if a desktop shortcut should be created (see Figure 7-9). To create an shortcut click the appropriate box(es) and click Yes. Thereafter, the application can be started merely by clicking the shortcut (either on the desktop or the Start Menu).

Figure 7-9 Java Web Start Shortcut Window




C H A P T E R



8Installing Standalone Statistics Collection Manager Software

This chapter provides step-by-step procedures to install the CWM Release 11 Statistics Collection Manager software on a standalone workstation. The CWM Release 11 Statistics Collection Manager Standalone (SCMSA) software installation uses InstallShield to simplify the process.

Three types of machines are supported for CWM Release 11 SCMSA software as standalone platforms. They are low-end, mid-range, and high-end platforms. Table 8-1 describes the configuration for each platform.

Note The minimum CPU speed requirement for all platforms is 300 MHz. The newer versions of the Sun Ultra 10 have a 450 MHz processor. All platforms require a 24-bit graphics card.

The maximum number of nodes supported by a given machine configuration is affected by the number of connection being supported by SCMSA. If the number of connections is high, the number of nodes specified in Table 8-1 may not be achieved

Before installing the CWM Release 11 SCMSA software on a standalone SCM workstation, the following software should have already been installed.


Install Solaris 2.7 according to the procedure described in Chapter 2.

Table 8-1 Sun Platform Requirements

Platform Type Machine Type

Number of CPUs

Size of RAM

Hard Disk Drive

Swap Space

Number of Nodes Supported

Low End

Sun Ultra 10 with SCSI controller

1 at least 512 MB

One 9-GB drive

1 GB Less than 20 nodes

Mid Range

Sun Ultra 60 2 at least 1 GB

One 9-GB drive

2 GB 20–100 nodes

High End

Sun Enterprise 450 at least 4 2 GB Two 9-GB drives or disk array

4 GB 100–250 nodes



Chapter 8 Installing Standalone Statistics Collection Manager SoftwareInstalling CWM Statistics Collection Manager Standalone

Installing CWM Statistics Collection Manager Standalone Installing the Statistics Collection Manager Standalone (SCMSA) software automatically creates a user with the name “svplus".


To install the CWM Release 11 SCMSA software, complete the following steps:

Step 1 Log in to the workstation as user root.

Step 2 Insert the Cisco WAN Manager Release 11 SCMSA CD-ROM into the CD-ROM drive.



Step 4 Check for the file InstallSCMSA.sh and begin the install process by entering the following command:

# ./InstallSCMSA.sh

The SCMSA Installation Welcome window is displayed, as shown in Figure 8-1.

Figure 8-1 SCMSA Installation Welcome Window


The Install Standalone Collection Server or Parser window, Figure 8-2, is displayed.




Figure 8-2 Install Standalone Collection Server or Parser Window

Step 6 Select one of the three options displayed in the window and click Next. The user can select to have the Standalone Collection Server, the Standalone Parser, or both installed. When upgrading from a previous release of SCMSA, the user must select either option 1 or option 3.

Note See Appendix A for more details on the SCM server options.

Step 7 After selecting an option, click Next. The Meta Devices window is displayed as shown in Figure 8-3.


Step 8 If you have no meta devices, accept the default No and click Next.








The Select the Raw Partition for SCMSA Database window is displayed, as shown in Figure 8-5.




Figure 8-5 Select the Raw Partition for SCMSA Database Window

Step 10 At the Select the Raw Partition for SCMSA Database window If multiple partitions are displayed, select any partition under 1995 MB in size, then click Next.


The SCM Control Server window is displayed, as shown in Figure 8-6.




Figure 8-6 SCM Control Server Window

Step 11 At the SCM Control Server window, enter the name of the CWM workstation where the SCM server application resides. Click Next.





The Enter the Domain Name window is displayed, as shown in Figure 8-8.





Step 13 At the Enter the Domain Name window, enter the domain name configured for the server workstation. This name allows the SCM application workstation access to the database.

Enter ping to ensure that the workstation and the domain is reachable.

Step 14 Click Next to display the SCMSA Choose Destination Directory window as shown in Figure 8-9.





In this release only the default directory (/usr/users/svplus) is be used.

Step 15 Click Next to display the Information about the SCMSA Upgrading procedure Window as shown in Figure 8-10.

The upgrade window is displayed only if option 1 or 3 was selected in the Install Standalone Collection Server and Parser window (see Figure 8-2), otherwise the next window to be displayed is the Installation Progress window (see Figure 8-11).

Figure 8-10 Information about the SCMSA Upgrading Procedure Window

Step 16 Select No (for installing), click Install.

The software installation process begins. This process will take from 30 to 60 minutes depending on the speed and resources of the workstation you are installing the standalone SCM application on. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 8-11.





After extracting the necessary SCM program files, the window refreshes, and the installation process begins creating and configuring the database. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the database creation process, as shown in Figure 8-12.





Chapter 8 Installing Standalone Statistics Collection Manager SoftwareFirst Time Login as User svplus



Doing so ends the software installation process, and the Install Shield window closes.

The first time (and only the first time) that SCMSA is installed, the system displays a message at this point stating that the kernel has been changed.

Step 18 Click OK to reboot the system.


The OK prompt is displayed.

Step 19 Push the CDROM eject button on the CDROM drive to eject the CWM Release 11 SCMSA software CD.

First Time Login as User svplusAfter completing the CWM Release 11 Statistics Collection Manager, Stand Alone software installation, perform the following steps.

Step 1 Check that the SCMSA CD-ROM has been removed from the CD drive. If not, type eject in the terminal window.


Step 3 Select CDE.


Step 5 Right-click on blank screen, select Tools, select Terminal.


Step 6 Right-click on blank screen highlight Hosts, then Terminal Console.







Step 8 Left-click on Screen, click screen saver on and screen lock off. Click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK


Do the same to all four screens, labeled One, Two, Three and Four in the CDE icon bar. In screen Four, click OK and return to screen One. This helps to conserve workstation resources.

Step 10 Click on the CDE icon labeled TTT, then click on Startup in the Style Manager. Click on Set Home Session. Click OK.


Step 11 Place the cursor in the terminal window, and enter the SCM command to start a stand alone SCM session.

% SCM

The first time that SCMSA is run, the database is create. The following messages are displayed.

# SCMRunning SCM for the very first time. Creating the database for use by SCM

[orbixd:Server "IT_daemon" is now available to the network ][ Configuration TCP/1570/Orbix-XDR ]

creating database :<scmdb>creating scm tables in database :<scmdb>dropping table collmethodcreating table collmethoddropping table collmethoddefcreating table collmethoddefdropping table node_infocreating table node_infodropping table collsvr_infocreating table collsvr_infodropping table statsdb_infocreating table statsdb_infodropping table coll_infocreating table coll_infodropping table sync_infocreating table sync_infodropping table sync_listcreating table sync_listdropping table coll_summ_listcreating table coll_summ_listdropping table file_infocreating table file_infodropping table pend_file_listcreating table pend_file_listdropping table comp_file_listcreating table comp_file_listdropping table collsvr_err_logcreating table collsvr_err_log




dropping table coll_err_logcreating table coll_err_logdropping table file_queue_logcreating table file_queue_logdropping table file_transfer_logcreating table file_transfer_logdropping table file_err_logcreating table file_err_logload from collmethod.unl into table collmethod

When the database is created, SCM displays its main menu as follows.

Welcome to Statistics Collection Manager [Collection Server] Release 10.5.10AP.SOL Thu Nov 8 22:00:18 PST 2001

Statistics Collection Manager is being run from the workstation, "aruna" . by svplus MAIN MENU --------- 1) Start SCM core 2) Stop SCM core x) Exit

enter number or x to exit:x

Step 12 Ensure that the SCM Control Server Process in the CWM Server workstation is running.

Step 13 Start the SCM core by selecting Option 1.

For information on configuring statistics collection using Stand Alone SCM, refer to the Cisco WAN Manager User’s Guide, Release 11, Chapter 8, “Statistics Collection Manager Stand Alone”.

C H A P T E R



9Upgrading Standalone Statistics Collection Manager Software

This chapter provides step-by-step procedures to upgrade the CWM Release 11 Statistics Collection Manager Standalone (SCMSA) software on a workstation from a previous release. The CWM Release 11 SCMSA software upgrade process uses InstallShield to simplify the process.

Three types of machines are supported for CWM Release 11 SCMSA software as standalone platforms. They are low-end, mid-range, and high-end platforms. Table 9-1 describes the configuration for each platform.

Note The minimum CPU speed requirement for all platforms is 300 MHz. The newer versions of the Sun Ultra 10 have a 450-MHz processor. All platforms require a 24-bit graphics card.

The maximum number of nodes supported by a given machine configuration is affected by the number of connection being supported by SCMSA. If the number of connections is high, the number of nodes specified in Table 9-1 may not be achieved

Before installing the CWM Release 11 SCMSA software on a standalone SCM workstation, the following software should have already been installed.


Install Solaris 2.7 according to the procedure described in Chapter 2.

Table 9-1 Sun Platform Requirements

Platform Type Machine Type

Number of CPUs

Size of RAM

Hard Disk Drive

Swap Space

Number of Nodes Supported

Low End

Sun Ultra 10 with SCSI controller

1 at least 512 MB

One 9 GB drive

1-GB Less than 20 nodes

Mid Range

Sun Ultra 60 2 at least 1 GB

One 9 GB drive

2-GB 20–100 nodes

High End

Sun Enterprise 450 at least 4 2 GB Two 9 GB drives or disk array

4-GB 100–250 nodes



Chapter 9 Upgrading Standalone Statistics Collection Manager SoftwareUpgrading CWM Statistics Collection Manager Standalone Software

Upgrading CWM Statistics Collection Manager Standalone Software


To install the CWM Release 11 Statistics Collection Manager Standalone (SCMSA) software, complete the following steps:

Step 1 Log in to the workstation as user root.

Step 2 Insert the Cisco WAN Manager Release 11 Stand Alone Statistics Collection Manager CD-ROM into the CDROM drive.



Step 4 Check for the file InstallSCMSA.sh .

Step 5 Begin the install process by entering the following command:

# ./InstallSCMSA.sh

The CWM Installation Welcome window is displayed, as shown in Figure 9-1.

Figure 9-1 SCMSA Installation Welcome Window


The Install Standalone Collection Server or Parser window, Figure 9-2, is displayed.




Figure 9-2 SCMSA Server or Parser Window

Select one of the three options displayed in the window. The user can select to have the Standalone Collection Server, the Standalone Parser, or both installed. When upgrading from a previous release of SCMSA, the user must select either option 1 or option 3.

Step 7 After selecting an option, click Next.

The Meta Devices window is displayed as shown in Figure 9-3.


Step 8 If you have no meta devices, accept the default No and click Next.








The Select the Raw Partition for SCMSA Database window is displayed, as shown in Figure 9-5.




Figure 9-5 Select the Raw Partition for SCMSA Database Window

Step 10 At the Select the Raw Partition for SCMSA Database window If multiple partitions are displayed, select any partition under 1995 MB in size, then click Next.


The SCM Control Server Location window is displayed, as shown in Figure 9-6.




Figure 9-6 SCM Control Server Location Window

Step 11 At the SCM Control Server Location window, enter the name of the CWM workstation where the SCM server application resides, then click Next.





The Enter the Domain Name window is displayed, as shown in Figure 9-8.





Step 13 At the Enter the Domain Name window, enter the domain name configured for the server workstation.

This name allows the SCM application workstation access to the database. Enter ping to ensure that the workstation and the domain is reachable.

Step 14 Click Next to display the Choose Destination Directory window as shown in Figure 9-9.


In this release only the default directory (/usr/users/svplus) is be used.




Step 15 Click Next to display the SCMSA Upgrade Window as shown in Figure 9-10. The upgrade window is displayed only if option 1 or 3 was selected in the Collection Server and Parser window (see Figure 9-2), otherwise the next window to be displayed is the Installation Progress window (see Figure 9-12).

Figure 9-10 CSMSA Upgrade Window

Step 16 Select Yes (for upgrading).

Step 17 Click Install.

Step 18 A confirming dialog box is displayed (see Figure 9-11) showing which version of SCMSA is being upgraded.

Step 19 Click OK.

Note The svplus version of SCMSA (in ~svplus/etc) must still be intact at this point otherwise the upgrade will fail.

Figure 9-11 SCMSA Upgrade Information Window

The software installation process begins. This process will take from 30 to 60 minutes depending on the speed and resources of the workstation you are installing the standalone SCM application on. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the installation process, as shown in Figure 9-12.





After extracting the necessary SCM program files, the window refreshes. The installation process begins creating and configuring the database. The installation window shows a dynamic indicator bar, which moves across the window, indicating the progress of the database creation process, as shown in Figure 9-13.





Chapter 9 Upgrading Standalone Statistics Collection Manager SoftwareUpgrading to the SCMSA 11 Software from Release 10.x with Multiple CWM Gateways



Doing so ends the software installation process, and the Install Shield window closes.

The first time (and only the first time) that SCMSA is installed, the system displays a message at this point stating that the kernel has been changed.

Step 21 Click OK to reboot the system.


The OK prompt is displayed.

Step 22 Push the CDROM eject button on the CDROM drive to eject the CWM Release 11 Stand Alone Statistics Collection Manager software CD.

Upgrading to the SCMSA 11 Software from Release 10.x with Multiple CWM Gateways

When upgrading from a network in which there are multiple CWM gateways, a special sequence of steps needs to be followed. This procedure ensure that, at all times, there is one and only one master CWM in a CWM domain for a particular release and that the integrity of the network configuration and user data files is maintained. This procedure does involve some downtime in the SCMSA workstations.

Initial Conditions before UpgradeConsider an example network that has three Release 10.5.10 CWM gateways (named A, B, and C), all in the same domain. The gateways consist of one master and two secondaries. All gateways are up and running, all are synced with the network configuration and user data.



Chapter 9 Upgrading Standalone Statistics Collection Manager SoftwareUpgrading to the SCMSA 11 Software from Release 10.x with Multiple CWM Gateways

Consider an example network that has two release 10.x CWM gateways consisting of, one master and one secondary and two release 10.x SCMSA workstations. All workstations are up and running, all are synced, and all need to be upgraded to Release 11.

Note Although this example uses a network with two CWM stations and two SCMSA stations, the same procedure can be extended to a network using any number of stations.

In release 10.4, 10.5, and 11 the first CWM station to be started is automatically assigned the role of primary station. The second station to be started becomes a secondary station with priority 1. Subsequent stations also become secondary stations with priorities of 2, 3, and so on. To ensure such a primary/secondary arrangement, the DomainGatewayList field in the CWMGateway.conf file for all CWM stations must list all CWM gateways.

As shown in Figure 9-14, CWM A station is primary and station CWM B is secondary. The CWMGateway.conf field for all three gateways contains the entry:

DomainGatewayList CWMA CWMB

The two SCMSA stations are shown as SCMSA A and SCMA B.Initial State of Workstations

Upgrade ProcedureThe following steps upgrade the stations, one by one, to Release 11.

Step 1 Stop the core process for all SCMSA stations.

Step 2 Stop the CWM core process for CWM A

This action causes CWM B to assume the role of primary.

Step 3 Use InstallCWM.sh to upgrade CWM A to release 11 as described in the Chapter 4, “Upgrading CWM Software”.

Use the Primary/Secondary select window to select CWM A as primary.

Start the CWM core process for CWM A. CWMA starts as primary but in a different gateway domain.

The new state of the stations is shown in Figure 9-15.

Figure 9-15 State of Workstations after Step 4

CWM A 10.5.10Core Running

PrimaryDomainGateway

List = A,B

CWM B 10.5.10Core Running

SecondaryDomainGateway

List = A,B

SCMSA A 10.5.10Core Running

SCMSA B 10.5.10Core Running

CWM A 11Core Running


List = A



List = A,B

SCMSA A 10.5.10Core Stopped

SCMSA B 10.5.10Core Stopped



Chapter 9 Upgrading Standalone Statistics Collection Manager SoftwareFirst Time Login as User svplus

Step 4 Upgrade SCMSA A and SCMSA B to Release 11.

Use the procedure described in the “Upgrading CWM Statistics Collection Manager Standalone Software” section on page 9-2.

Step 5 Start the core process for both SCMSA A and SCMSA B.

The state of the stations is now as shown in Figure 9-16.

Figure 9-16 State of Workstations after Step 6

Step 6 Stop the CWM core process for CWM B.

Step 7 Use InstallCWM.sh to upgrade CWM B to release 11. Use the Primary/Secondary select window to select CWM B as secondary and CWM A as primary.

Step 8 Start the CWM core process for CWM B. CWM B starts as secondary in the same domain as CWM A.

The new state of the stations is shown in Figure 9-17.


Step 9 At this point, all workstations are operating in the initial state except that they have all been upgraded to release 11.

The user must now update the DomainGatewayList in the CWMGateway.conf file for all three gateways to include CWMA, CWMB. In this way the gateways will be part of the same gateway domain when their cores are next restarted.

First Time Login as User svplusAfter completing the CWM Release 11 Statistics Collection Manager, Stand Alone software installation, perform the following steps.

Step 1 Check that the SCMSA CD-ROM has been removed from the CD drive. If not, type eject in the terminal window.


Step 3 Select CDE.



List = A



List = A,B

SCMSA A 11Core Running

SCMSA B 11Core Running



List = A,B

CWM B 11Core Running

SecondaryDomainGateway

List = A,B

SCMSA A 11Core Running

SCMSA B 11Core Running





Step 5 Right-click on blank screen, select Tools, select Terminal.


Step 6 Right-click on blank screen highlight Hosts, then Terminal Console.




Step 8 Left-click on Screen, click screen saver on and screen lock off. Click OK.

If you prefer to use the screen saver, highlight choice(s) and start the screen saver at 29 minutes. Start the screen lock at 30 minutes, click OK


Do the same to all four screens, labeled One, Two, Three and Four in the CDE icon bar. In screen Four, click OK and return to screen One. This helps to conserve workstation resources.

Step 10 Click on the CDE icon labeled TTT, then click on Startup in the Style Manager. Click on Set Home Session. Click OK.


Step 11 Place the cursor in the terminal window, and enter the SCM command to start a stand alone SCM session.

% SCM

The SCM menu displays, as shown below:




Figure 9-18 shows an xterm window displayed with the SCM main menu options.

Figure 9-18 SCM start core, stop core, and exit options

Step 12 Ensure that the SCM Control Server Process in the CWM Server workstation is running.

Step 13 Start the SCM core by selecting Option 1.

For information on configuring statistics collection using Stand Alone SCM, refer to the Cisco WAN Manager User’s Guide, Release 11, Chapter 8, “Statistics Collection Manager Stand Alone”.

C H A P T E R



10Configuration

This chapter provides information about the configuration required for the CWM workstation.

Configuring Topology DiscoveryThe network.conf file, located in the /usr/users/svplus/config/ directory, is used to specify the network(s) to be discovered and managed by CWM. Basically this file describes the routing protocol, the gateway address to the network, and whether in-band or out-of-band management is used.

The format of the file depends upon the type of network of which there are three as follows.

• AutoRoute network

• PNNI network

• Hybrid network (one consisting of AutoRoute and PNNI nodes connected via pnni/xlmi trunks)

To view the /usr/users/svplus/config/network.conf file, enter the following command:

host% more /usr/users/svplus/config/network.conf

Configuring AutoRoute TopologyTo configure the CWM workstation to use AutoRoute discovery. Modify the network.conf file in the /usr/users/svplus/config directory as shown in the following example.

Note The network.conf file example below is for a machine named nmsbpx02 on a network designated network1.

NETWORK:network1GATEWAYS:nmsbpx02DISCOVERY PROTOCOL:AUTOROUTEIP REACHABILITY FLAG:NWIP_ONOPTIONAL:”TIMEOUT=7, RETRANSMIT=6, THROTTLE=0, ACKNOWLEDGE=30, BLOCKSIZE=1024”



Chapter 10 ConfigurationConfiguring Topology Discovery

Configuring PNNI TopologyUse the Topology Configurator to provide information required to communicate with the nodes. Also use the configurator to specify Network IP.

Note These are nodes that have their SNMP community string for GET operations not set to public, and SNMP community string for SET operations not set to private.

Configuring PXM45 Cards

To configure a PXM45 card, telnet to the card and enter the following commands:

pxm45> shmsimulateresetReason 0pxm45> deltree “C:DB2”

Note The above commands should be used when inconsistency exists between the database and the image.

anotherPXM> addcontroller 2 i 2 7 “pxm45 controller”

Note The command above is only required after a dbtree or clrallcnf command.

anotherPXM> addpnport 9:1.1:1 anotherPXM> cnfpnportsig 9:1.1:1 -nniver pnni 10

Note Assumes an AMXSM in slot 9

Configuring AXSM Cards

To configure a AXSM card, telnet to the card and enter the following commands:

specificAXSM.a> cnfingsct -sct 5specificAXSM.a> upln 1.1specificAXSM.a> addport 1 1.1 9600 96000 5 2 specificAXSM.a> addpart 1 1 2 9600 96000 9600 96000 33 4095 33 65535 3 512specificAXSM.a> cnfilmi -if 1 -id 1 -ilmi 1 -trap 1specificAXSM.a> dspportsspecificAXSM.a> dsppartsspecificAXSM.a> dspilmisspecificAXSM.a> cc 7specificAXSM.a> dsppnportsspecificAXSM.a> uppnport 9:1.1:1specificAXSM.a> ipifconfig atm0 <ipaddress node NWIP>specificAXSM.a> cnffname <sysname>

Note Assumes PXM card is in slot 7



Chapter 10 ConfigurationConfiguring Topology Discovery

Configuring Hybrid TopologyTo configure CWM for Hybrid networks (AutoRoute and PNNI), the file has the following format.

NETWORK:Network1 (a name for CWM to identify the network)AR-GATEWAYS:sj123456(the name or IP address of the gateway to the Auroroute section of the

network)PNNI-GATEWAYS:sj123456(the name or IP address of the gateway to the PNNI section of the

network)DISCOVERY PROTOCOL:HYBRID (the discovery protocol, in this case always HYBRID)IP REACHABILITY FLAG:NWIP_OFF (specifies in-band or out-of-band management)OPTIONAL:"TIMEOUT = 7, RETRANSMIT = 6, THROTTLE = 0, ACKNOWLEDGE = 30, BLOCKSIZE = 1024"

(the optional field is used to specify parameters if the desired value is different from the default value,

Check that the mnemonic of the gateway node is correct. Also, for AutoRoute nodes, check the IP Reachability Flag is correct.

Configuring Standalone NodesIn a stand alone environment, the network.conf file does not require modification. Use the Topology Configurator to provide the following information:

• IP address (LAN IP)

• Mode, standalone

• Model information

Note Cisco MGX 8850 is the model for Cisco MGX 8850 Release 2 nodes only. For Cisco MGX 8850 Release 1 nodes choose Cisco MGX 8250.

To add a new node, complete the following steps:

Step 1 On the machine where Cisco WAN Manager Release 11 is installed, enter:

cd /usr/users/svplus/java/bin

Step 2 Enter runConfigurator <CWM hostname> < CWM login> <CWM password> on a shell’s command line.

The Network Configurator main window appears, displaying the options to add, delete, and modify nodes.

Step 3 To add a node, select Edit from the main menu bar of the Network Configurator window.

Step 4 Select Node from the Edit menu.

Step 5 Select Add from the Node menu.

A Node Dialog box appears after selecting Add from the Node menu. The Node Dialog box contains two tab windows, Node and Mode.

Step 6 In the Node window enter the new node name, the node Descriptor information, and FTP information, in the appropriate fields.

Step 7 In the Mode window enter the Mode, (Connected or Stand Alone), the MGX Model, the IP Address, and any Parent Information, including Feeder Slot, Feeder Port, Parent Name, Parent Slot, and Port.



Chapter 10 ConfigurationChecking the CWM Workstation File System

Note Enter the lnpci or atm0 address in the IP address field. (Correspondingly specify the chosen IP address as the trapip in the switch by entering the cnftrapip command on the switch.

Step 8 Press the OK button in the Node Dialog box.

The Network Configurator validates the new node by ensuring its IP address and unique node name. The node will be displayed in the Network Configurator main window if the node information is valid.

Step 9 Select Close from the Node Dialog pull down menu, located in the upper left hand corner of the window.

Step 10 Select File, then Save from the Network Configurator Window.

Note Changes made using the Network Configurator are not saved in the node_info table until you press the Save button. If the Cancel button is pressed, no changes will be made to the node_info table.

All MGX 8850 nodes will be displayed in both the standalone view and the integrated view.

For more information on configuring standalone MGX 8850 nodes for management by CWM, refer to Appendix B of the Cisco WAN Manager User’s Guide, Release 11.

Checking the CWM Workstation File SystemAt the CWM workstation, log in as user root, and examine the following files.

• /etc/hosts

• /etc/netmasks






• /system

• /etc/system


/etc/hosts









For each node:



Example:

172.70.207.9mgx1192.0.0.9mgx1-l


For each node:


Example:

172.70.209.9mgx4

BPX Nodes

For each node:


Example:

192.0.0.8bpx1

Example Host File






/etc/netmasks











/etc/defaultrouter


















• AutoRoute

• PNNI




• NETWORK ID

• GATEWAYS



• OPTIONS

NETWORK






NETWORK ID





GATEWAYS










AutoRoute


PNNI


Hybrid





.DISCOVERY PROTOCOL


















OPTIONAL






• TIMEOUT

• RETRANSMIT

• THROTTLE

• ACKNOWLEDGE

• BLOCKSIZE

TIMEOUT


RETRANSMIT


THROTTLE


ACKNOWLEDGE


BLOCKSIZE








NETWORK:Network1

GATEWAYS:B8650_SJ





NETWORK:Network2

GATEWAYS:M8850_LA




#NETWORK:Network3








For example:







Chapter 10 ConfigurationModifying the SNMP Community String

/system


# cd /system# ls

/etc/system







Modifying the SNMP Community StringIn Cisco IGX 8400 and Cisco BPX 8600 nodes require that you modify the SNMP Community string using the cnfsnmp command. For example:

host% cnfsnmp <getme> <setme> <trapme>

In addition, you must modify two files on the CWM workstation in directory /usr/users/svplus/config:

• svplus.conf

• process.conf

Modifying the svplus.conf FileAs user root on the CWM workstation, use vi or some other editor to edit the /usr/users/svplus/config/svplus.conf file and set SV_COMMUNITY to getme and set SV_SETCOMMUNITY to setme.

The svplus.conf file should look like the following example:

# Community name for BPX and IPX



Chapter 10 ConfigurationModifying the SNMP Community String

# SV_COMMUNITY=getmeSV_SETCOMMUNITY=setme

Note When using the vi Editor, remember to write your changes before quitting. To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.

Modifying the process.conf FileAs user svplus on the CWM workstation, edit the /usr/users/svplus/config/process.conf file. The process.conf file should have a line like the following example:

cmgrd on . cmgrd -c setme -C getme -i 5

Note When using the vi Editor, remember to write your changes before quitting. To save your changes while using the vi editor, remember to press Esc, colon (:), then wq!.

Setting Up the IP Address on an Cisco MGX 8850, Release 2 SwitchUse the following prodedure to set up IP Addresses on a Cisco MGX 8850 up to Release 2.1.60.

Procedure for Releases up to and including 2.1.60

Before you can manage the switch through the PXM45 LAN port, you must first assign an IP address to the LAN port. This Ethernet LAN port is located on the PXM45 back card. For additional instructions on physically connecting a terminal or workstation to this port, refer to the MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide .

To configure an IP address for the PXM45 LAN port, use the following procedure.

Step 1 Establish a CLI management session using a username with SUPER_GP privileges.

The default user name and password for this level are superuser, superuser.

Step 2 Verify that the IP address is not already configured by entering the dspipif command:

mgx8850a.7.PXM.a> dspipif lnPci0

Note If you omit the lnPci0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM45 LAN port interface (lnPci0), and the PXM45 maintenance port interface (sl0).

In the IP Interface Configuration Table, look for an Internet address entry under the lnPci entry. If an IP address is configured, you can use that address and skip the rest of this procedure. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step.



Chapter 10 ConfigurationSetting Up ATM WAN Connections

Step 3 To set the IP address for the LAN port, enter the ipifconfig command using the following format:

mgx8850a.7.PXM.a> ipifconfig lnPci0 <IP_Addr> <netmask Mask>

Replace IP_Addr with the IP address you want this port to use. Replace Mask with the network mask used on this network.

Tip Cisco recommends that you use the same subnet for all IP addresses defined on all MGX 8850 switches. This simplifies router configuration.

Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you do not define in a command remain unchanged. For more information on this command, refer to Cisco CWM Routing Switch Command Reference, Release 2.

After you complete this procedure, the switch is ready for management through the PXM45 Ethernet port.

Procedure for Releases 2.1.70 and later.

Use the following procedure to set up IP Addresses on a Cisco MGX 8850 up to Release 2.1.70 and later.



Step 2 Verify that the IP address is not already configured by entering the dspndparms command. Look at the value for option 8. If no address or the wrong address is found, enter the correct address entering the cnfndparms command (option 8).

Setting Up ATM WAN ConnectionsAn ATM connection extends switch management to all workstations that have access to the ATM network in which the switch is installed. Figure 10-1 shows the hardware required for an ATM WAN connection.




Figure 10-1 Hardware Required for an ATM WAN Connection

The workstation in Figure 10-1 uses a LAN to connect to a router that supports both LAN and ATM interfaces. An IP address is assigned to an ATM interface in each Cisco MGX 8850. To manage an MGX 8850, the workstation operator configures a network management program to communicate with the IP address assigned to the ATM interface. Network managers can use the following tools to manage the switch:

• Command line interface (CLI) using a Telnet session

• Cisco WAN Manager (CWM)

• Third-party Simple Network Management Protocol (SNMP) manager

To support the ATM SVCs over which the IP traffic travels, both the router and switch are configured to map the respective IP addresses to ATM End Station Addresses (AESAs). When a management session is initiated, the IP workstation directs all communications to the IP address assigned to the ATM interface on the switch. The router encapsulates this IP traffic in ATM cells and forwards it over SVCs to the switch. The destination switch retrieves the IP messages from the ATM cells and forwards them to the internal IP management tools. Replies to the workstation follow the same path in reverse.

This feature provides maximum flexibility for switch management. Any workstation with a connection to a properly-configured ATM router can manage any switch in the network. Furthermore, additional routers connected to other switches can be configured to support this feature, enabling switch configuration from multiple locations throughout an ATM network.

Configuring the SwitchTo support IP connectivity over the ATM interface, perform the following tasks:

• Assign an IP address to the ATM interface.

• Assign an AESA to the ATM interface.

• Define an AESA for every adjacent router that supports IP communications to the ATM interface.

• Configure ATM communications between the switch and the router.

To configure the switch to support IP connectivity to the ATM interface, use the following procedure.



Core ATMnetwork

CiscoMGX 8850

ATM SVCs

ATM SVCs

ATM router(Cisco or third-party)

IP workstation

IP over Ethernet LAN

CiscoMGX 8850

3866

6




Step 2 Verify that the IP address for the ATM interface is not already configured by entering the following command:

mgx8850a.7.PXM.a> dspipif atm0

Note If you omit the atm0 option, the switch displays the configuration for all switch IP interfaces: the ATM interface (atm0), the PXM45 LAN port interface (lnPci0), and the PXM45 maintenance port interface (sl0).

Step 3 In the IP Interface Configuration Table, look for an Internet address entry under the atm entry.

If an IP address is configured, you can use that address. However, if the address has not been entered or is incompatible with your network, you must configure a valid IP address as described in the next step.

Step 4 To set the switch IP address for the ATM interface, enter the ipifconfig command using the following format:

mgx8850a.7.PXM.a> ipifconfig atm0 <IP_Addr> <netmask Mask>

Replace IP_Addr with the IP address you want this port to use, and replace Mask with the network mask used on this network.

Tip Cisco recommends that you use the same subnet for all IP addresses defined on all MGX 8850 switches. This simplifies router configuration.

Note There are other options for the ipifconfig command, and you can set one or more options simultaneously. Any options you do not define in a command remain unchanged. For more information on this command, refer to MGX 8850 and MGX 8950 Command Reference, Release 2.1.

Step 5 To verify the IP address you configured, enter the following command:

mgx8850a.7.PXM.a> dspipif atm0

Step 6 Make a note of the IP address defined for the atm0 interface. This is the IP address switch administrators must use to manage the switch.

Step 7 Configure the switch AESA for IP connectivity by entering the following command:

mgx8850a.7.PXM.a> svcifconfig atm0 local <ATM_Addr>

Replace ATM_Addr with the AESA for the interface. This address must conform to the address plan for the switch.

Step 8 Define the AESA for the ATM router by entering the following command:

mgx8850a.7.PXM.a> svcifconfig atm0 router <ATM_Addr>

Replace ATM_Addr with the AESA for the interface. This address must conform to the address plan for the switch.

Step 9 To verify the ATM addresses you configured, enter the following command:

mgx8850a.7.PXM.a> dspsvcif

Step 10 If you have not already done so, configure the PNNI controller.




As described in “Configuring the PNNI Controller,” in Chapter 2, “Configuring General Switch Features” in the Cisco MGX 8850Software Configuration Guide Release 2 .

Step 11 Configure the ATM line to the ATM router as described in “Line Configuration Quickstart” in Chapter 5, “Provisioning AXSM Communication Links” in the Cisco MGX 8850 Software Configuration Guide, Release 2.

The line configuration should specify a UNI port, SCT 6, and a partition that supports at least 20 connections.

Step 12 To verify connectivity to directly attached ATM routers, enter the dsppnsysaddr command.

The ATM addresses of directly attached ATM routers should appear in the list the switch displays. To display an ATM address for a remote router, you need to establish a CLI session on the remote switch and enter the dsppnsysaddr command.

Step 13 To check the status of ports leading to directly-attached ATM routers, enter the dsppnports command.

The following example shows commands that you can use to configure an Cisco MGX 8850 for IP communications over ATM.

Example 10-1 Switch Commands for IP Communications over ATM

mgx8850a.7.PXM.a> ipifconfig atm0 A.B.E.F # Replace A.B.E.F with IP Addressmgmgx8850a.7.PXM.a> svcifconfig atm0 local 47.0091.8100.0000.0010.7b65.f258.0010.7b65.1111.01mgx8850a.7.PXM.a> svcifconfig atm0 router 47.0091.8100.0000.0010.7b65.f258.0010.7b65.ffff.f1mgx8850a.7.PXM.a> addcontroller 2 i 2 7 #if controller does not already existmgx8850a.10.AXSM.a > cnfcdsct 6mgx8850a.10.AXSM.a > upln 1.1mgx8850a.10.AXSM.a > addport 1 1.1 96000 96000 6 1mgx8850a.10.AXSM.a > addpart 1 1 2 500000 500000 500000 500000 1 20 32 52 1 20mgx8850a.10.AXSM.a > upport 1mgx8850a.10.AXSM.a > cnfilmi -if 1 -id 1 -ilmi 1 -vpi 0 -vci 16 -trap 1 -s 10 -t 10 -k 10 #Optional. This command configures ILMI for the port.mgx8850a.7.PXM.a> addaddr 10:1.1:1 47.0091.8100.0000.0010.7b65.f258.0010.7b65. ffff.f1 160 #Enter only at switch with direct connection to router. Omit if using ILMI.mgx8850a.7.PXM.a> dsppnsysaddr (example output)47.0091.8100.0000.0010.7b65.f258.0010.7b65.ffff/152Type: uni Port id: 17111041

mgx8850a.7.PXM.a> dsppnports

(example output)Per-port status summary PortId IF status Admin status ILMI state Total Activeconns 10:1.1:1 up up Undefined 3

Configuring the RouterTo support IP over ATM communications on the ATM router, you need to configure the following interfaces:




• ATM interface to switch

• Interface to the LAN that hosts the management workstation

To configure the ATM interface to the switch, you need to performs the following tasks:

• Create an ATM interface.

• Assign an IP address to the ATM interface.

• Assign an AESA to the ATM interface.

• Configure the ATM interface to be the ATMARP server for the switch.

If the router’s IP address for the ATM interface is on the same subnet as the IP address on the switch ATM interface, no additional configuration is required for the router’s IP LAN interface.

To configure the IP interface to the LAN, you need to perform the following tasks:

• If the router’s IP address for the ATM interface is not on the same subnet as the IP address on the switch ATM interface, you must manually configure on IP host-route for each MGX 8850 to which the interface will connect.

• Configure a routing protocol to broadcast the switch IP addresses to the LAN or create default routes to the switch on the management workstation.

The procedure you use to configure the ATM router will depend on the router you are using. The following example lists commands you can use on a Cisco router to support IP over ATM communications with the Cisco MGX 8850.

Example 10-2 Router Configuration Commands for IP Communications over ATM

config termip routingip route 0.0.0.0 0.0.0.0 W.X.Y.Z 1 (set default route)interface atm 0ip address A.B.C.D G.H.I.J # G.H.I.J = netmaskatm nsap-address 47.0091.8100.0000.0010.7b65.f258.0010.7b65.ffff.f1atm uni-version 3.1atm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmi #Optional. Enter to enable ILMI.atm ilmi-keepalive 10 #Optional. Enter to configure ILMI.atm esi-address 00107B65FFFF.F1 #Optional. Enter to support ILMI.atm arp-server selfno shut^Z

write memory



Chapter 10 Configurationcnflan

cnflan Configure LAN

This command configures node communication parameters, so the node can communicate with a Cisco WAN Manager terminal over an Ethernet LAN using TCP/IP protocol. The parameters all contain address information about the Ethernet TCP/IP network that connects the Cisco WAN Manager station to an IGX or BPX node. The values must conform to those of the network. The network administrator can supply the parameters.

Syntax

cnflan <IP_Address> <IP_Subnet_Mask> <Maximum LAN Transmit Unit> <TCP Service Port><GatewayIPAddr>

Related Commands

upln, dnln, cnfln

Attributes

<IPAddress> Specifies the Internet address of the node used in the TCP/IP protocol.

<IP Subnet Mask> Specifies a 32-bit mask that contains information about the bit lengths of the subnet ID and host ID address fields. The format of this field uses 1s for the subnet ID field and 0s for the host ID address field as defined in the TCP/IP protocol. The default value (in decimal notation) is 255 255 255.0. This mask denotes both subnet ID and host ID fields as 8-bit fields.

<Maximum. LAN Transmit Unit>

BPX nodes only: typical length is 1500 bytes.

<TCPServicePort> Specifies the node’s service point used by the transmission control protocol (TCP).

<GatewayIPAddr> Specifies the Internet gateway address.

Priviledge Jobs Log Node Lock

1 No Yes IGX, BPX Yes



Chapter 10 Configurationcnflan

Example

sw197 TN SuperUser IGX 8420 9.2 Apr. 7 1998 01:48 GMT Active IP Address: 172.29.9.111IP Subnet Mask: 255.255.255.0IP Service Port: 5120Default Gateway IP Address: 172.29.9.1Maximum LAN Transmit Unit: 1500Ethernet Address: 00.C0.43.00.1F.7F Type StateLAN READYTCP UNAVAILUDP READYTelnet READYTFTP READYTimeHdlr READYSNMP READY This Command: cnflan Enter IP Address:



Chapter 10 Configurationcnfnwip

cnfnwip Configure Network IP Address

The network IP address and subnet mask support statistics collection for Cisco WAN Manager. The cnfnwip command defines the IP address the system uses to pass messages between Cisco WAN Manager and the node. The Statistics Master process in Cisco WAN Manager Network collects statistics. The Statistics Manager requests and receives statistics using TFTP Get and Put messages. These TFTP messages pass between the node and the Statistics Master using IP Relay. (See the cnfstatmast description for details on setting the Statistics Master address.)

Syntax

cnfnwip <IPAddr> <IPSubnetMask>

Related Commands

None

Attributes

Example

cnfnwip 169.134.90.106 255.255.255.0

axiom TN Bootzilla IGX 32 9.2 Aug. 5 19981998 18:25 GMT

Active Network IP Address: 169.134.90.106Active Network IP Subnet Mask: 255.255.255.0

Last Command: cnfnwip 169.134.90.106 255.255.255.0

Next Command:

<IPAddr> IP address of the node: the format is nnn.nnn.nnn.nnn, where nnn can be 1–255

<IPSubnetMask> subnet mask: the format is nnn.nnn.nnn.nnn

Priviledge Jobs Log Node Lock

1 No Yes IGX, BPX Yes



Chapter 10 Configurationcnfstatmast

cnfstatmastConfigure statistics master SV+ address

Configures an IP address for the Statistics Master process in WAN Manager. The cnfstatmast command defines the IP address for routing the messages to and from the Statistics Master in WAN Manager.

The Statistics Master process requests and receives network statistics by using TFTP Get and Put messages. These TFTP messages pass between the node and the Statistics Master over IP Relay. See the cnfnwip description for details on setting a node address.

Syntax

cnfstatmast <ip Address>

Related Commands

cnfnwip, dspnwip

Attributes

Example

cnfstatmast 199.35.96.217

Configure 199.35.96.217 as the IP address for the Statistics Master.

ip address Specifies the IP address for the Statistics Master. IP addresses have 32-bits. The format of an IP address is x.x.x.x, where x is a value in the range 1–255.

Privilege Jobs Log Node Lock

1 Yes Yes IGX, BPX Yes



Chapter 10 ConfigurationConfiguring PNNI using CiscoView

Configuring PNNI using CiscoViewCiscoView provides the capability for configuring and displaying PNNI parameters on an MGX 8000 Series PXM 45 card.

Getting StartedStart the PNNI configuration by performing the following steps.

Step 1 In the svplus directory, start CiscoView by entering cview at the command prompt.

Step 2 Select the Cisco MGX 8000 device to be configured by selecting the IP address of the device in the top left corner of the CiscoView main window.

Step 3 When the device is displayed, right-click in the black area above or below the cards to display the configuration... message.

Step 4 Right click the configuration... message to display the Shelf Configuration window.

Step 5 Open the Category dropdown menu as shown in Figure 10-2.

Step 6 Select PNNI Controller Configuration.

Step 7 Click OK.

Figure 10-2 Shelf Configuration Window Showing Category Dropdown Menu

PNNI ConfigurationContinue the PNNI configuration by performing the following steps.

Step 1 Display the CiscoView PNNI Configuration window using steps 1 to 5 above.




This window has a drop-down menu that permits the user to select from 18-PNNI configuration categories. Categories consist of configuration dialog boxes and display boxes as shown in Figure 10-3.

Figure 10-3 PNNI Configuration

Step 2 Click on the desired configuration category to display its dialog box.

Each configuration dialog box consist of a table of parameter values associated with its category. Parameters that are configurable by the user have a white background and parameters that are for display only have a shaded background as shown in Figure 10-4.

Figure 10-4 Typical PNNI Configuration Dialog Box

Step 3 Where applicable, users can create a new row in a table by clicking the Create button at the bottom of the window. This action displays a Row Creation dialog box. The user enters the appropriate information about the new row and clicks OK. An example of a Row Creation dialog box is shown in Figure 10-5.

Figure 10-5 Row Creation Dialog Box

Step 4 When the configuration dialog box is configured, click OK. At this point another category can be selected.




PNNI Configuration CategoriesTable 10-1 shows the parameters for each of the PNNI categories.

Note Because of the large number of columns in some categories, some tables have been extended to a second category with the second category prefixed with "More". Hence the "More Atm Port Configurations" is an extension of "ATM Port Configuration". The same also applies to the "Atm Port Load Statistics" and "PNNI Node Configuration" categories.

Table 10-1 PNNI Parameters

PNNI Category Parameter

Atm Port Configuration cwspAdminStatus

ifIndexProp

cwspOperStatus

cwspSvcBlocked

cwspSpvcBlocked

cwspIlmiAddrReqEnable

cwspIlmiAutoConfEnable

cwspServReqEnable

cwspPhyIdentifierProp

cwspSignallingVpi

cwspSignallingVci

cwspRoutingVpi

cwspRoutingVci

cwspMaxVpiBits

cwspMaxVciBits

More ATM Port Configuration cwspUniType

ifIndexProp

cwspUniVersion

cwspNniVersion

cwspPhyIdentifierProp

cwspSide

cwspMaxP2pCalls

cwspMaxP2mpRoots

cwspMaxP2mpLeafs

cwspMinSvccVpi

cwspMaxSvccVpi

cwspMinSvccVci

cwspMaxSvccVci




cwspMinSvpcVpi

cwspMaxSvpcVpi

cwspEnhancedlisp

Atm Port Call Incoming Statistics cwspCountReset

PortIndexProp

cwspInCallAttempts

cwspInCallEstabs

InCallFailures

InFilterFailures

InRouteFailures

InResrcFailures

InTimerFailures

InCrankbacks

Atm Port Call Outgoing Statistics cwspOutCallAttempts

PortIndexProp

cwspOutCallEstabs

cwspOutCallFailures

cwspOutFilterFailures

cwspOutRouteFailures

cwspOutResrcFailures

cwspTimerFailures

cwspOutCrankbacks

Atm Port Load Statistics cwspLoadBwTotal

ifIndexProp

cwspLoadMaxBwCbr

cwspLoadMaxBwRtVbr

cwspLoadMaxBwNrtVbr

cwspLoadMaxBwAbr

cwspLoadMaxBwUbr

cwspLoadBwAvail

cwspLoadAvlBwCbr

cwspLoadAvlBwRtVbr

cwspLoadAvlBwNrtVbr

cwspLoadAvlBwAbr

cwspLoadAvlBwUbr

cwspLoadVcAvail

Table 10-1 PNNI Parameters (continued)





cwspLoadAvlVcCbr

cwspLoadAvlVcRtVbr

cwspLoadAvlVcNrtVbr

cwspLoadAvlVcAbr

cwspLoadAvlVcUbr

More Atm Port Load Statistics cwspLoadCtdCbr

ifIndexProp

cwspLoadCtdRtVbr

cwspLoadCtdNrtVbr

cwspLoadCtdAbr

cwspLoadCtdUbr

cwspLoadCtvCbr

cwspLoadCdvRtVbr

cwspLoadCdvNrtVbr

cwspLoadClr0Abr

cwspLoadClr0Ubr

cwspLoadClr1Cbr

cwspLoadClr1RtVbr

cwspLoadClr1NrtVbr

cwspLoadClr1Abr

cwspLoadClr1Ubr

cwspLoadMinGurCrCbr

cwspLoadMinGurCrRtVbr

cwspLoadMinGurCrNrtVbr

cwspLoadMinGurCrAbr

cwspLoadMinGurCrUbr

Atm Port Signalling Statistics (Rcv) cwspCallProcRcv

SigPortIndexProp

cwspConnectRcv

cwspConnectAckRcv

cwspSetupRcv

cwspReleaseRcv

cwspReleaseCommp[Rcv

cwspRestartRcv

cwspRestartAckRcv

cwspStatusRcv






cwspStatisEnqRcv

cwspNotifyRcv

cwspAlertRcv

cwspProgressRcv

cwspAddPtyRcv

cwspAddPtyAckRcv

cwspAddPtyRejRcv

cwspDropPtyRcv

cwspIncorrectMsgRcv

SigCounter Reset

Atm Port Signalling Statistics (Xmit) cwspCallProcXmt

SigPortIndexProp

cwspConnectXmt

cwspConnectAckXmt

cwspSetupXmt

cwspReleaseXmt

cwspReleaseCommp[Xmt

cwspRestartXmt

cwspRestartAckXmt

cwspStatusXmt

cwspStatisEnqXmt

cwspNotifyXmt

cwspAlertXmt

cwspProgressXmt

cwspAddPtyXmt

cwspAddPtyAckXmt

cwspAddPtyRejXmt

cwspDropPtyRcv

cwspTimerExpires

cwspTimerExpires

cwspLastCause

cwspDiagnostic

cwspSscopStatus

SigCounterReset

SVC CAC Configuration cwspMaxVcCbr

ifIndexProp






cwspMaxVcRtVbr

cwspMaxVcNrtVbr

cwspMaxVcAbr

cwspMaxVcUbr

cwspMinVcCbr

cwspMinVcRtVbr

cwspMinVcNrtVbr

cwspMinVcAbr

cwspMinVcUbr

cwspMaxVcBwCbr

cwspMaxVcBwRtVbr

cwspMaxVcBwNrtVbr

cwspMaxVcBwAbr

cwspMaxVcBwUbr

SVC CAC Configuration cwspDefaultCdvtCbr

InIndexProp

cwspDefaultCdvtRtVbr

cwspDefaultCdvtNrtVbr

cwspDefaultCdvtAbr

cwspDefaultCdvtUbr

cwspDefaultMbsRtVbr

cwspDefaultMbsNrtVbr

Atm Port Adresses cwspAtmAddressProp

ATMPortIndexProp

cwspAddrLenProp

cwspAddrType

cwspAddrProto

cwspAddrPlan

cwspAddrScope

cwspAddrRedistribute

CWSP Interfaces Operation Configuration ifIndexProp

cwspOperIlmiEnable

cwspOperIfcType

cwspOperIfcSide

cwspOperMaxVPCs

cwspOperMaxVCCs






cwspOperMaxVpiBits

cwspOperUniType

cwspOperUniVersion

cwspOperDeviceType

cwspOperIlmiVersion

cwspOperNniSigVersion

cwspOperMaxSvpcVci

cwspOperMinSvpcVci

cwspOperMaxSvpcVpi

cwspOperMinSvpcVpi

cwspOperMaxSvccVci

cwspOperMinSvccVci

PNNI Node Configuration pnniNodeIndexProp

pnniNodeLevel

pnniNodeId

pnniNodeLowest

pnniNodeAdminStatus

pnniNodeOperStatus

pnniNodeDomainName

pnniNodeAtmAddress

pnniNodePeerGroupId

More PNNI Node Configuration pnniNodeIndexProp

pnniNodeRestrictedTransitProp

pnniNodeRestrictedBranchingProp

pnniNodeComplexRepProp

pnniNodeDatabaseOverload

pnniNodePlses

PNNI PGL Configuration pnniNodePglLeadershipPriorityProp

pnniNodeCfgParentNodeIndexProp

pnniNodePglInitTimeProp

pnniNodePglOverrideDelayProp

pnniNodePglReelectTimeProp

pnniNodePglState

pnniNodePreferredPgl

pnniNodePeerGroupLeader

pnniNodePglTimeStamp






PNNI Address Summary pnniNodeActiveParentNodeId

Type

Type

PnniSummaryAddressAddressProp

PreficLength

pnniSummaryAddressSuppressState

PNNI Base Group Configuration pnniHighestVersion

pnniLowestVersion

pnniDt1CounterOriginator

pnniDt1CountBorder

pnniCrankbackCounterOriginator

pnniCrankbackCountBorder

pnniAltRouteCounterOriginator

pnniAltRouteCountBorder

pnniRouteFailCounterOriginator

pnniRouteFailCountBorder

pnniFailUnreachableCounterOriginator

pnniFailUnreachableCountBorder



C H A P T E R



11Migration From Automatic Routing Management to PNNI Using Cisco WAN Manager

This chapter provides details on the AutoRoute to PNNI migration process, including upgrading switch software, and creating and managing extended permanent virtual circuits (XPVCs) and extended permanent virtual paths (XPVPs).

Migration Process OverviewThe migration process consists of the following tasks:

• Upgrading Cisco WAN Manager from Release 10.x to 11

• Preparing to upgrade BPX switch software from Release 9.2.3z to 9.3.30

• Gracefully upgrading the BPX node (BCC card pair)

• Verifying that the upgrade has propagated to all the nodes in the network

• Upgrading the MGX 8850 from Release 2 to Release 2.1

Upgrade Cisco WAN Manager from 10.x to 11.Upgrade Cisco WAN Manager from Release 10.x to 11. Refer to the Upgrading Cisco WAN Manager chapter in the Cisco WAN Manager Installation Guide for Solaris, Release 11.

Preparing To Upgrade Cisco BPX Switch Software From 9.2.34 to 9.3.30Upgrade the Cisco BPX switch software from Release 9.2.34 to Release 9.3.30. Complete the following steps:

Step 1 Use “Configuration Save & Restore” on the node before starting the upgrade process.

Refer to Chapter 13, "Saving and Restoring Node Configurations", in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Config-save-restore GUI to save the configuration on the switch.

Step 2 Enter the dspcds command in a telnet window to verify that the BCC cards are running Release 9.2.34 of the BPX switch software.



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerMigration Process Overview

Step 3 Verify with the dspcds command that the node contains the appropriate firmware and hardware revisions.

Refer to the Compatibility Matrixes in the Switch Software Release Notes for Release 9.2.34 to confirm this.

The user can also verify the same information using Network Browser. Refer to Chapter 5, "Network Browser", in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser.

Step 4 Enter the clrlog, clrswlog and clrcderrs commands to clear the error logs and SW logs on the node.

Syntax and detailed descriptions of these commands are available in the Cisco WAN Switching Command Reference, Release 9.3.30.

Step 5 Verify that the nodes in the Automatic Routing Management network are free of alarms, including card alarms and SW alarms by entering the dspalms and dspnodes commands on the node.

Syntax and detailed descriptions of these commands are available in the Cisco WAN Switching Command Reference, Release 9.3.30.

Step 6 Verify that the Cisco WAN Manager Topology and Network Browser applications also show that the nodes are free of alarms

Step 7 Enter the dspcons, dspcons -fail, dspcons -abit, and dspcons -oam commands to verify that none of the existing complete connections is in failed state, and there are no A-bit or OAM alarms. All incomplete and failed connections are in failed state.

Step 8 Use the Connection Manager GUI, or the user_connection and atm_connection tables to verify that none of the existing complete connections is in failed state, and that there are no A-bit or OAM alarms. All incomplete and failed connections are in failed state.

Step 9 Enter the dspports command to verify that all the ports are free of alarms

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dspports command.

Step 10 Verify, using the Connection Manager and the Network Browser application, that the ports are free of alarms.

Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser GUI. Refer to Chapter 3, Connection Manager, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Connection Manager GUI.

Step 11 Enter the dsptrks and dsplns commands to verify that all the trunks and lines are free of alarms.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dsptrks and dsplns commands.

Step 12 Use the Topology application and the Network Browser application to verify that the lines are free of alarms.

Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Topology Manager, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Topology application.

Step 13 Enter the tstdelay command to verify data continuity on the complete end to end Automatic Routing Management PVCs.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstdelay command. All incomplete and failed connections are in failed state.

Step 14 Enter the tstconseg command to verify data continuity on all connections initiated to the CPE.




Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstconseg command. All incomplete and failed connections are in failed state.

Gracefully Upgrading the BCC Card Pair on the BPX nodePerform the following steps to upgrade gracefully the BCC cards on a BPX node

Step 1 Use tftp to load the saved configuration on the node as part of the upgrade process.

Refer to Chapter 12, Downloading Software and Firmware, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on entering TFTP commands to load the new version of software and firmware to the node.

Step 2 While upgrading the node, verify that the node is not shown in the topology GUI but comes up after the upgrade is done.

Step 3 Verify that both processor cards in the BPX node are upgraded to 9.3.30 version by entering the dspcd 7 and dspcd 8 commands to verify that the SWSW version displayed is 9.3.30.

Step 4 In Cisco WAN Manager, use the Network Browser and CiscoView applications to confirm that the upgraded version of system software (9.3.30) displays the installation correctly on both of the processor cards.

Gracefully Upgrading the Rest of the Cards on the BPX NodePerform the following steps to upgrade gracefully the remaining cards on a BPX node

Step 1 Verify that the BPX node is upgraded to 9.3.30 and is free from alarms by entering the dspcds command.

The SWSW version displayed should be 9.3.30 and all the cards in the network should not display any alarms.

Step 2 In Cisco WAN Manager, use the Network Browser and CiscoView applications to confirm that the upgraded version of system software (9.3.30) displays as having been installed correctly on all cards in the network.

Step 3 Enter the dspalms and dspnodes commands to verify that there are no network alarms.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dspalms and dspnodes commands.

Step 4 Verify, using the Topology application and the Network Browser application, that there are no network alarms.

Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser GUI. Refer to Chapter 3, Topology Manager, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Topology application.

Step 5 Enter the dspcons, dspcons -fail, dspcons -abit, and dspcons -oam commands to verify that none of the existing complete connections is in failed state, and there are no A-bit or OAM alarms. All incomplete and failed connections are in failed state.




The user can also verify the same information using the Connection Manager GUI, and/or the user_connection and atm_connection tables that none of the existing complete connections is in failed state, and there are no A-bit or OAM alarms. All incomplete and failed connections are in failed state.

Step 6 Enter the dspports command to verify that all the ports are free of alarms. Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dspports command.

The user can also verify the same information using the Connection Manager and the Network Browser application, that the ports are free of alarms.

Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Connection Manager, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Connection Manager GUI.

Step 7 Enter the dsptrks and dsplns commands to verify that all the trunks and lines are free of alarms.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the dsptrks and dsplns commands.

Step 8 Verify, using the Topology application and the Network Browser application, that the trunks and lines are free of alarms.

Refer to Chapter 5, Network Browser, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Network Browser GUI and to Chapter 3, Topology Manager, in the Cisco WAN Manager User’s Guide, Release 11 for detailed instructions on using the Topology application.

Step 9 Enter the tstdelay command to verify data continuity on the complete end to end Automatic Routing Management PVCs.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstdelay command. All incomplete and failed connections are in failed state.

Step 10 Enter the tstconseg command to verify data continuity on all connections initiated to the CPE.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for syntax and a detailed description of the tstconseg command. All incomplete and failed connections are in failed state.

Upgrading Existing Switch Software to 9.3.30This section describes the process of upgrading to the appropriate Release of switch software to migrate from Automatic Routing Management to PNNI. To begin the software upgrade procedure, enter the loadrev command. The node will search for the specified software revision from a Cisco WAN Manager workstation, a PC running StrataView Lite, or from another node. Once the node finds a download source, the flash EEPROM on the active processor card will erase. The flash EEPROM will then be loaded with the new software using a block file transfer protocol. This process takes approximately one hour using the 19.2 Kbps serial port or 45 minutes via Ethernet.

Much less time is required for downloading from neighbor nodes via network trunks. Output during a download is shown below:

Info NPM [or BCC or NPC] 1 downloading Flash with Revision 9.3.30 17:49:45Info NPM [or BCC or NPC] 1 downloaded Flash with Revision 9.3.30 18:39:29




Once the flash EEPROM on the active processor card has been loaded, the RAM image on the standby processor card is erased in preparation for the new software image download. Once the RAM is cleared, the new image is downloaded into RAM from the flash EEPROM on the active processor. When the RAM is successfully downloaded, the standby processor restarts with the new software. This example shows the NPM on an IGX; it is equally valid for a BCC on a BPX.

The following lines are typical event log messages resulting from the loadrev command completing the download.

Info NPM 2 Removed 18:39:32Info NPM 2 Restarted due to a Primary Revision Change 18:39:42Info Standby NPM [or BCC or NPC] 2 downloading Revision 8.3.20 18:39:48Info Standby NPM [or BCC or NPC] 2 Update Completed 18:41:11Info Standby NPM [or BCC or NPC] 2 downloaded Revision 8.3.20 18:52:25Info NPM 2 Removed 18:52:26Info NPM 2 Restarted due to a Completed Download 18:52:32

When a new revision of software is loaded into the standby processor card’s RAM, the existing database of configuration parameters must be converted to the new structure. When this process is completed, the standby processor card will enter the “Upgraded” state.

Info Standby NPM 2 Update Completed 19:00:52

To run the new software, enter the runrev command. This causes a processor switch-over, so the standby processor that's loaded with the new software version (in RAM) becomes the active processor. The processor with the original software revision enters a “locked” state. The original version of software is maintained in the locked processors' RAM in case a fall-back is necessary. The node operates in a non-redundant mode until the “locked” processor is upgraded to the new software revision.

Info NPM 1 Revision Installation - switched to NPM 2 19:40:09Info Standby NPM 1 downloaded Revision 9.2.34 19:40:09Info Standby NPM 1 Update Completed 19:40:18

When the new software revision is verified to be operating correctly, the “locked” processor must be updated with the new software. Enter another loaders command to purge the original software version. The “locked” processor restarts and loads RAM with the new software image from flash EEPROM.

Finally, both processor cards are loaded with the new software.

Info NPM 2 downloading Flash with Revision 8.3.20 19:41:57Info Standby NPM 1 Update Completed 19:42:54Info NPM 1 Removed 19:42:55Info NPM 1 Restarted due to a Completed Download 19:43:04Info NPM 2 downloaded Flash with Revision 8.3.20 19:44:23Info Standby NPM 1 Update Completed 19:52:05

Upgrading the MGX 8850 from Release 2 to Release 2.1 SoftwareRefer to Appendix A, “Downloading and Installing Software Upgrades” of the Cisco MGX 8850 and Cisco MGX 8950 Routing Switch Software Configuration Guide, Release 2.1. This appendix describes how to locate, download, and install software updates for the switch. Because software updates are stored in the switch file system, it also includes a section on browsing the file system. This appendix includes the following sections:

• Upgrade Process Overview

• Quickstart Procedures for Software Upgrades

• Quickstart Procedures for Software Downgrades

• Browsing the File System



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerXPVC Creation Overview

• Locating Software Updates

• Copying Software Files to the Switch

• Upgrade Procedures for PXM45 and AXSM Cards

• Upgrade Procedures for RPM-PR Cards

• Troubleshooting Upgrade Problems

XPVC Creation OverviewNote that in the following sections, mention of Extended Permanent Virtual Circuit (XPVC) also implies Extended Permanent Virtual Path (XPVP), unless the section says explicitly that one or the other is not applicable.

Step 1 Use the switch CLI to configure XLMI and ENNI on BPX and MGX ports

Extended Local Management Interface protocol (XLMI), in conjunction with the LMI Neighbor Discovery feature, enables the exchange of connection status and topology information between the BPX and MGX switches.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for command syntax and a detailed description of the process of configuring BPX ports to support XLMI. Refer to the Update to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 for command syntax and a detailed description of the process of configuring Cisco MGX 8850 Release 2.1 ports to support XLMI.

Enhanced (or Friendly) Network-to-Network Interface (ENNI) links individual networks of Cisco Automatic Routing Management switches to individual networks of PNNI switches. When a port is configured to ENNI, all new SPVC/SPVPs added to that port will have the OAM segment configured as non-segment.

Note If there are already existing connections on a port, you cannot configure the port from UNI or NNI to EUNI or ENNI, or vice versa. You must delete all existing connections on a port before configuring the port to ENNI or EUNI.

In a regular connection, links joining two network domains serve as segment endpoints for OAM (segment) loopback. In order for all OAM cell types to traverse end-to-end without being looped back or terminated at the ingress of the intermediate links, XPVCs and XPVPs are provisioned across ENNI networks to allow segment OAM cells to flow over end-to-end OAM segment loops for the provisioned length of the XPVC or XPVP.

Refer to the Cisco WAN Switching Command Reference, Release 9.3.30 for command syntax and a detailed description of the process of configuring BPX ports to support ENNI. Refer to the Update to the Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2.1 for command syntax and a detailed description of the process of configuring Cisco MGX 8850 Release 2.1 ports to support ENNI.

Step 2 Use the Network Browser and Topology Map to display XLMI link status.

Figure 11-1 below shows the popup menu item that appears when you right-click on an XLMI link.




Figure 11-1 Display XLMI Trunk Popup




The display that opens after selecting the Display Trunk popup is shown in Figure 11-2.

Figure 11-2 XLMI Trunks Display

You can also verify the status of the ENNI ports in the Network Browser application, as shown in Figure 11-3.




Figure 11-3 Verifying ENNI Ports in the Network Browser

For more information on the Network Browser application and its use, see Chapter 5, “Network Browser” of the Cisco WAN Manager User’s Guide, Release 11.

Step 3 Manually define the AR-PNNI interface(s). Use the XPVC Preferred Flag checkbox within the XPVC Preferred Table Configurator application in Cisco WAN Manager.) Define whether the selected BPX node should use a particular preferred node when setting up an XPVC connection.

For an example of the Preferred Table Configurator application, refer to Chapter 3 of the Cisco WAN Manager User’s Guide, Release 11.

Note Connection Manager is display-only for XPVCs.

Step 4 Evaluate the status of your XPVC using the end-to-end test delay diagnostic. See Figure 11-12 through Figure 11-14 in this chapter for examples of this diagnostic tool.

The above list summarizes the steps required to create and verify an XPVC using CWM Release 11.



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerXPVC as a Migration Connection

XPVC as a Migration ConnectionAn XPVC is an end-to-end virtual circuit that traverses at least one UNI or NNI interface on which XLMI has been enabled. The XPVC, which is shown in the following graphic, Figure 11-4, provides the first step towards migration from an existing proprietary Automatic Routing Management infrastructure toward standards-based PNNI by encompassing networks with both Automatic Routing Management and PNNI routing nodes.

Figure 11-4 Migration Connection Example

There are two basic types of XPVC that you can create using Cisco WAN Manager 11:

• AR-PNNI-AR—The XPVC originates and terminates at endpoints on an Automatic Routing Management BPX switch or MGX feeder node attached to a BPX switch. This is a three-segment (PVC to SPVC to PVC) XPVC.

• AR-PNNI—The XPVC originates at an Automatic Routing Management switch or feeder endpoint, and terminates at a PNNI endpoint on an Cisco MGX 8850 switch (or vice versa). This is a two-segment (PVC to SPVC) XPVC.

Each XPVC segment consists of an actual virtual circuit, that is a PVC, an SPVC, or a Hybrid (feeder) VC. Each of these circuits could, in turn, comprise more than one segment if feeders are included. Cisco WAN Manager software ties together these circuits to create an end-to-end XPVC. XPVC provisioning is supported across a maximum of three networks.

AR network

PNNI networkXLMI

BPX BPX

BPXBPX

PVC

MGX MGX

XLMI

Feeder

PVCSPVC 6625

5



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerXPVC as a Migration Connection

In earlier Releases, you could construct circuits across multiple networks that were connected with NNI interfaces. However, the NNI interface loops back the management messages (OAM segment cells) so that end-to-end management of the circuit is not possible. This problem is resolved with the proprietary ENNI interface that is supported on BXM cards in the Cisco BPX switch and on the AXSM and PXM45 cards in the MGX 8850 switches.

1. XLMI enables neighbor discovery between Automatic Routing Management and PNNI domains

2. ENNI enables end-to-end OAM cell flow, which provides end-to-end management

XPVC/XPVP Provisioning and ManagementThere are two ways to provision an XPVC using Cisco WAN Manager Release 11:

1. Using a special script (CWM-XPVC-CLI), from the Unix CLI prompt

2. Using the SNMP Service Agent

You can provision end-to-end XPVCs using either a script that is manually invoked from the Cisco WAN Manager Unix command line (the CWM-XPVC-CLI) or programmatically via the SNMP interface of the Service Agent. Note that the CWM-XPVC-CLI supports addition and deletion only, whereas you can also modify an existing XPVC using the Service Agent.

Before creating an XPVC you must configure the BPX and MGX ports that connect the Automatic Routing Management and PNNI networks to support XLMI and ENNI. This can be done by using the switch CLI. Once you have done this, you will be able to verify the successful activation and discovery of the XLMI links through the Network Browser and by inspection of the Topology Map.

Although Cisco WAN Manager is able to automatically discover the XLMI links, you must define manually how each BPX node, including those that are not directly attached to an MGX PNNI port, reaches the PNNI network. The XPVC Preferred Table Configurator application defines the XLMI interface that XPVCs from a particular BPX switch must use to reach the PNNI network. The Configurator also includes an XPVC Preferred Flag, which you must enable on a node-basis to enable XPVC routing between two BPX nodes. Details of the Configurator are included later in this chapter.

Once you have created the XPVC using the CWM-XPVC-CLI, you can use the Connection Manager to display status information and also to perform an end-to-end test that will provide the round-trip delay on a selected connection. End-to-end test delay is also available through the SNMP service agent.

Supported cards: BXM, ASI, AUSM, FRSM, RPM/RPM-PR, ATM = ATM or RPM endpoint

BPX feeder or MGX R2 feeder = Cisco MGX 8220, Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8850 Release 1

Table 11-1 Supported Connections for XPVCs

End Point Type XPVC type ATM-ATM FR-FR ATM-FR

BPX Feeder to BPX Feeder AR-PNNI-AR Y Y Y

BPX Feeder to MGX R2 Feeder AR-PNNI (Hybrid) Y Y Y

BPX to BPX AR-PNNI-AR Y — —

BPX to MGX 8850 AR-PNNI Y — —

BPX to BPX Feeder AR-PNNI-AR Y — Y

BPX to MGX R2 Feeder AR-PNNI (Hybrid) Y — Y

BPX Feeder to MGX 8850 AR-PNNI Y — Y



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerConnection Creation for XPVC/XPVPs

The above table summarizes the endpoint and XPVC connection types that are supported in Cisco WAN Manager 11. Associated with each connection type are specifically supported service types. Refer to the Cisco WAN Manager 11 Release Notes for a complete mapping of the specific connection and service types supported.

Note Not all service modules are supported for XPVC user endpoints in Cisco WAN Manager Release 11. Specifically, the CESM and VISM cards are not included.

Connection Creation for XPVC/XPVPsThe following steps summarize the process for creating and verifying an XPVC or XPVP.

Creating an XPVC

Step 1 Using the applicable switch CLI, do the following action

• Configure, activate and verify the XPVC endpoints (lines, ports)

– Activate XLMI on the BXM and AXSM ports

– Activate ENNI on the XLMI links

Step 2 Verify that the XLMI links are displayed on the Topology Map.

Step 3 Use the Cisco WAN Manager XPVC Preferred Table Configurator to associate BXM ports with MGX PNNI ports

Step 4 If your connections are using non-default parameters, modify the appropriate parameter file.

Step 5 Add the connection using the cwmAddConn script.

Step 6 Launch the Connection Manager GUI.

Step 7 Select Nod, > View > XPVC Segments.

Step 8 Test connection end-to-end round-trip delay.

XPVC Preferred Table ConfiguratorThe XPVC Preferred Table Configurator is a Cisco WAN Manager application that allows you to define the mapping between XLMI/ENNI ports on BPX nodes and the corresponding AXSM ports in the PNNI network. The overall function of the XPVC Preferred Table Configurator is described in Chapter 3, “Using Network Topology” in the Cisco WAN Manager User’s Guide, Release 11.



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerCWM-XPVC-CLI

CWM-XPVC-CLIThis section highlights the main features of the CWM-XPVC-CLI. These features are as follows.

• HP OpenView and Cisco WAN Manager Service Agent are required

• Cisco WAN Manager Release 11 uses an SNMP script that invokes the Service Agent ConnProxy

• Two new commands (formed from Unix shell scripts)

– cwmAddConn to add an XPVC

– cwmDelConn to delete an XPVC

• Four optional parameter files are used for non-default settings:

a. atmendpt.conf for ATM endpoint

b. frendpt.conf for Frame Relay endpoint

c. rpmendpt.conf for RPM endpoint

d. connparam.conf for connection parameters

The CLI is invoked from the Unix command line, and in turn invokes the ConnProxy process in the Cisco WAN Manager Service Agent. The Service Agent must have been previously installed on the Cisco WAN Manager workstation. Also, HP OpenView must be installed and running since the CLI uses the SNMP command tools included with OpenView.

The CLI supports the addition and deletion of XPVCs, but not modification. If you need to modify an XPVC, you must first delete it then add it again with the new parameters.

In addition to the add and delete scripts, Cisco WAN Manager provides several parameter files. These files are sample templates that you can modify if the default parameters are not appropriate. The parameter files are of two basic types:

1. Endpoint Parameters—Files are included for Frame Relay, ATM and RPM endpoints. For example, you can create a new ATM Endpoint file and define values for parameters such as the ingress policing for the connection.

2. Connection Parameters—You can use the standard file as a template for a new file with non-default connection-specific parameters, such as trunk avoidance.

The shell scripts and the parameter files are stored in the /usr/users/svplus/tools directory.

Adding an XPVCThe following example shows how the syntax for the cwmAddConn command is used to create an XPVC. This command and its associated parameters are entered at the Unix command line by an authorized Cisco WAN Manager user. Mandatory parameters are shown like this <cwmHost>, and optional parameters as shown inside brackets, for example: [-tout …].

Example (Add an XPVC Syntax)

Add an XPVC CLI syntax%cwmAddConn<cwmHost><snmpCommunity><localEndpoint><localEndpointType><remoteEndpoint>




<RemoteEndpointType><serviceType>[-help][-tout <TimeOut> ][-vc <VCType>][-desc \"<ConnectionDescriptor>\"][-lfile <LocalEndpointParameterFile>][-rfile <RemoteEndpointParameterFile>][-cfile <ConnectionParameterFile>]

The mandatory parameters for cwmAddConn are shown in Table 11-2.

Table 11-2 Mandatory Parameters

Parameter Description

cwmHost The name of the Unix host on which Cisco WAN Manager is running

snmpCommunity SNMP Community String to access Cisco WAN Manager SNMP Agent. The default string is “private”, but it can be changed by editing the file /usr/users/svplus/config/SNMPProxy.conf.

localEndpoint The local endpoint, defined as <RoutingNodename.FeederName.Slot.Line.Port.Vpi|Dlci[.Vci]>.

Examples of the endpoint syntax are as follows:

– An ATM VC originating on a BPX port: bpx01..4..1.20.250. Note that where a term is not required it is omitted, as is the following case where there is no FeederName or Line. Port equates to line in the case of the BPX node, since virtual ports are not supported with XPVCs.

– An ATM VP originating on a BPX port: bpx01..4..1.20.

– A VC originating on an RPM in an MGX feeder node: bpx02.mgx02.10..1.0.250

– A VP originating on an RPM in an MGX feeder node: bpx02.mgx02.10..1.30.

– A Frame Relay connection originating on a FRSM port in an MGX feeder node: bpx03.mgx01.5.2.5.300

localEndpointType fr, atm or rpm

remoteEndpoint The local endpoint, defined in the same format as the local endpoint.

remoteEndpointType fr, atm or rpm

serviceType cbr1, vbr1, vbr2, vbr3, abrfs, frfs, fr, ubr1, ubr2, abr1, rtvbr1, rtvbr2 or rtvbr3




Optional parameters are indicated by keywords, and are shown in Table 11-3

.

Note Endpoint parameter files for an RPM must contain the correct MGX node User ID and password, and the RPM password.

The following example shows a cwmAddConn command for creating an XPVC. In this example, the local endpoint is an ATM port on a BPX node, bpx1. The port is slot 4, port 1 and the VPI.VCI is 20.356. The remote endpoint is on port1, line 2 of the FRSM card in slot 6 of the feeder node mgx08 attached to bpx6. The circuit has the DLCI 356.

%cwmAddConncwm1 \ <cwmHost>private \ <snmpCommunity>bpx1..4..1.20.356 \ <localEndpoint>atm \ <localEndpointType>bpx6.mgx08.6.2.1.356 \ <remoteEndpoint>fr \ <RemoteEndpointType>vbr3 \ <serviceType>-desc “ATFR bpx1-mgx08” \-cfile /usr/users/ATFR_parms1

Note that each parameter in the command is entered on a separate line, and that each line except the last is terminated by “ \” (space backslash).

This example also includes a user-created connection parameter file (AFR_parms1) that includes one or non-default settings.

Table 11-3 Optional Parameters


help Outputs the help text with the command syntax.

tout <TimeOut> Defines the time out period in seconds before the system abandons the connection attempt.

vc <VCType> Defines the type of connection to be created. Choices are pvc, spvc, hybrid, or xpvc. You can use this parameter to override the standard Cisco WAN Manager provisioning rules. For example, if you want a connection between two BPX nodes that both have the XPVC Preferred Flag enabled to be routed as an Automatic Routing Management PVC,rather than as an XPVC, set the VCtype to pvc.

desc \”ConnectionDescriptor”\ Defines a Connection Descriptor string that must be entered inside double quotes.

lfile <LocalEndpointParameterFile> Defines the path to a user-created file for local endpoint parameters.

rfile <RemoteEndpointParameterFile> Defines the path to a user-created file for remote endpoint parameters.

cfile <ConnectionParameterFile> Defines the path to a user-created file for connection parameters.




%cd /usr/users/svplus/config%cp connfparm.conf /usr/users/ATFR_parms1%vi /usr/users/ATFR_parms1### ATFR_parms1svConnOvrSubOvrRide 2 # enable oversub on FRSMsvConnTrkAvoidType 2 # avoid satellite trunks#:wq!

Note Obtain parameter values from the Service MIB for supported parameters.You will need to verify the allowable values for the parameters you wish to modify. The Service MIB is stored in /usr/users/svplus/mibs/SV+Service.mib, and can be viewed from the Unix command line. Alternatively, refer to the Cisco WAN Manager SNMP Service Agent Release 11.

%cwmAddConncwm1 \...-cfile /usr/users/ATFR_parms1

Deleting an XPVCThe syntax for the cwmDelConn command is shown in the following example.

Example (Delete an XPVC Command Syntax)

Example 1

%cwmDelConn<cwmHost><snmpCommunity><anyEndpoint><EndpointType>[-help][-tout <TimeOut> ][-rend <RemoteEndPoint>][-lfile <LocalEndpointParameterFile>][-rfile <RemoteEndpointParameterFile>]

The following is an example of the cwmDelConn command that is used to delete an XPVC with RPM endpoints.

Example 2

%cwmDelConncwm1 \<cwmHost>private \<snmpCommunity>bpx2.mgx02.9..1.0.250 \<anyEndpoint>*rpm \<EndpointType>-lfile /usr/users/RPM/passwds **

Note anyEndpoint can either be local or remote; the EndpointType must match




Note The passwds parameter file must contain the user name and passwords for the RPM

When deleting an XPVC, you provide either the local or the remote endpoint.

The endpoint type must be appropriate for the endpoint that you select.

Parameters that differ from those for cwmAddConn are shown in Table 11-4.

:

Note Endpoint parameter files for an RPM must contain the correct MGX node User ID and password, and the RPM password.

Connection Manager Support for XPVCs

The Connection Manager in Cisco WAN Manager Release 11 provides support for XPVCs. Supported features include the following:

• Filter on XPVCs and dangling segments. A dangling segment is an XPVC segment that has been discovered by Cisco WAN Manager but which is not part of an end-to-end XPVC.

• View the parameters for XPVCs and individual XPVC segments

• Monitor alarm status for an XPVC or an individual XPVC segment

• Deletion of dangling segments

• End-to-end test delay

Table 11-4 Parameters differing from those in cwmAddConn


anyEndpoint The local or remote endpoint. If one of the endpoints is an RPM, this must be the RPM8,and both the –lfile and –rfile parameters must be defined.

EndpointType fr, atm, or rpm, corresponding to the selected endpoint

-rend <remoteEndpoint> For an RPM endpoint, this is the remote endpoint.If you define this optional parameter, then anyEndpoint must refer to the local endpoint.

-lfile <LocalEndpointParameterFile> Defines the path to a user-created file for local endpoint parameters. This is only required for an RPM endpoint.

-rfile <RemoteEndpointParameterFile> Defines the path to a user-created file for remote endpoint parameters. This is only required for an RPM endpoint.



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerXPVC Provisioning via Service Agent

XPVC Provisioning via Service AgentThis section provides procedures for provisioning XPVC connections via the Service Agent.

For a XLMI Configuration

SET svAtmPortSignallingProtocol in svATMPortTable to XLMI for NNI port.

For a ENNI Configuration

SET svATMPortType in svATMPortTable to ENNI or EUNI.

For Adding an XPVC Connection

SET endpoints and parameters in End Point Tables. rpmEndPointTable, atmEndPointTable, frEndPointTable are applicable.

SET svConnRowStatus in svConnTable to create (4).

SET svConnProtocolType to xpvc for XPVC connection.

An XPVC connection can be added using the CWM-XPVC-CLI without specifying the VC type or using the Service MIB without specifying the svConnProtocolType.

The ConnProxy will determine the correct protocol type (PVC/SPVC/HYBRID/XPVC) based on the endpoints chosen and the contents of the xpvc_preferred table.

The protocol type will be automatically chosen as XPVC provided all user endpoints chosen in the Automatic Routing network have a xpvc_preferred table entry with the preferred flag set.

For Deleting an XPVC Connection

SET svConnRowStatus for XPVC deletion.

For Modifying an XPVC Connection

SET endpoints and parameters in End Point Tables and svConnTable (except CC related objects).

SET cwmConnPrefRoute for PVC segment of the XPVC in cwmConnTable.

Location of ConnProxy ScriptsScripts can be found in /usr/users/svplus/scripts/proxyscripts/connproxy. The following scripts are provided:

• AddConn

• DelConn

• FaultIsolation

• GetAnyConn

• GetConErr

• Get ConnDetails

• GetConnIndex




• ModConn

• TestConnDelay

Adding an XPVC Connection: AddConn script

AddConn <proxyHost> <localType> <localNode> <localChan> <remoteType> <remoteNode> <remoteChan> <conSubType> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -> <remote_parameter_set | -> <connection type>

When configuring the parameters, the user should observe the following rules.

• localType or remoteType can be one of atm, ce, fr, voice, data, or rpm

Note XPVCs localType or remoteType cannot be set to “ce” (circuit emulation)

• connSubType can be one of cbr1, vbr1, vbr2, vbr3, abr-fs, fr-fs, fr, ubr1, ubr2, abr1, atfst, atfxfst, atftfst, voice, or data

• local_parameter_set or remote_parameter_set are names of the parameter files. Use "-" to take default values.

• connection type can be pvc, spvc, hybrid or xpvc. Use "-" to take default values.

• For ATM/VISM/RPM connection types, localChan or remoteChan should be given as "slot.port.vpi.vci" (for rpm connections port is the sub-interface number on switch + 1) (for rpm VC connections vpi is always 0).

• For FR connection type, localChan or remoteChan should be given as slot.line.port.dlci (for fr connections port is the l_port field in frp table for example., start ds0 number on switch)”

• For CE connection type, localChan or remoteChan should be given as slot.line.port (for CE connections port is the physical port number. It is the same as the l_port in frp table and is the starting DS0 time slot number. It is not the logical_port, which is the port number given in CLI)

Features

The script allows bulk provisioning by incrementing the VCI or the DLCI based on the value given for the input parameter “totalNumberOfConnections.” The script also allows simultaneous provisioning based on the value given for the input parameter “numberOfSimultaneousRequests”.

Example Parameter Files

Filename: /tmp/parmfile (atm connection) atmEndPointSCRZeroPlus1 87 atmEndPointPCRZeroPlus1 297 svConnCellRouting 1 svConnOvrSubOvrRide 1Filename: /tmp/parmfile (rpm connection on MGX8850 R1) rpmEndPointNodeUser cisco rpmEndPointNodePasswd cisco rpmEndPointRpmPasswd lab rpmEndPointPeak 50Filename: /tmp/parmfile (fr connection) frEndPointPercUtil 77 frEndPointCIR 67 svConnCellRouting 2




svConnOvrSubOvrRide 2

Example AddConn Commands:

AddConn host1 atm igx1 5.2.1.1 atm bpx1 2.2.1.1 vbr2 2000 8 - - -AddConn host1 fr pop1 2.0.1.1 atm pop2 3.1.10.10 abr-fs 1023 5 - - hybrid

Logs

AddConn.time.log in the $TMP_DIR contains the time log of all the connection additions using AddConn. $TMP_DIR/AddConn.<localChan>_<remoteChan>.out will be created for all the failure cases (For example, /tmp/AddConn.2.2.1.11_2.2.2.11.out).

Sample Output

In the following example, 3 connections are added with 2 simultaneous requests. The third connection addition fails, since the end-point is already in use.

AddConn cwmult60 atm nmsbpx16 2.2.1.9 atm nmsbpx16 2.2.2.9 vbr2 3 2 - - pvc

nmsbpx16 [2.2.1.9] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.9] nmsbpx16

+ /opt/OV/bin/snmpset -d -t 3000 -p 8161 -c private -r 0 cwmult60 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.1.9 integer 4 atmEndPointRowStatus.8.110.109.115.98.112.120.49.54.0.2.2.2.9 integer 4 svConnLocalEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.1.9 svConnRemoteEndPt.0 objectidentifier atmEndPointNodeName.8.110.109.115.98.112.120.49.54.0.2.2.2.9 svConnSubType.0 integer 3 svConnRowStatus.0 integer 4 svConnOvrSubOvrRide.0 integer 2 svConnProtocolType.0 integer 1+ 1>> /tmp/AddConn.2.2.1.9_2.2.2.9.out 2>& 1

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



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

nmsbpx16 [2.2.1.9] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.9] nmsbpx16Connection index of the connection given above: 2681

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

nmsbpx16 [2.2.1.10] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.10] nmsbpx16Connection index of the connection given above: 2682

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

Time elapsed to add 2 connection[s] in this loop : 4Total connections added till now : 2Total number of errors seen till now : 0Total time taken till now : 4




Average time to add a connection till now : 2.00

================================================================================



- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Connection : nmsbpx16 [2.2.1.11] [atm] <--- [vbr2] - [pvc] ---> [atm] [2.2.2.11] nmsbpx16

Log file : /tmp/AddConn.2.2.1.11_2.2.2.11.outRequest id : 12469

stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorReqId.12469 : INTEGER: 12469stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorDesc.12469 : DISPLAY STRING- (ascii): [08/14/2001 14:52:23] EndPoint already in use: 0.2.2.1.11stratacom.svplus.serviceGroup.connGroup.svCmpaErrorTable.svCmpaErrorEntry.svCmpaErrorEcode.12469 : INTEGER: endpt-exists- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Time elapsed to add 1 connection[s] in this loop : 0Total connections added till now : 2Total number of errors seen till now : 1Total time taken till now : 4Average time to add a connection till now : 1.33

================================================================================

********************************************************************************TOTAL NUMBER OF CONNECTIONS ADDED : 2TOTAL NUMBER OF CONNECTION ADDITIONS FAILED : 1TOTAL TIME TAKEN TO ADD ALL THE CONNECTIONS : 4APPROXIMATE AVERAGE TIME TAKEN TO ADD A CONNECTION : 1.33********************************************************************************

Deleting an XPVC Connection: DelConn script

Use the delComm command to delete an XPVC connection.

DelConn <proxyHost> <Type> <Node> <Chan> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -> <remote_parameter_set | -> <connection type>

When configuring the parameters, the user should observe the following rules.

• Type can be one of atm, ce, fr, voice, data, or rpm

• local_parameter_set or remote_parameter_set are names of the parameter files. Use "-" to take default values.




• connection type can be pvc, spvc, hybrid, or xpvc. Use "-" to take default values.

• For ATM/VISM/RPM connection types, Chan should be given asslot.port.vpi.vci (for RPM connections port is the sub-interface number on switch + 1) (for RPM VC connections the VPI is always 0).

• For FR connection type, Chan should be given as slot.line.port.dlci (for FR connections the port is the l_port field in the frp table for example, the starting ds0 DS0 time slot number on the switch)

• For CE connection type, Chan should be given as "slot.line.port" for CE connections port is the physical port number. It is the same as the l_port in frp table and is the starting DS0 time slot number. It is not the logical_port, which is the port number given in CLI). Note that the CE connection type is not supported for XPVCs.

Example

DelConn cwmult65 atm igx1 5.2.1.1 100 5 - -

Fault Segment Isolation: FaultIsolation script

FaultIsolation <cwmHost> <connIndex> <xpvcSegmentNumber>

where

The connIndex parameter is the xpvc_id in the XPVC table if the connection is an XPVC or the snmp_index in the user_connection table if the connection is either a PVC, an SPVC, or a hybrid connection.

Note The connIndex can be retrieved using the GetConnIndex script.

The xpvcSegmentNumber can be 1, 2, or 3. The numbering starts from the local end of the connection. This number should not exceed the number of segments in the specified connection, of course. You should not try to test for faults on segment 3 of a two segment connection.

Note This script can be used only on XPVCs to run test delay on each XPVC segment

Example

FaultIsolation cwmult65 1000000015 1

Check for faults on the first segment of the connection with the index of 1000000015

Get Any Connection: GetAnyConn script

GetAnyConn <Host> <connIndex> <local_parameter_set | -> <remote_parameter_set | ->

• local_parameter_set or remote_parameter_set are the names of the parameter files. Use “-” to take default values.




Example:

GetAnyConn cwmult65 1000000015 - -

Get Connection Errors: GetConErr script

GetConErr <Host> <“Request ids”>

• endptType can be one of the following types atm, ce, fr, voice, data, rpm

Note The CE connection type is not supported for XPVCs.

Get Connection Details: GetConnDetails script

GetConnDetails <Host> <Options> <ConnIndex>

• Options can be one of the following:

-l : Get local endPt.

-r : Get remote endPt.

-c : Get connection parameters

-a : Get all

Get Connection Index: GetConnIndex script

GetConnIndex <Host> <endptType> <Node[.Shelf]> <ChanInfo>

• endptType can be one of the following types atm, ce, fr, voice, data, rpm

Note The CE connection type is not supported for XPVCs.

Modifying an XPVC Connection: ModConn script

ModConn <proxyHost> <localType> <localNode> <localChan> <totalNumberOfConnections> <numberOfSimultaneousRequests> <local_parameter_set | -><remote_parameter_set | ->

• localType can be one of the following types atm, ce, fr, voice, data, rpm

• The CE connection type is not supported for XPVCs.

• local_parameter_set or remote_parameter_set are the names of the parameter files. Use “-” if you do not want to specify any parameters

Example

ModConn cwmult65 atm igx1 5.2.1.1 100 10 - -"

Give the local endpoint type, node and channel information, not the remote endpoint information




End to End Test Connection or Test Delay: TestConnDelay script

Use the TestConnDelay to execute and end-to-end connection.

TestConnDelay <ProxyHost> <ConnIndex> <1 for TestConn, 2 for TestDelay>

Example

TestConnDelay cwmult65 1000000015 1

Execute an end to end Test Connection on the connection with the index of 1000000015

Trap support for XPVCs

The following existing traps support XPVCs

• cwmUserConnComplete, #25113

• Sent to user when an incomplete XPVC connection becomes complete.

• cwmUserConnIncomplete, #25114

• Sent to user when a complete connection goes into incomplete state.

• cwmUserConnectionCleared, #25116

• Sent to user when there is a change in the alarm status of a XPVC connection and the end to end XPVC connection status is OK.

• cwmUserConnectionFailed, #25117

Sent to user when there is a change in the alarm status of a XPVC connection and the end to end XPVC connection status is failed.

• cwmUserConnectionDown, #25118

Sent to user when the entire XPVC connection or at least one segment of the XPVC connection is downed.

The following new traps support XPVC management:

• cwmTrapConnAdded, #25210

End-To-End Connection described by the above endpoints is added. This trap is generated when a new End-To-End connection is added from any Connection Manager interface (GUI or Service Agent). A connection alarm status trap is also generated along with this. Currently this TRAP is generated for XPVC connections only.

• cwmTrapConnDeleted, #25211

End-To-End Connection described by the above endpoints is deleted. This trap is generated when a connection is deleted from any Connection Manager interface (GUI or Service Agent). Currently this TRAP is generated for XPVC connections only.

• cwmTrapConnDescModified, #25212

Connection Descriptor for the End-To-End connection is modified. Currently this TRAP is generated for XPVC connections only.



Chapter 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN ManagerDisplaying XPVC Status

Displaying XPVC StatusTo view XPVC status within the Connection Manager, edit the filter settings to set the end to end Type to XPVC, and select Apply. You will then see a display similar to that shown in Figure 11-5 and/or Figure 11-6 below.

Figure 11-5 XPVC Display at Opening

Figure 11-6 XPVC Display Expanded

With Release 11 you can also view additional information relating to the individual XPVC segments. After highlighting to select an XPVC in the Main Window, activate the Segment View GUI by selecting View > XPVC Segments on the menu bar.

The information displayed includes the following:

1. The XLMI links for the XPVC. Primary links only are displayed in this screen. The secondary links are not currently supported.

2. The status of the end-to-end XPVC in the first line of the Connection and Segments pane.

3. The status and endpoint type of each of the two or three XPVC segments that constitute the end-to-end connection.




For an AR-PNNI-AR XPVC, there are two new End to End Types you can filter on:

1. XPVC

See Figure 11-7, below, for an illustration of the XPVC filter tab.

Figure 11-7 Filter Settings, XPVC

2. XPVC-D. This is a dangling XPVC.

See Figure 11-8, below, for an illustration of the Dangling Segments of XPVC filter tab.

Figure 11-8 Filter Settings, Dangling Segments of XPVC

Dangling Segments of XPVCs are Complete or Incomplete PVC, SPVC or Hybrid connections that terminate on one or two ENNI ports. Since Cisco WAN Manager can not automatically join discovered XPVC segments, these segments remain dangling. Dangling segments, like incomplete connections or incomplete XPVCs, can only be deleted. They cannot be modified.

Operations you can perform on XPVCs are similar to those available for SPVCs and PVCs:

1. Sorting

2. End to End XPVC Test Delay (this test is equivalent to the standard Test delay, but it crosses the two types of networks.)




Displaying Information on a Specified XPVC SegmentWith Release 11 of Cisco WAN Manager you can also view additional information relating to the individual XPVC segments. After selecting an XPVC in the Main Window activate the Segment View GUI by selecting View > XPVC Segments on the menu bar. See Figure 11-9, for an example of the pulldown menu.

Figure 11-9 Choose XPVC Segment Pull-down

You can also right-click on the chosen connection, and a popup menu appears, as shown in Figure 11-10.




Figure 11-10 Choose XPVC Segment Popup

The information displayed includes the following items

• The XLMI links for the XPVC. Provision is made for display of the secondary links that will be supported in a future Release.

• The status of the end-to-end XPVC in the first line of the Connection and Segments pane.

• The status and endpoint type of each of the two or three XPVC segments that constitute the end-to-end connection. The example in Figure 11-11 below lists the three segments for an AR-PNNI-AR XPVC.

Figure 11-11 Preferred Connection Primary Link Display




XPVC End-to-end Test DelayRelease 11 of Cisco WAN Manager supports an end-to-end Test Delay diagnostic for the XPVCs. The testing of individual segments is not supported in Release 11, but is supported by the BPX Switch Software CLI from Release 9.3.30 and on the AXSM card running Release 2.1.60 or later. Refer to the respective Command Reference manuals on your documentation CD for details on usage of the cnfoamseg BPX command and the cnfcon AXSM command.

Figure 11-12, shows a sample Test Delay Pop-up Menu.

Figure 11-12 Test Delay Pop-up Menu

Figure 11-13, shows a sample Test Delay in Progress Pop-up Menu.




Figure 11-13 .Test Delay in Progress Popup

Figure 11-14, shows a sample Test Delay Success Pop-up Menu.

Figure 11-14 Test Delay Success Popup

Connection Templates

For any connection you create, you have the option to store the modified parameter set in a new template. While the new connection is still displayed (before pressing OK), press Save Template to bring up the Save to Template dialog box. Enter a name and description for the new template, and then press OK. The system assigns a sequential template number and confirms the template creation. Press Close to close




the confirmation dialog box. You can later apply the template to other new connections by selecting Load Template on the New Connection screen. For further information on the Connection Template application, refer to Cisco WAN Manager User’s Guide, Release 11, Chapter 7.

Figure 11-15, shows a sample connection displayed in the Connection Manager window. The right pane of this display lists the parameters that can be saved in a Connection Template.

Figure 11-15 Connection Manager




A-1Cisco WAN Manager Installation Guide for Solaris 7


A P P E N D I X AStatistics Collection Manager Configuration

The Statistics Collection Manager (SCM) software is comprised of three major modules, namely an SCM Control Server, an SCM Collection Server, and an SCM Parser Server. All three modules can be installed and run in the same workstation as the CWM server, however the SCM Collection Server and the SCM Parser Server can also be installed as stand alone packages and distributed across several hardware workstations. The effect if this distribution is to spread the processing capability and storage capacity across several hardware systems thereby increasing the number of network nodes and statistics that can be supported by SCM.

Further an additional software module called scmProxy is used as an alternative user interface to aid in the configuration of the SCM servers

This appendix describes

• Each of these servers and the scmProxy module.

• The variety of ways in which these modules can be installed to suit different network needs.

Description of ModulesThis section provides a description of each of the SCM modules.

Figure A-1 shows a conceptual representation of how the three SCM modules are related.

Figure A-1 SCM Modules

SCM Control Server

SCM Collection Server SCM Parser Server

Stats DataBase

7068

2

CWM DataBase

SCM GUI scmProxy

IncomingStatistics

User

optionalmethods

status

enabledisable

stats



Appendix A Statistics Collection Manager ConfigurationSCM Installation Options

SCM Control ServerThe SCM Control Server manages the whole statistics collection operation and controls both the SCM Collection Server(s) and the SCM Parser Server(s). For example, it enables and disables the collection process and instructs the other two modules as to which modes and methods to use.

In turn, the SCM Control Server responded to user requests issued through the SCM GUI interface or through the contents of the scmProxy file.

The SCM Control Server is always installed with CWM in the CWM host server.

SCM Collection ServerUnder the control of the SCM Control Server, the SCM Collection Server uses FTP (or TFTP) to collect statistics from the network nodes and place them in directories for parsing by the SCM Parser Servers.

The SCM Collection Server is installed in the CWM host workstation as part of the CWM installation process. It can also be installed as a module in one or more standalone workstations.

SCM Parser ServerWhen started, the SCM Parser Server continuously parses statistics from the SCM Collection Server and places them in a statistics database. The parsing method is specified by the SCM Control Server.

The SCM Parser Server is installed in the CWM host workstation as part of the CWM installation process.

It can also be installed as a module in one or more standalone workstations. In the standalone situation, the Parser Server stores the statistics in its stats database.

The Wingz and Summary reporting features in CWM cannot be used to report statistics in the stats database (in a standalone parser server). Extracting records from stats database in a standalone parser is performed by using the Informix dbaccess command.

SCM Installation OptionsThe CWM and SCM standalone installation processes permit the user to distribute the SCM modules across multiple hardware platforms in a variety of ways.

The SCM Control Server is always installed in the CWM host workstation. In fact, all three CWM modules are installed in the CWM host automatically as part of the CWM installation procedure.

The simplest SCM installation, therefore, is to have CWM and all SCM modules in a single workstation. However, to improve the performance of SCM, the SCM Collection Server and SCM Parser Server can also be installed in standalone workstations. To do this, the user must install the optional Statistics Collection Manager Standalone (SCMSA) on each SCM standalone workstation. During the installation of SCMSA, the user specifies which servers are to be installed on each workstation.

The user can choose to install both the SCM Collection Server and the SCM Parser Server, install only the SCM Collection Server, or install only the SCM Parser Server.

The possible configurations of a workstation performing all or part of the SCM process are as follows.

• CWM host workstation with the SCM Control, SCM Collection, and SCM Parser servers.



Appendix A Statistics Collection Manager ConfigurationSCM Installation Options

• CWM host workstation with the SCM Control and SCM Collection servers only.

• CWM host workstation with the SCM Control and SCM Parser servers only.

• Standalone workstation with SCM Connection and SCM Parser servers.

• Standalone workstation with SCM Connection server only.

• Standalone workstation with SCM Parser server only.

Figure A-2, Figure A-3, and Figure A-4 show three SCM configuration examples.

Figure A-2 Single Workstation Configuration

Figure A-2 shows a single workstation configuration in which CWM and all three SCM modules are installed in the same hardware. In this case, only CWM needs to be installed because SCM is installed automatically as part of the CWM installation.

Figure A-3 Parser Servers Configured as Standalone

SCM ControlServer

SCM Collection Server

SCM Parser Server

CWM Host Workstation

CWMDataBase

StratacomDataBase

CWM

7068

3

SCM ControlServer



CWMDataBase

CWM

StatsDataBaseStats

DataBaseSCM Parser

ServerStats

DataBase

Standalone Workstation



7068

4



Appendix A Statistics Collection Manager ConfigurationScmProxy

Figure A-3 shows a configuration in which a number of SCM Parser Servers have been installed on standalone workstations. The effect of this configuration is to distribute the statistics database across several hardware platforms. The capacity for collecting statistics is not affected because the number of Collection Servers remains at one.

Figure A-4 Standalone Collection and Parser Servers

Figure A-4 shows a configuration in which there are three Collection Servers and three Parser Servers. Two of the Collection Servers are installed in their own standalone workstations whereas one Collection Server is installed in a standalone workstation along with its Parser Server.

In this type of configuration one of the Collection Servers could remain in the CWM host.

This configuration not only distributes the statistics database across several hardware platforms but it also increases the capacity to collect statistics by sharing the task between the three Collection Servers.

ScmProxyScmProxy is a software module that resides in the CWM host and provides an alternative user interface to the GUI. It also uses a nodelist file to discover the SCM server topology. The file describes the SCM server configurations (which Collection Servers are connected to which Parser Servers) and lists the network nodes that each Collection Server supports.



SCM Parser Server

StatsDataBase


SCM Parser Server

StatsDataBase


SCM Parser Server

StatsDataBase

Standalone WorkstationStandaloneWorkstation

StandaloneWorkstation


7068

4


CWMDataBase

CWM SCM ControlServer



Appendix A Statistics Collection Manager ConfigurationSetting Up the SCM Configurations

To launch scmproxy, the user is first required to create a nodelist file with the following format.

<Collparm:<template_name><collectionhostname><parserhostname><routinginfo>node_name1node_name2....<Collparm:<template_name><collectionhostname><parserhostname><routinginfo>node_name1node_name2....

The file consists of a number of records where each record specifies the stats template to be used, a collection server/parser server pair, and a list of nodes in the network for which the servers are collecting statistics.

template_name: This is the name of the applicable template. Stats templates can be created from the SCM GUI and saved in StrataCom database.

collectionhostname: This is the name of the collection server host. The collection server can be on a CWM host or in a standalone SCM machine.

parserhostname: This is the name of the parser server host. Stats parser can be on a CWM host or in a standalone SCM machine.

routinginfo: This field can be “in-band” or “outband.” The field depends on the routing method to the nodes.

node_name1, node_name2, etc. are node names in the network that the servers are collecting statisitics.

ScmProxy must be started from the CWM host machine by typing:

scmproxy<nodelist_filename> where “nodelist_filename” is the name the user has given to node list file.

ScmProxy then displays a menu from which the user can select from the following options.

Enable StatisticsDisable StatisticsStart CollectionStop CollectionExit the program

A error message is displayed if the node list file contains incorrect data (for example, a template that does not exist). Otherwise, the selected option is invoked.

Setting Up the SCM ConfigurationsSetting up SCM configurations with standalone servers consists of the following steps.

Step 1 Plan the number of workstations to be used for statistics collection. Determine the number for statistics collection and the number for parsing.

Step 2 List the network nodes to be associated with each SCM collection server.

Step 3 For each workstation install SCM.

For the CWM host machine this is performed automatically as part of the CWM installation. For each standalone machine choose the appropriate server options according to the plan developed in step 1.

Step 4 In the CWM host machine, create a nodelist file listing the SCM server relationships.

This file should indicate which servers support which network nodes.



Appendix A Statistics Collection Manager ConfigurationSetting Up the SCM Configurations

Step 5 For each parser server installed in a CWM host machine, specify which database is to be used for statistics storage. The options are the Stratacom database (DB) or the stats database (DB).

The option is set in the /usr/users/svplus/config/parseconfig.stats file.

The parserconfig.stats file is a list of parameters as follows:

-f config file name

-v verbose mode (0 = low, 1 = high)

-t FlushCount(not used)

-p Enable Perf (0 or 1)

-d database (1 = statsDB, 0 = StratacomDB)

-s StandAlone (1 = standalone, 0 = not standalone)

Enter vi to set the -d = 1 for the statsDB or -d = 0 (default value) for the StratacomDB.

Note For parser servers in standalone machines there are no database options. Statistics are always stored locally in the stats database. The -d parameter in the parserconfig.stats file is set to the default of 1 and must not be changed.

Further, the Wingz and Summary reporting features in CWM cannot be used to report statistics in the stats database (in a standalone parser server). Extracting records from stats database in a standalone parser is performed by using the Informix dbaccess command on the local machine.

Step 6 Start CWM.

Step 7 Start scmproxy specifying the nodelist file created in Step 3.

Step 8 At the scmproxy menu, select Enable Statistics.

Step 9 At the scmproxy menu, select Start Collection.

SCM RedundancyIn addition to being able to distribute the collection and parsing functions across several hardware platforms in order to improve performance, the user can also configure redundant servers that can take over in the event of a failure.

The user should install SCMSA on the intended redundant systems. When SCMSA is started in the primary hardware, the secondary and tertiary servers can be specified in the Start Collection Dialog box.

Refer to the Cisco WAN Manager User’s Guide Release 11 for more details.

B-1Cisco WAN Manager Installation Guide for Solaris 7


A P P E N D I X BIP Reachability

This appendix addresses the issue of how CWM accesses the nodes in the network that it is managing. In particular this appendix describes how to the configure the communication method using the IP reachability field in the svplus/config/network.conf file.

OverviewCWM needs to communicate with the network nodes that are being managed to perform the following applications.

• Network topology discovery (AutoRoute and PNNI)

• Network object management (SNMP)

• Statistics collections (TFTP and FTP)

• CLI (Telnet)

For all these applications, CWM uses IP addresses to identify the destination node that is to receive a packet or message. However, depending upon the application and network equipment types, several IP addressing schemes are configurable by the user. These schemes are listed below.

• AutoRoute networks

– In-band IP routing in the network nodes (referred to as NWIP ON)

– In-band using PVCs generated by the gateway node (referred to as NWIP OFF)

– Out-of-band using LANs (referred to as LANIP)

• PNNI networks

– ILMI management PVCs

– Out-of-band using LANs

For AutoRoute networks the scheme is selected by the value of the IP reachability field in the network.conf.

For PNNI networks, the default scheme uses the ILMI management PVCs provided by the ATM protocol. Alternatively, LANs can be used by configuring at the node level entering the CLI cnfndparms command.



Appendix B IP Reachability

General GuidelinesThe following guidelines should be observed when configuring IP reachability

• Each network must have at least one node designated as the gateway node.

• A gateway must be connected to the CWM workstation through its Ethernet port.

• The LAN IP address of a gateway must be specified in the network.conf file either as its IP address or its nodename (as specified in the etc/hosts file).

AutoRoute NetworksIn AutoRoute networks IP reachabilty can be either in-band or out-of-band.

In-band—NWIP ON

Figure B-1 shows an example of an AutoRoute network in which the communication method between CWM and the network nodes is in-band.

In this example there are four network nodes of which one is designated a gateway node. CWM communicates with the network through a LAN connection to the gateway node (via a router in this case). For CWM applications CWM uses the node’s NWIP address for specifying the destination node of a message. The network nodes use a Cisco proprietary IP relay protocol whereby a node can examine the destination IP address, look it up in a routing table, and relay the message to the next hop. Although the network uses ATM to transmit cells across the network links, the network, in effect, performs as an IP level 3 routing network for CWM messages.

To use this method, the user enters NWIP ON as the value in the IP reachability field of the svplus/config/network.conf file.

Figure B-1 Example of AutoRoute In-band Communications

CWM Workstation

Router

LAN

LAN ATM Cloud

NWIP= x.x.x.1

NWIP= x.x.x.2

NWIP= x.x.x.3

NWIP= x.x.x.4

Gateway

8013

7




In-band—NWIP OFF

Figure B-2 shows an example of an AutoRoute network in which communication between CWM and the network nodes is in-band and uses PVCs set up by the gateway node.

In this example there are four-network nodes of which one is designated a gateway node. CWM communicates with the network through a LAN connection to the gateway node (via a router in this case). Unlike the NWIP-ON case, only the gateway node performs the routing function. The gateway node uses its AutoRoute topology knowledge to set up a dedicated PVC to each network node for the purpose of transmitting CWM messages. For CWM applications CWM uses the node’s NWIP address for specifying the destination node of a message. When such a message is received by the gateway node, it looks up the PVC for the specified IP destination and uses the PVC to relay the message across the network to its destination.

To use this method, the user enters NWIP OFF as the value in the IP reachability field of the svplus/config/network.conf file.

Figure B-2 Example of AutoRoute Out-of-band Communications using PVCs

Out-of-band—LANIP

Figure B-3 shows an example of an AutoRoute network in which communication between CWM and the network nodes is out-of-band and uses PVCs set up by the gateway node.

In this example there are four network nodes where each is connected to CWM through a separate IP LAN (or LAN emulation network). In this case, no CWM messages are carried across the managed network. CWM communicates over the LAN using the node’s LAN IP address as the destination address.

To use this method, the user enters LANIP as the value in the IP reachability field of the svplus/config/network.conf file.

Mgt PVCs

Physical lines

CWM Workstation

Router

LAN

LAN ATM Cloud

Gateway

8013

8




Figure B-3 Example of AutoRoute Out-of-band Communications using LANs

PNNI NetworksFor communication between CWM and PNNI nodes, CWM does not use the IP reachability field in the network.conf file. If present, both the IP_REACHABITY field and the OPTIONS field are ignored.

Instead, the method of CWM communication with a PNNI node depends upon the managed node’s primary IP interface.

Option 8 in the configure node parameters (cnfndparms) command allows the user to set the node’s primary IP address as follows.

• 0: The atm0 interface is the primary.

• 1: No interface is used (This choice prevents the node’s discovery by CWM).

• 2: The lnPci0 interface is the primary

CWM learns the primary IP interface by doing a MIB-walk and reading the PNNI topology state element table. By this means, CWM uses either the atm0 address or lnPci0 address to communicate with the node.

atm0 Method

This is the default method and uses ATM’s ILMI (vpi = 0, vci = 16) facility and the neighbor routing protocol provided by PNNI. This method uses the node’s IP address which is configured at the node using option 8 in the cnfndparms command and entering 0 (atm0).

lnPcio Method

Alternatively, CWM can use the out-of-band method using a separate LAN (or LAN emulation network) similar to that shown in Figure B-3. To enable this method, the user must configure each node using the option 8 in the cnfndparms command and entering 2 (lnPci0).

LANIP

LAN LAN

LAN

CWM Workstation

Router

LAN

LAN

ATM Cloud

8013

9

LANIP

LANIPLANIP

IN-1Cisco WAN Manager Installation Guide for Solaris 7


I N D E X

XPVC

Symbols

.cshrc file 3-17, 4-20, 10-6

A

AddConn command example 11-20

AddConn script 11-19

example parameter files 11-19

Adding an XPVC

syntax 11-13

ATM 10-14

ATM interface

configuration example for management access 10-16

router configuraiton for management access 10-16

router configuration example 10-17

AutoRoute

verifying connection alarms 11-2

verifying node alarms 11-2

verifying port alarms 11-2

verifying trunk and line alarms 11-2

C

caution

definition xxi

symbol xxi

CiscoView

installation 3-9, 4-10, 5-2

uninstall 5-3

Configuration Save & Restore 11-1

ConnProxy Scripts

location 11-18

CWM Client

hardware requirements 2-5

software requirements 2-5

CWM server

hardware requirements 2-3

installation 3-1

login 3-14, 4-17

post installation tasks 3-14, 4-17

software requirements 2-3

upgrading from 10.4 with multiple CWM gateways 4-14, 9-10

workstation reboot 3-22, 4-25, 10-11

workstation requirements 2-2

CWM server requirements

software 2-3

CWM to HP OpenView communication 2-15

CWM-XPVC-CLI

defined 11-11

overview 11-13

D

dangling segment

defined 11-17

defaultrouter file 3-17, 4-20, 10-6

disk partitioning 2-9

dspipif atm0 command 10-15

dspipif lnPci0 command 10-12

dsppnsysaddr command 10-16

dspsvcif command 10-15

Index



E

End-to-end test delay

types 11-26

XPVC 11-26, 11-29

Enhanced Network-to-Network Interface See ENNI

ENNI

configuration via Service Agent 11-18

EUNI port configuration 11-6

interface compared with NNI interface 11-11

overview 11-6

verifying port status 11-8

Extended Local Management Interface See XLMI

Extended Permanent Virtual Circuit See XPVC

Extended Permanent Virtual Path See XPVP

F

files

/etc/defaultrouter 3-17, 4-20, 10-6

/etc/hosts 3-15, 4-18, 10-4

/etc/netmasks 3-16, 4-19, 10-6

/etc/rc2.d/S72inetsvc 3-16, 4-19, 10-6

/etc/system 3-21, 4-24, 10-11

/system 3-21, 4-24, 10-11

CWMGateway.conf 3-21, 4-24, 10-10

CWMgateway.conf file 3-21, 4-24, 10-10

defaultrouter 3-17, 4-20, 10-6

netmasks 3-16, 4-19, 10-6

Network.conf Examples 4-23, 10-10

network.conf file 3-17, 10-7

S72inetsvc 3-16, 4-19, 10-6

svplus/config/network.conf file 4-20

usr/users/svplus/.cshrc 3-17, 4-20, 10-6

H

hosts file 3-15, 4-18, 10-4

HP OpenView

installation 2-15

obtaining 2-15

starting 2-16

I

In-band B-2

in-band B-3

installation

CiscoView 3-9, 4-10, 5-2

CWM Servier 3-1

HP OpenView 2-15

Java plug-in 5-1

Java Web Start 7-12

SCMSA 8-2, 9-2

SNMP agent 6-1

Wingz 2-16

Installing 7-1

Installing CWM Client 7-1

ipifconfig atm0 command 10-15

ipifconfig lnPci0 command 10-13

IP Reachability

AutoRoute Networks B-2

general B-1

General Guidelines B-2

Overview B-1

PNNI Networks B-4

J

Java plug-in

general 5-1

Java Plug-in uninstall 5-2

Java Tools

requirements 7-4

Java tools

installing 7-4, 7-9

Index



L

LANIP B-3

log-in to Solaris 2-12

M

MGX 11-5

MGX 8850 Upgrade 11-5

Migration 11-10

AutoRoute to PNNI 11-4

connection example 11-10

modifying an XPVC connection

via Service Agent 11-18

Modifying the SNMP Community String 10-11

N

netmasks file 3-16, 4-19, 10-6

NNI interface

compared with ENNI interface 11-11

note

definition xxi

symbol xxi

NWIP OFF B-3

NWIP ON B-2

O

OAM cell flow 11-11

out-of-band B-3

P

PC Client

launching 7-13

overview 7-1

Requirements 7-2


preferred connection

Primary Link (figure) 11-28

Preferred Table Configurator 11-9

R

reate 11-9

S

S72inetsvc file 3-16, 4-19, 10-6

SCM

Collection Server A-2

configuration A-1

Control Server A-2

installation options A-2

module descriptions A-1

Parser Server A-2

redundancy A-6

workstation requirements 2-4

ScmProxy A-4

SCMSA

first time login 8-10

installation 8-2

Sun platform upgrades 9-1

system requirements 8-1

upgrade procedures 9-2

Service Agent

ENNI Configuration 11-18

XLMI configuration 11-18

XPVC connection, adding 11-18

XPVC connection, modifying 11-18

XPVC provisioning 11-18

SNMP

Agent.conf 6-7

Agent configuration file 6-7

Service Agent configuration file 6-7

Index



snmpd.cnf file 6-7

Software 2-3, 7-2

Solaris

initial configuration 2-7

installation 2-6

installing on the newly-partitioned disk 2-11

login first time 2-12

Stand Alone Statistics Collection Manager

See also SCMSA

Statistics Collection Manager Stand Alone

See SCMSA

supported connections for XPVCs 11-11

svcifconfig command 10-15

switch software upgrade 11-4

system file 3-21, 4-24, 10-11

T

test delay

in Progress screen (figure) 11-30

Success screen (figure) 11-30

Trap support for XPVC 11-24

trunk and line alarms verifying 11-2

U

uninstall 5-3

UNI to NNI port configuration 11-6

upgrading

CWM server from 10.4 with multiple gateways 4-14, 9-10

utomatic 11-2

V

Verifying 11-9

verifying data continuity 11-2

verifying port alarms 11-2

W

Web Start 7-2

Wingz installation 2-16

X

XLMI

definition 11-11

displaying trunks 11-7

overview 11-6

XLMI Configuration

via Service Agent 11-18

XLMI Trunks Display 11-8

XPVC

adding 11-13

adding a connection using Service Agent 11-18

adding a connection with AddConn 11-19

adding via CLI 11-13

as a Migration Connection 11-10

Connection Manager support 11-17

Connection Templates 11-30

connection templates 11-30

creating 11-9, 11-12

dangling 11-17

definition 11-10

deleting 11-16

deleting a connection 11-18

deleting via CLI 11-16

end-to-end Test Delay 11-29

end-to-end test delay 11-26

existing traps 11-24

management 11-11

overview 11-6

Preferred Flag 11-9

provisioning 11-11

segment to display (figure) 11-28

supported connections 11-11

trap support 11-24

Index



verifying 11-9

XPVC connection

adding via AddConn script 11-19

deleting via Service Agent 11-18

XPVC creation

overview 11-6

XPVC display

expanded 11-25

opening 11-25

XPVC Preferred Table Configurator 11-9, 11-12

XPVC Provisioning via Service Agent 11-18

XPVC segment

defined 11-10

viewing additional information 11-25

XPVC status

via Connection Manager 11-25

XPVC types

AR-PNNI 11-10

AR-PNNI-AR 11-10

XPVC user endpoints

limitations 11-12

XPVP

overview 11-6

Provisioning and Management 11-11

Index

