Views

The older "classic" architecture, where provisioning of InfoVista Servers is done by a VistaProvisioner component and the VistaMart is optional
The newer "centralized" architecture where VistaMart is no longer optional and provisions the Infovista Servers

Both architectures consist of:

Infovista Servers, which locally collect statistics into circular Objectstore databases, organized in time-slots.
VistaMart central repository (optional in "classic" architecture) consolidating data collected by multiple Infovista Servers
VistaPortals
- The VistaPortal "standard edition" that renders in real-time data collected by Infovista Servers, by directly connecting to them
- The VistaPortal for VistaMart, that provides historical consolidated/aggregated reporting from the VistaMart database
VistaCockpit, a central management and monitoring console for InfoVista distributed deployments.

In both architectures he VistaMart Gateway component collects data polled by InfoVista servers, aggregates and converts it to VistaMart format and then inserts it into the VistaMart Oracle Repository.

The Infovista Server collects statistics through SNMP polling, ICMP response-time measurement or log-file import. It is a software application running on Windows or Solaris servers and uses a local Objectstore database to store collected metrics into time-slots. The VistaMart is a data warehousing software application, running on a Windows or Solaris server and providing a central repository (based on a table-partitioned Oracle Database) and provides advanced reporting and analysis capabilities. The VistaPortals are software applications that provide a GUI interface for visualizing in real-time and historical reporting on the collected measurements from the Infovista Servers and the VistaMart. The VistaCockpit is a software application (offering a GUI console) that provides a central management console to administer and monitor the health of InfoVista components, both servers and services.

[edit]

Classic Architecture

In the ‘Classic’ architecture, a VistaProvisioner component uploads topology and configuration data onto designated InfoVista servers. Topology files are usually split to match server collecting capacity. A VistaGateway component is being used to synchronize objects in the VistaMart with those in the Infovista Servers.

[edit]

Centralized architecture

In the 'Centralized' architecture, VistaMart provisions topology data and configuration directly in the InfoVista Servers and sinchronizes its objects with those on the InfoVista Servers. In the Centralized Architecture there is no need for the VistaProvisioner component.

[edit]

VistaInsight components

A VistaInsight component provides the VistaPortal with advanced reporting on a specific area of Infrastructure. Each VistaInsight product addresses specific categories of measurements that focus on specific management needs for the IT infrastructure. Examples are VistaInsight for Servers, for Networks, for IP Telephony or for IP-VPN. Each VistaInsight adds to the "common" Vista model an area-specific part of the InfoVista [Object] Model, that organizes the IT objects being measured into functional categories and establishes the relationships between them.

[edit]

VistaInsight for Networks (VIN)

The VistaInsight for Networks provides functionality for capacity planning, performance monitoring, service-level verification, inventory and surveillance in network environments, by defining measures for:

Availability and reachability of network devices, services and interfaces
Saturation and downtime of network devices, services and interfaces
Capacity-in-use monitoring, reporting and trend analysis for capacity planning
Network inventory reporting

[edit]

VistaInsight for IP telephony

The VistaInsight for IP Telephony allows management and monitoring of resources and measurements specific to IP telephony environments, especially those related to the QoS aspect of the service. The VistaInsight for IP Telephony is an agentless solution and provides SNMP-based measurements on IP telephony components like Cisco voice gateways, routers or the Cisco Call Manager. It gathers and analyzes Cisco’s IPSLA measurements and Cisco CallManager CDRs to monitor both call and voice quality and to identify present conditions and potential performance issues. The optional VoIP Extension Module, similar in principle and offered functionality to Cisco's IPSLA feature, adds some capabilities to VistaInsight for IP telephony:

Capture of user-based quality of experience data
Generic VoIP QoS instrumentation
Detailed voice quality distributions on top of summary averages
Root cause analysis for voice quality degradation

The VoIP Extension Module is based on Psytechnics QoS measurement technology, using a Master/Responder configurations, measuring VoIP QoS between the Infovista Servers hosting the VoIP Extension Module. The licensed "Master" component injects synthetic RTP voice streams (every 1, 5, or 15 minutes) into the network with actual voice payload. The Responder receiving the synthetic voice stream calculates the jitter, delay and packet loss, and in turn, injects its own synthetic voice stream into the network.

These are the IP Telephony KPIs and Metrics provided by the VistaInsight for IP Telephony:

Telephony : call quality, successful vs failed calls, trending (time-to-SLA-violation)
Servers : workload, saturation, utilization, availability, trending (time-to-saturation)
Applications : utilization, availability
Network : QoS, delay, jitter, packet loss, utilization, availability, trending (time-to-capacity)

