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 |
|
|
|
|
|
|
Credential Requirements
| # | Requirement | Protocol | Importance | Mid Server updates/ Notes |
|---|---|---|---|---|
| 1 | windows class | JEA available in Orlando | High | interim solution will be to set up an integration |
| 2 | Linux/Unix Servers [including storage devices] | SSH User credentials w/ SUDO for target | High |
|
| 3 | Network Devices | SNMPv3 Read Only String | High | |
| 4 | vCenter | read only user/pass | ||
| 5 | MSSQL | Powershell user | High | interim solution will be to set up an integration |
| 6 | NetApp Storage | Basic Auth (net app read only) SNMP Read only string | High | |
| 7 | VMware vCenter | VMWARE Read only user/pass | High | |
| 8 | F5 Load Balancer | SNMP and read only shell BigIP user | High | |
| 9 | Oracle listener | sudo: can run crs_stat, lsnrctl, crsctl, srvctl) | High | |
| 10 |
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. |
Yale 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 | up | yes | windows |
New 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 |