Skip Headers
Oracle® Communications Network Intelligence User's Guide
Release 7.2.2

E36059-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

7 Using Trails

This section describes trails in Oracle Communications Network Intelligence, and other entities associated with trails; that is: trail groups, trail definitions, trail holders, and trail holder definitions.

Creating a Trail Definition

Before creating a trail, you must first create a trail definition, which is a blueprint for creating a trail.

To create a trail definition:

  1. Click Trail on the context toolbar.

  2. Click the Create icon to display the following options:

    • Trail Configuration Wizard

    • New Trail Definition

    • New Trail Holder Definition

  3. Select New Trail Definition to display the New Trail Definition window.

  4. Configure the trail definition using the following values:

    • Name: The name of the new trail definition. The name must be unique.

    • Structured: Select whether to create a structured, or an unstructured trail. A structured trail has child channels or time slots that carry other trails, and an unstructured trail does not.

      If you select an unstructured trail, you must add enabled trail definitions in a later step.

      The default is unstructured.

    • Capacity Required: Select the capacity required from the list of available capacity objects. This field determines the capacity that is demanded during forecasting of service demands that use this trail definition, and the capacity that is consumed when a trail is created based on this trail definition. This is a mandatory field for all trail definitions.

    • Capacity Enabled: This field is only available for unstructured trail definitions. It determines the capacity that may be consumed by child trails during forecasting of service demands. This is a mandatory field for unstructured trail definitions.

    • Trail Group: Select the group to which the trail associated with this trail definition belongs.

    • Trail Definition Group: Select the group to which this trail definition belongs. This step is optional.

    • Position: Select the position which this trail definition occupies. This field applies only to unstructured trails.

    • Consumption Threshold %: Set the threshold for the capacity that is consumed when a trail is created based on this trail definition.

    • Use Parent Term. Ports: Select to use parent termination ports.

  5. To select enabled trail definitions for an unstructured trail, click Add to display the Enabled Trail Definition Search window.

  6. Click Save.

Assigning Trail Definitions to Enabling Trail Holder Definitions

Having created a trail definition, you must specify what trail holder definitions can carry it. This ensures that higher bandwidth trail definitions with trail holder definition children are made available for path analysis routing. To assign a trail definition to enabling trail holder definitions, select the relevant trail holder definitions, and edit them.

To assign a trail definition:

  1. Click Trail on the context toolbar.

  2. Click Trail Holder Definition on the top of the Trails panel.

  3. Select the required trail holder definition to display the Trail Holder Definition window.

  4. Click Edit.

  5. In the Enabled Trail Definitions section, click Add to display a list of available trail definitions.

  6. Select the required trail definitions, and click Save.

Having assigned the trail definitions to an enabling trail holder definition, any parent trail definition that has a signal structure containing this trail holder definition is now available to carry circuits of the type defined in the trail holder definition.

Related Topics

Routing Trails

Working with the Trails Tree Browser

The trails tree browser displays:

  • All trails in Network Intelligence ordered in hierarchical folders by trail type, trail sub-type, and trail bandwidth.

  • All trail definitions in Network Intelligence, ordered alphabetically.

  • All trail holder definitions in Network Intelligence, ordered alphabetically.

Working with Trail Views

Trail views are a series of different sub-views of a network trail.

A trail offers the following views:

  • Payload View

  • Parent Hierarchy View

  • Equipment Traversal View

  • Geographical Map View

  • Hop by Hop Routing Report

  • Child Trails

  • Customer Trails View

  • Trail Costs

Using the Core (Trail) View

Double-click the trail to display the core view. This view defines the trail in terms of the following:

  • Name: The name of the trail.

  • Service: The supported service; for example: ATM, IP Business, Path.

  • Trail Group: The supported trail group; for example: PDH Trail, SDH Path.

  • Trail Definitions: The supported trail definition; for example: 2MB, E1.

  • Capacity: The supported capacity; for example: 10 MB, 1 GB.

  • Customer: The supported customer.

  • A Site: The name of the originating site.

  • Z Site: The name of the terminating site.

  • A Equipment: The name of the originating equipment.

  • Z Equipment: The name of the terminating equipment.

  • A Physical Port: The A physical port.

  • Z Physical Port: The Z physical port.

  • A Logical Port: The A logical port (if logical ports are created in the model; not all trails require logical ports).

  • Z Logical Port: The Z logical port (if logical ports are created in the model; not all trails require logical ports).

  • Status: The trail status; for example: Ceased, Faulty, Free, In Service, ONI Planned (where ONI signifies Oracle Network Intelligence).

  • Direction: The trail direction; for example: BothWays, Incoming, Outgoing.

  • Protection: The protection status for the trail; for example: Protected, Protection, Unprotected.

  • Protecting Trail: The protecting trail for this trail.

  • Presentation: The presentation type for the service demand: for example: CHS, CSH, ISH, ISI, or Normal.

  • Route: The name of the route.

  • Routed Status: The routed status; for example: Routed, Partially Routed, Unrouted.

  • SequenceNo: The sequence number of the trail.

  • Supplier: The supported supplier; for example: Alcatel, Ericsson.

  • Media Type: The supported media type; for example: Coax, Dark Fibre, Fibre.

  • External Source: The inventory source.

  • InService Date: The date on which the trail came into service.

  • OutService Date: The date on which the trail is due to be exhausted.

