RedHat linux7 虚拟化+集群安装精简手册

合集下载

Red Hat Linux 7.0为例说明安装过程

以Red Hat Linux 7.0为例说明安装过程，如下：塞入第一张光盘，让计算机从CDROM启动，马上就出现了简洁的欢迎信息。

敲回车，可以进入默认的安装模式-图形界面，鼠标操作，基本和6.1、6.2类似。

敲入“text”，可以进入文本安装模式，和6.0以前的版本相似。

不支持鼠标，需要使用键盘操作，主要是为了兼容。

如果你的计算机使用图形模式不好用，比如，屏幕出奇的大，按钮怎么也找不到，那就使用此模式。

打入“expert”，可以进入所谓的专家模式，实际上就是安装程序把所有的步骤都交给了你，随遍你怎么设置，如果你的机器有些特殊的硬件，安装程序无法正确配置，那就试试这样的方式。

敲入“linux rescue”，会进入“救援”模式，主要用于原有的Linux系统无法正常启动的情况。

使用这个办法，实际上你是进入了一个微型的Linux系统，里面有许多可以用来拯救操作系统的工具程序。

如果你有特殊硬件的安装驱动盘，就敲入“linux dd”，它会提示你插入软盘，读取进系统。

以便更好的利用它们。

敲回车进入默认安装模式，内核启动后，出现语言选择选单，18种语言，可惜就是没有中文。

选“english”，再挑键盘，鼠标。

值得一提的是，我的双飞燕4D+鼠标自动的被认出三键。

要知道，第三键在Linux环境下的作用很大。

许多操作可以用它来实现，如果你没有三键鼠标，就使用模拟三键的方法，左右键同时按下，即表示第三键。

安装界面非常好用，左面有及时详尽的帮助信息，右面是选项。

完全鼠标操作。

在系统安装的阶段，最重要的事情是看清楚左面的说明！因为许多的朋友都有过惨痛的教训-漫不经心，结果，硬盘里面所有的东西都被干掉了，系统瘫痪。

简直欲哭无泪，好些人不停的到网上请教恢复的办法。

这里详细说明一下，RedHat 7.0有两大类安装方式：Install 或者upgrade。

前者包含下面三种选择：WorkStation、ServerSystem、Custem System。

RedHat7 zookeeper集群(含observer配置)安装

一、服务器版本查看cat /etc/redhat-release二、新建目录：mkdir -p /softwares三、解压下载3.4.9版本，解压到/softwares目录cd /softwarestar zxvf zookeeper-3.4.9.tar.gz四、配置将conf目录下的zoo_sample.cfg改为zoo.cfgcd /softwares/zookeeper-3.4.9/confmv zoo_sample.cfg zoo.cfgmkdir -p /softwares/zookeeper-3.4.9/data查看配置cd /softwares/zookeeper-3.4.9/conf【yum install vim】vim zoo.cfg注意其中tickTime=2000dataDir=/softwares/zookeeper-3.4.9/dataclientPort=2181五、启动单机测试cd /softwares/zookeeper-3.4.9/bin(没有的话使用chmod u+x *.sh使以sh为扩展名的脚本都有运行权限) ./zkServer.sh start./zkServer.sh status使用命令./zkCli.sh -server 127.0.0.1:2181连接到zookeeper服务。

六、配置主机名和ip的映射vim /etc/hosts其中编辑增加如下内容192.168.18.202 logsrv01192.168.18.203 logsrv02192.168.18.208 logsrv03192.168.18.201 obsrv01七、配置Zookeeper的配置文件cd /softwares/zookeeper-3.4.9/bin./zkServer.sh stopcd /softwares/zookeeper-3.4.9/confvim zoo.cfg在clientPort=2181下增加如下内容server.1=logsrv01:2887:3887server.2=logsrv02:2888:3888server.3=logsrv03:2889:3889server.4=obsrv01:2886:3886:observerps: server.A=B：C：D：其中A 是一个数字，表示这个是第几号服务器；B 是这个服务器的ip 地址；C 表示的是这个服务器与集群中的Leader 服务器交换信息的端口；D 表示的是万一集群中的Leader 服务器挂了，需要一个端口来重新进行选举，选出一个新的Leader，而这个端口就是用来执行选举时服务器相互通信的端口。

RedHat LINUX安装全步骤(附图)

LINUX软件安装步骤1.在Vmware 中创建一个Linux 的虚拟机版本是Red Hat Linux ，其中硬盘最少要有2GB 的空间（建议分4GB 其他硬盘，网卡的配置和Windows 虚拟机一样即可）。

2.把Vmware 的光驱制定到对应的镜像文件上，我们这里是linux iso 文件中的第一张盘。

3.启动虚拟机，由光盘进入。

在这个界面中输入linux text 后回车才能进入文本安装界面。

4.提示检测介质。

因为我们使用的是镜像文件，所以可以直接单击Skip 如果使用的是光盘最好还是检测一下比较好。

（在LINUX 文本模式中基本都是使用键盘进行操作，鼠标也支持但是不像在Windos 中那样好用。

用户可以通过Tab键和方向键来切换选项，空格和回车来确定）如果上面选择的是Skip就会直接跳到第8步。

5.开始检测。

如果是使用的光盘CD 需要先插入CD 后在Test 因为我们使用的是镜像文件所以就可以直接Test6.检测完毕。

选择OK7.提示是否检测其他的盘。

如果你为了保险起见可以继续检测，但是时间可能会长一些。

8.选择语言安装过程，在这里选择英语。

（如果选择的不是英语的话，在以后的一些提示显示中会出现乱码看不懂）9.选择键盘类型，在这里选择us 即可。

10.选择鼠标类型，在Linux 这类操作系统中，经常用到三键鼠标，因此，除了选择鼠标类型外，一般还选中下面的“Emulate 3 Buttons?”，这样同时点击鼠标左右键，代表点击中键。

11.选择安装类型。

在这里我们选择第4个Custom（定制）。

12.准备分区。

在这里选择Autopartition 。

13.这里会让用户选择如何处理硬盘上的原始分区。

因为我们是新建的所以选那个都无所谓，但是如果在已经安装好Windows 的系统上进行安装，一般选择第三项。

意思就是使用硬盘当中没有使用的空间来创建相应的分区。

在下面会让用户选择。

要安装到那个硬盘中，在这里只有一个硬盘sda ，所以直接选择即可。

redhat7安装图文教程

redhat7安装图文教程 1.从光盘启动,选择"installred hat enterprise linux 7.0" 2.选择用那种语言进行安装 3.选择"date&time" 4.设置时区 5.选择语言支持 6.选择中文支持 7.对软件包进行选择 8.选择要安装的软件包 9.选择自动分区 10.选择开始安装 11.设置root用户密码 12.安装完成 13.点击license information 14.接受协议 15.设置kdump 16.进入登录界面 17.登录成功 2942b39d61 分享于 2020-08-02 16:44:10.0 redhat7安装图文教程文档格式: .pdf 文档页数: 8页文档大小: 794.65k 文档热度: 文档分类: 管理/人力资源 -- 管理学资料文档标签: redhat7安装图文教程系统标签: 图文安装教程软件包 kdump 时区
13.点击 LICENSE INFORMATION 14.接受协议
15.设置 Kdump 16.进入登录界面 17.登录成功
1.从光盘启动，选择“install Red Hat Enterprise Linux 7.0" 2.选择用那种语言进行安装
3.选择”DATE&支持 6.选择中文支持
7.对软件包进行选择 8.选择要安装的软件包
9.选择自动分区 10.选择开始安装
11.设置 root 用户密码 12.安装完成

Linux操作系统(RHEL7／CentOS7)课件第1章 Linux简介与安装

