Administer > Administer the NNM iSPI Performance for Traffic > Manage the NNM iSPI Performance for Traffic

Manage the NNM iSPI Performance for Traffic

This topic includes the following sections:

Diagnose the Health of the NNM iSPI Performance for Traffic

The Traffic Health view enables you to monitor the health of the NNM iSPI Performance for Traffic. The view presents a comprehensive list of all the problems encountered by the selected NNM iSPI Performance for Traffic Leaf Collector during its operation.

To open the Traffic Health view:

  1. In the NNM iSPI Performance for Traffic Configuration form, click System Health > Traffic Health.
  2. Click Refresh icon Refresh to refresh the list of Leaf Collectors available on the view.
  3. Select a Leaf Collector and click Open to open the Traffic Health view for the Leaf Collector.

The basic attributes of the view are the following:

Attributes Description
Problem ID ID of the problem encountered by the NNM iSPI Performance for Traffic
Severity Severity of the problem
Start Time Time when the problem started
End Time Time when the problem got resolved
Status Status of the problem
Message Problem description
Suggestion Suggestions to resolve the problem

Verify the Installation Configuration Parameters for Master Collector

For error-free performance, make sure that the NNM iSPI Performance for Traffic can communicate with the following applications and application components:

  • NNMi
  • NPS
  • Shared drive between NNMi, NPS, and the NNM iSPI Performance for TrafficMaster Collector.

  • Secondary NNMi Server (if you have configured the NNM iSPI Performance for Traffic for high availability)

    If the secondary NNMi server is configured correctly, the NNM iSPI Performance for Traffic can work even if the primary NNMi server is not configured correctly.

The NNM iSPI Performance for Traffic Installation Verification form enables you to view, verify and modify the configuration parameters you entered when installing the NNM iSPI Performance for TrafficMaster Collector.

The form displays the status of each configuration category.

Click Validate to display the invalid configuration settings in red and the highlight the invalid configuration settings.

