Platform for Design Driven Networking

NetYCE process control functions

The netYCE platform provides the following functions to ensure full design driven control throughout all network change processes:

Modeling

Architects and designers use the platform’s unique modeling capabilities to translate detailed network- & service designs into models. Also processes can be modeled with permissions and responsibilities based on user roles.

Build abstraction

Upon execution of the designed models and processes or by importing existing network information into the models, a vendor agnostic abstraction of the network and all services is created in the database. This segregation between an abstract and vendor specific network in one application is extremely powerful for migrations or mixing and replacing vendors seamlessly.

Create configurations ‘as designed’

Using smart templates, vendor specific configurations are generated, as designed and on the fly. This is done by using an engineer’s ‘golden configs’ and by substituting all parameters with the ones from the abstract network by means of (sub) templates. By using conditionals, different configurations are created automatically with only a limited number of smart templates.

Deploy changes

Once configurations and changes are created, these can be scheduled for activation in the production network. Using scenarios, engineers can define precisely how activation in the operational network should be implemented. Whether this is a standard job, an automatic rollback or a complex migration scenario, these can all be ‘designed once and used many’ by others in a standardized way.

Manage configurations

Configuration management is crucial to keep in sync with changes in the production network. On a job by job basis, individual configurations in the production network can be compared with the scheduled versions to detect differences since the last change. Combined with scenarios, engineers can define exactly how these situations should be handled in a pre-defined way. Also, on a periodic basis all production configurations can be retrieved from the network to ensure compliancy and control.

Operate

NetYCE supports a wide variety of functions for operations staff, such as generating and retrieving configs, ping nodes, scheduling changes, resolve differences or perform OS upgrades. Also troubleshooting is made easy as netYCE has an explicit understanding of all the topology, services and configurations. Without touching the production network investigations can first be done in netYCE database. Consequently, less incidents due to configuration errors occur, leading to a more stable network with more time available for engineers and operators.

Integrate

With all network information explicitly available in netYCE database, integrations can easily be realized with external systems. Examples are CMDB’s, OSS/BSS-, NMS-, IPAM- and Orchestration systems. Integrations can either be done via the netYCE database of through the northbound interface. In this way processes can be further optimized and automated.

Orchestrate

Once modeled and engineered in netYCE, all actions can also be initiated by an external system through the northbound interface. These are the same tasks that an operator can perform via his user interface.

Some examples are: integration with an orchestration system that provisions virtual servers, where netYCE automatically assigns IP addresses, VLAN’ numbers and activates the switch ports. Or provide a self service portal for helpdesk people and end users to perform certain tasks themselves. Another example is End to End automation from order initiation to fulfillment and activation whereby netYCE integrates with OSS/BSS systems. Finally, netYCE can also be used as a bridge between systems, without touching the network, to update e.g. external IP/DHCP/DNS systems.

Maintain

NetYCE provides an extensive set of functions to maintain networks throughout their complete Life Cycle. Some of these functions are (i)OS upgrades, network migrations, consolidations, deactivation of services or switching from hardware vendor. It also has a full network inventory that allows business owners and service managers to have an accurate overview how many devices or services are actually deployed and minimize maintenance cost for vendors or integrators. This is very useful when charging charge customers or departments.

Platform support

In addition to the process functions, the platform supports the following functionalities:

Role based access

NetYCE supports a granular role based access structure. Roles vary from administrator, modeller, designer, engineer, operator or persons with 'read only' privileges. These roles can furthermore be assigned to groups or by type of network, architecture or customer.

Process enforcement

Processes can be enforced in different ways. First, through models, templates and scenarios. Second, by means of roles as defined by the architect or functional owner of the process. Based on each user role, specific access is given in the application the desired way of working.

Knowledge management

All network information is stored in netYCE, ranging from design specific matters stored in models, templates and scenarios to specific operational information stored in configurations, log files and change history.

Inventory

NetYCE keeps a full inventory of the entire network, ranging from what devices are deployed where, for which customer, with what services and with accurate registration of all parameters such as ip addresses, vlan numbers, service details, profiles and more.

Multi vendor

Multi vendor capabilities are supported in two ways. First, through modeling, network abstractions are created that can be translated into configurations for almost any type of device and vendor. Second, for activation purposes, netYCE supports a variety of vendor modules, ranging from Cisco, Juniper, HP, Avaya, Fortinet a.o., with new vendor modules to be realized in 5 days or less.

Multi tenancy

Multi tenancy is the ability to organize different networks, architectures and customers in one group (tenant) for different users. This is extremely powerful for (managed) service providers who want to support multiple customers with different services from one platform.