| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Table of Contents
Discovery Schedule
The discovery schedule will contain a Location(cmn_location) and Data Center(cmdb_ci_datacenter) location data attributes
YaleSandbox1 Midserver Configuration
Configuration Parameter
Noted: added mid.log.level Value=trace
Supported Application
IP Ranges
Capabilities
Properties
Clusters
Note: IMPORTANT - You can restrict protocols from executing on your schedule by setting up discovery functionality on your schedule.
MidServer Services Architecture
The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network.
The MID Server facilitates communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.
| The MID Server enables communication between a Servicenow Instance and the customer network |
| It is a Java Application that runs as a Windows Service or a Unix Dameon |
| It requires only an outbound connection on Port 443 |
MIdServer Services Requirements
The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. The MID Server facilitates communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.
Windows server: To discover Windows-based servers, run Service Mapping patterns, or execute Orchestration commands on Windows devices, the MID Server must be installed on a Windows server. The MID Server supports all Windows Server 2008, 2012, and 2016 editions, virtual machines, and 64-bit systems. Note: .NET Framework version 3.5, 4.0, 4.5, 4.6, or 4.7 is required for Service Mapping support and for Windows pattern-based discovery. |
ServiceNow Configs
| · Ensure Discovery is able to write discovered objects to correct tables |
| · ServiceNow Administrator web browser must have Flash Player 10.1 or higher |
Clusters - Load Balancing and Failover
|
FireWall Ports |
|
|
|
|
|
|
Discovery Credential and Protocols Requirements
Probe to fire patterns for Horizontal discovery:
Probe Retrieves information for identifying it in the CMDB, such as serial number and NICs.
Probe Retrieve Linux installed software:
Probe Retrieves memory information:
Probe Gets detailed information about the memory modules installed in the system.
"| cat" is used because 1) Dmidecode tends to return junk error codes so "|" throws away the code, and 2) sudo command has a bug causing it to hang forever; see KB0683246 and https://bugzilla.sudo.ws/show_bug.cgi?:id=826 for details:
Probe Gets network information:
Probe Retrieve disk information
Probe Gathers fully qualified domain name:
Probe Retrieves serial numbers from DMI (BIOS)
"| cat" is used because 1) Dmidecode tends to return junk error codes so "|" throws away the code, and 2) sudo command has a bug causing it to hang forever; see KB0683246 and https://bugzilla.sudo.ws/show_bug.cgi?id=826 for details:
Probe Gets the distribution for Linux operation system:
Pattern to fire patterns for Horizontal discovery:
Pattern fires to obtain router information:
Pattern fires to obtain Routing information:
Network Routing Device - Light
Pattern fires to obtain switch information:
Basic Auth (net app read only)
SNMP Read only string
Pattern Obtains NetApp device storage details:
Pattern obtains NetApp Devices storage clusters
Probes a Unix machine for VMWare Workstation information:
Probe to get information from vCenter about ESX hosts, resource pools, and virtual machines. Implementation details for this probe are located in a MID server script include called VMWarevCenterProbe.
Probe Explores clusters and resource pools. Relate each cluster to its resource pools, ESX hosts and its containing folder or datacenter. The sensor will trigger the "ESX Hosts" probe to explore ESX hosts.This probe's implementation is located in a MID server script include named VMWarevCenterClustersProbe.:
Probe to get information about a vCenter's datacenters. The sensor will fire a probe for each type of vCenter object in each datacenter:
VMs, explored by the "VMWare - vCenter VMs" probe,
clusters, explored by the "VMWare - vCenter Clusters" probe,
datastores, explored by the "VMWare - vCenter Datastores" probe, and
networks, explored by the "VMWare - vCenter Networks" probe.
This probe's implementation is located in a MID server script include named VMWarevCenterDatacentersProbe.
As of the Istanbul release this probe replaces the "VMWare - vCenter" probe for Discovery:
Probe Explores datastores, datastore hostmounts and datastore disks.This probe's implementation is located in a MID server script include named VMWarevCenterDatastoresProbe:
Explore virtual networks.
This probe's implementation is located in a MID server script include named VMWarevCenterNetworksProbe.:
Probe Explores NICs installed in virtual machines.This probe's implementation is located in a MID server script include named VMWarevCenterVMNICsProbe:
Probe Explores VMs.This probe's implementation is located in a MID server script include named VMWarevCenterVMsProbe:
Probe Retrieves the BIG-IP Identity:
Probe Retrieves the BIG-IP chassis serial number, which is globally unique for this vendor:
SNMP - F5 BIG-IP - Identity - Serial
Probe Collects information on the F5 BIG-IP, including pools, services, and VLANs.:
Probe Retrieves Load balancing Info:
note: adding the service patch levet to the pattern
Probe Get the details of a specific Oracle instance:
Probe Obtain the PFile for Oracle instance:
Prober Gathers Oracle instance version information:
Probe Get the details of a specific Oracle listener:
Pattern Retrieves Oracle DB information on Unix:
MidServer Installation Process
ServiceNow Discovery Journey#MidServerInstallationProcess
Mid-Server Validation process
| VALIDATE MID-SERVERS | |
| Navigate to MID Server > Servers. | |
| Open the new MID Server from the list of MID Servers. | |
| Under Related Links click Validate. | |
| The Set Initial Selection Criteria window appears if there are no records in the Supported Applications, IP Ranges, or Capabilities related lists. | |
| On the Set Initial Selection Criteria window, use the switches to enable or disable selection criteria for this MID Server: | |
| Allow ALL capabilities: Allow all capabilities for Orchestration and Event Management use this MID Server. | |
| Note: Service Mapping and Event Management alert aggregation and RCA, which used capabilities in previous releases, rely on the application for MID Server selection starting with the Istanbul release. | |
| Allow ALL applications: Allow all applications that use MID Servers use this MID Server. | |
| Allow ALL IP ranges: Make all IP ranges valid for this MID Server, meaning that it can target any IP address. | |
| Setting initial selection criteria | |
| |
| If you click Cancel, the validation continues but none of the capabilities, applications, or IP ranges are added. | |
| Click OK. | |
| The Validated field on the dashboard is set to Validating, and then set to Yes after the validation completes. |
YaleSandbox Mid-Servers
| MidServer Name | ServiceNow Instance | Location | IP | host name | Status | Cluster | Host Os |
|---|---|---|---|---|---|---|---|
| yalesand1 | yalesandbox@service-now.com | Norwalk | 172.18.16.39 | snow-tst-mid1.yu.yale.edu | up | Yes | windows |
| yalesand2 | yalesandbox@service-now.com | west Campus | 172.18.16.52 | snow-tst-mid2.yu.yale.edu | up | Yes | windows |
| yalesand3 | yalesandbox@service-now.com | west campus | 172.18.16.52 | snow-tst-mid2.yu.yale.edu | up | yes | windows |
New Dev and Production MidServers
| New Production Mid-Servers | location | Host OS | cluster |
|---|---|---|---|
| Discovery 1 | West Campus | windows | Yes |
| Discovery 2 | West Campus | windows | Yes |
| Discovery 3 | Norwalk | windows | Yes |
| Discovery 4 | Norwalk | windows | Yes |
| Integration 1 | West Campus | windows | Yes |
| Integration 2 | Norwalk | windows | Yes |