27 research outputs found

    Peningkatan Konektifitas Service VPLS Redundant Path Dengan Rapid Spanning Tree Protocol

    Get PDF
    Virtual Private LAN Service is already very popular among the enterprise industry which is a point to point network or multipoint to multipoint l2VPN service, VPLS provides transparent bridge between customers connected to geographically dispersed locations delivered via MPLS backbone by utilizing features such as MPLS Fast reroute and traffic engineering. Redundant paths can be applied to the VPLS service on the access side and backbone to maintain link performance that aims to minimize down time during network fails on the VPLS service. In this research, the implementation of redundant path using RSTP to prevent forwarding loop switching network in VPLS service to protect end-to-end data traffic with VPLS mesh-pseudowire and spoke-pesudowire with RSTP is the most optimal result compared to STP and build reliable network System with high performance for use in modern industry

    Peningkatan Konektifitas Service VPLS Redundant Path dengan Rapid Spanning Tree Protocol

    Get PDF
    Virtual Private LAN Service is already very popular among the enterprise industry which is a point to point network or multipoint to multipoint l2VPN service, VPLS provides transparent bridge between customers connected to geographically dispersed locations delivered via MPLS backbone by utilizing features such as MPLS Fast reroute and traffic engineering. Redundant paths can be applied to the VPLS service on the access side and backbone to maintain link performance that aims to minimize down time during network fails on the VPLS service. In this research, the implementation of redundant path using RSTP to prevent forwarding loop switching network in VPLS service to protect end-to-end data traffic with VPLS mesh-pseudowire and spoke-pesudowire with RSTP is the most optimal result compared to STP and build reliable network System with high performance for use in modern industry

    A Disaggregated MEC Architecture Enabling Open Services and Novel Business Models

    Get PDF
    Network and Service Providers are exploring different exploitation strategies for the Multi-access Edge Computing (MEC), mainly motivated by the opportunities for saving costs and generating new revenues (e.g., through new business models). On the other hand, the overall standardization picture is still very fragmented, delaying or even jeopardizing the real exploitation of MEC; furthermore, current standardization efforts are mainly envisioning a traditional monolithic architecture, with many technological partners but a single administrative domain. This paper argues that a clear separation of IaaS, PaaS and SaaS levels for MEC, together with standardized interfaces, will help accelerating the development of new business roles (e.g., IaaS, PaaS and SaaS providers) and models, possibly replacing the current competition-oriented practices in the telco domain with new forms of cooperation, which are already starting to appear in the IT sector. In this direction, this paper proposes a disaggregated MEC architecture and presents two use cases that show how different categories of resources and services could be provided by infrastructure, platform and software providers in an evolutionary scenario towards 5G

    Evaluation of wide-area distributed services by SDN-FIT system

    Get PDF
    A wide area distributed application is affected by聽network failure due to natural disasters because the servers on聽which the application operates are distributed geographically in聽a wide area. Failure Injection Testing (FIT) is a method for聽verifying fault tolerance of widely distributed applications. In聽this paper, by limiting network failures to the connection line,聽whole FIT scenarios are generated and exhaustive evaluation of聽fault tolerance is performed. Authors evaluate the visualization聽method of performance data obtained from this evaluation and聽the reduction of the fault tolerance evaluation cost by the聽proposed method

    Migraci贸n de servicios en un sistema de virtualizaci贸n distribuido

    Get PDF
    Cloud applications are usually formed by different components (microservices) that may be located in different virtual and/or physical computers. To achieve the desired level of performance, availability, scalability, and robustness in this kind of system developers are forced to maintain and configure complex sets of infrastructure, platforms, and frameworks which are expensive to implement, operate and manage. Another approach would be to use a Distributed Virtualization System (DVS) that provides a mechanism that each component could use to communicate with others, regardless of their location and thus, avoiding the potential problems and complexity added by their distributed execution. This communication mechanism already has useful features for developing commercial-class distributed applications, such as replication support (active and passive) and process migration. This article describes the mechanisms used for the migration of server processes between nodes of a DVS cluster transparently for client and server processes, doing special focus on how to solve the problem of keeping client/server communications active even when the server process location lias changed.Las aplicaciones desarrolladas para ejecutar en la nube suelen estar constituidas por m煤ltiples componentes (microservicios) que se localizan en diferentes computadores f铆sicos o virtuales. Para alcanzar los niveles de rendimiento, disponibilidad, escalabilidad y robustez, en este tipo de sistemas los desarrolladores se ven forzados a mantener y configurar complejos conjuntos de infraestructura, plataformas y marcos de trabajo que son costosos de implementar, operar y gestionar. Otra forma de resolver este problema es haciendo uso de un Sistema de Virtualizaci贸n Distribuido (DVS) el que provee un mecanismo que permite comunicar entre s铆 los componentes de la aplicaci贸n en forma transparente a su localizaci贸n, ocultando los problemas y complejidades a帽adidos por su ejecuci贸n distribuida. Este mecanismo de comunicaciones cuenta con caracter铆sticas espec铆ficas para el desarrollo de aplicaciones distribuidas de clase-comercial tales como el soporte de Replicaci贸n (Activa y Pasiva) y de Migraci贸n de Procesos. En este art铆culo se describen los mecanismos que permiten realizar una migraci贸n de procesos servidores entre nodos de un cluster de un DVS en forma transparente para los procesos clientes y servidores, y la forma como se resuelve el problema de mantener activas las comunicaciones cliente/servidor aun cuando el proceso servidor haya cambiado de ubicaci贸n.Facultad de Inform谩tic

    Hybrid IP/SDN networking: open implementation and experiment management tools

    Full text link
    The introduction of SDN in large-scale IP provider networks is still an open issue and different solutions have been suggested so far. In this paper we propose a hybrid approach that allows the coexistence of traditional IP routing with SDN based forwarding within the same provider domain. The solution is called OSHI - Open Source Hybrid IP/SDN networking as we have fully implemented it combining and extending Open Source software. We discuss the OSHI system architecture and the design and implementation of advanced services like Pseudo Wires and Virtual Switches. In addition, we describe a set of Open Source management tools for the emulation of the proposed solution using either the Mininet emulator or distributed physical testbeds. We refer to this suite of tools as Mantoo (Management tools). Mantoo includes an extensible web-based graphical topology designer, which provides different layered network "views" (e.g. from physical links to service relationships among nodes). The suite can validate an input topology, automatically deploy it over a Mininet emulator or a distributed SDN testbed and allows access to emulated nodes by opening consoles in the web GUI. Mantoo provides also tools to evaluate the performance of the deployed nodes.Comment: Accepted for publication in IEEE Transaction of Network and Service Management - December 2015 http://dx.doi.org/10.1109/TNSM.2015.250762
    corecore