This is a safe operation - hosts in these subnets are either static or not in production. Please point the DHCP helper to the "usual" infra DHCP servers in each datacenter/BU for: ad.db.scl1 (scl1-vlan69) ad.db.scl3 (scl3-vlan69) wintest.releng.scl3 (scl3-releng-vlan240) ad.db.phx1 (phx1-vlan69) (This intentionally omits one of the VLANs in bug 798601, since that VLAN contains production builders that need to stay up. Once I'm confident this works elsewhere, I'll request that VLAN as well.)
I think the "usual" servers are, respectively: ad.db.scl1 (scl1-vlan69) -> admin1a/b.infra.scl1 ad.db.scl3 (scl3-vlan69) -> admin1a/b.private.scl3 wintest.releng.scl3 (scl3-releng-vlan240) -> admin1a/b.private.releng.scl3 ad.db.phx1 (phx1-vlan69) -> admin1a/b.private.phx1 but please double-check my guesses and confirm/deny, so I know which hosts to look at for logging.
I'm away next week, so let's hold off on this until the 16th.
Assignee: network-operations → dustin
Back to netops. Please make this change at your earliest convenience during working hours. The four VLANs here are low-risk, so no need for coordination around timing.
Assignee: dustin → network-operations
Comment 1 was correct, done
Assignee: network-operations → arzhel
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.