H3C交换机_典型配置举例-6W100-以太网链路聚合典型配置举例

1 以太网链路聚合配置任务简介表1-5 以太网链路聚合配置任务简介配置任务说明详细配置配置聚合组配置静态聚合组二者必选其一1.3.1 配置动态聚合组 1.3.2聚合接口相关配置配置聚合接口的描述信息可选 1.4.1 配置三层聚合接口MTU 可选 1.4.2 配置处理或转发三层聚合接口流量的业务处理板可选 1.4.3 开启聚合接口链路状态变化Trap功能可选 1.4.4 限制聚合组内选中端口的数量可选 1.4.5 关闭聚合接口可选 1.4.6 恢复聚合接口的缺省配置可选 1.4.7配置聚合负载分担配置聚合负载分担类型可选 1.5.1配置聚合负载分担为本地转发优先可选 1.5.2 配置聚合流量重定向功能可选 1.6 2 1.3 配置聚合组请根据需要聚合的以太网接口类型来配置相应类型的聚合组：当需要聚合的是二层以太网接口时，请配置二层聚合组；当需要聚合的是三层以太网接口时，请配置三层聚合组。

聚合链路的两端应配置相同的聚合模式。

●配置或使能了下列功能的端口将不能加入二层聚合组：RRPP（请参见“可靠性配置指导/RRPP”）、MAC地址认证（请参见“安全配置指导/MAC地址认证”）、端口安全模式（请参见“安全配置指导/端口安全”）、报文过滤功能（请参见“安全配置指导/防火墙”）、以太网帧过滤功能（请参见“安全配置指导/防火墙”）、IP Source Guard功能（请参见“安全配置指导/IP Source Guard”）、802.1X功能（请参见“安全配置指导/802.1X”）以及Portal免认证规则源接口（请参见“安全配置指导/Portal”）。

●配置或使能了下列功能的接口将不能加入三层聚合组：IP地址（请参见“三层技术-IP业务配置指导/IP地址”）、DHCP客户端（请参见“三层技术-IP业务配置指导/DHCP”）、BOOTP客户端（请参见“三层技术-IP业务配置指导/DHCP”）、VRRP功能（请参见“可靠性配置指导/VRRP”）和Portal功能（请参见“安全配置指导/Portal”）。

光纤链路排错经验一、组网：用户采用4台S5500作为接入交换机、1台S5500作为核心交换机组网，4台接入交换机分别在三个仓库以及门卫处与核心机房都是通过2根八芯单模光纤走地井连接，在这5个机房再通过跳纤来连接到交换上。

用户要求实现内网的用户主机访问公共服务器资源，并实现全网互通。

组网如下图所示：二、问题描述：PC现无法访问server服务器，进一步发现S5500光纤端口灯不亮，端口信息显示down状态。

在核心交换机端通过自环测试发现该端口以及光模块正常，接入交换机端也同样测试发现正常。

监控网络正常使用，再将网络接口转接到监控主干链路上，发现网络同样无法正常使用。

三、过程分析：想要恢复链路，首先要排查出故障点，根据故障点情况结合实际恢复链路通畅。

在这里主要分析光纤通路，光信号从接入交换机光口出来通过跳线，转接到主干光纤，然后再通过核心跳线转接到核心交换上。

由于该链路不通，首先要排除两端接口以及光模块问题，这里使用自环检测(如果是超远距离传输光纤线缆需要接光衰然后在自环，防止烧坏光模块)。

当检测完成发现无问题，再测试接入端的光纤跳纤：如果是多模光纤可以将一端接到多模光纤模块的tx口，检测对端是否有光；单模光纤如果没有光功率计可以使用光电笔检测(该方法只能检测出中间无断路，并不能检测出线路光衰较大的情况)。

最后再检测主线路部分，检测方式同跳线一样。

光路走向流程如图所示：四、解决方法：从上述的分析可以看出，只要保证了光信号一出一收两条路径都能正常就可以解决用户无法访问服务器的问题。