To modify a configuration parameter, follow these steps:

  1. On the Installation Verification form under System Health, click Edit to modify the value for any of the following parameters:

    The NNM iSPI Performance for Traffic Installation Verification form lists the following parameters:

    Parameter Title Parameter Detail Details Description
    Primary NNMi Server Details
    NNM HTTPS Port com.hp.ov.nms.spi.traffic-master.Nnm.https.port The HTTPS port that the primary NNMi server uses to communicate with the NNM iSPI Performance for TrafficMaster Collector
    NNM Password com.hp.ov.nms.spi.traffic-master.Nnm.password The administrator password for the primary NNMi server
    NNM Username com.hp.ov.nms.spi.traffic-master.Nnm.username The administrator user name for the primary NNMi server
    NNM Hostname com.hp.ov.nms.spi.traffic-master.Nnm.hostname The Fully Qualified Domain Name (FQDN) for the primary NNMi server
    NNM HTTP Port com.hp.ov.nms.spi.traffic-master.Nnm.port The HTTP Port that the primary NNMi server uses to communicate with the NNM iSPI Performance for TrafficMaster Collector
    Secondary NNMi Server Details (Applicable Only If the NNM iSPI Performance for Traffic is Configured for High Availability)
    NNM SECONDARY Username com.hp.ov.nms.spi.traffic-master.Nnm.secondary.username The administrator username for the secondary NNMi server
    NNM SECONDARY HTTPS Port com.hp.ov.nms.spi.traffic-master.Nnm.secondary.https.port The HTTPS port that the secondary NNMi server uses to communicate with the NNM iSPI Performance for TrafficMaster Collector
    NNM SECONDARY Hostname com.hp.ov.nms.spi.traffic-master.Nnm.secondary.hostname The Fully Qualified Domain Name (FQDN) for the secondary NNMi server
    NNM SECONDARY Present com.hp.ov.nms.spi.traffic-master.Nnm.secondary.present

    Specifies whether the secondary NNMi server is configured for High Availability and Application Failover

    True if Secondary NNM has been configured and failover enabled

    NNM SECONDARY HTTP Port com.hp.ov.nms.spi.traffic-master.Nnm.secondary.port The HTTP port that the secondary NNMi server uses to communicate with the NNM iSPI Performance for TrafficMaster Collector
    NNM SECONDARY Password com.hp.ov.nms.spi.traffic-master.Nnm.secondary.password The administrator password for the secondary NNMi server

    Primary Shared Drive Details
    NNM SPI Data Path com.hp.ov.nms.spi.traffic-master.Nnm.perfspidatapath

    The shared folder on the primary NNMi server that the Master Collector and NPS use for storing the data collected by the NNM iSPI Performance for Traffic
    Secondary Shared Drive Details (Applicable Only If NNM iSPI Performance for Traffic is Configured for High Availability)
    NNM SECONDARY SPI Data Path com.hp.ov.nms.spi.traffic-master.Nnm.secondary.perfspidatapath

    The shared folder on the secondary NNMi server that the Master Collector and NPS use for storing the data collected by the NNM iSPI Performance for Traffic
    NPS Details
    NPS Port com.hp.ov.nms.spi.traffic-master.nps.port

    The port that the Master Collector uses to communicate with the NPS server

    NPS and the NNM iSPI Performance for Traffic must use same mode of communication protocol. That is, if NPS uses HTTPS, the NNM iSPI Performance for Traffic must also use HTTPS protocol.
    NPS Sybase Username com.hp.ov.nms.spi.traffic-master.nps.sybase.user The administrator user name for the NPS database
    NPS Sybase Password com.hp.ov.nms.spi.traffic-master.nps.sybase.password The administrator password for the NPS database
    NPS Hostname com.hp.ov.nms.spi.traffic-master.nps.hostname The Fully Qualified Domain Name (FQDN) for the system where NPS and NNM iSPI Performance for Metrics are installed
  2. Specify the configuration value in the Value field.
  3. Click Save to save the modified value.

  4. The NNM iSPI Performance for Traffic validates your changes. If the values you specified are incorrect, the Installation Verification form displays an error message for the incorrect configuration setting.

  5. Restart the NNM iSPI Performance for TrafficMaster Collector to apply the changes.

Using this form, you can update the configuration parameters defined in the following properties files:

  • nnm.extended.properties
  • nps.extended.properties
  • nms-traffic-master.address.properties

You can find these properties files at the following location:

Windows:<Data_Dir>\nmsas\traffic-master\conf\

Linux:/var/opt/OV/nmsas/traffic-master/conf/

View Unresolved IPs

You can view the IP addresses of interfaces (which are capable of reporting the traffic flow data) that the NNM iSPI Performance for Traffic failed to resolve. The Unresolved NNM IP view in the NNM iSPI Performance for Traffic Configuration form enables you to view the list of IP addresses of interfaces that could not be resolved by the Network Node Manager i Software.

To view the unresolved IPs of flow reporting interfaces, click System Health > Unresolved NNMi IPs in the NNM iSPI Performance for Traffic Configuration form.

The view shows the following details:

  • IP address: IP address of the interface that is configured to report the traffic flow data.
  • Interface index: Index of the interface.
  • Last attempt time: Time-stamp of the last attempt made by the NNM iSPI Performance for Traffic to resolve the IP address.

Click Refresh iconRefresh to refresh the list of attempts.

Incident Types Supported by the NNM iSPI Performance for Traffic

The NNM iSPI Performance for Traffic supports the incident types listed below. All the incidents have Critical severity.

  1. InterfaceTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  2. InterfaceApplicationTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName for the application $application.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  3. InterfaceApplicationSiteTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName in site $siteName for an application $application.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  4. InterfaceSiteTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName for site $siteName.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  5. InterfaceTosTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName for the ToS $tos.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  6. InterfaceTosSiteTraffic: Signifies the following:
    • High traffic $mtype $metric reported through an interface $interfaceName on the node $nodeName for the ToS $tos in site $siteName.
    • Configured threshold: $configuredValue and Measured value: $reportedValue.
    • Measurement time is: $reportedTime
  7. NodeTraffic: Signifies that one or more interfaces on node: $node has breached the traffic thresholds, where:
    • $mtype is INGRESS or EGRESS
    • $metric is BANDWIDTH or VOLUME
    • $interfaceName is InterfaceName
    • $nodeName is nodeName
    • $configuredValue threshold condition
    • $reportedValue value reported
    • $reportedTime reporting time
    • $siteName is site name
    • $tos is tos.
    • $app is Application