第1章 Linux简介与安装
一本好的入门教材可以让读者快速领悟Linux的操作方式和系统的基本使用。
目前Linux的入门教材主要针对两类读者：非技术型、技术型。
非技术型读者：对Linux不是真的感兴趣，只是用Linux上网、听音乐、编辑文档等。针对非技术型用户的入门教材以插图为主，讲的内容主要是在GUI下的操作（鼠标），所以，这种使用Linux 的方式还是Windows的思维方式。
第1章 Linux简介与安装
1.1 Linux简介 1.2 实例—硬盘安装RedHat Enterprise Linux 7 1.3 引导工具GRUB的设置与应用 1.4 引导工具GRUB2的设置与应用 1.5 RHEL7的启动流程 1.6 本章总结 1.7 习题
本书的重点在前4章，只有学好前4章，读者才算对Linux真正入门，后面几章的学习才会比较轻松，甚至可以自学。随着读者学习、掌握越来越多的计算机主要课程的相关知识，你就可以在Linux的世界里纵深发展了。因此，本书是一本比较好的入门教材。也希望读者在学习的过程中重基础、重理论，切忌浮躁。
第1章 Linux简介与安装
技术型读者：对Linux很感兴趣，针脱离Windows的思维方式，这样会给读者以后的进一步学习带来很大帮助，也能使读者逐步领悟Linux的精髓（命令行）所在。
第1章 Linux简介与安装
本书针对的是技术型读者，主要是计算机专业（或相关专业）的学生。
本章学习目标：
❖ 了解Linux的起源、特点、内核版本和发行版本的区别 ❖ 了解硬盘分区和MBR ❖ 理解计算机的启动顺序 ❖ 理解引导工具GRUB/GRUB2 ❖ 理解RHEL 7的详细启动流程 ❖ 熟练掌握RedHat Enterprise Linux 7的安装 ❖ 熟练掌握系统引导工具GRUB/GRUB2设置及使用

Red Hat Enterprise Linux 7.X LE ALT 安装指南说明书

Installing Red Hat Enterprise Linux on IBM Power System IC922 (9183-22X) servers with virtual mediaQuick Start Guide for installing Linux® on IBM® Power® System IC922 (9183-22X) server.Version 1.0.0This guide helps you install Red Hat Enterprise Linux on IBM Power System IC922 (9183-22X) server.Note:© Copyright IBM Corp. 2020. US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.IBM, the IBM logo, and ® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" (/legal/copytrade.shtml).About this taskOverviewUse this information to install Red Hat® Enterprise Linux 7.X LE ALT on a non-virtualized or bare metal IBM Power System IC922 (9183-22X) server.To install Red Hat Enterprise Linux on IBM Power System IC922 (9183-22X) servers by using virtualmedia, use a PC and access the BMC web page by using a browser. You can connect your PC to theOpenBMC port of the server over a configured network so that the service processor can read the .iso file from the PC during the installation of the operating system.For a list of supported distributions, see Supported Linux distributions for POWER8® and POWER9™ Linux on Power systems.Procedurepleting the prerequisites and booting your firmwareBefore you power on the system, ensure that you have the following items:•Ethernet cable.•USB Keyboard.–Power cords and outlet for your system.•SSH client.•PC or Notebook with Linux installed on it.•Notes:–You do not need an ssh client and a PC with Linux installed on it, if you are using a VGA screen andkeyboard.–You do not need a USB keyboard if you are using a serial connection.Complete these steps:•Download the ISO image of Red Hat Enterprise Linux 7.X LE ALT from the https:///products/red-hat-enterprise-linux/#addl-arch website to your computer that you use to access theOpenBMC by using a web browser. Take the link for Downloads for Red Hat Enterprise Linux forPower, little endian. Log into your Red Hat account (if you have not already done so). Select RedHat Enterprise Linux for Power 9 from the Product Variant list. Look for the Red Hat EnterpriseLinux for Power 9 (v. 7.x for ppc64le) ISO file. The downloaded ISO file will include rhel-alt......isorather than rhel....iso in the path name.•If your system belongs in a rack, install your system into that rack. For instructions, see IBM Power Systems information at https:///support/knowledgecenter/POWER9/p9hdx/POWER9welcome.htm.•Make one of the following connections:–Connect an Ethernet cable to the dedicated BMC Ethernet port that is located close to the USB 3.0 port and it is labeled M. Connect the other end to your PC or Notebook which you use to configure the IP address.–You can also connect to the serial port of the server by using a serial connection.•Attach the USB to serial (RS232) adapter cable to the IPMI serial 9-pin D-shell connector on the Power system.•Attach USB connection to USB port on either PC or Notebook.•Open a terminal emulator program such as PuTTY or minicom.•Set the communications to use the following options:–115200 baud rate–Data bits of 8–Parity of None–Stop bits of 1•Connect the power cords to the system and plug them into the outlets.At this point, your firmware is booting. Wait for the green LED on the power button to start flashing, indicating that it is ready to use. If your system does not have a green LED indicator light, then wait 1 -2 minutes.2.Configuring the IP addressNote: You can use either a serial connection or a keyboard and monitor to connect to the BMC. After the IP details are configured, you can use SSH connection. For more information, see Managing BMC-based systems.To set up or enable your network connection to the BMC firmware, use the Petitboot bootloader interface. Follow these steps:a.Your system will power on to the Petitboot bootloader menu. This process usually takes about 1 - 2minutes to complete, but might take 5 - 10 minutes on the first boot or after a firmware update. Do not walk away from your system! When Petitboot loads, your monitor becomes active and you will need to push any key to interrupt the boot process.b.At the Petitboot bootloader main menu, select Exit to Shell.c.Program your BMC IP address by running the following commands:Note: The shared BMC port is located near to the USB 3.0 port and it is labeled 1 and the dedicated BMC port is located next to the shared BMC port and it is labeled M.1)Set the mode to static by running this command: ipmitool lan set 2 ipsrc static2)Set your IP address by running this command: ipmitool lan set 2 ipaddr ip_addresswhere ip_address is the static IP address that you are assigning to this system.3)Set your netmask by running this command: ipmitool lan set 2 netmasknetmask_address where netmask_address is the netmask for the system.4)Set your gateway server by running this command: ipmitool lan set 2 defgw ipaddrgateway_server where gateway_server is the gateway for this system.5)For the shared BMC port run the following command: Run ipmitool lan print 16)For the dedicated BMC port run the following command: Run ipmitool lan print 2d.To reset your firmware, run the following command: ipmitool mc reset cold.e.You should be able to ping the BMC now. If your ping does not return successfully within areasonable amount of time (2 - 3 minutes), try these additional steps:1)Power your system off with this command from the petitboot shell: poweroff2)Unplug the power cords from the back of the system. Wait 30 seconds and then apply power toboot BMC.3.Creating a bootable virtual mediaa.Open a supported web browser. In the address bar, enter the IP address of the BMC that you wantto connect to. For example, you can use the format https://<BMC IP> in the address bar of the web browser.b.From the OpenBMC logon window, enter the Host address of the BMC and the username andpassword that is assigned to you.c.Then select Server control → Virtual Media to network-attach the ISO image to the IBM PowerSystem IC922 (9183-22X) server. After clicking Start, the ISO is available to the server to start the operating system installation process.4.Powering on your server by using a PC or NotebookNote: After your system powers on, the Petitboot interface loads. If you do not interrupt the boot process by pressing any key within 10 seconds, Petitboot automatically boots the first option.To power on your server from a PC or Notebook that is running Linux, follow these steps:a.Connect an Ethernet cable from the BMC port to a PC or Notebook. Or you can also make sure yourPC or Notebook is on the same network as the BMC firmware.b.Open a terminal program on your PC or Notebook.c.Log in to the BMC by running the following commands.ssh root@<BMC server_ip_address>root@<BMC server password>where BMC server_ip_address is the IP address of the BMC and BMC server password is thepassword to authenticate.Note: The default username is root and the default password is 0penBmc (where, 0penBmc is using a zero and not a capital O).d.To power on your server, run the following command:$ root@<BMC server_ip_address>:~# obmcutil powerone.Connect to OS console and use the default password 0penBmc.ssh -p 2200 root@<BMC server_ip_address>root@where BMC server_ip_address is the IP address of the BMC and BMC server password is thepassword to authenticate.5.Configuring PetitbootAfter the system powers on, the Petitboot bootloader scans local boot devices and network interfaces to find boot options that are available to the system.a.After you start the system, Petitboot displays the virtual media boot device, and you can select theboot entry, but do not start the installation. If you start the installation, you might not be able to finish the installation and the system might show errors similar to the following string:dracut-initqueue[3537]: Warning: dracut-initqueue timeout - starting timeoutscriptsNote: Select Rescan devices if the virtual media boot device does not appear.b.Record the UUID of the virtual media boot device. The UUID of the virtual media boot device in thefollowing example is 2018-10-10-22-13-55-00.Petitboot (v1.11) 9183-22X 78002BA____________________________________________________________________________________[USB: sdc / 2018-10-10-22-13-55-00]Rescue Red Hat Enterprise Linux Alternate Architectures system (64 bit keTest this media & Install Red Hat Enterprise Linux Alternate Architectures* Install Red Hat Enterprise Linux Alternate Architectures 7.6 (64 bit kernelSystem informationSystem configurationSystem status logLanguageRescan devicesRetrieve config from URLPluginsExit to shell___________________________________________________________________________________Enter = accept, e=edit, n=new, x=exit, l=language, g=log, h=helpc.Select Install Red Hat Enterprise Linux Alternate Architectures 7.6 (64 bit kernel) and press e(Edit) to open the Petitboot Option Editor window.d.Move the cursor to the Boot arguments section and add the following information: inst.textinst.stage2=hd:UUID=your_UUID where your_UUID is the UUID that you recorded.Petitboot Option Editor_______________________________________________________________________Device: ( ) sda2 [3cb1868c-7fd4-466a-a7b0-70942ca452cd](*) sdb1 [2018-10-10-22-13-55-00]( ) Specify paths/URLs manuallyKernel: /ppc/ppc64/vmlinuzInitrd: /ppc/ppc64/initrd.imgDevice tree:Boot arguments: ro inst.text inst.stage2=hd:UUID=2018-10-10-22-13-55-00[ OK ] [ Help ] [ Cancel ]________________________________________________________________________tab=next, shift+tab=previous, x=exit, h=helpe.Select OK to save your options and return to the Main menu.f.Verify that Install Red Hat Enterprise Linux Alternate Architectures 7.6 (64 bit kernel) isselected and then press Enter to begin your installation.pleting your installationAfter you select to boot the Red Hat Enterprise Linux 7.X LE ALT installer, the installer wizard walks you through the steps.a.Follow the installation wizard for Red Hat Enterprise Linux to set up disk options, your usernameand password, time zones, and so on. The last step is to restart your system.b.After the system restarts, Petitboot displays the option to boot the Red Hat Enterprise Linux releasenumber. Select this option and press Enter.Note: Be sure to check for firmware updates. See https:///support/knowledgecenter/ POWER9/p9ei8/p9ei8_fixes_kickoff.htmWhat to do nextMore informationFor more information, see the following resources:•IBM Knowledge Center at https:///support/knowledgecenter/.•IBM Power System IC922 (9183-22X) server Redbook at /redpapers/ pdfs/redp5584.pdf.•The Linux on Power developer portal at Linux on Power developer portal.。