为了保证光路正常通路，最好的解决方法就是，通过使用光功率计来检测对端发射光在本端的光功率是否在光口可接受范围内。

由于用户组网使用了一些监控设备来接入该主干光缆，并且该光路现正常使用，通过将网络光纤转接到该监控主干光缆，发现网络光路仍然不通；并且两端端口自环检测正常。

由此可以判断出主要问题在两端的跳纤上。

如图所示：在没有光功率计并且客户业务又比较着急恢复的情况，可以先将两端的接入跳纤更换。

SecPath系列防火墙IPSec典型配置举例关键词：IKE、IPSec摘要：本章首先介绍了IKE和IPSec的基本概念，随后说明了防火墙的配置方法，最后给出两种典型应用的举例。

缩略语：缩略语英文全名中文解释IKE Internet Key Exchange 因特网密钥交换Security IP网络安全协议IPsec IP目录1 特性简介 (3)1.1 IPSec基本概念 (3)1.1.1 SA (3)1.1.2 封装模式 (3)2 应用场合 (4)3 配置指南 (4)3.1 配置概述 (4)3.2 配置ACL (6)3.3 配置IKE (6)3.3.1 配置IKE全局参数 (6)3.3.2 配置IKE安全提议 (7)3.3.3 配置IKE对等体 (8)3.4 IPSec安全提议 (10)3.5 配置安全策略模板 (12)3.6 配置安全策略 (14)3.7 应用安全策略组 (16)4 配置举例一：基本应用 (17)4.1 组网需求 (17)4.2 使用版本 (18)4.3 配置步骤 (18)4.4 配置结果验证 (27)4.4.1 查看IPSec安全联盟 (27)4.4.2 查看报文统计 (27)5 配置举例二：与NAT结合 (27)5.1 组网需求 (27)5.2 配置说明 (28)5.3 配置步骤 (28)5.4 配置验证结果 (34)5.4.1 查看IPSec安全联盟 (34)5.4.2 查看报文统计 (35)6 注意事项 (35)7 相关资料 (35)7.1 相关协议和标准 (35)7.2 其它相关资料 (36)1 特性简介IPsec（IP Security）协议族是IETF制定的一系列协议，它为IP数据报提供了高质量的、可互操作的、基于密码学的安全性。

特定的通信方之间在IP层通过加密与数据源验证等方式，来保证数据报在网络上传输时的私有性、完整性、真实性和防重放。

IPsec通过AH（Authentication Header，认证头）和ESP（Encapsulating Security Payload，封装安全载荷）这两个安全协议来实现上述目标，并且还可以通过IKE（Internet Key Exchange，因特网密钥交换协议）为IPsec提供自动协商交换密钥、建立和维护安全联盟的服务，以简化IPsec 的使用和管理。

H3C和CISCO交换机做聚合配置实例教学H3C和CISCO交换机做聚合配置实例教学端口聚合也叫做以太通道，主要用于交换机之间连接。

那么两种不同的交换机怎么做聚合配置呢?下面跟yjbys店铺一起来看看H3C和CISCO交换机做聚合配置实例教程，希望对同学们学习交换机有所帮助!一、网络环境本网络是xx大厦，3台交换机做端口聚合的课题网络环境：H3C_A交换机<----------------->H3C_B交换机<----- ----------------------->cisco(3560)交换机H3C_B交换机做为中心交换机由于带宽需要，加上该9楼上了很多美国著名的avocentKVM的监控设备，需要很大的带宽，因此做了4组的端口链路聚合的需要因此以下配置命令1、H3C_A的.配置如下：(动态链路聚合，LACP默认启动)[H3C_A]sys[H3C_A]int bridge-aggregation 1[H3C_A]link-aggregation mode dynamil[H3C_A]int giabthernet1/0/26[H3C_A_giabthernet1/0/26]duplex full[H3C_A_giabthernet1/0/26]speed 1000[H3C_A_giabthernet1/0/26]port link-type trunk[H3C_A_giabthernet1/0/26]port trunk permit vlan all因此，其它三个端口都是一样，如以上配置就可以了，同时H3C_B也是同样如H3C_A的配置一样，配好了，检查下端口的问题。

