Post by Nok (Alliance GM) on Feb 25, 2007 19:03:24 GMT -5
The Allied sites & forum back online! This includes TheMageTower.org!
Essentially the outage lasted approximately 12 hours. After the datacenter replaced a main power line, upon power up the host provider lost a core router. The new core router worked but failed to pick up the corrupted network connections of the old core router. After reconfiguring the new core router and updating the corrupted networking connections, network routers and servers were progressively powered up. Control panel, email, FTP and web servers are all back online now. As are we.
Here is the statement from the host provider:
Essentially the outage lasted approximately 12 hours. After the datacenter replaced a main power line, upon power up the host provider lost a core router. The new core router worked but failed to pick up the corrupted network connections of the old core router. After reconfiguring the new core router and updating the corrupted networking connections, network routers and servers were progressively powered up. Control panel, email, FTP and web servers are all back online now. As are we.
Here is the statement from the host provider:
Power Outage Update
Posted 13 hours, 39 minutes ago (February 25th, 2007 at 2:56 am PST) by Justin
Power has been restored to the building and all servers are back up and running. There currently is an issue with a blade in one of the core routers and it is being replaced, so the servers are still unreachable until this issue is corrected. We are working to get service restored as soon as possible. Our apologies for the inconvenience.
- UPDATE 04:51 PST -
The supervisor in one of our core routers went kaput when the power went off. It was replaced shortly after the original posting. Further problems arose with corrupt configurations left over from the old supervisor. These have been restored and we have re-established connection to seven out of our eight uplinks. We are currently working on the eighth uplink and everything is coming back to normal operation now. We are close to being 100% and thank everyone for their patience. As always, check this space for updates.
- UPDATE 11:21 PST -
The router is up and healthy, and the majority of our network is back up and running. However, a few of our servers are having issues because their file servers are not talking to the rest of the network correctly. There is a link down from one part of the datacenter back to the routers and that is causing the file server issues. If you are on a server whose name is a beverage, this will effect you. We are working very hard to resolve this issue, and we apologize for the inconvenience.
Posted 13 hours, 39 minutes ago (February 25th, 2007 at 2:56 am PST) by Justin
Power has been restored to the building and all servers are back up and running. There currently is an issue with a blade in one of the core routers and it is being replaced, so the servers are still unreachable until this issue is corrected. We are working to get service restored as soon as possible. Our apologies for the inconvenience.
- UPDATE 04:51 PST -
The supervisor in one of our core routers went kaput when the power went off. It was replaced shortly after the original posting. Further problems arose with corrupt configurations left over from the old supervisor. These have been restored and we have re-established connection to seven out of our eight uplinks. We are currently working on the eighth uplink and everything is coming back to normal operation now. We are close to being 100% and thank everyone for their patience. As always, check this space for updates.
- UPDATE 11:21 PST -
The router is up and healthy, and the majority of our network is back up and running. However, a few of our servers are having issues because their file servers are not talking to the rest of the network correctly. There is a link down from one part of the datacenter back to the routers and that is causing the file server issues. If you are on a server whose name is a beverage, this will effect you. We are working very hard to resolve this issue, and we apologize for the inconvenience.
