Welcome to VxRail Appliance Remote Support and Troubleshooting course.

Transcription

1 Welcome to course. Copyright 2016 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. DELL EMC MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any DELL EMC software described in this publication requires an applicable software license. The trademarks, logos, and service marks (collectively "Trademarks") appearing in this publication are the property of DELL EMC Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any Trademark without the prior written permission of the party that owns the Trademark. AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Aveksa, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect, ClaimPack, ClaimsEditor, Claralert,CLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration Intelligence, Configuresoft, Connectrix, Constellation Computing, CoprHD, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge, Data Protection Suite. Data Protection Advisor, DBClassify, DD Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, DSSD, ECS, elnput, E-Lab, Elastic Cloud Storage, Xaminer, Xtender, EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eroom, Event Explorer, FAST, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator, InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, Isilon, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor, Metro, MetroPoint, MirrorView, Mozy, Multi-Band Deduplication,Navisphere, Netstorage, NetWitness, NetWorker, EMC OnCourse, OnRack, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, Silver Trail, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, VCE. Velocity, Viewlets, ViPR, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O PLUS, VSET, VSPEX, Watch4net, WebXtender, xpression, xpresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage. Revision Date: <Published DATE /MM/YYYY> Revision Number: <Course Number>. <Product Version>.<<Edit Version> (Ex: MR-1CP- SYMCFG ) 1

2 This course provides the an introduction to the procedures used to support and troubleshot the VxRail Appliance. The content in this course is not considered all inclusive as platform operations and operator behavior is constantly evolving. This course provides lessons learned from earlier product versions as well as those unearthed in beta or some of the early customer deployments and should not be considered the definitive list as new issues and troubleshooting processes are being continuously developed. The topics covered in this training include: Identify common issues with VxRail Appliance installation and operations. Utilize the VxRail Manager and vcenter to monitor and troubleshoot VxRail Appliance issues. Perform procedures to properly gather information required for problem determination. Execute support procedures to address common VxRail Appliance issues. 2

3 This module covers Common VxRail Appliance installation and operations issues. Common VxRail Appliance installation and production issues Discuss issues with: Hardware Software Configuration Introduce the VxRail Appliance Knowledge Base articles used to expedite problem determination and remediation 3

4 Even the best built product can have issues. The goal is to identify them fast and expedite the problem resolution to get it back in production. The VxRail Appliance can have issues product deployment or once installed in production. Issues can range from faulty hardware, to configuration that adversely effect production or a problem can be related to resource availability. Whatever the reason, the objective when servicing a VxRail Appliance is to return the system to an optimal operating state. 4

5 VxRail Appliance problems can occur at installation or while in production. Installation issues provide a first impression of the platform and delay it from going into production, where production issues can have a direct impact on an organizations finances. That s why it s important to properly size the system as well as proactively monitor it to prevent an outage which could result in lost revenue. 5

6 When the VxRail Appliance was first introduced it was a partner/customer installable virtual appliance solution. Ease of deployment was an early advantage and might have been overstated as most deployments seemed to fail due to configuration issues. These were primarily network switch related as customers would supply a switch that met the requirements but was not properly configured for the VxRail Appliance. To address the issues with installation, professional services was enlisted to perform the installations, this reduced a large number of the basic configuration issues it did not eliminate all of them. 6

7 Production issues can be introduced by not sizing the system properly when initially purchase. If the system does not have sufficient resources it can be dynamically expanded on demand. All system resources should be leveraged throughout the entire appliance. Holding resources as reserved to used later limit the full capabilities of the appliance. As with most systems it is recommended to go wide before going deep. Network configuration issues are the most common issues when deploying VxRail Appliance solutions. 7

8 Hardware issues happen, it s not if it s when, and when they do there are procedures available in the EMC SolVe Desktop that provide instructions for how to do the component replacement. Each component has fault indicators but often theses are not enough and the system must be investigated to determine an actual failed part. This is where alerts and log files may be helpful but more on this later. 8

