Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- HPE Network Node Manager (NNMi) Integration
- Overview
- Supported Versions
- NNMi - UCMDB Integration Architecture
- Topology
- How to Run NNMi–UCMDB Integration
- How to Manually Add the IpAddress CI of the NNMi Server
- How to Set Up HPE NNMi–HPE UCMDB Integration
- NNMi Integration Job
- How to Customize Integration
- Troubleshooting and Limitations – NNMi Integration
NNMi Integration Job
Parameter |
Description |
---|---|
NNMiHost | The host name to use with the integration. You must fill in this parameter if FIPS is enabled. NNMiHost has priority over IP address, which means instead of IP address, NNMiHost will be used if it is filled in. |
credentialsId | The credential used for the integration. |
discoverDisabledIps |
Defines whether the integration should discover disabled IP addresses. When setting to false, the integration does not discover disabled IP addresses. Default: false. |
discoverLayer2 |
Defines whether the integration should discover the Layer2Connection CIs from NNMi. When set to true, the integration fetches all the Layer2Connections-related data, iteratively querying for a specified number of Layer2Connections from NNMi (based on value of the pageSizeLayer2 parameter), then querying for Network Interfaces on the ends of Layer2Connection and Nodes hosting these interfaces with instant push of collected topology to UCMDB. Default: true |
discoverNodes |
Defines whether the integration should discover all the Nodes that are registered in NNMi, regardless of their inclusion into Layer2 Topology or VLANs. When set to true, integration fetches all the Nodes with connected IpAddresses, Interfaces, HardwareBoards, Physical Ports and IpSubnets, iteratively querying for a specified number of Nodes with related data from NNMi (based on value of the pageSizeNodes parameter) and instantly pushing collected topology into UCMDB. Default: true |
discoverNonManagedInterfaces |
Defines whether the integration should discover non-managed interfaces. When set to false, the integration does not discover non-managed interfaces. Default: false. |
discoverNonManagedNodes |
Defines whether the integration should discover non-managed nodes. When set to false, the integration does not discover non-managed nodes. Default: false. When this parameter is set to true, discoverDisabledIps and discoverNonManagedInterfaces are ignored for non-managed nodes; the integration will discover everything, including disabled ips and non-managed interfaces. |
discoverPhysicalPorts |
Defines whether the integration should discover physical ports. When set to false, the integration does not discover physical ports. Default: false. When this parameter is set to false, the integration does not discover VLANs and HardwareBoards. |
discoverVlans |
Defines whether the integration should discover all the VLANs that are registered in NNMi. When set to true, integration fetches all the VLANs with member Physical Ports, Hardware Boards and Nodes hosting those Physical Ports and Node-related topology, iteratively querying for a specified number of VLANs (based on the value of pageSizeVlans parameter), getting all the necessary related topology and instantly reporting it back to UCMDB. Default: true This parameter is ignored if discoverPhysicalPorts is set to false. |
discoveryMode |
Specifies the adapter's mode of execution, either related or full. Default: related
|
pageSizeLayer2 |
Defines the number of Layer2Connection CIs to fetch from NNMi per one query. Default: 5 |
pageSizeNodes |
Defines the number of Nodes to fetch from NNMi per one query. Default: 10 |
pageSizeVlans |
Defines the number of VLANs to be queries from NNMi per one query. Default: 1 |
remoteJVMArgs | The JVM parameters that should be passed to the remote process. |
remoteJVMClasspath | The external JVM classpath. |
requestCustomAttributes |
Enables global querying for custom attributes of entities in the script. The script must still be modified to read the values and report them (this code modification is expected to be made by the customer). Without modification to the script, setting this parameter to true has no effect. For performance reason, by default, custom attributes are not read from the NNMi server . Default: false |
runInSeparateProcess |
Defines whether to run the adapter in the external JVM. Default: false |
-
Composition
-
Containment
-
HardwareBoard
- Interface
-
IPAddress
-
IpSubnet
-
Layer2Connection
-
Membership
-
Node
-
PhysicalPort
-
Realization
- Vlan
Note To view the topology, see Topology.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: