IBM Support in Lebanon After End of Life

IBM End-of-Life Support in Lebanon

The visible story in Lebanese telecoms is expansion: hundreds of thousands of households connected to fibre, mobile access sites multiplying, an airport network upgraded to current standards, capacity being built despite conditions that would excuse standing still. The part of that story nobody photographs is what happens behind it. Every new subscriber is a record in a billing system, an entry in a provisioning database, a line in a mediation batch — and those systems frequently run on IBM Power hardware sized for a subscriber base a fraction of the current one.

Growth lands hardest on the back office

Access networks scale by adding elements: another site, another port, another card. Back-office platforms do not scale that way. They absorb growth as larger tables, longer batch windows and more concurrent sessions on a machine that was specified years ago against a forecast nobody expected to be exceeded. The symptom is rarely a crash. It is a batch that used to finish at two and now finishes at five, and then one night does not finish at all.

Adding headroom to a withdrawn machine

The instinct at that point is replacement, which is a long and expensive programme. The cheaper intervention is usually to give the existing node more room: memory features to widen the working set, storage expansion to stop the dataset crowding its enclosure, faster drive features where the batch is IO-bound. None of that requires a new platform. All of it requires obtaining IBM features for a generation IBM has withdrawn, which is precisely what ends on the withdrawal date — the machine remains perfectly capable of accepting the upgrade, but the route to buying it closes.

Power conditions change the maintenance profile

A site drawing a substantial part of its electricity from private generation accumulates transfer events, and those events age specific components far faster than their rated life implies. Power supplies absorb the switching. Cache batteries in Storwize control enclosures cycle with every interruption and degrade accordingly. On a platform already under pressure from volume growth, losing a control enclosure to a battery nobody was tracking is an avoidable way to lose a night’s billing run.

Supporting growth on hardware the vendor has left

ICD supplies IBM Power and Storwize features matched by feature code and machine type, tested and serial-verified, with one to three years of warranty — both the replacement parts that keep an ageing platform running and the expansion features that let it carry more than it was sized for. Transit is three to four days from Cairo on the Levant lane, with clearance typically adding one to three days. Browse the IBM server parts catalogue, or the wider Lebanon server parts page.