When running Discovery on Stacked Switches, these are not properly updating their "Stack" field or "Primary/Secondary" status in the form record, and relationships are not properly created between Primary and Secondaries.
Run Discovery on Cisco switches in Primary/Secondary stack configuration.
This issue has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.
If you are unable to upgrade to a fixed release, perhaps the following workaround may provide temporary relief.
Change the following condition in Step 3 of Stacked Switches (37.3 in the "Network Switch" pattern on London) from:
$entPhysicalTable1.entPhysicalSerialNum EQUALS $cmdb_serial_number.serial_number
$entPhysicalTable1.entPhysicalSerialNum EQUALS $cmdb_serial_number_temp.serial_number