FUJITSU Server PRIMEQUEST 2000/1000 Series Notes on
Contents
1. File Explorer 7 Select lt EFI gt lt BOOT gt Bootx64 EFI 8 Input the following strings into the item of Input the description as the item of boot manager VMware ESXi 5 x C122 E200 01EN 25 Modify Boot Option Description 9 Select Commit Changes and Exit Change Boot Order VMware ESXi 5 0 Setup is over After that push Enter key and reboot the server 13 PRIMEQUEST 1000 Series If you have two or more disks please install VMware ESXi to first one 14 PRIMEQUEST 1000 Series VMware ESXi cannot perform remote installation in UEFI mode C122 E200 01EN 26 15 PRIMEQUEST 1000 Series If you install OS with UEFI mode you have to remove the JX40 16 PRIMEQUEST 1000 Series If you install VMware ESXi 5 5 with UEFI mode please take care of the following attention After automatic installation starts there is an inquiry for parameter of configuration Please input parameter again as the same as you input in GUI screen 8 Notes on ServerView Update Manager SVUM 1 PRIMEQUEST 2000 1000 Series PRIMEQUEST does not support this product 9 Notes on ServerView Update Manager Express SVUME 1 PRIMEQUEST 2000 1000 Series PRIMEQUEST does not support this product EOF C122 E200 01EN 27 co FUJITSU2. 122 E200 01EN FUJITSU Server PRIMEQUEST 2000 1000 Series Notes on ServerView Suite February 24 2014 FUJITSU LIMITED cO FUJITSU Contents L FG 3 II Notes on ServerView Suite V11 14 02 aa oso oo O GL a dwa 3 1 Notes on ServerView Operations Manager SVOM cccccccsesssscsseseeseeseesesecsecseeseeeeseeeseeessesseeaees 3 2 Notes on ServerView Agent woski AGB Ar GE Gd AAA OG R 5 3 Notes on ServerView RAJD zywa EA ko Gi EYE E dE 9 4 Notes on ServerView Mission Critical Option SVmco eueueu aaa 12 5 Notes on ServerView Mission Critical Option for VM SVimcovm cccccccccscessssessesseseesssseeesees 17 6 Notes on ServerView ESXi CIM Provider cccscccessseeessneecseeecseeecssaeeeceseeeesaeesseaeeeseaeeesenees 21 7 Notes on ServerView Installation Manager SVIM cccccccssessssessescescescsecseescesceecsecesseesseeaeeaes 21 8 Notes on ServerView Update Manager SVUM cccccccscssscesceseessesesesecsseseessesecesseseceseesseseeseeees 27 9 Notes on ServerView Update Manager Express SVUME cccccccsscsscessessesscsscesteseeseeseessceseeees 27 0 C122 E200 01EN I Preface This manual provides notes on ServerView Suite V11 14 02 or later as related to the PRIMEQUEST 2000 1000 series ll Notes on ServerView Suite V11 14 02 1 Notes on ServerView Operations Manager SVOM 1 PRIMEQUEST 2000 1000 Series Note the following point about adding a server
3. e 2 z a 2 Standby Not present 4 Standby Not present Standby Not present Standby Not present Standby Not present Please use One Command Manager of Emulex when you confirm Firmware Version C122 E200 01EN 14 confirmation method of Firmware Version The following are selected from the environment of the target 1 Start menu gt All programs gt Emulex gt OCManager 2 Confirm the Firmware Version of the target PCI card in the One Command Manager window OneCommand Manager File Edit View Port Discovery Batch Help ile ES DERA 97 a pa HEJ EH 4 Hosts 2 WIN MSD 1L5200PQ WmDCe10102 F E Port 0 e SD iqn 1991 05com mi E si Port 1 aB iqn 1991 05com mi EW LPe12002 M8 26 Port 0 236 Port I HM LPe1250 F8 26 Port 0 Adapter Information Firmware Model Serial Number Active Firmware Version Firmware State BIOS Version HW Version NOSI Version IPL File Name PCI Express Link Speed POI Express Bus Width Adapter Temperature Personality Current iSCSI Emulex 0Ce10102 F 10Gb 2 port POle Converged Network Adapter RT01815210 Lens gt Working 42401 25 E2 A2 N A N A x8 r License Features After Reboot FCoE iSCSI NIC on y Show License Features Install Feature Licenses C122 E200 01EN 15 9 PRIMEQUEST 2000 1000 Series If you use SVmco
4. m Syslog Dec 14 19 19 42 RHEL55onVM SVmcovm E 18565 0 14 0 0 SV RAID 10 24 76 104 LSI MegaRAID SAS 9280 8e 4 Device error State change on disk from operational to offline C122 E200 01EN 19 7 8 9 E REMCS SVmcovm P 2011 12 15 21 18 50JE 18565 0 14 0 0 SV RAID 10 24 76 104 LSI MegaRAID SAS 9280 8e 4 Device error State change on disk from operational to offline Dec 15 21 18 50 RHEL55onVM ServerView RAID 10505 Warning Adapter 10 24 76 104 LSI MegaRAID SAS 9280 8e 4 State change on disk 1 8 from operational to offline vendor INTEL model SSDSA2SH064G1GC serial no CVEM008 101VW064KGN M Mail SVmcovm P 1 011 12 28 14 22 50 E 18516 0 14 0 0 SV RAID 10 24 76 104 LSI MegaRAID SAS 9280 8e 3 Adapter error BBU temperature problem detected vendor id 1000 device id 0079 revision Dec 28 14 22 50 rhel5 ServerView RAID 10152 Error Adapter 10 24 76 104 LSI MegaRAID SAS 9280 8e 3 BBU temperature problem detected PRIMEQUEST 1000 Series The Unit name of the ServerView event message is displayed with Seg Bus Dev Func example 0 0 25 0 Unit name in Partition Event Log on MMB screen Unit name in output event of ServerView Refer to 9 Procedure for specifying PCI card error part in VMware5 of PRIMEQUEST 1000 Series ServerView Mission Critical Option User Manual for details PRIMEQUEST 1000 Series When the environment is configured of Windows Server 2012
5. use since SVmcovm 1 2 0 0 PRIMEQUEST 1000 Series When the environment is configured of VMware ESXi5 5 the message that fails in the System Status Change might be output to Syslog or Eventlog However the operation restart of SVmcovm described in the manual is unnecessary The message is the following Event ID 09135 The message System Status is Changed in the OS Running failed ret 1 1 is arbitrary numerical value C122 E200 01EN 20 6 Notes on ServerView ESXi CIM Provider 1 PRIMEQUEST 2000 1000 Series For monitoring PRIMEQUEST 1000 series Use ServerView CIM Provider V6 0 or later version 7 Notes on ServerView Installation Manager SVIM 1 PRIMEQUEST 2000 Series You cannot use the SVIM V11 14 02 for OS installation of PRIMEQUEST 1000 series Please use the manual installation guide 2 PRIMEQUEST 1000 Series A warning message may appear when HBAnyware starts If ServerView Installation Manager automatically installs the application HBAnyware the following warning message may appear when HBAnyware starts You can ignore this message RMServer Failed to register remote request handler for adapter 0 with 3 PRIMEQUEST 1000 Series Note the following points about configuring the RAID and disks in Guide mode Do not configure a disk partition across multiple disks To configure a disk partition across multiple disks do so manually after the installation is completed 4 PR
6. configuration information on PCI card disk is not reported to the REMCS center PRIMEQUEST 1000 Series When the environment is configured of VMware vSphere 5 PCI Express Card Information and Firmware Version in the table of PCI Express Slots of the MMB screen is not displayed IOB or PCI_Box of the menu of the MMB screen PRIMEQUEST 1000 Series The following table lists the packages required for SVmcovm operation Please confirm necessary package has been installed in the partition before installing SVmcovm Remarks To install to 64 bit RHELS or 6 you need to install 32 bit openssl package Also you only need to instsall 32 bit glibc package when you install svmcovm to 64 bit RHEL6 When these packages are not installed SVmcovm cannot be normally started Packages RHEL5 X86 X64 gdb x x x x 1386 gdb x x x x x86_64 tel x x x x 1386 tel x x x x x86 64 openssl x x x x x 1686 expect X X X X X 1386 expect X X X X X X86 64 openssh clients x x x x 1386 openssh clients x x x x x86 64 C122 E200 01EN 17 Packages RHEL6 X86 X64 gdb x x x x 1686 gdb x x x x x86_64 glibc x x x x 1686 tcl x x x x 1686 tcl x x x x x86_64 openssl x x x x x 1686 openssh clients x x x x 1686 openssh clients x x x x x86 64 expect X X X X X 1686 expect X X X X X X86 64 5 PRIMEQUEST 1000 Series The standard of the amount
7. in the PRIMEQUEST 1000 series to the server list When adding a server in the PRIMEQUEST 1000 series to the server list specify the MMB ManageMent Board as the object to be added If you specify a partition directly the following message is output and the object cannot be added It is not allowed to add the virtual PRIMEQEUST 2 PRIMEQUEST 2000 1000 Series In a test of a connection on the PRIMEQUEST MMB test trap in the Connection Test window always fails Use the test trap function of the MMB to test the trap connection For details on the test trap function of the MMB see the following manual PRIMEQUEST 1000 Series Tool Reference 1 5 6 SNMP Configuration menu SNMP Trap window 3 PRIMEQUEST 2000 1000 Series In rare cases a fatal error may occur during a new installation or update installation In such cases perform the new installation or update installation again 4 PRIMEQUEST 2000 1000 Series As soon as the event detected by the driver monitoring function is resolved clear the status If the status is not cleared the event of the hardware whose status is not Normal is suppressed and there is no notification Clearing the status 1 Open the driver monitoring window from the SVOM window 2 Select the component to clear its status and click the Approve button 3 Click the Update button at the top of the window C122 E200 01EN 5 PRIMEQUEST 2000 1000 Series In case of manage t
8. kernel scsi 1 0 2 0 sde Result hostbyte DID NO CONNECT driverbyte DRIVER OK Aug 26 22 40 11 PSA RHEL6 SP1 GA x64 kernel scsi 1 0 2 0 sdc CDB Read 10 28 00 08 8f c1 00 00 00 08 00 Aug 26 22 40 18 RHEL6 SP1 GA x64 Serverview 2151 MINOR Driver Monitoring warning event at server RHEL6 SP1 GA x64 RH61 offline 101 PID 3 14123 Unknown scsi sd_1 0 2 0 Device or Software error rejecting I O to offline device vendor lt VENDOR gt model serial no Find the logged event 14123 detected by ServerView Then find the item logged before it rejecting T O to The numbers shown immediately before the message are Host Channel Id Lun 1 0 2 0 in the above example The device name sde in the above example can be found from the log item that has the same Host Channel Id Lun C122 E200 01EN 3 4 3 You can find the mounting location of the faulty disk from the obtained PrimeCollect Open PrimeCollect and open the var log PrimeCollect tmp PCSysScan xml file in Word 1 MBD2300RC FUJITSU D007PA902HTO0 SASU 2 HDD 0 sda 1 MBD2300RC FUJITSU D007PA902HRR SASU 2 HDD 2 sdb 1 MBD2073RC FUJITSU BSF2P780004J From the device name sde in the above figure confirm the mounting location SASU 2 HDD 3 in the above example PRIMEQUEST 1000 Series Fujitsu does not support rsyslog in Red Hat Enterprise Linux 5 If rsyslog is installed ServerView Agent cannot detect and report errors in I
9. IMEQUEST 1000 Series To connect eight or more PCI cards the I O space assignment must be changed Note the following Assign I O space to the SASU SASRU For installation in a SAN environment assign I O space to the FC card that connects the SAN environment For remote installation assign I O space to the built in LAN port For details on I O space assignment see 5 5 Device Manager Menu in the PRIMEQUEST 1000 Series Tool Reference C122 E110EN C122 E200 01EN 21 5 PRIMEQUEST 1000 Series Note the following about using the Dual Chanel SAS array controller card Before using the Dual Channel SAS array controller card RAID card for an external disk unit in Red Hat Enterprise Linux assign I O space After Red Hat Enterprise Linux is installed if no I O space is assigned when that card is installed the operating system may not start For details on I O space assignment see 5 5 Device Manager Menu in the PRIMEQUEST 1000 Series Tool Reference C122 E110EN 6 PRIMEQUEST 1000 Series Note the following about a SAN or other environment that is connected to many hard disks and LUNs This software can recognize up to 64 hard disks or LUNs If many hard disks or LUNs are connected it may not recognize the installation destination If possible remove all the hard disks or LUNs that are not the installation destination 7 PRIMEQUEST 1000 Series Note the following about installing an operating system that does not suppo
10. O PCI Express card hard disk etc PRIMEQUEST 1000 Series You have a possibility the following message logged even if target system has no error when monitoring VMware ESX 4 x by SVOM Memory module DIMM 0D2 Memory Board 2 in cabinet 0 of server pqesx01 is failing Too many errors have occurred C122 E200 01EN It caused by slow process of VMware When ServerView Agents try to get memory status it takes a lot of times Therefore the process become timeout and logged error To avoid this timeout try to the following workaround lt Workaround gt 1 Calculate the time during booting by using boot completed time of EM_IPMI2 module from var log srvmagt log eecd E g The following message will be logged on the top of log eecd file Jan 12 10 58 24 VMware40U1 eecd F7F026C0 ServerView Agent eecd Version 4 92 60 Milestone N15 Built 2010 07 20 18 15 Start Jan 12 10 58 23 Wrap 0 You can know the boot completed time of EM_IPMI2 module by finding the following message in the log eecd file Jan 12 11 01 44 VMware40U1 eecd F7F026C0 Module EM_IPMI2 started In this case system start at Jan 12 10 58 24 and boot completed Jan 12 11 01 44 You can find the booting takes 3 min 20 sec 200 sec Execute the following procedure A Become root user B Stop ServerView Agents usr sbin srvmagt stop C Move to the directory for setting file cd etc srvmagt D Change the EM_IPMI2 value in th
11. e Module ini only for V5 30 or previous version EM_IPMI2 StartTimeout 300 Note In this case Change the default valu 180 sec to 300 This value are calculated as the below The vale calculated in step 1 200 x 1 5 300 E Change the General value in the Module ini General StartTimeout 420 C122 E200 01EN 5 6 7 8 9 Note In this case you should add same value that is difference between default value and current EM IPMI value F Change the boot script of Server View Agents etc init d srvmagt Line 275 count 420 Note you should use same value as General in step E for this property G Start ServerView Agents usr sbin srvmagt start 3 Confirm the error message still logged or not In case of the error logged you can find the flowing message in var log srvmagt log eecd_a file not log eecd file TIMEOUT Module EM IPMD did not start within Confirm workaround avoid the error specified the above New log eecd a file will be created every Server View Agents booting If still the error logged Change the timeout value more long and try workaround specified the above Note the time depend on the configuration of the system If configuration becomes bigger you should set more long time PRIMEQUEST 1000 Series Use Linux version of Agents V6 10 06 or higher If you have SSD drive on the PCI slot PRIMEQUEST 1000 Series Use Windows version of Agents V6 10 05 or higher If
12. he power of Partition Do not use the power management function on the SVOM Use the power Management function on the MMB 6 PRIMEQUEST 2000 1000 Series Use SVOM V6 10 05 or later for monitoring VMware vSphere 5 As soon as the event detected by the driver monitoring function is resolved clear the status If the status is not cleared the event of the hardware whose status is not Normal is suppressed and there is no notification Clearing the status 1 Open the driver monitoring window from the SVOM window 2 Select the component to clear its status and click the Approve button 3 Click the Update button at the top of the window C122 E200 01EN 2 Notes on ServerView Agent 1 PRIMEQUEST 2000 1000 Series The event information displayed by driver monitoring is cleared after an operating system or SVAgent restart 2 PRIMEQUEST 1000 Series In operation with Red Hat Enterprise Linux 6 if a hard disk connected to an SAS card fails and becomes unresponsive the Fault LED may not go on In such cases use the following method to find the fault location 1 If a hard disk connected to an SAS card fails and you receive notification of the failure obtain PrimeCollect 2 Check the device name in syslog Aug 26 22 40 11 RHEL6 SP1 GA x64 kernel scsi 1 0 2 0 rejecting L O to offline device Aug 26 22 40 11 PSA RHEL6 SP1 GA x64 kernel scsi 1 0 2 0 sde Unhandled error code Aug 26 22 40 11 PSA RHEL6 SP1 GA x64
13. ion number 3 Check the item of native Kernel 4 Check the check box of Virtual environment in Select packages Grub Bootloader Option Mount Options Screen 5 Check the check box of Install Bootloader 6 Check the check box of Boot XEN kernel as default C122 E200 01EN 23 9 PRIMEQUEST 1000 Series You cannot use guided mode in remote installation 10 PRIMEQUEST 1000 Series Note the following about using many CPU PCI card When many CPU PCI card mounted after choosing OS a warning message may be displayed on OS selection Screen Please install by once constituting small then 11 PRIMEQUEST 1000 Series When 16 or more LAN cards are mounted a screen may freeze in Language Selection If you wait for a while after a screen freezes it will recover but if you reduce the number of LAN cards a symptom can be canceled 12 PRIMEQUEST 1000 Series Please register the boot manager when you install the VMware ESXi 5 x in UEFI mode Procedure is the following 1 After power on push F2 key while FUJITSU logo is displayed The following UEFI screen is displayed 2 Select the menu in order to the below Boot Maintenance Manager Boot Options Delete Boot Option 3 Position cursor in VMware ESXi 5 x and push the space bar on it C122 E200 01EN 24 Delete Boot Option 4 Select Commit Change and Exit 5 Select Add Boot Option 6 Select the item of top ESXi
14. nager v5 7 3 and v5 7 8 are the following V5 7 3 can t inform some of event 10987 10988 of ServerView RAID Manager You can download these software from the following site http support ts fujitsu com Index asp 5 PRIMEQUEST 1000 Series If you find Error event ID 18500 18999 28500 28999 from ServerView RAID manager Execute appropriate action for the event and check ServerView RAID manager GUI another error event available or not You found another error event you should execute action for it C122 E200 01EN 11 4 Notes on ServerView Mission Critical Option SVmco 1 PRIMEQUEST 1000 Series For monitoring in the PRIMEQUEST 1800E2 install SVmco For monitoring in the PRIMEQUEST 18008 do not install SVmco For the PRIMEQUEST 1800E PSA monitors and reports errors 2 PRIMEQUEST 1000 Series If SVmco needs to be restarted for the post S Vmco installation settings in VMware 2 3 3 in the ServerView Mission Critical Option Version 1 0 User Manual execute the following procedure in the terminal window sbin service y30SVmco stop sbin service y10SVmco start sbin service y30S Vmco start 3 PRIMEQUEST 1000 Series For the PRIMEQUEST 1800E2 with Windows as the operating system install ServerView RAID Unless ServerView RAID is operating hardware configuration information about the disk is not sent correctly to the REMCS center 4 PRIMEQUEST 1000 Series When you use Oracle VM please install SVmc
15. o V1 2 0 or later in the Host OS 5 PRIMEQUEST 1000 Series When you use PCIe SSD card please install the following SVmco For Linux SVmco V1 4 1 or later For Windows SVmco V1 2 1 or later 6 PRIMEQUEST 1000 Series When you use Windows Server 2012 please install SVmco V1 1 0 2 or later and SIRMS V4 5 0 0 or later Note For the PSHED Plugin driver of less than the V1 8 0 edition the Windows hardware recognition for Windows Server 2012 is uncorrespondence The version for the Windows hardware recognition for Windows Server 2012 must use since the 1 8 0th edition Please use the SVmco V1 8 0 or later for the Windows Server 2012 C122 E200 01EN 12 However If you use the less than SVmco V1 8 0 does not indicate any functionally problem 7 PRIMEQUEST 1000 Series Please install the SVmco V1 2 0 0 or later of RHELS for the Oracle VM C122 E200 01EN 13 8 PRIMEQUEST 1000 Series Firmware Version is not displayed on the Slot of the correspondence of the MMB Web UI when you re operating Fiber Channel over Ethernet by composing iSCSI or NIC PRIMEQUEST 1800E2 W arnin gt System gt IOB gt IOB40 ET EEE IOB 0 Click the Status Clear button to clear the status Board Information CA21358 B32X B19AS PP0933012K og on om Brink Emulex LPe12002 SGb 2 port 0 190 PCle Fibre Channel Adapter 1 Standby Not present LJ a LJ a a a LJ J LJ LJ a a o a LI LE
16. of the resource of SVmcovm is the following Hard Configuration lpartition and 1SB 2CPU Linux At normal At failure detection CPU About 0 About 1 7 MEM About 21MB About the same left HDD About 32MB About the same left Windows At normal At failure detection CPU About 0 4 About 0 5 MEM About 13MB About the same left HDD About 13MB About the same left 18 C122 E200 01EN 6 PRIMEQUEST 1000 Series About the report time at failure detection Time in the report message to syslog REMCS and Mail is different according to the environment in which SVmcovm is installed RHEL6 1 Confirm the time of the following logs output to syslog SVmco I 00069 SVPM startup succeeded etc fujitsu SVmco global pmsvmco conf 2 Compare the time of the red line of the following example and the time examined according to procedure 1 gt After the time that SVmcovm started procedure 1 The report time is local time of a virtual machine in which SVmcovm is installed Before the time that SVmcovm started procedure 1 The report time is reported of with UTC Coordinated Universal Time RHELS AII the report time is local time of a virtual machine in which SVmcovm is installed The target time is a red line of the following example Refer to 8 Messages of PRIMEQUEST 1000 Series ServerView Mission Critical Option User Manual for details
17. r the following table and find correspond combination of software Model Name Software name OS ServerView RAID version V5 7 3 V5 7 8 or later 2 PRIMEQUEST PRIMEQUEST Windows20 x64 OS 2 11 1 2 16 x or later 1400S 1400E 1 Server Agent 03 or later planned OL SOE Windows20 x86 OS 2 11 0 00L 08 or later RHEL5 2 12 0 or later 2 16 0 or later RHEL6 2 11 1 or later 2 17 0 or later VMware 2 12 0 or later 2 16 0 or later ESX4 0 4 1 PRIMEQUEST ServerView Windows20 V6 11 03 or later V6 21 07 or 140082 Agents 08 later Lite 1400S2 Windows20 1400E2 1400L2 12 A PZA RHELS V5 50 20 or later V6 21 20 or RHEL6 later VMware V6 00 10 or later V6 21 20 or ESX4 0 4 1 later ServerView RHELS 1 0 5 or later 2 Critical VMware pon ESX4 1 RHEL6 1 0 5 or later Windows20 x64 OS 1 8 1 or later 08 x86 OS 1 0 3 or later 10 C122 E200 01EN Windows20 x64 OS 1 8 1 or later 12 x86 OS 1 1 0 or later ServerView RHEL5 1 1 2 or later 1 4 0 or later Mission Critical Option for VM RHEL6 1 1 2 or later 1 4 0 or later Windows20 x64 OS 1 3 1 or 1 4 x or later 08 later planned x86 OS 1 1 1 or later Windows20 x64 OS 1 3 1 or 1 4 x or later 12 later planned x86 OS 1 2 0 or later 1 About ServerView Mission Critical Operation for VM OS field means OS which installed to virtual system on VMware ESXi 5 2 The difference of ServerView RAID Ma
18. rt UEFI The PRIMEQUEST is in UEFI mode when shipped from the factory Before installing an operating system that does not support UEFI set BIOS mode The operating systems that support UEFI are as follows Windows Server 2008 64 bit Windows Server 2008 R2 Red Hat Enterprise Linux 6 for Intel64 To set BIOS mode use the following procedure 1 After powering on the partition press the F2 key while the FUJITSU logo is displayed to open the UEFI window C122 E200 01EN 22 2 Select the following menu items in the UEFI window in the order shown Boot Maintenance Manager Boot Options Change Boot Order Change the order 3 Specify that Legacy Boot be at the top Change Boot Order UEFI DVD CD The following shows the meanings of the menu items UEFI Embedded DVD CD Specify this item to use the built in DVD drive for installation in UEFI mode Legacy Boot Specify this item to set BIOS mode Specify it also to use remote storage for installation in BIOS mode UEFI Shell Use it to display the UEFI command prompt at startup 4 Specify Commit Changes and Exit Reset System and reboot the partition 8 PRIMEQUEST 1000 Series When you install the Red hat Enterprise Linux5 with Xen kernel please operate according to the following procedure Installation Manager Deployment Process Selection Screen 1 Select deployment process as Customised Package Selection Screen 2 Input installat
19. urce Disk Description An error during paging was detected on the device Device Harddiskx DRy gt gt If the event was recorded go to step 2 2 Confirm that the ServerView RAID window displays the device where the error occurred as described in the above step 1 gt gt If the device is not displayed even though it is mounted go to step 3 3 Confirm that the ServerView RAID window displays the RAID controller card on the device described the above 2 gt gt If the RAID controller card is not displayed even though it is mounted replace it SAS array disk unit or external RAID card In the above case follow the troubleshooting information provided by Microsoft 3 PRIMEQUEST 1000 Series In case of monitoring RAID on PRIMEQUEST 1000 series with VMware vSphere 5 install ServerView RAID to guest OS which ServerView Mission Critical Option for VM installed C122 E200 01EN 4 PRIMEQUEST 1000 Series Use correspond version of software combination for detect and inform error of ServerView RAID If you use the following software without the combination that specified the following table you will have some problem about RAID error handling E g No error event informed or error event information become garbled when error detected on the RAID Related Software PRIMEQUEST Server Agent PSA ServerView Mission Critical Option SVmco ServerView Mission Critical Option for VM SVmcovm ServerView Agents Refe
20. v1 4 or later and disable IPv6 you need to remove the setting of the snmptrapd file When the setting is not deleted Trap cannot be received In case of the PRIMECLUSTER remove there are a problem that Trap from another node cannot be received Please delete the setting according to the following procedures 1 Open the etc snmp snmptrapd conf and delete the udp6 162 Before snmpTrapdAddr udp 162 udp6 162 After snmpTrapdAddr udp 162 2 Restart snmptrad service and confirm to start normally etc init d snmptrad restart Stopping snmptrapd OK Starting samptrapd OK 10 PRIMEQUEST 1000 Series When you use Windows Server 2012 R2 please install SVmco V1 8 1 0 or later Note For the PSHED Plugin driver of less than the 1 8 1 0 th edition the Windows hardware recognition for Windows Server 2012 R2 is uncorrespondence Therefore there is functionally no problem though pop up is output when you install C122 E200 01EN 16 5 1 2 3 4 Notes on ServerView Mission Critical Option for VM SVmcovm PRIMEQUEST 1000 Series Select a virtual machine on the VMware ESXi 5 server to install SVmcovm in a virtual machine Virtual Machine is necessary in each partition that runs ESXi Refer to PRIMEQUEST 1000 Series ServerView Mission Critical Option User Manual for details PRIMEQUEST 1000 Series When the environment is configured of VMware vSphere 5 hard
21. you will use Windows Server 2012 PRIMEQUEST 1000 Series Use Linux version of Agents V6 10 06 or higher If you will use Oracle VM PRIMEQUEST 2000 1000 Series Check the I O on the SVOM after OS booting because it has possibility to fail the log monitoring during OS booting phase PRIMEQUEST 2000 Series In case of environment which installed Windows Server 2008 R2 without ServerView Installation Manager on PRIMEQUEST 2000 Series You should adopt the following Windows Hotfix before install ServerView Agents http support microsoft com kb 26749 13 en us C122 E200 01EN 3 Notes on ServerView RAID 1 PRIMEQUEST 1000 Series If the diskctrl command is used to execute a disk rotation stop instruction ServerView RAID may output the following message This message is output with the disk rotation stop instruction and does not indicate any operational problem Event ID 10451 Message State change on disk from available to failed lt Example of output gt ServerView RAID 10451 Error Adapter Linux Multiple Devices 0 State change on disk sdb 8 16 from available to failed 2 PRIMEQUEST 2000 1000 Series In a Windows environment if the following event ID 51 occurs a RAID card may have failed Use the following procedure to check whether the RAID card failed and to replace a failed card 1 Confirm that the following event was recorded in the event log Event ID 51 Type Warning So
Download Pdf Manuals
Related Search