DOCSLIB.ORG

Vtserver Reference Manual V4.0.1 1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Vtserver Reference Manual V4.0.1 1 vtServer® vtAlpha/vtVAX Bare Metal V4.0.1 Reference Manual BU-0002-27 vtServer Reference Manual BU-0002-27 (January 2, 2020) © 2019 AVT/Vere vtAlpha and vtVAX are marketed jointly by AVT and Vere Technologies LLC Table of Contents 1. First Steps .................................................................................................. 1 1.1. Why Use Virtualization ....................................................................... 3 1.2. Some Terminology ............................................................................. 4 1.3. Features Overview ............................................................................. 5 2. Installing vtServer ..................................................................................... 7 2.1. Prerequisites ...................................................................................... 7 2.2. Installing vtServer on a Hypervisor .................................................... 8 2.2.1. Impact of Running on a Virtual Host ........................................ 9 2.2.2. Virtual Host Criteria ............................................................... 10 2.2.3. Performance .......................................................................... 10 2.2.4. Shared Resources ................................................................. 10 2.2.5. CPU Requirements ................................................................ 10 2.2.6. USB Port................................................................................ 11 2.2.7. Storage .................................................................................. 12 2.2.8. Symmetric Multiprocessing (SMP) ......................................... 13 2.2.9. Licensing ............................................................................... 14 2.2.10. vtServer Software Installation ................................................ 14 2.2.11. Hypervisor Specific Information ............................................. 15 2.2.12. VMware ................................................................................. 15 2.2.13. Hyper_V................................................................................. 19 2.2.14. KVM ....................................................................................... 20 2.3. Performing the Installation ............................................................... 21 2.3.1. Upgrade/Repair ..................................................................... 21 2.3.2. Install vtServer ....................................................................... 22 2.4. Installation of Optional Kits .............................................................. 23 2.5. Install vtLicense ............................................................................... 25 2.6. Unattended Installation .................................................................... 26 2.7. Performing an Upgrade ................................................................... 26 2.8. Snapshot Management .................................................................... 27 2.9. Version Updates .............................................................................. 29 3. Managing vtServer/vtLicense ................................................................. 30 3.1. Open SSH Console ......................................................................... 30 3.2. Backup Host settings ....................................................................... 31 3.3. vtScan .............................................................................................. 33 4. Configuring vtServer/vtLicense ............................................................. 35 4.1. Navigation ........................................................................................ 35 4.2. Networking ....................................................................................... 39 4.2.1. Introduction to Virtual Networking .......................................... 40 4.2.2. Configure Network ................................................................. 44 4.2.3. Using a Virtual Switch ............................................................ 45 4.2.4. Using a Bond ......................................................................... 46 4.2.5. Setup a VLAN ........................................................................ 48 4.3. Storage ............................................................................................ 49 4.3.1. Storage Overview .................................................................. 50 4.3.2. Using Physical Disks ............................................................. 52 4.3.3. Creating and Using Logical Disks .......................................... 54 4.3.4. Tape Image Files ................................................................... 59 4.3.5. CD/DVD Support ................................................................... 61 4.3.6. NFS ....................................................................................... 64 4.3.7. SMB ....................................................................................... 66 4.3.8. iSCSI Storage ........................................................................ 67 4.3.9. Fiber Channel (SAN) ............................................................. 68 4.4. Hostname ........................................................................................ 70 4.5. Services ........................................................................................... 71 4.6. Date and Time ................................................................................. 73 4.7. User Management ........................................................................... 74 4.7.1. Users ..................................................................................... 76 4.7.2. Roles ..................................................................................... 79 4.7.3. Security Settings for Users .................................................... 82 4.8. Alerts ............................................................................................... 86 4.9. Keyboard ......................................................................................... 90 4.10. Snapshots ........................................................................................ 91 4.10.1. Important Things to Know When Using Snapshots ............... 93 4.10.2. Convert vtServer System Partition from ext4 to btrfs ............. 95 4.11. HTTPS and Certificates ................................................................... 97 4.12. System Parameters ....................................................................... 100 4.13. System Information ........................................................................ 102 4.14. Shutdown / Reboot ........................................................................ 103 4.15. Licensing ....................................................................................... 104 4.15.1. License Options ................................................................... 105 4.15.2. License Search Order .......................................................... 105 4.15.3. LED Color State ................................................................... 106 4.15.4. License Management .......................................................... 107 4.15.5. License in a Network ........................................................... 108 4.15.6. Network License Installation ................................................ 110 4.16. Firewall Settings (vtLicense only) .................................................. 113 4.17. Proxy Settings (vtLicense Only) ..................................................... 115 5. Virtual Machines .................................................................................... 116 5.1. Creating a Virtual Machine ............................................................ 116 5.2. Configuring a Virtual Alpha ............................................................ 118 5.2.1. Comment Box ...................................................................... 118 5.2.2. Virtual Machine Name ......................................................... 118 5.2.3. Hardware Settings ............................................................... 119 5.2.4. Advanced Options ............................................................... 120 5.2.5. Hardware Model .................................................................. 122 5.2.6. QBB ..................................................................................... 123 5.2.7. Virtual CPUs ........................................................................ 123 5.2.8. CPU Details ......................................................................... 125 5.2.9. Memory................................................................................ 126 5.2.10. OPA0 / COM2 ...................................................................... 127 5.2.11. PCI Bus ............................................................................... 133 5.2.12. PCI Slot ............................................................................... 134 5.2.13. Ethernet Adapter ................................................................. 136 5.2.14. Serial Lines Adapter ............................................................ 137 5.2.15. SCSI Adapter ....................................................................... 139 5.2.16. Fiber Channel Adapter .......................................................
Load more

