Chapter 14. Monitoring Multiple Services on a Multiservice Provisioning Platform Network

This chapter covers the following topics:

MSPP Fault Management

Using SNMP MIBs for Fault Management

Using TL1 for Fault Management

Using CTC for Fault Management

MSPP Performance Management

Ethernet Performance Monitoring

Using Local Craft Interface Application Versus EMS

This chapter first discusses two network management architectures in which a large enterprise or a service provider can use to monitor faults and performance levels of a Multiservice Provisioning Platform (MSPP) network. The Cisco ONS 15454, which is an MSPP, can support dense wavelength-division multiplexing (DWDM), Synchronous Optical Network (SONET), time-division multiplexing (TDM), Ethernet, and storage services. Reasons to implement a network management system can include the following:

Alarm filtering and consolidation
Event and alarm correlation

These functions ultimately help to reduce the average time it takes to troubleshoot a network problem. This is beneficial in a service provider environment when trouble tickets need to be created as quickly as possible so that a technician can be dispatched, thereby reducing the direct impact on operational costs. In addition, filtering and correlating data can help obtain meaningful performance information to track service-level agreements (SLAs) established between service providers and their customers.

This chapter introduces you to the fault-management and performance-management capabilities of the ONS 15454. It also addresses several areas that are essential in managing MSPP networks:

Simple Network Management Protocol (SNMP) Management Information Bases (MIBs), for fault management.
TL1, for fault management.
Available alarms by service type.
MSPP performance management for electrical, SONET, DWDM, Ethernet, and storage services.
Key differences in using the Local Craft Interface (Cisco Transport Controller [CTC]) versus the Element Management System (EMS).