Network Switch pattern fails to populate Location from the Discovery Schedule for the additional Cisco WAP device CIs - Known Error

Network Switch pattern fails to populate Location from the Discovery Schedule for the additional Cisco WAP device CIs Description It is documented that the Discovery Schedule "Location" field should be set on all [main device] CIs. "Location - Choose a location to assign to the CIs that the schedule discovers. If this field is blank, then no location is assigned." https://docs.servicenow.com/en-US/bundle/vancouver-it-operations-management/page/product/discovery/task/t_CreateADiscoverySchedule.html

Any record listed in the Devices list of the discovery status, linked to a main top-level CI, should be having Location set from the schedule.

The "Network Switch" pattern creates extra Device CIs for: - additional Switch CIs in the Stack (e.g. for Cisco Catalyst stacked switches) - WAP devices controlled by the switch [cmdb_ci_wap_network] (e.g. a Cisco WLC controlling lots of Cisco AIR devices)

As expected, the "IP-Switch Switch Stack" pre sensor script does add the location to the extra switch CIs, using the "IP-Switch Switch Stack" pre sensor script. But the "WAPs - Pre" pre sensor script fails to set the Location , which is a requirement of any pattern or sensor adding extra devices.

Steps to Reproduce

Create a discovery schedule for a Cisco WLC device, that controls at least one Cisco AIR device Add a location to that discovery schedule, then run it Expected behaviour: The Switch CI, plus the WAP CIs should have the "Location" field set from the schedule. Actual behaviour: Only the Switch CI has the Location set.

For confirmation of expected behaviour: Discover a Cisco Catalyst switch Stack. All main CIs linked from Device history records will have the location set, including the additional slave switch CIs.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

The attached update set ( sys_remote_update_set_a47bdea9dbd53d9071947e72f39619de.xml ) customises the out-of-box "WAPs - Pre" Pattern Pre/Post Script, to add the discovery schedule's location to the cmdb_ci_wap_network CIs as well as the cmdb_ci_ip_switch CI.

WARNING: This customisation will need reverting to the out-of-box version after upgrading to a fixed version. This script will be skipped in upgrades now that it is customised, meaning you will not get the fix, or any additional code and chages to that script, until it is reverted. Please subscribe to this KB article (3 dots menu under the title) to get notifications as the status changes to know which version fixies this out-of-box.