Module 2-8 - RAS.ppt

1、RAS - Reliability, Availability, Serviceability,Product Support Engineering,VMware Confidential,VI4 - Mod 2-8 - Slide,2,Module 2 Lessons,Lesson 1 vCenter Server High Availability Lesson 2 vCenter Server Distributed Resource Scheduler Lesson 3 Fault Tolerance Virtual Machines Lesson 4 Enhanced vMotio

2、n Compatibility Lesson 5 DPM - IPMI Lesson 6 vApps Lesson 7 Host Profiles Lesson 8 Reliability, Availability, Serviceability ( RAS ) Lesson 9 Web Access Lesson 10 vCenter Server Update Manager Lesson 11 Guided Consolidation Lesson 12 Health Status,VI4 - Mod 2-8 - Slide,3,Module 2-8 Lessons,Lesson 1

3、Overview of RAS Lesson 2 RAS objectives Lesson 3 Networking vProbs Lesson 4 Storage vProbs Lesson 5 VMFS vProbs Lesson 6 Migration vProb,VI4 - Mod 2-8 - Slide,4,Introduction,The long-term goal of the ESX RAS project is to make ESX more Reliable, Available and Serviceable. To do so the VMkernel needs

4、 to detect, report, recover, diagnose and repair/react to hardware and software problems which occur in the system. ESX RAS 1.0 will focus on detecting asynchronous hardware and synchronous software observations and reporting them.,VI4 - Mod 2-8 - Slide,5,RAS Objectives,ESX RAS team objective is to

5、increase the reliability, availability and serviceability of the vmkernel. This includes: Hardening of vmkernel drivers (hardware errors): CPU, Memory, PCI(-X/Express), SCSI, Networking. Hardening of vmkernel facilities (software errors): SCSI, Networking, VMotion, DMotion, etc. Developing a standar

6、dized method of reporting observations from software and hardware error handlers. Developing a method to diagnose a given stream of observations, down to one or more problems which may have caused them. Develop method for determining predictive failure of a given (sub-)system and feed analysis to co

7、nsumers (DRS, DPM, FT, HA) Gather and write service actions which correspond to the problem or set of problems which are possibly present. Develop automated policies for certain problems which may be taken care of without user action. Maintain and improve logging, coredump, and PSOD infrastructure i

8、n the vmkernel,VI4 - Mod 2-8 - Slide,6,RAS Terms,RAS: Reliability, Availability, Serviceability. Reliability: The ability of a system to perform and maintain its functions, in the face of hostile or unexpected circumstances. Availability: The proportion of time a system is in a functioning condition

9、. Serviceability: The ability to debug or perform root cause analysis in pursuit of solving a problem with a product. Hardening: To enhance a (sub-)system to be able to detect, report and handle errors which may be encountered, whether hardware or software related. Handling may involve panicing and/

10、or attempting recovery from a given error or stream of errors. VProb: A VProb is an automatically generated problem report.,VI4 - Mod 2-8 - Slide,7,RAS Categories,The framework defines the following use cases for vSphere 4.0: Each of the use cases link to respective KBs which describe where the erro

