IP Connection relationship discovered between Wireless Controller and servers

[Annie7]

ServiceNow Discovery creates an IP Connection relationship between Wireless Controllers (or WAP switches) and Servers. That causes Application Servers to appear as impacted in Change tickets when changes are made to Wireless Access Points (WAPs) or Wireless Controllers.

Does anyone have same situation in the organization? Is the IP Connection relationship setup correctly between a wireless controller and servers? 

Is there any best practice we can consider either to update discovery patterns or identification rules to prevent creating the relationship or  create customize script for change to stop the wireless change populates server impacted

[Mathew Hillyard]

Hi @Annie7 

This is very common with Discovery. All CMDBs contain many CIs that for Incident, Problem and Change are not relevant. 
ServiceNow includes the Manual CI Inclusions /Exclusions [svc_manual_ci_exclusions_inclusions] table. Define any CI classes you don’t want to assess for impact here and they will not be added to the Service Configuration Item Association [svc_ci_assoc] table, which is where impacted services are calculated from.

Note that with a few classes, like Tracked Configuration File, these are also brought in based on an entry in the Traversal Rule [svc_traversal_rules] table (which is related to Service Mapping), so that entry may need to be deactivated.

I hope this helps!
Mat

[MaxMixali]

Hi following the list of step to solve this problem, hope that can help

Step 1: Identify the Discovery Pattern
Navigate to: Discovery > Service Mapping > Patterns
Find pattern: "IP Network Connections" or "TCP Connections"
Open the pattern
Step 2: Modify Pattern to Exclude Wireless DevicesAdd exclusion logic to the pattern:javascript// In the pattern's "Parse" section or "Post-processing" script

// Exclude connections where source or target is a wireless device
var sourceCI = current.source; // Source CI
var targetCI = current.target; // Target CI

// Check if source is wireless controller/WAP
var sourceClass = new GlideRecord('cmdb_ci');
if (sourceClass.get(sourceCI)) {
if (sourceClass.sys_class_name == 'cmdb_ci_wap_network' ||
sourceClass.sys_class_name == 'cmdb_ci_wireless_ap' ||
sourceClass.name.indexOf('Wireless') > -1 ||
sourceClass.name.indexOf('WAP') > -1) {

// Skip creating this connection
ignore = true;
return;
}
}

// Check if target is wireless controller/WAP
var targetClass = new GlideRecord('cmdb_ci');
if (targetClass.get(targetCI)) {
if (targetClass.sys_class_name == 'cmdb_ci_wap_network' ||
targetClass.sys_class_name == 'cmdb_ci_wireless_ap' ||
targetClass.name.indexOf('Wireless') > -1 ||
targetClass.name.indexOf('WAP') > -1) {

// Skip creating this connection
ignore = true;
return;
}
}

Step 3: Test DiscoveryRun discovery on a wireless controller and verify IP connections to servers are NOT created.

[Simon Hendery]

@MaxMixali, my man - no!

This is a terrible answer, sure. That goes without saying. But even the way you cut and pasted it was poor!

#AI_slop 

[MaxMixali]

It's not cut and paste, I try to help and suggest one solution instead of