MRTG Link Loads: Preparing for an Import

NetPlanner can import link loads from MRTG. The following table lists the steps to do before you import MRTG data. After you do these steps, proceed to "Importing Baseline Traffic Loads".

Table 2: MRTG Link Loads: Pre-Import Checklist

Step When Required Reference
Specify aliases Once per scenario. Required for nodes or links that meet both these conditions:
- Were created manually
- Are referenced by the imported data
"Alias Formats and Requirements"
Create data files As needed. NetPlanner cannot generate MRTG data files automatically. Creating MRTG Link-Load Data

This section describes how to generate NetPlanner-compatible data files in MRTG version 2.9. Procedures might differ for other versions of MRTG. To see if your version is supported by NetPlanner, go to http://www.opnet.com/support, follow the link for NetPlanner, and view the system requirements.

To create log files that NetPlanner can read, you must use the following identifier.

Table 3: MRTG Identifier

MRTG Identifier Description Example
ip_ifDescr IP address and interface description 172.16.10.150.Serial1_0

For information about importing baseline loads, see "Importing Baseline Traffic Loads".

Procedure 1: Creating MRTG Log Files

  1. Specify the targets using one of the identifiers listed in Table 3. This ensures that the MRTG configuration file contains data in a form that NetPlanner can import.
  2. Verify that the log file names are in the correct format. By default, log file names have the format <mrtg_identifier>.log. For example, the log file name for an interface might be 172.16.10.150.Serial1_0.log.
  3. If an MRTG log file corresponds to a network object that was created manually, you must create aliases for the IP address and interface as described in Mapping MRTG Files to Interfaces,
  4. After you create data files and create aliases (if necessary), go to

Importing Traffic Files from an MRTG RRD

You can retrieve traffic files from a remote MRTG Round Robin Database (RRD) system and then import the files to NetPlanner just like all other MRTG files.

Note: The following procedure requires using an "RRDtool" utility program that is available for download from the Internet. For more information, follow the mrtg-rrd link on the MRTG website.

Procedure 2: Retrieving Files from MRTG RDD System

  1. Login to the MRTG RRD system.

  2. Change directory (cd) to the RRD binary directory (e.g., /usr/local/rrdtool/bin).

  3. Use the rrdtool program to export the data to a text file. The format is:

    rrdtool fetch [full path to RRD file].rrd [type*] >> [output file**].rrd_log
    

    *type is AVERAGE or MAX

    **the output file name should match the original, with the extension .rrd_log

    Example:

    rrdtool fetch AVERAGE /usr/local/mrtg-2/data/10.3.3.2_eth2c0_ip_layer.rrd > 10.3.3.2_eth2c0_ip_layer.rrd_log
    
  4. Repeat the previous step for all files you want to import.

After you have on the traffic files exported, you can then open the network model associated with the traffic you want to import and choose "Traffic > Import Baseline Loads > From MRTG."

Mapping MRTG Files to Interfaces

You must specify aliases for every object that meets both of these conditions:

  • Has load data specified in an imported MRTG files
  • Was created manually (that is, was not imported from device configuration files or an external program)

If these conditions are true for an object, you must specify aliases for both the IP address and the interface as specified in the MRTG log file name. Suppose you have an MRTG log file named 10.1.1.1.Serial1_0.log. Your network must have aliases for both the IP address (IP:10.1.1.1) and the interface number (IFName:Serial1_0). You can specify these aliases in either of the following ways:

  • IP address and interface as aliases on the same link interface
  • IP address as a node alias, and interface as an alias on the connected link interface

The following table lists the supported formats for MRTG aliases. For information about how to create node and interface aliases, see "Working with Aliases".

Table 4: Interface Aliases Used for MRTG Imports

Alias Format Specified As Example
IP:<node_name>
IP:<ip_number>
IP:<domain_name>
IP:<mrtg_log_file_name>
Node or interface alias IP:172.16.10.150
IP:wtn150.acme.com
IP:ita.acme.com
IP:ita.acme.com.2.log
IFName:<interface_description> Interface alias IFName:Serial1_0

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com