[edit]

VistaInsight for IP-VPN

VistaInsight for IP-VPN is geared toward capacity and performance management for MPLS-based VPNs. It relies on measurements obtained through Cisco IPSLA and Cisco proprietary Proxy Ping, for jitter, latency and packet loss. The Infovista Server will automatically provision and activate (through SNMP) the IPSLA probes into the the Cisco routers specified by the report. The following metrics are collected and analyzed:

Real-time and historical utilization (Avg, max, min and percentile)
CE to CE, PE to PE, and CE to PE performance metrics (jitter, latency and packet loss)
Class of Service usage (of bandwidth)
Real-time and historical error rates
Real-time and historical response time (Average, maximum)
Real-time and historical availability

[edit]

VistaViews

VistaViews define all the necessary provisioning within InfoVista Servers to collect, analyze, store and report on a particular set of performance metrics. Each VistaView comes with a set of pre-built reports targeted to specific performance metrics of specific categories of devices, equipment or technologies.

Available VistaViews:

Standard VistaViews
VistaViews for Network Infrastructures
VistaViews for Server Infrastructures
VistaViews for IP Networking Services
VistaViews for WAN Switches
VistaViews for Application Servers
VistaViews for Application E2E Performance
VistaViews for Network Security
VistaViews for Capacity and SLA Planning

[edit]

VistaView forInfoVista IP Telephony - Cisco CallManager

It uses source data coming from devices supporting the CISCO-CCM-MIB and NT-PERF-MON-MIB. It provides reporting on:

IP telephony device availability, phone statistics, gateway status, availability of conference bridges
CallManager cluster status, availability, CPU/memory utilization, bandwidth utilization, device registration statistics (IP phones and other devices)
MGCP performance reports on analog (FXS/FXO) and digital (T1CAS) voice ports (in-service and active)
IP Telephony conferencing resources usage (media, software and hardware), active participants
Availability and usage of CTI, MOH and transcoding resources
TFTP service performance (total/failed requests, heartbeat, availability)

[edit]

VistaView for MPLS Traffic Engineering

The VistaView for MPLS Traffic Engineering provides MPLS tunnel (LSP) service-performance statistics coming from the MPLS-LSR-MIB and the MPLS-LSR-TE-MIB. The metrics, which include load and error statistics (alowing network administrators to take traffic-rerouting decisions) and tunnel exceptions statistics (in the event of link failure or rerouting problems), allow reporting on:

MPLS Tunnel parameter information
Performance metrics like tunnel-load, errors, and traffic (in bytes and packets)
Summary statistics like "top" and "bottom" N for load, errors, and traffic (in bytes and packets)
Tunnel exception information

[edit]

VistaView for VoIP - Cisco IPSLA

The VistaView for VoIP - Cisco IPSLA provides QoS statistics by retrieving from CISCO-RTTMON-MIB the measurements obtained by running Cisco IPSLA tests. It provides reporting for:

Delay, jitter, throughput and packet loss along selected network paths and service classes
Target reachability, maximum stress, throughput, and estimates for maximum simultaneous calls (inferred based on bandwidth usage)
Detailed statistics for MOS and Calculated Planning Impairment Factor (ICPIF)

[edit]

VistaView for Cisco VoIP Gateways

The VistaView for Cisco VoIP Gateways is extracting information from a variety of voice-specific MIBs and provides reporting on:

Call statistics (success rate, Answer Seizure Ratio (ASR), blockage, duration, Minute Of Use (MOU), ICPIF, calls attempted, completed, disconnected, etc)
Trunk summary statistics giving per-slot channel utilization per slot, trunk information and statistics, active calls summary and calls/traffic summary.
Channel summary statistics,giving the operational states and metrics for each active channel the and slot/port information

[edit]

VistaBridge

A toolset allowing extending Infovista capabilities by importing data from external sources into :

Infovista Server (VistaBridge for Infovista)
VistaMart (VistaBridge for VistaMart)

Based on predefined configuration files VistaBridge handles instance creation or reconciliation and can start reports and associated indicators. Examples of use cases:

Importing data from external non-SNMP sources with instance creation thereof
Importing KPI from external SLA calculation and reconciliation with existing instances

[edit]

SMARTS InCharge

The original documentation for the SMARTS Incharge product suite can be found here. The Cisco's Network Connectivity Center is an OEM product based on SMARTS InCharge 6.2 and its documentation is a good reference for SMARTS InCharge.

