Related Documentation
Custom Rates
Field | Description |
|---|---|
Protocol | Displays the protocol to which this particular administrative weight applies to. The protocol displayed depends on the protocols and hardware used in the network. For example, for a router network possible values include “OSPF” or “ISIS”. For an ATM network, possible values include “ADMINWEIGHT” or “PNNI” (PNNI requires a license). The default value is “ALL”, indicating no protocol constraint. |
HW Type1 and HW Type2 | The hardware type of the end point where the administrative weight is applied. For example, if this column displays “ETHERNET” and the HW Type2 column displays “ASNODE”, then the admin weight is applied to all links originating at nodes designated with the “ETHERNET” hardware type and terminating at nodes designated with the “ASNODE” hardware type. |
Hlevel1 and Hlevel2 | Hierarchy levels CORE, REGULAR and ACCESS. These values are defined for each node in the Node Properties window. Core nodes are nodes residing in the center of the backbone and receive the heaviest traffic. Access nodes are either single-end or feeder nodes. (Single-end nodes only connect to one other node (it is a node with a single neighbor). Feeder nodes only connect to one other node, and only through one link (no parallel links to its single neighbor).) Regular nodes are all other nodes in the network not considered core or access. |
Trunk | Displays the trunk type for this administrative weight. |
Same Site | Indicates whether the administrative weight applies to links in the same site. A site represents node associations. These associations are typically user-defined by physical location. See Sites for more information. If Same Site is set on “True”, then this administrative weight is applied to all links within sites defined by you. “False” will apply this admin weight to links between sites. “Don’t Care” will apply this admin weight to all links found in the network. Possible Values:
|
Same PeerGroup (PNNI) | Indicates whether the administrative weight applies to links in the same peer group (if applicable). This field appears only for hierarchical PNNI networks. |
Fixed Weight | Displays the value of the fixed administrative weight. |
Variable Weight | Displays the value of the variable administrative weight. |
The Custom Rates window accessed from the main menu Network > More > Custom Rates > View Bands option is one of several methods of specifying link tariffs to price the backbone links. A backbone design run will add the necessary links to satisfy network demands while optimizing the link tariffs. For a list of the other ways to specify link costs and the order of precedence, see the File Format Reference for IP/MPLSView.
The window is divided into two halves. The upper half includes the link category, as defined by the vendor, service (for example, OC3, OC12), and the tariff classes of the link’s end-nodes. Additionally, it includes the non-recurring charge (install fee) for that link category. The bottom half displays the recurring charges and can have multiple rows if the recurring charge is distance-dependent.
Figure 81: Custom Rates Window
Link Category
The link category is defined by the link’s vendor, service (for example, OC3, OC12), and the tariff classes of the link’s end-nodes. The tariff classes should be specified ahead of time in the Custom Rates Class window (see Custom Rates Class). To specify rates within the same class, the class specified in the class1 and class2 field would be the same. Note that “ALL” is a reserved class name that applies to nodes of all tariff classes and is used as a default unless the rate for a specific class is specified.
Field | Description |
|---|---|
Vendor | Indicates the link vendor (for example, ATT, MCI, etc.) or DEF for default |
Link Type | Indicates the link type. Valid link types are: T1, E1, T2, T3, E3, HSSI, AIM, OC3, OC12, OC48, OC192, STM1, STM4, etc. |
Class1 | Indicates the class associated with the originating node. |
Class2 | Indicates the class associated with the destination node. |
General Tariff Parameters
Field | Description |
|---|---|
Currency | This drop-down menu allows you to choose the country currency to apply the tariff in. The default is United States (US dollars). Note: For the EURO currency (symbolized by “ER”), select ER EURO from the country list. |
Distance | Specifies the unit which distance is measured in. Default distance is set to the MILE. |
Inc. Distance | Incremental distance. This is the unit that is used for calculating the cost as specified in the incremental cost field. |
Tariff Bands
Field | Description |
|---|---|
Install Fee | This is the non-recurring charge (NRC) for this link category. All other costs are recurring (for example, monthly) charges. |
Distance (up to) | Defines a distance band starting from the previous distance, or 0 if no other distances are listed. The last distance value should be 9999 or higher. |
Fixed Cost | Sets the fixed cost for this band. Fixed costs do not vary with distance. |
Inc. Cost | Sets the incremental cost that must be paid for each incremental distance unit (for example, 1 mile) of the link whose distance falls within this tariff band. |
Calculating the Link Tariff
To determine a link’s tariff, the program finds the matching
link category. For the matching link category, the program then uses
the link’s distance (using airline mileage as an approximation)
to determine which distance band will apply. The recurring charge
is then determined by the fixed cost for that distance band plus a
variable cost per distance increment. The formula is as follows: Recurring_charge=Fixed_cost+(Inc_cost/Inc_dist)*linklength
where the value of Inc_cost and Fixed_cost are taken from the distance band within which the link’s airline distance falls.
Add / Modify Custom Rates
Click the Add or Modify button to add or modify the custom tariff rates for a link category.
- Add Row: Adds a new row to the Bands table.
- Delete Row: Deletes the selected row in the Bands table.
Upon saving the network, the custom tariffs information is saved in the custrate.runcode file. Tariff information can also be directly entered in from the text file. More details on the file format can be found in “The Cost Files” chapter of the File Format Reference For NPAT and IP/MPLSView.
