{"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\/sq\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","title":{"rendered":"Network-as-a-Service p\u00ebr nd\u00ebrmarrje t\u00eb m\u00ebdha: rast unik","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Network-as-a-Service
\nSi t\u00eb rinovohet pajisja rrjetore n\u00eb nj\u00eb nd\u00ebrmarrje t\u00eb madhe pa ndaluar prodhimin<\/i>? <\/i>P\u00ebr nj\u00eb projekt t\u00eb gjer\u00eb n\u00eb m\u00ebnyr\u00ebn e 'operacionit n\u00eb zem\u00ebr t\u00eb hapur' flet <\/i>menaxheri i menaxhimit t\u00eb projekteve n\u00eb Linxdatacenter, Oleg Fedorov.\u00a0<\/strong><\/i>
\n<\/a><\/noindex>
\nN\u00eb vitet e fundit, kemi v\u00ebrejtur nj\u00eb rritje t\u00eb k\u00ebrkes\u00ebs nga klient\u00ebt p\u00ebr sh\u00ebrbime q\u00eb lidhen me komponentin rrjetor t\u00eb infrastruktur\u00ebs IT. Nevoja p\u00ebr lidhshm\u00ebrin\u00eb e sistemeve IT, sh\u00ebrbimeve, aplikacioneve dhe detyrat e monitorimit dhe menaxhimit operativ t\u00eb biznesit n\u00eb pothuajse \u00e7do fush\u00eb po e detyrojn\u00eb sot kompanit\u00eb t'i kushtojn\u00eb v\u00ebmendje t\u00eb ve\u00e7ant\u00eb rrjeteve.\u00a0\u00a0<\/p>\n

Fushat e k\u00ebrkes\u00ebs shkojn\u00eb nga sigurimi i q\u00ebndrueshm\u00ebris\u00eb s\u00eb rrjetit deri te krijimi dhe menaxhimi i nj\u00eb sistemi autonom t\u00eb klientit me blerjen e nj\u00eb blloku IP-adresave<\/a>, konfigurimin e protokolleve t\u00eb rrug\u00ebzimit dhe menaxhimin e trafikut sipas politikave t\u00eb organizatave.<\/p>\n

Po ashtu, rritet k\u00ebrkesa p\u00ebr zgjidhje t\u00eb plota p\u00ebr nd\u00ebrtimin dhe mir\u00ebmbajtjen e infrastruktur\u00ebs rrjetore, kryesisht nga klient\u00ebt, infrastruktura e t\u00eb cil\u00ebve nd\u00ebrtuhet nga e para ose \u00ebsht\u00eb morali i vjet\u00ebr, duke k\u00ebrkuar modifikime t\u00eb konsiderueshme.\u00a0<\/p>\n

Ky trend p\u00ebrkoi me zhvillimin dhe kompleksitetin e infrastruktur\u00ebs son\u00eb rrjetore Linxdatacenter. Ne kemi zgjeruar gjeografin\u00eb e pranis\u00eb son\u00eb n\u00eb Evrop\u00eb me lidhjen e vendeve t\u00eb larg\u00ebta, gj\u00eb q\u00eb nga ana tjet\u00ebr k\u00ebrkoi edhe p\u00ebrmir\u00ebsimin e infrastruktur\u00ebs rrjetore.\u00a0<\/p>\n

Kompania lansoi nj\u00eb sh\u00ebrbim t\u00eb ri p\u00ebr klient\u00ebt, Network-as-a-Service: ne marrim p\u00ebrsip\u00ebr zgjidhjen e t\u00eb gjitha detyrave rrjetore t\u00eb klient\u00ebve, duke u lejuar atyre t\u00eb p\u00ebrqendrohen te biznesi i tyre kryesor.<\/p>\n

N\u00eb ver\u00ebn e vitit 2020 u p\u00ebrfundua projekti i par\u00eb t\u00eb madh n\u00eb k\u00ebt\u00eb drejtim, p\u00ebr t\u00eb cilin do t\u00eb doja t\u00eb flisja.\u00a0<\/p>\n

N\u00eb fillim\u00a0<\/h2>\n

\nNj\u00eb kompleks i madh industrial na kontaktoi p\u00ebr modernizimin e pjes\u00ebs s\u00eb rrjetit t\u00eb infrastruktur\u00ebs n\u00eb nj\u00eb nga nd\u00ebrmarrjet e tij. Duhej t\u00eb b\u00ebhej z\u00ebvend\u00ebsimi i pajisjeve t\u00eb vjetra me t\u00eb reja, duke p\u00ebrfshir\u00eb edhe b\u00ebrtham\u00ebn e rrjetit.<\/p>\n

Modernizimi i fundit i pajisjeve n\u00eb nd\u00ebrmarrje u zhvillua rreth 10 vjet m\u00eb par\u00eb. Drejtoria e re e nd\u00ebrmarrjes vendosi t\u00eb p\u00ebrmir\u00ebsoj\u00eb lidhshm\u00ebrin\u00eb, duke filluar nga rinovimi i infrastruktur\u00ebs n\u00eb nivelin m\u00eb themelor, at\u00eb fizik.\u00a0<\/p>\n

Projekti u ndan n\u00eb dy pjes\u00eb: p\u00ebrmir\u00ebsimi i parkut t\u00eb server\u00ebve dhe pajisjeve rrjetore. Ne ishim p\u00ebrgjegj\u00ebs p\u00ebr pjes\u00ebn e dyt\u00eb.\u00a0<\/p>\n

K\u00ebrkesat themelore p\u00ebr punimet p\u00ebrfshinin minimizimin e ndalesave t\u00eb linjave prodhuese t\u00eb nd\u00ebrmarrjes gjat\u00eb ekzekutimit t\u00eb pun\u00ebve (dhe n\u00eb disa mjete t\u00eb plota eliminimin e ndalesave). \u00c7do ndales\u00eb \u2013 do t\u00eb thoshte humbje t\u00eb drejtp\u00ebrdrejt\u00eb financiare p\u00ebr klientin, gj\u00eb q\u00eb nuk duhej t\u00eb ndodhte n\u00eb asnj\u00eb rast. Duke marr\u00eb parasysh modin e pun\u00ebs t\u00eb objektit 24x7x365, si dhe me marr\u00eb parasysh munges\u00ebn totale t\u00eb periudhave t\u00eb ndalesave t\u00eb planifikuara n\u00eb praktik\u00ebn e nd\u00ebrmarrjes, na u caktua nj\u00eb detyr\u00eb q\u00eb, n\u00eb thelb, t\u00eb ekzekutonim nj\u00eb operacion n\u00eb zem\u00ebr t\u00eb hapur. Kjo ishte dhe karakteristika kryesore e projektit.<\/p>\n

Le t\u00eb fillojm\u00eb<\/h2>\n

\nPunimet ishin planifikuar sipas parimit t\u00eb l\u00ebvizjes nga nyjet m\u00eb t\u00eb larg\u00ebta nga b\u00ebrthama e rrjetit drejt atyre m\u00eb t\u00eb af\u00ebrta, si dhe nga ato q\u00eb ndikonin m\u00eb pak n\u00eb pun\u00ebn e linjave prodhuese drejt atyre q\u00eb kishin nj\u00eb ndikim t\u00eb drejtp\u00ebrdrejt\u00eb.\u00a0<\/p>\n

P\u00ebr shembull, n\u00ebse p\u00ebrjashtojm\u00eb nj\u00eb nyje t\u00eb rrjetit n\u00eb departamentin e shitjeve, at\u00ebher\u00eb ndalimi i lidhjes si rezultat i punimeve n\u00eb k\u00ebt\u00eb departament nuk do t\u00eb prekte prodhimin. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, nj\u00eb ngjarje e till\u00eb do t\u00eb ndihmonte si kontraktori p\u00ebr t\u00eb kontrolluar sakt\u00ebsin\u00eb e qasjes s\u00eb zgjedhur p\u00ebr pun\u00ebn n\u00eb k\u00ebto nyje dhe, duke korrigjuar veprimet, do t\u00eb vazhdonim n\u00eb fazat e tjera t\u00eb projektit.\u00a0<\/p>\n

Duhet t\u00eb z\u00ebvend\u00ebsohen jo vet\u00ebm nyjet dhe kabllot n\u00eb rrjet, por gjithashtu t\u00eb konfigurohen sakt\u00ebsisht t\u00eb gjitha komponent\u00ebt p\u00ebr pun\u00ebn e duhur t\u00eb zgjidhjes n\u00eb t\u00ebr\u00ebsi. K\u00ebto konfigurime u kontrolluan n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb: duke filluar pun\u00ebn nga larg b\u00ebrtham\u00ebs, si\u00e7 duket, i jepnim vetes 't\u00eb drejt\u00ebn p\u00ebr t\u00eb gabuar', pa rrezikuar zonat kritike p\u00ebr pun\u00ebn e nd\u00ebrmarrjes.\u00a0<\/p>\n

Ne identifikuam zona q\u00eb nuk ndikojn\u00eb n\u00eb procesin e prodhimit, si dhe zona kritike \u2013 pun\u00ebtoria, blloku i shkarkimit dhe ngarkimit, magazinat etj. N\u00eb zonat ky\u00e7e u miratua nga klienti koha e pranueshme e ndales\u00ebs p\u00ebr \u00e7do nyje rrjeti ve\u00e7mas: nga 1 deri n\u00eb 15 minuta. Plot\u00ebsisht t\u00eb shmangim ndalimin e nyjeve t\u00eb ve\u00e7anta t\u00eb rrjetit ishte e pamundur, pasi kablloja duhet t\u00eb transferohej fizikisht nga pajisja e vjet\u00ebr te ajo e re, dhe gjat\u00eb procesit t\u00eb kalimit ne duhet gjithashtu t\u00eb deshtojm\u00eb 'boshll\u00ebkun' e kabllove, i cili ishte formuar gjat\u00eb disa viteve t\u00eb p\u00ebrdorimit pa kujdes t\u00eb duhur (nj\u00eb nga pasojat e jashtme t\u00eb pun\u00ebve n\u00eb montimin e linjave kabllore).<\/p>\n

Punimet u ndan\u00eb n\u00eb disa etapa.<\/p>\n

Faza 1<\/b> \u2013 Audit. P\u00ebrgatitja dhe miratimi i qasjes p\u00ebr planifikimin e punimeve dhe vler\u00ebsimi i gatishm\u00ebris\u00eb s\u00eb ekipeve: klientit, kontraktorit q\u00eb po kryen instalimin, dhe ekipit ton\u00eb.<\/p>\n

Faza 2<\/b> \u2013 Zhvillimi i formatit p\u00ebr kryerjen e punimeve, me analiz\u00eb dhe planifikim t\u00eb thell\u00eb dhe t\u00eb detajuar. Zgjedh\u00ebm formatin e list\u00ebs kontrolluese me p\u00ebrcaktimin e sakt\u00eb t\u00eb rendit dhe sekuenc\u00ebs s\u00eb veprimeve, deri te rendi i kalimit t\u00eb patch-kord\u00ebve n\u00eb porta.<\/p>\n

Faza 3<\/b> \u2013 Kryerja e punimeve n\u00eb dollap\u00ebt q\u00eb nuk ndikojn\u00eb n\u00eb prodhim. Vler\u00ebsimi dhe rregullimi i koh\u00ebs s\u00eb pushimit p\u00ebr etapet e m\u00ebvonshme t\u00eb punimeve.<\/p>\n

Faza 4<\/b> \u2013 Kryerja e punimeve n\u00eb dollap\u00ebt q\u00eb ndikojn\u00eb drejtp\u00ebrdrejt n\u00eb prodhim. Vler\u00ebsimi dhe rregullimi i koh\u00ebs s\u00eb pushimit p\u00ebr etap\u00ebn finale t\u00eb pun\u00ebve.<\/p>\n

Etapa 5<\/b> \u2013 Kryerja e punimeve n\u00eb server p\u00ebr kalimin e pajisjeve t\u00eb mbetura. Aktivizimi i rutimit n\u00eb thelbin e ri.<\/p>\n

Etapa 6<\/b> \u2013 Kalimi i radh\u00ebs i thelbit t\u00eb sistemit nga konfigurimet e vjetra rrjetore n\u00eb t\u00eb reja p\u00ebr nj\u00eb kalim t\u00eb qet\u00eb t\u00eb gjith\u00eb kompleksit t\u00eb sistemit (VLAN, rutim, etj.). N\u00eb k\u00ebt\u00eb etap\u00eb lidh\u00ebm t\u00eb gjith\u00eb p\u00ebrdoruesit dhe transferuam t\u00eb gjitha sh\u00ebrbimet n\u00eb pajisjet e reja, kontrolluam sakt\u00ebsin\u00eb e lidhjes, siguruam q\u00eb asnj\u00eb nga sh\u00ebrbimet e nd\u00ebrmarrjes nuk ndaloi, garantuam q\u00eb n\u00eb rast t\u00eb ndonj\u00eb problemi, ato do t\u00eb ishin t\u00eb lidhura drejtp\u00ebrdrejt me thelbin, duke leht\u00ebsuar zgjidhjen e mundshme t\u00eb problemeve dhe konfigurimin p\u00ebrfundimtar.\u00a0<\/p>\n

P\u00ebrkujdesja p\u00ebr kabllot<\/h2>\n

\nProjekti doli jo i leht\u00eb edhe p\u00ebr shkak t\u00eb kushteve t\u00eb komplikuara fillestare.\u00a0<\/p>\n

S\u00eb pari, kjo \u00ebsht\u00eb nj\u00eb sasi e madhe nyjash dhe pjes\u00ebsh t\u00eb rrjetit, me topologji t\u00eb komplikuar dhe klasifikimin e kabllove sipas q\u00ebllimit t\u00eb tyre. K\u00ebto 'p\u00ebrkujdesje' duhej t\u00eb nxirreshin nga dollap\u00ebt dhe t\u00eb 'p\u00ebrkujdeseshin' me kujdes, duke e kuptuar se cili kabllo p\u00ebr \u00e7far\u00eb po shkon.\u00a0<\/p>\n

Duket k\u00ebshtu:<\/p>\n

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

\"Network-as-a-Service
\nose k\u00ebshtu:\u00a0<\/p>\n

\"Network-as-a-Service
\nS\u00eb dyti, p\u00ebr \u00e7do p\u00ebrpjekje t\u00eb till\u00eb ishte e nevojshme t\u00eb p\u00ebrgatitej nj\u00eb skedar p\u00ebrshkrimi t\u00eb procesit. 'Merr nj\u00eb kabllo X nga porta 1 e pajisjeve t\u00eb vjetra dhe vendoseni n\u00eb port\u00ebn 18 t\u00eb pajisjeve t\u00eb reja.' D\u00ebgjohet e thjesht\u00eb, por kur ke n\u00eb t\u00eb dh\u00ebnat fillestare 48 porta krejt\u00ebsisht t\u00eb mbushura, dhe gjithashtu mungon opsioni i pushimit (ne e mbajm\u00eb mend p\u00ebr 24x7x365), zgjidhja e vetme \u00ebsht\u00eb t\u00eb punosh n\u00eb blloqe. Sa m\u00eb shum\u00eb kabllot mund t\u00eb nxirren nga pajisjet e vjetra nj\u00eb her\u00eb, aq m\u00eb shpejt mund t'i p\u00ebrkujdesim dhe t'i vendosim n\u00eb 'hekurudhat' e reja t\u00eb rrjetit, duke shmangur nd\u00ebrprerjet dhe pushimet n\u00eb pun\u00ebn e rrjetit.\u00a0<\/p>\n

Prandaj, n\u00eb faz\u00ebn p\u00ebrgatitore, ne b\u00ebm\u00eb ndarjen e rrjetit n\u00eb blloqe \u2013 secili prej tyre i p\u00ebrkiste nj\u00eb VLAN t\u00eb caktuar. \u00c7do port (ose n\u00ebngrup i tij) n\u00eb pajisjet e vjetra \u00ebsht\u00eb nj\u00eb nga VLAN-t\u00eb n\u00eb topologjin\u00eb e re t\u00eb rrjetit. Ne i grupuam ato k\u00ebshtu: n\u00eb portat e para t\u00eb kaluareve vendos\u00ebm rrjetet e p\u00ebrdoruesve, n\u00eb mes \u2013 rrjetet prodhuese, dhe n\u00eb t\u00eb fundit \u2013 pik\u00ebprerjet dhe lidhjet.\u00a0<\/p>\n

Ky qasje lejonte q\u00eb n\u00eb nj\u00eb her\u00eb t\u00eb nxirreshin dhe p\u00ebrkujdesej nga pajisjet e vjetra jo 1 kabllo, por 10-15. Kjo e p\u00ebrshpejtoi ndjesh\u00ebm procesin e pun\u00ebs.\u00a0\u00a0<\/p>\n

K\u00ebshtu duken kabllot n\u00eb dollap\u00eb pas p\u00ebrkujdesjes:\u00a0<\/p>\n

\"Network-as-a-Service
\nose, p\u00ebr shembull, k\u00ebshtu:\u00a0<\/p>\n

\"Network-as-a-Service
\nPas p\u00ebrfundimit t\u00eb etap\u00ebs s\u00eb 2-t\u00eb, mor\u00ebm nj\u00eb pauz\u00eb p\u00ebr t\u00eb analizuar gabimet dhe dinamiken e projektit. P\u00ebr shembull, u shfaq\u00ebn menj\u00ebher\u00eb mang\u00ebsi t\u00eb vogla p\u00ebr shkak t\u00eb pasakt\u00ebsive n\u00eb skemat e rrjetit q\u00eb na ishin p\u00ebrgatitur (konnektori i gabuar n\u00eb skem\u00eb \u2013 patch-kordi i gabuar i bler\u00eb dhe nevoja p\u00ebr ta z\u00ebvend\u00ebsuar at\u00eb).\u00a0<\/p>\n

Pauza ishte e nevojshme, pasi gjat\u00eb pun\u00ebs n\u00eb server t\u00eb drejtat, madje dhe nj\u00eb ndales\u00eb e vog\u00ebl n\u00eb proces ishte e papranueshme. N\u00ebse kishte nj\u00eb q\u00ebllim p\u00ebr t\u00eb siguruar nj\u00eb koh\u00eb ndalese n\u00eb pjes\u00ebn e rrjetit q\u00eb nuk kalon 5 minuta, at\u00ebher\u00eb nuk duhej te kalonte. \u00c7do devijim i mundsh\u00ebm nga plani duhej t\u00eb miratohej me klientin.\u00a0<\/p>\n

Megjithat\u00eb, planifikimi paraprak dhe ndarja e projektit n\u00eb blloqe na lejuan t\u00eb p\u00ebrfitojm\u00eb n\u00eb koh\u00ebn e parashikuar t\u00eb ndaljes n\u00eb t\u00eb gjitha segmentet, dhe n\u00eb shumic\u00ebn e rasteve t\u00eb kalojm\u00eb pa ndalesat.\u00a0<\/p>\n

Sfid\u00eb e koh\u00ebs \u2013 projekti n\u00ebn COVID-in\u00a0<\/h2>\n

\nPa v\u00ebshtir\u00ebsi shtes\u00eb, megjithat\u00eb, nuk kaluam. Sigurisht, nj\u00eb nga pengesat ishte koronavirusi.\u00a0<\/p>\n

Pun\u00ebt u komplikuan sepse filloi pandemia dhe nuk ishte e mundur q\u00eb t\u00eb pranishin gjat\u00eb kryerjes s\u00eb punimeve n\u00eb vendin e klientit t\u00eb gjith\u00eb specialist\u00ebt e angazhuar n\u00eb proces. N\u00eb vendin e pun\u00ebs u lejuan vet\u00ebm punonj\u00ebsit e organizat\u00ebs s\u00eb instalimit, nd\u00ebrsa kontrolli u krye p\u00ebrmes dhom\u00ebs n\u00eb Zoom \u2013 aty ishin inxhinieri rrjetor nga Linxdatacenter, un\u00eb si drejtues projekti, inxhinieri rrjetor nga klienti, p\u00ebrgjegj\u00ebs p\u00ebr kryerjen e pun\u00ebve, dhe ekipi q\u00eb po kryente punimet e instalimit.<\/p>\n

Gjat\u00eb punimeve dol\u00ebn probleme t\u00eb paplanifikuara, dhe duhej t\u00eb b\u00ebheshin korrigjime n\u00eb m\u00ebnyr\u00eb t\u00eb menj\u00ebhershme. K\u00ebshtu, arrit\u00ebm t\u00eb parandalojm\u00eb shpejt ndikimin e faktor\u00ebve njer\u00ebzor\u00eb (gabime n\u00eb skem\u00eb, gabime n\u00eb p\u00ebrcaktimin e statusit t\u00eb aktivizimit t\u00eb nd\u00ebrfaqes etj.).<\/p>\n

Megjith\u00ebse formati i pun\u00ebs n\u00eb distanc\u00eb dukej i \u00e7uditsh\u00ebm n\u00eb fillim t\u00eb projektit, ne u p\u00ebrshtat\u00ebm mjaft shpejt me kushtet e reja dhe arrit\u00ebm n\u00eb faz\u00ebn p\u00ebrfundimtare t\u00eb punimeve.\u00a0<\/p>\n

Ne lan\u00e7uam nj\u00eb konfigurim t\u00eb p\u00ebrkohsh\u00ebm t\u00eb cil\u00ebsimeve t\u00eb rrjetit p\u00ebr funksionimin paralel t\u00eb dy nyjeve rrjetore \u2013 t\u00eb vjetrit dhe t\u00eb riun \u2013 me q\u00ebllim t\u00eb realizimit t\u00eb nj\u00eb kalimi t\u00eb qet\u00eb. Megjithat\u00eb, rezultoi se nj\u00eb rresht t\u00eb panevojsh\u00ebm n\u00eb skedarin e konfigurimit t\u00eb nyjes s\u00eb re nuk ishte fshir\u00eb, dhe kalimi nuk ndodhi. Kjo na detyroi t\u00eb kalojm\u00eb nj\u00eb koh\u00eb t\u00eb caktuar n\u00eb k\u00ebrkimin e problemit.\u00a0<\/p>\n

Doli se trafiku kryesor kalonte si\u00e7 duhet, nd\u00ebrsa trafiku menaxhues nuk arrinte n\u00eb nyj\u00eb p\u00ebrmes nyjes s\u00eb re. Fal\u00eb ndarjes t\u00eb qart\u00eb t\u00eb projektit n\u00eb faza, arrit\u00ebm t\u00eb identifikojm\u00eb shpejt pjes\u00ebn e rrjetit ku kishte ndodhur problemi, t\u00eb zbulojm\u00eb \u00e7\u00ebshtjen dhe ta zgjidhim at\u00eb.\u00a0<\/p>\n

Dhe si rezultat<\/h2>\n

\nP\u00ebrmbledhje teknike e projektit\u00a0<\/i><\/p>\n

N\u00eb radh\u00eb t\u00eb par\u00eb, u krijua nj\u00eb nyje e re e rrjetit t\u00eb ri t\u00eb kompanis\u00eb, p\u00ebr t\u00eb cil\u00ebn nd\u00ebrtuam unaza fizike\/logjike. Kjo u b\u00eb n\u00eb m\u00ebnyr\u00eb q\u00eb \u00e7do switch n\u00eb rrjet t\u00eb kishte nj\u00eb \"shpatull t\u00eb dyt\u00eb\". N\u00eb rrjetin e vjet\u00ebr, shum\u00eb switches lidhnin me nyj\u00ebn p\u00ebrmes nj\u00eb rruge, nj\u00eb shpatulle (uplink). N\u00ebse ajo shk\u00ebputej, switch-i b\u00ebhej krejt\u00ebsisht i pap\u00ebrshkuesh\u00ebm. Dhe n\u00ebse disa switches ishin lidhur p\u00ebrmes nj\u00eb uplink, at\u00ebher\u00eb nj\u00eb avari do ta d\u00ebmtonte nj\u00eb departament t\u00eb t\u00ebr\u00eb ose nj\u00eb linj\u00eb prodhimi n\u00eb kompani.\u00a0<\/p>\n

N\u00eb rrjetin e ri, asnj\u00eb incident rrjetor mjaft serioz nuk mund t\u00eb \"vras\u00eb\" t\u00eb gjith\u00eb rrjetin ose nj\u00eb pjes\u00eb t\u00eb r\u00ebnd\u00ebsishme t\u00eb tij n\u00eb asnj\u00eb skenar.\u00a0<\/p>\n

90% e pajisjeve rrjetore jan\u00eb p\u00ebrdit\u00ebsuar, jan\u00eb hequr nga qarkullimi konvertor\u00ebt e mediave (transformuesit e mediave p\u00ebr p\u00ebrhapjen e sinjalit), si dhe \u00ebsht\u00eb eliminuar nevoja p\u00ebr linja t\u00eb dedikuara energjie p\u00ebr furnizimin e pajisjeve p\u00ebrmes lidhjes me switches PoE, ku furnizimi i energjis\u00eb realizohet p\u00ebrmes kabllove Ethernet.\u00a0<\/p>\n

Gjithashtu, jan\u00eb markuar t\u00eb gjitha lidhjet optike n\u00eb server dhe n\u00eb dollap\u00ebt n\u00eb vendet \u2013 n\u00eb t\u00eb gjitha nyjet kryesore t\u00eb komunikacionit. Kjo leht\u00ebsoi p\u00ebrgatitjen e nj\u00eb skeme topologjike t\u00eb pajisjeve dhe lidhjeve n\u00eb rrjet, q\u00eb pasqyron gjendjen e saj aktuale sot.\u00a0<\/p>\n

Skema e rrjetit<\/i>
\n\"Network-as-a-Service
\nP\u00ebrmbledhja m\u00eb e r\u00ebnd\u00ebsishme n\u00eb aspektin teknik: pun\u00eb t\u00eb mjaftueshme infrastrukturore jan\u00eb kryer shpejt, pa krijuar asnj\u00eb penges\u00eb n\u00eb pun\u00ebn e kompanis\u00eb dhe praktisht pa u v\u00ebn\u00eb re nga stafi i saj.\u00a0<\/p>\n

P\u00ebrmbledhje biznesi e projektit<\/i><\/p>\n

Sipas mendimit tim, ky projekt \u00ebsht\u00eb i interesant n\u00eb radh\u00eb t\u00eb par\u00eb jo nga ana teknike, por nga ana organizative. V\u00ebshtir\u00ebsia ishte kryesisht n\u00eb planifikimin dhe mendimin p\u00ebr hapat e realizimit t\u00eb detyrave projektore.\u00a0<\/p>\n

Suksesi i projektit lejon t\u00eb flasim se iniciativa jon\u00eb p\u00ebr zhvillimin e drejtimit t\u00eb rrjetit brenda portofolit t\u00eb sh\u00ebrbimeve Linxdatacenter \u2013 \u00ebsht\u00eb nj\u00eb zgjedhje e sakt\u00eb p\u00ebr evolucionin e kompanis\u00eb. Qasja p\u00ebrgjegj\u00ebse ndaj menaxhimit t\u00eb projekteve, strategjia e duhur, planifikimi i qart\u00eb na lejuan t\u00eb kryejm\u00eb pun\u00ebn n\u00eb nivelin e duhur.\u00a0<\/p>\n

Konfirmimi i cil\u00ebsis\u00eb s\u00eb pun\u00ebs \u2013 k\u00ebrkesa nga klienti p\u00ebr vazhdimin e ofrimit t\u00eb sh\u00ebrbimeve p\u00ebr modernizimin e rrjetit n\u00eb vendet e tij t\u00eb tjera n\u00eb Rusi.
\n
Burimi: 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\udd47Rrjeti si Sh\u00ebrbim p\u00ebr nj\u00eb kompani t\u00eb madhe: rast i pazakont\u00eb | ProHoster","description":"Si e p\u00ebrmir\u00ebsoni rrjetin.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/95643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=95643"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/95643\/revisions"}],"predecessor-version":[{"id":158014,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/95643\/revisions\/158014"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/95644"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=95643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=95643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=95643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}