搜档网
当前位置:搜档网 › H3C VDI安装配置指导

H3C VDI安装配置指导

H3C VDI安装配置指导
H3C VDI安装配置指导

目录

1概述···························································································································· 1-1

1.1 产品简介···················································································································1-1

1.2 产品组件···················································································································1-1

1.3 典型组网···················································································································1-2

1.3.1 组织架构··········································································································1-2

1.3.2 典型组网··········································································································1-2 2安装前的准备工作·········································································································· 2-1

2.1 安装前需确认的内容····································································································2-1

2.2 Broker服务器配置要求 ································································································2-1

2.3 AD服务器配置要求·····································································································2-1

2.4 CAS服务器配置要求···································································································2-2 3安装VDI云桌面管理平台 ································································································ 3-1

3.1 安装CAS ··················································································································3-1

3.2 安装AD域控服务器 ····································································································3-1

3.2.1 通过命令行启动安装域控制器和DNS配置。 ···························································3-1

3.2.2 在弹出的对话框中点击下一步。 ············································································3-2

3.2.3 在弹出的对话框中点击下一步。 ············································································3-3

3.2.4 在弹出的对话框中选中”在心林中新建域”,点击下一步。 ············································3-3

3.2.5 在弹出的对话框输入根级域名,点击下一步。 ··························································3-4

3.2.6 选中正确的林功能级别(本服务器安装的是2008 Server R2),点击下一步 . ·····················3-5

3.2.7 自动配置DNS ···································································································3-6

3.2.8 因为没有创建DNS服务器委派,弹出警告提示,单击”是”继续下一步································3-8

3.2.9 指定AD域的数据库.日志文件的存放路径································································3-9

3.2.10 设定administrator的密码,单击”下一步”······························································· 3-10

3.2.11 查看安装域控前的摘要信息,确认无误后单击下一步················································ 3-11

3.2.12 配置域控服务 ································································································ 3-11

3.2.13 安装完成后,重新启动服务器·············································································· 3-12

3.3 安装Broker服务器 ··································································································· 3-13

3.3.1 解压VDI安装包 ······························································································ 3-13

3.3.2 修改数据库配置······························································································· 3-13

3.3.3 CAS服务器数据库配置 ····················································································· 3-14

3.3.4 初始化数据并注册系统服务················································································ 3-15

3.3.5 运行VDI Broker服务························································································ 3-15

i

3.3.6 测试H3C VDI管理界面是否正常········································································· 3-17

3.4 VM安装 ················································································································· 3-18

3.4.1 创建VM ········································································································· 3-18

3.4.2 配置VM IP地址 ······························································································ 3-19

3.4.3 关闭VM防火墙······························································································· 3-20

3.4.4 开启VM的远程登录权限 ··················································································· 3-21

3.4.5 安装CAS Tools ······························································································· 3-21

3.4.6 将VM增加到AD域控。 ······························································错误!未定义书签。

3.4.7 H3Cloud Desktop vAgent安装部署 ···································································· 3-22

3.4.8 RGS Sender安装 ·······································································错误!未定义书签。

3.5 H3Cloud Desktop Client安装部署 ················································································ 3-24

3.5.1 Client安装 ····································································································· 3-24

3.5.2 RGS Receiver安装 ·····································································错误!未定义书签。

4 VDI云桌面配置 ············································································································4-27

4.1 AD域控配置············································································································ 4-27

4.1.1 添加组织········································································································ 4-27

4.1.2 添加用户········································································································ 4-27

4.2 VDI云桌面配置········································································································ 4-29

4.2.1 添加CVM资源································································································ 4-29

4.2.2 添加LDAP服务器···························································································· 4-30

4.2.3 添加OU及同步用户 ························································································· 4-30

4.2.4 添加外部存储·································································································· 4-31

4.2.5 创建虚拟机模板······························································································· 4-35

4.2.6 动态桌面池配置······························································································· 4-36

4.2.7 静态桌面池配置······························································································· 4-40 5业务测试·····················································································································5-43

5.1 使用动态桌面池账号测试···························································································· 5-43

5.2 使用静态桌面池账号测试···························································································· 5-45 6参考文档······················································································································ 6-1

ii

1 概述

1.1 产品简介

