SJC1: Please audit and locate cross-connects for Layer42/Level3/and Zayo if present

RESOLVED FIXED

Status

Infrastructure & Operations
DCOps
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: jbarnell, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Team:  We're trying to handle the final disposition of SJC1.  In order to do that we need to get an audit of the cross connects and have coresite disconnect those.  Can you please audit the locations of those cross connects and update the bug?

Updated

3 years ago
colo-trip: --- → sjc1

Comment 1

3 years ago
Let me know if you need more info.

layer42
-mozilla ca.L12c #1 to layer42 ca.yc53 (w/o 47596)
-mozilla ca.L12c to layer42 ca.yc53 (w/o 47604)
-mozilla ca.L12c #2 to layer42 ca.yc53 (w/o 47596)


internap
-mozilla ca.L12c #1 to internap cab.zj10 (w/o 47603)
-mozilla ca.L12c #2 to internap cab.zj10 (w/o 47603)


gbx
-cr1435 cage L12c #1 to rr.03 ODP.FP.31 & 32 (w/o 47599)
-cr1435 cage L12c #2 to rr.03 ODP.FP.33 & 34 (w/o 47599)


zayo
-cr1435 cage L12c #1 to rr.03 odp.fp.35 &36 (w/0 47601)
-cr1435 cage L12c #2 to rr.03 odp.fp.37 &38 (w/o 47601)


ANY2
-mozilla IDC1435 CA.L12C to IDC14.MLX8.01 SL.03 P.01 (w/o 65713)
-cr1435 cage L12c to rr.03 ODP.E P.85 & 86 (w/o 47606)
(Reporter)

Comment 2

3 years ago
Vinh/Van:

Can you open a ticket with Coresite to remove the cross connects for layer42, gbx, zayo, and any2?  Once that's opened if you can attach copies of the work order I'd appreciate it.

James

Comment 3

3 years ago
Created attachment 8493839 [details]
coresite.jpg

Cancellation #26106 -> Workorder ID#: 	47599
Cancellation #26107 -> Workorder ID#: 	47601
Cancellation #26108 -> Workorder ID#: 	47603
Cancellation #26109 -> Workorder ID#: 	47604
Cancellation #26110 -> Workorder ID#: 	47596
Cancellation #26111 -> Workorder ID#: 	65713

Comment 4

3 years ago
these cross connects are scheduled to be disconnected 9/29/14. please reopen if you need further hands-on.
Status: NEW → RESOLVED
Last Resolved: 3 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.