The software components of the SMARTS InCharge solution are:

Service Assurance Manager (SAM), providing the Global Consoles, an "adapter interface" and optional modules:
- InCharge Service Assurance Manager Open Integration (OI) platform, allowing getting/generating notifications from/to external sources.
- InCharge Business Impact Manager (BIM) allowing to associate "business impacts" on "business elements" to "problems" correlated by SAM
- InCharge Report Manager [1] allowing advanced reporting (with Crystal Reports) on metrics related to faults, exceptions and their impact on business operations.
- InCharge WebConsole, a web application using Java-applet and Java-webstart technology
- InCharge Business Dashboard, showing in summary form the map and status of business elements in terms of active exceptions and impacts
InCharge Adapter Modules [2]
InCharge IP Performance and Availability Manager (AM/PM)
InCharge Application Services Manager (ASM), with different optional modules and "editions"

[edit]

ICIM Hierarchies

The InCharge CIM (ICIM) model represents the managed network system as two parallel hierarchies: physical and logical. A physical network element is a hardware device or component to which one could attach an inventory tag (e.g. a server, router or switch). A logical network element provides some service or connection between other elements, e.g. a protocol, routing table, virtual interface, VLAN or class of service. The element classes are connected through association relationships (e.g. "ComposedOf" or "PartOf"). All physical element classes (e.g. Card, Chassis, Rack) are subclassing the ICIM_PhysicalElement class (actually ICIM_PhysicalPackage), describing elements with physical characteristics. In terms of object model, ICIM_PhysicalPackage, represents physical elements that can contain or host other physical elements. All logical element classes are subclassing the ICIM_LogicalElement class, which describes abstract system components (e.g. ProtocolEndpoints, LogicalLinks, logical devices). During the discovery process, when specific instances for the "leaf" ICIM classes are generated, the AM/PM tries to match the SysObjectID values it reads (through SNMP) from discovered Network Elements against an internal database of "certified" devices. Each instance of a particular "leaf" class has metrics associated that the AM/PM can collect through SNMP, from standard or proprietary MIBs. Not all logical elements are recognized on all device types, even on "certified" ones, as many of the metrics might reside in proprietary MIBs, although the certified Cisco network devices are generally well supported in terms of MIBs.

Important ICIM logical element classes, largely modeled after DMTF`s CIM framework, are:

ICIM_ComputerSystem, having as important subclasses:
- Host, e.g. a "certified" workstation or server
- Certified relay devices (e.g Hub, Switch, Bridge and Router), which are Layer 2 or Layer 3 packet forwarders
- Node, i.e. generic SNMP-pollable node, without making other assumptions about supported MIBs.
- Uncertified device, i.e. its sysObjectId was not found in the AM/PM`s internal database of certified devices
NetworkAdapter, representing Layer 2 connection points, with 2 subclasses : Interface and Port )(each associated with a MIB)
ICIM_ServiceAccessPoint, whose only subclass ProtocolEndpoint having beneath a taxonomy of classes (each associated with a MIB) representing access protocols to a device:
- DLCI, a Frame Relay Data Connection Link Identifier (having associated a set of metrics)
- MAC, a Media Access Control protocol (also having a set of metrics)
- IP,UDP,TCP, all layer 3 and 4 protocols having ssociated MIBs and statistics
- OSPF- and BGP-related classes representing different sets of metrics retrievable from associated MIBs
ICIM_Connection, representing communication paths between physical or logical elements, having as subclasses:
- ICIM_DeviceConnection, a path between a pair of network adapters
- ICIM_ServiceConnection, a logical network communication path between software applications (e.g. Session, Transaction)
- ICIM_LogicalLink, a logical network connection between Computer Systems (e.g. TCPConnection, VirtualCircuit, OSPFNetwork)

During the discovery process logical association relationships among created element-class instances are established, as for instance:

A ComputerSystem is "composed of" Network Adapter instances, each one having an "Underlying" MAC and being "ConnectedVia" NetworkConnection instances to other NetworkAdapter instances.
A NetworkAdapter has an "Underlying" IP ICIM_ServiceAccessPoint, which is "ConnectedVia" to an IP Network.

These relationships are built by detecting "containment" (e.g. an interface belongs to a card that is plugged into a chassis) and "adjacency" (e.g. interfaces which are hooked on the same LAN segment). Once the relationships are built, the topology of the network system is recorded in memory and will serve as basis for event correlation and root-cause analysis can be done (in the SAM) using the "codebook" correlation technique.

