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 > Security Configuration > Communication Configuration > Configuring SSL Communications for Web Access and RMI Communications

Configuring SSL Communications for Web Access and RMI Communications

NNMi includes a suite of default ciphers that are used in configuring Secure Sockets Layer (SSL) in Web access and Java Remote Method Invocation (RMI) communications. The ciphers are listed in the nms-jboss.properties file.

Caution Adding or removing ciphers from the cipher list without the approval of is not supported; doing so may cause damage to the product or cause the product to become inoperable.

Requirement for New NNMi 10.30 Installations

New installations of NNMi support only TLS v1.2 protocol by default. However, to be able to discover and monitor ESXi 5.1 hypervisors, NNMi is required to use the TLSv1 cryptographic protocol.

To configure NNMi to support the TLSv1 cryptographic protocol for device communication:

Note This procedure enables NNMi to use less secure cryptographic protocols that are not FIPS 140-2-certified. This is a global change and may reduce the security of the product.

Log on to the NNMi management server.
Open the following file with a text editor:
- Windows: %NnmDataDir%\nmsas\NNM\server.properties
- Linux: /var/opt/OV/nmsas/NNM/server.properties
Update the com.hp.ov.nms.ssl.PROTOCOLS property to include the value TLSv1.

If the property does not exist, add the following line:

com.hp.ov.nms.ssl.PROTOCOLS=TLSv1.2,TLSv1.1,TLSv1
Configure NNMi to allow protocols and algorithms that are not FIPS-certified:
1. On the NNMi management server, go to the following directory:
  - On Windows: %nnminstalldir%\newconfig\HPNmsServStgs\Windows
  - On Linux: /opt/OV/newconfig/HPNmsServStgs/Linux
2. Copy the java.security file, and then place the copied file in the following directory:
  - On Windows: %nnmdatadir%\conf\nnm
  - On Linux: /var/opt/OV/conf/nnm
Restart the NNMi processes by running the following commands:
- On Windows:
  1. %nnminstalldir%\bin\ovstop -c
  2. %nnminstalldir%\bin\ovstart -c
- On Linux:
  1. /opt/OV/bin/ovstop -c
  2. /opt/OV/bin/ovstart -c

Send Help Center feedback