Introduction

The Linux OS - Agentless (SSH) Application facilitates agentless discovery of SSH-enabled devices.

Linux flavors

The following Linux flavors are supported:

  • Ubuntu
  • Debian
  • CentOS
  • Fedora
  • SUSE
  • OpenSUSE
  • Red Hat Enterprise Server
  • Oracle Server
  • Amazon Linux

Components discovered

The gateway discovers the following data:

  • Basic device details such as OS, Mac, Make, Model and Serial No.
  • BIOS information
  • CPU processor information
  • Physical disk drives
  • Logical disk drives
  • Network cards information
  • Video cards information
  • Services
  • Installed applications

Prerequisites

  • An OpsRamp gateway is installed. See NextGen Gateways on how to install a gateway.
  • SSH credentials (SSH keys) are required.
  • IP addresses of the SSH-based machines.

Linux OS - Agentless (SSH) Discovery

Agentless discovery uses a Linux gateway instead of an agent to discover SSH-enabled resources.

Follow these steps to discover the Linux resources through SSH from gateway:

Configure integration

  1. Click All Clients, select a client.

  2. Click Setup > Account.

  3. Select the Integrations tile.

  4. The Installed Integrations screen is displayed, with all the installed applications. Click + ADD on the Installed Integrations screen.

  5. If you do not have any installed applications, you will be navigated to the Available Integrations screen. The Available Integrations screen displays all the available applications along with the newly created application with the version.
    Note: Search for the application using the search option available. Alternatively, use the All Categories option to search.

  6. Click ADD on the Linux OS - Agentless (SSH) tile.

    Linux OS - Agentless (SSH) Configuration screen

  7. From the CONFIGURATION screen, click + ADD. The Add Configuration dialog box is displayed.

    Linux OS - Agentless (SSH) Configuration screen

  8. Enter the below mentioned BASIC INFORMATION:

Table Note
FieldField TypeDescription
NameStringEnter the name for the integration.
Host Name/IP AddressStringHost name or the IP address provided from the installation.
SSH CredentialDropdownSelect an existing credential or create a new credential.
(Optional) Click + ADD to create a new credential. In the ADD CREDENTIAL window that appears, enter the following information:
  • Name - Enter the name.
  • Description - Provide a description.
  • Authentication Type - The Password or Keypair option is available. For the password option, enter the username, password, and confirm password fields. For the keypair option, upload a file through the Upload via file option or provide a link through the Already has a link option.
  • User Name (mandatory) - Enter the username.
  • Password - Enter the password. To ensure that you have typed the correct password, click the eye icon to view the password that you entered.
  • Confirm Password - Reenter the password. To ensure that you have typed the correct password, click the eye icon to view the password that you entered.
  • SSH Key Passphrase - Enter the passphrase. To ensure that you have typed the correct passphrase, click the eye icon to view the passphrase that you entered.
  • Confirm SSH Key Passphrase - Reenter the passphrase. To ensure that you have typed the correct passphrase, click the eye icon to view the passphrase that you entered.
  • Secure - Select the option based on your preference.
  • Port - Enter the port number - 22
  • Connection Timeout(ms) - Enter a value.
  • Click ADD.
Discover only SSH enabled devicesCheckboxIf you choose this option, only SSH enabled devices are discovered.
Perform ActionsCheckboxSelect the Manage Device checkbox, to manage the devices. The +Query option is displayed.
  • Use queries to filter the resources you want to manage.
    Note: If you do not select the Manage Device option, the devices will be in the discovered state.
  1. In DISCOVERY SCHEDULE section, select the recurrence pattern to add one of the following patterns:
    • None
    • Hourly
    • Daily
    • Weekly
    • Monthly

  2. Click ADD.

  3. The integration is saved and displayed on the configurations screen after you save it. From the same screen, you can Edit and Remove the created configuration.
Edit and Remove options
  1. Click Next. The SELECT COLLECTOR PROFILE screen is displayed.