Store and Analyze Flow Packets

The NNM iSPI Performance for Traffic provides you with a mechanism to store and analyze raw flow packets obtained from different sources by the Leaf Collector. When adding a new Leaf Collector, you can specify if you want to collect raw flow packets. After the NNM iSPI Performance for Traffic stores the flow packets on the Leaf Collector system, you can use the nmstrafficinspectiontool.ovpl utility to analyze the flow packets.

When you add a new Leaf Collector instance or edit an existing Leaf Collector instance, select true for the Store Flow in the File field. The Leaf Collector stores the received flow packets in the following directory:

  • On Windows:
    <Data_Dir>\nmsas\traffic-leaf\data\<Leaf_Collector_Instance>\<IP_Address_of_Source>
  • On Linux:
    /var/opt/OV/nmsas/traffic-leaf/data/<Leaf_Collector_Instance>/<IP_Address_of_Source>

    Use this feature only for troubleshooting. This option has a significant impact on the performance of the Leaf Collector.

In this instance:
<Data_Dir>: Data directory that you chose during the installation of the Leaf Collector.
<Leaf_Collector_Instance>: Name of the Leaf Collector instance
<IP_Address_of_Source>: IP address of the device where the flow packet originated.

To disable the mechanism to store flow packets:

  1. Go to the Leaf Collector view.
  2. Select the Leaf Collector instance for which you want to disable the flow packet storing mechanism.
  3. Click Open. A new form opens.
  4. In the new form, set Store Flow in File to false.
  5. To remove the existing flow packet files, remove the *.flow files from the following directory:
    • On Windows:
      <Data_Dir>\nmsas\traffic-leaf\data\<Leaf_Collector_Instance>\<IP_Address_of_Source>
    • On Linux:
      /var/opt/OV/nmsas/traffic-leaf/data/<Leaf_Collector_Instance>/<IP_Address_of_Source>

Do not delete the directories; delete only the *.flow files. If you delete the directory, the Leaf Collector fails to store flow packets when you enable the storing mechanism again.

In this instance:
<Data_Dir>: Data directory that you chose during the installation of the Leaf Collector.
<Leaf_Collector_Instance>: Name of the Leaf Collector instance
<IP_Address_of_Source>: IP address of the device where the flow packet originated.

View and Analyze Flow Packets

The nmstrafficinspectiontool.ovpl utility enables you to view and analyze the flow packets (*.flow files) that are stored in the following directory:

  • On Windows:
    <Data_Dir>\nmsas\traffic-leaf\data\<Leaf_Collector_Instance>\<IP_Address_of_Source>
  • On Linux:
    /var/opt/OV/nmsas/traffic-leaf/data/<Leaf_Collector_Instance>/<IP_Address_of_Source>

The raw flow packets are saved by the Leaf Collector with the following file name format:

<IP_Address_of_Source>_<Date>_<Time>_<FlowType>_<Leaf_Collector_Instance>.flow

In this instance:

<Data_Dir>: Data directory that you chose during the installation of the Leaf Collector.
<Leaf_Collector_Instance>: Name of the Leaf Collector instance.
<IP_Address_of_Source>: IP address of the device where the flow packet originated.
<Time>: The time (in the hour_minute format) when the collector starts storing the flow packet on the system.

<FlowType>: The type of the flow packet. Possible values are NetFlowV5, NetFlowV9, sFlow, IPFIX, and JFlow.

<Leaf_Collector_Instance>: Name of the Leaf Collector instance that receives the packet.