To further refine the trail search, use the Searchable Site Fields, or the external attribute fields.

Click Search to return the required entities, or click Reset to clear all the search fields.

Note:

In Edit mode, using the enabled search buttons '...', you can edit the start and end (A and Z) Site, Equipment, Port, and Logical Port values. Do not do this if the trail has been loaded from a master inventory source.

Tip:

Leaving all search fields blank returns all network entities of that particular type.

Editing the Trail Definition

To edit the trail definition:

  1. Click Edit to modify the trail details in the core view.

  2. Modify the details, as outlined in "Using the Core (Trail) View".

  3. Click Save.

Deleting a Trail

To delete a trail:

  1. Click Delete in the core view.

  2. Confirm the deletion.

The trail is no longer displayed in the GUI.

Viewing the Protection and Protected Trail

From the Trail Search Results view, you can view the protection or protected trail for the selected trail:

  • If the protection status for a trail is Protected, you can right-click the row and select View Protection to view the protection trail for the selected trail.

  • If the protection status for a trail is Protection, you can right-click the row and select View Protected to view the protected trail for the selected trail.

See Network Intelligence Concepts for more information about trail protection.

See "Protecting an Existing Trail" for more information about protecting existing trails.

Using the Payload View

This view presents the trail's payload timeslots/channels graphically. This view only applies to trails that are structured, that is, they have child channels or time slots that carry other trails. The view displays both timeslot and trail entities. Timeslot entities are colored mustard and trail entities are colored blue.

Viewing a Trail

Double-click any trail to see a full trail view.

All trails are represented graphically depicting the service that the trail is carrying.

Editing Object Relationships in the Payload View

The payload view has object relationship editing capabilities to repair incorrect objects relationships, or to capture missing relationships when Network Intelligence is being used as a master data source.

In most cases, the trail hierarchical object model is maintained in an inventory system and is loaded into Network Intelligence in a correct state, so there is no need for object relationship editing. However, to edit the object relationships, you can do the following:

  • Add a trail to a trail holder

  • Remove a trail from a trail holder

  • Move a trail from one trail holder to another trail holder

Adding a Trail to a Structured Trail

To add a trail to a structured trail, you must add it to an existing trail holder of that structured trail:

  1. Open the Hierarchy View for a structured trail.

  2. Right-click the required trail holder.

  3. Select Add.

    The Trail Search window is displayed. Use this to find the trail you want to add.

  4. Select the trail and close the window.

    The trail is displayed as a child of the trail holder.

  5. To commit the changes to the database, see "Saving Configuration Results".

Adding a Trail to an Unstructured Trail

To add a trail to an unstructured parent trail, you must add it directly to the trail itself. This results in a trail holder and child trail being added to the parent:

  1. Open the Payload View for a trail.

  2. Right-click the trail.

  3. Select Add.

    The Trail Search window is displayed. Use this to find the trail.

  4. Select the trail.

    A trail holder and child trail are added to the unstructured trail and are modeled in the payload view.

    The capacity required for parent trail holders is the child trail capacity reduced by the service overbooking rate specified by the service demand policy. This capacity is of type Trail Holder Capacity. If this capacity does not exist within Network Intelligence, it is created dynamically, and added as a trail holder capacity type with a prefix of UC- (for unstructured capacity). All such trail holder capacity types are grouped under the trail holder folder in the capacity tree browser.

    See "Using Capacities" for more information.

  5. To commit the changes to the database, see "Saving Configuration Results".

Removing a Trail from a Trail Holder

To remove a trail from a trail holder on a structured trail:

  1. Open the Payload View for a trail.

  2. Right-click the trail to remove from a trail holder.

  3. Select Cut to remove the trail.

    After a few moments, the color of the trail changes to orange, and the object icon changes to a scissors.

  4. To commit the changes to the database, see "Saving Configuration Results".

Moving a Trail between Trail Holders

To move a trail from one trail holder on a structured trail to another:

  1. Open the Payload View for a trail.

  2. Right-click the trail to move.

  3. Select Cut to remove the trail.

    After a few moments, the color of the trail changes to orange, and the object icon changes to a scissors.

  4. Select Paste to add the trail to another trail holder. The trail reverts to its normal color.

  5. To commit the changes to the database, see "Saving Configuration Results".

Removing a Trail Holder from an Unstructured Trail

To remove a trail holder from an unstructured trail:

  1. Open the Payload View for a trail.

  2. Right-click the trail holder to remove.

  3. Select Delete to remove the trail.

    After a few moments, the color of the trail holder changes to red, and the object icon changes to a trashcan.

  4. To commit the changes to the database, see "Saving Configuration Results".

    Note:

    After deleting the trail holder, it is removed from the database.

About the Traversal View

The traversal views display a trail's routed path across the network in terms of the equipment used, and the different trails that transport it.

