{"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":"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/41a850152b71e5f63bd359ceb3af3f01.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Si t\u00eb rinovoni pajisjet rrjet\u00ebsore n\u00eb nj\u00eb nd\u00ebrmarrje t\u00eb madhe pa nd\u00ebrprer\u00eb prodhimin<\/i><i>? <\/i><i>Rreth nj\u00eb projekti t\u00eb gjer\u00eb n\u00eb modin \"operacion mbi zemr\u00ebn e hapur\" flet <\/i><i><strong>menaxheri i menaxhimit t\u00eb projekteve n\u00eb Linxdatacenter, Oleg Fedorov.\u00a0<\/strong><\/i><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nN\u00eb vitet e fundit, kemi v\u00ebn\u00eb re nj\u00eb rritje t\u00eb k\u00ebrkesave nga klient\u00ebt p\u00ebr sh\u00ebrbime q\u00eb lidhen me komponentin rrjet\u00ebsor t\u00eb infrastruktur\u00ebs IT. Nevoja p\u00ebr lidhshm\u00ebrin\u00eb e sistemeve IT, sh\u00ebrbimeve, aplikacioneve, detyrat e monitorimit dhe menaxhimit operacional t\u00eb biznesit, praktikisht n\u00eb \u00e7do fush\u00eb, i detyron sot kompanit\u00eb t\u00eb p\u00ebrkushtohen m\u00eb shum\u00eb rrjetit.\u00a0\u00a0<\/p>\n<p>Rekllamat variojn\u00eb nga sigurimi i q\u00ebndrueshm\u00ebris\u00eb s\u00eb rrjetit deri te krijimi dhe menaxhimi i nj\u00eb sistemi autonom klient\u00ebsh duke bler\u00eb blokun <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sq\/lir\/ipv4\/\"   title=\"IP-adresat\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"823\">IP-adresat<\/a>, duke konfiguruar protokollet e rrug\u00ebzimit dhe menaxhimin e trafikut n\u00eb p\u00ebrputhje me politikat e organizatave.<\/p>\n<p>Po ashtu, rritet k\u00ebrkesa p\u00ebr zgjidhje t\u00eb plota p\u00ebr nd\u00ebrtimin dhe mir\u00ebmbajtjen e infrastruktur\u00ebs rrjet\u00ebsore, kryesisht nga klient\u00ebt, infrastrukturat rrjet\u00ebsore t\u00eb t\u00eb cil\u00ebve krijohen nga e para ose jan\u00eb morale e vjetruar, q\u00eb k\u00ebrkon modifikime serioze.\u00a0<\/p>\n<p>Ky trend u p\u00ebrputh me zhvillimin dhe nd\u00ebrlikimin e infrastruktur\u00ebs son\u00eb rrjet\u00ebsore n\u00eb Linxdatacenter. Ne zgjeruam gjeografin\u00eb e pranis\u00eb son\u00eb n\u00eb Evrop\u00eb duke u lidhur me site t\u00eb larg\u00ebta, q\u00eb nga ana tjet\u00ebr k\u00ebrkonte p\u00ebrmir\u00ebsimin e infrastruktur\u00ebs s\u00eb rrjetit.\u00a0<\/p>\n<p>Kompania lan\u00e7oi nj\u00eb sh\u00ebrbim t\u00eb ri p\u00ebr klient\u00ebt, Rrjeti si Sh\u00ebrbim: ne marrim p\u00ebrsip\u00ebr zgjidhjen e t\u00eb gjitha problemeve rrjet\u00ebsore t\u00eb klient\u00ebve, duke u lejuar atyre t\u00eb p\u00ebrqendrohen n\u00eb biznesin e tyre kryesor.<\/p>\n<p>N\u00eb ver\u00ebn e vitit 2020 p\u00ebrfundoi projekti i par\u00eb i madh n\u00eb k\u00ebt\u00eb drejtim, p\u00ebr t\u00eb cilin do t\u00eb flasim.\u00a0<\/p>\n<h2>N\u00eb fillim\u00a0<\/h2>\n<p>\nNj\u00eb kompleks i madh industrial na u drejtua p\u00ebr modernizimin e pjes\u00ebs rrjet\u00ebsore t\u00eb infrastruktur\u00ebs n\u00eb nj\u00eb nga nd\u00ebrmarrjet e tij. Duhej t\u00eb z\u00ebvend\u00ebsohej pajisjet e vjetra me t\u00eb reja, p\u00ebrfshir\u00eb dhe b\u00ebrtham\u00ebn e rrjetit.<\/p>\n<p>Modernizimi i fundit i pajisjeve n\u00eb nd\u00ebrmarrje ishte kryer rreth 10 vjet m\u00eb par\u00eb. Drejtimi i ri i nd\u00ebrmarrjes vendosi t\u00eb p\u00ebrmir\u00ebsoj\u00eb lidhshm\u00ebrin\u00eb, duke filluar nga rinovimi i infrastruktur\u00ebs n\u00eb nivelin m\u00eb t\u00eb ul\u00ebt, fizik.\u00a0<\/p>\n<p>Projekti u nda n\u00eb dy pjes\u00eb: p\u00ebrmir\u00ebsimi i parqeve server dhe pajisjeve rrjet\u00ebsore. Ne ishim p\u00ebrgjegj\u00ebs p\u00ebr pjes\u00ebn e dyt\u00eb.\u00a0<\/p>\n<p>K\u00ebrkesat themelore p\u00ebr punimet p\u00ebrfshinin minimizimin e stagnimeve t\u00eb linjave prodhuese t\u00eb nd\u00ebrmarrjes gjat\u00eb kryerjes s\u00eb pun\u00ebve (dhe n\u00eb disa segmente, p\u00ebrjashtimin e plots\u00eb t\u00eb stagnimeve). \u00c7do ndalese \u00ebsht\u00eb humbje direkte parash p\u00ebr klientin, e cila nuk duhej t\u00eb ndodhte n\u00eb asnj\u00eb rast. P\u00ebr shkak t\u00eb orarit t\u00eb pun\u00ebs s\u00eb objektit 24x7x365, si dhe duke marr\u00eb parasysh munges\u00ebn totale t\u00eb periudhave t\u00eb stagnimeve t\u00eb planifikuara n\u00eb praktik\u00ebn e nd\u00ebrmarrjes, na u caktua detyra, n\u00eb thelb, t\u00eb kryejm\u00eb nj\u00eb operacion n\u00eb nj\u00eb zem\u00ebr t\u00eb hapur. Kjo u b\u00eb karakteristika kryesore e projektit.<\/p>\n<h2>N\u00eb rrug\u00eb<\/h2>\n<p>\nPunimet jan\u00eb planifikuar mbi parimin e l\u00ebvizjes nga nyjet e larg\u00ebta nga b\u00ebrthama e rrjetit drejt atyre m\u00eb t\u00eb af\u00ebrta, si dhe nga ato q\u00eb kan\u00eb ndikim m\u00eb t\u00eb vog\u00ebl n\u00eb funksionimin e linjave prodhuese n\u00eb ato q\u00eb ndikojn\u00eb drejtp\u00ebrdrejt n\u00eb k\u00ebt\u00eb pun\u00eb.\u00a0<\/p>\n<p>P\u00ebr shembull, n\u00ebse e marrim nj\u00eb nyje t\u00eb rrjetit n\u00eb departamentin e shitjeve, nj\u00eb nd\u00ebrprerje komunikimi si rezultat i punimeve n\u00eb k\u00ebt\u00eb departament nuk do t\u00eb prekej prodhimi. Megjithat\u00eb, nj\u00eb incident i till\u00eb do t\u00eb ndihmoj\u00eb ne si n\u00ebnkontraktor\u00eb t\u00eb verifikojm\u00eb sakt\u00ebsin\u00eb e qasjes t\u00eb zgjedhur p\u00ebr pun\u00ebn n\u00eb k\u00ebto nyje dhe, duke korrigjuar veprimet, t\u00eb punojm\u00eb n\u00eb fazat e ardhshme t\u00eb projektit.\u00a0<\/p>\n<p>Duhet jo vet\u00ebm t\u00eb z\u00ebvend\u00ebsohen nyjet dhe kabllot n\u00eb rrjet, por edhe t\u00eb konfigurohen sakt\u00ebsisht t\u00eb gjitha komponent\u00ebt p\u00ebr funksionimin e duhur t\u00eb zgjidhjes n\u00eb t\u00ebr\u00ebsi. Pik\u00ebrisht konfigurimet u kontrolluan n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb: duke filluar pun\u00ebn n\u00eb larg\u00ebsi nga b\u00ebrthama, ne si t\u00eb thuash u jepnim vetes \"t\u00eb drejt\u00ebn p\u00ebr gabim\", duke mos v\u00ebn\u00eb n\u00eb rrezik zona kritike p\u00ebr funksionimin e nd\u00ebrmarrjes.\u00a0<\/p>\n<p>Ne p\u00ebrcaktuam zona q\u00eb nuk ndikojn\u00eb n\u00eb procesin prodhues, si dhe segmente kritike \u2013 punishtet, blloku i ngarkimit dhe shkarkimit, magazinat etj. N\u00eb segmentet kryesore me klientin u ra dakord p\u00ebr koh\u00ebn e pranueshme t\u00eb ndaljes p\u00ebr \u00e7do nyje rrjeti ve\u00e7mas: nga 1 deri n\u00eb 15 minuta. T\u00eb shmangeshim plot\u00ebsisht nga nd\u00ebrprerja e nyjeve t\u00eb ve\u00e7anta t\u00eb rrjetit ishte e pamundur, pasi kablli duhet t\u00eb kaloj\u00eb fizikisht nga pajisja e vjet\u00ebr n\u00eb at\u00eb t\u00eb re, dhe gjat\u00eb procesit t\u00eb kalimit duhet gjithashtu t\u00eb zgjidhet \"mjekra\" e kabllove, e cila \u00ebsht\u00eb formuar gjat\u00eb disa viteve shfryt\u00ebzimi pa kujdesin e duhur (nj\u00eb nga pasojat e outsourcimit t\u00eb pun\u00ebve p\u00ebr montimin e linjave kabllore).<\/p>\n<p>Punimet u ndan\u00eb n\u00eb disa faza.<\/p>\n<p><b>Faza 1<\/b> \u2013 Audit. Preparing and agreeing on the approach to work planning and assessing the readiness of the client's team, the contractor's team handling the installation, and our team.<\/p>\n<p><b>Stage 2<\/b> \u2013 Developing a format for conducting work, with a thorough detailed analysis and planning. We chose a checklist format with precise indications of the order and sequence of actions, down to the sequence of switching patch cords between ports.<\/p>\n<p><b>Stage 3<\/b> \u2013 Conducting works in cabinets that do not affect production. Assessing and adjusting downtime for subsequent stages of work.<\/p>\n<p><b>Stage 4<\/b> \u2013 Conducting works in cabinets that directly affect production. Assessing and adjusting downtime for the final stage of work.<\/p>\n<p><b>Stage 5<\/b> \u2013 Conducting works in the server room for switching the remaining equipment. Launching routing on the new core.<\/p>\n<p><b>Stage 6<\/b> \u2013 Sequentially switching the system core from old network configurations to new ones for a smooth transition of the entire system complex (VLAN, routing, etc.). At this stage, we connected all users and transferred all services to the new equipment, checked the correctness of the connections, ensured that none of the enterprise services stopped, and guaranteed that in case of any issues, they would be directly related to the core, thus facilitating troubleshooting and final setup.\u00a0<\/p>\n<h2>Cable beard grooming<\/h2>\n<p>\nThe project turned out to be complicated due to the challenging initial conditions.\u00a0<\/p>\n<p>Firstly, there was a huge number of nodes and sections of the network, with a tangled topology and classification of wires by their purpose. Such 'beards' had to be extracted from cabinets and meticulously 'groomed,' figuring out which wire comes from where and where it leads.\u00a0<\/p>\n<p>It looked something like this:<\/p>\n<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/250765ff4f34b562faabfa17419345fb.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\ne till\u00eb:<\/p>\n<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/4b010a2c0679143230cb355d9eea5a17.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nose k\u00ebshtu:\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/c5c25358974e0ec219ac7a1ab97b84e9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nP\u00ebr m\u00eb tep\u00ebr, p\u00ebr \u00e7do detyr\u00eb t\u00eb till\u00eb, ishte e nevojshme t\u00eb p\u00ebrgatitej nj\u00eb skedar me p\u00ebrshkrimin e procesit. \"Marrim telin H nga porta 1 e pajisjeve t\u00eb vjetra, e lidhim at\u00eb 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 hyr\u00ebse 48 porta t\u00eb plota, si dhe mungon opsioni p\u00ebr ndalim (ne e kujtojm\u00eb pun\u00ebn 24x7x365), rruga e vetme \u00ebsht\u00eb t\u00eb punosh n\u00eb blloqe. Sa m\u00eb shum\u00eb tela t\u00eb mund t\u00eb nxjerr\u00ebsh nga pajisjet e vjetra n\u00eb nj\u00eb her\u00eb, aq m\u00eb shpejt mund t'i organizosh dhe t'i lidh\u00ebsh n\u00eb \"harduerin\" e ri t\u00eb rrjetit, duke shmangur d\u00ebshtimet dhe ndalimet n\u00eb pun\u00ebn e rrjetit.\u00a0<\/p>\n<p>Prandaj, n\u00eb faz\u00ebn e p\u00ebrgatitjes, ne kryem 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 tyre) n\u00eb pajisjet e vjetra \u00ebsht\u00eb nj\u00eb nga VLAN n\u00eb topologjin\u00eb e re t\u00eb rrjetit. I grumbulluam ata k\u00ebshtu: n\u00eb portet e para t\u00eb switch-it u vendos\u00ebn rrjetet p\u00ebrdoruese, n\u00eb mes \u2013 rrjetet prodhuese, dhe n\u00eb fund \u2013 pikat e qasjes dhe up-link-et.\u00a0<\/p>\n<p>Ky qasje e lejoi q\u00eb n\u00eb nj\u00eb her\u00eb t\u00eb nxirrnim dhe organizonim nga pajisjet e vjetra jo 1 tel, por 10-15. Kjo e p\u00ebrshpejtoi ndjesh\u00ebm procesin e pun\u00ebs.\u00a0\u00a0<\/p>\n<p>Gjithashtu, ja si duken telat n\u00eb kabinet pas organizimit:\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/18ae2427926aaa85bf7c730bcd3c7ea3.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nose, p\u00ebr shembull, k\u00ebshtu:\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/42b661d166bf5c8f67ea084045e7f04f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPas p\u00ebrfundimit t\u00eb faz\u00ebs s\u00eb dyt\u00eb, mor\u00ebm nj\u00eb pauz\u00eb p\u00ebr t\u00eb analizuar gabimet dhe dinamik\u00ebn e projektit. P\u00ebr shembull, menj\u00ebher\u00eb u shfaq\u00ebn disa gabime t\u00eb vogla p\u00ebr shkak t\u00eb pasakt\u00ebsive n\u00eb diagramet e rrjetit q\u00eb na ishin ofruar (konnektori i gabuar n\u00eb diagram \u2013 patch cord i gabuar i bler\u00eb dhe nevoja p\u00ebr ta z\u00ebvend\u00ebsuar).\u00a0<\/p>\n<p>Pauza ishte e nevojshme, sepse kur punon me servera, edhe ndonj\u00eb gabim i vog\u00ebl n\u00eb proces \u00ebsht\u00eb i papranuesh\u00ebm. N\u00ebse q\u00ebllimi \u00ebsht\u00eb t\u00eb sigurohet koh\u00eb ndalimi n\u00eb nj\u00eb segment t\u00eb rrjetit jo m\u00eb shum\u00eb se 5 minuta, at\u00ebher\u00eb nuk duhej t\u00eb kalonte at\u00eb. \u00c7do devijim t\u00eb mundsh\u00ebm nga plani duhej t\u00eb miratohej me klientin.\u00a0<\/p>\n<p>Megjithat\u00eb, planifikimi paraprak dhe ndarja e projektit n\u00eb blloqe na lejuan t\u00eb p\u00ebrfshiheshim brenda koh\u00ebs s\u00eb planifikuar t\u00eb ndalimit n\u00eb t\u00eb gjitha segmentet, dhe n\u00eb shumic\u00ebn e rasteve, madje edhe ta kalonim at\u00eb pa ndalim.\u00a0<\/p>\n<h2>Sfida e momentit \u2013 projekti gjat\u00eb COVID-it\u00a0<\/h2>\n<p>\nPa v\u00ebshtir\u00ebsi t\u00eb tjera, megjithat\u00eb, nuk ia doli pa ndodhur. Sigurisht, si nj\u00eb nga pengesat doli koronavirusi.\u00a0<\/p>\n<p>Puna u r\u00ebndua nga fillimi i pandemis\u00eb, e cila b\u00ebri t\u00eb pamundur pranin\u00eb e t\u00eb gjith\u00eb specialist\u00ebve t\u00eb angazhuar n\u00eb proces gjat\u00eb punimeve n\u00eb vendin e klientit. Vet\u00ebm punonj\u00ebsit e organizat\u00ebs s\u00eb montimit ishin t\u00eb lejuar n\u00eb vend dhe kontrolli u krye p\u00ebrmes nj\u00eb dhome n\u00eb Zoom \u2013 aty ishin inxhinieri i rrjetit nga Linxdatacenter, un\u00eb si menaxher projekti, inxhinieri i rrjetit nga ana e klientit p\u00ebrgjegj\u00ebs p\u00ebr realizimin e pun\u00ebve, dhe ekipi q\u00eb kryente pun\u00ebt e montimit.<\/p>\n<p>Gjat\u00eb punimeve dol\u00ebn probleme t\u00eb paqena dhe na u desh t\u00eb b\u00ebnim korrigjime n\u00eb l\u00ebvizje. K\u00ebshtu mund\u00ebm t\u00eb parandalonim shpejt ndikimin e faktor\u00ebve njer\u00ebzor\u00eb (gabime n\u00eb skem\u00eb, gabime n\u00eb p\u00ebrcaktimin e statusit t\u00eb aktivizmit t\u00eb nd\u00ebrfaqes, etj.).<\/p>\n<p>Megjith\u00ebse formati i pun\u00ebs n\u00eb distanc\u00eb dukej i pazakont\u00eb n\u00eb fillim t\u00eb projektit, ne u akomodua shpejt me kushtet e reja dhe arrit\u00ebm n\u00eb faz\u00ebn p\u00ebrfundimtare t\u00eb punimeve.\u00a0<\/p>\n<p>Ne aktivizuam nj\u00eb konfigurim t\u00eb p\u00ebrkohsh\u00ebm t\u00eb cil\u00ebsimeve t\u00eb rrjetit p\u00ebr funksionimin paralele t\u00eb dy t\u00ebr\u00ebsive rrjet\u00ebrore \u2013 t\u00eb vjet\u00ebr dhe t\u00eb re \u2013 me q\u00ebllim realizimin e nj\u00eb kalimi t\u00eb qet\u00eb. Megjithat\u00eb, doli se nj\u00eb rresht i panevojsh\u00ebm nuk ishte fshir\u00eb nga skedari i konfigurimit t\u00eb t\u00ebr\u00ebsis\u00eb s\u00eb re, dhe kalimi nuk ndodhi. Kjo na detyroi t\u00eb kalonim nj\u00ebfar\u00eb kohe n\u00eb k\u00ebrkimin e problemit.\u00a0<\/p>\n<p>U zbuluar se trafiku kryesor u d\u00ebrgua si\u00e7 duhet, nd\u00ebrsa trafiku i menaxhimit nuk arrinte n\u00eb nyj\u00eb p\u00ebrmes t\u00ebr\u00ebsis\u00eb s\u00eb re. Fal\u00eb ndarjes s\u00eb qart\u00eb t\u00eb projektit n\u00eb faza, arrit\u00ebm q\u00eb t\u00eb vendosnim fast nj\u00eb pjes\u00eb t\u00eb rrjetit, ku pati v\u00ebshtir\u00ebsi, t\u00eb identifikonim problemin dhe ta zgjidhnim at\u00eb.\u00a0<\/p>\n<h2>Si rezultat<\/h2>\n<p>\n<i>P\u00ebrfundimet teknike t\u00eb projektit\u00a0<\/i><\/p>\n<p>S\u00eb pari, u krijua nj\u00eb t\u00ebr\u00ebsi e re e rrjetit t\u00eb ri t\u00eb nd\u00ebrmarrjes, p\u00ebr t\u00eb cilin 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 'sht\u00ebpi t\u00eb dyt\u00eb'. N\u00eb rrjetin e vjet\u00ebr shum\u00eb switches u lidh\u00ebn me t\u00ebr\u00ebsin\u00eb p\u00ebrmes nj\u00eb rruge, nj\u00eb shpine (uplink). N\u00ebse ajo prishej, switch-i b\u00ebhej plot\u00ebsisht i paqart\u00eb. Dhe n\u00ebse disa switches lidhen p\u00ebrmes nj\u00eb uplink-u, nj\u00eb aksident do t\u00eb d\u00ebmtonte nj\u00eb departament t\u00eb t\u00ebr\u00eb ose nj\u00eb linj\u00eb prodhimi n\u00eb nd\u00ebrmarrje.\u00a0<\/p>\n<p>N\u00eb rrjetin e ri, madje edhe nj\u00eb incident i r\u00ebnd\u00eb rrjetor n\u00eb asnj\u00eb skenar nuk do t\u00eb mund t\u00eb \u2018shg\u00ebnjente\u2019 t\u00eb gjith\u00eb rrjetin ose nj\u00eb pjes\u00eb t\u00eb r\u00ebnd\u00ebsishme t\u00eb tij.\u00a0<\/p>\n<p>90% e gjith\u00eb pajisjeve rrjetore jan\u00eb p\u00ebrdit\u00ebsuar, jan\u00eb hequr nga p\u00ebrdorimi konvertuesit e mediumit (p\u00ebrkthyesit e sinjalit), dhe gjithashtu \u00ebsht\u00eb eliminuar nevoja p\u00ebr linja t\u00eb dedikuara energjie p\u00ebr furnizimin e pajisjeve p\u00ebrmes lidhjes me switch-at PoE, ku furnizimi me energji b\u00ebhet p\u00ebrmes kabllove Ethernet.\u00a0<\/p>\n<p>Gjithashtu, t\u00eb gjitha lidhjet optike n\u00eb dhom\u00ebn e server\u00ebve dhe n\u00eb kabinetet n\u00eb vend jan\u00eb etiketuar - n\u00eb t\u00eb gjitha nyjat ky\u00e7e t\u00eb lidhjes. Kjo ka mund\u00ebsuar p\u00ebrgatitjen e nj\u00eb skeme topologjike t\u00eb pajisjeve dhe lidhjeve n\u00eb rrjet, q\u00eb reflekton gjendjen e saj aktuale sot.\u00a0<\/p>\n<p><i>Skema e rrjetit<\/i><br \/>\n<img decoding=\"async\" alt=\"Sh\u00ebrbimi i Rrjetit si Sh\u00ebrbim p\u00ebr Nd\u00ebrmarrjet e M\u00ebdha: Rast i ve\u00e7ant\u00eb\" src=\"\/wp-content\/uploads\/2020\/10\/03227daadfdd7e86146f76c5755b1fc2.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nKryefjala m\u00eb e r\u00ebnd\u00ebsishme n\u00eb aspektin teknik: pun\u00ebt infrastrukturore t\u00eb ndjeshme jan\u00eb realizuar shpejt, pa shkaktuar ndonj\u00eb penges\u00eb n\u00eb funksionimin e kompanis\u00eb dhe pothuajse pa u v\u00ebn\u00eb re nga stafi i saj.\u00a0<\/p>\n<p><i>Bilancet e biznesit t\u00eb projektit<\/i><\/p>\n<p>Sipas mendimit tim, ky projekt \u00ebsht\u00eb m\u00eb interesant kryesisht nga ana organizative, sesa nga ajo teknike. V\u00ebshtir\u00ebsia p\u00ebrb\u00ebhej kryesisht nga planifikimi dhe mendimi i hapave p\u00ebr zbatimin e detyrave t\u00eb projektit.\u00a0<\/p>\n<p>Suksesi i projektit na lejon t\u00eb flasim se iniciativa jon\u00eb p\u00ebr zhvillimin e drejtimit rrjetor brenda portofolit t\u00eb sh\u00ebrbimeve Linxdatacenter \u00ebsht\u00eb nj\u00eb zgjedhje e sakt\u00eb e drejtimit t\u00eb zhvillimit t\u00eb kompanis\u00eb. Qasja p\u00ebrgjegj\u00ebse ndaj menaxhimit t\u00eb projekteve, strategjia e men\u00e7ur, planifikimi i sakt\u00eb na lejuan t\u00eb kryejm\u00eb pun\u00ebn n\u00eb nivelin e duhur.\u00a0<\/p>\n<p>Konfirmimi i cil\u00ebsis\u00eb s\u00eb pun\u00ebs \u00ebsht\u00eb k\u00ebrkesa nga klienti p\u00ebr vazhdimin e sh\u00ebrbimeve p\u00ebr modernizimin e rrjetit n\u00eb lokacione t\u00eb tjera t\u00eb tij n\u00eb Rusi.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/linxdatacenter\/blog\/521352\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\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 [&hellip;]<\/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<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\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\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-10-01T11:42:18+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-10-01T11:42:18+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Networking-as-a-Service p\u00ebr nj\u00eb nd\u00ebrmarrje t\u00eb madhe: nj\u00eb rast jostandarde | ProHoster","description":"Si t\u00eb p\u00ebrdit\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}]}}