Cisco WAN Manager

Document ID: 47740

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Inter-Process Communications
      Ilog Messages
      Corba
      Shared Memory
Protocol-Specific Communications
      Stratacom Proprietary
      SNMP
      TFTP
      FTP
      Telnet
Conclusions
Cisco Support Community - Featured Conversations
Related Information

Introduction

This document explains the different internal and external data flows generated by Cisco WAN Manager (CWM). Two types of flow exist:

• Inter-process communications (IPCs): among the different CWM modules

• Protocol specific communications: between CWM modules and managed devices

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• CWM 11.0

• CWM 12.0

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

These conventions are specific to this document:

• Names of processes are written in italic bold, for example: watchdog .

• Names of scripts are written in italic only, for example: start_SV+.

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Inter-Process Communications

Communications between processes can occur locally or through the network because CWM can be fully distributed. On the local server, CWM IPCs can conflict with other products when the ports that are used conflict.

CWM uses several ways for IPCs:

• Ilog messages

• Corba

• Shared memory

Ilog Messages

Ilog is an implementation of the remote procedure call. These processes use ilog:

• Topod

• TopoServer

• linktopoc

• filetopoc

• ILMITopoc

• CWMGateway

• watchdog

• emd

• emc

• ooemc

• cwmftpd

• tftpd

• iosmgr

• CwmGs

• snmpcomm

• databroker

• rtm

• cmgrd

• *Proxy

• vnd

• svmain

• emsd

• emsc

• cmsvr

• extractd

• scmctrlsvr

Corba

These processes use Corba (Orbix implementation):

• CWM Gateway

• CM Server and CM GUI

• Log Server

• Network Topology and related GUIs

• CWM Generic Server and Security Manager GUI

• Config Save Restore Server (CSRID) and GUI

• Wandest Server and Client

• Corba Service Agent

• Audit Logger

• SCM (Control server, Collection Server and Parser)

• SCMGateway

Corba communications can happen across networks, such as statistic collector with statistic controller. There is a warning about firewall port restriction that can affect topology display in 12.0. Refer to CWM 12.0 Release-notes for more information on how to tune your network. For more information on processes, refer to Cisco Wan Manager Processes

Shared Memory

Some parts of the CWM server, such as element managers with sdbrokers and Informix, use shared memory to exchange data. The installation script updates /etc/system in order to make sure there is enough shared memory resource.

Protocol-Specific Communications

Many CWM services must contact switches for operations. These are the different protocols used:

• Stratacom proprietary

• SNMP

• TFTP

• FTP

• Telnet

Stratacom Proprietary

To discover an Autoroute network, CWM talks to the gateway switch with the Stratacom proprietary protocol. To do so, CWM opens port 5120 on the gateway node. The process svmain is responsible for that connection. To troubleshoot Autoroute network discovery done through svmain , refer to Troubleshooting Autoroute Network Discovery.

SNMP

This management protocol is used to verify the stats master configured on a switch, PNNI network discovery, and connection provisioning. You must make sure the communities are consistent on switches and the CWM. You can tune communities on the CWM server with the Network configurator application. CWM 12.0 introduces a new interface to achieve this configuration. Refer to the CWM 12.0 User's Guide for instructions.

Every process that must send SNMP requests, uses snmpcomm process to perform the actual request.

TFTP

This trivial file transfer protocol (TFTP) is mainly used for:

• switch configuration download during MGX discovery (8220, pxm1 based switches)

• SWSW upload, configuration upload

• and statistic files download from Autoroute clouds

FTP

The file transfer protocol is more reliable than TFTP and is used for:

• PNNI switch discovery when uploading configuration files

• Statistic files upload from PNNI switches

• Communications between CWM servers, that is between wandest server and client, between statistic collectors and statistic controller.

The cwmftpd process is responsible for all the FTP transactions.

Telnet

You need the telnet protocol when you configure connections on IOS based elements, such as RPM cards. CWM also uses that protocol when it must execute commands on the switches using, for example, the CLI load configuration.

Conclusions

Many different technologies and protocols are used for CWM communications. You must be sure your server and network setups do not block these communications. You must consult release-notes to see which sockets CWM servers use. The release-notes can also give guidelines about port and firewall configurations.

To see which sockets are used by the product, refer to CWM release-notes:

• CWM 11.0: CWM Dedicated IP Ports

• CWM 12.0: CWM Dedicated IP Ports

Cisco Support Community - Featured Conversations

Related Information

• Cisco WAN Manager Technical Tips
• Cisco WAN Manager Documentation
• Cisco WAN Manager Patches
• Technical Support - Cisco Systems