321 Studios OL-2706-01 User Manual

Overview

CHAPTER

2

Provisioning

The Provisioning Management chapter of the Cisco Internet OSS for VoIP: Infrastructure Manager
(Cisco VoIP: Infrastructure Manager) Solution is the second chapter in a four chapter Cisco VoIP:
Infrastructure Manager Solution document. Provisioning management, in the context of this Solution,
deals with the provisioning of network elements and the management of those configuration files. This
guide details the network architecture, provisioning management applications, configuration file
management applications, and the deployment strategies surrounding Cisco's Configuration
Management Solution.

Cisco employs adistributed model for its service provider, Voice overIP (VoIP) product suite. Although,
at a certain level, each deployed device requires a unique instance of an Element Management System
(EMS) to provide upstream information pertaining to fault, performance, and provisioning, it is
incumbent upon the Network Management System (NMS) to appear as a virtual entity that hides the
individual element complexity.

A complete NMS Solution adheres to the Fault, Configuration, Accounting, Performance and Security
(FCAPS) model. The solution covered in this document finds its place in the Configuration portion of
the FCAPS model. It is a component chapter in the Cisco VoIP: Infrastructure Manager Solution and
deals specifically with configuration and provisioning management. It is intended to be referenced in
conjunction with the companion chapters dealing with performance and fault management.

Description

OL-2706-01

This chapter is a collection of published material, all available on Cisco Connection Online (CCO). All
the specifics of importance in this document can be found in one or more of the documents listed in the

“Related Documents” section. Each URL listed in the “Related Documents” section points to

documentation for a particularapplication orpair ofapplications and is complete in its own right for that
application. This guide pulls together the information available for all of the provisioning applications
of importance to the Cisco VoIP: Infrastructure Manager Solution.

For all of the applications or functionality detailed in this guide, there is a comprehensive set of
documents available on CCO. The “Related Documents” section is a to guide to finding them.

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-1

Overview

Target Market

The applications and devices described in this document are positioned for service providerscale, VoIP
networks. Although many ofthe applications can be deployedin enterprises andsmaller scale networks,
the solution suite referred to in this Solution guide is aimed at the large carriers and providers of VoIP
network bandwidth and services. It also concentrates on the devices deployed in a VoIP network,
although non-VoIP devices integral to the VoIP network must also be taken into account.

Scope of the Solution

The provisioning component of the Cisco VoIP: Infrastructure Manager Solution provides the
applications and network level visibility required to manage the distributed telephony architectures
detailed in the next sections.

The Cisco Packet Telephony Center application operates at the Network Management Layer (NML) of
the Telecommunications Management Network (TMN) hierarchy. Its most important function is the
realization of a virtual entity view, hiding much of the internal complexity of the OPT network detailed
in the“Solution Architecture”section. The Cisco Voice RoutingCenter (CiscoVRC) application is used
to help service providers manage dial plans for H.323 based VoIP networks. Cisco VRC can be applied
to existing networks with working dial plans and can also be used to design new dial plans for the set of
gateways, gatekeepers, and directory gatekeepers.

The Cisco CNS Intelligence Engine 2100 Series (Cisco CNS IE2100 Series) is a network management
device that acts as a configuration service for automating the deployment and management of network
devices and services.

The Cisco MGC Node Manager (CMNM) provides an element management system for the PSTN
Gateway (PGW 2200). CMNM provides alarm processing and performance data collection that can be
displayed in a self contained Graphical User Interface (GUI) or forwarded to upstream processing
applications.

The provisioning component of the CMNM comprises two applications:

• Voice Services Provisioning Tool (VSPT)

• CiscoView.

VSPT is used as a provisioning service for the PGW 2200. VSPT communicates in Man Machine
Language (MML) to the PGW 2200, to configure point codes, link sets and SS7 paths and routes
CiscoView displays and monitors, and provides a GUI for chassis configuration for the Cisco SLT
(c2600 series) and LAN switch (Cisco Catalyst 2900, 5500 and 6509) devices.

Chapter 2 Provisioning

Document Purpose

A large collection of documentation, referenced in the “Related Documents” section, covering the
descriptions, installation,and preliminary setup of theapplications and components of thisProvisioning
Management Solution.The purposeof this chapter is todescribe a basic network containing the network
elements that are covered by these applications, install the management applications that comprise the
provisioning application set of the Internet OSS (IOSS) for packet voice networks, complete initial
configuration of those applications, and then use them to provision a sample network.

For detailed, in-depth information on installation and configuration of the individual applications, refer
to the documentation listed in the “Related Documents” section, that is available on Cisco Connection
Online. This chapter attempts to serve as a quick start guide to help you understand the entire
Provisioning Solution and how it fits into the overall Cisco VoIP: Infrastructure Manager Solution.

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-2

OL-2706-01

Chapter 2 Provisioning

Solution Architecture

Open Packet Telephony Overview

As an introduction to the Cisco VoIP: Infrastructure Manager Solution’s provisioning component
applications and devices, the following overview of the emerging technology of distributed packet
telephony is presented.

Telephony is no longer solely the domain of Public Switched Telephone Networks (PSTNs). Software
and protocols that allow telephone calls over packet networks, such as the Internet, have entered the
market place. They are based on:

• the Media Gateway Control Protocol (MGCP) and related protocols such as the Simple Gateway

Control Protocol (SGCP) and Megaco/H.248

• the Session Initiation Protocol (SIP)

• H.323.

This discussion focuses on MGCP and H.323, which are both supported by the Cisco Packet Telephony
Center and the entire provisioning suite of applications in the Internet OSS for packet based voice
networks.