9 When investigating a problem believed to be software related, first check the knowledge base for articles related to the issue. If the issue is after a recent component replacement or expansion, validate systems are operating at the correct software and firmware levels. Also validate systems are at the same maintenance or patch level as there can be compatibility issues across maintenance releases. 9

10 The process of determining what action to take may take many forms, some are systematic and others just from product knowledge. Experience administrators jump into an issue with a proposed fix based on a small amount of information. This may be because they may recognize and easily distinguished an issue. Their knowledge and expertise is such that they are able to resolve the issue successfully with a minimum of investigation. With the VxRail Appliance having so many integrated components it is important to validate a change to fix a problem does not introduce a regression in some other functional area. Monitoring the log files after altering the system will help validate the system is performing as expected. 10

11 Dell EMC has defined a common framework for supporting the VxRail Appliance. It is a software life cycle processes, with well-defined processes and procedures that are required to quickly expedite the support process. 11

12 VxRail Appliance includes knowledge base (KB) articles that provide both structured and unstructured information used to size, deploy and support the system. VxRail Appliance has a master Knowledge Base (KB) article that references all VxRail Appliance KBs created for the product line. 12

13 Support procedures on a VxRail Appliance help us find and address issues that impact installation and production. Installation issues prevent the appliance from going operational and impact time to value. Once installed and integrated into the environment, issues that impact production impact revenue and reputation. Hardware issues happen and when they do there are certain steps that should be followed to help find and fix the problem. When investigating a problem believed to be software related, first check the knowledge base system. 13

14 Upon completion of this module, you should be able to: Discuss how ESRS VE provides remote connection between Dell EMC Customer Service and the VxRail Appliance Introduce the different VxRail Appliance Baseboard Management Controller (BMC) interfaces Quanta Compute Nodes use IPMI Interface Dell Compute Nodes use idrac Interface Explain the primary VxRail Management Interfaces VMware vcenter to monitor the VMware virtual environment VxRail Manager to monitor the VxRail Appliance 14

15 Use EMC Secure Remote Services Virtual Edition is a proactive and predictive customer service capability that is included in with the VxRail Appliance warranty or maintenance agreement. It allows customer service to monitor and access a VxRail Appliance in a secure, high-speed manor that operates 24/7. 15

16 On the VxRail Manager Support page click View the Last Configuration Sent. The customer must have a registered EMC Online account (SSO registered account) with proper synchronization to LDAP. The customer account must have an authorized contact relationship to the SiteID and must have Web Support enabled The PSNT (Product S/N) must be in a status of Install and there must be an Active support contract SiteID must be auto-registered (listed in ESRS v3 site verification database) 16

17 ESRS VE will receive all the connect home files transmitted by the VxRail Appliance but the CE on site still needs to configure connect home that will use the ESRS VE for connect home. The ESRS VE performs the same basic functions as the ESRS Gateway, ESRS Gateway is ESRS version 2 and the ESRS VE is ESRS version 3. 17

18 Quanta Servers use the Intelligent Platform Management Interface (IPMI) for hardware management. This provides a standardized interfaces for VxRail Systems with Quanta nodes for server platform management services. Dell Remote Access Controller (idrac) is embedded in every Dell PowerEdge server and is used to manage and monitor VxRail Appliances with Dell compute nodes. 18

19 Every major network switch manufacturer includes a command line interface to make modifications to the environment. Some include a graphical interface but all will include a way to monitor, configure and troubleshoot the physical switch from a CLI. For support to be able to investigate an issue with the network the switch must be configured on the network with access via a terminal emulation tool. The putty tool is a preferred tool from support and is required on the jump server so support can provide assistance in validating a switch configuration for a customer provided switch or troubleshoot a Dell EMC provided switch. 19