Redhat7系统安装教程

Redhat7系统安装教程系统的安装部署过程第⼀个历程：进⼊系统引导界⾯进⾏配置引导项说明：1. 安装centos7系统（*）2. 测试光盘镜像并安装系统3. 排错模式（修复系统重置系统密码）===============================================补充：centos7系统⽹卡名称centos6默认系统的⽹卡名称为 eth0 eth1centos7默认系统的⽹卡名称为 ens33 ens34如何调整⽹卡名称：选择安装Install CenOS7--tab键 -- net.ifnames=0 biosdevname=0===============================================从虚拟主机返回到windows系统⽅法：ctrl+alt第⼆个历程：对安装系统语⾔进⾏设置第三个历程：对系统安装过程进⾏配置1. 系统⽹络的配置2. 系统分区的配置Linux系统磁盘分区知识简介:在分区之前，需要先简单介绍⼀下磁盘分区相关知识，便于⼤家更好地理解学习。

1）磁盘在使⽤前⼀般要先分区（相当于买房要有⼏居⼀样）。

2）磁盘分区有主分区、扩展分区和逻辑分区之分。

⼀块磁盘最多可以有4个主分区，其中⼀个主分区的位置可以⽤⼀个扩展分区替换，在这个扩展分区内可以划分多个逻辑分区。

3）如果规划的分区数量超过4个，则分区组合为3primary+1extend或2p+1e或1p+1e。

4）⼀块磁盘最多只能有⼀个扩展分区，扩展分区不能直接使⽤，必须在扩展分区上划分逻辑分区，然后格式化（创建⽂件系统），之后才能存取数据或装系统。

磁盘分区命名及编号⽅式（1）以设备名命名在Linux系统中，磁盘设备对应于系统中的特殊⽂件，这些特殊的⽂件存放在“/dev”⽬录中，不同的设备对应的设备名称如下：❑系统的第⼀块有IDE接⼝的硬盘称为/dev/hda。

❑系统的第⼆块有IDE接⼝的硬盘称为/dev/hdb。

RedHat7 FlumeNg安装

一、服务器版本查看cat /etc/redhat-release二、新建目录：mkdir -p /softwares上传apache-flume-1.7.0-bin.tar.gz到/softwares三、解压cd /softwarestar zxvf apache-flume-1.7.0-bin.tar.gz四、配置文件创建flume-env.sh文件cp /softwares/apache-flume-1.7.0-bin/conf/flume-env.sh.template /softwares/apache-flume-1.7.0-bin/conf/flume-env.sh示例如下图：创建测试目录mkdir -p /softwares/data/logsmkdir -p /softwares/data/logs/channels/a1/checkpointmkdir -p /softwares/data/logs/channels/a1/datamkdir -p /softwares/data/local/collectormkdir -p /softwares/data/logs/channels/a2/checkpointmkdir -p /softwares/data/logs/channels/a2/data创建配置文件cp /softwares/apache-flume-1.7.0-bin/conf/flume-conf.properties.template /softwares/apache-flume-1.7.0-bin/conf/flume.confvim /softwares/apache-flume-1.7.0-bin/conf/flume.conf查看被占用的PIDnetstat -aon | grep "4545"在文件末尾加入以下配置：# Agent a1a1.sources = r1a1.sinks = k1a1.channels = c1# source 配置a1.sources.r1.type = execmand = tail -F /softwares/data/logs/system.log# sink 配置a1.sinks.k1.type=avroa1.sinks.k1.hostname=192.168.18.200a1.sinks.k1.port=4545# channel 配置a1.channels.c1.type = filea1.channels.c1.checkpointDir=/softwares/data/logs/channels/a1/checkpointa1.channels.c1.dataDirs = /softwares/data/logs/channels/a1/data# 绑定source、single到channel上a1.sources.r1.channels = c1a1.sinks.k1.channel = c1#ageng a2a2.sources=r2a2.sinks=k2a2.channels=c2#a2 source 配置a2.sources.r2.type=avroa2.sources.r2.bind=0.0.0.0 # 使用0.0.0.0表示绑定机器所有的接口a2.sources.r2.port=4545#a2 sink 配置将合并后的日志数据写到/softwares/data/local/collector目录下a2.sinks.k2.type = file_rolla2.sinks.k2.sink.directory = /softwares/data/local/collectora2.sinks.k2.sink.rollInterval=3600##下面是注释掉的代码为配置sink ,日志按天合并后保存到单独的文件夹中#a2.sinks.k2.type=hdfs#a2.sinks.k2.hdfs.path=hdfs://hadoop-master:9000/events/%y-%m-%d#a2.sinks.k2.hdfs.filePrefix=events-#a2.sinks.k2.hdfs.rollInterval=0#a2.sinks.k2.hdfs.rollSize=0#a2.sinks.k2.hdfs.rollCount=0#eLocalTimeStamp=true#a2 channel配置a2.channels.c2.type = filea2.channels.c2.checkpointDir=/softwares/data/logs/channels/a2/checkpoint a2.channels.c2.dataDirs = /softwares/data/logs/channels/a2/data# 绑定source、single到channel上a2.sources.r2.channels=c2a2.sinks.k2.channel=c2scp -r /softwares/apache-flume-1.7.0-bin 192.168.18.200:/softwares/scp -r /softwares/apache-flume-1.7.0-bin 192.168.18.205:/softwares/五、生成测试数据的python小程序cd /softwares/apache-flume-1.7.0-bin/binvim runTestLog.py#!/usr/bin/pythonimport osimport randomfrom time import ctime,sleepfor i in range(1,1000000):smil=random.randint(50,100)print smil/1000.0com="echo \"hello message from 192.168.18.200\t"+str(i)+"\">>/softwares/data/logs/system.log";print comos.system(com)sleep(smil/1000.0)运行python runTestLog.py六、运行在192.168.18.200上使用下面命令启动Agent2(a2)cd /softwares/apache-flume-1.7.0-bin/bin./flume-ng agent --conf /softwares/apache-flume-1.7.0-bin/conf --conf-file /softwares/apache-flume-1.7.0-bin/conf/flume.conf --name a2 -Dflume.root.logger=INFO,console &在192.168.18.200另启动一个终端，运行下面命令启动Agent1(a1)cd /softwares/apache-flume-1.7.0-bin/bin./flume-ng agent --conf /softwares/apache-flume-1.7.0-bin/conf --conf-file /softwares/apache-flume-1.7.0-bin/conf/flume.conf --name a1 -Dflume.root.logger=INFO,console &分别在192.168.18.204~205上同样启动Agent1(a1)cd /softwares/apache-flume-1.7.0-bin/bin./flume-ng agent --conf /softwares/apache-flume-1.7.0-bin/conf --conf-file /softwares/apache-flume-1.7.0-bin/conf/flume.conf --name a1 -Dflume.root.logger=INFO,console &。