Solution Architecture

Examples of Open Packet Telephony Networks

Figure 2-1 depicts an example of an MGCP-based OPT network. (In this discussion, there is no need to

distinguish further between the different MGCP derivatives, Megaco, H.248, and SGCP.) The bearer
plane is responsible for the transport of the actual payload. Network elements within the bearer plane
need not be concerned with the specifics of telephony applications. Switches or routers between media
gateways at the edge of the OPT network provide for the actual bearer fabric (the data cloud), shuffling
data packets back and forth. The control plane is responsible for signaling processing and call control;
it is here that the actual call-processing intelligence resides. The components in the control plane are
commonly referred to as Media Gateway Controllers (MGCs). MGCs control media gateways by
instructing them when to set up or tear down connections, requesting notification of specific events for
further processing, and so on. They contain all the logic required for telephony applications, including
Signaling System 7 (SS7) signaling termination, collection of accounting information, and, very
importantly, directory functions and call-level routing based on dial plans. In terms of numbers of
devices, there tend tobe much fewer MGCs than media gateways, meaningthat call intelligence is fairly
centralized.

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-3

Solution Architecture

Figure 2-1 MGCP Packet Voice Network

Media Gateway Controller (MGC)

MGC

VoP network

Circuit

Core/TDM

Class 4

Signaling and control

IP

network

SS7

STP STP

network

Chapter 2 Provisioning

Call control
MGCP, H. 248,
Megaco, SCTP,
signaling

backhaul,....

V

Media

PBX

Gateway

Figure 2-2 depicts an H.323-based network for Voice Infrastructure and Applications (VIA) Solution.

Similar to the MGCP network, gateways are at the edge of the network, with routers between them
providing for the bearer fabric that shuffles the payload back and forth. In H.323, unlike in MGCP, call
intelligence and the ability to process signaling does reside in the H.323 gateways. Intelligence is,
therefore, much more distributed, compared with MGCP-based networks. However, call processing is
still distributed between gateways and gatekeepers. Gatekeepers are able to make call-level routing
decisions based on dial plans.

In addition, gatekeeper hierarchies can be deployed, reflecting dial-plan hierarchies, with directory
gatekeepers on top of gatekeepers. Likewise, gatekeepers can be supported by route servers in their
decisions. If required, SS7 capabilities are provided through signaling converters that mediate and back
haul the signaling information between the gateway and the SS7 Signal Transfer Point.

Figure 2-2 H.323 Based Packet Voice Network

IP, PNNI, ...

Media

Gateway

Bearer

V

V

PBX

84405

CPE

Ingress

ITSP

STP

Ingress/Egress

SS7 TDM

carrier

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-4

GK

Ingress DGK

Ingress DGK

V

V

V

Prompts RADIUS

VV

GK GK

GK

GK

V

GK

Egress DGK

Egress DGK

Egress

TDM

carrier

Egress

ITSP

Egress

ASP

84408

OL-2706-01

Chapter 2 Provisioning

Virtual Entities in the Network

The requirements for coordinated element management are extensive. For instance, the media gateway
and MGC must be synchronized regarding the voice endpoints. Although the MGC has a concept of a
trunk, this concept is unknown to the media gateway that has the actual resources (TDM endpoints,
ports) that constitute the trunk.Therefore, theknowledge that boththe mediagateway and theMGC have
of the trunk must be managed in a coordinated way. Registration and synchronization of capabilities
must be assured. Beyond element management, failuresin voice service, observed at the MGC, must be
correlated with failures in the bearer network. Resources used at the media gateway and controlled by
the MGC must be associated with voice service, which the media gateway has no concept of.

Users require support for such management coordination. Components in the bearer and control planes
operate in conjunction to perform the function of a switch, as far as voice service is concerned.

Usually an MGC and a set of media gatewaysare clearlyassociated withone anotherand jointlyperform
the same function as a TDM switch, thus forming a virtual switch. This raises the expectation that this
virtual switch can, in fact, be managed as a switch, with a management system shielding many of the
aspects of the distribution of this virtual entity from users. This way, users do not have to be concerned
with the peculiarities of setting up control communications between the devices (interfaces that used to
be closed); for example, MGCP and signaling back haul, with the coordination of the configuration of
endpoints on the media gateway and of trunks that refer to those end points on the MGC and that now
collectively simply form virtual trunks of the virtual switch, and so on. Figure 2-3 depicts the concept
of a virtual switch.

Solution Architecture

Figure 2-3 Virtual Switch

Virtual switch

V

V

V

V

V

V

V

84409

Similarly, H.323 gateways and gatekeepers in a zone should be managed as just that, a virtual zone, as
if they were one entity. A virtual zone is in essence the H.323 flavor of a virtual switch. Also, gateways
and the signaling controller jointly provide the functionality of a virtual gateway that has SS7
capabilities.

A potent Management Solution should allow for a holistic management of those entities. Figure 2-4
depicts the concept of a virtual zone (which deals with dependencies between gateways within a zone,
as well as between gateways and gatekeepers), a virtual SS7 gateway (which deals with dependencies
between an H.323 gateway and a signaling controller that converts SS7 to Q.931 signaling for the
gateway), and a zone connection (which deals with dependencies between gatekeepers, or between
gatekeepers and directory gatekeepers).

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-5

Solution Architecture

Chapter 2 Provisioning

Figure 2-4 Other Virtual Network Entities

Ingress

The concept of virtual network entities is key to the management of packet voice networks. Cisco PTC
and it's companion provisioning management applications readily support this concept.

NMS Architecture

Figure 2-5 depicts theentire CiscoInternet OSS forVoIP: InfrastructureManager Solution architecture.

The three functional areas are provisioning/configuration, fault, and performance. This architecture is
shown here to help you better understand the complete Packet Voice Management Solution.

Virtual SS7

Gateway

SS7

STP

ITSP

Trunk

PGW 2200

V

AS5xxx

Virtual zone

V

V

GK

Virtual region

DGK DGK

V

V

V

GK

V V

GK

V V

84410

Figure 2-5 Cisco Internet OSS for VoIP: Infrastructure Manager Solution Architecture

Customer provided OSS components

Launcpad/portal (PTC)

Performance

Perform

(3rd party)

CNS

Perf ormance

Engine

Fault

Cisco

Info

Center

CNS

Notification

Engine

Gateways/

Gatekeepers

Pack et Telephony Center

Voice

Routing Center

CNS

Intelligence

Engine

Configuration/Provisioning

V oice

CORBA GW

Cisco
MGC
Node

Manager

Voice Services

Provisioning Tool

PGW 2200

Management

entry point

Network
elements

80941

2-6

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

IOSS Provisioning Component Architecture

Figure 2-6 depicts the proposed Provisioning Management Solution for OPT networks, as applied to an

H.323-based global long-distance network. The key component is the Cisco Packet Telephony Center
(Cisco PTC),which provides for overall configuration managementof the OPT network and realizes the
virtual entities as discussed. A module within Cisco PTC, called Cisco VRC, provides for H.323
dial-plan management. Cisco PTC enables context sensitive launching of other management tools, that
is, where itmakes sensefrom a navigationstandpoint, foran integrated userexperience. A pre-integrated
application is the Voice Services Provisioning Tool (VSPT), which can be used to bulk configure the
Cisco PSTN Gateway (PGW) 2200. VSPT is used for initial configuration of the PGW 2200 with SS7
components suchas pointcodes, link sets, SS7 paths and routes,SS7 subsystems,and ethernet cards and
interfaces, which are prerequisites to Cisco PTC configuringRLMs and nailed trunks in the PGW2200.

To communicate with underlying network devices, Cisco PTC makes use of underlying EMSs, such as
the Cisco MGC Node Manager (CMNM) for the Cisco PGW 2200. EMSs can also be launched as
auxiliary tools by the user to drill downinto the device or obtaina graphical device view. In cases where
an EMS is not readily available, Cisco PTC can also interface to devices directly or, as in the case of
Cisco IOS devices, utilize the Cisco CNS Intelligence Engine (Cisco CNS IE2100). It should be noted
that theapplicability ofthe Cisco PTC and itsfundamental concepts goes beyond any particular solution
and is not limited to support only certain device types; it is expected that essentially any Open Packet
Telephony (OPT) Solution can be added.

The network elements that can be provisioned with the pictured applications include:

1. Virtual zones of IOS based H.323 voice gateways and gatekeepers including:
a. AS5000 series.
b. c2600, c3600, c7200 series.

2. Virtual gateway node elements including:
a. Signaling Link Terminals.
b. PGW 2200 Signaling Controller.
c. Catalyst switches.
d. AS5000 series voice gateways.

Solution Architecture

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-7

Solution Architecture

Chapter 2 Provisioning

Figure 2-6 Provisioning Management Component Devices

Customer provided OSS components

Pack et Telephony Center

Voice Services

Cisco Voice Routing Center

CNS Intelligence Engine

Functional Description

Cisco PTC oversees the entire network. It is a network management tool that provides a GUI for the
initial andongoing support for configuringCisco Voice over IP(VoIP) networks, comprising PGW 2200
elements, H.323 gateways, and gatekeeper devices.

Cisco PTC is fully integrated with the Cisco VRC application. Cisco VRC provisions the dial plan
related functionality of the H.323 VoIP network elements (gateways and gatekeepers).

The Cisco MGC Node Manager (CMNM), built upon the Cisco Element Management Framework
(CEMF), integrates the management interfaces and management functionality of the PGW 2200
components into onecomprehensive human interfaceand datarepository.CMNM provides anintegrated
management application for fault, configuration, performance, and security of the PGW 2200 node
elements. CiscoView is integrated into theCMNM application asa monitoring andprovisioning tool for
PGW 2200 network elements.

The VSPT provides a GUI for bulk provisioning the PGW 2200.
The Cisco CNS Intelligence Engine is a networkmanagement device that acts as a configurationservice

for automating the deployment and management of network devices and services. The Cisco CNS
IE2100 Series is the hardware platform for the Cisco CNS Configuration Registrar application.

Cisco MGC

Node Manager

Voice Services

Provisioning Tool

PGW 2200Gateways Gatekeepers

84412

Interconnection/Interoperability

This chapter of the Cisco VoIP: Infrastructure Manager Solution specifically details the configuration
and provisioning management components of the Solution. These applications are intended to operate
in conjunction with applications that deal with fault and performance processing. There are several
points of interconnection between the function-specific applications.

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-8

OL-2706-01

Chapter 2 Provisioning

Configuration and Provisioning Solution Components

The gateways and gatekeepers that comprise the H.323 voice network send fault and performance data
directly to the fault and performance processing applications (Cisco CNS Notification Engine,
Cisco Info Center, and Cisco CNS Performance Engine). Protocols for transporting this data include
SNMP, Syslog, and RADIUS.

CMNM is a self-contained fault,configuration,performance, andsecurity (FCPS)Element Management
System (EMS) for the PGW 2200. It can stand on its own or operate in conjunction with the fault and
performance components of the Cisco VoIP: Infrastructure Manager Solution. CMNM can send
performance datato the CiscoCNS Performance Engine through periodic FTP uploads and can transmit
fault data directly to theCisco InfoCenter usingthe CEMFprobe describedin detailin Chapter 4,“Fault

Management.” Cisco PTC sends provisioning commands to the PGW 2200 elements through the Voice

CORBA interface in CMNM provided by CEMF.

Configuration and Provisioning Solution Components

Component List

The components that comprise the Cisco VoIP: Infrastructure Manager Solution’s configuration and
provisioning solution suite provision the network elements and manage the configuration files for those
elements. Version 1.1 of the Cisco VoIP: Infrastructure Manager Solution includes:

1. Cisco Packet Telephony Center integrated with:
a. Cisco Voice Routing Center (Cisco VRC).

2. Cisco MGC Node Manager built upon the Cisco Element Management Framework including:
a. Voice Services Provisioning Tool (VSPT).
b. CiscoView (native component in CiscoWorks2000).
c. Cisco CNS Configuration Registrar (Cisco CNS IE2100 Series).

The following sections detail the specifics of each of these applications.

Cisco Packet Telephony Center

The Cisco Packet Telephony Center provides a Management Solution for large-scale H.323 networks.
Cisco PTC providesnetwork managementlayer functionalityand managesthe network through Element
Management Systems (EMSs), or through the network element's management interface (for example,
SNMP or Command Line Interface (CLI)). Cisco PTC maintains a repository of the data, consisting of
customer and services information, for the managed network. This repository is used to configure the
network, provision new services, and to detect network layer configuration inconsistencies.

Refer to the Cisco Packet Telephony Center User Guide for an overview of the Cisco PTC domain
manager as well as other useful information about the product.

For a Cisco H.323 VoIP network composed of VoIP gateways and gatekeepers, Cisco PTC is integrated
with Cisco VRC.

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-9

Configuration and Provisioning Solution Components

Cisco Voice Routing Center

Cisco VRC is a GUI-based networkmanagement tool specifically designed for managing dial plans in a
Voice over IP (VoIP) network.

Cisco VRC, version 1.1, is targeted for H.323-based networks. H.323 VoIP dial plans are statically
configured and managed on gateway and gatekeeper platforms. The infrastructure of a typical H.323
VoIP network includes gateways and gatekeepers.

You can deploy Cisco VRCto discoverthe dial plan of an existing network. Youcan alsouse it to design
new dial plans incorporating Cisco routers running as gateways, gatekeepers, and directory gatekeepers.

For a complete description, installation instructions, and Release Notes for the Cisco VRC application,
refer to the “Related Documents” section.

Recommended Hardware Configuration for Cisco PTC and Cisco VRC

The minimum platform recommendations for the Cisco PTC and Cisco VRC applications are provided
in Table 2-1.

Table 2-1 Cisco PTC and Cisco VRC Hardware Requirements

Chapter 2 Provisioning

Number of Gateways Sun Workstation Model RAM Hard Disk Space Swap Space CPUs

Less than 1000 Entry level UltraSparcIII

(for example, a
Sun Fire 280R)

1000 to 3000 Entry level UltraSparcIII

(for example, a
Sun Fire 280R)

Cisco Media Gateway Control Node Manager

CMNM integrates the management interfaces and management functionality of the PGW 2200
components into one comprehensive human interface and data repository. The PGW 2200 consists of the
Cisco MGC host, one or more Cisco Signaling Link Terminals (Cisco SLTs) and the Cisco Catalyst
5500, Catalyst 2900 XL, or Catalyst 6509 LAN switch. CMNM provides fault, configuration, and
performance management for all components of the Cisco MGC node.

CMNM provides the element-specific management features for the Cisco MGC node. It blends the
management framework features of the Cisco Element Management Framework (Cisco EMF) with the
individual interfaces and object structures of each managed element to produce an integrated
management application. Figure 2-7 illustrates the element details of the MGC node and the CMNM
applications server(s).

Figure 2-7 provides the details of the network elements that comprise the PGW 2200 and CMNM.

1GB 9GB with at least

6GB available
under the /opt
directory

2GB 18GB with at

least 12GB
available under
the /opt directory

2GB 2

4GB 2

2-10

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Configuration and Provisioning Solution Components

Figure 2-7 PGW 2200 and MGC Node Manager Details

End user Xterminal

Cisco
PGW

2200

Catalyst

CMNM Features

MGC Node Manager

Presentation Server

Host/

SLT

detail

SLT SLT

Link

set A

MGC Node Manager

Management Server

Active Host Standby Host

Checkpointing

Signaling Control network

To Gateways and other

SS7 A or F links

set B

Cisco PGW 2200 nodes

Link

84413

The mostcommon Cisco EMF installation includesplug-in modules referred to asElement Managers or
Element Management Systems (EMSs). In the Cisco MGC node architecture, CMNM is a Cisco
EMF-based EMS responsible for managing the Cisco MGC node (PGW 2200). CMNM adds specific
GUI windows and modeling behavior to the standard Cisco EMF system to allow the management of
specific network elements.

CMNM uses Cisco EMF to manage the following components of the Cisco MGC node:

• Cisco MGC

• Cisco SLT

• LAN switch (Cisco Catalyst 2900, 5500 and 6509).

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-11

Configuration and Provisioning Solution Components

CMNM Configuration

You can open the following configuration tools from CMNM:

• Voice Services Provisioning Tool (VSPT)

• CiscoView, which allows you to configure and monitor the Cisco SLT and the LAN switch (Cisco

Catalyst 2900, 5500 and 6509) devices.

