1. The document describes various Moshell commands used for managing RBS nodes.
2. The acc 0 manualrestart command is used to restart the RBS node, while the pol 5 5 command polls the node every 5 seconds to check when the MO service is ready after restart.
3. Other commands described are for checking CV configuration (cvcu, cvls), managing CVs (cvset, cvmk, cvrm), and accessing measurement data (st mme, ue print).
Cs hs drop analysis and optimization presentationDaniel Amaning
The document discusses various strategies and parameters for optimizing HS and speech call drops in a mobile network. It analyzes call drop reasons like congestion, soft handover failures, missing neighbors, and synchronization issues. It provides guidance on improving neighbor planning, resource utilization, interference reduction features, HS mobility parameters, load balancing between carriers, and URA PCH configuration for fast dormancy. The optimization strategies aim to reduce specific counter metrics for different call drop causes and improve key performance indicators for HS connections.
1. The document describes various Moshell commands used for managing RBS nodes.
2. The acc 0 manualrestart command is used to restart the RBS node, while the pol 5 5 command polls the node every 5 seconds to check when the MO service is ready after restart.
3. Other commands described are for checking CV configuration (cvcu, cvls), managing CVs (cvset, cvmk, cvrm), and accessing measurement data (st mme, ue print).
The document discusses some of the most commonly used commands in the AMOS LTE command line interface (CLI) for managing and troubleshooting an LTE network. It provides examples of using commands like lt all to load all managed objects, st fdd to check the administrative and operational states of cells, ue print -admitted to check the number of connected users and bearers per cell, get . earfcn to check the E-ARFCN numbers in use for downlink and uplink, and ping to test X2 connectivity between eNodeBs. It also mentions using commands to check power configuration, neighbor lists, license capacity, bandwidth usage, and X2 and S1 connection status.
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 a troubleshooting guide for LTE inter-radio access technology (IRAT) handovers. It describes why IRAT is needed as voice revenues remain important while data revenues grow. It also outlines the applications of IRAT, delivery policies for idle mode, connected mode, and voice services. Signaling procedures for IRAT handovers including reselection, redirection, and PS handover are defined. Key performance indicators for IRAT including control plane delays and user plane interruption times are also defined to help diagnose IRAT issues.
Ericsson important optimization parametersPagla Knight
The document lists important optimization parameters for Ericsson including parameters related to system configuration, capacity management, directed retry, handover, HSDPA/EUL, IRAT, and idle mode selection and reselection. It provides descriptions of over 50 parameters that control aspects such as power levels, admission limits, thresholds for cell reselection, and criteria for measurements.
2 g and 3g kpi improvement by parameter optimization (nsn, ericsson, huawei) ...Jean de la Sagesse
The document discusses key performance indicators (KPIs) for 2G and 3G networks and how top telecom vendors like Ericsson, Huawei, and NSN optimize parameters to improve these KPIs. It outlines techniques for reducing TCH blocking, SD blocking, TCH drop, HOSR, TASR, SD drop, and improving paging success rate through actions like changing configuration parameters, enabling features, addressing hardware issues, and optimizing cells physically. The optimization of these parameters can help maintain balance between network throughput, capacity and radio quality while ensuring a seamless transition between 2G and 3G.
This document contains parameters related to 2G cell configuration for an Axis network with 2247 sites and 19 BSCs. It includes common cell data parameters like AGBLK, MFRMS, ACCMIN, INDOOR_CELL values. It also includes locating cell filter data parameters like BSPWR, BSTXPWR, MSRXMIN, BSRXMIN for path loss calculation. Finally, it contains locating urgency cell data parameters like TALIM, PSSBQ, PTIMBQ, QLIMDL for handling call quality issues. The parameters need to be optimized for Axis' coverage-limited network.
Cs hs drop analysis and optimization presentationDaniel Amaning
The document discusses various strategies and parameters for optimizing HS and speech call drops in a mobile network. It analyzes call drop reasons like congestion, soft handover failures, missing neighbors, and synchronization issues. It provides guidance on improving neighbor planning, resource utilization, interference reduction features, HS mobility parameters, load balancing between carriers, and URA PCH configuration for fast dormancy. The optimization strategies aim to reduce specific counter metrics for different call drop causes and improve key performance indicators for HS connections.
1. The document describes various Moshell commands used for managing RBS nodes.
2. The acc 0 manualrestart command is used to restart the RBS node, while the pol 5 5 command polls the node every 5 seconds to check when the MO service is ready after restart.
3. Other commands described are for checking CV configuration (cvcu, cvls), managing CVs (cvset, cvmk, cvrm), and accessing measurement data (st mme, ue print).
The document discusses some of the most commonly used commands in the AMOS LTE command line interface (CLI) for managing and troubleshooting an LTE network. It provides examples of using commands like lt all to load all managed objects, st fdd to check the administrative and operational states of cells, ue print -admitted to check the number of connected users and bearers per cell, get . earfcn to check the E-ARFCN numbers in use for downlink and uplink, and ping to test X2 connectivity between eNodeBs. It also mentions using commands to check power configuration, neighbor lists, license capacity, bandwidth usage, and X2 and S1 connection status.
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 a troubleshooting guide for LTE inter-radio access technology (IRAT) handovers. It describes why IRAT is needed as voice revenues remain important while data revenues grow. It also outlines the applications of IRAT, delivery policies for idle mode, connected mode, and voice services. Signaling procedures for IRAT handovers including reselection, redirection, and PS handover are defined. Key performance indicators for IRAT including control plane delays and user plane interruption times are also defined to help diagnose IRAT issues.
Ericsson important optimization parametersPagla Knight
The document lists important optimization parameters for Ericsson including parameters related to system configuration, capacity management, directed retry, handover, HSDPA/EUL, IRAT, and idle mode selection and reselection. It provides descriptions of over 50 parameters that control aspects such as power levels, admission limits, thresholds for cell reselection, and criteria for measurements.
2 g and 3g kpi improvement by parameter optimization (nsn, ericsson, huawei) ...Jean de la Sagesse
The document discusses key performance indicators (KPIs) for 2G and 3G networks and how top telecom vendors like Ericsson, Huawei, and NSN optimize parameters to improve these KPIs. It outlines techniques for reducing TCH blocking, SD blocking, TCH drop, HOSR, TASR, SD drop, and improving paging success rate through actions like changing configuration parameters, enabling features, addressing hardware issues, and optimizing cells physically. The optimization of these parameters can help maintain balance between network throughput, capacity and radio quality while ensuring a seamless transition between 2G and 3G.
This document contains parameters related to 2G cell configuration for an Axis network with 2247 sites and 19 BSCs. It includes common cell data parameters like AGBLK, MFRMS, ACCMIN, INDOOR_CELL values. It also includes locating cell filter data parameters like BSPWR, BSTXPWR, MSRXMIN, BSRXMIN for path loss calculation. Finally, it contains locating urgency cell data parameters like TALIM, PSSBQ, PTIMBQ, QLIMDL for handling call quality issues. The parameters need to be optimized for Axis' coverage-limited network.
This document provides guidelines for optimizing accessibility in Ericsson networks. It discusses key performance indicators (KPIs) for measuring accessibility, including call setup success rate and overall service accessibility. It also analyzes factors that can affect accessibility, such as admission control, processor load, and issues after call admission like congestion. Annexes describe user equipment idle mode procedures and call establishment procedures in detail.
The document describes traffic counter systems in RNCs (Radio Network Controllers) and cells in 3G WCDMA networks. It discusses key performance indicators for traffic, including Erlang load, throughput, number of radio bearers, and more. Counters are grouped by their measurement location (RNC or cell) and type (traffic, radio bearers, HSDPA, transmit power). The purpose is to understand and monitor traffic patterns and performance at different levels of the 3G network.
This document provides instructions for using the AMOS command line interface. It describes how to launch AMOS from different interfaces and lists common commands for checking alarms, nodes, hardware, and connectivity in RNCs and NodeBs. Key information includes IP addresses and passwords for accessing different RNCs, commands for listing and blocking nodes, and checking Ranap and Rnsap connections between network elements.
E nodeb useful commands for rf engineerVishal Padhya
This document provides instructions for verifying various network connections and configurations in an eNodeB using Moshell commands:
1. The st mme and st termpointtomme commands can check the S1-CP connection between the eNodeB and MME after a restart.
2. Verifying S1-UP connectivity requires pinging from a UE to an application server.
3. The st termpointtoenb command displays configured X2 links between eNodeBs.
4. The get intralte command checks if the Intra-LTE Handover feature is activated, required for handovers.
This document describes various 3G network traffic scenarios related to connection setup, resource allocation, mobility management, and radio link management. For each scenario, the main counters used to monitor performance are listed. The scenarios include RRC connection setup for circuit-switched and packet-switched calls, RAB establishment, paging, retention, connection and RAB release, admission control, quality monitoring, channel switching, system utilization, congestion detection and resolution, code allocation, compressed mode, cell availability, updates, mobility handovers between frequencies and radio technologies, radio link additions, deletions, and reconfigurations, soft handover operations, and CN hard handovers on CS and PS RABs.
The document discusses the requirements and configuration of Inter Frequency Load Balancing (IFLB) in LTE networks. IFLB aims to balance traffic load across cells on different frequencies by offloading user equipment between those cells. Key steps in IFLB include determining cell load, exchanging load information, selecting offload candidates, and handing users over to target cells if their signal quality is sufficient. The document provides guidance on setting parameters that control IFLB behavior and thresholds.
The document provides commands for the MoShell interface used to manage various network elements in a UMTS radio access network, including the radio network controller (RNC), radio network explorer/installer (RXI), and radio base station (RBS). The commands can be used to view status information, configure parameters, and troubleshoot issues relating to cells, modules, boards, interfaces, alarms, software, and other components on the RNC, RXI, and RBS.
LTE KPI Optimization - A to Z Abiola.pptxssuser574918
1. The document discusses LTE post launch optimization, including problem causes, solutions, and case studies.
2. It describes different types of counters used to collect PM statistics, including peg, gauge, accumulator, scan, PDF, DDM, calculated, trigACC, and trigSCAN counters.
3. Potential causes of poor accessibility for E-RAB establishment are discussed, including poor coverage, alarms, high load, hardware issues, high UL interference, PCI conflicts, RACH root sequence index planning, UE camping in wrong cells, wrong system constant settings, and VSWR or cell availability issues.
The document discusses UMTS planning and dimensioning processes. It describes:
1) The overall planning process which includes system dimensioning, radio network planning, pre-launch optimization, performance monitoring, and post-launch optimization.
2) The inputs, assumptions, and steps used for air interface dimensioning which includes uplink and downlink link budget analysis to determine coverage requirements and capacity needs.
3) Traffic modelling and load calculation methods to estimate subscriber traffic per cell based on factors like subscriber density, traffic profiles, and cell area.
The document summarizes different 3G events that can trigger handover procedures in UMTS networks. It describes 7 categories of events related to primary pilot channel, frequency, quality, channel traffic volume, CRCs, Rx-Tx parameters, and location/position. Each category contains multiple specific events that are monitored and can trigger handovers based on thresholds being passed for radio frequency parameters. The events monitor factors like signal quality, interference levels, traffic loads, transmission power, and device location to determine when a UE should hand over to a better serving cell.
The document discusses various resources in an LTE network that need to be monitored to ensure capacity and quality of service. It describes several key performance indicators (KPIs) related to resources like connected users, traffic volume, paging messages, processor usage, and provides thresholds and solutions to address issues.
This document summarizes various LTE KPIs and performance metrics related to random access, RRC connection establishment, ERAB establishment, and issues that may impact them. It provides potential causes for high values or failures in these metrics as well as recommended actions to investigate like checking RF parameters, capacity, licenses, alarms, configuration, and optimizing physical antenna settings.
. Overview
2. Handover Causes & Priorities
3. Threshold Comparison Process
4. Target Cell Evaluation Process
5. Handover Algorithms
Power Budget (PBGT)
Level & Quality (RXLEV & RXQUAL)
Umbrella (& Combined Umbrella/PBGT)
MS Speed (FMMS & MS_SPEED_DETECTION)
6. Imperative Handovers
Distance
Rapid Field Drop (RFD) & Enhanced Rapid Field Drop (ERFD)
7. Handover Timers
Call continuity - to ensure a call can be maintained as a MS moves geographical location from the coverage area of one cell to another
Call quality - to ensure that if an MS moves into a poor quality/coverage area the call can be moved from the serving cell to a neighbouring cell (with better quality) without dropping the call
Traffic Reasons - to ensure that the traffic within the network is optimally
distributed between the different layers/bands of a network
If 2 or more handover (PC) criteria are satisfied simultaneously the following priority list
is used in determining which process is performed;
. Uplink and downlink Interference
2. Uplink quality
3. Downlink quality
4. Uplink level
5. Downlink level
6. Distance
7. Enhanced (RFD)
8. Rapid Field Drop (RFD)
9. Slow moving MS
10. Better cell i.e. Periodic check (Power Budget HO or Umbrella HO)
11. PC: Lower quality/level thresholds (UL/DL)
12. PC: Upper quality/level thresholds (UL/DL)
This document discusses 3G capacity optimization and monitoring software. It provides an overview of network elements and capacity features, including blocking and utilization counters, methodology parameters, and best practices. It also covers capacity features for various technologies like HSDPA, HSUPA, and HSPA+, listing codes, descriptions, and capabilities.
This document provides an overview of call reestablishment in WCDMA RAN networks. It describes the technical principles and triggers for call reestablishment when uplink radio link failure, SRB reset, TRB reset, air-interface process overlap, or air-interface process timeout issues occur. It also covers related features, network impacts, parameter optimization, and troubleshooting steps for deploying and monitoring call reestablishment.
The document provides information on the fundamentals and evolution of 3G mobile communication standards. It discusses:
- 1st generation standards including AMPS, TACS, NMT, and others operating between 30-200 KHz.
- 2nd generation standards including GSM, IS-136, IS-95, and PDC operating at 200 KHz, utilizing TDMA and early digital technologies.
- UMTS (3G) evolution through 3GPP releases, utilizing WCDMA technology, and achieving speeds up to 2 Mbps through improvements like HSPA and LTE.
A study on the effect of handover parameters on the network performance will be done in a trial cluster (part of Cerritos)
The parameter change to be implemented as an iterative process with each drive and the results to be compared to analyze the effect of the parameters
The document describes the architecture of Cassandra, including its startup process, layers (API, Dynamo, database), services (StorageProxy, MessagingService, Gossip), and failure handling. It also details how nodes communicate via the Gossip protocol to exchange state information and maintain a consistent cluster view.
The document discusses Cisco Discovery Protocol (CDP) and how it can be used to gather information about neighboring and remote network devices. CDP discovers information like device identifiers, address lists, port identifiers, and capabilities without needing to know the data link layer protocol. The summary also describes how to use commands like show cdp neighbor, show cdp entry, ping, and telnet to view CDP information and connect to remote devices.
This document provides guidelines for optimizing accessibility in Ericsson networks. It discusses key performance indicators (KPIs) for measuring accessibility, including call setup success rate and overall service accessibility. It also analyzes factors that can affect accessibility, such as admission control, processor load, and issues after call admission like congestion. Annexes describe user equipment idle mode procedures and call establishment procedures in detail.
The document describes traffic counter systems in RNCs (Radio Network Controllers) and cells in 3G WCDMA networks. It discusses key performance indicators for traffic, including Erlang load, throughput, number of radio bearers, and more. Counters are grouped by their measurement location (RNC or cell) and type (traffic, radio bearers, HSDPA, transmit power). The purpose is to understand and monitor traffic patterns and performance at different levels of the 3G network.
This document provides instructions for using the AMOS command line interface. It describes how to launch AMOS from different interfaces and lists common commands for checking alarms, nodes, hardware, and connectivity in RNCs and NodeBs. Key information includes IP addresses and passwords for accessing different RNCs, commands for listing and blocking nodes, and checking Ranap and Rnsap connections between network elements.
E nodeb useful commands for rf engineerVishal Padhya
This document provides instructions for verifying various network connections and configurations in an eNodeB using Moshell commands:
1. The st mme and st termpointtomme commands can check the S1-CP connection between the eNodeB and MME after a restart.
2. Verifying S1-UP connectivity requires pinging from a UE to an application server.
3. The st termpointtoenb command displays configured X2 links between eNodeBs.
4. The get intralte command checks if the Intra-LTE Handover feature is activated, required for handovers.
This document describes various 3G network traffic scenarios related to connection setup, resource allocation, mobility management, and radio link management. For each scenario, the main counters used to monitor performance are listed. The scenarios include RRC connection setup for circuit-switched and packet-switched calls, RAB establishment, paging, retention, connection and RAB release, admission control, quality monitoring, channel switching, system utilization, congestion detection and resolution, code allocation, compressed mode, cell availability, updates, mobility handovers between frequencies and radio technologies, radio link additions, deletions, and reconfigurations, soft handover operations, and CN hard handovers on CS and PS RABs.
The document discusses the requirements and configuration of Inter Frequency Load Balancing (IFLB) in LTE networks. IFLB aims to balance traffic load across cells on different frequencies by offloading user equipment between those cells. Key steps in IFLB include determining cell load, exchanging load information, selecting offload candidates, and handing users over to target cells if their signal quality is sufficient. The document provides guidance on setting parameters that control IFLB behavior and thresholds.
The document provides commands for the MoShell interface used to manage various network elements in a UMTS radio access network, including the radio network controller (RNC), radio network explorer/installer (RXI), and radio base station (RBS). The commands can be used to view status information, configure parameters, and troubleshoot issues relating to cells, modules, boards, interfaces, alarms, software, and other components on the RNC, RXI, and RBS.
LTE KPI Optimization - A to Z Abiola.pptxssuser574918
1. The document discusses LTE post launch optimization, including problem causes, solutions, and case studies.
2. It describes different types of counters used to collect PM statistics, including peg, gauge, accumulator, scan, PDF, DDM, calculated, trigACC, and trigSCAN counters.
3. Potential causes of poor accessibility for E-RAB establishment are discussed, including poor coverage, alarms, high load, hardware issues, high UL interference, PCI conflicts, RACH root sequence index planning, UE camping in wrong cells, wrong system constant settings, and VSWR or cell availability issues.
The document discusses UMTS planning and dimensioning processes. It describes:
1) The overall planning process which includes system dimensioning, radio network planning, pre-launch optimization, performance monitoring, and post-launch optimization.
2) The inputs, assumptions, and steps used for air interface dimensioning which includes uplink and downlink link budget analysis to determine coverage requirements and capacity needs.
3) Traffic modelling and load calculation methods to estimate subscriber traffic per cell based on factors like subscriber density, traffic profiles, and cell area.
The document summarizes different 3G events that can trigger handover procedures in UMTS networks. It describes 7 categories of events related to primary pilot channel, frequency, quality, channel traffic volume, CRCs, Rx-Tx parameters, and location/position. Each category contains multiple specific events that are monitored and can trigger handovers based on thresholds being passed for radio frequency parameters. The events monitor factors like signal quality, interference levels, traffic loads, transmission power, and device location to determine when a UE should hand over to a better serving cell.
The document discusses various resources in an LTE network that need to be monitored to ensure capacity and quality of service. It describes several key performance indicators (KPIs) related to resources like connected users, traffic volume, paging messages, processor usage, and provides thresholds and solutions to address issues.
This document summarizes various LTE KPIs and performance metrics related to random access, RRC connection establishment, ERAB establishment, and issues that may impact them. It provides potential causes for high values or failures in these metrics as well as recommended actions to investigate like checking RF parameters, capacity, licenses, alarms, configuration, and optimizing physical antenna settings.
. Overview
2. Handover Causes & Priorities
3. Threshold Comparison Process
4. Target Cell Evaluation Process
5. Handover Algorithms
Power Budget (PBGT)
Level & Quality (RXLEV & RXQUAL)
Umbrella (& Combined Umbrella/PBGT)
MS Speed (FMMS & MS_SPEED_DETECTION)
6. Imperative Handovers
Distance
Rapid Field Drop (RFD) & Enhanced Rapid Field Drop (ERFD)
7. Handover Timers
Call continuity - to ensure a call can be maintained as a MS moves geographical location from the coverage area of one cell to another
Call quality - to ensure that if an MS moves into a poor quality/coverage area the call can be moved from the serving cell to a neighbouring cell (with better quality) without dropping the call
Traffic Reasons - to ensure that the traffic within the network is optimally
distributed between the different layers/bands of a network
If 2 or more handover (PC) criteria are satisfied simultaneously the following priority list
is used in determining which process is performed;
. Uplink and downlink Interference
2. Uplink quality
3. Downlink quality
4. Uplink level
5. Downlink level
6. Distance
7. Enhanced (RFD)
8. Rapid Field Drop (RFD)
9. Slow moving MS
10. Better cell i.e. Periodic check (Power Budget HO or Umbrella HO)
11. PC: Lower quality/level thresholds (UL/DL)
12. PC: Upper quality/level thresholds (UL/DL)
This document discusses 3G capacity optimization and monitoring software. It provides an overview of network elements and capacity features, including blocking and utilization counters, methodology parameters, and best practices. It also covers capacity features for various technologies like HSDPA, HSUPA, and HSPA+, listing codes, descriptions, and capabilities.
This document provides an overview of call reestablishment in WCDMA RAN networks. It describes the technical principles and triggers for call reestablishment when uplink radio link failure, SRB reset, TRB reset, air-interface process overlap, or air-interface process timeout issues occur. It also covers related features, network impacts, parameter optimization, and troubleshooting steps for deploying and monitoring call reestablishment.
The document provides information on the fundamentals and evolution of 3G mobile communication standards. It discusses:
- 1st generation standards including AMPS, TACS, NMT, and others operating between 30-200 KHz.
- 2nd generation standards including GSM, IS-136, IS-95, and PDC operating at 200 KHz, utilizing TDMA and early digital technologies.
- UMTS (3G) evolution through 3GPP releases, utilizing WCDMA technology, and achieving speeds up to 2 Mbps through improvements like HSPA and LTE.
A study on the effect of handover parameters on the network performance will be done in a trial cluster (part of Cerritos)
The parameter change to be implemented as an iterative process with each drive and the results to be compared to analyze the effect of the parameters
The document describes the architecture of Cassandra, including its startup process, layers (API, Dynamo, database), services (StorageProxy, MessagingService, Gossip), and failure handling. It also details how nodes communicate via the Gossip protocol to exchange state information and maintain a consistent cluster view.
The document discusses Cisco Discovery Protocol (CDP) and how it can be used to gather information about neighboring and remote network devices. CDP discovers information like device identifiers, address lists, port identifiers, and capabilities without needing to know the data link layer protocol. The summary also describes how to use commands like show cdp neighbor, show cdp entry, ping, and telnet to view CDP information and connect to remote devices.
Upon reading the document, the key steps in a router's start-up process can be summarized as follows:
1. When power is applied, the router performs a power-on self-test and loads the bootstrap code from ROM to initialize hardware and find the IOS image.
2. The IOS image is then loaded from flash memory or another source such as TFTP into RAM where it is decompressed and executed.
3. The startup configuration is loaded, typically from NVRAM. If no configuration is present, the router enters setup mode to configure initial settings.
OAM 3G Network Ericsson discusses operation and maintenance of Ericsson's 3G radio access network. Session 1 covers the OSS, EMAS and other tools used for network operation. Session 2 discusses commissioning radio base stations, replacing modules, backing up network nodes, and upgrading base station capacity. Key tools include OSS, EMAS, element manager and scripts for configuration tasks. Proper planning, tools and procedures are needed for tasks like commissioning, module replacement, backups and hardware upgrades.
Multicloud connectivity using OpenNHRPBob Melander
The document discusses using OpenNHRP to enable multicloud connectivity across hybrid cloud deployments. It provides instructions for installing and configuring OpenNHRP on Ubuntu to set up a dynamic multipoint VPN (DMVPN) with one hub and two spoke nodes in different cloud environments. The configuration allows the spoke nodes to connect directly via an encrypted GRE tunnel without traversing the hub, providing optimized traffic flow across clouds.
한컴MDS_Virtual Target Debugging with TRACE32HANCOM MDS
Virtual Target provides a debug environment for targets that cannot be physically connected. It supports various debug interfaces like GTL, CADI, and debug tools from different vendors on different host operating systems and processor architectures. GTL was introduced to address limitations of slow RTL simulation and FPGA-based verification like long build times and difficulty retrieving debug information. It uses a virtual JTAG/bus interface over procedural Verilog interfaces and a software transactor plugin to enable co-simulation with debug tools.
The document discusses techniques from the DARPA Cyber Grand Challenge (CGC) and DEFCON CTF for developing automatic attack and defense systems, including fuzzing, symbolic/concolic execution, and software hardening. It provides an overview of the CGC competition format and challenges competitors to analyze binaries to discover vulnerabilities and generate exploits or patches. The competition was won by Team Mayhem from startup ForAllSecure, which utilized techniques like symbolic execution to analyze programs.
Operator E CA(Carrier Aggregation) Feature Test Guide.docxAkhtar Khan
This document provides a test guide for carrier aggregation (CA) features on Operator E's LTE network. It describes introducing multiple component carriers to expand bandwidth up to 100MHz. The test uses three carriers in different bands to test downlink carrier aggregation of up to 60MHz. Key steps included configuring the core network to allow high bandwidth, setting up the radio network for contiguous and non-contiguous carriers, verifying UE capabilities, and monitoring throughput results. Testing showed throughput increases with CA and supported band combinations depending on the UE model.
O'Reilly Velocity New York 2016 presentation on modern Linux tracing tools and technology. Highlights the available tracing data sources on Linux (ftrace, perf_events, BPF) and demonstrates some tools that can be used to obtain traces, including DebugFS, the perf front-end, and most importantly, the BCC/BPF tool collection.
WinDbg is a low-level debugger for Windows that provides features like usermode debugging, kernel debugging, post-mortem debugging, and support for debugging extensions. It can be used to debug crashes, analyze memory leaks, find deadlocks, and investigate other issues when the higher-level Visual Studio debugger is not sufficient. The document provides examples of using WinDbg commands and extensions like SOS to debug memory leaks, analyze crashes based on offset or dump files, and investigate .NET deadlocks.
This document provides guidance on collecting diagnostic information from a Juniper firewall for different types of issues. It outlines 7 sections for collecting data on system crashes, high CPU usage, NSRP problems, throughput and forwarding performance issues, high memory usage, data flow problems, and static routing problems. For each issue, it lists basic information and detailed commands to run to gather relevant logs, configurations, performance metrics and debug outputs.
This document provides information on various debugging and profiling tools that can be used for Ruby including:
- lsof to list open files for a process
- strace to trace system calls and signals
- tcpdump to dump network traffic
- google perftools profiler for CPU profiling
- pprof to analyze profiling data
It also discusses how some of these tools have helped identify specific performance issues with Ruby like excessive calls to sigprocmask and memcpy calls slowing down EventMachine with threads.
This document summarizes the setup of a ROS-based robot system, including:
1. Describing the robot frame, ROS host, and microcontroller client nodes.
2. Explaining how to set up teleoperation, odometry, sensor integration, and the navigation stack.
3. Detailing the preparation of the robot frame and parts, ROS host, and microcontroller client.
The document provides instructions for configuring three Ubiquiti EdgeRouter devices (R1, R2, R3) with OSPF routing. It describes setting the IP addresses and OSPF parameters for each router, including their router IDs, networks, and areas. It confirms the OSPF configuration is working by showing R1 has learned the route to network 10.0.60.0/24 through R2 and can ping and trace route to R3 on that network. It also lists some common OSPF commands for viewing routes, neighbors, and interface information.
1. The document discusses OpenStack Neutron and Open vSwitch (OVS), describing their architecture and configuration. It explains that Neutron uses OVS to provide virtual networking and switching capabilities between virtual machines.
2. Key components of the Neutron-OVS architecture include the Neutron server, OVS agents on compute nodes, and the OVS daemon that implements the switch in the kernel and userspace.
3. The document also provides examples of configuring an OVS bridge and ports for virtual networking in OpenStack.
How to-mount-3 par-san-virtual-copy-onto-rhel-servers-by-Dusan-BaljevicCircling Cycle
The document describes how to mount a 3PAR virtual copy volume onto a RHEL server. It involves creating host definitions and exporting volumes from 3PAR to the server. The volumes are then mapped, formatted, and mounted. Finally, a virtual copy is created on 3PAR and exported to the server, where it is detected as a new volume.
Using the new extended Berkley Packet Filter capabilities in Linux to the improve performance of auditing security relevant kernel events around network, file and process actions.
This document discusses adding a new pass to the BOLT binary optimizer. It begins with an overview of the BOLT pipeline and intermediate representation. It then provides an example of adding a simple peephole optimization rule. The document outlines various techniques for debugging and testing new passes, such as triaging crashes with a bisection script, printing analysis results, and dumping functions to files. It concludes with notes on implementing a new pass by inheriting from the BinaryFunctionPass class and integrating it into the pass manager to run on whole programs in parallel.
Similar to 216506756-Moshell-Basic-Command-v1-0.ppt (20)
CAKE: Sharing Slices of Confidential Data on BlockchainClaudio Di Ciccio
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Infrastructure Challenges in Scaling RAG with Custom AI models
216506756-Moshell-Basic-Command-v1-0.ppt
1. Moshell (Basic command)
1. momt ( 전체 MO Tree 파악하기 )
2. moshell 169.254.1.10 , lt all (RBS 접속 )
3. cvcu, cvls, cvset, cvrm, cvmk (cv 관련 )
4. acc 0 manualrestart (Restart RBS )
5. st mme , st fdd , get mme ipaddress ( MME, cell 상태 )
6. st cell , bl , deb ( Cell Block, Unblock )
7. pr AntennaUnit , lpr RfBranch, stde , st riport ( RU 점검 )
8. diff (Compare MO)
9. al , ala , alt ( Alarm Check )
10. lga , lgx, lg ( alarm log 등 log 보기 )
11. get . tac ( tac 확인 )
12. get . earfcn ( Center 주파수 확인 )
13. get . band ( 주파수 Bandwidth 확인 )
14. get . feature ( Feature 확인 )
15. inv ( license State 확인 )
16. get sync ( Clock 상태 확인 )
17. get . ntp NTP (동기 서버 ) 확인
18. get 1 , readclock ( 시간 확인 )
19. ue print -admitted ( 몇 call 결렸는지 확인 )
20. appsh oper , appsh data <{udp|gtp}> <sid> (bearer 정보 )
21. get extemal , get term , get point , get . relation (Handover 확인)
22. get . ipaddress , get . vid (IP Address 및 VLAN ID 확인 )
23. cabr , caba ( 장애발생시 확인 )
24. cabx , lhsh BXP_3_1 fui get vswr ( VSWR 확인 )
25. cabx , lhsh BXP_0_1 warpA read DL_PM_PA0_C0 ( 실재 출력 확인 )
26. get . Power ( 출력 타겟 확인하기 )
27. pr security ( Security 확인 )
28. get systemc ( System constant : customer 공개금지 )
29. get . nooftx , noofrx ( ANT나 전송 모드 선택 )
30. pr anr ( ANR 설정 )
31. license server , get . fingerprint (License 관리 )
32. acc IpAccessHostEt ping (ping 확인 )
33. Statistics DATA
34. get . inac , set Rcs=1 tInactivityTimer ( Inactivity timer )
35. get upgr stat, pr upgrade ( Upgrade 확인 )
3. [~]$ moshell 169.254.1.10
####################################################################
# Welcome to MoShell 8.0r #
# Finn Magnusson, Jan Pettersson #
# http://utran01.au.ao.ericsson.se/moshell #
# Contact: Finn.Magnusson@ericsson.com #
# David.Smith@ericsson.com #
####################################################################
Checking ip contact...OK
HELP MENU : h
BASIC MO COMMANDS : m
OTHER MO COMMANDS : n
OTHER COMMANDS : o
PM COMMANDS : p
QUIT : q
169.254.1.10> lt all
110323-21:50:44 169.254.1.10 8.0r stopfile=/tmp/2920
Checking MOM version...ERBS_NODE_MODEL_B_1_40
Using MOM version: ERBS_NODE_MODEL_B_1_40_COMPLETE
Parsing MOM (cached): /home/Administrator/moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.cache.gz .....................................................Done.
Using paramfile /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt
Parsing file /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt ............................................................................Done.
Fetching IOR file...Done.
Connecting to 10.0.0.165:56834 (CorbaSecurity=OFF, corba_class=2, java=1.6.0_23, jacoms=R73D19, jacorb=R73D01)
**** Welcome to the Simple Mo Browser (version 3.0)!
Trying file=C:/cygwin/home/Administrator/moshell_logfiles/logs_moshell/tempfiles/20110323-215038_1808/ior1808
**** Test Construction OK
****
$mobrowser_pid = 3436
Connected to 169.254.1.10 (SubNetwork=ONRM_ROOT_MO_R,SubNetwork=TEST,MeContext=ENB04,ManagedElement=1)
Connected to 169.254.1.10 (SubNetwork=ONRM_ROOT_MO_R,SubNetwork=TEST,MeContext=ENB04,ManagedElement=1)
Last MO: 1043. Loaded 1043 MOs. Total: 1044 MOs.
ENB04>
Connect to RBS
1. Have laptop setting same as left.
2. Enter moshell 169.254.1.10 for connection.
3. Enter lt all
1. The above is a access method when you connect directly to LNB PORT in the station.
2. In case of access through LSM, use (10.0.0.163)
4. ENB02> cvcu
110326-10:42:02 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/896
===================================================================================================
110326-10:42 CV Name Upgrade Package Release
===================================================================================================
Startable: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Loaded: RU_SW_Change_R25S-alarmc_cdmaHOcell33 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Executing: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Last created: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
-------------------------------------------------------------------------------------------------------------------
Current UpgradePkg: UpgradePackage=R9AS CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
AutoCreatedCV: Disabled
Countdown status: Deactivated
Ongoing CV activity: 0 (IDLE)
Rollback status: Rollback is off
=================================================================================================
ENB02> cvls
110326-10:42:06 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/896
==================================================================================================
110326-10:42 CV Name Upgrade Package Release
==================================================================================================
Startable: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Loaded: RU_SW_Change_R25S-alarmc_cdmaHOcell33 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Executing: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
Last created: selfconfig_autocreated1 CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
-------------------------------------------------------------------------------------------------------------------
Current UpgradePkg: UpgradePackage=R9AS CXP102051/12_R9AS L11B (LSV59.3-4-CPP_8.0.2)
AutoCreatedCV: Disabled
Countdown status: Deactivated
Ongoing CV activity: 0 (IDLE)
Rollback status: Rollback is off
===================================================================================================
UP name ProductData CVs LMs PrDate LastCV state Release CompatIndex
===================================================================================================
InitialUP 0_0 0 0 0 IDLE, ONLY_DELETEABLE
Virtual_2_of_CXP102051/10_R5EA CXP102051/10_R5EA 0 0 100906 IDLE, ONLY_DELETEABLE L11A
Virtual_0_of_CXP102051/12_R8AA CXP102051/12_R8AA 1 0 110216 110314 IDLE, ONLY_DELETEABLE L11B
Virtual_1_of_CXP102051/12_R7AK CXP102051/12_R7AK 4 0 110203 110315 IDLE, ONLY_DELETEABLE L11B (LSV59.3-3-CPP_8.0.2)
R9BE%2 CXP102051/10_R9BE/2 29 192 101207 110323 IDLE, UPGRADE_COMPLETED L11A.0.1.0 (EP30-CPP_8.0.0.3) CXP102051%1-R4
R9AS CXP102051/12_R9AS 16 200 110303 110325 IDLE, UPGRADE_COMPLETED L11B (LSV59.3-4-CPP_8.0.2) CXP102051%1-R4
==================================================================================================
CV Name Creation Date UpgradePackage Release Type Operator Comment
==================================================================================================
BasicCV_CXP102106%10_R9BE%2 2010-12-07 13:28 CXP102051/10_R9BE/2 L11A.0.1.0 other unknown none
LTE_Initial 2010-12-07 13:33 CXP102051/10_R9BE/2 L11A.0.1.0 other ProductionTest ProductionTest
L11A-artiza-vlanoff 2011-03-01 02:26 CXP102051/10_R9BE/2 L11A.0.1.0 other cwcho none
===================================================================================================
>>> Total: 50 CV's, 6 UP's
ENB03>
CV
※ What is CV ?
Similar to system restoration point of Windows.
It has all Parameter and Version information for rollback
to the previous status promptly in case of failure to
reduce no service time. ( Maximum number of CVs
stored in each station is 50.)
CV type: Manual rollback point (Made by user)
Installation rollback point (Automatically
created during upgrade)
System rollback point (Automatically
created by system)
Startable : Display CV activated at the time of reset
Loaded :
Executing : Display CV currently in operation
Last created : Display CV created most recently
1. Current CV check: cvcu
2. Entire CV check: cvls
3. CV change: cvset ( Select certain CV among saved
4. CV creation: cvmk
5. CV deletion: cvrm
6. CV creation & startable change: cvms
7. reset: acc 0 manualrestart <┛
y <┛
3 <┛
0 <┛
0 <┛
6. pol 5 5 <┛
5. Restart RBS
ENB03> acc 0 manualrestart
110323-22:33:17 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3644
The node has been restarted on a different CV: from OptimizedUDPDL2 to selfconfig_autocreated2.
Rereading MOM and MIB...
Connected to 169.254.1.10 (SubNetwork=ONRM_ROOT_MO_R,SubNetwork=TEST,MeContext=ENB03,ManagedElement=1)
Last MO: 835. Loaded 835 MOs. Total: 836 MOs.
Checking MOM version...ERBS_NODE_MODEL_B_1_40
Using MOM version: ERBS_NODE_MODEL_B_1_40_COMPLETE
Parsing MOM (cached): /home/Administrator/moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.cache.gz ....................................................Done.
Using paramfile /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt
Parsing file /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt ...........................................................................Done.
Call Action manualrestart on following 1 MOs ?
===================================================================================
0 ManagedElement=1
INFO: The RBS node ENB03 will be restarted on CV: selfconfig_autocreated2
===================================================================================
Call action manualrestart on 1 MOs. Are you Sure [y/n] ? y
================================================================================================================
Proxy MO Action Nr of Params
================================================================================================================
0 ManagedElement=1 manualRestart 3
Parameter 1 of 3, restartRank (enumRef-RestartRank):
Enter one of the following integers: 0:RESTART_WARM, 1:RESTART_REFRESH, 2:RESTART_COLD, 3:RESTART_COLDWTEST: 3
Parameter 2 of 3, restartReason (enumRef-RestartReason):
Enter one of the following integers: 0:PLANNED_RECONFIGURATION, 1:UNPLANNED_NODE_EXTERNAL_PROBLEMS, 2:UNPLANNED_NODE_UPGRADE_PROBLEMS, 3:UNPL
ANNED_O_AND_M_ISSUE, 4:UNPLANNED_CYCLIC_RECOVERY, 5:UNPLANNED_LOCKED_RESOURCES, 6:UNPLANNED_COLD_WITH_HW_TEST,
7:UNPLANNED_CALL_PROCESSING_DEGRA DATION, 8:UNPLANNED_LOW_COVERAGE, 30:UPGRADE_BOARD_RESTART: 0
Parameter 3 of 3, restartInfo (string): 0
>>> Return value = null
===============================================================================================================
Total: 1 MOs attempted, 1 MOs actioned
ENB03>
ENB03> pol 5 5
110323-22:33:35 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3644
Waiting 5 seconds before starting to poll...
No contact to port 80, retrying in 1 second...
No contact to port 80, retrying in 1 second...
No contact to port 80, retrying in 1 second...
CORBA.OBJECT_NOT_EXIST Polling for 0m41s, MO service not ready, retrying in 5 seconds...
CORBA.OBJECT_NOT_EXIST Polling for 0m46s, MO service not ready, retrying in 5 seconds...
CORBA.OBJECT_NOT_EXIST Polling for 0m51s, MO service not ready, retrying in 5 seconds...
CORBA.OBJECT_NOT_EXIST Polling for 1m02s, MO service not ready, retrying in 5 seconds...
MO service is ready.
ENB03>
1. acc 0 manualrestart
2. y
3. 3
4. 0
5. 0
pol 5 5
Use it when you want to know
when the signal resumes after
disconnection.
pol 5: interval 5: wait time
169.254.1.10> polu 5 5
110331-12:35:07 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE
stopfile=/tmp/2168
Waiting 5 seconds before starting to poll...
No ongoing activity on the UpgradePackage MOs.
169.254.1.10> pol 5 5
110331-12:35:25 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE
stopfile=/tmp/2168
Waiting 5 seconds before starting to poll...
MO service is ready.
169.254.1.10>
6. eNB3> lst mme
110310-16:38:07 10.0.0.164 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/4728
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
536 1 (UNLOCKED) 1 (ENABLED) ENodeBFunction=1,TermPointToMme=LGERMME01
===================================================================================
Total: 1 MOs
eNB3> lst fdd
110328-15:19:52 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3796
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
854 1 (UNLOCKED) 1 (ENABLED) ENodeBFunction=1,EUtranCellFDD=33
879 0 (LOCKED) 0 (DISABLED) ENodeBFunction=1,EUtranCellFDD=32
905 1 (UNLOCKED) 1 (ENABLED) ENodeBFunction=1,EUtranCellFDD=31
===================================================================================
Total: 3 MOs
eNB3> st sector
110324-12:20:57 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/2740
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
1030 1 (UNLOCKED) 0 (DISABLED) SectorEquipmentFunction=S1
1031 1 (UNLOCKED) 0 (DISABLED) SectorEquipmentFunction=S2
1036 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=S3
===================================================================================
Total: 3 MOs
eNB3> get mme ipaddress
110310-16:38:40 10.0.0.164 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/4728
=================================================================================================================
MO Attribute Value
=================================================================================================================
TermPointToMme=LGERMME01 ipAddress1 4.2.0.132
TermPointToMme=LGERMME01 ipAddress2 0.0.0.0
TermPointToMme=LGERMME01 usedIpAddress 4.2.0.132
=================================================================================================================
Total: 1 MOs
MME , CELL Status
To check MME status
Check CELL status
Same command lst cell
MME Node addition method
cr ENodeBFunction=1,TermPointToMme=LGERMME02
lget ENodeBFunction=1,TermPointToMme=LGERMME02
lset ENodeBFunction=1,TermPointToMme=LGERMME02 ipAddress1 xxx.xxx.xxx.xxx
deb LGERMME02
MME IP modification method (From
station side)
ENB03> get mme ip
ENB03> bl mme
ENB03> set mme ipAddress1 100.100.100.150
ENB03> deb mme
ENB03> lst mme
7. ENB03> st cell
110328-15:10:05 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/1940
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
147 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,SubDeviceGroup=bb-1,CellDeviceSet=1
854 1 (UNLOCKED) 1 (ENABLED) ENodeBFunction=1,EUtranCellFDD=33
879 0 (LOCKED) 0 (DISABLED) ENodeBFunction=1,EUtranCellFDD=32
905 1 (UNLOCKED) 1 (ENABLED) ENodeBFunction=1,EUtranCellFDD=31
===================================================================================
ENB03> deb 879
110328-15:12:50 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/1940
Deblock following 1 MOs ?
===================================================================================
879 ENodeBFunction=1,EUtranCellFDD=32
===================================================================================
Deblock 1 MOs. Are you Sure [y/n] ? y
====================================================================================
Id MO administrativeState Result
====================================================================================
879 EUtranCellFDD=32 1 >>> Set.
====================================================================================
Total: 1 MOs attempted, 1 MOs set
ENB03> bl 879
110328-15:13:04 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/1940
Block following 1 MOs ?
===================================================================================
879 ENodeBFunction=1,EUtranCellFDD=32
===================================================================================
Block 1 MOs. Are you Sure [y/n] ? y
Block, Unblock
Unblock Cell no. 32, currently
blocked.
Check Cell status.
Block Cell no. 32, currently
unblocked.
8. RU Check
ENB03> lk fdd
110331-15:40:07 169.254.1.10 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/2392
===============================================================================
Proxy Adm State Op. State MOs linked to 476:EUtranCellFDD=31
===============================================================================
476 1 (UNLOCKED) 0 (DISABLED) EUtranCellFDD=31
477 EUtranCellFDD=31,UeMeasControl=1
480 EUtranCellFDD=31,UeMeasControl=1,ReportConfigEUtraBestCell=1
479 EUtranCellFDD=31,UeMeasControl=1,ReportConfigEUtraBadCovSec=1
478 EUtranCellFDD=31,UeMeasControl=1,ReportConfigEUtraBadCovPrim=1
492 1 (UNLOCKED) 0 (DISABLED) SectorEquipmentFunction=S1
147 AntennaUnitGroup=1,RfBranch=1
149 AntennaUnitGroup=1,RfBranch=2
123 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,RiPort=DATA_1
131 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,RiPort=DATA_2
143 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,RiPort=DATA_1
135 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,RiPort=DATA_2
126 1 (UNLOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru,RfPort=A
130 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru,RfPort=B
138 1 (UNLOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,DeviceGroup=ru,RfPort=A
141 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,DeviceGroup=ru,RfPort=B
127 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru,RfPort=RXA_IO
125 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru,RfPort=RXB_IO
140 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,DeviceGroup=ru,RfPort=RXA_IO
142 0 (LOCKED) 0 (DISABLED) RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,DeviceGroup=ru,RfPort=RXB_IO
===============================================================================
Total: 20 MOs
eNB3> st aux
110331-15:40:14 169.254.1.10 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/2392
===============================================================================
Proxy Adm State Op. State MO
===============================================================================
122 1 (UNLOCKED) 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1
134 1 (UNLOCKED) 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2
===============================================================================
Total: 2 MOs
eNB3> st ru
110331-15:40:18 169.254.1.10 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/2392
===============================================================================
Proxy Adm State Op. State MO
===============================================================================
63 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,GeneralProcessorUnit=1
122 1 (UNLOCKED) 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1
124 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=1,AuxPlugInUnit=RU-1-1,DeviceGroup=ru
134 1 (UNLOCKED) 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2
136 0 (DISABLED) Equipment=1,RbsSubrack=1,RbsSlot=2,AuxPlugInUnit=RU-1-2,DeviceGroup=ru
===============================================================================
Total: 5 MOs
eNB3> lh ru vii
110331-15:41:29 169.254.1.10 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/
Please enter Node Password:
Checking available boards on node...
...
Created following board-groups: all, allp, mp, bp, tu, coremp, ommp, scb, sxb, scx, sccpmp
, et, etmfg, etmfx, aal2ap, aal2ncc, aal2cpsrc, aal2rh, xp, rax, tx,gcpu.
>>> Type "bp" to view available board-groups and "bp <group>" to view group contents.
============================================================
$ lhsh BXP_0_1 vii
BXP_0_1: Indicated states:
BXP_0_1: Red:
BXP_0_1: Default (off)
BXP_0_1: Green:
BXP_0_1: Default (steady light)
BXP_0_1: Yellow:
BXP_0_1: Default (off)
===========================================================
$ lhsh BXP_3_1 vii
BXP_3_1: Indicated states:
BXP_3_1: Red:
BXP_3_1: Default (off)
BXP_3_1: Green:
BXP_3_1: Default (steady light)
BXP_3_1: Yellow:
BXP_3_1: Default (off)
$
12. ENB02> al
110310-13:47:12 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE stopfile=/tmp/2848
Connecting to 10.0.0.163:56834 (CorbaSecurity=OFF, corba_class=2, java=1.6.0_23, jacoms=R73D19, jacorb=R73D01)
Trying file=C:/cygwin/home/Administrator/moshell_logfiles/logs_moshell/tempfiles/20110310-134651_4212/ior4212
Resolving the alarm service in OMS...
Simple Alarm Client initialized...
Starting to retrieve active alarms
Nr of active alarms are: 9
================================================================================================
Sever Specific Problem Cause Mo-Reference
================================================================================================
Maj Disconnected equipment_malfunction HwUnit=SCU
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=21
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=22
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=23
Maj TU Synch Reference Loss of Signal loss_of_signal Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=GPS
Min Emergency Unlock of Software Licensing alarm_indication_signal Licensing=1
Min HwFault equipment_malfunction Subrack=1,Slot=1,PlugInUnit=1,RiPort=A
Min HwFault equipment_malfunction Subrack=1,Slot=1,PlugInUnit=1,RiPort=D
Min Loss of Synch Reference Redundancy replaceable_unit_problem Synchronization=1
>>> Total: 9 Alarms (0 Critical, 5 Major)
ENB02> ala
110310-13:47:18 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE stopfile=/tmp/2848
Connecting to 10.0.0.163:56834 (CorbaSecurity=OFF, corba_class=2, java=1.6.0_23, jacoms=R73D19, jacorb=R73D01)
Trying file=C:/cygwin/home/Administrator/moshell_logfiles/logs_moshell/tempfiles/20110310-134651_4212/ior4212
Resolving the alarm service in OMS...
Simple Alarm Client initialized...
Starting to retrieve active alarms
Nr of active alarms are: 9
================================================================================================
Sever Specific Problem Cause Mo-Reference
================================================================================================
Maj Disconnected equipment_malfunction HwUnit=SCU
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=21
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=22
Maj ResourceAllocationFailure configuration_or_customizing_error EUtranCellFDD=23
Maj TU Synch Reference Loss of Signal loss_of_signal Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=GPS
Min Emergency Unlock of Software Licensing alarm_indication_signal Licensing=1
Min HwFault equipment_malfunction Subrack=1,Slot=1,PlugInUnit=1,RiPort=A
Min HwFault equipment_malfunction Subrack=1,Slot=1,PlugInUnit=1,RiPort=D
Min Loss of Synch Reference Redundancy replaceable_unit_problem Synchronization=1
Alarm Id : SubNetwork=ONRM_ROOT_MO_R,SubNetwork=TEST,MeContext=ENB02_4
Event Time : 2011. 3. 10 $ 9:51:13
Perceived Severity : Major
Check Alarm
Brief check of Alarm al
Detailed check of Alarm ala
Check Alarm by the hour alt
13. ENB03> lga
110328-16:46:20 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/2764
Please enter Node Password:
Startdate=19661031.231320, Enddate=20110329.074624
....................Get /c/logfiles/alarm_event/ALARM_LOG.xml /home/Administrator/moshell_logfiles/logs_moshell/tempfiles/20110328-161024_2612/alarmLog2
764.xml ... OK
=======================================================================================================
Timestamp (UTC) S Problem Cause MO-reference
=======================================================================================================
2011-03-28 01:53:03 AL m Loss of Synch Reference Redundancy replaceable_unit_problem Synchronization=1
2011-03-28 02:42:20 AL * Synch Reference Not Reliable clock_synchronisation_problem Synchronization=1
2011-03-28 02:42:20 AL * Loss of Synch Reference Redundancy replaceable_unit_problem Synchronization=1
2011-03-28 05:52:58 AL M ServiceUnavailable underlying_resource_unavailable EUtranCellFDD=31
2011-03-28 05:53:37 AL * ServiceUnavailable underlying_resource_unavailable EUtranCellFDD=31
2011-03-28 06:23:23 AL M TU Synch Reference Loss of Signal loss_of_signal
Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1,TuSyncRef=GPS
2011-03-28 06:23:47 AL M Synch Reference Not Reliable clock_synchronisation_problem Synchronization=1
2011-03-28 06:24:31 AL * Synch Reference Not Reliable clock_synchronisation_problem Synchronization=1
2011-03-28 06:27:18 AL M System Clock in Holdover Mode replaceable_unit_problem Synchronization=1
ENB03> lg
110328-16:56:25 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/464
***************************************************************************************
lg[acdefghilmnopqrstuvwxyz] [-l <logdirectory|logfile|zipfile>] [-m <minustime>] [-p <plustime>] [-s <startdate>] [-e <enddate>] [-g
<boardgroup >] [-n <nodefilter>] [|<unixcmds>]
***************************************************************************************
Fetching and processing of node logs
All options can be combined together, except options "d","w","x","f" which can only be combined with the options "r" and "c".
Log Options:
************
- a: Alarm log (ALARM_LOG.xml). History of alarms raising and ceasing.
- x: Active alarms (ALARM_LOG.xml). Snapshot of alarms active on a specific date/time given in -m/-s option.
- e: Event log (EVENT_LOG.xml). History of MO events.
- v: Availability log (CELLO_AVAILABILITY2_LOG.xml). History of node/board/program restarts.
- s: System log (/c/logfiles/systemlog). History of node/board/program restarts.
- p: Post Mortem Dumps (/c/pmd) and LTE ENodeB error files (/c/logfiles/troubleshooting/error). History of board/program crashes. PMD files are
saved permanently in moshell_logfiles/logs_moshell/pmdfiles/<nodeaddress>/pmd .
- u: Upgrade log (Trace.log and Trace.log_old). History of system upgrades.
- d: Downtime log. History of node outages.
- o: MO command log (CORBA_AUDITTRAIL_LOG.xml). History of MO write commands (set/action/create/delete).
- q: MO command log in "trun" format (CORBA_AUDITTRAIL_LOG.xml). Useful for recovering configuration data which was not saved to CV before node
Check log
14. ENB03> get . tac
110329-15:36:22 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3924
==========================================================================================================
=======
MO Attribute Value
==========================================================================================================
=======
Security=1 targetMonitorPortActive true
EUtraNetwork=1,ExternalENodeBFunction=Samsung,ExternalEUtranCellFDD=4506-18-1 tac 4
EUtraNetwork=1,ExternalENodeBFunction=Samsung,ExternalEUtranCellFDD=4506-18-2 tac 4
EUtraNetwork=1,ExternalENodeBFunction=Samsung,ExternalEUtranCellFDD=Samsung tac 4
EUtraNetwork=1,ExternalENodeBFunction=NSN,ExternalEUtranCellFDD=NSN tac 52
EUtraNetwork=1,ExternalENodeBFunction=ENB02,ExternalEUtranCellFDD=4506-2-21 tac 4
EUtraNetwork=1,ExternalENodeBFunction=ENB02,ExternalEUtranCellFDD=4506-2-22 tac 4
EUtraNetwork=1,ExternalENodeBFunction=ENB02,ExternalEUtranCellFDD=ENB02 tac 4
EUtraNetwork=1,ExternalENodeBFunction=1,ExternalEUtranCellFDD=43 tac 4
EUtraNetwork=1,ExternalENodeBFunction=1,ExternalEUtranCellFDD=42 tac 4
EUtraNetwork=1,ExternalENodeBFunction=1,ExternalEUtranCellFDD=4506-4-41 tac 4
EUtranCellFDD=33 dlInterferenceManagementActive true
EUtranCellFDD=33 tac 2
EUtranCellFDD=33 ulInterferenceManagementActive true
EUtranCellFDD=32 dlInterferenceManagementActive true
EUtranCellFDD=32 tac 2
EUtranCellFDD=32 ulInterferenceManagementActive true
EUtranCellFDD=31 dlInterferenceManagementActive true
EUtranCellFDD=31 tac 2
EUtranCellFDD=31 ulInterferenceManagementActive true
==========================================================================================================
=======
Total: 14 Mos
ENB04> eset1 EUtranCellFDD tac 4
110303-09:38:35 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE stopfile=/tmp/2136
Set following 3 attributes?
============================================================================================================
762 EUtranCellFDD=41 tac
784 EUtranCellFDD=43 tac
808 EUtranCellFDD=42 tac
============================================================================================================
Set 3 attributes. Are you Sure [y/n] ? y
============================================================================================================
=====
Id MO Attribute Value Result
============================================================================================================
=====
762 EUtranCellFDD=41 tac 3 >>> Set.
784 EUtranCellFDD=43 tac 3 >>> Set.
Check Tac
TAC : Tracking Area Code
15. ENB04> get . earfcn
110322-21:48:28 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2744
=================================================================================================================
MO Attribute Value
=================================================================================================================
EUtranCellFDD=41 earfcndl 2600
EUtranCellFDD=41 earfcnul 20600
EUtranCellFDD=43 earfcndl 2600
EUtranCellFDD=43 earfcnul 20600
EUtranCellFDD=42 earfcndl 2600
EUtranCellFDD=42 earfcnul 20600
=================================================================================================================
Total: 3 MOs
Check Center frequency
Check frequency allocation
information
LGU+ Center Frequency
889.0Mhz(DL) : 2600
844.0Mhz(UL) : 20600
set EUtranCellFDD earfcnul 21400
set EUtranCellFDD earfcndl 3400
LGU+ Center Freq
889.0Mhz(DL) : 2600
844.0Mhz(UL) : 20600
set EUtranCellFDD earfcnul 20600
set EUtranCellFDD earfcndl 2600
Attribute 1 of 8, earfcndl (long): 3400
Attribute 2 of 8, earfcnul (long): 21400
16. ENB02> get . band
110322-22:04:47 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/4500
=================================================================================================
MO Attribute Value
=================================================================================================
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=10MHz CapacityChannelBandwidthId 10MHz
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=10MHz capacityUnitChannelBandwidth Number of 10000kHz licenses
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=10MHz keyIdChannelBandwidth CXC4010718
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=10MHz licenseCapacityChannelBandwidth 1
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=10MHz licenseStateChannelBandwidth 1 (ENABLED)
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=15MHz CapacityChannelBandwidthId 15MHz
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=15MHz capacityUnitChannelBandwidth Number of 15000kHz licenses
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=15MHz keyIdChannelBandwidth CXC4010719
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=15MHz licenseCapacityChannelBandwidth 1
Licensing=1,CapacityLicenses=1,CapacityChannelBandwidth=15MHz licenseStateChannelBandwidth 1 (ENABLED)
Licensing=1,CapacityLicenses=1,UlBasebandCapacity=1 UlBasebandCapacityId 1
ENodeBFunction=1 dlTransNwBandwidth 1000
ENodeBFunction=1 ulTransNwBandwidth 1000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-31 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-31 ulChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-32 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-32 ulChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-33 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-33 ulChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-41 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-41 ulChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-42 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-42 ulChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-43 dlChannelBandwidth 10000
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-43 ulChannelBandwidth 10000
EUtranCellFDD=21 dlChannelBandwidth 10000
EUtranCellFDD=21 prsBandwidth 4 (N100)
EUtranCellFDD=21 ulChannelBandwidth 10000
EUtranCellFDD=22 dlChannelBandwidth 10000
EUtranCellFDD=22 prsBandwidth 4 (N100)
EUtranCellFDD=22 ulChannelBandwidth 10000
EUtranCellFDD=22,EUtranFreqRelation=3 allowedMeasBandwidth 6
Cdma2000Network=1,Cdma2000FreqBand=1 Cdma2000FreqBandId 1
Cdma2000Network=1,Cdma2000FreqBand=1 hrpdBandClass 4 (BAND_CLASS_4)
EUtranCellFDD=23 dlChannelBandwidth 10000
EUtranCellFDD=23 prsBandwidth 4 (N100)
EUtranCellFDD=23 ulChannelBandwidth 10000
AdmissionControl=1 dlTransNwBandwidth 1000
AdmissionControl=1 ulTransNwBandwidth 1000
SectorEquipmentFunction=S1 fqBand 0
SectorEquipmentFunction=S2 fqBand 5
SectorEquipmentFunction=S3 fqBand 5
================================================================================================
Total: 24 MOs
Check frequency bandwidth
Use for frequency Bandwidth
check
Downlink to no. 21 Cell
downlink bandwidth is
10Mhz
Uplink to no. 21 Cell
bandwidth is 10Mhz
Bandwidth change
get . dlchannel
get . ulchannel
lst cell
bl 865
set EUtranCellFDD=31 dlChannelBandwidth 5000
set EUtranCellFDD=31 ulChannelBandwidth 5000
get . Channelband
lst cell
deb 865
get 865
17. ENB02> get . feature
110323-11:41:12 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/3220
==========================================================================================
MO Attribute Value
==========================================================================================
Licensing=1,OptionalFeatures=1 OptionalFeaturesId 1
Licensing=1,OptionalFeatures=1,SharedNetworkSupport=1 featureStateSharedNetworkSupport 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Dl64Qam=1 featureStateDl64Qam 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,MixedMode=1 featureStateMixedMode 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,IntraLTEHandover=1 featureStateIntraLTEHandover 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,CsfbForLimitedDualRadioUE=1 featureStateCsfbForLimitedDualRadioUE 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,AirIfLoadGenerator=1 featureStateAilg 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,RetSupport=1 featureStateRetSupport 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Anr=1 featureStateAnr 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Aisgv2FwDownload=1 featureStateAisgv2FwDownload 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,InterFrequencyLTEHandover=1 featureStateInterFrequencyLTEHandover 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,Irc=1 featureStateIrc 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,MultiErabsPerUser=1 featureStateMultiErabsPerUser 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,WcdmaSessionContinuity=1 featureStateWcdmaSessionContinuity 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,RbsEventStreamer=1 featureStateEventStreaming 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,OtdoaSupl=1 featureStateOtdoaSupl 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,RlcUm=1 featureStateRlcUm 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,PmInitiatedUeMeasurements=1 featureStatePmInitiatedUeMeasurements 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,TimeAndPhaseSynchWithGPS=1 featureStateTimeAndPhaseSynchWithGPS 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,AgpsSupl=1 featureStateAgpsSupl 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,InterFrequencySessionContinuity=1 featureStateInterFrequencySessionContinuity 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,UePosCellId=1 featureStateCellId 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,RetCascading=1 featureStateRetCascading 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,VswrSupervision=1 featureStateVswrSupervision 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,DualAntDlPerfPkg=1 featureStateDualAntDlPerfPkg 1 (ACTIVATED)
Licensing=1,OptionalFeatures=1,IntraLTEHODataFwd=1 featureStateIntraLTEHODataFwd 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,GsmSessionContinuity=1 featureStateGsmSessionContinuity 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,TmaSupport=1 featureStateTmaSupport 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Cdma2000SessionContinuity=1 featureStateCdma2000SessionContinuity 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,RetConfigurationMgt=1 featureStateRetConfigurationMgt 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,MaximumCellRange=1 featureStateMaximumCellRange 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,QosAwareScheduler=1 featureStateQosAwareScheduler 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,CsfbToGsmWcdma=1 featureStateCsfbToGsmWcdma 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Drx=1 featureStateDrx 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,EcsCsfb=1 featureStateEcsCsfb 0 (DEACTIVATED)
Licensing=1,OptionalFeatures=1,Ul16Qam=1 featureStateUl16Qam 1 (ACTIVATED)
IpSec=1 featureState 0 (DEACTIVATED)
=========================================================================================
Total: 37 MOs
Check Feature (Major functions)
Status check command to see if Feature(major functions) are
ACTIVATED or DEACTIVATED
For example) Certain function
(ANR : Auto Neighbor
relation) is DEACTIVATED,
thus will not work.
When the function is
DEACTIVATED, it is impossible to
have MIMO configuration.
When the function is
DEACTIVATED, SIB5 doesn’t go
down.
20. Check Sync data
0 UNKNOWN_MODE
1 STARTUP_MODE
The system clock is starting up.
2 LOCKED_MODE
The system clock signal on the Timing Unit is locked: a synchronization
reference is used to generate the system clock, the clock accuracy is 50 ppb
or better.
3 HOLD_OVER_MODE
The system clock signal on the Timing Unit has holdover quality: no
synchronization reference is used to generate the system clock, the clock
accuracy is 50 ppb or better.
4 FREE_RUNNING_MODE
The system clock signal on the Timing Unit is free-running: no
synchronization reference is used to generate the system clock, the clock
accuracy is 4.6 ppm or better.
5 FAILED_MODE
The system clock signal on the Timing Unit is failed: there is fault in
generating the system clock, no guarantee of clock accuracy level.
6 LOSS_OF_TRACKING_MODE
The frequency of the system clock is at its upper or lower limit.
7 NOT_APPLICABLE
The system clock signal on Timing Unit is not applicable: the TUB or the CBU
is not present.
0 FAILED
Synchronization reference cannot perform its required tasks.
1 DEGRADED
Capability of the synchronization reference to perform its required tasks is
degraded, for example, because of high bit error rate. This value is applicable
only for synchronization references that carry traffic, that is, for ET physical
path terminations.
2 LOSS_OF_TRACKING
The algorithm for system clock regulation cannot follow the synchronization
reference signal either because of the poor quality of the signal or because of
a HW fault.
3 OK
Synchronization reference is capable of performing its required tasks.
4 REF_PATH_FAILED_A
Synchronization reference cannot be distributed on plane A.
5 REF_PATH_FAILED_B
Synchronization reference cannot be distributed on plane B.
6 NOT_RELIABLE
No NTP packets are received from the server. This value is only used for IP
synchronization references.
7 LOW_QUALITY
The time stamp packets received from the NTP server are not reliable and the
synchronization algorithm cannot lock to IP reference. This value is only used
for IP synchronization references.
0 NO_STATUS
No other availability status for this resource is currently present.
1 IN_TEST
The resource is undergoing a test procedure. Tests that do not exclude additional users can be present in any operational sta te or administrative state.
2 FAILED
The resource has an internal fault that prevents it from operating. The operational state is disabled.
4 POWER_OFF
The resource requires power to be applied and is not powered on. The operational state is disabled.
8 OFF_LINE
The resource requires a routine operation to be performed to place it online and make it available for use. The operation may be manual, automatic, or both. The
operational state is disabled or enabled.
16 OFF_DUTY
The resource has been made inactive by some internal control process in accordance with a predetermined time schedule. Under normal conditions the control process
can be expected to reactivate the resource at some scheduled time, and it is therefore considered to be optional. The operational state is enabled or disabled.
64 DEGRADED
The service available from the resource is degraded in some respect, such as in speed or operating capacity. However, the res ource remains available for service, either
because some services are satisfactory or because degraded service is preferable to no service at all. The operational state is enabled.
128 NOT_INSTALLED
The resource represented by the managed object is not present, or is incomplete. For example, a plug-in unit is missing, a cable is disconnected, or a software module is
not loaded. The operational state is disabled.
256 LOG_FULL
This indicates a log full condition. Currently not used.
544 DEPENDENCY_LOCKED
The administrative state of a resource that this resource depends on is locked or the availability status of the other resour ce is dependency locked. The operational state is
disabled.
1056 DEPENDENCY_FAILED
The availability status of a resource that this resource depends on is failed or dependency failed. The operational state is disabled.
2080 DEPENDENCY_SHUTTINGDOWN
The administrative state of a resource that this resource depends on is shutting down or the availability status of the other resource is dependency shutting down. The
operational state is disabled.
21. ENB02> get . ntp
110323-19:34:48 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/884
=============================================================================================
MO Attribute Value
=============================================================================================
ManagedElementData=1 ntpBurstFlagPrimary true
ManagedElementData=1 ntpBurstFlagSecondary false
ManagedElementData=1 ntpBurstFlagThird false
ManagedElementData=1 ntpMaxPollPrimary 1024
ManagedElementData=1 ntpMaxPollSecondary 1024
ManagedElementData=1 ntpMaxPollThird 1024
ManagedElementData=1 ntpMinPollPrimary 16
ManagedElementData=1 ntpMinPollSecondary 64
ManagedElementData=1 ntpMinPollThird 64
ManagedElementData=1 ntpServerAddressPrimary 10.0.0.19
ManagedElementData=1 ntpServerAddressSecondary 0.0.0.0
ManagedElementData=1 ntpServerAddressThird 0.0.0.0
ManagedElementData=1 ntpServiceActivePrimary true
ManagedElementData=1 ntpServiceActiveSecondary false
ManagedElementData=1 ntpServiceActiveThird false
IpAccessHostEt=1 ntpDscp 46
IpAccessHostEt=1 ntpServerMode 0 (DISABLED)
IpAccessHostEt=1,IpSyncRef=1 ntpServerIpAddress 172.30.108.217
EUtranCellFDD=21,UeMeasControl=1 measurementPriority 0 (ANR_PRIO)
EUtranCellFDD=21,UeMeasControl=1,ReportConfigEUtraIntraFreqPm=1 reportAmountPm 0
EUtranCellFDD=22,UeMeasControl=1 measurementPriority 0 (ANR_PRIO)
EUtranCellFDD=23,UeMeasControl=1 measurementPriority 1 (PM_PRIO)
EUtranCellFDD=23,UeMeasControl=1,ReportConfigEUtraIntraFreqPm=1 reportAmountPm 0
==============================================================================================
Total: 8 MOs
Check NTP (Synchronization Server)
Have StatisticsData
based on the server
Sync clock based on
the server
22. ENB04> get 1
110323-16:49:20 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/1000
============================================================================
1 ManagedElementData=1
============================================================================
ManagedElementDataId 1
autoConfigurationAllowed true
autoConfigurationStatus 0 (IDLE)
daylightSavingTime false
docLibSystemDefined
docLibUserDefined
documentServerAddress
hdVolumeCFreespace 658620416
hdVolumeCSize 1203199488
logonServerAddress
minimumHdVolumeCFreespace 200
nodeLocalTimeZone GMT
nodeUTCTime 1300866547000
nodeUniqueID
ntpBurstFlagPrimary true
ntpBurstFlagSecondary false
ntpBurstFlagThird false
ntpMaxPollPrimary 1024
ntpMaxPollSecondary 1024
ntpMaxPollThird 1024
ntpMinPollPrimary 16
ntpMinPollSecondary 64
ntpMinPollThird 64
ntpServerAddressPrimary 10.0.0.19
ntpServerAddressSecondary 0.0.0.0
ntpServerAddressThird 0.0.0.0
ntpServiceActivePrimary true
ntpServiceActiveSecondary false
ntpServiceActiveThird false
piuGroupEscalationType 4 (WARM_AT_PIU_RESTART)
swServerUrlList
===========================================================================
Total: 1 MOs
ENB04> readclock
110323-16:49:25 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/1000
$ readclock
Date: 2011-03-23 UTC Time: 07:49:12. Wednesday
Check time
Laptop time (2011.03.22 16:49:25)
Check time Data
eNB time (2011.03.23 07:49:12)
JST, KST Standard
time
ENB02> ntpconfig info
110323-18:23:31 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/508
$ ntpconfig info
Primary server: 10.0.0.19
No secondary server found
No tertiary server found
NTP synchronized 2011-03-23 08:48:59
NTP changed server 2011-03-23 08:32:11 10.0.0.19
NTP clock stepped 2011-03-23 08:31:51 2011-03-23 08:31:51.127->2011-03-23 08:31:51.129 (src 10.0.0.19
$
23. ENB02> ue print -admitted
110329-17:03:42 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3224
$ ue print -admitted
CellId #UE:s #Bearers
31 2 2
32 2 2
33 1 1
Check how many calls were made
By default, when there is a call in UE 1,
Bearers display 1 as well.
Command to check how many calls are in
operation
ENB03> ue print -ue -allcell
110329-17:02:46 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3224
$ ue print -ue -allcell
CellId RacUeRef BbUeRef {traceRef,interfaces,traceDepth,ipAddress} TypeOfActiveTrace SetByColi CTSess
31 20 520100256 X CRUT false 43711
31 23 520100416 X CRUT false 43714
32 17 536877568 X CRUT false 21863
32 19 536877728 X CRUT false 21865
33 169 553654880 X CRUT false 170
$ /home/Administrator/moshell/commonjars/connect: connection timed out
$
24. ENB02> appsh oper
110329-16:58:33 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3224
Please enter Node Password:
$ appsh oper
egr_sid: ipIf | host | ipDA | dstPort | status
None found
0 UDP sessions in operational
egr_sid: laid | ipDA | teid | status
18 : 0 | 4.3.0.148 | 2487747802 | ok
21 : 0 | 4.2.0.150 | 3235900547 | ok
22 : 0 | 4.2.0.150 | 3620931837 | ok
23 : 0 | 4.2.0.150 | 988112966 | ok
24 : 0 | 4.2.0.150 | 2032833662 | ok
5 GTP sessions in operational
$
ENB02> appsh data 6
110318-20:05:42 10.0.0.163 8.0s ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/5752
$ appsh data 6
appsh data <{udp|gtp}> <sid>
ENB02> appsh data gtp 21
110318-20:06:15 10.0.0.163 8.0s ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/5752
$ appsh data gtp 4
ipInterfaceIndex = 0
hostIndex = 1
ipInterfaceIndex_old = 7
hostIndex_old = 31
remoteIpAddress = 4.2.0.150
receiveTEID = 1671200888
dscp = 20
clientInternalSwitchAddress = 02:00:01:03:00:03
serverInternalSwitchAddress = 02:00:01:02:00:03
internalVLANID = 10
sessionId = 4
ENB02> appsh data gtp 22
110318-20:06:47 10.0.0.163 8.0s ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/5752
$ appsh data gtp 5
ipInterfaceIndex = 0
hostIndex = 1
ipInterfaceIndex_old = 7
hostIndex_old = 31
remoteIpAddress = 4.2.0.150
receiveTEID = 615576315
dscp = 46
clientInternalSwitchAddress = 02:00:01:03:00:03
serverInternalSwitchAddress = 02:00:01:02:00:03
internalVLANID = 10
sessionId = 5
How to check bearer information
Check TEID in S1 side to distinguish default /
dedicated bearer
25. ENB02> get . term
110323-11:00:58 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/3220
=================================================================================================================
MO Attribute Value
=================================================================================================================
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1 ExchangeTerminalIpId 1
TermPointToMme=LGERMME02 TermPointToMmeId LGERMME02
EUtraNetwork=1,ExternalENodeBFunction=4506-3,TermPointToENB=4506-3 TermPointToENBId 4506-3
EUtraNetwork=1,ExternalENodeBFunction=4506-4,TermPointToENB=4506-4 TermPointToENBId 4506-4
TermPointToMme=Samsung2 TermPointToMmeId Samsung2
TermPointToMme=LGERMME01 TermPointToMmeId LGERMME01
TermPointToMme=Samsung1 TermPointToMmeId Samsung1
=================================================================================================================
Total: 7 MOs
ENB02> get . relation
110323-11:01:07 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/3220
=================================================================================================================
MO Attribute Value
=================================================================================================================
EUtranCellFDD=22,EUtranFreqRelation=3 EUtranFreqRelationId 3
=================================================================================================================
Total: 1 Mos
ENB02> get . external
110323-11:00:53 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/3220
=================================================================================================================
MO Attribute Value
=================================================================================================================
HwUnit=SCU,AlarmPort=14 activeExternalAlarm false
HwUnit=SCU,AlarmPort=7 activeExternalAlarm false
HwUnit=SCU,AlarmPort=11 activeExternalAlarm false
EUtraNetwork=1,ExternalENodeBFunction=4506-3 ExternalENodeBFunctionId 4506-3
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-31 ExternalEUtranCellFDDId 4506-3-31
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-32 ExternalEUtranCellFDDId 4506-3-32
EUtraNetwork=1,ExternalENodeBFunction=4506-3,ExternalEUtranCellFDD=4506-3-33 ExternalEUtranCellFDDId 4506-3-33
EUtraNetwork=1,ExternalENodeBFunction=4506-4 ExternalENodeBFunctionId 4506-4
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-41 ExternalEUtranCellFDDId 4506-4-41
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-42 ExternalEUtranCellFDDId 4506-4-42
EUtraNetwork=1,ExternalENodeBFunction=4506-4,ExternalEUtranCellFDD=4506-4-43 ExternalEUtranCellFDDId 4506-4-43
=================================================================================================================
Total: 24 MOs
Handover
Inter eNB connection information for X2
Handover
Inter cell information for X2 Handover
eNB information for Handover
26. ENB02> get . ipaddress
110322-22:15:54 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/4500
==========================================================================================
MO Attribute Value
==========================================================================================
Security=1 aAServerIPAddressList s[0] =
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1 ownIpAddressActive 0.0.0.0
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1 ownIpAddressPassive 0.0.0.0
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=2 ownIpAddressActive 10.0.0.163
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=2 ownIpAddressPassive 0.0.0.0
UpgradePackage=R20HN ftpServerIpAddress 192.168.10.10
UpgradePackage=InitialUP ftpServerIpAddress FTP_ServerIP_Address
UpgradePackage=CXP102051/10_R9BE/2 ftpServerIpAddress 10.0.0.36
UpgradePackage=R9AS ftpServerIpAddress 169.254.1.11
UpgradePackage=R7AK ftpServerIpAddress 169.254.1.11
Ip=1 nodeIpAddress 10.0.0.163
Ip=1,EthernetLink=1 ipAddress 169.254.1.10
Ip=1,IpHostLink=1 ipAddress 10.0.0.163
IpAccessHostEt=1 ipAddress 4.2.0.18
IpAccessHostEt=1,IpSyncRef=1 cachedIpAddress
IpAccessHostEt=1,IpSyncRef=1 ntpServerIpAddress 172.30.108.217
TermPointToMme=LGERMME02 ipAddress1 4.2.0.140
TermPointToMme=LGERMME02 ipAddress2 0.0.0.0
TermPointToMme=LGERMME02 usedIpAddress 0.0.0.0
EUtraNetwork=1,ExternalENodeBFunction=4506-3,TermPointToENB=4506-3 ipAddress 4.2.0.34
EUtraNetwork=1,ExternalENodeBFunction=4506-3,TermPointToENB=4506-3 usedIpAddress 0.0.0.0
EUtraNetwork=1,ExternalENodeBFunction=4506-4,TermPointToENB=4506-4 ipAddress 4.2.0.50
EUtraNetwork=1,ExternalENodeBFunction=4506-4,TermPointToENB=4506-4 usedIpAddress 0.0.0.0
TermPointToMme=Samsung2 ipAddress1 4.3.0.140
TermPointToMme=Samsung2 ipAddress2 0.0.0.0
TermPointToMme=Samsung2 usedIpAddress 0.0.0.0
TermPointToMme=LGERMME01 ipAddress1 4.2.0.132
TermPointToMme=LGERMME01 ipAddress2 0.0.0.0
TermPointToMme=LGERMME01 usedIpAddress 0.0.0.0
TermPointToMme=Samsung1 ipAddress1 4.3.0.132
TermPointToMme=Samsung1 ipAddress2 0.0.0.0
TermPointToMme=Samsung1 usedIpAddress 4.3.0.132
===========================================================================================
Total: 19 Mos
10.0.0.164> get . vid
110330-18:00:18 10.0.0.164 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/6012
===========================================================================================
MO Attribute Value
===========================================================================================
Subrack=1,Slot=1,PlugInUnit=1,ExchangeTerminalIp=1,GigaBitEthernet=1,IpInterface=1 vid 900
===========================================================================================
Total: 1 MOs
Check IP Address, v-LAN id
Check station IP address
Check MME IP address
Check O&M IP address
27. Checklist in case of failure
ENB03> cabr
110329-15:05:39 10.0.0.163 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/3652
====================================================================================================
Pos Date and Time Domain OS Process Errorcode Cause (PMD ID)
====================================================================================================
0001 00-00-00 00:00:00 Processor BASIC 0x00000003 Error log was cleared at last restart. Power on restart
0001 11-03-28 01:26:04 Processor BASIC Cs_boardManager_proc 0xB0AD0002 Board manager restart. Restart ordered by system manager
0001 11-03-28 01:26:12 Processor BASIC bmLoaderClientHelper 0xB0AD0001 Board manager restart. Mismatch of files in flash, goto backup
0001 11-03-28 01:26:48 Processor BACKUP bmLoaderClientHelper 0xB0AD0001 Board manager restart. Reset after backupmode
0001 11-03-28 01:27:40 Processor BASIC Cs_boardManager_proc 0xB0AD0006 Board manager restart. Restart ordered by system manager
---------------------------------------------------------------------------------------------------------------
ENB02> caba
110329-15:05:51 10.0.0.163 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/3652
=====================================================================================================
Pos Date and Time Domain OS Process Errorcode Cause (PMD ID)
=====================================================================================================
0001 00-00-00 00:00:00 Processor BASIC 0x00000003 Error log was cleared at last restart. Power on restart
---------------------------------------------------------------------------------------------------------------
$
28. Check VSWR
ENB01> cabx
============================================================================================================
====================
SMN APN PORT BOARD GREEN YELLOW RED PRODUCT NR REV DATE SERIAL NR
============================================================================================================
====================
0 1 BXP_0_1 RUS01B5 steady 16hz off KRC11864/2 R1C 20100923 C823763459
0 1 BXP_3_1 RUS01B5 steady 16hz off KRC11864/2 R1C 20101103 C823863797
--------------------------------------------------------------------------------------------------------------------------------
ENB01> lhsh BXP_4_1 fui get vswr
110110-18:33:56 10.0.0.162 8.0n ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/5096
$ lhsh BXP_3_1 fui get vswr
vswr: 28.5[dB]
ENB01> cabx
===============================================================================================
SMN APN PORT BOARD GREEN YELLOW RED PRODUCT NR REV DATE SERIAL NR
===============================================================================================
0 1 BXP_0_1 RUS01B5 steady 16hz off KRC11864/2 R1C 20100923 C823763459
0 1 BXP_3_1 RUS01B5 steady 16hz off KRC11864/2 R1C 20101103 C823863797
--------------------------------------------------------------------------------------------------------------------------------
ENB01> lhsh BXP_3_1 fui get vswr
110110-18:33:56 10.0.0.162 8.0n ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/5096
$ lhsh BXP_3_1 fui get vswr
vswr: 28.5[dB]
ntpServerIpAddress 172.30.108.217
Check O&M IP address
29. Check current output
ENB02> cabx
110323-20:16:29 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2260
==============================================================================================
SMN APN PORT BOARD GREEN YELLOW RED PRODUCT NR REV DATE SERIAL NR
=============================================================================================
0 1 BXP_2_1 RUS01B5 steady off off KRC11864/2 R1C 20101103 C823863785
0 1 BXP_5_1 RUS01B5 steady off off KRC11864/2 R1C 20100913 C823738900
--------------------------------------------------------------------------------------------------------------------------------
ENB02> lhsh BXP_2_1 warpA read DL_PM_PA0_C0
110323-20:17:07 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2260
$ lhsh BXP_2_1 warpA read DL_PM_PA0_C0
Value 0x002DE4FF (3007743) read from address 0x00000B8F.
$
ENB02> lhsh BXP_2_1 warpA read DL_PM_PA0_C1
110323-20:17:31 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2260
$ lhsh BXP_2_1 warpA read DL_PM_PA0_C1
Value 0x003BB172 (3912050) read from address 0x00000B90.
$
ENB02> lhsh BXP_2_1 warpA read DL_PM_PA0_C2
110323-20:17:38 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2260
$ lhsh BXP_2_1 warpA read DL_PM_PA0_C2
Value 0x003888B1 (3705009) read from address 0x00000B91.
$
ENB02> lhsh BXP_2_1 warpA read DL_PM_PA0_C3
110323-20:17:44 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/2260
$ lhsh BXP_2_1 warpA read DL_PM_PA0_C3
Value 0x002E0F80 (3018624) read from address 0x00000B92.
If there is a value here, you
can see there is TX output.
Provide accurate output value
a. p_c0 = p_reg_c0*(2^14)/(15*81920) = p_reg_c0 * 16384 / 1228800
b. p_c1 = p_reg_c1*(2^14)/(15*81920) = p_reg_c1 * 16384 / 1228800
c. p_c2 = p_reg_c2*(2^14)/(15*81920) = p_reg_c2 * 16384 / 1228800
d. p_c3 = p_reg_c3*(2^14)/(15*81920) = p_reg_c3 * 16384 / 1228800
Total = p_c0 + p_c1 + p_c2 + p_c3
(Total / 2914^2) * 60 W
30. Check output target
How to change station output
ENB03> get . power
ENB03> set EUtranCellFDD=43 partOfRadioPower 20 ( Command that modify from 60% of 43.7dBm to 20%.
ENB03> st cell
ENB03> bl cell
ENB03> deb cell
ENB04> get . power
110323-15:17:48 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/1800
============================================================================================
MO Attribute Value
============================================================================================
Licensing=1,CapacityLicenses=1,CapacityOutputPower=60Watt CapacityOutputPowerId 60Watt
Licensing=1,CapacityLicenses=1,CapacityOutputPower=60Watt capacityUnitOutputPower Number of 60 Watt Licenses
Licensing=1,CapacityLicenses=1,CapacityOutputPower=60Watt keyIdOutputPower CXC4010626
Licensing=1,CapacityLicenses=1,CapacityOutputPower=60Watt licenseCapacityOutputPower 6
Licensing=1,CapacityLicenses=1,CapacityOutputPower=60Watt licenseStateOutputPower 1 (ENABLED)
HwUnit=SAU powerDistrFaultIndicator 1 (NOT_AVAILABLE)
Subrack=1 maxPowerDissipation -1
Subrack=1 powerMeasurements Struct{5}
>>> 1.currentLeft = -1
>>> 2.currentRight = -1
>>> 3.distributedPower = 0
>>> 4.voltageLeft = -1
>>> 5.voltageRight = -1
HwUnit=PDU-1 powerDistrFaultIndicator 1 (NOT_AVAILABLE)
HwUnit=SCU powerDistrFaultIndicator 1 (NOT_AVAILABLE)
SubrackProdType=ROJ999999_* maxPowerDissipation 0
HwUnit=PDU-2 powerDistrFaultIndicator 1 (NOT_AVAILABLE)
EUtranCellFDD=43 maximumTransmissionPower 437
EUtranCellFDD=43 partOfRadioPower 60
EUtranCellFDD=43 partOfSectorPower 60
SectorEquipmentFunction=S2 confOutputPower 40
SectorEquipmentFunction=S2 sectorPower 0
PowerSupply=1 PowerSupplyId 1
PowerDistribution=1 PowerDistributionId 1
=============================================================================================
Total: 16 MOs
Use when you check
output value
31. ENB04> pr security
110321-23:23:42 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/5744
===================================================================================
Proxy MO
===================================================================================
57 SystemFunctions=1,Security=1
962 ENodeBFunction=1,SecurityHandling=1
===================================================================================
Total: 2 MOs
ENB04> get 962
110321-23:23:55 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40 stopfile=/tmp/5744
============================================================================================
962 ENodeBFunction=1,SecurityHandling=1
===========================================================================================
SecurityHandlingId 1
cipheringAlgorithms 14 (EEA0)
countWrapSupervisionActive true
integrityProtectionAlgorithms 8 (EIA2)
rbIdSupervisionActive false
============================================================================================
Total: 1 MOs
ENB04>
Check Security
Check whether Security should be used during handset
connection to RRC.
Enter get 962 (value confirmed in the above) to check detailed
information.
True: Use Security during RRC connection.
False: Do not use security during RRC connection.
32. ENB04> parsemom moshell/jarxml/
ERBS_NODE_MODEL_A_9_2.xml.cache.gz* ERBS_NODE_MODEL_B_1_30_COMPLETE.xml.gz* jacoms.jar*
ERBS_NODE_MODEL_A_9_2.xml.gz* ERBS_NODE_MODEL_B_1_40.xml.cache.gz jacorb.jar*
ERBS_NODE_MODEL_A_9_53.xml.cache.gz* ERBS_NODE_MODEL_B_1_40.xml.gz lmids.txt
ERBS_NODE_MODEL_A_9_53.xml.gz* ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.cache.gz* lmids.txt.old2.gz*
ERBS_NODE_MODEL_A_9_53_COMPLETE.xml.cache.gz ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.gz* moshellrc*
ERBS_NODE_MODEL_A_9_53_COMPLETE.xml.gz* MGW_R2.xml.cache.gz moshellrc.bak*
ERBS_NODE_MODEL_B_1_30.xml.cache.gz MGW_R2.xml.gz* updata.txt*
ERBS_NODE_MODEL_B_1_30.xml.gz cppdata.txt uptomom.txt
ERBS_NODE_MODEL_B_1_30_COMPLETE.xml.cache.gz* event/
ENB04> parsemom moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.gz
Parsing MOM: moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.gz .................................Done.
Caching MOM to: moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.cache .....Done.
Compressing to: moshell/jarxml/ERBS_NODE_MODEL_B_1_40_COMPLETE.xml.cache.gz ...Done.
Using paramfile /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt
Parsing file /home/Administrator/moshell/commonjars/pm/PARAM_ERBS_B_1_0.txt ............................................................................Done.
ENB04> get systemc
110323-20:59:05 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/356
=================================================================================================
964 ENodeBFunction=1,SystemConstants=1
=================================================================================================
SystemConstantsId 1
systConstants 38:0,125:3,204:100,213:200,242:1,70:90,73:86,195:10,27:-20,256:0,258:0,229:19600
=================================================================================================
1036 SupportSystemConfiguration=1
==================================================================================================
SupportSystemConfigurationId 1
==================================================================================================
Total: 2 MOs
ENB04>
Check System constant ※ don’t open to customer
1. Put Complete mom file in C:cygwinhomeAdministratormoshelljarxml.
2. Enter command ( parsemom moshell/jarxml/ ) and select tab key to display Complete mom in the folder.
3. Drag and paste, then select Enter.
4. Able to check system constant status at the time of entering get systemc.
Complete mom is changed at the time of version upgrade,
and it needs constant upgrade.
33. SISO/SIMO:
Set system constant value as 125:1
Set Tx Ant number as 1
EUtranCellFDD=21 noOfTxAntennas 1
EUtranCellFDD=21 noOfRxAntennas 1
Transmit Diversity
Set system constant value as 125:2
Set Tx Ant number as 2
EUtranCellFDD=21 noOfTxAntennas 2
EUtranCellFDD=21 noOfRxAntennas 2
Configure Licensing=1,OptionalFeatures=1,DualAntDlPerfPkg=1 featureStateDualAntDlPerfPkg 1 (ACTIVATED) //DualAntDlPerfPkg License Enable
SM
Set system constant value as 125:3 // Operate as Transmit Diversity or SM(Large CDD), according to channel environment
Set Tx Ant number as 2
EUtranCellFDD=21 noOfTxAntennas 2
EUtranCellFDD=21 noOfRxAntennas 2
Configure Licensing=1,OptionalFeatures=1,DualAntDlPerfPkg=1 featureStateDualAntDlPerfPkg 1 (ACTIVATED) //DualAntDlPerfPkg License Enable
TM(Transmission mode) check and set ANT
number ENB02> get systemc
110324-11:45:26 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/620
============================================================================
1102 ENodeBFunction=1,SystemConstants=1
============================================================================
SystemConstantsId 1
systConstants 38:0,125:3,204:100,213:200,242:1,70:90,73:86,195:10,27:-20,256:0,258:0,229:19600
============================================================================
1166 SupportSystemConfiguration=1
============================================================================
SupportSystemConfigurationId 1
============================================================================
Total: 2 Mos
eNB3> get . antenna
110331-16:00:11 169.254.1.10 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/2392
==============================================================================
MO Attribute Value
==============================================================================
AntennaUnitGroup=1 AntennaUnitGroupId 1
AntennaUnitGroup=1,AntennaUnit=1 AntennaUnitId 1
AntennaUnitGroup=1,AntennaUnit=1 mechanicalAntennaTilt 0
EUtranCellFDD=31 noOfRxAntennas 2
EUtranCellFDD=31 noOfTxAntennas 2
EUtranCellFDD=31 noOfUsedTxAntennas 2
=============================================================================
Total: 3 MOs
ENB02> get . nooftx
110324-11:46:07 10.0.0.163 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/620
=============================================================================
MO Attribute Value
=============================================================================
EUtranCellFDD=21 noOfTxAntennas 1
EUtranCellFDD=22 noOfTxAntennas 1
EUtranCellFDD=23 noOfTxAntennas 1
=============================================================================
Total: 3 MOs
TM (Transmission Mode) : Set transmission
mode.
3: MIMO
2: SIMO
1: SISO
Numbur of TX ANT is currently 1
To check RX ANT number: get . noofrx
34. ENB04> get systemc
110402-20:51:30 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_50_COMPLETE stopfile=/tmp/5756
======================================================================================================
746 ENodeBFunction=1,SystemConstants=1
======================================================================================================
SystemConstantsId 1
systConstants
======================================================================================================
776 SupportSystemConfiguration=1
======================================================================================================
SupportSystemConfigurationId 1
======================================================================================================
Total: 2 MOs
ENB04> acl systemc
110402-20:51:36 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_50_COMPLETE stopfile=/tmp/5756
======================================================================================================
Proxy MO Action Nr of Params
======================================================================================================
746 SystemConstants=1 resetSystConst 1
746 SystemConstants=1 writeSystConst 2
776 SupportSystemConfiguration=1 configureSupportSystem 1
======================================================================================================
ENB04> acc 746 writeSystConst
110402-20:51:42 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_50_COMPLETE stopfile=/tmp/5756
Call Action writesystconst on following 1 MOs ?
===================================================================================
746 ENodeBFunction=1,SystemConstants=1
===================================================================================
Call action writesystconst on 1 MOs. Are you Sure [y/n] ? y
======================================================================================================
Proxy MO Action Nr of Params
======================================================================================================
746 SystemConstants=1 writeSystConst 2
Parameter 1 of 2, name (string): 125
Parameter 2 of 2, value (string): 3
>>> Return value = null
======================================================================================================
Total: 1 MOs attempted, 1 MOs actioned
TM(Transmission mode)
Check and set ANT
number
35. ENB04> pr anr
110324-14:14:53 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/640
===================================================================================
Proxy MO
===================================================================================
29 SystemFunctions=1,Licensing=1,OptionalFeatures=1,Anr=1
973 ENodeBFunction=1,EUtranCellFDD=41,UeMeasControl=1,ReportConfigEUtraBestCell=1,ReportConfigEUtraBestCellAnr=1
978 ENodeBFunction=1,EUtranCellFDD=41,UeMeasControl=1,ReportConfigA5=1,ReportConfigA5Anr=1
996 ENodeBFunction=1,EUtranCellFDD=43,UeMeasControl=1,ReportConfigEUtraBestCell=1,ReportConfigEUtraBestCellAnr=1
1003 ENodeBFunction=1,EUtranCellFDD=43,UeMeasControl=1,ReportConfigA5=1,ReportConfigA5Anr=1
1006 ENodeBFunction=1,AnrFunction=1
1007 ENodeBFunction=1,AnrFunction=1,AnrFunctionGeran=1
1008 ENodeBFunction=1,AnrFunction=1,AnrFunctionUtran=1
1009 ENodeBFunction=1,AnrFunction=1,AnrFunctionEUtran=1
1014 ENodeBFunction=1,EUtranCellFDD=42,UeMeasControl=1,ReportConfigEUtraBestCell=1,ReportConfigEUtraBestCellAnr=1
1022 ENodeBFunction=1,EUtranCellFDD=42,UeMeasControl=1,ReportConfigA5=1,ReportConfigA5Anr=1
===================================================================================
Total: 11 MOs
ENB04> get ENodeBFunction=1,AnrFunction=1,AnrFunctionEUtran=1
110324-14:15:54 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/640
=================================================================================================================
1009 ENodeBFunction=1,AnrFunction=1,AnrFunctionEUtran=1
=================================================================================================================
AnrFunctionEUtranId 1
anrInterFreqState 0 (DEACTIVATED)
anrIntraFreqState 1 (ACTIVATED)
anrUesEUtraIntraFDecr 10
anrUesEUtraIntraFIncrAnr 20
anrUesEUtraIntraFIncrHo 100
anrUesEUtraIntraFMax 20
anrUesEUtraIntraFMin 1
anrUesThreshInterFDecr 10
anrUesThreshInterFIncrAnr 20
anrUesThreshInterFIncrHo 100
anrUesThreshInterFMax 20
anrUesThreshInterFMin 1
cellAddRsrpThresholdEutran -1440
cellAddRsrqThresholdEutran -1920
hoAllowedEutranPolicy true
x2SetupPolicy true
=================================================================================================================
Total: 1 MOs
ENB04> mom . cellAddRsrpThresholdEutran
110324-14:16:58 10.0.0.165 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/640
####################################################################################################################################
MO Class Attribute Type Flags
####################################################################################################################################
AnrFunction cellAddRsrpThresholdEutran long deprecated
------------------------------------------------------------------------------------------------------------------------------------
Deprecated: Since L11B. Replaced by AnrFunctionEUtran::cellAddRsrpThresholdEutran.
Threshold value for reported power for a cell to be automatically added as neighbor.
Takes effects: Immediately.
Unit: 0.1 dBm
Resolution: -
Range: -1440 to 0, Default=-1440
************************************************************************************************************************************
AnrFunctionEUtran cellAddRsrpThresholdEutran long
------------------------------------------------------------------------------------------------------------------------------------
Threshold value for reported power for a cell to be automatically added as neighbor.
Takes effects: Immediately.
Unit: 0.1 dBm
Resolution: -
Range: -1440 to 0, Default=-1440
************************************************************************************************************************************
Configure
ANR
36. Manage and apply License
ENB03> license server
110326-11:56:09 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/896
$ license server
License Server : 000101d4
Latest PV : 3
License Key File : Installed, Mon Mar 14 14:19:58 2011
Sequence Number : 1008
Node Identity State : 1
Unique Logical Name : eNB3
Validation Start : Sat Mar 26 13:17:56 2011
Validation Interval : 1 Day
Emergency Status : Deactivated
Emergency State : 2
Emergency Counter : 1
Emergency State Time : Tue Mar 8 09:56:59 2011
Emergency Time Limit : 7 Days
$ /home/Administrator/moshell/commonjars/connect: connection timed out
$
ENB03> get . fingerprint
110330-18:53:37 10.0.0.164 8.0r ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/6012
=========================================================================
MO Attribute Value
=========================================================================
Licensing=1 fingerprint eNB3
=========================================================================
Total: 1 MOs
4.7.1 Problem Description
License keys are required in combination with any given enabled feature in order to allow full access to a feature.
The following Command Line Interface (COLI) command printouts must be taken from DUL if they are not already collected:
- license server (License Server details)
- license client (License Client details)
- License sub –a (Feature status information)
- license lkf (Status of license key file)
- license key (License key information)
All files in the /c/license/ directory must be transferred by FTP, binary mode, from the node.
Save the output in an attachment called “license_files.zip”
169.254.1.10> acc RbsConfiguration=1 setUniqueLogicalName
110307-19:21:26 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE
stopfile=/tmp/2748
Call Action setuniquelogicalname on following 1 MOs ?
================================================
776 ENodeBFunction=1,RbsConfiguration=1
================================================
Call action setuniquelogicalname on 1 MOs. Are you Sure [y/n] ? y
================================================
Proxy MO Action
Nr of Params
================================================
776 RbsConfiguration=1
setUniqueLogicalName 1
Parameter 1 of 1, uniqueLogicalName (string): eNB1
!!! Exception failure: org.omg.CORBA.COMM_FAILURE: vmcid: 0x0 minor
code: 0 completed: Maybe
>>> Return value = null
================================================
Total: 1 MOs attempted, 0 MOs actioned
How to enter Fingerprint
New Sequence Number
must be bigger than
existing value.
37. ENB03> acl 6
101224-13:55:39 10.0.0.165 8.0n ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/676
==========================================================================
Proxy MO Action Nr of Params
==========================================================================
6 Licensing=1 setEmergencyState 0
6 Licensing=1 updateLicenseKeyFile 4
==========================================================================
ENB04> acc 6 updateLicenseKeyFile
101224-14:08:46 10.0.0.165 8.0n ERBS_NODE_MODEL_A_9_53_COMPLETE stopfile=/tmp/676
Call Action updatelicensekeyfile on following 1 MOs ?
==========================================================================
6 SystemFunctions=1,Licensing=1
==========================================================================
Call action updatelicensekeyfile on 1 MOs. Are you Sure [y/n] ? y
==========================================================================
Proxy MO Action Nr of Params
==========================================================================
6 Licensing=1 updateLicenseKeyFile 4
Parameter 1 of 4, userId (string): lte
Parameter 2 of 4, password (string): lte
Parameter 3 of 4, ipAddress (string): 169.254.1.12
Parameter 4 of 4, sFile (string): eNB4_101224_004441.xml
>>> Return value = null
==========================================================================
Total: 1 MOs attempted, 1 MOs actioned
ENB02> inv
==========================================================================
Feature keyId licenseState featureState serviceState
description
==========================================================================
AgpsSupl=1 CXC4010963 1 (DISABLED) 0 (DEACTIVATED) 0 (INOPERABLE)
AirIfLoadGenerator=1 CXC4010955 1 (DISABLED) 0 (DEACTIVATED) 0 (INOPERABLE)
169.254.1.10> license lkf
110307-19:28:15 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_30_COMPLETE stopfile=/tmp/2748
$ license lkf
License Key File Status : 2 (LKF_ERROR)
Additional Info : Faulty fingerprint in the license key file.
$
1. Upload license file(.xml) to FTP
2. Enter nmsadm if file to OSS-RC’s UAS(10.0.0.19) (Use FTP,
ID ; nmsadm, PW: nms275)
2. Put the file into My Computer (169.254.1.12) (Use FTP, ID:
lte, pw: lte
3. Follow MOshell command procedure.
Manage and apply License
Check with these commands if there is
any error after applying License.
38. Check ping
ENB03> get . ipadd
110330-14:25:26 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3652
=====================================================================
MO Attribute Value
=====================================================================
UpgradePackage=R9AS ftpServerIpAddress 169.254.1.11
UpgradePackage=R9BE%2 ftpServerIpAddress 192.168.10.10
Ip=1 nodeIpAddress 10.0.0.164
Ip=1,EthernetLink=1 ipAddress 169.254.1.10
Ip=1,IpHostLink=1 ipAddress 10.0.0.164
IpAccessHostEt=1 ipAddress 4.2.0.34
IpAccessHostEt=1,IpSyncRef=1 cachedIpAddress
IpAccessHostEt=1,IpSyncRef=1 ntpServerIpAddress 172.30.108.217
ENodeBFunction=1 ipAddress 4.2.0.34
ENodeBFunction=1 x2IpAddrViaS1Active true
TermPointToMme=LGERMME02 ipAddress1 4.2.0.140
TermPointToMme=LGERMME02 ipAddress2 0.0.0.0
TermPointToMme=LGERMME02 usedIpAddress 4.2.0.140
EUtraNetwork=1,ExternalENodeBFunction=ENB02,TermPointToENB=ENB02 ipAddress 4.2.0.18
EUtraNetwork=1,ExternalENodeBFunction=ENB02,TermPointToENB=ENB02 usedIpAddress
TermPointToMme=LGERMME01 ipAddress1 4.2.0.132
TermPointToMme=LGERMME01 ipAddress2 0.0.0.0
TermPointToMme=LGERMME01 usedIpAddress 0.0.0.0
=====================================================================
Total: 20 MOs
ENB03> acc IpAccessHostEt ping
110330-14:25:44 10.0.0.164 8.0r ERBS_NODE_MODEL_B_1_40_COMPLETE stopfile=/tmp/3652
Call Action ping on following 1 MOs ?
=====================================================================
721 IpSystem=1,IpAccessHostEt=1
=====================================================================
Call action ping on 1 MOs. Are you Sure [y/n] ? y
=====================================================================
Proxy MO Action Nr of Params
=====================================================================
721 IpAccessHostEt=1 ping 1
Parameter 1 of 1, host (string): 4.2.0.35
>>> Return value = 4.2.0.35 no answer
======================================================================
Total: 1 MOs attempted, 1 MOs actioned
When ping comes back normally:
Parameter 1 of 1, host (string): 4.3.0.18
>>> Return value = 4.3.0.18 is alive
ENB03> acc ipoam ping
110407-15:17:35 169.254.1.10 8.0r ERBS_NODE_MODEL_B_1_50_COMPLETE stopfile=/tmp/3892
Call Action ping on following 1 MOs ?
================================================================
662 IpOam=1
================================================================
Call action ping on 1 MOs. Are you Sure [y/n] ? y
=================================================================
Proxy MO Action Nr of Params
===================================================================
662 IpOam=1 ping 1
Parameter 1 of 1, host (string): 10.0.0.19
>>> Return value = no answer from * / 10.0.0.19
===================================================================
Total: 1 MOs attempted, 1 MOs actioned