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 |
|
- Supported Protocols
- AMQP Protocol
- AS400 Protocol
- AWS Protocol
- CA CMDB Protocol
- CIM Protocol
- Generic DB (SQL) Protocol
- Generic Protocol
- HP Network Automation Java Protocol
- HP SIM Protocol
- HTTP Protocol
- JBoss Protocol
- LDAP Protocol
- NetApp Protocol
- NetApp SANscreen/OnCommand Protocol
- NNM Protocol
- NTCMD Protocol
- PowerCmd Protocol
- PowerShell Protocol
- Remedy Protocol
- Salesforce Rest Protocol
- SAP JMX Protocol
- SAP Protocol
- ServiceNow Protocol
- Siebel Gateway Protocol
- SNMP Protocol
- SSH Protocol
- Telnet Protocol
- TIBCO Protocol
- UCS Protocol
- UDDI Registry Protocol
- Universal Discovery Protocol
- vCloud Protocol
- VMware Infrastructure Management (VIM) Protocol
- WebLogic Protocol
- WebSphere Protocol
- WMI Protocol
Telnet Protocol
Parameter |
Description |
---|---|
Port Number |
The port number. By default a Telnet agent uses port 23. If you are using a different port for Telnet in your environment, enter the required port number. |
Connection Timeout |
Time-out in milliseconds after which the Probe stops trying to connect to the remote machine. For UNIX platforms: If your server is slow, it is recommended to change Connection Timeout to 40000. |
Authentication Method |
Choose one of the following authentication options to access Telnet:
|
Username |
The name of the user needed to connect to the host. |
Password |
The password of the user needed to connect to the host. |
Prompts and Responses |
(Enabled when the The following is an example of prompts and expected responses: Prompt: Please enter your user name. Response: Shelly-Ann Prompt: What is your age? Response: 21 Prompt: This computer is HP property. Press y to enter. Response: y To create these prompts and responses, enter the following strings in the fields, separated by commas: Prompts: user,age,enter Response: Shelly-Ann,21,y You can enter the full string as it appears in the Telnet prompt, or you can enter a key word, for example, user. DFM maps this word to the correct prompt. |
Note When the CyberArk integration is enabled, two radio buttons (Regular Credential and External Vault) are enabled. The existing Username and Password parameters are grouped under the Regular Credential radio button, and CyberArk integration specific parameters Type and Reference are enabled and grouped under the External Vault radio button, as described in the table below.
Parameter |
Description |
---|---|
Regular Credential |
Enabled when CyberArk integration is enabled. Select this radio button to use regular credential as before.
|
External Vault |
Enabled when CyberArk integration is enabled. Select this radio button to use an external credential vault.
|
Privileged Mode Properties
Policy |
Select one of the following options:
|
Mode |
Based on your Policy selection, select the Mode. For Privileged Mode, select one of the following options:
For Sudo-like, select one of the following options:
For Privileged Mode or Sudo-like, select an option in each panel. |
<Privileged Mode/Su> |
When you select Privileged Mode as the policy and Su as the mode, the following fields are relevant:
|
<Privileged Mode/Enable> |
When you select Privileged Mode as the policy and Enable as the mode, the following fields are relevant:
|
<Privileged Mode/Custom> |
When you select Privileged Mode as the policy and Custom as the mode, the following fields are relevant:
|
<Sudo-like/Sudo> |
When you select Sudo-like as the policy and Sudo as the mode, the following fields are relevant:
|
<Sudo-like/Custom> |
When you select Sudo-like as the policy and Custom as the mode, the following fields are relevant:
|
<Privileged Mode or Sudo-like> | When you select Privileged Mode or Sudo-like as the policy, you have the option to configure both types of policy. Each policy appears in a separate panel with the relevant options as described for each policy/mode selection. |
Command List |
Enter a list of commands that can be executed with the current policy/mode selection. Commands must be separated by commas. This field accepts a sudo command that prompts for the user's password. To select all possible commands to be executed in the current policy/mode, enter an asterisk (*) in this field. You can also select commands by pattern matching and pattern completion using Python/Jython regular expressions. For example, entering *uname would select all of the following expressions:
Note
|
-
Problem: Failure to connect to the TTY (SSH/Telnet) agent.
Solution: To troubleshoot connectivity problems with the TTY (SSH/Telnet) agent, use a utility that can verify the connectivity with the TTY (SSH/Telnet) agent. An example of such a utility is the client tool PuTTY.
Limitation: The Telnet protocol does not support discovery of Windows Telnet servers.
-
Problem: Discovery job(s) fail with error message “Time out exception”.
Solution 1. Increase the value of the shellGlobalCommandTimeout parameter in globalSettings.xml.
Solution 2. Check the shell of the discovery user on the discovered destination. The command line for the ksh(korn shell) has a limit of 256 characters. Some discovery commands exceed that limit and can cause a “Time out exception” error message. In this case (a) Change the default shell for the discovery user from ksh to bash; or (b) Consult with the system administrator to determine if it is possible to increase the maximum command line size for korn shell on the problematic destination.
Note If you use the SSH or Telnet credentials for discovery, it is recommended to add the following folders to the system path:
-
/sbin
-
/usr/sbin
-
/usr/local/sbin