CMNM Troubleshooting

CMNM providesa fullrange of diagnostic and troubleshootingtools, such as IP and SNMP Ping, Alarm
and System Log, Host Status Check, Cross-Device Audit, and the Cisco MGC Toolbar that includes
CDR Viewer, Log Viewer, Trace Viewer, and Translation Verification Viewer.

Recommended Hardware Configuration for CMNM

The CMNM has substantial hardware requirements. The main consumer of resources in the CMNM
application is the CEMF application. The requirements below have been designed in order to create an
environment optimized for speed of response. These are general “rule of thumb” requirements and can
be adjusted to suit specific network deployments. Consultation with an experienced network design
specialist is recommended.

Chapter 2 Provisioning

Table 2-2 CMNM Hardware Requirements

Small Network:
1-3Operators
1-5 Nodes

Network Element

Number of machines One machine Two machines Three machines
Configuration Standalone Distributed

RAM (GB) 2 2 2 2 4
Swap (GB) 2 1 2 1 2
Hard drives @ 9GB

each (minimum)
Number of CPUs

and Speed

1 trap/second

41418

2 at 440Mhz 2 at 440Mhz 2 at 440Mhz 4 at 440Mhz 2 at 440Mhz

The Sun Fire 280R entrylevel server satisfies the above requirements.Refer to the CMNM User'sGuide,
at the following URL, for in depth details about CEMF and the Cisco MGC Node Manager:

http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/cmnm21/index.htm.

Medium Network:
4-6 Operators
6-10 Nodes
2 traps/second

Presentation Server Management Server

Large Network:
7-10 Operators
11-20 Nodes
4 traps/second

Distributed
Presentation Server Management Server

2-12

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Voice Services Provisioning Tool

Provisioning with the VSPT is the process of preparing a Cisco Media PGW 2200 to communicate with
an SS7 network, with Cisco media gateways, and with the other components of an OPT Solution. The
VSPT application provides an easy to use GUI to provision the Cisco PGW 2200.

VSPT can be deployed as an integrated component of the CMNM or as a standalone application. In the
Cisco VoIP: Infrastructure Manager Solution configuration, it runs on the CMNM server. It allows you
to import an existing configuration, modify the configuration, and export it to the same or different
devices; or wizards guide you through high-level configuration steps to create the initial network
provisioning informationfor a newlyinstalled node, creating iterative entries from a single operation.It
can alsofacilitate provisioningof individualcall parameters, simplifying the provisioningof a large live
network.

During a provisioning session, VSPT automatically generates the Man Machine Language (MML) or
command line interface (CLI) scripts used to configure network elements, assembles these commands
into a batch file, and deploys the file to the appropriate network device. VSPT is used to augment the
Cisco PTC provisioning application, providing bulk provisioning support and an alternative for
provisioning the PGW 2000.

Configuration and Provisioning Solution Components

Recommended Hardware Configuration for VSPT

VSPT runs on the CMNM server in this Cisco VoIP: Infrastructure Manager Solution.

CiscoView

CiscoView is a device monitoring application that is built into the CiscoWorks 2000 network
management package. Installing CiscoWorks 2000 is the method of adding CiscoView to your network
management applications. This Solution installs CiscoView (through the installation of
CiscoWorks 2000) on a separate Solaris 8 host. A prerequisite to the installation of CiscoWorks2K on
Solaris 8 is the installation of Solaris 8 patch 108827-19 or later. This Solution assumes you will install
the entire recommended patch cluster for Solaris 8 as outlined in the “Installing the Solaris 8 Patch

Cluster” section.

CiscoView is launched by the CMNM application to provide a device level view of Cisco network
devices.CiscoViewprovidessupport fora widerange ofdevicesand hasthe capabilityof adding support
for futuredevices throughdownload ofdevice specific description files. CiscoView aids in zeroing in on
trouble spots in the network or in providing device specific hardware and interface usage data.

Recommended Hardware Configuration for CiscoView

CiscoView is installed on the CMNM host machine and is already considered in the hardware
recommendations for CMNM.

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-13

Configuration and Provisioning Solution Components

Cisco CNS Intelligence Engine

Cisco CNS Intelligence Engine and Cisco CNS Bus Technology

The Cisco CNS IntelligenceEngine (CiscoCNS IE2100Series) isa networkmanagement appliancethat
acts as a configuration service for automating the deployment and management of network devices and
services. The Cisco CNS IE2100 appliance sits between Cisco PTC/Cisco VRC and the network
elements, utilizing the Cisco CNS Integration Bus for data transport between the provisioning
applications and the network elements.

The Cisco CNS Configuration Registrar applicationis aweb-based systemfor automaticallydistributing
configurationfiles to Cisco IOS network devices running Cisco IOSversion 12.2(2) T, or later. Once the
Cisco CNS IE2100 appliance is initially configured and the network elements are configured to use the
Cisco CNS IE2100appliance withtwo command linearguments, the systemthen operatesautomatically.

Note If youare running devices that useand earlier version of CiscoIOS or a different operating system, such

as Catalyst, you should invoke the Intelligent Modular Gateway (IMG) for communicating with the
device.

Chapter 2 Provisioning

The Cisco CNS Configuration Registrar application utilizes the following industry standards and
technologies:

• eXtensible Markup Language (XML)

• Java Naming Directory Interface (JNDI)

• Hypertext Transport Protocol (HTTP)

• Java servlets

• Lightweight Directory Access Protocol (LDAP).