For example: 172.16.10.5_21-May-2010_11-20_NetflowV5_collector125.flow

To view stored flow packets:

  1. Log on to the Leaf Collector system with the root (Linux) or administrator (Windows) privileges.
  2. Go to the following directory:

    On Windows: <Data_Dir>\nmsas\traffic-leaf\data\<Leaf_Collector_Instance>\<IP_Address_of_Source>

    On Linux: /var/opt/OV/nmsas/traffic-leaf/data/<Leaf_Collector_Instance>/<IP_Address_of_Source>

  3. To view the contents of all the flow packet files stored by the Leaf Collector, run the following command:
    nmstrafficinspectiontool.ovpl
    The contents of all the flow packet files appear in the command line console in the following format:
    4. Router   SrcIP   DstIP   IPProtocol NFSNMPInputIndex NFSNMPOutputIndex SrcPort DstPort TCPFlags IPToS NumPacket NumBytes64 StartTime EndTime
    172.16.10.5   172.17.10.1   172.17.10.9   UDP                 11:20:15 PST 05/12/2010 11:30:17 PST 05/12/2010
  4. In addition to viewing the contents of all the flow packet files available in the directory, you can perform the following operations:
    • Filter the output
      You can filter out the contents of flow packets that are not of your interest by using the -filter option.
      To filter out flow packets, run the following command:
      nmstrafficinspectiontool.ovpl -[f|file] <FlowPacketFileName> -filter <filter_condition>,<filter_condition>,...
      In this instance, <filter_condition> is the filter condition created with one of the attributes of flow packets. The command shows the contents of the flow packets that match the filter condition. For example, the command nmstrafficinspectiontool.ovpl -filter SrcIP 172.17.10.* shows the contents of the flow packets that originated from systems with the given source IP address.
    • View selected attributes
      To view only select attributes of packet files, run the following command:
      nmstrafficinspectiontool.ovpl -[f|file] <FlowPacketFileName> -[hc|hidecolumns] <attribute_name>,<attribute_name>,...
      In this instance:
      <FlowPacketFileName> is the name of the flow packet file (*.flow file).
      <attribute_name>       is the name of the attribute that you want to hide.
    • View a single file
      To view the contents of a particular file, run the following command:
      nmstrafficinspectiontool.ovpl -[f|file] <FlowPacketFileName>
      In this instance, <FlowPacketFileName>is the name of the flow packet file (*.flow file).
      The contents of the file appear in the command line console.
    • Export the contents of packet files to CSV files
      To export the contents of the files into a CSV file, run the following command:
      nmstrafficinspectiontool.ovpl -[d|dir] <directoryPath> -csv -csvdir <csvDirectory> -csvname<csvFileName>
      In this instance:
      <directoryPath> is the full directory path where the flow packets are stored on the Leaf Collector.
      <csvDirectory>       is the directory on the Leaf Collector system where the CSV file is saved.
      <csvFileName> is the file name with which the Leaf Collector saves the CSV file.
    • Export the contents of a particular file to a CSV file
      To export the contents of a particular file to a CSV file, run the following command:
      nmstrafficinspectiontool.ovpl [-f|file] <FlowPacketFileName> -csv -csvdir<csvDirectory>-csvname <csvFileName>
      In this instance:
      <FlowPacketFileName>is the name of the flow packet file (*.flow file).
      <csvDirectory> is the directory on the Leaf Collector system where the CSV file is saved.
      <csvFileName> is the file name with which the Leaf Collector saves the CSV file.
    • Export filtered contents to a CSV file
      You can combine the -csv and -filter options to export filtered content to a CSV file.
      To export filtered content to a CSV file, run the following command:
      nmstrafficinspectiontool.ovpl -filter <filter_condition>,<filter_condition>,... -csv -csvdir <csvDirectory>-csvname<csvFileName>
      In this instance:
      <filter_condition> is the filter condition created with one of the attributes of flow packets. The command shows the contents of the flow packets that match the filter condition.
      <csvDirectory> is the directory on the Leaf Collector system where the CSV file is saved.
      <csvFileName> is the file name with which the Leaf Collector saves the CSV file.
    • Inspect the files based on the time range
      To inspect the files based on the time range, run the following commands:
      nmstrafficinspectiontool.ovpl -[d|dir]<directoryPath>-[fr|from]<fromTime>-[to]<toTime>
      In this instance:
      <directoryPath> is the full directory path where the flow packets are stored on the Leaf Collector.
      <fromTime>       is the start time ( in the MM/dd/yyyy HH:mm:ss format) from which you want to inspect the files.
      <toTime> is the end time ( in the MM/dd/yyyy HH:mm:ss format) after which you do not want to inspect the files.
      You can also combine the filter and hidecolumns options to inspect files based on a time range.
    • Export the contents from a directory to a CSV file based on time range
      To export the contents from a directory to a CSV file based on time range, run the following command:
      nmstrafficinspectiontool.ovpl -[d|dir]<directoryPath>-[f|from]<fromTime>-[t|to]<toTime>-csv -csvdir<csvDirectory>-csvname<csvFileName>
      In this instance:
      <directoryPath> is the full directory path where the flow packets are stored on the Leaf Collector.
      <fromTime> is the start time ( in the MM/dd/yyyy HH:mm:ss format) from which you want to inspect the files.
      <toTime> is the end time ( in the MM/dd/yyyy HH:mm:ss format) after which you do not want to inspect the files.
      <csvDirectory> is the directory on the Leaf Collector system where the CSV file is saved.
      <csvFileName> is the on the Leaf Collector system where the CSV file is saved.
    • View the error messages
      To print the errors on screen, run the following command:
      nmstrafficinspectiontool.ovpl [-f|file] <FlowPacketFileName> -e
      In this instance, <FlowPacketFileName>is the name of the flow packet file (*.flow file).
      The errors appear on the console.

