The great thing about their working reality is that you can organize just about any eventuality. We know the people, we know the business logic, we know of "death to die." When the reality then they are in business growth, is a source of pride twofold: first, that management is excellent, you see because productivity and farm size grows. The second is growing on a solid and stable foundation. The role of us in IT is just that: create a foundation that does not show signs of yielding to any sort of demand to the Management.
Keyword: growth. Requirements: planning.
Some planning is one thing upon which they based their work: I speak of course of the Project Manager. The problem is that sometimes they do not know the problems that may occur. We, on the other hand, we know our field and we know perfectly what are the weak links in the chain. In business growth, in particular the addition of a home to a corporate network, the weak link is the time (but not for all projects?).
times in Italy to activate a new line data is nothing short of appalling. When it goes well, we make it in two weeks to have a connection, when it's bad ... we have to wait almost a year (see "TLC operators in the limelight). Of course we can not hope that all goes well, so (as always) we have to find a solution. Here's my vision.
"We start with a new home in a month." Announcement fantastic, they are all happy. The IT department normally assume a heavy where people start to panic. "A month!? But we'll never no! ".
with us is different.
a day. Here comes the mandate. Open a new place, there will be no people to work and play this or that role. Let's load data, a short meeting per capire quali sono i requisiti della sede, raccogliere i dati significanti come indirizzo, condizioni dello stabile e cose così. Partono le prime telefonate ai fornitori con cui abbiamo stretta collaborazione. Armadio rack mezza altezza, pannelli di permutazione, router, switch di rete, prese di distribuzione, UPS, server dipartimentale e centralino telefonico. Conferme degli ordini ricevuti in giornata (abbiamo dei fornitori tosti ;)) e i tempi di consegna: settimana prossima abbiamo tutto il materiale. Intanto sentiamo anche l’elettricista e chiediamo autorizzazione al Capo per fare un sopraluogo della sede. Già che ci siamo sentiamo anche i nostri operatori per capire quanti ceri dovremo accendere per avere le linee dati (funzionanti) at that place.
Day two: all quiet, the usual tram tram work. Some minor operation on Active Directory and system management / publishing. Continue to collect data on new home, you go to see her tomorrow.
Day three: vision of the home, an electrician and a representative of corporate management to understand what they want to do there. Framing the technical area, we define electrical work and any wiring. The seat is large, it will take even a wireless access point for the meeting room and a videoconferencing system. Already made phone calls to suppliers (ah yes, in the past months we have drawn up a strict policy on products and services we are going to implement, and even before the site is "thought" we already know what it will cost the infrastructure of the core). OK suppliers, everything proceeds normally.
Day seven: got most of the material, everything is functioning properly. We have already printed and labeled all the equipment, configure the network switch and the departmental server ... limps. It has a power supply failure. Support Request (NBD?) And meanwhile we close the closet, certifying the operation. We continue with our day by day, so that you never get bored.
Day Ten: ready rack, mounted and loaded into the van. We have an appointment with the electrician who has finished the laying of electric line in place. Arrive on site, the placement of the cabinet. Attached to the floor, plugged in, e. .. okay. The core of the site is functional (too bad there are still ADSL). Telecom, however, brought us the studs ISDN, so we can establish temporary connections. Verification of network points and correct configuration of the equipment. We ISDN connections and verify that everything is in order. We understand that it is (thanks to the documentation that we have drawn in the previous months).
Day Fifteen: users of the new headquarters are in the main office for a short training course on the system we're going to propose: Windows GUI and web applications available anywhere. They also illustrate our security policies and explain the reasons for them. Our aim is only to protect the corporation, so no objections. Brochures to hand to all users, with user manuals and any routine procedures (such as contacting the Help Desk, such as numbers for what, who are people in the IT department and what they do). In short, we introduce ourselves as people who have the desire to transmit something, just do not work behind the scenes. At the end we are all in the same boat. End of presentation, we leave room for some question e. .. duty coffee break.
Day winds from remote test site, the first operational checks. Users can actually work, there should be no major hitches. Double check the documentation to make minor changes to the project, we document everything and we'll get it.
twenty-nine Day: recent tests, definitive. We are OK with everything, we did troubleshooting lower in recent days for good luck, but now we're really ready.
Day thirty six in the morning: a man in place for technical testing, ignition system and configuration of those situations that can be considered as a "last minute". Nine in the morning: there's our new colleagues, they enter the office and we found our man (probably the twelfth coffee) hyper active and ready to teach them how to identify network devices and how to act on them: in other words: "read here, hit here." The cables are color-proof color blind, so we should not expect scenes like "oh my God the red wire or the blue wire?". But I do not believe I did the right we have also applied the labels clearly visible on the cables and pasted on the door of a better plan (which, moreover, has also written the phone number to call for technical support).
Day sixty (maybe) come the xDSL. The operator shall notify the company's technical services office must simply certify that the cables of xDSL on the patch panel, paragraph 23 and paragraph 24. Point 23 is in ATM0 port of router A, while point 24 goes into the router ATM0 B. The links are UP (wonderful invention the remote control) and then we can release the service on the corporate VPN. 45 seconds of disservice to the convergence of the whole system, only the operator, after 200 phone calls, hath been cut off from the router. No problem: the phone call to colleague in office: "I can follow the procedure to restart the router?". After two minutes, the router is manageable again, we end configurations (half coffee to remember that we use BGP and OSPF), and we find that everything works.
copy running-config startup config
and good work.
is a utopian vision? Sfidatemi.
0 comments:
Post a Comment