The Cisco CNS IE2100 Series can be used as the runtime component for deployment of
customer-developed applications. These applications can be developed using the Cisco CNS SDK 1.5.
Complete descriptions and installation and configuration information can be found at the URL listed in
the “Related Documents” section.

Hardware Requirements

The Cisco CNS Configuration Registrar is an application that runs on its own piece of hardware which
is typically a 1 RU IBM rack mount server running the Linux Operating System.

2-14

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Step by Step Installation and Initial Configuration

Step by Step Installation and Initial Configuration

Overview of Installation

The order of installation follows the plan below:

1. Install and configure the Cisco CNS IE2100 appliance with a subnet IP address.

2. On the CMNM host, install the Cisco MGC Node Manager application, including:
a. Voice Services Provisioning Tool.
b. CEMF 3.2.
c. CiscoView upgrade if necessary.
d. Cisco MGC Node Manager (server).

3. On the Cisco PTC/Cisco VRC host, install Cisco PTC, version 2.1.1, integrated with Cisco VRC,

version 1.1.

Once the applications are installed, they are started, and then checked for running processes on each
machine.

Dependencies

It is highly recommended that you obtain all of the Installation and User Guides referenced in the

“Related Documents” section, for Cisco CNS IE2100 Series, CMNM, and Cisco PTC/Cisco VRC.

Although lengthy, these guides provide a clear, organized way to approach preparing for, obtaining, and
installing thevarious applicationsoftware. There are many interdependenciesthat make the deployment
of this management software non-trivial. This chapter makes many references to the User and
Installation Guides, as well as the other collateral referenced in the “Related Documents” section.

You may wonder why the installation information is repeated in this chapter when it is available in the
other guides as well. In fact, the installation information in this chapter is mostly copied from the
individual User and Installation guides of the different applications adding little that is new or specific
to this chapter. The answer is that this chapter is detailing a solution that incorporates at least five
different applications and devices. So, instead of pointing you to the many guides, requiring that you
either read the guide electronically and activate the various links or much typing of URLs into web
browsers, we wish to create a guide that can be accessed either in soft or hard copy that is somewhat
complete in itself.

Somewhat complete means that the “official” User and Installation guides cover every situation that the
developers could envision, whereas this guide is specifically pointed at a certain solution and
deployment and can be less detailed than the guides that accompany the application.

Installing the Cisco CNS IE2100 Configuration Engine

The Cisco CNS Configuration Registrarrefers to the application, while the Cisco CNS IE2100 appliance
is a specific device that makes use of the application software. The Cisco CNS Configuration Registrar
is a self contained, Linux based application, which runs on a one RU, rack mount, IBM host. In
preparation for installation, the Cisco CNS IE2100 appliance should be rack mounted and connected to
the management network through its Ethernet port.

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-15

Step by Step Installation and Initial Configuration

Installation Overview

The installation procedure for the Cisco CNS Configuration Registrar is straightforward. The software
is installed and configured through a console connection to the serial port. The console connection
parameters are the same as for other Cisco IOS devices, that is:

• 9600 baud

• Parity: 8/None

• Stop bits: 1.

Step 1 After the Cisco CNS IE2100 appliance is optionally racked, plugged in, and turned on, insert the

CDROM installation disk and press the Reset button.
You can not monitor the installation procedure as the console logic does not begin until the Operating

System isstarted. After the automatic installation procedure completes, theCD ejects automatically and
the system restarts, at which point the login prompt appears in the Console window.

Step 2 Log in as user setup.

The Setup program starts.

Step 3 Enter responses to the prompts that appear.

After you enter a response, you cannot edit it again. To change an entered response, you must exit the
Setup program and enter your responses again. You can exit the Setup program in two ways:

• Press Ctrl-c. The login prompt appears. Use the login setup to run the Setup program.

• Enter n at the final prompt. The Setup program exits, then restarts.

Refer to the sample setup session below for an example of the prompts and their responses:

Step 4 Press ESC to log in:

USER ID:
LILO
boot:
boot:

Loading linux......................

Linux version 2.4.2-2 ([e-mail]) (gcc version 2.96
20000731 (Red Hat Linux 7.1 2.96-79)) #1 Sun Apr 8 20:41:30 EDT 2001
BIOS-provided physical RAM map:
BIOS-e820: 000000000009dc00 @ 0000000000000000 (usable)
BIOS-e820: 0000000000002400 @ 000000000009dc00 (reserved)
BIOS-e820: 0000000000020000 @ 00000000000e0000 (reserved)
BIOS-e820: 000000003feec340 @ 0000000000100000 (usable)
BIOS-e820: 0000000000010000 @ 000000003fff0000 (reserved)
BIOS-e820: 0000000000003cc0 @ 000000003ffec340 (ACPI data)
BIOS-e820: 0000000001400000 @ 00000000fec00000 (reserved)
127MB HIGHMEM available.
On node 0 totalpages: 262124
zone(0): 4096 pages.
zone DMA has max 32 cached pages.
zone(1): 225280 pages.
zone Normal has max 1024 cached pages.

Chapter 2 Provisioning

2-16

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Step by Step Installation and Initial Configuration

