Architects are able to model different types of clients, sites, nodes and parameter groups that all are used for the creation of ‘service types’. These service types are used by engineers and operators to quickly build networks and services based on predefined choices and standards.
The use and allocation of IP addresses can be modeled in granular detail. This is done by modelling the way supernets, IP plans and subnets are to be used. Even for every subnet, subnet plans can be defined for offsets and other design rules.
Configurations are generated by using different main-, sub- and port templates. These are made by engineers after testing the golden configs in the lab. By substituting and conditionalizing parameters, these templates can be used over and over, while generating different configs for different devices. Remarks and notes can be added to share the logic behind certain (design) choices.
Upon deploying changes to the network, netYCE can detect if changes have been made outside the system since the last change. Either an operator will be prompted or by using scenarios, an automatic process can be started.
Besides keeping track of all individual device configurations, NetYCE maintains an administration of services across multiple device configurations. In this way service deployment and decommissioning can be fully automated.
NetYCE supports both pre- and post compliancy checks for configurations. First, all configurations are generated as designed and therefore comply to the set standards. Second, netYCE periodically compares the production configurations to validate compliance and makes adjustments if needed.
Once created, config changes can be deployed directly on devices or via other systems. NetYCE can do this for both traditional (multi vendor) networking devices, virtualized devices or by using third party interfaces to virtualization platforms or SDN controllers.
Besides configurations, netYCE also supports full multi vendor (i)OS upgrades. This can be used standalone without any of the other functionalities. NetYCE detects the current OS versions and guides the operator through a process to upgrade to the desired OS versions. This can be done on a massive scale.
Scenarios are basically scripts that engineers define to determine exactly how certain changes in the network should take place. These also support variables and conditions to facilitate standard jobs or complex rollback- or migration scenarios with predefined steps.
The scheduler takes care of deploying changes in the production network and can be tuned to facilitate large scale rollouts. From hundreds to thousands a day without errors. Scheduling can be done for a specific maintenance window, a specific time or upon approval.
The platform supports a variety of other functions, such as job control, logging, reporting, monitoring to maintain full control of all processes.
The netYCE platform has an extensive REST full northbound interface that allows all operational tasks also to be initiated through an external application. By simply asking status information from netYCE or initiating jobs and commands, further automation and orchestration is possible.
NetYCE supports many integrations with Network management vendors to streamline and automate additional NMS processes. The includes CMDB’s, IP/DHCP/DNS systems and fault-, event- and performance management.
Service providers who use OSS/BSS systems for order management in combination with service catalogues, can orchestrate processes and provision networks by using the northbound interface.