The Service Name property identifies an entry in the services file that completes the definition of the communications link that Operations Sentinel uses to connect to the managed system. The Service Name property value defaults to spo_telnet, which assumes you are monitoring the system using TELNET. If you are monitoring using any other method, you must change this value by editing the Service Name property.
Multiple UNIX and Linux systems can have the same Service Name, as long as their Network Names differ. This is useful for TELNET connections, since all TELNET servers generally listen on port 23.
The service name you enter depends on the type of communications link. The communication link can be one of the following: LAN-based connections, ping monitoring, or direct serial connections.
For LAN-based connections (such as TELNET, SSH, and terminal/communications server), the entry identifies the port on which a server is listening for connection requests:
TELNET connections
This port is typically port 23. If your port is 23, specify spo_telnet as the Service Name and you do not need to add an entry in the services file on the Operations Sentinel server.
To use any other port number, the services file on the Operations Sentinel server must include the line
servicename port/spo_telnet
where:
servicename is the Service Name you specify here, and port is the TELNET listen port. On the managed system, the services file must include the line
telnet port/tcp
SSH connections
This port is typically 22. If your port is 22, specify spo_ssh, spo_ssh1, or spo_ssh2 as the Service Name.
To use any other port number, the services file on the Operations Sentinel server must include one of the following lines:
servicename port/spo_ssh
servicename port/spo_ssh1
servicename port/spo_ssh2
where:
servicename is the Service Name you specify here, and port is the SSH listen port. On the managed system, the services file must include the following line. If the SSH server on the monitored system does not use the services files, you must set the configuration of the SSH server to specify the port
ssh port/tcp
Terminal/communications server connections
This port corresponds to the physical port on the terminal/communications server to which the managed system is connected. This physical port number is typically offset by a base value to indicate TELNET protocol (or SSH protocol). See the configuration guide for the specific terminal/communications server for the details. The services file on the Operations Sentinel server must include the line
servicename port /spo_telnet
where:
servicename is the Service Name you specify here, and port is the TELNET listen port. On the terminal/communications server, the services file must include the line
telnet port/tcp
For ping monitoring, there is no port association so you do not need to define this in the services file. Specify spo_ping as the Service Name property value.
For direct serial connections, the service name and corresponding entry in the services file identify the serial port on the Operations Sentinel server where the managed system is connected. You must create an entry for this name in the services file. The service name must be unique and only one system can use this service name.
To change the service name
Under the Managed Objects node in the navigation pane, click UNIX/Linux Systems.
In the display pane, click the desired system(s).
In the details pane, change the Service Name property to the desired name. The name can consist of any sequence of characters, except a space, tab, newline, and the comment character (#). The name is case-sensitive.
Save your changes.