您所在的组无权查看该日志

Install ESXi 5.5 with Realtek 8111/8168 NIC Posted by Paul Brarenon Tue Sep 24th, 2013 (edited on Mon Dec 16th, 2013) in ESXi, Network ⋅ 18 CommentsESXi 5.0 and 5.1 all worked fine with the common Realtek 8111/8168 series of network adapters, typically found in a variety of consumer-class motherboards. What to do in the home lab? Suddenly you can’t even install ESXi, even though you have a perfectly workable system that happens to already have Realtek onboard. Such as my very own vZilla? Yes, with 5.5, you’ll get the dreaded “No compatible network adapter found please consult Hardware Compatibility Guide for supported adapters” message. Even though you likely won’t find this chipset on the HCL, this article gets you clear of that hurtle, offering two approaches.Software fix #1:  Inject the 5.1 driver into the 5.5 installation media.How’s simply adding the driver from 5.1 back into your installer ISO image sound. You know, the driver that VMware has apparent...

添加RTL8168、8111驱动到ESXI5.5 Adding Realtek R8168 Driver to ESXi 5.5.0 ISO The ESXi 5.5.0 Build 1331820  that came out yesterday, did not include any Realtek R8168 or R8169 driver in it. So if your homelab ESXi host only has these Realtek 8168 network cards, you need to build a custom ISO.The most simple tool to use is Andreas Peetz’s (@VFrontDE)  ESXi Customizer 2.7.1 tool. The ESXi Customizer tool allows you to select the ESXi 5.5.0 ISO file and include into it a new Driver in .vib format.You can then download and extract the VMware Bookbank NET-R8168 driver from vSphere 5.1 ISO or download it from the following link for your conveniance. VMware_bootbank_net-r8168_8.013.00-3vmw.510.0.0.799733VMware_bootbank_net-r8169_6.011.00-2vmw.510.0.0.799733Launch the ESXi Customizer and build your new .ISO fileThis will create a ESXi-Custom.ISO file that you can burn to a CD and use to install vSphere 5.5 on your host.

How to Create a Completely Separate Network Inside XenServer Document ID: CTX116456   /   Created On: 2008-5-7   /   Updated On: 2009-10-19 Average Rating: (8 ratings) View products this document applies to  SummaryThis document describes how to create a separate network inside a XenServer. Such a network can be used for testing purposes because it is completely separate from other networks (behind network address translation). For example, full Active Directory implementation where you can also configure a DHCP server. The DHCP server will not interfere with other DHCP servers on other networks connected to the XenServer.This implementation was tested on XenServer 4.x and does not include a firewall configuration.RequirementsLinux Templates installedKnowledge of Nano or Vi text editor (this article uses the Nano editor for simplicity)Basic Linux knowledgeBasic IP and network understandingBasic XenServer administr...

How to Set up XenServer in a Routed Network View products this document applies to  SummaryIn some cases (such as hosting environments), multiple subnets of IP addresses are provided on a single interface where subnets other than the original are not assigned a default gateway. This configuration works when an IP interface exists within the same subnet as the default gateway from the primary subnet, however this is not always possible.The diagram below depicts this scenario:In this case, if a VM is configured within the 172.16.20.0/24 subnet, the customer’s default gateway (172.16.1.1) cannot be used and connectivity to subnets other than 172.16.20.0/24 isn not possible.Whenever possible, you should configure the default gateway for the secondary subnets as secondary IP addresses on the VLAN. This action completely avoids the need for complex workarounds.NoticeThis article makes changes to the XenServer configuration which, if made improperly, might prevent network access to...

