Export Topology Operations

The Export Topology submenu contains operations that let you export your network model in various formats. Operations include:

To EMA…

WARNING: EMA source code files for all models have the same suffix, .em.c, regardless of model type. Be sure that the EMA file you create will not overwrite a previously-created file you want to keep.

This operation allows you to generate External Model Access (EMA) source code that represents the model currently present in the active tool. EMA code is in text format, allowing you to edit it with an ordinary text editor.

Procedure 92: Generating EMA Code

  1. Make sure the model for which you want to produce EMA code is active. If not, choose Open from the File menu and display the model in the editor window.
  2. Choose Topology > Export Topology > To EMA.
    • The program generates the EMA code and stores it in the file <model name>.em.c.

For more information about EMA, see "External Model Access" on page 1.

To Spreadsheet…

This operation generates a report that can have a variable amount of detail on the objects in a network model, depending on what values you specify for certain preferences.

For more information, see "Text Reports" on page 851.

To Visio…

This operation creates a text file and supporting TIFF graphics files that represent the network currently shown in the editor window. These files can be imported to the Visio drawing program to produce a representation of the network.

For more information, see "Publishing Network Information" on page 837.

To XML…

This operation generates an XML file that describes the network topology of the current scenario in the project. The resulting XML file can be viewed and edited using an XML editor.

For more information, see "Publishing Network Information" on page 837.

Subnet Hierarchy to NetCollector as Groups

The Export Topology to NetCollector as Groups operations allows you to export your subnet hierarchy to NetCollector. Subnets are mapped to NetCollector groups in a one-to-one fashion.

When the NetCollector group information is in sync with the network topology defined in the Project Editor, you can more efficiently perform analyses on specific subnets and nodes of interest.

Note: If you perform a cut-and-paste operation or a copy-and-paste operation on nodes in your model, the nodes will not be exported to groups on NetCollector.

Procedure 93: Exporting Subnet Hierarchy to NetCollector as Groups

  1. Select the subnets for which you want to export information. Or select no subnets to export information for the entire network.

  2. Choose Topology > Export Topology > Subnet Hierarchy to NetCollector as Groups.

  3. Choose an option from the submenu:

    • Entire Network – Exports all subnets and nodes to groups that contain nodes on NetCollector.
    • Selected Subnets – Exports subnets selected in the project editor to NetCollector groups.

    The Export to NetCollector dialog box appears requesting the server name and port number. The values defined for the preferences vne_import.vne_server_name and vne_export.port display as the default values.

  4. If necessary, specify the server name and port number and select OK.

    • A message appears indicating that the subnet information has been exported to NetCollector.

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · 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