About the Parent Hierarchy View

This view displays both graphical and textual parent-child hierarchical representations of the trail's equipment linked by a parent trail.

About the Graphical View

Click the Graphic tab to display the graphical view. The graphical view displays the parent equipment nodes for the trail, and parent links and timeslots of the parent's links (if the trails are channelized). The graphical view contains powerful editing capability to allow the removal or insertion of trail parents. You can add a parent link to a trail. The color-coding of trails in the parent hierarchy view is the same as that used in the equipment traversal view. See "About the Equipment Traversal View" for more information.

Sometimes parent links timeslots for a trail are loaded into Network Intelligence in the wrong order, such that the end-to-end trail does not align correctly as it proceeds from site to site. To fix this problem, the parent links must be correctly ordered 1, 2, and so on. You can change the sequence number of a trail's timeslot.

To add a parent link to a trail:

  1. Right-click the trail to which you want to add a parent link.

  2. Select Add.

    The Add Parent Trail window is displayed.

  3. Click Select Parent Trail to search for the parent trail to add.

  4. Select a parent trail.

  5. Click Timeslot and select a timeslot. If the selected parent trail is unstructured, then the timeslot selection is disabled as a dynamic trail holder is created.

  6. Click Apply.

    The parent link is added to the trail.

  7. Right-click anywhere in the view panel and select Save Configuration Changes.

  8. Click OK to confirm the changes.

To change the sequence number of a trail timeslot:

  1. Select the timeslot object.

  2. Right-click the timeslot object and select Update.

    The Update Timeslot window is displayed. The window displays the current timeslot sequence number and enables a new sequence number to be entered.

  3. Enter the new sequence number.

  4. Click Apply.

  5. Right-click anywhere in the view panel and select Save Configuration Changes.

  6. Click OK to confirm the changes.

To remove a parent trail holder from a trail:

  1. Select the timeslot object.

  2. Right-click the timeslot object and select Cut.

    After a few moments, the color of the timeslot and its tree changes to orange, and the object icon for the timeslot and its tree changes to a scissors.

  3. Right-click anywhere in the view panel and select Save Configuration Changes.

  4. Click OK to confirm the changes.

About the Textual View

Click the Text tab to display the textual view, defined in terms of:

  • Trail: the name of the parent trail.

  • Site: the name of the site on which the node carrying the trail originates.

  • Node: the name of the node on which the trail originates.

  • Platform: the trail technology; for example: SDH.

  • Node Type: the type of the node.

  • Node Definition: the definition of the node.

  • Shelf Name: the name of the shelf bearing the slot on which the card is located.

  • Slot Name: the name of the slot on the shelf.

  • Card Name: the name of the card on the slot.

  • Port Name: the name of the port on the card.

  • Port Number: the sequence number of the port on card.

Adding a Trail Holder and Parent Trail to a Trail

To add a trail holder and parent trail to a trail:

  1. Open the parent hierarchy view for a trail.

  2. Right-click the trail, and select Add to display the Add Parent Circuit dialog box.

  3. Select a parent trail and timeslot to apply to the parent circuit.

    For unstructured trails, timeslot selection is grayed out.

  4. Click Apply to model the new entities in the parent hierarchy view.

Removing a Trail from a Trail Holder

To remove a trail from a trail holder:

  1. Open the Hierarchy View for a trail.

  2. Right-click the trail to remove from a trail holder.

  3. Select Cut to remove the trail.

    After a few moments, the color of the trail changes to orange, and the object icon changes to a scissors.

  4. To commit the changes to the database, see "Saving Configuration Results".

Removing the Parent Trail Holder of an Unstructured Trail

To remove the parent trail holder of an unstructured trail:

  1. Open the Hierarchy View for a trail.

  2. Right-click the trail to remove the parent trail holder.

  3. Select Delete to remove the trail holder.

    After a few moments, the color of the trail holder changes to red, and the object icon changes to a trashcan.

  4. To commit the changes to the database, see "Saving Configuration Results".

    Note:

    After deleting the trail holder, it is removed from the database.

Moving a Trail between Trail Holders

To move a trail from one trail holder to another:

  1. Open the Hierarchy View for a trail.

  2. Right-click the trail to move.

  3. Select Cut to remove the trail.

    After a few moments, the color of the trail changes to orange, and the object icon changes to a scissors.

  4. Select Paste to add the trail to another trail holder. The trail reverts to its normal color.

  5. To commit the changes to the database, see "Saving Configuration Results".

About the Equipment Traversal View

This view displays both graphical and textual A-to-Z network traversal representations of the trail's equipment linked by a parent trail.

About the Graphical View

Click the Graphic tab to display a graphical A-to-Z network traversal representation of the trail's equipment linked by a parent trail. A symbol is used to denote that a parent path or parent link is unrouted.

Figure 7-1 shows part of an equipment traversal view.

Figure 7-1 Network Traversal Representation of Trail's Equipment

Description of Figure 7-1 follows
Description of "Figure 7-1 Network Traversal Representation of Trail's Equipment"