RHEL 7.0系统安装配置图解教程

RHEL 7.0系统安装配置图解教程截止目前RHEL 7.x最新版本为RHEL 7.0，下面介绍RHEL 7.0的具体安装配置过程,需要的朋友可以参考下服务器相关设置如下：操作系统：RHEL 7.0 64位IP地址：192.168.21.128网关：192.168.21.2DNS：8.8.8.8 8.8.4.4备注：生产服务器如果是大内存（4G以上内存），建议安装64位版本rhel-server-7.0-x86_64-dvd.iso一、安装RHEL 7.0成功引导系统后，会出现下面的界面界面说明：Install Red Hat Enterprise Linux 7.0 安装RHEL 7.0Test this media & install Red Hat Enterprise Linux 7.0 测试安装文件并安装RHEL 7.0 Troubleshooting 修复故障这里选择第一项，安装RHEL 7.0，回车，进入下面的界面选择语言：中文-简体中文（中国）#正式生产服务器建议安装英文版本继续选择-系统-安装位置，进入磁盘分区界面选择-其它存储选项-分区-我要配置分区，点左上角的“完成”，进入下面的界面分区前先规划好swap #交换分区，一般设置为内存的2倍/ #剩余所有空间备注：生产服务器建议单独再划分一个/data分区存放数据点左下角的“+”号挂载点：swap 期望容量：2048 添加挂载点继续点左下角的“+”号挂载点：/期望容量：13.31GB #剩余所有空间添加挂载点点左上角的“完成”，进入下面的界面接受更改，进入下面的界面开始安装，进入下面的界面选择-用户设置-ROOT密码，进入下面的界面设置Root密码如果密码长度少于8位，会提示要按“完成”两次来确认，安装继续安装完成之后，会进入下面的界面点重启系统重新启动进入登录界面账号输入root 回车再输入上面设置的root密码回车系统登录成功二、设置IP地址、网关DNS说明：RHEL 7.0默认安装好之后是没有自动开启网络连接的！cd /etc/sysconfig/network-scripts/ #进入网络配置文件目录vi ifcfg-eno16777736 #编辑配置文件，添加修改以下内容TYPE="Ethernet"BOOTPROTO="static" #启用静态IP地址DEFROUTE="yes"IPV4_FAILURE_FATAL="no"IPV6INIT="yes"IPV6_AUTOCONF="yes"IPV6_DEFROUTE="yes"IPV6_FAILURE_FATAL="no"NAME="eno16777736"UUID="8071cc7b-d407-4dea-a41e-16f7d2e75ee9" ONBOOT="yes" #开启自动启用网络连接IPADDR0="192.168.21.128" #设置IP地址PREFIX0="24" #设置子网掩码GATEWAY0="192.168.21.2" #设置网关DNS1="8.8.8.8" #设置主DNSDNS2="8.8.4.4" #设置备DNSHWADDR="00:0C:29:EB:F2:B3"IPV6_PEERDNS="yes"IPV6_PEERROUTES="yes":wq! #保存退出service network restart #重启网络ping #测试网络是否正常ip addr #查看IP地址三、使用系统镜像文件配置本地yum源1、使用WinSCP.exe工具上传系统镜像文件rhel-server-7.0-x86_64-dvd.iso到/usr/local/src目录2、使用Putty.exe工具远程连接到RHEL服务器3、挂载系统镜像文件mkdir /media/cdrom #新建镜像文件挂载目录cd /usr/local/src #进入系统镜像文件存放目录ls #列出目录文件，可以看到刚刚上传的系统镜像文件mount -t iso9660 -o loop /usr/local/src/rhel-server-7.0-x86_64-dvd.iso /media/cdrom #挂载系统镜像cd /media/cdrom #进入挂载目录，使用ls命令可以看到已经有文件存在了备注：umount /media/cdrom #卸载系统镜像4、设置开机自动挂载系统镜像文件vi /etc/fstab #添加以下代码。

RedHatlinux7-虚拟化+集群安装精简手册簿

