340 creates 588 an shs tuple the tuco for the node is then added 590 to the shs tuple and the topology converter 340 proceeds to the next node 550 if the node is not in a star segment then the topology converter 340 knows that it is in the bus segment if there is not already an mhs tuple for the node 594 then the topology converter 340 creates 596 an mhs tuple the tuco for the node is then added 598 to the mhs tuple and the topology converter proceeds to the next node 550 fig1 shows a flow chart for the discard duplicates phase 936 of the topology converter 340 for each tuple in the new tuples nt 600 the topology converter looks for 602 an exact match in the current tuples stored in the topodb if an exact match is found 604 then the new tuple is marked 606 as u201c no change u201d indicating that this is an identical tuple fig2 a u2013 d show a flow chart for the identify different tuples phase 938 the system looks through each tuple in the new singlyheardsegments newshs tuple list 608 and tries to identify and fix 610 swapped ports on connectors swapped ports are identified by considering those segment tuples in both the new topology and the existing topology that differ only by the port specification in the tuco each tuple that is fixed as a swapped port is marked 612 as u201c handled u201d the system also looks through each tuple in the new multiheardsegments tuple list newmhs 614 and tries to identify and fix 616 swapped ports on connectors each tuple that is.