20 The VMware vsphere virtualized infrastructure is managed by VMware vcenter Server 6.0. The VMware vcenter Server provides the management of vsphere deployments, and the rapid provisioning, monitoring, and controlling of virtual machines. In VxRail deployments, all the ESXi nodes in the appliances and the vsan Datastore are backed by a single instance of the VMware vcenter Server. The VMware vcenter Server framework is installed as a single virtual machine configuration on the primary node or connected to an external vcenter environment. VxRail Manager monitors its virtual infrastructure also which we will be discussing in this presentation. 20

21 The vsphere web client is a powerful interface which let s you view an initial Summary of the ESXi host on the Summary tab after selecting the ESXi host in the left navigation pane. This is where you can start. From here from here you can get more detail related to each ESXi host. You are able to review issues, performance, tasks, events, hardware status and view the logs for a host. 21

22 On the vsphere web client navigate from the Home icon to Storage. This will present a high level view of the storage and its entities. You can start with the Summary tab always a good place to begin. You ll notice 5 datastores in this 4 node appliance example we re looking at. There is one for each node in this cluster. You ll also notice the MARVIN-Virtual-SAN. vsan entity. You can select any of device in the left pane to and see Summary information on the right. This is a good place to see their storage allocation. You can page down to get more details. 22

23 On the vsphere web client staying with the vsan selection and Monitor tab, you can see 4 options Issues, Performance, Tasks and Events. Each gives you more detail if ever needed. In the Performance/Space option you can see how much space is in use for multiple entities such as swap files, virtual disk, free space, etc. 23

24 VxRail Appliance includes the Virtual SAN Health Service to monitor the overall health of vsan in the Cluster. vsan Health Service provides tools that not only identify an issue but also provide specifics on why it might report an error. 24

25 The VxRail Manager interface provides a simplified way to perform some of the common tasks usually done in vcenter. While vcenter remains available for all management tasks, VxRail Manager monitors overall system health, gathering log bundles, and viewing events. The various areas on VxRail Appliance management can be accessed by the simple navigation bar on the left side of the interface. 25

26 The VxRail Manager Events tab displays a list of current system events. System events: The System events list displays all of the VxRail Appliance events. Event details: Displays information for the selected event in the System events list. If there are critical events detected, the Health icon displays the number of unread events, in red, in the navigation bar. 26

27 The Physical tab of the VxRail Manager Health window displays information about the hardware components of your appliance. A graphical representation of the appliances in your cluster makes it easy to navigate for event and status information. Use the Physical tab to view the following: Appliances in the cluster: View appliance status and information such as ID, serial number, and so on. Individual appliance components: Drill down to see status and information for appliance components such as disks, compute nodes, and power supplies. 27

28 The Logical tab of the VxRail Manager Health window displays information about the hardware components of your appliance. A graphical representation of the appliances in your cluster makes it easy to navigate for event and status information. At the top you see the VxRail Serial number that is assigned, here it starts with EMC8SQ If there are multiple appliances in one cluster you will see an entry across the top for each one. Each appliance is selectable to review it s component information. On the top half of the screen we see the Main Health timeline for Storage IOPS, CPU Usage and Memory Usage with additional numbers in each category providing a good high level view of the appliance use. Under the main health timeline you ll find the Storage Information providing capacity, used, free and provisioned. 28

29 When you scroll down the Logical Health page you can see the individual nodes for the selected appliance. Each attribute line for a node can be expanded. Notice here that we have expanded the NIC information for node1. 29

30 Key points covered in this module: VMware vsphere 6.0 provides the virtual infrastructure for the VxRail Appliance. Virtualized infrastructure support performed using vcenter Server 6.0. VxRail Manager is used to generate log files. 30

31 This module covers the following topics: Collecting customer and incident information Gathering component information Network switch VMware vcenter VMware ESXi VMware vrealize Log Insight VxRail includes a master collection Knowledge Base references a log collection article 31

32 Field resources and customers have been told that they should expect to provide these resources to enable support to quickly provide assistance. Formulate a short, concise problem description Characterize the problem Is it an isolated component or systemic? Is the problem intermittent or consistent? Is the problem performance related? Has something changed? What is the expected performance? What is the impact of issue? 32