For more information on the nmstrafficinspectiontool.ovpl command, see reference pages.

Contents of the Flow Packet Files

A flow packet file includes the following details in its content:

  • Router: The router or switch that sent the flow packet to the Leaf Collector.
  • SrcIP: IP address of the system where the IP flow originated.
  • DstIP: IP address of the destination system of the IP flow.
  • IPProtocol: IP protocol used by the flow.
  • NFSNMPInputIndex: SNMP index of the egress interface.
  • NFSNMPOutputIndex: SNMP index of the ingress interface.
  • SrcPort: Egress port.
  • DstPort: Ingress port.
  • TCPFlags: TCP flag of the traffic flow.
  • IPToS: Type of Service property of the traffic flow.
  • NumPacket: Number of packets in the traffic flow.
  • NumBytes64: Number of bytes in the traffic flow.
  • StartTime: Time when the traffic flow originated from the source system.
  • EndTime: Time when the traffic flow arrived on the destination system.

Limit the Number of the Flow Packet Files

Once configured, the Leaf Collector continues to create flow packet files on the system, which eventually consume a significant amount of disk space. When the available disk space of the Leaf Collector system decreases to 10%, the Leaf Collector automatically stops creating any new flow packet files. The NNM iSPI Performance for Traffic provides you with a mechanism to control the maximum number of flow packet files on the system.

To limit the number of flow packet files:

  1. Log on to the Leaf Collector system.
  2. Go to the following location:
    • On Windows:
      <DataDir>\nmsas\traffic-leaf\conf
      In this instance, <DataDir> is the directory where you chose to place the data files while installing the Leaf Collector.
    • On Linux:
      /var/opt/OV/nmsas/traffic-leaf/conf
  3. Open the nms-traffic-leaf.address.properties file with a text editor.
  4. Set the max.dump.hours property to the number of hours for which you want to store the flow packet files.
  5. Save the file.
  6. Enable the packet file storing mechanism.
    After creating a flow packet file, the Leaf Collector retains the file for the number of hours specified for the max.dump.hours property.
    For example, if you set the max.dump.hours property to 1, the Leaf Collector instance retains a flow packet file only for 1 hour after its creation.

