Thursday, January 31, 2008

Bringing Order to an Existing Chaos

Team,

Let's systematize the installation of Karspersky. We are talking about hundreds of computers here, and so it is easy to get confused and miss.

Installation will be "one Engineer per branch" to avoid confusion as to which computer of which branch is already done by who. If you decide to take one branch, all computers in that branch are yours. On RT, you are to create "one RT ticket per branch", and the subject shall be "Karspersky AV Installation - ". All tickets shall be created under the Network::Projects queue. To know which branch is already taken, please ask Tina who will keep the master list (to be submitted to Martin). As to how you compute the Time Worked, just simply be honest. And don't dilly-dally, there is a way to be sure!

Thanks.

Sanny

Note: With the help of the software's own automated installation, the project progressed fairly fast. And the tracking of completed branches, were smooth and swift. The department was commended for being systematic.

Commending a Good Friend

Renz,

Brother, I'd like to greet you as an associate and fellow for bravely and firmly standing by the principles of honesty and for protecting the good of our department in the D-Link router issue, which caused broadcast of invalid IP Addresses at the Tower. It's a highly confidential issue therefore it is a high profile courage on your part.

The procedures and tools you conducted, as primitive as what's available to us, were used very diligently that the dreaded further outbreak was prevented, saving IT and the Bank.

The same commendations also to all the people who helped you in this problem especially our Heads.

Magaling! Masipag! Indispensable! Inspiring!


Comrade,

Sanny

An Appointment

Sir,

Thanks. It was like a training session with you.

About the kind of leadership that you want all your people to learn, I commit to honesty, sincerity, and quality. I also commit, as well as pray to God, that I will neither be like a fly standing boastfully and comfortably on top of a cow nor seek to ride the back of a tiger and crazily end up inside.

My actions will remain objective rather than or rarely be subjective.

God bless our company.

Sanny


Note: The appointment as Department Head-in charge did not push through because the incumbent revoked his resignation.
Partners,

Below are the details of the result of the commissioning of new wireless antenna radios and the testing of Bellevue’s backup Internet connection via Plaza B, Northgate Cyberzone by the FITI Group.

The new wireless antennae, Ovislink AirLive, were successfully commissioned on the afternoon of January 17, 2008. The wireless link that connects Bellevue to Plaza B was restored at around 2pm by replacing the old radio antennae that were reported having intermittent wireless link a few months back. The new Ovislink Airlive antenna registered a stable RSSI of –50dbm and the result of PING across the wireless link indicated a steady radio-to-radio link.

>From the 3Com hub at the Roof Deck, the testing of Internet was successful with our laptop connected to one if its ports. All PING to (1 & 2)Airlive radios, (3) Northgate router, (4) a test PC, and the Internet were all successful. Iperf were also conducted and registered a throughput of up to 10mbps. The testing was conducted twice (January 17 & 18) which lasted for almost 3 hours on each occasion and the link was observed to be stable based on the aforementioned diagnostics conducted. Attached herewith are all the snapshots taken during the testing for your reference.

The connection, however, encountered problem when we transferred the connection from our laptop to the BelleVue network via the 3Com hub and your LAN extender. While the link remained connected and stable at the RF level, our PING to each hop points timed out. During this time, we observed that all the IP addresses that we are PING-ing would register a MAC address in the ARP table of our router and our laptop that is not their own. All four IP addresses appeared on the ARP table with a single "unidentified MAC address". The PING would restore only when we remove it from the 3Com hub, at which time our devices will restore its original and correct respective MAC addresses.

To try to resolve this, we changed the IP address settings of our router and radios but resulted to the same problem. We suspect that the switch that your LAN extender is connected to a router do not have proper VLAN configuration or there is a device or a PC that is causing this kind of malicious network activity.

This report is being provided to you to both inform you that the wireless link problem had been resolved, and to seek your attention about the problem above-mentioned.


Thank you very much.

Sanny Sison


Note:

The Bellevue link problem was finally resolved after months of speculations. The internal LAN problem at Bellevue, however, persisted, and shall be handled by their own IT people.