33 The VxRail has logging enabled on multiple layers of the software stack from both VMware and EMC sides. The VxRail Manager interface has a simple button to automatically collect and download all the logs, but if it is failing for any reason, then log collection becomes a manual task. 33

34 The marvin.log file can provide additional details about anything that has been done in the VxRail system including installation issues. The marvin.log file is located in the vcenter Server at the path described here. During installation, it is very useful to connect via SSH and tail the log file. The CLI window will be automatically updated as the installation progresses. 34

35 The VxRail Appliance offers the fastest path to a VMware virtual infrastructure solution. It can only run the vsphere hypervisor and leverages the VMware software defined storage with Virtual SAN. To troubleshoot the virtual environment you need to access the VMware support log bundle. For a detailed look at what the bundle offers, refer to VMware KB articles for more information on: Collecting diagnostic information for ESX/ESXi hosts and vcenter Server using the vsphere Web Client ( ) Collecting Virtual SAN (vsan) support logs and uploading to VMware ( ) Collecting diagnostic information for VMware vcenter Server and ESX/ESXi using the vsphere PowerCLI ( ) 35

36 To access log files on either vcenter or on an ESXi node will require access to the systems from a Command Line Interface (CLI) All VMware systems by default are secured with no secure shell (ssh) access. Secure shell must be enabled for CLI access. 36

37 The vc-support.sh script can be run to collect the vcenter log bundle. It records all logs and the information from the vcsa until the time of the collection. This script creates a vcsupport.zip file in the /root directory of the vcsa that can be downloaded to the service laptop or local machine for troubleshooting purposes. The current VCSA does not allow FTP/scp directly from the appliance - because you hit the commnand> prompt upon ssh to the appliance, so to pull the resultant vc-support.tgz file from the VCSA - you need to either scp the file off to another location or use - then use root credentials to download. 37

38 The vm-support command can be run on ESXi nodes to generate the vsphere log bundle. The vsphere bundle is the standard vmsupport bundle collected in typical ESXi troubleshooting. The bundle contains all log files for a specific node. It takes a few minutes to generate this log bundle. This command creates a.tgz file which contains many log files related to the ESXi node. This file should be copied from the ESXi node to a service laptop or local machine using SCP. To run the CLI command, the user must login into each one of the nodes as root via SSH connection. By default SSH is not enabled - this can be enabled either through manage->settings->security or through the DCUI Troubleshooting options. 38

39 Switch logs are important for viewing the state and events of the network switch in a VxRail Appliance. They show information related to performance and traffic as well as error logs used to fix a problem on an individual ports such as: port and NIC speed or duplex mismatch, bad cables, or bad NIC hardware or drivers. Be aware that each switch has its own operating systems and commands will differ across vendors. You may need to ask the customer for log files for switches you are unfamiliar with. 39

40 vrealize Log Insight is included in the VxRail Appliance. It delivers highly scalable log management with intuitive, actionable dashboards, sophisticated analytics and extensibility, providing deep operational visibility and faster troubleshooting for issues across the components within the appliance. For the most up to date information on capturing Log Insight logs please reference: Collecting diagnostic information for VMware vrealize Log Insight ( ) 40

41 Key points covered in this module: Every VxRail Appliance issue must capture specifics about the customer, system and problem to expedite the problem resolution. Log bundles are available for each component in the VxRail Appliance: vsphere Network Switch VMware vrealize Log Insight is available for VxRail Appliance log correlation. 41

42 This module covers the following topics: Considerations for managing installation issues: Some issues require a simple retry to resolve the problem. Some installation issues may require the VxRail Appliance be reset using the Dell EMC provided reset script. EMC Solve Desktop provides VxRail Appliance hardware replacement procedures. VxRail Appliance is a new platform that runs multiple software components which may require frequent software updates. 42

