DOCSLIB.ORG

Shelf Manager User Guide (May 15, 2018) Page 1 / 321

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Shelf Manager User Guide (May 15, 2018) Page 1 / 321 User Guide Pigeon Point Shelf Manager Release 3.7.1 May 15, 2018 nVent Schroff GmbH [email protected] www.pigeonpoint.com schroff.nVent.com This document is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by nVent. nVent assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, manual, recording, or otherwise, without the prior written permission of nVent. The Pigeon Point Shelf Manager uses an implementation of the MD5 Message-Digest algorithm that is derived from the RSA Data Security, Inc. MD5 Message-Digest algorithm. All nVent marks and logos are owned or licensed by nVent Services GmbH or its affiliates. All other trademarks are the property of their respective owners. nVent reserves the right to change specifications without notice. Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 1 / 321 Table of contents 1 About this document 9 1.1 Shelf Manager documentation 9 1.1.1 Conventions used in this document 9 1.2 Additional resources 10 2 Introduction 11 2.1 In this section 11 2.2 Intelligent Platform Management: an ATCA overview 11 2.3 Pigeon Point Board Management Reference: hardware and firmware 14 2.4 Pigeon Point Shelf Manager and ShMM 15 2.4.1 Pigeon Point Shelf Manager features 15 2.4.2 Support for dual redundant operation 16 2.4.3 System Manager Interface 18 2.4.4 Pigeon Point ShMM Shelf Management Mezzanines 19 3 Configuration 22 3.1 In this section 22 3.2 Setting up U-Boot 22 3.2.1 U-Boot environment variables 24 3.2.2 Assigning values to environment variables 34 3.2.3 Configuring U-Boot environment variables for the Shelf Manager 34 3.2.4 Establishing the secondary RC script 37 3.3 Setting up Shelf Manager configuration file 38 3.3.1 Carrier-specific configuration file 96 3.3.2 Obtaining configuration variables from Shelf FRU Information 96 3.3.2.1 Using the FRU Info Compiler to place configuration variables in the Shelf FRU Information 96 3.3.2.2 Using the Shelf Manager Command Line Interface to place configuration variables in the Shelf FRU Information 97 3.3.3 Verbosity level description 97 3.3.4 Verbosity console level description 98 3.4 Setting up Ethernet 98 3.4.1 Usage of the first Ethernet interface 98 3.4.1.1 Assigning an additional IP address to the first network interface 98 3.4.1.2 RMCP address propagation 99 3.4.2 Usage of the second Ethernet interface 99 3.4.2.1 Active-standby usage of the two network interfaces 100 3.4.2.2 Active-active usage of the two network interfaces 101 3.4.2.3 Support for site-dependent ShMC cross-connects 102 3.4.2.4 Bonded usage of the two network interfaces 103 3.4.3 Setting up the HPM.2 client channel 104 3.4.4 Using the ShMM-500 and ShMM-700 alternate software redundancy interface 107 3.4.5 Using the ShMM-1500 alternate software redundancy interface 109 3.4.6 Changing the default ShMM network parameters 110 Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 2 / 321 3.4.7 Assigning VLAN IDs 118 3.4.8 Assigning IP addresses to the Shelf Manager via DHCP (version 4) 119 3.4.9 Using IPv6 for shelf-external access to the Shelf Manager (ShMM-700 only) 126 3.4.10 Assigning IPv6 addresses to the Shelf Manager via DHCPv6 (ShMM-700 only) 128 3.4.10.1 Handling DHCPv6 options 129 3.5 Configuring the FRU Information 132 3.5.1 Accessing the Shelf FRU Information 132 3.5.2 Setting up the Shelf FRU Information 134 3.5.3 Setting up the Shelf FRU Information using the CLI 136 3.5.4 Other FRU Information repositories 137 3.6 Configuring carrier and shelf attributes using HPDL 137 3.6.1 Compiling HPDL definitions 138 3.6.2 Compiling SDRs 139 3.6.3 Deploying HPDL data to the ShMM file system 139 3.6.4 Deploying HPDL Data to FRU Information areas 139 3.6.4.1 Specifying the location of the Carrier FRU Information 140 3.6.4.2 Using the FRU Info Compiler to place HPDL and SDR data in FRU Information 141 3.6.4.3 Using the Shelf Manager Command Line Interface 141 3.6.4.4 Placing HPDL data and SDRs in the FRU Information for specific FRUs 142 3.7 Configuring the cooling management strategy 142 3.7.1 Default cooling management strategy 143 3.7.2 Configuring a specific cooling management strategy 145 3.8 Configuring local sensors 145 3.9 Setting the Auxiliary Firmware Revision 151 3.10 Setting up the clock 151 3.10.1 Obtaining date and time from a time server 152 3.11 Setting up and using ShMM Power On Self Tests 153 3.12 Configuring external event handling 154 3.12.1 Detailed steps to configure external event handling 155 3.12.2 External event handler operation 156 3.13 Configuring the Platform Event Trap format 157 3.13.1 Parsed example of SNMP Trap 159 3.14 Configuring the IntegralHPI interface 160 3.14.1 HPI domain support in IntegralHPI 160 3.14.2 HPI SNMP subagent support 160 3.14.3 IntegralHPI client configuration 160 3.15 Configuring system services 161 3.16 Configuring the speed of I2C buses (ShMM-700 only) 165 4 Using the Shelf Manager 167 4.1 In this section 167 4.2 ShMM login 167 4.3 Starting the Shelf Manager 167 4.4 Redundant operation 176 Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 3 / 321 4.4.1 Initialization of the redundant Shelf Managers 178 4.4.2 Redundancy and CPLD State sensor 179 4.4.3 Reboot Reason sensor 182 4.5 Operation in shelves with radial IPMB-0 183 4.5.1 Operation in ShMM-500-based shelves with radial IPMB-0 183 4.5.2 Operation in ShMM-1500-based shelves with radial IPMB-0 185 4.5.3 Operation in ShMM-700-based shelves with radial IPMB-0 189 4.5.3.1 Upgrading the routing element SmartFusion cSoC(s) 190 4.6 Automatic SEL truncation 191 4.7 Cooling state sensors 191 4.8 Deadlock detection 193 4.9 I2C Bus fault isolation 197 4.9.1 I2C bus fault isolation – original approach (single multiplexer or switch, not HPDL-based) 198 4.9.2 I2C bus fault isolation – HPDL-based approach (multiple multiplexers or switches) 199 4.10 Assignment of LAN configuration parameters to boards and modules 200 4.10.1 Structure and composition of the supported parameters 201 4.10.2 Obtaining LAN configuration parameters on the Shelf Manager level 201 4.10.2.1 Using the FRU Info Compiler to place LAN configuration data in the Shelf FRU Information 203 4.10.2.2 Using the Shelf Manager Command Line Interface to place LAN configuration parameters in the Shelf FRU Information 203 4.10.2.3 Configuring a Linux DHCP server for obtaining LAN configuration parameters 203 4.10.3 Dispatching LAN configuration parameters to boards 205 4.10.4 Synchronous assignment of LAN configuration parameters to boards 206 4.11 HPI System Event sensor 207 4.12 ShMM tests available via the diagnostic infrastructure 207 5 Using the IPMI analysis tools 211 5.1 In this section 211 5.2 IPMB trace collection daemon (ipmb_traced) 211 5.3 IPMI trace analyzer 215 5.3.1 Introduction to the Wireshark GUI 215 5.3.2 Introduction to terminal-oriented Wireshark 218 5.3.3 Installing IPMI analyzer software 219 5.4 Collecting and analyzing a trace using the GUI and command line tools 219 5.4.1 Collecting IPMI traces on IPMB-0 in unattended mode 219 5.4.2 Collecting IPMI traces on IPMB-0 in controlled mode 224 5.4.3 Collecting an IPMI trace in board trace mode 227 5.4.4 Collecting traces of IPMI traffic over the network 227 5.4.5 Analyzing a trace using the GUI 230 5.4.6 Analyzing a trace using command-line tools 232 6 Re-initializing the ShMM 235 6.1 In this section 235 6.2 Re-initializing the U-Boot environment 235 6.3 Re-initializing the file system 236 Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 4 / 321 6.4 Resetting the login password 237 7 Re-programming the ShMM-500/1500 238 7.1 In this section 238 7.2 Firmware reliable upgrade procedure overview 238 7.3 Flash partitioning 239 7.4 The /var/upgrade file system 245 7.5 Reliable upgrade procedure status file 245 7.6 Reliable upgrade utility 245 7.7 Reliable upgrade utility use scenarios 252 7.8 Reliable upgrade examples 253 7.8.1 Example 1 253 7.8.2 Example 2 256 7.8.3 Example 3 259 8 Re-programming the ShMM-700 263 8.1 In this section 263 8.2 Firmware reliable upgrade procedure overview 263 8.3 Flash partitioning and image layout 265 8.4 Changing the ‘user’ flash partition format to JFFS2 267 8.5 Reliable upgrade procedure status file 270 8.6 Reliable upgrade utility 271 8.7 Reliable upgrade of SmartFusion cSoC image 278 8.8 Reliable upgrade utility use scenarios 279 8.9 Finding out component versions via the imls utility 280 8.10 Reliable upgrade examples 282 8.10.1 Example 1 282 8.10.2 Example 2 289 8.10.3 Example 3 293 8.10.4 Example 4 300 9 HPI-based Shelf Manager upgrades 307 Appendix A Converting to ShMM-700-based Shelf Managers in ShMM-500 shelves 308 Appendix B Customer support 310 Appendix C Revision history 311 C.1 Release 2.1.0 311 C.2 Release 2.2.0 311 C.3 Release 2.3.0 311 C.4 Release 2.4.0 312 C.5 Release 2.4.1 312 C.6 Release 2.4.2 313 C.7 Release 2.4.4 313 C.8 Release 2.5.0 313 C.9 Release 2.5.2 313 Pigeon Point Shelf Manager User Guide (May 15, 2018) Page 5 / 321 C.10 Release 2.5.3 314 C.11 Release 2.6.0 314 C.12 Release 2.6.1 314 C.13 Release 2.6.4 315 C.14 Release 2.6.4.2 315 C.15 Release 2.6.4.4 315 C.16 Release 2.7.0 315 C.17 Release 2.7.1 316 C.18 Release 2.7.2 316 C.19 Release 2.7.3 316 C.20 Release 2.7.4 317 C.21 Release 2.8.0 317 C.22 Release 2.8.1 317 C.23 Release 2.8.2 317 C.24 Release 3.0.0 317 C.25 Release 3.1.1 318 C.26 Release 3.2.0 318 C.27 Release 3.3.0 319 C.28 Release 3.4.0 319 C.29 Release 3.5.0 320 C.30 Release 3.5.0.1 320 C.31 Release 3.5.1 320 C.32 Release 3.6.0 320 C.33 Release 3.6.1 320 C.34 Release 3.6.1.2 321 C.35 Release 3.6.1.5 321 C.36 Release 3.6.1.6 321 C.37 Release 3.7.0 321 C.38 Release 3.7.1 321 List of figures Figure 1: Management aspects and potential Pigeon Point product sites in an example AdvancedTCA shelf ..............................................................................................................
Load more

