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 > NNMi Communications > Configure Communications > Device Support Using the Network Configuration Protocol (NETCONF) > Network Configuration Protocol (NETCONF) Operations

Network Configuration Protocol (NETCONF) Operations

Details of NETCONF communication between NNMi and the managed device are transparent to the NNMi user. However, the following overview may be helpful for troubleshooting:

A NETCONF client (management application, such as NNMi) establishes an SSH connection with the NETCONF server (subsystem) on the managed device. Valid SSH user name and password credentials must be specified by the client and authenticated by the device.
The client application and device exchange capabilities in the form of <hello> messages.
The client initiates requests to the device in the form of Remote Procedure Call (RPC) messages; including standard <get> or <get-config> operations, plus any vendor-specific operations that are defined for the device.
The device responds with results of the operations in the form of RPC reply messages.
When the client application has finished sending requests and processing the responses, it sends a <close-session> RPC message to the device.
The device acknowledges with an <ok> RPC reply message.
Finally, both sides terminate the SSH connection.

Send Help Center feedback