H3C VDI是我司自行研发的云桌面产品,旨在为最终用户提供虚拟云桌面。桌面虚拟化即VDI(Virtual Desktop Infrastructure)是一种基于服务器的计算模型,其利用服务器虚拟化技术,并结合传统的瘦客户端技术,将桌面组件(包括应用、操作系统和用户设置等)转移到数据中心进行集中管理,通过桌面连接协议生成独立的桌面操作系统,发送给本地终端设备,供用户在本地终端上使用。

管理员可以通过虚拟桌面管理平台将所有虚拟化的桌面在数据中心进行托管,并进行统一管理、集中控制。用户可以在使用虚拟化桌面时获得PC机类似的使用体验,可以利用终端设备、PC或者其他任何可以连接到网络的设备通过应用程序或者浏览器访问驻留在服务器端的桌面操作系统。1.2 产品组件

VDI由五个组件构成:

?H3CDClient客户端

运行在客户端,实现远程访问虚拟桌面功能,包括PC及瘦客户端两个版本,提供RDP、RGS两种登录方式。Client客户端通过和Broker进行通信获取所分配的虚拟机列表。

?H3CDvAgent服务端

安装在虚拟机内,vAgent和broker之间进行通信,将虚拟机状态通告给Broker

?Broker服务器

Broker服务器作为云桌面管理平台的核心组件,与LDAP服务器通信获取用户列表,与vAgent通信获取虚拟机列表,并提供对用户虚拟桌面的分配、授权功能,当client用户时将分配的虚拟机列表传给用户。

?AD域控服务器

提供域控服务功能,进行组织、用户的创建、管理、验证功能,以及虚拟机的域管理。

CAS虚拟化平台

我司的云计算管理平台,提供服务器虚拟化的基础功能

1-1

1.3 典型组网

1.3.1 组织架构

1.3.2 典型组网

1-2

2 安装前的准备工作

在安装VDI之前,请确认安装包的完整性、版本是否配套,以及服务器的硬件配置是否满足安装要求。

2.1 安装前需确认的内容

在安装VDI之前,请准备好安装所需的所有程序及安装包,并保证所有安装包之间的版本配套。

表2-1安装前需确认的内容

2.2 Broker服务器配置要求

Broker服务器的硬件配置要求

表2-2Broker服务器硬件配置要求

2.3 AD服务器配置要求

AD服务器的硬件配置要求

2-1

表2-3AD服务器硬件配置要求

2.4 CAS服务器配置要求

CAS服务器的硬件配置要求物理资源大于运行在其上的所有虚拟机资源的总和。具体的硬件配置要表2-4CAS服务器硬件配置要求

2-2

3 安装VDI云桌面管理平台

3.1 安装CAS

CAS是我司的虚拟化管理平台,包括CVK、CVM、CIC三个组件,VDI用到了其中CVK、CVM两个组件。目前VDI只支持一个CVM,一个CVM可以管理多个CVK。当环境中存在多台主机时,只需其中一台安装CVM即可,其他主机CVM组件可选。有关CAS的安装配置,请参考《H3C CAS云计算安装指导文档-V1.0》

H3C

CAS安装指导.docx

3.2 安装AD域控服务器

VDI云桌面的VM必须加入AD域控,VDI的接入用户也必须从AD通过LDAP协议进行同步及校验。故AD在VDI云桌面解决方案中是必不可少的角色。AD域控的安装步骤,如下以Windows Server 2008为例:3.2.1 通过命令行启动安装域控制器和DNS配置。

3-1

3.2.2 在弹出的对话框中点击下一步。

3-2

3.2.3 在弹出的对话框中点击下一步。

3.2.4 在弹出的对话框中选中”在心林中新建域”,点击下一步。

3-3

3.2.5 在弹出的对话框输入根级域名,点击下一步。

3-4

3.2.6 选中正确的林功能级别(本服务器安装的是2008 Server R2),点击下一步 .

3-5

3.2.7 自动配置DNS

3-6

3-7

3.2.8 因为没有创建DNS服务器委派,弹出警告提示,单击”是”继续下一步

3-8

3.2.9 指定AD域的数据库.日志文件的存放路径

3-9

3.2.10 设定administrator的密码,单击”下一步”

3-10

3.2.11 查看安装域控前的摘要信息,确认无误后单击下一步

3.2.12 配置域控服务

3-11

3.2.13 安装完成后,重新启动服务器

3-12

3.3 安装Broker服务器

Broker服务器建议安装Windows Server 2008上,Windows Server 2008可以安装在虚拟机上,也可以安装在物理服务器上。

