Monitoring of computer networks is central to ensuring that they function as intended, with solutions based on SNMP being used since the inception of the protocol. SNMP is however increasingly being challenged by solutions that, instead of requiring a request-response message flow, simply send information to a central collector at predefined intervals. These solutions are often based on Protobuf and gRPC, which are supported and promoted by equipment manufacturers such as Cisco, Huawei, and Juniper. Two models exist for monitoring. The pull model used by SNMP where requests are sent out in order to retrieve data, has historically been widely used. The push model, where data is sent at predefined intervals without a preceding request, is used by the implementations using Protobuf and gRPC. There is a perceived need to understand which model more efficiently uses bandwidth and the monitored system’s memory and processing resources. The purpose of the thesis is to compare two monitoring solutions, one being SNMP, and one based on Protobuf and gRPC. This is done to determine if one solution makes more efficient use of bandwidth and the system resources available to the network equipment. This could aid those who operate networks or develop monitoring software in determining how to implement their solutions. The study is conducted as a case study, where two routers manufactured by Cisco and Huawei were used to gather data about the bandwidth, memory, and CPU utilisation of the two solutions. The results of the measurements show that when retrieving information about objects that have 1-byte values SNMP was the better performer. When objects with larger values were retrieved SNMP performed best until 26 objects were retrieved per message. Above this point the combination of Protobuf and gRPC performed better, resulting in fewer bytes being sent for a given number of objects. No impact on the memory and CPU utilisation in the routers was shown. / Övervakning av nätverk är av yttersta vikt för att säkerställa att de fungerar som tänkt. Lösningar baserade på SNMP har använts sen protokollet kom till. SNMP utmanas mer och mer av lösningar som, istället för att använda ett meddelandeflöde baserat på fråga-svar, helt enkelt sänder information till en insamlande enhet i fördefinierade intervall. Dessa lösningar baseras ofta på Protobuf och gRPC, vilka stöds och propageras för av bland andra utrustningstillverkarna Cisco, Huawei, och Juniper. Två modeller för övervakning finns. Pull-modellen där frågor skickas ut för att hämta data, används av SNMP och har historiskt sett använts i stor skala. Push- modellen, där data skickas i fördefinierade intervall utan föregående fråga, används av lösningar som använder Protobuf och gRPC. Det finns ett behov av att förstå vilken modell som på ett mer effektivt sätt använder bandbredd och de övervakade systemens minnes- och processorresurser. Syftet med denna rapport är att jämföra två övervakningslösningar. SNMP är den ena lösningen, och den andra lösningen är baserad på Protobuf och gRPC. Detta i syfte att utröna om endera lösning på ett mer effektivt sätt använder bandbredd och systemresurser i nätverksutrustning. Detta kan hjälpa nätverksoperatörer och utvecklare av mjukvara för övervakning att avgöra hur dessa bör implementeras. För att besvara detta används en fallstudie, där två routrar tillverkade av Cisco och Huawei används för att samla in data om de två lösningarnas användning av bandbredd, minne, och processorkraft. Mätningarnas resultat visade att när objekt vars värde var 1 byte hämtades så presterade SNMP bättre. När objekt vars värden var större hämtades presterade SNMP bäst tills 26 objekt hämtades per meddelande. Därefter presterade kombinationen Protobuf och gRPC bättre, och krävde färre bytes för att skicka information om ett givet antal objekt. Ingen påverkan på minnes- eller processoranvändningen i routrarna påvisades av mätresultaten.

Approved for public release; distribution is unlimited / Simple Network Management Protocol (SNMP) allows users of network equipment (i.e. Network Administrators) to remotely query the state of any device being tested for system load, utilization and configuration. Windows NT, Windows 2000 and Windows XP Professional are all equipped with SNMP service so that an SNMP manager can communicate with an SNMP agent running on a wireless 802.11b client. However the rest of Windows operating systems, including Windows CE and a Pocket PC, have to run third party proxy SNMP agents in order to be recognized by an SNMP management application. This thesis describes an implementation of a Pocket PC SNMP agent for two Pocket PC mobile devices accessing a wired network via an 802.11b wireless link. As a result of the implementation performed in this thesis, an SNMP manager can wirelessly communicate with a Pocket PC client. However, other results found that only some of the commercially available SNMP managers are able to access the mobile SNMP client and its management information base, due to incompatible implementations of the server and client software. / Lieutenant, Royal Thai Air Force