Recommended publications
  • The Evolution of Econometric Software Design: a Developer's View
    Journal of Economic and Social Measurement 29 (2004) 205–259 205 IOS Press The evolution of econometric software design: A developer’s view Houston H. Stokes Department of Economics, College of Business Administration, University of Illinois at Chicago, 601 South Morgan Street, Room 2103, Chicago, IL 60607-7121, USA E-mail: [email protected] In the last 30 years, changes in operating systems, computer hardware, compiler technology and the needs of research in applied econometrics have all influenced econometric software development and the environment of statistical computing. The evolution of various representative software systems, including B34S developed by the author, are used to illustrate differences in software design and the interrelation of a number of factors that influenced these choices. A list of desired econometric software features, software design goals and econometric programming language characteristics are suggested. It is stressed that there is no one “ideal” software system that will work effectively in all situations. System integration of statistical software provides a means by which capability can be leveraged. 1. Introduction 1.1. Overview The development of modern econometric software has been influenced by the changing needs of applied econometric research, the expanding capability of com- puter hardware (CPU speed, disk storage and memory), changes in the design and capability of compilers, and the availability of high-quality subroutine libraries. Soft- ware design in turn has itself impacted applied econometric research, which has seen its horizons expand rapidly in the last 30 years as new techniques of analysis became computationally possible. How some of these interrelationships have evolved over time is illustrated by a discussion of the evolution of the design and capability of the B34S Software system [55] which is contrasted to a selection of other software systems.
    [Show full text]
  • Alpha AXP Firmware Porting Guide Revision/Update Information: Version 1.0
    Alpha AXP Firmware Porting Guide Revision/Update Information: Version 1.0 Order Number: EK-AXFRM-PG. A01 November, 1994 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Reproduction or duplication of this courseware in any form, in whole or in part, is prohibited without the prior written permission of Digital Equipment Corporation. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1994. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, Bookreader, DEC, DECchip, DEC OSF/1, DECwindows, Digital, OpenVMS, VAX, VMS, VMScluster, the DIGITAL logo and the AXP mark. MIPS is a trademark of MIPS Computer Systems, Inc. NCR is a registered trademark of the NCR Corporation. NetWare is a registered trademark of Novell, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. Windows NT is a registered trademark of the Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. Contents Preface ............................................................ xiii 1 Porting Strategy Overview .......................................................
    [Show full text]
  • The Commission's Assessment of Microsoft's
    The Commission's assessment of Microsoft's innovation claims In the column "Prior Art", the symbol [PA] indicates that the reference is cited as prior art, the symbol [R] means that it is cited as a reference. The following applies in the column "References": [July-T, x] = 8 July Trustee report, page x [March-T, x] = 3 March Trustee report (as amending the 22 February Trustee report), page x [Ecis, x] = Ecis's comments to Microsoft's Response to the 1 March SO, page x Date of Reference in Microsoft's Protocol Technology Description of the technology Claimed benefit Assessment Prior Art References claim filing Active ADFS Combination of The combination of all the mentioned April 2004 The use of the five Microsoft's innovation report The claimed innovation is the [July-T, 4] Directory ADFS ADFS technologies. individual ADFS on "Microsoft Web Browse combination of different features Federation Technologies innovations in Federated Sign-on Protocol & belonging to the same protocol. Services combination is Microsoft Web Browser Combining these individual undisclosed and not Federated Sign-On Protocol features is an obvious step for a obvious. Extensions" person skilled in the art. NON-INNOVATIVE Active ADFS Defining ADFS defines communications between April 2004 The protocol Microsoft's innovation report The claim concerns resolving [PA] Anderson, Steve et al: Web Services [July-T, 4] Directory Authentication a resource identity provider and a web delivers on "Microsoft Web Browse problems which are specific to Trust Language (WS-Trust) (1 May 2004; [March-T, 110] Federation Communications service resource. maintainability by Federated Sign-on Protocol & Microsoft's implementation.
    [Show full text]
  • Digital Alphastation 250 Series User Information
    Digital AlphaStation™ 250 Series User Information Order Number: EK-PCCTA-UI. A01 Digital Equipment Corporation Maynard, Massachusetts January 1995 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that might appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright 1995 Digital Equipment Corporation. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: AlphaGeneration, AlphaStation, DEC, Digital, OpenVMS, ThinWire, and the DIGITAL logo. The following are third-party trademarks: Microsoft and Windows NT are registered trademarks of Microsoft Corporation. SIMM is a trademark of Molex Corporation. OSF/1 is a trademark of the Open Software Foundation, Inc. All other trademarks or registered trademarks are the property of their respective holders. This document was produced with Microsoft Word for Windows, V2.0c. FCC Information - Class B This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules.
    [Show full text]
  • Digital Personal Workstation Service Maintenance Guide
    Digital Personal Workstation Service Maintenance Manual DIGITAL PERSONAL WORKSTATION Digital Personal Workstation Service Maintenance Manual Part Number: ER-B30WW-SM. A01 DIGITAL PERSONAL WORKSTATION Digital Equipment Corporation September 1996 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that might appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Digital Personal Workstation Service Maintenance Manual Copyright Digital Equipment Corporation. All Rights Reserved. DEC and the Digital logo are registered trademarks of Digital Equipment Corporation. Intel is a registered trademark of Intel Corporation. Pentium-Pro are registered trademarks of Intel Corporation. Microsoft and Windows NT are registered trademarks of Microsoft Corporation. SIMM is a registered trademark of Wang Laboratories. All other trademarks and registered trademarks are the property of their respective holders. The FCC wants you to know... This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules.
    [Show full text]
  • The Computer History Simulation Project
    The Computer History Simulation Project The Computer History Simulation Project The Computer History Simulation Project is a loose Internet-based collective of people interested in restoring historically significant computer hardware and software systems by simulation. The goal of the project is to create highly portable system simulators and to publish them as freeware on the Internet, with freely available copies of significant or representative software. Simulators SIMH is a highly portable, multi-system simulator. ● Download the latest sources for SIMH (V3.5-1 updated 15-Oct-2005 - see change log). ● Download a zip file containing Windows executables for all the SIMH simulators. The VAX and PDP-11 are compiled without Ethernet support. Versions with Ethernet support are available here. If you download the executables, you should download the source archive as well, as it contains the documentation and other supporting files. ● If your host system is Alpha/VMS, and you want Ethernet support, you need to download the VMS Pcap library and execlet here. SIMH implements simulators for: ● Data General Nova, Eclipse ● Digital Equipment Corporation PDP-1, PDP-4, PDP-7, PDP-8, PDP-9, PDP-10, PDP-11, PDP- 15, VAX ● GRI Corporation GRI-909 ● IBM 1401, 1620, 1130, System 3 ● Interdata (Perkin-Elmer) 16b and 32b systems ● Hewlett-Packard 2116, 2100, 21MX ● Honeywell H316/H516 ● MITS Altair 8800, with both 8080 and Z80 ● Royal-Mcbee LGP-30, LGP-21 ● Scientific Data Systems SDS 940 Also available is a collection of tools for manipulating simulator file formats and for cross- assembling code for the PDP-1, PDP-7, PDP-8, and PDP-11.
    [Show full text]
  • A File System Component Compiler
    A File System Component Compiler Erez Zadok [email protected] Computer Science Department Columbia University New York, NY 10027 CUCS-033-97 April 28, 1997 THESIS PROPOSAL File System development is a difficult and time consuming task, the results of which are rarely portable across operating systems. Several proposals to improve the vnode interface to allow for more flexible file system design and implementation have been made in recent years, but none is used in practice because they require costly fundamental changes to kernel interfaces, only operating systems vendors can make those changes, are still non-portable, tend to degrade performance, and do not appear to provide immediate return on such an investment. This proposal advocates a language for describing file systems, called FiST. The associated translator can generate portable C code — kernel resident or not — that implements the described file system. No kernel source code is needed and no existing vnode interface must change. The performance of the file systems automatically generated by FiST can be within a few percent of comparable hand-written file systems. The main benefits to automation are that development and maintenance costs are greatly reduced, and that it becomes practical to prototype, implement, test, debug, and compose a vastly larger set of such file systems with different properties. The proposed thesis will describe the language and its translator, use it to implement a few file systems on more than one platform, and evaluate the performance of the automatically generated code. i Contents 1 Introduction 1 1.1TheProblem.......................................... 2 1.2MySolution........................................... 2 1.3AdvantagesofMySolution.................................
    [Show full text]
  • Hack Attacks Revealed
    Hack Attacks Revealed A Complete Reference with Custom Security Hacking Toolkit John Chirillo This netLibrary eBook does not include the ancillary media that was packaged with the original printed version of the book. Publisher: Robert Ipsen Editor: Carol A. Long Assistant Editor: Adaobi Obi Managing Editor: Micheline Frederick New Media Editor: Brian Snapp Text Design & Composition: Thomark Design Designations used by companies to distinguish their products are often claimed as trademarks. In all instances where John Wiley & Sons, Inc., is aware of a claim, the product names appear in initial capital or ALL CAPITAL LETTERS. Readers, however, should contact the appropriate companies for more complete information regarding trademarks and registration. Copyright © 2001 by John Chirillo. All rights reserved. Published by John Wiley & Sons, Inc. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per- copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750- 8400, fax (978) 750-4744. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 605 Third Avenue, New York, NY 10158-0012, (212) 850-6011, fax (212) 850-6008, E-Mail: PERMREQ @ WILEY.COM. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in professional services.
    [Show full text]
  • Alpha Architecture Handbook
    Alpha Architecture Handbook Order Number EC–QD2KB–TE Revision/Update Information: This is Version 3 of the Alpha Architecture Handbook. The changes and additions in this book are subsequent to the Alpha AXP Architecture Reference Manual, Second Edition, and the Alpha AXP Architecture Handbook, Version 2. Digital Equipment Corporation Maynard, Massachusetts October 1996 While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Copyright ©1996 Digital Equipment Corporation. All rights reserved. The following are trademarks of Digital Equipment Corporation: AlphaGeneration, Alpha AXP, AXP, DEC, Digital, OpenVMS, PDP–11, VAX, VAX DOCUMENT, the AlphaGeneration design mark, and the DIGITAL logo. Cray is a registered trademark of Cray Research, Inc. IBM is a registered trademark of International Business Machines Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. Windows NT is a trademark of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1-1. Contents Preface xv Chapter 1 Introduction (I) 1.1 The Alpha Approach to RISC Architecture ................................. 1–1 1.2 Data Format Overview ................................................. 1–3 1.3 Instruction Format Overview .
    [Show full text]
  • File:System Programming Textbook from Illinois
    Coursebook B. Venkatesh, L. Angrave, et Al. Contents 1 Introduction 1 1.1 Authors . 1 2 Background 7 2.1 Systems Architecture . 7 2.1.1 Assembly . 7 2.1.2 Atomic Operations . 7 2.1.3 Caching . 8 2.1.4 Interrupts . 8 2.1.5 Optional: Hyperthreading . 9 2.2 Debugging and Environments . 9 2.2.1 ssh . 9 2.2.2 git . 10 2.2.3 Editors . 12 2.2.4 Clean Code . 13 2.2.5 Asserts . 14 2.3 Valgrind . 14 2.3.1 TSAN . 16 2.4 GDB......................................................... 17 2.4.1 Involved gdb example . 19 2.4.2 Shell . 21 2.4.3 Undefined Behavior Sanitizer . 21 2.4.4 Clang Static Build Tools . 21 2.4.5 strace and ltrace . 21 2.4.6 printfs . 23 2.5 Homework 0 . 25 2.5.1 So you want to master System Programming? And get a better grade than B? . 25 2.5.2 Watch the videos and write up your answers to the following questions . 26 2.5.3 Chapter 1 . 26 2.5.4 Chapter 2 . 27 2.5.5 Chapter 3 . 28 2.5.6 Chapter 4 . 28 2.5.7 Chapter 5 . 29 2.5.8 C Development . 29 2.5.9 Optional: Just for fun . 30 2.6 UIUC Specific Guidelines . 30 2.6.1 Piazza . 30 3 The C Programming Language 33 ii CONTENTS CONTENTS 3.1 History of C . 33 3.1.1 Features . 34 3.2 Crash course introduction to C . 34 3.2.1 Preprocessor .
    [Show full text]
  • Alphaserver 1200 User's Guide
    AlphaServer 1200 User’s Guide Order Number: EK–AS120–UG. A01 This manual is for anyone who manages, operates, or services the AlphaServer 1200 system. It covers operation, firmware, initial troubleshooting, and component installation. Digital Equipment Corporation Maynard, Massachusetts First Printing, October 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright 1997 by Digital Equipment Corporation. All rights reserved. The following are trademarks of Digital Equipment Corporation: AlphaServer, OpenVMS, StorageWorks, VAX, and the DIGITAL logo. The following are third-party trademarks: Lifestyle 28.8 DATA/FAX Modem is a trademark of Motorola, Inc. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. U.S. Robotics and Sportster are registered trademarks of U.S.
    [Show full text]
  • Security Probes for Industrial Control Networks
    Master in Informatics Engineering Dissertation Final Report Security Probes for Industrial Control Networks Jorge Filipe Barrigas [email protected] Academic Advisor: Prof. Tiago José dos Santos Martins da Cruz Date: July 01, 2014 Acknowledgements I would like to express my special appreciation and thanks to my advisor Professor Tiago Cruz for his excellent guidance, caring, patience, and providing me with an excellent atmosphere for doing research. I would also like to thank the LCT team and Professor Dr. Paulo Simões for all the support in my research. Finally, I would also like to thank my parents. They were always supporting me and encouraging me with their best wishes. Summary During the last years, some of the attacks towards SCADA made headlines, helping raise awareness . Some of the vulnerabilities may even be exploited to harm other systems, eventually, ending compromising specific points of SCADA networks. At the same time, a growing number of threats related with the physical layer made new issues and low-level mechanisms emerged, requiring careful approach and monitoring to secure such devices. Threats of this type are considered to be even more dangerous than SCADA-specific ones, since these operate at a lower level, unnoticed to scanners and anti-viruses. Considering this scenario we can expect a growing number of these threats to be affecting SCADA components, if adequate countermeasures are not taken. Over the last ten months (from September 16, 2013 until June 27, 2014), a new concept was developed, in the context of the FP7 CockpitCI project, for the current thesis, to reinforce the security of SCADA systems.
    [Show full text]