Closed
Bug 921757
Opened 12 years ago
Closed 12 years ago
admin1.private.pek2 is unreachable
Categories
(Infrastructure & Operations Graveyard :: NetOps: DC Other, task)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 921953
People
(Reporter: ericz, Assigned: adam)
Details
admin1.private.pek2 is unreachable and I can't even reach its ilo. Not sure if this is a netops or dcops issue. It appears Asterisk is having troubles in PEK2 as well, but some things in PEK2 are ok.
| Reporter | ||
Updated•12 years ago
|
Assignee: server-ops-dcops → network-operations
Component: Server Operations: DCOps → NetOps: DC Other
Product: mozilla.org → Infrastructure & Operations
QA Contact: dmoore → adam
| Reporter | ||
Comment 1•12 years ago
|
||
Appears that the connection from pek1 to pek2 may be the issue, moving to netops queue.
Comment 2•12 years ago
|
||
the metro ethernet circuit from pek1 to pek2 is up, however, I see no traffic/MAC addresses. CC'ing nli as we don't have any visibility or access into that area as it could be power or some other failure on the remote side.
| Assignee | ||
Updated•12 years ago
|
Assignee: network-operations → adam
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•