上次在某机房遇到的问题，ip在母鸡可以用，小鸡不可用。后来这样解决。现在来和大家分享。请执行下列步骤配置的XenServer：1。使用下面的命令来确定桥XenServer所使用的接口在同一子网route | grep default复制代码1.gif(3.99 KB, 下载次数: 0)2。在 /etc/sysconfig/network-scripts 新建一个 “xenbrX“DEVICE=xenbrX:1ONBOOT=yesBOOTPROTO=noneNETMASK= <SUBNET MASK>IPADDR= <IP ADDRESS>复制代码3。启用IP转发的XenServer Dom0中为路由器，通过编辑/ etc / sysctl.conf并改变线路：- from -net.ipv4.ip_forward = 0- to -net.ipv4.ip_forward = 1复制代码3.gif(6.98 KB, 下载次数: 0)4。配置防火墙 ，取代xenbrX步骤1中确定的值后，通过添加下面一行到/ etc / sysconfig中/ iptables的启用IP接口之间转发） ：-A RH-Firewall-1-INPUT -i xenbrX -o xenbrX -j ACCEPT复制代码4.gif(14.55 KB, 下载次数: 0)5.应用通过运行以下命令sysctl -pifup xenbrX:1service iptables restart6. Assign VMs to the managem复制代码

ESXi 和 vCenter Server 5.5 文档 > vSphere 安装和设置 > 系统要求 ESXi 硬件要求确保主机符合 ESXi 5.5 支持的最低硬件配置。 硬件和系统资源要安装和使用 ESXi 5.5，您的硬件和系统资源必须满足下列要求： ■ 支持的服务器平台。有关支持的平台的列表，请参见《VMware 兼容性指南》，网址为 http://www.vmware.com/resources/compatibility。 ■ ESXi 5.5 将仅在安装有 64 位 x86 CPU 的服务器上安装和运行。 ■ ESXi 5.5 要求主机至少具有两个内核。 ■ ESXi 5.5 仅支持 LAHF 和 SAHF CPU 指令。 ■ ESXi 5.5 需要在 BIOS 中针对 CPU 启用 NX/XD 位。 ■ ESXi 支持多种 x64 多核处理器。有关受支持处理器的完整列表，请参见《VMware 兼容性指南》，网址为 http://www.vmware.com/resources/compatibility。 ■ ...

Traffic accounting with iptablesJump to: navigation,searchSuppose you need to know how much traffic your containers eat. It can be easily doneusing iptables.Contents [hide] 1 Situation description2 Solution3 More complicated cases4 Scripting4.1 Get CTIDs of all running containers4.2 Get all IPs of running containers4.3 Set up all needed iptables rules4.4 Generate a traffic.log4.5 Sample php script to store the trafficlog in a database4.6 A SQL query to get the traffic for the last 30 days4.7 Notes5 See also[edit] Situation description Let's consider the very simple situation: one container with one IP address on the Hardware Nodewith only one network interface. To be more exact, assume that container ID is 200, the IP address of the HNis 192.168.0.56, the network interface name is eth0, and the IP address of the container is 192.168.0.117.You wish to know how many bytes container 200 eats. One more assumption is that there are no iptables ruleson HN now. All these assumptio...

Proxmox using iptables in openvz guests I recently upgraded Proxmox and noticed iptables was not working in the guests.Turns out a small edit is required to /etc/vz/vz.conf (we need to add some more modules to be used in the openvz guests).Using any editor, open /etc/vz/vz.conf and change and find the “IPTABLES=” lineChange:IPTABLES="ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length"To:IPTABLES="ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp"Then reboot (you can probably just re-start your guests).

OpenVZ 更加好支持iptables 在硬件节点内修改iptables挂载模组vim /etc/sysconfig/iptables-configIPTABLES_MODULES="ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp"vim /etc/sysconfig/vzIPTABLES="ipt_REJECTipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp"重新启动VZ服务service vz restart放行更加多的iptables 条目# vzctl set $CTID --numiptent 400 --savevzctl enter $CTIDiptables -P INPUT DROPiptables -P FORWARD DROPiptables -I INPUT -j ACCEPT -m state --state ESTABLISHED,RELATEDiptables -I FORWARD -j ACCEPT -m state --state ESTABLISHED,RELATEDiptables -I INPUT -j ACCEPT -i loiptables -I INPUT -p tcp --dport 25 -j ACCEPTiptables -I INPUT -p tcp --dport 110 -j ACCEPTiptables -I INPUT -p tcp --dport 995 -j ACCEPTiptables -I INPUT -p ...