How it works
Managing heterogeneous networks in modern times has become a very complex task. Different services often are provided by highly specialized hardware running various kinds of operating systems.
Also, the types of services a network needs to provide have changed. Nowadays, networks do not just have to offer simple connectivity but advanced services, like VoIP, streaming media or VLAN and VPN services. All of these services must be configured in a consistent way on the corresponding devices. As the network is constantly evolving – services and devices are changed, added or removed – keeping everything up to date and consistent is a very hard task.
In addition, by providing extended features, network components are more prone to attack and abuse, adding further burden on the network operator. He now needs to check for security announcements published by the network component vendors. The increased requirements and the inherent complexity have led to different, separate (software) solutions, each dealing with a single problem aspect:
A major issue with these systems is that a lot of manual work is necessary to maintain all these systems. Typically, sooner or later, the documentation in the NCM database does neither match the service definitions in the provisioning system nor the actual configuration in the network.
StableNet®’s Reconciliation feature fills this gap.
Automated Service Delivery
Service Activation with StableNet® enables you to automate provisioning of complex services in a multi-vendor environment. As StableNet® integrates Service Activation, Service Monitoring and Service Reporting on a single platform, you can automate your entire OSS process by receipt of service reporting orders - a true zero touch flow-through provisioning.
StableNet® Service Activation is based on so-called Jobs. Each Job can contain an arbitrary complex provisioning logic for services such as MPLS VPN. This promotes business effectiveness while still being extremely flexible. Jobs abstract business logic in XML templates, which contain all knowledge to provision certain services on a device. Jobs interact with elements via SSH, Telnet, TL1, Netconf (RFC 4741, 4742) or similar interfaces at runtime.
Provisioning complex service like this MPLS VPN becomes simple and efficient
Bulk Device Configuration
With the bulk device configuration, StableNet® provides a powerful tool to roll out configuration changes on a large number of device efficiently and swiftly. For example the configuration for a new/changed COS policy can be deployed on 1000 devices within minutes while still considering the different vendors and various firmware versions at the same time. Devices that are unavailable during the provisioning run, can be automatically re-provisioned, either on a schedule or on demand.
An easy results dialog makes bulk provisioning simple
StableNet already is aware of the current configuration on the network. How to use Backup Jobs to read a device’s configuration.
The main task for the reconciliation engine is checking the configuration for the presence or absence of certain configuration commands. In StableNet, such a set of configuration commands is called Configuration Snippets. Typically, they constitute a functional unit, like the configuration of a certain feature.
They optionally can use information read from Service Provisioning and Inventory Databases using DB-Variables. When running some kind of policy check job, the device’s configuration is checked against these Configuration Snippets. For custom and even more complex checks, it is also possible to write Policy Check scripts using the Perl programming language. Last but not least, the Reconciliation engine supports Vulnerability checks on the network. Security announcements are defined once in StableNet and automatically checked against the whole network.
All these checks produce Violations or compliant Check Results similar to measurement data. It can be displayed and analyzed in StableNet®’s Group Analyser and Policy Check Analyser.
|Last Updated on Thursday, 28 June 2012 14:02|
Deep Fibre, FTTx
|Sitemap | Disclaimer | Privacy|
|Copyright 2003 - 2012 Infosim GmbH & Co. KG|