Select Collector Profile screen

  1. Select a collector from the list.
    You can also add a new collector profile. Click +ADD and provide a name or use the pre-populated name.

  2. Click FINISH.
    The integration is installed and displayed on the Installed Integration screen. Use the search field to find the installed integration.

Actions on Integration

You can perform actions like Export, Edit, Uninstall on the integration.

  • See here for more information.

View the Linux OS - Agentless (SSH) Details

Navigate to Infrastructure > Resources > Server. You can go to the Attributes tab to view the below discovery details:

Permissions Required and Commands Used

AttributeCommandPermission
KERNEL_NAMEunameRoot permission is not required.
SYSTEM_INFORMATION_ALLuname -aRoot permission is not required.
LSB_RELEASE_ALLlsb_release -aRoot permission is not required.
OS_NAME/etc/os-release | grep PRETTY_NAMERoot permission is not required.
OS_VERSIONlsb_release -rsRoot permission is not required.
OS_DISTRIBUTION_IDlsb_release -isRoot permission is not required.
CPU_INFORMATION_ALL/proc/cpuinfo | grep -i 'processor\\|vendor_id\\|cpu family\\|model name\\|cpu MHz\\|cpu cores\\|power management'Root permission is not required.
PROCESSOR_SPEEDlscpu | grep -i mhzRoot permission is not required.
PROCESSOR_TYPElscpu | grep -i 'model name'Root permission is not required.
PROCESSOR_COUNTlscpuRoot permission is not required.
PROCESSOR_WIDTHlshw -C cpu | grep 'bus info\\|width'Root permission is not required.
PROCESSOR_L2_CACHE_SIZE/sys/devices/system/cpu/cpu/cache/index2/sizeRoot permission is not required.
WHOAMIwhoamiRoot permission is not required.
HOST_ADDRESSESdomainname -iRoot permission is not required.
ALL_HOST_ADDRESSESdomainname -IRoot permission is not required.
DNS_DOMAIN_NAMEdomainname -dRoot permission is not required.
LONG_HOST_NAMEdomainname -fRoot permission is not required.
SHORT_HOST_NAMEdomainname -sRoot permission is not required.
DNS_SERVERS/etc/resolv.confRoot permission is not required.
DEFAULT_GATEWAY_BY_ROUTEroute -nRoot permission is not required.
DEFAULT_GATEWAY_BY_IPip route showRoot permission is not required.
DEFAULT_GATEWAY_BY_NETSTATnetstat -rnRoot permission is not required.
DEFAULT_GATEWAY_BY_IFCFG_FILE_PATH/etc/sysconfig/network-scripts/ifcfg-eth0Root permission is not required.
DEFAULT_GATEWAY_BY_NETWORK_INTERFACES_FILE_PATH/etc/network/interfacesRoot permission is not required.
MEM_INFOgrep MemTotal /proc/meminfoRoot permission is not required.
ASSET_TAG_FILE_PATH/sys/class/dmi/id/chassis_asset_tagRoot permission is not required.
HOSTNAMEhostname -sRoot permission is not required.
HOSTNAME_WITH_DOMAIN_INFOhostname -fRoot permission is not required.
DOMAIN_INFOhostname -dRoot permission is not required.
NETWORK_INTERFACES_NAMES/sys/class/netRoot permission is not required.
NETWORK_INTERFACE_STATUS/sys/class/net//operstateRoot permission is not required.
NETWORK_INTERFACE_MACADDRESS/sys/class/net//addressRoot permission is not required.
NETWORK_INTERFACE_IPADDRESSip addr show | grep 'inet ' |Awk '{print $2}' | cut -f1 -d'/'Root permission is not required.
RPM_SOFTWARE_INSTALLED_APPLICATIONSrpm -qa --queryformat \"{'name' : '\"%{NAME}\"', 'architecture' : '\"%{ARCH}\"', 'version' : '\"%{VERSION}\"', 'release': '\"%{RELEASE}\"', 'installdate' : '\"%{INSTALLTIME:date}\"', 'size' : '\"%{SIZE}\"', 'vendor' : '\"%{VENDOR}\"','summary' : '\"%{SUMMARY}\"'\\},\\n\"Root permission is not required.
DEBIAN_SOFTWARE_INSTALLED_APPLICATIONSdpkg-query --show -f='{\"package\" : \"${Package}\", \"version\" : \"${Version}\", \"installedsize\" : \"${Installed-Size}\", \"comments\" : \"${Comments}\"},\\n'Root permission is not required.
PHYSICAL_DISK_VENDOR_AND_MODELcat /sys/class/block//device/{vendoR,model}Root permission is not required.
PHYSICAL_DISK_PARTITIONScat /proc/partitions | grep '[0-9]'Root permission is not required.
PHYSICAL_DISK_MEDIA_TYPE_PATH1cat /sys/block//removableRoot permission is not required.
PHYSICAL_DISK_MEDIA_TYPE_PATH2cat /proc/ide//removableRoot permission is not required.
LOGICAL_DISK_DETAILScat /etc/mtab | grep /[sh][d][a-z]Root permission is not required.
LOGICAL_DISK_SPACE_DETAILSdf -h | grep /[sh][d][a-z]Root permission is not required.
BASE_BOARD_MANUFACTURER_FILE_PATH/sys/class/dmi/id/board_vendorRoot permission is not required.
BASE_BOARD_PRODUCT_NAME_FILE_PATH/sys/class/dmi/id/board_nameRoot permission is not required.
SYSTEM_MANUFACTURER_FILE_PATH/sys/class/dmi/id/sys_vendorRoot permission is not required.
SYSTEM_PRODUCT_NAME_FILE_PATH/sys/class/dmi/id/product_nameRoot permission is not required.
BIOS_VERSION_FILE_PATH/sys/class/dmi/id/bios_versionRoot permission is not required.
BIOS_RELEASE_DATE_FILE_PATH/sys/class/dmi/id/bios_dateRoot permission is not required.
BIOS_VENDOR_FILE_PATH/sys/class/dmi/id/bios_vendorRoot permission is not required.
BASE_BOARD_SERIAL_NUMBER_FILE_PATH/sys/class/dmi/id/board_serialRoot permission is required.
SYSTEM_SERIAL_NUMBER_FILE_PATH/sys/class/dmi/id/chassis_serialRoot permission is required.
SYSTEM_PRODUCT_UUID_FILE_PATH/sys/class/dmi/id/product_uuidRoot permission is required.

