Use > Discovery Modules > Network Infrastructure > Host Connection > Host Connection by Shell Job > Discovery Mechanism

Discovery Mechanism

This part of the discovery depends on whether you are discovering components installed on Windows machines, UNIX-based machines, or Nexus machines. For details on the DFM processes, see:

Note

  • DFM runs through the credentials defined for the protocol and tries to connect successfully through one of them. Whenever there is a successful connection, the discovery remembers the last successful credential and caches it for reuse the next time the discovery is run.

  • If the credentials (last used for this destination) do not exist, DFM iterates through the list of all configured shell credentials.

    DFM uses the following flow for this iteration: SSH, then Telnet, then NTCMD protocol credentials, to try to connect to the discovered destination.

    DFM skips credential entry if the IP Address of the discovered destination is outside the IP range scope of the credential.

    DFM immediately stops using a protocol for the discovered destination if:

    • There is no agent on the remote machine

    • Connection is refused

    • Connection times out

    • There is an IO exception on opening a socket

    DFM stops iteration through the list of configured credentials if:

    • It successfully establishes connection

    • It fails to connect to the discovered destination after trying all configured credentials

Windows Processes

This section describes the part of the workflow that DFM performs for discovering components residing on Windows machines.

  1. DFM discovers host attributes (OS name, version, build number, service pack, installation type). DFM starts by using the first instruction in the following list to discover the host attributes. If that fails, DFM continues to the next:

    1. WMIC "OS" object;

      Full command: 

      'wmic os get caption, otherTypeDescription, version, buildnumber, csdversion /format:list < %SystemRoot%\win.ini'

    2. Windows registry;

      Full query: 

      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion VER command; %SYSTEMROOT%\system32\prodspec.ini processing

  2. Define BIOS UUID (wmic)

    Full command: 

    'wmic path win32_ComputerSystemProduct get uuid /format:list < %SystemRoot%\win.ini'

  3. Define the default gateway (netstat).

    Full command: 

    'netstat -r -n'

  4. Define the DNS server IPs (ipconfig).

  5. Define the boot date.

    Full command: 

    'wmic OS Get LastBootUpTime /format:list < %SystemRoot%\win.ini'

  6. Define the network interfaces. The wmic command is used first because it retrieves more information about the interface. If that fails, the output of the ipconfig command is used.

    1. Querying NICCONFIG object we get information about MAC address, IP addresses, interface description, subnet IPs, dynamic or static flag.

      Full command: 

      'wmic nicconfig where "MACAddress <> NULL" get IPAddress,MACAddress,IPSubnet,Description,DhcpEnabled /format:list < %SystemRoot%\\win.ini'

    2. IP filtering. Malformed and local IPs are ignored.

  7. DFM checks whether the destination IP is local. If it is, DFM reports the host and IP only. If it is not local:

    1. DFM reports network interfaces apart from:

      • Interfaces that do not have a MAC address

      • Interfaces that belong to one of the following types: loopback, wireless, virtual, WAN miniport, RAS ASYNC, Bluetooth, FireWire, VPN, IPv6 tunneling.

      • The VMware interface, if ignoreVmwareInterfaces is set to true in the globalSettings.xml configuration file.

    2. DFM reports networks, IPs, and corresponding links.

UNIX-Based Processes

This section describes the part of the workflow that DFM performs for discovering components residing on UNIX-based machines. DFM defines the Operating System. For details, see the descriptions below of what DFM discovers for the following Operating Systems:

Full command:'uname -a'

Note

Before reporting the discovery, DFM makes the following verifications:

  • If the destination IP is a virtual address, only the IP and host are reported.

  • In the case of the ZLinux OS, when the host model is s390x, the host is defined by the IP and domain name.

  • If the interface has an invalid MAC address, DFM does not report it.

ClosedAIX

DFM discovers:

  1. The DHCP enabled network interfaces (ps).

    Full command:'ps -aef | grep dhcpcd | grep -v grep'

  2. The network interfaces (MAC address, name, description) (lsdev, entstat)

    Full command:'lsdev -Cc adapter -S | egrep ^ent'

  3. The IPs (ifconfig).

    Full command:'ifconfig -a inet'

  4. DFM defines the boot date, domain name, and default gateway in the same manner as for FreeBSD.

  5. The model and vendor (uname).

    Full command:'uname -M'

  6. The serial number (lsattr).

  7. The OS version (oslevel).