RedHat linux 7虚拟化环境集群安装精简手册1、前期准备挂载磁盘/* 通过制作iso，方便后续安装动作，在知识库中应形成iso镜像体系 */dd if=/dev/sr0 of=/app/rh71.isomount -o loop /app/rh71.iso /mnt挂载制作的isomount -loop /dev/sr0 /mnt查看少什么包/* 如果想要是用vgscan指令，系统至少需要安装lvm2包，这个从安装好的系统上查 */ [root@jttldb1 host5]# rpm -qf /sbin/vgscanlvm2-2.02.83-3.el6.x86_64常用包安装net-tools (ifconfig等用)yum -y install nautilus-open-terminal（右键添加terminal）配置yum/* 根据具体挂载的路径和版本调整 */建立文件/etc/yum.repos.d/mycdrom.repo[Base]name=RHELbaseurl=file:///mntenabled=1gpgcheck=0[Cluster]name=RHELbaseurl=file:///mnt/addons/HighAvailabilityenabled=1gpgcheck=0配置ipIPADDR=10.88.89.100GATEWAY=10.88.89.1NETMASK=255.255.255.0ONBOOT=yes单网卡配置多ipifconfig team0:0 10.88.89.101 netmask 255.255.255.0 （临时添加一个ip，重启后消失，如果想永久拥有，需要配置ifcfg-ens32:0 文件）临时文件取消：ifconfig ens32:0 down网卡绑定1）创建组接口（会生产一个ifcfg-team0）nmcli con add type team con-name team0 ifname team0 config '{"runner":{"name":"activebackup"}}'nmcli con del team0 （删除绑定team）2）查看组接口配置nmcli con show3）给组接口添加设备nmcli con add type team-slave con-name team0-port1 ifname enp11s0f0 master team0 nmcli con add type team-slave con-name team0-port2 ifname enp16s0f0 master team0 nmcli con mod type team-slave con-name team0-port2 ifname enp16s0f0 master team04）配置ip[root@jttldb2 network-scripts]# more ifcfg-team0DEVICE=team0DEVICETYPE=TeamTEAM_CONFIG="{\"runner\":{\"name\":\"activebackup\"}}"BOOTPROTO=noneIPADDR=10.88.89.100PREFIX=25GATEWAY=10.88.89.1DEFROUTE=yesIPV4_FAILURE_FATAL=yesIPV6INIT=yesIPV6_AUTOCONF=yesIPV6_DEFROUTE=yesIPV6_PEERDNS=yesIPV6_PEERROUTES=yesIPV6_FAILURE_FATAL=noNAME=team0UUID=afa9d1a3-05d8-4cad-af44-fd187c5be16f ONBOOT=yes查看网卡状态teamdctl team0 state验证nmcli dev dis eno 断开nmcli dev con eno 连接OS版本查询lsb_release -a需要安装包（yum install redhat-lsb）起停服务systemctl stop firewalldsystemctl start firewalldsystemctl status firewalldsystemctl|grep是否开机启动systemctl enable XXX 开机启动systemctl disable xxx 开机不启动systemctl status XXX 查看状态关闭防火墙[root@localhost ~]# systemctl stop firewalld [root@localhost ~]# systemctl disable firewalld关闭selinux[root@localhost ~]# vi /etc/sysconfig/selinux把SELINUX=enforcing改为SELINUX=disabled[root@localhost ~]# reboot查看#getenforce临时关闭# setenforce 0LVM配置虚机上共享磁盘配置要求磁盘置备：厚置备置零磁盘模式：独立持久在ha1上，创建pv、vg、lv挂载文件系统，在ha2上重启系统即可识别vg信息修改主机名称：linu7通过hostname临时修改主机名，加hostnamectl static修改静态主机名的方式实现永久生效主机名（修改主机名后注意修改hosts）hostnamehostnamectl --static set-hostname linux7-ha2而在linux7之前是没有hostnamectl命令的，永久修改主机名的方式是通过hostname加修改/etc/sysconfig/network文件的方式配置vnc连接rehhat71）安装包yum install tigervnc-server创建一个登录密码：#vncserver2）配置vnccp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@:1.service替换文件#Type=forking改成 Type=simple3）重启systemdsystemctl daemon-reload4）启动vcnsystemctl start vncserver@:1.servicesystemctl status vncserver@:1.service永久启动systemctl enable vncserver@:1.service5）关闭vncsystemctl stop vncserver@:1.service开机不启动systemctl disable vncserver@:1.service客户端服务器段需要关闭防火墙，或修改过滤2、oracle静默安装安装必要的包yum -y install binutils compat-db compat-gcc-34 compat-gcc-34-c++ compat-libstdc++-33 elfutils-libelf-devel gcc gcc-c++ glibc-* libXp.so.6 libXt.so.6 libXtst.so.6 libgcc* ksh libXp libaio-devel numactl numactl-devel sysstat unixODBC unixODBC-devel pdkshyum install静默安装oracle修改./database/response/db_install.rspdb_install.rsp如下内容oracle.install.option=INSTALL_DB_SWONLYUNIX_GROUP_NAME=oinstallINVENTORY_LOCATION=/u01/app/oraInventoryORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1ORACLE_BASE=/u01/app/oracleoracle.install.db.InstallEdition=EEoracle.install.db.EEOptionsSelection=trueoracle.install.db.optionalComponents=oracle.rdbms.partitioning:11.2.0.3.0,oracl e.oraolap:11.2.0.3.0,oracle.rdbms.dm:11.2.0.3.0,oracle.rdbms.lbac:11.2.0.3.0,or acle.rdbms.rat:11.2.0.3.0oracle.install.db.DBA_GROUP=dbaoracle.install.db.OPER_GROUP=operoracle.install.db.isRACOneInstall=falseDECLINE_SECURITY_UPDATES=true执行静默安装软件./runInstaller -silent -ignoreSysPrereqs -ignorePrereq -showProgress -responseFile /oracle/database/response/db_install.rsp执行静默安装数据库（在dbca.rsp中添加实例名称）dbca -silent -responseFile /oracle/database/response/dbca.rsp对数据库做必要的调整3、linux7 vmware下ha安装调试----pacemaker取代rgmanager ssh 双机信任配置1）在两个节点上生产证书# ssh-keygen -t rsa注意：在程序提示输入passphrase时直接输入回车，表示无证书密码。

Red Hat Enterprise Linux 7 DM 多路径配置和管理文档说明书

Red Hat Enterprise Linux 7DM 多路径Configuring and managing Device Mapper MultipathLast Updated: 2023-03-25Red Hat Enterprise Linux 7 DM 多路径Configuring and managing Device Mapper Multipath Steven LevineRed Hat Customer Content Services******************. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .目录第 1 章设备映射器多路径1.1. NEW AND CHANGED FEATURES 1.2. OVERVIEW OF DM MULTIPATH 1.3. 存储阵列支持1.4. DM MULTIPATH COMPONENTS1.5. DM MULTIPATH SETUP OVERVIEW 第 2 章多路径设备2.1. 多路径设备识别器2.2. 在群集中保持多路径设备名称一致2.3. 多路径设备属性2.4. 逻辑卷中的多路径设备第 3 章 SETTING UP DM MULTIPATH 3.1. SETTING UP DM MULTIPATH 3.2. 在生成多路径设备时忽略逻辑磁盘3.3. CONFIGURING STORAGE DEVICES 3.4. SETTING UP MULTIPATHING IN THE INITRAMFS FILE SYSTEM 第 4 章 THE DM MULTIPATH CONFIGURATION FILE 4.1. 配置文件总览4.2. 配置文件黑名单4.3. 配置文件默认设置4.4. 多路径设备配置属性4.5. 配置文件设备4.6. ISCSI AND DM MULTIPATH OVERRIDES 第 5 章 DM MULTIPATH ADMINISTRATION AND TROUBLESHOOTING5.1. AUTOMATIC CONFIGURATION FILE GENERATION WITH MULTIPATH HELPER 5.2. RESIZING AN ONLINE MULTIPATH DEVICE 5.3. MOVING ROOT FILE SYSTEMS FROM A SINGLE PATH DEVICE TO A MULTIPATH DEVICE 5.4. MOVING SWAP FILE SYSTEMS FROM A SINGLE PATH DEVICE TO A MULTIPATH DEVICE 5.5. THE MULTIPATH DAEMON 5.6. ISSUES WITH QUEUE_IF_NO_PATH FEATURE 5.7. MULTIPATH COMMAND OUTPUT 5.8. MULTIPATH QUERIES WITH MULTIPATH COMMAND 5.9. MULTIPATH COMMAND OPTIONS 5.10. 使用 DMSETUP 命令确定设备映射器条目5.11. THE MULTIPATHD COMMANDS 5.12. TROUBLESHOOTING WITH THE MULTIPATHD INTERACTIVE CONSOLE 5.13. CLEANING UP MULTIPATH FILES ON PACKAGE REMOVAL 附录 A. 修订记录索引335778999101012121314151616172031364345454545474747484949505051525354目录1DM 多路径2第 1 章设备映射器多路径3DM 多路径4第 1 章设备映射器多路径5DM 多路径6第 1 章设备映射器多路径在这个配置中，可将 I/O分布到那四条路径中。

使用U盘方式安装rhel7_图文

使用U盘方式安装rhel linux 7
安装前需要准备的事项：
1、8G或以上的U盘；
2、下载最新版UltraISO；
3、准备rhel-server-7.0-x86_64-dvd.iso；
4、U盘配置好后将安装镜像拷贝到U根目录；
1. 使用最新版UltraISO将ISO镜像刻录到U盘
一定要是最新版，试用版都可以，按下图操作：
2. 使用新配置U盘启动电脑进入安装界面
正常情况下你应该会看到下面的这个界面：
选择第一项，然后按TAB键将原始信息修改成：
>vmlinuz initrd=initrd.img repo=hd:/dev/sda4:/ quiet
以下是顺利进入图形安装界面：
3.确认U盘设备信息方法
按TAB键的命令按以下方式确认U盘的设备信息
将命令修改为：>vmlinuz initrd=initrd.img linux dd quiet之后回车，会列出你的设备列表了，在这个列表里面，能很清楚的辨认哪个是U盘：
准确确认U盘设备信息后，重复第2步，然后改成：
>vmlinuz initrd=initrd.img inst.stage2=hd:/dev/sda4:/ quiet
>vmlinuz initrd=initrd.img repo=hd:/dev/sda4:/ quiet
Sda4得改成U盘所对应的名称，然后回车。

会来到选择语言的界面了，再接着就是图形化设置界面了。

备注：
安装过程可能出现常见错误：
以上问题可以使用使用最新版UltraISO重新配置启动U盘解决；
该问题使用cd /dev 确认U盘设备信息后再重复第2步完成安装。

红帽企业Linux安装指南说明书

