Upload network topology

This section describes steps for importing the network topology from an excel sheet. Only one network can be imported at a time. Following are the steps to import network topology:

1. To upload a new network topology, click on Add New Network button which is at top-right corner; a new form will appear.

   

2. Following are the form parameters:
   • Name of the Network: Allows user to provide name to the network.
   • Description of the Network: Allows user to add a small description of the network.
   • Network Data in Excel File: Allows user to import network topology using excel file. Only Microsoft Excel document with file extension .xlsx is supported. Click on Browse button and browse into your system, select the input excel sheet to upload the network topology. A sample sheet is available in the documentation tab.
3. Each excel file should have three sheets. Following should be the structure of the Excel File:
   • Sheet one with name Nodes
   • Sheet two with name Topology
   • Sheet three with name Services

     NOTE: Any sheet with any other name will not be processed. Make sure all three sheets are present in the input excel file. Do not use: "_", "-" and " " in node and service names. Please add simple text as node and service names.

   1. Nodes sheet: Lists all the nodes and their respective design criteria within the network. Example is shown in figure.

      

   • Node Name: Provide simple and unique alphanumeric name.
   • Node Type: Provide one of the supported node types such as ROADM, FOADM, GTN and ILA.
   • Node Design: Provide one of the abbreviations for the node design: A for Directional, D for Directionless, CD for Colorless Directionless, CDC for Colorless-Directionless-Contentionless for ROADM as Node Type. For Node Type FOADM, Node design should also be FOADM( FOADM for Fixed-Optical-Add-Drop-Multiplexer). Node Type and Node design are same for GTN and ILA.

     NOTE: Node Name, Node Type, and Node Design are mandatory fields.

   • Attenuation: Provide attenuation if a glass through node is given (Node type and Node design is GTN for glass through node).

     NOTE: All the parameters can be overwritten by the application, if user selects the wrong type of node.

     If more than 8 lambdas are originating from a node, then the node can be considered as ROADM node with directionless solution.

   • Degree: Provide node degree if the node type is FOADM or ROADM. The degrees supported for FOADM is 1 and for ROADM are 2,4 or 8. If degree is left blank, tool will automatically decide the degree based on the number of links.
   • Exclusion: Provide I (Include) or E(Exclude). By default tool takes I (Include).
   1. Topology sheet: Creates or describes the network in the form of links or connections between the nodes listed in the Nodes sheet. Example is shown in figure.

      

   • Source: Provide source node name, that is the node from where service is originating. DWDM services are carried over two fibers and therefore bidirectional. For downstream, traffic source node will be the node where the lambda will be originating. For upstream, traffic source node will be the node where the lambda will be terminating.
   • Destination: Provide destination node name, that is the node where service should terminate.
   • Distance: Provide distance between two nodes in kilometers.
   • Link: Link name must be unique between two nodes. It is used to identify multiple links between two nodes. Unique name can be given to each link also.
   • Fiber Type: G.652, G.653, G.654, G.655-LEAF and G.655-TW types are supported.

     NOTE: Source, Destination, Distance, Link, and Fiber Type are mandatory fields.

   • Raman Amplifier: Provide Raman amplifier. If Raman amplifier has to be placed on a particular link, then provide enable, else provide disable.
   • Connectors: Provide number of connectors in a link.
   • Splices: Provide number of splices in a link.
   • Uplink Loss (in dB): Measured loss in dB.
   • Downlink Loss (in dB): Measured in dB.

     NOTE: If uplink and downlink losses are mentioned, connectors and splices are ignored.

   • Loss (in dB): Measured in dB.
   • SRLG Info: SRLG stands for Shared Risk Link Group and this information identifies the set of links or edges that share the same conduit.

     NOTE: Comma separated list of all links which share the same conduit should be provided. Format should <Source Node>-<Destination Node>-<Link Name>.

   • Exclusion Type: Provide I (Include) or E (Exclude). By default, tool takes I (Include).
   • No of Spans: Provide number of spans.
   1. Services sheet: Contains list of all services flowing within the network.
   • Source: Provide source node name, that is, the node from where service is originating. DWDM services are carried over two fibers and therefore bidirectional. For downstream traffic source node will be the node where the lambda will be originating. For upstream traffic source node will be the node where the lambda will be terminating.
   • Destination: Provide destination node name, that is the node where service should terminate.
   • Service ID: Provide unique alphanumeric Service ID for each service, for example, S1, AB, etc.
   • Quantity: An integer value to duplicate a particular service.
   • Line Side Traffic: Line side traffic can be 10,100-600 in steps of 100. Auto can be given as input.

     NOTE: For Line Side Traffic to be auto, then input for Modulation should be also be auto.

     Estimate line rate and modulation type check box must be enabled.

   • Client Side Traffic: User can add multiple client types in the form m*datatype1+n*datatype2. For example, 10x10GE+2x100GE.

     

   • Protection: Following Protection modes are supported:

     - 1: This stands for work path which would have been provisioned, where only one path is available for the service to flow, if the work path fails then another protection or restoration path will not be provided.

     - 1+1: This stands for both work and protected path which would have been provisioned. If work path fails, then the service which is flowing through work path is routed to protected path. If the protected path fails, then another path will not be provided.

     NOTE: 1+1+1+1, 1+1, 1+R, 1+1+R, 1+1+F are also available.

   • Protection Design: Available options are DWDM, WSON, and NA.

     

   • Service Protection: Refer to the above table for the available options. It also supports mix and match of the service protection types.