Where:

km length is a cumulation of all trail lengths, in kilometers.

Total Hops is made up of:

  • Inter hops, that is, the number of hops between sites; for example: underground cables between cities

  • Intra hops, that is, the number of hops within a site; for example: cables between racks in a building

Double-click to view any GUI element; for example: the LKY site icon or the STM-16 1 equipment icon. Dashed, vertical lines divide the sites; for example: LKY from CBR. Horizontal lines of various colors depict different trail types:

  • Path: Light-blue

  • Link: Mid-blue

  • Trail: Lilac

  • Timeslot: Yellow

The colors used to represent different trail types in the equipment traversal view are also displayed in the parent hierarchy view. See "About the Parent Hierarchy View".

About the Text View

Click the Text tab to display to display a textual A-to-Z network traversal representation of the trail's equipment linked by a parent trail.

About the Geographical Map View

The Geographical Map view displays the path routing of the trail in terms of nodes and links, with the nodes placed according to geographical location coordinates.

To display the geographical map view for a trail, click Geographical Map View in the View panel.

The nodes that are displayed in the map view are equipment nodes. When multiple equipment displayed in the view belong to the same site, they can appear on top of each other because they have the same location coordinates. The view is more useful for showing nodes in physically separate sites connected by links.

Double-click a node object to display the equipment's detail view. Double-click a link object to display the links detail view.

Viewing Link Layers

The links displayed in the map by default contain both link (transport) and path (bearer) type links.

To view the link or path layer:

  1. Right-click in the map view to display the map menu.

  2. Select Link Layers, and select one of the views:

    • Transport (link)

    • Bearer (path)

Note:

The Geographical Map View is displayed only if you have Oracle Fusion Middleware MapViewer (MapViewer) configured and running in the application server.

See Network Intelligence Installation Guide for further information about licensing and installing MapViewer.

About the Hop by Hop Routing View

The Hop by Hop Routing view depicts, in tabular format, all individual hops on the trail for an end to end circuit. The hops displayed can be inter hops, that is, hops between sites; for example: underground cables between cities, or intra hops, that is, hops within a site; for example: cables between racks in a building.

So, for example, on a VC-12 circuit consisting of six individual trails, the Hop by Hop Routing view displays a table listing each hop defined by:

  • Ingress Equipment: The originating equipment for the trail making up the hop.

  • Ingress Port: The originating port for the trail making up the hop.

  • Ingress Logical Port: The originating logical port for the trail making up the hop.

  • Trail Name: The name of the trail making up the hop; for more information on trail naming conventions, see "Generating a Trail Name".

  • Channel Position: The sequence number of the timeslot or channel, position held by the trail.

  • Egress Equipment: The terminating equipment for the trail making up the hop.

  • Egress Port: The terminating port for the trail making up the hop.

  • Egress Logical Port: The terminating logical port for the trail making up the hop.

Double-click a trail to display its details. Save the data in the table in a variety of formats: HTML, CSV, or Microsoft Excel. Select which columns to display. However, unlike most table views, you cannot sort the trails by column, or otherwise alter the fixed trail sequence shown, in the Hop by Hop Report view.

Viewing an Equipment

Double-click any equipment icon or name to see a full equipment view.

Double-click any site icon or name to see a full site view.

Viewing a Trail

Double-click any trail to see a full trail view.

Generating a Trail Name

On a trail view, you can automatically generate a name for the trail as follows:

  1. Click Edit on the trail view to enable configuration of the trail.

  2. Click Generate Name beside the Name field to create a name for the trail. There are two possible results, depending on the type of trail:

    • If the trail is between sites, Network Intelligence concatenates the names of the A Site and Z Site, the trail capacity, and the next available sequence number for the trail, to create a name of the form: ASite-ZSite/Capacity/001.

    • If the trail is between equipment, Network Intelligence concatenates the names of the A Equipment and Z Equipment, the trail capacity, and the next available sequence number for the trail, to create a name of the form: AEquipment-ZEquipment/Capacity/001.

    The sequence number allocated in this name is the next available to a trail, and does not match the sequence number listed in the SequenceNo field in the trail view.

    If you modify any of the elements that comprise the trail name, for example, you change the A Site, Z Site, or capacity, click Generate Name again to update the name to include the new element.

    You can update the database function create_trail_name to change the implementation of trail naming in Network Intelligence.

    See Network Intelligence Developer's Guide for further information on configuring database functions.

    When you have configured the trail, click Next to proceed to the final wizard step.

  3. Click Save to commit the changes to the database, and to display the new trail name in the GUI.

About the Trail View

The trail view for the trail is made up of the following view:

  • Child Trails View

These views are common to many supported entities in Network Intelligence, and are described in "Using Object Type Trail Views".

About the Customer Trails View

The customer trails view displays a detailed list of all customer traffic the trail is carrying. The list view uses the trail search filter.

About the Trail Group Object Views

There are several trail object collection views. These views display data for a related group of trails.