Recommended publications
  • Openflow, in Proceedings of the Interna- Tional Conference on Pervasive Computing and Communication Workshops (Percom Workshops)
    Traffic Control for Multi-homed End-hosts via Software Defined Networking Anees Mohsin Hadi Al-Najjar B.Sc. (Computer Science), M.Sc. (Computer Science) A thesis submitted for the degree of Doctor of Philosophy at The University of Queensland in 2019 School of Information Technology & Electrical Engineering Abstract Software Defined Networking (SDN) is an emerging technology that allows computer networks to be more efficiently managed and controlled by providing a high level of abstraction and network programmability. Having powerful abstractions and pro- grammability via a centralised network controller provides new potential improve- ments to computer networks, such as easier network management, faster innovation and reduced cost. SDN has been successfully applied in wide area and data centre networks, and has achieved a significant improvement in network performance and efficiency. However, using SDN to control network traffic in end-host devices has not been investigated thoroughly. The research presented in this thesis aims to address this gap and inves- tigates the potential benefits of SDN for end-hosts. This thesis explores the feasibility of applying the SDN methodology to control network traffic on multi-homed end de- vices. The objective was to create a control mechanism by changing the network stack on the client in a way that is transparent to the application layer, the network infras- tructure, and other hosts on the network. In contrast to other solutions such as MPTCP, which require a protocol stack upgrade on all the participating nodes, the approach presented in this thesis allows quick and easy client-side-only deployment. This thesis presents an architecture for embedding SDN components, i.e.
    [Show full text]
  • Ipv6 for Helenos
    Charles University in Prague Faculty of Mathematics and Physics MASTER THESIS Mgr. Bc. Anton´ınSteinhauser IPv6 for HelenOS Department of Distributed and Dependable Systems Supervisor of the master thesis: Mgr. Martin Dˇeck´y Study programme: Informatics Specialization: Software Systems Prague 2013 I am much obliged to my thesis supervisor, Mgr. Martin Dˇeck´y,for his advices and hints in this research. I declare that I carried out this master thesis independently, and only with the cited sources, literature and other professional sources. I understand that my work relates to the rights and obligations under the Act No. 121/2000 Coll., the Copyright Act, as amended, in particular the fact that the Charles University in Prague has the right to conclude a license agreement on the use of this work as a school work pursuant to Section 60 paragraph 1 of the Copyright Act. In Prague date 18. 7. 2013 Anton´ınSteinhauser N´azevpr´ace:IPv6 for HelenOS Autor: Anton´ınSteinhauser Katedra: Katedra distribuovan´ych a spolehliv´ych syst´em˚u Vedouc´ıdiplomov´epr´ace: Mgr. Martin Dˇeck´y,Katedra distribuovan´ych a spolehliv´ych syst´em˚u Abstrakt: Tato pr´acerozˇsiˇrujeoperaˇcn´ısyst´emHelenOS o podporu nov´ehoIPv6 protokolu. Implementace protokolu IPv6 je na stejn´e´urovni jako dˇr´ıvˇejˇs´ıimple- mentace IPv4 protokolu. S´ıˇtov´ystack HelenOS nyn´ınab´ız´ıtˇrim´odypr´acese s´ıt´ı: uˇz´ıv´an´ıpouze IPv4 protokolu, uˇz´ıv´an´ıpouze IPv6 protokolu a du´aln´ım´od, kter´y umoˇzˇnujepouˇz´ıvat oba protokoly najednou. Pr´acepopisuje pˇredchoz´ıstav s´ıˇtov´ehostacku HelenOS, analyzuje rozd´ılymezi IPv4 protokolem a IPv6 protokolem a zd˚uvodˇnujejednotliv´astrategick´arozhod- nut´ı.
    [Show full text]
  • Linux Audio Conference 2019
    Proceedings of the Linux Audio Conference 2019 March 23rd – 26th, 2019 Center for Computer Research in Music and Acoustics (CCRMA) Stanford University, USA “In Ping(uins) e trust! Published by CCRMA, Stanford University, California, US March 2019 All copyrights remain with the authors http://lac.linuxaudio.org/2019 ISBN 978-0-359-46387-9 Credits Layout: Frank Neumann and Romain Michon Typesetting: LATEX and pdfLaTeX Logo Design: The Linuxaudio.org logo and its variations copyright Thorsten Wilms c 2006, imported into "LAC 2014" logo by Robin Gareus Thanks to: Martin Monperrus for his webpage "Creating proceedings from PDF files" ii Partners and Sponsors Linuxaudio.org iii iv Foreword Welcome everyone to LAC 2019 at CCRMA! For the second time in its seventeen year history, the Linux Audio Conference (LAC) is hosted in the United Stated of America by the Center for Computer Research in Mu- sic and Acoustics (CCRMA) at Stanford University. With its informal workshop-like at- mosphere, LAC is a blend of scientific and technical papers, tutorials, sound installations, and concerts centered on the free GNU/Linux operating system and open-source free soft- ware for audio, multimedia, and musical applications. LAC is a unique platform during which members of this community gather to exchange ideas, draft new projects, and see old friends. In these times of increasing political tensions and of rising extremism throughout the world, we believe that emphasizing and promoting the universality of this type of event is of the utmost importance. The Linux audio community exists worldwide; we believe it should remain a priority to diversify LAC’s geographical location from year to year for the benefit of those who can’t afford to travel to the other side of the world.
    [Show full text]
  • WM PAN9420 Software Guide.Pdf
    PAN9420 Software Guide Rev. 1.0 Wireless Modules PAN9420 Wi-Fi Module By purchase of any of the products described in this document the customer accepts the document's validity and declares their agreement and understanding of its contents and recommendations. Panasonic Industrial Devices Europe GmbH (Panasonic) reserves the right to make changes as required at any time without notification. © Panasonic Industrial Devices Europe GmbH 2019. This document is copyrighted. Reproduction of this document is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Do not disclose it to a third party. All rights reserved. This Software Guide does not lodge the claim to be complete and free of mistakes. The information contained herein is presented only as guidance for Product use. No responsibility is assumed by Panasonic for any infringement of patents or any other intellectual property rights of third parties that may result from the use of Product. No license to any intellectual property right is granted by this document, whether express or implied, by estoppel or otherwise. Description of hardware, software, and other information in this document is only intended to illustrate the functionality of the referred Panasonic product. It should not be construed as guaranteeing specific functionality of the product as described or suitable for a particular application. Any provided (source) code shall not be used or incorporated into any products or systems whose manufacture, use or sale is prohibited under any applicable laws or regulations. Any outlined or referenced (source) code within this document is provided on an “as is” basis without any right to technical support or updates and without warranty of any kind on a free of charge basis according to § 516 German Civil Law (BGB) including without limitation, any warranties or conditions of title, non-infringement, merchantability, or fitness for a particular purpose.
    [Show full text]
  • All-Type-Of-Attack
    Attack Types Documented by: Mr. Ahmed Khan Mr. Dipak Mr. Kannan Mr. Kiran Mr. Kulkarni Madunix Mr. Mohamed Iqbal Mr. Nitai Mr. Sagar Mr. Shrikanth Draft Copy : 01.03 Attacks • An attack is any attempt to destroy, expose, alter, disable, steal or gain unauthorized access to or make unauthorized use of an asset. • Without proper security measures and controls in place, our data might be subjected to an attack. Some attacks are passive, meaning information is monitored; others are active, meaning the information is altered with intent to corrupt or destroy the data or the network itself. • Attacks can be Insider or via external Attacks Active Attacks: An active attack is a network exploit ation in which a hacker attempts to make changes to data on the target or data en route to the target. Passive Attacks: A passive attack is a network attack in which a system is monitored and sometimes scanned for open ports and vulnerabilities. The purpose is solely to gain information about the target and no data is changed on the target. Active :Listens Passive : Modifies Man-In-The-Middle AKA MITM • It is an attack where the attacker secretly relays and possibly alters the communication between two parties who believe they are directly communicating with each other. Countermeasures • Digital signature • Mutual authentication Brute Force • A brute-force attack consists of an attacker trying many passwords or passphrases with the hope of eventually guessing correctly • The attacker systematically checks all possible passwords and passphrases until the correct one is found. • When password guessing, this method is very fast when used to check all short passwords.
    [Show full text]
  • Prosafe Managed Switch Command Line Interface (CLI) User Manual
    ProSafe Managed Switch Command Line Interface (CLI) User Manual 10.0 GSM7328Sv2 GSM7352Sv2 GSM7228PS GSM7252PS M5300-28G3 M5300-52G3 M5300-28G-POE+ M5300-52G-POE+ M5300-28GF3 M5300-28G M5300-52G 350 East Plumeria Drive San Jose, CA 95134 USA November 2012 202-11054-02 1.0 ProSafe Managed Switch © 2012 NETGEAR, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of NETGEAR, Inc. Technical Support Thank you for choosing NETGEAR. To register your product, get the latest product updates, or get support online, visit us at http://support.netgear.com. Phone (US & Canada only): 1-888-NETGEAR Phone (Other Countries): See Support information card. Trademarks NETGEAR, the NETGEAR logo, ReadyNAS, ProSafe, Smart Wizard, Auto Uplink, X-RAID2, and NeoTV are trademarks or registered trademarks of NETGEAR, Inc. Microsoft, Windows, Windows NT, and Vista are registered trademarks of Microsoft Corporation. Other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions To improve internal design, operational function, and/or reliability, NETGEAR reserves the right to make changes to the products described in this document without notice. NETGEAR does not assume any liability that may occur due to the use, or application of, the product(s) or circuit layout(s) described herein. Revision History Publication Part Version Publish DateComments Number 202-11054-02 1.0 November 2012 Added mixed stacking commands. 202-11054-01 1.0 August 2012 Replaced the private group commands with private VLAN commands, replaced the Auto-Voice over IP Commands chapter, and added iSCSI commands.
    [Show full text]
  • Binding Request in Wireshark
    Binding Request In Wireshark Unassisting and wonderful Richmond still salved his warships temporarily. Lao Lamar relocated no abstractors deciding gelidly after Truman refurnishes tunelessly, quite afflictive. Gail is veloce well-directed after exploitive Si glooms his plunderers plum. One inside of the activity appears as direct peer, in binding wireshark Confidentiality for the application data relayed by TURN is best provided by the application protocol itself, since running TURN over TLS does not protect application data between the server and the peer. DNS works in detail. Each message format specifies the location of the verifier, which always follows any stub data, if applicable. Fi network can see all traffic, purely due to the nature of radio communication. CODE attribute is used in error response messages. Complex networks can consist of thousands of LANs connected through thousands of routers worldwide. When i connect the computer directly to a cable modem, it works. If the snapshot length is not set specifically, the default snapshot length is used if provided. Run wireshark on a list of packets wrpcap Write a list of packets to a pcap file Some of these functions we have used others I will let you play around with yourself. Malware, or MBAM, to scan your computer for any any infections or adware that may be present. Do you have some idea where the problem could come from? Another thought I had was file sharing. SR at any time. We have an issue in our setup. Other usages may use other means to prevent these attacks. SIP Invite spoof capture.
    [Show full text]
  • Microchip TCP/IP Lite Stack
    AN1921 Microchip TCP/IP Lite Stack KB Flash (TCP/IP), while still having a fully functional Authors: Janaki Kuruganti, TCP/IPv4 stack. The stack will allow users to add wired Alin Stoicescu, communication and interoperability with other systems Marius Cristea, to their applications over Ethernet. Microchip Technology Inc. The Microchip TCP/IP Lite Stack is implemented in a configurable and modular way, allowing users to INTRODUCTION include only the intended features or functionalities to their application. The stack is written in C programming This application note describes the structure and the language and it is intended to be compiled with the interface for the Microchip Transmission Control MPLAB® XC8 compiler. Protocol/Internet Protocol (TCP/IP) Lite Stack library, and includes some simple example applications using MPLAB® Code Configurator (MCC). The purpose of TCP/IP STACK ARCHITECTURE the implementation is to provide an optimized (low The TCP/IP Lite library implementation is based on the Flash and RAM footprint) TCP/IP stack for TCP/IP communication model, as shown in Figure 1: microcontrollers with 8 KB Flash (UDP only) and 16 FIGURE 1: MULTILAYER TCP/IP COMMUNICATION MODEL 2015-2017 Microchip Technology Inc. DS00001921D-page 1 AN1921 The TCP/IP stack is divided into multiple layers controller starts dropping the received packets if it does (Figure 1). Each layer in the Microchip TCP/IP Lite not have enough memory left to store the incoming Stack can directly access one or more layers situated packets. above or below it. Ethernet packets to be transmitted are also built and The TCP/IP stack needs a background task called kept in the Ethernet controller’s memory.
    [Show full text]
  • Networking and TCP/IP Stack for Helenos System
    Charles University in Prague Faculty of Mathematics and Physics MASTER THESIS Bc. Luk´aˇsMejdrech Networking and TCP/IP stack for HelenOS system Department of Software Engineering Master thesis supervisor: Mgr. Martin Dˇeck´y Study programme: Computer Science, Software systems 2009 Acknowledgements I wish to thank to my thesis supervisor, Mgr. Martin Dˇeck´y, for his advice and direction in this research. I owe the greatest gratitude to my family, for making this thesis possible and their constant patience and support. I hereby declare that I have created this work completely on my own and used no other sources or tools than the ones listed, and that I have marked any citations accordingly. I agree with lending and publishing this work. Prohlaˇsuji, ˇze jsem svou diplomovou pr´aci napsal samostatnˇea v´yhradnˇes pouˇzit´ım citovan´ych pramen˚u. Souhlas´ım se zap˚ujˇcov´an´ım pr´ace a jej´ım zveˇrejˇnov´an´ım. In Prague Bc. Luk´aˇsMejdrech 2 N´azev pr´ace: Networking a TCP/IP stack pro syst´em HelenOS Autor: Bc. Luk´aˇsMejdrech Katedra: Katedra softwarov´eho inˇzen´yrstv´ı Vedouc´ıpr´ace: Mgr. Martin Dˇeck´y E-mail vedouc´ıho: [email protected]ff.cuni.cz Abstrakt: V t´eto pr´aci studujeme implementaci TCP/IP subsyst´emu. D˚uraz je kladen na n´avrh a implementaci respektuj´ıc´ıkoncept operaˇcn´ıho syst´emu s mikroj´adrem. Praktickou ˇc´ast´ıpak byl v´yvoj TCP/IP subsyst´emu pro syst´em HelenOS. Nejprve jsou pops´any koncepty s´ıt’ov´earchitektury a TCP/IP subsyst´emu obecnˇe. N´asleduj´ı specifick´easpekty kladen´esyst´emem s mikroj´adrem.
    [Show full text]
  • Investigating Methods for Measuring Network Convergence Times
    Mälardalen University School of Innovation Design and Engineering Västerås, Sweden Thesis for the Degree of Master of Science in Computer Science with Specialization in Embedded Systems 30.0 credits INVESTIGATING METHODS FOR MEASURING NETWORK CONVERGENCE TIMES Jakob Danielsson [email protected] Tobias Andersson [email protected] Examiner: Thomas Nolte Mälardalen University, Västerås, Sweden Supervisor: Mohammad Ashjaei Mälardalen University, Västerås, Sweden Company supervisor: Thomas Sörensen, Westermo, Västerås, Vallby Institutet June 10, 2016 Mälardalen University Master Thesis Table of Contents 1 Introduction 5 1.1 Motivation........................................6 1.2 Thesis outline.......................................6 2 Background 7 2.1 The OSI model......................................7 2.2 Convergence time in layer 2...............................7 2.2.1 FRNT - Fast Reconfiguration of Network Topology..............8 2.2.2 FRNT Ring Coupling..............................8 2.2.3 Multi-Link Dual Homing............................8 2.2.4 Rapid spanning tree protocol - RSTP and STP................8 2.3 Convergence time in layer 3...............................9 2.3.1 RIP - Routing Information Protocol......................9 2.3.2 OSPF - Open Shortest Path First.......................9 2.3.3 VRRP - Virtual router redundancy protocol..................9 2.4 Convergence measurement tools............................. 10 2.5 The Linux operating system............................... 10 3 Related Work 11 4 Problem Formulation
    [Show full text]
  • Citrix-Workspace-App-For-Mac.Pdf
    Citrix Workspace app for Mac Citrix Product Documentation | docs.citrix.com September 29, 2021 Citrix Workspace app for Mac Contents About this release 3 System requirements and compatibility 27 Install, Uninstall, and Upgrade 32 Configure 34 Authenticate 70 Secure communications 72 © 1999–2021 Citrix Systems, Inc. All rights reserved. 2 Citrix Workspace app for Mac About this release September 29, 2021 Important Starting with macOS Catalina, Apple has enforced extra requirements for root CA certificates and intermediate certificates which administrators must configure. For more information, see Apple Support article HT210176. What’s new in 2109 Note: If Service continuity is enabled, and you upgrade to version 2109, the connection lease files are refreshed. All the existing leases are deleted and new leases are fetched as part of functionality enhancements. Citrix Workspace app for Mac on macOS Monterey Beta Citrix Workspace app 2109 for Mac has been tested on macOS Monterey Beta 7. Please use this setup in a test environment and provide your feedback. Caution: Do not use Citrix Workspace app for Mac on macOS Monterey Beta versions in production envi‑ ronments. Email‑based auto‑discovery of store With this release, you can simply provide your email address in Citrix Workspace app for Mac to au‑ tomatically discover the store associated with the email address. If there are multiple stores associ‑ ated with a domain, then by default the first store returned by the Global App Configuration Service is added as the store of choice for logging in and accessing a store. Users can always switch to another store if necessary.
    [Show full text]
  • Oracle Coherence Developer's Guide, Release 3.7.1 E22837-01
    Oracle® Coherence Developer’s Guide Release 3.7.1 E22837-01 September 2011 Provides contextual information, instructions, and examples that are designed to teach Developers and Architects how to use Coherence and develop Coherence-based applications. Oracle Coherence Developer's Guide, Release 3.7.1 E22837-01 Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved. Primary Author: Joseph Ruzzi This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. IIf this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]