Home  Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > UNIX Remote Preferences > Unix Server Profile Settings



Unix Server Profile Settings

The following describes the settings used for Unix Server Profiles.

Main Settings

You use the Main Settings section to enter information that defines the Unix Server Profile. Complete the Main Settings section for the Unix Server Profile as described below.

Host

The IP address or host name of the server you wish to monitor. If you are using the HTTP method of monitoring, enter the full URL of the CGI script (for example: http://demo.thiscompany.com/cgi-bin/run.sh) To use the same login credentials to configure multiple servers at the same time, enter the server addresses separated by commas. For example, if you are using NetBIOS to connect to other servers, you can enter a comma-separated string of server addresses such as: serveraddress1,serveraddress2,serveraddress3,serveraddress4. When you complete the other required entries on the form and click OK, SiteScope creates a new remote connection profile for each server address in the list.

Note: When adding multiple servers in a single operation, SiteScope does not automatically test connectivity with each server. You can click Test in the table listing the Unix Servers to test connectivity after the profiles have been added.

Login

The login for the remote server.

Password

The password for the remote server or the passphrase for the SSH key file. When using SSH authentication with public/private key based authentication enter the passphrase for the identity file here.

Name

A name by which the remote machine should be known in SiteScope. This name will appear in the drop-down list of the Choose Server page for monitors that can connect to remote servers.

Trace

Check this option to trace messages to and from the remote server in the RunMonitor.log file

OS

The operating system running on the remote server. This is required so that the correct information can be obtained from that server. Use the drop-down list feature to select from the default operating systems. SiteScope currently includes default support for the following versions of UNIX:

AIX
FreeBSD
HP/UX
HP/UX 64-bit
Linux
MacOSX
OPENSERVER
SCO
SGI Irix
Sun Solaris
Tru64 5.x
Tru64 Pre 4.x (Digital)

For servers running versions of UNIX which are not included in the list, see the section on Remote UNIX Adapter Kit in the Advanced SiteScope Topics section.

Method

The method for connecting to the server. The currently supported methods are:

Connection Method
Description
Telnet
Log in to the remote server using Telnet
SSH
Log in to the remote server using the SSH protocol. This may require additional software and setup depending on the version of UNIX you are working with. See the document on Secure Shell in the Advanced SiteScope Topics section for more information on SSH requirements.
Rlogin
Log in to the remote server using the Rlogin protocol
HTTP
Connect to an HTTP server on the remote server and run the command via a CGI. For this method the Login and Password are optional and are used for authorizing SiteScope to log on to the remote machine if required.

Prompt

This is the prompt output when the remote system is ready to handle a command - the default is #

Login Prompt

This is the prompt output when the system is waiting for the login to be entered - the default is "ogin:"

Password Prompt

This is the prompt output when the system is waiting for the password to be entered - the default is "assword:"

Secondary Prompt

In the case the telnet connection to the remote server causes the remote server to prompt for more information about the connection, enter the secondary prompt(s) here. Separate multiple prompt string by commas (,). For example, for Telnet connections to some remote servers, the remote server may ask what terminal type should be emulated for the connection. In this case you might need to enter Terminal type? as the secondary prompt. The response to the secondary prompt is entered in the Secondary Response box below.

Secondary Response

Enter the response(s) to any secondary prompts required to establish connections with this remote server. Separate multiple responses with commas (,).

Initialize Shell Environment

Enter any shell commands to be executed at beginning of the session. Separate multiple commands with a semicolon (;). You use this option to specify shell commands to be executed on the remote machine directly after a Telnet or SSH session has been initiated. These commands can be used to customize the shell for each SiteScope remote. Some example cases include:

Remote Machine Encoding

If the remote server is running an operating system version that uses a different character encoding than the server on which SiteScope is running, enter the encoding to use for the remote server. This will enable SiteScope to display encoded content correctly. By default, SiteScope uses Cp1252 encoding. Examples of other encodings are Cp1251, Cp1256, Shift_JIS and EUC_JP.

Advanced Settings

You use the Advanced Settings section to customize the Unix Server Profile. Complete the entries as needed and click the Add or OK button to save the settings.

Description

Enter an optional description text to further describe this Unix Server Profile. For example, you may enter some text describing the purpose or conditions relating to the use of this Unix Server Profile.

SSH Connection Method

The client to use for this connection. The currently supported clients are:

Client
Description
Internal Java Libraries
Connect using the Java SSH client integrated with SiteScope.
Plink/External SSH Client
Connect using an external SSH client. On NT, SiteScope ships with Plink on UNIX or Linux SiteScope will use an installed client such as OpenSSH.

SSH Port Number

Enter the port that the remote SSH server is listening on.

Disable Connection Caching

Check this option to turn off connection caching for this remote. By default SiteScope caches open connections.

Connection Limit

This setting controls the number of open connections that SiteScope will allow for this remote. If you have a large number of monitors configured to use this connection then set this number high enough to relieve the potential bottleneck.

Note: This setting does not effect the running of tests for a remote, tests will always create a new connection.

SSH Authentication Method

The authentication method to use for SSH connections. The currently supported methods are:

Authentication
Description
Password
Authenticate using a password.
Key File
Authenticate using public/private key authentication. When this option is selected SiteScope uses the private key in the file SiteScope/groups/identity to authenticate. The corresponding public key must be listed in the authorized_keys file on the remote host. See the document on Secure Shell in the Advanced SiteScope Topics section for more information on SSH requirements.

Key File for SSH connections

Select the file that contains the private key for this connection. The default key file is SiteScope\groups\identity. This setting only applies when the authentication method is Key File .

SSH Version 2 Only

Check this option to force SiteScope to use SSH protocol version 2 only. This option only applies when using the integrated Java Client. See the section on Configuring SSH Using an External Client for information on configuring an external SSH client to use SSH2 protocol.

Custom Commandline

Enter a custom commandline for a remote using the External Client. This option can be used when needing to pass specific options to the external client being executed. Valid substitution variable are

Use the following steps to add a remote UNIX server profile to SiteScope.




Copyright 2006 Mercury Interactive Corporation