To display the trail group object views:

  1. Click the object group view icon. See "Displaying Object Group Views".

  2. Select from the view options:

    • Trail Channel Utilization View

    • Trail Cumulative Channel Utilization View

    • Trail Node to Node Utilization View

    • Trail Media Breakdown View

    • Long Trails View

    • Trail Hop Optimization View

    • Site Trail Utilization View

    • Leased Line Utilization Report

About the Trail Channel Utilization View

The Trail Channel Utilization View is a tabular view that shows the payload utilization of link and path trails.

The list view uses the trail search filter (see "Filtering View Data"). You can filter on:

  • Trail Group: Select from the trail group type; for example: link, trail, path, undefined.

  • Capacity: Filter on the capacity of the trail.

  • Fill percentage: Select trails with utilization greater than, or equal to, the fill setting. The percentage values are 0, 10, 20, 30, 40, 50, 60, 70, 80, 90, or 100.

  • Trail Definition: Filter on the trail definition; for example: 100Mb Ethernet Bearer.

  • A Node, or Z Node, Platform: The platform of the originating and terminating nodes; for example: SDH.

  • A Node, or Z Node, Definition: The definition of the originating and terminating nodes; for example: 1664 SM.

After the utilization percentage is set, the view returns only trails with utilization greater than, or equal to, the fill setting.

You can also include full and protected trails.

About the Trail Cumulative Channel Utilization View

The Trail Cumulative Channel Utilization View is a tabular view that shows the channel utilization of link and path trails. This is the same view as the trail channel utilization view, except that the utilization is cumulatively summed for all trails that share the same start and end equipment.

The Trail Cumulative Channel Utilization View also displays cumulative utilization for all equipment that share the same start- and end location (these are known as inter-site trails).

See "About the Trail Channel Utilization View".

Abou the Trail Media Breakdown View

The Trail Media Breakdown View is a detailed list report for each trail level in the network. It provides a complete breakdown of the number of hops per media type used by a particular trail group and capacity.

The trail media breakdown view uses the trail search filter. See "Filtering View Data".

To create a trail media breakdown report:

  1. Open the filter.

  2. Select the desired trail levels for:

    • Group type

    • Group

    • Service

    • Capacity

    • Date range

  3. Click Apply.

About the Long Trails View

The Long Trails View finds trails for the chosen filter settings that have the greatest number of physical hops in the network. These trails may then be considered candidates for rerouting more efficiently using the Trail Routing Manager module to free up potentially very useful capacity. See "Routing Trails".

The Long Trails View uses the trail search filter. See "Filtering View Data".

To create a long trails view:

  1. Open the filter.

  2. Select the trail capacity and the minimum number of parent hops to display:

    • Group type

    • Group

    • Service

    • Capacity

    • Date range

    • Minimum Hops

  3. Click Apply.

About the Customer Group View

Use the Customer Group View to group several customers to analyze their accumulated trails and utilizations. The list view uses the trail search filter. See "Filtering View Data".

About the Trail Hop Optimization View

The Trail Hop Optimization View finds trails at the chosen capacity that have been inefficiently routed, and presents more optimal solution links for suggested reroutes of these trails. The optimization algorithm is based on considering the least number of physical hops.

About the Site Trail Utilization View

The Site Trail Utilization View is specific to the Z Site, as the Z Site functions as an interconnect site in some configurations. There is no A site filter for this view.

You can filter on:

  • Z Site Search: Find the required site.

  • Incumbent: Select the incumbent.

  • State: Select the state in which the site is located.

  • Area: Select the specific area in which the site is located.

  • Capacity: Select the capacity of the trail.

  • Service Group: Select the service group that applies to the trail.

  • Legacy Company: Select the legacy company that applies to the trail.

  • Trail Group: Select the trail group that applies to the trail.

  • Fill percentage: Select trails with utilization greater than, or equal to, the fill setting. The percentage values are from 0 to 100, in 5 percent increments.

    After the utilization percentage is set, the view returns only trails with utilization greater than, or equal to, the fill setting.

Displaying Trail Models

All modeled trail definitions can be viewed in the trail tree browser by clicking the Trail Definition tab.

Double-click the trail definition to open the trail definition details view.

You can modify or update the trail definition attributes and physical dimensions.

  1. Click Edit to make changes.

  2. Perform one of the following:

    • Click Save to create the new definition in the database. The trail definition must not be the same as an existing definition name. A warning dialog box is displayed if the user attempts to create a definition with the same name as an existing definition.

      The trail definition tree browser is refreshed to show the new definition in the definition list.

    • Click Cancel to close the panel without making any modifications.

Creating a New Trail

You create new trails using the Trail Configuration wizard.

To create anew trail:

  1. Open the Trails tree browser.

  2. Select Trail Configuration Wizard from the Tools menu, or by clicking the Create icon while browsing trails.

    The Trail Configuration wizard appears.

  3. Select Create New Trail, and click Next.

  4. Enter the trail details.

    The policy is set when you select the service, assuming the service has a policy. The trail definition and capacity are set if you have created a service trail definitions rule as part of the policy.

  5. Click Next to display the trail values. The trail has not yet been routed.

  6. (Optional) Click Find Trail Routing to find a route.

    Trail Routing Manager starts. The service demand and policy details are automatically set. Select Analyze to view the suggested solutions (if any), and choose the required option by right-clicking the Select icon, and selecting Default Configuration as Main Path or Manual Configuration as Main Path.

    The A and Z Equipment (and A and Z Port, if any are accepted) are filled in automatically for all newly created circuits in the next page of the Circuit Creation Wizard.

    See "Routing Trails".

  7. Click Next and add more details about the trail.

  8. (Optional) Click Generate Name beside the Name field to create a name for the trail. There are two possible results, depending on the type of trail:

    • If the trail is between sites, Network Intelligence concatenates the names of the A Site and Z Site, the trail capacity, and the next available sequence number for the trail, to create a name of the form: ASite-ZSite/Capacity/001.

    • If the trail is between equipment, Network Intelligence concatenates the names of the A Equipment and Z Equipment, the trail capacity, and the next available sequence number for the trail, to create a name of the form: AEquipment-ZEquipment/Capacity/001.

    The sequence number allocated in this name is the next available to a trail, and matches the sequence number listed in the SequenceNo field in the trail view.

    If you modify any of the elements that comprise the trail name, for example, you change the A Site, Z Site, or capacity, click Generate Name again to update the name to include the new element.

    You can update the database function create_trail_name to change the implementation of trail naming in Network Intelligence.

    See Network Intelligence Developer's Guide for further information on configuring database functions.

    When you have configured the trail, click Next to proceed to the final wizard step.

  9. You are prompted whether you want to display the new trail on saving it. Accept the default to display the trail, or deselect the check box.

  10. Click Finish to save the trail. The trail is saved in the database, and displayed in the appropriate folder in the Trails tree browser.

    If a child trail is added to a parent trail on the last remaining channel or timeslot, then this parent trail should no longer be considered for routing.

Adding a Signal Structure

A structured trail definition has a signal structure that defines the set of child trail holders that the trail payload supports.

To add a signal structure:

  1. Open the Trails tree browser.

  2. Click the Trail Definition tab to display the existing trail definitions, or create a trail definition. See "Creating a Trail Definition".

  3. Select the View tab to display the associated reports.

  4. Click Signal Structure to display the modeled trail definition.

  5. Right-click the trail definition, and select Add to display the Add Signal Structure dialog box.

  6. Complete the details of the signal structure:

    • Select the trail holder definition.

    • Enter the number of trail holders or timeslots.

    • (Optional) Add a prefix to all of the trail holders in the Stub Label field.

    • Enter the base channels group size.

    • (Optional) Edit the names of the trail holders or timeslots in the Label fields.

  7. Click Apply to display the signal structure hierarchy in the GUI.

    You can remove, or rename, trail holders, or add a trail definition by right-clicking any of the modeled trail holders.

    You can add a default trail on the signal structure.

Adding a Default Trail on the Signal Structure

You can add a trail on the signal structure of a trail definition so that every time an instance of a trail based on this trail definition is created, a trail is added on one, or more, of its constituent trail holders.

To add a default trail on the signal structure:

  1. Open the Trails tree browser.

  2. Create a trail definition. See "Creating a Trail Definition".

    You must:

  3. Select the View tab to display the associated reports.

  4. Click Signal Structure to display the modeled trail definition.

  5. Right-click one of the trail holders on the trail definition, and select Add to display the Add a Default Trail Definition dialog box.

  6. Complete the details of the trail by selecting its associated service, policy, and trail definition.

  7. (Optional) Add default trails to the other trail holders.

  8. Click Apply to display the trail in the signal structure view.

  9. Click Save to commit the changes.

Creating Multiple Trails

You can also use the trail configuration wizard to create multiple trails at the same time. This is useful to create a group of trails that have similar properties.

Note:

You can create multiple trails only if the start and end sites are the same for each trail demand.

To create multiple trails:

  1. Open the Trails tree browser.

  2. Select Trail Configuration Wizard from the Tools menu, or by clicking the Create icon while browsing trails.

  3. Select Create New Trail and click Next.

  4. Enter the trail details, entering the Total Trails value for the number of trails required.

  5. Click Next to display the trail values. The trails have not yet been routed.

  6. (Optional) Click Find Trail Routing to find route paths for each trail.

    Trail Routing Manager starts. See "Routing Trails".

  7. Click Next and add more details about the trail.

  8. Enter all the first trail details.

  9. (Optional) Click Generate Name beside the Name field to create a name for the trail.

  10. To autopopulate the remaining trail forms, click Replicate Values for all Trails, which is displayed last in the selected Trail detail view.

    This button uses all the values entered in this form (except name and start and end ports) to auto-populate the remaining trail forms. This saves a lot of time, however, the user must still generate the trail name for each trail. Selected ports and logical ports are not replicated for other trails, so if the trails require port selection, these must be selected for each individual trail.

  11. After you configure the trail, click Next.

  12. You are prompted whether you want to display the first new trail on saving it. Accept the default to display the trail, or deselect the check box.

  13. Click Finish to save the trails. The trails are saved in the database, and displayed in the appropriate folder in the Trails tree browser.

    Note:

    Only the first trail is automatically loaded and displayed in the main workbench on bulk trail save. To see the other trails, look for them in the appropriate folder in the trail tree browser or use the trail search window.

