DOCSLIB.ORG

Connectx Programmers' Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Connectx Programmers' Reference Manual Mellanox FlexBoot User Manual Rev 1.4 www.mellanox.com Rev 1.4 NOTE: THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES “AS-IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUSTOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO(S) AND/OR THE SYSTEM USING IT. THEREFORE, MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, BUT NOT LIMITED TO, PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Mellanox Technologies Mellanox Technologies, Ltd. 350 Oakmead Parkway Suite 100 Beit Mellanox Sunnyvale, CA 94085 PO Box 586 Yokneam 20692 U.S.A. Israel www.mellanox.com www.mellanox.com Tel: (408) 970-3400 Tel: +972 (0)74 723 7200 Fax: (408) 970-3403 Fax: +972 (0)4 959 3245 © Copyright 2013. Mellanox Technologies. All Rights Reserved. Mellanox®, Mellanox logo, BridgeX®, ConnectX®, CORE-Direct®, InfiniBridge®, InfiniHost®, InfiniScale®, MLNX-OS®, PhyX®, SwitchX®, UFM®, Virtual Protocol Interconnect® and Voltaire® are registered trademarks of Mellanox Technologies, Ltd. Connect-IB™, ExtendX™, FabricIT™, Mellanox Open Ethernet™, Mellanox Virtual Modular Switch™, MetroX™, MetroDX™, ScalableHPC™, Unbreakable-Link™ are trademarks of Mellanox Technologies, Ltd. All other trademarks are property of their respective owners. 2 Mellanox Technologies Document Number: 3218 Rev 1.4 Table of Contents Table of Contents . 1 Document Revision History . 2 Related Documents . .2 Chapter 1 Mellanox FlexBoot . 3 1.1 Overview . 3 1.2 FlexBoot Package . 3 1.3 Reference Documents and Downloads . 3 Chapter 2 Burning the Expansion ROM Image . 4 2.1 Burning the Image on ConnectX®-2/ ConnectX®-3 Devices . 4 2.1.1 Prerequisites . 4 2.1.2 Image Burning Procedure . 4 2.2 Removing the Expansion ROM Image . 4 Chapter 3 Preparing the DHCP Server in Linux . 5 3.1 Case I: InfiniBand Ports. 5 3.1.1 Installing DHCP . 5 3.1.2 Configuring the DHCP Server . 5 3.1.3 Running the DHCP Server . 6 3.1.4 Running the DHCP Client (Optional). 7 3.2 Case II: Ethernet Ports . 7 3.2.1 Extracting the MAC Address – Method I . 7 3.2.2 Extracting the MAC Address – Method II . 8 3.2.3 Placing MAC Addresses in /etc/dhcpd.conf . 8 Chapter 4 Subnet Manager – OpenSM . 9 Chapter 5 BIOS Configuration. 10 Chapter 6 Operation . 11 6.1 Prerequisites. 11 6.2 Starting Boot . 11 Chapter 7 Diskless Machines . 12 7.1 Case I: InfiniBand Ports. 12 7.1.1 Example: Adding an IB Driver to initrd (Linux) . 12 7.2 Case II: Ethernet Ports . 15 7.2.1 Example: Adding an Ethernet Driver to initrd (Linux). 16 Chapter 8 iSCSI Boot . 18 8.1 Configuring an iSCSI Target in Linux Environment . 18 8.1.1 Prerequisites . 18 8.1.2 Configuring the DHCP Server to Boot From an iSCSI Target. 18 Mellanox Technologies 1 Rev 1.4 Document Revision History Table 1 - Document Revision History Revision Date Description Rev 1.4 20-August-2013 • Removed the following sections: • Supported Mellanox Adapter Devices and Firmware • Tested Platforms • Command Line Interface (CLI) • Preparing the DHCP Server in Linux • TFTP Server •WinPE • Updated the following section: • “FlexBoot Package” on page 3 • “Starting Boot” on page 11 Rev 1.3 21-July-2011 • Added ConnectX®-3 • Removed the following sections: • iSCSI Boot Example of SLES 10 SP2 OS • For InfiniHost III Family Devices (PCI Device IDs: 25204, 25218) Rev 1.2.1 16-January-2011 Added section ““Removing the Expansion ROM Image” on page 4 Rev 1.2 15-September-2010 Added module “ipoib_helper.ko” in the section “Case I: InfiniBand Ports” on page 5 Rev 1.1 15-February-2010 Dropped an extra byte of “00” in the dhcp-client-identifier Rev 1.0 21-December-2009 Initial Release Related Documents For further information, please refer to the following documents: • Linux PXE User Guide (www.mellanox.com > Products > Adapter IB/VPI SW > Flex- Boot) • Windows PXE User Guide (www.mellanox.com > Products > Adapter IB/VPI SW > FlexBoot) 2 Mellanox Technologies Rev 1.4 1 Mellanox FlexBoot 1.1 Overview Mellanox FlexBoot is a multiprotocol remote boot technology. FlexBoot supports remote Boot over InfiniBand (BoIB) and over Ethernet. Using Mellanox Virtual Protocol Interconnect (VPI) technologies available in ConnectX® adapt- ers, FlexBoot gives IT Managers’ the choice to boot from a remote storage target (iSCSI target) or a LAN target (Ethernet Remote Boot Server) using a single ROM image on Mellanox Con- nectX products. FlexBoot is based on the open source project iPXE available at http://www.ipxe.org. FlexBoot first initializes the adapter device, senses the port protocol – Ethernet or InfiniBand, and brings up the port. Then it connects to a DHCP server to obtain its assigned IP address and network parameters, and also to obtain the source location of the kernel/OS to boot from. The DHCP server instructs FlexBoot to access the kernel/OS through a TFTP server, an iSCSI target, or some other service. For an InfiniBand port, Mellanox FlexBoot implements a network driver with IP over IB acting as the transport layer. IP over IB is part of the Mellanox OFED for Linux software package (see www.mellanox.com > Products > InfiniBand/VPI SW/Drivers ). The binary code is exported by the device as an expansion ROM image. 1.2 FlexBoot Package The FlexBoot package is provided as a tarball (.tgz extension). Uncompress it using the com- mand “tar zxf <package file name>”. The tarball contains PXE binary files (with the *.mrom extension) for the supported adapter devices. See the release notes file FlexBoot- <flexboot_version>_release_notes.txt for details. The pacakge includes the following files: • dhcpd.conf – sample DHCP configuration file • dhcp.patch – patch file for DHCP v3.1.3 1.3 Reference Documents and Downloads • The Mellanox Firmware Tools (MFT) package and documentation can be downloaded from www.mellanox.com > Products > InfiniBand/VPI Drivers > Firmware Tools. • The MLNX OFED software stack and documentation can be downloaded from www.mellanox.com > Products > InfiniBand Software/Drivers > Linux SW/Drivers. Mellanox Technologies 3 Rev 1.4 Burning the Expansion ROM Image 2 Burning the Expansion ROM Image 2.1 Burning the Image on ConnectX®-2/ ConnectX®-3 Devices This section is valid for ConnectX®-2 devices with firmware versions 2.9.1000 or later and ConnectX®-3 firmware versions 2.30.3000 or later. 2.1.1 Prerequisites 1. Expansion ROM Image The expansion ROM images are provided as part of the Mellanox FlexBoot package and are listed in the release notes file FlexBoot-<flexboot_version>_release_notes.txt. 2. Firmware Burning Tools You need to install the Mellanox Firmware Tools (MFT) package (version 3.0.0 or later) in order to burn the PXE ROM image. To download MFT, see Firmware Tools under www.mellanox.com > Products > InfiniBand/VPI Drivers > Firmware Tools. 2.1.2 Image Burning Procedure To burn the composite image, perform the following steps: Step 1. Obtain the MST device name. Run: # mst start # mst status The device name will be of the form: mt<dev_id>_pci{_cr0|conf0}.1 Step 2. Create and burn the composite image. Run: flint -dev <mst device name> brom <expansion ROM image> Example on Linux: flint -dev /dev/mst/mt26428_pci_cr0 brom ConnectX_26428_ROM-X_X_XXX.mrom Example on Windows: flint -dev mt26428_pci_cr0 brom ConnectX_26428_ROM-X_X_XXX.mrom 2.2 Removing the Expansion ROM Image • Remove the expansion ROM image. Run: flint -dev <mst device name> drom When removing the expansion ROM image, you also remove Flexboot from the boot device list. 1. Depending on the OS, the device name may be superceded with a prefix. 4 Mellanox Technologies Rev 1.4 3 Preparing the DHCP Server in Linux When the boot session starts, the PXE firmware attempts to bring up an adapter network link (port). If it succeeds to bring up a connected link, the PXE firmware communicates with the DHCP server. The DHCP server assigns an IP address to the PXE client and provides it with the location of the boot program. 3.1 Case I: InfiniBand Ports 3.1.1 Installing DHCP FlexBoot requires that the DHCP server runs on a machine which supports IP over IB. 1. Prior to installing DHCP, make sure that Mellanox OFED for Linux is already installed on your DHCP server – see www.mellanox.com. 2. Download and install DHCP v3.1.3 from www.isc.org. A special patch for DHCP is required for supporting IPoIB. The patch file “dhcp.patch” is available under the docs/ directory. 3. To download and install other supported DHCP server versions, please download Mellanox OFED from www.mellanox.com > Products > InfiniBand Software/Drivers > Linux SW/ Drivers and refer to docs/dhcp/README. Standard DHCP fields holding MAC addresses are not large enough to contain an IPoIB hard- ware address. To overcome this problem, DHCP over InfiniBand messages convey a client iden- tifier field used to identify the DHCP session.
Load more