ClosedFreeBSD

DFM discovers:

  1. The DHCP enabled interfaces (ps).

    Full command:'ps aux | grep dhclient | grep -v grep'

  2. The boot date (uptime).

  3. The network interfaces (name, MAC, IP, network mask, DHCPenabled flag) and IPs (ifconfig).

    Full command:'ifconfig -a'

    The host is defined by the lowest MAC address among the network interfaces.

  4. The OS version and host model (uname).

    Full command:

    'uname -r' for the version

    'uname -m' for the model

  5. The domain name (domainname).

    Report only filtered name: '(none)','localdomain'

  6. The BIOS UUID (dmidecode).

    Full command:'dmidecode | grep UUID'

  7. The default gateway (netstat).

    Full command:'netstat -r -n'

ClosedHP-UX

  1. DFM discovers the network interfaces by one of the following methods:

    1. nwmgr

    2. lanscan (if nwmgr is unsuccessful)

  2. DFM defines aliases (netstat) for the discovered interfaces.

    Full command:'netstat -I'

  3. For each interface, DFM defines IPs (ifconfig).

  4. DFM discovers the host model, boot date, OS version, serial number, and default gateway.

  5. DFM discovers the OS flavor (swlist).

    Full command:'swlist | grep -E "HPUX.*?OE"'

ClosedLinux

DFM discovers:

  1. The DHCP enabled network interfaces (ps).

    Full command:'ps aux | grep dhclient | grep -v grep'

  2. The IPs and network interfaces (MAC address, name, description) (ifconfig).

    Full command:'ifconfig -a'

  3. The boot date, serial number (dmidecode), OS version, host model, domain name, and default gateway.

  4. Information about HMC (Hardware Management Console) and its IPs (lshmc).

    Full command:'lshmc -V'

  5. The BIOS UUID (dmidecode).

    Full command:'dmidecode | grep UUID'

  6. The OS flavor (redhat-release).

    Full command:'cat /etc/redhat-release'

ClosedOpenBSD

DFM discovers:

  1. The DHCP enabled interfaces (ps).

    Full command:'ps aux | grep dhclient | grep -v grep'

  2. The boot date (uptime).

  3. The network interfaces (name, MAC, IP, network mask, DHCPenabled flag) and IPs (ifconfig).

    Full command:'ifconfig -a'

    The host is defined by the lowest MAC address among the network interfaces.

  4. The OS version and host model (uname).

    Full command:

    'uname -r' for the version

    'uname -m' for the model

  5. The domain name (domainname).

    Report only filtered name: '(none)','localdomain'

  6. The BIOS UUID (dmidecode).

    Full command:'dmidecode | grep UUID'

  7. The default gateway (netstat).

    Full command:'netstat -r -n'

ClosedSunOs

DFM discovers:

  1. The network interfaces (netstat)

    Full command:'netstat -np'

  2. The IP addresses.

    Full command:'ifconfig -a'

  3. The boot date, domain name, BIOS UUID, and default gateway.

  4. The OS version and release (uname).

    Full command:'uname -rv'

  5. The host model (prtdiag)

  6. The manufacturer (showrev)

  7. The serial number (dmidecode)

    Full command:'dmidecode | grep UUID'

ClosedVMKernel

DFM discovers:

  1. The network interfaces (MAC address, name) and IPs (esxcfg-vmknic)

    Full command:'esxcfg-vmknic -l'

  2. The boot date, OS version, and host model.

  3. The domain name (esxcfg-info).

    Full command:'esxcfg-info | grep Domain'

  4. The BIOS UUID (esxcfg-info).

    Full command:'esxcfg-info | grep \'BIOS UUID\'

  5. The serial number (esxcfg-info).

    Full command:'esxcfg-info -w | grep \'Serial Number\''

  6. The default gateway (esxcfg-route).

  7. The OS flavor (vmware)

    Full command:'vmware -v'

Nexus Processes

This section describes the part of the workflow that DFM performs for discovering components residing on Nexus machines.

  1. DFM gets the host name using the command sh hostname.
  2. DFM gets version, build and feature information for the switch using the command sh ver.
  3. DFM gets dns server and local host data using the command sh hosts.
  4. DFM get interface and configured IP information using the command sh int.

Send Help Center feedback