2、思科的配置[cisco]int port-channel 2[cisco]swit trunk encapsulation dot1q[cisco]swit mode trunk[cisco]swit trunk allowed vlan all[cisco]进入端口模式配置[cisco]int gig0/19[cisco]duplex full[cisco]speed 1000[cisco]swit trun encapsulation dot1q[cisco]swit mode trunk[cisco]swit trunk allowed vlan all[cisco]channel-group 2 mode active其它的端口同样的配置配置好了在H3C交换机用 dis link-aggregation summary查看信息同时，在思科交换机用show ethernetchannel summary查看信息最后经过上面的配置，端口聚合就可以通了。

H3C路由器NAT典型配置案列（史上最详细）神马CCIE，H3CIE,HCIE等网络工程师日常实施运维必备，你懂的。

1.11 NAT典型配置举例1.11.1 内网用户通过NAT地址访问外网（静态地址转换）1. 组网需求内部网络用户10.110.10.8/24使用外网地址202.38.1.100访问Internet。

2. 组网图图1-5 静态地址转换典型配置组网图3. 配置步骤# 按照组网图配置各接口的IP地址，具体配置过程略。

# 配置内网IP地址10.110.10.8到外网地址202.38.1.100之间的一对一静态地址转换映射。

<Router> system-view[Router] nat static outbound 10.110.10.8 202.38.1.100# 使配置的静态地址转换在接口GigabitEthernet1/2上生效。

[Router] interface gigabitethernet 1/2[Router-GigabitEthernet1/2] nat static enable[Router-GigabitEthernet1/2] quit4. 验证配置# 以上配置完成后，内网主机可以访问外网服务器。

通过查看如下显示信息，可以验证以上配置成功。

[Router] display nat staticStatic NAT mappings:There are 1 outbound static NAT mappings.IP-to-IP:Local IP : 10.110.10.8Global IP : 202.38.1.100Interfaces enabled with static NAT:There are 1 interfaces enabled with static NAT.Interface: GigabitEthernet1/2# 通过以下显示命令，可以看到Host访问某外网服务器时生成NAT会话信息。

H3C三层交换机配置实例H3C三层交换机配置实例1 网络拓扑图 02 配置要求 03划分VLAN并描述 (1)3.1进入系统视图 (1)3.2 创建VLAN并描述 (1)4 给VLAN设置网关 (2)4.1 VLAN1的IP地址设置 (2)4.2 VLAN100的网关设置 (2)4.3 VLAN101的网关设置 (2)4.4 VLAN102的网关设置 (3)4.5 VLAN103的网关设置 (3)5 给VLAN指定端口，设置端口类型 (3)5.1 VLAN100指定端口 (3)5.2 VLAN102指定端口 (4)5.3 VLAN1/101/103指定端口 (4)6 配置路由协议 (5)6.1 默认路由 (5)6.2配置流分类 (5)6.3 定义行为 (5)6.4 应用QOS策略 (6)6.5 接口配置QOS策略 (6)1 网络拓扑图图1-1 网络拓扑图2 配置要求用户1网络：172.16.1.0/24 至出口1网络：172.16.100.0/24 用户2网络：192.168.1.0/24 至出口2网络：192.168.100.0/24实现功能：用户1通过互联网出口1，用户2通过互联网出口2。

3划分VLAN并描述3.1进入系统视图<H3C>system-view //进入系统视图图3-1 系统视图3.2 创建VLAN并描述[H3C]vlan 1 //本交换机使用[H3C-vlan1]description Manager //描述为“Manager”[H3C-vlan1]quit[H3C]vlan 100 //划分vlan100[H3C-vlan100]description VLAN 100 //描述为“VLAN 100”[H3C-vlan100]quit[H3C]vlan 101 //划分vlan101[H3C-vlan101]description VLAN 101 //描述为“VLAN 101”[H3C-vlan101]quit[H3C]vlan 102 //划分vlan102[H3C-vlan102]description VLAN 102 //描述为“VLAN 102”[H3C-vlan102]quit[H3C]vlan 103 //划分vlan103[H3C-vlan103]description VLAN 103 //描述为“VLAN 103”[H3C-vlan103]quit[H3C]图3-2 划分VLAN及描述4 给VLAN设置网关4.1 VLAN1的IP地址设置把VLAN1的IP地址设置为192.168.0.254，子网掩码为255.255.255.0，用于本地使用。