3.3.1 解压VDI安装包

拷贝H3CDServer文件夹至指定目录(不支持中文目录,不包含空格),如C:\H3CDServer,后续使用INSTALL_PATH代替描述。

3.3.2 修改数据库配置

将%INSTALL_PATH%/mysql/my.ini中红色标注部分(C:/H3CDServer)修改为INSTALL_PATH。

3-13

注意:目标部署环境不能安装MySQL,并且在如下目录中也不能存在MySQL的遗留配置文件(C:\Windows\my.ini C:\Windows\https://www.sodocs.net/doc/08658983.html,f C:\my.ini C:\https://www.sodocs.net/doc/08658983.html,f)。

3.3.3 CAS服务器数据库配置

解除本地地址访问的绑定;user表中增加主机名为‘%’的root用户记录。

使用“SSH Secure Shell Client”连接至CAS服务器,按照如下步骤操作:

(注意:数据库安装在CVM上,而不是CVK上,所以SSH要登陆到安装CVM的CAS,这点需要注意)

3-14

H3C交换机DHCP服务器接口地址池典型配置指导

1.2 DHCP服务器接口地址池典型配置指导 1.2.1 组网图 图1-2 DHCP服务器接口地址池配置举例 1.2.2 应用要求 ●Switch A作为DHCP服务器,其VLAN接口1的IP地址为192.168.0.1/24; ●客户端属于VLAN1,通过DHCP方式动态获取IP地址; ●DHCP服务器通过接口地址池为MAC地址为000D-88F7-0001的客户文件服务器分配固定的IP地址192.168.0.10/24,为其它客户端主机分配192.168.0.0/24网段的IP地址,有效期限为10天。DNS服务器地址为192.168.0.20/24,WINS服务器地址为192.168.0.30/24。 1.2.3 适用产品、版本 表1-2 配置适用的产品与软硬件版本关系 1.2.4 配置过程和解释 # 使能DHCP服务 system-view [SwitchA] dhcp enable # 配置不参与自动分配的IP地址(DNS服务器、WINS服务器、文件服务器) [SwitchA] dhcp server forbidden-ip 192.168.0.10 [SwitchA] dhcp server forbidden-ip 192.168.0.20 [SwitchA] dhcp server forbidden-ip 192.168.0.30 # 配置VLAN接口1的IP地址为192.168.0.1/24 [SwitchA] interface Vlan-interface 1

[SwitchA-Vlan-interface1] ip address 192.168.0.1 24 # 配置VLAN接口1工作在DHCP接口地址池模式 [SwitchA-Vlan-interface1] dhcp select interface # 配置DHCP接口地址池中的静态绑定地址 [SwitchA-Vlan-interface1] dhcp server static-bind ip-address 192.168.0.10 mac-address 000D-88F7-0001 # 配置DHCP接口地址池的地址池范围、DNS服务器地址、WINS服务器地址 [SwitchA-Vlan-interface1] dhcp server expired day 10 [SwitchA-Vlan-interface1] dhcp server dns-list 192.168.0.20 [SwitchA-Vlan-interface1] dhcp server nbns-list 192.168.0.30 [SwitchA-Vlan-interface1] quit 1.2.5 完整配置 # interface Vlan-interface1 ip address 192.168.0.1 255.255.255.0 dhcp select interface dhcp server static-bind ip-address 192.168.1.10 mac-address 000d-88f7-0001 dhcp server dns-list 192.168.0.20 dhcp server nbns-list 192.168.0.30 dhcp server expired day 10 # dhcp server forbidden-ip 192.168.0.10 dhcp server forbidden-ip 192.168.0.20 dhcp server forbidden-ip 192.168.0.30 # 1.2.6 配置注意事项 当DHCP服务器采用接口地址池模式分配地址时,在接口地址池中的地址分配完之后,将会从包含该接口地址池网段的全局地址池中挑选IP地址分配给客户端,从而导致获取到全局地址池地址的客户端与获取到接口地址池地址的客户端处在不同网段,无法正常进行通信。 故在本例中,建议从VLAN接口1申请IP地址的客户端数目不要超过250个。

telnet 远程登录交换机典型配置指导

telnet 远程登录交换机典型配置指导 system-view System View: return to User View with Ctrl+Z. [H3C]user-interface vty 0 [H3C-ui-vty0]authentication-mode password [H3C-ui-vty0]set authentication password simple 123456 [H3C-ui-vty0]local-user guest New local user added.

[H3C-luser-guest]password simple 123456 [H3C-luser-guest]service-type telnet level 3 [H3C-luser-guest]quit [H3C]user-interface vty 0 [H3C-ui-vty0]authentication-mode scheme [H3C-ui-vty0]quit [H3C]save The configuration will be written to the device. Are you sure?[Y/N]y

Please input the file name(*.cfg)(To leave the existing filename unchanged press the enter key): Now saving current configuration to the device. Saving configuration. Please wait... ... Unit1 save configuration flash:/20111025.cfg successfully [H3C] %Apr 3 17:39:34:984 2000 H3C CFM/3/CFM_LOG:- 1 -Unit1 saved

华为链路聚合典型配置指导

链路聚合典型配置指导(版本切换前) 链路聚合是将多个物理以太网端口聚合在一起形成一个逻辑上的聚合组,使用链路聚合服务 的上层实体把同一聚合组内的多条物理链路视为一条逻辑链路。 链路聚合可以实现出/入负荷在聚合组中各个成员端口之间分担,以增加带宽。同时,同一 聚合组的各个成员端口之间彼此动态备份,提高了连接可靠性。 组网图 链路聚合配置示例图 应用要求 设备Switch A用3个端口聚合接入设备Switch B,从而实现出/入负荷在各成 员端口中分担。 Switch A 的接入端口为GigabitEthernet1/0/1 ?GigabitEthernet1/0/3 。 适用产品、版本 配置过程和解释 说明: 以下只列出对Switch A的配置,对Switch B也需要作相同的配置,才能实现链路聚合。 配置聚合组,实现端口的负载分担(下面两种方式任选其一) 采用手工聚合方式 #创建手工聚合组1。 system-view [SwitchA] link-aggregation group 1 mode manual | # 将以太网端口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 采用静态LACP聚合方式 #创建静态LACP聚合组1。 system-view [SwitchA] link-aggregation group 1 mode static #将以太网端口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 完整配置 采用手工聚合方式: # link-aggregation group 1 mode manual # interface GigabitEthernet1/0/1 port link-aggregation group 1 # interface GigabitEthernet1/0/2 port link-aggregation group 1 # interface GigabitEthernet1/0/3 | port link-aggregation group 1 # 采用静态LACP聚合方式: # link-aggregation group 1 mode static interface GigabitEthernet1/0/1 port link-aggregation group 1 # interface GigabitEthernet1/0/2 port link-aggregation group 1 # interface GigabitEthernet1/0/3 port link-aggregation group 1 # 配置注意事项 不同平台软件对静态聚合方式的实现不同,所以不同平台软件的产品采用静态 聚合方式对接时,容易产生问题。有关平台软件的版本信息可以通过 display version 命令查看。

H3C交换机IRF典型配置指导

目录 1 IRF典型配置举例 ······························································································································· 1-1 1.1 简介 ··················································································································································· 1-1 1.2 使用限制············································································································································ 1-1 1.2.1 硬件限制 ································································································································· 1-1 1.2.2 软件限制 ································································································································· 1-1 1.2.3 单板使用限制 ·························································································································· 1-1 1.2.4 IRF端口连接限制 ···················································································································· 1-1 1.3 选择MAD检测方式····························································································································· 1-2 1.4 使用四台设备搭建IRF典型配置举例(LACP MAD检测方式) ························································· 1-2 1.4.1 适用产品和版本 ······················································································································ 1-2 1.4.2 组网需求 ································································································································· 1-2 1.4.3 搭建IRF的配置························································································································ 1-3 1.4.4 LACP MAD配置 ······················································································································ 1-8 1.4.5 业务配置 ······························································································································· 1-10 1.4.6 验证配置 ······························································································································· 1-14 1.4.7 配置文件 ······························································································································· 1-16 1.5 使用四台设备搭建IRF典型配置举例(BFD MAD检测方式)·························································· 1-21 1.5.1 适用产品和版本 ···················································································································· 1-21 1.5.2 组网需求 ······························································································································· 1-21 1.5.3 搭建IRF的配置······················································································································ 1-22 1.5.4 BFD MAD配置 ······················································································································ 1-26 1.5.5 业务配置 ······························································································································· 1-28 1.5.6 验证配置 ······························································································································· 1-33 1.5.7 配置文件 ······························································································································· 1-35

EPON灵活QINQ典型配置指导手册V1.0

EPON灵活QINQ典型配置指导手册 编号: 版本:V1.0 编制:技术中心热线部 审核:熊志军 批准: 瑞斯康达科技发展股份有限公司

文档修订记录 文档说明: 本文档主要用于指导工程师完成EPON灵活QINQ典型配置,本文以某商用网络为例,介绍了新在EPON系统上具体的配置操作步骤和注意事项。

前言 读者对象: 本文档适合ISCOM5000系列EPON设备灵活QinQ操作维护管理人员使用,主要面向各区域工程师。本文档介绍ISCOM5000系列EPON设备根据灵活QinQ的配置、常用故障排查方法、FAQ 等内容。 编写时间:2010年3月 相关参考手册: ISCOM 5000 EPON设备主要手册及用途如下

目录 前言 (3) 一、Q-IN-Q概述 (6) 二、技术介绍 (6) 2.1 QinQ报文格式 (6) 2.2 QinQ封装 (7) 2.2.1 基于端口的QinQ封装 (7) 2.2.2 基于流的QinQ封装 (7) 三、典型案例配置 (8) 3.1 EPON交换端口VLAN配置 (8) 3.2 根据以太网报文类型灵活Q-IN-Q 应用拓扑 (10) 3.3三种数据的业务流向及处理过程 (12) 3.4配置流程 (13) 3.5 具体数据配置流程: (14) 1) 创建加载板卡 (14) 2) 在olt上配置数据业务,创建vlan ,修改TPID值 (14) 3)配置3槽位PON板第一个PON口 (14) 4)配置上联GE口(PORT 11) (15) 5)配置上联GE口(PORT 12) (15) 6)配置网管地址及网关 (15) 7)EPON 以太网报文类型灵活Q-IN-Q配置实例 (15) 8)灵活Q-IN-Q抓包样本 (15) 四、常见故障处理FAQ (16) EPON以太网报文类型灵活Q-IN-Q常见FAQ (16) Q1:在配置根据以太网报文的灵活Q-IN-Q时,若两种数据存在一样的以太网报文类 型,该怎么区分? (16) Q2:为什么从OLT上无法PING通EOC及交换机的网管地址,而经过USR或者BRAS 的网管服务器可以PING通EOC、交换机及OLT。 (16) Q3:为什么同一台电脑在测试过一个业务后,马上测试另外一种业务,该电脑会存在

