| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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. |
...
| # | Approve CI Classes | Protocol | Port Probe | Protocol - Probes/Pattern | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Linux/Unix Servers [including storage devices] | SSH User credentials w/ SUDO for target | ssh |
| 2 | Network DevicesSNMPv3 Read Only String | snmp | 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. Probe Gets network information: Probe Retrieve disk information Probe Gathers fully qualified domain name: Probe Retrieves serial numbers from DMI (BIOS) | //bugzilla.sudo.ws/show_bug.cgi?id=826 for details: Probe Gets the distribution for Linux operation system: | |
| 2 | Network Devices | SNMPv3 Read Only String | snmp | 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: | ||||||
| 3 | NetApp Storage | Basic Auth (net app read only) SNMP Read only string | snmp | Pattern Obtains NetApp device storage details: Pattern obtains NetApp Devices storage clusters | ||||||
| 4 | VMware vCenter | VMWARE Read only user/pass | vmapp | 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: 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: | ||||||
| 5 | F5 Load Balancer | SNMP and read only shell BigIP user | snmp | 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: | ||||||
| 6 | Oracle | sudo: can run crs_stat, lsnrctl, crsctl, srvctl) | 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: | ||||||
| 7 | JEA available in Orlando for window servers and MSSQL scans | |||||||||
| 8 | windows servers | JEA available in Orlando | interim solution will be to set up an integration | |||||||
| 9 | MSSQL | JEA available in Orlando | interim solution will be to set up an integration | |||||||
...
| 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 |
...