WWB6_QUICKSTART_v1_0
Redhat 6.5基于网络安装服务器配置
概述本文以Redhat6.5为基础，通过配置网络安装服务器，实现Redhat Linux的网络安装。
主要用到的软件（服务）有DHCP,TFTP,NFS,Kickstart等。
本文只列出具体步骤，不含原理说明。
1. 基础配置1.1 更改IP地址[root@localhost ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth0[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0DEVICE=eth0HWADDR=08:00:27:53:44:fbTYPE=EthernetUUID=82affeef-922e-40b2-b89f-a5df8e9fa236ONBOOT=yesNM_CONTROLLED=yesBOOTPROTO=noneIPADDR=192.168.7.30NETMASK=255.255.255.0GATEWAY=192.168.7.1IPV6INIT=noUSERCTL=no[root@localhost ~]# ifup eth0Active connection state: activatedActive connection path: /org/freedesktop/NetworkManager/ActiveConnection/11.2 更改hostnme[root@localhost ~]# vi /etc/sysconfig/network[root@redhatnis ~]# cat /etc/sysconfig/networkNETWORKING=yesHOSTNAME=redhatnis[root@localhost ~]# vi /etc/hosts[root@localhost ~]# cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6192.168.7.30 redhatnis1.3 关闭SELINUX及防火墙（iptables）[root@localhost ~]# vi /etc/selinux/config[root@redhatnis ~]# cat /etc/selinux/config |grep disa# d isabled - SELinux is fully disabled.SELINUX=disabled[root@localhost ~]# chkconfig |grep iptaiptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off[root@localhost ~]# chkconfig --level 2345 iptables off[root@localhost ~]# shutdown -ry 02. 软件安装2.1 挂载安装光盘[root@redhatnis ~]# mount /dev/sr0 /mntmount: block device /dev/sr0 is write-protected, mounting read-only[root@redhatnis ~]# df -hFilesystem Size Used Avail Use% Mounted on/dev/mapper/vg_root-lv_root 20G 6.2G 12G 35% /tmpfs 940M 72K 940M 1% /dev/shm/dev/sda1 485M 39M 421M 9% /boot/dev/sr0 3.6G 3.6G 0 100% /mnt2.2 配置YUM源[root@redhatnis ~]# cd /etc/yum.repos.d[root@redhatnisyum.repos.d]# vi installmedia.repo[root@redhatnisyum.repos.d]# cat installmedia.repo[InstallMedia]name=Red Hat Enterprise Linux 6.5baseurl=file:///mnt/Serverenabled=1gpgcheck=0[root@redhatnisyum.repos.d]# yum listLoaded plugins: product-id, refresh-packagekit, security, subscription-managerThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.InstallMedia| 3.9 kB 00:00 ...Installed PackagesConsoleKit.x86_64 0.4.1-3.el6 @anaconda-RedHatEnterpriseLinux-201311111358.x86_64/6.52.3 安装所需软件[root@redhatnis ~]# yum install -y -q xinetdtftptftp-server ftp vsftpddhcpnfs-utilsThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.3. 配置DHCP Server[root@redhatnis ~]# cd /etc/dhcp[root@redhatnisdhcp]# vi dhcpd.conf[root@redhatnisdhcp]# cat dhcpd.conf## DHCP Server Configuration file.# see /usr/share/doc/dhcp*/dhcpd.conf.sample# see 'man 5 dhcpd.conf'#allow booting;allow bootp;#Boot 所需文件filename "pxelinux.0";#TFTP服务器IPnext-server 192.168.7.30;subnet 192.168.7.0 netmask 255.255.255.0{option subnet-mask 255.255.255.0;#IP地址范围range 192.168.7.31 192.168.7.100;default-lease-time 21600;max-lease-time 43200;}[root@redhatnisdhcp]# service dhcpd startStarting dhcpd: [ OK ][root@redhatnisdhcp]# chkconfig --level 345 dhcpd on[root@redhatnisdhcp]# chkconfig |grep dhcpddhcpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off4. 通过FTP（vsftpd）方式上传ISO镜像[root@redhatnis ~]# cd /etc/vsftpd/[root@redhatnisvsftpd]# vi ftpusers[root@redhatnisvsftpd]# cat ftpusers |grep root#root[root@redhatnisvsftpd]# vi user_list[root@redhatnisvsftpd]# cat user_list |grep root#root[root@redhatnis ~]# service vsftpd startStarting vsftpd for vsftpd: [ OK ][root@redhatnis ~]# chkconfig --level 345 vsftpd on此处上传ISO镜像[root@redhatnis ~]# ll /tmp |grep iso-rw-r--r-- 1 root root 3853516800 Feb 16 08:40 rhel-server-6.5-x86_64-dvd.iso5. 配置NFS[root@redhatnis ~]# mkdir /iso[root@redhatnis ~]# mv /tmp/rhel-server-6.5-x86_64-dvd.iso /iso[root@redhatnis ~]# vi /etc/exports[root@redhatnis ~]# cat /etc/exports/iso *(ro)/mnt *(ro)[root@redhatnis ~]# service rpcbind statusrpcbind (pid 931) is running...[root@redhatnis ~]# service rpcidmapd statusrpc.idmapd (pid 1435) is running...[root@redhatnis ~]# service nfs startStarting NFS services: [ OK ]Starting NFS quotas: [ OK ]Starting NFS mountd: [ OK ] Starting NFS daemon: [ OK ] Starting RPC idmapd: [ OK ] [root@redhatnis ~]# showmount -eExport list for redhatnis:/mnt */iso *[root@redhatnis ~]# chkconfig --level 345 nfs on[root@redhatnis ~]# chkconfig |grep nfsnfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off6. 配置TFTP Server[root@redhatnis ~]# mkdir /tftpboot[root@redhatnis ~]# vi /etc/xinetd.d/tftp[root@redhatnis ~]# cat /etc/xinetd.d/tftp# default: off# description: The tftp server serves files using the trivial file transfer \# p rotocol. The tftp protocol is often used to boot diskless \# w orkstations, download configuration files to network-aware printers, \# a nd to start the installation process for some operating systems.service tftp{socket_type = dgramprotocol = udpwait = yesuser = rootserver = /usr/sbin/in.tftpdserver_args = -s /tftpbootdisable = noper_source = 11cps = 100 2flags = IPv4}7. 复制相关文件[root@redhatnis ~]# mount -t iso9660 -o loop,ro /iso/rhel-server-6.5-x86_64-dvd.iso /mnt [root@redhatnis ~]# cp -pr /mnt/images /iso[root@redhatnis ~]# cp -pr /mnt/Packages/syslinux-4.02-8.el6.x86_64.rpm /iso[root@redhatnis ~]# ll /isototal 3764068dr-xr-xr-x 3 root root 4096 Nov 12 2013 images-rw-r--r-- 1 root root 3853516800 Feb 16 14:10 rhel-server-6.5-x86_64-dvd.iso-r--r--r-- 1 root root 879224 Jan 4 2013 syslinux-4.02-8.el6.x86_64.rpm[root@redhatnis ~]# ll /iso/images/total 185548-r--r--r-- 1 root root 380928 Nov 12 2013 efiboot.img-r--r--r-- 1 root root 37976064 Nov 12 2013 efidisk.img-r--r--r-- 1 root root 145731584 Nov 12 2013 install.img-r--r--r-- 1 root root 5898240 Nov 12 2013 product.img[root@redhatnis ~]# cd /iso[root@redhatnisiso]# rpm2cpio syslinux-4.02-8.el6.x86_64.rpm |cpio -dimv[root@redhatnisiso]# lsimages rhel-server-6.5-x86_64-dvd.iso syslinux-4.02-8.el6.x86_64.rpm usr[root@redhatnisiso]# cp ./usr/share/syslinux/pxelinux.0 /tftpboot[root@redhatnisiso]# cp ./images/pxeboot/{vmlinuz,initrd.img} /tftpboot[root@redhatnisiso]# cd /tftpboot/[root@redhatnistftpboot]# cp /boot/grub/splash.xpm.gz ./8. 创建default文件[root@redhatnistftpboot]# mkdirpxelinux.cfg[root@redhatnistftpboot]# cd pxelinux.cfg[root@redhatnispxelinux.cfg]# cp /mnt/isolinux/isolinux.cfg ./default[root@redhatnispxelinux.cfg]# vi default[root@redhatnispxelinux.cfg]# cat defaultdefault linuxprompt 1timeout 60menu background splash.jpgmenu title Welcome to Red Hat Enterprise Linux 6.5!menu color border 0 #ffffffff #00000000menu color sel 7 #ffffffff #ff000000menu color title 0 #ffffffff #00000000menu color tabmsg 0 #ffffffff #00000000menu color unsel 0 #ffffffff #00000000menu color hotsel 0 #ff000000 #ffffffffmenu color hotkey 7 #ffffffff #ff000000menu color scrollbar 0 #ffffffff #00000000label linuxmenu label ^Install or upgrade an existing systemmenu defaultkernel vmlinuzappend ks=nfs:192.168.7.30:/iso/ks.cfginitrd=initrd.imglabel vesamenu label Install system with ^basic video driverkernel vmlinuzappend initrd=initrd.imgxdriver=vesanomodesetlabel rescuemenu label ^Rescue installed systemkernel vmlinuzappend initrd=initrd.img rescuelabel localmenu label Boot from ^local drivelocalboot 0xfffflabel memtest86menu label ^Memory testkernel memtestappend -[root@redhatnispxelinux.cfg]# cd ..[root@redhatnistftpboot]# lltotal 36676-r--r--r-- 1 root root 33383449 Feb 16 15:07 initrd.img-rw-r--r-- 1 root root 26828 Feb 16 14:59 pxelinux.0drwxr-xr-x 2 root root 4096 Feb 16 15:04 pxelinux.cfg-rw-r--r-- 1 root root 1341 Feb 16 15:06 splash.xpm.gz-r-xr-xr-x 1 root root 4128944 Feb 16 15:07 vmlinuz9. 创建Kickstart 配置文件系统安装完后会在/root下生产anaconda-ks.cfg文件，也可以通过Kickstart Configurator 软件来配置生成该文件。
华三路由器软件升级指南
操作快速指南 Quick Start
MV440/MV420读码器测试快速指南说明：本文档只用于初次使用MV420/440的使用者基本设定参考，在“调整”模式下测试读码能力。
更多参数设定及运行模式的说明请参考用户手册。
硬件准备：作为读码调整应用，最少需要准备的邮件设备如下：1：读码器本体（MV420/440）：2：电缆：M16接口电缆（接口中最粗大那个）用于供电M12-RJ45电缆（用于连接电脑网口）3：电源：24V电源，电流在250mA或以上PC端软件准备：1：IE浏览器2：JAVA插件（通过IE浏览器设置中可以看到是否有装）若没有安装JAVA，可以在随设备的光盘中找到JAVA安装程序。
硬件连接：1：将M16电缆中红色的接24V电源正，蓝色的接24V电源负。
2：将M16电缆接口连接到MV420M12-RJ45电缆一头接MV420，一头接电脑网口。
PC端设置：1a：将PC中网络设置端TCP/IP协议中的IP地址设置为如图：附注：出厂的读码器一般设置为：192.168.0.XX，PC端的IP地址只有和该地址最后两位设置不同即可。
（0～255的任意其他数）。
2：查看读码器内置IP地址。
常规出厂会设置为192.168.0.42，也可能会是其他IP地址，可以通过软件“Primary Setup Tool”查看，附带的CD中有该软件的安装程序。
打开该程序：选择Network->Browser, 或按快捷键。
（选中Assign IP parameter之前的单选框也可以对该读写器IP地址进行改写）开始调试：1：进入IE浏览器，在地址栏中键入该读写器的IP地址，比如：192.168.0.42. 2：可以看到如下界面，说明读码器和PC连接正常。
在界面右上角，可以选择语言，支持中文简体界面。
3：点击读码器图标，进入后续调试界面4：在界面中，点击左侧第一项：调整（Adjustment）,进入如下图形界面4：此时，在界面右上半部分可以看到成像的结果5：首先设置曝光为自动曝光（一般应用场合自动模式即可）6：调整镜头：对MV420，请用附带的六角改锥将镜头保护罩上的3个小螺丝松开。
linux启动引导过程(greb)
linux grub 引导启动过程详解2008-01-08 17:18这几天看了很多文档,算是对linux的启动过程有了比较细致的了解.网上有很多文章谈到这方面的内容,但总觉得没有一篇完全的解析linux启动的细节,下面是我小弟在学习的过程中总结出来的一些东东.这个是完整的linux启动过程,不涉及内核,但是我觉得比较详细哦.(由于本人比较懒,这一段是从网上抄的)机器加电启动后,BIOS开始检测系统参数,如内存的大小,日期和时间,磁盘设备以及这些磁盘设备用来引导的顺序,通常情况下，BIOS都是被配置成首先检查软驱或者光驱（或两者都检查），然后再尝试从硬盘引导。
如果在这些可移动的设备中，没有找到可引导的介质，那么BIOS通常是转向第一块硬盘最初的几个扇区，寻找用于装载操作系统的指令。
装载操作系统的这个程序就是boot loader. linux里面的boot loader通常是lilo或者grub,从Red Hat Linux 7.2起，GRUB( GRand Unified Bootloader)取代LILO成为了默认的启动装载程序。
那么启动的时候grub是如何被载入的呢grub有几个重要的文件,stage1,stage2,有的时候需要stage1.5.这些文件一般都在/boot/grub文件夹下面.grub被载入通常包括以下几个步骤:1. 装载基本的引导装载程序(stage1),stage1很小,网上说是512字节,但是在我的系统上用 du -b /boot/grub/stage1 显示的是1024个字节,不知道是不是grub版本不同的缘故还是我理解有误.stage1通常位于主引导扇区里面,对于硬盘就是MBR 了,stage1的主要功能就是装载第二引导程序(stage2).这主要是归结于在主引导扇区中没有足够的空间用于其他东西了,我用的是grub 0.93,stage2文件的大小是 107520 bit.2. 装载第二引导装载程序(stage2),这第二引导装载程序实际上是引出更高级的功能,以允许用户装载入一个特定的操作系统。
cloudera-quickstart安装使用总结
一、cloudera-quickstart的安装（1）在官网上下载一种版本的cloudera-quickstart（有三种不同版本分别对应的可以在三种不同的虚拟机上运行）（2）根据下载的不同版本下载虚拟机（VMware or VisualBox）（3）以VisualBox虚拟机为例则可以运行cloudera-quickstar的基本配置如下：RAM内存至少为8G虚拟处理器分配为两个（4）虚拟机配置好以后，不用先安装Linux操作系统。
因为cloudera-qiuckstart对包括操作系统在内的都已经打好包了，所以只需将下载的cloudera-quickstart的虚拟磁盘（比如：cloudera-quickstart-vm-5.1.0-1-virtualbox-disk1.vmdk）添加到虚拟机控制器的位置然后启动虚拟机中的该的系统，cloudera-quickstart所包含的一整套系统就可以使用了，这就是quickstart 版本的方便之处。
具体操作如下：进入配置好的虚拟机页面，选择“存储”，然后点下图红圈标注的位置会弹出来如下对话框，选择“使用现有的虚拟盘”然后再找到你下载的cloudera-quickstart的虚拟磁盘所在的位置，点击“打开”则虚拟磁盘就被添加进去了，如下图所示最后启动该系统对于win7系统上如果安装VMware虚拟机有可能在启动虚拟磁盘时会提示出现内部错误（如下图所示），此时只需要以管理员身份运行虚拟机就可以解决该问题了。
二、cloudera manager控制页面启动虚拟机进入cloudera-quickstart操作系统桌面后，会自动跳出浏览器上cloudera的控制平台。
但有可能会出现接口连接不上服务器的状况，如下图所示：此时有两种解决方法：（1）点击桌面上的“Launch cloudera manager”(2)打开Linux的控制终端输入：“sudo/home/cloudera/cloudera-manager--force”一般我比较喜欢采取第二种方法。
vm虚拟机使用kickstart自动安装linux教程
在vm虚拟机中用kickstart自动安装linux教程学习完kickstart，想尝试下在VM虚拟机中实现无人值守安装linux系统。
通过U盘来引导。
1 准备kickstart文件下面是kickstart文件：# System timezonetimezone Asia/Shanghaiignoredisk --drives=sdb1bootloader --driveorder=sdabootloader --location=mbr --driveorder=sda,sdb --append="nomodesetcrashkernel=auto rhgb quiet"# Network information设置IP、网关等network --bootproto=static --device=eth0 --gateway=192.168.4.1 --ip=192.168.4.199 --hostname= --nameserver=219.141.136.10 --netmask=255.255.255.0 --onboot=on --noipv6 #network --bootproto=static --device=eth1 --ip=10.12.1.240 --netmask=255.255.255.0 --onboot=on --noipv6# System bootloader configuration# Clear the Master Boot Recordzerombr# Partition clearing informationclearpart --all --initlabel# Disk partitioning informationpart /boot --fstype="ext4" --size=200part swap --fstype="swap" --size=8192part / --fstype="ext4" --grow --size=1user --name=javadev%packages@base@basic-desktop@chinese-support@compat-libraries@console-internet@debugging@fonts@graphical-admin-tools @legacy-unix@network-tools@performance@scientific@system-admin-tools@system-management-snmp compat-openmpicompat-openmpi-psmdumphttpdftpiptrafjwhoislogwatchmuttnet-snmp-perlnet-snmp-pythonnmaprrdtoolrrdtoolrwhosystem-config-kickstart tcp_wrapperstelnettftplm_sensorstigervnc-serveryum-plugin-downloadonly -authconfig-gtk-b43-fwcutter-cas-control-center-extra-crash-crash-gcore-command-crash-trace-command-elfutils-elinks-eog-avahi-gdm-plugin-fingerprint -gnome-applets-gnome-disk-utility-gnome-media-gnome-packagekit-gnome-packagekit-gnome-vfs2-smb-gok-ibus-table-cangjie-ibus-table-erbi-ibus-table-wubi-ltrace-mdadm-microcode_ctl-nano-openssh-askpass-oprofile-orca-pcmciautils-perf-powertop-pulseaudio-module-gconf -pulseaudio-module-x11-rfkill-scl-utils-seekwatcher-setuptool-smartmontools-sos-system-config-users-units-valgrind-vconfig-vino-wireless-tools-words%post# Install the yum repository configuration files#post you will need to add it here/bin/echo "nameserver 8.8.8.8" > /etc/resolv.conf#下文为自动执行脚本，自动安装puppet、拷贝oracle安装程序等，如果不需要可注释cd /tmp/bin/rpm -ivh "/pub/epel/6/x86_64/epel-release-6-8.noarch.rp m"/bin/rpm -ivh "/el/6/products/x86_64/puppetlabs-release-6-7.no arch.rpm"/usr/bin/wget"/rpmforge-release/rpmforge-release-0.5.3-1.el6. rf.x86_64.rpm"/bin/rpm -ivh ./rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm/bin/mkdir -p /home/software /tmp/mnt/bin/mount /dev/sdb2 /tmp/mnt#/bin/cp -prf /tmp/mnt/*.rpm /home/software//bin/rpm -ivh /home/software/*.rpm/bin/rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6上述文件保存为yufa199.cfg2 制作可引导U盘另外制作一个可引导的U盘，具体过程如下：准备工作：1.准备一个大于8G的U盘2.Linux系统在vm下手动安装一个也可以将U盘插入系统，然后格式U盘, 将U盘格式化为2个分区,一个为msdos分区, 500M空间, 另一个为ext2分区,余下的所有空间,分2个区的主要原因是因为,一个盘符做引导,另外一个盘符放置iso文件, iso文件较大,如果都放在一个分区下, 重做格式化还需要再次拷贝iso文件耗时长.完整配置方法:Command actiona toggle a bootable flag#设置启动盘b edit bsddisklabelc toggle the dos compatibility flagd delete a partition #删除分区l list known partition typesm print this menun add a new partition #添加分区o create a new empty DOS partition tablep print the partition table #打印分区信息q quit without saving changess create a new empty Sun disklabelt change a partition's system id #修改分区系统IDu change display/entry unitsv verify the partition tablew write table to disk and exit #写入并退出x extra functionality (experts only)Command (m for help): n #添加一个新分区Command actione extendedp primary partition (1-4)p #分区格式为主分区Partition number (1-4): 1 #第一个分区First cylinder (1-14786, default 1):Using default value 1Last cylinder, +cylinders or +size{K,M,G} (1-14786, default 14786): +500M #设置分区大小为500MCommand (m for help): n #再添加一个分区Command actione extendedp primary partition (1-4)p至此U盘启动就已经完成,将U盘接入windows系统，可以看到500M的空间，将上文中的yufa199文件拷贝到该U盘（第一个分区）。
ModscanQuickStart
Modscan32 Quick-Start GuideThis is a brief "quick start" guide to using Modscan32 to communicate with the Controlotron flowmeter using the Modbus protocol. Modscan32 is distributed by Win-Tech, / as a trial version and it function for a limited time. If you find this software useful, it may be purchased directly from them.Note the device address of the Modbus card and the communication parameters of the Modbus network. This differs from the serial communications of the flowmeter as selected from the front panel.When Modscan32 starts, the following screen is displayed:Step 1 – Establish a connection. Select 'Connection' from the pull-down menu and choose the COM port which has been wired to the Modbus network or directly to the flowmeter.For this example, we have chosen COM1 at 9600 baud, 8 data bits, no parity and 1 stop bit.Step 2 – Select the Device ID, Address (of the first Modbus register), and Length (number of registers to query). Note: The default length of 100 will almost always produce a communications error. The length parameter must be set to no more than the number of registers available.Once Modscan32 is put on-line, the status message "Device NOT CONNECTED!" will no longer be displayed. These messages appear just above the displayed registers.If the status message is "Exception Response" or "Invalid Response," this indicates that the flowmeter does not understand the read command. Double-check the address range, length, and type of registers being examined.There are four types of Modbus registers available from the pull-down menu, "01: Coil Status", "02: Input Status", "03: Holding Register", and "04: Input Register". We are concerned with the last two types: Holding Registers for values such as flow rate and temperature, and Input Registers for Date, Time, Signal Strength, Aeration, and Alarms. Other data may be examined by referring to the Modbus Register Map for each individual flowmeter. Each one may reflect a unique configuration.To examine Holding Registers, select either "Floating Pt. or "Swapped FP" depending ifyour meter is configured for "Word Normal" or "Word Reversed." ModScan32 will thencombine two adjacent 16-bit registers to form a single 32-bit IEEE format floating point number.Corresponding values for Flow Rate, Raw Flow, etc will appear as odd-numbered register pairs:The other set of registers we concern ourselves with is Input Registers for Date, Time, Signal Strength, Aeration, and Alarms. Select "04: Input Register" from the pull-down menu. Click on "Hex" from the data format selection:Next, reduce the number of registers to no more than the number of available Input Registers for your meter. If the length specified exceeds the number of actual registers, no data will be displayed.ASCII values are packed in adjacent bytes. In this example, "SiteName" is shown in registers 30001 thru 30004, which is 48 42 31 20 20 20 20 20 or "HB1 ".The alarms are returned as ASCII hex digits. In this example, the alarms are at 30011 thru 30012, which is 37 46 46 20, or "7FF ". This hex value indicates status alarms (inverted), bit encoded as follows:0x001 - spacing0x002 - Zeromatic channel fault0x004 - empty0x008 - hi/lo flowrate0x010 - fault0x020 - aeration or turbulence (GAS)0x040 - memory0x080 - makeup0x100 - interface0x200 - pig detect0x400 - channel/path enableA condition of 7FF indicates no alarms. These four bytes of "3746 4620" may also be examined for decoding of alarms as follows:1 2 3 47FF - 37 46 46 20 - Good6xx 36 xx xx 20 - Channel disabled (x = don't care)xEx xx 45 xx 20 - Fault indicatedxCx xx 43 xx 20 - Fault, aeration indicatedxxE xx xx 45 20 - Spacing indicatorxxC xx xx 43 20 - Zeromatc channel faultxxB xx xx 42 20 - Empty Pipexx7 xx xx 37 20 - hi/lo flowrateThe date this example is contained in registers 30005 thru 30006, which is 33 30 43 34, 30C4 hex is encoded as follows:date_of_month + (month * 32) + ((year - 1980) * 512). In this example, 30C4 or 12484 represents June 4th, 2004.The time field is the number of minutes past midnight, contained in registers 30007 thru 30008 (first three bytes only). In this example, 33 43 33, 3C3 hex is 963 minutes past the hour, or 16:03 (4:03pm).。
RHEL6 PXE DHCP FTP Kickstart无人值守安装RHCE实验室环境
RHEL6+PXE+DHCP+FTP+Kickstart无人值守安装RHCE实验室环境原理和概念：1.1 什么是PXE严格来说，PXE 并不是一种安装方式，而是一种引导的方式。
进行PXE 安装的必要条件是要安装的计算机中包含一个PXE 支持的网卡（NIC），即网卡中必须要有PXE Client。
PXE （Pre-boot Execution Environment）协议使计算机可以通过网络启动。
协议分为client 和server 端，PXE client 在网卡的ROM 中，当计算机引导时，BIOS 把PXE client 调入内存执行，由PXE client 将放置在远端的文件通过网络下载到本地运行。
运行PXE 协议需要设置DHCP 服务器和TFTP 服务器。
DHCP 服务器用来给PXE client（将要安装系统的主机）分配一个IP 地址，由于是给PXE client 分配IP 地址，所以在配置DHCP 服务器时需要增加相应的PXE 设置。
此外，在PXE client 的ROM 中，已经存在了TFTP Client。
PXE Client 通过TFTP 协议到TFTP Server 上下载所需的文件。
1.2 什么是KickStartKickStart是一种无人职守安装方式。
KickStart的工作原理是通过记录典型的安装过程中所需人工干预填写的各种参数，并生成一个名为ks.cfg的文件；在其后的安装过程中（不只局限于生成KickStart安装文件的机器）当出现要求填写参数的情况时，安装程序会首先去查找KickStart生成的文件，当找到合适的参数时，就采用找到的参数，当没有找到合适的参数时，才需要安装者手工干预。
这样，如果KickStart文件涵盖了安装过程中出现的所有需要填写的参数时，安装者完全可以只告诉安装程序从何处取ks.cfg文件，然后去忙自己的事情。
等安装完毕，安装程序会根据ks.cfg中设置的重启选项来重启系统，并结束安装。
SERVOSTAR 640 670 (S640 S670) Quickstart Guide
SERVOSTAR640/670(S640/S670) Quickstart GuideVersion12.2014Keep all manuals as aproduct component duringthe life span of the product.Pass all manuals to futureusers/owners of the product.PreparationThe CD-ROM delivered with the servo amplifier contains all the manuals in PDF for-mat and the setup software.Insert the CD-ROM into your PC.Autostart function activated:A window with the start screen opens.Autostart function deactivated:Click START(task bar),then on Run.Enterx:\index.htm or x:\autorun.exe(x=CD drive letter).Click OK.The start screen opens.Install Setup SoftwareMultilanguage CD-ROM:On the start screen you find a link to the setup software: Install Setup Software SERVOSTAR S400/S600Release_.__Build__Click it and follow the instructions from here.North American CD-ROM:Click the product name,then select Install Software from the next screen.Follow the instructions from here.DocumentsYou need Acrobat Reader to read the PDFs(installation link on every screen). Multilanguage CD-ROM:Select the language version on the start screen of theCD-ROM.Click"Servo Drives"in the column"Technical Manuals".A table with links to all manuals appears.North American CD-ROM:Click on any manual title automatically brings up the document.Mechanical and Electrical Installation of the Servo Amplifier1.Unpack servo amplifier and accessories2.Keep the instructions manual ready(print if necessary)3.Observe safety instructions in the manuals4.Mount the servo amplifier as described in the instructions manual5.Wire the servo amplifier as described in the instructions manual or apply the mini-mum wiring for drive test(see next page)2Minimum Wiring for Drive Operation3Motor-FeedbackM o t o r -P o w e rMotorPower ON24V DC +-EnablePower2318345X4X324V ON15Choke FilterBrake Res.This wiring does not fulfill anyrequirements to safety or functionality of your application,it just shows the required wiring for drive testing without load.Connectl Connect the interface cable to a serial interface on your PC and to the serial in-terface X6of the servo B to serial converter can be used optionally. l Switch on the24V logic power supply for the servo amplifier.l Wait about30the front display of the servo amplifier displays thecurrent rating(e.g.for40amps).If the supply voltage isswitched on,too,a leading P is displayed(e.g.for Power,40amps).If a fault code()or a warning()or a status message("."or"_" or"E"or"S")appears in the display,you will find the description and hints for trouble shooting in the instructions manual.If there is fault,fix the problem.Double-Click the Drive.exe icon on your Windows desktop to start thesoftware.You can work offline or online withDrive.exe.Work ONLINE now.Select the interfacewhere the servo amplifier is connected to. 4The software tries to com-municate with the drive and to upload the param-eters.If it's not success-ful,you receive this error message:Frequent causes:-wrong interface chosen-wrong connector chosen at the servo amplifier -interface is used by another software-24V auxiliary voltage for the servo amplifier not working -interface cable broken or wrong wiringClick OK to remove the error message.Detect and remove the error source.Restart the software.If communication works,parameters are transmitted from the servoam-plifier to the computer.Then you see the start screen.Make sure,that the amplifier is disabled (Input HW-En-able connector X3pin 15must be 0V or open)!5Important Screen ElementsHelp FunctionThe Online-Help gives detailed information to all parameters the servo amplifier can work with.Key F1Starts Online Help for the actual screen page. Menu Bar?/Online HTML Help Starts Online Help with table of contents.Tool BarSave to EEPROM,required if you changed parameters.Reset(coldstart),required if you changed important configuration parameters.Operation Mode,use Digital Velocity mode fordrive testing.Disable and Enable of the amplifier's outputstage via software.Status Bar6Basic SetupOn the start screen click"Basic Setup"button.Regen Resistor:Select"external"max.Regen Power:Fill in the power of the connected regen resistor.max.Mains Voltage:Select the nominal mains AC voltageMains Phase Missing:You can select either warning"n05"or error"F19"in case of phase loss.The setting"F19"disables the output stage,"n05"is just a message. Units:Acceleration,Velocity,PositionSelect usable units for your application referring to the moved load.Leave all other fields unchanged.Click OK.On the start screen,click"Motor"button.7Motor(synchronous)Press function key F12(Software Disable).Motor Type:Select Synchronous Motor.If you use a linear motor or an induction motor,please contact our support department.Number-Name:Click the list to start uploading the motor parameter table,which is stored in the servo amplifier.Search and select the connected motor.If your motor is not listed,please contact our support department.Leave all other fields unchanged.Click OK.8If your motor has a built-in brake,click Yes,otherwise"No".If Software Enable is active,a warning ap-pears.You can proceed,but after the ampli-fier is restarted,you must check whether theholding brake configuration is correct.Click OK.Parameters are uploaded to the ampli-fier's RAM now(takes some seconds).When this is done,you have to acceptthe changed configuration with"Yes"orto discard the changes in the appearingscreen.If you click"Yes",the parameters aresaved in the EEPROM and the ampli-fier makes a coldstart(reset).Thistakes some seconds.On the start screen,click"Feedback"button.9FeedbackPress F12(SW disable)before changingfeedback parameters.Feedback Type:Select the feedback type used.Leave all other fields unchanged.If Software Enable is active,a warningappears.The configuration changecannot be performed.Click OK on thewarnings,press F12(SW disable)and start the Feedback procedureagain.If everything was ok,the same procedure(parameter upload)that has been describedfor the motor selection starts.If you click"Yes",the parameters are savedin the EEPROM and the amplifier makes acoldstart(reset).This takes some seconds. 10Save Parameters and RestartYou are going to finish setup and you have changed several basic parameters. Depending on the parameters you changed,two possible reactions can occur: Configuration parameters changedA warning appears,that you have to restart the amplifier.This is called"coldstart". Click"YES".The parameters are saved to the amplifier's EEPROM automatically and a reset command restarts the amplifier(takes a few seconds).For example,this happens after motor or feedback selection.Other parameters changedNo warning appears.Parameters are saved in the volatile RAM only.Save the parameters to the EEPROM of the servo amplifier manually by clicking thesymbol in the tool bar.A coldstart of the amplifier is not necessary.Reset the amplifierYou can reset the amplifier manually(e.g.in case of an error).Click icon11Jogging the Motor(Speed Control)Be aware that the actual position of the load permits the subsequent moving operations.The axis could move to the hardware limit-switch or the mechanical stop.Make sure that a jerk or a fast acceleration of the load cannot cause any damage.l Switch on the power supply for the drive.l Hardware-Enable:+24VDC to Enable[connector X3pin15].l Software-Enable:Click the"Enable"button on the start screen or use key Now,the front display shows an E and the cur-rent rating(e.g.for Enable,40amps)l Click the icon"Oscilloscope":12l Select Service-Mode"Speed F6",then click"Parameter"buttonl Enter a safe speed.The sign defines the direction of movement.Observe the"safe reduced speed"requirements for your application!l Click OK.l Start the service function("Start"button or press F6).Click OK on the warning notice.Opmode is switched to"0"and the output stage is enabled automatically.The symbol's color changes to green as long as the function is active.l The function is active until you click the"Stop"button or press F9.l The output stage can be disabled by pressing function key F12.13StatusActual warnings and errors are listed on the Status screen,which can be accessed on the start screen by clicking the"Status"button.This button monitors the current status of the amplifier and can appear with different text.The Reset button can be used to clear some actual error messages.A description of errors/warnings can be found in the online help.Now you have setup and tested the basic functions of the drive successfully.Additional Setup ParametersObserve the safety instructions in the manuals when you change additional parameters.Detailed information on all setup functions can be found in the Online Help syste-mand and the integrated command reference.14MonitorClick the icon"Monitor"The Monitor screen shows allimportant electrical and mechan-ical actual values.DocumentsYou need access to these documents(located on the product CD-ROM,you can download the latest editions from our website):l Instructions Manual(Assembly,Installation,Setup)l CANopen communication profileDepending on the installed expansion card,you need one of these documents:l PROFIBUS DP communication profilel DeviceNet communication profilel SERCOS communication profilel EtherCAT communication profileYou need Acrobat Reader to read the PDFs,an installation link is on every screen of the product CD-ROM.15Technical changes which improve the performance of the equipment may be made without prior notice!All rights reserved.No part of this work may be reproduced in any form(by photoco-pying,microfilm or any other method)or stored,processed,copied or distributed by electronic means without the written permission of Kollmorgen Europe GmbH. Kollmorgen Customer Support-North AmericaE-Mail**********************Tel.:+1-540-633-3545Fax:+1-540-639-4162Kollmorgen Customer Support-EuropeE-Mail**********************Tel.:+49(0)2102-9394-0Fax:+49(0)2102-9394-3110。
红帽企业版Linux 6安装指南
红帽企业版 Linux 6安装指南一、简介 二、启动选项 三、无盘(GRUB)安装 四、准备服务器 五、使用 Kickstart 无人值守安装 六、无人值守安装的完整示例 七、故障示例分析 一、简介： 本文翻译自 Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US。
闲来无事、游手好闲，因此特将该文件的第28至33章翻译出来。
内容较多，若翻译有误望大家指点。
在翻译原文的过程中会对原文做一些补充说明，望大家可以忍受。
本手册描述了如何启动红帽企业版 Linux 6安装程序(anaconda)以及如何安装红帽企业版6操作系统，同时还 涵盖了高级安装方式，如 Kickstart 无人值守安装、VNC 安装。
最后还将对常见问题进行分析说明。
二、Boot Options(启动选项): 2.1 概述 红帽企业 Linux 6安装程序为管理员提供了一系列的功能与选项，要使用这些选项你可以在 boot:提示符后 输入 linux option。
在 RHEL6的图形安装中，如果要得到 boot:提示符，可以按 Esc 键。
如何你希望在此指定多个安装选项， 那么在选项之间需要一个空格分隔。
linux option1 option2 option3 ... 如： 2.2 RHEL6启动菜单简单选项： 语言 显示分辨率 接口类型(图形、字符) 安装方式 网络设置 # 语言： 为安装程序及系统设置语言， 使用 lang 选项指定语言(采用的是 ISO 标准语言编码， 中文为 zh)， 使用 keymap 选项指定键盘类型。
如：使用 ISO 编码 el_GR 和 gr 分别指定希腊语言与系列键盘linux lang=el_GR keymap=gr# 分辨率： 输入 resolution=setting 选项设置显示分辨率，如设置分辨率为：1024*768linux resolution=1024*768# 文本模式： 输入 linux text 进入文本安装模式 使用 display=ip:0允许将安装图形转发到远程主机，在远程主机你需要执行 xhost +remotehostname 命令 # 升级 anaconda(红帽安装程序的名称)输入 linux updates 升级新版本的 anaconda 安装程序linux updates= 通过网络加载 anaconda 升级程序，后跟 URL 地址# 指定安装方式 首先，开机出现安装界面后可以按 Tab 键，将显示以>vmlinuz initrd=initrd.img 开始的附加界面，在此我们 可以输入 askmethod 回车， >vmlinuz initrd=initrd.img askmethod 几个下一步之后安装程序会询问我们安装方式。
Shure WWB Wireless Workbench Quick Start Guide
WWBWireless Workbench Quick Start GuideThe quick setup guide for Shure Wireless Workbench software.Version: 5.0 (2023-F)Table of ContentsWWB Wireless Workbench Quick Start Guide3 Overview3 Step 1: Download Wireless Workbench 3 Step 2: Connect Shure devices to your network 3 Automatic IP addressing 4 Manual IP addressing 4 Step 3: Configure the firewall 4 Mac 5Windows 5 Step 4: Open Wireless Workbench 5 Step 5: Verify your network connection 6 Network troubleshooting 6 Step 6: Coordinate frequencies7 Step 7: Set transmitter frequencies using IR sync7 Step 8: Monitor and control your system8 Step 9: Learn more 8••••••••••WWBWireless Workbench Quick Start GuideOverviewWireless Workbench (WWB) is free device management, coordination, and monitoring software that helps RF coordinators, touring, broadcast, theater and house of worship audio professionals manage everything from pre-show planning to frequency coordination, live channel monitoring, and post-performance analysis.Note: This is a quick setup guide for Wireless Workbench. For the full instruction manual, see the Wireless Workbench help page .By bringing together networkable and non-networkable Shure and third-party devices combined with RF data, this software al-lows you to quickly manage and coordinate your wireless devices so you can focus on mixing. Workbench facilitates quick and easy configuration, operation, and monitoring of your wireless devices, and is compatible with the following Shure networked systems:QLX-D Digital Wireless System ULX-D Digital Wireless System Axient Wireless Management Network PSM 1000 Personal Monitoring System UHF-R Wireless System Axient Digital Wireless System SLX-D Digital Wireless System ResourcesFor detailed help with Wireless Workbench, visit the Wireless Workbench Help page . To find the same help content within Wireless Workbench, press F1 or go to Help > Wireless Workbench help system .Other online resources:Workbench release notesWorkbench video tutorialsAnswers to frequently asked questionsStep 1: Download Wireless WorkbenchTo download Wireless Workbench, visit the Wireless Workbench page . Launch the installer and follow the steps to complete the installation.Note: You must be logged in to your computer as an administrator to install Wireless Workbench.®®®®®®®1.2.3.1.2.3.4.Step 2: Connect Shure devices to your networkWireless Workbench communicates with connected devices through an Ethernet network. Each device on the network must have a unique and valid IP address assigned to communicate with other devices on the network. IP addresses can be as-signed automatically by a computer, switch, or router that employs DHCP addressing.Automatic IP addressingTo take advantage of DHCP addressing, Shure devices have an automatic IP mode for quick and easy setup. If specific IP ad-dresses need to be assigned, the IP mode can be set to manual.Connect your computer and devices using CAT5 or better Ethernet cable. For multiple device systems, adding a routeror switch as shown in the diagram is recommended. Avoid using cross-over cables for any connections.Turn on your computer and all devices connected to the network.For each device, enter the network menu and set the IP address mode to Automatic to enable automatic IP addressing.Manual IP addressingAs an alternative to automatic IP addressing, a manual addressing option is available if you want to assign specific IP address-es to your devices.Connect your computer and devices using CAT5 or better Ethernet cable. For multiple device systems, adding a routeror switch as shown in the diagram is recommended. Avoid using cross-over cables for any connections.Turn on your computer and all devices connected to the network.For each device, enter the network menu and set the IP address mode to Manual.Assign unique IP addresses to each device. Assign the identical subnet mask to all devices.Step 3: Configure the firewallIf you have a firewall protecting your computer, you'll need to grant access to Wireless Workbench. Log in to your computer as an administrator to gain full access to your firewall settings or contact your IT administrator for help.For third-party firewall software, refer to the manufacturer's instructions for granting access to each instance of an application (there may be more than one instance).Note: If you receive an alert pop-up that blocks Wireless Workbench, check the boxes to allow access for all networks (Domain Networks, Private Networks, and Public Networks).1.2.3.◦◦1.2.◦◦1.2.MacFrom System Preferences , access firewall settings.If the firewall is on, open the Firewall Options to view the applications that request network access.For each of the following applications, select Automatically allow built-in software to receive incoming connections andAutomatically allow downloaded signed software to receive incoming connections :snetDameonWireless Workbench.appWindowsOpen the Windows Firewall on your computer.Place a check next to each instance of an application--there may be more than one instance--for the following applica-tions to allow access to Domain Networks, Private Networks, and Public Networks:snetDameonwireless workbenchRefer to the Microsoft Support website if you need more help with firewall configuration.Step 4: Open Wireless WorkbenchIn the welcome screen, set up a network connection and choose to create or open a show.Choose a network: Select the network that closely matches the numbering order and format of the IP address yourdevice is connected to. The first few numbers of the address shown in Wireless Workbench will match the first fewnumbers of the device's IP address.Tip: If you're not sure which IP address to choose, go to the network menu on the device to see what IP address it is using. Model-specific instructions for accessing the network menu are available in the hardware user guides, found on the user guide home page .Open an existing show or create a new show. If you create a new show, you are prompted to enter show informationand add devices to your show. Click Closewhen you are finished adding devices.1.2.3.• 1.2.• 1.Step 5: Verify your network connection Once you have selected a network, confirm the connection by looking for the network icon () on the display or front panel ofeach device.Devices connected to the network will automatically appear in the Inventory tab. To verify that your devices are connected:View the device ID, channel name, and other parameters.Click a device icon to flash the front panel of the device for remote identification.Verify that the devices online indicator is green. The number of devices listed should match the number of devices con-nected to the network.Network troubleshootingTry the following solutions for common problems. If the issue you're having doesn't appear here, see the Network Trou-bleshooting topic of the full Wireless Workbench help system .If the network icon doesn't appear on a device's screen:Check all cables and connections.Click the network status indicator and verify that the IP address of the network in your preferences correspondswith the IP addresses of your networked devices.If one of your devices doesn't appear in the Inventory tab:Check IP address to verify that device is on the same network as the computer network. Select Reports >Firmware and Network Summary for a report of the IP addresses of your computer and any discovered devices.2.•1.2.3.4.5.6.Open a terminal and try to ping the IP address of the device (to do this, type "ping" and enter the device's IP ad-dress).If the Device online indicator is gray, click the network status indicator and verify that the IP address of the network in your preferences corresponds with the IP addresses of your networked devices.Step 6: Coordinate frequenciesIn the Frequency coordination tab, you can organize, manage, and calculate frequencies for your system. As part of the coordi-nation, you can analyze the frequencies to make sure they are compatible with all the devices in your system and then deploy them to your devices.Perform a scan. In the scanning sidebar, select devices to scan with and start the scan.Add frequencies to the coordination. In the Add frequencies tab, choose to select frequencies from the inventory.Choose All frequencies from Inventory and click OK to bring frequencies into the coordination workspace.Select Analyze to check the compatibility of the current frequencies.Select Calculate to find compatible frequencies for all unlocked entries.Select Assign and Deploy to preview the assignments of channels and frequencies.Deploy the frequencies to your devices.Step 7: Set transmitter frequencies using IR syncPerforming an IR sync automatically tunes the portable device to the same frequency that was deployed to the networked de-vice. When the IR sync is complete, a wireless audio channel is formed between the two devices.Align the IR sync windows of the portable device and networked device, and then press sync or access the sync menu. Refer to the hardware user guides for details about IR sync for your model of transmitter and receiver.1.2.3.4.5.Step 8: Monitor and control your systemIn the Monitor tab, you can add channel strips and Mini-Timelines to monitor your devices. The properties panel displays RF and audio meters and allow you to adjust parameters in real-time.Add channel strips and a Mini-Timeline by dragging and dropping channels from the right pane. You can also use theStrip and Timeline checkboxes.Right-click a channel strip to see configuration options.Double-click a channel strip to see and change detailed device parameters.Click Auto to update the way your channel strip is arranged. Snap it to the frame or move it freely about the screen.Select the gear icon in the lower-right corner of the screen to customize channel strips.Step 9: Learn moreFor more information and support for Wireless Workbench, see the following resources: Shure Audio Institute - Trainings, educational materials, and other instructional content Wireless Workbench video tutorials on YouTubeWireless Workbench release notesAnswers to frequently asked questions。
IBM System Storage N 系列 AIX 主机实用程序 6.0 快速入门指南说明书
IBM System Storage N series AIX Host Utilities6.0Quick Start GuideThis guide is for experienced AIX users.It provides the basic information required to get the AIX Host Utilities installed and set up on an AIX host.The steps listed are for a typical installation and cover multiple AIX environments,including MPIO and PowerVM.While many steps are common to all environments,some steps apply only to a specific environment.If you are not an experienced AIX user,see the AIX Host Utilities Installation and Setup Guide.That document provides detailed steps and examples.It also includes troubleshooting information as well as instructions for optional tasks,such as setting up a SAN boot LUN.For information about installing and setting up third-party hardware and applications,such as host bus adapters,see the documentation that accompanies those products.Note:Occasionally there are known problems that can affect your system setup.Read the AIX Host Utilities Release Notes before you install the Host Utilities.The Release Notes are updated whenever an issue is found and might contain the information that was discovered after this guide wasproduced.Task1:Make sure the prerequisites for installing and setting up the Host Utilities have been metTo install the Host Utilities and set up your system,you must perform tasks on both the host and the storage system.In some cases,the tasks you perform vary depending on your environment;for example, the protocol you are using and whether you are using AIX MPIO for multipathing.Note:The N series interoperability matrix website contains the most current information about supported environments for the Host Utilities.1.Verify that your host system is correct,including:v Host operating system version,technology levels,and appropriate updatesv HBAs and drivers,model and version,or software initiatorv Volume management and multipathing,if you are using multipathingv PowerVM,if you are using PowerVMThe Host Utilities support both PowerVM vSCSI and PowerVM NPIV.2.Verify that your storage system is set up correctly,which includes having:v The correct version of Data ONTAP installed.v The appropriate license for the protocol on which your environment runs.v Appropriate HBAs or software initiators set up to work with the host as needed by your protocol.v ALUA enabled on all platforms that support it.Note:Starting with Data ONTAP8.0,ALUA is the default igroup.For FC environments where ALUA is not supported,the AIX Host Utilities provide the dotpaths utility.v Working volumes and qtrees(if desired)set up.3.(FC environments)If you are using a fabric connection,verify that the switch is set up correctly,which includes having the switch:v Cabled according to the instructions in the SAN Configuration Guide(called Fibre Channel and iSCSI Configuration Guide in Data ONTAP8.1and earlier)for your version of Data ONTAP.vZoned appropriately,using the supported zoning technique in single initiator zoning from a host's initiator's standpoint.v Powered on in the correct order:switch,disk shelves,storage systems,and then the host.Note:For information about supported topologies,see the SAN Configuration Guide(called Fibre Channel and iSCSI Configuration Guide in Data ONTAP8.1and earlier)for your version of DataONTAP.4.(FC direct-attached environment)If you use a direct-attached,FC configuration,set the media typeof the target HBA on the storage system to loop.Use the fcp config command to stop the HBA,set it to loop(fcp config adapter mediatype loop), and then restart the adapter.You can use the default HBA settings for the initiator HBA in the host,but you must configure the5.Confirm that the host and the storage system can communicate.Task2:Install and set up the Host UtilitiesTo install and set up the Host Utilities,you must get the software package for your Host Utilities environment and the software package for the SAN Toolkit.After you install these packages,you might need to perform additional configuration steps for your environment.You must be logged on as root to install or uninstall the Host Utilities.Note:(PowerVM vSCSI environments)If you are using PowerVM with vSCSI,you must switch into the OEM setup shell to install the Host Utilities on the VIO server:1.Log on to the host as padmin.2.Enter the command:oem_setup_envComplete the following steps to get,install,and set up the Host Utilities:1.Download the compressed file containing the Host Utilities from N series support website at/storage/support/nseries/.2.Uncompress the file and get the SAN Toolkit software package(Ontap.SAN_toolkit)for allenvironments and the host settings software package for your environment:Host Utilities environment Software packageAIX MPIO,PowerVM MPIO/Ontap.MPIO_Host_Utilities_KitSAN Tool Kit SAN_Tool_Kit/Ontap.SAN_toolkit You can use the zcat and tar commands to uncompress the file and extract the software;for example: zcat ibm_aix_host_utilities_6.0.tar.Z|tar-xvf-3.Install or upgrade the existing Host Utilities SAN Toolkit software package and the host settingssoftware package that you extracted.2From the directory containing the extracted software packages,use one of the following methods to install the two software packages:v SMITUse the smitty install command to start this program.Go to the Software Installation andMaintenance screen and choose the Install and Update Software option.v The command installp-aXYd FileSet_Path_NameRegardless of which method you use,you must execute it twice to install both the SAN Toolkitsoftware package and the host settings software package.(PowerVM NPIV environments)If you have a PowerVM NPIV environment running FC,you must install the SAN Toolkit on each VIO client.Doing this lets you run the sanlun utility on each VIO client.Note:If you have a PowerVM vSCSI environment,the Host Utilities is only installed on the VIO server and not the VIO client.4.(FC environments)Enable AIX Fast I/O Failure by setting the fc_err_recov parameter to fast_fail.a.For each host HBA(fcsci X where X is the HBA number),enable the AIX Fast I/O Failure featureby entering the following command:chdev-l fscsiX-a fc_err_recov=fast_fail-Pb.After you have set these values on each host HBA,reboot the system to enable the change to takeplace.e the command lsattr-El fscsiX to verify that the AIX Fast I/O Failure feature and DynamicTracking are enabled.Task3:Set up access between the host and the LUNs on the storage systemTo complete the Host Utilities setup,you must ensure your host discovers and can work with the LUNs on the storage system.The steps you perform differ depending on your environment.You must be logged in as root administrator to execute the Host Utilities commands.(PowerVM environments only)When you are setting access between the host and LUNs,the commands you enter in a PowerVM environment vary depending on whether you are running PowerVM vSCSI or PowerVM NPIV.If you are using PowerVM vSCSI and VIO servers,you must use the padmin login and the commands appropriate for that login to configure and discover LUNs.When you use the Host Utilities commands, you must become root by entering the oem_setup_env command.If you are using PowerVM NPIV,you run all the commands on the VIO client.This is the same as running AIX MPIO.1.Create and map igroups and LUNs.You must create at least one igroup and one LUN,and then map the LUN to the igroup.The lun setup command helps you through this process.For details about creating an igroup and LUNs,see the SAN Administration Guide(called Data ONTAP Block Access Management Guide for iSCSI and FC in Data ONTAP8.1and earlier)for your version of Data ONTAP.2.(FC)If your environment is running the FC protocol and supports ALUA,make sure ALUA isenabled.With Data ONTAP8.0and later,ALUA is automatically enabled when you create an igroup in an environment using FC.To determine whether ALUA is enabled,enter the command:igroup show-v igroup_nameIf ALUA is not enabled,enable it by entering the following command:igroup set igroup_name alua yes3.Discover the new LUNs by entering the appropriate command for your environment.3AIX MPIO and PowerVM NPIV environments cfgmgrPowerVM vSCSI environments cfgdev4.Verify that the host has discovered the LUNs by displaying all the AIX disks.(AIX MPIO and all PowerVM environments)Write down the hdisk instance numbers so you can supply them when you perform the path configurations.AIX MPIO and PowerVM NPIV environments lsdev-Cc diskPowerVM vSCSI environments lsdev-type disk5.(AIX MPIO and all PowerVM environments)Display information about your environment.AIX MPIO and PowerVM NPIV environments lsattr-El hdisk_namePowerVM vSCSI environments only lsdev-dev hdisk_name-attr6.(PowerVM vSCSI environments)Become root by entering the following command:oem_setup_env7.(AIX MPIO and all PowerVM FC environments)In FC environments,set the path priorities.ALUA handles this automatically.If ALUA is not supported and you are using an MPIO environment, you can use the dotpaths utility that comes with the Host Utilities to set the path priorities.If you enter dotpaths without any options,it sets the priority for all Data ONTAP LUNs.8.(PowerVM vSCSI environments)If you have LUNs presented to a VIO server from multiplethird-party storage vendors,make sure that all the LUNs use the same maximum transfer size.Enter the following command:lsattr-El hdisk_name-a max_transfer9.Display information about the LUNs and the HBAs by using the command sanlun.For example,toverify that the host has discovered the LUNs,enter the command:sanlun lun showIf you are using multipathing,you can display information about the primary and secondary paths available to the LUNs by entering the following command:sanlun lun show-pNote:The sanlun command displays path information for each LUN;however,it only displays the native multipathing policy.To see the multipathing policy for other vendors,you must usevendor-specific commands.WebsitesIBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates.The following web pages provide N series information:v A listing of currently available N series products and features can be found at the following web page: /storage/nas/v The IBM System Storage N series support website requires users to register in order to obtain access to N series support content on the web.To understand how the N series support web content is organized and navigated,and to access the N series support website,refer to the following publicly accessible web page:/storage/support/nseries/This web page also provides links to AutoSupport information as well as other important N series product resources.v IBM System Storage N series products attach to a variety of servers and operating systems.To determine the latest supported attachments,go to the IBM N series interoperability matrix at the following web page:/systems/storage/network/interophome.html4v For the latest N series hardware product documentation,including planning,installation and setup, and hardware monitoring,service and diagnostics,see the IBM N series Information Center at the following web page:/infocenter/nasinfo/nseries/index.jspNA210-05812_A0,Printed in USA©Copyright IBM Corporation2012.US Government Users Restricted Rights–Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.GI13-2806-01。
QuickClip Portlet, BEA WebLogic Edition 6.1 安装指南说明
All other names and marks are property of their respective owners.
Contents
QuickClip Portlet, BEA WebLogic Edition .................................................................... 1 Installation Guide ............................................................................................................ 1 Contents.......................................................................................................................... iii Installation Guide ............................................................................................................ 1 Installing the software .................................................................................................... 1 Domain Upgrade ............................................................................................................. 2 Portal Project Upgrade ................................................................................................... 3
Digi JumpStart for Windows Embedded CE 6.0 使用指南说明书
This document provides an exercise using Digi JumpStart for Windows Embedded CE 6.0. This document shows how to develop, run, and debug a simple application on your target hardware platform. This tutorial takes about 30 minutes. For detailed information, see Digi JumpStart for Windows Embedded CE 6.0 User’s Guide integrated in Visual Studio Help > Contents.Complete all the tasks in this guide in the order presented.Conventions in this tutorialThis document uses these conventions, frames, and symbols to display information:Convention UseStyle New terms and variables in commands, code, and other input.Style In examples, to show the contents of files, the output from commands.In text, the C code.Variables to be replaced with actual values are shown in italics.Style For menu items, dialogs, tabs, buttons, and other controls.In examples, to show the text that should be entered literally.$ A prompt that indicates the action is performed in the host computer.\> A prompt that indicates the action is performed in the target device.Menu name > option A menu followed by one or more options; for example, File > New.This manual also uses these frames and symbols:A warning that helps to solve or to avoid common mistakes orproblems.A hint that contains useful information about a topic.$A host computer session.Bold text indicates what must be input.\> A target session.\> Bold text indicates what must be input.90000850_D1.Introduction1.1. Software and hardware requirements before beginning this tutorialThe instructions in this guide assume that the Digi JumpStart for Windows Embedded CE software is installed on the host computer, and the host computer is connected to the development board. If the software is not installed or the hardware connected, do both now.See your network administrator for this information needed to configure the target’s networksettings:∙IP address of the development computer∙IP address to use for the target∙Netmask for the Ethernet interface∙Netmask for the wireless interface (ConnectCore Wi-9C and ConnectCore Wi-9M 2443 only) ∙IP address to use for the target’s WLAN interface, ask the network administrator for a free IP address for the wireless connection (ConnectCore Wi-9C and ConnectCore Wi-9M 2443 only).2.Configure the IP addresses and network settingsThis task opens and configures the Target Administrator, powers up the target, and configures the target’s network settings.2.1. Open Target AdministratorFor Visual Studio to communicate with the target a new remote configuration–a set of configuration options for a specific target–is needed.To create a new remote configuration, select Digi Addins > Target Administrator. Or click in the Target Administrator icon:Remote configuration settings are organized on three tabs:On the General tab, in the IP Address field, enter the IP address of the target; for example,192.168.42.30.Click on the File Transfer tab to configure the file transfer mechanism between Visual Studio and the embedded system. If you check Requires Login/Password checkbox you must file Login and Password fields, if not, values will set to “anonymous”.You can also select your local FTP Upload and Download folders, using by Remote File Inspector.Click on the Hardware tab to identify the hardware components of the target device. Depending on the model type of the development board, select the appropriate values for Processor, Module, and Base BoardClick the Save button to save the configurations made and then click the Set configuration as current button to make this remote configuration the current configuration used by Visual Studio.2.2. Open and configure the Serial Console viewThe target board prints out messages on the serial port. To open the Serial Console view in Visual Studio, select Digi Addins > Serial Console or click in the Serial Console icon:Open the Serial Console Options dialog by clicking the Serial Console Options button on the Serial Console view's toolbar.The Serial Port must be configured with the device node into which the serial cable is plugged. Try with each one of the serial ports detected before until the correct one is found. Do not change the other values (38400 baud, 8 data bits, 1 stop bit, no parity). Click OK to accept the configuration.Once the serial port is configured, establish the connection by clicking the Open Port button of the Serial Console view's toolbar.2.3. Power up the targetPower up the target using the main power on the development board.Turn on the switch SW5 on the ConnectCore 9C/Wi-9C development board, or turn on the switch S2 on the ConnectCore 9P 9360 development board or on the ConnectCore 9M/Wi-9M 2443development board .For more information about the position of the switch, see the DevelopmentBoard chapter of the ConnectCore_9C_Wi-9C_Hardware_Reference.pdf,ConnectCore_9P_9360_Hardware_Reference.pdf or ConnectCore_9M_Wi-9M_2443_Hardware_Reference.pdf, depending the platform being used.After power-up, the LEDs on the development board light up.After a few seconds the system will print boot messages in the Serial Console window.Press any key within four seconds of receiving messages to stop the auto boot process.2.4. Configure IP addresses and network settings1. From the boot loader shell, enter these commands:#setenv ipaddr aaa.aaa.aaa.aaa#setenv netmask bbb.bbb.bbb.bbb#setenv ipaddr_wlan c#setenv netmask_wlan ddd.ddd.ddd.ddd#setenv serverip eee.eee.eee.eee#saveenvIn the commands, replace the variables with these actual values:∙aaa.aaa.aaa.aaa with the IP address to assign to the target.∙bbb.bbb.bbb.bbb with the target’s network mask.∙c with the IP address for the WLAN adapter ( ConnectCore Wi-9C and ConnectCore Wi-9M 2443 only).∙ddd.ddd.ddd.ddd with the wireless network mask (ConnectCore Wi-9C and ConnectCore Wi-9M 2443 only).∙eee.eee.eee.eee with the IP address of the development computer.Do not use the equal sign (=) with setenv2. Reset the target. Depending on the development board, press the reset button: on theConnectCore 9C/Wi-9C development board, press switch SW6, on the ConnectCore 9P 9360 and ConnectCore 9M/Wi-9M 2443 development boards, press switch S1.For more information about the position of the switch, see the DevelopmentBoard chapter of the ConnectCore_9C_Wi-9C_Hardware_Reference.pdf, ConnectCore_9P_9360_Hardware_Reference.pdf or ConnectCore_9M_Wi-9M_2443_Hardware_Reference.pdf, depending on the platform being used.3.Explore networking capabilities3.1. Open a Telnet ConsoleA Telnet client server is included in the Digi Addins, making it possible to open a Telnet sessionfrom the development computer.To open a Telnet console view in Visual Studio, select Digi Addins > Telnet Console or click in the Telnet Console icon:Open the Telnet Console Options dialog by clicking the Telnet Console Options button on the Telnet Console view's toolbar.Select Use current Telnet configuration to use the current configuration.Once the Telnet Console is configured, establish the connection by clicking the Connect button of the Telnet Console view's toolbar.To see a list of all available commands, enter:helpThis command list is displayed:The following commands are available:ATTRIB Set/display file attributes.CALL Call batch script.CD Change directory.CHDIR Same as CD.CLS Clear the screen.COPY Copy files.DATE Display/set system date.DEL Delete a file.DIR Print contents of a directory.ECHO Echo output on the screen or change echoing parameters.ERASE Same as DEL.EXIT Exit command interpreter.HELP Print help for command interpreter or individual commands. GOTO Transfer control to a label in batch processing.IF Conditionally execute a command.MD Create a directory.MKDIR Same as MD.MOVE Move/rename files.PATH Alias for SET PATH.PAUSE Suspend execution of a batch file.PROMPT Reconfigure system prompt.PWD Print current working directory.RD Remove directory.REM Record comments in batch file.REN Change file name.RENAME Same as REN.RMDIR Same as RD.SET Set or list environment variables.SHIFT Shift arguments of a batch file.START Start detached process.TIME Display/change system time.TITLE Set the window title for a CMD.EXE session.TYPE Output contents of a file or files to the screen.Use HELP [command name] to display extended help for given command, or HELP CMD to display help on general topics such ascommand input options, I/O redirection or CMD parameters.3.2. Connect to Web ServerA Web server is included and started by default, and serves a default Windows CE Web page thatresides in the target image. To connect to the Web server:1. Open a browser.2. In the Address box, enter the IP address of the target.The default Web page opens:4.Configure device transportTo transfer an application to the target and debug it, a device transport configuration must becreated. To create a device transport configuration:1. Start Visual Studio® 2005.2. Select Tools > Options.Options dialog opens.The3. Select Device Tools > Devices.4. From the Show devices for platform pulldown menu, select Windows CE5.0. (This selectionis also valid for Windows Embedded CE 6.0.)5. In the Devices list box, select Windows CE 5.0 Device. Under Default device, selectWindows CE 5.0 Device. (This selection is also valid for Windows Embedded CE 6.0.)6. Click Properties.Windows CE 5.0 Device Properties dialog opens:The7. Select these values:∙Default output location: Program Files Folder∙Transport: TCP Connect Transport∙Bootstrapper: ActiveSync Startup Provider8. At the right of the Transport method pulldown menu, click Configure.The Configure TCP/IP Transport dialog opens:9. Click Use specific IP address, enter the target’s IP address, and click OK.10. To accept the device transportation configuration, click OK in the remaining open dialogs. Visual Studio 2005 is now ready to transfer and debug any Windows Embedded CE application to the target device.5.Develop an application with Visual Studio 2005This task creates and builds a simple HelloWorld program using Visual C#®. The project will have an empty form and basic source files.5.1. Create the project1. Select File > New > Project.New Project dialog box opens:The2. Do these steps:∙ In the Project Types tree select Visual C# (if Visual C# is not your default language in Visual Studio, expand Other Languages > Visual C#) select SmartDevice, andWindows CE 5.0 (This selection is also valid for Windows Embedded CE 6.0.) ∙ In the Templates section, select Device Application.∙In the bottom part of the dialog box, in the Name input box, enter HelloWorld for project name.∙ In the Location input box, enter the location for the source files.When everything is entered, click OK.5.2. Generate the interfaceNow add some information in the form to generate the interface:1. To open the toolbox, select View > Toolbox.2. Drag and drop a button into the empty form.3. Drag and drop two labels into the form so the interface looks like this:4. Right-click the button and select Properties. Then, in the Appearance > Text field, enterPress Me as the new text. Leave the default text for the labels as they are.5.3. Generate the source codeNext, add some code in the button’s click method.1. To open the button’s click method source code, double-click the button on the form. Codesimilar to this is displayed:using System;using System.Collections.Generic;using ponentModel;using System.Data;using System.Drawing;using System.Text;using System.Windows.Forms;namespace HelloWorld{public partial class Form1 : Form{public Form1(){InitializeComponent();}private void button1_Click(object sender, EventArgs e){}}}2. Set label1 to display Hello World! and label2 to display a counter’s value that increases witheach click of the button. Enter:using System;using System.Collections.Generic;using ponentModel;using System.Data;using System.Drawing;using System.Text;using System.Windows.Forms;namespace HelloWorld{public partial class Form1 : Form{int counter = 1;public Form1(){InitializeComponent();}private void button1_Click(object sender, EventArgs e){label1.Text = “Hello World!”;label2.Text = counter.ToString();counter++;}}}3. Save the file.5.4. Build the sample applicationTo build the sample application, select Build > Build Solution:When the build completes, messages in the output window (View > Output) indicate: ∙That the build process was successful∙The location of the executable image6.Transfer the application to the target using Remote FileInspectorNow use the Remote File Inspector to transfer the application executable into the embedded platform’s RAM:1. Open the Remote File Inspector, select Digi Addins > Remote File Inspector or click in theRemote File Inspector icon:2. Open the Remote File Inspector settings dialog by clicking the Remote File Inspectorsettings button on the Telnet Console view's toolbar.Use current FTP configuration to use the current configuration.Select3. Connect the Remote File Inspector by clicking the Connect button4. Upload the file by clicking the Upload button.5. Select the application binary surfing through the browser.6. Click Open and the file will be uploaded into the embedded platform.7.Run the applicationNow go to the target device and run the application.1. On the target’s desktop, double-click My Device, and the double-click HelloWorld.2. Click the Press Me button several times.label1 displays Hello World!, and label2 displays the number of times the Press Me buttonwas pressed:.3. Close the application by clicking the X on the application’s title bar.8.Debug the application8.1. Establish the debug connection1. In Visual Studio 2005, select Tools > Connect to Device.2. Select Windows CE 5.0 Device (also valid for Windows Embedded CE 6.0), and clickConnect. A dialog opens and reports whether the connection was successful.3. Close the dialog.8.2. Begin to deploy and debug the applicationSelect Debug > Start Debugging, and select Windows CE 5.0 Device again.(To keep this dialog from opening, uncheck Show me this dialog every time I deploy theapplication.)Then click Deploy.This step transfers the application to the target and runs it for debugging. The Visual Studioperspective changes to Debug mode.8.3. Add/remove breakpointsTo add a breakpoint, in any line of code, either click the left border of the editor or press F9. A red circle appears where the code was clicked.To remove a breakpoint, click again.Try adding a breakpoint to any line in the button’s click method. Then, in the target, click the button.The code stops at the breakpoint; the yellow arrow indicates the line where the program counter is.8.4. Other debugging controlsOther debugging controls and options accessible from the Debug menu include watching andmodifying variables, stepping over or into the code, viewing and editing memory locations. Forinformation about these and other debugging controls, see the Digi JumpStart for WindowsEmbedded CE 6.0 User’s Guide.8.5. What’s next?Congratulations – you have created, built, run, and debugged your first application for the targetdevice. Now you are ready to do more real development of the Windows CE kernel and complex applications to create a powerful system for your device.To learn more about Windows Embedded CE 6.0, see the Digi JumpStart for WindowsEmbedded CE 6.0 User’s Guide integrated in Visual Studio Help > Contents.For documentation on your module please see the Digi Web site at . For Windows CE specific documentation please see the Visual Studio 2005 integrated help. Tonavigate to the integrated help start Visual Studio 2005 then go to 'Help -> Contents'. Next, under the 'Filtered by:' drop down menu, select '(unfiltered)' then see the section entitled 'Digi Jumpstart for Windows Embedded CE 6.0 User's Guide'.。
BT-MS-EN-E 快速启动手册说明书
BT-MS-EN-E 快速启动手册BEACON GLOBAL TECHNOLOGY目录BT-MS-EN-E简介 (2)模块初始配置 (2)配置模块做 EtherNet/IP Server (5)配置模块做 EtherNet/IP Client (11)配置模块做MSSQL数据库主站 (17)举例1.配置插入整型数到MSSQL数据库 (20)举例2.配置插入浮点数到MSSQL数据库 (23)举例3.配置更新整型数到MSSQL数据库（更新条件为数字） (26)举例4.配置更新整型数到MSSQL数据库（更新条件为字符） (28)举例5.配置模块读取MSSQL数据库传输给LONGIX5000（读取条件为字符） (30)举例6.模块读取LONGIX5000浮点数标签，插入到MSSQL数据库 (33)联系我们 (37)BT-MS-EN-E简介BT-MS-EN-E系列模块是MS SQL Server-EtherNet/IP通讯模块，支持在数据库和EtherNet/IP协议网络中数据交换，最大5000个字数据交换区。
MS SQL Server可以进行通讯的版本有Microsoft SQL Server 7.0，Microsoft SQL Server 2000，Microsoft SQL Server 2005，Microsoft SQL Server 2008，Microsoft SQL Server 2012，Microsoft SQL Server 2014和更高版本。
EtherNet/IP可以进行通讯的设备有罗克韦尔1756系列，1769系列，1746系列，PLC-2系列，PLC-5系列，SLC500系列，Micrologix PLC系列，PowerFlex变频器系列，E300智能马达保护器，Power Monitor智能电力监控仪，上位机RSView_SE等。
MS SQL Server-EtherNet/IP可以使用相同网段或者不同网段进行通讯。
快速启动指南10678说明书
1.3 Directly mounted to electrical panel – preferred methodThe preferred installation is to mount the SPD directly to the electrical panel. For Type 4X applications, use the supplied mounting feet to secure the device.Figure 1. Preferred installation.1.4 Mounted to electrical panel with conduit – alternate methodAn alternate installation method is to install the SPD with a short piece straight conduit. Avoid using 90°conduit elbows and keep the conduit run as short and straight as possible. In this application, install the SPD as close as possible to the electrical panel. For Type 4X applications, use weatherproof conduit and fittings along with the supplied mounting feet to secure the device.Figure 2. Alternate installation.2. Wiring installationLocate the electrical system’s applicable wiring schematic from section 3. Wiring diagrams and refer to it while wiring the SPD.TURN OFF power to the electrical equipment being connected to the SPD in accordance with NEC, CEC, state, county and local codes for all safety ratings. Bussmann series SPDs covered in this guide are designed with internal overcurrent protection and do not require an externalovercurrent protective device (OCPD) unless otherwise required by NEC, UL and local electrical requirements to protect electrical conductors. NEC Article 310.15 (B) (16) defines the maximum rating of the OCPD required to protect the electrical conductors. NEC shows #10 AWG conductors at 60°C typically requiring a 1-pole (for single-phase systems), 2-pole (for split-phase systems) or 3-pole (for 3-phase systems) 30 A branch circuit breaker to protect SPD conductors.Twist and bind the SPD wires tightly together. Minimize overall lead length to optimize SPD performance. To maximize the SPD’sperformance, phase wire length should be less than 14” (35cm) twisted and bound together. To maximize performance for wire lengths longer than four inches, phase wires should be twisted once for each four inches of wire length.If the SPD is configured for remote monitoring (not available on allmodels), connect the Form C relay contact wiring to an alarm or building monitoring system. Refer to the installation manual (Publication No. 10679) for Form C relay ratings.Note: Utilization of Form C contacts is optional. Connecting Form C wires is not required for the SPD to operate.Tighten and recheck all connections and mounting before proceeding to section 4. Operation .BSPA Type 1 and Type 2 surge protective devices1. IntroductionThis quick start guide is for the installation, wiring and operation of the Bussmann™ series BSPA surge protective device (SPD). Only qualified personnel should perform this installation. For additional information regarding installation, wiring and operation of this device, refer to theinstallation manual (Publication No. 10679). If you require further information regarding a particular installation, application or maintenance activity, please *****************************************************************between 7:00 a.m. and 5:00 p.m. Central time, Monday-Friday. This quick start guide is not intended to cover all details, variations or combinations of the device’s storage, delivery, installation, operation or maintenance.1.1 Safety precautionsWARNINGWARNING – SHOCK HAZARD – DO NOT OPENAVERTISSEMENT – RISQUE DE CHOC – NE PAS OUVRIR WARNING NO SERVICEABLE PARTSATTENTION: AUCUNE PIÈCE REMPLACABLE OU RÉPARABLEA LICENSED/QUALIFIED ELECTRICIAN MUST COMPLETE ALL INSTRUCTIONS IN THIS GUIDE IN ACCORDANCE WITH THENATIONAL ELECTRICAL CODE (NEC ®), CANADIAN ELECTRICAL CODE (CEC), STATE, COUNTY AND LOCAL SAFETY RATINGS, OR OTHER APPLICABLE COUNTRY CODES. ALL APPLICABLE LOCAL ELECTRICAL CODES SUPERSEDE THESE INSTRUCTIONS.IMPROPER WIRING COULD CAUSE DEATH, INJURY AND/OREQUIPMENT DAMAGE. ONLY LICENSED/QUALIFIED ELECTRICIANS WHO ARE TRAINED IN THE INSTALLATION AND SERVICE OF ELECTRICAL SERVICES ARE TO INSTALL AND SERVICE THIS EQUIPMENT.CHECK THE VOLTAGE-RATING LABEL LOCATED ON THE SIDE OF THE SPD TO VERIFY THAT THE ELECTRICAL SYSTEM’S VOLTAGE AND WIRING CONFIGURATION ARE THE SAME AS THE SPD.CONDUCTING DIELECTRIC, MEGGAR, OR HI-POTENTIAL TESTING WITH THE SPD INSTALLED WILL CAUSE INTERNAL DAMAGE TO THE SPD. THE SPD WILL CAUSE THE TEST TO FAIL.IMPROPER INSTALLATION COULD CAUSE DEATH, INJURY AND EQUIPMENT DAMAGE. FOLLOW ALL WARNINGS AND CAUTIONS. COMPLETELY READ AND UNDERSTAND THE INFORMATION IN THIS GUIDE BEFORE ATTEMPTING TO INSTALL OR OPERATE THIS EQUIPMENT.ARC FLASH DURING INSTALLATION COULD CAUSE INJURY ORDEATH. USE APPROPRIATE SAFETY PRECAUTIONS AND PERSONAL PROTECTION EQUIPMENT FOR ARC FLASH PROTECTION.CHECK THE FACILITY’S GROUNDING SYSTEM. ALL GROUNDING, BONDING AND EARTHING PRACTICES MUST MEET NEC, CEC AND LOCAL APPROVED PRACTICES. A POOR GROUND, OR A GROUNDING / BONDING VIOLATION WILL SERIOUSLY AFFECT THE SPD’S ABILITY TO FUNCTION AS SPECIFIED.INSTALLING AN SPD THAT IS IMPROPERLY RATED FOR THEELECTRICAL SYSTEM VOLTAGE COULD CREATE A POTENTIALLY HAZARDOUS CONDITION, RESULTING IN INJURY OR EQUIPMENT DAMAGE.WHEN MOUNTING THE SPD OUTDOORS, USE WEATHERPROOF CONDUIT AND FITTINGS TO MAINTAIN THE ENCLOSURE’S NEMA RATING.FOR USE ON CIRCUITS DELIVERING UP TO 5000 RMS AMPS.CONVIENT Á DES CIRCUITS PRODUCISANT AU PLUS 5000 A EFF.1.2 Enclosure dimensionsRefer to the installation manual (Publication No. 10679) for unit size and dimensions.BSPA T ype 1 and T ype 2 surge protective devicesQuick start guide 10678Effective October 2017Eaton and Bussmann are valuable trademarks of Eaton in the U.S. and other countries. Y ou are not permitted to use the Eaton trademarks without prior written consent of Eaton.Eaton1000 Eaton Boulevard Cleveland, OH Bussmann Division 114 Old State Road Ellisville, MO 63021United States/bussmannseries © 2017 EatonAll Rights Reserved Printed in USAPublication No. 10678October 2017CSA is a registered trademark of the Canadian Standards Group.NEC is a registered trademark of the National Fire Protection Association.UL is a registered trademark of the Underwriters Laboratories, Inc.3. Wiring diagramsL2 (Phase B)Black L3 (Phase C)Black NeutralWhiteGround / protected earthGreen with yellow stripeTable 1. BSPA phase wire color codes.If the connected LEDs do not light, remove power, re-check connections, and test again. If the LEDs still do not light, contact your local authorized Bussmann series product distributor or Bussmann series product representative, as the SPD may be damaged.4.2 LED color statesWhen properly installed, only green status LEDs should be illuminated. Refer to the installation manual (Publication No. 10679) for more information regarding BSPA LED color states.5. MaintenanceThe Bussmann series BSPA SPD devices covered in this guide are self-contained devices that do not require maintenance or contain serviceable parts. If any LED changes state, the unit has lost surge protection and must be replaced. Please contact your local authorized Bussmann series product distributor or Bussmann series product representative, as the SPD may be under warranty.6. LiabilityThis guide is published solely for information purposes and should not be considered all-inclusive. If further information is required, you should consult the installation manual (Publication No. 10679) or Application Engineering. Sale of the product shown in this guide is subject to terms and conditions outlined in appropriate Bussmann Division selling policies or other contractual agreements between the parties. This guide is not intended to and does not enlarge or add to any such contract. The sole source governing the rights and remedies of any purchaser of this equipment is the contract between the purchaser and the Bussmann Division.NO WARRANTIES, EXPRESSED OR IMPLIED, INCLUDINGWARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE OR MERCHANTABILITY , OR WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, ARE MADE REGARDING THE INFORMATION, RECOMMENDATIONS AND DESCRIPTIONS CONTAINED HEREIN.In no event will the Bussmann Division be responsible to the purchaser or user in contract, in tort (including negligence), strict liability orotherwise for any special, indirect, incidental or consequential damage or loss whatsoever, including but not limited to damage or loss of equipment use, plant or power system, cost of capital, loss of power, additional expenses in the use of existing power facilities or claimsagainst the purchaser or user by its customers resulting from the use of the information, recommendations and description contained herein.7. WarrantyRefer to the Bussmann series warranty statement 3A1502 at /bussmannseries.8. Supplementary manualsFor additional information regarding installation, wiring and operation of this device, refer to installation manual 10679 at /bussmannseries.If you have any questions or need additional information, please contact *************************************************************between 7:00 a.m. and 5:00 p.m., Monday-Friday.Figure 3. Single-phase (2W+G)Figure 5. Three-phase Delta(3W+G)Figure 4. Split-phase (3W+G)Figure 6. Three-phase Wye(4W+G)4. Operation4.1 Power up and system checkoutTighten and recheck all connections and mounting before proceeding. Switch main panel power to ON and, if applicable, then switch SPD branch circuit breaker(s) to ON . One LED should light for each phase voltage being protected. Single-phase electrical systems will light only one LED, split-phase systems light two LEDs, and three-phase systemswill light all three LEDs.。
HPE Workload Aware Security for Linux (WASL) Softw
================================================== Read Before Installing HPE Workload Aware Security for Linux (WASL) Software 1.2.0 ================================================== Edition: 3 Published: Jan 2019 (C) Copyright 2019 Hewlett Packard Enterprise Development LP Confidential computer software. Valid license from HPE required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.The information contained herein is subject to change without notice. The only warranties for HPE products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein must be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.Read Before Installing HPE Workload Aware Security for Linux (WASL) Software 1.2.0 Printed in Puerto Rico *Q8K94-96003*Q8K94-96003Contents==================================================1. Overview2. Supported Operating System, Server, Storage and Virtual appliance3. Software and RPM Bundles4. Signature Verification5. Installation Instructions6. Related Documentation================================================== 1. Overview==================================================Introduction---------------HPE WASL is an easy-to-use security compliance tool designed to secure Operating System instances and Applications. It automates security compliance for SAP HANA workloads and the underlying Linux Operating System, reducing with a single click.Centralized dashboard, WASL Security Management Station (SMS), can evaluate system compliance and perform remediation with the push of a button. WASL SMS displays overall compliance score and alerts users new policy updates.WASL also offers rich actionable reports and log files post evaluation and recommends remediation steps. WASL provides the ability to rollback remediation action and restore the workload configuration to a pre-remediation state.WASL uses compliance profiles built using XCCDF specification language enabling extensibility of the profile set. It currently provides the following standard profile set addressing theglobal benchmark standards for OS and SAP HANA application* OS Security Level 2 for SLES 12* OS Security Level 1 for SLES for SAP Applications 12* OS Security Level 2 for SLES for SAP Applications 12* OS Security extras for SAP HANA* OS Security Level 1 for RHEL 7* OS Security Level 2 for RHEL 7* SAP HANA 1.0 DB Security Level 1* SAP HANA 1.0 DB Security Level 2* SAP HANA 2.0 DB Security Level 1* SAP HANA 2.0 DB Security Level 2Licensing Information--------------------------There are two variants of the WASL license:1) WASL Basic - Designed to automate security compliance of theLinux operating system.One non-transferable WASL Basic license is required for eachactive instance of Red Hat Linux OS or SUSE Linux being covered by WASL. This includes both physical and virtual servers.2) WASL Advanced - Designed for SAP HANA customer seekingSAP HANA and Linux Operating System security compliance on HPE appliances and/or TDI deployments.Each license purchase includes 1 year of 24x7 Technical Support and Software Updates Service.Note: All Standard profile sets are included in the HPE WASLvirtual appliance. Based on the license purchased the profile will be applicable.NOTE: For information about the latest updates on the productRefer to the WASL product page at HPE Software Depot and navigate to Linux -> Mission Critical x86 Software, or visit: https:///servers/wasl================================================== 2. Supported Operating System, Server, Storage and Virtual appliance ================================================== HPE WASL SMS:--------------------HPE WASL SMS is packaged and shipped as a virtual appliance (OVA format) that can be provisioned on a VMware vSphere Hypervisor 6.0, 6.5 and 6.7 versions.WASL Nodes:----------------Nodes that can be registered and secured using HPE WASL should run one of the following operating system variants.* SUSE Linux Enterprise Server 12 (SP1, SP2, SP3)* SUSE Linux Enterprise Server for SAP Applications 12 (SP1 , SP2 & SP3)* Red Hat Enterprise Linux 7 (7.2, 7.3, 7.4, 7.5)For detailed information on the supported Operating System, Server, Storage and virtual appliance requirements, see "HPE WASL Install and Setup Guide".================================================== 3. Software and RPM Bundles================================================== The following is the list of packages bundled in the virtualappliance for the WASL SMS and the Nodes.----------------------------------------------------------------1. WASL SMS Virtual appliance----------------------------------------------------------------The following ova file can be provisioned on a VMware vSphere Hypervisor.Q8K93-11003.ova2. WASL SMS 1.1.0 backup package----------------------------------------------------------------The following rpm package is required to take a backup ofWASL 1.1.0 setup. This can be installed only on SLES 11 SP4 node running WASL1.1.0 SMS.hpe-wasl-sms-backup-1.1.0-1.x86_64.rpm-----------------------------------------------------------------3. WASL Node packages-----------------------------------------------------------------RHEL 7:hpe_wasl_core-1.2.0-1.rhel7.x86_64.rpmhpe_wasl_os-1.2.0-1.rhel7.x86_64.rpmhpe_wasl_saphana-1.2.0-1.rhel7.x86_64.rpmopenscap_1-1.2.15-1.0.x86_64.rpmSLES 12:hpe_wasl_core-1.2.0-1.sles12.x86_64.rpmhpe_wasl_os-1.2.0-1.sles12.x86_64.rpmhpe_wasl_saphana-1.2.0-1.sles12.x86_64.rpmopenscap_1-1.2.15-1.0.x86_64.rpm================================================== 4. Signature verification================================================== Overview-----------The HPE WASL Virtual appliance and node rpms are signed with private digital keys held by HPE and the integrity of the packages can be verified before installing. This ensures that the packages have not been manipulated by a third party.Download the keys-----------------------Copy the compressed tar file (HPE-GPG-Public-Keys.tar.gz) fromhttps:///pub/keys/HPE-GPG-Public-Keys.tar.gzTransfer this keys compressed tar file to the client machine from Which the WASL Virtual appliance is being deployed. In-order to verify the Node Packages, copy the tar file to the WASL Nodewhere the node packages needto be installed.1) WASL Virtual appliance can be verified using the GPGmethodology described below.Import the key for gpg:---------------------------Import the public keys, one at a time while logged in with anadministrator account by running the following command on the host:C:\Users\admin> gpg --import <Key#>.pubVerifying HPE WASL Virtual appliance:----------------------------------------------C:\Users\admin>gpg --verify <filename>.ova.sig <filename>.ova<filename>.ova.sig file can be found in the same location of<filename>.ova fileExample output:C:\Users\admin> gpg --verify Q8K93-11003.ova.sig Q8K93-11003.ovagpg: Signature made <Time stamp>using RSA <key ID #>gpg: Good signature from "Hewlett Packard Enterprise Company RSA-2048-48<**************>"If your file does not pass verification or you do not have the HPE public key Installed, the following error is displayed:gpg: Signature made Tue Nov 27 22:02:59 2018 IST using RSA key ID 78DD34EEgpg: Can't check signature: public key not foundIf the verification fails, then do not use the WASL SMS virtualappliance as the file has been modified since it was released from HPE.2) WASL Node Packages and WASL SMS 1.1.0 backup package can be verified using the RPM methodology described below.Import the keys for RPM:------------------------------Import the public keys, one at a time while logged in as root byrunning the following command on the installing host:# rpm --import /path_to_the_key/file_name_of_the_keyExample:# rpm --import /path_to_the_key/B1275EA3.pubVerify using RPM---------------------Use the rpm --checksig command to validate and verify the digital signature of the signed file.# rpm --checksig filename_of_the_rpmThe following example command output indicates the validity of the signature:"filename_of_the_rpm.rpm: sha1 md5 OK"If your file does not pass verification or you do not have the HPE public key installed, the following error is displayed:Example output:"sample_file.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: key#)"been modified since it was released from HPE.See the following link for more details:https:///portal/swdepot/displayProductInfo. do? productNumber=HPLinuxCodeSigning================================================== 5. Installation Instructions================================================== If you are installing HPE WASL for the first time, follow theinstructions mentioned in "HPE WASL Install and Setup Guide".================================================== 6. Related Documentation================================================== For the latest documentation, go to HPE Software Depot andnavigate to WASL under Linux -> Mission Critical x86 Software, or visit:https:///portal/swdepot/displayProductInfo. do?productNumber=WASL* HPE WASL Release Notes* HPE WASL User Guide* HPE WASL Install and Setup Guide* HPE WASL Troubleshooting Guide==================================================。
installingmysql,thismaytakeafewminutes,holdon。。。
installingmysql,thismaytakeafewminutes,holdon。
centos6安装wdcp时make in progress卡住的解决办法今天在⼀台centos6的vps上安装wdcp出现的这个问题，到安装程序滚动⾄下⾯这⾥时出现“卡死”。
….setenforce:selinux is disabledinstalling mysql,this may take a few minutes,hold on plz…cofigure in progress…make in progress…在这⾥卡住了，本以为是上⾯的selinux is disabled的原故。
其实没有半⽑钱的关系。
安装在这⾥卡住后，不必⼼急，也不必强⾏退出安装程序重新安装，你所要做的就是⼀个字：等。
等了⼤约五分钟左右时，进度⼜向下滚动了⼀⾏：make install in progress …这时，⼜卡住了，你需要做的是去喝⼀杯茶。
过了五六分钟（可能更长）的样⼦，进度⼜向下滚了⼀⾏，提⽰安装mysql成功：Starting Mysql. success!installing httpd…[这⾥会卡个四五分钟]installing libiconv …[这⾥也会卡个四五分钟]installing php…[这⾥还会卡个四五分钟]installing wdcp apache… [这⾥卡的时间稍长，五⾄⼗分钟不等]Staring httpd:[ok]iptables:Saving firewall rules to /etc/sysconfig/iptables:[ok]installing wdcp php … [同上]卡了⼤半天，然后终于见到安装完成并成功启动各个服务的提⽰。
所以在安装wdcp时如果也遇到了卡的情况，还是要多等，只要它没有提⽰error错误。
当然，如果你真的等了⼤半天（６个⼩时）那还是别等了，重装吧。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Wireless Workbench 6© 2014 Shure Incorporated 27A26148 (Rev. 1)无线控制应用程序2舒尔 Wireless Workbench 6软件Wireless Workbench ® 6 (WWB6) 是一款适用于 Mac 和 Windows 的免费桌面应用程序，可充分发挥无线系统的潜力。
WWB6 可对计算机的联网舒尔无线系统进行全面监控，并实时更改设备和通道参数。
此外，该应用程序还包含一套功能强大的频率协调和可视化工具，用于计算所有无线系统（包括第三方无线系统）的兼容频率。
WWB6 能够轻松快速地配置、操作和监视您的无线系统，并可兼容以下联网的舒尔系统：• QLX-D™ 数字无线系统• ULX-D ® 数字无线系统• PSM ® 1000 个人监听系统• Axient ® 无线管理网络• UHF-R ® 无线系统本指南中的下述步骤可帮助您设置网络并实现组件与 Wireless Workbench 6之间的连接。
下载舒尔 Wireless Workbench 6您可访问 /software 免费下载 Wireless Workbench 6。
启动安装程序并按照步骤完成安装。
注：您必须以管理员身份登录才能安装 Wireless Workbench 。
Wireless Workbench 帮助和资源Wireless Workbench 6 包含所有的帮助主题和特定功能的使用说明。
您可以在 上找到以下舒尔无线产品资源：• Wireless Workbench 6 论坛• 舒尔产品用户指南• 常见问题解答• 发行说明• 使用视频3步骤 1：网络连接交换机/路由器（可选）联网组件步骤 2：防火墙配置MacWirel ess Workbench 6 使用以太网控制联网组件并与之通信。
每个联网组件都必须分配有一个唯一且有效的 IP 地址，以确保正常通信。
IP 地址可由具有 DHCP 寻址功能的计算机、交换机或路由器自动分配。
为了充分利用 DHCP 寻址功能，舒尔组件具有设置便捷的自动 IP 模式。
如需分配特定的 IP 地址，可将 IP 模式设为手动。
下面是设置网络连接的步骤简述：• 步骤 1：使用 CAT5 或更优质的以太网线缆连接计算机和组件。
对于多组件系统，建议增设路由器或交换机（如图所示），而不要使用菊花链连接。
• 步骤 2：打开计算机和所有的联网组件。
• 步骤 3：针对每个组件，在网络菜单中将 IP 地址模式设为“自动”，以启用自动 IP 寻址功能。
有关访问网络菜单的具体型号说明，请单击此处。
如果您要向组件分配特定的 IP 地址，除了自动 IP 寻址以外，还可以选择手动寻址。
• 步骤 1：使用 CAT5 或更优质的以太网线缆连接计算机和组件。
对于多组件系统，建议增设路由器或交换机（如图所示），而不要使用菊花链连接。
• 步骤 2：打开计算机和所有的联网组件。
• 步骤 3：针对每个组件，在网络菜单中将 IP 地址模式设为“手动”，以启用自动 IP 寻址。
有关访问网络菜单的具体型号说明，请单击此处。
• 步骤 4：为每个组件分配唯一的 IP 地址。
为所有组件分配相同的子网掩码。
1. 在“系统首选项”中，访问防火墙设置。
2. 如果防火墙为开启状态，打开“防火墙选项”，查看要求网络访问权限的应用程序。
3. 针对以下每一个应用程序，选择“允许入站连接”：- Wireless Workbench 6.app - snetDameon1. 打开计算机上的“Windows 防火墙”。
提示：在“开始”菜单搜索窗口中键入“允许的程序”，以快速访问防火墙设置。
2. 勾选以下应用程序的每个应用程序实例（可能有多个）旁的复选框，以允许访问域网络、专用网络和公共网络：- snetDameon - wireless workbench 6如需更多与防火墙配置有关的帮助信息，请访问 Microsoft 网站。
手动 IP 寻址选项如果您的计算机安装了防火墙，则需通过防火墙设置访问 Wireless Workbench 6 的权限。
以管理员身份登录计算机，以获取设置防火墙的所有权限，或联系您的 IT 管理员，以获取帮助。
以下章节详细介绍了如何授予 WWB6 穿透操作系统自带防火墙的访问权限。
对于第三方防火墙软件，请参阅制造商的说明手册，以向应用程序的每个实例（可能有多个实例）授予访问权限。
注：如果您收到阻止 Workbench 的警告弹出窗口，请选中允许访问所有网络（域网络、专用网络以及公共网络）的复选框。
Windows4检查连接网络故障排除及技巧症状解决方案组件显示区内未出现网络图标。
检查所有线缆和连接。
组件未出现在“目录”选项卡中。
检查 IP 地址，确认组件与计算机在同一网络上。
联机设备指示灯显示为灰色。
检查 WWB6 中的“网络首选项”，确保所选“网络接口”的地址与联网组件的 IP地址相一致。
模式：自动IP ：192.168.1.10子网掩码：255.255.255.0网关：0.0.0.0首次打开 Wireless Workbench 时，系统会提示您选择计算机与联网组件通信时使用的网络接口。
计算机与联网组件之间的 IP 地址必须在同一网络上，以确保正常通信。
1. 打开 Wireless Workbench 6。
提示：如果未显示提示，请使用以下路径访问网络设置：- Windows ：工具 > 首选项 > 网络选项卡- Mac ：Wireless Workbench 6 > 工具 > 首选项 > 网络选项卡2. “网络选择”窗口将提示您选择网络。
请在任意联网组件上打开 IP 菜单，然后记下所分配的 IP 地址，以便选择正确的接口。
有关访问网络菜单的具体型号说明，请单击此处。
在本例中，组件的 IP 地址为：192.168.1.103. 比较分配给该组件的 IP 地址和“网络选择”窗口中列出的可用 IP 地址。
选择与匹配组件 IP 地址的编号顺序和格式近似匹配的网络（在本例中，为 192.168.1）。
注：最后几个数字不会完全匹配。
4. 单击“保存”，完成网络接口选择。
选择网络接口后，检查显示屏或每个组件前面板上的网络图标 ，以确认连接。
联网组件将自动显示在“目录”选项卡中。
打开“目录”选项卡并执行以下检查，以确认连接：查看组件名称、通道名称及其他设备参数。
单击组件图标，设备的前面板闪烁，以进行远程识别。
“设备联机”指示灯显示为绿色，所列设备数应与联网组件数相符。
步骤 3：选择网络接口5扫描数据图步骤 4：扫描以查找最佳可用频率联网至 Wireless Workbench 的接收机或频谱管理器可扫描射频频谱，以查找适合您系统的最佳可用频率。
扫描结果以图形方式显示该射频频谱内的所有活动。
选择“频率协调”选项卡。
选择“更改扫描数据”按钮，打开“扫描数据”窗口。
选择“设置”按钮，打开“现场扫描设置”对话窗口。
勾选要用作扫描仪的设备复选框。
按开始按钮进行扫描。
等待两根天线完成扫描。
Wireless Workbench 可扫描整个射频频谱。
如下扫描图中的峰值表示接收机附近存在射频能。
6cont rol RF audio gai n power pus hSCANsyn cEXIT ENTER onULXD2co ntr ol R F au diog ain po we rpu shSC ANsy ncEX IT EN TE R !! ! ! !! ! ! ! ! ! !! ! !! ! ! ! ! ! 步骤 5：计算频率并将其部署至联网组件步骤 6：使用红外同步设置发射机频率在本步骤中，Wireless Workbench 将分析扫描数据并计算最佳可用频率，以确保无线系统的成功运行。
计算完成后，您可以将最终频率部署至联网组件。
选择“频率协调”选项卡。
选择“计算新频率”。
此时会打开“射频协调结果”窗口，并显示找到的最终频率。
选择“部署至目录”，将频率分配给联网组件。
所有组件上的前面板 LED 将闪烁，以确认部署。
执行红外同步可自动调节发射机的频率，与部署至接收机的频率相同。
红外同步完成后，接收机与发射机之间会形成一个匹配的无线音频通道。
发射机将显示在 Wireless Workbench 的目录中。
将发射机与接收机的红外同步窗口对准，然后按同步按钮或使用同步菜单。
更多有关您发射机、接收机型号的红外同步信息，请参阅组件用户指南。
7系统监控组件联网后，WWB6 将提供多种设备监视图：• 通道条：通道条显示基本的组件参数。
• 属性面板：该视图是最全面的特定通道监控界面，用于显示所有的可用参数。
在“监视”选项卡中，从右侧列表中选择“通道”，以查看“通道条”。
• 点击并拖动可以调整“监视”选项卡中“通道条”的位置• 要修改通道条上显示的参数，右击该通道条，然后选择“通道条设置”右击通道条上的“属性”按钮，打开“属性”面板。
该视图是最全面的特定通道监控界面，用于显示所有的可用参数。
Europe, Middle East, Africa:PT. GOSHEN SWARA INDONESIAKompleks Harco Mangga Dua Blok L No. 35 Jakarta PusatI.16.GSI31.00501.0211。