Thesis (M.S. in Computer Science)--Naval Postgraduate School, March 2003. / Thesis advisor(s): Ted Lewis, Geoffrey Xie, Gurminder Singh. Includes bibliographical references (p. 89). Also available online.

Thesis (M. Sc.)--Carleton University, 2002. / Includes bibliographical references (p. 117-122). Also available in electronic format on the Internet.

Thesis (M. Sc.)--Carleton University, 2003. / Includes bibliographical references (p. 115-117). Also available in electronic format on the Internet.

Thesis (M.S. in Electrical Engineering)--Naval Postgraduate School, March 2005. / Thesis Advisor(s): John C. McEachen. Includes bibliographical references (p. 51-53). Also available online.

The purpose of the Walkstation II project is to create a testbed for a wireless communication system with access to the Internet. The Mobile INTernet (MINT) router is a core element of this project. Most of the routers and many other nodes of today's Internet support network management. This includes the remote control of various parameters which caracterize the status of physical interfaces, protocols and many other objects. The Simple Network Management Protocol (SNMP) which was used in the current work is a standard protocol of the TCP/IP suite. All the managed nodes of the Internet have a common set of management capabilities. Their implementation is available in software development packages. The management of mobile stations requires a new set of management capabilities. They will allow for the control of mobility support and the radio links. The current work consists in adapting the set of standard SNMP capabilities to the MINT router and of the creation of a set of new capabilities specific to the MINT. / <p>I do not know the number of university credits, but entered it as 30 ECTS. This was an exchange student and I do not know if they were actually registered at KTH.</p>

No description available.

A virtualização de rede surgiu como uma alternativa para contornar as limitações no uso compartilhado da infraestrutura atual da Internet. Com a virtualização, sob uma mesma estrutura física, ou substrato, é possível a construção de múltiplas redes virtuais, cada uma das quais empregando seus próprios protocolos, mecanismos de endereçamento e políticas de forma independente e isolada. Essas redes são formadas por roteadores, interfaces e enlaces virtuais mapeados sobre componentes reais. Por serem desacopláveis, os elementos virtuais trazem uma grande flexibilidade, sendo possível a construção de múltiplas redes sobrepostas para usuários com demandas distintas, por exemplo. Roteadores virtuais podem migrar de um roteador físico para outro, conforme necessidades de manutenção ou balanceamento de carga. Além disso, a possibilidade de se conduzir experimentos de rede em uma estrutura real, sujeita as condições de utilização e de tráfego que normalmente serão encontradas na prática, sem que se precise interromper a operação da rede, traz a possibilidade de se instalar poderosos e sofisticados ambientes de teste (testbeds ). Nesse ambiente, contudo, existem desafios de pesquisa a serem tratados e questões em aberto, em especial com relação ao gerenciamento de dispositivos. Em uma rede com suporte a virtualização, os roteadores físicos precisam ser gerenciados para que roteadores virtuais possam ser criados, modificados, duplicados, destruídos e movimentados. As interfaces de gerenciamento atuais, porém, não suportam tais ações de forma efetiva, obrigando o administrador dos dispositivos a realizar intervenções manuais através de interfaces de linha de comandos (CLIs) não padronizadas. Existe, assim, a necessidade de se definir uma interface de gerenciamento adequada para roteadores físicos que abrigam roteadores virtuais. Tendo como objetivo abordar estas questões, este trabalho consiste na investigação de uma solução para gerenciar roteadores virtuais. Para isto foram levantadas e definidas as principais ações de gerenciamento necessárias aos dispositivos, de forma integrada, visando a definição de uma interface padronizada de gerencia- mento para cenários heterogêneos de utilização. / Network virtualization emerged as an alternative to overcome limitations on use of the shared infrastructure of current Internet. With virtualization, over the same physical structure, or substrate, it is possible to build multiple virtual networks, each of them employing its own protocols, addressing mechanisms and policies, on an isolated and independent way. These networks are formed by virtual routers, interfaces and links mapped to real components. Because they are detachable, the virtual elements bring a great flexibility, being possible constructing many overlaid networks for users with different demands, for example. Virtual routers can migrate from one physical router to another as needed form maintenance or load balancing. Besides, the possibily of running network experiments in a real structure, subject to the conditions of use and traffic that will normally be encountered in practice, without interrupting network operation, make it possible to install powerfull and sofisticated testbeds. In such environment, however, there are research challenges to be managed and open questions, specially related to devices management. In a network with virtu- alization support, physicall routers must be managed so that virtual routers can be created, modified, copied, removed and moved. Nevertheless, current management interfaces do not support such action in an effictive way, compelling the devices manager to make manual interventions through non standardized command line interfaces (CLIs). So, there exist the need to define an adequate management interface for physicall routers that host virtual routers. Having as an objective to address these questions, this work consist in investi- gating a solution to manage virtual routers. For this, were raised and defined the main management actions required for devices, through an integrated way, aiming to define a standardized management interface for heterogeneous use scenarios.

