This document contains commands and instructions for monitoring and troubleshooting various network elements including BTS, BSC, MSC, routes, alarms, and more. It includes commands to:
1. Check the status of BTS sites, cells, traffic levels, alarms and reset or restart sites.
2. Monitor routes between network elements, block or unblock routes, and check the status of route blocking supervision.
3. Check the status of various core network elements like C7 links, STM lines, DIPs, and alarms on BSC, MSC.
4. Monitor alarms related to power supply, synchronization, size alteration and restart processes to resolve issues.
This document provides commands to check alarms, monitor radio equipment status, configure cells and frequencies, upgrade sectors, and change cell parameters in a mobile network. It includes commands to check major, critical, and minor alarms, print radio equipment status, check and configure frequencies and channels in cells, upgrade sectors by configuring transceivers and antennas, and change cell identifiers and frequencies.
To remove an RBS, the document outlines the following steps:
1. Delete the AAL2 routing case MO in the RXI using the proxy and AAL2 routing case identifier.
2. Delete the UniSAAL TP MOs in the RXI.
3. Delete the AAL5 TP VCC TP MOs in the RXI.
4. Delete the VC MOs in the RXI to remove the VC links.
5. Delete the main .b MO in the RXI to remove the remaining RBS objects.
This document provides an overview of techniques for troubleshooting LTE throughput problems. It discusses isolating throughput issues to the radio, transport, or end-to-end domains. The agenda includes initial checks of network changes, UE capabilities, and RBS parameters. Radio analysis examines the baseband scheduler traces and signal traces between blocks to identify issues. Transport analysis evaluates network infrastructure. End-to-end analysis looks at the entire path from UE to application server. The goal is to pinpoint the root cause of throughput degradation within each domain using theory, traces, and examples.
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 provides commands to check various components and statuses in RNC and Node B equipment. Some examples include checking site status in RNC, E1 status and errors in Node B, Iub status of a site, alarms in RNC and Node B, hardware status in Node B, license status in Node B, and more. Instructions are given on using commands like lt, st, pget, altk, and others.
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.
This document contains commands for configuring and monitoring a BSC and its associated cells. It includes commands to:
1. Check status and configuration of cells, TRXs, channels, frequencies and other network elements; make changes to parameters like power levels, thresholds and cell configurations.
2. Add, modify and delete network resources like TRXs, channels, frequencies and cell configurations.
3. Block, unblock and manage the state of network elements for maintenance activities.
This document provides commands to check alarms, monitor radio equipment status, configure cells and frequencies, upgrade sectors, and change cell parameters in a mobile network. It includes commands to check major, critical, and minor alarms, print radio equipment status, check and configure frequencies and channels in cells, upgrade sectors by configuring transceivers and antennas, and change cell identifiers and frequencies.
To remove an RBS, the document outlines the following steps:
1. Delete the AAL2 routing case MO in the RXI using the proxy and AAL2 routing case identifier.
2. Delete the UniSAAL TP MOs in the RXI.
3. Delete the AAL5 TP VCC TP MOs in the RXI.
4. Delete the VC MOs in the RXI to remove the VC links.
5. Delete the main .b MO in the RXI to remove the remaining RBS objects.
This document provides an overview of techniques for troubleshooting LTE throughput problems. It discusses isolating throughput issues to the radio, transport, or end-to-end domains. The agenda includes initial checks of network changes, UE capabilities, and RBS parameters. Radio analysis examines the baseband scheduler traces and signal traces between blocks to identify issues. Transport analysis evaluates network infrastructure. End-to-end analysis looks at the entire path from UE to application server. The goal is to pinpoint the root cause of throughput degradation within each domain using theory, traces, and examples.
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 provides commands to check various components and statuses in RNC and Node B equipment. Some examples include checking site status in RNC, E1 status and errors in Node B, Iub status of a site, alarms in RNC and Node B, hardware status in Node B, license status in Node B, and more. Instructions are given on using commands like lt, st, pget, altk, and others.
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.
This document contains commands for configuring and monitoring a BSC and its associated cells. It includes commands to:
1. Check status and configuration of cells, TRXs, channels, frequencies and other network elements; make changes to parameters like power levels, thresholds and cell configurations.
2. Add, modify and delete network resources like TRXs, channels, frequencies and cell configurations.
3. Block, unblock and manage the state of network elements for maintenance activities.
The document provides an overview and analysis flow for optimizing the performance of a mobile network. It discusses various problems that can occur like low availability of control channels, congestion on signaling and traffic channels, and high drop call rates. For each problem, it lists probable causes and recommends actions to identify the issue and solutions to resolve it, such as adjusting configuration parameters, adding network capacity, or improving frequency planning. MML commands are also provided to check device logs, resources, and performance statistics for troubleshooting purposes.
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.
The document outlines the 8 step process for configuring a Sprint 4G Cascaded RET including:
1) Creating pre and post configuration version snapshots
2) Validating the RET and antenna configuration
3) Running scripts to cascade the RETs for different antenna vendors
4) Populating unique IDs for each RET
5) Setting the tilt boundaries
6) Matching the 1900 CDMA RET tilts to the 1900 LTE tilts
7) Verifying the new RET configuration
8) Continuing integration and troubleshooting any issues.
This document contains a list of Ericsson commands used to manage various network elements like BSCs, MSCs, radios, cells, logical channels, and faults. Some key commands include:
1. "eaw CIRCLE+BSC" to enter BSC mode and manage BSC objects.
2. "allip:acl=a1" to check external alarms on the BSC.
3. "rxbli:mo=rxotrx-188-6,subord,force" to block a radio forcefully.
4. "rlstc:cell=no0088c,state=halted" to halt a cell.
5. "rx
The document discusses working with BSC nodes in ENM and provides the following key points:
- BSC node configuration is done through managed objects (MOs) below the BscM object which have non-standard behavior for create, update, and delete operations.
- There are limitations when making changes to BscM MOs including only allowing 100 operations per command and only one user making changes at a time.
- Commands on BscM MOs can partially succeed, with some attributes or objects succeeding and others failing. It is important to review any failed operations carefully.
This document provides an overview of GSM MSC/MSC-S R12 configuration. It discusses network architecture models including vertically and horizontally integrated networks. It describes the different network layers and nodes in GSM and WCDMA systems. These include the base station system, core network nodes like the MSC and SGSN. It also covers signaling protocols used in the core network like SS7, SIGTRAN, BICC and H.248. The document provides information on identities used in GSM and WCDMA networks like IMSI, MSISDN. It discusses addressing of switching system entities using global and mobile global titles. Finally, it introduces concepts related to MSC servers and media gateways.
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).
Ericsson technical interview questionssethshivam75
This document contains technical interview questions asked by Ericsson including:
1) Questions about how mobile phones work, handoffs in GSM networks, differences between TCP/IP and SSL, DNS lookups, TCP layers, converting decimal to binary, prime numbers, multiplexing, and modulation techniques.
2) A tip that ECE students interviewing at Ericsson should have programming skills.
3) Additional questions about waveguide propagation, Ethernet frame formats, STP/RSTP, VSWR, waveguides, the ALOHA protocol, information theory concepts, antenna properties, and GSM/CDMA comparisons.
It is a handbook of UMTS/WCDMA call flows for PS services.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
This document provides a commissioning procedure for an RBS 6201 2G system. It involves requirements for OMT and software versions, EC bus termination, pin configurations, defining sectors and parameters in the configuration wizard, shelf and slot positions, hub position, feeder loss, delay, PCM, ties, power configuration, and installing the IDB while changing the DUG maintenance state. The procedure guides configuring the 2G part of the 6201 and defines shelves, slots, and positions for DUG, RUG, and PDU units.
The document provides guidance on configuring remote electrical tilt (RET) in different scenarios. It describes RET introduction and support requirements. Configuration steps are outlined for single and multi-antenna RET devices controlled by the radio remote unit (RRU) or RET interface unit (RIU). The document also covers cascading RET configuration, where multiple RET units can be controlled by a single RRU.
The document provides a high-level summary and proposed strategy for mobility and traffic steering across 2G, 3G, and 4G networks. It analyzes the current configuration and proposes updated thresholds and parameters to optimize idle and connected mode mobility between different radio access technologies and frequency layers. The proposed strategy includes adjusting cell reselection, handover, and load balancing parameters to improve coverage and throughput. Four scenarios are outlined to implement a full U900 layer that incorporate different 3G frequency layer configurations along with 2G and 4G.
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.
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.
146661638 configuring-rbs-6201-gsm-with-rusSyed Ahmad
This document discusses configuring a Remote Unit Subsystem (RUS) for a GSM network. It describes the available RUS variants using the naming convention RU<t> <gg> <bb>. It also details the RUS's certified output power levels, use of license keys to adjust the power level, and main functions which include transceiving, filtering, power amplification, and supporting up to four carriers. The document then discusses defining the configuration in the Integrated DataBase (IDB) including settings for Multi Carrier Transceivers (MCTRs) and their power distributions based on the number of transceivers. It concludes with steps for defining node, ESB delay, and time frequency compensation parameters
The document describes resolving an alarm related to a mismatch between the number of hardware entities and cabinets in the configuration. It provides steps to clear the alarm by setting the product data for equipment and cabinet, and then restarting the baseband to refresh the product data and clear the alarm.
The document is a training manual for troubleshooting the Ericsson SSR 8000 family of systems. It contains over 50 pages of instructions, configuration examples, and troubleshooting exercises for trainees. The document states it is intended solely for training purposes and contains simplifications, so it should not be considered an official system specification. It also contains notes for instructors on customizing exercises for the specific equipment available for training.
This document provides information on balancing a vegetarian diet according to yogic principles. It discusses the major nutritional components needed - proteins, fats, carbohydrates, minerals and vitamins. It describes the six tastes (sweet, sour, salty, hot, bitter, astringent) that should be included in a meal and where they are found and their properties. Guidelines are given for eating organically, freshly prepared local foods in moderation according to one's body type to support health.
Este documento describe elementos clave para el desarrollo de políticas educativas en Perú entre 2011-2016. Propone políticas para reducir brechas educativas y promover derechos de grupos indígenas como los quechuas y aimaras, que representan alrededor del 94% de la población indígena peruana. Las políticas se enfocarán en educación intercultural bilingüe y educación en áreas rurales para servir mejor a estas comunidades.
The document provides an overview and analysis flow for optimizing the performance of a mobile network. It discusses various problems that can occur like low availability of control channels, congestion on signaling and traffic channels, and high drop call rates. For each problem, it lists probable causes and recommends actions to identify the issue and solutions to resolve it, such as adjusting configuration parameters, adding network capacity, or improving frequency planning. MML commands are also provided to check device logs, resources, and performance statistics for troubleshooting purposes.
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.
The document outlines the 8 step process for configuring a Sprint 4G Cascaded RET including:
1) Creating pre and post configuration version snapshots
2) Validating the RET and antenna configuration
3) Running scripts to cascade the RETs for different antenna vendors
4) Populating unique IDs for each RET
5) Setting the tilt boundaries
6) Matching the 1900 CDMA RET tilts to the 1900 LTE tilts
7) Verifying the new RET configuration
8) Continuing integration and troubleshooting any issues.
This document contains a list of Ericsson commands used to manage various network elements like BSCs, MSCs, radios, cells, logical channels, and faults. Some key commands include:
1. "eaw CIRCLE+BSC" to enter BSC mode and manage BSC objects.
2. "allip:acl=a1" to check external alarms on the BSC.
3. "rxbli:mo=rxotrx-188-6,subord,force" to block a radio forcefully.
4. "rlstc:cell=no0088c,state=halted" to halt a cell.
5. "rx
The document discusses working with BSC nodes in ENM and provides the following key points:
- BSC node configuration is done through managed objects (MOs) below the BscM object which have non-standard behavior for create, update, and delete operations.
- There are limitations when making changes to BscM MOs including only allowing 100 operations per command and only one user making changes at a time.
- Commands on BscM MOs can partially succeed, with some attributes or objects succeeding and others failing. It is important to review any failed operations carefully.
This document provides an overview of GSM MSC/MSC-S R12 configuration. It discusses network architecture models including vertically and horizontally integrated networks. It describes the different network layers and nodes in GSM and WCDMA systems. These include the base station system, core network nodes like the MSC and SGSN. It also covers signaling protocols used in the core network like SS7, SIGTRAN, BICC and H.248. The document provides information on identities used in GSM and WCDMA networks like IMSI, MSISDN. It discusses addressing of switching system entities using global and mobile global titles. Finally, it introduces concepts related to MSC servers and media gateways.
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).
Ericsson technical interview questionssethshivam75
This document contains technical interview questions asked by Ericsson including:
1) Questions about how mobile phones work, handoffs in GSM networks, differences between TCP/IP and SSL, DNS lookups, TCP layers, converting decimal to binary, prime numbers, multiplexing, and modulation techniques.
2) A tip that ECE students interviewing at Ericsson should have programming skills.
3) Additional questions about waveguide propagation, Ethernet frame formats, STP/RSTP, VSWR, waveguides, the ALOHA protocol, information theory concepts, antenna properties, and GSM/CDMA comparisons.
It is a handbook of UMTS/WCDMA call flows for PS services.
This document is originally edited by Justin MA and it is free to share to everyone who are interested.
All reference/resource are from internet. If there is any copy-right issue, please kindly inform Justin by majachang@gmail.com.
Thanks for your reading!
This document provides a commissioning procedure for an RBS 6201 2G system. It involves requirements for OMT and software versions, EC bus termination, pin configurations, defining sectors and parameters in the configuration wizard, shelf and slot positions, hub position, feeder loss, delay, PCM, ties, power configuration, and installing the IDB while changing the DUG maintenance state. The procedure guides configuring the 2G part of the 6201 and defines shelves, slots, and positions for DUG, RUG, and PDU units.
The document provides guidance on configuring remote electrical tilt (RET) in different scenarios. It describes RET introduction and support requirements. Configuration steps are outlined for single and multi-antenna RET devices controlled by the radio remote unit (RRU) or RET interface unit (RIU). The document also covers cascading RET configuration, where multiple RET units can be controlled by a single RRU.
The document provides a high-level summary and proposed strategy for mobility and traffic steering across 2G, 3G, and 4G networks. It analyzes the current configuration and proposes updated thresholds and parameters to optimize idle and connected mode mobility between different radio access technologies and frequency layers. The proposed strategy includes adjusting cell reselection, handover, and load balancing parameters to improve coverage and throughput. Four scenarios are outlined to implement a full U900 layer that incorporate different 3G frequency layer configurations along with 2G and 4G.
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.
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.
146661638 configuring-rbs-6201-gsm-with-rusSyed Ahmad
This document discusses configuring a Remote Unit Subsystem (RUS) for a GSM network. It describes the available RUS variants using the naming convention RU<t> <gg> <bb>. It also details the RUS's certified output power levels, use of license keys to adjust the power level, and main functions which include transceiving, filtering, power amplification, and supporting up to four carriers. The document then discusses defining the configuration in the Integrated DataBase (IDB) including settings for Multi Carrier Transceivers (MCTRs) and their power distributions based on the number of transceivers. It concludes with steps for defining node, ESB delay, and time frequency compensation parameters
The document describes resolving an alarm related to a mismatch between the number of hardware entities and cabinets in the configuration. It provides steps to clear the alarm by setting the product data for equipment and cabinet, and then restarting the baseband to refresh the product data and clear the alarm.
The document is a training manual for troubleshooting the Ericsson SSR 8000 family of systems. It contains over 50 pages of instructions, configuration examples, and troubleshooting exercises for trainees. The document states it is intended solely for training purposes and contains simplifications, so it should not be considered an official system specification. It also contains notes for instructors on customizing exercises for the specific equipment available for training.
This document provides information on balancing a vegetarian diet according to yogic principles. It discusses the major nutritional components needed - proteins, fats, carbohydrates, minerals and vitamins. It describes the six tastes (sweet, sour, salty, hot, bitter, astringent) that should be included in a meal and where they are found and their properties. Guidelines are given for eating organically, freshly prepared local foods in moderation according to one's body type to support health.
Este documento describe elementos clave para el desarrollo de políticas educativas en Perú entre 2011-2016. Propone políticas para reducir brechas educativas y promover derechos de grupos indígenas como los quechuas y aimaras, que representan alrededor del 94% de la población indígena peruana. Las políticas se enfocarán en educación intercultural bilingüe y educación en áreas rurales para servir mejor a estas comunidades.
Nerve injuries /certified fixed orthodontic courses by Indian dental academy Indian dental academy
Dental Courses by Indian Dental Academy
The Indian Dental Academy is the Leader in continuing dental education , training dentists in all aspects of dentistry and offering a wide range of dental certified courses in different formats.
Indian dental academy provides dental crown & Bridge,rotary endodontics,fixed orthodontics,
Dental implants courses.for details pls visit www.indiandentalacademy.com ,or call
0091-9248678078
This document discusses using MKS Integrity and the MKS-CM Connector with Model Management to provide application lifecycle management for CA 2E and CA Plex software development. It describes challenges with managing objects across multiple platforms and the benefits of an integrated ALM solution. The presentation covers how the MKS-CM Connector integrates CA Plex models into the change management process and allows checking out objects from the Plex model. It demonstrates typical development workflows and new features in CA Plex 6.1 that extend ALM capabilities.
Receita de ano novo – Carlos Drummond de Andrade e MonkeyBusinessMonkeyBusiness
O poema descreve os desejos para um ano novo verdadeiramente novo, não apenas no calendário, mas nas ações e no interior das pessoas. Para que o ano seja novo, as pessoas precisam merecê-lo fazendo escolhas conscientes que tragam clareza, justiça e direitos para todos.
O documento discute estratégias de persistência de objetos em Java, com foco no framework Hibernate. Hibernate mapeia objetos Java para tabelas de banco de dados relacional, permitindo que os desenvolvedores trabalhem com objetos ao invés de SQL. O documento explica como configurar e usar Hibernate, incluindo a criação de entidades, consultas, transações e associações entre objetos.
Fashion 2.0. exploring current social media trends from fashion business pers...Sanna Ketonen-Oksi
With web 2.0 businesses are stepping into an era with better appreciation of the business (1), more effective marketing (2), stronger networking (3) and value creation (4), i.e new kind of business thinking. Here some thoughts gathered related to how the small and medium sized fashion businesses could start / improve their social media presence. The presentation has been created during a Baltic Sea Region -funded Baltic Fashion project, at the campus of Novia University of Applied Sciences.
Explorando Analysis Services: Power Pivot, Tabular y MultidimensionalSpanishPASSVC
El concepto del Unified Dimensional Modeling (UDM) fue introducido en Analysis Services 2005 como una capa semántica para facilitar el desarrollo de cubos OLAP de fuentes diversas. En Analysis Services 2012 se introduce el concepto del Business Intelligence Semantic Model (BISM) como una evolución al UDM ofreciendo dos “sabores”: Multidiemnsional y Tabular. El BISM representa el corazón de la estrategia de Inteligencia de Negocios de Microsoft. Esta sesión explicara los conceptos básicos de Analysis Services 2012 y PowerPivot. Discutiremos los diferentes escenarios que permitirán a desarrolladores y arquitectos de BI a tomar mejores decisiones al momento de desarrollar los cimientos de la estrategia empresarial para el análisis de sus datos.
Este documento presenta información sobre técnicas de pesca y recuperación de tuberías. Explica los diferentes tipos de pesca como pesca de basura, pesca de tubería partida o desconectada. Describe las herramientas utilizadas como imanes de pesca, canastas para basura y taladros. También cubre procedimientos de recuperación de tuberías como indicadores de punto libre, retroceso y corte de tubería. El documento concluye presentando el sistema de calidad de Weatherford para el envío, uso y archivo de herram
In diesem Bootcamp steht das WARUM und das WIE im Vordergrund. Sie erhalten umfassende Informationen, fundiertes Wissen zu Online Marketing für Ihr Unternehmen und einen Überblick über aktuelle Trends. Techniken, Instrumente und Maßnahmen werden vorgestellt und selbst erarbeitet, wobei Nutzen und Handhabung im Mittelpunkt stehen. Hierdurch gelingt der Sprung von der Theorie in die Praxis problemlos. Auf diesen Workshop werden Taten folgen, mit welchen Sie und Ihr Unternehmen Erfolge feiern. Es ist Zeit für effektives Online Marketing
Guia rápido sobre como utilizar OKR - Objectives and Key Results.
Uma técnica para alinhamento da estratégia com a execução, desenvolvida na Intel e utilizada pelo Google, LinkedIn e várias outras empresas.
QFD is a customer-driven approach to quality function deployment that was developed in Japan in the 1960s. It enables companies to deploy the voice of the customer into new product development. Key aspects of QFD include translating customer requirements into technical requirements, using a house of quality matrix to show relationships between customer and technical requirements, and prioritizing requirements. Benefits of QFD include fewer changes, lower costs, fewer problems, and satisfied customers.
Haustuerkatalog Sternstunden von Fenster-Schmidinger / DoorsFlorian Schmidinger
Überzeugen Sie sich von unserer vielfältigen Auswahl an unterschiedlichen Türen. Egal ob Haustüren, Firmenportale oder Hebeschiebetüren. Jedes Produkt überzeugt durch optimale technische Vorraussetzungen und einer zeitgemäßen Optik. Die Mitarbeiter der Firma Fenster Schmidinger stehen Ihnen von der Beratung Vorort oder im Schauraum in Gramastetten bis zur Montage Ihrer Türen gerne begleitend zur Seite.
Shopleiter-Magazin Nr. 4 - Juli 2010:
- Wissensmanagement mit Mediawiki
- Schlüsselwörter für Websuche
- Hardware-Ausfall beim Hosting-Anbieter
- Universal Search als Traffic-Magnet (Textprovider)
- Käuferschutz als Conversion-Booster im eCommerce (sofortüberweisung)
- Buch-Rezension The Art of SEO (von E. Enge, S. Spencer, R. Fishkin und J. Stricchiola)
Las fuentes describen la política soviética hacia Afganistán desde finales de los años 60 hasta la retirada de las tropas soviéticas en 1989. La Fuente A presenta la Doctrina Brezhnev de 1968 que establece la responsabilidad de los partidos comunistas hacia otros países socialistas. Las Fuentes B y C muestran el creciente apoyo militar y económico de la URSS a Afganistán en 1979-1980. La Fuente D detalla la condena y sanciones de EE.UU. a la invasión soviética. La Fuente E
The document describes the CDLCP command, which prints long duration call supervision data. It lists the command format, parameters, function, examples, and resulting printouts. The command has no parameters and prints data on long calls, including setup information and whether automatic disconnection is enabled.
The document provides explanations of various ERICSSON commands used for network monitoring and troubleshooting. The commands are used to view cells, digital paths, subscriber information, routes, blocking/deblocking of digital paths, management object status, fault prints, and more. Additional details are given on commands to check digital path quality statistics, determine the T1 a radio is using, and check traffic on a specific radio.
The document contains configuration and fault information for a radio system with the cell identifier MS4099E. It provides details on frequency configuration, neighbor cell relations, equipment alarms, status and configurations for various components including the RXOTG transmitter group and receiver units RXORX-321-0, RXORX-321-1, and RXORX-321-4 which are reporting faults.
The document contains configuration and fault information for a radio system with the cell identifier MS4099E. It provides details on frequency configuration, neighbor cell relations, equipment alarms, status and configurations for various managed objects, as well as fault codes for receivers with issues.
An approach for load-time hacking using LD_PRELOAD is presented.
We discuss a simple, yet intriguing, strategy for overcoming the limitations discussed in Part 1 (i.e., the first publication given in the reference) of reverse engineering and exploitation using LD_PRELOAD, a dynamic linking technique. In particular, we relax the need for exit(1) in the main function. The essence of the technique is that both the stack pointer (esp) and the base frame pointer (ebp) are carefully adjusted when the wrapper to the library function is called. The proposed solution allows us to safely return to libc after dynamically modifying the control flow in the wrapper to (library) functions.
This program controls a robot using a microcontroller. It defines pins for sensors and motors, includes libraries, and declares interrupt routines to control pulse-width modulation for motor speed. The main routine initializes ports, timers and interrupts, then calls functions for the robot to scan its environment, turn right, and repeat in a loop.
The document describes the steps to build a mechanically scanned LED clock called "The Propeller Clock". It uses a DC motor to spin a circuit board with LED digits. The motor's armature is used to power the circuit board. A PIC microcontroller is programmed to control the LED display and keep time. Modifications are suggested to adapt it to different motors.
The document contains C code for controlling an LCD display to show a traffic intersection. It includes functions to initialize the LCD and SPI interface, write characters to the display, and display the intersection graphics and traffic lights. It also has code to interface with sensors to detect vehicle requests and update the displayed lights and requests accordingly. The main traffic controller code implements a simple traffic light sequence and calls the LCD and sensor functions.
The document describes interfacing a 16x2 character LCD display with an 89C51 microcontroller using a 4-bit interface with 6 I/O pins. It includes the objective, background on LCD displays, control sequences, circuit schematic, command codes, and code files for initializing and writing to the LCD.
The document discusses UART (Universal Asynchronous Receiver/Transmitter) and RS-232 communication standards. It describes the voltage levels used, the need for a converter chip between UART and RS-232, synchronous vs asynchronous transmission, baud rates, frame formats, and provides VHDL code for a UART transmitter and receiver implementation including state machines and registers.
The document contains examples of Verilog code including:
1. A 2-D flip-flop synchronizer module and testbench.
2. Three different finite state machine (FSM) design techniques using single, two, and three always blocks.
3. A generic pipeline/repeater module and testbench.
4. Simple D flip-flop modules with synchronous and asynchronous resets and testbenches.
5. A mod-M counter module that generates a tick pulse and testbench.
6. A clock pulse generator module.
This document discusses cascaded RC circuits and their analysis in both open loop and closed loop configurations. It presents the transfer function for a cascaded RC circuit in the open loop case. For the closed loop case, it derives the transfer function including a proportional feedback controller. It also discusses using an Arduino board to implement analog input and output to experimentally validate the closed loop control of a cascaded RC circuit.
This document contains assembly code macros and variables for a game involving planes, ships, and helicopters on different levels. It defines macros for drawing graphics, handling input, random number generation, and dynamic movement of objects. Variables track positions, speeds, and statuses of objects and the level parameters. The code implements game logic and object behavior through calls to the macros.
This document provides a cheat sheet for using the Mona.py tool to analyze crashes and facilitate exploit development. It outlines commands for configuring Mona, searching for pointers and patterns in memory, finding code snippets, generating cyclic patterns, and automating ROP chain generation for bypassing DEP. The document explains how to use Mona to suggest exploit primitives after a crash, find useful gadgets like POP/POP/RET sequences, and provide starting points for ROP payloads.
This document provides information about data types and variables in Java. It discusses the basic data types like int, float, boolean etc. and their ranges. It also covers arrays, literals, identifiers, comments, keywords, operators and variables. For each topic, it provides details on syntax and examples. The document is an introduction to basic data types and variables in Java.
RNASeqR: RNA-Seq workflow for case-control studyKuanHaoChao
This R package is designed for case-control RNA-Seq analysis (two-group). There are six steps: "RNASeqRParam S4 Object Creation", "Environment Setup", "Quality Assessment", "Reads Alignment & Quantification", "Gene-level Differential Analyses" and "Functional Analyses". Each step corresponds to a function in this package. After running functions in order, a basic RNASeq analysis would be done easily.
This document provides information about the microcontroller PIC16F84A, including:
1) It describes what a microcontroller is and introduces the PIC16F84A microcontroller.
2) It lists the ports and pins available on the PIC16F84A, including Port A and Port B pins for input/output.
3) It provides examples of using ports as inputs to read buttons or switches, and as outputs to control LEDs.
This document contains code for initializing and sending data to an LCD module using a PIC microcontroller. It includes macros and subroutines for initializing the LCD, sending control signals and data, and displaying the message "HOLA MUNDO" on the LCD screen. When the user presses a button, the display will be cleared and the message will redraw.
This document discusses procedures in assembly language. It covers defining procedures, calling procedures using the CALL and RET instructions, passing parameters to procedures, and managing the runtime stack. Procedures use stack frames to access parameters passed on the stack and allocate space for local variables. Examples are provided of procedures that pass arguments by value and by reference.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
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.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
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.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
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.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
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.
1. *********************RBS Commande*****************
rxasp:moty=rxotg; ! all PB in BSC!
rlcrp:cell=all; ! all alarm BTS in BSC!
RXTCP:moty=rxotg,cell=23642A; ! pour avoir le tg!
rxtcp:mo=rxotg-11; ! pour avoir la cell!
rxcdp:mo=rxotg-442; ! check if site down!
rxasp:mo=rxotg-442; ! site down TRANS ou PWR !
RLCRP:CELL=23108A; !voir traffic par cell!
rxmfp:mo=rxoCF-13; !voir le code de la classe de l'alarm Excel!
rxmfp:mo=rxoTRX-49-0;
rxmfp:mo=rxoRX-69-4; !voir le code de la classe de l'alarm Excel!
rxmfp:mo=rxoTX-69-4,faulty;
rxmfp:mo=rxoTF-69;
rxmfp:mo=rxoTS-55-11-2;
rxmsp:mo=rxoCF-21,subord; !voir SI IL EST MBL!
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%% restart site%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
rxBLI:mo=rxoCF-431,subord,force;
rxese:mo=rxoCF-431,subord;
rxesi:mo=rxoCF-431,subord;
rxtei:mo=rxoCF-431;
rxble:mo=rxoCF-431,subord;
* CAS TS SYNC FAULT ( time slot)
rxasp:mo=rxotg-x
rxbli:mo=rxots-;
rxese:mo=rxots-;
rxesi:mo=rxots-;
rxtei:mo=rxots-;
rxlti:mo=rxots-;
rxble:mo=rxots-;
rxcdp:mo=rxotg-x
*****************************************************************************
* CAS LOOP TEST FAILED TSLOT
rxasp:mo=rxotg-x;
rxbli:mo=rxots-;
rxtei:mo=rxots-;
rxlti:mo=rxots-;
rxble:mo=rxots- ;
rxcdp:mo=rxots-;
*****************check DIP E1***************************
dtqsr:dip= 7RBL2,degr,unacc,sf; !compteur DIP a zero!
rxapp:mo=rxotg-400; !check etat dip!
radep:dev=RBLT2-1567;
ntcop:snt=ETM2-0;
dtstp:dip= 48RBL2;
dtqup:dip=3RBLT; ! BER:error rate(taux d'erreur)!
*****************************************************
rrgbp; !check GPRS!
*****************rreset site**************************
rxbli:mo=rxocf-32,force,subord;
rxbli:mo=rxois-444;
rxese:mo=rxois-444;
3. aploc;
NE=BSCANB1,NODE=A
cluster node
prcstate -l
raidutil -L logical
mml
EXIT
rrntp; ! pour voir si c un bscremot ou non (avec ou sans trc)!
APLOC; !apres lost connection on les alarms ap file ..... and
charging estin......!
ALIST ! listy les alarms de la apg!
afpls -ls tqbgw ! verifier les fichies qui nont pas ete envoyer !
afpfti -f TQBGW ! si oui on va le renvoi à nouveau !
exit ! sortie apg!
********************** C7 CHECK **********************
********************** STM ********************
tpstp:sdip=19E1551;
tpcop:sdip=19E1551;
dtstp:dip=1326UPD;
ntcop:snt=ET1551-24;
STDEP:DEV=1326UPD;
dtqup:dip=ALL;
strsp:r=RBEODTI;
strdp:r=RBEODTI,state=seal&bloc&libl;
DTSTP:dip=all;
**************BSC****************
C7LTP:ls=all;
c7ltp:ls=3-482;
c7ldp:ls=3-482;
c7rsp:ls=3-463;
exscp:dev= C7ST2C-97;
radep:dev=RTLTT2-1264;
ntcop:snt=ETM2-3;
dtstp:dip=26rtt2;
dtqup:dip=
**************MSC***************
C7LTP:ls=all;
c7ltp:ls=3-484;
c7ldp:ls=3-484;
c7rsp:ls=3-484;
exscp:dev=C7ST2C-18;
exdep:dev=UPD1-12272;
ntcop:snt=ET1551-9;
dtstp:dip=380UPD1;
dtqup:dip=654upd1;
******************************** check BTS ********************************
rxtcp:moty=rxoTg,cell=16763A;
rxtcp:mo=rXOTG-145;
rxcdp:mo=rxotg-315;
rxasp:mo=rxotg-112;
rxasp:moty=rxotg; !donne toute les alarm su!
rxmfp:mo=RXOCF-449;
rxmsp:mo=rxotg-197,subord; !voir si mbl OU BLOC!
rxmop:mo=rxoCF-37; !pour voir la cell ou se trouve le tx!
rxcap:mo=rxotg-22; !if site cascaded!
rlstp:cell=18654B; !voir si cell halted!
rlstp:cell=ALL;
rlcrp:cell=16242a; !voir s'il y a traffic!
rlcrp:cell=all;
4. rlcfp:cell=16658a; !donne les frequence de cell!
rasap; !pour voir les devices non utilise ou les devices toujour occupe!
RXMLP:MO=RXOTG-41;
RXELP:MO=RXOTG-41;
rrntp; !check type of bsc!
******************************* check DIP *********************************
rxapp:mo=rxotg-104;
radep:dev=rblt2-1071;
ntcop:snt=eTM2-0;
dtstp:dip=55rBLT;
dtqup:dip=119rblT; !voir le taux d'erreur!
dtqsr:dip=29rbl2,degr,unacc; !pour restarter le dip!
****************************** BTS BLOCK-DEBLOCK **************************
RXBLI:MO=RXOTS-115-5-2;
RXESE:MO=RXOTG-37,SUBORD;
RLSTC:CELL=16276A,STATE=HALTED;
RXESI:MO=RXOTG-37,SUBORD;
RXBLE:MO=RXOTS-115-5-2;
RLSTC:CELL=06629C,STATE=ACTIVE;
******************** deblok bts cas loop test *******************************
RXBLI:MO=RXOTG-106,subord;
RXTEI:MO=RXOT-106;
RXLTI:MO=RXOTG-106;
RXBLE:MO=RXOTG-106;
********************************* C7 CHECK ***********************************
STM
tpstp:sdip=19E1551;
tpcop:sdip=19E1551;
dtstp:dip=1326UPD;
ntcop:snt=ET1551-24;
STDEP:DEV=1326UPD;
dtqup:dip=ALL;
strsp:r=BADR1TI;
strdp:r=bHASS1o,state=seal&bloc&libl;
DTSTP:dip=all;
*************** check route racimo/spanish/vms ***********************
strsp:r=ivrp1to; !Racimo MSCMUS1!
strsp:r=ptfk1to&ptfk2to&ptfk3to;
strsp:r=vms1t1o&vms02to;
strsp:r=PMHI2TI&PMHI2TO;
**************BSC****************
C7LTP:ls=all;
c7ltp:ls=3-463;
c7ldp:ls=3-463;
c7rsp:ls=3-463;
exscp:dev= C7ST2C-19;
radep:dev=RTLTT2-1264;
ntcop:snt=ETM2-3;
dtstp:dip=26rtt2;
dtqup:dip=
**************MSC***************
C7LTP:ls=all;
c7ltp:ls=3-600;
c7ldp:ls=2-5034;
c7rsp:ls=3-110;
exscp:dev=C7ST2C-103;
exdep:dev=UPD-1505;
ntcop:snt=UPET-47;
5. dtstp:dip=47UPDP;
dtqup:dip=654upd1;
DTDIP:dip=315mal1; ! pour trouver stm a partir du dip!
exdrp:dev=c7sth-1&&-31; !pour voir le rp qui connect ces mic!
C7RADEP; !voir les alternances des routes!
c7ltp:dest=2-35; ! voir les route!
stdep:dev=c7sth-0;
nsstp; !pour voir network suncronisation!
tpstp:sdip=0e1551; !pour voir si ms bloc manualy!
strdp:r=BSALHTO; !pour voir le dev a partir de la route!
strdp:r=CNCP3TO,state=seal&libl&bloc; !voir les device de bloking supervision!
strsp:r=CNCP3TO; !voir l'etat de la route OU BIEN TOUT LES
ROUTES!
blorp; !voir les routes qui sont bloquie!
mgbsp:bsc=all; !voir les BSC ratachees!
mgnmp:msc=all; !voir les BSC ratachees!
ne=BSCMLA1,node=a; !ecrit ga dans network element pour checker si on a
pb trans ou pb dans APG!
dpwsp; !cp stat!
exscp:name=name; !semipermanent connection data!
****************** pour definir le correspondance bsc-bsc **************
RACIP:DEV=RTLTT2-63;
on prend atercic ,on lance la CMD RACIP dans l'autre BSC
RACIP:ATERCIC=63;
GdSTP;
nsstp;
****************** pour definir le correspondance Msc-Msc **************
exdep:dev=upd1-xxxx; ! on prend le cic "misc1"
vers l'autre MSC on lance la commande
exdep:r=xxx,misc1=x;
*************************** check alarm APZ & APT ***************************
c7ltp:ls=aLl;
allip;
allip:alcat=APz;
allip:alcat=APT,acl=A3;
allip:alcat=poweR;
allip:alcat=ext;
allip:prca=43;
syrip:survey; !voir historique des alarm!
syrip:log;
PLLDP;
RRGBP;
SYELP; !soft error !
AFTSP:TEST=110,sae=all;
strdp:r=ALL,state=abl; !bloking supervisionAPZ!
dbtsp:tab=saactions; !size alteration!
SAOCP; !SIZE ALTERATION CONTROL!
saaep:sae=700,block=all;
saaii:sae=36,ni=1680; !size alteration increas!
saadi; !(for size alteration decrease /not common/!
tpstp:sdip=20e1551; !pour voir ms alarm:NETWORK PROTECTION UNPROTECTED MODE!
ntdcp:snt=20e1551-9,subsnt=1;!pour voir ms alarm:NETWORK PROTECTION UNPROTECTED
MODE!
mml
rlvap; !CELL SEIZURE SUPERVISION OF LOGICAL CHANNELS!
rlvar:CHTYPE=TCH;
hgsdc;
gdstp; !voir groupe switc!
****************** desactivation c7 ****************************
C7LAI:LS=2-206;
6. C7LAE:ls=3-206;
***************** !SYNCHRONOUS DIGITAL PATH QUALITY SUPERVISION! **********
tpqsr:sdip=2ETM2,unacc,degr; !reset!
TPSTP:SDIP=2Etm2;
tpcop:sdip=2Etm2;
************************ cas lost connection APG *****************************
AplOC;
ipconfig
alist
DPWSP;
MML
prcstate -l
cluster group
CLUSTER NODE
HOSTNAME
PRCSTATE
NET START ACS_PRC_ClusterControl
PTCOI;
PTWSP;
PTCOE;
CLUSTER RES
exit;
******************* APG command *******************************
hwver; !check APG version!
*************************** check seizure alarm ******************************
rasap;
racip:dev=RALT2-5464;
stdep:dev=RALT2-5464;
*********************** semipermanent connection data *************************
EXSCP:name=BSCKHS1_0;
stdep:dev=C7ST2C-0;
**************** delete DIGITAL PATH QUALITY SUPERVISION alarm ***************
dtqsr:dip=all,es,ses,sf;
dtqsr:dip=all,es2,ses2,sf;
************************************ buckup********************************
SYBUE; !Passive Dump!
SYBUP:FILE; !Make Dump!
; !Confirm!
SYBFP:FILE; !Check Dump File!
SYTUC; !Change/Rotate Software!
SYBUI; !Activate APG40!
SYBUI:DISC; !Activate IOG20!
sybue; !stop automatic backup!
sybup:file=refsw2; !send new backup!
sybhp; ! voir si le buckup est hunging si pas hinging alors tu peut faire le
buckup!
*************************** pour eliminer sae ***********************
dbtri;
dbtse:tab=saactions,actnum=1;
dbtre:com;
********************* DISTRIBUTED GROUP SWITCH FAULT hlr *************
gdbli:unit=mux3-A-14;
gdble:unit=mux3-A-14;
gdstp;
*********************************************************************
7. RASAP; !SEIZURE SUPERVISION OF DEVICES IN BSC ALARMED DEVICES!
RASAR:DETY=RALT2; !CLEAR ALARM!
RLVAP; !CELL SEIZURE SUPERVISION OF LOGICAL CHANNELS ALARMED OBJECTS
DATA!
RLVAR:CHTYPE=TCH; !CLEAR ALARM!
**************************** restriction sur BSC *****************************
RLSBP:cell=all;
rlsbc:cell=all,acc=clear;
******************** rp fault *********************************
EXrpP:RP=ALL;
EXRPP:RP=548; !RP DATA!
REPRI:RP=195; !RP DIAGNOSIS-block RP!
REMRI:RP=195,pcb=RPPS1; !RP MANUAL INTERVENTION!
RECRI:RP=195; !RP REPAIR-deblock RP!
EXEMP:RP=548,em=all; !what rp control!
************************************ others **********************************
SAOSP; !VERSION OF APZ.! !APZ PRINTOUT !
RLSTP:CELL=ALL; !CELL STATUS!
RLCFP:CELL=15642b; !CELL CONFIGURATION FREQUENCY DATA!
RLDEP:CELL=15642b; !CELL DESCRIPTION DATA!
RLCPP:CELL=15642b; !CELL CONFIGURATION POWER DATA!
RLSSP:CELL=15642b; !CELL SYSTEM INFORMATION SACCH AND BCCH DATA!
RLSLP:CELL=15642a; !CELL SUPERVISION OF LOGICAL CHANNEL AVAILABILITY DATA!
RLSBP:CELL=15644B; !CELL SYSTEM INFORMATION BCCH DATA!
*************************** for checking number ****************************
hgrsp; !check state of HLR!
MGssp:imsi=603013023923296; !pour voir si le tel est ferme!
mgssi:imsi=661707319; !pour voir si le telephone est fermi!
hgsdp:msisdn=213661707319,all;
ctrai:msisdn=numero;
**************** pour chercher les cmd utilise dans winfiol ***************
APLOC;
alogfind -e date -s rlstc
***************** localisation ********************
hgsdp:msisdn=213661698613,all; !pour recuperrer le N0 msc!
mgcap; !pour verfifier le N0 msc!
MGSSP:IMSI=603011001111794; !pour recuperer le N0 de bsc!
Mgbsp:BSC=all; !voir bsc connecter a msc!
Mgcep:cell=all; !voir tout les cell connecter a bsc ou msc et prend le nom de
bsc!
******************* LOCALIZATION********************
hgsdp:msisdn=213659336995,all;
mgcap;
MGSSP:IMSI= 603012023656995;
ctrai:msisdn=213659336995;
TEST SYSTEM;
PRINT VAR MTV 93836:H'147;
END TEST;
Mgcep:LAI=603-01-19101;
************** renvoie d 'appel *******************
hgsdp:msisdn=213662210924,all; !pour CHECK LE RENVOI!
HGSSI:MSISDN=21368628632,SS=CFU,FNUM=021652487; !POUR FAIRE LE RENVOIE!
HGSSE:MSISDN=213661690431,SS=cFU; ! ANNULER LE RENVOIE!
hgsdp:connected;
8. hgsdp:msisdn=213661737019,ssda;
cdlcp; !call duration!
********************** pour mettre swap a un site ******************
MGCEP:CELL=37101A;
MGCEE:CELL=37101C;
MGCEI:CELL=37101C,CGI=603-01-37101-11013,BSC=BTINDFN;
MGBSP:BSC=ALL;
******************** BLOCK NUMERO **********************
HGSDP:MSISDN=213661601152,all;
HGSDC:MSISDN=213661601152,sud=oba-1; !ca est equivalent a obi-1 in et obo-1 out!
!blocage emission/reception obi-1 obo-1!
**************************** Etat APG**********************************
aploc;
prcstate -l
cluster group
exit;
*************************GPRS**************************
rrgbp;
rrgbp:ncbd;
radep:dev=rtglt2-33;
ntcop:snt=etrtg-1;
ntcop:snt=etm2-2;
dtstp:dip=1rtglt;
rrmap:trapool=all;
******************* *S'IL Y A EDGE ***************
rxcap:mo=rxots-435-10-6;
rlbdp:cell=xxxx;
*************** *BSC avec /sans TRC******************
rrntp;
***********************CELL NEIGHBOUR********************
rlncp:cell=all;
********************************************************
*BLOCKING SUPERVISION OF DEVICE*
stbsp:dety=ralt;
******************* SAE CLEAR ****************
dbtsp:tab=saactions;
dbtri;
dbtse:tab=saactions,actnum=4;
dbtre:com;
***************** pb bscstf1 **************
gdstp;
gdbli:unit=xm-B-0-0;
gdble:unit=xm-B-0-0;
gdstp;
*************** ROUTAGE **************
ANBSP:b=all,rc=646;
anrsp:rc=646;
anrsp:rc=647;
anrsi:br=tmr-0&-3&-4,p01=1,r=cncp4to,ess=1,esr=0;
anrsi:br=tmr-1&-2,p02=1,r=cncp4to,ess=0,esr=0;