Time really fly. Its been nearly a month since I last updated my blog!
What was i busy about? That is a good question. Actually I am busy doing the windows update for the conflicker virus and cleaning up those unfortunate machines that are infected. Lucky our patching are up-to-date for most machines so I do not need to spend too much time on all the 100 odd machines exclude servers
Then after the windows update came the customer project. For business sense, I will note disclose the customer publicly; But since I am in charge of network and infrastructure, I am entrusted to ensure the customer is able to go to the internet and is kind enough to give us two workstation. We need to go to their HQ to get their standards. So was busy getting quote and working out the details.
Then singtel decided to kill my weekends and brain cells. We change our plan from a 2MB/512KB line to a 3MB/768kb line. Right after the change our line went down every 5 hours. At first we thought it is our configuration or old equipment (our cisco 837 is in use since 2002) Then we tried all the methods include cleaning up the configuration but to no avail. Finally we got singtel since they are providing the infrastructure. The singtel contractor was kind enough to see that our line is giving us problem backend so we did a change in our circuit on May 19. Then all back to normal.
After the above, we thought everything back to normal. Then singtel for no reasons, moved my another 512kb/256kb line to a new circuit. Problem is the new circuit will only be activated on May 26. So I was unable to do site to site VPN with my parent company for a mission critical application. After I screamed at Qala which is caught between singtel and us since we got the line from them, agree to a Joint test on may 23 morning. We only get the line back up on May 23 2.45pm. Reason: They change the circuit and ask the contractor to do a test on the DP which is working fine all these while. So the contractor was 'screwed' by the singtel backend to do troubleshooting for a problem that belongs to the backend, back at the exchange. With the incident concluded, I shoot a mail to Qala demanding a incident report and prepared to take with my boss for legal advice to make Singtel pay for its reckless mistake.
No comments:
Post a Comment