下载文档原格式
KVM安装步骤及基本操作KVM（Kernel-based Virtual Machine）是一种基于Linux内核的开源虚拟化技术，可以将服务器硬件资源划分为多个虚拟机来运行不同的操作系统。
安装KVM的步骤及基本操作如下：1.系统要求在安装KVM之前，需要确保系统满足以下要求：-64位操作系统- 支持虚拟化技术的CPU（例如Intel的VT-x或AMD的AMD-V）-至少4GB的内存-大于40GB的可用磁盘空间- 安装了最新的Linux内核2.安装KVM软件包首先，使用适用于你的Linux发行版的软件包管理器来安装KVM软件包。
例如，在Ubuntu上可以使用apt命令：```sudo apt updatesudo apt install qemu-kvm libvirt-daemon-system libvirt-clients virtinst bridge-utils```3.启用虚拟化扩展4.创建网络桥接KVM使用网络桥接来连接虚拟机和物理网络。
创建网络桥接需要使用bridge-utils软件包。
在终端中执行以下命令创建桥接网络：```sudo brctl addbr br0sudo brctl addif br0 ens33```其中，ens33是你的物理网络接口的名称。
可以使用ip a命令查看你的接口名称。
5.配置网络连接```sudo nano /etc/network/interfaces```在文件中添加以下行来配置网络桥接：```auto br0iface br0 inet dhcpbridge_ports ens33保存文件并退出。
6. 启动libvirt服务执行以下命令启动libvirt服务：```sudo systemctl start libvirtdsudo systemctl enable libvirtd```7.创建虚拟机使用virt-install命令创建虚拟机。
KVM--安装及初步使⽤KVM是Kernel-based Virtual Machine的简称,是⼀个开源的虚拟化模块,今天我将在CentOS7的操作系统上安装KVM,以下是我的安装步骤.⼀.环境信息系统: CentOS 7.2 IP: 10.0.0.12/24在虚拟机安装时,需要启⽤CPU的虚拟化功能⼆. KVM安装步骤1. 安装qemu-kvm和libvirt[root@kvm-node1 ~]# yum install -y qemu-kvm libvirt ###qemu-kvm⽤来创建虚拟机硬盘,libvirt⽤来管理虚拟机2. 安装virt-install[root@kvm-node1 ~]# yum install -y virt-install ###⽤来创建虚拟机3. 启动libvirtd,并将它设为开机启动,启动后使⽤ifconfig查看,发现会多出来⼀块virbr0的⽹卡,ip默认为192.168.122.1/24,说明libvirtd启动成功,如果默认没有ifconfig命令,使⽤yuminstall -y net-tools安装[root@kvm-node1 ~]# systemctl start libvirtd && systemctl enable libvirtd[root@kvm-node1 ~]# ifconfigens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet 10.0.0.12 netmask 255.255.255.0 broadcast 10.0.0.255inet6 fe80::5505:5aa:3f96:f3f8 prefixlen 64 scopeid 0x20<link>ether 00:0c:29:51:09:70 txqueuelen 1000 (Ethernet)RX packets 22459 bytes 29147955 (27.7 MiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 5161 bytes 587757 (573.9 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536inet 127.0.0.1 netmask 255.0.0.0inet6 ::1 prefixlen 128 scopeid 0x10<host>loop txqueuelen 1 (Local Loopback)RX packets 0 bytes 0 (0.0 B)RX errors 0 dropped 0 overruns 0 frame 0TX packets 0 bytes 0 (0.0 B)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255ether 52:54:00:fb:b1:55 txqueuelen 1000 (Ethernet)RX packets 0 bytes 0 (0.0 B)RX errors 0 dropped 0 overruns 0 frame 0TX packets 0 bytes 0 (0.0 B)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0经过以上三步,KVM安装成功,下⾯开始使⽤KVM创建虚拟机.三. 使⽤KVM创建虚拟机(CentOS7)1. 使⽤qemu命令创建⼀个10G的硬盘(最⼩10,G,可以更多),硬盘的名称为: CentOS-7-x86_64.raw[root@kvm-node1 ~]# qemu-img create -f raw /opt/CentOS-7-x86_64.raw 10GFormatting '/opt/CentOS-7-x86_64.raw', fmt=raw size=10737418240[root@kvm-node1 ~]# ll -h /opttotal 0-rw-r--r-- 1 root root 10G Aug 2207:59 CentOS-7-x86_64.raw2. 使⽤virt-install创建名称为CentOS-7-x86_64的虚拟机,在创建之前,先上传⼀个CentOS7的ISO镜像,最好在根⽬录下创建⼀个ISO的⽬录⽂件夹[root@kvm-node1 ~]# virt-install --virt-type kvm --name CentOS-7-x86_64 --ram 1024 --cdrom=/ISO/CentOS-7-x86_64-Everything-1611.iso --disk path=/opt/CentOS-7-x86_64.raw --network network=default --graphics vnc,listen=0.0.0.0 Starting install...Creating domain... | 0 B 00:03Domain installation still in progress. You can reconnect tothe console to complete the installation process.这时候使⽤TightVNC⼯具,连接主机IP 10.0.0.12,设置安装操作系统的⽹卡名称为eth0,如图所⽰安装步骤和我们平时安装操作系统的⽅法⼀样,安装完成后,可以使⽤virsh list --all显⽰KVM上所有的虚拟机[root@kvm-node1 ~]# virsh list --allId Name State----------------------------------------------------- CentOS-7-x86_64 shut off ### 可以看到虚拟机的名称和状态四. 管理KVM1. 使⽤virsh启动KVM中的虚拟机[root@kvm-node1 ~]# virsh start CentOS-7-x86_64Domain CentOS-7-x86_64 started启动后,使⽤VNC连接⼯具,登录后可以看到⽹卡的名称为eth0,默认没有ip地址,是因为⽹卡没有激活,将ONBOOT改为yes,重启⽹卡,可以看到ip地址为192.168.122.0⽹段的当KVM中的虚拟机启动后,可以在/etc/libvirt/qemu⽬录下,看到启动的虚拟机的信息[root@kvm-node1 ~]# cd /etc/libvirt/qemu[root@kvm-node1 qemu]# pwd/etc/libvirt/qemu[root@kvm-node1 qemu]# ls -lhtotal 4.0K-rw------- 1 root root 3.8K Aug 2208:18 CentOS-7-x86_64.xmldrwx------ 3 root root 42 Aug 2207:51 networksCentOS-7-x86_64.xml就是启动的虚拟机的信息,当我们使⽤vim编辑器查看时,会提⽰如下信息:<!--WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BEOVERWRITTEN AND LOST. Changes to this xml configuration should be made using:virsh edit CentOS-7-x86_64or other application using the libvirt API.-->看到提⽰需要修改虚拟机的信息,需要使⽤命令 virsh edit CentOS-7-x86_64,是⽤这条命令后,我们可以看到很多虚拟机的信息,包括vcpu,memory等2. CPU热添加(KVM⽀持CPU的热添加,不过局限是宿主机和虚拟机的系统相同才⾏,这⾥宿主机是CentOS7,虚拟机也是CentOS7,所以可以模拟CPU热添加,不过真实⽣产环境不建议这样操作)[root@kvm-node1 ~]# virsh edit CentOS-7-x86_646 <vcpu placement='static'>1</vcpu> 修改为:<vcpu placement='auto' current="1">4</vcpu>##意思是当前cpu为1核,最多可以有4核,修改完虚拟机的配置⽂件,必须关闭虚拟机再启动,配置才能⽣效[root@kvm-node1 ~]# virsh shutdown CentOS-7-x86_64 ##关闭虚拟机Domain CentOS-7-x86_64 is being shutdown[root@kvm-node1 ~]# virsh list --all ##查看虚拟机状态Id Name State----------------------------------------------------- CentOS-7-x86_64 shut off[root@kvm-node1 ~]# virsh start CentOS-7-x86_64 ##启动虚拟机Domain CentOS-7-x86_64 started[root@kvm-node1 ~]# virsh list --allId Name State----------------------------------------------------3 CentOS-7-x86_64 running先通过VNC⼯具查看虚拟机的cpu信息在宿主机上通过命令添加核数[root@kvm-node1 ~]# virsh setvcpus CentOS-7-x86_64 2 --live ##虚拟机的cpu添加到2core再通过VNC⼯具查看虚拟机CPU信息3. 内存热添加(还是不建议⽣产中使⽤,知道功能就⾏了)通过VNC连接虚拟机,查看虚拟机内存[root@kvm-node1 ~]# virsh qemu-monitor-command CentOS-7-x86_64 --hmp --cmd info balloon ## 查看当前虚拟机的内存balloon: actual=1024[root@kvm-node1 ~]# virsh qemu-monitor-command CentOS-7-x86_64 --hmp --cmd balloon 512 ## 修改当前虚拟机的内存为512 [root@kvm-node1 ~]# virsh qemu-monitor-command CentOS-7-x86_64 --hmp --cmd info balloon ## 查看修改的内存信息已经改变成了512 balloon: actual=512使⽤VNC⼯具连接虚拟机,查看内存是否有变:4. ⽹卡配置(如何将KVM虚拟机中的⽹卡改为桥接模式,让局域⽹的其他⽤户可以正常访问)[root@kvm-node1 ~]# brctl show ##查看已有⽹桥bridge name bridge id STP enabled interfacesvirbr0 8000.525400fbb155 yes virbr0-nicvnet0创建⼀个脚本,删除ens33⽹卡的ip信息,新建⼀个桥接⽹卡,并且将ens33⽹卡的ip信息富裕新建的桥接⽹卡[root@kvm-node1 ~]# vim br0.sh#!/bin/bashbrctl addbr br0 #创建⼀个桥接⽹卡br0brctl addif br0 ens33 #将ens33⽹卡的桥接信息转到br0⽹卡ip addr del dev ens33 10.0.0.12/24 #将ens33⽹卡的ip信息删除ifconfig br0 10.0.0.12/24 up #将ens33⽹卡的ip信息这只到br0⽹卡上route add default gw 10.0.0.2 #添加⽹关[root@kvm-node1 ~]# chmod u+x br0.sh[root@kvm-node1 ~]# ./br0.sh使⽤ifocnfig查看⽹卡的ip信息,可以看到br0的地址已经变为了10.0.0.12/24[root@kvm-node1 ~]# ifconfigbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet 10.0.0.12 netmask 255.255.255.0 broadcast 10.0.0.255inet6 fe80::20c:29ff:fe51:970 prefixlen 64 scopeid 0x20<link>ether 00:0c:29:51:09:70 txqueuelen 1000 (Ethernet)RX packets 553 bytes 41723 (40.7 KiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 680 bytes 63511 (62.0 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet6 fe80::5505:5aa:3f96:f3f8 prefixlen 64 scopeid 0x20<link>ether 00:0c:29:51:09:70 txqueuelen 1000 (Ethernet)RX packets 6107998 bytes 8708309251 (8.1 GiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 534420 bytes 68906654 (65.7 MiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536inet 127.0.0.1 netmask 255.0.0.0inet6 ::1 prefixlen 128 scopeid 0x10<host>loop txqueuelen 1 (Local Loopback)RX packets 0 bytes 0 (0.0 B)RX errors 0 dropped 0 overruns 0 frame 0TX packets 0 bytes 0 (0.0 B)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255ether 52:54:00:fb:b1:55 txqueuelen 1000 (Ethernet)RX packets 6685 bytes 278745 (272.2 KiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 6981 bytes 34351624 (32.7 MiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500inet6 fe80::fc54:ff:fe6b:5fee prefixlen 64 scopeid 0x20<link>ether fe:54:00:6b:5f:ee txqueuelen 1000 (Ethernet)RX packets 16 bytes 1650 (1.6 KiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 987 bytes 52236 (51.0 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0使⽤命令修改KVM虚拟机的信息[root@kvm-node1 ~]# virsh edit CentOS-7-x86_6469 <interface type='network'> 修改为:<interface type='bridge'> ##桥接71 <source network='default'/> 修改为:<source bridge='br0'/>修改完成后关闭虚拟机,启动虚拟机,通过VNC⼯具修改ip为10.0.0.14/24,尝试ping宿主机是否可以ping通,并通过ssh连接[root@kvm-node1 ~]# virsh shutdown CentOS-7-x86_64Domain CentOS-7-x86_64 is being shutdown[root@kvm-node1 ~]# virsh start CentOS-7-x86_64Domain CentOS-7-x86_64 started通过本地的ssh软件,尝试连接,可以连接,并且可以看到IP信息以上就是CentOS7中KVM的安装和简单管理.。
一、查看cpu是否支持kvmKVM 需要有CPU 的支持（Intel vmx或AMD svm），在安装KVM 之前检查一下CPU 是否提供了虚拟技术的支持：egrep '(vmx|svm)' --color=always /proc/cpuinfo如果输出的结果包含VMX，它是Intel处理器虚拟机技术标志：如果包含SVM，它是AMD 处理器虚拟机技术的标志，如果你什么都没有得到，那应你的系统并没有支持虚拟化的处理，不能使用KVM，另处linux发行版本必须在64bit环境中才能使用KVM。
二、BIOS中开启Virtual Technolege在主板BIOS中开启CPU的Virtual Technolege(VT，虚化技术)，不同主板所在菜单不同例如：华硕主板开启虚拟化Intel主板开启虚拟化三、安装KVM服务器安装KVM 虚拟机和安装其他服务器一样，在选择操作系统类型是选择“Virtual Host”即可，其它步骤可参考“AiSchool平台安装指导”中操作系统安装部分。
如果使用此服务器管理其他KVM 主机，需要额外安装openssh-askpass软件包。
注：（已安装好的操作系统，里面有重要资料无法重新安装的可以在已有的系统上安装如下软件包yum install kvmkmod-kvmqemukvm-qemu-imgvirt-viewer virt-manager libvirtlibvirt-python python-virtinstopenssh-askpass或者如下图，安装需要的组四、检查kvm模块是否安装使用以下命令显示两个模块则表示安装完成[root@vm76 ~]# lsmod | grepkvmkvm_intel54285 0kvm 333172 1 kvm_intel以上表明安装完成五、配置宿主机1、关闭防火墙（如不用）chkconfigiptables offserviceiptables stop2、执行如下命令打开文件selinux配置文件。
基本过程1、KVM 需要有CPU 的支持（Intel vmx或AMD svm），在安装KVM 之前检查一下CPU 是否提供了虚拟技术的支持# egrep '^flags.*(vmx|svm)' /proc/cpuinfo有显示说明CPU支持VT功能2、在主板BIOS中开启CPU的Virtual Technolege(VT，虚化技术)3、安装kvm# yum install kvmvirt-* libvirt4、检查kvm模块是否安装# lsmod | grepkvm5、启动服务# service libvirtd start6、启动界面管理# virt-manager作业环境服务器端操作系统：Red Hat Enterprise Linux Server release 6.0 (Santiago)KVM：qemu-kvm-0.12.1.2-2.113.el6.x86_64客户端操作系统：Windows 7KVM管理工具：Xming 6.9一、安装KVM及相关软件1、KVM 需要有 CPU 的支持（Intel vmx 或 AMD svm），在安装 KVM 之前检查一下 CPU 是否提供了虚拟技术的支持：[root@etone ~]# egrep '^flags.*(vmx|svm)' /proc/cpuinfo有显示, 有显示则说明处理器具有VT功能2、在主板BIOS中开启CPU的Virtual Technolege(VT，虚化技术)3、安装kvm及其需要的软件包[root@etone ~]# yum install kvmvirt-* libvirt4、检查kvm模块是否安装，使用以下命令显示两个模块则表示安装完成[root@etone ~]# lsmod | grepkvm5、客户端安装Xming远程管理软件一路默认就OK了，装到当前Win 7系统的系统盘。
二、启动virt-manager管理界面1、客户端运行Xming，需要若干设置，基本是一路默认，在“Specify parameter settings”中，勾选“No Access Control”选项。
KVM使用说明范文KVM，即Kernel-based Virtual Machine，是一种用于Linux平台的开源虚拟化架构。
它允许用户在Linux操作系统上创建和管理虚拟机，将一台物理服务器分割成多个独立的虚拟机，每个虚拟机可以运行自己的操作系统和应用程序。
KVM是基于Linux内核的模块化架构，利用硬件虚拟化支持来提供高性能的虚拟化解决方案。
一、KVM安装配置1.硬件要求在安装KVM之前，首先需要确保硬件满足以下条件：- 64位的处理器，支持硬件虚拟化扩展（如Intel的VT-x或AMD的AMD-V）；-至少4GB的内存；-虚拟机使用的磁盘空间和网络带宽的要求根据具体需求确定。
2.操作系统要求KVM可以在多种Linux发行版上运行，包括Red Hat Enterprise Linux、CentOS、Ubuntu等。
3.安装KVM使用以下命令可以在Ubuntu上安装KVM：```sudo apt updatesudo apt install qemu-kvm libvirt-daemon-system virtinst bridge-utils```4.配置网络桥接在KVM中，可以选择使用桥接网络或NAT网络。
桥接网络可以使虚拟机直接连接到宿主机所连接的网络上，提供更好的网络性能和灵活性。
要配置网络桥接，首先需要创建一个网桥，可以使用以下命令：```sudo brctl addbr br0sudo brctl addif br0 eth0```其中，eth0是物理网卡的名称。
```auto br0iface br0 inet dhcpbridge_ports eth0bridge_stp offbridge_fd 0bridge_maxwait 0```重启网络服务以使配置生效：```sudo systemctl restart networking```5.创建和管理虚拟机使用virt-manager工具可以方便地创建和管理虚拟机，该工具提供了图形化的界面。
XX机房集中控管系统解决方案2009年9月目录1、机房集中控管系统需求分析 (3)1.1 简介 (3)1.2 客户需求 (3)2、机房集中控管系统针对性解决方案 (4)2.1 集中控制管理系统拓扑图 (4)2.2 机房方案实现概述 (5)2.3 集中控制管理针对性实现说明 (5)2.4 先进的Virtual Media管理方式 (7)2.5 Avocent机房系统资源整体解决方案特点总结 (7)3、数据中心集中控管系统产品简介 (9)4、Avocent公司介绍及解决方案成功案例 (14)4.1 Avocent公司介绍 (14)4.2 Avocent解决方案成功案例应用介绍 (16)1、机房集中控管系统需求分析1.1 简介现有先进完备的数据中心机房，由于操作人员时常需在监控室进行办公，需通过本地终端对机房内的各种服务器及串口设备进行各种统一管理。
现正在寻求一种能够满足这种需求的解决方案，以便使有关操作人员不必去到机房内也能操控所有的机房服务器和串口设备，且当系统规模扩张时仍能保持整个系统的完整性而达到管理上的简单有效。
1.2 客户需求根据通盘考虑，所有数据中心机房的众多设备需在一个整合了多种机房系统资源的集成大平台上得到统一管理，以解决因大量设备分散分布所带来的管理上的不便性，免除了众多不必要的外围设备而节省大量空间，使得各管理员可在监控室内从键盘、鼠标、显示器组成的控制台便可登陆所有的设备，方便快捷地排除机器故障，从而更有效地保障整体机房的正常运营。
具体需求如下：1)本项目KVM系统至少能控制40台设备，其中20台服务器设备，20台串口设备，用户通过KVM系统对机房设备进行全域远程控制。
2)考虑到单点故障率和布线的方便，要求单台数字KVM端口数不低于32，32口的KVM支持的并发用户数不低于2个；3)要求KVM和串口管理设备在同一集中认证平台上集中管理；在综合考虑了以上各因素及反复探讨后，我方经过反复研究，推出以下合理化方案供各位领导参考。
一，什么是KVMKVM包括很多部件：首先，它是一个Linux内核模块（现在包括在主线中）用于转换处理器到一种新的用户（guset）模式。
用户模式有自己的ring状态集合,但是特权ring0的指令会陷入到管理器(hypervisor)的代码。
由于这是一个新的处理器执行模型，代码不需要任何的改动。
除了处理器状态转换，这个内核模块同样处理很小一部分低层次的模拟，比如MMU注册（用于管理VM）和一部分PCI模拟的硬件。
在可预见的未来，Qemu团队专注于硬件模拟和可移植性，同时KVM团队专注于内核模块（如果某些部分确实有性能提升的话，KVM会将一小部分模拟代码移进来）和与剩下的用户空间代码的交互。
kvm-qemu可执行程序像普通Qemu一样：分配RAM,加载代码，不同于重新编译或者调用calling KQemu，它创建了一个线程（这个很重要）；这个线程调用KVM 内核模块去切换到用户模式，并且去执行VM代码。
当遇到一个特权指令，它从新切换会KVM内核模块，该内核模块在需要的时候，像Qemu线程发信号去处理大部分的硬件仿真。
这个体系结构一个比较巧妙的一个地方就是客户代码被模拟在一个posix线程，这允许你使用通常Linux工具管理。
如果你需要一个有2或者4核的虚拟机，kvm-qemu创建2或者4个线程，每个线程调用KVM内核模块并开始执行。
并发性（若果你有足够多的真实核）或者调度（如果你不管）是被通用的Linux调度器，这个使得KVM代码量十分的小当一起工作的时候，KVM管理CPU和MEM的访问，QEMU仿真硬件资源（硬盘，声卡，USB，等等）当QEMU单独运行时，QEMU同时模拟CPU和硬件。
二，安装配置KVM查看复制打印?1.# yum -y install kvm python-virtinst libvirt bridge-utils \2.virt-manager qemu-kvm-tools virt-viewer virt-v2v qemu-kvm tunctl3.4.[root@localhost ~]#vim /etc/sysconfig/selinux //关闭selinux5.6.SELINUX=disabled7.8.[root@localhost ~]#reboot9.10.[root@localhost ~]# cat /etc/redhat-release11.CentOS release 6.5 (Final) //centos 6.5三，启动libvirtd查看复制打印?1.[root@localhost ~]# /etc/init.d/libvirtd start //启动2.3.[root@localhost ~]# ps -e|grep libvirtd //查看是否启动4.19458 ? 00:00:01 libvirtd四，查看kvm模块是否正确加载1.[root@localhost ~]# lsmod |grep kvm2.kvm_intel 54285 03.kvm 333172 1 kvm_intel五，配置网络桥接查看复制打印?1.[root@localhost network-scripts]# cat ifcfg-eth0 |awk '{if($0 !~ /^$/ && $0 !~/^#/) {print $0}}'2.DEVICE=eth03.TYPE=Ethernet4.ONBOOT=yes5.BOOTPROTO=none6.BRIDGE=br07.IPV6INIT=no8.HWADDR=F8:BC:12:60:99:869.10.[root@localhost network-scripts]# cat ifcfg-br0 |awk '{if($0 !~ /^$/ && $0 !~ /^#/){print $0}}'11.DEVICE=br012.TYPE=Bridge13.ONBOOT=yes14.BOOTPROTO=static15.IPADDR=192.168.10.10316.GATEWAY=192.168.10.1MASK=255.255.255.018.DNS1=192.168.10.119.IPV6INIT=no20.DELAY=0重启网络，发现报以下错误：查看复制打印?1.[root@localhost network-scripts]# /etc/init.d/network start2.弹出环回接口： [确定]3.弹出界面 eth0：错误：激活连接失败：Master connection not found or invalid4.[失败]5.弹出界面 br0：错误：激活连接失败：Failed to determine connection's virtual interfacename6.[失败]7.RTNETLINK answers: File exists8.RTNETLINK answers: File exists9.RTNETLINK answers: File exists解决办法：查看复制打印?1.[root@localhost rules.d]# service NetworkManager stop //这个关闭掉就行2.停止 NetworkManager 守护进程： [确定]3.4.[root@localhost rules.d]# service network restart5.正在关闭接口 br0： [确定]6.正在关闭接口 eth0： [确定]7.关闭环回接口： [确定]8.弹出环回接口： [确定]9.弹出界面 eth0： [确定]10.弹出界面 br0： Determining if ip address 192.168.10.103 is already in use for devicebr0...11.[确定]如果以下内容就说明配置成功了：查看复制打印?1.[root@localhost network-scripts]# ifconfig2.br0 Link encap:Ethernet HWaddr F8:BC:12:60:99:86 //有这个就OK3.inet addr:192.168.10.103 Bcast:192.168.10.255 Mask:255.255.255.04.inet6 addr: fe80::fabc:12ff:fe60:9986/64 Scope:Link5.UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:16.RX packets:36416 errors:0 dropped:0 overruns:0 frame:07.TX packets:28648 errors:0 dropped:0 overruns:0 carrier:08.collisions:0 txqueuelen:09.RX bytes:13151508 (12.5 MiB) TX bytes:5962449 (5.6 MiB)10.11.eth0 Link encap:Ethernet HWaddr F8:BC:12:60:99:8612.inet6 addr: fe80::fabc:12ff:fe60:9986/64 Scope:Link13.UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:114.RX packets:1360857 errors:0 dropped:0 overruns:0 frame:015.TX packets:902173 errors:0 dropped:0 overruns:0 carrier:016.collisions:0 txqueuelen:100017.RX bytes:1913592871 (1.7 GiB) TX bytes:72387220 (69.0 MiB)18.19.lo Link encap:Local Loopback20.inet addr:127.0.0.1 Mask:255.0.0.021.inet6 addr: ::1/128 Scope:Host22.UP LOOPBACK RUNNING MTU:16436 Metric:123.RX packets:176842 errors:0 dropped:0 overruns:0 frame:024.TX packets:176842 errors:0 dropped:0 overruns:0 carrier:025.collisions:0 txqueuelen:026.RX bytes:880282316 (839.5 MiB) TX bytes:880282316 (839.5 MiB)27.28.virbr0 Link encap:Ethernet HWaddr 52:54:00:1A:B6:F129.inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.030.UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:131.RX packets:0 errors:0 dropped:0 overruns:0 frame:032.TX packets:37 errors:0 dropped:0 overruns:0 carrier:033.collisions:0 txqueuelen:034.RX bytes:0 (0.0 b) TX bytes:4651 (4.5 KiB)35.36.[root@localhost network-scripts]# brctl show37.bridge name bridge id STP enabled interfaces38.br0 8000.f8bc12609986 no eth0 //有这个就OK39.virbr0 8000.5254001ab6f1 yes virbr0-nic六，用virt-install生成.img文件1.# virt-install --name=ubuntu1 \2.--ram 1024 --vcpus=1 \3.--disk path=/root/ubuntu1.img,size=10 \4.--accelerate --cdrom /root/ubuntu-14.04-desktop-amd64.iso \5.--graphics vnc,port=5920 --network bridge=br0如果报以下错误：1.could not open disk image : Permission denied解决方法：查看复制打印?1.[root@localhost ~]# cat /etc/libvirt/qemu.conf |awk '{if($0 !~ /^$/ && $0 !~ /^#/){print $0}}'2.vnc_listen = "0.0.0.0"er = "root"//去掉注释4.group = "root"//去掉注释5.dynamic_ownership = 0 //去掉注释，把1改为0这一步做完，系统文件就好了。
KVM虚拟化安装部署及管理教程⽬录1.kvm部署1.1 kvm安装1.2 kvm web管理界⾯安装1.3 kvm web界⾯管理1.3.1 kvm连接管理1.3.2 kvm存储管理1.3.3 kvm⽹络管理1.3.4 实例管理故障1.kvm部署1.1 kvm安装//关闭防⽕墙和selinux[root@kvm ~]# systemctl disable --now firewalld.serviceRemoved /etc/systemd/system/multi-user.target.wants/firewalld.service.Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.[root@kvm ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config[root@kvm ~]# reboot//下载epel源和⼯具包[root@kvm ~]# yum -y install epel-release vim wget net-tools unzip zip gcc gcc-c++//验证CPU是否⽀持KVM；如果结果中有vmx（Intel）或svm(AMD)字样，就说明CPU的⽀持的[root@kvm ~]# egrep -o 'vmx|svm' /proc/cpuinfo//安装kvm[root@kvm ~]# yum -y install qemu-kvm qemu-kvm-tools qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils libguestfs-tools//桥接⽹卡，⽤br0来桥接ens160⽹卡[root@kvm ~]# cd /etc/sysconfig/network-scripts/[root@kvm network-scripts]# cp ifcfg-ens33 ifcfg-br0[root@kvm network-scripts]# cat ifcfg-br0TYPE=BridgeDEVICE=br0NM_CONTROLLED=noBOOTPROTO=staticNAME=br0ONBOOT=yesIPADDR=192.168.237.131NETMASK=255.255.255.0GATEWAY=192.168.237.2DNS1=114.114.114.114DNS2=8.8.8.8[root@kvm network-scripts]# cat ifcfg-ens33TYPE=EthernetBOOTPROTO=staticNAME=ens33DEVICE=ens33ONBOOT=yesBRIDGE=br0NM_CONTROLLED=no//重启⽹络[root@kvm ~]# systemctl restart network[root@kvm ~]# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000link/ether 00:0c:29:7b:10:a5 brd ff:ff:ff:ff:ff:ffinet6 fe80::20c:29ff:fe7b:10a5/64 scope linkvalid_lft forever preferred_lft forever3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether 00:0c:29:7b:10:a5 brd ff:ff:ff:ff:ff:ffinet 192.168.237.131/24 brd 192.168.237.255 scope global br0valid_lft forever preferred_lft foreverinet6 fe80::20c:29ff:fe7b:10a5/64 scope linkvalid_lft forever preferred_lft forever4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000link/ether 52:54:00:1c:33:d6 brd ff:ff:ff:ff:ff:ffinet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0valid_lft forever preferred_lft forever5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000link/ether 52:54:00:1c:33:d6 brd ff:ff:ff:ff:ff:ff//启动服务[root@kvm ~]# systemctl enable --now libvirtd//验证安装结果[root@kvm ~]# lsmod|grep kvmkvm_intel 188740 0kvm 637289 1 kvm_intelirqbypass 13503 1 kvm//测试[root@kvm ~]# virsh -c qemu:///system listId 名称状态----------------------------------------------------[root@kvm ~]# virsh --version4.5.0[root@kvm ~]# virt-install --version1.5.0[root@kvm ~]# ln -s /usr/libexec/qemu-kvm /usr/bin/qemu-kvm[root@kvm ~]# ll /usr/bin/qemu-kvmlrwxrwxrwx 1 root root 21 10⽉ 20 23:14 /usr/bin/qemu-kvm -> /usr/libexec/qemu-kvm//查看⽹桥信息[root@kvm ~]# brctl showbridge name bridge id STP enabled interfacesbr0 8000.000c297b10a5 no ens33virbr0 8000.5254001c33d6 yes virbr0-nic1.2 kvm web管理界⾯安装kvm 的 web 管理界⾯是由 webvirtmgr 程序提供的。
MERGEPOINT UNITY®SWITCHInstaller/User GuideEuropean Union NotificationWARNING:This is a class A product.In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.USA NotificationWARNING:Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.NOTE:This equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part15of the FCC Rules.These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.This equipment generates,uses and can radiate radio frequency energy and,if not installed and used in accordance with the instruction manual,may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmful interference,in which case the user will be required to correct the interference at his/her own expense.Canadian NotificationThis Class A digital apparatus complies with Canadian ICES-003.Cet appareil numérique de la classe A est conformeàla norme NMB-003du Canada. Japanese NotificationKorean NotificationMergePoint Unity®Switch Installer/User GuideAvocent,the Avocent logo,The Power of Being There,MergePoint Unity,DSView and Dambrackas Video Compression are registered trademarks ofAvocent Corporation or its affiliates in the U.S.and other countries.All othermarks are the property of their respective owners.©2009Avocent Corporation.590-883-501CInstructionsThis symbol is intended to alert the user to the presence of important operating and maintenance(servicing)instructions in the literature accompanying the appliance.Dangerous VoltageThis symbol is intended to alert the user to the presence of uninsulated dangerous voltage within the product’s enclosure that may be of sufficient magnitude to constitute a risk of electric shock to persons.Power OnThis symbol indicates the principal on/off switch is in the on position.Power OffThis symbol indicates the principal on/off switch is in the off position.Protective Grounding TerminalThis symbol indicates a terminal which must be connected to earth ground prior to making any other connections to the equipment.iiiProduct Overview1 Features and Benefits1 Reduce cable bulk2 KVM switching capabilities2 True serial capabilities2 Local and remote user interfaces2 Control of virtual media and smart card-capable appliances2 Access the MergePoint Unity switch via a standard TCP/IP network3 DSView3management software plug-in3 Sample Configuration4 Installation5 MergePoint Unity Switch Connectivity5 Getting started7 Setting up your network8 Rack Mounting a MergePoint Unity Switch8 Rack mounting safety considerations8 Connecting the MergePoint Unity Switch Hardware9 Cascading MergePoint Unity Switches11 Configuring the MergePoint Unity Switch12 Setting up the built-in web server12 Connecting to the OBWI through a firewall12 Verifying the Connections14 Front and rear panel Ethernet connection LEDs14 Front panel status LEDs14 Rear panel power status LEDs14 IQ and DSRIQ-SRL modules15 Adjusting Mouse Settings on Target Devices15 Local and Remote Configuration17 The User Interfaces17 Local UI17iv MergePoint Unity®Switch Installer/User GuideOBWI18Using the user interfaces19Viewing System Information22MergePoint Unity Switch Sessions23Launching a session23Configuring sessions23Closing a session24MergePoint Unity Switch Appliance Tools24Rebooting the MergePoint Unity switch25Upgrading the MergePoint Unity switch firmware25Saving and restoring appliance configurations and appliance user databases26Network Settings27DNS Settings28Local UI Settings28Local port user settings28Virtual Media29Local virtual media settings30Modem Settings31Scan Mode31DSView3Server IP Addresses32User Accounts32Managing local accounts32Access levels32SNMP Settings34Event Settings34Setting Event Destinations35Configuring IQ Modules35Upgrading IQ modules36Power Device Settings36The Video Viewer39Table of Contents vThe Video Viewer Window39 Changing the toolbar41 Launching a Session42 Session time-out42 Window Size42 Adjusting the View43 Refreshing the Image44 Video Settings44 Additional video adjustment44 Target video settings46 Automatic video adjustment46 Video Test Pattern46 Vendor-specific video settings46 Color Settings47 Adjusting Color Depth47 Contrast and brightness47 Noise Settings47 Detection thresholds47 Block Noise Threshold and Pixel Noise Threshold47 Mouse Settings48 Adjusting mouse options48 Cursor type48 Mouse scaling50 Mouse alignment and synchronization51 Avocent Mouse Sync51 Virtual Media52 Requirements52 Sharing and preemption considerations52 Virtual Media dialog box53 Opening a virtual media session53vi MergePoint Unity®Switch Installer/User GuideClosing a virtual media session56Smart Cards56Keyboard Pass-through57Macros58Saving the View58Closing a Session58LDAP59Configuring LDAP in the User Interface59LDAP Overview parameters59LDAP Search parameters60LDAP Query parameters61Appliance and Target Device Query Modes62Setting up Active Directory for Performing Queries65Appendix A:Terminal Operations67Appendix B:Using Serial IQ Modules69Appendix C:UTP Cabling75Appendix D:Cable Pinout Information78Appendix E:Technical Specifications80Appendix F:Sun Advanced Key Emulation84Appendix G:Technical Support8711Features and BenefitsThe Avocent MergePoint Unity®KVM over IP and serial console switch combines analog anddigital technology to provide flexible,centralized control of data center servers and virtualmedia,and to facilitate the OA&M(operations,activation and maintenance)of remote branchoffices where trained operators may be unavailable.The IP-based MergePoint Unity switch gives you flexible target device management control and secure remote access from anywhere atanytime.The MergePoint Unity switch provides enterprise customers with the following features andoptions:•significant reduction of cable volume•keyboard,video and mouse(KVM)capabilites,configurable for analog(local)or digital (remote)connectivity•true serial capability through Secure Shell(SSH)and Telnet•enhanced video resolution support,up to1600x1200or1680x1050(wide-screen)native from target to remote•optional dual power models for redundancy•optional support for managing intelligent power devices•virtual media capability accessed through USB ports•dual independent local port video paths(dedicated to ACI)•dual stack IPv4(DHCP)and IPv6(DHCPv6and auto configuration)for simultaneous access •smart card capability•accessibility to target devices across10/100or1000BaseT(some models)LAN port(s)2MergePoint Unity®Switch Installer/User Guide•a MODEM port that supports V.34,V.90or V.92-compatible modems that may be used to access the switch when an Ethernet connection is not availableReduce cable bulkWith server densities continually increasing,cable bulk remains a major concern for networkadministrators.The MergePoint Unity switches significantly reduce KVM cable volume in the rack by utilizing the innovative IQ module and single,industry-standard Unshielded TwistedPair(UTP)cabling.This allows a higher server density while providing greater airflow andcooling capacity.KVM switching capabilitiesThe MergePoint Unity switch supports IQ modules,which are powered directly from the target device and provides Keep Alive functionality when the switch is not powered.The followingIQ modules are supported: DSRIQ-PS2,DSRIQ-USB,DSRIQ-VMC,DSRIQ-SUN,DSAVIQ-USB2DSAVIQ-PS2M and MPUIQ-VMC modules.The DSAVIQ-USB2,DSAVIQ-PS2MDSRIQ-VMC and MPUIQ-VMC modules are virtual media-capable.The DSRIQ-VMC andMPUIQ-VMC modules are also smart card-capable.True serial capabilitiesThe MergePoint Unity switch supports the MPUIQ-SRL module,which provides true serialcapabilities through Telnet.You can launch an SSH session or launch a serial viewer from the on-board web interface(OBWI)to connect the MergePoint Unity switch's attached targetdevices that have an MPUIQ-SRL module.Local and remote user interfacesYou can use the local user interface(local UI)by connecting directly to the local port tomanage the MergePoint Unity switch.You can also use the remote OBWI to manage yourswitch system.The OBWI is web-browser based and is launched directly from the switch,andany servers connected to the MergePoint Unity switch are automatically detected.The two user interfaces share a similar look and feel for an optimal user experience.Control of virtual media and smart card-capable appliancesThe MergePoint Unity switches allow you to view,move or copy data located on virtual media to and from any target device.Manage remote systems more efficiently by allowing operatingsystem installation,operating system recovery,hard drive recovery or duplication,BIOSupdating and target device backup.The MergePoint Unity switches allow you to use smart cards in conjunction with yourMergePoint Unity switch system.Smart cards are pocket-sized cards that store and processChapter1:Product Overview3 information.Smart cards such as the Common Access Card(CAC)can be used to storeidentification and authentication to enable access to computers,networks and secure rooms or buildings.Virtual media and smart card readers can be connected directly to the switch using USB ports located on the switch.In addition,virtual media and smart card readers may be connected toany remote workstation that is running the remote OBWI or DSView®3management software and is connected to the MergePoint Unity switch using an Ethernet connection.NOTE:To open a virtual media session with a target device,you must first connect the target device to a switchusing a virtual media capable DSAVIQ-USB2,DSRIQ-PS/2M DSRIQ-VMC or MPUIQ-VMC module.For a smart card,you must first connect the target device to a switch using a smart card-capable DSRIQ-VMC or MPUIQ-VMC module.Access the MergePoint Unity switch via a standard TCP/IP network The MergePoint Unity switches provide agentless remote control and access.No specialsoftware or drivers are required on the attached servers or client.NOTE:The client connects to the server housing the DSView3management software using an Internet browser.For modem access,you must install MergePoint Unity Remote Operations software included on the DSView3software CD-ROM(see the DSView3Installer/User Guide for more information).Users access the MergePoint Unity switch and all attached systems via Ethernet or using aV.34,V.90or V.92modem from a client.The clients can be located anywhere a valid network connection exists.DSView3management software plug-inThe DSView3software may be used with the MergePoint Unity switch to allow ITadministrators to remotely access,monitor and control target devices on multiple platformsthrough a single,web-based user interface.For more information,see the DSView3SoftwarePlug-In for MergePoint Unity Switches Technical Bulletin.SampleConfigurationFigure 1.1:Example MergePoint Unity Switch ConfigurationTable 1.1:Descriptions for Figure 1.1NumberDescription Number Description 1CAT 5Connection 6Telephone Network 2KVM Connection to the Switch 7Ethernet 3Remote IP Connection 8DSView 3Server 4MergePoint Unity Switch 9Analog User (local UI)5Modem 10Digital User (computer with Internet browser,remote OBWI)4MergePoint Unity®Switch Installer/User Guide52MergePoint Unity Switch ConnectivityA MergePoint Unity switching system transmits KVM and serial information between operatorsand target devices attached to the switch over a network using either an Ethernet or modemconnection.The MergePoint Unity switch uses TCP/IP for communication over Ethernet.Although10BaseT Ethernet may be used,Avocent recommends a dedicated,switched100BaseT or1000BaseTnetwork for switches that support it.The MergePoint Unity switch uses the Point-to-Point Protocol(PPP)for communication over aV.34,V.90or V.92modem.You can perform KVM and serial switching tasks by using theOBWI or the DSView3software.For more information on the DSView3software,visit or see the DSView3Installer/User Guide.Figure2.1illustrates a basic configuration for the MergePoint Unity switch,using theMergePoint Unity8032switch model for the example.Descriptions follow in Table2.1.Figure 2.1:Basic MergePoint Unity Switch Configuration (MergePoint Unity 8032Switch Shown)Table 2.1:Descriptions for Figure 2.1NumberDescription Number Description 1Digital User 8Power Cord 2Telephone Network 9Ports 1-326MergePoint Unity®Switch Installer/User GuideNumber Description Number Description3Network10Local USB Connections 4Modem11Power Control Device 5Analog User12Target Devices1-326External Virtual Media13IQ Modules(PS/2,USB,VMC,Sun and serial are available)7MergePoint Unity8035 SwitchGetting startedBefore installing your MergePoint Unity switch,refer to the following lists to ensure you have all items that shipped with the MergePoint Unity switch,as well as other items necessary forproper installation.Supplied with the MergePoint Unity switch•Rack mount bracket kit•Rack Mounting Bracket Quick Installation Guide•MergePoint Unity Switch Quick Installation Guide•Safety and Regulatory Statements Guide•Cables and adaptors for the MODEM and SETUP ports•AC power cord(s)Additional items needed•One IQ module per target device•One DSRIQ-SRL or MPUIQ-SRL module per serial device•One UTP patch cable per IQ module(4-pair UTP,up to45meters)•UTP patch cable(s)for network connectivity(4-pair UTP,up to45meters)•One DSAVIQ-USB2,DSAVIQ-PS2M DSRIQ-VMC or MPUIQ-VMC module per target device for virtual media sessions•One DSRIQ-VMC or MPUIQ-VMC module per target device for smart card control•(Optional)DSView3software•(Optional)V.34,V.90or V.92-compatible modem and cablesChapter2:Installation78MergePoint Unity®Switch Installer/User Guide•(Optional)Power control device(s)Setting up your networkThe MergePoint Unity switching system uses IP addresses to uniquely identify the switch and the target devices.The MergePoint Unity switch family supports both Dynamic HostConfiguration Protocol(DHCP)and static IP addressing.Avocent recommends that IP addresses be reserved for each switch and that they remain static while the switches are connected to the network.For additional information on setting up the MergePoint Unity switch using the DSView3software,and for information on how the MergePoint Unity switch uses TCP/IP,see theDSView3Installer/User Guide.Rack Mounting a MergePoint Unity SwitchA rack mounting kit is supplied with each MergePoint Unity switch.You may either place theMergePoint Unity switch on the rack shelf or mount the switch directly into an ElectronicIndustries Alliance(EIA)standard rack.Most MergePoint Unity switches may be rack mounted in a1U configuration.The MergePoint Unity switch family does not support a0U configuration.Rack mounting safety considerations•Rack Loading:Overloading or uneven loading of racks may result in shelf or rack failure, causing damage to equipment and possible personal injury.Stabilize racks in a permanentlocation before loading begins.Mount components beginning at the bottom of the rack,then work to the top.Do not exceed your rack load rating.•Power Considerations:Connect only to the power source specified on the unit.When multiple electrical components are installed in a rack,ensure that the total componentpower ratings do not exceed circuit capabilities.Overloaded power sources and extensioncords present fire and shock hazards.•Elevated Ambient Temperature:If installed in a closed rack assembly,the operating temperature of the rack environment may be greater than room e care not toexceed the rated maximum ambient temperature of the switch.•Reduced Air Flow:Install the equipment in the rack so that the amount of airflow required for safe operation of the equipment is not compromised.•Reliable Earthing:Maintain reliable earthing of rack mounted equipment.Pay particular attention to supply connections other than direct connections to the branch circuit(forexample,use of power strips).Chapter2:Installation9 For complete instructions on installing the rack mounting bracket,please refer to your RackMounting Bracket Quick Installation Guide.Connecting the MergePoint Unity Switch HardwareTo connect and turn on your MergePoint Unity switch:NOTE:To avoid potential video and/or keyboard problems when using Avocent products:If thebuilding has3-phase AC power,ensure that the computer and monitor are on the same phase.For best results,they should be on the same circuit.WARNING:To reduce the risk of electric shock or damage to your equipment:-Do not disable the power grounding plug.The grounding plug is an important safety feature.-Plug the power cord into a grounded(earthed)outlet that is easily accessible at all times.-Disconnect the power from the product by unplugging the power cord from either the electrical outlet or theproduct.-The AC inlet is the main disconnect for removing power to this product.For products that have more than one AC inlet,to remove power completely,all AC line cords must be disconnected.-This product has no user serviceable parts inside the product enclosure.Do not open or remove product cover.1.Plug your VGA monitor and USB keyboard and mouse cables into the appropriatelylabeled ports.You must install both a keyboard and mouse on the local ports or thekeyboard will not initialize properly.2.Choose an available port on the MergePoint Unity switch.Plug one end of a CAT5cable(4-pair,up to150ft/45m)into a numbered port.Plug the other end into an RJ-45connector of an IQ module.3.Plug the IQ module into the appropriate ports on the back of a target device.Repeat thisprocedure for all target devices you want to connect.NOTE:When connecting a DSRIQ-SUN module,you must use a multi-sync monitor in the local port toaccommodate Sun computers that support both VGA and sync-on-green or composite sync.4.Plug a CAT5cable from the Ethernet network into a LAN port on the back of theMergePoint Unity work users will access the MergePoint Unity switch throughthis port.5.(Optional)The MergePoint Unity switch may also be accessed using an ITU V.92,V.90orV.24-compatible modem.Plug one end of an RJ-45cable into the MODEM port on theMergePoint Unity switch.Plug the other end into the RJ-45to DB-9(male)adaptor,whichthen plugs into the appropriate port on the back of the modem.NOTE:Using a modem connection instead of a LAN connection will limit the performance capability of yourMergePoint Unity switch.10MergePoint Unity®Switch Installer/User Guide6.(Optional)Plug one end of the RJ-45cable supplied with the Power Distribution Unit(PDU)into the PDU1port on the MergePoint Unity ing the supplied RJ-45adaptor,plug the other end into the PDU.Plug the power cords from the target devices intothe PDU.Plug the PDU into an appropriate AC wall outlet.Repeat this procedure for thePDU2port to connect a second PDU,if desired.7.Turn on each target device,then locate the power cord that came with the MergePointUnity switch.Plug one end into the power socket on the rear of the MergePoint Unityswitch.Plug the other end into an appropriate AC wall outlet.If using a model equippedwith dual power,use your second power cord to connect to the second power socket onthe rear of the MergePoint Unity switch and plug the other end into an appropriate ACwall outlet.To connect local virtual media or a smart card reader:Connect the virtual media or smart card reader to an available USB port on the MergePointUnity switch.NOTE:For all virtual media sessions,you must use a DSAVIQ-USB2,DSAVIQ-PS2M,DSRIQ-VMC or MPUIQ-VMC module.For all smart card readers,you must use a DSRIQ-VMC or MPUIQ-VMC module.For information on connecting virtual media remotely,see Virtual Media on page52.Forinformation on connecting a smart card reader remotely,see Smart Cards on page56.To connect a DSRIQ-SRL module to a serial device:1.Attach the DSRIQ-SRL module9-pin serial connector to the serial port of the device to beconnected to your MergePoint Unity switch.2.Attach one end of the UTP patch cable to the RJ-45connector on the DSRIQ-SRL module.Connect the other end of the UTP patch cable to the desired port on the back of yourMergePoint Unity switch.NOTE:The DSRIQ-SRL module is a DCE device and only supports VT100terminal emulation.3.Connect the power supply to the power connector on your DSRIQ-SRL module.The cableexpander can be used to provide power for up to four DSRIQ-SRL modules from a singlepower supply.4.Connect the DSRIQ-SRL module power supply to a grounded AC wall outlet.Turn onyour serial device.See Using DSRIQ-SRL Modules on page69.To connect an MPUIQ-SRL module to a serial device:1.Attach the MPUIQ-SRL module CAT5connector to the serial device.Chapter2:Installation112.(Optional)Attach the MPUIQ-SRL module to an RJ-45to9-pin female adaptor.Attach theadaptor to the serial port of the serial device.3.Plug one end of a CAT5cable(4-pair,up to150ft/45m)into an available numbered porton the rear of the MergePoint Unity switch.Plug the other end into the RJ-45connector ofthe MPUIQ-SRL module.4.Connect the power supply to the power connector on your MPUIQ-SRL module.The cableexpander can be used to provide power for up to four MPUIQ-SRL modules from a singlepower supply.5.(Optional)Attach a USB-to-barrel power cord to the power connector on your MPUIQ-SRLmodule.Plug the USB connector on the USB-to-barrel power cord into any available USBport on the serial target device.NOTE:You can not use the cable expander with the USB-to-barrel power cord.Multiple MPUIQ modules can usepower off of the power supply,but not off of the target device.6.If using the power supply,connect the MPUIQ-SRL module power supply to anappropriate AC wall outlet.Turn on your serial device.Cascading MergePoint Unity SwitchesYou can cascade up to two levels of MergePoint Unity switches,enabling users to connect toup to1024servers.In a cascaded system,each target port on the main MergePoint Unity switch will connect to the ACI port on each cascaded MergePoint Unity switch.Each cascaded switch can then be connected to a server with an IQ module.To cascade multiple MergePoint Unity switches:1.Attach one end of a CAT5cable to a target port on the MergePoint Unity switch.2.Connect the other end of the CAT5cable to the ACI port on the back of your cascadedMergePoint Unity switch.3.Connect the devices to your cascaded MergePoint Unity switch.4.Repeat these steps for all the cascaded MergePoint Unity switches you wish to attach toyour system.NOTE:The system will automatically“merge”the two switches.All servers connected to the cascaded MergePoint Unity switch will display on the main MergePoint Unity switch server list in the local UI.NOTE:The MergePoint Unity switch supports one cascaded switch per target port of the main switch.You cannotattach more switches to the cascaded switches.NOTE:Local port cascading is not supported on the MergePoint Unity switch.Configuring the MergePoint Unity SwitchOnce all physical connections have been made,you will need to configure the switch for use in the overall switching system.This can be accomplished in two ways.To configure the MergePoint Unity switch using the DSView3software:See the DSView3Installer/User Guide for detailed instructions.To configure the MergePoint Unity switch using the local UI:See Network Settings on page27for detailed instructions on using the local UI to configureinitial network setup.Setting up the built-in web serverYou can access the MergePoint Unity switch via an embedded web server that handles mostday-to-day switching tasks.Before using the web server to access the switch,first specify an IP address through the local port on the back panel of the switch or local UI.See Chapter3fordetailed instructions on using the user interface for switching.Connecting to the OBWI through a firewallFor MergePoint Unity switch installations that use the OBWI for access,four ports must beopened in a firewall if outside access is desired.TCP PortNumberFunction22Used for SSH for serial sessions to an MPUIQ-SRL module23Used for Telnet(when Telnet is enabled)80Used for the initial downloading of the Avocent Video Viewer(for downloading the Java applet)443Used by the web browser interface for managing the MergePoint Unity switch and launching KVM sessions2068Transmission of KVM session data(mouse&keyboard)or transmission of video on MergePoint Unity switchesTable2.2:TCP Ports and Functions for the MergePoint Unity Switch OBWIIn a typical configuration,as shown in Figure2.2,the user’s computer is located outside of the firewall,and the MergePoint Unity switch resides inside the firewall.12MergePoint Unity®Switch Installer/User GuideFigure 2.2:Typical MergePoint Unity Switch Firewall ConfigurationTable 2.3:Descriptions for Figure 2.2Number Description 1MergePoint Unity Switch 2Firewall 3User’s Computer 4Firewall Forwards HTTP Requests and KVM Traffic to the MergePoint Unity Switch 5User Browses to Firewall’s External IP AddressTo configure the firewall:To access the MergePoint Unity switch from outside a firewall,configure your firewall to forward ports 22,23(if Telnet is enabled),80,443and 2068from its external interface to the KVM switch through the firewall’s internal interface.Consult the manual for your firewall for specific port forwarding instructions.For information on launching the OBWI,see OBWI on page 18.Chapter 2:Installation 1314MergePoint Unity®Switch Installer/User GuideVerifying the ConnectionsFront and rear panel Ethernet connection LEDsOn16-port and32-port models of the MergePoint Unity switch,the front and rear panelsfeature two LEDs indicating the Ethernet LAN1connection status and two LEDs indicating the Ethernet LAN2connection status.On the4-port and8-port switches,all LEDs are on the rearpanel.•The green LEDs illuminate when a valid connection to the network is established and blink when there is activity on the port.•The bi-color LEDs may illuminate either green or amber.•They illuminate green when the communication speed is1000M.•They illuminate amber when the communication speed is100M.•They are not illuminated when the communication speed is10M.Front panel status LEDsThe front panel of MergePoint Unity switches(16-port and32-port models only)have a bi-color general status LED that may illuminate green or amber.•The LED illuminates green when the MergePoint Unity switch is turned on and operating normally.•The LED blinks green when the MergePoint Unity switch is booting.•The LED illuminates amber if a fault condition occurs,such as power supply failure(for MergePoint Unity switches equipped with dual power supplies),elevated ambienttemperature or fan failure.The LED will continue to illuminate amber as long as the failurepersists.•The LED blinks between green and amber when the MergePoint Unity switch is Flash downloading.Rear panel power status LEDsThe rear panel of16-port and32-port MergePoint Unity switches feature one power status LED for single power MergePoint Unity switches and two power status LEDs for dual powerMergePoint Unity switches.On the4-port and8-port switches,all LED status indicators are on the rear panel.The LED(s)illuminate green when the MergePoint Unity switch is turned onand operating normally.•The LED is off if the power supply does not have power or has failed.。