H3C交换机配置链路聚合H3C交换机配置链路聚合如何?要如何弄H3C交换机配置链路聚合.下面是店铺收集整理的H3C交换机配置链路聚合，希望对大家有帮助~~H3C交换机配置链路聚合创建聚合组1(根据具体情况选择下面两种方式之一)。

l采用静态聚合模式：创建二层聚合接口1system-view[SwitchA] interface bridge-aggregation 1[SwitchA-Bridge-Aggregation1] quitl采用动态聚合模式：创建二层聚合接口，并配置动态聚合模式system-view[SwitchA] interface bridge-aggregation 1[SwitchA-Bridge-Aggregation1] link-aggregation mode dynamic# 将以太网端口GigabitEthernet1/0/1至GigabitEthernet1/0/3加入聚合组1。

[SwitchA] interface GigabitEthernet 1/0/1[SwitchA-GigabitEthernet1/0/1] port link-aggregation group 1[SwitchA-GigabitEthernet1/0/1] interface GigabitEthernet 1/0/2[SwitchA-GigabitEthernet1/0/2] port link-aggregation group 1[SwitchA-GigabitEthernet1/0/2] interface GigabitEthernet 1/0/3[SwitchA-GigabitEthernet1/0/3] port link-aggregation group 1[SwitchA-GigabitEthernet1/0/3] quit# 配置二层聚合接口1所属VLAN，并将该配置批量下发到各成员端口上。