Routing an Unrouted Trail

To route an unrouted trail, use the trail configuration wizard. Many of the steps in this procedure are similar to those described in "Creating a New Trail".

  1. Select Trail Configuration Wizard from the Tools menu, or by clicking the Create icon while browsing trails.

  2. Select Route an Unrouted Trail, and click Next.

  3. Click Find Trail and use the Search window to select a trail to route.

  4. Click Find Trail Routing to find a route.

    Trail Routing Manager starts. See "Routing Trails".

  5. When an information message is displayed that Trail Routing Manager processing is complete, and the service demand is successful, select from the routes suggested by Trail Routing Manager.

  6. Click Accept on the Trail Routing Manager configuration screen.

  7. Click Next on the Trail Configuration wizard screen to add more details about the trail.

  8. You are prompted whether you want to display the new trail on saving it. Accept the default to display the trail, or deselect the check box.

  9. Click Finish to save the trail.

Deleting an Existing Trail

You can delete a trail using the trail configuration wizard:

  1. Select Trail Configuration Wizard from the Tools menu, or by clicking the Create icon while browsing trails.

  2. Select Delete Existing Trail, and click Next.

  3. Select the trail for deletion by clicking Find Trail.

  4. Enter the details about the trail.

  5. Click Search to find the trail.

  6. From the list of trails, click Select to choose the trail for deletion.

  7. Confirm the trail deletion.

    If a child trail is removed from a parent trail, it changes a channel or timeslot on the parent trail to free, and this parent trail can be considered for routing.

    Note:

    Deletion of the trail from the Network Intelligence database is permanent, and the data is not recoverable.

Upgrading an Existing Trail

You can upgrade the trail definition associated with a trail so that the trail can carry more traffic. You can upgrade the cards on each of the trail's terminating ends.

You can upgrade unstructured and hybrid trails. The upgrade procedure for unstructured and hybrid trails is the same, except for the specific case of increasing the capacity of unstructured child trails.

For unstructured trails, the service being carried and the underlying trail capacity (set in the trail definition) are also updated accordingly. Parent-child relationships between the trail being upgraded and its existing child trails are preserved. Updating ports and cards remains unchanged.

To upgrade a trail using the trail configuration wizard:

  1. Select Trail Configuration Wizard from the Tools menu, or by clicking the Create icon while browsing trails.

  2. Select Upgrade Existing Trail, and click Next.

  3. Click Find Trail to select the trail to be upgraded.

  4. Enter the details about the trail.

  5. Click Search to find the trail.

  6. From the list of trails, click Select to choose the trail.

  7. Click Next to display the service and trail definition upgrade screen.

    Update the service.

    If the service has no trail definition assigned, you must select one. If a trail definition is present for this service, you cannot edit the trail definition.

  8. Click Next to display the signal structure mapping screen.

    This screen is not presented in the following cases:

    • When a (structured) trail is being upgraded to an unstructured trail. This is because an unstructured trail does not have a defined signal structure, and timeslots are generated dynamically. As a result, mapping of child trails is not required in this instance.

    • When a trail being upgraded has no child trail, there is no mapping requirement.

  9. Reassign the trail holders on the trail definition. All populated trail holders must be mapped. Each populated trail holder must match the trail holder to which it is being mapped. In other words, a child trail can only be validly mapped to a destination trail holder that has enabled the trail definition of the child trail. If the mapping is not valid, an error message is displayed.

    Each trail definition is defined by sequence number, trail holder definition, child trail definition, and reassigned sequence number.

    On the left pane, select a row containing a trail holder, and click the Seq No field to revise the sequence number. The Seq No on the right pane is automatically filled in.

  10. Click Next to display the A terminating side upgrade screen.

  11. Select one of the following options:

    • Leave physical port as is

      Proceed to the configuration of the Z terminating side of the trail.

    • Select different physical port on the same equipment

      Reconfigure the A physical port.

      Click Next to proceed to the configuration of the Z terminating side of the trail.

    • Replace card

      Reconfigure the A card.

      Click Next to proceed to the mapping of the ports on the A card.

  12. (Optional) Reassign the ports on the A card by mapping connected trails from original ports to new ports. All populated ports must be mapped.

    Each port is defined by sequence number, name, trail, and sequence number to assign to.

    On the left pane, select a row containing a port, and click the Seq No field to revise the sequence number. The Seq No on the right pane is automatically completed.

  13. Click Next to display the Z terminating side upgrade screen.

  14. Select one of the following options:

    • Leave physical port as is

      Proceed to the configuration of the trail name.

    • Select different physical port on the same equipment

      Reconfigure the Z physical port.

      Click Next to proceed to the configuration of the trail name.

    • Replace card

      Reconfigure the Z card.

      Click Next to proceed to the mapping of the ports on the Z card.

  15. (Optional) Reassign the ports on the Z card by mapping connected trails from original ports to new ports. All populated ports must be mapped.

    Each port is defined by sequence number, name, trail, and sequence number to assign to.

    On the left pane, select a row containing a port, and click the To Seq No field to revise the sequence number. The From Seq No on the right pane is automatically completed.

  16. Click Next to display the trail name configuration screen.

  17. Edit the name of the trail.

    Click Next to proceed to the final wizard step.

  18. (Optional) Click Generate Name beside the Name field to create a name for the trail. There are two possible results, depending on the type of trail:

    • If the trail is between sites, Network Intelligence concatenates the names of the A Site and Z Site, the trail capacity, and the next available sequence number for the trail, to create a name of the form: ASite-ZSite/Capacity/001.

    • If the trail is between equipment, Network Intelligence concatenates the names of the A Equipment and Z Equipment, the trail capacity, and the next available sequence number for the trail, to create a name of the form: AEquipment-ZEquipment/Capacity/001.

    The sequence number allocated in this name is the next available to a trail, and matches the sequence number listed in the SequenceNo field in the trail view.

    If you modify any of the elements that comprise the trail name, for example, you change the A Site, Z Site, or capacity, click Generate Name again to update the name to include the new element.

    You can update the database function create_trail_name to change the implementation of trail naming in Network Intelligence.

    See Network Intelligence Developer's Guide for further information on configuring database functions.

    Note:

    If a hybrid trail is being upgraded to a higher capacity hybrid trail, its unstructured child may also be upgraded to consume the full capacity of the new trail holder to which it is mapped.

    In this case, separate Edit dialog boxes are provided to modify both the child trail name and the parent trail name.

    When you have configured the trail name, click Next to proceed to the final wizard step.

  19. You are prompted whether you want to display the new trail on saving it. Accept the default to display the trail, or deselect the check box.

  20. Click Finish to save the trail. The trail is saved in the database, and displayed in the appropriate folder in the Trails tree browser.

    If a child trail is added to a parent trail on the last remaining channel or timeslot, then this parent trail should no longer be considered for routing.

    Note:

    If the ports (A Port, Z Port) assigned to a new logical trail; for example: a VC-12, are consumed by another trail, the trail save succeeds. In previous releases of Network Intelligence, such trail saves failed.

