Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure the NNMi User Interface > Configure Maps > Configure a Path View Map

Configure a Path View Map

Configuring a Path View map is useful when you have two or more areas of your network which are separated by undiscovered devices, such as service provider nodes. NNMi enables you to configure a Path View map that traverses undiscovered regions of your network. To configure this kind of Path View map, create a PathConnections.xml file that defines the following:

Required. A Start node for each <CONNECT> to be included in the Path View map

Note The Start node specified must be a Router or Switch-Router device that is managed by NNMi.
Optional. A unique identifier for a <CONNECT>
Optional. The outbound interface from each Start node per <CONNECT>
Required. Any number of undiscovered nodes you want to be included in the map between each <CONNECT>
Optional. An End node for a <CONNECT> to be included in the Path View map.

Note The End node specified must be a Router or Switch-Router device that is managed by NNMi.
Optional. The inbound interface to each End node per <CONNECT> specified.

Each time NNMi determines a node in the Path View, NNMi checks whether the node is specified as a Start node in the PathConnections.xml file. If the node is specified as a Start node in PathConnections.xml, each <CONNECT> configured in PathConnections.xml is inserted in the Path View map.

Note (NNMi Advanced, plus Route Analytics Management System (RAMS) for MPLS WAN) NNMi can use RAMS data to determine router paths. When RAMS data is used to determine the router paths, NNMi ignores the PathConnections.xml file.

(NNMi Advanced) Path View works only with IPv4 addresses. The NNMi Advanced IPv6 address values are not valid choices for Path View. Any devices in your network that are configured with IPv6 addresses cannot be displayed on Path View maps.

To configure a Path View map:

Using the required format, create a PathConnections.xml file in the following location (see Manage environment variables for more information):

Windows
%NnmDataDir%/shared/nnm/conf/PathConnections.xml

Linux
$NnmDataDir/shared/nnm/conf/PathConnections.xml

The following table describes each of the file elements and its format requirements. (Also see the sample file)

Note Each segment of the path that you specify using the <CONNECT> element is directional. If you want to view the path between two nodes in both directions, make sure you include the Start and End nodes for each direction. You should also include the inbound interface for the Start node. If you do not limit the possible routers by including the inbound interface for the Start node, Path View might find additional routers in the path.

Elements for the Path View Configuration File
Element Descriptions
`<CONNECTIONS>` Required parent element. The file must include only one `<CONNECTIONS>` element.
`<CONNECT>` Specifies a segment of the path. Each `<CONNECT>` designates a start and stop location for the `<CONNECT>`. The file can include more than one `<CONNECT>` element.
`<ID>` `C1</ID>` Optional. Identifies the connection. NNMi uses the ID value you enter when reporting errors for a `<CONNECT>`. If you do not provide an ID value for the path between a Start and End node, any error message for the `<CONNECT>` displays `Not Applicable` rather than the unique identification value.
`<START> <IP_OR_DNS>xxx.xx.xxx.x</IP_OR_DNS> <OUTBOUND_INTERFACE_IFINDEX>x</OUTBOUND_INTERFACE_IFINDEX> <NEXT_HOPS> <HOP>xxx.xx.xxx.x</HOP> <HOP>xxx.xx.xxx.x</HOP> </NEXT_HOPS> </START>` Specifies the node where a segment of the path starts. You provide values for the following elements: `<IP_OR_DNS>` provides the name or IPv4 address of a node in your network. See Configure the Node Name Strategy for more information about node names. Optional. `<OUTBOUND_INTERFACE_IFINDEX>` designates which of the Start node's interfaces to use for this segment of the path. `<NEXT_HOPS>` designates one or more specific IPv4 addresses or nodes that you want to be included in the path.
`<END> <IP_OR_DNS>xxx.xx.xxx.x</IP_OR_DNS> <INBOUND_INTERFACE_IFINDEX>x</INBOUND_INTERFACE_IFINDEX> </END>` Specifies the node where the `<CONNECT>` ends. You provide values for the following elements: `<IP_OR_DNS>` provides the name or IPv4 address of a node in your network. Optional.`<INBOUND_INTERFACE_IFINDEX>` designates which of the End node's interfaces to use for this segment of the path.
`</CONNECT>` Required. Designates the end of the XML code that defines one segment of your path view.
`</CONNECTIONS>` Required parent element. Designates the end of the XML code that defines your path view.

When viewing Path View maps that are configured using the PathConnections.xml file, note the following:

If the <END> element is not specified, NNMi connects directly to the Destination node to complete the path.
If the <END> element is specified, then the associated <IP_OR_DNS> specifies a discovered node as the End node of this segment of your Path View.

Send Help Center feedback