H3C华三链路聚合的原理及配置1.链路聚合的作⽤：将多条物理链路捆绑在⼀起形成⼀条以太⽹逻辑链路，实现增加链路带宽的⽬的，同时这些捆绑在⼀起的链路通过相互动态备份，可以有效地提⾼链路的可靠性2.聚合模式：⑴静态聚合：⼀旦配置好后，端⼝的选中/⾮选中状态就不会受⽹络环境的影响，⽐较稳定⑵动态聚合：通过LACP协议实现，能够根据对端和本端的信息调整端⼝的选中/⾮选中状态，⽐较灵活3.静态聚合的⼯作机制⑴参考端⼝的选举：⽤来选择聚合成员端⼝的标准端⼝；优先级->全双⼯/⾼速率->全双⼯/低速率->半双⼯/⾼速率->半双⼯/低速率的优先次序，若优先级相同则选择端⼝号最⼩的的端⼝⑵确定成员端⼝状态为选中端⼝①端⼝要处于up状态②端⼝的操作key和属性类配置与参考端⼝要相同③聚合组中候选端⼝的数量没有超过上限*操作key：⽤于选择链路聚合成员端⼝的配置信息，由参考端⼝的第⼆类配置⽣成，第⼆类配置与操作Key⼀致，端⼝才能被选中*属性类配置：包括速率、双⼯模式、链路状态(UP/DOWN）这三项配置，速率和双⼯模式会参与参考端⼝选举，链路状态会影响成员端⼝是否被选中*端⼝的第⼀类配置：不参与操作Key计算的配置信息；例如：MVRP、MSTP等*端⼝的第⼆类配置：参与操作Key计算的配置信息；例如：Vlan配置、端⼝类型、QinQ、Mac地址学习配置4.动态聚合的⼯作机制⑴参考端⼝的选举：⽤来选择聚合成员端⼝的标准端⼝；设备ID越⼩的优先，设备ID=LACP优先级+MAC地址（LACP优先级默认为32768），如果优先级相同再⽐较其系统MAC地址，MAC地址越⼩其设备ID越⼩聚合端⼝ID⼩的优先，端⼝ID=端⼝优先级+端⼝编号（端⼝优先级默认为32768）⑵确定成员端⼝状态为选中端⼝①端⼝要处于up状态②端⼝的操作key和属性类配置与参考端⼝要相同③聚合组中候选端⼝的数量没有超过上限5.静态聚合的配置⑴组⽹图⑵配置步骤①配置S1# 创建⼆层聚合接⼝1[S1] interface bridge-aggregation 1[S1-Bridge-Aggregation1] quit# 分别将端⼝GigabitEthernet1/0/1和GigabitEthernet1/0/2加⼊到聚合组1中。

目录之巴公井开创作H3C 交换机配置命令手册：2交换机端口链路类型介绍：2认证方式为Scheme时Telnet登录方式的配置2Vlan 的创建及描述2将端口配置为Trunk端口，并允许VLAN10和VLAN20通过3DHCP典型配制举例：3链路聚合典型配置3三层交换的IP路由配置：4(1)配置各接口的IP地址4(2) 配置静态路由4# 在Switch B上配置两条静态路由。

5配置举例：建立SSL Proxy服务器51. 组网需求52. 组网图53. 配置步调5# 配置接口IP地址。

5SSL服务器端战略配置：6证书属性过滤组的配置：6证书ACP战略配置：7SSL Proxy服务器战略配置：7# 配置目标HTTP服务器。

7运行SSL Proxy服务器：7# 配置ACL，用来匹配将要进行SSL代理的数据流。

7# 将路由战略应用到接口上。

8H3C 交换机配置命令手册：交换机端口链路类型介绍：1．Access类型的端口只能属于1个VLAN，一般用于连接计算机的端口；2．Trunk类型的端口可以属于多个VLAN，可以接收和发送多个VLAN的报文，一般用于交换机之间连接的端口；3．Hybrid类型的端口可以属于多个VLAN，可以接收和发送多个VLAN的报文，可以用于交换机之间连接，也可以用于连接用户的计算机。

认证方式为Scheme时Telnet登录方式的配置#telnet server enable#local-user guestservice-type telnetlevel 3password simple 123456#Vlan 的创建及描述#<SwitchA> system-view#进入配置选项命令行[SwitchA] vlan 100#创建当前VLAN[SwitchA-vlan100] description Dept1#当前VLAN的描述[SwitchA-vlan100] port GigabitEthernet 1/0/1#将当前端口加入到对就的VLAN下面将端口配置为Trunk端口，并允许VLAN10和VLAN20通过[SwitchA]interface GigabitEthernet 1/1#进入当前端口[SwitchA-GigabitEthernet1/1]port link-type trunk#将当前端口设为中继[SwitchA-GigabitEthernet1/1]port trunk permit vlan all #允许所有VLAN通过[SwitchA-vlan100] quit#退出DHCP典型配制举例：#[SwitchA] dhcp server ip-pool 0#建立DHCP组[SwitchA-dhcp-pool-0] network 10.1.1.0 mask 255.255.255.0#地址池范围[SwitchA-dhcp-pool-0] domain-name #WINS服务器地址[SwitchA-dhcp-pool-0] dns-list 10.1.1.2#DNS服务器地址[SwitchA-dhcp-pool-0]nbns-list 10.1.1.4#从DNS的配制[SwitchA] dhcp server forbidden-ip 10.1.1.2#不介入的地址分配的地址（保存地址）[SwitchA] dhcp server detect# 配置伪服务器检测功能。

H3C交换机链路聚合典型配置指导（续）7.2 链路聚合典型配置指导7.2.1 组网图7.2.2 应用要求设备 Device A 用 3 个端口聚合接入设备 Device B，从而实现出/入负荷在各成员端口中分担。

Device A 的接入端口为 Ethernet2/0/1～Ethernet2/0/3。

7.2.3 配置过程和解释说明：以下只列出对Device A 的配置，对Device B 也需要作相同的配置，才能实现链路聚合。

采用静态聚合模式# 创建二层聚合端口 1。

system-view[DeviceA] interface bridge-aggregation 1 [DeviceA-Bridge-Aggregation1] quit# 将以太网端口 Ethernet2/0/1 至 Ethernet2/0/3 加入聚合组 1。

[DeviceA] interface ethernet 2/0/1[DeviceA-Ethernet2/0/1] port link-aggregation group 1 [DeviceA-Ethernet2/0/1] interface ethernet 2/0/2 [DeviceA-Ethernet2/0/2] port link-aggregation group 1 [DeviceA-Ethernet2/0/2] interface ethernet 2/0/3 [DeviceA-Ethernet2/0/3] port link-aggregation group 1采用动态聚合模式# 创建二层聚合端口 1，并配置成动态聚合模式。

system-view[DeviceA] interface bridge-aggregation 1[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic [DeviceA-Bridge-Aggregation1] quit# 将以太网端口 Ethernet2/0/1 至 Ethernet2/0/3 加入聚合组 1。

H3C S5130-EI NTP典型配置举例Copyright © 2014 杭州华三通信技术有限公司版权所有，保留一切权利。

非经本公司书面许可，任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部，并不得以任何形式传播。

本文档中的信息可能变动，恕不另行通知。

目录1 简介 ··················································································································································· 1-12 配置前提 ············································································································································ 1-13 NTP服务器/客户端模式典型配置举例 ································································································ 3-13.1 组网需求············································································································································ 3-13.2 使用版本············································································································································ 3-13.3 配置步骤············································································································································ 3-23.3.1 Device A的配置 ······················································································································ 3-23.3.2 Device B的配置 ······················································································································ 3-23.3.3 Device C的配置 ······················································································································ 3-23.4 验证配置············································································································································ 3-23.5 配置文件············································································································································ 3-34 NTP广播模式典型配置举例 ··············································································································· 4-34.1 组网需求············································································································································ 4-34.2 使用版本············································································································································ 4-44.3 配置步骤············································································································································ 4-44.3.1 Device C的配置 ······················································································································ 4-44.3.2 Device A的配置 ······················································································································ 4-44.4 验证配置············································································································································ 4-54.5 配置文件············································································································································ 4-55 NTP组播模式典型配置举例 ··············································································································· 5-65.1 组网需求············································································································································ 5-65.2 使用版本············································································································································ 5-75.3 配置步骤············································································································································ 5-75.3.1 Device C的配置 ······················································································································ 5-75.3.2 Device D的配置 ······················································································································ 5-75.3.3 Device B的配置 ······················································································································ 5-85.3.4 Device A的配置 ······················································································································ 5-85.4 验证配置············································································································································ 5-85.5 配置文件············································································································································ 5-96 带身份验证的NTP客户端/服务器模式典型配置举例········································································· 6-106.1 组网需求·········································································································································· 6-106.2 使用版本·········································································································································· 6-106.3 配置步骤·········································································································································· 6-116.3.1 Device A的配置 ···················································································································· 6-116.3.2 Device B的配置 ···················································································································· 6-116.3.3 Device C的配置 ···················································································································· 6-116.4 验证配置·········································································································································· 6-126.5 配置文件·········································································································································· 6-127 SNTP典型配置举例 ························································································································· 7-137.1 组网需求·········································································································································· 7-137.2 使用版本·········································································································································· 7-147.3 配置步骤·········································································································································· 7-147.3.1 Device A的配置 ···················································································································· 7-147.3.2 Device B的配置 ···················································································································· 7-147.3.3 Device C的配置 ···················································································································· 7-147.4 验证配置·········································································································································· 7-157.5 配置文件·········································································································································· 7-158 IPv6 NTP服务器/客户端模式典型配置举例 ······················································································ 8-168.1 组网需求·········································································································································· 8-168.2 使用版本·········································································································································· 8-168.3 配置步骤·········································································································································· 8-168.3.1 Device A的配置 ···················································································································· 8-168.3.2 Device B的配置 ···················································································································· 8-168.3.3 Device C的配置 ···················································································································· 8-178.4 验证配置·········································································································································· 8-178.5 配置文件·········································································································································· 8-189 IPv6 NTP组播模式典型配置举例 ····································································································· 9-189.1 组网需求·········································································································································· 9-189.2 使用版本·········································································································································· 9-199.3 配置步骤·········································································································································· 9-199.3.1 Device C的配置 ···················································································································· 9-199.3.2 Device D的配置 ···················································································································· 9-199.3.3 Device B的配置 ···················································································································· 9-209.3.4 Device A的配置 ···················································································································· 9-209.4 验证配置·········································································································································· 9-209.5 配置文件·········································································································································· 9-2110 带身份验证的NTP广播模式典型配置举例 ···················································································· 10-2210.1 组网需求······································································································································ 10-2210.2 使用版本······································································································································ 10-23。

交换机设置教程图解(2010-07-13 11:01:03)标签：电脑vlandhcp服务器lease最近在单位用Linux做了一台DHCP服务器，使用H3C S7506R交换机做中继，为两个VLAN提供DHCP服务，经过两个月的测试效果很好。

在这里把服务器和交换机的设置方法写出来供有相似需求的朋友参考。

首先贴一下网络拓扑：此主题相关图片如下dhcp中继.jpg：一DHCP服务器设置步骤如下：1)安装好Linux操作系统，我用的发行版本是CentOS 5.2。

2)设置服务器的网络参数如下IP地址:192.168.6.7子网掩码:255.255.255.0网关:192.168.6.254DNS:192.168.6.103)安装DHCP服务CentOS和Red Hat Enterprise Linux等系统默认并不安装DHCP服务。