List the Undefined Applications for a Leaf Collector

When a flow record contains applications that do not satisfy any existing application mapping rule, the NNM iSPI Performance for Traffic marks these applications as "Undefined Application".

The NNM iSPI Performance for Traffic Undefined Applications form enables you to list and view the applications for which no application mapping exists.

If you see these Undefined Applications generating significant volume of traffic, you can create the application mappings to identify the applications contributing to traffic volume.

The Undefined Applications form (under Application Mapping Configuration) lists the following parameters:

Column Name Description
Destination Port The port that does not have any application mapping configured
Number of Bytes Traffic volume generated from this port
Node Name The node for which the port is configured
Interface Name The interface for which the port is configured
Ingress/Egress Type of traffic generated from the port

Disable Interfaces to Report Flow Data

You can configure the NNM iSPI Performance for Trafficto stop processing flows from select interfaces. As a result, flows reported by the selected interfaces are not analyzed and those flows do not contribute to the reports. The NNM iSPI Performance for Traffic provides you with a command line utility to perform this configuration.

To configure the NNM iSPI Performance for Traffic to stop processing flows:

  1. Log on to the Master Collector system with the root or administrator privileges.
  2. Go to the following directory:
    On Windows:
    <Master_Install_Dir>\nonOV\traffic-master\bin
    On Linux:
    /opt/OV/nonOV/traffic-master/bin
  3. Run the following command:
    nmstrafficdisableflow.ovpl --username=<username> --password=<password> --uuid=<interface_uuid>
    In this instance,
    <username> is the user name of the Master Collector system user (created during installation)
    <password>     is the password for the Master Collector system user (created during the installation)
    <Interface_UUID> is the UUID of the flow reporting interface that you want to exclude.

    The status of the interface in the Flow Reporting Interfaces view appears as Disabled. As a result, the license consumption of the NNM iSPI Performance for Traffic is also reduced accordingly. For example, if you stop processing flows from a NetFlow interface, the license consumption of the NNM iSPI Performance for Traffic gets reduced by five iSPI points.

    To find the UUID of an interface, go to the Interfaces View (inventory) in the NNMi console and select the interface. Open the Interface form, and then go to the Registration tab. The UUID of the interface is displayed in the Registration tab.

To include the flows from the interface again, run the following command:

nmstrafficenableflow.ovpl --username=<username> --password=<password> --uuid=<interface_uuid>

View the NNM iSPI Performance for Traffic Maps

The NNM iSPI Performance for Traffic maps help you understand traffic flows on your network. NNM iSPI Performance for Traffic maps obtain information from all the nodes that send traffic flow to your network.

The following NNM iSPI Performance for Traffic maps are available in the NNMi console:

  • Destination and Application Map
  • Top Sources by Destination Map
  • Traffic Path View

You can view all the top destinations and applications that contribute to the traffic flow in your network at any given point of time.

Access Maps

To access the maps:

  1. Select the table view you want from the Workspaces navigation panel. (For example, select the Inventory workspace, Nodes view.)
  2. In the table view, click the selection box corresponding to the required node.
  3. Select the Actions menu in the main toolbar and select Traffic Maps.
  4. Select the required map from the list.
  5. Filter the information as required.
  6. Click Get Data in the selected map form.

Types of Maps