43 The first indicator to a problem is the fault indicators on the chassis and nodes. To simply state it, Blue indicates the system is operating as expected while Amber indicates a problem. 43

44 The SolVe Desktop tool will not only provide procedures for common tasks, it will also perform technical reviews by comparing the proposed engagement against known issues using built-in rules. 44

45 The SolVe Desktop provides procedures for common tasks such as FRU/CRU replacement. Additionally, SolVe includes only relevant information for end-users, is fully offline capable, and avoids out of date content. End-users also have access to up-to-date Knowledge Base content. All relevant information is available to users at the time of procedure generation. 45

46 The VxRail Appliance Reset Script is destructive and should only be used only if other measures to fix a faulted installation do not work. It does require the system to be properly configured for successful execution. The script has dependencies on the 2.6 version of Python. If the reset for a node fails, try cleaning up all the existing VMs, any leftover vsan objects, remove the node from maintenance mode before trying to reset it again 46

47 VxRail Appliance is a new platform that runs multiple software components which may require frequent updates to the VMware and Dell EMC software used to manage and operate the VxRail Appliance. It is recommended to view log files, release notes and check for configuration changes that may be effected with a new feature or software upgrade. 47

48 Problems may arise if the VxRail Appliance is not powered-up or powered-down in the proper sequence. Cluster startup is very easy, simply by powering up the nodes in the cluster. Because it is a cluster, intelligence is built in to start the nodes in the proper order. Note: NTP is highly recommended in a cluster so their clock times are kept in sync. This also assists debugging activities. 48

49 The VxRail Manager includes procedures to simplify the shutdown of the VxRail Appliance and cluster, especially for multiple appliance installations. Simply navigate to the Configuration tab on the left and select General on the top, then scroll down to the Cluster Shutdown button. Select and confirm the operation to invoke a simplified process to stop Virtual Machine before stopping the nodes running the ESXi hypervisor. System diagnostics will be run before the shutdown process. Graceful shutdown is a composite operation that systematically brings down system resources within the VxRail Appliance cluster so the system experiences no data loss and can seamlessly brought back online. 49

50 Key points covered in this module: Introduced installation issues that range from simple that require a simple retry to more difficult that may require a full system reset to factory defaults. The EMC Solve Desktop should be followed when a hardware issue requires a component replacement. Includes the hardware replacement procedures for VxRail. VxRail Appliance may require software updates. Validate software levels to make sure previous updates haven t introduced any regressions. 50

51 Upon completion of this module, you should be able to: Explain how troubleshooting on a VxRail Appliance requires knowledge of: The physical components The logical configuration The virtual infrastructure Describe common VxRail Appliance Network Issues Describe common VxRail Appliance Installation Issues Describe common Virtual SAN (vsan) Issues 51

52 Troubleshooting on a VxRail Appliance is problem solving across physical, logical and virtual resources. It not only applied to repair failed components but also the issues that arise from misconfiguration of software that makeup the solution. The goal is to quickly identify the issue and solve it to return the system to production. 52

53 On the VxRail Appliance the management network require IPv4 and IPv6 with multicast support for the Management port groups VLAN to allow Loudmouth communication. There is also loudmouth client on the ESXi /usr/lib/vmware/loudmouth/loudmouthc. The vsan network requires IPv4 with multicast support for the vsan port group VLAN. The Multicast requirements for Snooping and Querier are recommended for optimal performance, but in some cases during troubleshooting you may want to disable them. In multi-switch configurations, the multicast group needs to be configured to traverse all switches connected to all hosts in the same cluster. 53

54 The first indication that there is an installation issue will be on the VxRail GUI interface. The GUI will display an error if there is a problem. The percentage shown will help determine at what point in the installation it failed. The lower right hand side of the screen will also indicate what the problem could potentially be. 54