11、r happened (i.e. affected vmnic#, portgroup, vSwitches, storage path etc.) and provides troubleshooting tips to fix the issue. Networking .connectivity.lost .redundancy.lost .redundancy.degraded .e1000.ts06.notsupported Storage vprob.storage.connectivity.lost vprob.storage.redundancy.lost vprob.stor

12、age.redundancy.degraded,VI4 - Mod 2-8 - Slide,8,RAS Categories,VMFS specific: vprob.vmfs.nfs.server.disconnect vprob.vmfs.nfs.server.restored vprob.vmfs.heartbeat.timedout vprob.vmfs.heartbeat.recovered vprob.vmfs.heartbeat.unrecoverable vrpob.vmfs.lock.corruptiondisk vprob.vmfs.resource.corruptiond

13、isk vprob.vmfs.volume.locked Migration Specific: .migrate.vmknic The Public KBs will be available at GA time.,VI4 - Mod 2-8 - Slide,9,Networking VProb,.connectivity.lost Connectivity to a physical network has been lost, all the affected portgroups are part of the message (e.g. Lost network connectiv

14、ity on virtual switch system. Physical NIC vmnic1 is down. Affected port groups: cos, VM Network.),VI4 - Mod 2-8 - Slide,10,Networking VProb,.redundancy.lost Only one physical NIC is currently connected, one more failure will result in a loss of connectivity (e.g. Lost uplink redundancy on virtual s

15、witch system. Physical NIC vmnic0 is down. Affected port groups: cos, VM Network.),VI4 - Mod 2-8 - Slide,11,Networking VProb,.redundancy.degraded One of the physical NICs in your NIC team has gone down, you still have n-1 NICs available (e.g. Uplink redundancy degraded on virtual switch vSwitch0. Ph

16、ysical NIC vmnic1 is down. 2 uplinks still up. Affected portgroups: VM Network.),VI4 - Mod 2-8 - Slide,12,Networking VProb,.e1000.tso6.notsupported (KB article) Guest e1000 driver is misbehaving and sending TSO IPv6 packets, which will be dropped. The vprob specifies the affected VM, and the KB arti

17、cle discusses ways to fix this. Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machineXYZ, or use a different virtual adapter.,VI4 - Mod 2-8 - Slide,13,Storage VProb,vprob.storage.connectivity.lost The connectivi

18、ty to a specific device has been lost (e.g. Lost connectivity to storage device naa.60a9800043346534645a433967325334. Path vmhba35:C1:T0:L7 is down),VI4 - Mod 2-8 - Slide,14,Storage VProb,vprob.storage.redundancy.lost Only one path is remaining to a device and you no longer have any redundancy (e.g.

19、 Lost path redundancy to storage device naa.60a9800043346534645a433967325334. Path vmhba35:C1:T0:L7 is down.),VI4 - Mod 2-8 - Slide,15,Storage VProb,vprob.storage.redundancy.degraded One of your paths to a device has been lost but you still have n-1 paths remaining (e.g. Path redundancy to storage d

20、evice naa.60a9800043346534645a433967325334 degraded. Path vmhba35:C1:T0:L7 is down. 3 remaining active paths.),VI4 - Mod 2-8 - Slide,16,VMFS vProb,vprob.vmfs.nfs.server.disconnect vprob.vmfs.nfs.server.restored Lost connection to server nfs-server mount point /share, mounted as 1264e433-5854ee53-000

21、0-000000000000 (nfs-share),VI4 - Mod 2-8 - Slide,17,VMFS vProb,vprob.vmfs.heartbeat.timedout VMFS Volume Connectivity Degraded 496befed-1c79c817-6beb-001ec9b60619 san-lun-100,VI4 - Mod 2-8 - Slide,18,VMFS vProb,vprob.vmfs.heartbeat.recovered VMFS Volume Connectivity Restored 496befed-1c79c817-6beb-0

22、01ec9b60619 san-lun-100,VI4 - Mod 2-8 - Slide,19,VMFS vProb,vprob.vmfs.heartbeat.unrecoverable VMFS Volume Connectivity lost 496befed-1c79c817-6beb-001ec9b60619 san-lun-100,VI4 - Mod 2-8 - Slide,20,VMFS vProb,vrpob.vmfs.lock.corruptiondisk vprob.vmfs.resource.corruptiondisk Volume 4976b16c-bd394790-6fd8-00215aaf0626 (san-lun-100) may be damaged on disk. Corrupt lock detected at offset O Volume 4976b16c-bd394790-6fd8-00215aaf0626 (san-lun-100) may be damaged on disk. Resource cluster metadata corruption detected,VI4 - Mod 2-8 - Slide,21,VMFS vProb,vprob.vmfs.volume.locked Volume