Cisco Active Network Abstraction Customization User Guide, 3.6.6 - Introducing the Cisco ANA Soft Properties Manager [Cisco Active Network Abstraction]

Table Of Contents

Introducing the Cisco ANA Soft Properties Manager

About the Soft Properties Manager

Soft Properties

Alarm Thresholds

Basic Concepts and Terms

Introducing the Cisco ANA Soft Properties Manager

This chapter describes the Cisco ANA Soft Properties Manager. In addition, it provides a brief explanation of terms used throughout this guide.

•About the Soft Properties Manager

•Soft Properties

•Alarm Thresholds

•Basic Concepts and Terms

Note Changes to the registry should be performed only with the support of Cisco. For details, contact the Cisco Project Manager or Cisco Account Team.

About the Soft Properties Manager

Cisco ANA provides deep autodiscovery and maintains a live model of the network. This model is based on Cisco's Device Component Modeling (DCM) architecture, in which each NE is modeled as an interconnected hierarchy of Device Components (DCs), both physical (for example, cards and ports) and logical (for example, forwarding tables and profiles). Each DC maintains a set of properties, which contain its actual data (such as status, configuration, or performance).

When interacting with northbound clients, the DCM information is translated internally into IMOs, Cisco's TMF513-based Northbound IMO, which is the public language of the Cisco ANA system with external systems.

The Cisco ANA property management framework enables you to extend (in runtime) the system's coverage and capabilities in two areas:

•Soft Properties—Extending the NE data collection and modeling by adding new properties to the DCs, and assigning them to NE MIB variables. The new soft properties are also automatically added to the Northbound IMO.

•Alarm Thresholds—Assigning various types of alarm conditions to soft properties.

All property definitions and parameters are maintained in XML metadata in the registry. To ease the definition process, Cisco ANA provides a friendly, simple-to-use GUI that guides you through the definition and testing process, and hides the underlying XML definitions.

Soft Properties

By default, Cisco ANA VNEs model a subset of the device properties, which cover the most important and commonly used properties. Cisco ANA offers the Soft Properties mechanism to enable user-configurable extension of device modeling, which can cover any unsupported MIB variable. This enables adding new monitored NE properties in runtime to the default set of supported properties.

The Soft Properties mechanism enables quick adaptation to new software upgrades and new requirements that arise during ongoing operation and deployment. It provides the field engineer with the ability to adapt the currently installed Cisco ANA software to changes in the deployed network.

Every Soft Property is implemented through a set of definitions that determine how to retrieve, parse, and display a certain MIB variable from the NE. The definition process is done through a simple GUI utility, and does not require system restart. Soft properties are retrieved from the NE using SNMP or Telnet/SSH.

For example, consider the case where the Cisco ANA system monitors the port parameters of an ATM switch, and the operator installs a new software version on the switch that is capable of reporting the bit error rate (BER) for each of the ports. Since this capability was not supported in previous software versions of the NE, the Cisco ANA VNE might not support the property. To avoid the need for a new VNE from Cisco, the Soft Property mechanism enables you to immediately support the new BER feature in the currently installed version.

Alarm Thresholds

The main positioning of Cisco ANA is as a mediation layer between the network and the operational and business support systems. As such, it abstracts the physical network and provides a generic, vendor-neutral network model, with a consistent information model and interface.

Cisco ANA also provides you with the ability to leverage its live network model for intelligent data processing within the mediation layer. This ability enables Cisco ANA to conduct advanced processing in areas such as fault correlation, root-cause analysis, impact analysis, and activation design and validation. It also enables Cisco ANA to provide processed information to the applications in the upper tiers. Finally, it enables Cisco ANA to enhance application functionality, while dramatically reducing the application's complexity and the uploaded data volumes.

Alarm thresholding is one of the major areas in which Cisco ANA can boost its northbound clients. With this mechanism, Cisco ANA constantly monitors selected properties and generates an alarm every time these properties cross a user-defined threshold or violate a condition. This eliminates the need for OSS/BSS applications to constantly upload huge amounts of data and process it. Instead, Cisco ANA filters out irrelevant data, and sends only meaningful notifications.

Basic Concepts and Terms

•Managed Element—Anything managed by the system; usually a component managed by the VNE, such as a device.

•Network Element (NE)—A user-named physical component or device existing in the network.

•Virtual Network Element (VNE)—A virtual representation of a single network element as a modeled component. VNEs all communicate with each other to present Cisco network service management applications with a single, common device abstraction for network element discovery, configuration, status collection, fault analysis, and other basic network (FCAPS) functions. VNEs can be extended to support new application functionality.

	Cisco Active Network Abstraction Customization User Guide, 3.6.6
	Introducing the Cisco ANA Soft Properties Manager