[edit]

Service Assurance Manager

The InCharge Service Assurance Manager (SAM), also reffered to as Global Manager, consolidates topology information and event information it receives from its underlying "domain" managers:

InCharge Service Assurance Manager Adapters
- The Trap adapter used to create notifications from SNMP traps received by the trapd daemon listening on UDP/162.
- The NetIQ AppManager adapter used for retrieving notifications from NetIQ's AppManager event database.
- The SQL Data Interface SDI adapter used for recording SAM notifications in an external Oracle or SQL Server database, according to a predefined schema.
- The XML adapter allowing the import and export of ICIM-based SAM topology information in XML format.
- The Notification adapters, allowing propagation of notifications generated by SAM as:
  - E-Mail to multiple destinations, encoding in the subject and body of the message the notification attributes
  - Records in a log file, containing the notification attributes
  - SNMP traps to multiple destinations, where the var-bindings contain the notification attributes
  - User-defined ASL scripts, that can perform arbitrary actions using received notification attributes

InCharge IP [Performance] and Availability Manager (AM/PM) instances (one per domain)
InCharge Application Services Manager instances

Each domain manager (AM/PM or other) is responsible for discovering the network topology of the domain it manages. The SAM consolidates the event information, does root-cause analysis and applies business rules (e.g. setting severities, applying escalation rules, correlating events, opening incident tickets within ticketing systems). Detailed and summary event and alarm information are displayed in the SAM Consoles (Notification log, Topology Browser, Map Console,Summary View). From these consoles, operations personnel can invoke diagnostic or corrective tools, acknowledge events or generate reports. The connectivity among the Incharge components (SAM, domain managers, adapters) goes through the Incharge Broker, which allows for encrypted communication and automatic failover schemes.

[edit]

SAM Open Integration (OI) and the Trap Adapter

The InCharge Service Assurance Manager permits development and interfacing of "adapters", through the Open Integration platform APIs. The adapters inject events they detect into the SAM, where the same business rules, correlation and consolidation apply as for events coming from the other domain managers. The Trap Adapter is such an adapter which receives SNMP traps (on UDP/162) and remaps the TRAP contents into an event format to be fed to SAM. The mapping of TRAP contents (generic/specific TRAP IDs and var-bindings) into SAM event attributes is doner through a mapping configuration whic may invoke advanced mapping scripts written in ASL language. The Trap adapter is a convenient means of propagating into SAM events generated by other monitoring systems, e.g. Integrated Research Prognosis IP Telephony Manager. It is advisable that the network elements identified as "source" (after trap attributes processing through the mapping configuration) exist in the SAM topology, either discovered or manually entered. Several instances of trap adapter can run on the same SAM, each one listening on a particular port and mapping traps with its own configuration, allowing per-domain processing of external events. The XML adapter offers a convenient means of importing and exporting SAM network topology information (using the ICIM XML external format).

[edit]

IP Availability/Performance Managers

The Availability Manager (AM) instances, one per domain, discover and monitor the network elements using ICMP ping and SNMP polling as well as by receiving and processing SNMP traps sent by network elements. The abnormal or "back-to-normal" situations detected by the AM are analyzed for root-cause then fed to the SAM as notifications, being displayed in the Notification Log console. The types of notifications are "up", "down", "unstable" (i.e. flapping), or "not responding" for systems, network adapters, cards, connections, etc. A number of standard and proprietary MIB objects are supported by the AM. Once the network elements are discovered and the network topology built, the InCharge Performance Manager (PM) would monitors specific metrics and the status of these elements by periodically querying them through SNMP polling, ICMP ping as well as by receiving and processing SNMP traps. The decision on which network elements to monitor is based on "management policies", which can be configured. Those network elements being declared in "unmanaged" status are nor monitored (e.g. by default switch access ports are not managed). Singular abnormal conditions (e.g. high utilization on a port) result in "fault" notifications whereas related faults are aggregated and reported as "exception" notifications. Several instances of AM/PM managers, also reffered to as Domain Managers, can independently run on the same server by binding to different virtual interfaces and managing each network elements in a particular IP ddressing domain. This collocation feature allows Managed Service Providers (MSP) to reduce the infrastructure costs and manage overlapped the private IP addressing domains of multiple clients, using Policy Based Routing (PBR) based on source IP address.

[edit]

SMARTS extensibility

What distinguishes SMARTS InCharge from other Network Management Systems is its extensibility features:

