Making pending configuration active in the network.
A network element that accepted a new version of configuration on its own behalf or on behalf of other network elements. Network sites are usually, but not always, synonymous with nodes.
See "Equipment Module."
To make the pending changes in the CPC database visible to all users and free the CMS (Configuration Management Services) objects for further modifications.
Configuration objects store description of the network configuration. Can be of two kinds:
Fabric elements —physical objects, such as nodes, ports, etc.
Service elements—logical objects, such as circuits and link connections between circuit.
A collection of managed entities grouped for administrative reasons. Also known as Administrative Domain, Management Domain, MD.
A software component that is responsible for a particular group of network elements.
EM (Equipment Module)
The CPC plug-in component that provides support for a specific piece of equipment from a specific vendor. It contains a CMS (Configuration Management Services) package, a client package and optionally a Network Interface. Also known as Blade.
Equipment Module Model
A set of CMS (Configuration Management Services) classes supported by a given Equipment Module. May include multiple technologies (for example, different objects in the Equipment Module model can be derived from different resource models).
Equipment Module Resource Mode
An Equipment Module-specific Resource Model. Also known as BRM (Blade-specific Resource Model).
Objects that represent the network "fabric" upon which Services are provisioned. These objects include the hardware, software and configurations that must be present before a Service can be added (ports, protocol stacks, etc.).
FTI (Flow-Through Interface)
The primary interface to CPC implemented either in Script Language or in CORBA. Allows a flow-through application to perform all Cisco Provisioning Center functions that are available through the GUI, as well as some additional functions. Enables integration of Cisco Provisioning Center with other applications, such as Order Management, etc. For more information, see the CPC Programmer's Guide.
An entity that defines a topological relationship (including available transport capacity) between two nodes in different subnetworks. Multiple links may exist between a pair of subnetworks. Also known as Logical Link.
A persistent object that stores information about the configuration (current, pending, suspended views) of a particular managed network element. It has three parts—attributes, relationships and behavior
MD (Management Domain)
An object that is changed in the context of a given transaction.
MIB (Management Information Base)
A definition of management items for a network component that can be accessed by the network manager. A MIB includes the names of objects the component contains and the type of information required for each of these objects.
NE (Network Element)
A part of the network representation. It models the configuration of the equipment using network management object models. Each Equipment Module has its own object model, but all objects in all Equipment Modules are derived from a common set of base classes.
NNI (Network-to- Network Interface) Resiliency
The NNI Resiliency functionality provides NNI gateway fail, recover, and rebalance operations that are used when links between <sub>networks fail.
A general term used to refer to a networked computer or device. Nodes in the network are connected by links.
OAF (Object Attribute File)
Text file that stores definitions of object attributes and their interrelationships.
OId (Object Identifier)
The unique identifier assigned to every Cisco Provisioning Center object. It is defined as Class:Instance where Class is the name of the class the object belongs to and Instance is a unique number within the class assigned by Cisco Provisioning Center.
A set of CMS (Configuration Management Service) classes representing a specific technology (Frame Relay, ATM, etc.). Classes in Equipment Module models are derived from the corresponding classes in resource models.
SA (Service Application)
A package of Service Objects that enables provisioning of a particular Service offering (FR, ATM, etc.). In some cases, the provisioning requires the use of several SAs in conjunction.
A low-level object that is created and modified in order to provision a Service (for example, PVC, Access Control List, etc.). Service Elements are manipulated and applied to the network by Service Objects.
Service Element Profile
An object used to store default attribute values for Service Elements. When creating or modifying a Service Element, you can supply the profile name as one of the attributes. All profiled attributes of the created/modified Service Element accept the default values stored in the profile. You can override the default values for the attributes whose mode is READWRITE.
SO (Service Object)
An object that stores the requested description of a service. There is a service object for each of the services that the provider offers. These objects are instances of the service class, which identifies the nature of the service (for example, end-to-end Frame Relay connectivity service). Service objects offer an end-user view of the components that make up that service. Related service objects are delivered in packages called Service Applications.
An object used to store default attribute values for Service Objects. When creating or modifying a Service Object, you can supply the profile name as one of the attributes. All profiled attributes of the created/modified Service Object accept the default values stored in the profile. You can override the default values for the attributes whose mode is READWRITE.
An execution thread in CPC. Changes to configuration and to service objects are made in the context of a session.
Choosing a provisioning path for a service across the managed networks. The following types of threading are available in Cisco Provisioning Center:
Automatic (default): as defined by the Threader (every Resource Model includes a Threader—a software component that calculates the optimal service path using a threading algorithm)
Manual: overrides the Threader-defined (default) path; specified manually as a sequence of IDs of links to be used in the path
Custom: a custom Java code that is invoked before the default threading algorithm
Transactions provide context for service and configuration changes. Interrelated changes are applied in the context of a single, network-wide transaction. If one of the changes fails, the entire transaction is rolled back, leaving the database in a consistent state.
UNI (User-to-Network Interface) Resiliency
The UNI Resiliency functionality provides UNI fail and recover operations that are used when a foreground logical port fails.
Process of extracting configuration data from the physical network into the Cisco Provisioning Center database. Performed in the context of an upload request.
Data that represent the configuration of a CMS (Configuration Management Services) object at a particular time. The following versions are defined:
Current: represents the actual running configuration of a network element. There is at most one current version.
Pending: represents a configuration that has been defined in the database (based on the current version), but has not been committed. There is at most one pending version.
VPN (Virtual Private Network)
A logical grouping of network devices and resources that identifies the CPC objects with a customer.
List of Abbreviations
This following list contains definitions for abbreviations and acronyms included in this document.
Asymmetric Digital Subscriber Line
Asynchronous Transfer Mode
ADSL Transceiver Unit - Central Office
ADSL Transceiver Unit - Remote
The Cisco Provisioning Center component code for the Cisco NI-1 DSLAM Equipment Module.