The NNM iSPI Performance for Traffic shows the following types of maps:

  • Destination and Application Map: This map displays the top destinations and applications that contribute to the traffic flow to your network. If the applications are directly connected to an IP address, the IP address is considered a destination. Some destination IP addresses may be connected to multiple applications. The map is neither a network topology map nor a device centric map. It represents the logical views of traffic flows in a network. Top N means top N application and top N destinations grouped together.
  • Top Sources by Destination Map: This map displays the top source IP addresses that contribute to the traffic flow to a destination. You can get the information about the top contributors of traffic on your network. The map is displayed based on the IP address specified in the NNMi console. This selected IP address is considered as the source of the traffic flow. The IP address of the node from which the map is launched, should be recognized by the respective Leaf Collector.
    This map enables you to:
    • View the traffic flow heading to any destination IP address in the network. It is not necessary for the IP address to be managed by NNMi.
    • Generate the logical views of traffic flowing from the Top N sources to the specified destination in a network. This map is neither a network topology map nor a device centric map.
    • Display the traffic flowing from each IP address if a flow generator (router or switch) has multiple IP addresses. The colors of destination IP addresses displayed in the NNM iSPI Performance for Trafficmap are not associated with the status colors in NNMi.
  • Traffic Path View: This map displays the flow of network traffic. The NNM iSPI Performance for Traffic calculates the route of data flow along the Layer 3 path between two nodes (end nodes or routers) that are enabled to export flows and presents a map of that information on the Traffic Path View. To display meaningful information in the Path View map, make sure that you select valid IP addresses in the Source Node and Destination Node fields. This map enables you to:
    • Generate a topology map where the NNM iSPI Performance for Traffic information is overlaid on the NNMi information.
    • Display the direction of the traffic flow.
    • Deduce the metric data on the inflow side based on the reported flows on the first flow exporter in the path.
    • Deduce the destination metric data by the last flow exporter on the path.
    • Query the destination host IP address in the database for IP addresses entered in the map controls and Destination Host Name for the FQDN. When accessing the Traffic Path view map, besides applying the common filters, in the Source and Destination fields, you must designate the IP addresses at both ends of the path using either the IPv4 address.

Global Network Management Environment

You can deploy the NNM iSPI Performance for Traffic in the Global Network Management (GNM) setup, which consists of regional NNMi management servers and a global NNMi management server.

In a GNM setup, you can add Master Collector and Leaf Collectors that belong to a different regional manager to your local configuration as remote collectors.

The NNM iSPI Performance for Traffic offers full support for deployment in a Global Network Management environment. Each instance has the following components:

  • NNMi
  • Network Performance Server
  • The NNM iSPI Performance for TrafficMaster Collector
  • The NNM iSPI Performance for TrafficLeaf Collectors

The NNMi in the Global Manager receives data from the regional managers. The Master Collector in the global manager can be configured to receive data from the regional Master Collectors in the following ways:

  • The Master Collector in the global manager can receive data from the Master Collector in the regional manager. In this case, you must add the regional Master Collector as a remote Master source in the Global Master Collector. This ensures that the complete set of data received by the regional Master Collector is forwarded to the Global Master Collector. In the above scenario, the global Master Collector receives data processed by both Traffic Leaf 1 and Traffic Leaf 2.
  • The Master Collector in the global manager can receive data directly from a regional Leaf Collector system, bypassing the regional Master Collector. In this case, the regional Leaf Collector (Traffic Leaf 3 in the above scenario) can be added as a leaf remote source to the global Master Collector. This ensures that the data received by all the Leaf Collectors on the remote Leaf Collector system is sent to the regional Master Collector as well as the global Master Collector. The regional Master Collector or the regional Leaf Collector can only be configured to send data to the global Traffic Master Collector. The global Master Collector cannot administer and manage these components.

Best Practice

Add all the regional Master Collectors as remote Master sources to the global Master Collector.

Add Remote Leaf Collectors

The NNM iSPI Performance for Traffic Configuration form enables you to add Leaf Collectors that belong to a different regional NNMi to your local configuration.