The Managed Object Definition Language (MODEL), a declarative language used to develop "compiled" correlation models
The Dynamic Modeling, an extension of the MODEL language, allowing run-time modification of the ICIM model
The InCharge Remote API, allowing run-time access to the ICIM instantiation representing a managed network topology, from Perl, Java and C++ programs.
The ASL scripting engine allowing user-defined action hooks to be invoked by SMARTS InCharge applications

The MODEL language allows the base ICIM model to be extended with user-defined classes to represent new types on Network Elements to manage. The "base" ICIM model, which is "compiled" into a set of SMARTS InCharge shared libraries is actually defined in MODEL. As new classes are defined by the user in MODEL scripts, they have to be run through the MODEL compiler which first translates them in C++ clases then to binary-compiled shared libraries to be loaded by SMARTS at startup. The MODEL-defined extensions to the ICIM model are "static" in the sense that one need to restart the SMARTS InCharge applications to activate them.

Technology-specific "managers" exist for SMARTS InCharge to fulfill advanced monitoring needs for:

Monitoring of MPLS networks : InCharge MPLS/VPN Manager
Monitoring of ATM and Frame Relay networks : InCharge ATM/Frame Relay Availability Manager

The Dynamic Modeling is a MODEL extension that permits extending at run-time the "base" ICIM model with new classes or add attributes to existing classes, with no need for restarting the SMARTS InCharge applications. The Dynamic Modeling ICIM extensions are defined in a MODEL-like scripting language but, rather than statically compiled and linked into the applications, the Dynamic Model compiler directly produces .ldm files that are dynamically loaded by an InCharge Manager.

The SMARTS InCharge Remote API interface, a RPC mechanism based on a client-server protocol that allows remote applications to invoke SMARTS InCharge services and manipulate objects in a SMARTS InCharge ICIM instantiation. To do this, the Client application is using the classes and methods implemented in the libraries provided with the Remote API SDK libraries, which would issue requests and synchronously waiting for responses, while doing the marshalling/demarshalling of request/response parameters into/from messages. The following basic functionalities are provided through the Remote API:

Querying, traversing and editing the topology (i.e. ICIM instantiation) as well as saving/restoring it to/from a file.
Querying, traversing and editing the ICIM model (e.g. enumerating/finding classes and properties) and class instances (e.g. setting/retrieving property values, relationships, etc)
Retrieving from the class instances values of special properties representing momentanous availability and performance indicators polled by AM/PM.
Subscribing for asynchronous event notifications from SAM, using an observer-notifier mechanism based on callbacks.
Remote invocation of programs on the SMARTS InCharge server or ICIM class operations on class instances
Invocation of Codebook correlation engine

These extension mechanisms permit development of third-party applications that complement the SMARTS InCharge capabilities for fulfilling special requirements. One such example is the Advanced Performance Grapher (APG) which adds historical perfprmance reporting and analysis capabilities to SMARTS InCharge.

[edit]

Other Performance Monitoring Tools

Other Availability, Fault and Performance management tools are being used by IS/IT organizations and Network Providers - Among these are Concord (now Computer Associates) eHealth suite, HP OpenView Network Node Manager (NNM), IBM Tivoli Suite and others. Despite the vast choise, the information below refers only to eHealth, NetScout nGenius suite and the Application Performance Monitoring tools from Compuware and Packeteer.

[edit]

Concord eHealth

Concord Communications, who bought in 2005 Aprisma Management Technologies (for the "Spectrum" fault and service management), was bought the same year by Computer Associates. The CA/Concord eHealth suite is valued by many organizations for its powerful performance reporting capabilities,for just about every aspect of network monitoring, including VOIP. The eHealth suite is primarily a network performance monitoring tool, collecting its information through SNMP (directly from devices or from RMON probes) as well as from proprietary SystemEdge and Application Response agents deployed on monitored servers. The eHealth suite also provides a VOIP deployment planning and assessment module which is using the agents and the Cisco IPSLA metrics to assess network impairments. In typical deployments eHealth does the performance monitoring and HP-OV NNM the fault monitoring and topology map.

[edit]

IBM/Micromuse Netcool

The IBM Tivoli/Netcool suite is primarily a Manager of Managers (MOM) whose core is the Netcool/OMNIbus system, which collects, archives, consolidates and presents in real-time enterprise-wide event/alarm information from various sources. The strong point of Netcool is the abondance of adapters and proves for different other Network Management Systems and Network Devices. Using these adapters and probes Netcool can import Network Topology, correlate event information and assess the business impacts of network troubles.