Accessing Red Hat Enterprise Linux installation binariesThe Cloud Paks include entitlement to Red Hat OpenShift Container Platform and Red Hat Enterprise Linux. The preferred method of accessing and installing these offerings is to follow the standard installation documentation from Red Hat and register your systems using your Red Hat Network subscription. Installation binaries, documentation, and entitlement information can all be accessed from the Red Hat Customer Portal at https://. If you are new to the Red Hat Customer Portal, click Getting Started after you have logged in (or use this link: https:///start/) to take a guided tour of the and learn how to get the most out of your Red Hat subscription.Note: The preferred installation method requires an active Red Hat Network subscription and entitlement in a sufficient quantity to for the systems where you are installing, and connectivity to the internet or to a local Red Hat Satellite Server. It is also possible to install Red Hat OpenShift Container Platform before your subscription has been activated in the Red Hat Customer Portal by accessing the installation binaries from IBM Passport Advantage and performing a manual offline installation.Preferred method: using the Red Hat Customer PortalAccessing installation binaries through the Red Hat Customer PortalAfter your Cloud Pak order has been processed, you will receive an email from Red Hat at the address associated with your order indicating that the entitlement quantities for your Red Hat OpenShift Container Platform and subscription has been updated.To verify that the entitlement quantities have been added to your account, log in to the Red Hat Customer Portal and click Subscriptions. Red Hat Open Shift entitlements will be displayed in the table titled OPENSHIFT.Installing Red Hat Enterprise LinuxInstalling OpenShift Container Platform 3.11 requires Red Hat Enterprise Linux 7.6 to be installed on the host systems or virtual machines where OpenShift Container Platform will be installed. Entitlement to Red Hat Enterprise Linux is included with your Cloud Pak entitlement. If you do not already have Red Hat Enterprise Linux installed, use the following documentation to complete the installation of Red Hat Enterprise Linux.Red Hat Enterprise Linux 7.6 installation media can be accessed through the Red Hat Customer portal at https:///downloads/content/69/ver=/rhel---7/7.6/x86_64/product-softwareInstructions for downloading and installing Red Hat Enterprise Linux 7.6, including registering your installation using Subscription Manager, can be found in the Red Hat Customer Portal at:https:///documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-getting-startedInstalling Red Hat OpenShift Container PlatformOnce you have successfully provisioned hosts or virtual machines with Red Hat Enterprise Linux 7.6 installed and registered, proceed to install OpenShift Container Platform3.11 by following the documentation provided in the Red Hat Customer Portal:https:///documentation/en-us/openshift_container_platform/3.11/html/getting_started/getting-started-index Alternate Method: using IBM Passport AdvantageAccessing binaries for manual installation from IBM Passport AdvantageIf you require the ability to install the Cloud Pak before your entitlements have been updated in the Red Hat Customer Portal, all of the binary files necessary to perform a manual installation are available for download from IBM Passport Advantage or the public internet. Installation images and RPMs for Red Hat Enterprise Linux can be downloaded from IBM Passport Advantage (Part number CC3KEEN , which is part of your Cloud Pak eAssembly.) This file has the description “IBM Red Hat OpenShift 3.11 English only eImage” in IBM Passport Advantage. It contains the Red Hat Enterprise Linux installation binaries, including the files that enable you to install Red Hat OpenShift Container Platform 3.11 over the internet. This installation should be registered and associated with your Red Hat Network ID at a later time.The download is approximately 60GB in size, and additional storage will be required when extracting the files.This manual installation process requires the creation of a local HTTP server to host the RPM files that are provided in the above download package. These steps are not required when using the preferred installation method described above, since that scenario enables access to the necessary files through Red Hat Network.To perform a manual installation, follow the procedure outlined below:1.Download the Red Hat Enterprise Linux installation files from Passport Advantage (if youdon’t already have Red Hat Enterprise Linux installed)2.Provision a web server to host a Yum repository3.Copy the downloaded files to the web server4.Install Red Hat Enterprise Linux on the master and worker nodes5.Prepare the worker nodes6.Prepare the master node7.Install OpenShift Container PlatformDownload the Red Hat Enterprise Linux installation files from Passport AdvantageLog into IBM Passport Advantage and download “IBM Red Hat OpenShift 3.11 English only eImage” (part number CC3KEEN) which is associated with the Cloud Pak eAssembly. This will download a file named IBM_RED_HAT_OPENSHIFT_3.11_ENGLISH.tgz. Despite the description and filename, this package contains the files needed to install Red Hat Enterprise Linux.Provision a web server to host a Yum repositoryProvision a physical host or virtual machine with an HTTP server to support the local installation. You can use the web server of your choice as the repository.If you do not have a web server available, you can install and configure the Apache web server on a Red Hat Enterprise Linux system using the documentation provided by Red Hat under the heading “Prepare and populate the repository server”: https:///container-platform/3.11/install/disconnected_install.html#disconnected-repo-serverCopy the downloaded files to the web serverCopy IBM_RED_HAT_OPENSHIFT_3.11_ENGLISH.tgz to the web server and extract it into a subdirectory named “repos” under your web server’s document root (/var/www/html/repos if you have created a web server using the documentation above.)Ensure that the repository files can be read by any user (chmod -R +r /var/www/html/repos) Install Red Hat Enterprise Linux on the master and worker nodesOpenShift Container Platform 3.11 requires Red Hat Enterprise Linux 7.6 to be installed on the host systems or virtual machines where OpenShift Container Platform will be installed. Entitlement to Red Hat Enterprise Linux is included with your Cloud Pak entitlement. If you do not already have Red Hat Enterprise Linux installed, use the following documentation to complete the installation of Red Hat Enterprise Linux.If you don’t already have Red Hat Enterprise Linux installed, provision the hosts or VMs that will be used for the master and worker nodes for the OpenShift Container Platform cluster where you will install the Cloud Pak, and install Red Hat Enterprise Linux using the ISO downloaded from IBM Passport Advantage.Complete instructions for downloading and installing Red Hat Enterprise Linux 7.6, including prerequisites and host preparation, can be found in the Red Hat Customer Portal at:https:///documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-getting-started An ISO image of the installation media (rhel-server-7.6-x86_64-dvd.iso) can be found in the directory where you extracted the file downloaded from IBM Passport Advantageabove. Use these files in place of steps in Chapter 2 of the Red Hat Enterprise Linuxinstallation guide that describe downloading Red Hat Enterprise Linux from the Red Hat Customer Portal. If you are creating virtual machines to provision your nodes, this image can be used directly.If you are installing Red Hat Enterprise Linux on a physical host, refer to Chapter 3 of the Red Hat Enterprise Linux installation guide for information on creating physicalinstallation media or accessing installation media over a network:https:///documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-making-mediaPrepare the worker nodesEnsure that each of the worker nodes has been prepared to meet the requirements described under “Preparing your hosts”: https:///container-platform/3.11/install/host_preparation.html#install-config-install-host-preparationUpdate /etc/yum.repos.d/ose.repo on the master and worker nodes to use the local repository for installing RPMs, by updating the “baseurl” in each collection with the hostname or IP address of the local repository server. In the example shown below, the repository’s hostname is “myserver” – use your own hostname or IP address instead.Sample ose.repo file:[rhel-7-server-rpms]name=rhel-7-server-rpmsbaseurl=http://myserver/repos/rhel-7-server-rpmsenabled=1gpgcheck=0[rhel-7-server-extras-rpms]name=rhel-7-server-extras-rpmsbaseurl=http://myserver/repos/rhel-7-server-extras-rpmsenabled=1gpgcheck=0[rhel-7-server-ansible-2.6-rpms]name=rhel-7-server-ansible-2.6-rpmsbaseurl=http://myseerver/repos/rhel-7-server-ansible-2.6-rpmsenabled=1gpgcheck=0[rhel-7-server-ose-3.11-rpms]name=rhel-7-server-ose-3.11-rpmsbaseurl=http://myserver/repos/rhel-7-server-ose-3.11-rpmsenabled=1gpgcheck=0Refer to the section “Preparing cluster hosts” in the Red Hat OpenShift Container Platform documentation if you require additional information: https:///container-platform/3.11/install/disconnected_install.html#disconnected-openshift-systemsPrepare the master nodeEnsure that the master node has been prepared to meet the requirements described under “Preparing your hosts”: https:///container-platform/3.11/install/host_preparation.html#install-config-install-host-preparation Customize an inventory file on your master node to describe the details of your cluster and set as the registry for installation. Refer to “Customizing inventory files” (https:///container-platform/3.11/install/configuring_inventory_file.html#configuring-ansible) for more information and to review example inventory files.You must set the variable “oreg_url” to “/openshift3/ose-${component}:${version}” in your inventory file exactly as shown below:oreg_url=/openshift3/ose-${component}:${version}Install Red Hat OpenShift Container PlatformFollow the documentation provided by Red Hat to install OpenShift Container Platform 3.11 in the section titled “Installing OpenShift Container Platform”:https:///container-platform/3.11/install/running_install.html#install-running-installation-playbooks。

