BFS++客户端安装手册
FRC客户端配置及使用指导手册
客户端配置及使用指导手册北京西觅亚科技有限公司一、()编程环境安装1、安装及配置环境()想要使用必须先正确的安装配置,你可以从以下网址获得该安装程序。
也可以自己在上找合适的版本。
()安装,选择安装目录。
安装过程中会出现两次安装提示。
第一次是安装,第二次是安装。
建议两个都安装在同一个文件夹中的不同文件夹中。
(不能都安装在文件夹的根目录下,和安装在同一文件夹会出错)如图所示安装,随意选择目录,只需把默认安装目录 \ 之前的目录修改即可。
安装→更改→ \ 之前目录和安装目录相同即可。
注:若无安装目录要求,可全默认设置。
无需做任何修改,两次均直接点下一步。
()安装完后配置环境变量计算机→属性→高级系统设置→高级→环境变量系统变量→新建变量。
变量值填写的安装目录(本人是 :\\)系统变量→寻找变量→编辑在变量值最后输入 \\\;(注意原来的变量值末尾有没有;号,如果没有,先输入;号再输入上面的代码)系统变量→新建变量变量值填写 \\\(注意最前面有一点)()系统变量配置完毕,检验是否配置成功运行输入(和之间有空格)若如图所示显示版本信息则说明安装和配置成功。
2、安装 ( )()可以从以下网址获取相应的安装程序,选择适合你的安装包。
()双击安装程序,根据提示进行安装。
3、安装()安装程序可以从以下网址处获得请注意下载适合自己系统的版本(2)下载后进行解压。
()将解压后的文件夹,移动到盘目录下()找到,启动。
首次启动需配置工作空间,可以直接默认或设置自己喜爱的项目存储路径。
、配置:. "". " ".. ,. "..." " " :. :. :. "".如果不能够自动更新插件时可使用手动进行更新。
注:经测试由于国内网关限制,部分插件可能无法正常更新。
可将更新失败插件下载下来,拷贝到目录下,然后再次执行更新过程,这样既可保证更新完成。
服务器安装SOP
服务器安装SOP一、安装SQL SERVER 2000 ENTERPRISE安装SQL2000数据库1.在服务器上安装数据库,需要安装SQL2000企业版,打开安装文件后,出现如下界面:2.点击【安装 SQL Server 2000 组件】,出现如下界面,然后点击【安装数据库服务器】3.点击【下一步】4.选择【本地计算机】,然后点【下一步】5.选择【创建新的SQL Server实例,或安装【客户端工具】】,然后点击【下一步】6.随意输入姓名与公司,然后点击【下一步】7.点击【是】8.选择【服务器和客户端工具】,然后点击【下一步】9.选择【默认】,然后点击【下一步】10.选择【典型】,然后点击【程序文件】后面的【浏览】与【数据文件】后面的【浏览】,将安装的路径全部修改在D盘,然后单击【下一步】11.上面选择【对每个服务使用同一帐户,自动启动SQL Server服务】,下面选择【使用本地系统帐户】,正确选择完成后,单击【下一步】12.身份验证模式需要选择为【混合模式】,然后在下面输入sa的密码,密码为:admin。
密码输入两次完成后,单击【下一步】13.单击【下一步】14.随后系统会进行自动安装并复制文件,请耐心等待15.安装完成后,点击【完成】,会自动退出安装界面安装SQL2000的SP4补丁1.点击安装文件setup.bat,出现安装界面2.单击【下一步】3.点击【是】4.单击【下一步】5.按照默认的选择,直接单击【下一步】6.将【升级Microsoft Search并应用SQL Server 2000 SP4(必需)】打上勾,然后点击【继续】7.直接点击【确定】8.直接单击【下一步】9.安装程序进行文件的复制,请耐心等待10.直接点击【确定】11.单击【完成】注:SP4补丁打完后需要重新启动服务器。
二、安装透明车间安装透明车间数据库1.运行安装包中的CJS_DB_Files_3_0,进行数据库的安装,如下图所示,点击【NEXT】2.一路【NEXT】,直到出现以下的界面,在这里可以选择安装路径。
S60 系统 FTOS 8.3.3.9 安装和操作指南说明书
FTOS Configuration Guide forthe S60 SystemFTOS 8.3.3.9Notes, 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.Information in this publication is subject to change without notice.©2013Dell Force10.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™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and V ostro™ are trademarks of Dell Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD®is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc. Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat®Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware®, Virtual SMP®, vMotion®, vCenter® and vSphere® are registered trademarks or trademarks of VMware, Inc. in the United States or other countries. IBM® is a registered trademark of International Business Machines Corporation.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.April 20131About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Information Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Configuration Fundamentals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Accessing the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25CLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Navigating CLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 The do Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Undoing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Obtaining Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Entering and Editing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Filtering show Command Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Multiple Users in Configuration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Console access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Serial console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36USB-B console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Configure a Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Access the System Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Access the C-Series and E-Series and the S60 Remotely . . . . . . . . . . . . . . . . . . . .39Access the S-Series Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Configure the Enable Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Copy Files to and from the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Save the Running-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44View Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 File System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47View command history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Upgrading and Downgrading FTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Configure Privilege Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Create a Custom Privilege Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Apply a Privilege Level to a Username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Apply a Privilege Level to a Terminal Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53|34|www.dell.com|support.dell.comConfigure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Log Messages in the Internal Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Configuration Task List for System Log Management . . . . . . . . . . . . . . . . . . . . . . . .54Disable System Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Send System Messages to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Configure a Unix System as a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Change System Logging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Display the Logging Buffer and the Logging Configuration . . . . . . . . . . . . . . . . . . . . . . .56Configure a UNIX logging facility level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Synchronize log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Enable timestamp on syslog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59File Transfer Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Configuration Task List for File Transfer Services . . . . . . . . . . . . . . . . . . . . . . . . . . .60Terminal Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Deny and Permit Access to a Terminal Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Configure Login Authentication for Terminal Lines . . . . . . . . . . . . . . . . . . . . . . . . . .63Time out of EXEC Privilege Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Telnet to Another Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Lock CONFIGURATION mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Viewing the Configuration Lock Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Recovering from a Forgotten Password on the S60 . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Recovering from a Forgotten Enable Password on the S60 . . . . . . . . . . . . . . . . . . .68Recovering from a Failed Start on the S60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .695802.1ag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Ethernet CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Maintenance Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Maintenance Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Maintenance End Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Configure CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Related Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Enable Ethernet CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Create a Maintenance Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Create a Maintenance Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Create Maintenance Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Create a Maintenance End Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Create a Maintenance Intermediate Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77MP Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Continuity Check Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Enable CCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Enable Cross-checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Loopback Message and Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Linktrace Message and Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Link Trace Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Enable CFM SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Display Ethernet CFM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .836Access Control Lists (ACL), Prefix Lists, and Route-maps. . . . . . . . . . . . . . . . . . 85 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85IP Access Control Lists (ACLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 CAM Profiling, CAM Allocation, and CAM Optimization . . . . . . . . . . . . . . . . . . . . . .86Implementing ACLs on FTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 IP Fragment Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Configure a standard IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Configure an extended IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Configuring Layer 2 and Layer 3 ACLs on an Interface . . . . . . . . . . . . . . . . . . . . . . . . .98Assign an IP ACL to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Counting ACL Hits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Configuring Ingress ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Configuring Egress ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Egress Layer 3 ACL Lookup for Control-plane IP Traffic . . . . . . . . . . . . . . . . . . . .102 Configuring ACLs to Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Applying an ACL on Loopback Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 IP Prefix Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Configuration Task List for Prefix Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 ACL Resequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Resequencing an ACL or Prefix List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Route Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Configuration Task List for Route Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1127Border Gateway Protocol IPv4 (BGPv4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 Autonomous Systems (AS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Sessions and Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Route Reflectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Confederations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 BGP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Best Path Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Local Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Multi-Exit Discriminators (MEDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129|56|www.dell.com|support.dell.comAS Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Next Hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Multiprotocol BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Implementing BGP with FTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1314-Byte AS Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132AS4 Number Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133AS Number Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135BGP4 Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Configuration Task List for BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139MBGP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180BGP Regular Expression Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Debugging BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Storing Last and Bad PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Capturing PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183PDU Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1858Bare Metal Provisioning 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196JumpStart mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Domain Name Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Switch boot and set-up behavior in JumpStart Mode . . . . . . . . . . . . . . . . . . . . . . .2009Content Addressable Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Content Addressable Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203CAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204Microcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206CAM Profiling for ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Boot Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207When to Use CAM Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Select CAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209CAM Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Test CAM Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211View CAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212View CAM-ACL settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212View CAM Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Configure IPv4Flow Sub-partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Configure Ingress Layer 2 ACL Sub-partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Return to the Default CAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218CAM Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219Applications for CAM Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219 LAG Hashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219LAG Hashing based on Bidirectional Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220CAM profile for the VLAN ACL group feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220 Troubleshoot CAM Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220 CAM Profile Mismatches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220QoS CAM Region Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22110Debugging and Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Offline diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224Running Offline Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Trace logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227 Auto Save on Crash or Rollover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228 Last restart reason (S60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228show hardware commands (S60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228Hardware watchdog timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230Buffer tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230 Deciding to tune buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Buffer tuning commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Sample buffer profile configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Multicast Buffering on the S60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236Troubleshooting packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 Displaying Drop Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Dataplane Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239Displaying Stack Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241Displaying Stack Member Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Application core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Mini core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24211Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 DHCP Packet Format and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246Assigning an IP Address using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Configure the System to be a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249|78|w w w .d e l l .c o m |s u p p o r t .d e l l .c o m Configure the Server for Automatic Address Allocation . . . . . . . . . . . . . . . . . . . . .250Specify a Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251Enable DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251Configure a Method of Hostname Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252Create Manual Binding Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Debug DHCP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253DHCP Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Configure the System to be a Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Configure the System for User Port Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255Configure Secure DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255Option 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256Drop DHCP packets on snooped VLANs only . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Dynamic ARP Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259Source Address Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26112Force10 Resilient Ring Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Ring Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Multiple FRRP Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Important FRRP Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Important FRRP Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Implementing FRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270FRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271Troubleshooting FRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Configuration Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Sample Configuration and Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27513GARP VLAN Registration Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Configuring GVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Related Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281Enabling GVRP Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281Enabling GVRP on a Layer 2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Configuring GVRP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Configuring a GARP Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28314Internet Group Management Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285IGMP Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285IGMP Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286IGMP version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286。
(售后服务)FBSD全能服务器安装手册之基础介绍篇BSD的简史
(售后服务)FBSD全能服务器安装手册之基础介绍篇BSD的简史FreeBSD全能服务器安装手册之基础介绍篇--BSD的简史有四种主要的BSD变体。
其中有三种(FreeBSD、OpenBSD和NetBSD)是完全免费的。
第四种(MacOSX)于技术上是壹种操作系统的核心,大多数人甚至不认为它是壹种BSD的变体。
要了解不同版本之间的区别,让我们先简单回顾壹下BSD的历史以便了解这些不同的版本是如何开发出来的。
今天的BSD变体是原来的AT&TUnix操作系统的开源软件版本。
实际上,这些变体均来自于加州大学伯克利分校开发的Unix。
BSD实际上是伯克利分校软件发布版的缩写字。
原来BSD代码的很大壹部分是以免费的AT&TUnix代码为基础的。
于WilliamF.Jolitz等原来的BSD开发小组的关键成员的努力之下,这个代码的最后壹部分根据开源软件许可证协议开发出来了,且且制作出了386BSD。
1993年,386BSD分裂为我们目前所知道的俩个主要版本:NetBSD和FreeBSD。
这俩个版本是根据不同的目的和目标建立起来的。
毫不奇怪,每壹个版本均有自己的历史。
第三个版本OpenBSD是于1996年推出的。
这个版本主要是为了解决其它变体中存于的壹些安全问题。
MacOSX操作系统中采用的BSD核心被人们称作Darwin(达尔文)。
它是壹个完全独立的组件。
Darwin软件本身来自于NeXT公司开发的NextStep操作系统的BSD层。
NeXT公司是史蒂夫*乔布斯于80年代离开苹果公司之后创建的。
从技术上说,MacOSX操作系统是以FreeBSD内核为基础的。
OSX10.3是以FreeBSD5.x为基础的。
然而,MacOSX已经超出了基本的BSD代码,完全是个性化设计的。
MacOSX的关键优势于于其AquaGUI(图形用户界面)。
这个图形界面能够让OSX系统像原来的MacOSX操作系统壹样运行,可是同时具有壹个高效率的BSD内核的全部优点和灵活性。
海康WEB客户端软件安装手册
B/S客户端软件安装手册杭州海康威视系统技术有限公司技术热线:400-700-59982010-06-03 Author: hu jun非常感谢您购买我公司的产品,如果您有什么疑问或需要请随时联系我们。
本手册可能包含技术上不准确的地方、或与产品功能及操作不相符的地方、或印刷错误。
我司将根据产品功能的增强而更新本手册的内容,并将定期改进或更新本手册中描述的产品或程序。
更新的内容将会在本手册的新版本中加入,恕不另行通知。
目录1.安装B/S软件 (3)2.软件使用参数配置 (9)3.正确使用IE浏览器选项设置 (11)4.卸载B/S软件 (14)1.安装B/S软件请参考以下步骤将电警BS项目安装到个人计算机上。
第一步:开始安装。
运行安装程序第二步:选择“确定”第三步:选择安装语言,点击“下一步”。
正在安装Install Wizard,请等待。
第五步:点击“下一步”。
接受许可证协议,选中“我接受”,点击“下一步”。
第七步:输入您的信息:“用户名”和“公司名称”,点击“下一步”。
选择安装路径,点击“下一步”。
第九步:安装程序,点击“安装”。
正在安装,请等待。
第十一步:安装完成,选择“完成”。
IE地址栏访问:http://localhost:8080或者http://yourIp:8080 ,即可进入软件登录界面.2.软件使用参数配置以下所有操作都在安装目录apache-tomcat-6.0.18下:2.1. 访问地址端口号修改:系统默认安装时使用8080端口,可根据自己实际需要修改apache-tomcat-6.0.18\conf\server.xml文件:<Connector port="8080"protocol="HTTP/1.1"connectionTimeout="20000"redirectPort="8443" />2.2 配置数据库连接信息,相对目录:apache-tomcat-6.0.18\ conf,打开并修改context.xml文件:username="system" //登录数据库用户名password="hulj888" //登录数据库密码url="jdbc:oracle:thin:@172.12.67.100:1521:IVMS8620" //‘172.12.67.100’为数据库服务器IP //‘IVMS8620’为数据库名称注:其它参数勿改。
Dragon 专业个人客户端安装指南说明书
Installation guide GuideDragon speech recognition Enterprise solutionFor v15 of:Dragon Professional Individual Client Installation GuideCopyrightDragon Professional Individual, Dragon Legal Individual, v15.2019 Nuance Communications, Inc.This material may not include some last-minute technical changes and/or revisions to the software. Changes are periodicallymade to the information provided here. Future versions of this material will incorporate these changes.No part of this manual or software may be reproduced in any form or by any means, including, without limitation, electronic ormechanical, such as photocopying or recording, or by any information storage and retrieval systems, without the express written consent of Nuance Communications, Inc. Specifications are subject to change without notice.End-of-life: Third-party environmentsSupport for third-party environments is only valid as long as they are supported by the corresponding vendor and might besubject to other restrictions. Contact Nuance Technical Support for details. For more information, see the documentationdelivered with the third-party product and supporting Nuance documentation.When standard support by the vendor has stopped, Nuance will continue support if an issue is specific to the Nuance solution,within the limitations of the vendor’s standard end-of-life and Nuance's policy. This means that issues that are a combination of the vendor’s component and the Nuance solution cannot be supported.Copyright © 2019 Nuance Communications, Inc. All rights reserved.Nuance, ScanSoft, the Nuance logo, the Dragon logo, Dragon, DragonBar, NaturallySpeaking, NaturallyMobile, RealSpeak,Nothing But Speech (NBS), Natural Language Technology, Select-and-Say, MouseGrid, and Vocabulary Editor are registered trademarks or trademarks of Nuance Communications, Inc. in the United States or other countries. A ll other names andtrademarks referenced herein are trademarks of Nuance Communications or their respective owners. Designations used bythird-party manufacturers and sellers to distinguish their products may be claimed as trademarks by those third-parties.DisclaimerNuance makes no warranty, express or implied, with respect to the quality, reliability, currency, accuracy, or freedom from error of this document or the product or products referred to herein and specifically disclaims any implied warranties, including, without limitation, any implied warranty of merchantability, fitness for any particular purpose, or non-infringement.Nuance disclaims all liability for any direct, indirect, incidental, consequential, special, or exemplary damages resulting from the use of the information in this document. Mention of any product not manufactured by Nuance does not constitute anendorsement by Nuance of that product.NoticeNuance Communications, Inc. is strongly committed to creating high quality voice and data management products that, whenused in conjunction with your own company’s security policies and practices, deliver an efficient and secure means of managing confidential information.Nuance believes that data security is best maintained by limiting access to various types of information to authorized users only.Although no software product can completely guarantee against security failure, Dragon s oftware contains configurablepassword features that, when used properly, provide a high degree of protection.We strongly urge current owners of Nuance products that include optional system password features to verify that these features are enabled! You can call our support line if you need assistance in setting up passwords correctly or in verifying your existingsecurity settings.Published by Nuance Communications, Inc., Burlington, Massachusetts, USAVisit us on the Web at . Links to our international web sites are shown there.1/17/20192Dragon Individual Installation Guide ContentsDragon Individual Installation Guide1 Copyright2Contents3 Chapter 1: About this guide4 About Dragon Professional Individual5Additional resources6Documentation6Interactive tutorial6Training6Support6 Chapter 2: Preparing to install Dragon7 Preparing for an installation8Storage space considerations9Dragon system requirements10 Chapter 3: Initial Installation of Dragon Professional Individual11 Install Dragon and choose the default settings12Installing Dragon on a single computer12Dragon file structure15Windows 7, Windows 8.1, and Windows 1015Accessing program files163Dragon Professional Individual Client Installation GuideChapter 1: About this guideAbout Dragon Professional Individual5Additional resources6 4Chapter1:About this guide About Dragon Professional IndividualDragon Professional Individual allows users to create reports, spreadsheets, presentations and otherdocumentation more efficiently with fast, accurate dictation and transcription. Dragon ProfessionalIndividual also includes voice commands that allow users to perform everyday tasks without using themouse or keyboard. For example, use voice commands to:l Correct and format text.l Launch applications.l Navigate in applications.l Access buttons and menus in supported programs, including Microsoft Word, CorelWordPerfect, WordPad, and moreDragon Professional Individual can be installed on each client computer manually .5Dragon Professional Individual Client Installation GuideAdditional resourcesThe following resources are available in addition to this guide to help you manage your Dragoninstallation.Documentationclick the Help icon () on theInteractive tutorialDragon Professional Individual includes an interactive tutorial with progressive simulations that help you learn Dragon skills.When you are connected to the internet, Dragon connects to a web-based interactive tutorial. If youdon't have an internet connection, the tutorial runs locally.TrainingNuance provides several Dragon training offerings, like webinars, demos, and Nuance University online training courses. For more information, s ee the Dragon Support web site.SupportThe Dragon Support web site provides many resources to assist you with your Dragon installation. For more information on Support offerings, see the Dragon Support web site at:https:///support.html6Chapter2:Preparing to install Dragon Chapter 2: Preparing to installDragonPreparing for an installation8Storage space considerations9Dragon system requirements107Dragon Professional Individual Client Installation GuidePreparing for an installationBefore installing, modifying, or upgrading Dragon Professional Individual:l Install any pending Windows updates, and then restart the computer.l Turn off or disable any antivirus software until installation is complete. Installation can sometimes trigger a false virus report.l Close all open applications.l Ensure your system meets the requirements before attempting to install Dragon Professional Individual.For more information, see “Dragon system requirements” on page 10.Installation considerationsl Administrator rights are not required to create a user profile or use the software afterinstallation. Note that if an administrator creates a user profile while logged in as anadministrator, that profile is not accessible to users with restricted privileges.l Users are permitted to create multiple profiles, provided each profile is for one person.Additional users must purchase a separate license for Dragon Professional Individual. Volumelicense agreements are available.8Chapter2:Preparing to install Dragon Storage space considerationsEach Dragon user must have his or her own user profile. This is a set of files in which Dragon storesinformation about each user’s voice, frequently-used words and phrases, optional settings, andcustom commands (if applicable). Each computer on which Dragon is installed must have enough freespace for the required user profile(s).Use the following guidelines for allocating disk space on your system. The actual amount of diskspace varies from site to site.To set the amount of data to store:1. From the DragonBar, select Tools>Administrative Settings.The Administrative Settings dialog box opens.2. Select the Disk space reserved for network archive option.For each u ser profile:l127 MB of hard disk spaceDragon periodically creates a backup copy of a u ser profile and stores the copy on the local computer.9Dragon Professional Individual Client Installation GuideDragon system requirementsDuring the installation process, the software checks that your system meets the following requirements. If they are not met, Dragon Professional Individual is not installed.10Chapter 3: Initial Installation of Dragon Professional IndividualInstall Dragon and choose the default settings12 Installing Dragon on a single computer12 Dragon file structure15 Windows 7, Windows 8.1, and Windows 1015 Accessing program files16Install Dragon and choose the default settingsInstall Dragon Professional Individual on the client computer using the downloaded installer file orinstallation DVD. If you plan to install Dragon on multiple computers, run through an initial installationbefore attempting to install Dragon from a server. Use the initial client installation to set default values for Administrative and Auto-Formatting options. You can then install Dragon Professional Individual on other computers using the same options.Notes:l You must have Windows Administrator rights to install or uninstall Dragon Professional Individual.l If you have more than one language, the installation process uses your operating system’s language, if supported. If Dragon does not support your operating system language, theinstaller runs in English. You cannot install Dragon using a language other than the primarylanguage. For example, if you install the German software on a French operating system,the installation interface is in French. If you install the German software on a Chineseoperating system, the installation interface is in English.l The installation process does not present the QuickStart option. You can enable this option in the Options dialog box after Dragon is installed. For more information, see the onlineDragon Professional Individual help.Installing Dragon on a single computer1. Run the Dragon installation file you downloaded.OrInsert the product DVD. If the installation does not start automatically, run setup.exe from theDVD.The Dragon InstallShield Wizard opens.2. Click Next to proceed to the License Agreement screen.3. Read the text of the agreement, select I accept…, and then click Next.The Customer Information screen appears.4. Enter your User Name, Organization, and the Serial Number supplied with your DVD ordownload of Dragon, and then click Next.The Region Selection screen appears.5. Select a region to install, or select All English regions to install more than one region.The region determines the accents and vocabularies available on this installation. Selecting a single region saves disk space, but users cannot create user profiles with an accent that is not included with the selected region.6. Optional: To change the installation directory, select Advanced, then click Next.The Advanced screen appears.1. Click Change…A Browse For Folder dialog box opens.2. Navigate to the folder where you want to install Dragon (or create a new folder byclicking the Make New Folder button) and then click OK.Note: By default, Dragon is installed in:C:\Program Files(x86)\Nuance\NaturallySpeaking157. Click Next to proceed to the Ready to Install the Program screen.8. Click Install.The installation process begins. It may take several minutes to install Dragon ProfessionalIndividual. At times, the progress bar may not appear to be advancing, but the installation is still proceeding internally.9. When installation of Dragon is complete, the installer displays the completion screen. ClickFinish.The Product Registration window appears.10. Choose whether to register Dragon online now or to have Dragon remind you to register inseven days, and then click OK. Registering the product provides faster access to NuanceTechnical Support.You can open Dragon using the desktop shortcut, or find Dragon in the Start menu:l Windows 7: Select Start > All Programs > Dragon.l Windows 8.1: From the Start screen, select the down arrow to show all applications, and then scroll to the right to view the Dragon applications.l Windows 10: Select Start > All apps > Dragon.Activating DragonThe first time you start Dragon, you are prompted to activate your copy of Dragon. If you do not activate, Dragon stops working after you start it five times.Dragon file structureDuring installation, Dragon creates the following default folders for application and data file storage.Note: Upgrading Dragon from an earlier version automatically relocates some directories andfiles.Windows 7, Windows 8.1, and Windows 10Dragon setup log (dgnsetup.log)C:\ProgramData\Nuance\NaturallySpeaking15\logsDragon logC:\ProgramData\Nuance\NaturallySpeaking15\logs\<Windows_User_Name> User profilesC:\ProgramData\Nuance\NaturallySpeaking15\UsersUpgrade logC:\Users\<Windows_User_Name>\AppData\Roaming\Nuance\NaturallySpeaking15 Vocabularies and acoustic modelsC:\ProgramData\Nuance\NaturallySpeaking15\DataCustom words and commandsC:\ProgramData\Nuance\NaturallySpeaking15\custom\<language>\Program filesHelpInteractive TutorialAccessing program filesYou can access the Dragon client and many associated utilities through the Start menu. Their location varies by operating system:l Windows 7: Select Start > All Programs > Dragon.l Some utilities are located inside the Dragon Tools subfolder.l Windows 8.1: From the Start screen, click the down arrow to show all applications. Scroll to find Dragon.l Windows 10: Select Start > All apps > Dragon.。
Nsight Systems安装指南 v2022.1.1 一月2022说明书
Nsight Systems Installation GuideTABLE OF CONTENTS Chapter 1. Overview (1)Chapter 2. System Requirements (3)Supported Platforms (3)CUDA Version (3)Requirements for x86_64, Power, and Arm SBSA T argets on Linux (4)x86_64 Windows T arget Device Requirements (5)Host Application Requirements (5)Chapter 3. Getting Started Guide (7)3.1. Finding the Right Package (7)3.2. Installing GUI on the Host System (8)3.3. Optional: Setting up the CLI (8)3.4. Launching the GUI (9)Nsight Systems is a statistical sampling profiler with tracing features. It is designed to work with devices and devkits based on NVIDIA Tegra SoCs (system-on-chip), Arm SBSA (server based system architecture) systems, IBM Power systems, and systems based on the x86_64 processor architecture that also include NVIDIA GPU(s). Throughout this document we will refer to the device on which profiling happens as the target, and the computer on which the user works and controls the profiling session as the host. Note that for x86_64 based systems these may be on the same device, whereas with Tegra, Arm, or IBM Power based systems they will always be separate. Furthermore, three different activities are distinguished as follows:‣Profiling — The process of collecting any performance data. A profiling session in Nsight Systems typically includes sampling and tracing.‣Sampling — The process of periodically stopping the profilee (the application under investigation during the profiling session), typically to collect backtraces (call stacks of active threads), which allows you to understand statistically how much time is spent in each function. Additionally, hardware counters can also be sampled. This process is inherently imprecise when a low number of samples have been collected.‣Tracing — The process of collecting precise information about various activities happening in the profilee or in the system. For example, profilee API execution may be traced providing the exact time and duration of a function call.Nsight Systems supports multiple generations of Tegra SoCs, NVIDIA discrete GPUs, and various CPU architectures, as well as various target and host operating systems. This documentation describes the full set of features available in any version of Nsight Systems. In the event that a feature is not available in all versions, that will be noted in the text. In general, Nsight Systems Embedded Platforms Edition indicates the package that supports Tegra processors for the embedded and automotive market and Nsight Systems Workstation Edition supports x86_64, IBM Power, and Arm server (SBSA) processors for the workstation and cluster market.Common features that are supported by Nsight Systems on most platforms include the following:‣Sampling of the profilee and collecting backtraces using multiple algorithms (such as frame pointers or DWARF data). Building top-down, bottom-up, and flat viewsOverviewas appropriate. This information helps identify performance bottlenecks in CPU-intensive code.‣Sampling or tracing system power behaviors, such as CPU frequency.‣(Only on Nsight Systems Embedded Platforms Edition)Sampling counters from Arm PMU (Performance Monitoring Unit). Information such as cache misses gets statistically correlated with function execution.‣Support for multiple windows. Users with multiple monitors can see multiple reports simultaneously, or have multiple views into the same report file.With Nsight Systems, a user could:‣Identify call paths that monopolize the CPU.‣Identify individual functions that monopolize the CPU (across different call paths).‣For Nsight Systems Embedded Platforms Edition, identify functions that have poor cache utilization.‣If platform supports CUDA, see visual representation of CUDA Runtime and Driver API calls, as well as CUDA GPU workload. Nsight Systems uses the CUDA Profiling Tools Interface (CUPTI), for more information, see: CUPTI documentation.‣If the user annotates with NVIDIA Tools Extension (NVTX), see visual representation of NVTX annotations: ranges, markers, and thread names.‣For Windows targets, see visual representation of D3D12: which API calls are being made on the CPU, graphic frames, stutter analysis, as well as GPU workloads(command lists and debug ranges).‣For x86_64 targets, see visual representation of Vulkan: which API calls are being made on the CPU, graphic frames, stutter analysis, as well as Vulkan GPU workloads (command buffers and debug ranges).Nsight Systems supports multiple platforms. For simplicity, stentryink of these as Nsight Systems Embedded Platforms Edition and Nsight Systems Workstation Edition, where Nsight Systems Workstation Edition supports desktops, workstations, and clusters with x86_64, IBM Power, and Arm SBSA CPUs on Linux and Windows OSs, while Nsight Systems Embedded Platforms Edition supports NVIDIA Tegra products for the embedded and gaming space on Linux for Tegra and QNX OSs.Supported PlatformsDepending on your OS, different GPUs are supportedL4T (Linux for Tegra)‣Jetson AGX Xavier‣Jetson TX2‣Jetson TX2i‣Jetson TX‣Jetson Nano‣Jetson Xavier NXx86_64, IBM Power (from Power 9), or Arm SBSA‣NVIDIA GPU architectures starting with Pascal‣OS (64 bit only)‣Ubuntu 18.04 and 20.04‣CentOS and RedHat Enterprise Linux 7.4+ with kernel version 3.10.0-693 or later.‣Windows 10, 11CUDA Version‣Nsight Systems supports CUDA 10.0, 10.1, 10.2, and 11.X for most platforms‣Nsight Systems on Arm SBSA supports 10.2 and 11.X Note that CUDA version and driver version must be compatible.CUDA Version Driver minimum version11.045010.2440.3010.1418.3910.0410.48From CUDA 11.X on, any driver from 450 on will be supported, although new features introduced in more recent drivers will not be available.For information about which drivers were specifically released with each toolkit, see CUDA Toolkit Release Notes - Major Component VersionsRequirements for x86_64, Power, and Arm SBSAT argets on LinuxWhen attaching to x86_64, Power, or Arm SBSA Linux-based target from the GUI on the host, the connection is established through SSH.Use of Linux Perf: To collect thread scheduling data and IP (instruction pointer) samples, the Linux operating system's perf_event_paranoid level must be 2 or less. Use the following command to check:If the output is >2, then do the following to temporarily adjust the paranoid level (note that this has to be done after each reboot):To make the change permanent, use the following command:Kernel version: To collect thread scheduling data and IP (instruction pointer) samples and backtraces, the kernel version must be:‣ 3.10.0-693 or later for CentOS and RedHat Enterprise Linux 7.4+‣ 4.3 or greater for all other distros including UbuntuTo check the version number of the kernel on a target device, run the following command on the device:Note that only CentOS, RedHat, and Ubuntu distros are tested/confirmed to work correctly.glibc version: To check the glibc version on a target device, run the following command:Nsight Systems requires glibc 2.17 or more recent.CUDA: See above for supported CUDA versions in this release. Use the deviceQuery command to determine the CUDA driver and runtime versions on the system. the deviceQuery command is available in the CUDA SDK. It is normally installed at:Only pure 64-bit environments are supported. In other words, 32-bit systems or 32-bit processes running within a 64-bit environment are not supported.Nsight Systems requires write permission to the /var/lock directory on the target system.Docker: See Collecting Data within a Docker section of Profiling in a Docker on Linux Devices for more information.x86_64 Windows T arget Device RequirementsDX12 Requires:‣Windows 10 with NVIDIA Driver 411.63 or higher for DX12 trace‣Windows 10 April 2018 Update (version 1803, AKA Redstone 4) with NVIDIA Driver 411.63 or higher for DirectX Ray Tracing, and tracing DX12 Copy command queues.Host Application RequirementsThe Nsight Systems host application runs on the following host platforms:‣Windows 10, Windows Server 2019. Only 64-bit versions are supported.‣Linux Ubuntu 14.04 and higher are known to work, running on other modern distributions should be possible as well. Only 64-bit versions are supported.‣OS X 10.10 "Yosemite" and higher.3.1. Finding the Right PackageNsight Systems is available for multiple targets and multiple host OSs. To choose the right package, first consider the target system to be analyzed.‣For Tegra target systems, select Nsight Systems for Tegra available as part of NVIDIA JetPack SDK.‣For x86_64, IBM Power target systems, or Arm SBSA select from the target packages from Nsight Systems for Workstations, available from https:/// nsight-systems. This web release will always contain the latest and greatest Nsight Systems features.‣The x86_64, IBM Power, and Arm SBSA target versions of Nsight Systems are also available in the CUDA Toolkit.Each package is limited to one architecture. For example, Tegra packages do not contain support for profiling x86 targets, and x86 packages do not contain support for profiling Tegra targets.After choosing an appropriate target version, select the package corresponding to the host OS, the OS on the system where results will be viewed. These packages are inthe form of common installer types: .msi for Windows; .run, .rpm, and .deb for x86 Linux; .deb and .rpm for Linux on IBM Power; and .dmg for the macOS installer. Note: the IBM Power and Arm SBSA packages do not have a GUI for visualization of the result. If you wish to visualize your result, please download and install the GUI available for macOS, x86_64 Linux, or Windows systems.Tegra packages‣Windows host – Install .msi on Windows machine. Enables remote access to Tegra device for profiling.‣Linux host – Install .run on Linux system. Enables remote access to Tegra device for profiling.‣macOS host – Install .dmg on macOS machine. Enables remote access to Tegra device for profiling.Getting Started Guidex86_64 packages‣Windows host – Install .msi on Windows machine. Enables remote access to Linux x86_64 or Windows devices for profiling as well as running on local system.‣Linux host – Install .run, .rpm, or .deb on Linux system. Enables remote access to Linux x86_64 or Windows devices for profiling or running collection on localhost.‣Linux CLI only – The Linux CLI is shipped in all x86 packages, but if you just want the CLI, we have a package for that. Install .deb on Linux system. Enables only CLI collection, report can be imported or opened in x86_64 host.‣macOS host – Install .dmg on macOS machine. Enables remote access to Linux x86_64 device for profiling.IBM Power packages‣Power CLI only - The IBM Power support does not include a host GUI. Install .deb or .rpm on your Power system. Enables only CLI collection, report can be imported or opened in GUI on any supported host platform.Arm SBSA packages‣Arm SBSA CLI only - Arm SBSA support does not include a host GUI. Install .deb or .rpm on your Arm SBSA system. Enables only CLI collection, report can beimported or opened in GUI on any supported host platform.3.2. Installing GUI on the Host SystemCopy the appropriate file to your host system in a directory where you have write and execute permissions. Run the install file, accept the EULA, and Nsight Systems will install on your system.On Linux, there are special options to enable automated installation. Running the installer with the --accept flag will automatically accept the EULA, running withthe --accept flag and the --quiet flag will automatically accept the EULA without printing to stdout. Running with --quiet without --accept will display an error. The installation will create a Host directory for this host and a Target directory for each target this Nsight Systems package supports.All binaries needed to collect data on a target device will be installed on the target by the host on first connection to the device. There is no need to install the package on the target device.If installing from the CUDA Toolkit, see the CUDA Toolkit documentation.3.3. Optional: Setting up the CLIAll Nsight Systems targets can be profiled using the CLI. IBM Power and Arm SBSA targets can only be profiled using the CLI. The CLI is especially helpful when scripts are used to run unattended collections or when access to the target system via ssh is not possible. In particular, this can be used to enable collection in a Docker container.Getting Started Guide Installation Guide v2022.1.1 | 9The CLI can be found in the Target directory of the Nsight Systems installation. Users who want to install the CLI as a standalone tool can do so by copying the files within the Target directory to the location of their choice.If you wish to run the CLI without root (recommended mode) you will want to install in a directory where you have full access.Once you have the CLI set up, you can use the nsys status -e command to check your environment.~$ nsys status -e Sampling Environment Check Linux Kernel Paranoid Level = 1: OK Linux Distribution = Ubuntu Linux Kernel Version = 4.15.0-109-generic: OK Linux perf_event_open syscall available: OK Sampling trigger event available: OK Intel(c) Last Branch Record support: Available Sampling Environment: OKThis status check allows you to ensure that the system requirements for CPU sampling using Nsight Systems are met in your local environment. If the Sampling Environment is not OK, you will still be able to run various trace operations.Intel(c) Last Branch Record allows tools, including Nsight Systems to use hardware to quickly get limited stack information. Nsight Systems will use this method for stack resolution by default if available.For information about changing these environment settings, see System Requirements section in the Installation Guide. For information about changing the backtrace method,see Profiling from the CLI in the User Guide.To get started using the CLI, run nsys --help for a list of options or see Profiling Applications from the CLI in the User Guide for full documentation.3.4. Launching the GUIDepending on your OS, Nsight Systems will have installed an icon on your host desktop that you can use to launch the GUI. To launch the GUI directly, run the nsight-sys executable in the Host sub-directory of your installation.。
Bosch Security Systems 软件手册 AM18-Q0635说明书
Bosch Security Systems
软件手册
目录 | zh 5
37 37 37 37 37 37 38 39 39 39 39 39 39 39 39 39 40 40 40 41 41 41
42 42 42 42 42 42 42 42 42 42 43 44 45 45
AM18-Q0635 | v5.6 | 2013.01
摄像机浏览器界面
NIN-832 FW5.7
zh 软件手册
摄像机浏览器界面
目录
1 1.1 1.2 1.2.1 1.3
浏览器连接 系统要求 建立连接 摄像机中的密码保护 受保护的网络
2
系统概述
2.1
实况页面
2.2
录像
2.3
设置
3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.1.9 3.1.10 3.1.11 3.2 3.2.1 3.2.2 3.2.3 3.2.4
设置
Bosch Security Systems
软件手册
目录 | zh 3
12 12 13 13 13
14 14 14 14
15 15 15 16 17 18 19 20 20 20 20 20 21 22 22 23 23 24
26 26 27
AM18-Q0635 | v5.6 | 2013.01
网络 网络访问 自动 IP 分配 IP V4 地址 IP V6 地址 DNS 服务器地址 视频传输 TCP 速率控制 HTTP 浏览器端口 HTTPS 浏览器端口 RCP+ 端口 1756 Telnet 支持 接口模式 ETH 网络 MSS [ 字节 ] iSCSI MSS [ 字节 ] 网络 MTU [ 字节 ] 启用 DynDNS 提供商 主机名称 用户名 密码 立即强制注册 通知邮件 状态 高级 SNMP
FreeBSD安装图解
FreeBSD安装图解今天我们来安装下FreeBSD,FreeBSD在性能上是很优异的,据说网易的服务器用的就是他。
其实网上也有很多资料的,但看过之后都觉得很不全面,所以才写了这个教程。
废话少说,为了便于截图我们使用了VMWare。
先从网站上下载光盘iso。
我一般不从官网下,那个比较慢。
推荐用台湾各个大学的服务器。
我这里用的义守大学的.tw/里面有很多软件,打开FreeBSD下载就行了。
现在最新版是7.1.我们还是选择7.0的安装。
截图一:速度还行。
安装好DeamonTools虚拟光驱(安装过程中切换CD)。
用VMWare直接加载影响也可。
不过无法切换。
开始安装:1.在VMWare中新建一个虚拟机,操作系统选择“其他-》FreeBSD”其它选项默认。
设置CD-ROM为虚拟光驱的位置。
将cd1光盘映像加载到虚拟光驱中。
截图二要慢,但为了切换方便还是用Deamon。
截图三:安装提示。
认美国,下一步。
截图四。
4.接着出现sysinstall的主菜单。
第一项标准,第二项快速,第三项自定义,第四个是安装完以后的配置,其他的一些说明文档等。
我们选择第三项自定义。
截图五。
5.安装选项。
第三项第四项是分区选项、第五项软件选择、第六项安装媒介选择、第七项确认执行安装。
在这几个菜单中可以随时按Esc取消切换出来。
截图六。
6.FreeBSD的分区和一般的Linux不太一样。
先要划分出一块FreeBSD专用空间称作Slice。
然后再在这块Slice里分区(分区叫做Label)。
我们选择Partition进入,如果有多块硬盘还会有硬盘选择的窗口。
我这里直接进入,如图:硬盘名字ad0,按C来创建一块Slice,空间全部用掉就行。
然后会提示Slice类型,默认165,ok,设置完如下图。
按Q结束,按U取消操作。
截图7、8、9、10.7.接着会弹出安装启动管理选项,多系统选择“BootMgr”,只装Freebsd就选第二个。
选完之后回到图六的菜单,在选择第四项Label,如图。
FreeBsd_8.2_x64系统安装与web环境搭建
FreeBsd_8.2_x64系统安装与web环境搭建网海过客目录FreeBsd_8.2_x64系统安装与web环境搭建 (1)一、FreeBsd 操作系统安装 (3)1.1、光驱引导,选择默认启动模式,输入回车 (3)1.2、选择国家,选择中国(china) (3)1.3、选择键盘,直接选择OK (4)1.4、选择自定义(Custom)安装 (4)1.5、选择分区(Partition) (5)1.6、选择标准(Standard)引导管理器 (6)1.7、选择标签(Label),创建FreeBsd分区 (6)1.8、选择安装包,选择最小化(Minimal)安装 (7)1.9、选择安装介质,选择CD/DVD (9)1.10、选择提交(Commit) (10)1.11、设置root密码 (11)1.12、添加wheel用户 (12)1.13、设置时区 (13)1.14、配置IP (15)1.15、启用sshd (17)1.16、完成安装,重启系统。
(18)二、添加国内ports更新源 (18)三、Vpn服务器 (18)3.1、mpd5 软件包安装 (18)3.2、修改mpd配置文件 (19)3.3、创建vpn账号 (19)3.4、添加自启动vpn服务 (19)3.5、启动vpn服务器 (20)3.6、查看vpn端口 (20)3.7、添加vpn日志功能 (20)四、编译内核支持NAT (20)4.1、修改内核配置文件 (20)4.2、编译安装内核 (21)4.3、添加自启动服务 (21)4.4、添加ipfw日志功能 (21)五、Vsftpd服务器 (22)5.1、Vsftpd软件包安装 (22)5.2、修改vsftpd配置文件 (22)5.3、创建FTP虚拟用户 (22)5.4、添加自启动vsftpd服务 (24)5.5、添加vsftpd ssl登录功能 (24)5.6、启动Vftpd (24)5.7、查看vsftpd 端口 (24)5.8、添加vsftpd日志 (25)六、Ipfw防火墙 (25)6.1、添加ipfw脚本 (25)6.2、Ipfw常用命令 (26)Nginx+Php+Mysql环境 (26)目录说明 (26)配置文件 (26)启动文件 (27)七、nginx安装 (27)八、mysql 安装 (27)8.1、添加mysql组和mysql用户 (27)8.2、编译与安装 (28)8.3、mysql目录权限设置 (28)8.4、添加mysql配置文件 (28)九、php安装 (28)9.1、安装GD相关软件包 (29)9.2、安装PHP相关软件包 (30)十、常用命令与问题? (32)十一、Freebsd学习资料 (33)一、FreeBsd 操作系统安装1.1、光驱引导,选择默认启动模式,输入回车1.2、选择国家,选择中国(china)1.3、选择键盘,直接选择OK1.4、选择自定义(Custom)安装1.5、选择分区(Partition)输入A,使用整个磁盘,输入Q完成1.6、选择标准(Standard)引导管理器1.7、选择标签(Label),创建FreeBsd分区使用C创建分区大小和分区目录,可根据需求创建分区。
容错服务器FT4500 Linux 安装手册
容错服务器ftServer4500RedHat Linux 5系统安装&配置简明手册(Hite V1-2010)一、 安装预览安装介质Stratus ftServer System Software (ftSSS) for the Linux Operating System CD/DVD 7.04Red Hat Enterprise Linux 5.4 Server or Advanced Platform DVD or CDs安装前检测确认机器已正确上架安装,接通双模块电源,连接好USB键盘、鼠标和VGA显示器。
断开机器与其他外部设备的连接,如果外部存储、备份设备。
确认机器没有安装第三方非兼容性硬件设备。
只保留每个CPU/IO的Slot 0内SAS硬盘,其余硬盘必须全部取出。
二、启动系统并修改BIOS参数启动机器,当光驱LED灯闪烁时,插入光盘ftSSS 7.04 DVD Disc。
系统开始启动,按下F2键进入BIOS配置界面(需等待两分钟左右)。
A、在ftServer BIOS主配置界面,选择Server->Monitoring Configuration->OS Boot Monitoring,使用键盘{+}号改变值为Disabled,然后按Esc键返回BIOS主配置界面;B、选择Advanced->Option ROM Scan Monitoring,将Embedded PXE#1 和 #2值改为Disabled,然后按Esc键返回BIOS主配置界面;C、选择Boot,用上下方向键和{+}键选择USB CDROM移至启动列表最顶端。
D、按下F10键,保存设置并退出三、系统开始安装Stratus ftSys 图标显示并提示你选择安装方式,显示器出现Boot:时,按下Enter 键选择默认安装。
如果选择自定义安装请查阅官方英文文档。
安装程序提示一个错误消息(Unable to download the kickstart file…),选择OK并按Enter键,安装继续。
NETGEAR Insight App 安装指南说明书
安装指南4. 要检查从交换机到您连接的已通电设备的端口连接,请执行以下操作:• 确保以太网线已正确插入。
• 检查交换机上每个端口的左侧 LED。
左侧端口 LED 呈绿色常亮,表示与已通电设备的连接有效;呈绿色闪烁,表示此端口正在处理流量。
3. 配置交换机1. 在您的移动设备或平板电脑上,连接到交换机所在的同一网络。
2. 打开 NETGEAR Insight app 并登录您的帐户。
3. 请将您的移动设备连接到交换机所连接的接入点的 WiFi 网络。
您必须使用本地 WiFi 访问以进行初始配置。
在完成初始配置并找到交换机后,若交换机已连接至互联网,您将能够使用云访问。
4. 在您的移动设备上下载 NETGEAR Insight app。
5. 轻触LOG IN(登录)并输入您的凭据。
6. 单击右上角的+号以新建网络/位置。
7. 请为您的网络命名,并指定适用于添加到此网络中的所有设备的设备管理密码。
NETGEAR Insight 网管8 端口千兆以太网智能云交换机(含 2 个 SFP 光纤端口)(GC110) 8 端口千兆以太网 PoE 智能云交换机(含 2 个 SFP 光纤端口)(GC110P)包装内容• 交换机型号 GC110 或 GC110P• 电源适配器(因地区而异)• 用于墙式安装的壁挂螺钉• 用于桌面安装的四个橡胶脚垫• 安装指南• 超五类 (Cat 5e) 扁平以太网线1. 通过 NETGEAR Insight App 注册使用 NETGEAR Insight App 创建网络拓扑,安装、配置和监控交换机,注册交换机,激活保修以及访问支持。
1. 在您的 iOS 或 Android 移动设备或平板电脑上,访问 app 商店,搜索并下载最新版 NETGEAR Insight app。
2. 打开 NETGEAR Insight app。
3. 如果尚未设置 NETGEAR 帐户,轻触CREATE NETGEAR ACCOUNT(创建NETGEAR帐户)并按照界面说明操作。
丛文录音服务器安装操作手册说明书
丛文录音服务器安装操作手册2016年1月版权说明本手册版权归深圳市丛文安全电子有限公司所有。
保留一切版权。
除了版权法允许的使用方法之外,未经事先许可,任何人不得复制、改编或翻译。
保证说明本手册所含之内容如有改变,恕不另行通知。
深圳市丛文安全电子有限公司对由于本手册的错误而引起的损害不承担责任,对由于提供或使用本手册而随带发生的损害亦不承担责任。
商标说明丛文®是深圳市丛文安全电子有限公司的注册商标。
CONWIN®是深圳市丛文安全电子有限公司的注册商标。
简介目录第1章系统功能概述 (2)1.1简介 (2)1.2功能特点 (2)1.3产品型号 (2)1.4系统结构及流程图 (2)1.5录音服务器安装流程图 (3)第2章安装录音服务器 (4)2.1安装环境 (4)硬件环境 (4)软件环境 (4)2.2硬件板卡安装 (4)硬件安装 (4)录音服务器2线/4线板卡接线方法 (4)录音服务器8线板卡接线方法 (8)2.3软件安装 (10)2.4卸载 (15)第3章录音服务器应用 (16)3.1系统功能 (16)系统设置 (16)录音设置 (16)查看语音卡安装及录音情况 (19)系统登陆与注销 (20)登陆密码管理 (21)3.2查看信息资料 (21)录音记录管理 (21)站点信息 (22)查看系统错误信息 (23)第4章报警中心启用录音服务器设置 (24)4.1启用录音服务器 (24)4.2录音并关联警情 (24)自动拨打电话关联警情 (24)手动关联相关警情 (26)查看相关的报警 (27)导出录音文件 (27)播放录音文件 (27)第5章售后服务 (29)第6章加密锁安装及升级方法 (30)简介第1章 系统功能概述1.1 简介录音服务器应用于接警中心领域,通过联网报警中心软件拨打用户电话,减少手动拨打出现的出错几率并与用户确警的电话进行全程录音,同时录音文件会与当时发生的警情自动相互关联,以备日后在查看警情的同时播放录音文件,为报警中心与公安机关留下关键有力的证据。
BFSS(摆渡)使用说明书
BFSS双机文件同步系统使用说明书1.功能说明●通过usb传输线(目前采用BAFO7313)在内网服务器和外网服务器之间传输文件;●采用WinUSB架构,支持Windows XP、Windows2003、Windows Vista操作系统;●支持usb2.0协议,实验室环境下平均传输速度在10MB/s至15MB/s之间;●支持双向传输;●通过文件夹监控方式支持文件自动传输;●支持文件类型过滤和文件大小过滤,支持任意类型和任意大小的文件;●支持文件夹传输;●支持文件正确性校验(MD5码校验);●支持传输完成后对源文件的处理,如备份或删除;●有详细的日志记录2.安装说明1)安装BFSS服务程序前,保证目标机器内BFSS服务处于停止状态或BFSS服务已近被删除。
查看方法是在Windows服务中查询NAV BFSS。
2)安装WinUSB驱动:执行安装光盘下drive文件夹下的Microsoft WinUsbInstall-v1.0.exe。
3)安装BAFO7313驱动:插入USB传输线,再提示查找驱动时选择自己查找驱动,驱动在安装光盘下drive文件夹下EasyTransfer USB cable Driver文件夹内4)执行安装光盘下的setup.exe,按照提示完成安装。
5)安装完成后会自动注册BFSS服务,成功注册后可在Windows服务中看到NA VBFSS。
若注册未成功参照4.1。
3.使用说明BFSS服务随操作系统自动启动,一般不需要人为干预。
若要修改BFSS服务默认配置,启动“开始\程序\NewAutoVideo\BFSS\配置管理”。
如图所示。
1)启动服务/停止服务:启动或停止BFSS服务。
若按钮可用表示当BFSS服务未成功注册。
2)保存配置:保存BFSS服务默认配置,BFSS服务下次启动时生效。
3)应用配置:保存BFSS服务默认配置并立即生效。
4)查看日志:查看BFSS服务当天日志。
若要查看更多日志,请进入安装位置的Log文件下查看。
BFSS(摆渡)使用说明书
BFSS双机文件同步系统使用说明书1.功能说明●通过usb传输线(目前采用BAFO7313)在内网服务器和外网服务器之间传输文件;●采用WinUSB架构,支持Windows XP、Windows2003、Windows Vista操作系统;●支持usb2.0协议,实验室环境下平均传输速度在10MB/s至15MB/s之间;●支持双向传输;●通过文件夹监控方式支持文件自动传输;●支持文件类型过滤和文件大小过滤,支持任意类型和任意大小的文件;●支持文件夹传输;●支持文件正确性校验(MD5码校验);●支持传输完成后对源文件的处理,如备份或删除;●有详细的日志记录2.安装说明1)安装BFSS服务程序前,保证目标机器内BFSS服务处于停止状态或BFSS服务已近被删除。
查看方法是在Windows服务中查询NAV BFSS。
2)安装WinUSB驱动:执行安装光盘下drive文件夹下的Microsoft WinUsbInstall-v1.0.exe。
3)安装BAFO7313驱动:插入USB传输线,再提示查找驱动时选择自己查找驱动,驱动在安装光盘下drive文件夹下EasyTransfer USB cable Driver文件夹内4)执行安装光盘下的setup.exe,按照提示完成安装。
5)安装完成后会自动注册BFSS服务,成功注册后可在Windows服务中看到NA VBFSS。
若注册未成功参照4.1。
3.使用说明BFSS服务随操作系统自动启动,一般不需要人为干预。
若要修改BFSS服务默认配置,启动“开始\程序\NewAutoVideo\BFSS\配置管理”。
如图所示。
1)启动服务/停止服务:启动或停止BFSS服务。
若按钮可用表示当BFSS服务未成功注册。
2)保存配置:保存BFSS服务默认配置,BFSS服务下次启动时生效。
3)应用配置:保存BFSS服务默认配置并立即生效。
4)查看日志:查看BFSS服务当天日志。
若要查看更多日志,请进入安装位置的Log文件下查看。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
一﹑概述 (2)
二﹑Oracle客户端安装 (2)
三﹑Web-Key的安装 (10)
四﹑BFS++程序安装 (13)
4.1﹑映射安装程序 (13)
4.2﹑注册控件 (14)
4.3﹑创建快捷方式 (14)
一﹑概述
BFS++客户端安装大分为三个大的步骤:Oracle数据库客户端安装、wibu-key加密狗的安装和BFS++程序客户端安装。
二﹑Oracle客户端安装
1.点“开始”—>“运行”,在运行里输入\\16.16.166.3\输入用户名:bfs 和密码bfs 然后回车,如下图:
双击安装目录中的‘setup.exe’,打开欢迎界面,点击‘下一步’,则出现文件定位界(见图1):
(图1)
在来源下的路径中输入安装文件路径(一般默认就可以),目标下的路径输入要安装的位置,名称按默认值,无需改变。
2.点击‘下一步’,稍侯片刻,出现安装产品选择界面(见图2),选择Oracle 9i Client 9.2.0.1.0。
(图2)
3.点击‘下一步’,出现安装类型选择窗口(见图3),选择‘运行时’。
(图3)
4.点击‘下一步’,稍侯片刻出现摘要窗口,点击‘安装’按纽,系统便开始正式安装Oracle(见图4)。
(图4)
安装一段时间后会出现下面的图:(见图5)
(图5)
安装一段时间后,会出现要求插入第二张磁盘的提示(见图6),我们把1为成2,选择安装路径为第二张磁盘,点‘确定’按纽,则安装过程继续。
(图6)
一段时间后,会出现要求插入第三张磁盘的提示(见图7),我们同上面的做法一样,将2
改为3,点‘确定’按纽,则安装过程继续。
(图7)
一段时间后,会出现是否使用目录服务的窗口(见图8),选择‘不,我要自己创建目录服务’。
(图8)
点击‘下一步’,出现数据库版本选择提问窗口(见图9),选择‘Oralce8i或更高版本数据库或服务’。
(图9)
点击‘下一步’,出现服务名输入窗口(图10),输入服务器数据库全局数据库名,如bfs。
图10
点击‘下一步’,默认网络协议为TCP协议。
见(图11)
(图11)
点击‘下一步’,出现提示输入主机名窗口(见图12),输入服务器主机名或服务器IP地址,使用默认端口1521。
(图12)
点击‘下一步’,出现测试窗口(见图13),选择‘是,进行测试’。
(图13)
点击‘下一步’,如果测试的用户名和密码不正确,则出现图14的提示,遇到这种情况点更改登录,输入用户名:scott 密码tiger 进行测试
(图14)
(图15)点击“确定”,会出现如下界面:(图16)
(图16)
点击‘下一步’,出现提示输入网络服务名的窗口,按默认即可。
点击‘下一步’,默认设置,点击‘下一步’,默认,最后点击‘完成’。
点击‘退出’,安装Oralce全部结束。
三﹑Web-Key的安装
点“开始”—>“运行”,在运行里输入\\16.16.166.3\回车,如下图:
双击”WKDU-Int”会出现如下界面:
点击”Next”,会出现如下界面
点击”Next”,会出现如下界面
点击”Next”,会出现如下界面
点击”Next”,会出现如下界面
点击”Next”,会出现如下界面
点击”Finish”,即完成webui-key的安装
1.2.3.webui-key的设置
1.2.3.1.点击”开始”->”设置”->”控制面板”,进入控制面板双击”wibu-key”
会出现如下界面,然后进行如下配置.在设置完后点击应用即可.
然后我们要去contents下去做测试,我们双击contents下的network,如果能搜索到USB接口说明安装成功
这样Wibu_key即设置完成。
四﹑BFS++程序安装
4.1﹑映射安装程序
点开始—>运行输入\\16.16.166.3\回车,
点右键出现以下画面,选择映射网络驱动器
一般情况下我们要把映射盘符改为P盘并且选中‘登陆时新连接’(见图12),点击‘完成’
按纽
这样我们的映射安装程序就安装完成了。
4.2﹑注册控件
系统使用到的几个控件需要注册,我们可以在映射的P或T盘目录下找到一个‘BFS++注册’的文件,双击这个文件,进行控件注册。
4.3﹑创建快捷方式
在P盘目录下找到文件‘BFS++正式环境’,右键点击‘发送到桌面快捷方式’,创建运行程序到桌面即可。