The managed system must have an active SSH server to interface with Operations Sentinel through an SSH connection. Operations Sentinel uses SSH version 1 or version 2.
The SSH version 1 server must support at least one algorithm in each of the following categories:
Encryption and Decryption algorithm
3des-cbc
des-cbc (not supported by the industry standard)
User authentication method
password
The SSH version 2 server must support at least one algorithm in each of the following categories:
Key exchange algorithm
diffie-hellman-group-group1-sha1
Host key algorithms
ssh-rsa
ssh-dss
Encryption and Decryption algorithm
aes256-cbc
rijndael256-cbc (same as aes256-cbc, but older name)
aes192-cbc
rijndael192-cbc (same as aes192-cbc, but older name)
aes128-cbc
rijndael1280cbc (same as aes128-cbc, but older name)
3des-cbc
des-cbc (not supported by the industry standard)
Message authentication code
hmac-sha1
hmac-md5
none
User authentication method
password
Because SSH is essentially a secured version of TELNET, all characteristics described in “Ping Monitoring” apply to the SSH connection. See Figure 4–1 for more information.
SSH Connection Considerations
The following are the advantages:
Highly secure
Inexpensive, using an existing LAN or WAN
Full control and automation after the boot process
Multiple console traffic sessions possible
Easy to set up
The following are the disadvantages:
No control of the managed system’s boot process
No means to redirect console traffic to an SSH session for certain UNIX and Linux operating systems
May have to purchase or acquire a server compatible with SSH version 1 or version 2 for the managed system