安装RedHat Linux 7

安装RedHat Linux 7.4 1.创建新的虚拟机
2.选择“自定义（高级）”
3.选择“下一步”
4.选择“稍后安装操作系统”
5.选择操作系统的类型
6.设置虚拟机名称和保存路径
8.下一步
9.设置网络类型，选择“使用仅主机模式网络”
11.下一步
12.下一步
13.设置硬盘容量，可以适当大一些
14.下一步
15.点击“完成”
16.加载ISO光盘，并启动虚拟机
17.选择第一个选项，并回车
18.选择“Continue”
19.选择“设置时区”
20.配置安装选项
在选择“Server With GUI”，一定把“Development Tools”安装上。

21.配置网络和主机名（非常重要）
22.开始安装
23.设置root用户的密码
24.重启虚拟机
25.完成配置
26.完成向导。

Red Hat Enterprise Linux (RHEL) 7.7 驱动用户手册说明书

Red Hat Enterprise Linux (RHEL) 7.7 DriverUser ManualRHEL 7.7NOTE: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 PRODUCT(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 Technologies350 Oakmead Parkway Suite 100Sunnyvale, CA 94085U.S.A.Tel: (408) 970-3400Fax: (408) 970-3403© Copyright 2019. Mellanox Technologies Ltd. All Rights Reserved.Mellanox®, Mellanox logo, Mellanox Open Ethernet®, LinkX®, Mellanox Spectrum®, Mellanox Virtual Modular Switch®, MetroDX®, MetroX®, MLNX-OS®, ONE SWITCH. A WORLD OF OPTIONS®, Open Ethernet logo, Spectrum logo, Switch-IB®, SwitchX®, UFM®, and Virtual Protocol Interconnect® are registered trademarks of Mellanox Technologies, Ltd.For the complete and most updated list of Mellanox trademarks, visit /page/trademarks.All other trademarks are property of their respective owners.Table of ContentsDocument Revision History (5)1Firmware Burning (6)2Port Type Management (7)3Modules Loading and Unloading (8)4Important Packages and Their Installation (9)5SR-IOV Configuration (10)5.1Setting up SR-IOV (10)6Default RoCE Mode Setting (12)7PXE over InfiniBand Installation (13)List of TablesTable 1: Document Revision History (5)Document Revision HistoryTable 1: Document Revision HistoryRevision Date DescriptionRHEL 7.7 October 22, 2019 Initial version of this document.1 Firmware Burning1.Check the device’s PCI address.lspci | grep MellanoxExample:00:06.0 Infiniband controller: Mellanox Technologies MT27520 Family[ConnectX-3 Pro]2.Identify the adapter card's PSID.# mstflint -d 81:00.0 qImage type: FS2FW Version: 2.42.5000FW Release Date: 26.7.2017Rom Info: type=PXE version=3.4.752 devid=4103Device ID: 4103Description: Node Port1 Port2Sys imageGUIDs: e41d2d0300b3f590 e41d2d0300b3f591 e41d2d0300b3f592e41d2d0300b3f593MACs: e41d2db3f591 e41d2db3f592VSD:PSID: MT_10901110193.Download the firmware BIN file from the Mellanox website that matches your card'sPSID.4.Burn the firmware.# mstflint -d <lspci-device-id> -i <image-file> b5.Reboot your machine after the firmware burning is completed.2 Port Type ManagementConnectX®-3 onwards adapter cards’ ports can be individually configured to work asInfiniBand or Ethernet ports. By default, ConnectX® family adapter cards VPI ports areinitialized as InfiniBand ports. If you wish to change the port type use the mstconfig afterthe driver is loaded.1.Install mstflint tools.yum install mstflint2.Check the device’s PCI address.lspci | grep MellanoxExample:00:06.0 Infiniband controller: Mellanox Technologies MT27520 Family[ConnectX-3 Pro]e mstconfig to change the link type as desired IB – for InfiniBand, ETH – for Ethernet.mstconfig –d <device pci> s LINK_TYPE_P1/2=<ETH|IB|VPI>Example:# mstconfig -d 00:06.0 s LINK_TYPE_P1=ETHDevice #1:----------Device type: ConnectX3ProPCI device: 00:06.0Configurations: Current NewLINK_TYPE_P1 IB(1) ETH(2)Apply new Configuration? ? (y/n) [n] : yApplying... Done!-I- Please reboot machine to load new configurations.4.Reboot your machine.3 Modules Loading and UnloadingMellanox modules for ConnectX®-2/ConnectX®-3/ConnectX®-3 Pro are:•mlx4_en, mlx4_core, mlx4_ibMellanox modules for ConnectX®-4/ConnectX®-4 Lx/ ConnectX®-5/ ConnectX®-5Ex/ConnectX-6 are:•mlx5_core, mlx5_ibIn order to unload the driver, you need to first unload mlx*_en/ mlx*_ib and then themlx*_core module.To load and unload the modules, use the commands below:•Loading the driver: modprobe <module name># modprobe mlx5_ib•Unloading the driver: modprobe –r <module name># modprobe –r mlx5_ib4 Important Packages and Their Installationrdma-corerdma-core RDMA core userspace libraries and daemonslibibmad: Low layer InfiniBand diagnostic and management programslibibmad OpenFabrics Alliance InfiniBand MAD libraryopensm: InfiniBand Subnet Manageropensm-libs Libraries used by OpenSM and included utilitiesopensm OpenIB InfiniBand Subnet Manager and management utilitiesIbutils: OpenIB Mellanox InfiniBand Diagnostic Toolsibutils-libs Shared libraries used by ibutils binariesibutils OpenIB Mellanox InfiniBand Diagnostic Toolsinfiniband-diags: OpenFabrics Alliance InfiniBand Diagnostic Toolsinfiniband-diags OpenFabrics Alliance InfiniBand Diagnostic Toolsperftest: IB Performance testsperftest IB Performance Testsmstflint: Mellanox Firmware Burning and Diagnostics Toolsmstflint Mellanox firmware burning toolTo install the packages above run:# yum install libibverbs librdmacm libibcm libibmad libibumad libmlx4libmlx5 opensm ibutils infiniband-diags srptools perftest mstflint rdmacm-utils ibverbs-utils librdmacm-utils -y5 SR-IOV Configuration5.1 Setting up SR-IOV1.Install the mstflint tools.# yum install mstflint2.Check the device’s PCI.# lspci | grep MellanoxExample:00:06.0 Infiniband controller: Mellanox Technologies MT27520 Family[ConnectX-3 Pro]3.Check if SR-IOV is enabled in the firmware.mstconfig -d <device pci> qExample:# mstconfig -d 00:06.0 qDevice #1:----------Device type: ConnectX3ProPCI device: 00:06.0Configurations: CurrentSRIOV_EN True(1)NUM_OF_VFS 8LINK_TYPE_P1 ETH(2)LINK_TYPE_P2 IB(1)LOG_BAR_SIZE 3BOOT_PKEY_P1 0BOOT_PKEY_P2 0BOOT_OPTION_ROM_EN_P1 True(1)BOOT_VLAN_EN_P1 False(0)BOOT_RETRY_CNT_P1 0LEGACY_BOOT_PROTOCOL_P1 PXE(1)BOOT_VLAN_P1 1BOOT_OPTION_ROM_EN_P2 True(1)BOOT_VLAN_EN_P2 False(0)BOOT_RETRY_CNT_P2 0LEGACY_BOOT_PROTOCOL_P2 PXE(1)BOOT_VLAN_P2 1IP_VER_P1 IPv4(0)IP_VER_P2 IPv4(04.Enable SR-IOV:mstconfig –d <device pci> s SRIOV_EN=<False|True>5.Configure the needed number of VFsmstconfig –d <device pci> s NUM_OF_VFS=<NUM>NOTE: This file will be generated only if IOMMU is set in the grub.conf file (byadding “intel_iommu=on” to /boot/grub/grub.conf file).6.[mlx4 devices only] Create/Edit the file /etc/modprobe.d/mlx4.conf:options mlx4_core num_vfs=[needed num of VFs] port_type_array=[1/2 for IB/ETH],[ 1/2 for IB/ETH]Example:options mlx4_core num_vfs=8 port_type_array=1,17.[mlx5 devices only] Write to the sysfs file the number of needed VFs.echo [num_vfs] > sys/class/net/ib2/device/sriov_numvfsExample:# echo 8 > /sys/class/net/ib2/device/sriov_numvfs8.Reboot the driver.9.Load the driver and verify that the VFs were created.# lspci | grep mellanoxExample:00:06.0 Network controller: Mellanox Technologies MT27520 Family[ConnectX-3 Pro]00:06.1 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.2 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.3 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.4 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.5 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.6 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.7 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]00:06.0 Network controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]For further information, refer to section Setting Up SR-IOV MLNX_OFED User Manual.6 Default RoCE Mode Setting1.Mount the configfs file.# mount -t configfs none /sys/kernel/config2.Create a directory for the mlx4/mlx5 device.# mkdir -p /sys/kernel/config/rdma_cm/mlx4_0/3.Validate what is the used RoCE mode in the default_roce_mode configfs file.# cat /sys/kernel/config/rdma_cm/mlx4_0/ports/1/default_roce_modeIB/RoCE v14.Change the default RoCE mode,•For RoCE v1: IB/RoCE v1•For RoCE v2: RoCE v2# echo "RoCE v2" >/sys/kernel/config/rdma_cm/mlx4_0/ports/1/default_roce_mode# cat /sys/kernel/config/rdma_cm/mlx4_0/ports/1/default_roce_modeRoCE v2# echo "IB/RoCE v1" >/sys/kernel/config/rdma_cm/mlx4_0/ports/1/default_roce_mode# cat /sys/kernel/config/rdma_cm/mlx4_0/ports/1/default_roce_modeIB/RoCE v17 PXE over InfiniBand InstallationPXE over InfiniBand infrastructure has additional parameter in the Boot Loader file forloading the necessary modules and interfaces and for allowing sufficient time to get the link.To install RHEL from PXE using the IPoIB interfaces, add the following parameters to theBoot Loader file, located in the var/lib/tftpboot/pxelinux.cfg directory, at thePXE server:bootdev=ib0 ksdevice=ib0 net.ifnames=0 biosdevname=0 rd.neednet=1rd.bootif=0 rd.driver.pre=mlx5_ib,mlx4_ib,ib_ipoib ip=ib0:dhcp.dhcp.retry=10 .timeout.iflink=60 .timeout.ifup=80.timeout.carrier=80Example:default RH7.5prompt 1timeout 600label RH7.5kernelappend bootdev=ib0 ksdevice=ib0 net.ifnames=0 biosdevname=0 rd.neednet=1rd.bootif=0 rd.driver.pre=mlx5_ib,mlx4_ib,ib_ipoib ip=ib0:dhcp.dhcp.retry=10 .timeout.iflink=60 .timeout.ifup=80.timeout.carrier=80。

RHEL7HA集群安装配置文档

没有Fencing设备时，禁用STONITH组建功能，在stonith-enabled=false情况下，分布式锁管理器哦（DLM）等资源以及依赖DLM的所有服务（例如 cLVM2, GFS2 ,和OCFS2）都将无法启动。

#pcs property set stonith-enabled=false系统环境描述本文档基于Vmware虚拟机环境测试系统环境创建，描述如下：序号Hostname固定IP Ha-hostname心跳IP1ceph-node2192.168.200.37ceph-node2192.168.200.372ceph-node3192.168.200.38ceph-node3192.168.200.383浮动IP：192.168.200.40注：实际生产环境如使用物理服务器，则需要单独配置心跳网卡的IP及对应的主机名。

注：以下所有安装步骤，如无特殊声明，需要在2台系统上都运行相关操作。

Red Hat HA部署安装HA相关软件包关闭selinux,关闭防火墙，关闭NetworkManager,配置服务器时间；vim /etc/selinux/config systemctl stop firewalld systemctl disabled firewalld systemctl stop NetworkManager systemctl disable NetworkManager date -s "2019-02-27 10:25:00" hwclock --systohc修改主机名：echo node1 > /etc/hostname hostname node1 sudo -i echo node2 >/etc/hostname hostname node2 sudo -i修改hosts文件并配置集群间认证修改/etc/hosts文件，分别加入hostname解析和主机节点状态监测网络解析：# vi /etc/hosts……192.168.200.37node1192.168.200.38 node2修改/etc/yum.repos.d/rhel7.repo文件，加入HA的repo资源：# cat /etc/yum.repos.d/rhel7.repo[HA]name=HighAvailabilitybaseurl=file:///mnt/addons\HighAvailabilityenabled=1gpgcheck=0 //将配置好的文件同步到另外一台机器： :wq rsync /etc/hosts 192.168.100.38:/etc rsync /etc/yum.repos.d/rhel7.repo 192.168.100.38:/etc/yum.repos.d/安装Red Hat HA相关软件包：（需要在2个节点服务器上面都操作）#yum install pcs fence-agents-all systemctl start pcsd systemctl enable pcsd //给默认集群管理用户设置密码 echo 123456 | passwd --stdin hacluster //2台机器都需要设置密码执行以下命令，配置集群节点之间的hacluster用户认证。

Red Hat Enterprise Linux 7 虚拟化调整和优化指南说明书

Red Hat Enterprise Linux 7虚拟化调整和优化指南在 RHEL 中为主机系统和虚拟客户机使用 KVM 性能功能Last Updated: 2023-03-25Red Hat Enterprise Linux 7 虚拟化调整和优化指南在 RHEL 中为主机系统和虚拟客户机使用 KVM 性能功能Enter your first name here. Enter your surname here.Enter your organisation's name here. Enter your organisational division here. Enter your email address here.法律通告Copyright © 2022 | You need to change the HOLDER entity in the en-US/Virtualization_Tuning_and_Optimization_Guide.ent file |.The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates.XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.All other trademarks are the property of their respective owners.摘要Red Hat Enterprise Linux 虚拟化调整和优化指南涵盖 KVM 和虚拟化性能。

Linux操作系统安装之RedHat的安装超详细教程

完成项目一的第二步：LINUX操作系统的安装配置前言：服务器上架完成后，我们就得立马安装操作系统，因为第二天会有业务上线，所以得赶紧，我们这里选择安装的是(Red Hat Enterprise Linux 企业版的linux)Linux创始人林纳斯·托瓦兹(Linus Torvalds)Linux诞生于1991 年的10 月5 日（这是第一次正式向外公布的时间）1996年，Torvalds为Linux选定了企鹅作为它的吉祥物Ok，了解完基本的信息情况后，我们继续完成剩下的项目首先下载系统的ISO镜像文件，地址是：地址一：地址二：湘南学院的同学可以找群内的童罗同学拷贝镜像)下载之后放在特定的目录夹下面，如下准备就绪后，我们开始安装操作系统：接着上一步，如下图点击”Edit virtual machine setting”设置我们虚拟机的系统安装源，也就是我们下载的rhel-server-i386-dvd文件。

点击”CD/DVD(IDE)”，右边选择”Use ISO image file:”,点击”Browse”按钮选择需要的操作系统镜像设置完成，点击ok结束现在回到主页面，点击上面有三个地方需要注意：第一个红圈表示直接回车安装linux，默认是以图形界面来安装第二个红圈表示，在下面boot:的位置输入 linux text 将进入字符界面安装第三个红圈表示，需要输入引导的选项(直接回车或是输入linuxtext)我们这里直接回车就可以了下图表示要对我们的ISO文件进行完整性检测，这个很费时间，所以我们跳过”skip”，在这里我们可以使用上下左右键移动光标，然后回车选择，也可以使用tab键跳动光标，空格或回车确认现在我们点击”Next”选择简体中文，然后下一步”Next”现在选择我们的键盘类型，默认都是美国英语式，然后下一步(因为上面我们选择了简体中文，所以这里的界面就是中文显示了)下面是要输入安装号码，也就是我们常说的激活码，windows也存在这一点，跳过也能安装让我们去访问redhat的官网，依然跳过，然后，下一步。