可以使用这个命令来检查系统是否已经安装DHCP服务：rpm –q dhcp如果返回提示“package dhcp is not installed”，说明没有安装DHCP服务。

把CentOS 安装DVD光盘放入光驱，执行以下命令：cd /media/CentOS_5.2_Final/CentOSrpm –ivh dhcp-3.0.5-13.el5.i386.rpm系统会显示安装进度，安装成功后再次执行“rpm –q dhcp”命令，系统会返回消息“dhcp-3.0.5-13.el5”，说明DHCP服务已正确安装。

4)把配置文件模板复制为dhcpd.confDHCP服务的配置要靠编辑/etc/dhcpd.conf来进行。

DHCP服务程序默认没有建立dhcpd.conf 配置文件，但自带配置模板，只要稍加修改就可以使用。

执行“cp /usr/share/doc/dhcp-3.0.5/dhcpd.conf.sample /etc/dhcpd.conf”命令，可以把系统自带的配置文件模板复制到/etc目录并重命名为dhcpd.conf。

H3C交换机配置链路聚合<H3C>system-view //进⼊配置模式动态链路聚合：[SW]dis cu //查看所有配置端⼝信息[SW]int Bridge-Aggregation 1 //创建链路聚合组端⼝1[SW-Bridge-Aggregation1]link-aggregation mode dynamic //链路聚合模式动态[SW-Bridge-Aggregation1]interface gigabitethernet 1/0/1 //进⼊⽹⼝[SW-Ethernet1/0/1]port link-aggregation group 1 //加⼊链路聚合组[SW-Ethernet1/0/1]quit //退出[SW]interface Ethernet（gigabitethernet） 1/0/2[SW-Ethernet1/0/2]port link-aggregation group 1 //加⼊链路聚合组[SW-Ethernet1/0/1]quit[SW-Bridge-Aggregation1]port link-type trunk //改为trunk模式[SW-Bridge-Aggregation1]port trunk permit vlan all //所有的vlan适⽤删除链路聚合：步骤1 将原来已加⼊的聚合组的端⼝退出步骤2 删除聚合组命令参考如下，（具体的端⼝号，聚合组请根据你的实际情况修改）：interface GigabitEthernet 0/8undo port link-aggregation group 1quitundo link-aggregation group 1查看命令：display link-aggregation summary[S1]display link-aggregation verbose负载分担：[S1]link-aggregation load-sharing mode destination-mac 两端都配置（貌似接⼝也可以配置）[SW]save //保存配置信息[SW]reboot //重启交换机。