高级IPv4 ACL典型配置指导

1.1 高级IPv4 ACL典型配置指导 高级IPv4 ACL可以使用报文的源IP地址信息、目的IP地址信息、IP承载的 协议类型、协议的特性(例如TCP或UDP的源端口、目的端口,ICMP协议 的消息类型、消息码等)等信息来制定匹配规则。 高级IPv4 ACL支持对三种报文优先级的分析处理: ●ToS(Type of Service,服务类型)优先级 ●IP优先级 ●DSCP(Differentiated Services CodePoint,差分服务编码点)优先级 用户可以利用高级IPv4 ACL定义比基本IPv4 ACL更准确、更丰富、更灵活的 匹配规则。 高级IPv4 ACL的序号取值范围为3000~3999。 1.1.1 组网图 总裁办公室 192.168.1.0/24 研发部门 192.168.2.0/24192.168.3.0/24 图1-1配置高级IPv4 ACL组网图 1.1.2 应用要求 公司企业网通过交换机(以S5500-EI为例)实现各部门之间的互连。要求配 置高级IPv4 ACL,禁止研发部门和市场部门在上班时间(8:00至18:00)访问 工资查询服务器(IP地址为192.168.4.1),而总裁办公室不受限制,可以随 时访问。

1.1.3 适用产品、版本 表1-1配置适用的产品与软硬件版本关系 1.1.4 配置过程和解释 (1) 定义工作时间段 # 定义8:00至18:00的周期时间段。 system-view [Switch] time-range trname 8:00 to 18:00 working-day (2) 定义到工资查询服务器的访问规则 # 定义研发部门到工资查询服务器的访问规则。 [Switch] acl number 3000 [Switch-acl-adv-3000] rule deny ip source 192.168.2.0 0.0.0.255 destination 192.168.4.1 0 time-range trname [Switch-acl-adv-3000] quit # 定义市场部门到工资查询服务器的访问规则。 [Switch] acl number 3001 [Switch-acl-adv-3001] rule deny ip source 192.168.3.0 0.0.0.255 destination 192.168.4.1 0 time-range trname [Switch-acl-adv-3001] quit (3) 应用访问规则 # 定义类classifier_rd,对匹配高级IPv4 ACL 3000的报文进行分类。 [Switch] traffic classifier classifier_rd [Switch-classifier-classifier_rd] if-match acl 3000 [Switch-classifier-classifier_rd] quit # 定义流行为behavior_rd,动作为拒绝报文通过。 [Switch] traffic behavior behavior_rd [Switch-behavior-behavior_rd] filter deny [Switch-behavior-behavior_rd] quit # 定义类classifier_market,对匹配高级IPv4 ACL 3001的报文进行分类。 [Switch] traffic classifier classifier_market [Switch-classifier-classifier_market] if-match acl 3001 [Switch-classifier-classifier_market] quit # 定义流行为behavior_market,动作为拒绝报文通过。 [Switch] traffic behavior behavior_market [Switch-behavior-behavior_market] filter deny [Switch-behavior-behavior_market] quit