Use Case

Behavior of Linux OS - Agentless (SSH) discovery

Assume you have 40 resources that are divided as follows:

  • For 10 resources, SSHD enabled with credentials 1
  • For 5 resources, SSHD enabled with credentials 2
  • For 25 resources, SSHD is not enabled

Scenario-1: Create a configuration with credentials 1

  • If “Discover only SSH enabled devices” option enabled: Only the 10 resources of credentials 1 will get discovered with valid data (OS, Make, and Model).
  • If “Discover only SSH enabled devices” option disabled: 10 resources of credentials 1 will get discovered with valid data (OS, Make, and Model) and 25 resources for which SSHD not enabled will get discovered with resource type as Other.

Scenario-2: Create a configuration with credentials 2

  • If “Discover only SSH enabled devices” option enabled: Only the 5 resources of credentials 2 will get discovered with valid data (OS, Make, and Model).
  • If “Discover only SSH enabled devices” option disabled: 5 resources of credentials 2 will get discovered with valid data (OS, Make, and Model) and 25 resources for which SSHD not enabled will get discovered with resource type as Other.

Scenario-3: Create a configuration with credentials 3 (invalid credentials)

  • If “Discover only SSH enabled devices” option enabled: No resource will be discovered.
  • If “Discover only SSH enabled devices” option disabled: All 40 resources will get discovered with resource type as Other.