【最新整理，下载后即可编辑】H3C三层交换机配置实例1 网络拓扑图 (1)2 配置要求 (1)3划分VLAN并描述 (2)3.1进入系统视图 (2)3.2 创建VLAN并描述 (2)4 给VLAN设置网关 (3)4.1 VLAN1的IP地址设置 (3)4.2 VLAN100的网关设置 (3)4.3 VLAN101的网关设置 (4)4.4 VLAN102的网关设置 (4)4.5 VLAN103的网关设置 (4)5 给VLAN指定端口，设置端口类型 (5)5.1 VLAN100指定端口 (5)5.2 VLAN102指定端口 (5)5.3 VLAN1/101/103指定端口 (6)6 配置路由协议 (7)6.1 默认路由 (7)6.2配置流分类 (7)6.3 定义行为 (7)6.4 应用QOS策略 (8)6.5 接口配置QOS策略 (8)1 网络拓扑图图1-1 网络拓扑图2 配置要求用户1网络：172.16.1.0/24 至出口1网络：172.16.100.0/24用户2网络：192.168.1.0/24 至出口2网络：192.168.100.0/24实现功能：用户1通过互联网出口1，用户2通过互联网出口2。

3划分VLAN并描述3.1进入系统视图<H3C>system-view //进入系统视图图3-1 系统视图3.2 创建VLAN并描述[H3C]vlan 1 //本交换机使用[H3C-vlan1]description Manager //描述为“Manager”[H3C-vlan1]quit[H3C]vlan 100 //划分vlan100[H3C-vlan100]description VLAN 100 //描述为“VLAN 100”[H3C-vlan100]quit[H3C]vlan 101 //划分vlan101[H3C-vlan101]description VLAN 101 //描述为“VLAN 101”[H3C-vlan101]quit[H3C]vlan 102 //划分vlan102[H3C-vlan102]description VLAN 102 //描述为“VLAN 102”[H3C-vlan102]quit[H3C]vlan 103 //划分vlan103[H3C-vlan103]description VLAN 103 //描述为“VLAN 103”[H3C-vlan103]quit[H3C]图3-2 划分VLAN及描述4 给VLAN设置网关4.1 VLAN1的IP地址设置把VLAN1的IP地址设置为192.168.0.254，子网掩码为255.255.255.0，用于本地使用。

