|Oracle® Communications Network Intelligence User's Guide
|PDF · Mobi · ePub|
This section describes networks in Oracle Communications Network Intelligence. A network consists of a series of points or nodes connected by communication paths.
The network tree browser contains a list of all defined networks in the Network Intelligence database. Networks in Network Intelligence are generated in one of the following ways:
Networks are created in the Network Intelligence GUI. See "Creating a Network".
Networks are loaded from the inventory management system (IMS) in which they are modeled. See Network Intelligence Concepts for further information on data loading.
You can create every type of object required for use in planning use cases using the Network Intelligence user interface.
The Create icon is used to create new network entities. All entities that are created in Network Intelligence have a default status of Planned (signifying that it is a Network Intelligence planned object). After the new object is created, it may be used in Forecast Manager for network simulations and planning.
To create a network:
Click Network on the context toolbar.
Click the Create icon:
The New Network window is displayed.
Configure the network using the following values:
Name: The name of the new network. The name must be unique.
Parent Network: Select from the list of available networks.
InService Date: Select the date on which the network comes into service.
OutService Date: Select the date on which the network goes out of service.
Status: The status of the network. The status is ONI Planned (where ONI signifies Oracle Communications Network Intelligence) by default, but may be changed to another status; for example: Planned Cease, Reserved in Service, Reserved Reprovide, Testing, and so on.
Policy: Setting a policy for a network allows specific routing constraints to be applied for the network when path routing.
The network object offers the following views:
Network Node View
Customer Bandwidth View
The network node view displays a logical view of the network's equipment nodes and their connecting trails. A network has nodes associated with it when a topology is assigned to reference a network.
In the network node view, you can filter trails to decide what trail connectivity is required between network nodes.
This view has the same behavior as that described in "Running the Inter Equipment Trail Mesh Report".
Note:This report does not use active filtering. See "Active Filtering".
The equipment search view displays a table view of the network's equipment.
You can filter the equipment as follows:
Select from the labels corresponding to the equipment filters:
Status: The status of the equipment. By default, the status is planned, but may be changed to another status; for example: Planned Cease, Reserved in Service, Reserved Reprovide, Testing, and so on.
Date range: Select the in service date for the equipment.
Click to select the required equipment.
Click Apply to generate the view.
The child trails view displays a filterable list of trails that reference nodes of the network.
The child trails view for the network is common to many supported entities. See "Using Object Type Trail Views" for a description of the view.
The customer bandwidth view provides a list of every customer subscribing to a service carried on the network.
The customer bandwidth can be filtered by both customer and capacity. You can extract and save the customer bandwidth data.
To view the customer bandwidth view for the network:
Click Select to search for the customer, or select the customer from the list in the Network Customer Bandwidth Report table.
Select the capacity.
The default is all available capacities on the network.
Click Retrieve to view the customer bandwidth for the network.
Customer bandwidth is defined by customer name, capacity name, the number of trails of that type allocated to the customer, and bandwidth (in Mbps).