IBM Tivoli/Netcool home page
Tivoli Netcool/OMNIbus documentation documentation
Tivoli Netcool Resources [3]

[edit]

Netscout nGenius Performance Monitoring

NetScout Systems nGenius suite combines network monitoring, application service-level management and capacity planning in one package. The NetScout suite evolved since the acquisition in 2000 of NextPoint Networks. It provides Real Time Monitoring, Application Service Level Management and Capacity Planning. The information is gathered by SNMP from NetScout probes, NetFlow collectors, from routers and switches and other sources. The collected metrics are analyzed in realtime for pinpointing issues and stored in a database for reporting and trend analysis. Starting with version 4.5, NetScout introduced a unified Common Data Model(CDM) format (provided in the proprietary CDM Flow MIB residing on the nGenius probes) for the metrics collected by the nGenius probes.Along with CDM, the nGenius PM server supports a Common Data Export (CDE) format for easier integration with 3'rd party applications.

nGenius Instrumentation Overview [4]
Cutting Through the Complexity of MPLS Performance Monitoring [5]
RMON2 & NetScout [6]

A Newer addition to the nGenius portfolio is the ability to measure response time for networked applications, available through the Universal Response Time (URT) MIB, supported on all types of nGenius probes (WAN, ATM, LAN, POS, etc.). According to a review, the NetScout solution for Network Performance Management has some advantages compared to Compuware's Vantage family of products.

[edit]

Compuware Application Vantage and Packeteer AppVantage

The Compuware Application Vantage is a tool for monitoring application & transaction performance.

AppVantage Features [7]
Packeteer’s AppVantage [8]

[edit]

Network Change and Configuration Management (NCCM)

These are tools able to retrieve and audit configurations from network elements, to keep an inventory of Network Components with their attributes. Some tools can also automatically push configuration and firmware updates to devices and alert in case of unauthorized changes. ACcording to Gartner up to 80% of all network infrastructure failures are direct results of mis-administration and poor configuration The NCCM market leader seems still to be Alterpoint with its DeviceAuthority/NetworkAuthority suite, with a base configuration starting at US$10000. An Open Source version of the framework (ZipTie) allows for customization and adapter development. The Opsware Network Automation System (NAS) is based on the acquisition of Rendition TrueControl and benefits from a Cisco partnership. It competes with AlterPoint, Intelliden and Voyence, with a pricing starting at $20,000 for 50 nodes. AdventNet offers also the Device Expert NCCM product. A very low cost alternative to these expensive toolsets is Kiwi CatTools For server configuration auditing, the Tripwire toolset is widely used in the industry.

Network Configuration Management Software [9]
An Introduction to Network Configuration Management - Rancid, Alterpoint and other products [10]
Opsware makes good on acquisition [11]
Cisco and Opsware: Partners in data center automation [12]
AlterPoint adds regulatory compliance measures to DeviceAuthority [13]
Voyence adds virtual design tools to upgraded management software [14]
DeviceAuthority Protects Your System Configurations [15]
TripWire Enterprise Overview [16]
WinAgents HyperConf - detects configuration changes via the SYSLOG messages monitoring, records when and who accessed the device, what exactly has been changed, makes scheduled backups of all network devices and allows configuration rollbacks
SolarWinds Engineer's Toolset allows limited configuration management functionality for Cisco devices

[edit]

Retrieved from "http://www.mindtrek.dnsalias.net/components/com_mambowiki/index.php/Telecom:OSS:Commercial-NMS"

Views

Telecom:OSS:Commercial-NMS

Contents

Navigation

Related categories

About this page

Commercial Network Management tools

Infovista

Infovista architecture

Classic Architecture

Centralized architecture

VistaInsight components

VistaInsight for Networks (VIN)

VistaInsight for IP telephony

VistaInsight for IP-VPN

VistaViews

VistaView forInfoVista IP Telephony - Cisco CallManager

VistaView for MPLS Traffic Engineering

VistaView for VoIP - Cisco IPSLA

VistaView for Cisco VoIP Gateways

VistaBridge

SMARTS InCharge

ICIM Hierarchies

Service Assurance Manager

SAM Open Integration (OI) and the Trap Adapter

IP Availability/Performance Managers

SMARTS extensibility

Other Performance Monitoring Tools

Concord eHealth

IBM/Micromuse Netcool

Netscout nGenius Performance Monitoring

Compuware Application Vantage and Packeteer AppVantage

Network Change and Configuration Management (NCCM)

Other Network Management tools