Recommended publications
  • Working with DHCP in Oracle® Solaris 11.2
    ® Working With DHCP in Oracle Solaris 11.2 Part No: E36812 July 2014 Copyright © 1999, 2014, Oracle and/or its affiliates. All rights reserved. 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. If 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 END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
    [Show full text]
  • Pf3e Index.Pdf
    INDEX Note: Pages numbers followed by f, n, priority-based queues, 136–145 or t indicate figures, notes, and tables, match rule for queue assignment, respectively. 137–138 overview, 134–135 Symbols performance improvement, 136–137 # (hash mark), 13, 15 queuing for servers in DMZ, ! (logical NOT) operator, 42 142–144 setting up, 135–136 A on FreeBSD, 135–136 on NetBSD, 136 Acar, Can Erkin, 173 on OpenBSD, 135 ACK (acknowledgment) packets transitioning to priority and class-based bandwidth allocation, queuing system, 131–133 139–140 anchors, 35–36 HFSC algorithm, 124, 126, 142 authpf program, 61, 63 priority queues, 132, 137–138 listing current contents of, 92 two-priority configuration, loading rules into, 92 120–121, 120n1 manipulating contents, 92 adaptive.end value, 188 relayd daemon, 74 adaptive firewalls, 97–99 restructuring rule set with, 91–94 adaptive.start value, 188 tagging to help policy routing, 93 advbase parameter, 153–154 ancontrol command, 46n1 advskew parameter, 153–154, 158–159 antispoof tool, 27, 193–195, 194f aggressive value, 192 ARP balancing, 151, 157–158 ALTQ (alternate queuing) framework, atomic rule set load, 21 9, 133–145, 133n2 authpf program, 59–63, 60 basic concepts, 134 basic authenticating gateways, class-based bandwidth allocation, 60–62 139–140 public networks, 62–63 overview, 135 queue definition, 139–140 tying queues into rule set, 140 B handling unwanted traffic, 144–145 bandwidth operating system-based queue actual available, 142–143 assignments, 145 class-based allocation of, 139–140 overloading to
    [Show full text]
  • Install and Setup DHCP Service
    Install and setup DHCP Service Synopsis: DHCP or Dynamic Host Configuration Protocol allows for automatic management of IP addresses on your internal network. By providing DHCP on your LAN, you eliminate the bother of having to configure manually PCs, laptops, or smart phones. They will automatically get an IP address and be configured with default gateway and DNS server information. It is important that only one DHCP server be active on a network. So, check carefully any other network devices on your network, especially wireless Access Points, to be sure their DHCP service is disabled. I. Installation Log into the Freebsd system as root. (Assumes networking is already configured.) # # cd /usr/ports/net/isc-dhcp44-server && make install clean # II. Startup Configuration Enable DHCP daemon at startup and assign the internal LAN (sk0 in this project) interface; # # echo 'dhcpd_enable="YES"' >> /etc/rc.conf # echo 'dhcpd_ifaces="sk0"' >> /etc/rc.conf # III. Setup configuration file # # cd /usr/local/etc # If there is a dhcpd.conf file, rename it; # # mv dhcpd.conf dhcpd.conf.original # Copy the following text, modify for your personal use, and paste it into a new dhcpd.conf file. You will need to modify the subnet (i.e., your network zero) and mask, the IP pool range, the DNS server (in this case 8.8.8.8 is the Google DNS server), the domain name, the router/gateway and the broadcast address (i.e., your network 255). The settings shown assumes our LAN subnet will be the private range 192.168.1.0 to 192.168.1.255. This machine will have LAN address configured as 192.168.1.254 and will be the default gateway for the LAN network.
    [Show full text]
  • The Complete Freebsd
    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
    [Show full text]
  • Utilising Configuration Management Node Data for Network Infrastructure
    Aalto University School of Science Degree Programme in Computer Science and Engineering Lauri Tirkkonen Utilising configuration management node data for network infrastructure man- agement Master's Thesis Espoo, May 4, 2016 Supervisor: Professor Heikki Saikkonen Advisor: Jaakko Kotim¨akiM.Sc. (Tech.) Aalto University School of Science ABSTRACT OF Degree Programme in Computer Science and Engineering MASTER'S THESIS Author: Lauri Tirkkonen Title: Utilising configuration management node data for network infrastructure man- agement Date: May 4, 2016 Pages: 38 Major: Software Technology Code: T-106 Supervisor: Professor Heikki Saikkonen Advisor: Jaakko Kotim¨akiM.Sc. (Tech.) Configuration management software running on nodes solves problems such as configuration drift on the nodes themselves, but the necessary node configura- tion data can also be utilised in managing network infrastructure, for example to reduce configuration errors by facilitating node life cycle management. Many configuration management software systems depend on a working network, but we can utilise the data to create large parts of the network infrastructure config- uration itself using node data from the configuration management system before the nodes themselves are provisioned, as well as remove obsolete configuration as nodes are decommissioned. Keywords: configuration management, network infrastructure configura- tion, life cycle management Language: English 2 Aalto-yliopisto Perustieteiden korkeakoulu DIPLOMITYON¨ Tietotekniikan koulutusohjelma TIIVISTELMA¨ Tekij¨a: Lauri Tirkkonen
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]
  • Free, Functional, and Secure
    Free, Functional, and Secure Dante Catalfamo What is OpenBSD? Not Linux? ● Unix-like ● Similar layout ● Similar tools ● POSIX ● NOT the same History ● Originated at AT&T, who were unable to compete in the industry (1970s) ● Given to Universities for educational purposes ● Universities improved the code under the BSD license The License The license: ● Retain the copyright notice ● No warranty ● Don’t use the author's name to promote the product History Cont’d ● After 15 years, the partnership ended ● Almost the entire OS had been rewritten ● The university released the (now mostly BSD licensed) code for free History Cont’d ● AT&T launching Unix System Labories (USL) ● Sued UC Berkeley ● Berkeley fought back, claiming the code didn’t belong to AT&T ● 2 year lawsuit ● AT&T lost, and was found guilty of violating the BSD license History Cont’d ● BSD4.4-Lite released ● The only operating system ever released incomplete ● This became the base of FreeBSD and NetBSD, and eventually OpenBSD and MacOS History Cont’d ● Theo DeRaadt ○ Originally a NetBSD developer ○ Forked NetBSD into OpenBSD after disagreement the direction of the project *fork* Innovations W^X ● Pioneered by the OpenBSD project in 3.3 in 2002, strictly enforced in 6.0 ● Memory can either be write or execute, but but both (XOR) ● Similar to PaX Linux kernel extension (developed later) AnonCVS ● First project with a public source tree featuring version control (1995) ● Now an extremely popular model of software development anonymous anonymous anonymous anonymous anonymous IPSec ● First free operating system to implement an IPSec VPN stack Privilege Separation ● First implemented in 3.2 ● Split a program into processes performing different sub-functions ● Now used in almost all privileged programs in OpenBSD like httpd, bgpd, dhcpd, syslog, sndio, etc.
    [Show full text]
  • Alcatel-Lucent Vitalqip DNS/DHCP & IP MANAGEMENT SOFTWARE
    Alcatel-Lucent VitalQIP DNS/DHCP & IP MANAGEMENT SOFTWARE | LUCENT DHCP RELEASE 5.4 BUILD 45 RELEASE NOTES ALCATEL-LUCENT PROPRIETARY This document contains proprietary information of Alcatel-Lucent and 190-409-113R5.4 is not to be disclosed or used except in accordance with applicable NOVEMBER 2008 agreements. ISSUE 12 Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright © 2008 Alcatel-Lucent. All Rights Reserved. Alcatel-Lucent – Proprietary See notice on first page Contents About this document vii Reason for reissue..........................................................................................................vii Conventions used............................................................................................................ ix Typographical conventions............................................................................................. ix Technical Support............................................................................................................ x How to comment............................................................................................................. xi 1 Overview 1-1 2 Release components 2-1 Software deliverables..................................................................................................2-2 Software
    [Show full text]
  • CREID: Development of Reliable and Scalable DHCP System for Carrier IP Networks
    CREID: Development of reliable and scalable DHCP system for carrier IP networks Katsuhiro Naito Department of Electrical and Electronic Engineering, Mie University, 1577 Kurimamachiya, Tsu, 514-8507, Japan Email: [email protected] Makoto Nishide Net Step Inc. 213 Obatachomiyamae, Ise, 519-0504, Japan Email: [email protected] Eiji Miyazoe OSS BroadNet Inc. 3-5-7 Hisamoto, Takatsuku, Kawasaki, 213-0011, Japan Email: [email protected] Abstract— Dynamic host configuration protocol (DHCP) is of ISC-DHCP is distributed over various kinds of UNIX OS. essential service to configure information about networks at Therefore, many users use the software in local networks. On user terminals in Internet service providers (ISPs). Therefore, the contrary, the transaction performance of ISC-DHCP is not many DHCP programs are released in Internet. However, few free software DHCP programs can achieve required reliability high comparing to the requirement in commercial large ISPs. and scalability in ISP’s usage. In this paper, we develop the Additionally, the fail-over mechanisms of ISC-DHCP are not reliable and scalable DHCP system called CNR Emulator on enough to achieve a stable DHCP service in commercial ISPs ISC-DHCP (CREID) based on free software such as ISC-DHCP, [9], [10], [11]. Duplicated Replicated Block Device (DRBD), and Pacemaker. In this paper, we develop the reliable and scalable DHCP ISC-DHCP supports Internet Protocol (IP) v4 and IPv6 that are required in commercial ISP services. DRBD and Pacemaker system called CNR Emulator on ISC-DHCP (CREID) based can construct clustering systems over some physical computers. on free software such as ISC-DHCP, Duplicated Replicated From the numerical results, we can find that the developed DHCP Block Device (DRBD) [12], and Pacemaker [13].
    [Show full text]
  • V3.5 IP Address Management Software
    GestióIP IPAM v3.5 IP address management software Documentation v1.11 www.gestioip.net GestióIP Copyright © Marc Uebel 2021 Documentation GestióIP IPAM v3.5 Table of Contents 1 Introduction......................................................................................................................................7 2 Use....................................................................................................................................................8 2.1 Access.......................................................................................................................................8 2.2 Show networks..........................................................................................................................8 2.2.1 Root networks.................................................................................................................10 2.3 Show hosts..............................................................................................................................11 2.3.1 Host list view..................................................................................................................11 2.3.2 Host overview.................................................................................................................13 2.3.3 Host status view..............................................................................................................13 2.3.4 Host check.......................................................................................................................14
    [Show full text]
  • CERN Dhcpv6 Implementation
    CERN DHCPv6 implementation WLCG Workshop 2017 - Manchester 21st of June 2017 [email protected] Why DHCPv6 and not SLAAC CERN DHCP[v6] servers offer a lease only to registered MAC addresses, because of: - device tracking for - user’s own security - user traceability - user support - DNS and Firewall automation - static address assignment (optional) 2 DHCPv6 client-server exchange 1. The client sends a Solicit message to the All_DHCP_Relay_Agents_and_Servers multicast address, requesting the assignment of addresses and other configuration information 2. The server responds with a Reply message that contains the confirmed addresses and configuration. Each address assigned to the client has associated preferred and valid lifetime … 3a. Periodically, the client sends a Renew message to the server to request an extension of the lifetimes of an address 3b. The server sends a Reply message to the client with the new lifetimes, allowing the client to continue to use the address without interruption [RFC3315] 3 DHCPv6 Options - IPv6 address, OPTION_IAADDR [RFC3315] - DHCPv6 timers: - preferred-lifetime (time a valid address is preferred) - valid-lifetime (time an address remains in valid state) [RFC2462] - DNS servers, OPTION_DNS_SERVERS [RFC3646] Other options exist 4 DHCPv6 client-server exchange # tcpdump -i eth0 -vvv -n ip6 and port 547 3:52:22.644967 IP6 (hlim 60, next-header UDP (17) payload length: 106) 2001:db8:305:10::2.dhcpv6-server > 2001:db8:1000::9.dhcpv6-server: [udp sum ok] dhcp6 relay-fwd (linkaddr=2001:db8:221:5::1 peeraddr=fe80::16:3eff:fe01:b3a1
    [Show full text]
  • Download CVS 1.11.1P1-3 From: Ftp://Ftp.Software.Ibm.Com/Aix/Freesoftware/Aixtoolbox/RPMS/Ppc/Cvs/ Cvs-1.11.1P1-3.Aix4.3.Ppc.Rpm
    2003 CERT Advisories CERT Division [DISTRIBUTION STATEMENT A] Approved for public release and unlimited distribution. http://www.sei.cmu.edu REV-03.18.2016.0 Copyright 2017 Carnegie Mellon University. All Rights Reserved. This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be con- strued as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trade mark, manu- facturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100 NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribu- tion. Please see Copyright notice for non-US Government use and distribution.
    [Show full text]