MD3000 config doc for Win
Dell PowerVault MD3000i 配置指南说明书
Dell PowerVault MD3000iConfiguration Guide for VMware ESX Server SoftwareJanuary 2008Dell Virtualization Solutions Engineering/vmwareTable of Contents1. Introduction (3)2. Architectural Setup (3)3. iSCSI Connectivity Support (4)4. PowerVault MD3000i Storage Setup and Configuration (4)5. iSCSI Software Initiator Configuration on ESX Server (5)6. Configure iSCSI storage on ESX Server (8)7. References (9)Dell Inc Page 31.IntroductionThe Dell ™PowerVault ™ MD3000i storage solution consists of a standard or high availability configuration. The standard model has a single controller with two 1GbE ports. It can be deployed to support up to 16 hosts non-redundantly. The high availability model has dual controllers with two 1GbE ports per controller for a total of four 1GbE ports. The dual controller option can connect up to 16 fully redundant hosts. This document provides instructions to setup the MD3000i iSCSI storage solution for usage with VMware® ESX Server ™ software.The Dell PowerVault MD3000i iSCSI storage array contains four Ethernet ports through which the VD can be accessed affording both redundancy and availability of data. Provisioning of storage on servers in a VM environment is a multiple step process starting with definition of the server names for host access. The iSCSI connection is then established from the storage subsystem, and after detection and configuration is established as a two way link with the associated ESX server(s), completing the iSCSI communication subsystem. The final step allocates the detected storage to the individual virtual machines (VM’s), where all or part of the configured storage can be assigned to individual VM’s.2. Architectural SetupThe following figure illustrates a typical high availability setup for using the MD3000i in an ESX Server farm. As a best practice, Dell recommends using a separate Gigabit Ethernet network switch to handle iSCSI storage traffic. Two servers are connected to two switches. Each switch has a path to the MD3000i via the two dual port controllers. In this base HA configuration, the servers, switches, and MD3000i ports share the same subnet. The NIC ports serving iSCSI traffic on the ESX servers are teamed.Figure 1: MD3000i High Availability ConfigurationLANESX Server 1MD3000iESX Server 2MD1000MD1000Ethernet Switches3.iSCSI Connectivity SupportOperating System Host Bus AdapterVMware ESX Server 3.5 iSCSI software initiator with ESX Server 4.PowerVault MD3000i Storage Setup and Configuration Create virtual disks on MD3000i using steps described in:/support/edocs/systems/md3000i/en/IG/PDF/IGbk0HR.pdf.After opening the Modular Disk Storage Manager and selecting the MD3000i storage array to be configured, select the Configure tab.Note: in the examples to follow the Storage array “sg23_training” is an MD3000i withvirtual disks already configured using the Create Virtual Disks selection. The new server being added to an existing host group is named “Valhalla”.From the Configure tab1. Select Configure Host Access (Manual).2. Enter the host name for the server which has the ESX Server software is installed.3. Select Linux as the host type.From the next screen, specify the iSCSI Initiator by selecting the New button (lower right on screen). On the Enter New iSCSI Initiator screen enter a name for the iSCSI initiator name. The label is auto-populated from the server name.Figure 2: iSCSI Initiator WindowHost Group configuratio n starts from the following screen titled “Configure Host Access (Manual) –Specify Host Group”. For ESX servers supporting VMotion, HA, and DRS, a host group must be defined so the MD3000i storage subsystem has a configured iSCSI path to each of the hosts.Select “Yes: This host will share access to the same virtual disks with other hosts”If a new host group is desired select the radio button for that option and enter in a namefor your host group using standard host naming conventions (e.g. no spaces etc).Should you already have one or more host groups assigned, select the radio buttonenabling selection from a drop down list of existing host groups. This option is to beused when configuring the second, third, etc. host in a group. Once the host group isselected previously configured hosts for that host group will be displayed. Note thatthese are shown as Linux hosts even though they are configured as ESX servers. Selecting Next provides a Confirmation screen in which the new server being configured is shown and the other previously configured associated hosts are named. For the first server configured in a new host group there will be no associated hosts listed under the Associated host group.Figure 3: Modular Disk Storage Manager Configure TabSelect Finish confirming the new host definition. This initiates the wizard configuration of the new host.On completion,Select Yes to proceed to the next host you wish to configure, orSelect No to end the configuration wizard.Helpful Hint: Record the MD3000i IP address for later configuration5.iSCSI Software Initiator Configuration on ESX ServerThis section lists the steps required to configure the software initiator on the VMware ESX Server. Connect to the ESX server/VirtualCenter using VI Client, and follow the below steps:1. Select Configuration->Security Profile on the ESX server.2. Click on Properties. The Firewall Properties box appears.Figure 5: Firewall Properties Window3. Check Software iSCSI Client.4. Select Configuration->Storage Adapters on the ESX server.5. Select iSCSI software adapter and click on Properties.Figure 6: iSCSI software adapter under Storage Adapters on VI client6. The iSCSI initiator Properties window appears.7. Under the general tab select Configure tab. Select the Enabled checkbox and click OK.Select Close.Figure 7: iSCSI software initiator properties window8. Select iSCSI software adapter under storage. You should now see your iSCSI Targetname listed.Figure 8: iSCSI software adapter after initial configuration9. Select Properties under storage adapters. Select Dynamic Discovery. Select Add.Provide the IP address of the MD3000i and click OK. There may be a slight delay before the process completes.Figure 9: iSCSI software initiator properties window10. Click Close.6.Configure iSCSI storage on ESX ServerConnect to the ESX server/Virtual Center using VI Client and follow the steps below.1. Go to the configuration tab and select Storage Adapters. Select the iSCSI SoftwareAdapter and click Rescan. The newly created iSCSI target and LUN should be visiblefrom the ESX server.Figure 10: iSCSI target and LUNs as visible through VI client2. Go to the configuration tab and select Storage. Click on Add Storage, select Disk/Lunand click Next. Select the newly added storage and click Next.3. Select the newly created iSCSI LUN and click Next.4. Review the disk layout and click Next.5. Provide a name for the VMFS datastore and click Next.6. Select the appropriate block size and capacity for the VMFS datastore and click Next.7. Review the disk layout and click Finish to create the VMFS datastore. The new datastoreis now ready to be used for storing virtual machine images.7. References1. Dell PowerVault MD3000i support documents:/support/edocs/systems/md3000i/2. Drivers download page for MD3000i:/support/downloads/driverslist.aspx?c=us&cs=555&l=en&s=biz&Se rviceTag=&SystemID=PWV_MD3000I&os=NAA&osl=EN3. VMware Virtual Infrastructure 3 Documentation:/support/pubs/vi_pubs.html4. Dell|VMware alliance home page: /vmwareTHIS DOCUMENT IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND.Microsoft and Windows are registered trademarks of Microsoft Corporation. VMware is a registered trademark and VMotion, Virtual SMP, and ESX Server are trademarks of VMware, Inc. Intel and Xeon are registered trademarks of Intel Corp. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others.Copyright 2007 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. Information in this document is subject to change without notice.。
发那科机器人焊接应用IO配置(总线型)
发那科机器人焊接应用的I/O配置(总线型)<H2><A NAME="1">Version Information</A></H2> <PRE><A HREF="#TOP">【TOP】</A><br>F Number: YH14979VERSION : SpotTool+$VERSION: V7.5093 06/14/2010DATE: 14-AUG-11 18:21VERSION INFORMATION::SOFTWARE: ID:SpotTool+ 7DA5/12S/W Serial No. : 88150Controller ID : YH14979Default Personality (from FD)R-2000iB/210F V7.50P/12Servo Code : V15.01Cart. Mot. Parameter: V3.00JNT. Mot. Parameter : V3.00DCS : NoneSoftware Edition No.: V7.50P/12Update Version : NoneCustomization Ver. : NoneRoot Version : V7.5093Boot MONITOR : V7.70P/06Teach Pendant : 7D0F/01MBrowser Plugins : V7.7004TP Core Firmware : V7.7004Media from FRL 06/24/2010CONFIG::FEATURE: ORD NO:SpotTool+ H590English Dictionary H521Multi Language (CHIN) H539AA Vision Mastering AAVMAnalog I/O H550Auto Software Update ATUPAutomatic Backup J545Background Editing J616Camera I/F VCAMCell I/O CLIOCommon shell R645Common shell core CMSC Common so CMSP Common style select STYL Condition Monitor J628 Constant Path R663 Control Reliable CNRE Corner Region R654 Diagnostic log RSCH Disable Faults CDSB Dispense Plug-in SPLG Dual Check Safety UIF DCSU Enhanced Mirror Image R698 Enhanced Rob Serv Req ORSR Enhanced T1 Mode R680 Enhanced User Frame J604 Ext. DIO Config EIOC Extended Error Log R542 External DI BWD ESET FCTN Menu Save J516J716Group Mask Exchange MASK High-Speed Skip J627 Host Communications HOCO Hour Meter J513 I/O Interconnect 2 J542Incr Instruction J510 KAREL Cmd. Language J650 KAREL Run-Time Env J539 Kernel + Basic S/W H510 License Checker LCHK LogBook(System) OPLG MACROs, Skip/Offset J503 MH gripper common MHGC Mat.Handling Option MPLG MechStop Protection MCSP Mirror Shift J506 Mixed logic J554 Mode Switch MDSW Motion logger R637 Multi Appl Enabler MAEN Multi Equipment J617 Multi-Tasking J600 Position Registers J514 Print Function J507Prog Num Selection J515 Program Adjust J517 Program Shift J505 Program Status PRST Program ToolBox R598 RDM Robot Discovery FRDM Robot Service Request SRSR Robot Servo Code H930 SNPX basic SNBA Seal Common SLCM Shift Library SHLB Shift and Mirror Lib SMLB Soft Parts in VCCM SPVC Spot Plug-in SPPG TCP Auto Set J520 TCP Speed Prediction J524 TCP/IP Interface HTCP TMILIB Interface TMIL TP Menu Accounting TPAC TPTX TPTX Telnet Interface TELN Tool Offset J509 Unexcepted motn Check UECK User Frame UFRM Vision Core VCOR Vision Library VIPL Vision SP CSXC CSXC Vision Shift Tool CVVF Web Server HTTP Web Svr Enhancements R626 iPendant CGTP iPendant Grid Display IGUI iPendant Setup IPGSR-2000iB/210F H601 Servo Gun Axes H869 Auto Tuning CS J952 Collision Guard R534 Collision Guard Pack J684 Cycle Time Priority J523 DeviceNet Interface J753 DeviceNet(Slave) J754 Disp 2nd analog port R528 Extended Axis Control J518 Extended User Frames R696FANUC ServoGun Change J665 FRL Params R651 HMI Device (SNPX) R553 Multi-Group Motion J601 PC Interface R641 PMC(FAPT Ladder) J760 Password Protection J541 ROS Ethernet Packets R603 Servo Gun Option J643 Servo Gun WT Compens J933 Space Check J609 USB port on iPendant J957 YELLOW BOX J775 iRCalibration VShift J994Arc Advisor R666 Aux Servo Code SVMO Common calib UIF CUIF Cycle time Opt. CTOP Extended Axis Speed EXTS Func stup FCSP HTTP Proxy Svr PRXY High Speed ServoGun J886 IntelligentTP PC I/F J770JPN ARCPSU PRM J885 Motherboard driver MOBO PC Send Macros SEND Pressure Control PCTL Requires CP CPRQ Robot Library Setup RLCM SSPC error text ETSS Servo Gun Core J670 Servo Hand Change SVHC Sgdiag core SGDG Socket Messaging R636 Soft Limit SLMT TCPP Extention TCPE VCalibration Common VCCM VisShift I/F Common CVVC Vision Shift Common CVVS istdpnl IPNL iPendant HMI Setup U001 RM HELP INCL VIS PKGS U004 SMB TP Backup U006 RIPE GET_VAR FIX U007FLEXTOOL: ADD R729.FD U008 CVIS ADD EP ADV PKG U009 CVIS NO WTWTEST LOAD U010 LOAD HELP FOR SELECT U011 FALSE ALARM CPMO-130 U012 MD: HANG FROM INTP U013 R709 DRAM AVAILCHECKS U014 CVIS VPCS SUPP LIMCHK U015 CVIS VPFF POS DIF FIX U0168-12 CHARACTER PROGRA U017 SAVE FRAMEVAR.SV U018 TP Enable NOAM U026 STRCTURE SHADOW UPDAT U027 RIPE STATICS TOO MUCH U028 TIMQ MOTN-003 U030 ROBOGUIDE DAUGHTER U032 Disable touch in Edit U033 PATH NODE MOVETO U035 RIPEREMOVE TIME RETRY U038 VMXPACK MAY ASSERT U039 CYCLE DATA MAY BE COR U040 TOO MANY ARC OPTIONS U043 PMC Display wait fix U044 APSH-171 fix U045 SLOW T1 MOTN U046 GET_POS_TPE fix U047 jog disable by app wa U048 CVIS VPEP HIST RT FIX U049 MXSPD TB CPMO003 U050 CVIS BARCODE ENHANCE U051 prv save may not work U052 High RIPE traffic fix U053print from sysvar scr U054 PROGRAM ADJUST FOR SH U058 RIPE/GETSET ERROR HAN U060 IPENDANT SCREEN UNREA U061 HANDLE PART CORRECTIO U064 NO ED U066CVIS EP PKG INCL SVIP U067SIX DIGIT VERSIONS U068 CVIS NEW VERSION P06 U069 IMAGE SAVE LOAD U070 DISP PROC ISSUE U071 REPLAN JOINT DELTA U078TP EDIT CALLFROM FIX U079 CVIS FIX IPNDT RT IMG U080 $coord_mask default U084R719 ENHANCEMNT/FIXES U085 Local Hold TIMQ Adjus U097 PG: CHDELMON can caus U100 CVIS: 3D multi-view d U101 Increase Number of FD U103 KAREL CANNOT ACCESS M U104 Robot Settings are lo U108 PAINT - Wait/Release U109 FlexTool: Backward mo U114 PAINT - PaintPRO Repa U117 EDIT SCREEN IS CLOSED U500 ANTIDEFECT UIF FIX U507 PNIO V750 FIX1 U509 FIX LOADING DB SYSVAR U510 FIX EDGE DETECTION U511 ONLINE HELP BUGFIX U512 CVIS: CAM CALIB FIX U514 DISP CUSTOM FOR SSGUN U515 FIX ABC JARKY MOTION U517 MILLIMETER CONVERSION U518 GARBLED STR REG U519 ALARM TEXT BUG FIX U520 DISP CUST DRY FOR SSG U521 IMPROVE LWR DETECTION U523 CVIS FREEZE VLOG TASK U525VP2S MM CONVERSION U526 FIX TP FREEZE IBPX U527FX DB/TB BUSY RUNNING U528 RECORD CALIBRATION LO U529 DIV CALCULATION FIX U530 FIX FOR BWD RETURN U531 CONDITION MONITOR FIX U532 VOFS: UNEXP ALARM FIX U533 FIX SERVO GUN TEXT U534 FIX FENCE SVEMG ABNML U535 DCS CC_SAFEIO ALARM U537 IMPROVED GUN TOUCHUP U540 FIX GUN CHG WITH DNET U541 UPDATE GUNTCH PAEAMS U542 DOT PETTERN BUG U543 CVIS: IRVISION BUG FI U544UPDATE SVGN ERROR TXT U545FIX TOOLCHG WITH DNET U546MLOCK CHK WITH GUNCHG U547MECH COMP FOR GUNTCH U549IMPROVE GUNTCH PARAMS U550VISION MEMORY LEAK U551FIX UNWANTED MESSAGE U552SUPPORT DET SOFT WORK U553CVIS:SPEC CHANGE OF V U554GRID DETECT BUG FIX U559MOTOR::GR: AX: MOTOR ID AND INFO:1 1 ACaiSR30/3000 80A H1 DSP1-L1 2 ACaiSR30/3000 80A H2 DSP1-M1 3 ACaiSR30/3000 80A H3 DSP1-J1 4 ACa12/4000iS 40A H4 DSP1-K1 5 ACa12/4000iS 40A H5 DSP2-L1 6 ACa12/4000iS 40A H6 DSP2-M1 7 aiF22/3000 80A H DSP -2 1 aiS8/4000 80A H DSP -SERVO::GROUP: AXIS: SERVO PARAM ID:1 1 P02.061 2 P02.061 3 P02.061 4 P02.061 5 P02.061 6 P02.061 7 P00.392 1 P00.39</PRE><H2><A NAME="2">Memory Detail</A></H2> <PRE><A HREF="#TOP">【TOP】</A><P>MEMORY USAGE::MEMORY DETAIL (MAIN):Pools TOTAL AVAILABLE LARGEST TPP 800.0KB 577.8KB 555.0KB PERM 1978.0KB 371.6KB 366.5KB SYSTEM 7182.0KB 2.5KB 2.5KBSHADOW 5894.5KB 5556.5KB 32.0KBTEMP 21052.5KB 1422.8KB 714.2KBFROM 31857.0KB 9258.0KB .0KBHARDWAREFROM 32MBDRAM 32MBSRAM 2MBMEMORY DETAIL (COMM):Pools TOTAL AVAILABLE LARGESTTPP 0.0KB 0.0KB 0.0KBPERM 48.0KB 47.8KB 47.8KBSYSTEM 6144.0KB 5553.0KB 5553.0KBSHADOW 5894.5KB 5556.5KB 32.0KBTEMP 9844.5KB 8201.3KB 7949.9KB</PRE><H2><A NAME="3">Program Status Information</A></H2><PRE><A HREF="#TOP">【TOP】</A><P>TASK STATES:1 RESET status = ABORTED****** History Data ******Routine depth: 0 Routine: RESETLine: 1 Program: RESET Type: TP 2 STHICHNG status = ABORTED****** History Data ******Routine depth: 0 Routine: STHICHNGLine: 128 Program: STHICHNG Type: PC 3 PNLINST status = ABORTED****** History Data ******Routine depth: 0 Routine: PNLINSTLine: 223 Program: PNLINST Type: PC 4 PSCOLD status = ABORTED****** History Data ******Routine depth: 0 Routine: PSCOLDLine: 93 Program: PSCOLD Type: PC5 SYRSRUTL status = ABORTED****** History Data ******Routine depth: 0 Routine: SYRSRUTLLine: 63 Program: SYRSRUTL Type: PC 6 SVGNCH status = ABORTED****** History Data ******Routine depth: 0 Routine: SVGNCHLine: 287 Program: SVGNCH Type: PC 7 SGDIAINI status = ABORTED****** History Data ******Routine depth: 0 Routine: SGDIAINILine: 204 Program: SGDIAINI Type: PC8 ATSHELL RUNNING @ 1055 in ATSHELL of ATSHELL****** History Data ******Routine depth: 0 Routine: ATSHELLLine: 1055 Program: ATSHELL Type: PC 9 LOADCELL status = ABORTED****** History Data ******Routine depth: 0 Routine: PBCORELine: 0 Program: PBCORE Type: 0 10 MHGRSHLL RUNNING @ 1213 in MHGRSHLL of MHGRSHLL****** History Data ******Routine depth: 0 Routine: MHGRSHLLLine: 1213 Program: MHGRSHLL Type: PC 11 SWAXTSK1 RUNNING @ 758 in PROCESSAMR of SWAXTCMN****** History Data ******Routine depth: 1 Routine: PROCESSAMRLine: 758 Program: SWAXTCMN Type: PC Routine depth: 0 Routine: SWAXTSK1Line: 172 Program: SWAXTSK1 Type: PC12 SWAXTSK2 RUNNING @ 758 in PROCESSAMR of SWAXTCMN****** History Data ******Routine depth: 1 Routine: PROCESSAMRLine: 758 Program: SWAXTCMN Type: PCRoutine depth: 0 Routine: SWAXTSK2Line: 120 Program: SWAXTSK2 Type: PC 13 SLCUSTOM RUNNING @ 1647 in SLCUSTOM of SLCUSTOM****** History Data ******Routine depth: 0 Routine: SLCUSTOMLine: 1647 Program: SLCUSTOM Type: PC 14 SWIMSET status = ABORTED****** History Data ******Routine depth: 0 Routine: SWIMSETLine: 348 Program: SWIMSET Type: PC</PRE><H2><A NAME="4">I/O status information</A></H2><PRE><A HREF="#TOP"></A><P>IO STATUS::DIN【1】OFFDIN【2】OFFDIN【3】OFFDIN【4】OFFDIN【5】OFF UPPER TIP RESETDIN【6】OFF LOWER TIP RESETDIN【7】OFF TEST RUNDIN【8】OFF TIP CHANGE COMPLETEDIN【9】OFFDIN【10】OFFDIN【11】OFF DRESS_1 COMPLETEDIN【12】OFF DRESS_2 COMPLETEDIN【13】OFF DRESS_1 ADV.LSDIN【14】OFF DRESS_2 ADV.LSDIN【15】OFF DRESS_1 RET.LSDIN【16】OFF DRESS_2 RET.LSDIN【17】OFFDIN【18】OFFDIN【19】OFF TC1 5STEP 1DIN【20】OFF TC1 5STEP 2DIN【21】OFF TC1 5STEP 3DIN【22】OFF TC1 5STEP 4DIN【23】OFF TC2 5STEP 1DIN【24】OFF TC2 5STEP 2DIN【25】OFF TC2 5STEP 3DIN【26】OFF TC2 5STEP 4DIN【27】OFF POP WELD COMPLETE DIN【28】OFFDIN【29】OFFDIN【30】OFFDIN【31】OFF GUN COVER OPENDIN【32】ON GUN COVER CLOSE LS DIN【33】OFF HAND COVER OPEN DIN【34】ON HAND COVER CLOSE DIN【35】OFF AHC COVER-3 OPEN LS DIN【36】OFF AHC COVER-3 CLOSE LS DIN【37】OFF AHC COVER-4 OPEN LS DIN【38】OFF AHC COVER-4 CLOSE LS DIN【39】OFF GUN1 2ND ST OPEN LS DIN【40】OFF GUN2 2ND ST OPEN LS DIN【41】OFF CHUCK OPEN CONFIRM DIN【42】ON CHUCK CLOSE CONFIRM DIN【43】ON AHC FACEDIN【44】OFFDIN【45】OFFDIN【46】OFFDIN【47】OFF ROBOT 2ND STARTDIN【48】OFFDIN【49】OFF WELD COMPLETEDIN【50】OFFDIN【51】OFFDIN【52】OFFDIN【53】OFFDIN【54】OFFDIN【55】ON STYLE1DIN【56】OFF STYLE2DIN【57】OFF STYLE4DIN【58】OFF STYLE8DIN【59】OFF STYLE16DIN【60】OFF STYLE32DIN【61】OFF STYLE64DIN【62】OFF STYLE128DIN【63】OFF GUN1 STEADDIN【64】OFF HAND STEADDIN【65】OFF TOOL STEAD 3DIN【66】OFF TOOL STEAD 4DIN【67】OFFDIN【68】OFFDIN【69】OFFDIN【70】OFFDIN【71】OFF Jig Non-int.DIN【72】OFF Shuttle Nnn-int.DIN【73】OFFDIN【74】OFF Weld Enable 1DIN【75】OFF Weld Enable 2DIN【76】ON Robot_G Weld Comp.1 DIN【77】OFFDIN【78】OFFDIN【79】ON Pick Up Ok Feeder DIN【80】OFFDIN【81】OFF Hand Jig Conf.DIN【82】OFF Hand Rock Adv Comp DIN【83】OFF Jig Cover Close Comp. DIN【84】OFF Hand Rock Ret Comp. DIN【85】OFF Jig Cover Open Comp. DIN【86】ON Robct_G I/L1DIN【87】ON Robot_G I/L2DIN【88】OFFDIN【89】OFFDIN【90】OFFDIN【91】OFFDIN【92】OFFDIN【93】OFFDIN【94】OFF Sealer HoldDIN【95】OFFDIN【96】OFFDIN【97】OFFDIN【98】OFFDIN【99】OFFDIN【100】OFFDIN【101】OFFDIN【102】OFFDIN【103】OFFDIN【104】OFFDIN【105】OFFDIN【106】OFF PART IN STATION CONFIRM DIN【107】ON ROBOT AWAY FROM STATION DIN【108】OFFDIN【109】ON GUN IN STATIONDIN【110】OFF HANDKING IN STATIONDIN【113】ON SEALING MATERIAL OKDIN【114】OFF SEALING MATERIAL LACKING DIN【115】OFFDIN【116】OFF HEATING NOT OKDIN【117】OFFDIN【118】OFFDIN【119】OFFDIN【120】OFFDIN【121】OFFDIN【122】OFFDIN【123】OFFDIN【124】OFFDIN【125】OFFDIN【126】OFFDIN【127】OFFDIN【128】OFFDIN【129】OFF Clamp 1 openDIN【130】ON Clamp 1 closedDIN【131】OFF Clamp 2 openDIN【132】ON Clamp 2 closedDIN【133】OFF Clamp 3 openDIN【134】ON Clamp 3 closedDIN【135】OFF Clamp 4 openDIN【136】ON Clamp 4 closedDIN【137】OFF Clamp 5 openDIN【138】ON Clamp 5 closedDIN【139】OFF Clamp 6 openDIN【140】ON Clamp 6 closedDIN【141】OFF _DIN【142】OFF _DIN【143】OFF _DIN【144】OFF _DIN【145】OFF Part present 1DIN【146】OFF Part present 2DIN【147】OFFDIN【148】OFFDIN【149】OFF 2-1-ONDIN【150】ON 2-1-OFFDIN【151】OFF 2-2-ONDIN【152】ON 2-2-OFFDIN【153】ON 2-3-OFFDIN【154】ON 2-4-OFFDIN【155】OFFDIN【156】OFFDIN【157】ON 3-1-OFFDIN【158】OFF 3-1-ONDIN【159】ON 3-2-OFFDIN【160】OFF 3-2-ONDOUT【1】OFF ROBOT USER ALARM DOUT【2】OFF STYLE VAERITY FAULT DOUT【3】OFFDOUT【4】OFFDOUT【5】OFF GUN COVER OPENDOUT【6】OFF GUN COVER CLOSEDOUT【7】OFF HAND COVER OPEN DOUT【8】OFF HAND COVER CLOSE DOUT【9】OFF AHC COVER-3 OPEN DOUT【10】OFF AHC COVER-3 CLOSE DOUT【11】OFF AHC COVER-4 OPEN DOUT【12】OFF AHC COVER-4 CLOSE DOUT【13】OFFDOUT【14】OFF TIP WEAR OVER MOVE DOUT【15】OFF TIP WEAR OVER FIXDOUT【16】OFF TIP CHANGE POSITION DOUT【17】OFF TC1 GUN FAULT CHECK DOUT【18】OFF TC1 OFF_SET MEASURING DOUT【19】OFFDOUT【20】OFFDOUT【21】OFFDOUT【22】OFFDOUT【23】OFFDOUT【24】OFFDOUT【25】OFFDOUT【26】OFFDOUT【27】OFFDOUT【28】OFFDOUT【29】OFF DRESSOR-1 STARTDOUT【30】OFF DRESSOR-2 STARTDOUT【31】OFF DRESSOR SHIFT1 ADV.SERVO DOUT【32】OFF DRESSOR SHIFT2 ADV.SERVO DOUT【33】OFF POP START1DOUT【34】OFF POP START2DOUT【35】OFF POP START3DOUT【36】OFF POP START4DOUT【37】OFF POP WELD CONDITION 1 DOUT【38】OFF POP WELD CONDITION 2 DOUT【39】OFF POP WELD CONDITION 4 DOUT【40】OFF POP WELD CONDITION 8 DOUT【41】OFF POP WELD CONDITION 16 DOUT【42】OFF POP WELD CONDITION 32 DOUT【43】OFF POP SWING ADV.DOUT【44】OFFDOUT【45】OFF WORK COMPLETE DOUT【46】ON Shuttle Run Enable DOUT【47】OFF 2nd Work Comp.DOUT【48】OFF GUN1 PRESSDOUT【49】OFFDOUT【50】OFFDOUT【51】OFF UNCHUCK POSITION DOUT【52】OFF AHC FaceDOUT【53】OFF CHUCK OPENDOUT【54】ON CHUCK CLOSEDOUT【55】OFF Sealer FaultDOUT【56】OFF Sealer EM.StopDOUT【57】OFF Sealer LowDOUT【58】OFF SEAL AIR PRESSDOUT【59】OFFDOUT【60】OFFDOUT【61】OFF WELD CONDITION 1 DOUT【62】OFF WELD CONDITION 2 DOUT【63】OFF WELD CONDITION 4 DOUT【64】OFF WELD CONDITION 8 DOUT【65】OFF WELD CONDITION16 DOUT【66】OFF WELD CONDITION32 DOUT【67】OFF WELD CONDITION64 DOUT【68】OFF WELD CONDITION128 DOUT【69】ON Jig Non-int.DOUT【70】ON Shuttle Non-int.DOUT【71】OFF Tip Change Run.DOUT【72】OFF Tip Dress Run.DOUT【73】OFFDOUT【74】OFFDOUT【75】OFFDOUT【76】OFFDOUT【77】ON Fdr. Non-int.DOUT【78】OFF Fdr. unload comp.DOUT【79】OFFDOUT【80】OFF Jig Hand ClampDOUT【81】OFF Jig Cover CloseDOUT【82】OFF Jig Hand UnclampDOUT【83】OFF Jig Cover OpenDOUT【84】ON Robot_G I/L1DOUT【85】ON Robot_G I/L2DOUT【86】OFFDOUT【87】OFFDOUT【88】OFFDOUT【89】OFFDOUT【90】OFF SEALING MATERIAL LACKING DOUT【91】OFF SEALING HEATING NOT OK DOUT【92】OFF SEALING GUN OPEN DOUT【93】OFFDOUT【94】OFF CC-LINK STATUSDOUT【95】OFF CC-LINK STATUSDOUT【96】OFF CC-LINK STATUSDOUT【97】OFF CC-LINK STATUSDOUT【98】OFF CC-LINK STATUSDOUT【99】OFF CC-LINK STATUSDOUT【100】OFF CC-LINK STATUSDOUT【101】OFF CC-LINK STATUSDOUT【102】OFFDOUT【103】OFFDOUT【104】OFF JIG CLAMP OPEN REQUEST DOUT【105】OFFDOUT【106】OFF PART IN STATIONDOUT【107】OFFDOUT【108】OFFDOUT【113】OFF SEALING STARTDOUT【114】ON SEALING STOPDOUT【115】OFFDOUT【116】OFFDOUT【117】OFFDOUT【118】OFFDOUT【119】OFFDOUT【120】OFFDOUT【121】OFFDOUT【122】OFFDOUT【123】OFFDOUT【124】OFFDOUT【125】OFFDOUT【127】OFFDOUT【128】OFFDOUT【129】OFF SPAREDOUT【130】OFF SPAREDOUT【131】OFF CLAMP_3_ON DOUT【132】ON CLAMP_3_OFF DOUT【133】OFF CLAMP_2_ON DOUT【134】ON CLAMP_2_OFF DOUT【135】OFF CLAMP_1_ON DOUT【136】ON CLAMP_1_OFF DOUT【137】OFF SPAREDOUT【138】OFF SPAREDOUT【139】OFF _DOUT【140】OFF _DOUT【141】OFF _DOUT【142】OFF _DOUT【143】OFF _DOUT【144】OFF _GIN【1】 1 Style No.GOUT【1】0UI【1】ON *IMSTPUI【2】ON *HoldUI【3】ON *SFSPDUI【4】OFF Cycle stopUI【5】OFF Fault resetUI【6】OFF StartUI【7】OFF HomeUI【8】ON EnableUI【9】OFF RSR1/PNS1UI【10】OFF RSR2/PNS2UI【11】OFF RSR3/PNS3UI【12】OFF RSR4/PNS4UI【13】OFF RSR5/PNS5UI【14】OFF RSR6/PNS6UI【15】OFF RSR7/PNS7UI【16】OFF RSR8/PNS8UI【17】OFF PNS strobeUI【18】OFF Prod startUO【1】ON Cmd enabled UO【2】ON System ready UO【3】OFF Prg runningUO【4】OFF Prg pausedUO【5】OFF Motion heldUO【7】ON At perchUO【8】OFF TP enabledUO【9】OFF Batt alarmUO【10】OFF BusyUO【11】OFF ACK1/SNO1UO【12】OFF ACK2/SNO2UO【13】OFF ACK3/SNO3UO【14】OFF ACK4/SNO4UO【15】OFF ACK5/SNO5UO【16】OFF ACK6/SNO6UO【17】OFF ACK7/SNO7UO【18】OFF ACK8/SNO8UO【19】OFF SNACKUO【20】OFF ReservedSI【1】OFF Fault resetSI【2】ON RemoteSI【3】ON HoldSI【4】OFF User PB#1SI【5】OFF User PB#2SI【6】OFF Cycle startSI【7】OFFSI【8】ON CE/CRｓｅｌｅｃｔb0 SI【9】ON CE/CRｓｅｌｅｃｔb1 SI【10】OFFSI【11】OFFSI【12】OFFSI【13】OFFSI【14】OFFSI【15】OFFSI【16】ONSO【1】OFF Cycle startSO【2】OFF HoldSO【3】OFF Fault LEDSO【4】OFF Batt alarmSO【5】OFF User LED#1SO【6】ON User LED#2SO【7】OFF TP enabledSO【8】OFFSO【9】OFFSO【10】OFFSO【11】OFFSO【12】OFFSO【13】OFFSO【15】OFFSO【16】ONUI【1】ON *IMSTPUI【2】ON *HoldUI【3】ON *SFSPDUI【4】OFF Cycle stopUI【5】OFF Fault resetUI【6】OFF StartUI【7】OFF HomeUI【8】ON EnableUI【9】OFF RSR1/PNS1UI【10】OFF RSR2/PNS2UI【11】OFF RSR3/PNS3UI【12】OFF RSR4/PNS4UI【13】OFF RSR5/PNS5UI【14】OFF RSR6/PNS6UI【15】OFF RSR7/PNS7UI【16】OFF RSR8/PNS8UI【17】OFF PNS strobeUI【18】OFF Prod startUO【1】ON Cmd enabled UO【2】ON System ready UO【3】OFF Prg running UO【4】OFF Prg paused UO【5】OFF Motion held UO【6】OFF FaultUO【7】ON At perchUO【8】OFF TP enabled UO【9】OFF Batt alarm UO【10】OFF BusyUO【11】OFF ACK1/SNO1 UO【12】OFF ACK2/SNO2 UO【13】OFF ACK3/SNO3 UO【14】OFF ACK4/SNO4 UO【15】OFF ACK5/SNO5 UO【16】OFF ACK6/SNO6 UO【17】OFF ACK7/SNO7 UO【18】OFF ACK8/SNO8 UO【19】OFF SNACKUO【20】OFF ReservedRI【1】OFFRI【2】OFFRI【3】OFFRI【5】OFFRI【6】OFFRI【7】OFFRI【8】OFFRO【1】OFFRO【2】OFFRO【3】OFFRO【4】OFFRO【5】OFFRO【6】OFFRO【7】OFFRO【8】OFF</PRE><H2><A NAME="5">I/O Configuration Information</A></H2> <PRE><A HREF="#TOP">【TOP】</A><P>IO CONFIGURATION::DIN【5】UPPER TIP RESETDIN【6】LOWER TIP RESETDIN【7】TEST RUNDIN【8】TIP CHANGE COMPLETEDIN 1 - 8 RACK: 81 SLOT: 15 PORT: 19DIN【11】DRESS_1 COMPLETEDIN【12】DRESS_2 COMPLETEDIN【13】DRESS_1 ADV.LSDIN【14】DRESS_2 ADV.LSDIN【15】DRESS_1 RET.LSDIN【16】DRESS_2 RET.LSDIN 9 - 16 RACK: 81 SLOT: 15 PORT: 27DIN【19】TC1 5STEP 1DIN【20】TC1 5STEP 2DIN【21】TC1 5STEP 3DIN【22】TC1 5STEP 4DIN【23】TC2 5STEP 1DIN【24】TC2 5STEP 2DIN 17 - 24 RACK: 81 SLOT: 15 PORT: 35DIN【25】TC2 5STEP 3DIN【26】TC2 5STEP 4DIN【27】POP WELD COMPLETEDIN【31】GUN COVER OPENDIN【32】GUN COVER CLOSE LSDIN 25 - 32 RACK: 81 SLOT: 15 PORT: 43DIN【33】HAND COVER OPENDIN【34】HAND COVER CLOSEDIN【35】AHC COVER-3 OPEN LSDIN【36】AHC COVER-3 CLOSE LSDIN【37】AHC COVER-4 OPEN LSDIN【38】AHC COVER-4 CLOSE LSDIN【39】GUN1 2ND ST OPEN LSDIN【40】GUN2 2ND ST OPEN LSDIN 33 - 40 RACK: 81 SLOT: 15 PORT: 51 DIN【41】CHUCK OPEN CONFIRMDIN【42】CHUCK CLOSE CONFIRMDIN【43】AHC FACEDIN【47】ROBOT 2ND STARTDIN 41 - 48 RACK: 81 SLOT: 15 PORT: 59 DIN【49】WELD COMPLETEDIN【55】STYLE1DIN【56】STYLE2DIN 49 - 56 RACK: 81 SLOT: 15 PORT: 67 DIN【57】STYLE4DIN【58】STYLE8DIN【59】STYLE16DIN【60】STYLE32DIN【61】STYLE64DIN【62】STYLE128DIN【63】GUN1 STEADDIN【64】HAND STEADDIN 57 - 64 RACK: 81 SLOT: 15 PORT: 75 DIN【65】TOOL STEAD 3DIN【66】TOOL STEAD 4DIN【71】Jig Non-int.DIN【72】Shuttle Nnn-int.DIN 65 - 72 RACK: 81 SLOT: 15 PORT: 83 DIN【74】Weld Enable 1DIN【75】Weld Enable 2DIN【76】Robot_G Weld Comp.1DIN【79】Pick Up Ok FeederDIN 73 - 80 RACK: 81 SLOT: 15 PORT: 91 DIN【81】Hand Jig Conf.DIN【82】Hand Rock Adv CompDIN【83】Jig Cover Close Comp.DIN【84】Hand Rock Ret Comp.DIN【85】Jig Cover Open Comp.DIN【86】Robct_G I/L1DIN【87】Robot_G I/L2DIN 81 - 88 RACK: 81 SLOT: 15 PORT: 99DIN【94】Sealer HoldDIN 89 - 96 RACK: 81 SLOT: 15 PORT: 107 DIN【101】DIN【104】DIN 97 - 104 RACK: 81 SLOT: 15 PORT: 115 DIN【106】PART IN STATION CONFIRMDIN【107】ROBOT AWAY FROM STATIONDIN【109】GUN IN STATIONDIN【110】HANDKING IN STATIONDIN 105 - 110 RACK: 81 SLOT: 15 PORT: 123 DIN【113】SEALING MATERIAL OKDIN【114】SEALING MATERIAL LACKINGDIN【116】HEATING NOT OKDIN 113 - 120 RACK: 82 SLOT: 6 PORT: 1 DIN 121 - 128 RACK: 82 SLOT: 6 PORT: 9 DIN【129】Clamp 1 openDIN【130】Clamp 1 closedDIN【131】Clamp 2 openDIN【132】Clamp 2 closedDIN【133】Clamp 3 openDIN【134】Clamp 3 closedDIN【135】Clamp 4 openDIN【136】Clamp 4 closedDIN 129 - 136 RACK: 82 SLOT: 4 PORT: 1 DIN【137】Clamp 5 openDIN【138】Clamp 5 closedDIN【139】Clamp 6 openDIN【140】Clamp 6 closedDIN【141】_DIN【142】_DIN【143】_DIN【144】_DIN 137 - 144 RACK: 82 SLOT: 4 PORT: 9 DIN【145】Part present 1DIN【146】Part present 2DIN【149】2-1-ONDIN【150】2-1-OFFDIN【151】2-2-ONDIN【152】2-2-OFFDIN 145 - 152 RACK: 82 SLOT: 5 PORT: 1 DIN【153】2-3-OFFDIN【154】2-4-OFFDIN【157】3-1-OFFDIN【158】3-1-ONDIN【159】3-2-OFFDIN【160】3-2-ONDIN 153 - 160 RACK: 82 SLOT: 5 PORT: 9 DOUT【1】ROBOT USER ALARMDOUT【2】STYLE VAERITY FAULTDOUT【5】GUN COVER OPENDOUT【6】GUN COVER CLOSEDOUT【7】HAND COVER OPENDOUT【8】HAND COVER CLOSEDOUT 1 - 8 RACK: 81 SLOT: 15 PORT: 21 DOUT【9】AHC COVER-3 OPENDOUT【10】AHC COVER-3 CLOSEDOUT【11】AHC COVER-4 OPENDOUT【12】AHC COVER-4 CLOSEDOUT【14】TIP WEAR OVER MOVEDOUT【15】TIP WEAR OVER FIXDOUT【16】TIP CHANGE POSITIONDOUT 9 - 16 RACK: 81 SLOT: 15 PORT: 29 DOUT【17】TC1 GUN FAULT CHECKDOUT【18】TC1 OFF_SET MEASURINGDOUT 17 - 24 RACK: 81 SLOT: 15 PORT: 37 DOUT【29】DRESSOR-1 STARTDOUT【30】DRESSOR-2 STARTDOUT【31】DRESSOR SHIFT1 ADV.SERVODOUT【32】DRESSOR SHIFT2 ADV.SERVODOUT 25 - 32 RACK: 81 SLOT: 15 PORT: 45 DOUT【33】POP START1DOUT【34】POP START2DOUT【35】POP START3DOUT【36】POP START4DOUT【37】POP WELD CONDITION 1DOUT【38】POP WELD CONDITION 2DOUT【39】POP WELD CONDITION 4DOUT【40】POP WELD CONDITION 8DOUT 33 - 40 RACK: 81 SLOT: 15 PORT: 53 DOUT【41】POP WELD CONDITION 16DOUT【42】POP WELD CONDITION 32DOUT【43】POP SWING ADV.DOUT【45】WORK COMPLETEDOUT【46】Shuttle Run EnableDOUT【47】2nd Work Comp.DOUT【48】GUN1 PRESSDOUT 41 - 48 RACK: 81 SLOT: 15 PORT: 61 DOUT【51】UNCHUCK POSITIONDOUT【52】AHC FaceDOUT【53】CHUCK OPENDOUT【54】CHUCK CLOSEDOUT【55】Sealer FaultDOUT【56】Sealer EM.StopDOUT 49 - 56 RACK: 81 SLOT: 15 PORT: 69 DOUT【57】Sealer LowDOUT【58】SEAL AIR PRESSDOUT【61】WELD CONDITION 1DOUT【62】WELD CONDITION 2DOUT【63】WELD CONDITION 4DOUT【64】WELD CONDITION 8DOUT 57 - 64 RACK: 81 SLOT: 15 PORT: 77 DOUT【65】WELD CONDITION16DOUT【66】WELD CONDITION32DOUT【67】WELD CONDITION64DOUT【68】WELD CONDITION128DOUT【69】Jig Non-int.DOUT【70】Shuttle Non-int.DOUT【71】Tip Change Run.DOUT【72】Tip Dress Run.DOUT 65 - 72 RACK: 81 SLOT: 15 PORT: 85 DOUT【77】Fdr. Non-int.DOUT【78】Fdr. unload comp.DOUT【80】Jig Hand ClampDOUT 73 - 80 RACK: 81 SLOT: 15 PORT: 93 DOUT【81】Jig Cover CloseDOUT【82】Jig Hand UnclampDOUT【83】Jig Cover OpenDOUT【84】Robot_G I/L1DOUT【85】Robot_G I/L2DOUT 81 - 88 RACK: 81 SLOT: 15 PORT: 101 DOUT【90】SEALING MATERIAL LACKINGDOUT【91】SEALING HEATING NOT OKDOUT【92】SEALING GUN OPENDOUT【94】CC-LINK STATUSDOUT【95】CC-LINK STATUSDOUT【96】CC-LINK STATUSDOUT 89 - 96 RACK: 81 SLOT: 15 PORT: 109 DOUT【97】CC-LINK STATUSDOUT【98】CC-LINK STATUSDOUT【99】CC-LINK STATUSDOUT【100】CC-LINK STATUSDOUT【101】CC-LINK STATUSDOUT【103】DOUT【104】JIG CLAMP OPEN REQUESTDOUT 97 - 104 RACK: 81 SLOT: 15 PORT: 117DOUT【106】PART IN STATIONDOUT 105 - 108 RACK: 81 SLOT: 15 PORT: 125DOUT【113】SEALING STARTDOUT【114】SEALING STOPDOUT 113 - 120 RACK: 82 SLOT: 6 PORT: 1 DOUT 121 - 128 RACK: 82 SLOT: 6 PORT: 9 DOUT【129】SPAREDOUT【130】SPAREDOUT【131】CLAMP_3_ONDOUT【132】CLAMP_3_OFFDOUT【133】CLAMP_2_ONDOUT【134】CLAMP_2_OFFDOUT【135】CLAMP_1_ONDOUT【136】CLAMP_1_OFFDOUT 129 - 136 RACK: 82 SLOT: 4 PORT: 1 DOUT【137】SPAREDOUT【138】SPAREDOUT【139】_DOUT【140】_DOUT【141】_DOUT【142】_DOUT【143】_DOUT【144】_DOUT 137 - 144 RACK: 82 SLOT: 4 PORT: 9GIN【1】Style No.GIN 1 RACK: 81 SLOT: 15 PORT: 73 #NUM: 8 GOUT 1 RACK: 81 SLOT: 15 PORT: 81 #NUM: 6 UI【1】*IMSTPUI【2】*HoldUI【3】*SFSPDUI【4】Cycle stopUI【5】Fault resetUI【6】StartUI【7】HomeUI【8】EnableUI 1 - 8 RACK: 81 SLOT: 15 PORT: 1UI【9】RSR1/PNS1UI【10】RSR2/PNS2UI【11】RSR3/PNS3UI【12】RSR4/PNS4UI【13】RSR5/PNS5UI【14】RSR6/PNS6UI【15】RSR7/PNS7UI【16】RSR8/PNS8UI 9 - 16 RACK: 81 SLOT: 15 PORT: 9UI【17】PNS strobeUI【18】Prod startUI 17 - 18 RACK: 81 SLOT: 15 PORT: 17 UO【1】Cmd enabledUO【2】System readyUO【3】Prg runningUO【4】Prg pausedUO【5】Motion heldUO【6】FaultUO【7】At perchUO【8】TP enabledUO 1 - 8 RACK: 81 SLOT: 15 PORT: 1 UO【9】Batt alarmUO【10】BusyUO【11】ACK1/SNO1UO【12】ACK2/SNO2UO【13】ACK3/SNO3UO【14】ACK4/SNO4UO【15】ACK5/SNO5UO【16】ACK6/SNO6UO 9 - 16 RACK: 81 SLOT: 15 PORT: 9 UO【17】ACK7/SNO7UO【18】ACK8/SNO8UO【19】SNACKUO【20】ReservedUO 17 - 20 RACK: 81 SLOT: 15 PORT: 17</PRE><H2><A NAME="6">Safety Status Information</A></H2> <PRE><A HREF="#TOP">【TOP】</A><P>SAFETY SIGNALS::External ESTOP FALSESOP Estop FALSETP ESTOP FALSEHand Broken TRUEOverTravel FALSELow Air Alarm FALSEFence Open FALSEBelt Broken FALSETP Enable FALSETP Deadman FALSESVOFF Detect FALSEServo Disconnect FALSENon Teacher Enb FALSE</PRE><H2><A NAME="7">Current Position Information</A></H2> <PRE><A HREF="#TOP">【TOP】</A><P>CURRENT ROBOT POSITION::Group #: 1CURRENT JOINT POSITION:Joint 1: 98.31Joint 2: -21.86Joint 3: -15.51Joint 4: 3.71Joint 5: -60.75Joint 6: 227.81EXTAXS: 1: 1036.33Frame #: 0 Tool #: 2CURRENT USER FRAME POSITION:X: -559.31Y: 1592.64Z: 151.27W: -.58P: -12.93R: 89.70CFG: N U T, 0, 0, 1EXTAXS: 1: 1036.33Tool #: 2CURRENT WORLD POSITION:X: -559.31Y: 1592.64Z: 151.27W: -.58P: -12.93R: 89.70CFG: N U T, 0, 0, 1EXTAXS: 1: 1036.33CURRENT ROBOT POSITION::。
DELL MD3000I 双机热备简单说明
3000I群集安装简单说明（WINDOWS）
之前看过资料做过3000的双机，其实3000I除了ISCSI，其他和3000一样。
实验用的是一台R200做AD，两台R410做SERVER1和SERVER2，一台3000I双控。
IP如下
AD 192.168.2.3
SERVER1 PRIVATE 192.168.3.1 PUBLIC 192.168.2.1
SERVER2 PRIVATE 192.168.3.2 PUBLIC 192.168.2.2
3000I除了两管理口，就只连了130.101和130.102
群集192.168.2.4
大多数配置过程和3000一样，就简单的说下自己遇到的问题吧（有什么错误还请指正）。
两个节点加入AD的时候是用的域管理员的账号和密码，并非在AD 建立的CLUSTER用户，不知道有人用CLUSTER成功过没。
PRIVATE的模式AUTO就可以使用，不象有的要手工指定，手工指定反倒是不行。
3000I配置主机访问，只有三项，选择CLUSTERED，注意主机名不能和SERVER1，2的服务器重名。
3000I的仲裁是这样的，同事之前做好多次没成功可能和这点有关。
做好之后两个服务器磁盘管理是这样的。
在群集管理器里手工移动组的时候SERVER2在我的电脑里看不到盘符号，不过在磁盘管理里可以看到，而且可以正常使用，SERVER1没
问题，其实这并不影响群集的正常使用，因为手动关闭SERVER1，登陆SERVER2一切正常，我的电脑里盘符都可以看到并且可以正常访问。
END。
MD3000双口双控固件升级步骤
MD3000双口双控固件升级步骤(从06版本升级到07版本)升级前准备：1、备份数据并导出MD3000日志2、停止所有的I/O访问（建议关闭服务器或在MDSM中暂时断开映射）3、安装最新版的管理软件（一般建议用带外方式进行更新：MDSM软件只需要安装在连到网络、可进行带外管理的机器上——台式机或笔记本）4、更新固件（两种方式：固件更新工具或MDSM中的固件上传工具）（需要1小时左右，更新初始化完成后控制器会自动重启，请耐心等待）5、重启服务器（或重建映射）一．固件和最新的光盘下载地址06版本最新的固件（版本06.70.17.60, A04）：/SAS-RAID/R193925.zip07版本的最新固件（版本07.35.31.60,）：/SAS-RAID/DELL_MD3000-SAS-RAID-CONTROL_A08_R242526.zip最新的MD3000光盘：/RCD/md3000_2.1_R264258.iso二．升级控制器固件和Firmware1.安装最新的MD3000程序，运行FW升级工具MD Firmware Cross Generation Upgrade Utility，看下图2.点Add，用手动，输入MD3000的二个raid 控制器的管理IP。
1.找到现有的盘柜后，会列出当前的固件版本，选择对应的文件升级，如图选择对于的文件升级到07最新版，如图点 Dowmlaod，去浏览，选择你下载的最新FW文件。
然后开始升级：注意红色圈的内容，看view log检测升级过程。
在MD Firmware Cross Generation Upgrade Utility升级完成后界面如下：左右。
(这个过程一定要有耐心，不要重启机器，等到Firmware ok后才表示升级完成。
)。
MD3000 Windows下安装步骤
MD3000 Windows下安装步骤:1.MDSM管理软件安装2.设置主机访问3. 创建虚拟磁盘和热备份MD3000安装第一步:MDSM管理软件安装1.首先安装SAS5/E驱动程序, 如底下说明有提示, 请先完成.2.然后点击安装MD3000存储软件, 选择语言, 可以选中文和英文, 这里选择英文, 点OK.3.点下一步:4.接受协议:5.选择安装路径:6.选择安装类型, 如果不知道选什么, 请选择全安装:7.选择自动启动监视:8.提示所需空间:9.提示安装完成:10.如有提示重启请确认.MD3000安装第二步: 设置主机访问1.打开开始→程序→DELL→MD Storage Manager→Modular Disk Storage Manager Client2.选择自动, 开始搜索(手动分为带内和带外管理, 分别代表通过SAS管理和通过管理网口管理)3.一两分钟后显示搜索到的服务器和存储:4.点关闭后, 可以看到存储的大概配置信息:5.重新打开后, 可以看到带内和带外的IP地址.(带外IP地址就是两个控制器的IP地址, 默认是192.168.128.101; 192.168.128.102)6.更改网络配置(根据需要可选)更改IP地址会引起带外管理重新配置. 不影响带内管理7.配置主机访问: 先看自动配置: (手动和自动任选一项)8. 把左边可用的主机加到右边:9. 点击确定即可.10. 手动配置主机访问:11. 输入主机名, 选择主机类型:12. 点击下一步:13. 选择对应的SAS卡WWN:14. 选择创建主机或主机组(针对Cluster)15. 点击完成.MD3000安装第三步: 创建虚拟磁盘和热备份1.选择创建虚拟磁盘:2.显示没有磁盘组, 点下一步:3.手动创建:4.选择磁盘和阵列级别:5.点击计算容量:6.选择要创建的虚拟磁盘大小和IO参数:7.选择要把该虚拟磁盘分配给哪一台主机使用:8.如果有多余的磁盘, 建议配置一块热备份磁盘:9.手动配置:10.选择硬盘组合, 点分配:11.本例选了两块硬盘做热备:12.点击完成.13.打开该服务器的设备管理器, 刷新14.查看是否有MD3000开头的磁盘, 如没有, 请重启机器:15.打开磁盘管理器, 配置分区:。
DS3000系统的安装配置
1服务器配置步骤 (3)1.1安装sun服务器操作系统——UNIX (solaris9) (3)1.2安装服务器数据库oracle9i (19)1.3安装DS3100系统 (21)1.3.1拷入DS3100文件夹 (21)1.3.2 每个节点都有指定的license，拷入ds3100文件夹下，系统才能运行。
(22)1.4配置SUN环境变量 (22)1.5访问历史服务器数据库的网络配置 (23)1.5.1前置、SCADA服务器访问历史服务器数据库的网络配置 (23)1.5.2历史服务器数据库的网络配置（主机名填历史服务器的IP） (24)1.6历史服务器建库 (26)1.6.1建库 (26)1.6.2建表 (26)1.6.3导入数据 (26)2工作站配置步骤 (27)2.1安装WINDOWS 2000 professional (27)2.2安装客户端数据库oracle： (28)2.3安装java (28)2.4安装DS3100系统 (28)2.5配置环境变量（NT） (28)2.6在客户端配置服务器 (31)2.7配置客户端调度系统的网络 (34)3NT下DS3100数据库置库 (37)4Web安装说明 (48)4.1DS3100环境建立 (48)4.2web应用程序安装 (49)4.2.1安装jdk(最好安装在C:\) (49)4.2.2安装Tomcat (49)4.3配置num文件夹 (52)4.4配置IIS服务 (52)5配置物理隔离设备 (54)5.1网络安全隔离设备在网络中的位置 (54)5.2网络安全隔离设备的接线图 (55)5.3系统的设置 (55)5.4网络安全隔离设备的配置 (55)5.5规则写入 (58)6卫星钟配置 (63)7UNIX系统下一些常用命令 (64)7.1SUN机器网卡安装说明 (4)7.2设置SUN机器的开机自检参数 (4)7.3查看SUN机器的网卡名称 (5)7.4修改SUN机器的分辨率 (5)7.5SUN的拷贝命令 (5)7.6修改SUN字体 (5)7.7SUN机器挂其他硬盘 (5)7.8编辑hosts.equiv文件 (6)7.9SUN操作系统下各个环境.................................................... 错误！未定义书签。
MD3K(二)-初始化盘柜和网络设置
MD3000 调试和配置–单机版(二) 初始化盘柜和网络设置首先，初始化MD3000 1．经过上面的准备，我们可以配置阵列了：2．打开软件，开始自动监测，在软件中发现MD3000的信息2．如果MD3000中有残留的信息，我们可用命令行的方法，先对MD3000进行初始化。
当然，这一步也可以跳过4．首先，start---run----cmd 打开MSdos命令行5．然后，在命令行中，进入MDSM程序所在的子目录运行 cd C:\Program Files\Dell\MD Storage Manager\client\6．进入目录后，运行： SMcli 127.0.0.1 （如果是带外管理，把127.0.0.1替换成相应的控制器访问IP）注意大小写，回车，然后就进入了MD3000的命令行模式7．在命令行模式下，运行下面的命令：clear storageArray configuration；请注意大小写，还有最后的分号回车，大概5分钟后，MD3k前面板左上角的状态指示灯会变成紫色，待指示灯由紫色恢复成蓝色后，初始化完成8．完成后，MD3000就可以恢复到初始的状态了下面，来看如何设置MD3000控制器的访问IPMD3000即可以用带内方式管理（通过SAS数据线），也可以用带外方式辅助管理（通过连接控制器的网线）。
带外管理对于系统的调试和故障排查非常有用。
1．选择 modify –Network configure2．在这里可以修改控制模块的IP默认的IP ：控制器0 --- 192.168.128.101 （正对机器右侧的控制器为0号）控制器1--- 192.168.128.102特别提醒：IP地址一旦忘记，需要在工厂模式下恢复，操作非常繁琐请尽量保留默认IP或妥善记录更改后的IP3．用网线连接设备，等待3-5分钟，确认可以ping通控制器IP后，就可以使用带外管理了点选阵列名称旁边的new 选项，然后让软件自动扫描一次4．可以看到两种管理方式都有了带内管理（通过SAS数据线管理）： 127.0.0.1 带外管理（通过网线）：192.168.128.101。
带 Microsoft Windows Server 故障转移群集的 Dell PowerVault
带 Microsoft ® Windows Server ® 故障转移群集的 Dell™ PowerVault™ MD3000 存储阵列硬件安装与故障排除指南简介群集硬件的布线准备用于群集的系统故障排除群集数据表注、注意和警告本说明文件中的信息如有更改，恕不另行通知。
© 2008 Dell Inc. 版权所有，翻印必究。
未经 Dell Inc. 书面许可，严禁以任何形式进行复制。
本文中使用的商标：Dell 、DELL 徽标、PowerEdge 、 PowerVault 和 OpenManage 是 Dell Inc. 的商标；Microsoft 、SQL Server 、Windows 、 和 Windows NT 是 Microsoft Corporation 在美国和/或其它国家和地区的商标或注册商标。
本文中述及的其它商标和产品名称是指拥有相应商标和产品名称的公司或其制造的产品。
Dell Inc. 对本公司的商标和产品名称之外的其它商标和产品名称不拥有任何专有权。
2008 年 4 月 修订版 A00注： "注"表示可以帮助您更好地使用计算机的重要信息。
注意： "注意"表示可能会损坏硬件或导致数据丢失，并告诉您如何避免此类问题。
警告： "警告"表示可能会导致财产损失、人身伤害甚至死亡。
返回目录页面群集硬件的布线带Microsoft ® Windows Server ® 故障转移群集的 Dell™ PowerVault™ MD3000 存储阵列硬件安装与故障排除指南鼠标、键盘和显示器的布线电源设备的布线公用网络和专用网络的布线存储系统的布线以下部分将帮助您将电源、网络和存储电缆连接至群集。
连接硬件组件后，本文档中的后续部分将向您提供配置群集的说明。
鼠标、键盘和显示器的布线在机架中安装群集配置时，必须安装切换器盒，以将鼠标、键盘和显示器连接至节点。
PC3000 for windows UDMA详细说明
PC3000 for windows UDMA详细说明PC-3000PC-3000不止是一种工具，更是一种技术，当硬盘驱动器为物理损坏时，可以让数据恢复公司在典型数据恢复环境中修复硬盘访问用户的数据。
此项技术适用于涉密政府机关、军队、大中型企业、数据恢复公司。
什么是PC-3000 for windows(UDMA)?这是一款新的软件，它结合了我们的第一代产品功能和特点：PC-2000 MFM/RLL, PC-3000 DOS (ISA), 和PC-3000 for Windows PCI的优点。
这些软件都是为世界范围的数据恢复专家所认可的。
目前国内很多数据恢复公司，国家机关都在用这种数据恢复设备。
基本操作原理.PC-3000 for windows(UDMA)是基于以下原理:1.这款产品由通用程序和专用程序组成.通用程序可以很快速地诊断硬盘，给客户对下一步硬盘修复的方法提供有效的信息。
支持任何3.5" . 2.5"，1.8" 串口或PATA 硬盘或1.0"闪存接口硬盘。
专业程序提供在专业的工厂模式下诊断和恢复硬盘的功能。
该模式是不能通用，它对每一个硬盘系列都是唯一的。
这就是为什么该工具要为每个硬盘系列准备单独的工厂模式程序的原因。
专业程序提供更深层次的驱动器故障检测以及功能修复。
另外，如果硬盘不能被修复，这个套装也可以获取到用户数据。
2.对硬盘的操作都可通过PC-3000 for windows UDMA的专门双端口测试卡来实现.3.所有切换硬盘至工厂模式的专业接口和适配器均包含在此套装中.4.这个套装同样也包含工厂硬盘资源的数据库：闪存硬盘ROM内容，服务区模块和轨道，等。
所有的资源都根据系列，型号和固件版本来分组。
你可以在数据库中搜索特定资源，也可从最新型号硬盘中增加新对象.PC-3000 for windows(UDMA)可解决什么问题?专家们在使用这个工具时会有不同的熟练程度。
MD3000电池出现故障
电池出现故障
存储阵列: 未命名
电池出现故障
允许维修操作(卸下): 否
组件上的维修操作 LED: 否
机柜: RAID 控制器模块/扩展机柜
位置: 0
造成该问题的原因是什么？
RAID 控制器模块中的电池出现故障。
恢复 Guru 的“详情”区域提供您在执行恢复步骤时所需的具体信息。
警告：静电释放会损坏敏感组件。
请在操作组件时始终使用适当的抗静电保护。
在没有适当接地的情况下触摸组件，可能会损坏设备。
重要说明
∙电池的作用是当出现电源故障时保留高速缓存数据。
因此，您应该尽快更换电池。
∙此存储阵列上的电池集成在 RAID 控制器模块中，因此，在更换出现故障的电池之前，需要取下RAID 控制器模块。
∙在更换电池并充满电之前，虚拟磁盘写入高速缓存和高速缓存镜像将自动挂起。
∙如果在 RAID 控制器模块上使用 DHCP 配置，则在根据需要将新的 RAID 控制器模块插入存储阵列前，请首先更新 DHCP 服务器，以便它将新 RAID 控制器模块的硬件以太网 (MAC) 地址与以前分配给已卸下 RAID 控制器模块的 IP 地址相关联。
恢复步骤
具有一个控制器的存储阵列的过程
具有两个控制器的存储阵列的过程。
数据恢复 和 pc-3000 for windows基础与应用案例全解析
数据恢复和 pc-3000 for windows基础与应用案例全解析数据恢复和PC-3000 for Windows基础与应用案例全解析导语在当今信息化时代，数据已经成为我们生活和工作中不可或缺的一部分。
然而，由于各种原因，数据丢失或损坏的情况时有发生。
为了解决这个问题，数据恢复技术应运而生。
而PC-3000 for Windows作为一款专业的数据恢复工具，其基础与应用案例更是备受关注。
本文将从数据恢复的基本概念入手，深入探讨PC-3000 for Windows的原理和应用案例，帮助读者更好地理解和应用这一技术。
一、数据恢复的基本概念数据恢复是指将由于意外删除、病毒攻击、硬件故障等原因丢失的数据进行恢复的一种技术。
其主要目的是尽可能地找回和重建丢失的数据，以保证数据的完整性和可用性。
数据恢复技术在当今信息化社会中具有重要的意义，能够帮助个人和组织避免不必要的损失，提高数据安全性和可靠性。
二、PC-3000 for Windows的基础原理PC-3000 for Windows是一款专业的数据恢复工具，其核心原理包括逻辑层数据恢复、物理层数据恢复和固态硬盘数据恢复。
逻辑层数据恢复主要通过软件对存储设备进行扫描和识别，找回丢失的文件和目录信息；物理层数据恢复则是通过硬件工具对存储设备进行操作，修复硬盘的物理损坏；固态硬盘数据恢复则是针对固态硬盘进行特殊处理，以确保数据的完整性和可用性。
PC-3000 for Windows凭借其独特的原理和优秀的性能，成为业内领先的数据恢复工具之一。
三、PC-3000 for Windows的应用案例解析1. 案例一：意外删除的数据恢复某公司的员工不慎将重要的文件删除，导致数据丢失严重影响了工作进程。
在这种情况下，利用PC-3000 for Windows的逻辑层数据恢复功能，成功找回了被删除的文件，并将其恢复到原始状态，实现了数据的完整性和可用性。
2. 案例二：硬盘物理故障的数据恢复一台服务器的硬盘出现了物理故障，导致数据无法读取。
MD3000i更换RAID控制器模块说明书
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.Replacing a RAID Controller Module in a Single-Controller MD3000iThis document describes how to replace a failed RAID controller module in a single-controller MD3000i. After replacing the RAID controller, you will also need to update its controller and NVSRAM firmware. These steps are described in "Updating RAID Controller and NVSRAM Firmware on the Replacement RAID Controller Module" later in this document.Replacing the RAID Controller ModuleWARNING: Always wear a wrist grounding strap when handling equipment withstatic-sensitive components. See your Product Information Guide for safetyinformation.Removing the RAID Controller Module1Power down the MD3000i enclosure.2Disconnect all cables from the failed RAID controller module.3Push up on the release tab on the left side of the module (see Figure 1).4At the same time, pull out on the release lever. When the lever is pulled out, the controller module partially ejects from the enclosure.5Remove the module from the enclosure and place it on a flat, secure surface.CAUTION: To avoid damage to the sensitive EMI (ElectroMagnetic Interference)contacts on the bottom of the controller module, do not stack or place the module on a hard surface.Figure 1.Removing and Installing a RAID Controller ModuleInstalling a Replacement RAID Controller Module1Carefully insert the replacement RAID controller module into the empty module slot.2Push the module into the back of the slot until it is firmly seated in the backplane connector (see Figure 1).3Push the release lever in (towards the enclosure) until the module is retracted into the slot and is secure.Proceed to the next section to update the RAID controller and NVSRAM firmware on the new controller.1release tab 2release leverUpdating RAID Controller and NVSRAM Firmware on the Replacement RAID Controller ModuleThe following procedure is required only if a single controller storage array enters lockdown mode after replacement of a failed controller.To update the RAID controller module and NVSRAM firmware, the following items will be required:•Server, workstation, or laptop computer with access to the management port of the RAID controller module•Single Controller Replacement UtilityUsing the Single Controller Replacement UtilityNOTE: The Single Controller Replacement Utility will not update any RAID controller that is not in lockdown mode. If your RAID controller is not in lockdown mode, use the update procedure described in the Dell TM PowerVault TM MD3000i User’s Guide.NOTE: In order to update the firmware, the RAID enclosure must contain at least two disk drives.The Single Controller Replacement Utility should be run after replacing a failed controller in a single-controller system. The utility ensures that the firmware version in the replacement controller is in sync with the firmware expected by the virtual disks. After running the utility, the storage array should return to the configuration it was in prior to the controller failure.The utility can be run from any computer with access to the management port of the storage array by following these steps:1Extract all files and folders from the utility .zip file to a temporary location. 2Navigate to the location of the extracted files.If you are using a Windows system, run the simplex.bat file.If you are using a Linux system, execute the simplex.sh file.A GUI-based wizard will guide you through the remaining steps necessary toupdate the controller.3When the wizard completes, click Finish.The update process is complete.____________________Information in this document is subject to change without notice.©2008Dell Inc.All rights reserved.Reproduction in any manner whatsoever without the written permission of Dell Inc.is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, and PowerVault are trademarks of Dell Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Microsoft and Windows are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.December 2008。
MC3000的PC端同步程序操作手册
MC3000 PC端同步程序操作手册北京南开戈德信息技术有限公司同步软件(Microsoft ActiveSync)的安装过程这个软件是微软公司开发的软件。
它的功能是让计算机(PC)与安装WinCE平台的手持终端（我们这里的是MC3000）进行通讯。
所以这个软件的安装和正确运行是手持终端程序的安装、数据上传、下载的基础。
在以后的业务操作中遇到手持终端程序的安装、数据的上传、下载，首先确定Microsoft ActiveSync软件的正确运行。
一个简单的判断方法是：在屏幕的右下角的windows系统托盘中的标志成为绿色。
如下图：下面我们介绍这个同步软件的安装过程。
在安装盘的目录中会有一个文件Microsoft ActiveSync 4.1.exe。
同步软件的安装只需要这一个文件。
双击运行它。
出现如下界面：然后出现点击“下一步”按钮，出现如下界面：选择我接受协议点击“下一步”按钮，出现如下界面您可以通过“更改”按钮来改变同步软件安装的目录。
一般安装在默认的目录，点击“下一步”按钮，出现文件拷贝界面，然后是如下界面：这安装完毕后，通常同步程序会自动启动，如果没有启动，请进入程序菜单手工启动MicroSoft Active Sync；安装程序会自动将同步程序加到启动组中，这样你每次重新启动PC时就自动启动同步程序。
同步软件(Microsoft ActiveSync)的使用过程第一次启动同步程序，如果连接好了设备，会提示你建立合作关系如果要连接，出现如下界面：点击“下一步”按钮，出现如下界面：点击“下一步”按钮，出现如下界面：通常情况下，将所有的勾都去掉，点击下一步通常情况下，将所有的勾都去掉，点击完成同时，您会听到叮叮的响声，表明同步软件正在自动搜索手持终端与PC想连接的接口，USB口或者串口，我们使用的MC3000是用USB通信，一般把MC3000连接在PC的USB口上。
连接成功后就出现如下界面：此时表明手持终端已经与PC机正确连接了，您这时可以使用手持程序的安装软件和进行上传、下载数据的操作了。
MD3000 MD3000i硬盘固件升级步骤
MD3000 MD3000i硬盘固件升级步骤
备注：升级前请备份数据。
一．固件下载地址
MD3000/MD3000i 西数硬盘(M020F)最新固件下载地址:
/sas-hdd/DELL_MULTI-DEVICE_A20_R271714.exe
二．升级硬盘固件
进入Modular Disk Storage Manager软件，收集盘柜日志信息，为下面的升级做准备，了解所接硬盘的具体型号，便于升级。
通过收集到的日志确认硬盘的厂家和固件版本信息，为下面的升级做准备。
进入Modular Disk Storage Manager软件，选择Support，进入Download Physical Disk Firmware菜单，根据步骤1、2、3操作。
选择正确的固件版本，如果是可升级的版本，会显示为This package is compatible
如果不是可升级的版本会提示This package is not compatible。
升级选择如下：
输入“yes”确认升级。
升级过程如下：
升级完成后，会在Progress栏，显示Successful。
注意两个菜单：
1.Save as：可以保持升级的日志。
2.Transfer More:有些硬盘固件无法一次升到最高版本，需要逐级升级，可以
选择这个菜单。
至此，MD3000，MD3000i硬盘固件升级就完成了。
DELL Dell PowerVault MD3000 Systems 说明书
Dell™ PowerVault™MD3000Systems Information UpdateNotes, Cautions, and WarningsNOTE: A NOTE indicates important information that helps you make better use of your computer.CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.WARNING: A WARNING indicates a potential for property damage, personalinjury, or death.____________________Information in this document is subject to change without notice.©2008–2009Dell Inc.All rights reserved.Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.Trademarks used in this text: Dell, the DELL logo, and PowerVault are trademarks of Dell Inc.; Microsoft, Windows, and Windows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries; SUSE is a registered trademark of Novell, Inc., in the United States and other countries; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries.Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.September 2009Rev. A02ContentsDetermining Your Firmware Version (5)Important Information Before Upgrading YourFirmware (5)Performance Affected after Upgrading to SecondGeneration Firmware (5)Virtual Disk Copy Operation on SATA Disks (6)Load Balancing in Microsoft Windows Server 2008 (6)Installing Linux Operating System (6)Battery Learn Cycle (6)Creating Host to Virtual Disk Mappings (7)Additional Disk Group and Virtual Disk ExpansionInformation (7)Storage Manager for SANs (8)Unable to Assign LUNs to Windows 2008Server (8)Array Password Reset Using Microsoft WindowsServer 2008 (8)Modular Disk Storage Manager (9)Physical Disk Migration (9)RAID Level (9)Change Disk Group RAID Level (9)RAID Level Migration Requirements (10)Contents3Under-Reported Disk Capacity (10)Configuration File Write Error (10)Limitations of NTFS-Formatted Disks (11)Password Reset Procedure (11)Updates to the MD3000 Documentation (12)Hardware Owner’s Manual (12)Command Line Interface Guide (12)Installation Guide (12)4ContentsDetermining Your Firmware VersionTo determine if your software is first generation or second generation, perform the following steps:1Connect to the system using the Dell™ PowerVault™ MD Storage Manager.2Select the Support tab.3Click Storage Array Profile.Note the firmware version:If it is 06.xx.xx.xx, it is first generation.If it is 07.xx.xx.xx, it is second generation.Important Information Before Upgrading Your FirmwarePrior to performing the firmware upgrade, perform a complete backup of the data, and use the Gather Support Information tool to save the system configuration. This recommendation applies whenever you make changes to your configuration.Performance Affected after Upgrading to Second Generation FirmwareAfter upgrading to second generation firmware, you may experience a temporary performance impact. This impact is caused by the second generation firmware, which adds smart-battery functionality to the MD3000. In order to accurately measure battery parameters, the batteries are taken through a “learn cycle” and the system’s write cache is disabled for the duration of the learn cycle. The first learn cycle starts soon after the firmware upgrade is completed and takes around 15 hours to complete. During this time, you may experience a temporary performance slowdown for certain kinds of file operations as the write cache is disabled. Once the learn cycle is complete, the write cache is automatically enabled.Future learn cycles are scheduled for every 13 weeks. Y ou can adjust the day and time of the day of future learn cycles using MD Storage Manager (click Tools and select Change Battery Settings).Information Update5Virtual Disk Copy Operation on SATA DisksA virtual disk copy operation may take much longer when a new copy is created on SATA disks. To improve the performance, first create the virtual disk. After the virtual disk is initialized, start the virtual disk copy operation. Load Balancing in Microsoft Windows Server 2008Load balancing in Microsoft® Windows Server® 2008 is provided by the MPIO driver under the MPIO tab. For information about accessing the MPIO tab, see the Installation Guide at /manuals. The following options are supported by MD3000:•Least Path Weight•Least Queue DepthInstalling Linux Operating SystemDuring a Linux operating system installation, the installer lists all the volumes that are discovered from MD3000, including virtual disks that are mapped to the host and Universal Xport. If the operating system needs to be installed on an MD3000 virtual disk, you must ensure that you select the appropriate virtual disk. The array does not respond if you select the Universal Xport disk(s) for installation.Battery Learn CycleIn second generation firmware systems, the cache offload battery undergoes a learn cycle once in every 13 weeks to ensure that the battery is in a good state. The learn cycle performs a complete discharge of the battery followed by a complete recharge. During this cycle, the system cache is disabled on all virtual disks in the system. There may be a temporary impact on the performance of the system when the battery undergoes a learn cycle. A learn cycle takes place under the following situations:•First time upgrade from first generation firmware to second generation firmware•Once in every 13 weeks6Information UpdateThe next scheduled learn cycle can be seen under Tools→Change Battery Settings in the MD Storage Manager. The learn cycle can be postponed by up to seven days at a time through the GUI. Y ou can also use the following SMcli command to postpone a learn cycle: set storageArray learnCycleDate daysToNextLearnCycle=[x]For more information, see the Command Line Interface Guide at /manuals.Creating Host to Virtual Disk MappingsY ou can create Host-to-Virtual Disk mappings to a host group or to a single host. If you have created the mapping to a host that is part of a host group, the mapped host alone will have access to the virtual disk. Additional Disk Group and Virtual Disk Expansion InformationTo expand disks groups or virtual disks, you can use the MD Storage Manager or the command line interface. It is only possible to add one disk at a time or two in the case of RAID10 to expand the disk group.To expand the virtual disk using the command line interface, type: set virtualDisk [VDname] addCapacity=sizetobeaddedFor more information, see the Command Line Interface Guide at /manuals.During disk group and virtual disk expansion operations, you have complete access to the virtual disks and disk group redundancy is maintained at all times. The impact on the performance is minimal during the operation.For more information, see the User's Guide at /manuals.Information Update7Storage Manager for SANsUnable to Assign LUNs to Windows 2008 ServerThe Windows Server 2008 Storage Manager for SANs utility can be used to create and manage virtual disks in the MD3000 from the host server. If the host server contains SAS 5/i HBAs, the SAS 5/i ports must be disabled in the Storage Manager for SANs utility to prevent issues with assigning virtual disks (LUNs) to the host server.Perform the following steps:1Click LUN Management.2Click Manage Server Connection.3Select the host server.4In the Fiber Channel Ports tab, disable all the SAS 5/i ports and leave the SAS5/e ports enabled.There are 8 SAS 5/i ports per SAS 5/i HBA in the host server. The HBA Port WWN has the following format: xx:xx:xx:xx:xx:xx:xx:00 toxx:xx:xx:xx:xx:xx:xx:07.NOTE: SAS 5/e HBAs have two ports with HBA Port WWN as follows:yy:yy:yy:yy:yy:yy:yy:00 and yy:yy:yy:yy:yy:yy:yy:04Array Password Reset Using Microsoft Windows Server 2008To reset a lost or forgotten password on an MD3000 array, a command must be issued via the serial port on either controller in the array to clear the existing password. This task is accomplished through COM port connection from a server, workstation or laptop to a controller on the MD3000 array.On most Windows operating systems, the HyperTerminal application is used to establish the COM port connection to the serial port on the controller. However, HyperTerminal is not available on Windows Server 2008 systems.8Information UpdateComplete the following steps to reset the password to an MD3000 array if your system is running the Windows Server 2008 operating system:1Obtain a terminal application capable of COM port connections.2Configure the application to use the communication settings as described on page 23 of the Dell PowerVault Modular Disk Storage Manager User’s Guide.3Proceed with the password reset procedure described on page 24 of the User’s Guide.Modular Disk Storage ManagerThe following updates apply to the Modular Disk Storage Manager(MD Storage Manager):•When the MD Storage Manager is installed on Red Hat® Enterprise Linux® systems or SUSE® Linux Enterprise Servers, or when theMD Storage Manager is running on SUSE Linux Enterprise Servers,Japanese and Simplified Chinese are not supported.Physical Disk MigrationCold power-up migration of physical disk s from one MD3000 duplex configuration to another MD3000 duplex configuration is supported only when all physical disk s are moved from one system to another. No other migrations, including partial physical disk migration and RAID controller module migration, are supported.RAID LevelChange Disk Group RAID LevelFollow these instructions to change the RAID level of a disk group as needed: 1In MD Storage Manager, click the Modify tab and click Change Disk Group RAID Level.2Select the disk group that you want to modify.3Select the new RAID level from the drop-down menu.4Click Change to start the process.Information Update910Information UpdateNOTE: Dell recommends backing up the disk group before modifying the RAIDlevel.NOTE: The number of disks in the disk group should meet its RAID level criteria. RAID1 and RAID10 require an even number of disks. On the MD3000, RAID 5requires a minimum of 3disks and RAID 6 requires a minimum of 5 disks. You may need to add free capacity to the disk group before changing the RAID level.RAID Level Migration RequirementsSuccessful RAID Level Migration (RLM) requires that the appropriate number of physical disk s are present in your disk group. To perform RLM from a RAID 1 or RAID 10 to an odd-number of physical disks (five or more) in RAID 5, first add an even number of disks to the RAID 1 or RAID 10, convert to RAID 5, then add another physical disk to make the count odd.Under-Reported Disk CapacityThe unit Gigabyte (GB) is often used to refer to calculation of both 109bytes and 230 bytes. The MD Storage Manager calculates hard disk capacity in GB using 230 bytes as compared to 109 that is used by hard disk manufacturers, and therefore displays a smaller capacity than reported by the hard drive vendor. There is no actual loss of available data capacity, and the MD3000 only reserves 512 MB (106) of space per hard disk for meta-data usage.Configuration File Write ErrorUsing the MD Storage Manager with Microsoft Windows Server 2008 or Microsoft Windows Vista can result in a Configuration File Write Error . The MD Storage Manager will be unable to save any changes to the configuration files. This error is seen when the application is run as a user without Local Administrator privileges. MD Storage Manager requires Local Administrator privileges for full functionality.Workaround: This error can be bypassed by running the MD StorageManager with local administrator privileges. This can be set by right-clicking the shortcut and clicking Run as Administrator . This setting can be made permanent by modifying the shortcut properties and enabling Always run as administrator .Limitations of NTFS-Formatted DisksThe following error may occur when formatting virtual disks larger than 2TB using the NTFS protocol:The format operation did not complete because the cluster count is higher than expected.This error is caused by the limitations of NTFS-formatted disks based on cluster size.Table 1-1.Limitations of NTFS-Formatted Disks Based on Cluster SizeCluster size Maximum NTFS Volume Size (bytes RAW)5122,199,023,255,040 (2TB)1,0244,398,046,510,080 (4TB)2,0488,796,093,020,160 (8TB)4,09617,592,186,040,320 (16TB)8,19235,184,372,080,640 (32TB)16,38470,368,744,161,280 (64TB)32,768140,737,488,322,560 (128TB)65,536281,474,976,645,120 (256TB)As seen in T able1-1, you will need to modify cluster size to format certain virtual disks. T o expand existing virtual disks beyond the limits, back up the data on any existing virtual disks and reformat the virtual disk with the new cluster size. Please refer to Microsoft KB302873 and KB814594 for additional information. Password Reset ProcedureThe password reset procedure differs slightly between the first generation and second generation controllers. Please see the latest version of theDell PowerVault MD3000 RAID Controller Password Reset on for details on the password reset procedures.Information Update11Updates to the MD3000 DocumentationHardware Owner’s ManualThe following update applies to the Dell™ PowerVault™ MD3000 RAID Enclosure Hardware Owner’s Manual:Table 1-1 and Table 1-2—Flashing amber in the enclosure status LED indicates that the solution is in a non-optimal state. See the MD Storage Manager error recovery console or contact technical support to resolve this state.Command Line Interface GuideThe following are the corrections/additions in the list of parameters described in Table 1-2:•d: Used to display the array details from the array configuration file.•V: Used along with the -d parameter to display the version of SMcli that is connected to the array.Installation GuideThe following update applies to the Dell™ PowerVault™ Modular Disk 3000 Installation Guide:•The multi-pathing MPP driver is installed directly from the CD on Linux.Step 12 of the host installation procedure should read - "Return to the CD main menu and select the Install Multi-Pathing Driver option".•The note stating that the MD3000 supports only round robin load-balancing policies is no longer applicable.12Information UpdateDell™ PowerVault™MD3000系统信息更新注、小心和警告注：“注”表示可以帮助您更好地使用计算机的重要信息。
DELL_MD3000 群集手册
. 群集服务安装前的准备1、环境描述：操作系统：Windows 2003 Server 简体中文企业版数据库: SQL Server 2000DC服务器：DELL服务器1：DELL 2950服务器2：DELL 2950磁盘阵列：DELL MD3000 （300G硬盘*15）HBA卡：SAS 5/E2、群集拓扑图如下图所示：群集拓扑结构图2、磁盘阵列与服务器连接SAS 5/E 上面有两个接口分别为0、1，MD3000上一般有两个In接口，和一个Out接口。
接主机一般使用两个In接口。
需要注意的是：如果一台服务器的SAS卡使用了ID为“1”的接口，另一台则需要使用ID为“0”的接口。
如上图所示。
3、账号信息：本地管理员账号：administrator密码：********域管理员账号：administrator（51654874）密码：********群集管理员账号：cluster (域管理员组)密码：********SQL管理员账号：sqladmin (域管理员组)密码：********SA密码：sa4、服务器信息：域服务器服务器名：DCIP地址：192.168.2.5子网掩网：255.255.255.0网关：192.168.2.1DNS：192.168.2.5域名：Test.local域还原模式密码：******** 第一台服务器服务器名：Server1公网IP地址：192.168.2.2 子网掩网：255.255.255.0网关：192.168.2.1DNS：192.168.2.5心跳侦测地址：192.168.18.1 子网掩码：255.255.255.0第二台服务器服务器名：Server2公网IP地址：192.168.2.3 子网掩网：255.255.255.0网关：192.168.2.1DNS：192.168.2.5心跳侦测地址：192.168.18.2子网掩码：255.255.255.05、群集5.1 群集名称：data.test.local5.1虚拟IP地址：192.168.2.556、SQL Server 20006.1 虚拟服务器名称：VIRSQLCLUSTER6.2 虚拟IP地址：192.168.2.667、磁盘配置：Label DeviceC: SYSTEM 40GB | 本机D: DATA 96GB | 本机E: CDROM | 本机P: DATA 300GB | 磁盘阵列S: SHARE 剩余空间 | 磁盘阵列Q: Quorum 1GB | 磁盘阵列8、MD3000 控制器管理IP：控制器0：192.168.2.101控制器1：192.168.2.1022. 群集服务器安装及配置 2.1 硬件设备情况步骤节点1 节点2 存储注释安装配置系统上电上电断电检查所有共享总线上的存储设备是否都已经断电，给各节点上电。
DCBI-3000用户web自服务使用手册
DCBI-3000用户web自服务使用手册Version 3.0神州数码网络（北京）有限公司版权所有2007年1月前言作为Internet上网业务的运营系统，对于宽带上网或拨号上网而言，计费管理都是至关重要的。
但由于适用于窄带接入按时长计费的单一策略对宽带网络已不太适用，所以宽带网络需要增加不同于窄带接入的多种计费手段，以最大限度的发展用户，又能够最大限度的利用已有的资源，实现收益最大化。
神州数码DCBI-3000认证计费管理系统可以针对每个宽带上网用户，提供准确、详实的计费数据；并且可以为服务商提供方便、灵活的计费策略。
DCBI-3000认证计费系统可以支持PPPOE认证、Web 方式认证、基于端口或基于MAC地址的802.1x认证方式，该系统是基于标准认证、计费协议－－RADIUS协议开发的产品。
可以完成用户的身份验证、访问授权、上网控制、计费信息采集、用户管理、计费管理、费用结算以及营业点受理和客户查询服务等多种功能。
从模块上划分，可以分为认证及计费信息实时采集模块、数据库模块、管理模块、帐务模块。
从功能上划分，可以分为认证功能、计费功能、管理功能以及帐目结算功能。
同时为了方便客户的使用，提供了用户web 自服务子系统。
DCBI-3000认证计费系统可以和支持PPPOE认证、Web 方式认证的DCRS6608、DCRS6610系列路由交换机，和支持802.1x认证计费的DCS2000E、DCS3926S、DCS3950S。
DCRS5526S、DCRS5512GC等系列交换机实现对接入用户的认证、计费、授权管理功能。
有效地为各种企业用户、各高校及运营商提供一套完整的解决方案。
本使用手册版权和著作权属于神州数码网络（北京）有限公司，未经书面许可任何个人或团体组织不得将本使用手册内容的局部或全部以任何形式转载使用或出版销售。
版权所有，侵权必究！目录第1章系统简介 ________________________________________________ 5 1.1 系统结构_____________________________________________________________ 5 第2章系统Web服务器安装 _____________________________________ 6 2.1 安装包内容简介_______________________________________________________ 6 2.2 安装步骤_____________________________________________________________ 6 2.3 卸载方法_____________________________________________________________ 7 2.4 Web服务器的启停____________________________________________________ 7 2.5 连接web自服务______________________________________________________ 8 第3章系统使用 ________________________________________________ 9 3.1 用户密码修改________________________________________________________ 10 3.2 上网记录查询________________________________________________________ 12 3.3 查询费用帐单________________________________________________________ 14 3.4 帐户明细查询________________________________________________________ 16 3.5 充值卡充值__________________________________________________________ 18 3.6 用户余额查询________________________________________________________ 20 3.7 用户累积额度查询____________________________________________________ 22 3.8 用户web注册 _______________________________________________________ 24 3.9 用户信息修改________________________________________________________ 26 3.10 预付包天用户自主启停________________________________________________ 27 3.11 预付包月用户自主启停________________________________________________ 29 3.12 用户问题报修________________________________________________________ 31 3.13 问题报修结果查询____________________________________________________ 32 3.14 问题报修处理________________________________________________________ 33 3.15 用户激活____________________________________________________________ 34 3.16 修改计费类型________________________________________________________ 35 3.17 计费类型修改日志查询________________________________________________ 36 第4章客户端软件配置要求 _____________________________________ 38 4.1 操作系统____________________________________________________________ 38 4.2 浏览器配置要求______________________________________________________ 38第1章系统简介1.1 系统结构DCBI-3000用户web自服务是神州数码DCBI认证计费管理系统的一个组成部分。
MD3000集群文件共享操作方法
MD3000集群文件共享操作方法(原)一、应用目的：中心需要共享存储中心，需要的要求为能提供高可用性和高速率的课件文件的点播。
由于SAN环境成本较高，现采用磁盘阵列加存储服务器的方式向流媒体服务器和课件服务器提供NAS服务。
NAS机头采用两台服务器集群的方式。
二、环境构成：a)服务器：两台DELL 1950服务器（CPU1.6*2 4GB 146GB*2 PERC4/DC Raid1 1000M*2）b)磁盘阵列：DELL MD3000 （双口双控制卡300GBSAS*15 SAS5/E卡*4）三、操作方法：a)MD3000的配置按照DELL的建议，我们采用双机双冗余HBA卡方式构建MD3000环境。
先开启MD3000磁盘阵列柜，需要开启两个电源模块（否则工作的电源模块的风扇将会以超负荷工作，声音很响）。
然后开启所有的服务器。
登入所有1950服务器。
安装SAS卡驱动。
驱动可通过插入随机附带的MD3000的盘，会自动运行检测SAS卡的驱动，如果要安装只需根据操作进行安装即可。
安装Modular Disk Storage Manager Client。
第一次运行时使用自动选项添加存储阵列，然后再在Tools菜单栏中选择重命名，将新添的阵列命名为自己需要的。
再在Configure菜单栏中设置Host Access可以看到，1950-1（主机名为MD3000-1）和1950-2（主机名为MD3000-2）分别连接的HBA卡的物理地址，和他们的连接存储的类型（集群型）。
然后我们将需要建立集群的主机和附带的HBA卡加入一个组中，通过按Configure-Create Host Group。
在组名中键入新组名，我们设为nas，将所有左边的设备都加到右边的组中，点OK，此时在Modify的Edit Topology中我们可以看见如下图：接着进行盘柜资源的分配，一般首先设置热备盘，在Configure菜单下有Configure Hot Spares选项。
MD3K(三)虚拟磁盘的的创建
MD3000 调试和配置–单机版(三 ) 如何创建和管理虚拟磁盘首先，我们要在MD3000中创建主机1．选择 configure – create Host access ，选用手动方式2．选择创建主机的方式，这里是单机，所以选：non-cluster host name 要填写服务器的主机名，注意要大写3．选择HBA卡每块SAS5/E有两个接口，每个接口都被认为是一个独立HBA卡，这里我们连接了两个接口，将它们都选择上4．暂时不作主机组设置（在双机cluster模式中，我们要设置主机组），直接继续：5．一路继续，完成后，在 modify –Edit topology 中查看配置好的主机6．可以看到，主机下有两块HBA卡了接下来，我们要配置Virtual Lun(虚拟磁盘) 1．选择 configure --- create Vitual Disk2．Raid类型选择raid5 ，将左边选中的硬盘移动到右边3．注意，选择完硬盘后，一定要：calculate capacity (计算容量)，不然逻辑磁盘无法被识别4．继续，现在Disk Group 已经建立，我们可以在DiskGroup中划出一定的空间，创建一个Virtual Lun （有时也称逻辑驱动器）注意：一个V-Lun，在window中就相当于一个独立的磁盘。
这里划出了2G的空间创建V-Lun 1，剩余空间回头还可以建立新的V-LunMD3K中单个V-Lun最大容量是2T，大于这个容量，系统会自动限制到2T5．这里可以直接把创建的 V-Lun 映射给某个主机，当然，也可以不映射先继续6．创建完Virtual-Lun，我们还可以创建一块 hotspare 热备盘选择 configure ---hot spare7．然后选择手动，在右边选择一块热备盘，放入左边的列表中8．如果要撤销 hot spare 盘，请选择下面的 unassign最后，让我们建立 Virtual Lun 和 Host 主机间的映射关系1．现在V-Lun和Host 主机我们都已经创建完成，下面需要将两者映射在一起选择：configure ---create Host to V-disk mapping2．选择要挂接V-Lun的主机3．选择目标 V-Lun。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
MD3000安装指南
MD3000连接通过两个SAS接口连接一台服务器的两个接口，实现线路冗余。
最多可连接四台服务器
在服务器上安装MDSM管理软件，选择语言
点击下一步安装
选择安装目录
选择典型安装
完成安装
选择自动搜索MD3000
搜索到带内管理方式的MD3000，带内管理需要SM client 和SM agent 和Access Virtual Disk
也可以选择手动方式，使用带外方式连接，带外需要SM client 和SM agent和网线连接
带外管理方式登陆
配置菜单
器上安装SM agent
完成主机访问名搜索（自动）
修改菜单
选择“编辑拓朴”，查看服务器的详细信息
选择“主机类型”，可以更换主机的类型，如做win2000server 2003 clustered
选择“配置”-“创建虚拟磁盘”，来进行RAID和VD的创建
选择“手动”创建RAID
配置RAID5
创建虚拟磁盘（VD），指定数据块大小
把VD和服务器相对应。
完成RAID和VD配置
选择“配置”-“配置热备份”配置热备份硬盘
手动指定热备份硬盘
选择“配置”-“创建主机到虚拟磁盘的映射”，创建VD和服务器对应关系
配置对应关系
完成VD和服务器对应关系
Disk，在带内管理下是不能删除的，但是带外下可删除。
支持菜单
选择“查看事件日志”
选择“查看存储阵列配置文件”，可以导出配置
选择“收集文件信息”，可以导出MD3000所有的日记，以供TS分析。
工具菜单
选择“设置或更改密码”，默认是没有密码的，一但设置密码，每次修改都需要输入
如果忘记密码和IP地址，通过以下方法恢复，首先连接COM线到MD3000的“PS/2”，波
特率“115200”
按ctrl+b,会出现如下菜单。
选择“10”
选择“1”
选择“Q”
选择“R”
到sodmain complete，就可以输入命令了
使用clearSYMbolPassword清除密码，注意大小写
使用ifsHow获得IP address，注意大小写
如果删除了Access Virtual Disk，可以用以下命令来恢复，要安装MDSM管理软件，注意这个操作会删除所有配置和数据。
输入以下命令即可
MD3000上有紫色灯亮，说明已经成功。