|
|
Table Of Contents
1.1 Cisco MetroPlanner Features
1.2.1 Network Design Optimization
1.2.2 Network Design Constraints
1.2.5 Protection Scheme Support
1.3 Cisco MetroPlanner Process Flow
1.4 Planning Traffic in Cisco MetroPlanner 7.0
1.5 Cisco MetroPlanner 7.0 Traffic
1.5.1 Point-to-Point Traffic Groups
Overview
Cisco MetroPlanner Release 7.0 provides a way to model and test wavelength division multiplexing (WDM) optical networks in a graphical environment. The primary purpose of Cisco MetroPlanner is to help sales engineers (SEs) design and validate networks of Cisco Optical Networking System (ONS) 15454 Multi-Service Transport Platforms (MSTP). Using Cisco MetroPlanner Release 7.0, an SE can create multiple instances of a network to modify different parameters in each instance for comparison. Cisco MetroPlanner generates a shelf view of all the sites deployed in the optical network and provides a complete bill of materials (BOM) for the network and the differences between instances of a network.
This chapter describes how you use Cisco MetroPlanner to design, analyze, and optimize new or existing Cisco optical networks and contains the following sections:
•
Cisco MetroPlanner Process Flow
•
•
1.1 Cisco MetroPlanner Features
Cisco MetroPlanner Release 7.0 provides a simple tool set for designing optical networks with Cisco ONS 15454 MSTP products. You can enter all of the network parameters or minimal information, such as site distance, and Cisco MetroPlanner will model the network you need to build and generate a detailed BOM with ordering information. Designing optical networks requires the verification of multiple constraints such as optical budget limitations and platform architectural restrictions. One Cisco MetroPlanner project can contain multiple copies of a network. This allows you to change parameters in one network copy, then analyze and compare to another network copy to determine the differences. In addition to this capability, Cisco MetroPlanner Release 7.0 provides the following new features:
•
•
•
•
•
•
•
•
•
•
•
•
•
1.2 Network Design Process
To generate a network design, the SE enters the following parameters:
•
•
•
•
•
When the network parameters are entered, Cisco MetroPlanner finds the best routing, defines the required add/drop filters, and places optical amplifiers and dispersion compensation units (DCUs) to fit the user traffic demands at the minimum cost. Optimization is performed to meet the boundary conditions. The optimization includes attenuation and amplification.
Finally, Cisco MetroPlanner generates a BOM, which includes the product codes, the quantities, and pricing information. In addition, it creates other reports, such as a shelf-level view of the configuration, which can be printed. This helps the SE understand how the shelf is built and helps to avoid confusion and errors during the actual deployment. Within the BOM is the total network cost, which allows a quick comparison of various design options. The total network cost is the cost of the equipment for all of the sites in the designed network.
1.2.1 Network Design Optimization
Cisco MetroPlanner searches for the best solution to a designed network using an optimization algorithm.
1.2.2 Network Design Constraints
A network design must meet the optical budget and receiver overload criteria to operate efficiently. An analysis of optical budget and receiver overload evaluates the strength of the signal traversing the ring. If a design solution satisfies the constraints, it is a valid design. The Cisco MetroPlanner Release 7.0 optimization algorithms generate multiple solutions and verify the constraints against those solutions. If the constraints are satisfied, the solution with the lowest cost-to-utilization ratio is selected as the optimal solution.
If the network design solution fails to satisfy all the constraints, Cisco MetroPlanner Release 7.0 makes adjustments to parameters such as signal attenuation and amplification. Amplification is achieved by using an erbium-doped fiber amplifier (EDFA). Attenuation is achieved by using variable optical attenuator (VOA) modules integrated into the platform. Cisco MetroPlanner Release 7.0 corrects the optical budget using an algorithm that includes automatic placement of EDFAs and VOA regulation.
For each internodal demand, Cisco MetroPlanner Release 7.0 performs an optical budget and receiver overload analysis and displays the results in various reports in the GUI. If the network design algorithms are not able to provide a solution, then you can modify the input data (for example, by relaxing some user constraints) and run the analysis again.
1.2.3 Platform Support
Cisco MetroPlanner Release 7.0 supports the Cisco ONS 15454 DWDM optical platform Software Releases 4.7, 5.0, and 7.0.
1.2.4 Topology Support
Cisco MetroPlanner 7.0 supports the following network topologies:
•
•
•
•
Cisco MetroPlanner 7.0 allows you to design flexible networks with up to 60 site locations. A flexible network is a network that, using ROADM nodes, allows traffic modification/reconfiguration as traffic requirements change. The main feature of flexible networks is the traffic reconfiguration/modification among all the networked nodes or among a subset of them.
The maximum number of locations where the optical service channel (OSC) is terminated is 20. The maximum number of add/drop locations is 16.
1.2.5 Protection Scheme Support
Cisco MetroPlanner 7.0 designs support the following protection schemes:
•
•
•
•
1.2.6 Service Support
Cisco MetroPlanner 7.0 can support any subset of the following services:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
•
•
•
Refer to the Cisco ONS 15454 DWDM Reference Manual for more information about the supported topologies for the ETR and CLO services.
1.3 Cisco MetroPlanner Process Flow
The following stages are used to complete a network design. See Figure 1-1 for the process flow.
1.
2.
3.
4.
5.
6.
7.
8.
Figure 1-1 Cisco MetroPlanner Process Flow
1.4 Planning Traffic in Cisco MetroPlanner 7.0
Traffic in Cisco MetroPlanner is defined as an optical path for each pair of nodes requiring a service demand. An optical path is the combined channels between the two nodes. The following list gives definitions for some basic traffic items:
•
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
•
–
–
–
ROADM circuits have the same protection types and services. The number of circuits is not user-specified and can vary from 0 to 32. For ROADM, only L-band is supported.
1.5 Cisco MetroPlanner 7.0 Traffic
Cisco MetroPlanner 7.0 represents all of the user-defined traffic services as a tree view within the Project Explorer pane. The Project Explorer shows all of the open project information, including the networks, the network dependencies, sites, fibers, services, etc. ( Figure 1-2).
Figure 1-2 Project Explorer View
After you analyze a network design, the colors of tree view change according to the error/warning condition of the network design. The icons display as red if there are errors in the network design; orange if there are warnings but no errors; and green of there are no warnings or errors. The icon shows the color of the most severe condition. For more information about analyzing the network, see the "2.4 Analyzing the Network" section on page 2-36.
Right-clicking on certain items in the Project Explorer tree allows you to edit the parameters. Refer to Chapter 2, "Designing Networks with Cisco MetroPlanner" for more information about optical results, the traffic matrix, and editing.
1.5.1 Point-to-Point Traffic Groups
Point-to-point traffic groups appear in the Groups > PointToPoint folders in the Project Explorer pane. Each point-to-point traffic group is categorized by its source and destination site names. All of the point-to-point services between the two sites appear under the designated demand name ( Figure 1-3).
Figure 1-3 Point-to-Point Traffic Group in the Project Explorer
A point-to-point traffic demand includes the following information:
•
•
•
1.5.2 P-Ring Traffic Groups
Each protected ring (P-ring) traffic group appears in the Project Explorer pane under the Groups > P-Rings folders. Figure 1-4 shows an example of a P-ring traffic group in the Project Explorer.
Figure 1-4 P-Ring Traffic Group in the Project Explorer
All the P-ring channels between each site pair are listed under each P-ring traffic group. Each demand is labeled with the following information:
•
•
•
•
1.5.3 ROADM Traffic Groups
Each ROADM traffic group appears in the Project Explorer under the Groups > ROADMs folders. The ROADM traffic group folder contains one folder for each defined ROADM demand. You can define more demands for the same ROADM group for the same set of nodes. Figure 1-5 shows an example of a ROADM traffic group.
Figure 1-5 ROADM Traffic Group in the Project Explorer
In the Project Explorer, each ROADM demand includes the ROADM demand name and a list of DWDM card types that support the client service types. Protection types appear in parentheses.
A ROADM demand can have multiple client service types and supports multiple DWDM card interfaces for each client service type. A ROADM demand supports the following routing strategies:
•
•
•
•
Posted: Fri Nov 30 10:29:02 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
