Dell OpenFlow deployment and user guid(SDN) version 3.0
- 格式:pdf
- 大小:1001.23 KB
- 文档页数:50
Dell OpenManage Deployment Toolkit Installation GuideNotes and CautionsNOTE: A NOTE indicates important information that helps you make better use of your computer.____________________Information in this publication is subject to change without notice.© 2012 Dell Inc. All rights reserved.Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.Trademarks used in this text: Dell™ and OpenManage™, are trademarks of Dell Inc. Red Hat Enterprise Linux® and Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. SUSE ™ is a trademark of Novell Inc. in the United States and other countries. Microsoft®, Windows®, Windows Vista® and Windows® 7 are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux®is a registered trademark of Linus Torvalds.Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.2012 – 02IntroductionThe Dell OpenManage Deployment Toolkit (DTK) includes a set of utilities, sample scripts, and sample configuration files that you need, to deploy and configure your Dell system. Y ou can use DTK to build script-based and RPM-based installation for deploying large number of systems on apre-operating system environment in a reliable way, without changing their current deployment processes.Documents You Will Need•Dell OpenManage Deployment T oolkit Command Line Interface Reference Guide•Dell OpenManage Deployment T oolkit User’s Guide•Operating system documentationFor a complete list of supported operating systems, BIOS firmware, and hardware, see the Dell Systems Software Support Matrix available at /manuals→Software→Systems Management→Dell OpenManage Releases. Click the appropriate product version to access the Support Matrix.PrerequisitesBefore using DTK to deploy Microsoft Windows Pre-installation Environment (PE) or embedded Linux environment (Red Hat Enterprise Linux or SUSE Linux Enterprise Server), ensure you have the following prerequisites:Table 1-1.Prerequisites for InstallationWindows PE Environment Embedded Linux EnvironmentThe DTK self-extracting zip file (DTKX.X-WINPE-XX.exe) available at .The DTK ISO image available at .A Windows workstation that has at least 512 MB of RAM.A workstation that has at least 512 MB of RAM.Quick Installation Guide3Deployment OverviewDTK offers a complete set of utilities, sample scripts, and RPM packages that can be used to automate the deployment of Dell systems.Before running the deployment, ensure that you create specific deployment media to facilitate the deployment method you choose. For more information, see the Dell OpenManage Deployment T oolkit User’s Guide available on /manuals→Software→Systems Management→Dell OpenManage Deployment Toolkit.Deployment PrerequisitesBefore beginning the deployment process for Windows PE, ensure that you have all of the following tools, software, and information ready to use or consult:•Windows Automated Installation Kit (AIK) 1.1 released with Microsoft Windows Vista SP1 and Windows Server 2008 to build Windows PE 2.0.•Windows AIK for Windows 7 to build Windows PE 3.0.•An unzip utility.•Working knowledge to build Windows PE 2.0 and Windows PE 3.0 (See the Microsoft documentation to customize Windows PE).•Working knowledge of Microsoft Remote Installation Services (RIS) and Automated Deployment Services (ADS) (including setting up of RIS and ADS environments) or any other third party deployment system or tool for Windows PE.•Working knowledge of Windows Deployment Services (WDS) or any other third party deployment system or tool for Windows PE.• A workstation with the following capabilities:–Writable media drive–Network access• A target system with a media drive, if performing a local deployment.• A target system with a media drive and network access, if performing a network deployment.•All DTK utilities, sample scripts, and sample configuration files.•Dell Systems Management Tools and Documentation DVD.4Quick Installation GuideQuick Installation Guide 5•Y our operating system software and documentation.•An optimally configured source system with network access. NOTE: You can also download the latest drivers from .For embedded Linux, ensure that you have all of the following tools, software, and information ready to use or consult:•Advanced knowledge of Linux and Linux scripting (bash), Linux networking, installing and working with RPM Package Managers (RPMs), and creating and modifying loop file systems.•Any third party deployment system or tool.• A workstation with the following capabilities:–A writable media drive –Network access •A target system with a media drive, if performing a local deployment.•A target system with a media drive and network access, if performing a network deployment.•All DTK utilities, sample scripts, sample configuration files, and RPM packages.•All operating system RPM packages that DTK RPMs require.NOTE: Tools such as Yellowdog Updater Modified (YUM), Yet Another Setup Tool (YAST), and Advanced Packaging Tool (APT) can be used to manage RPM dependency issues.•All other utilities and files necessary to perform the deployment, including all required Linux drivers, operating system drivers, and the Dell utility partition file.•Dell Systems Management Tools and Documentation DVD.•Y our operating system software and documentation.•An optimally configured source system with network access.NOTE: You can download the latest drivers from .6Quick Installation GuidePreparing for DeploymentIf you are using the Windows PE environment:1Copy or extract DTK utilities, sample scripts, sample configuration files, and drivers provided (in the zip file) to the Windows PE image.2Organize DTK utilities, script files, configuration files, the operating system installation files, and the requisite system files and drivers on a network share or local media.3Set up a Source System by using the Dell Systems Build and Update Utility (to install your operating system) and the Systems Service and Diagnostics Tools (to load drivers). The Source System acts as a masterserver that is used to replicate settings to the T argetServers .NOTE: You can also download the latest drivers from the Dell Support website at .4Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the Source System . Copy the generated configuration files to a read/write share on the workstation or server.NOTE: You can obtain the system BIOS, BMC, RAID, and/or RAC configuration files by booting from DTK Windows PE image and running the SYSCAP .BAT , RAIDCAP .BAT , and RACCAP .BAT scripts. 5Create an operating system answer file that contains unattended operating system software installation information.6Edit DTK sample script files that access the system configuration files to set up the system BIOS, BMC, RAID, and RAC and then, install an operating system on a Target Server .If you are using the embedded Linux environment:1Obtain the DTK Linux ISO image, which is a self-contained bootable ISO image.2Use and customize the sample scripts as per your requirements.3Set up a Source System by using the Systems Build and Update Utility on the Dell Systems Management T ools and Documentation DVD (to install your operating system) and the Systems Service and Diagnostics Tools (to load drivers).NOTE: You can also download the latest drivers from the Dell Support website at .4Generate a system BIOS, BMC, RAID, and/or RAC configuration profile from the optimally configured source system. Copy the generatedconfiguration files to a read/write share onto the workstation or server.NOTE: You can obtain the system BIOS, BMC, RAID, and/or RAC configurationfiles by booting from DTK Linux ISO image and running the syscap.sh,raidcap.sh, and raccap.sh scripts.5Create an operating system answer file that contains unattended operating system software installation information.6Install an operating system on a T arget Server.DeployingTo proceed with deployment, ensure that you have prepared all scripts, files, and utilities. Y ou can deploy the Win PE and embedded Linux using one of the following methods:•Deploy using removable boot media with a network connection (media-based)•Deploy using removable boot media without a network connection (media-based)•Network-based deployment (remote)For information on these methods, see the Dell OpenManage DeploymentT oolkit User’s Guide available on /manuals→Software→Systems Management→Dell OpenManage Deployment Toolkit.Upgrading Your DTK VersionWhen upgrading from a previous release of DTK, ensure that you create the environment for new DTK version separately from the previous version. This step is necessary because the environments and requirements for the new DTK versions are completely different.Quick Installation Guide78Quick Installation Guide。
Dell OpenManage IT Assistant 版本 8.8 用户指南注和小心本出版物中的信息如有更改,恕不另行通知。
© 2010 Dell Inc. 版权所有,翻印必究。
未经 Dell Inc. 书面许可,严禁以任何形式复制这些材料。
本文中使用的商标:Dell ™、DELL 徽标、Dell Precision ™、OpenManage ™、OptiPlex ™、PowerEdge ™、PowerVault ™、PowerConnect ™、EqualLogic ™、KACE ™、FlexAddress ™ 和 Vostro ™ 是 Dell Inc. 的商标。
Intel ®、Pentium ®、Xeon ®、Core ® 和 Celeron ® 是 Intel Corporation 在美国 和其它国家/地区的商标或注册商标。
AMD ® 是注册商标并且 AMD Opteron ®、AMD Phenom ® 和 AMD Sempronyx 是 Advanced Micro Devices, Inc. 的商标。
VMware ®、Virtual SMP ®、vMotion ®、vCenter ®、vSphere ® 和 ESX ® Serveryx 是 VMware, Inc. 在美国和/或其他管辖区的注册商标或商标。
Microsoft ®、Windows ®、Windows NT ®、Windows Server ®、Microsoft Hyper-V Server 2008®、Windows Vista ®、Active Directory ®、Internet Explorer ®、SQL Server ® 和 Excel ® 是 Microsoft Corporation 在美国和/或其他国家/地区的商标或注册商标。
Dell EMC OpenManage Enterprise 用户指南Version 3.82021 10注意、小心和警告:“注意”表示帮助您更好地使用该产品的重要信息。
:“小心”表示可能会损坏硬件或导致数据丢失,并告诉您如何避免此类问题。
:“警告”表示可能会导致财产损失、人身伤害甚至死亡。
© 2017 - 2021 Dell Inc. 或其子公司。
保留所有权利。
Dell、EMC 和其他商标是 Dell Inc. 或其附属机构的商标。
其他商标可能是其各自所有者的商标。
修订历史记录下表显示的是本文档的修订记录:修订版日期说明12021 年 10 月OpenManage Enterprise 3.8 的第一版。
●能够配置内部设备共享,以通过 HTTPS 或 CIFS(默认)提供内容。
●支持在 Windows 2022 上部署设备。
●启用现场服务调试 (FSD) 后,您现在可以使用审核日志 > 故障处理子菜单而不是文本用户界面(TUI) 上传签名的 .dat 文件和 SSH 公钥。
修订历史记录3前言为了改进产品线,我们会定期发布软件的修订版。
因此,本文档中介绍的一些功能可能只受当前正在使用的部分软件版本的支持。
产品发行说明提供了有关产品功能的最新信息。
如果某款产品不能正常运行或其功能与本文档的描述不符,请与您的技术支持专业人员联系。
:本文档在发布时准确无误。
请访问在线支持网站 (https:///support),以确保您使用的是本文档的最新版本。
用途本文档包含有关管理 OpenManage Enterprise 的概念性信息。
读者对象本文档供通过 OpenManage Enterprise 进行系统管理和监视的管理员、设备管理者和查看者使用。
相关说明文件以下出版物提供了更多信息:●OpenManage Enterprise 支持矩阵●OpenManage Enterprise 发行说明●OpenManage Enterprise 安全配置指南●OpenManage Enterprise 用户指南●OpenManage Enterprise RESTful API 指南●OpenManage Enterprise RESTful API,网址:https:///apis。
Dell™ OpenManage™5.5 版 Server Administrator 命令行界面用户指南"注"和"注意"本说明文件中的信息如有更改,恕不另行通知。
© 2008 Dell Inc. 版权所有,翻印必究。
未经 Dell Inc. 书面许可,严禁以任何形式复制这些材料。
本文中使用的商标:Dell 、DELL 徽标、PowerEdge 、PowerVault 和 OpenManage 是 Dell Inc. 的商标;Microsoft 、Windows 、Active Directory 、Hyper-V 和 Windows Server 是 Microsoft 公司在美国和/或其它国家或地区的商标或注册商标;SUSE 是 Novell, Inc. 在美国和其它国家或地区的注册商标;Red Hat 和 Red Hat Enterprise Linux 是 Red Hat, Inc. 的注册商标;Intel 、Pentium 和 Itanium 是 IntelCorporation 的注册商标,Intel386 是 Intel Corporation 的商标;AMD 、AMD Opteron 、AMD-V 和 AMD PowerNow!是 Advanced Micro Devices, Inc. 的商标;VESA 是 Video Electronic Standards Association 的注册商标;UNIX 是 The Open Group 在美国和其它国家或地区的注册商标;OS/2 是 International Business Machines Corporation 的注册商标;Rambus 是 Rambus, Inc 的注册商标;Citrix 和 XenServer 是 Citrix Systems, Inc. 在美国和/或其它国家或地区的注册商标或商标。
dell服务器系统开机提⽰错误解决⽅法DELL 服务器有时会若硬件的改动,在开机以后会提⽰错误信息。
信息⼀般会提⽰在显⽰器上,以后举出如下信息的解决办法。
信息原因纠正措施Alert! iDRAC6 not responding.Rebooting. iDRAC6 未响应 BIOS 通信,⼀种原因是它未正常运⾏,另⼀种原因是它未完成初始化。
系统将重新引导。
请等待系统重新引导。
Alert! iDRAC6 not responding.Power required may exceed PSU wattage.Alert! Continuing system boot accepts the risk that system may power down without warning. iDRAC6 挂起。
系统在引导时,iDRAC6 被远程重设。
在交流电恢复之后,iDRAC6 需要⽐正常情况下更长的时间来引导。
断开系统的交流电源 10 秒,然后重新启动系统。
Alert! Node Interleaving disabled! Memory configuration does not support Node Interleaving. 内存配置不⽀持节点交叉,或配置已更改(例如,内存模块出现故障),导致⽆法⽀持节点交叉。
系统将继续运⾏,但没有节点交叉功能。
请确保将内存模块安装在⽀持节点交叉的配置中。
请查看其它系统信息,以获取有关可能原因的更多信息。
有关内存配置信息,请参阅内存模块⼀般安装原则。
如果问题仍然存在,请参阅系统内存故障排除。
Alert! Power required exceeds PSU wattage.Check PSU and system configuration.Alert! Continuing system boot accepts the risk that system may power down without warning. 电源设备可能不⽀持处理器、内存模块和扩充卡的系统配置。
Dell OpenManage Server AdministratorVersion 7.1用户指南注和小心注:“注”表示可以帮助您更好地使用计算机的重要信息。
小心:“小心”表示可能会损坏硬件或导致数据丢失,并说明如何避免此类问题。
____________________本文中的信息如有更改,恕不另行通知。
©2012Dell Inc.保留所有权利。
未经 Dell Inc. 书面许可,严禁以任何形式复制这些材料。
本文中使用的商标:Dell™、DELL 徽标、PowerEdge™、PowerVault™ 和 OpenManage™ 是Dell Inc. 的商标。
Microsoft®、Windows®、Internet Explorer®、Active Directory®和 Windows Server®是 Microsoft Corporation 在美国和/或其他国家/地区的商标或注册商标。
EMC®是EMC Corporation 的注册商标。
Java®是 Oracle 和/或其附属公司的注册商标。
Novell®和SUSE®是 Novell, Inc. 在美国和其他国家或地区的注册商标。
Red Hat®和 Red Hat Enterprise Linux® 是 Red Hat, Inc. 在美国和其他国家或地区的注册商标。
VMware®是 VMware Inc 在美国和/或其他管辖区域的注册商标,ESX Server®是 VMware Inc 在美国和/或其他管辖区域的商标。
Mozilla®和 Firefox®是 Mozilla Foundation 的注册商标。
Citrix®、Xen®、XenServer®和 XenMotion®是 Citrix Systems, Inc. 在美国和/或其他国家或地区的注册商标或商标。
DELL(戴尔)BIOSLegacySelect 技术控制LegacySelect 技术控制可以基于通用平台、硬盘驱动器映像和帮助桌面程序提供完全使用、部分使用或不使用传统功能的解决方案。
管理员可以通过系统设置程序、Dell OpenManage™ IT Assistant 或Dell™ 工厂集成服务进行控制。
LegacySelect 使管理员可以通过电子方式激活或取消激活连接器和介质设备(包括串行和USB 连接器、并行连接器、软盘驱动器、PCI 插槽和PS/2 鼠标)。
取消激活连接器和介质设备后,便可以使用资源。
您必须重新启动计算机才能使更改生效。
可管理性Dell OpenManage™ IT Assistant IT Assistant 可以配置、管理和监测公司网络上的计算机及其它设备,并可以为配备行业标准管理软件的计算机管理资产、配置、事件(警报)和安全保护。
它支持符合SNMP、DMI 和CIM 行业标准的工具。
Dell OpenManage Client Instrumentation 基于DMI 和CIM,可用于您的计算机。
有关IT Assistant 的信息,请参阅Dell 支持Web 站点 上的Dell OpenManage IT Assistant 用户指南。
Dell OpenManage Client Instrumentation Dell OpenManage Client Instrumentation 软件可以使远程管理程序(例如IT Assistant)执行以下操作:查看计算机信息,例如计算机处理器的数量以及计算机运行的操作系统监测计算机状态,例如侦听温度探测器上的温度警报或存储设备发出的硬盘驱动器故障警报更改计算机状态,例如更新计算机的BIOS 或远程关闭计算机有关Dell OpenManage Client Instrumentation 的信息,请参阅Dell 支持Web 站点 上的Dell OpenManage Client Instrumentation 用户指南。
Dell™ OpenManage™ 安装和安全用户指南注、注意和警告本说明文件中的信息如有更改,恕不另行通知。
© 2008 Dell Inc. 版权所有,翻版必究。
未经 Dell Inc. 书面许可,严禁以任何形式复制这些材料。
本文中使用的商标:Dell 、DELL 徽标、OpenManage 、PowerEdge 、PowerConnect 和 PowerVault 是 Dell Inc. 的商标;Microsoft 、Windows 、Windows NT 、Windows Server 、Vista 、Hyper-V 和 ActiveDirectory 是 Microsoft Corporation 在美国和/或其它国家/地区的商标或注册商标;Red Hat 和 Red Hat Enterprise Linux 是 Red Hat, Inc. 在美国和其它国家/地区的注册商标;VMware 是 VMware Inc 在美国和/或其它管辖区域的注册商标,ESX Server 是其商标;Novell 、SUSE 和 ConsoleOne 是 Novell, Inc. 在美国和其它国家/地区的注册商标;UNIX 是 The Open Group 在美国和其它国家/地区的注册商标;Intel 是 Intel Corporation 在美国 和其它国家(或地区)的注册商标;VMware 是 VMware, Inc. 的注册商标,而 ESX Server 是 VMware, Inc. 的商标;Citrix 和 XenServer 是 Citrix Systems, Inc. 在美国和/或其它国家/地区的注册商标或商标。
本说明文件中述及的其它商标和产品名称是指拥有相应商标和产品名称的公司或其制造的产品。
Dell Inc. 对本公司的商标和产品名称之外的其它商标和产品名称不拥有任何专有权。
2008 年 11 月简介在 Microsoft Windows Server 2008 Core 和 Microsoft Hyper-V Server 上安装 Dell OpenManage 软件Dell OpenManage 安全保护在支持的 Linux 操作系统上安装 Managed System Software 设置和管理使用 Microsoft Active Directory使用 Unified Server Configurator 安装操作系统前提条件检查程序使用系统构建和更新工具安装操作系统常见问题安装 Management Station Software 词汇表在 Microsoft Windows 操作系统上安装 Managed System Software注: "注"表示可以帮助您更好地使用计算机的重要信息。
Dell OpenManage Essentials Version 1.3 User's Guide注、小心和警告注: “注”表示可以帮助您更好地使用计算机的重要信息。
小心: “小心”表示可能会计坏硬件或计致数据计失,并计明如何避免此计计计。
警告: “警告”表示可能会造成计计计失、人身计害甚至死亡。
版计所有© 2014 Dell Inc. 保留所有计利。
本计品受美国、国计版计和知计计计法律保计。
Dell™和 Dell 徽计是 Dell Inc. 在美国和 / 或其他管计区域的商计。
所有此计提及的其他商计和计品名称可能是其各自所属公司的商计。
2014 - 02Rev. A00Contents1 关于 OpenManage Essentials (15)本计行版中的新增功能 (15)您可能需要的其他信息 (15)计系 Dell (17)2 安装 OpenManage Essentials (19)安装的前提条件和最低要求 (19)最低建计硬件 (19)最低要求 (19)使用关系数据计管理系计的条款及计计 (20)数据计大小和可计展性 (21)网计计计利用率 (21)Microsoft SQL Server 的最低计限登计角色 (21)下计 OpenManage Essentials (22)安装 OpenManage Essentials (22)自定计计置安装 (23)在域控制器上安装 OpenManage Essentials 计的考计事计 (24)在计程 SQL Server 上计置 OpenManage Essentials 数据计 (24)安装 Dell SupportAssist (25)安装 Repository Manager (26)安装 Dell License Manager (26)卸计 OpenManage Essentials (27)升计到 OpenManage Essentials 1.3 版 (27)计置和配置 VMware ESXi 5 (29)从 IT Assistant 迁移至 OpenManage Essentials (29)3 OpenManage Essentials 使用入计 (31)启计 OpenManage Essentials (31)配置 OpenManage Essentials (31)使用 OpenManage Essentials 计计主计 (32)OpenManage Essentials 计计横幅 (32)自定计计计 (33)计示其它可用的计表和计形 (34)提取计表和计告以计得更多信息 (34)保存与计入计计布局 (35)更新计计数据 (35)计藏计形和计告(计件) (35)重新排列计形和计告(计件)或计整其大小 (35)计计数据 (36)搜索计 (36)搜索计目 (36)搜索下拉列表 (37)计计操作 (37)地计计计(主计)计计 (37)计看用计信息 (38)以不同用计身份登计 (38)使用“有可用更新”通知计计 (38)使用保修警示牌通知计计 (39)4 OpenManage Essentials 主计计计 — 参考 (41)计表板 (41)计计主计计告 (41)按状计分计的计计 (42)按计重性分计的警计 (42)已计找到的计计与已计行计源清册计计之计比 (42)任计状计 (43)计划计计 (43)计划计计计置 (43)计计保修计告 (44)地计计计(主计)计计界面 (44)5 计计计找和计源清册 (45)支持的计计、计计和功能计表 (45)支持的操作系计(服计器)、计计和功能计表 (48)支持的存计计计、计计和功能计表 (49)计例和定计 (50)使用计找和计源清册计计 (51)用于计找的计计支持计表 (51)用于系计更新的计计支持计表 (53)计计未计告服计计计 (53)配置计找和计源清册任计 (54)更改默计的 SNMP 端口 (55)使用 WS-Man 计计和根计计计找和计源清册 Dell 计计 (55)排除范计 (56)计看已配置的计找和计源清册范计 (56)计划计找 (57)计找速度滑计 (57)多计程 (57)计划计源清册 (58)配置状计计计计率 (58)6 计找和计源清册 - 参考 (59)计找和计源清册计计计面计计 (59)计找和计源清册计计 (59)上一次计找和计源清册 (60)已计找到的计计与已计行计源清册计计之计比 (60)任计状计 (61)计看计计摘要 (61)计看计计摘要计计计计 (61)添加计找范计/ 添加计找范计计 (62)计找配置 (62)计找配置计计 (62)ICMP 配置 (63)ICMP 配置计计 (64)SNMP 配置 (64)SNMP 配置计计 (64)WMI 配置 (65)WMI 配置计计 (65)存计配置 (65)存计配置计计 (65)WS-Man 配置 (65)WS-Man 配置计计 (66)SSH 配置 (66)SSH 配置计计 (66)IPMI 配置 (67)IPMI 配置计计 (67)计找范计操作 (67)摘要 (68)添加排除范计 (68)添加排除范计计计 (68)配置 (68)计找计划 (68)计源清册计划 (70)状计计划 (70)7 管理计计 (73)计看计计 (73)计计摘要计面 (73)计点和符号计明 (75)计计计情 (75)计看计计的计源清册 (76)计看警计摘要 (77)计看系计事件日志 (77)搜索计计 (77)计建新计 (77)将计计添加到新计 (78)将计计添加到计有计 (78)计藏计 (78)计除计 (79)计一登计 (79)计建自定计 URL (79)启计自定计 URL (80)配置保修计子计件通知 (80)配置保修警示牌通知 (80)使用地计计计 (81)地计提供程序 (83)配置地计计置 (83)一般计航和计放 (84)主计计 (84)工具提示 (84)在地计计计上计计计计 (85)运行和计接状计 (85)在相同位置的多个计计 (86)计置主计计 (86)计看所有地计位置 (86)将计计添加到地计 (87)使用“计计位置计计信息”计计移计计计位置 (87)计入已授计计计 (88)使用地计计计搜索计 (89)移除所有地计位置 (90)计计地计位置 (91)移除地计位置 (91)计出所有计计位置 (92)Dell PowerEdge FX 机箱计计 (92)工具提示和计计计计 (93)覆盖 (93)右计计计操作 (94)计航痕迹 (94)支持 PowerEdge FX 机箱底座 (94)Dell NAS 计计支持 (94)OEM 计计支持 (95)8 计计 — 参考 (97)计看计源清册 (97)计看警计 (98)计看硬件日志 (98)硬件日志计计情况 (98)警计计计器 (98)计看非符合系计 (99)非符合系计 (99)计计搜索 (99)计计计果 (100)计建计计计 (100)计计计配置 (100)计计计计 (101)摘要 — 计配置 (101)地计计计(计计)计计卡界面 (101)在此位置的计计 (102)地计计置 (103)9 计看计源清册计告 (105)计计计定计计告 (105)计定计计告 (105)计计计告数据 (106)计出计告 (107)10 计告 — 参考 (109)代理程序和警计摘要 (110)代理摘要 (110)计计警告 (110)生成警计最多的系计 (110)服计器概计 (110)服计器计件和版本 (111)计计收计信息 (111)计计计计信息 (112)计计支持信息 (112)硬计计计器信息 (113)ESX 信息 (114)HyperV 信息 (114)计计可替计计元 (FRU) 信息 (114)计可计信息 (115)内存信息 (115)模计化机柜信息 (115)NIC 信息 (116)PCI 计计信息 (116)存计控制器信息 (116)保修信息 (117)11 计看保修计告 (119)延计保修 (119)12 管理警计 (121)计看警计和警计计计 (121)计看警计日志 (121)了解警计计型 (121)计看内部警计 (122)计看警计计计 (122)计看警计源计计信息 (122)计看先前配置的警计措施 (122)计看计用程序启计警计措施 (122)计看计子计件警计措施 (123)计看警计忽略措施 (123)计看警计陷阱计计措施 (123)计理警计 (123)计计警计 (123)计建和计计新计计 (123)配置警计措施 (124)计置计子计件通知 (124)忽略警计 (125)运行自定计脚本 (125)计计警计 (126)计计警计用例案例 (126)参考计本警计措施使用案例 (127)警计措施中的用例 (127)配置警计日志计置 (127)重命名警计计计和警计源 (127)警计计出通知 (128)配置警计计出通知 (128)启用或禁用警计计出通知 (128)13 警计 — 参考 (131)警计日志 (131)计定计的警计计计计计器 (132)警计日志字段 (132)警计计计信息 (133)警计日志计置 (133)警计计计计计器 (133)警计计计器名称 (133)计重性 (134)确计 (134)摘要 —— 警计计计计计器 (134)警计措施 (135)名称和计明 (135)计重性关计 (136)计用程序启计配置 (136)计子计件配置 (137)陷阱计计 (138)计计和源关计 (138)计计关计 (138)日期和计计范计 (139)警计措施 - 重复警计关计 (140)摘要 - 警计操作计计信息 (140)警计计计 (141)警计计计计计 (141)警计源 (142)14 更新服计器 BIOS、固件、计计程序和计用程序 (145)计看系计更新计面 (145)了解服计器 BIOS 固件和计计程序源 (146)计更新计计正确源 (146)计计更新目计源 (146)计看比计计果 (147)计看符合服计器 (147)计看非符合服计器 (147)计看未计点的服计器 (147)计看有计计的服计器和解决方案 (147)系计更新用例案例 (147)计用系计更新 (149)计看更新状计 (150)计看当前目计 (150)计计和解决方案用例案例 (150)15 系计更新 — 参考 (153)计计计计 (153)系计更新 (154)符合性计告 (154)符合系计 (155)非符合系计 (156)系计更新任计 (156)未计源清册的系计 (157)计源清册系计 (157)所有系计更新任计 (158)计计和解决方案 (158)任计计行计史 (158)计计目计源 (159)Dell Update Package(Dell 更新计件包) (159)Dell OpenManage Server Update Utility (159)Repository Manager (159)计看当前目计 (160)16 管理计程任计 (161)关于计程任计 (161)管理命令行任计 (161)管理 RACADM 命令行任计 (162)管理通用命令行任计 (163)管理服计器计源计计 (164)部署 Server Administrator (164)支持的 Windows 和 Linux 计件包 (165)参数 (166)使用计本计程任计用例 (166)计程任计用例 (167)计计功能计表 (168)17 计程任计— 参考 (171)计程任计主计 (171)计程任计 (172)所有任计 (172)任计计行计史 (173)服计器计源计计 (173)部署 Server Administrator 任计 (175)命令行任计 (176)计程 Server Administrator 命令 (177)通用命令 (178)IPMI 命令 (180)RACADM 命令行 (181)18 管理安全计置 (183)使用安全角色和计限 (183)Microsoft Windows 计计 (183)分配用计计限 (184)使用自定计 SSL 计计(可计) (184)配置 IIS 服计 (184)在 OpenManage Essentials 中支持的计计和端口 (184)在管理站上支持的计计和端口 (184)在受管计点上支持的计计和端口 (185)19 故障排除 (187)OpenManage Essentials 故障排除工具 (187)排除故障的程序 (187)计源清册的故障排除 (187)计计计找的故障排除 (188)排除接收 SNMP 陷阱故障 (189)基于 Windows Server 2008 服计器计找的故障排除 (189)计计 ESX 或 ESXi 版本 3.5、4.x 或 5.0 的 SNMP 陷阱计行故障排除 (189)使用 Microsoft Internet Explorer 计行故障排除 (189)地计计计故障排除 (190)20 常计计计 (193)安装 (193)升计 (193)任计 (194)可计命令行计置 (194)自定计参数 (195)MSI 返回代计 (196)计子计件警计措施 (196)计找 (196)计源清册 (198)系计更新 (198)计计计计限 (199)计计计计限计计 (199)计程和系计更新任计 (199)自定计计计计 (200)日志 (200)日志计计 (201)故障排除 (201)21 管理计计计计限 (203)向 OmeSiteAdministrators 角色添加用计 (203)向用计分配计计计 (204)从 OmeSiteAdministrators 角色移除用计 (205)22 OpenManage Mobile 计置 (207)启用或禁用 OpenManage 移计的警计通知 (207)启用或禁用 OpenManage Mobile 计计 (208)计除 OpenManage Mobile 计计 (208)计看警计通知服计状计 (208)通知服计状计 (209)计看 OpenManage Mobile 计计信息 (209)移计计计信息 (209)OpenManage Mobile 故障排除 (210)23 首计计 — 参考 (213)控制台计置 (213)计子计件计置 (214)警计计置 (214)自定计 URL 计置 (215)保修通知计置 (215)计计计计限 (216)常计任计 (216)管理计计计计限 (216)用于计行任计和打计丁的计计计 (216)24 日志 — 参考 (219)用计界面日志 (219)计用程序日志 (219)25 计展 (221)26 右计计计操作 (223)计划计计 (223)计计状计 (223)计找范计摘要 (224)管理包含范计 (224)计看计计器 (224)警计 (225)计程任计 (225)自定计 URL (225)系计更新任计 (225)27 教程 (227)28 使用 OpenManage Essentials 命令行界面 (229)启计 OpenManage Essentials 命令行界面 (229)计建计找配置文件计入文件 (229)使用 XML 或 CSV 文件指定 IP、范计或主机名 (229)在 PowerShell 中指定计入文件 (230)命令行界面命令 (230)计建计找范计 (230)计除计找范计 (231)计建计找范计计 (231)计除计找范计计 (232)计计计找范计 (232)计计计找范计计 (232)启用计找范计或计找范计计 (233)禁用计找范计或计找范计计 (233)计建计找排除范计 (233)计除计找排除范计 (233)运行计找、计源清册和状计计计任计 (234)移除计计 (234)计索计找范计的状计计行计度 (235)停止正在运行的计找范计或计 (235)计建自定计计计计 (235)将计计添加到自定计计 (236)计除计 (236)141关于 OpenManage EssentialsOpenManage Essentials 是一个硬件管理应用程序,可对企业网络中的 Dell 系统、设备和组件提供全面概览。
Dell OpenFlow Deployment and User Guide 3.0Dell Software-Defined Networking (SDN)Notes, Cautions, and WarningsNOTE: A NOTE indicates important information that helps you make better use of your computer.CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.WARNING: A WARNING indicates a potential for property damage, personal injury, or death.Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.2015–02Rev. A02Contents1 Introduction (5)OpenFlow 1.0 Support (6)OpenFlow 1.3 Support (8)2 Configuring ACL CAM Carving on the S4810, S4820T, S6000, S5000, and MXL switch (11)3 Configuring ACL CAM Carving on Z9000 and Z9500 (13)4 Flow Types (14)5 Configuring OpenFlow Instances (17)6 Forwarding Features (20)7 Egress QoS (22)Caveats (22)8 OpenFlow Interfaces (23)9 Flow Setup (26)10 Exceptions (31)11 OpenFlow Commands (33)SDN Command Modes (33)connect retry-interval (34)controller (35)debug openflow packets (36)echo-request interval (38)fail-mode secure (38)flow-map (39)flow-misses drop (40)interface-type (40)interface vlan (41)multiple-fwd-table enable (42)of-instance (Interface) (42)of-instance (Configuration) (44)of-version (45)openflow vlan (46)show openflow (47)show openflow flows (48)shutdown (OpenFlow Instance) (49)src-suppression (49)1 IntroductionOpenFlow (OF) 1.0 [STD-1] is supported on the S4810, S4820T, S6000, Z9000, and MXL switches. OverviewIn a software-defined network (SDN), an external controller cluster manages the network and the resources on each switch. OpenFlow is a protocol used for communication between the controller and the switch.In the example topology below, the controller uses the OpenFlow protocol to communicate with twoS4810 switches.Figure 1. OpenFlow TopologyOpenFlow offloads all switching and routing protocol state machines to the controller. A simplified and efficient software layer on the switch programs the forwarding tables.Dell currently supports OpenFlow version 1.0. For information about exceptions, refer to Exceptions.5OpenFlow 1.0 SupportOpenFlow (OF) 1.0 [STD-1] is supported on the S4810, S4820T, S6000, Z9000, and MXL switches. OpenFlow (OF) 1.3 [STD-1] is supported on the S4810, S4820T, S5000, S6000, Z9000, Z9500, and MXL switches.NOTE: When of-instance is enabled with version 1.3, the OpenFlow 1.0 functionality is alsosupported.Match Parameters and Supported ValuesUsing OpenFlow, you can transmit the switch’s ports and forwarding tables to the controller, allowing the controller to configure forwarding entries on the switch. OpenFlow also allows the controller to insert control packets through the switch and to redirect any missed flow packets from the switch to the controller.The flows in OpenFlow allow the switch to match based on the following parameters and values:Table 1. Match Parameters and Supported ValuesThe software forwards the match results out of one or more network ports, with the option to modify the packet headers.6Supported Flow ActionsThe following flow actions are supported:•OFPAT_FLOOD or OFPAT_ALL: Floods packets to all ports and VLANs on the OF interface.•OFPAT_CONTROLLER: Sends all NO_MATCH or ACTION packets to the controller specified by the packet’s VLAN tag.•OFPAT_out_port: Displays a list of ports that can receive traffic.•OFPAT_DROP: Drops all packets that match the specified criteria.•MODIFY FIELD — Set VLAN ID: Assigns a VLAN ID (0 to 4094).•MODIFY FIELD — Set VLAN priority: Assigns a priority to a VLAN (0 to 7).•MODIFY FIELD — Modify Ethernet source MAC address: Changes the Ethernet source MAC address to the specified value.•MODIFY FIELD — Modify Ethernet destination MAC address: Changes the Ethernet destination MAC address to the specified value.•MODIFY FIELD — Modify IPv4 ToS bits: Changes the IPv4 ToS in the packet header to the specified value.•OFPAT_ENQUEUE: Send the specified flow to the queue.NOTE: If there is a conflict between actions, the action with the higher priority takes precedence. Unsupported OpenFlow MessagesThe following OpenFlow messages are not supported. Some unsupported messages generateOFPT_ERROR, which is an error message sent to the controller.Table 2. Unsupported OpenFlow MessagesFor supported flow-match and flow action parameters for each flow type, refer to Flow Types.The following is a list of actions that are not supported for any flow types. All of the following commands generate an OFPT_ERROR message.•OFPAT_SET_NW_SRC (set src-ip)•OFPAT_SET_NW_DST (set dst-ip)•OFPAT_SET_TP_SRC (set tcp/udp src-port)•OFPAT_SET_TP_DST (set tcp/udp dst-port)•OFPAT_OUTPUT to OFPP_IN_PORT•OFPAT_OUTPUT to OFPP_TABLE7•OFPAT_OUTPUT to OFPP_NORMAL•OFPAT_OUTPUT to OFPP_LOCAL•FORWARD — Normal•FORWARD — LOCAL•FORWARD — Inport•MODIFY FIELD — Strip VLAN header•MODIFY FIELD — Modify IPv4 source address•MODIFY FIELD — Modify IPv4 destination address•MODIFY FIELD — Modify transport source port•MODIFY FIELD — Modify transport destination port•MAX_BYTES_TO_SENDLimitations•OFPAT_OUTPUT to OFPP_FLOOD and OFPP_ALL are supported on the S4810, S4820T, S6000, and MXL switches. Support for these commands on the Z9000 was introduced in version 9.4(0.0).•Multiple output ports are supported on S4810, S4820T, and MXL switches. Multiple output ports are not supported on the Z9000 platform.•The set/modify actions must precede the output ports actions. If you specify multiple output ports, the switch cannot transmit different copies.•You cannot specify individual output ports for ALL or FLOOD actions.OpenFlow 1.3 SupportOpenFlow (OF) 1.3 [STD-1] is supported on the S4810, S4820T, S5000, S6000, Z9000, Z9500, and MXL switches.Dell Networking OS supports OpenFlow 1.3 message types. Although OpenFlow 1.3 is enabled, the OpenFlow 1.0 functionality is also supported. Additionally, the group flow and multipart message types features are supported. The multipart message types features replaces the statistics feature in OpenFlow 1.0 version.Match Parameters and Supported ValuesUsing OpenFlow, you can transmit the switch’s ports and forwarding tables to the controller, allowing the controller to configure forwarding entries on the switch. OpenFlow also allows the controller to insert control packets through the switch and to redirect any missed flow packets from the switch to the controller.The flows in OpenFlow allow the switch to match based on the following parameters and values:Table 3. Match Parameters and Supported Values8The software forwards the match results out of one or more network ports, with the option to modify the packet headers.Supported Flow ActionsThe following flow actions are supported:•OFPAT_FLOOD or OFPAT_ALL: Floods packets to all ports and VLANs on the OF interface.•OFPAT_CONTROLLER: Sends all NO_MATCH or ACTION packets to the controller specified by the packet’s VLAN tag.•OFPAT_out_port: Displays a list of ports that can receive traffic.•OFPAT_DROP: Drops all packets that match the specified criteria.•OFPXMT12_OFB_ETH_TYPE — Ethernet frame type•OFPXMT12_OFB_VLAN_PCP — VLAN priority•MODIFY FIELD — Set VLAN ID: Assigns a VLAN ID (0 to 4094).•MODIFY FIELD - Strip Vlan ID: Strips VLAN ID from the packet.•MODIFY FIELD — Set VLAN priority: Assigns a priority to a VLAN (0 to 7).•MODIFY FIELD — Modify Ethernet source MAC address: Changes the Ethernet source MAC address to the specified value.•MODIFY FIELD — Modify Ethernet destination MAC address: Changes the Ethernet destination MAC address to the specified value.•MODIFY FIELD — Modify IPv4 ToS bits: Changes the IPv4 ToS in the packet header to the specified value.•OFPAT_ENQUEUE: Send the specified flow to the queue.NOTE: If there is a conflict between actions, the action with the higher priority takes precedence.9Unsupported OpenFlow MessagesThe following OpenFlow messages are not supported. Some unsupported messages generateOFPT_ERROR, which is an error message sent to the controller.Table 4. Unsupported OpenFlow MessagesFor supported flow-match and flow action parameters for each flow type, refer to Flow Types.The following is a list of actions that are not supported for any flow types. All of the following commands generate an OFPT_ERROR message.•OFPAT_SET_NW_SRC (set src-ip)•OFPAT_SET_NW_DST (set dst-ip)•OFPAT_SET_TP_SRC (set tcp/udp src-port)•OFPAT_SET_TP_DST (set tcp/udp dst-port)•OFPAT_OUTPUT to OFPP_IN_PORT•OFPAT_OUTPUT to OFPP_TABLE•OFPAT_OUTPUT to OFPP_NORMAL•OFPAT_OUTPUT to OFPP_LOCAL•FORWARD — Normal•FORWARD — LOCAL•FORWARD — Inport•MODIFY FIELD — Strip VLAN header•MODIFY FIELD — Modify IPv4 source address•MODIFY FIELD — Modify IPv4 destination address•MODIFY FIELD — Modify transport source port•MODIFY FIELD — Modify transport destination port•MAX_BYTES_TO_SENDLimitationsLimitations•OFPAT_OUTPUT to OFPP_FLOOD and OFPP_ALL are supported on the S4810, S4820T, S6000, and MXL switches. Support for these commands on the Z9000 was introduced in version 9.4(0.0).•Multiple output ports are supported on S4810, S4820T,Z9000, and MXL switches.•The set/modify actions must precede the output ports actions. If you specify multiple output ports, the switch cannot transmit different copies.•You cannot specify individual output ports for ALL or FLOOD actions.102 Configuring ACL CAM Carving on theS4810, S4820T, S6000, S5000, and MXL switchDell Networking switches can operate in Hybrid mode, which enables OpenFlow and legacy functionality on the same switch. By default, access control list content addressable memory (ACL CAM) space is not allocated for OpenFlow. To enable OpenFlow, reserve CAM space for OpenFlow using the following commands. The amount of CAM space that you allocate for OpenFlow determines the number of available ACL entries. For more information on CAM, refer to the Content Addressable Memory (CAM) chapter in the FTOS Configuration Guide.NOTE: The commands to allocate CAM space for OpenFlow on the S4810, S4820T, S6000, S5000, and MXL switches differ from the commands used for the Z9000 and Z9500.1.Enter a value for cam-acl.Select one of the following values for cam-acl:•0 (default): No space is allocated for OpenFlow. Change this value to four or eight to enable OpenFlow.•4: Allocates space for up to 242 flow entries (20 entries are reserved for internal purposes from the 256 available flows, leaving 242 entries for use by OpenFlow). For S6000, entering a 4allocates space for up to 498 flow entries (14 entries are reserved for internal purposes from the 512 available flows, leaving 498 entries for use by OpenFlow).•8: Allocates space for up to 498 flow entries (14 entries are reserved for internal purposes from the 512 available flows, leaving 498 entries for use by OpenFlow). For S6000, entering an 8allocates space for up to 998 flow entries (14 entries are reserved for internal purposes from the 1012 available flows, leaving 998 entries for use by OpenFlow).The following sample S4810 configuration reserves 512 entries for OpenFlow:Dell(conf)#cam-acl l2acl 3 ipv4acl 2 ipv6acl 0 ipv4qos 2 l2qos 2 l2pt 0ipmacacl 0 vman-qos 0 ecfmacl 0 openflow 8 fcoeacl 0 iscsioptacl 02.Enter a value for cam-acl-vlan.Select one of the following values for cam-acl-vlan:•0 (default): No space is allocated for OpenFlow. Change this value to 1 to enable OpenFlow.•1: Enables OpenFlow.The following sample configuration shows a value of 1 for cam-acl-vlan:Dell(conf)#cam-acl-vlan vlanopenflow 1 vlaniscsi 13.Reboot the switch after changing the cam-acl and cam-vlan-acl values. If you do not reboot theswitch, the configuration changes do not take effect.11NOTE:To upgrade any configuration changes that have changed the NVRAM content if you enableBMP 3.0, use the reload conditional nvram-cfg-change command to perform a reload on the chassis.123 Configuring ACL CAM Carving on Z9000 and Z9500Dell Networking switches can operate in Hybrid mode, which enables OpenFlow and legacy functionality on the same switch. By default, access control list content addressable memory (ACL CAM) space is not allocated for OpenFlow. To enable OpenFlow, reserve CAM space for OpenFlow using the following commands. The amount of CAM space that you allocate for OpenFlow determines the number of available ACL entries. For more information on CAM, refer to the Content Addressable Memory (CAM) chapter in the FTOS Configuration Guide.NOTE: The commands to allocate CAM space for OpenFlow on the Z9000 and Z9500 differ from the commands used for the S4810, S4820T, S6000, S5000, and MXL switches.1.Enter a value for cam-acl.Select one of the following values for cam-acl:•0 (default): No space is allocated for OpenFlow. Change this value to four or eight to enable OpenFlow.•4: Allocates space for up to 242 flow entries (14 entries are reserved for internal purposes from the 256 available flows, leaving 242 entries for use by OpenFlow).•8: Allocates space for up to 498 flow entries (14 entries are reserved for internal purposes from the 512 available flows, leaving 498 entries for use by OpenFlow).The following sample Z9000 and Z9500 configuration reserves 512 entries for OpenFlow:Dell(conf)# cam-acl l2acl 2 ipv4acl 2 ipv6acl 0 ipv4qos 4 l2qos 1 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 0 openflow 8NOTE: For Z9000 and Z9500, the cam-acl-vlan value is set to 1 (enabled) by default; noadditional configuration is required.2.Reboot the switch after changing the cam-acl values. If you do not reboot the switch, theconfiguration changes do not take effect.NOTE:To upgrade any configuration changes that have changed the NVRAM content, if you enableBMP 3.0, use the reload conditional nvram-cfg-change command to perform a reload on the chassis .134 Flow TypesDell Networking switches support three types of flows:•ACL•L2•L3The following sections describe the mandatory match fields, optional match fields, mandatory actions, and optional actions for each flow type.ACL FlowsParameter Type ParametersNone; any of the match parameters can be wildcards.Mandatory matchfieldsAll 12 match fields defined in OpenFlow (OF) 1.0 are supported.Optional matchfieldsMandatory actions None.Optional actions•set_vlan_id•set_vlan_pcp•strip_vlan•set_dl_src (set src-mac)•set_dl_dst (set dst-mac)•set_nw_tos•output to one or more switch portsNOTE: For output action limitations, refer to OpenFlow 1.0 Support.L3 FlowsParameter Type ParametersMandatory matchfields•You must specify dl_dst (dst-mac) as the switch’s port mac.•You must specify dl_type (ether-type) as 0x800.Optional matchfields•nw_dst (dst-ip)14Parameter Type Parameters•All fields other than the ones listed in “Mandatory match fields” and “Optionalmatch fields” must be wildcards.Mandatory actions•You must specify set_dl_src (set src-mac) as the port mac (local mac) for the swtich.•set_dl_dst (set dst-mac)•Single OFPAT_OUTPUT action to a switch port.Optional actions OFPAT_SET_VLAN is optional for OpenFlow (OF) ports and mandatory for OFvirtual local area networks (VLANs).L2 FlowsParameter Type ParametersMandatory matchfields•dl_vlan (input vlan id)•dl_dst (dst-mac)Optional matchAll fields other than dl_vlan and dl_dst must be wildcards.fieldsMandatory actions Single OFPAT_OUTPUT action to a switch port.Optional actions None.Max LimitsThis section defines the maximum number of permitted flow types. The number of available flow types varies depending on the type of flow.•You can provision up to 8 OF instances on each switch.•The number of flows supported on each switch depends on the flow type.•OF flow types can be combined — for example, the following flow combination is supported: 256 ACL flows, 48,000 L2 flows, and 6,000 L3 flows.15Group FlowsParameter Types ParametersNone.Mandatory MatchFieldsOptional MatchNone.FieldsAction Types•ALLMandatory Actions•output_portNOTE: Multiple actions in a single bucket is not supported. This feature isavailable only when of-instance version is set to 1.3.Optional Actions None.The following example shows the Group Flow details:Instance: 2, Table: acl, Flow: 5, Cookie: 0xc80a3c5800000000Priority: 22016, Internal Priority: 22016Up Time: 2d 20:34:54, Hard Timeout: 0 secondsIdle Timeout: 0 seconds, Internal Idle Timeout: 0 secondsPackets: 0, Bytes: 0Match Parameters:Valid Match: InPort,Etype,DMACIn Port : Te 0/13 EType : arpSMAC : *DMAC : 01:00:00:00:00:00 / 01:00:00:00:00:00VLAN id : * VLAN PCP : *IP TOS : * IP proto : *Src IP : * Dest IP : *Src Port : * Dest Port : *Actions:Output: Group:0x0x10000001 Type:AllBuckets:controllerTe 0/13Po 112165 Configuring OpenFlow InstancesThis section describes how to enable and configure OpenFlow instances on a switch.•You can use up to 8 OpenFlow instances on a switch. The OpenFlow (OF) ID range is from 1 to 8.•You must allocate CAM blocks for use by OpenFlow before configuring any OpenFlow instances. For more information, refer to Configuring ACL CAM Carving on the S4810, S4820T, S6000, and MXL switch for S4810, S4820T, S6000, and MXL switches or Configuring ACL CAM Carving on Z9000 for the Z9000 platform.•Only transmission control protocol (TCP) connections are supported on Dell Networking switches.Transport layer security (TLS) connections are not supported.•You can configure only one controller IP and one TCP port for each OF instance.•The connection is established when you enable the OF instance using the no shut command.•You cannot modify the OF instance while it is enabled. To make configuration changes, use the shutdown command to disable the OF instance, as shown below.Dell#show running-config openflow of-instance!openflow of-instance 1controller 1 10.11.205.184 tcpshutdownDell#•The show openflow of-instance command displays details on the instance, as shown below: Dell#show openflow of-instance 1Instance : 2Admin State : UpOF Version : V1-3Interface Type : VlanDP Id : 00:02:74:86:7a:ff:6f:e4Forwarding Tbls : acl, mac, routeFlow map :l2, l3EchoReq interval: 15 secondsConnect interval: 15 secondsNumber of Flows : 21 (acl:21)Packets (acl) : 575600Bytes (acl) : 36838400Fail mode : secureFlow misses : copy-to-controllerController 1 : TCP, 10.11.54.186/6633, rcv/sndbuf 1000/1000, connected (equal) high-priorityController 2 : -Port List :Vlan List :Vl 200Vlan Mbr list :Fo 1/16 (209), Fo 1/20 (213), Fo 2/0 (385)17If you do not specify a default VLAN for packet routing, the software assigns the first available VLAN as the default VLAN when you create the first OF instance. To specify a default VLAN, use the openflow vlan command.1.Create or modify an OF instance.CONFIGURATION modeopenflow of-instance of-id2.If this is a new OF instance, continue to step3. To change an existing OF instance, disable it first.NOTE: All new OF instances are disabled by default. For existing OF instances, you must disable the OpenFlow instance before you can configure it.OPENFLOW INSTANCE modeshutdown3.Add a physical interface or VLAN to an OpenFlow instance.INTERFACE modeof-instance of-idNOTE: For more information, refer to OpenFlow Interfaces4.Specify the interface type for the OF instance.OPENFLOW INSTANCE modeinterface-type {any|port|vlan}NOTE: Dell Networking does not recommend selecting any for the interface-type unlessboth OF ports and OF VLANs are required in a single instance. If you select any for theinterface-type, the number of available ACL flows is reduced by half (128 of 256 entries or256 of 512 entries).NOTE: Dell Networking does not recommend configuring global spanning-tree protocol (STP)instances on ports using both legacy virtual local area networks (VLANs) and OF VLANs.5.Specify the OF controller configuration used by OF to establish a connection.OPENFLOW INSTANCE modecontroller {controller-id}{ip-address}[port port-number]tcp6.(OPTIONAL) Configure the high-priority value for the OF - controller.OPENFLOW INSTANCE modecontroller {controller-id} {ip-address} tcp high-priority7.(OPTIONAL) Configure the timed interval (in seconds) that the OF instance waits after attempting toestablish a connection with the OF controller.OPENFLOW INSTANCE modeconnect retry-interval interval8.(OPTIONAL) Configure the controller to be a High Priority controller.OPENFLOW INSTANCE modecontroller {controller–id} {ip–address} {tcp} [high-priority]189.(OPTIONAL) Specify if flows installed by the controller should be interpreted by the switch forplacement in L2 or L3 tables.OPENFLOW INSTANCE modeflow-map {l2|l3} enable10.(OPTIONAL) Advertise all forwarding tables (ACL, L2, and L3) to the controller.OPENFLOW INSTANCE modemultiple-fwd-table enable11.Enable the OF instance.OPENFLOW INSTANCE modeno shutdown196 Forwarding FeaturesFlow FailoverThis feature provides failover support if a controller is unavailable. If the connection to a controller is lost, installed flows are retained and used for forwarding traffic until they are updated. This feature is enabled by default but you can disable failover on individual instances by using the use the no fail-mode secure command. If you disable failover, all flows to the unavailable controller are dropped. For more information, refer to the fail-mode secure command.Flow MissesBy default, flows that do not reach their intended destination (flow misses), are copied to the controller. To disable this feature on an OF instance, configure the controller to drop flow misses instead of copying them to the controller by using the flow-misses drop command. For more information, refer to the flow-misses drop command.Default VLANIn the previous version of OpenFlow, some packet types, such as untagged ARP broadcasts, received on an OF port could not be forwarded from a physical port and could only be copied to the controller. To resolve this issue, assign a default VLAN to the OF ports using the openflow vlan command. If you do not assign a VLAN, the software selects one when you create the first OF instance. The default VLAN applies to all OF instances and can only be configured if you have not configured any OF instances. For more information, refer to the openflow vlan command.Source SuppressionSource suppression prevents received packets from being transmitted from the ingress port. Source suppression is enabled by default and is applied to all instances on the switch. If you disable source suppression, received packets can be transmitted from the ingress port.NOTE: If you disable source suppression, the following conditions apply:•Dell Networking does not recommend enabling legacy features.•You cannot enable Hybrid mode.•If you install flows using OFPP_FLOOD or OFPP_ALL, traffic loops may occur. If you disable source suppression, Dell Networking recommends that you do not install flows using theseparameters.For more information, refer to the src-suppression command.20VLAN Tag RemovalThis feature allows an interface processor (IFP) action to remove the outer VLAN tag from a packet before sending it out of the egress port. OpenFlow VLAN egress ports are now supported and flows with the strip-vlan action and an OF VLAN member port as the egress port are accepted.NOTE: This feature is supported for OF egress ports only.217 Egress QoSThe controller can provide basic egress quality of service (QoS) policies for packets and assign a priority based on match parameters specified by the controller.To enable QoS, use one flow to determine the egress port for the packet (for example, an L3 flow) and another flow such as an ACL flow to determine the egress port for all packets matching the specified parameters. Using the Set Enqueue action, the controller specifies the egress queue for received packets matching the specified parameters. You can configure queues and queue rates on individual ports or for all physical ports in the OF instance.There are four data queues available, from Q0 to Q3. The minimum rate of a queue is calculated using the default weights associated with the queue. If you use legacy CLIs, there is no change in the rate. The following table displays the default weight assigned to each queue:After the controller identifies the queues and their rates, it can install flows using the Set Enqueue command. For example, to send all packets with the source IP address 1.1.1.1 from Queue 0, regardless of the egress port, the controller creates the following flow:•Match parameters = Source IP 1.1.1.1•Action = Set Enqueue•Queue = 0Caveats•Ingress and egress QoS legacy commands are not supported.•Queues and queue rates are based on default values. You must disable the instance before configuring queue and queue rates.228 OpenFlow InterfacesThis section describes how you can apply OpenFlow to specific interfaces.•You can use the S4810, S4820T, S6000, S5000, Z9000, Z9500, or MXL switch as a Hybrid switch, allowing both OpenFlow (OF) and legacy functionality simultaneously.•By default, all ports are available for legacy functionality.•To enable OpenFlow, associate a port or virtual local area network (VLAN) to an OF instance. You can only do this when the OF instance is disabled.•OpenFlow is supported with link aggregation groups (LAGs); for example, you can configure port channel interfaces as OF ports or as members of OF VLANs.OF PortsThe following configuration example associates two ports (Te 0/7 and Te 0/31) to of-instance 1:Dell(conf)#interface tengigabitethernet 0/7Dell(conf-if-te-0/7)#of-instance 1Dell(conf-if-te-0/7)#interface tengigabitethernet 0/31Dell(conf-if-te-0/31)#of-instance 1Dell(conf-if-te-0/31)#To see the list of ports associated with an OF instance, use the show openflow of-instance command. The number displayed in parentheses is the port ID sent to the controller (for example, Te 0/7 is sent to the controller as of-port 8, as shown below).Dell#show openflow of-instance 1Instance : 2Admin State : UpOF Version : V1-3Interface Type : VlanDP Id : 00:02:74:86:7a:ff:6f:e4Forwarding Tbls : acl, mac, routeFlow map :l2, l3EchoReq interval: 15 secondsConnect interval: 15 secondsNumber of Flows : 21 (acl:21)Packets (acl) : 575600Bytes (acl) : 36838400Fail mode : secureFlow misses : copy-to-controllerController 1 : TCP, 10.11.54.186/6633, rcv/sndbuf 1000/1000, connected (equal) high-priorityController 2 : -Port List :Vlan List :Vl 200Vlan Mbr list :Fo 1/16 (209), Fo 1/20 (213), Fo 2/0 (385)23。