Page MenuHomePhabricator

Codfw row A-B server moves - port-block constraint / numbering
Closed, ResolvedPublic



You have probably already considered this. But for the codfw server migrations to the new switches in codfw row's A/B there is a headache due to the constraint on port block speeds on the QFX5120s. i.e. if there is a 10G link currently from a device in U17 in a rack, and the device in U18 is connected at 1G, we have a conflict. We can't have port 16 on the switch at 10G and port 17 at 1G.

Has there been any thought put into how to process these? The obvious answer is to move the location of servers in the racks before we do any work I guess? Or allow exceptions to our port-numbering scheme based on rack location?

Event Timeline

cmooney triaged this task as Medium priority.Oct 4 2023, 11:00 AM
cmooney created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
cmooney renamed this task from Server moves in codfw to support switch numbering scheme to Codfw row A-B server moves - port-block constraint / numbering.Oct 4 2023, 11:08 AM

@Papaul answered in T348129#9224878, seems like we're in a good place given previous rack assignment as '1G' or '10G' racks.