Network Planning

Due to continuous requirement for bandwidth from internal and external customers of telcos IP & Transmission Networks, the network undergoes continuous changes and expansion. There are few tools or systems available track these changes in the ecosystem. Usually, the Planning team creates plans for expansion and network changes and issues them to the concerned teams (Deployment, Operation and Maintenance, and NOC) for implementation and execution offline. The CygNet Network Planning tool automates this entire process, so that it can be used by the Planning team for creating and tracking the plans. It significantly reduces costs by eliminating process inefficiencies, and minimizing errors by implementing checks and balances.

Main Features

Integrated Functions

lps

Often, large CSP networks plan certain activities for purposes of maintenance, upgradtion or expansion. These activities have an impact on customer services, backbone network capacity and on PoP links. The CygNet Planned Event Impact Analysis tool simulates the planned event and gives the CSP a picture of its impact on Service and Capacity, providing valuable inputs to the decision making process of how and when the planned activity should be carried out. A “What-if-analysis” context may be created, and one or more events of the following types initiated

  • Failure of a entire NE
  • Failure of a slot in an NE
  • Failure of an interface in an NE

The CygNet Planned Event Impact Analysis module computes the service impact analysis based on the current state of the network and indicates the impacted services - Resource Facing Service (Network Service Affecting- NSA) and Customer Facing Service (Customer Service Affecting- CSA). In a like manner, a “What-if-analysis” context may be created for a capacity impact analysis. On this “What-if” context, user can initiate one or more events of failure of a WAN interface between PoPs. In this case, the capacity impact analysis is computed, based on the current link utilization data. Multiple simultaneous What-if-Analysis at a given point of time are also possible.

IAMS - IP Address Planning

With the explosive growth in network sizes and IoT, the number of IP addresses in any IT organization, and in particular CSPs has grown enormous. Managing these manually has become impractical, in fact, impossible. CygNet-IAMS provides the IPv4/IPv6 Address Management functionality and this also goes hand-in-hand with the Service Activation component. The following are the key components of the IP Address Management System at a high level. IP Address Management General Requirements

  • IP Addresses Life Cycle Management
  • IP Address Discovery, Reconciliation and Activation
  • Reports and Views

IP Address Life Cycle Management addresses the requirements of reservation, allocation to de-allocation of IP Address space allocated against Work Order or without Work Order. This service also deals with setting expiry duration for the reserved/ allocated IP Address spaces for Services or Customers. TheLife Cycle Management service supports scanning a subnet for IP address availability and displaying available IP addresses as a report. Subnets corresponding to a given CIDR block can be created automatically. The IP Address Autodiscovery feature periodically scans the network and updates the latest status of IP address availability. Live graphical Views provide users with current status regarding allocation of IP addresses. Trends of IP address utilization, allocation based on historical data are available as graphical reports.

Summary

Feature Summary of End User Experience Management:

  • Measures the end users' experiences based on transactions
  • Deployable as an appliance-based system
  • Detect user impacting defects and anomalies
  • Missing component within transaction.
  • Pro-actively determine transaction defects, their location and status.
  • Provide the ability to create user groups.
  • Provide user usage analysis.
  • Detect and alert when user experience HTTP error codes.
  • Provide root-cause probability graphs.
  • Allow for SLA monitoring.