HP Insight Control Software for Linux - Manual (Page 251)

sysUpTimeInstance = Timeticks: (29922197) 3 days, 11:07:01.97
sysContact.0 = STRING: Root root@localhost (configure /etc/snmp/snmp.local.conf)
sysName.0 = STRING: pluto.example.com
sysLocation.0 = STRING: Unknown (edit /etc/snmp/snmpd.conf)
sysORLastChange.0 = Timeticks: (0) 0:00:00.00
sysORID.1 = OID: ifMIB
sysORID.2 = OID: snmpMIB
sysORID.3 = OID: tcpMIB
sysORID.4 = OID: ip
sysORID.5 = OID: udpMIB
sysORID.6 = OID: vacmBasicGroup
sysORID.7 = OID: snmpFrameworkMIBCompliance
sysORID.8 = OID: snmpMPDCompliance
sysORID.9 = OID: usmMIBCompliance
sysORDescr.1 = STRING: The MIB module to describe generic objects for network
interface sub-layers
sysORDescr.2 = STRING: The MIB module for SNMPv2 entities
sysORDescr.3 = STRING: The MIB module for managing TCP implementations
sysORDescr.4 = STRING: The MIB module for managing IP and ICMP implementations
sysORDescr.5 = STRING: The MIB module for managing UDP implementations
sysORDescr.6 = STRING: View-based Access Control Model for SNMP.
sysORDescr.7 = STRING: The SNMP Management Architecture MIB.
sysORDescr.8 = STRING: The MIB for Message Processing and Dispatching.
sysORDescr.9 = STRING: The management information definitions for the SNMP
User-based Security Model.
sysORUpTime.1 = Timeticks: (0) 0:00:00.00
sysORUpTime.2 = Timeticks: (0) 0:00:00.00
sysORUpTime.3 = Timeticks: (0) 0:00:00.00
sysORUpTime.4 = Timeticks: (0) 0:00:00.00
sysORUpTime.5 = Timeticks: (0) 0:00:00.00
sysORUpTime.6 = Timeticks: (0) 0:00:00.00
sysORUpTime.7 = Timeticks: (0) 0:00:00.00
sysORUpTime.8 = Timeticks: (0) 0:00:00.00
sysORUpTime.9 = Timeticks: (0) 0:00:00.00
23.21 Troubleshooting SSH credentials
The following table describes possible causes of problems with the Secure Shell (SSH) credentials
and provides actions to correct them.
Corrective actions Cause/Symptom
Set the SSH credentials for the target system using the HP
SIM Options
→Credentials tool. Specify Global or
System credentials as appropriate. For more information,
see “Setting SSH credentials on managed systems”
(page 197) and the HP Systems Insight Manager online
help.
SSH credentials missing for a server
The SSH credentials for a server, required for running
commands remotely, are missing. The cause may be one
of the following:
• The credentials were never set for the server.
• The managed system was deleted and re-registered.
• HP SIM orphaned the server and removed its
credentials.
• View the target system's properties to verify that HP
SIM has the correct IP address registered for the target
system.
• Verify that the target system is routable from the CMS
network.
• Use the command line SSH client to test that it is
possible to run SSH from the CMS to the target system.
• Verify that a firewall is not blocking port 22.
Unable to Create SSH Connection: No Route To Host
SSH cannot make a connection to the target system,
usually because the target system's IP address is not
accessible from the CMS.
• Verify that the SSH daemon is running on the remote
system.
• Verify that a firewall is not blocking port 22.
Unable to Create SSH Connection: Connection Refused
SSH was unable to connect to the target system because
the sshd daemon is not running on the target system.
23.21 Troubleshooting SSH credentials 251