744677 - switch camino-xserve4.scl3.mozilla.com uplink to NIC2

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Per dmoore in bug 744553 comment 3, NIC1 on camino-xserve4 has seen better days, so we should switch the network connection to use NIC2 (which was also what was in use in the old colo, post-bug 557145).

In terms of scheduling, there are no pressing scheduling concerns on our end right now, but I assume downtime would be minimal anyway?  If that assumption is correct, feel free to do this at any point (a heads-up in this bug would always be appreciated).  Mostly my concern is that the cable doesn't slip out of NIC1 again unexpectedly, particularly at some point when we do need to this machine for critical work ;-)

If the downtime required is going to be extended or there are other scheduling concerns on IT's end, then we can schedule something more concretely.

Thanks!

Comment 1

[Derek Moore [:dmoore]]

Let's schedule this for Monday, April 16th. That's the next time we'll have someone onsite.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

SGTM.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to Derek Moore from comment #1)
> Let's schedule this for Monday, April 16th. That's the next time we'll have
> someone onsite.

Did this happen?

Comment 4

[Vinh Hua [:vinh]]

I've just checked and camino-xserve4 is using NIC2. Closing ticket.