Bulk Updating Trails

To update trails; for example: to edit a list of trails in an impacted trails routing report generated as part of an outage plan:

  1. Select the required trails from the trail list.

  2. Right-click the selection, and select Bulk Update Trails to display the Bulk Entity Update dialog box.

  3. Perform one of the following options:

    • Click Add to display the Trail Search dialog box. Select the trails to include.

    • Select a trail, and click Remove to delete it from the list.

    • Select a trail, and click Modify to change the trail status; for example: to change the trail status from Planned to Ceased.

  4. Click Apply to commit the changes.

Protecting an Existing Trail

You can create a protection trail with the Trail Configuration wizard.

  1. Do one of the following:

    • Open the Trail Configuration wizard from the Trails tree browser:

      1. Open the Trails tree browser.

      2. Click the Create icon.

        The Trail Configuration wizard appears.

      3. Select Protect Existing Trail, and click Next.

      4. Click Find Trail.

        The Circuit Search dialog box appears with the Protection list already set to Unprotected.

        Use the Circuit Search dialog box to search for the unprotected trail you want to protect.

      5. Click Next.

    • Open the Trail Configuration wizard from the Trail search:

      1. Open the Trails tree browser.

      2. Click the Search icon.

        The Trail Search appears.

      3. From the Protection list, select Unprotected.

      4. Specify any other search criteria and select Search.

        The search results appear.

      5. Right-click the trail you want to protect and select Protect Trail.

    The Trail Configuration wizard displays the selected trail.

  2. Specify the A and Z equipment for the portion of trail you want to protect:

    1. Right-click the A equipment and select Select A Equipment.

    2. Right-click the Z equipment and select Select Z Equipment.

    3. Click Next.

      The Enter Service Demands Details screen appears.

      Note:

      A fully-protected trail is one where the start and end of the trail are the A and Z equipment. A partially-protected trail is one where either the start or end of the trail are not the A or Z equipment.
  3. Specify the service demand details for the protection path:

    1. In the Capacity field, select the capacity for the protection trail.

    2. In the A Site and Z Site fields, select the A site and Z site for the protection trail.

    3. In the A Equipment and Z Equipment fields, select the A equipment and Z equipment on the working trail between which the protection trail is to be created.

    4. Click Next.

    The Trail Routing screen appears.

  4. Click Find Trail Routing to route the trail. See "Routing an Unrouted Trail" for more information.

Creating a Trail Holder Definition

You can create new trail holder definitions to group trails. A trail holder definition includes the following attributes:

  • Name

  • Capacity; for example:

    • 100 MB

    • VC-4

  • Enabled trail definitions

To create a trail holder definition:

  1. Click New while browsing trails.

  2. Select New Trail Holder Definition.

  3. Enter the trail holder details.

  4. Click Save.