zone(2): 32748 pages.
zone HighMem has max 255 cached pages.
hm, page 01000000 reserved twice.
Kernel command line: auto BOOT_IMAGE=linux ro root=806
BOOT_FILE=/boot/vmlinuz-2.4.2-2 console=ttyS0,9600n8
Initializing CPU#0
Detected 1130.197 MHz processor.
Console: color VGA+ 80x25
Calibrating delay loop... 2254.43 BogoMIPS
Memory: 1028188k/1048496k available (1365k kernel code, 19912k reserved,
92k data, 236k init, 130992k highmem)
Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
VFS: Diskquotas version dquot_6.5.0 initialized
CPU: Before vendor init, caps: 0383fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0383fbff 00000000 00000000 00000000
CPU: After generic, caps: 0383fbff 00000000 00000000 00000000
CPU: Common caps: 0383fbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) III CPU family 1133MHz stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.37 (20001109) Richard Gooch ([e-mail])
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfd61c, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Discovered peer bus 01
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd v1.8
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
block: queued sectors max/low 682808kB/551736kB, 2048 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-17

Step by Step Installation and Initial Configuration

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
ServerWorks OSB4: chipset revision 0
ServerWorks OSB4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0x0708-0x070f, BIOS settings: hdc:DMA, hdd:DMA
hda: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 359k freed
Serial driver version 5.02 (2000-08-09) with MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10d
md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md.c: sizeof(mdp_super_t) = 4096
autodetecting RAID arrays
autorun ...
... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem).
Red Hat nash verSCSI subsystem driver Revision: 1.00
version 3.0.10 starting
Loading sc(scsi0) <Adaptec AIC-7892 Ultra 160/m SCSI host adapter> found at si_mod module
LPCI 1/3/0
Loading sd_mod mo(scsi0) Wide module
Loading aiChannel, SCSI ID=7, c7xxx module
32/255 SCBs
(scsi0) Downloading sequencer code... 396 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0
<Adaptec AIC-7892 Ultra 160/m SCSI host adapter>
(scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec, offset 63.
Vendor: IBM-ESXS Model: ST318305LC !# Rev: B245
Type: Direct-Access ANSI SCSI revision: 03
Vendor: IBM Model: FTlV1 S2 Rev: 0
Type: Processor ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 35548320 512-byte hdwr sectors (18201 MB)

Chapter 2 Provisioning

2-18

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Step by Step Installation and Initial Configuration

Partition check:
sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 >
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=3
Trying to unmount old root ... okay
Freeing unused kernel memory: 236k freed
INIT: version 2.78 booting
Welcome to Red Hat Linux
Press 'I' to enter interactive startup.
Mounting proc filesystem: [OK]
Configuring kernel parameters: [OK]
Setting clock (localtime): Fri Oct 4 10:02:43 PDT 2002 [OK]
Activating swap partitions: [OK]
Setting hostname localhost.localdomain: [OK]
Mounting USB filesystem: [OK]
Initializing USB controller (usb-ohci): [OK]
Checking root filesystem
/: clean, 16950/263296 files, 22733/526120 blocks
[/sbin/fsck.ext2 -- /] fsck.ext2 -a /dev/sda6 [OK]
Remounting root filesystem in read-write mode: [OK]
Finding module dependencies: [OK]
Checking filesystems
/boot: clean, 28/14056 files, 5656/56196 blocks
/extra: clean, 12/131616 files, 4147/263056 blocks
/home: clean, 27/244320 files, 7697/487966 blocks
/opt: clean, 3290/263296 files, 68085/526120 blocks
/tmp: clean, 16/131616 files, 4153/263056 blocks
/usr: clean, 33248/525888 files, 142855/1050241 blocks
/var: clean, 338/131616 files, 7654/263056 blocks
Checking all file systems.
[/sbin/fsck.ext2 -- /boot] fsck.ext2 -a /dev/sda1
[/sbin/fsck.ext2 -- /extra] fsck.ext2 -a /dev/sda13
[/sbin/fsck.ext2 -- /home] fsck.ext2 -a /dev/sda10
[/sbin/fsck.ext2 -- /opt] fsck.ext2 -a /dev/sda7
[/sbin/fsck.ext2 -- /tmp] fsck.ext2 -a /dev/sda12
[/sbin/fsck.ext2 -- /usr] fsck.ext2 -a /dev/sda5
[/sbin/fsck.ext2 -- /var] fsck.ext2 -a /dev/sda11 [OK]
Mounting local filesystems: [OK]
Turning on user and group quotas for local filesystems: [OK]
Enabling swap space: [OK]
INIT: Entering runlevel: 3
Entering non-interactive startup
Updating /etc/fstab [OK]
Checking for new hardware [OK]
Setting network parameters: [OK]
Bringing up interface lo: [OK]

OL-2706-01

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-19

Step by Step Installation and Initial Configuration

Starting system logger: [OK]
Starting kernel logger: [OK]
Starting portmapper: [OK]
Starting NFS file locking services:
Starting NFS statd: [OK]
Starting keytable: [OK]
Initializing random number generator: [OK]
Mounting other filesystems: [OK]
Starting automount:[OK]
Starting atd: [OK]
Starting sshd: [OK]
Starting xinetd: [OK]
Starting lpd: No Printers Defined[OK]
Starting sendmail: [OK]
Starting console mouse services: [OK]
Starting crond: [OK]
Starting xfs: [OK]
Starting anacron: [OK]
This Appliance is not configured.
Please login as setup to configure the appliance.

Chapter 2 Provisioning

localhost.localdomain login: setup
Cisco Intelligence Engine 2110
Cisco Configuration Registrar (tm) Software, Version 1.2(1a) [ming_cao-ie2100_1_2_fcs.p1

100]
Copyright (c) 2001, 2002 by cisco Systems, Inc.
Compiled Tue 05-Mar-2002 20:37 by ming_cao

Entering Network Appliance Setup
Type ctrl-c to exit

Where is the setup file? 0=local, 1=remote. [0]
Choose operational mode for the appliance. 0=internal directory mode,
1=external directory mode. [0]
Enter the root user password: ******
Re-Enter the root user password: ******
Enter the host name: ie-tme
Enter the domain name: cisco.com
Enter the administrative username: admin
Enter the admin password: ******
Re-Enter the admin password: ******
Enter the eth0 ip address: 172.19.49.20
Enter the eth0 network mask: 255.255.255.224
Enter the eth0 default gateway ip address: 172.19.49.1
Enter the eth1 ip address:
Enter the Primary DNS Server IP address: 171.70.168.183

2-20

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Step by Step Installation and Initial Configuration

Enter the Secondary DNS Server IP address: 171.68.226.120
Enter the Country Code: us
Enter the Company Code: cisco
Enter the ConfigService AdminID: csadmin
Enter the ConfigService password: ******
Re-Enter the ConfigService password: ******
Enter the NSM Directives:
This field requires an input.
Enter the NSM Directives: default://
Enter the Event Gateway Debug Log (y/n): n
Enter the # of Event Gateways N for serving 500 x N devices: 1
Enter the CNS Event Bus Network Parameter: [ie-tme]
Enter the CNS Event Bus Service Parameter: [7500]

Current settings of IMGW:

------------------------­Gateway ID: ie-tme
Run as daemon (true/false): true
Script Operation Timeout (sec): 180
Device Prompt Timeout (sec): 60
Concurrent Telnet Session Limit: 20
Remove Temp File (true/false): true
Location of Temp Files: /tmp
Hoptest Success Retry Interval (sec): 7200
Hoptest Failure Retry Interval (sec): 3600
Logging Level (error,verbose,silent): error
Logging File Prefix: IMGW-LOG
Log File Size (byte): 50331648
Log File Rotation Timer (minute): 60
Logging Mode (append,overwrite): append

OL-2706-01

Re-configure IMGW (y/n): n

Please review the following parameters:
root user password: ******
host name: ie-tme
domain name: cisco.com
administrative username: admin
admin password: ******
eth0 ip address: 172.19.49.20
eth0 network mask: 255.255.255.224
eth0 default gateway ip address: 172.19.49.1
eth1 ip address:
Primary DNS Server IP address: 171.70.168.183
Secondary DNS Server IP address: 171.68.226.120
Country Code: us

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

2-21

Step by Step Installation and Initial Configuration

Company Code: cisco
ConfigService AdminID: csadmin
ConfigService password: ******
NSM Directives: default://
Event Gateway Debug Log (y/n): n
# of Event Gateways N for serving 500 x N devices: 1
CNS Event Bus Network Parameter: ie-tme
CNS Event Bus Service Parameter: 7500
Re-configure IMGW (y/n): n
Commit changes (y/n): y
Update administrator info ...
Shutdown servers ...
Configure network ...
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<[e-mail]> and others
Configure IMGW ...
Configure DCL ...
Run configurator ...
Configure EvtGateway start/stop file ...
Register tibco rvrd start/stop script for system shutdown/restart ...
Run NSM configurator ...
Start servers ...
/etc/rc.d/init.d/NetAppDCL start
Start tibco

Chapter 2 Provisioning

2-22

/etc/rc.d/init.d/tibco start >> /var/log/appliance-setup.log 2>&1
/etc/rc.d/init.d/httpd start
/etc/rc.d/init.d/Imgw start >> /var/log/appliance-setup.log 2>&1
/etc/rc.d/init.d/EvtGateway start >> /var/log/appliance-setup.log 2>&1
Initialize DCL for Internal Mode ...
Configure DAT ...
Install IBM Director takes approximately 4 minutes ...
IBM Advanced System Management Device Driver loaded.
cd /opt/IBMDirectorInstall; nohup sh /opt/IBMDirectorInstall/dirinstall
>> /var/log/appliance-setup.log 2>&1
Setup completed!
Press <Enter> to login!

Red Hat Linux release 7.1 (Seawolf)
Kernel 2.4.2-2 on an i686

ie-tme.cisco.com login: root
Password:
Last login: Fri Oct 4 10:12:27 on ttyS0

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

Chapter 2 Provisioning

Step by Step Installation and Initial Configuration

Cisco Intelligence Engine 2110
Cisco Configuration Registrar (tm) Software, Version 1.2(1a) [ming_cao-ie2100_1_2_fcs.p1

100]
Copyright (c) 2001, 2002 by cisco Systems, Inc.
Compiled Tue 05-Mar-2002 20:37 by ming_cao

[root@ie-tme /root]#

Refer to the Cisco CNS Configuration Registrar Installation Guide for more details. The “Related

Documents” section provides a URL to the Cisco CNS Configuration Registrar documentation.Once the

Cisco CNS IE2100 appliance has been setup, you should be able to access it through a web browser at
the URL:

http://<hostname or IP address of IE2100>/config/login.html.

The Cisco CNS Configuration Registrar Login window, shown in Figure 2-8, appears.

Figure 2-8 Cisco CNS IE2100 Cisco CNS Configuration Registrar Login Window

When you see this screen, you are ready to configure the Cisco CNS IE2100 appliance.

Configuring IOS Devices to Communicate with a Cisco CNS IE2100 Appliance

In order to support communication with the Cisco CNS IE2100 appliance, IOS network elements must
be operating with IOS version 12.2(8)T or later. Two IOS commands must be entered into the IOS
device:

• us-gw-1(config)# cns config partial 172.19.49.20 80

• us-gw-1(config)# cns event 172.19.49.20 keepalive 100 30

Cisco Internet OSS for VoIP: Infrastructure Manager Implementation Guide

OL-2706-01

2-23