Versions Compared

Old Version 32

changes.mady.by.user Allena Kendrick (Unlicensed)

Saved on

compared with

New Version 33

changes.mady.by.user Allena Kendrick (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties



Platform OwnerDeanna Burns (Unlicensed)
Project ManagerDavid Swanson (Unlicensed)
Document status
Status
colourGreen
titleWork in Progess
SN Discovery SME

Allena Kendrick (Unlicensed)

CMDB ManagerChristopher Abbott (Unlicensed)
Technical writersVandana Bansal
Yale Technical LeadAndrew Newman (Unlicensed)
SN CMDB LeadVimalpriya Kothandapani (Unlicensed)


...

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.

...

FireWall Ports

  • Local LAN inbound (from MID server IP to scanned IPs)
  • Any/Any for Windows desktop firewall
  • Access to admin share (e.g. C$)
  •   Allow 22, 80, 135, 161, 443, 445, 8585, 1024-65535
  •  May need additional allowed ports if targets not listening on default ports on scanned devices

Discovery Credential and Protocols Requirements

interim solution will be to set up an integration 910
#RequirementApprove CI ClassesProtocolPort Probe Protocol - Probes/Pattern 
1windows serversJEA available in Orlando
JEA
2Linux/Unix Servers [including storage devices] SSH User credentials w/ SUDO for targetssh

 


32Network DevicesSNMPv3 Read Only Stringsnmp
4MSSQL Powershell userJEAinterim solution will be to set up an integration 

53NetApp Storage

Basic Auth (net app read only)

SNMP Read only string

snmp
64VMware vCenter VMWARE Read only user/passvmapp

Probes a Unix machine for VMWare Workstation information:

UNIX - Get VMWare Workstation

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.

VMWare - vCenter

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.:

VMWare - vCenter Clusters

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:

VMWare - vCenter Datacenters

Probe Explores datastores, datastore hostmounts and datastore disks.This probe's implementation is located in a MID server script include named VMWarevCenterDatastoresProbe:

VMWare - vCenter Datastores

Explore virtual networks.

This probe's implementation is located in a MID server script include named VMWarevCenterNetworksProbe.:

VMWare - vCenter Networks

Probe Explores NICs installed in virtual machines.This probe's implementation is located in a MID server script include named VMWarevCenterVMNICsProbe:

VMWare - vCenter VM NICs

Probe Explores VMs.This probe's implementation is located in a MID server script include named VMWarevCenterVMsProbe:

VMWare - vCenter VMs



75F5 Load Balancer SNMP and read only shell BigIP usersnmp

Probe Retrieves the BIG-IP Identity:

SNMP - F5 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.:

SNMP - F5 BIG-IP - System   

Probe Retrieves Load balancing Info:

F5 BigIP LTM       

F5 BigIP GTM                               

86Oracle  sudo: can run crs_stat, lsnrctl, crsctl, srvctl)


ssh

note: adding the service patch levet to the pattern

Probe Get the details of a specific Oracle instance:

Oracle - Instance Details   

Probe Obtain the PFile for Oracle instance:       

Oracle - Instance PFile

Prober Gathers Oracle instance version information:

Oracle - Instance Version

Probe Get the details of a specific Oracle listener:

Oracle - Listener Details

Pattern Retrieves Oracle DB information on Unix:

Oracle DB On Unix


7                                        JEA available in Orlando for window servers and MSSQL scans
8windows servers


JEA available in Orlando
interim solution will be to set up an integration 
9MSSQLJEA available in Orlando
interim solution will be to set up an integration 

MidServer Installation 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 NameServiceNow InstanceLocationIPhost nameStatusClusterHost Os
yalesand1yalesandbox@service-now.comNorwalk172.18.16.39snow-tst-mid1.yu.yale.eduupYeswindows
yalesand2yalesandbox@service-now.comwest Campus 172.18.16.52snow-tst-mid2.yu.yale.eduupYeswindows
yalesand3yalesandbox@service-now.comwest campus172.18.16.52snow-tst-mid2.yu.yale.eduupyeswindows


New Dev and Production MidServers

New Production Mid-ServerslocationHost OScluster
Discovery 1West CampuswindowsYes
Discovery 2West CampuswindowsYes
Discovery 3NorwalkwindowsYes
Discovery 4NorwalkwindowsYes
Integration 1West CampuswindowsYes
Integration 2NorwalkwindowsYes

...