To add a remote Leaf Collector:

  1. In the NNM iSPI Performance for Traffic Configuration form, click Leaf Configuration > Leaf Remote Sources.
  2. In the Leaf Remote Sources view, click Add iconAdd. A new form opens.
  3. In the new form, specify the following details:
    • Remote Leaf Hostname: Type the hostname of the remote Leaf Collector system.
    • Leaf Password: Type the password of the Leaf Collector configured during the installation of the collector.
    • JNDI Port: Type the JNDI port number for the Leaf Collector system. 11099 is the default JNDI port number.
    • Use Encryption: Enable this option if you want the global Master Collector to use secure sockets layer encryption (HTTPS/SSL) to access the remote Leaf Collector system. This option is disabled by default.

      If the Master Collector is not installed on the NNMi management server, you must import certificates from the Leaf Collector to the Master Collector to use encryption to access the Leaf Collector. For more information, see the Enabling Security between the Master Collector and the Leaf Collector section in the Network Node Manager iSPI Performance for Traffic Software Interactive Installation Guide.

      If the Master Collector is installed on the NNMi management server, you can configure the global network management feature to use self-signed certificates. For more information, see the Configuring the Global Network Management Feature to use Self-Signed Certificates section in the Network Node Manager i Software Deployment Reference Guide.

    • HTTP(S) Port: Type the port number of the Leaf Collector system:
      • Type the HTTP port number if you do not select the Use Encryption option. 11080 is the default HTTP port number of the Leaf Collector system.
      • Type the HTTPS port number if you select the Use Encryption option. 11043 is the default HTTPS port number of the Leaf Collector system.
  4. Click Save & Close.

Modify Remote Leaf Collectors

The NNM iSPI Performance for Traffic Configuration form enables you to edit the existing remote Leaf Collectors in your configuration.

To modify a remote Leaf Collector:

  1. In the NNM iSPI Performance for Traffic Configuration form, click Leaf Configuration > Leaf Remote Sources.
  2. In the Leaf Remote Sources view, select a Leaf Collector, and then click Open iconOpen. A new form opens.
  3. In the new form, you can modify the following:
    • Leaf Password
    • JNDI port
    • Use Encryption
    • HTTP(S) Port
  4. Click Save & Close.

Add Remote Master Collectors

The NNM iSPI Performance for Traffic Configuration form enables you to add Master Collectors that belong to a different regional NNMi to your local configuration. You can use this procedure to associate all the regional managers with the global manager.

To add a remoteMaster Collector:

  1. In the NNM iSPI Performance for Traffic Configuration form, click Master Configuration > Master Remote Sources.
  2. In the Master Remote Sources view, click Add iconAdd. A new form opens.
  3. In the new form, specify the following details:
    • Remote Master Hostname: Type the hostname of the remote Master Collector system.
    • Master Password: Type the password for the Master Collector configured during the installation of the Master Collector.
    • JNDI Port: Type the JNDI port number for the Master Collector system. 12099 is the default JNDI port number.
    • Use Encryption: Enable this option if you want the global Master Collector to use secure sockets layer encryption (HTTPS/SSL) to access the remote Master Collector system. This option is disabled by default.

      If the Master Collector is not installed on the NNMi management server, you must import certificates from the Leaf Collector to the Master Collector to use encryption to access the Leaf Collector. For more information, see the Enabling Security between the Master Collector and the Leaf Collector section in the Network Node Manager iSPI Performance for Traffic Software Interactive Installation Guide.

      If the Master Collector is installed on the NNMi management server, you can configure the global network management feature to use self-signed certificates.

      If the Master Collector is installed on the NNMi management server, you can configure the global network management feature to use self-signed certificates.

    • HTTP(S) Port: Type the port number of the Master Collector system.

      • Type the HTTP port number if you do not select the Use Encryption option. 12080 is the default HTTP port number of the Master Collector system.

      • Type the HTTPS port number if you select the Use Encryption option. 12043 is the default HTTPS port number of the remote Master Collector system.

  4. Click Save & Close.

Modify Remote Master Collectors

The NNM iSPI Performance for Traffic Configuration form enables you to edit the existing remote Master Collectors in your configuration.

To modify a remote Master Collector:

  1. In the NNM iSPI Performance for Traffic Configuration form, click Master Configuration > Master Remote Sources.
  2. In the Master Remote Sources view, select a Master Collector, and then click Open iconOpen. A new form opens.
  3. In the new form, you can modify the following:
    • Master password
    • JNDI port

    • Use Encryption

    • HTTP(S) Port
  4. Click Save & Close.

Related Topics

Accessing Details of Traffic Data Sources

Send Help Center feedback