Cisco Active Network Abstraction Customization User Guide, 3.6.6 Preface Overview Cisco ANA Overview Customizing Network Element Information Using the Soft Properties Manager Introducing the Cisco ANA Soft Properties Manager Getting Started with the Soft Properties Manager Soft Property Examples Parsing Operators/Rules Alarm Threshold Triggers Regular Expressions Using the Workflow Editor to Create Task Workflows Introducing the Cisco ANA Workflow Editor Working With the Cisco ANA Workflow Editor Getting Started with the Workflow Editor Managing Workflows Customizing the Workflow Editor Managing and Deploying Configuration Changes Using the Command Builder Introducing the Command Builder Getting Started with the Command Builder Creating an ANA Macro Language Command: An Example Running Command Scripts ANA Macro Language Bean Shell Commands Using the Shell Interface Introducing the Cisco ANA Shell Interface Understanding Cisco ANA Shell Behavior Regular Expressions Cisco ANA Shell Potential Errors Working with BQL Getting Started with BQL Understanding IMO IMO Specification BQL Generic Commands Encrypted SSL Sockets Detailed BQL Errors Catalog and Examples Best Practices for Integration BQL Parsing Index	Download this chapter Introducing the Cisco ANA Soft Properties Manager Download the complete book PDF of Cisco ANA 3.6.6 Customization User Guide (PDF - 4 MB) Table Of Contents Introducing the Cisco ANA Soft Properties Manager About the Soft Properties Manager Soft Properties Alarm Thresholds Basic Concepts and Terms Introducing the Cisco ANA Soft Properties Manager This chapter describes the Cisco ANA Soft Properties Manager. In addition, it provides a brief explanation of terms used throughout this guide. •About the Soft Properties Manager •Soft Properties •Alarm Thresholds •Basic Concepts and Terms Note Changes to the registry should be performed only with the support of Cisco. For details, contact the Cisco Project Manager or Cisco Account Team. About the Soft Properties Manager Cisco ANA provides deep autodiscovery and maintains a live model of the network. This model is based on Cisco's Device Component Modeling (DCM) architecture, in which each NE is modeled as an interconnected hierarchy of Device Components (DCs), both physical (for example, cards and ports) and logical (for example, forwarding tables and profiles). Each DC maintains a set of properties, which contain its actual data (such as status, configuration, or performance). When interacting with northbound clients, the DCM information is translated internally into IMOs, Cisco's TMF513-based Northbound IMO, which is the public language of the Cisco ANA system with external systems. The Cisco ANA property management framework enables you to extend (in runtime) the system's coverage and capabilities in two areas: •Soft Properties—Extending the NE data collection and modeling by adding new properties to the DCs, and assigning them to NE MIB variables. The new soft properties are also automatically added to the Northbound IMO. •Alarm Thresholds—Assigning various types of alarm conditions to soft properties. All property definitions and parameters are maintained in XML metadata in the registry. To ease the definition process, Cisco ANA provides a friendly, simple-to-use GUI that guides you through the definition and testing process, and hides the underlying XML definitions. Soft Properties By default, Cisco ANA VNEs model a subset of the device properties, which cover the most important and commonly used properties. Cisco ANA offers the Soft Properties mechanism to enable user-configurable extension of device modeling, which can cover any unsupported MIB variable. This enables adding new monitored NE properties in runtime to the default set of supported properties. The Soft Properties mechanism enables quick adaptation to new software upgrades and new requirements that arise during ongoing operation and deployment. It provides the field engineer with the ability to adapt the currently installed Cisco ANA software to changes in the deployed network. Every Soft Property is implemented through a set of definitions that determine how to retrieve, parse, and display a certain MIB variable from the NE. The definition process is done through a simple GUI utility, and does not require system restart. Soft properties are retrieved from the NE using SNMP or Telnet/SSH. For example, consider the case where the Cisco ANA system monitors the port parameters of an ATM switch, and the operator installs a new software version on the switch that is capable of reporting the bit error rate (BER) for each of the ports. Since this capability was not supported in previous software versions of the NE, the Cisco ANA VNE might not support the property. To avoid the need for a new VNE from Cisco, the Soft Property mechanism enables you to immediately support the new BER feature in the currently installed version. Alarm Thresholds The main positioning of Cisco ANA is as a mediation layer between the network and the operational and business support systems. As such, it abstracts the physical network and provides a generic, vendor-neutral network model, with a consistent information model and interface. Cisco ANA also provides you with the ability to leverage its live network model for intelligent data processing within the mediation layer. This ability enables Cisco ANA to conduct advanced processing in areas such as fault correlation, root-cause analysis, impact analysis, and activation design and validation. It also enables Cisco ANA to provide processed information to the applications in the upper tiers. Finally, it enables Cisco ANA to enhance application functionality, while dramatically reducing the application's complexity and the uploaded data volumes. Alarm thresholding is one of the major areas in which Cisco ANA can boost its northbound clients. With this mechanism, Cisco ANA constantly monitors selected properties and generates an alarm every time these properties cross a user-defined threshold or violate a condition. This eliminates the need for OSS/BSS applications to constantly upload huge amounts of data and process it. Instead, Cisco ANA filters out irrelevant data, and sends only meaningful notifications. Basic Concepts and Terms •Managed Element—Anything managed by the system; usually a component managed by the VNE, such as a device. •Network Element (NE)—A user-named physical component or device existing in the network. •Virtual Network Element (VNE)—A virtual representation of a single network element as a modeled component. VNEs all communicate with each other to present Cisco network service management applications with a single, common device abstraction for network element discovery, configuration, status collection, fault analysis, and other basic network (FCAPS) functions. VNEs can be extended to support new application functionality.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.