A virtualização de rede surgiu como uma alternativa para contornar as limitações no uso compartilhado da infraestrutura atual da Internet. Com a virtualização, sob uma mesma estrutura física, ou substrato, é possível a construção de múltiplas redes virtuais, cada uma das quais empregando seus próprios protocolos, mecanismos de endereçamento e políticas de forma independente e isolada. Essas redes são formadas por roteadores, interfaces e enlaces virtuais mapeados sobre componentes reais. Por serem desacopláveis, os elementos virtuais trazem uma grande flexibilidade, sendo possível a construção de múltiplas redes sobrepostas para usuários com demandas distintas, por exemplo. Roteadores virtuais podem migrar de um roteador físico para outro, conforme necessidades de manutenção ou balanceamento de carga. Além disso, a possibilidade de se conduzir experimentos de rede em uma estrutura real, sujeita as condições de utilização e de tráfego que normalmente serão encontradas na prática, sem que se precise interromper a operação da rede, traz a possibilidade de se instalar poderosos e sofisticados ambientes de teste (testbeds ). Nesse ambiente, contudo, existem desafios de pesquisa a serem tratados e questões em aberto, em especial com relação ao gerenciamento de dispositivos. Em uma rede com suporte a virtualização, os roteadores físicos precisam ser gerenciados para que roteadores virtuais possam ser criados, modificados, duplicados, destruídos e movimentados. As interfaces de gerenciamento atuais, porém, não suportam tais ações de forma efetiva, obrigando o administrador dos dispositivos a realizar intervenções manuais através de interfaces de linha de comandos (CLIs) não padronizadas. Existe, assim, a necessidade de se definir uma interface de gerenciamento adequada para roteadores físicos que abrigam roteadores virtuais. Tendo como objetivo abordar estas questões, este trabalho consiste na investigação de uma solução para gerenciar roteadores virtuais. Para isto foram levantadas e definidas as principais ações de gerenciamento necessárias aos dispositivos, de forma integrada, visando a definição de uma interface padronizada de gerencia- mento para cenários heterogêneos de utilização. / Network virtualization emerged as an alternative to overcome limitations on use of the shared infrastructure of current Internet. With virtualization, over the same physical structure, or substrate, it is possible to build multiple virtual networks, each of them employing its own protocols, addressing mechanisms and policies, on an isolated and independent way. These networks are formed by virtual routers, interfaces and links mapped to real components. Because they are detachable, the virtual elements bring a great flexibility, being possible constructing many overlaid networks for users with different demands, for example. Virtual routers can migrate from one physical router to another as needed form maintenance or load balancing. Besides, the possibily of running network experiments in a real structure, subject to the conditions of use and traffic that will normally be encountered in practice, without interrupting network operation, make it possible to install powerfull and sofisticated testbeds. In such environment, however, there are research challenges to be managed and open questions, specially related to devices management. In a network with virtu- alization support, physicall routers must be managed so that virtual routers can be created, modified, copied, removed and moved. Nevertheless, current management interfaces do not support such action in an effictive way, compelling the devices manager to make manual interventions through non standardized command line interfaces (CLIs). So, there exist the need to define an adequate management interface for physicall routers that host virtual routers. Having as an objective to address these questions, this work consist in investi- gating a solution to manage virtual routers. For this, were raised and defined the main management actions required for devices, through an integrated way, aiming to define a standardized management interface for heterogeneous use scenarios.