55 Top issues preventing successful deployment of ESRS on VxRail include Name resolution where DNS is not properly resolving hostnames on either the ESRS VE Virtual Machine or on the VxRail Manager. Issues with the Customer EMC support account can be problematic if the support account being used to deploy ESRS is not present in the site id where the VxRail serial number resides or is not web support enabled. External vcenter ESRS deployment may fail with Invalid target datastore specified or similar during the OVF deployment phase of ESRS deployment. VxRail Manager may not properly identify the external vcenter components to deploy the ESRS OVF properly. Manual ESRS deployment would be required in this instance Blocked ports Customer firewall may be blocking ports required for successful ESRS deployment. 55

56 An ESX host that has been instructed to enter maintenance mode may show "in progress" for an indefinite amount of time under Tasks in vcenter. When this happens, no virtual machines are migrated and the task cannot be cancelled. Before a host can enter maintenance mode all virtual machines need to be powered off or migrated to another host. If a host is unable to be placed in maintenance mode in VxRail there may be a problem with inaccessible/unhealthy vsan objects or resource availability. 56

57 The initial VxRail Appliance configuration will embed specifically named objects and items into vcenter that must not be altered by the customer. The initial VxRail configuration will apply configuration settings into vcenter that also must not be modified. If the named objects and items reserved for VxRail use are modified post-implementation, there is a high risk of system failure. If the configuration settings applied for VxRail use are modified post-implementation, there also is a high risk of system failure. The configurator will create a cluster on the vcenter instance for exclusive use by VxRail. The cluster name must not be changed. The cluster created by the VxRail configurator is placed under a Data Center in vcenter. The name of the Data Center must not be modified. The hostnames of the ESXi hosts in the VxRail cluster must not be modified. VxRail is dependent on the set of virtual machines deployed by VxRail configurator (VxRail Manager, vcenter. PSC, Log Insight, ESRS-VE). These virtual machines must not be modified. 57

58 If the vsan health check reports component metadata health errors this may be related to Ops backlog. This is usually temporary, run the health check again in a few minutes. If it reports an error related to an invalid state, this is a known issue and is believed to be resolved in the release running on the VxRail Appliance. If the health check reports physical disks have failed, this may be a logical problem that a host reboot typically resolves this type of failure or it could be an actual drive failure. If the heath check reports some errors about stats.db this may be related to the performance service being enabled. 58

59 If there are problems seen with powering on a virtual machine with errors about the swap file. Check cluster connectivity as this can cause a situation where the VM is unable to create a new file. Also confirm all the hosts and drives are in the cluster and there is enough capacity. 59

60 Network partitions can be the result of logical configuration on the hosts or physical configuration on the physical network especially with Multicast and IGMP settings. Most network partitions will not impact vsan health long-term, as long as the misconfiguration is identified, and corrected. Standard networking tests should be used for basic connectivity. When troubleshooting a vsan network, verify all vsan hosts can ping each other over the vsan-enabled vmkernel ports and logical configuration of addresses, subnets, VLANs, and physical connectivity. 60

61 The network is a critical component to the VxRail Appliance and is provided by the customer who is also responsible for its configuration. When troubleshooting the system it is important to know how to use basic networking tools to validate the appliance configuration. 61

62 Key points covered in this module: Basic VxRail Appliance troubleshooting requires knowledge of: The physical components The logical configuration The virtual infrastructure The most common type of VxRail Appliance Network problem is network switch not properly configured Problems with a VxRail Appliance Installation can often be fixed by retrying the failed script Catastrophic failures may require a full system reset Virtual SAN (vsan) is very specific with package versioning, when troubleshooting always validate software versions 62

63 Key points covered in this course: VxRail Appliance introduces support procedures for problem determination and remediation. Platform is managed using vcenter and VxRail Manager to access support chat and generate log files. Every VxRail Appliance issue must capture specifics about the customer, system and problem to expedite the problem resolution. VxRail Appliance include procedures to address configuration, hardware and software issues. 63

64 Do not record. Feedback Link will be inserted by Production Team. (Do not include this slide in Student Guide> 64

65 Thank you! 65