NOTE: Refer to the above table for Path Protection Type, Protection Design and Service Protection Type compatibility.

• Modulation: Supports for OOK, QPSK, 8QAM, 16QAM, 32QAM, 64QAM modulation types. Refer to the following table for supported modulation and linerate.

  

  NOTE: Estimate Linerate and Modulation should be enabled in GUI for Auto.

  All the above fields, under Services Sheet are mandatory.

• Wavelength: If not known, add NA, or leave it blank. Wavelength number must be Tejas supported lambda number.
• Disjoint Services: Comma separated list of service IDs which current service ID should not share a common link, edge, span.
• Paths: There are three ways to add paths.

  - Allow the tool to populate the paths. If user want the application to use calculated paths, then the column can be left empty in the excel sheet, application will calculate.

  - The second way is to assign paths that are disjoint. The tool does not accept paths that have overlapping links. The links should be as disjoint as possible from start to end.

  - The third is applicable when there are protected services.

  For e.g: NODE0====NODE1====NODE2 Two links each between NODE0 and NODE2.

  The path cell  will look like this:W:NODE0-NODE1-A3;NODE1-NODE2-A4,P:NODE0-NODE1-A1;NODE1-NODE2-A2

  Where W stands for work and P stands for protect.

  NOTE: Format of the path should be <Path Name>: NODE1- NODE2-L1;NODE2-NODE3-L1. Only through Excel file user can add paths.

  Please follow the column rules while adding data, else APT application cannot provide the expected output.

  The tool sometimes decides on a path that does not exactly match with the provided path but is parallel to the one given.

• FEC type: Provide forward error correction. Following are the forward error correction scheme:

  NOTE: Quantity is mandatory field.

  - GFEC (generic forward error correction), it is used to reduce the actual threshold value in 10G networks. The OSNR threshold is reduced to 17dB from 23dB for 10G lambdas with GFEC.

  - EFEC (enhanced forward error correction), it is used to reduce the actual threshold value in 10G networks.The OSNR threshold is reduced to 14dB from 23dB for 10G lambdas with EFEC.

  - SDFEC (soft decision forward error correction), it is used to reduce the OSNR threshold value for networks with linerates of 100G and above. The exact reduction of OSNR threshold depends on the linerate and modulation.

• Regeneration: Enable or Disable according to user requirements.
• Maximum Regenerations: Provide Maximum number of Regenerations (Integer Value).
• Regen Nodes: Provide regen nodes.

NOTE: Format of the path should be <Path Name>: NODE1;NODE2.

• Destination list: Provide Destination list if required. If a service has single source and multiple destinations for protection then they can be given separated by commas.

  NOTE: It depends on protection as follows:

  1 - one destination has to be given

  1+1 - two destinations have to be given

  1+1+1 - three destinations have to be given

  If destination list is left empty, then the destination for work and protect paths is considered to be the same.

• SRLG: Provide SRLG.

4. Fill the form and click on Submit to save the topology.