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

13 Using Configuration Plans

This section describes configuration planning in Oracle Communications Network Intelligence. You can capture live configuration changes to network resources in Network Intelligence; for example: site creation, equipment modification, or trail deletion, and view these actions - and interactions with other supported entities - in a configuration plan. The contents of the configuration plan can be exported in various formats, or viewed in a report.

Configuration plans apply to the following entities:

Creating a Configuration Plan

You can create a configuration plan without enabling Configuration Planning mode. If you are in Network Modeling mode and create a new configuration plan, it automatically enables Configuration Planning mode, and populates the planning toolbar with the details of the newly created plan.

See "Using the Toolbar" for further information about the modes offered on the toolbar.

To create a configuration plan:

  1. Select one of the following:

    • From the context toolbar, click Plans, and from the Plans tree browser, click the create icon: Create object icon

      Select Create New Configuration Plan.

    • From the Network Intelligence toolbar, click the Create Configuration Plan icon: Create configuration plan icon

  2. Complete the details of the plan, such as the name and planning type. See "Using the Configuration Plan Details View" for definitions of the fields.

  3. Click Save to create the plan.

    The toolbar is automatically updated with the details of the plan.

Using the Configuration Plan Details View

The configuration plan details view, selected by double-clicking a configuration plan in the tree browser, displays the plan object and lists its primary attributes.

A configuration plan has the following attributes:

Table 13-1 Configuration Plan Attributes

Plan attribute Description

Name

The name used to identify the plan.

Planning type

The type of plan:

  • Configuration

  • Forecast

  • Migration

  • Outage

Configuration is the default.

Plan action

The task to be carried out.

You can add plan actions using

  • The Metadata administration web portal, which creates, administers, and maintains metadata data values in Network Intelligence.

    See the Domains chapter of Network Intelligence Developer's Guide.

  • Using the domain_value_stg table in the Staging schema. See the chapter on populating the staging database in Network Intelligence Developer's Guide.

Start date

The first time period date of the plan.

End date

The last time period of the plan.

Shared

Whether this plan is shared with other users.

Notes

Other information about the plan; for example: information relating to part of a works order to be completed using the plan.


Creating a Sample Configuration Plan

In this plan, Network Intelligence is used to make changes to the path taken by an existing trail, by reconfiguring its parent trail assignments. All resource configuration changes are captured against a configuration plan called Reconfigure Trail Path. All changes can be viewed in the Configuration Change Report.

To create the sample configuration plan:

  1. Perform the first four steps listed in "Creating a Configuration Plan".

  2. Enter the details of the plan, such as the name and planning type. See "Configuring the Sample Configuration Plan".

  3. Click Save to create the plan.

Configuring the Sample Configuration Plan

The sample configuration plan has the following attributes:

Table 13-2 Sample Configuration Plan Attributes

Plan attribute Description

Name

Reconfigure Trail Path.

Planning type

The type of plan:

  • Configuration

This field cannot be edited.

Plan action

Trail path upgrade.

Start date

August 4, 2012.

End date

August 7, 2012.

Shared

Yes.

Notes

This plan forms the basis for a Trail Path Rearrange works order for a trail called Intersite 1GB Ethernet Trail. The works order must be completed before 31st October, 2012.


Recording Data for the Configuration Plan

After creating the configuration plan, you can use it to record configuration actions.

To record data:

  1. Click the record icon on the Network Intelligence toolbar. See Figure 13-1.

    Figure 13-1 Configuration Plan: Recording Icon

    Configuration Plan Recording Icon
  2. Click OK to accept the message that all changes are being captured against the selected plan:

    Recording configuration actions against Configuration Plan: Plan Name.

  3. Perform the required configuration.

  4. Click the stop recording icon on the Network Intelligence toolbar. See Figure 13-2.

    Figure 13-2 Configuration Plan: Stop Recording Icon

    Configuration Plan Stop Recording Icon
  5. Click OK to accept the message that no subsequent changes are captured against the selected plan:

    Recording stopped. No longer capturing configuration actions against Configuration Plan: Plan Name.

  6. Examine the data in the configuration report. See "Viewing the Configuration Change Report".

Viewing the Configuration Change Report

The configuration change report is a table listing all configuration actions recorded against the configuration plan. The most recent actions are listed first. Actions are defined by:

  • Configuration: The action type; for example: Add, Remove, Modify, Create, Delete, and so on.

  • Entity: The entity created, modified, or deleted.

  • Name: The name of the entity.

  • Description: Further information about the configuration action.

  • Field Name: The name of the field modified; for example: Status, Service, Name, and so on.

  • Old Value: The value of the field before the modification; for example, for a trail currently in use, but planned for decommissioning, In Service.

  • New Value: The value of the field after the modification; for example, for a trail that has been taken out of commission, Ceased.

  • Child Entity: The type of the child of the entity; for example: ports and cards are children of an equipment entity.

  • Child Name: The name of the child of the entity.

  • Child Description: A full description of the child entity; for example, for a port: Site/Equipment/Sub Rack/Shelf/Slot/Card/Port.

  • Changed By: The user who carried out the configuration action.

  • Time: When the configuration action took place.