A large international corporation was building a hub/spoke system for most of the European Union nations. The hub was located in England, and the central support personnel were primarily English-speaking. The company hired contractors for each country, instructing them to install English on each server. When the German contractor got on-site, the local personnel convinced him he must be mistaken: Why wouldn't he install German on the German server? You can imagine the English team's surprise when it first attempted to remotely administer the server.
Lesson learned: You can't always get what you want, WAN you want.
A multinational corporation was working against the clock to build an international network. Unable to install fixed lines quickly enough, it opted for an ISDN network, which it believed would allow quick implementation (four to five days in most countries) and buy time for a longer-term solution with adequate bandwidth. This worked out fairly well in most countries. But when the company approached Telnor in Spain, the nationalized PTT said the ISDN switch was full and would not be available until someone relinquished service. Fortunately, the company was able to talk local IT folks from a sister unit into letting it share some WAN capacity as a stopgap measure.
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