H3C交换机链路聚合的典型配置静态链路聚合的典型配置一、组网需求：两台H3C S3500-EA A,B之间做静态链路聚合。

这里假设e1/0/1,e1/0/2,e1/0/3端口都是trunk端口，允许vlan 10,20,30通过二、配置步骤：(1)设备A上的配置#创建二层聚合端口[switch-A] interface Bridge-Aggregation 1[switch-A-Bridge-Aggregation1] port link-type trunk[switch-A-Bridge-Aggregation1] port trunk permit vlan 10 20 30#分别将设备A上端口e1/0/1,e1/0/2,e1/0/3加入到聚合组中[switch-A] interface Ethernet 1/0/1[switch-A-Ethernet1/0/1] port link-type trunk[switch-A-Ethernet1/0/1] port trunk permit vlan 10 20 30[switch-A-Ethernet1/0/1]port link-aggregation group 1[switch-A] interface Ethernet 1/0/2[switch-A-Ethernet1/0/2] port link-type trunk[switch-A-Ethernet1/0/2] port trunk permit vlan 10 20 30[switch-A-Ethernet1/0/2]port link-aggregation group 1[switch-A] interface Ethernet 1/0/3[switch-A-Ethernet1/0/3] port link-type trunk[switch-A-Ethernet1/0/3] port trunk permit vlan 10 20 30[switch-A-Ethernet1/0/3]port link-aggregation group 1(2)设备B上的配置设备B上的配置和A类似，这里从略。