华为链路聚合典型配置指导(终审稿)

华为链路聚合典型配置 指导 文稿归稿存档编号:[KKUY-KKIO69-OTM243-OLUI129-G00I-FDQS58-

链路聚合典型配置指导(版本切换前) 链路聚合是将多个物理以太网端口聚合在一起形成一个逻辑上 的聚合组,使用链路聚合服务的上层实体把同一聚合组内的多 条物理链路视为一条逻辑链路。 链路聚合可以实现出/入负荷在聚合组中各个成员端口之间分 担,以增加带宽。同时,同一聚合组的各个成员端口之间彼此 动态备份,提高了连接可靠性。 组网图 链路聚合配置示例图 应用要求 设备Switch A用3个端口聚合接入设备Switch B,从而实现出/入负荷在各成员端口中分担。 Switch A的接入端口为GigabitEthernet1/0/1~ GigabitEthernet1/0/3。 适用产品、版本 配置适用的产品与软硬件版本关系

配置过程和解释 说明: 以下只列出对Switch A的配置,对Switch B也需要作相同的配置,才能实现链路聚合。 配置聚合组,实现端口的负载分担(下面两种方式任选其一) 采用手工聚合方式 # 创建手工聚合组1。 system-view [SwitchA] link-aggregation group 1 mode manual # 将以太网端口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 采用静态LACP聚合方式 # 创建静态LACP聚合组1。 system-view [SwitchA] link-aggregation group 1 mode static # 将以太网端口GigabitEthernet1/0/1至 GigabitEthernet1/0/3加入聚合组1。 [SwitchA] interface GigabitEthernet 1/0/1

华为链路聚合典型配置指导

链路聚合典型配置指导(版本切换前) 链路聚合是将多个物理以太网端口聚合在一起形成一个逻辑上的聚合组,使用 链路聚合服务的上层实体把同一聚合组内的多条物理链路视为一条逻辑链路。 链路聚合可以实现出/入负荷在聚合组中各个成员端口之间分担,以增加带宽。 同时,同一聚合组的各个成员端口之间彼此动态备份,提高了连接可靠性。组网图 链路聚合配置示例图 应用要求 设备Switch A用3个端口聚合接入设备Switch B,从而实现出/入负荷在各成员端口中分担。 Switch A的接入端口为GigabitEthernet1/0/1~GigabitEthernet1/0/3。 适用产品、版本 配置适用的产品与软硬件版本关系 配置过程和解释 说明: 以下只列出对Switch A的配置,对Switch B也需要作相同的配置,才能实现链路聚合。 配置聚合组,实现端口的负载分担(下面两种方式任选其一) 采用手工聚合方式 # 创建手工聚合组1。 system-view [SwitchA] link-aggregation group 1 mode manual # 将以太网端口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 采用静态LACP聚合方式 # 创建静态LACP聚合组1。 system-view [SwitchA] link-aggregation group 1 mode static # 将以太网端口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 完整配置 采用手工聚合方式: # link-aggregation group 1 mode manual # interface GigabitEthernet1/0/1 port link-aggregation group 1 # interface GigabitEthernet1/0/2 port link-aggregation group 1 # interface GigabitEthernet1/0/3 port link-aggregation group 1 # 采用静态LACP聚合方式: # link-aggregation group 1 mode static interface GigabitEthernet1/0/1 port link-aggregation group 1 # interface GigabitEthernet1/0/2 port link-aggregation group 1 # interface GigabitEthernet1/0/3 port link-aggregation group 1 # 配置注意事项 不同平台软件对静态聚合方式的实现不同,所以不同平台软件的产品采用静态聚合方式对接时,容易产生问题。有关平台软件的版本信息可以通过 display version命令查看。 配置了RRPP的端口、配置了静态MAC地址或者黑洞MAC地址的端口、使能Voice VLAN的端口以及使能802.1x的端口不能加入聚合组。 链路聚合典型配置指导(版本切换后) 组网图 链路聚合配置示例图

Cluster典型配置指导

目录 第1章Cluster典型配置指导................................................................................................... 1-1 1.1 Cluster典型配置指导 ....................................................................................................... 1-1 1.1.1 组网图.................................................................................................................... 1-1 1.1.2 应用要求 ................................................................................................................ 1-1 1.1.3 适用产品、版本..................................................................................................... 1-2 1.1.4 配置过程和解释..................................................................................................... 1-2 1.1.5 完整配置 ................................................................................................................ 1-5 1.1.6 配置注意事项......................................................................................................... 1-5 1.2 Cluster实际组网配置指导................................................................................................ 1-6 1.2.1 组网图.................................................................................................................... 1-6 1.2.2 应用要求 ................................................................................................................ 1-6 1.2.3 适用产品、版本..................................................................................................... 1-7 1.2.4 配置过程和解释..................................................................................................... 1-7 1.2.5 完整配置 .............................................................................................................. 1-10

H3C交换机最详细配置实例手册

H3C交换机最详细配置实例手册 目录 1.登录交换机典型配置指导 (7) 1.1 通过Console口配置Telnet登录方式典型配置指导 (7) 1.1.1 组网图 (7) 1.1.2 应用要求 (7) 1.1.3 配置过程和解释 (7) 1.1.4 完整配置 (8) 1.2 通过Telnet配置Console口登录方式典型配置指导 (9) 1.2.1 组网图 (9) 1.2.2 应用要求 (9) 1.2.3 配置过程和解释 (9) 1.2.4 完整配置 (10) 1.3 通过WEB网管登录交换机典型配置指导 (11) 1.3.1 组网图 (11) 1.3.2 应用要求 (11) 1.3.4 配置过程和解释 (11) 1.3.5 完整配置 (12) 1.3.6 配置注意事项 (12) 1.4 对登录用户的控制典型配置指导 (12) 1.4.1 组网图 (12) 1.4.2 应用要求 (12) 1.4.3 配置过程和解释 (12) 1.4.4 完整配置 (13) 2. VLAN典型配置指导 (14) 2.1 基于端口的VLAN典型配置指导 (14) 2.1.1 组网图 (14) 2.1.2 应用要求 (14) 2.1.3 配置过程和解释 (14) 2.1.4完整配置 (15) 2.2 基于MAC的VLAN典型配置指导 (16) 2.2.1组网图 (16) 2.2.2 应用要求 (16) 2.2.3 配置过程和解释 (16) 2.2.4 完整配置 (17)

2.2.5 配置注意事项 (18) 2.3 基于协议的VLAN典型配置指导 (18) 2.3.1 组网图 (18) 2.3.2 应用要求 (19) 2.3.3 配置过程和解释 (19) 2.3.4 完整配置 (19) 2.4 基于IP子网的VLAN典型配置指导 (20) 2.4.1 组网图 (20) 2.4.2 应用要求 (20) 2.4.3 配置过程和解释 (21) 2.4.5 完整配置 (21) 2.5 Isolate-user-vlan典型配置指导 (22) 2.5.1 组网图 (22) 2.5.2 应用要求 (22) 2.5.3 配置过程和解释 (22) 2.5.6 完整配置 (23) 3. IPv4 ACL典型配置指导 (25) 3.1 基本IPv4 ACL典型配置指导 (25) 3.1.1 组网图 (25) 3.1.2 应用要求 (25) 3.1.3 配置过程和解释 (25) 3.1.4 完整配置 (26) 3.1.5 配置注意事项 (26) 3.2 高级IPv4 ACL典型配置指导 (27) 3.2.1 组网图 (28) 3.2.2 应用要求 (28) 3.2.3 配置过程和解释 (28) 3.2.4 完整配置 (29) 3.2.5 配置注意事项 (30) 3.3 二层ACL典型配置指导 (30) 3.3.1 组网图 (31) 3.3.2 应用要求 (31) 3.3.3 配置过程和解释 (31) 3.3.4 完整配置 (31) 3.3.5 配置注意事项 (32) 3.4 用户自定义ACL和流模板典型配置指导 (32) 3.4.1组网图 (33) 3.4.2 应用要求 (33) 3.4.3 配置过程和解释 (33) 3.4.4 完整配置 (34)

ASG典型配置指导

SSL远程登陆配置指导 一、网络配置(提示勾选默认路由) 在网络配置中,选择相应的网口,此例以单臂部署方式为例。勾选的缺省路由为设备的默认路由。 二、用户组 在远程访问---用户组与用户管理中,添加用户组。此用户组为所有应用控制策略的对象,既应用控制策略以组的方式划分。

三、组高级配置---网络资源配置 1、地址池 在地址池中配置用户远程访问到VPN后,被分配的内网地址。 启用地址伪装后,所有用户访问VPN的源地址被伪装成单臂的内网口地址; 不启用地址伪装,将使用地址池分配的地址(分配的地址不可与内网其他地址重复,需再内网内可路由)。 2、静态路由 静态路由,为组自己的路由,优先级高于设备默认路由。如果未配置此项,数据包将走设备默认的路由。故勾选默认路由和组路由必须至少填写一项。

3、h ttp服务菜单 http服务菜单为组内的资源。 其与用户登录后的组内资源页面相对应。

分为反向代理和插件两种。 反向代理是纯web应用的即B/S架构应用,访问时会改写URL,可以在不登陆插件下使用; 插件支持所有C/S架构应用,其中包括:https、本身带插件的应用如CRM和U8、客户端模式的如notes等,不会改写URL,但必须登陆插件才可使用。 四、应用程序库配置 在远程访问应用程序库配置中,添加调用项,本例以增加策略网段为例。

其中执行文件名称是用户端执行文件是否可访问VPN的限制,*表示所有应用。 目的地址为策略网段,其他默认即可。 五、组高级配置---策略配置 1、Web插件应用程序策略 组web插件应用程序策略,为使用web插件时所遵循的应用程序控制策略。它分成默认策略和例外策略。例外策略将调用上文所设置的应用程序库配置项。

H3C SecBlade LB典型配置指导V1[1].00

SecBlade LB 典型配置指导 关键词:LB 摘 要:本文主要描述了SecBlade LB 在各种应用场景中的典型配置 缩略语: 缩略语 英文全名 中文解释 LB Load Balancing 负载均衡 SLB Server Load Balance 服务器负载均衡 NAT Network Address Translation 网络地址转换 DNAT Destination NAT 目的地址NAT VSIP Virtual Service IP Address 虚服务IP 地址 U n R e g i s t e r e d

目 录 1 产品简介..................................................................................................................................4 2 应用场合. (5) 2.1 企业园区网中的中小型数据中心应用............................................................................5 2.2 电信运营商和门户网站的大型数据中心应用.................................................................6 3 注意事项..................................................................................................................................8 4 NAT 负载均衡组网配置举例 (8) 4.1 组网需求........................................................................................................................8 4.2 配置思路 (8) 4.3 使用版本........................................................................................................................9 4.4 配置步骤 (9) 4.4.1 S7503E 的配置....................................................................................................9 4.4.2 SecBlade LB 的配置..........................................................................................12 5 DR 负载均衡组网配置举例.. (19) 5.1 组网需求......................................................................................................................19 5.2 配置思路. (19) 5.3 使用版本......................................................................................................................19 5.4 配置步骤. (20) 5.4.1 S7503E 的配置 (20) 5.4.2 SecBlade LB 的配置..........................................................................................22 5.4.3 服务器网卡的配置.............................................................................................27 6 SecBlade LB 支持冗余备份方案配置举例 (34) 6.1 组网需求......................................................................................................................34 6.2 配置思路......................................................................................................................35 6.3 使用版本......................................................................................................................36 6.4 配置步骤. (36) 6.4.1 S7503E 的配置..................................................................................................36 6.4.2 SecBlade LB_1的配置......................................................................................40 6.4.3 SecBlade LB_2的配置......................................................................................41 6.4.4 LB 的主要配置截图.. (43) 7 相关资料 (44) 7.1 相关协议和标准 (44) U n R e g i s t e r e d

相关主题