The document provides steps to upgrade the Cisco IOS on an Aironet 1130AG Series access point. It outlines downloading the appropriate IOS file from Cisco's website or another source, then using the access point's web interface or CLI to navigate to the System Software menu, select Software Upgrade, choose TFTP Upgrade, and select the IOS file to upload and initiate the upgrade process. It also describes using TFTP to transfer the file and monitoring the upgrade status until completion.
Foreman and Puppet Master Install process - Customer Used Case Kanwar Batra
The above process was used for a Customer to automate and deploy virtual and physical infrastrucutre using Foreman. This document outlines the my Install process of Foreman too
This document provides installation instructions for graphics drivers for various Intel chipsets on Windows 2000 and Windows XP systems. It includes requirements, localized language abbreviations, manual and automated installation steps, and instructions for verifying the installation and identifying the driver version number. The driver package supports Intel 855GM, 852GM, 855GME, 852GME, 910GL, 915GV, 945G, 915GM, 910GML, 915GMS, 915G, and 945GM chipsets.
HKG15-505: Power Management interactions with OP-TEE and Trusted FirmwareLinaro
The document discusses power management in ARMv8-A and the integration of OP-TEE with the ARM Trusted Firmware. It provides an overview of the software stack and PSCI requirements. It then describes OP-TEE's system view and how it integrates with ARM Trusted Firmware as a runtime service. Finally, it discusses the programmer's view of PSCI and provides examples of how CPU_ON, CPU_OFF, and CPU_SUSPEND operations are handled between Linux, ARM Trusted Firmware, and OP-TEE.
HKG15-505: Power Management interactions with OP-TEE and Trusted FirmwareLinaro
HKG15-505: Power Management interactions with OP-TEE and Trusted Firmware
---------------------------------------------------
Speaker: Jorge Ramirez-Ortiz
Date: February 13, 2015
---------------------------------------------------
★ Session Summary ★
[Note: this is a joint Security/Power Management session) Understand what use cases related to Power Management have to interact with Trusted Firmware via Secure calls. Walk through some key use cases like CPU Suspend and explain how PM Linux drivers interacts with Trusted Firmware / PSCI
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250855
Video: https://www.youtube.com/watch?v=hQ2ITjHZY4s
Etherpad: http://pad.linaro.org/p/hkg15-505
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Upgrading from ESM 5.0 SP2 or 5.2 to ESM 5.5Protect724
This document provides instructions for upgrading the ArcSight database components from version 5.0 SP2 or 5.2 to version 5.5. It includes steps for upgrading the Oracle software to version 11.2.0.3, preparing the ArcSight database, and upgrading the database software and partition archiver. It also describes how to transfer partition archiver settings during the upgrade process.
1) SPI (Serial Peripheral Interface) is a synchronous serial communication interface standard used for communicating with serial peripheral devices.
2) SPI uses four signals - Serial Clock (SCLK), Master Output Slave Input (MOSI), Master Input Slave Output (MISO), and Slave Select (SS). It can support multiple slaves through individual SS lines.
3) SPI is full duplex, allowing simultaneous transmission and reception of data. It provides higher throughput than I2C but requires more pins and the master must control all communication.
This document provides instructions for installing PHP on Windows systems. It discusses using the Windows installer, performing a manual installation, installing PECL extensions, and configuring PHP and web servers. The key steps for manual installation are extracting the PHP zip file, adding the PHP directory to the system PATH so required DLL files can be found, and setting up the php.ini configuration file. The document also provides an overview of PHP modules for different web servers that are included with PHP distributions for Windows.
The document provides steps to upgrade the Cisco IOS on an Aironet 1130AG Series access point. It outlines downloading the appropriate IOS file from Cisco's website or another source, then using the access point's web interface or CLI to navigate to the System Software menu, select Software Upgrade, choose TFTP Upgrade, and select the IOS file to upload and initiate the upgrade process. It also describes using TFTP to transfer the file and monitoring the upgrade status until completion.
Foreman and Puppet Master Install process - Customer Used Case Kanwar Batra
The above process was used for a Customer to automate and deploy virtual and physical infrastrucutre using Foreman. This document outlines the my Install process of Foreman too
This document provides installation instructions for graphics drivers for various Intel chipsets on Windows 2000 and Windows XP systems. It includes requirements, localized language abbreviations, manual and automated installation steps, and instructions for verifying the installation and identifying the driver version number. The driver package supports Intel 855GM, 852GM, 855GME, 852GME, 910GL, 915GV, 945G, 915GM, 910GML, 915GMS, 915G, and 945GM chipsets.
HKG15-505: Power Management interactions with OP-TEE and Trusted FirmwareLinaro
The document discusses power management in ARMv8-A and the integration of OP-TEE with the ARM Trusted Firmware. It provides an overview of the software stack and PSCI requirements. It then describes OP-TEE's system view and how it integrates with ARM Trusted Firmware as a runtime service. Finally, it discusses the programmer's view of PSCI and provides examples of how CPU_ON, CPU_OFF, and CPU_SUSPEND operations are handled between Linux, ARM Trusted Firmware, and OP-TEE.
HKG15-505: Power Management interactions with OP-TEE and Trusted FirmwareLinaro
HKG15-505: Power Management interactions with OP-TEE and Trusted Firmware
---------------------------------------------------
Speaker: Jorge Ramirez-Ortiz
Date: February 13, 2015
---------------------------------------------------
★ Session Summary ★
[Note: this is a joint Security/Power Management session) Understand what use cases related to Power Management have to interact with Trusted Firmware via Secure calls. Walk through some key use cases like CPU Suspend and explain how PM Linux drivers interacts with Trusted Firmware / PSCI
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250855
Video: https://www.youtube.com/watch?v=hQ2ITjHZY4s
Etherpad: http://pad.linaro.org/p/hkg15-505
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
Upgrading from ESM 5.0 SP2 or 5.2 to ESM 5.5Protect724
This document provides instructions for upgrading the ArcSight database components from version 5.0 SP2 or 5.2 to version 5.5. It includes steps for upgrading the Oracle software to version 11.2.0.3, preparing the ArcSight database, and upgrading the database software and partition archiver. It also describes how to transfer partition archiver settings during the upgrade process.
1) SPI (Serial Peripheral Interface) is a synchronous serial communication interface standard used for communicating with serial peripheral devices.
2) SPI uses four signals - Serial Clock (SCLK), Master Output Slave Input (MOSI), Master Input Slave Output (MISO), and Slave Select (SS). It can support multiple slaves through individual SS lines.
3) SPI is full duplex, allowing simultaneous transmission and reception of data. It provides higher throughput than I2C but requires more pins and the master must control all communication.
This document provides instructions for installing PHP on Windows systems. It discusses using the Windows installer, performing a manual installation, installing PECL extensions, and configuring PHP and web servers. The key steps for manual installation are extracting the PHP zip file, adding the PHP directory to the system PATH so required DLL files can be found, and setting up the php.ini configuration file. The document also provides an overview of PHP modules for different web servers that are included with PHP distributions for Windows.
This document provides instructions for upgrading or downgrading the software on a TCU (Telecommunications Control Unit) using a SolarWind SFTP server. It describes how to configure the SFTP server by setting the TCP port, IP address, and file storage location. It then lists the steps to check the current TCU software revision, start an upgrade session, download the new software file from the SFTP server, check the download status, activate the new software, end the upgrade session, and check the software revision after completion.
This document provides instructions for installing Oracle Database Client 12c on IBM AIX on POWER Systems (64-bit). It describes reviewing information, logging in as root, configuring servers, checking requirements and installing Oracle software. Operating system requirements include supported versions of AIX 6.1, 7.1 and 7.2, required filesets and APAR fixes. Additional drivers, software and requirements for connectivity, messaging and programming environments are also listed.
This document outlines the steps to install AIX on Power servers using a NIM server. It describes powering on the HMC and configuring its IP addresses. LPARs are then created on the Power servers and connected to the HMC. AIX is installed on the LPARs by booting from media and navigating the installation steps. SSH is enabled and the NIM master server is configured by installing filesets and defining the NIM environment. A standalone NIM client is added and connectivity is tested between the client and NIM server using SMS ping.
This document discusses Automotive Embedded Systems and the AUTOSAR Application Layer. It covers topics like use cases in AUTOSAR, AUTOSAR basic software modules, the AUTOSAR system design process, software components, runnables, events, and the internal behavior of software components. Diagrams and examples are provided to illustrate concepts like software component types, the relationship between software components and runnables, event types that can trigger runnables, and how a timing event is defined in XML.
LCU13: Deep Dive into ARM Trusted Firmware
Resource: LCU13
Name: Deep Dive into ARM Trusted Firmware
Date: 31-10-2013
Speaker: Dan Handley / Charles Garcia-Tobin
Linux provides a common mailbox framework for communication between controller and client drivers. The framework includes mailbox_controller and mailbox_client header files. Several device drivers implement this framework for communication with hardware mailboxes, including drivers for ARM MHU, Broadcom, Altera, STMicro, and TI mailboxes. The mailbox framework supports synchronous and asynchronous message notification and defines mailbox channel operations for sending/receiving data and initializing/shutting down channels. ARM's SCPI protocol is commonly used with the mailbox framework for communication between application and system control processors over an MHU. The Linux kernel documentation describes supporting the SCPI protocol via the mailbox framework and device tree bindings.
IBM Lotusphere 2012 Show301: Leveraging the Sametime Proxy to support Mobile ...William Holmes
This document discusses deploying and configuring the IBM Sametime proxy server. It begins with an agenda that covers prerequisites, planning the deployment architecture, installation, configuration, and supporting mobile devices and applications. Key points include that the proxy server requires IBM WebSphere Application Server and a Sametime community server. The proxy connects to the community server on port 1516 and supports single sign-on. Deployment types include a single server, clustered, or using a load balancer. The document provides installation and configuration instructions for upgrading the system console and proxy servers to a new release.
This document discusses the AUTOSAR application layer. It explains that the application layer provides the system functionality through software components (SWCs) that contain software. The document outlines different types of SWCs and their elements like ports, runnable entities, and events. It also discusses how SWCs communicate internally and across ECUs using the virtual functional bus. The mapping of runnable entities to operating system tasks is mentioned as the topic for the next session.
This document provides information about administering ColdFusion MX servers. It discusses ColdFusion editions and configurations, installing and connecting the ColdFusion server to a web server, managing datasources and databases, monitoring server activity, and tuning server settings.
SFO15-TR9: PSCI, ACPI (and UEFI to boot)
Speaker: Bill Fletcher
Date: September 24, 2015
★ Session Description ★
An introductory session of a system-level overview at Power State Coordination
- Focus on ARMv8
- Goes top-down from ACPI
- A demo based on the current code in qemu
- The specifications are very dynamic - what’s onging for ACPI and PSCI
★ Resources ★
Video: https://www.youtube.com/watch?v=vXzPdpaZVto
Presentation: http://www.slideshare.net/linaroorg/sfo15tr9-psci-acpi-and-uefi-to-boot
Etherpad: pad.linaro.org/p/sfo15-tr9
Pathable: https://sfo15.pathable.com/meetings/303087
★ Event Details ★
Linaro Connect San Francisco 2015 - #SFO15
September 21-25, 2015
Hyatt Regency Hotel
http://www.linaro.org
http://connect.linaro.org
In recent years, we have been witnessing a steady increase in security vulnerabilities in firmware. Nearly all of these issues require local (often privileged) or physical access to exploit. In this talk, we will present novel *remote* attacks on system firmware.
In this talk, we will show different remote attack vectors into system firmware, including networking, updates over the Internet, and error reporting. We will also be demonstrating and remotely exploiting vulnerabilities in different UEFI firmware implementations which can lead to installing persistent implants remotely at scale. The proof-of-concept exploit is less than 800 bytes.
How can we defend against such firmware attacks? We will analyze the remotely exploitable UEFI and BMC attack surface of modern systems, explain specific mitigations for the discussed vulnerabilities, and provide recommendations to detect such attacks and discover compromised systems.
The document provides a step-by-step guide for installing Oracle Business Intelligence 11g on Linux. It outlines downloading required software, preparing the Linux machine, installing Oracle Database, Java, the Repository Creation Utility, WebLogic Server, and BI software. It also describes configuring the BI installation and middleware.
Slide deck for my presentation at the Google Developer Group San Francisco. Step-by-step guide to turning a ThinkPad X220 into a Chromium OS Android development machine. Covers hardware, firmware and software upgrades. Dynamic up-to-date slides at https://goo.gl/ivaugY
My presentation for Google Developer Group San Francisco. Step-by-step guide to turning a ThinkPad X220 into a Chromium OS Android development machine. Covers flashing modified Coreboot firmware, building and installing Chromium OS from source, and hardware upgrades.
Updated slides at https://goo.gl/ivaugY
This document discusses Controller Area Network (CAN) which is a vehicle bus standard that allows microcontrollers and devices to communicate with each other within a vehicle without a host computer. It covers the general characteristics of CAN including its event-driven nature, bus arbitration, message filtering, and the different types of CAN messages including data frames, remote frames, error frames, and overload frames. The document provides detailed explanations and illustrations of the fields that make up CAN data frames.
This document provides information about the Intel(R) Chipset Software Installation Utility version 7.0.0.1025, which is designed to install Windows INF files to configure Intel chipset components like PCI support, storage support, and USB support. It discusses the product details, system requirements, installation modes (interactive, silent, unattended preload), available command line options, installation process, and troubleshooting.
Fedora Atomic Workshop handout for Fudcon Pune 2015rranjithrajaram
This document provides instructions for deploying and using Fedora Atomic Host, an operating system designed for containers. It includes steps to:
1) Configure Fedora Atomic images using cloud-init files to set usernames, passwords, and hostnames.
2) Upgrade and rollback the Atomic host using rpm-ostree commands.
3) Understand how OSTree manages operating system updates and deployments.
4) Deploy Docker containers on the Atomic host and use Cockpit to manage containers.
Controller Area Network (CAN) is a serial communication protocol that is most commonly used in automotive applications. It allows microcontrollers and devices to communicate with each other in real-time. CAN uses a multi-master broadcast communication style where nodes can transmit messages at any time and all nodes receive all messages. It uses priority-based arbitration to determine which message is transmitted when two nodes transmit simultaneously. CAN provides efficient, reliable, and economical communication between sensors, actuators and electronic control units in automotive and other embedded systems applications.
This project has been funded with support from the European Commission.
This publication reflects the views only of the author, and the
Commission cannot be held responsible for any use which may be made of the information contained therein.
The document summarizes steps taken to update the database (db) nodes on an Exadata system from software version 11.2.3.2.1 to 11.2.3.3.0 using the dbnodeupdate.sh utility. It provides details of prerequisites, running the utility in update mode with the -u flag and specified media source, and validations performed during the process including dependency checks. The summary includes checking for known issues, collecting diagnostics, and noting next steps after upgrade completion.
Harry Hartland analyzed the results of a survey about magazine design. Question 1 found that the audience prefers red and black color schemes. Question 2 showed that 6 photos on the contents page is best. Question 3 was close but a low angle shot is more conventional. Question 4 confirmed that readers expect puffs. Question 5 found mixed placement of photos and text is balanced. Question 6 showed front covers should not be cluttered. Question 7 revealed the importance of cover and contents typography. Question 8 covered using different fonts. Question 9 disagreed that pictures should outweigh text. Question 10 confirmed the subject should make eye contact. Overall, the survey provided useful guidance for Harry's magazine design.
This document provides instructions for upgrading or downgrading the software on a TCU (Telecommunications Control Unit) using a SolarWind SFTP server. It describes how to configure the SFTP server by setting the TCP port, IP address, and file storage location. It then lists the steps to check the current TCU software revision, start an upgrade session, download the new software file from the SFTP server, check the download status, activate the new software, end the upgrade session, and check the software revision after completion.
This document provides instructions for installing Oracle Database Client 12c on IBM AIX on POWER Systems (64-bit). It describes reviewing information, logging in as root, configuring servers, checking requirements and installing Oracle software. Operating system requirements include supported versions of AIX 6.1, 7.1 and 7.2, required filesets and APAR fixes. Additional drivers, software and requirements for connectivity, messaging and programming environments are also listed.
This document outlines the steps to install AIX on Power servers using a NIM server. It describes powering on the HMC and configuring its IP addresses. LPARs are then created on the Power servers and connected to the HMC. AIX is installed on the LPARs by booting from media and navigating the installation steps. SSH is enabled and the NIM master server is configured by installing filesets and defining the NIM environment. A standalone NIM client is added and connectivity is tested between the client and NIM server using SMS ping.
This document discusses Automotive Embedded Systems and the AUTOSAR Application Layer. It covers topics like use cases in AUTOSAR, AUTOSAR basic software modules, the AUTOSAR system design process, software components, runnables, events, and the internal behavior of software components. Diagrams and examples are provided to illustrate concepts like software component types, the relationship between software components and runnables, event types that can trigger runnables, and how a timing event is defined in XML.
LCU13: Deep Dive into ARM Trusted Firmware
Resource: LCU13
Name: Deep Dive into ARM Trusted Firmware
Date: 31-10-2013
Speaker: Dan Handley / Charles Garcia-Tobin
Linux provides a common mailbox framework for communication between controller and client drivers. The framework includes mailbox_controller and mailbox_client header files. Several device drivers implement this framework for communication with hardware mailboxes, including drivers for ARM MHU, Broadcom, Altera, STMicro, and TI mailboxes. The mailbox framework supports synchronous and asynchronous message notification and defines mailbox channel operations for sending/receiving data and initializing/shutting down channels. ARM's SCPI protocol is commonly used with the mailbox framework for communication between application and system control processors over an MHU. The Linux kernel documentation describes supporting the SCPI protocol via the mailbox framework and device tree bindings.
IBM Lotusphere 2012 Show301: Leveraging the Sametime Proxy to support Mobile ...William Holmes
This document discusses deploying and configuring the IBM Sametime proxy server. It begins with an agenda that covers prerequisites, planning the deployment architecture, installation, configuration, and supporting mobile devices and applications. Key points include that the proxy server requires IBM WebSphere Application Server and a Sametime community server. The proxy connects to the community server on port 1516 and supports single sign-on. Deployment types include a single server, clustered, or using a load balancer. The document provides installation and configuration instructions for upgrading the system console and proxy servers to a new release.
This document discusses the AUTOSAR application layer. It explains that the application layer provides the system functionality through software components (SWCs) that contain software. The document outlines different types of SWCs and their elements like ports, runnable entities, and events. It also discusses how SWCs communicate internally and across ECUs using the virtual functional bus. The mapping of runnable entities to operating system tasks is mentioned as the topic for the next session.
This document provides information about administering ColdFusion MX servers. It discusses ColdFusion editions and configurations, installing and connecting the ColdFusion server to a web server, managing datasources and databases, monitoring server activity, and tuning server settings.
SFO15-TR9: PSCI, ACPI (and UEFI to boot)
Speaker: Bill Fletcher
Date: September 24, 2015
★ Session Description ★
An introductory session of a system-level overview at Power State Coordination
- Focus on ARMv8
- Goes top-down from ACPI
- A demo based on the current code in qemu
- The specifications are very dynamic - what’s onging for ACPI and PSCI
★ Resources ★
Video: https://www.youtube.com/watch?v=vXzPdpaZVto
Presentation: http://www.slideshare.net/linaroorg/sfo15tr9-psci-acpi-and-uefi-to-boot
Etherpad: pad.linaro.org/p/sfo15-tr9
Pathable: https://sfo15.pathable.com/meetings/303087
★ Event Details ★
Linaro Connect San Francisco 2015 - #SFO15
September 21-25, 2015
Hyatt Regency Hotel
http://www.linaro.org
http://connect.linaro.org
In recent years, we have been witnessing a steady increase in security vulnerabilities in firmware. Nearly all of these issues require local (often privileged) or physical access to exploit. In this talk, we will present novel *remote* attacks on system firmware.
In this talk, we will show different remote attack vectors into system firmware, including networking, updates over the Internet, and error reporting. We will also be demonstrating and remotely exploiting vulnerabilities in different UEFI firmware implementations which can lead to installing persistent implants remotely at scale. The proof-of-concept exploit is less than 800 bytes.
How can we defend against such firmware attacks? We will analyze the remotely exploitable UEFI and BMC attack surface of modern systems, explain specific mitigations for the discussed vulnerabilities, and provide recommendations to detect such attacks and discover compromised systems.
The document provides a step-by-step guide for installing Oracle Business Intelligence 11g on Linux. It outlines downloading required software, preparing the Linux machine, installing Oracle Database, Java, the Repository Creation Utility, WebLogic Server, and BI software. It also describes configuring the BI installation and middleware.
Slide deck for my presentation at the Google Developer Group San Francisco. Step-by-step guide to turning a ThinkPad X220 into a Chromium OS Android development machine. Covers hardware, firmware and software upgrades. Dynamic up-to-date slides at https://goo.gl/ivaugY
My presentation for Google Developer Group San Francisco. Step-by-step guide to turning a ThinkPad X220 into a Chromium OS Android development machine. Covers flashing modified Coreboot firmware, building and installing Chromium OS from source, and hardware upgrades.
Updated slides at https://goo.gl/ivaugY
This document discusses Controller Area Network (CAN) which is a vehicle bus standard that allows microcontrollers and devices to communicate with each other within a vehicle without a host computer. It covers the general characteristics of CAN including its event-driven nature, bus arbitration, message filtering, and the different types of CAN messages including data frames, remote frames, error frames, and overload frames. The document provides detailed explanations and illustrations of the fields that make up CAN data frames.
This document provides information about the Intel(R) Chipset Software Installation Utility version 7.0.0.1025, which is designed to install Windows INF files to configure Intel chipset components like PCI support, storage support, and USB support. It discusses the product details, system requirements, installation modes (interactive, silent, unattended preload), available command line options, installation process, and troubleshooting.
Fedora Atomic Workshop handout for Fudcon Pune 2015rranjithrajaram
This document provides instructions for deploying and using Fedora Atomic Host, an operating system designed for containers. It includes steps to:
1) Configure Fedora Atomic images using cloud-init files to set usernames, passwords, and hostnames.
2) Upgrade and rollback the Atomic host using rpm-ostree commands.
3) Understand how OSTree manages operating system updates and deployments.
4) Deploy Docker containers on the Atomic host and use Cockpit to manage containers.
Controller Area Network (CAN) is a serial communication protocol that is most commonly used in automotive applications. It allows microcontrollers and devices to communicate with each other in real-time. CAN uses a multi-master broadcast communication style where nodes can transmit messages at any time and all nodes receive all messages. It uses priority-based arbitration to determine which message is transmitted when two nodes transmit simultaneously. CAN provides efficient, reliable, and economical communication between sensors, actuators and electronic control units in automotive and other embedded systems applications.
This project has been funded with support from the European Commission.
This publication reflects the views only of the author, and the
Commission cannot be held responsible for any use which may be made of the information contained therein.
The document summarizes steps taken to update the database (db) nodes on an Exadata system from software version 11.2.3.2.1 to 11.2.3.3.0 using the dbnodeupdate.sh utility. It provides details of prerequisites, running the utility in update mode with the -u flag and specified media source, and validations performed during the process including dependency checks. The summary includes checking for known issues, collecting diagnostics, and noting next steps after upgrade completion.
Harry Hartland analyzed the results of a survey about magazine design. Question 1 found that the audience prefers red and black color schemes. Question 2 showed that 6 photos on the contents page is best. Question 3 was close but a low angle shot is more conventional. Question 4 confirmed that readers expect puffs. Question 5 found mixed placement of photos and text is balanced. Question 6 showed front covers should not be cluttered. Question 7 revealed the importance of cover and contents typography. Question 8 covered using different fonts. Question 9 disagreed that pictures should outweigh text. Question 10 confirmed the subject should make eye contact. Overall, the survey provided useful guidance for Harry's magazine design.
UK Spectrum Policy Forum - Luigi Ardito, Qualcomm - The future of mobile broa...techUK
UK Spectrum Policy Forum
Cluster 2 Meeting – 24 July 2014
Luigi Ardito, Senior Manager for Government Affairs, Qualcomm
The future of mobile broadband – Spectrum
More information at: http://www.techuk.org/about/uk-spectrum-policy-forum
All rights reserved
La estética en el fútbol - Diego LatorreDiego Menino
El documento resume que la estética en el fútbol no es una búsqueda o objetivo, sino una consecuencia de jugar bien. Ningún entrenador enseña a "jugar lindo" ni es una aspiración de los jugadores. La estética aparece cuando el estilo de juego alcanza la excelencia, no es algo que se busca intencionalmente. Además, no existe una disyuntiva entre jugar lindo y perder o jugar feo y ganar; los equipos entrenan para jugar lo mejor posible, no necesariamente lo más
El anciano Labon coloca ratoneras y muebles en el techo de su casa para atrapar a los ratones que lo molestaban. Los ratones, confundidos al ver el "suelo" en el techo, comienzan a sentirse mareados y desmayarse al ponerse cabeza abajo, creyendo que estaban de pie. Al día siguiente, Labon encuentra el suelo lleno de ratones desmayados.
Turkey sees space as a strategic priority and tool for development. The document outlines Turkey's growing involvement in space activities over the past 20 years. It summarizes Turkey's potential in space and involvement in international programs. While Turkey has lagged behind in space, it now recognizes space as important for protecting civilization and economic development. Turkey is working to develop national space policies and infrastructure to realize its potential and compete internationally in the long run.
Este documento describe un proyecto para medir la altura de cajas que circulan sobre una cinta transportadora utilizando medición láser por triangulación. Se evalúan métodos como ultrasonido y láser para elegir el más apropiado. El método de láser por triangulación usa un láser, cámara y DSP para determinar la ubicación del punto láser e inferir la distancia mediante triangulación. El objetivo es desarrollar un sistema que mida alturas de hasta 60cm con un tiempo de tránsito mayor a 1 segundo.
Este documento describe una propiedad agrícola de 10 hectáreas en venta en la provincia de Huaral, Perú. La tierra está ubicada a 5 minutos de la plaza principal de Huaral y a 5.5 km de la carretera Huaral-Chancay, tiene suelo cultivable y acceso a riego por el río Chancay y agua subterránea. La propiedad tiene luz eléctrica disponible, un camino de acceso independiente y árboles de sauce alrededor del perímetro. Se vende por un precio total de
This document appears to be from a music magazine, as it contains sections for an interview, top 40 charts, and regular columns. While there is limited contextual information provided, the document seems focused on music industry news and content.
ETF Operational Considerations and Developments WebinarNICSA
This document summarizes a panel discussion on ETF operational considerations and developments. The panel discussed trends in the ETF market such as growth drivers and actively managed ETFs. They covered topics like ETF mechanics, the launch process, and ongoing servicing requirements. Attendees were polled on their ETF knowledge and predictions for future growth in ETF assets. The panelists were from State Street Global Services, Brown Brothers Harriman, and PwC.
Together with Alissa Ramsay (MilliCare Textile & Carpet Care), Haley Connor (Pinot's Palette) and Deb Evans (Franchise Foundry), a presentation at the International Franchise Association's 2015 annual convention in February 2015 on creative social media campaigns for franchise marketing.
Smart Beta Investing - Trends and OpportunitiesAmit Sinha
Additional content available at www.focus262.com/blog
Presentation by Amit Sinha at the Copal Amba Breakfast Series that walks through the what, why and where of Smart Beta investing.
Beginning with what is smart beta, then moving to why investors can benefit from smart beta and concluding with where the industry is headed - highlighting the potential market opportunity, challenges, and business models followed by asset managers such as Dimensional, AQR, GSAM, etc.
Mi experiencia con los medios de comunicación ha sido en su mayoría positiva. He aprendido mucho sobre cómo contar historias a través de fotos y videos, y me gusta usar esas habilidades para compartir momentos importantes de mi vida y causas en las que creo. Si bien a veces puede ser abrumador ver mi vida privada expuesta públicamente, en general siento que las redes sociales y los medios me permiten conectarme con otras personas y crear conciencia sobre temas que son importantes para mí.
The document summarizes discussions from an OECD Tax Talks event on international tax issues. It provides updates on the implementation of the BEPS project including country progress, guidance development, and the establishment of an inclusive framework for monitoring and peer review. It also discusses developments in tax transparency, such as the increasing number of countries committing to automatic information exchange. Finally, it outlines collaboration between organizations on domestic resource mobilization and next steps for the international tax agenda.
VNS Vietnam Minerals produces and exports calcium carbonate and limestone products. It operates limestone quarries in Mong Son, Tan Minh, and Quang Ninh with over 50 million tons of reserves. VNS also runs a calcium carbonate processing factory near the Mong Son quarry with a production capacity of 12,000 tons per month. In addition to its core minerals business, VNS invests in and exports various consumer goods.
Supported upgrade paths for forti os 5.0.11samarpitsri
This document provides guidance on upgrading FortiGate firmware versions. It includes a table listing supported upgrade paths between versions. The document scope is limited to FortiGate OS firmware upgrades. It describes how to read the upgrade table and understand FortiGate version numbering. It also notes potential issues to be aware of when upgrading firmware and recommends carefully reviewing release notes.
Motherboard/system firmware refers to the low-level software that controls a storage system's motherboard. On NetApp systems, this is also known as BIOS, CFE, or OFW depending on the model. It is similar to the BIOS firmware on a PC motherboard. To update it, one downloads the latest version from NetApp's support site and transfers it to the system's boot device (CompactFlash card) using commands like download-d or update_flash. Beginning with Data ONTAP 8.0, subsequent BIOS updates are often automatic during booting.
Upgrade to IBM z/OS V2.4 technical actionsMarna Walle
Yes, "upgrade" is the new name for these traditional "migration" sessions! This is part one of a two-part session that will be of interest to System Programmers and their managers who are upgrading to z/OS 2.4 from either z/OS 2.2 or 2.3. It is strongly recommended that you review sessions for a complete upgrade picture.
The general availability date for z/OS V2.4 was September 30, 2019.
Upgrade to IBM z/OS V2.5 technical actionsMarna Walle
Yes, "upgrade" is the new name for these traditional "migration" sessions! This is part one of a two-part session that will be of interest to System Programmers and their managers who are upgrading to z/OS V2.5 from either z/OS V2.3 or V2.4. It is strongly recommended that you review sessions for a complete upgrade picture.
The general availability date for z/OS V2.5 was September 30, 2021.
Orangescrum In App Chat Add-on User ManualOrangescrum
The In-App chat add-on will help you to install the add-on & guide you about the features of chat add-on.
It's a real-time chat widget built for the Orangescrum Community Version. It offers fully secure, single or multi-user chat with private messaging, chat invitations and more.
Explore chat add-on details at: http://www.orangescrum.org/add-on/chat
The document provides instructions for upgrading ESM from version 6.5c to 6.5c SP1. It discusses supported upgrade paths, important log files to reference in case of issues, planning steps like verifying the current ESM installation and opening a support ticket. The main steps include stopping services, running the upgrade installer, and post-upgrade tasks like upgrading connectors and checking existing content.
Oracle forms and reports 11g installation on linuxVenu Palakolanu
The document provides steps to install Oracle Forms and Reports 11g on Linux 5.4. It includes instructions on modifying OS configuration files, installing prerequisite RPM packages, setting up the user oracle and groups, installing Java JDK, unzipping the Forms and Reports software, running the installer, configuring the domain, and starting the servers. It also provides URLs to access the Forms and Reports applications and tips on deploying and running forms.
This document provides best practices for installing Sophos Endpoint Security and Control on-premise. It discusses what software is included, features that require planning like installation locations, update management, and role-based administration. It then describes the installation process and considerations for a single-site network, including deploying management and client software, setting up roles, and designing an update structure tailored to the network size and types of computers.
Control Assistant is a utility that communicates with Woodward controls via serial or Ethernet connections to monitor parameters, view alarms and events, graph and trend data, and perform tunable maintenance. It supports live parameter monitoring and tuning, viewing alarms and events, offline and live trending with user-defined calculation pens and triggers, and importing/exporting data. The SOS Servlink OPC server provides an OPC interface to access data from Woodward controls using the Servlink protocol. Both require Windows XP/Vista/7/8/10 and the .NET framework, and recent versions address crashes, bugs, and compatibility issues.
This document provides instructions for installing a BMC Atrium Discovery virtual appliance in 3 steps:
1) Downloading and installing VMware Server 2.0 to run the virtual appliance.
2) Obtaining the virtual appliance file and expanding it.
3) Adding the virtual appliance to the VMware Server inventory and powering it on.
This document provides release notes for ArcSight ESM version 5.5 Patch 1, including instructions for installing the patch for the ArcSight Database, Manager, Console, and Web components. It describes issues fixed in this patch release and lists open issues. The patch addresses critical issues in ESM v5.5 and provides updates for vulnerability mapping.
This document provides release notes for ArcSight ESM version 6.0c Patch 1. It includes instructions for installing the patch, which addresses critical issues and provides updates for the ArcSight Manager, Console, Web, and CORR-Engine components. Details are given for stopping services, backing up files, downloading and running the patch installer, accepting the license agreement, and restarting services after installation. Issues fixed and open issues still under investigation are also summarized for each component.
This document provides instructions for installing VMWare Tools on CentOS 7. It outlines pre-requisites like installing kernel headers and packages. It describes mounting the CDROM and extracting the installer. The key steps are running the vmware-install.pl script from the installer directory and rebooting the system. Verification involves checking that the vmtoolsd daemon is running. Troubleshooting tips address issues finding ipconfig, a bad perl interpreter, or missing fuse packages. Uninstallation runs the vmware-uninstall-tools script.
This document provides instructions for upgrading the ArcSight database components from version 5.0 SP1 or SP2 to version 5.2. It describes preparing the Oracle database software, verifying the readiness of the existing database, and running the database installer to upgrade the database schema and partition archiver service. Post-upgrade steps include transferring partition archiver settings and completing additional tasks on AIX platforms.
The upgrade process begins by stopping all services, extracting the upgrade files, and opening required TCP ports. The user then runs the upgrade binary file and confirms the upgrade. The upgrade performs pre-checks and upgrades components in the following order - Logger, Manager, Web, and Services. Finally, post-upgrade tasks include upgrading connectors and checking customized content. Any issues encountered should be addressed by reviewing upgrade logs and contacting HP support.
Upgrading ArcSight Express 3.0 to ArcSight Express 4.0Protect724v2
This document provides instructions for upgrading ArcSight Express from version 3.0 to 4.0. It describes downloading the upgrade file, verifying the file, and running the upgrade process. Post-upgrade steps include configuring connectors and verifying content. A trial version of Reputation Security Monitor is included in version 4.0.
The document provides instructions for upgrading from ESM version 5.5 to 5.6. It outlines the following high-level steps:
1. Preparing existing content and downloading necessary installation files and scripts.
2. Upgrading the ArcSight database components and Oracle database software.
3. Upgrading the ArcSight Manager, Console, and Web applications.
4. Checking the state of existing content and upgrading SmartConnectors after the upgrade is complete.
It also provides guidance for upgrading hierarchical or multi-manager ESM installations.
Installing and using the omni pcx enterprise pc installer v2.26 softwareNuno Torres
This document provides instructions for installing and using the OmniPCX Enterprise PC Installer V2.26 software. It describes how to install versions, patches, Linux on inactive partitions, and binaries on OmniPCX Enterprise Releases 5.1.x, 6.x and higher. The installation is performed using the setup.exe file and involves selecting options like installation type, call server type, and network configuration. The document also provides details on uninstalling, managing servers, and known restrictions for the software.
Credentials and VM Installation - Basic course.pdfShubham Sidana
This document provides instructions for downloading and installing a virtual machine (VM) containing ABBYY FlexiCapture 12 for training purposes. It includes details on:
- Credentials and links to download the VM files, training materials, and license file
- Creating folders to store the downloaded files
- Downloading and extracting the VM files using a provided executable file
- Importing and launching the VM using virtualization software like VMware or VirtualBox
- Activating the ABBYY FlexiCapture 12 license on the VM
- Answers to frequently asked questions about downloading, extraction, and virtualization software configuration
The document provides instructions for upgrading an HP ArcSight ESM installation from version 6.0c or 6.5c SP1 to version 6.8c. It outlines important prerequisites like backing up data and freeing up disk space. The upgrade process involves untarring the installation file, stopping ArcSight services, running the upgrade script, and completing post-upgrade tasks like upgrading connectors and checking existing content. The document provides detailed steps and cautions at each phase of the upgrade process.
Westermo propose une gamme complète de solutions de communication de données pour des applications exigeantes dans des secteurs tels que les transports et les marchés de l’eau et de l'énergie.
Cette fiche applicative présente la configuration du routage dynamique avec le protocole OSPF. Vous devez avoir auparavant lu la fiche « Création de réseaux et des réseaux virtuels VLAN ».
Reliez votre Smartphone/Tablette aux routeurs #Westermo.
Cette fiche applicative présente la configuration d’un VPN IPSec de type accès distant entre un routeur MRD 4/3xx ou WeOS et le client NCP
WeOS création de réseaux et de réseaux virtuels VLANFabian Vandendyck
Cette fiche applicative présente la création de réseaux dans un switch Westermo. Nous aborderons tout d’abord la configuration des réseaux virtuels VLAN et nous expliquerons à partir d’eux comment créer des réseaux routés.
The document provides information on Westermo's product range of industrial Ethernet switches. It summarizes that Westermo provides a full range of managed and unmanaged, industrial Ethernet switches designed to withstand harsh environments. It also lists several specific managed switch models along with their key features such as port types and speeds, operating voltage/temperature ranges, and management capabilities.
Cette fiche applicative présente la configuration du routage statique multicast dans les équipements WeOS.
Le multicast est un type de communication basée sur le principe d’abonnement à un flux. Un groupe de machines clientes traite l’unique flux de paquets issu d’un serveur multicast.
Cela évite de surcharger le réseau puisque les paquets ne sont pas distribués à toutes les machines du réseau mais seulement à celle qui en ont besoin.
Ensure reliable mission critical networks.
The drive for greater business efficiency and customer satisfaction, coupled with the desire for a smaller environmental footprint is creating new networking challenges for many companies.
Cette fiche applicative présente la fonctionnalité du Dual Homing qui permet de mettre en oeuvre de la résilience à partir d’un seul switch.
Plusieurs architectures sont possibles et vous seront présentées par la
suite.
This document provides instructions for configuring multicast routing between two separate networks using IPSec VPN tunnels and GRE tunnels. It describes creating the necessary interfaces, configuring the IPSec and GRE tunnels between the routers, enabling OSPF routing, configuring static multicast routing, and verifying connectivity for multicast traffic passing through the tunnels.
Cette fiche applicative est la suite de la fiche « Génération de certificats SSL ». Elle présente la configuration d’un tunnel OpenVPN SSL entre un routeur WeOS Westermo et le client SecurePoint SSL VPN.
Les certificats sont des fichiers informatiques qui participent à un processus d’authentification et qui associent une clé publique à son propriétaire.
WeOS est l’acronyme de « Westermo Operating System » : c’est un système d’exploitation conçu et développé
par notre société afin de répondre aux besoins des réseaux industriels d’aujourd’hui et de demain.
Cette fiche applicative présente la configuration d’une zone démilitarisée ou DMZ. Celle-ci permet de rendre accessible des services tels que le serveur web ou la messagerie aux personnes se trouvant soit dans
l’entreprise ou à l’extérieur de celle-ci.
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
This presentation was provided by Rebecca Benner, Ph.D., of the American Society of Anesthesiologists, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
The chapter Lifelines of National Economy in Class 10 Geography focuses on the various modes of transportation and communication that play a vital role in the economic development of a country. These lifelines are crucial for the movement of goods, services, and people, thereby connecting different regions and promoting economic activities.
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
LAND USE LAND COVER AND NDVI OF MIRZAPUR DISTRICT, UPRAHUL
This Dissertation explores the particular circumstances of Mirzapur, a region located in the
core of India. Mirzapur, with its varied terrains and abundant biodiversity, offers an optimal
environment for investigating the changes in vegetation cover dynamics. Our study utilizes
advanced technologies such as GIS (Geographic Information Systems) and Remote sensing to
analyze the transformations that have taken place over the course of a decade.
The complex relationship between human activities and the environment has been the focus
of extensive research and worry. As the global community grapples with swift urbanization,
population expansion, and economic progress, the effects on natural ecosystems are becoming
more evident. A crucial element of this impact is the alteration of vegetation cover, which plays a
significant role in maintaining the ecological equilibrium of our planet.Land serves as the foundation for all human activities and provides the necessary materials for
these activities. As the most crucial natural resource, its utilization by humans results in different
'Land uses,' which are determined by both human activities and the physical characteristics of the
land.
The utilization of land is impacted by human needs and environmental factors. In countries
like India, rapid population growth and the emphasis on extensive resource exploitation can lead
to significant land degradation, adversely affecting the region's land cover.
Therefore, human intervention has significantly influenced land use patterns over many
centuries, evolving its structure over time and space. In the present era, these changes have
accelerated due to factors such as agriculture and urbanization. Information regarding land use and
cover is essential for various planning and management tasks related to the Earth's surface,
providing crucial environmental data for scientific, resource management, policy purposes, and
diverse human activities.
Accurate understanding of land use and cover is imperative for the development planning
of any area. Consequently, a wide range of professionals, including earth system scientists, land
and water managers, and urban planners, are interested in obtaining data on land use and cover
changes, conversion trends, and other related patterns. The spatial dimensions of land use and
cover support policymakers and scientists in making well-informed decisions, as alterations in
these patterns indicate shifts in economic and social conditions. Monitoring such changes with the
help of Advanced technologies like Remote Sensing and Geographic Information Systems is
crucial for coordinated efforts across different administrative levels. Advanced technologies like
Remote Sensing and Geographic Information Systems
9
Changes in vegetation cover refer to variations in the distribution, composition, and overall
structure of plant communities across different temporal and spatial scales. These changes can
occur natural.
2. TechNote002-WeOS Upgrade ver1.0-rev.00
Table of Contents
Aim………………………………………………………………………………………………………………………………………………………………………………………………...3
Introduction……………………………………………………………………………………………………………………………………………………… 3
The WeOS Firmware………………………………………………………………………………………………………………………………………... 4
The .pkg File……………………………………………………………………………………………………………………………………………………..4
All WeOS Feature Releases so far in Chronological Order…………...……..4
1. Determining Firmware Versions………………………………………………………………………………………….. 5
2. Choose Upgrade Procedure……………………………………………………………………………………………………….. 6
WEB Upgrade Using CGI………………………………………………………………………………………………………………….7
WEB Upgrade Using FTP/TFTP………………………………………………………………………………………………..8
Notes on Upgrading from CLI…………………………………………………………………………………………………….9
CLI Upgrade Using FTP/TFTP…………………………………………………………………………………………………….10
CLI Upgrade Using USB…………………………………………………………………………………………………………………….11
3. Multiple Version Upgrade Procedures……………………………………………………………………....12
Multiple Version Upgrade with Factory Default Configuration….……. 12
Multiple Version Upgrade Keeping the Configuration…………..…………………… 13
Upgrading Early RedFox Units Using WeOS 4.0.0…………………………………………14
Boot Loader Upgrade……………………………………………………………………………………………………………………………………..15
Downgrade………………………………………………………………………………………………………………………………………………………………………. 16
Insufficient RAM-memory for Upgrade…………………………………………………………………………..… 17
Appendix…………………………………………………………………………………………………………………………………………………………………………….. 18
Setting up a TFTP Server…………………………………………………………………………………………………………………18
Configuration Saving…………………………………………………………………………………………………………………………… 19
Save the Configuration from the CLI……………………………………………………………………………..19
Save the Configuration from the WEB Interface………………………………………………….19
Configuration Backup…………………………………………………………………………………………………………………………. 20
Backup the Configuration from the WEB Interface…………………………………………..20
Backup the Configuration from the CLI………………………………………………………………………20
Configuration Restore………………………………………………………………………………………………………………………… 21
Restore the Configuration from the WEB Interface…………………………………………. 21
Restore the Configuration from the CLI…………………………………………………………………….. 21
Factory Reset……………………………………………………………………………………………………………………………….…………………22
Factory Reset from the CLI…………………………………………………………………………………………………… 22
Factory Reset from the WEB Interface…………………...…………………………………………………... 22
www.westermo.com page 2
3. TechNote002-WeOS Upgrade ver1.0-rev.00
Aim
The Westermo Operating System (WeOS) was first released in 2009 with version 4.0.0.
Fifteen feature releases later and with a whole lot of new functionality added since then, it
becomes more important to know how to correctly upgrade WeOS units to ensure proper
configuration functionality between the releases.
WeOS are able to support configuration syntax changes from one feature release to the
next. This is so that the old syntax from the previous release can be parsed correctly into
the new release. In this way a WeOS unit can be upgraded one step without having to be
reconfigured after the upgrade.
For example when upgrading from 4.12.1 to 4.13.4 no reconfiguration of the unit is needed
for configuration compatibility between the firmware versions.
A feature release is defined by the figure in the middle of the version number e.g. 4.6.x,
4.12.x, 4.13.x etc. See the full list of all WeOS feature releases on the next page.
No special considerations concerning the configuration compability needs to be taken
when upgrading within a feature release e.g. 4.13.1 to 4.13.4.
Taking into account the above information precautions are needed if an upgrade has to be
made in more than one step and at the same time keep the configuration intact e.g.
upgrading from 4.8.2 to 4.13.4. This procedure is described in detail in the Multiple Version
Upgrade chapter.
Boot loader upgrades are an exception to this as it can be upgraded more than one step at
the time, read more about this in the Boot Loader Upgrade chapter.
Downgrading the firmware is generally not recommended but sometimes it might be
necessary and how to do this is described in the Downgrade chapter.
In the Appendix section the procedures associated with upgrade process are described.
The first part of the document will describe how to make proper preparations for the
upgrade and the different ways an upgrade can be executed in WeOS.
Please Note! Always look through the Release Notes, it will describe the new
features, fixed issues and known issues of a firmware release. Any problem
reporting should be based on the latest official WeOS release.
All examples and screen dumps in this document are made with WeOS version 4.13.4.
This document will handle all types of upgrade procedures supported by WeOS and how to
correctly execute an upgrade based on different scenarios.
Introduction
www.westermo.com page 3
4. TechNote002-WeOS Upgrade ver1.0-rev.00
The WeOS Firmware
The latest firmware release is available from the Westermo homepage at
www.westermo.com
Also all previously released versions are available here in the history files.
All WeOS Feature Releases so far in Chronological Order
00) 4.0.0 .img
01) customer specific release
02) 4.2.1 .img
03) 4.3.0 .img
04) 4.4.0 .img
05) 4.5.1 .img
06) 4.6.2 .img
07) customer specific release
08) 4.8.2 .img
09) 4.9.2 .img
10) customer specific release
11) 4.11.2 .img
12) 4.12.1 .img
13) 4.13.4 .img and .pkg
14) 4.14.2 .pkg
Before WeOS version 4.13.x all firmware files were distributed as separate .img and .bin
files.
The .img is the WeOS firmware file and the .bin file is the boot loader firmware.
All WeOS product groups had its own set of these files named after its group.
RedFox: rwXXXX.img xscale-redboot-YYY.bin
Lynx and Viper:lwXXXX.img imx27-redboot-ZZZ.bin
Wolverine: wwXXXX.img imx27-redboot-ZZZ.bin
Falcon: fwXXXX.img imx27-redboot-ZZZ.bin
From WeOS 4.13.x this was changed to a unified file containing all the WeOS product’s
firmware and boot loader images. It does not matter if there is a boot loader upgrade or a
firmware upgrade that needs to be done, only one file is needed, the .pkg file.
When upgrading from a firmware version previous to 4.13.x to versions above 4.13.x there
always have to be an intermediate step to 4.13.x to turn the upgrade procedure to the .pkg
type of upgrade. See the Multiple Version Upgrade section for more details.
The upgrade procedure is the same no matter if it is done with .img, .bin or a .pkg file.
The .pkg File
www.westermo.com page 4
5. TechNote002-WeOS Upgrade ver1.0-rev.00
1. Determining Firmware Versions
WeOS have a primary and a backup firmware and also a boot loader firmware, which is
handled later in the Boot Loader Upgrade chapter.
The primary firmware contains the main system software which is used by the switch at
normal startup.
The backup firmware is loaded in case an error (such as a check-sum error) occurs while
loading the primary firmware.
Please Note! It is strongly recommended to use the same version on both the
primary and backup firmware. This is to ensure the same interpretation of the
configuration file if a failover to the backup firmware is needed.
The firmware versions used by the switch can be seen in the WEB interface by going to
Status -> System -> Details:
and in the CLI using the show system-information command:
www.westermo.com page 5
6. TechNote002-WeOS Upgrade ver1.0-rev.00
2. Choose Upgrade Procedure
WeOS can be upgraded from the CLI and from the WEB interface using FTP or TFTP.
WEB interface upgrade also allows for CGI upload from the WEB browser directly so no
external FTP or TFTP servers are needed.
A USB upgrade is also supported from the CLI.
www.westermo.com page 6
7. TechNote002-WeOS Upgrade ver1.0-rev.00
WEB Upgrade Using CGI
Upgrading from the WEB interface using CGI does not require any additional measures as
long as the WEB interface can be reached for configuration.
To upgrade using WEB and CGI upload use these steps:
1) Make a backup copy of the configuration, see appendix for instructions.
2) Do this procedure first for the Backup firmware, then for the Primary firmware.
3) Go to Maintenance -> F/W Upgrade -> and click Enable File Upload.
4) Choose the firmware file to upgrade to.
5) State if it is the Backup or Primary firmware that should be upgraded.
6) Start the upgrade by clicking the Upgrade button.
7) After the upgrade has completed it is possible to verify that the correct firmware version
is active by going to Status -> System -> Details, see the chapter Determining
Firmware Versions
8) Complete the process by saving the configuration, see appendix for instructions.
This status output is
from the pre 4.13.x
releases.
After the upgrade has
finished successfully
the WeOS unit will
reboot.
3.
4.
5.
6.
www.westermo.com page 7
8. TechNote002-WeOS Upgrade ver1.0-rev.00
When upgrading from a FTP/TFTP server the WeOS unit will download its firmware file
from the server, so any firewalls or routers in the path must allow this traffic to pass.
To FTP/TFTP upgrade from the WEB follow these steps:
1) Make a backup copy of the configuration, see appendix for instructions.
2) Do this procedure first for the Backup firmware, then for the Primary firmware.
3) Go to Maintenance -> F/W Upgrade -> FTP/TFTP Upgrade.
4) Add the firmware file to be downloaded for the upgrade.
5) State the IP-address of the FTP or TFTP server used.
6) Choose if it is the Backup or Primary firmware that shall be upgraded.
7) Click the Upgrade button to start upgrading.
8) After the upgrade has completed it is possible to verify that the correct firmware version
is active by going to Status -> System -> Details, see the chapter Determining
Firmware Versions
9) Complete the process by saving the configuration, see appendix for instructions.
WEB Upgrade Using FTP/TFTP
The WeOS unit will
first try FTP and then
TFTP if no FTP server
is available.
Please note that when using TFTP upgrade
with .pkg files the TFTP server must support
large files as defined in RFC2347.
This status output is
from the 4.13 release.
After the upgrade has
finished successfully
the WeOS unit will
reboot.
7.
6.
5.
4.
3.
www.westermo.com page 8
9. TechNote002-WeOS Upgrade ver1.0-rev.00
Notes on Upgrading from the CLI
There are three possible ways to upgrade the firmware from the CLI, by using FTP, TFTP
or USB and they all use the upgrade command:
upgrade <pri|sec|boot> <[URI://][ADDRESS[:PORT]/]FILE | ADDRESS FILE]>
For more detailed information about this command use help upgrade from the CLI prompt.
When upgrading from the CLI several upgrades can be made before a reboot is forced.
This is different from the WEB upgrade where a reboot is forced after each upgrade
performed.
When upgrading in the sequential order described below the unit will not reboot until the
Primary firmware is upgraded.
Please Note! That the utput from show system-information will not show any
changes until a reboot is made.
Please Note! In the CLI the Backup firmware is named Secondary firmware.
1) Upgrade the Boot loader firmware if neccessary, see the Boot Loader Upgrade chapter
first!
2) Upgrade the Backup (secondary) firmware.
3) Upgrade the Primary firmware and a reboot will follow this command.
www.westermo.com page 9
10. TechNote002-WeOS Upgrade ver1.0-rev.00
When upgrading from a FTP or TFTP server the WeOS unit will download its firmware file
from the server, so any firewalls or routers in the path must allow this traffic to pass.
Execute the FTP/TFTP upgrade using these steps:
1) Make a backup copy of the configuration, see appendix for instructions.
2) Make sure the FTP/TFTP server is ready, see appendix for tftp instructions.
3) Excecute the upgrade command for the Backup (secondary) firmware, e.g.
upgrade secondary tftp://192.168.2.70/WeOS-4.13.4.pkg
4) Excecute the upgrade command for the Primary firmware, e.g.
upgrade primary tftp://192.168.2.70/WeOS-4.13.4.pkg
5) After the upgrade has completed it is possible to verify with the show system-information
command that the correct firmware version is active, see the chapter Determining
Firmware Versions
6) Complete the process by saving the configuration, see appendix for instructions.
Examples:
upgrade secondary ftp://192.168.2.70/lw4134.img
upgrade primary tftp://192.168.2.70/WeOS-4.13.4.pkg
CLI Upgrade Using FTP/TFTP
www.westermo.com page 10
11. TechNote002-WeOS Upgrade ver1.0-rev.00
CLI Upgrade Using USB
When upgrading using USB the USB-stick must be prepared according to the following:
- Be partitioned
- Be formatted as VFAT or FAT32 on the first partition
Otherwise WeOS might not be able to read the firmware file from the USB-stick.
To execute the USB upgrade use these steps:
1) Make a backup copy of the configuration, see appendix for instructions.
2) Make sure the USB-stick is prepared, loaded with the firmware file and inserted into the
unit.
3) Excecute the upgrade command for the Backup (secondary) firmware, e.g.
upgrade secondary usb://WeOS-Firmware/WeOS-4.13.4.pkg.
4) Excecute the upgrade command for the Primary firmware, e.g.
upgrade primary usb://WeOS-Firmware/WeOS-4.13.4.pkg.
5) After the upgrade has completed it is possible to verify with the show system-information
command that the correct firmware version is active, see the chapter Determining
Firmware Versions
6) Complete the process by saving the configuration, see appendix for instructions.
Example:
upgrade primary usb://WeOS-Firmware/WeOS-4.13.4.pkg
www.westermo.com page 11
12. TechNote002-WeOS Upgrade ver1.0-rev.00
3. Multiple Version Upgrade Procedures
WeOS supports configuration compatibility when upgrading to the next feature release, see
the Introduction section for the feature release definition.
When a WeOS unit must be upgraded several feature releases and keeping the
configuration, steps must be taken inorder to ensure that the configuration is compatible
with the new firmware version.
There are two ways to upgrade multiple firmware versions, either with a cleared
configuration i.e. factory defaulting the unit after upgrade or upgrade keeping the
configuration compatible between the firmware versions by upgrading step by step.
Multiple Version Upgrade with Factory Default Configuration
The quickest upgrade procedure when upgrading several WeOS releases is to do a Factory
Reset after the upgrade has finished. In this way the upgrade can be done in one step
going directly to the desired firmware version. Although it also means that all configuration
settings on the unit will be erased so a new configuration must be made on the new
firmware version.
Please Note! When upgrading multiple versions, upgrade first the Primary firmware
and then the Backup firmware, as the Backup firmware do not have to consider the
configuration aspects of the upgrade
Please Note! From 4.14.x only the .pkg file upgrade is supported. So when upgrading
from any release previous 4.13.x all upgrades must first be to 4.13.4 in order to get
the .pkg upgrade support.
To upgrade in this way follow these steps:
1) For releases previous to 4.13.x upgrade the Primary firmware directly to 4.13.4 using
one of the methods described in the Choose Upgrade Procedure chapter,
e.g. 4.6.2 -> 4.13.4 with the .img file.
2) Then upgrade the Primary firmware directly to the firmware version above 4.13.x that is
wanted using one of the methods described in the Choose Upgrade Procedure chapter,
e.g. 4.13.4 -> 4.14.2 with the .pkg file.
3) Upgrade the Backup firmware directly to the new firmware version, e.g. 4.6.2 -> 4.14.2.
4) When the upgrade has finished perform a Factory Reset so all configuration settings are
reset and the new factory default settings are activated.
5) Redo the configuration on the new firmware version.
www.westermo.com page 12
13. TechNote002-WeOS Upgrade ver1.0-rev.00
Multiple Version Upgrade Keeping the Configuration
To keep the configuration from an old firmware compatible with a new firmware when
upgrading WeOS over multiple versions, the upgrade must be done in a step by step
manner. Going from feature release to feature release will ensure configuration
compatibility.
At each step of a feature release upgrade the configuration needs to be saved in the new
firmware format.
See the Introduction section for the definition of a feature release.
Please Note! When upgrading multiple versions, upgrade first the Primary firmware
and then the Backup firmware, as the Backup firmware do not have to consider the
configuration aspects of the upgrade.
In order to keep the configuration, upgrade using these steps:
1) Upgrade the Primary firmware to the next feature release in the list using one of the
methods described in the Choose Upgrade Procedure chapter.
2) When the upgrade has finished save the configuration via CLI or WEB, see appendix.
3) Repeat the procedure until the version needed is reached.
4) Then upgrade the Backup firmware directly to the new firmware version.
Example:
1) Upgrade Primary firmware 4.9.2 -> 4.11.2 using the .img file.
2) Save the configuration.
3) Upgrade Primary firmware 4.11.2 -> 4.12.1. using the .img file.
4) Save the configuration.
5) Upgrade Primary firmware 4.12.1 -> 4.13.4. using the .img file.
6) Save the configuration.
7) Upgrade Primary firmware 4.13.4 -> 4.14.2. using the .pkg file.
8) Save the configuration.
9) Upgrade Backup firmware 4.9.2 -> 4.14.2 using the .pkg file, in this case the unit
understands .pkg files as it’s Primary firmware is already upgraded to 4.14.2
Through this procedure the configuration of the unit is now kept compatible all the way from
4.9.2 to 4.14.2.
www.westermo.com page 13
14. TechNote002-WeOS Upgrade ver1.0-rev.00
Upgrading Early RedFox Units Using WeOS 4.0.0
Early RedFox units (Industrial and Rail) delivered with WeOS 4.0.0, comes with
a flash memory partition unsuitable for the larger firmware image size of WeOS
4.3.x and later.
If the RedFox unit have an article number and a serial number that fits the table below a
partition table upgrade is needed, otherwise this section can be ignored:
To find out the units model, article number and the serial number go to Status -> System ->
Details in the WEB interface or issue the command show system-information in the CLI.
Please Note!
Updating the flash partition table will corrupt your system!
Configuration files, certificates and backup image will be destroyed.
Please Note!
Although this update facility has been tested extensively by Westermo there
are no guarantees it will work flawlessly for all use cases.
Therefore, we do not recommend this action on active running units in the
field. Instead, replace the unit with a spare one first.
Update the flash table using these steps:
1) Backup your .cfg files, startup-config and any certificate files to a USB-stick or remote
(T)FTP/SCP server.
2) If you are running WeOS version 4.2.0 or later proceed directly to the next step. If you
are running WeOS 4.0.0, you must first upgrade your primary firmware to a later release,
e.g., 4.2.0 or 4.3.0, see the other sections of this document on how to upgrade correctly.
3) Access the CLI via the console port, run the flash-table-update command, and wait for
it to finish. The unit reboots when it has completed the update.
4) Restore configuration files, any necessary certificates and the system backup image.
The flash-table-update command is only available on WeOS 4.2.0 and later, and is only
visible if you have a RedFox with the old partition table.
www.westermo.com page 14
15. TechNote002-WeOS Upgrade ver1.0-rev.00
Boot Loader Upgrade
Please Note! Unless the release notes explicitly recommend it, there is no need to
upgrade the boot loader.
The boot loader firmware can only be upgraded from the CLI using the upgrade command:
upgrade <pri|sec|boot> <[URI://][ADDRESS[:PORT]/]FILE | ADDRESS FILE]>
The current version (updated at boot) is visible in the output from the
show system-information command, see the chapter Determining Firmware Versions
The boot loader firmware does not follow the WeOS firmware version numbers, it has its
own version numbering scheme and it is CPU platform specific, see the section The WeOS
Firmware.
To execute the boot loader upgrade use these steps:
1) Make a backup copy of the configuration, see appendix for instructions.
2) Chose upgrade procedure FTP, TFTP or USB and make sure everything is set.
3) Excecute the upgrade command.
4) Reboot the unit.
5) After the reboot has completed it is possible to verify with the show system-information
command that the correct boot loader version is active, see the chapter Determining
Firmware Versions
Example:
upgrade bootloader tftp://192.168.2.70/imx27-redboot-4.11.bin
upgrade bootloader usb://WeOS-Firmware/WeOS-4.13.4.pkg
www.westermo.com page 15
16. TechNote002-WeOS Upgrade ver1.0-rev.00
Downgrading
Although downgrading is discuraged it might sometimes be neccessary.
The downgrade process is much more complex than upgrading as the new firmware
version will contain several new features that the old firmware is not aware of.
Therefore it is not possible to downgrade with the configuration completely compatible.
This is why it is so important to backup the configuration before upgrading so a downgrade
can be made without having to reconfigure the unit. See the upgrade sections for details on
how to upgrade.
Downgrading is perfomed using these steps:
1) Make sure there is a backed up configuration for the firmware version the unit is to be
downgraded to or be prepared to do a Factory Reset of the unit after downgrade.
2) Execute the downgrade in the same way as the upgrade is performed (but with an older
firmware), see the upgrade sections for details. Example 4.14.2 -> 4.12.1 and please
note, as it is not possible to keep the configuration intact, downgrading in steps is of
no use in this case.
3) When the downgrade is finished perform a Factory Reset of the unit to make sure it has
the factory default settings of the firmware downgraded to, see appendix for details.
4) If desired restore a configuration file saved in the firmware version downgraded to e.g.
4.12.1, see appendix for details.
www.westermo.com page 16
17. TechNote002-WeOS Upgrade ver1.0-rev.00
Insufficient RAM-memory for Upgrade
When a WeOS unit is to be upgraded a RAM-disk will be created in RAM memory where
the firmware image is stored. In some rare cases there might not be enough memory left in
RAM for the RAM-disk to be created. This could happen if a firmware version is used where
there is a memory leakage, see relese notes for information.
In such a case the unit will first try to disable some functions that is not needed for the
upgrade and then it will try to create the RAM-disk again and if that is successful the
upgrade can continue.
But if there is still not enough memory available the upgrade will fail. See picture below.
In this case first try to reboot the unit to clear RAM of unneccessary allocations and then try
the upgrade again.
www.westermo.com page 17
18. TechNote002-WeOS Upgrade ver1.0-rev.00
Setting up a TFTP Server
The TFTPD server software can be downloaded from http://tftpd32.jounin.net.
This particular server does not have to be installed on the computer it will be run from.
Use the Browse
button to add the
folder where the
firmware files are
stored.
Choose the correct
interface on the PC so the
WeOS unit can acces the
firmware file.
Appendix
Please Note! Do not forget to adapt the firewall for the PC that shall run the TFTP
server so the WeOS unit can download it’s firmware file from it.
www.westermo.com page 18
19. TechNote002-WeOS Upgrade ver1.0-rev.00
Configuration Saving
A WeOS unit’s configuration can be saved from either the CLI or the WEB interface.
Save the Configuration from the CLI
The copy command is used for saving the configuration from the CLI.
copy [force] [URI://]<from> [URI://]<to>
Use help copy from the prompt for more information about the copy command.
To save the configuration just execute:
copy running-config startup-config.
Save the Configuration from the WEB Interface
In the WEB interface all configuration changes are saved automatically, however in this
case no configuration changes have been made, only the save is needed.
To do this from the WEB an Apply button needs to be clicked and this will trigger a save of
the running-config to the startup-config.
Any Apply button may be clicked, the example below shows the Configuration -> System ->
Date & Time Apply button.
www.westermo.com page 19
20. TechNote002-WeOS Upgrade ver1.0-rev.00
Configuration Backup
A WeOS unit’s configuration can be backed up from either the CLI or the WEB interface.
Backup the Configuration from the CLI
The copy command is used for configuration backup from the CLI.
copy [force] [URI://]<from> [URI://]<to>
Use help copy from the prompt for more information about the copy command.
The configuration can be saved to the following storage places FTP, TFTP, SCP or USB.
Examples:
copy running-config tftp://192.168.2.70/backup-Wolverine.cfg
copy running-config usb://backup-Wolverine.cfg
Backup the Configuration from the WEB Interface
The configuration can be backed up by going to:
Maintenance -> Backup & Restore and clicking the Backup button in the WEB interface.
www.westermo.com page 20
21. TechNote002-WeOS Upgrade ver1.0-rev.00
Configuration Restore
A WeOS unit’s configuration can be restored from either the CLI or the WEB interface.
Restore the Configuration from the CLI
The copy command is used for configuration restore from the CLI.
copy [force] [URI://]<from> [URI://]<to>
Use help copy from the prompt for more information about the copy command.
The configuration can be restored from the following storage places FTP, TFTP, SCP or
USB. Copy the configuration file to the running-config first to make sure the copy procedure
went well and all settings are correct, then copy it to the startup-config.
Restore a configuration using these steps:
1) Use the copy command e.g.
copy tftp://192.168.2.70/backup_lynx_20140413_1229.cfg running-config
2) Verify the configuration by executing show running-config
3) Save the restored configuration with copy running-config startup-config
Restore the Configuration from the WEB Interface
The configuration can be restored in the WEB interface by going to:
Maintenance -> Backup & Restore, click the Browse button and choose the configuration
file to be restored. Execute by clicking the Restore button.
Verify the configuration by browsing the WEB interface.
www.westermo.com page 21
22. TechNote002-WeOS Upgrade ver1.0-rev.00
Factory Reset
A WeOS unit can be set to factory default from either the CLI or the WEB interface.
Factory Reset from the CLI
Perform a Factory Reset from the CLI using the copy command.
copy [force] [URI://]<from> [URI://]<to>
Use help copy from the prompt for more information about the copy command.
Issue a Factory Reset using these commands:
1) copy factory-config startup-config
2) reboot
Factory Reset from the WEB Interface
To execute a Factory Reset from the WEB interface go to Maintenance -> Factory reset and
click the Reset button.
www.westermo.com page 22