{"id":95643,"date":"2020-10-01T13:42:18","date_gmt":"2020-10-01T11:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs"},"modified":"2020-10-01T13:42:18","modified_gmt":"2020-10-01T11:42:18","slug":"network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","title":{"rendered":"Network-as-a-Service pentru o mare companie: un caz neobi\u0219nuit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Network-as-a-Service
\nCum s\u0103 actualiz\u0103m echipamentele de re\u021bea \u00eentr-o mare \u00eentreprindere f\u0103r\u0103 a opri produc\u021bia<\/i>? <\/i>Despre un proiect pe scar\u0103 larg\u0103 \u00een modul \u201eopera\u021bie pe inim\u0103 deschis\u0103\u201d vorbe\u0219te <\/i>managerul de gestionare a proiectelor Linxdatacenter, Oleg Fedorov.\u00a0<\/strong><\/i>
\n<\/a><\/noindex>
\n\u00cen ultimii c\u00e2\u021biva ani, am observat o cerere crescut\u0103 din partea clien\u021bilor pentru servicii legate de componentele de re\u021bea ale infrastructurii IT. Necesitatea conectivit\u0103\u021bii sistemelor IT, serviciilor, aplica\u021biilor, sarcinile de monitorizare \u0219i gestionare opera\u021bional\u0103 a afacerii \u00een aproape orice domeniu determin\u0103 ast\u0103zi companiile s\u0103 acorde o aten\u021bie sporit\u0103 re\u021belelor.\u00a0\u00a0<\/p>\n

Gama de solicit\u0103ri variaz\u0103 de la asigurarea rezilien\u021bei re\u021belei p\u00e2n\u0103 la crearea \u0219i gestionarea unui sistem autonom pentru clien\u021bi, cu achizi\u021bia de echipamente adreselor IP<\/a>, configurarea protocoalelor de rutare \u0219i gestionarea traficului conform politicilor organiza\u021biilor.<\/p>\n

De asemenea, cre\u0219te cererea pentru solu\u021bii complexe de construc\u021bie \u0219i \u00eentre\u021binere a infrastructurii de re\u021bea, \u00een primul r\u00e2nd din partea clien\u021bilor ale c\u0103ror infrastructuri de re\u021bea sunt construite de la zero sau sunt moral dep\u0103\u0219ite, necesit\u00e2nd modific\u0103ri serioase.\u00a0<\/p>\n

Aceast\u0103 tendin\u021b\u0103 s-a desf\u0103\u0219urat \u00een paralel cu perioada de dezvoltare \u0219i complicare a propriei infrastructuri de re\u021bea Linxdatacenter. Ne-am extins geografia prezen\u021bei noastre \u00een Europa prin conectarea la site-uri \u00eendep\u0103rtate, ceea ce a necesitat, la r\u00e2ndul s\u0103u, \u00eembun\u0103t\u0103\u021birea infrastructurii re\u021belei.\u00a0<\/p>\n

Compania a lansat un nou serviciu pentru clien\u021bi, Network-as-a-Service: ne asum\u0103m solu\u021bionarea tuturor sarcinilor de re\u021bea ale clien\u021bilor, permi\u021b\u00e2ndu-le s\u0103 se concentreze asupra afacerii principale.<\/p>\n

\u00cen vara anului 2020, s-a \u00eencheiat primul mare proiect \u00een aceast\u0103 direc\u021bie, despre care ne-ar pl\u0103cea s\u0103 vorbim.\u00a0<\/p>\n

La \u00eenceput\u00a0<\/h2>\n

\nUn mare complex industrial s-a adresat nou\u0103 pentru modernizarea p\u0103r\u021bii de re\u021bea a infrastructurii pe unul dintre site-urile sale. Era necesar\u0103 \u00eenlocuirea echipamentului vechi cu unul nou, inclusiv nucleul re\u021belei.<\/p>\n

Ultima modernizare a echipamentului din \u00eentreprindere a avut loc acum aproximativ 10 ani. Noua conducere a companiei a decis s\u0103 \u00eembun\u0103t\u0103\u021beasc\u0103 conectivitatea, \u00eencep\u00e2nd cu actualizarea infrastructurii la cel mai de baz\u0103, nivel fizic.\u00a0<\/p>\n

Proiectul a fost \u00eemp\u0103r\u021bit \u00een dou\u0103 p\u0103r\u021bi: upgrade-ul serverelor \u0219i echipamentelor de re\u021bea. Noi am fost responsabili pentru a doua parte.\u00a0<\/p>\n

Cerin\u021bele de baz\u0103 pentru lucr\u0103ri au inclus minimizarea timpilor de nefunc\u021bionare a liniilor de produc\u021bie ale \u00eentreprinderii \u00een timpul desf\u0103\u0219ur\u0103rii lucr\u0103rilor (iar \u00een unele zone, excluderea complet\u0103 a timpilor de nefunc\u021bionare). Orice oprire \u00eenseamn\u0103 pierderi financiare directe pentru client, ceea ce nu trebuia s\u0103 se \u00eent\u00e2mple \u00een niciun caz. Av\u00e2nd \u00een vedere regimul de lucru al obiectivului 24x7x365 \u0219i lipsa total\u0103 a perioadelor de nefunc\u021bionare planificate \u00een practica \u00eentreprinderii, ne-a fost stabilit\u0103 sarcina de a efectua, \u00een esen\u021b\u0103, o opera\u021biune pe un inim\u0103 deschis\u0103. Aceasta a devenit caracteristica principal\u0103 a proiectului.<\/p>\n

S\u0103 incepem<\/h2>\n

\nLucr\u0103rile au fost planificate conform principiului de a se deplasa de la nodurile re\u021belei \u00eendep\u0103rtate de nucleu c\u0103tre cele mai apropiate, precum \u0219i de la cele care au un impact mai mic asupra func\u021bion\u0103rii liniilor de produc\u021bie c\u0103tre cele care influen\u021beaz\u0103 direct aceast\u0103 activitate.\u00a0<\/p>\n

De exemplu, dac\u0103 lu\u0103m nodul re\u021belei din departamentul de v\u00e2nz\u0103ri, o \u00eentrerupere a comunica\u021biei ca urmare a lucr\u0103rilor din acest departament nu va afecta \u00een niciun fel produc\u021bia. Totu\u0219i, un astfel de incident ne va ajuta, ca subcontractori, s\u0103 verific\u0103m corectitudinea abord\u0103rii aleas\u0103 pentru lucrul cu astfel de noduri \u0219i, corect\u00e2nd ac\u021biunile, s\u0103 lucr\u0103m la etapele urm\u0103toare ale proiectului.\u00a0<\/p>\n

Trebuie s\u0103 \u00eenlocuim nu doar nodurile \u0219i firele din re\u021bea, ci \u0219i s\u0103 configur\u0103m corect toate componentele pentru func\u021bionarea adecvat\u0103 a solu\u021biei \u00een ansamblu. Configura\u021biile au fost verificate astfel: \u00eencep\u00e2nd lucr\u0103rile de la distan\u021ba fa\u021b\u0103 de nucleu, ne-am acordat practic un \u201edrept la gre\u0219eal\u0103\u201d, neexpun\u00e2nd la risc sec\u021biunile critice ale activit\u0103\u021bii \u00eentreprinderii.\u00a0<\/p>\n

Am identificat zonele care nu afecteaz\u0103 procesul de produc\u021bie, precum \u0219i sec\u021biunile critice \u2013 atelierele, blocul de \u00eenc\u0103rcare-desc\u0103rcare, depozitele etc. La punctele cheie, cu clientul a fost convenit timpul acceptabil de nefunc\u021bionare pentru fiecare nod al re\u021belei \u00een parte: de la 1 la 15 minute. Evitarea complet\u0103 a deconect\u0103rii unor noduri ale re\u021belei a fost imposibil\u0103, deoarece cablul trebuie deconectat fizic din echipamentele vechi \u00een cele noi, iar \u00een procesul de comutare trebuie, de asemenea, s\u0103 desf\u0103\u0219ur\u0103m \u201ep\u0103rul\u201d de fire, care s-a format \u00een perioada de c\u00e2\u021biva ani de exploatare f\u0103r\u0103 \u00eentre\u021binere corespunz\u0103toare (una dintre consecin\u021bele externaliz\u0103rii muncii de instalare a liniilor de cablu).<\/p>\n

Lucr\u0103rile au fost \u00eemp\u0103r\u021bite \u00een mai multe etape.<\/p>\n

Etapa 1<\/b> \u2013 Audit. Preg\u0103tirea \u0219i agrearea abord\u0103rii pentru planificarea lucr\u0103rilor \u0219i evaluarea preg\u0103tirii echipelor: clientul, contractorul ce efectueaz\u0103 montajul \u0219i echipa noastr\u0103.<\/p>\n

Etapa 2<\/b> \u2013 Elaborarea formatului pentru desf\u0103\u0219urarea lucr\u0103rilor, cu o analiz\u0103 detaliat\u0103 \u0219i o planificare profund\u0103. Am ales formatul listei de verificare, cu specificarea exact\u0103 a ordinii \u0219i secven\u021bei ac\u021biunilor, p\u00e2n\u0103 la secven\u021ba de comutare a cablurilor patch pe porturi.<\/p>\n

Etapa 3<\/b> \u2013 Derularea lucr\u0103rilor \u00een dulapuri care nu influen\u021beaz\u0103 produc\u021bia. Evaluarea \u0219i corectarea timpului de nefunc\u021bionare pentru etapele ulterioare de lucr\u0103ri.<\/p>\n

Etapa 4<\/b> \u2013 Derularea lucr\u0103rilor \u00een dulapuri care influen\u021beaz\u0103 direct produc\u021bia. Evaluarea \u0219i corectarea timpului de nefunc\u021bionare pentru etapa final\u0103 a lucr\u0103rilor.<\/p>\n

Etapa 5<\/b> \u2013 Derularea lucr\u0103rilor \u00een sala serverelor pentru comutarea echipamentului r\u0103mas. Lansarea pe rutare pe noul nucleu.<\/p>\n

Etapa 6<\/b> \u2013 Comutarea succesiv\u0103 a nucleului sistemului de la configura\u021biile de re\u021bea vechi la cele noi pentru o tranzi\u021bie lin\u0103 a \u00eentregului complex de sistem (VLAN, rutare etc.). \u00cen aceast\u0103 etap\u0103, am conectat to\u021bi utilizatorii \u0219i am transferat toate serviciile pe noul echipament, am verificat corectitudinea conexiunii, ne-am asigurat c\u0103 niciunul dintre serviciile \u00eentreprinderii nu s-a oprit, garant\u00e2nd c\u0103, \u00een caz de apari\u021bia unor probleme, acestea ar fi legate direct de nucleu, ceea ce a facilitat rezolvarea posibilelor defec\u021biuni \u0219i configurarea final\u0103.\u00a0<\/p>\n

Frizura cablurilor<\/h2>\n

\nProiectul s-a dovedit a fi complicat \u0219i din cauza condi\u021biilor ini\u021biale complexe.\u00a0<\/p>\n

\u00cen primul r\u00e2nd, este vorba despre un num\u0103r uria\u0219 de noduri \u0219i por\u021biuni de re\u021bea, cu o topologie complicat\u0103 \u0219i clasificarea cablurilor \u00een func\u021bie de destina\u021bia lor. Astfel de 'frizuri' trebuiau scoase din dulapuri \u0219i aranjate cu grij\u0103, stabilind fiecare cablu de unde provine \u0219i unde duce.\u00a0<\/p>\n

Asta ar\u0103ta aproximativ a\u0219a:<\/p>\n

\"Network-as-a-Service
\na\u0219a:<\/p>\n

\"Network-as-a-Service
\nsau a\u0219a:\u00a0<\/p>\n

\"Network-as-a-Service
\n\u00cen al doilea r\u00e2nd, pentru fiecare dintre aceste sarcini a fost necesar s\u0103 preg\u0103tim un fi\u0219ier cu descrierea procesului. \u201eLu\u0103m cablul X din portul 1 al echipamentului vechi, \u00eel conect\u0103m la portul 18 al noului echipament.\u201d P\u0103rea simplu, dar c\u00e2nd datele de intrare con\u021bin 48 de porturi complet ocupate \u0219i op\u021biunea de oprire nu este disponibil\u0103 (ne amintim de 24x7x365), singura solu\u021bie este s\u0103 lucr\u0103m pe blocuri. Cu c\u00e2t putem scoate mai multe cabluri din echipamentul vechi simultan, cu at\u00e2t mai repede putem s\u0103 le aranj\u0103m \u0219i s\u0103 le introducem \u00een noua \u201ecoroan\u0103\u201d de re\u021bea, evit\u00e2nd \u00eentreruperile \u0219i opririle \u00een func\u021bionarea re\u021belei.\u00a0<\/p>\n

Prin urmare, \u00een etapa de preg\u0103tire am realizat o \u00eemp\u0103r\u021bire a re\u021belei \u00een blocuri \u2013 fiecare dintre acestea coresponda unui VLAN specific. Fiecare port (sau un subset al acestora) de pe echipamentul vechi era un VLAN din noua topologie a re\u021belei. Le-am grupat astfel: pe primele porturi ale switch-ului s-au plasat re\u021belele utilizatorilor, \u00een mijloc \u2013 re\u021belele de produc\u021bie, iar pe ultimele \u2013 punctele de acces \u0219i uplink-urile.\u00a0<\/p>\n

Aceast\u0103 abordare a permis, \u00eentr-o singur\u0103 mi\u0219care, s\u0103 scoatem \u0219i s\u0103 aranj\u0103m din echipamentul vechi nu un cablu, ci 10-15. Acest lucru a accelerat semnificativ procesul de lucru.\u00a0\u00a0<\/p>\n

Apropo, iat\u0103 cum arat\u0103 cablurile \u00een dulapuri dup\u0103 ce au fost aranjate:\u00a0<\/p>\n

\"Network-as-a-Service
\nsau, de exemplu, a\u0219a:\u00a0<\/p>\n

\"Network-as-a-Service
\nDup\u0103 finalizarea etapei a 2-a, am luat o pauz\u0103 pentru analiza erorilor \u0219i dinamica proiectului. De exemplu, imediat au ie\u0219it la iveal\u0103 mici neajunsuri din cauza inexactit\u0103\u021bilor din schemele de re\u021bea furnizate (conector gre\u0219it \u00een schem\u0103 \u2013 patch cord gre\u0219it cump\u0103rat \u0219i necesitatea de a-l \u00eenlocui).\u00a0<\/p>\n

Pauza a fost necesar\u0103, deoarece, lucr\u00e2nd cu serverul, orice mic e\u0219ec \u00een proces era inadmisibil. Dac\u0103 s-a stabilit obiectivul de a asigura un timp de nefunc\u021bionare \u00een segmentul re\u021belei de maximum 5 minute, acesta nu putea fi dep\u0103\u0219it. Orice abateri posibile de la program trebuiau s\u0103 fie coordonate cu clientul.\u00a0<\/p>\n

Cu toate acestea, planificarea prealabil\u0103 \u0219i \u00eemp\u0103r\u021birea proiectului \u00een blocuri au permis respectarea timpului de nefunc\u021bionare planificat pe toate segmentele, iar \u00een cele mai multe cazuri s-a reu\u0219it chiar s\u0103 ne descurc\u0103m f\u0103r\u0103 acesta.\u00a0<\/p>\n

Provocarea timpului \u2013 proiectul sub COVID\u00a0<\/h2>\n

\nF\u0103r\u0103 dificult\u0103\u021bi suplimentare, totu\u0219i, nu s-a putut. Desigur, coronavirusul a fost unul dintre obstacole.\u00a0<\/p>\n

Lucr\u0103rile au fost complicate de faptul c\u0103 a \u00eenceput pandemia \u0219i nu a fost posibil ca to\u021bi speciali\u0219tii implica\u021bi \u00een proces s\u0103 fie prezen\u021bi pe \u0219antierul clientului. Pe \u0219antier au fost accepta\u021bi doar angaja\u021bii organiza\u021biei de montaj, iar controlul a fost realizat printr-o camer\u0103 \u00een Zoom \u2013 \u00een care s-au aflat inginerul de re\u021bea din partea Linxdatacenter, eu ca manager de proiect, inginerul de re\u021bea din partea clientului, responsabil pentru desf\u0103\u0219urarea lucr\u0103rilor, \u0219i echipa care executa lucr\u0103rile de montaj.<\/p>\n

Pe parcursul lucr\u0103rilor au ap\u0103rut probleme neprev\u0103zute, iar ajust\u0103rile au trebuit f\u0103cute pe parcurs. Astfel, am reu\u0219it s\u0103 prevenim rapid influen\u021ba factorului uman (erori \u00een schem\u0103, erori \u00een determinarea statutului de activitate a interfe\u021bei etc.).<\/p>\n

De\u0219i formatul de lucru la distan\u021b\u0103 p\u0103rea neobi\u0219nuit la \u00eenceputul proiectului, ne-am adaptat destul de repede la noile condi\u021bii \u0219i am ajuns \u00een etapa final\u0103 a lucr\u0103rilor.\u00a0<\/p>\n

Am lansat o configura\u021bie temporar\u0103 a set\u0103rilor re\u021belei pentru a permite func\u021bionarea \u00een paralel a dou\u0103 nuclee de re\u021bea \u2013 vechi \u0219i nou \u2013 pentru a asigura o tranzi\u021bie lin\u0103. Totu\u0219i, s-a dovedit c\u0103 nu fusese eliminat\u0103 o linie inutil\u0103 din fi\u0219ierul de configura\u021bie al noului nucleu, iar tranzi\u021bia nu a avut loc. Acest lucru ne-a determinat s\u0103 pierdem timp pentru a g\u0103si problema.\u00a0<\/p>\n

Am constatat c\u0103 traficul principal era transmis corect, iar traficul de control nu ajungea la nod prin noul nucleu. Datorit\u0103 separ\u0103rii clare a proiectului \u00een etape, am reu\u0219it s\u0103 stabilim destul de repede sec\u021biunea de re\u021bea unde a ap\u0103rut dificultatea, s\u0103 identific\u0103m problema \u0219i s\u0103 o remediem.\u00a0<\/p>\n

Iar ca rezultat<\/h2>\n

\nConcluziile tehnice ale proiectului\u00a0<\/i><\/p>\n

\u00cen primul r\u00e2nd, a fost creat un nou nucleu al noii re\u021bele a \u00eentreprinderii, pentru care am construit inele fizice\/logice. Aceasta a fost realizat\u0103 astfel \u00eenc\u00e2t fiecare switch din re\u021bea s\u0103 aib\u0103 un \u00abal doilea bra\u021b\u00bb. \u00cen vechea re\u021bea, multe switch-uri erau conectate la nucleu printr-o singur\u0103 rut\u0103, un singur bra\u021b (uplink). Dac\u0103 acesta se rupea, switch-ul devenea complet inaccesibil. Iar dac\u0103 se conectau mai multe switch-uri printr-un singur uplink, o avarie afectua un \u00eentreg departament sau linie de produc\u021bie a \u00eentreprinderii.\u00a0<\/p>\n

\u00cen noua re\u021bea, niciun incident de re\u021bea sever nu va putea, \u00een niciun scenariu, s\u0103 \u00abpune la p\u0103m\u00e2nt\u00bb \u00eentreaga re\u021bea sau o por\u021biune semnificativ\u0103 a acesteia.\u00a0<\/p>\n

90% din echipamentele de re\u021bea au fost actualizate, convertoarele de mediu au fost scoase din func\u021biune, iar necesitatea de linii electrice dedicate pentru alimentarea echipamentelor a fost eliminat\u0103 prin conectarea la switch-uri PoE, unde alimentarea se realizeaz\u0103 prin cabluri Ethernet.\u00a0<\/p>\n

De asemenea, toate conexiunile optice din sala serverului \u0219i din dulapuri la fa\u021ba locului au fost marcate \u2013 \u00een toate nodurile cheie ale re\u021belei. Acest lucru a permis preg\u0103tirea unui schema topologic\u0103 a echipamentelor \u0219i conexiunilor din re\u021bea, reflect\u00e2nd starea lor actual\u0103.\u00a0<\/p>\n

Schema re\u021belei<\/i>
\n\"Network-as-a-Service
\nCel mai important rezultat din punct de vedere tehnic: lucr\u0103rile infrastructurale relativ ample au fost realizate rapid, f\u0103r\u0103 a crea vreo perturbare \u00een activitatea \u00eentreprinderii \u0219i practic f\u0103r\u0103 ca personalul s\u0103 observe.\u00a0<\/p>\n

Rezultatele de afaceri ale proiectului<\/i><\/p>\n

Din punctul meu de vedere, acest proiect este interesant \u00een primul r\u00e2nd din perspectiva organizatoric\u0103, nu tehnic\u0103. Complexitatea a constatat \u00een primul r\u00e2nd \u00een planificarea \u0219i g\u00e2ndirea pa\u0219ilor pentru implementarea sarcinilor de proiect.\u00a0<\/p>\n

Succesul proiectului ne permite s\u0103 afirm\u0103m c\u0103 ini\u021biativa noastr\u0103 de a dezvolta direc\u021bia de re\u021bea \u00een cadrul portofoliului de servicii Linxdatacenter este o alegere corect\u0103 \u00een direc\u021bia de dezvoltare a companiei. O abordare responsabil\u0103 \u00een gestionarea proiectelor, o strategie bine g\u00e2ndit\u0103 \u0219i o planificare clar\u0103 ne-au permis s\u0103 realiz\u0103m lucrarea la un nivel adecvat.\u00a0<\/p>\n

Confirmarea calit\u0103\u021bii muncii este cererea din partea clientului pentru continuarea serviciilor de modernizare a re\u021belei \u00een celelalte loca\u021bii ale sale din Rusia.
\n
Sursa: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u043e\u0431\u043e\u0440\u0443\u0434\u043e\u0432\u0430\u043d\u0438\u0435 \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u043e\u043c \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0438 \u0431\u0435\u0437 \u043e\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0441\u0442\u0432\u0430? \u041e \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u043d\u043e\u043c \u043f\u0440\u043e\u0435\u043a\u0442\u0435 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 \u00ab\u043e\u043f\u0435\u0440\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0442\u043a\u0440\u044b\u0442\u043e\u043c \u0441\u0435\u0440\u0434\u0446\u0435\u00bb \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440 \u043f\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044e \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u043c\u0438 Linxdatacenter \u041e\u043b\u0435\u0433 \u0424\u0435\u0434\u043e\u0440\u043e\u0432.\u00a0 \u0412 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043c\u044b \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u043c \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u043d\u044b\u0439 \u0441\u043f\u0440\u043e\u0441 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u043e\u0432 \u043d\u0430 \u0443\u0441\u043b\u0443\u0433\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0435 \u0441 \u0441\u0435\u0442\u0435\u0432\u044b\u043c \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u043c \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b. \u041f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u0432 \u0441\u0432\u044f\u0437\u043d\u043e\u0441\u0442\u0438 \u0418\u0422-\u0441\u0438\u0441\u0442\u0435\u043c, \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u0437\u0430\u0434\u0430\u0447\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430 \u0438 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0433\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441\u043e\u043c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":95644,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-95643","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Network-as-a-Service pentru o mare \u00eentreprindere: caz non-standard | ProHoster","description":"Cum s\u0103 actualizezi re\u021beaua.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Network-as-a-Service \u0434\u043b\u044f \u043a\u0440\u0443\u043f\u043d\u043e\u0433\u043e \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f: \u043d\u0435\u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u044b\u0439 \u043a\u0435\u0439\u0441 | ProHoster","og:description":"\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-10-01T11:42:18+00:00","article:modified_time":"2020-10-01T11:42:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"95643","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:01:22","updated":"2026-02-08 20:40:13","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=95643"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95643\/revisions"}],"predecessor-version":[{"id":158014,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/95643\/revisions\/158014"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/95644"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=95643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=95643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=95643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}