Inter-frequency and inter-RAT handovers can be coverage, load, or service based. Coverage-based handovers are triggered by certain A3/A4/A5 events for inter-frequency and B1/B2 events for inter-RAT. The document discusses the parameters involved in measuring cells and configuring handovers, including measurement reports, handover commands, and key performance indicators for analyzing handover issues. Common causes of handover problems include poor downlink quality, interference, and abnormal X2 interface signaling.
3.oeo000020 lte call drop diagnosis issue 1Klajdi Husi
油
This document discusses LTE call drop diagnosis. It provides statistics and counters related to abnormal call releases, including those caused by radio network faults, transport network faults, and network congestion. It also discusses call drops related to handover failures, corner effects, and ping-pong handovers. The document emphasizes this is confidential information of Huawei and cannot be shared without permission.
The document provides guidance on handling speech quality issues in UMTS networks. It classifies speech quality problems as either Mean Opinion Score (MOS) issues or perceptual issues, and outlines prescribed actions and related cases for each type. For MOS problems, it describes 11 actions to check factors like testing methods, equipment versions, parameters, coding/decoding, and handovers. For perceptual issues like silence and noise, it lists 6 actions including processing cases. The document also details deliverables for reporting speech quality problems.
This document contains a presentation on LTE TDD given by Bong Youl Cho of Nokia Solutions and Networks. The presentation provides an overview of LTE TDD technology, including comparisons to WiMAX and 3G TDD, details on TDD configurations and carrier aggregation, enhancements in Release 12 and beyond, and the growth of LTE TDD deployment by major operators worldwide. It aims to demonstrate that LTE TDD and FDD can be highly integrated to provide "the best LTE" network through global roaming and seamless handovers between the technologies.
This document provides an overview of Open vSwitch, including what it is, its main components, features, and how it can be used to build virtual network topologies. Open vSwitch is a software-defined networking switch that can be used to create virtual networks and handle network traffic between virtual machines and tunnels. It uses a distributed database, ovsdb-server, and a userspace daemon, ovs-vswitchd, to implement features like virtual switching, tunneling protocols, and OpenFlow support. Examples are provided for using Open vSwitch with KVM virtual machines and GRE tunnels to create virtual network topologies.
The document discusses Huawei's handover algorithm II for cellular networks. It describes the different types of handovers considered in the algorithm (forced, emergency, intra-cell, inter-cell) and the procedures involved, including determining triggering conditions, selecting candidate cell lists, and performing a comprehensive decision to determine the best candidate cell. It also discusses related concepts like handover priority, penalty adjustments, and measurement report processing.
This document describes setting up network slicing on a Mininet testbed using FlowVisor. It outlines creating an upper and lower network slice managed by separate SDN controllers. Flow spaces are configured on switches to delegate traffic on certain ports to each slice. Connectivity tests show the slices isolate hosts from each other while intra-slice communication is maintained.
This document discusses various key performance indicators (KPIs) for Voice over LTE (VoLTE) networks. It describes KPIs for VoLTE control plane performance like registration success rate, call setup success rate, and call setup time. It also covers user plane KPIs such as mute rate, mean opinion score, RTP packet loss rate, and one way call rate. Additionally, it lists KPIs for packet core network elements like attach success rate, paging success rate, and IP pool utilization. The document provides details on calculating each KPI and healthy range benchmarks.
This document provides an overview of OpenStack, including what it is, the main OpenStack services, and how to perform single node and multinode installations using DevStack and PackStack. OpenStack is an open-source cloud computing platform that provides infrastructure as a service. It consists of interrelated components to control hardware resources like processing, storage, and networking. The document describes the main OpenStack services like Dashboard, Compute, Networking, Object Storage, Block Storage, Image Service, Telemetry, and Orchestration. It then covers how to do a single node installation on Ubuntu, the networking requirements for multinode, and how to install and configure DevStack and PackStack for OpenStack deployment.
This document discusses diagnosing LTE traffic faults through drive testing. It provides probes and indicators for issues related to insufficient resources for scheduling, coding with low values, poor coverage, abnormal receive power, and other potential problems. Diagnosis involves checking for operations and external events that could affect service rates. Specific alarms and their impacts are also listed. The document is marked as confidential information that requires permission before spreading.
This document provides instructions for various monitoring and configuration tasks in an EMS system for 2G, 3G, and 4G networks. It describes how to check alarms, monitor cell and board status, view and query KPIs, export and import configuration data using ICM, modify parameters, and more. The steps provided allow technicians to troubleshoot issues and configure elements like alarms, cells, boards, and neighbor relations across RNCs, BSCs and other network equipment.
This document provides guidelines for LTE radio frequency (RF) network optimization. It describes the network optimization process including single site verification and RF optimization. Key aspects of RF optimization covered include preparing by collecting data and analyzing problems, adjusting parameters such as transmit power and neighbor lists, and ensuring optimization objectives like coverage, signal quality, and handover success rates are met. The document also details common issues like weak coverage, lack of a dominant cell, and cross coverage and methods for resolving them.
- The RRC setup procedure success rate (RRC SR%) measures the percentage of successful RRC connection setups. Failures can be due to resource limitations, radio conditions, or configuration issues.
- The E-RAB setup success rate (E-RAB SR%) measures the percentage of successful data radio bearer setups. Failures can be due to radio resource constraints, transport issues, or security problems.
- The circuit-switched fallback success rate (CSFB SR%) measures the percentage of successful handovers from LTE to GSM or UMTS for circuit-switched calls. This allows LTE networks to support legacy telephone services.
1. The document provides Huawei's mobility strategy recommendations for Maxis' LTE network, which involves LTE, UMTS, and GSM networks.
2. The strategy addresses cell selection and reselection procedures in both idle and connected modes between the different RATs and frequencies. It aims to optimize coverage and load balancing through configuration of various priority and threshold parameters.
3. Over multiple revisions from 2012 to 2018, the strategy has been updated based on trials and discussions between Maxis and Huawei to refine the parameter settings and push more users to preferred frequencies like L2600.
This document provides guidance on optimizing the success rate of uplink TBF establishments in GSM networks. It defines key terms related to uplink TBF establishment success rate and describes how to measure the number of successful, failed, and total attempted uplink TBF establishments. The document then details various factors that could affect uplink TBF establishment success rate and provides troubleshooting steps to check each factor. Finally, it presents three case studies where optimizations were made to improve low uplink TBF establishment success rates in actual networks.
This document discusses a feature called Fast Return to WCDMA (FASTRET3G) that allows user equipment to select a WCDMA network after a call disconnect on a 2G network. This is intended to reduce load on the 2G network by encouraging reselection to 3G, reduce page outage time for subscribers, and improve a key performance indicator for call drops on the secondary dedicated control channel. The document outlines objectives of the feature, that it has no network impact, pre-checks needed before activation like ensuring 2G-3G handover is set up, and plans to test it in a cluster with the highest number of 3G sites and worst 2G call drop rates.
This presentation gives a summary of SDXCentral 2017 Report on NFV Industry and its trends. The presentation gives jump start for beginners to navigate through NFV forest by getting necessary details and expand understanding elaborating each piece of puzzle.
The document discusses mobility management in LTE networks. It covers connected mode mobility including an overview of mobility triggers and handover thresholds, measurement configuration, intra-frequency handovers, inter-frequency handovers, and inter-RAT handovers. It also discusses idle mode mobility including system information blocks and cell selection procedures for intra-frequency, inter-frequency, and inter-RAT mobility. The presentation provides details on the different mobility management procedures and configuration parameters in LTE networks.
Lte ue initial attach & detach from networkxtharinduwije
油
The document outlines the key steps in an LTE UE initial attach process:
1) An RRC connection is established between the UE and eNB after the UE connects.
2) The UE then sends an attach request and PDN connectivity request to the network to attach to the network and establish bearers.
3) The MME authenticates the UE by querying the HSS for authentication details and comparing the UE's response to the values from the HSS.
The document discusses VoLTE optimization services including RAN and EPC analysis using various tools. It details accomplishments like optimizing sites for carriers and analyzing problems like VoLTE drop issues. The key services described are VoLTE parameter audits, drive log analysis, UETR analysis, and end-to-end VoLTE call tracing. Case studies provided examine issues like QCI profile not defined, RRC drops without VoLTE drops, and improvements gained from features like ICIC and parameter changes.
Cloud native is a new paradigm for developing, deploying, and running applications using containers, microservices, and container orchestration. The Cloud Native Computing Foundation (CNCF) drives adoption of this paradigm through open source projects like Kubernetes, Prometheus, and Envoy. Cloud native applications are packaged as lightweight containers, developed as loosely coupled microservices, and deployed on elastic cloud infrastructure to optimize resource utilization. CNCF seeks to make these innovations accessible to everyone.
Kube-proxy is a Kubernetes component responsible to re-conciliate the state of the Service resources. This component can be configured in four different modes: userspace, iptables, IPVS or Kernel space (Windows). In big scales, the IPVS mode offers better performance resulting in an attractive offer. In this session, I'll try to explain the IPVS internals, and how Kubernetes automates the management of services through basic examples.
Docker Hub: Past, Present and Future by Ken Cochrane & BC WongDocker, Inc.
油
This document provides an overview of Docker Hub, including its history and features. Docker Hub is a cloud registry service that allows users to share applications and automate workflows. It currently has over 240,000 users, 150,000 repositories, and handles over 1 billion pulls annually. The document discusses Docker Hub's growth over time and upcoming features like improved performance, automated builds using Kubernetes, and a redesigned user interface.
Huawei eRAN 7.0 VoLTE feature deep dive_20140515.pptxQasimQadir3
油
The document describes various enhanced features for VoLTE including TTI bundling, ROHC, semi-persistent scheduling, and delay-based scheduling. It provides details on how these features work, when they are triggered, parameters used, and key performance indicators. The enhanced features aim to improve coverage, capacity, and quality of VoLTE services over LTE networks.
This document discusses OpenvSwitch, an open source virtual switch that provides virtual networking and network virtualization capabilities. It describes OpenvSwitch's architecture, features, configuration, and use cases with OpenStack, VMware NSX, MidoNet, Pica8, and Intel DPDK. OpenvSwitch supports virtual networking functions like VLANs, STP, QoS, and tunneling protocols. It integrates with hypervisors and controllers to enable network virtualization and software-defined networking.
O-RAN is an approach to making radio access networks more open and interoperable. It uses open source software, standardized interfaces, and general purpose hardware to allow for innovation and flexibility compared to traditional monolithic and proprietary systems. The high-level design involves splitting the network functions into different units like Distributed Units and Centralized Units that can be deployed in various locations like at the edge of the network or in centralized data centers. Key use cases focus on allowing telecom operators to innovate and improve their networks as well as enabling new applications that require low latency edge computing capabilities.
This document provides an overview of OpenStack, including what it is, the main OpenStack services, and how to perform single node and multinode installations using DevStack and PackStack. OpenStack is an open-source cloud computing platform that provides infrastructure as a service. It consists of interrelated components to control hardware resources like processing, storage, and networking. The document describes the main OpenStack services like Dashboard, Compute, Networking, Object Storage, Block Storage, Image Service, Telemetry, and Orchestration. It then covers how to do a single node installation on Ubuntu, the networking requirements for multinode, and how to install and configure DevStack and PackStack for OpenStack deployment.
This document discusses diagnosing LTE traffic faults through drive testing. It provides probes and indicators for issues related to insufficient resources for scheduling, coding with low values, poor coverage, abnormal receive power, and other potential problems. Diagnosis involves checking for operations and external events that could affect service rates. Specific alarms and their impacts are also listed. The document is marked as confidential information that requires permission before spreading.
This document provides instructions for various monitoring and configuration tasks in an EMS system for 2G, 3G, and 4G networks. It describes how to check alarms, monitor cell and board status, view and query KPIs, export and import configuration data using ICM, modify parameters, and more. The steps provided allow technicians to troubleshoot issues and configure elements like alarms, cells, boards, and neighbor relations across RNCs, BSCs and other network equipment.
This document provides guidelines for LTE radio frequency (RF) network optimization. It describes the network optimization process including single site verification and RF optimization. Key aspects of RF optimization covered include preparing by collecting data and analyzing problems, adjusting parameters such as transmit power and neighbor lists, and ensuring optimization objectives like coverage, signal quality, and handover success rates are met. The document also details common issues like weak coverage, lack of a dominant cell, and cross coverage and methods for resolving them.
- The RRC setup procedure success rate (RRC SR%) measures the percentage of successful RRC connection setups. Failures can be due to resource limitations, radio conditions, or configuration issues.
- The E-RAB setup success rate (E-RAB SR%) measures the percentage of successful data radio bearer setups. Failures can be due to radio resource constraints, transport issues, or security problems.
- The circuit-switched fallback success rate (CSFB SR%) measures the percentage of successful handovers from LTE to GSM or UMTS for circuit-switched calls. This allows LTE networks to support legacy telephone services.
1. The document provides Huawei's mobility strategy recommendations for Maxis' LTE network, which involves LTE, UMTS, and GSM networks.
2. The strategy addresses cell selection and reselection procedures in both idle and connected modes between the different RATs and frequencies. It aims to optimize coverage and load balancing through configuration of various priority and threshold parameters.
3. Over multiple revisions from 2012 to 2018, the strategy has been updated based on trials and discussions between Maxis and Huawei to refine the parameter settings and push more users to preferred frequencies like L2600.
This document provides guidance on optimizing the success rate of uplink TBF establishments in GSM networks. It defines key terms related to uplink TBF establishment success rate and describes how to measure the number of successful, failed, and total attempted uplink TBF establishments. The document then details various factors that could affect uplink TBF establishment success rate and provides troubleshooting steps to check each factor. Finally, it presents three case studies where optimizations were made to improve low uplink TBF establishment success rates in actual networks.
This document discusses a feature called Fast Return to WCDMA (FASTRET3G) that allows user equipment to select a WCDMA network after a call disconnect on a 2G network. This is intended to reduce load on the 2G network by encouraging reselection to 3G, reduce page outage time for subscribers, and improve a key performance indicator for call drops on the secondary dedicated control channel. The document outlines objectives of the feature, that it has no network impact, pre-checks needed before activation like ensuring 2G-3G handover is set up, and plans to test it in a cluster with the highest number of 3G sites and worst 2G call drop rates.
This presentation gives a summary of SDXCentral 2017 Report on NFV Industry and its trends. The presentation gives jump start for beginners to navigate through NFV forest by getting necessary details and expand understanding elaborating each piece of puzzle.
The document discusses mobility management in LTE networks. It covers connected mode mobility including an overview of mobility triggers and handover thresholds, measurement configuration, intra-frequency handovers, inter-frequency handovers, and inter-RAT handovers. It also discusses idle mode mobility including system information blocks and cell selection procedures for intra-frequency, inter-frequency, and inter-RAT mobility. The presentation provides details on the different mobility management procedures and configuration parameters in LTE networks.
Lte ue initial attach & detach from networkxtharinduwije
油
The document outlines the key steps in an LTE UE initial attach process:
1) An RRC connection is established between the UE and eNB after the UE connects.
2) The UE then sends an attach request and PDN connectivity request to the network to attach to the network and establish bearers.
3) The MME authenticates the UE by querying the HSS for authentication details and comparing the UE's response to the values from the HSS.
The document discusses VoLTE optimization services including RAN and EPC analysis using various tools. It details accomplishments like optimizing sites for carriers and analyzing problems like VoLTE drop issues. The key services described are VoLTE parameter audits, drive log analysis, UETR analysis, and end-to-end VoLTE call tracing. Case studies provided examine issues like QCI profile not defined, RRC drops without VoLTE drops, and improvements gained from features like ICIC and parameter changes.
Cloud native is a new paradigm for developing, deploying, and running applications using containers, microservices, and container orchestration. The Cloud Native Computing Foundation (CNCF) drives adoption of this paradigm through open source projects like Kubernetes, Prometheus, and Envoy. Cloud native applications are packaged as lightweight containers, developed as loosely coupled microservices, and deployed on elastic cloud infrastructure to optimize resource utilization. CNCF seeks to make these innovations accessible to everyone.
Kube-proxy is a Kubernetes component responsible to re-conciliate the state of the Service resources. This component can be configured in four different modes: userspace, iptables, IPVS or Kernel space (Windows). In big scales, the IPVS mode offers better performance resulting in an attractive offer. In this session, I'll try to explain the IPVS internals, and how Kubernetes automates the management of services through basic examples.
Docker Hub: Past, Present and Future by Ken Cochrane & BC WongDocker, Inc.
油
This document provides an overview of Docker Hub, including its history and features. Docker Hub is a cloud registry service that allows users to share applications and automate workflows. It currently has over 240,000 users, 150,000 repositories, and handles over 1 billion pulls annually. The document discusses Docker Hub's growth over time and upcoming features like improved performance, automated builds using Kubernetes, and a redesigned user interface.
Huawei eRAN 7.0 VoLTE feature deep dive_20140515.pptxQasimQadir3
油
The document describes various enhanced features for VoLTE including TTI bundling, ROHC, semi-persistent scheduling, and delay-based scheduling. It provides details on how these features work, when they are triggered, parameters used, and key performance indicators. The enhanced features aim to improve coverage, capacity, and quality of VoLTE services over LTE networks.
This document discusses OpenvSwitch, an open source virtual switch that provides virtual networking and network virtualization capabilities. It describes OpenvSwitch's architecture, features, configuration, and use cases with OpenStack, VMware NSX, MidoNet, Pica8, and Intel DPDK. OpenvSwitch supports virtual networking functions like VLANs, STP, QoS, and tunneling protocols. It integrates with hypervisors and controllers to enable network virtualization and software-defined networking.
O-RAN is an approach to making radio access networks more open and interoperable. It uses open source software, standardized interfaces, and general purpose hardware to allow for innovation and flexibility compared to traditional monolithic and proprietary systems. The high-level design involves splitting the network functions into different units like Distributed Units and Centralized Units that can be deployed in various locations like at the edge of the network or in centralized data centers. Key use cases focus on allowing telecom operators to innovate and improve their networks as well as enabling new applications that require low latency edge computing capabilities.
This document discusses SDN (Software-Defined Networking) and ONOS (Open Network Operating System). It provides an overview of SDN, describing it as managing and controlling networks through software and making networks programmable. It then introduces ONOS, an open-source SDN controller developed to be carrier-grade and support high availability, performance, and scalability. It discusses ONOS's architecture, key subsystems, and capabilities for network virtualization including topology, address, and control function virtualization and virtual network snapshotting.
This document describes OpenVirteX, a network virtualization platform that enables multiple virtual networks to run concurrently over a single physical network infrastructure. It allows each tenant to define their own virtual network topologies. OpenVirteX decouples the physical and virtual networks and provides isolation between tenant traffic. It performs functions like topology virtualization, address space virtualization, and control function virtualization to manage the virtual networks. OpenVirteX also enables networks to be reconfigured at runtime and automatically recovers from physical network failures.
This document discusses XOS and its role in OpenCORD. It describes how XOS uses a synchronizer to manage state changes to data models and synchronize them with OpenStack. Core components of OpenCORD include OpenStack, ONOS, XOS, and OCP. OpenCORD projects on GitHub include platform installation tools, XOS, MaaS, and services like AAA and Voltha. XOS assembles services using separate containers for the database, webserver, and synchronizer. TOSCA is used to describe application topologies and orchestrate operations across cloud providers.
This document discusses CORD (Central Office Re-architecture as a DC) and its components. CORD combines SDN, NFV and cloud technologies to deliver services for telecommunications providers using open source software and commodity hardware. It discusses the requirements and types of CORD (M-CORD for mobile, E-CORD for enterprise, R-CORD for residential services). The core components that make up CORD are OpenStack for infrastructure, ONOS for control, and XOS as the service controller. XOS assembles and orchestrates the virtual network functions and services on top of the infrastructure and control layers.
Introduction of ONOS and core technologysangyun han
油
This document provides an overview of ONOS (Open Network Operating System) including:
- ONOS is an open-source SDN controller created by ON.LAB to provide carriers with an SDN/NFV solution.
- It aims to be carrier-grade with high availability, scalability, and performance through a distributed architecture.
- ONOS uses southbound protocols like OpenFlow and Netconf to configure network elements while providing northbound APIs and applications.
ONOS Raspberry Pi 蠍磯 螳覓朱Μ SDN れ 蟆 蟲豢螻 螳覦sangyun han
油
The document provides information about setting up an SDN testbed using ONOS and Raspberry Pi. It introduces ONOS, an open source SDN operating system, and provides details on installing and running a single ONOS instance. It also covers setting up and managing multiple ONOS instances in a distributed deployment. Finally, it introduces OpenVirteX, a network virtualization platform, and provides an overview of its key features and the installation process.
The document discusses the RAFT consensus algorithm and the Copycat framework. It provides an overview of RAFT and how it uses a replicated state machine approach with log replication to achieve consensus. Key aspects of RAFT include leader election, log replication using append entries RPC calls, and three states that nodes can be in: follower, candidate, or leader. It also describes how Copycat is an implementation of RAFT that adds features like passive followers that replicate logs asynchronously using a gossip protocol for improved scalability.
ONOS - setting, configuration, installation, and test
1. ONOS SDN Controller
れ 覿 覦 SDN 螳覦
Mobile Convergence Lab, Computer Engineering,
Kyung Hee University
Sangyun Han
Email : sangyun0628@khu.ac.kr
SDN/NFV 企, れ, 豕
[ONOS 蟆曙れ, 觜 覦 ろ 蟆 蟲豢]
2. Setting
Mobile Convergence Laboratory 2
覈谿
A Table of Contents
Install
Test
蟆曙れ
螳襾語 , ろ語 蟆 れ
譟伎SW れ 覦 觜
蟯 ろ れ 覦 覲 れ, 觜
ろ 蟆 蟲豢
SDN 貉碁, ろ碁ゼ 覓朱Μ 覦 螳 蟆
Q&A
讌
3. Prerequisites
Ubuntu 14.04 LTS 64bits
2GB or more RAM
2 or more processors
8GB or more storage
Java 8 JDK
Apache Maven(3.3.9 and later)
Apache Karaf(3.0.5 and later)
Git
Mobile Convergence Laboratory 3
4. 螻給 VM instance
Ubuntu 14.04 LTS
2GB memory
12GB hard disk
(dynamic allocation)
eth0 NAT / eth1 host-only
username : sdn
password : mclab
Mobile Convergence Laboratory 4
5. Setting
1. Installing VM
2. Creating VM instance
3. Configuring network option
Mobile Convergence Laboratory 5
16. 1. Install Java 8
Mobile Convergence Laboratory 16
Single Instance Setting (1/10)
Java8 殊伎
17. 2. Configure Java Path
on Ubuntu
$ env | grep JAVA_HOME
JAVA_HOME=/usr/lib/jvm/java-8-oracle
$ export JAVA_HOME=/usr/lib/jvm/java-8-oracle
Mobile Convergence Laboratory 17
Single Instance Setting (2/10)
18. 3. Install Git
$ sudo apt-get install git-core
$ git --version
Mobile Convergence Laboratory 18
Single Instance Setting (3/10)
19. 4. Set Maven
$ cd; mkdir Downloads Applications
$ cd Downloads
$ wget http://archive.apache.org/dist/maven/maven-
3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
$ tar -zxvf apache-maven-3.3.9-bin.tar.gz -C ../Applications/
Mobile Convergence Laboratory 19
Single Instance Setting (4/10)
20. 4. Set Maven
$ cd; mkdir Downloads Applications
$ cd Downloads
$ wget http://archive.apache.org/dist/maven/maven-
3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
$ tar -zxvf apache-maven-3.3.9-bin.tar.gz -C ../Applications/
Mobile Convergence Laboratory 20
Single Instance Setting (4/10)
譴!
static path
21. 5. Set Karaf
$ cd Downloads
$ wget http://archive.apache.org/dist/karaf/3.0.5/apache-karaf-
3.0.5.tar.gz
$ tar -zxvf apache-karaf-3.0.5.tar.gz -C ../Applications/
Mobile Convergence Laboratory 21
Single Instance Setting (5/10)
22. 6. Clone ONOS
$ cd ~/
$ git clone https://gerrit.onosproject.org/onos/
$ cd onos
if> getting specific ONOS version
$ git checkout onos-1.5
Mobile Convergence Laboratory 22
Single Instance Setting (6/10)
23. 7. Configure ONOS Path
$ export ONOS_ROOT=~/onos
$ source $ONOS_ROOT/tools/dev/bash_profile
Mobile Convergence Laboratory 23
Single Instance Setting (7/10)
# add bash
sudo vi /etc/bash.bashrc
export ONOS_ROOT=~/onos
source $ONOS_ROOT/tools/dev/bash_profile
24. 8. Build ONOS
$ cd ~/onos
$ mvn clean install
Mobile Convergence Laboratory 24
觜 炎概
Single Instance Setting (8/10)
25. 9. Start ONOS CLI
$ ok clean
Mobile Convergence Laboratory 25
Single Instance Setting (9/10)
26. 10. Start ONOS GUI
start ONOS (ONOS CLI)
In web browser
http://localhost:8181/onos/ui/login.html
Default ID: karaf / PW: karaf
Mobile Convergence Laboratory 26
Single Instance Setting (10/10)