129
© 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL VCE™ VBLOCK SYSTEM ADMINSTRATION LAB GUIDE April 14, 2014

2014 April 14 Lab Guide Vce Vblock System Administration v0.62

Embed Size (px)

DESCRIPTION

.

Citation preview

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL

    VCE VBLOCK SYSTEM ADMINSTRATION LAB GUIDE

    April 14, 2014

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 2

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 3

    Introduction In order to successfully administer a Vblock System, you need to be able to monitor the environment, provision resources on demand and integrate the Vblock Systems into the existing datacenter operational processes and procedures.

    The labs included in this guide focus on how to monitor the Vblock System physical and virtual infrastructure to understand the environment and to quickly identify where a problem may exist and how that problem may impact the Vblock System services. The labs cover the most common administrative and management tasks that a Vblock System administrator will make for normal day-to-day operations. Additional tasks for organization operation tasks are also covered but these may vary based on the model of Vblock System deployed as well as the steps outlined by the organization.

    VCE as well as the individual component parent companies provide tools to monitor and manage the availability, performance and configuration compliance of both the physical and virtual Vblock System environment. These tools provide complete visibility into the Vblock System infrastructure to identify how resources are being consumed and whether SLAs are being met. These tools provide system administrators with an extensible management framework to simplify the transformation to the VCE Vblock System Cloud.

    VCE is working to introduce that single pane of glass for Vblock System administration. VCE Vision Intelligent Operation Intelligent Operations has been recently introduced to provide that single interface for Vblock System administration. In its current state VCE Vision Intelligent Operation cannot perform all of the required monitoring and management tasks so native element managers are still required. As the capabilities are added to VCE Vision Intelligent Operation, the need for native component interfaces will diminish. The goal of Vision Intelligent Operations is to treat the Vblock System as the single entity that it is with multiple active components.

    This lab guide is provided in a run book manner with each of the specific section objectives performed as tasks that would be executed during the course of normal maintenance and administration. Each lab provides a specific customer use case or scenario so the tasks are applicable to any datacenter deploying a Vblock System. The tasks are not all inclusive and sometimes vary to actual production as to account for the limitation of the training environment or to achieve specific learning objectives. These conditions will be identified in the appropriate sections for this book.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 4

    Lab Scenario: Company Profile and Business Problem Statement Welcome to Counterfake Inc. Counterfake Inc. is a world leader in mock financial transactions. They have had a series of recent production systems outages that have ranged from administrators accidentally bringing down production to multiple hardware failures that have gone undetected that have caused production outage. They have recently acquired a Vblock System, as a complete solution to their datacenter needs. This lab will focus on Counterfake Inc. business problems and how they can best manage their Vblock System. IT management has tasked you to efficiently find issues in both the physical and virtual infrastructure that would possibly impact production. Silos of administration have been torn down and you have the responsibility of managing the entire converged infrastructure of the Vblock System. This requires an understanding of all the components within a Vblock System and the steps to manage each entity in depth. The problems to date include but are not limited to: Component Failure - Server, switch, storage or VM failures can cost Counterfake revenue and reputation if you dont quickly identify each failure and the impact of exceeding SLA time constraints. Secure Access - All administrators across all domains have administrative rights for the entire infrastructure. Administrators and operators can make modifications to systems without the ability to audit who performed what, when. Configuration Management - The environment is dynamic so changes are regularly made to the infrastructure to support business requirements. There have been occasions when infrastructure changes have caused outages. Capacity Management - End users only report a problem when they experience an increase in response time. There is no proactive anticipation of resources nearing performance thresholds; capacity is only expanded after resources pass critical performance thresholds. Data Protection - Backups are taken but you have no confidence that they can be used for a successful restore. There is no consistency in the backup process and no documented and proven recovery process.

    In this lab you will help Counterfake Inc. address their business problems while successfully administering and managing their new Vblock System.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 5

    Lab Architecture

    VCE Vblock Infrastructure Management

    1 - Health Check and Alerting

    Health Check - Monitor the Vblock System as a whole as a well as the individual components.

    Alerting - Configure tools and techniques for unattended alerts and notification.

    2 - Security

    Multi-Tenancy - Logically segregate environments for a secure workspace.

    Hardening - Lock down existing environment for a highly secure Vblock System.

    3 - Management

    Configuration Management - Expand current resource configuration capabilities.

    Capacity Management - Expand current resource bandwidth.

    Automation - Provision resource through automation.

    3 - Protection

    Backup and Recovery - Protect Vblock System metadata and integrate into existing environment.

    Compliance - Validate Vblock System security meets corporate security standards.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 6

    In this class you will be introduced to and work with the VCE proprietary Vblock System management utility, and the element managers of each of the components that make up a Vblock System. The components of Vblock Infrastructure Platforms can be directly controlled using these independent tool sets:

    VCE Vision The VCE Vision software suite provides an integrated set of software products for managing a Vblock System. It enables Vblock System customers to discover their Vblock System, identify where it is located, and what components it contains. It reports on the health or operating status of the Vblock System. It also reports on how compliant the Vblock System is with a VCE Release Certification Matrix and allows customers to automatically update any firmware or software that is not compliant.

    Cisco Unified Computing System Manager (UCSM)

    An embedded web-based management interface for all software and hardware components of the Cisco UCS across multiple chassis and thousands of virtual machines (VMs). The entire UCS is managed as a single logical entity through an intuitive graphical user interface, a command-line interface (CLI), or an XML application-programming interface (API). It provides flexible role- and policy-based management using service profiles and templates to reduce management and administration expenses, which are among the largest costs in most IT budgets.

    Cisco Nexus Operating System (NX-OS)

    Cisco NX-OS streamlines the management and monitoring of the LAN and SAN components offering visibility and control through a single management interface for the Cisco Nexus, and Cisco MDS Family of products.

    EMC Unisphere for VNX

    Web-based management interface for discovering, monitoring, and configuring EMC Unified storage. Unisphere for VNX offers quick access to real-time online support tools. It provides automatic event notification to proactively manage critical status changes.

    EMC Unisphere for VMAX

    Web-based management interface for discovering, monitoring, configuring, and controlling Symmetrix VMAX arrays. Unisphere for VMAX enables initial system discovery and configuration, including device creation and configuration, along with basic device masking and support for managing local and remote replication activities.

    VMware vCenter

    Provides unified management of all the hosts and VMs in the data center from a single console to an aggregate performance monitoring of clusters, hosts, and VMs. VMware vCenter Server gives administrators deep insight into the status and configuration of clusters, hosts, VMs, storage, the guest operating system, and other critical components of a virtual infrastructure. Individual element managers can be polled individually or can be integrated into a customers existing management framework to provide significant intelligence about the resource relationships and dependencies, and the state of business services running on the Vblock System.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 7

    Vblock System Administration and Management Lab Diagram

    For the lab exercises in this guide you will access the Vblock System Management interfaces using the appropriate interface to access the components that compose the training Vblock System. Network connectivity addresses will be supplied on a per team basis for the particular Vblock System setup used during your class.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 8

    Lab Use Cases for Counterfake Inc.

    This Vblock System Administration and Management Lab focuses on specific use case scenarios built around managing the

    VCE Vblock System for Counterfake Inc. To execute the various lab scenarios you will access a simulated an Advanced Management Pod (AMP) that has the preinstalled management interfaces for each of the specific tasks required for lab completion. Most administrative tasks in a Vblock System cross multiple component domains. To emulate the actual management behavior, this guide is written in a Run Book format to align to an administrators execution of an actual datacenter procedure. To simplify the actual lab execution the labs include all required steps regardless of the component domain in which they are run. Labs include the tasks to quickly and efficiently find issues in the physical and virtual environments that would impact a customers ability to maintain production applications on a Vblock System. This is extremely important because if there are issues in the network, storage or physical/virtual servers, customer may experience service interruptions.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 9

    Table of Contents: Vblock Systems Administration and Management

    Introduction .................................................................................................................................. 3

    Lab Scenario: Company Profile and Business Problem Statement ............................................ 4

    Lab Architecture ........................................................................................................................... 5

    Vblock System Administration and Management Lab Diagram .................................................. 7

    Lab Use Cases for Counterfake Inc. ........................................................................................... 8

    Table of Contents: Vblock Systems Administration and Management .................................... 9

    LAB 1. Connecting to the VDC ................................................................................................ 13

    A) Accessing your assigned Windows Management Host. ............................................ 13

    Pre-Lab Notes ............................................................................................................................ 14

    Pre-Lab Considerations ............................................................................................................... 15

    LAB 2. Capturing the Vblock System Configuration Baseline ............................................ 17

    Establish a Vblock System Configuration Baseline ................................................................... 17

    A) UCS Manager GUI (TST): Capture Compute Resource Configuration ..................... 17

    B) UCS Manager CLI (TST): Capture Compute Resource Configuration ..................... 21

    C) EMC Unisphere for VNX (TST): Capture VNX Storage Configuration Information . 23

    D) Navisphere CLI (TST): Capture VNX Storage Configuration using ......................... 24

    E) Solutions Enabler CLI (TST): Capture VMAX Storage Configuration (Optional) .... 26

    F) CLI for MDS Switch (TST): Capture Storage Area Network (SAN) Configuration .. 28

    G) CLI for Nexus 5548 (TST): Capture Network Configuration ..................................... 29

    H) vSphere Web Client (TST): Explore vCenter Configuration .................................... 31

    I) Collection Support Information (TST): VCE Vision and vSphere .............................. 32

    LAB 3. VCE Vision: Administration ........................................................................................ 33

    VCE Vision Utilization ................................................................................................................ 33

    A) VCE Vision System Library (TST): Administration ..................................................... 33

    LAB 4. VCE Vision Plug-in for vCenter................................................................................... 37

    A) Install VCE Vision Plug-in for vCenter (OST) ............................................................. 37

    LAB 5. Monitoring for Component Errors or Failures .......................................................... 40

    A) Vblock System Events (TST) ..................................................................................... 40

    B) Log Browser (TST) ..................................................................................................... 40

    C) UCS Fault Detection (TST) ........................................................................................ 41

    D) Storage Alerts (TST) .................................................................................................. 42

    LAB 6. Securing the Vblock System ....................................................................................... 43

    Security ...................................................................................................................................... 43

    A) vCenter Password Retention (TST) ........................................................................... 43

    B) VCE Vision Appliance and Central Authorization (TST) ............................................ 43

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 10

    C) Adjusting Syslog maximum log file size (TST) ........................................................... 44

    D) Securing a New VLANs with Roles (TST) .................................................................. 45

    E) Creating a QoS Policy on the Nexus 1000v (OST) .................................................... 45

    LAB 7. Trusted Multi-tenant in a Vblock System ................................................................... 48

    Trusted Multi-Tenancy ............................................................................................................... 48

    A) Create Sub-Organizations (TST) ............................................................................... 48

    B) Create Locales (TST) ................................................................................................. 49

    C) Create User Accounts (TST) ...................................................................................... 49

    D) Explore Multi-tenancy restrictions for users in different locales (TST) ....................... 50

    LAB 8. Service Profile Templates and Service Profiles ........................................................ 54

    A) Modifying an Initial Service Profile Template (OST) .................................................. 54

    B) Modifying the Service Profile by Bind to an Initial Service Profile Template (OST) ... 55

    C) Cloning a Service Profile to an Updating Service Profile Template (OST) ................ 57

    D) Modifying Updating Service Profile Template and Bound Service Profile (OST) ...... 58

    LAB 9. UCS Manager: Expanding Address and ID Pools ..................................................... 60

    A) UUID Pool (OST)........................................................................................................ 60

    B) Expand MAC Address Pool (OST) ............................................................................. 61

    C) Expand WWNN Address Pools (OST) ....................................................................... 63

    D) Expand the WWPN Pool (OST) ................................................................................. 64

    LAB 10. Managing Boot Devices and Paths ........................................................................ 66

    A) MDS CLI: WWPN and Zoning Verification ................................................................. 66

    B) UCS Manager: New Boot Policy (VNX) (OST) .......................................................... 69

    LAB 11. UCS Manager: Create a Service Profile from Scratch .......................................... 72

    A) Creating a New Service Profile (OST) ....................................................................... 72

    B) Associate a new service profile (OST) ....................................................................... 74

    C) Unisphere for VNX: Connecting to VNX Storage - New Initiators .............................. 75

    D) Unisphere for VNX: Connecting to VNX Storage Storage Groups ......................... 78

    E) Unisphere for VNX: Connecting to VNX Storage - Creating a boot LUN................... 78

    F) Installing ESXi (OST) ................................................................................................. 79

    G) Restore Original Service Profile (OST) ...................................................................... 82

    LAB 12. Deploying Virtual Machines .................................................................................... 84

    Creating a New Datastore ......................................................................................................... 84

    A) Provision an Additional LUN (OST) ............................................................................ 84

    B) Create a New Datastore (OST) .................................................................................. 85

    Creating a Virtual Machine ........................................................................................................ 86

    C) Creating a New VM in vSphere Web Client (OST) .................................................... 86

    D) Accessing and configuring the first Linux VM (OST) ................................................. 87

    Capacity Management ............................................................................................................... 88

    E) VMware Capacity Monitoring (TST) ........................................................................... 88

    Monitoring Storage .................................................................................................................... 90

    F) Monitor a Storage Pool (TST) .................................................................................... 90

    G) Monitoring a RAID group (TST) ................................................................................. 90

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 11

    Capacity Expansion ................................................................................................................... 90

    H) Expand A Storage Pool (TST) .................................................................................... 91

    I) Expand an Existing LUN (OST) ..................................................................................... 91

    J) Expand a Data Store (OST) ........................................................................................... 91

    Virtual Machine Template Creation and Usage ......................................................................... 92

    K) Creating a VM Template in vSphere Web Client (OST) ............................................ 92

    L) Creating a VM from a Template (OST) ...................................................................... 93

    M) Accessing the new VM Created from a Template (OST) ........................................... 94

    VLAN Creation ........................................................................................................................... 95

    N) Add a VLAN on UCS (OST) ....................................................................................... 95

    O) Adding a VLAN to the Cisco Nexus 5000 (OST) ....................................................... 98

    P) Adding a VLAN to the Cisco Nexus 1000V (OST) ................................................... 100

    Q) Adding the VLAN to VMware Virtual Switch (OST) .................................................. 100

    R) Changing the VLAN for the Application VMs (OST) ................................................ 101

    LAB 13. Creating NFS Stores .............................................................................................. 103

    A) Configuring advanced settings for VMware vSpere ESXi (TST) ............................. 103

    B) Configure File System and NFS Exports (OST) ...................................................... 104

    C) ESXi NFS Configuration (OST) ................................................................................ 105

    VM Access to the NFS File System ......................................................................................... 107

    D) Finding the NFS VLAN ............................................................................................. 107

    E) Adding a New Interface To VNX .............................................................................. 107

    F) Create new network in vSphere ............................................................................... 108

    G) Create new NIC the Application VMs ....................................................................... 108

    H) Create The NFS Mount on the VM........................................................................... 109

    LAB 14. Managing CIFS ....................................................................................................... 111

    A) Creating a CIFS Server ............................................................................................ 111

    B) Create a Volume ...................................................................................................... 111

    C) Creating a File System Pool ..................................................................................... 112

    D) Creating a CIFS file system ..................................................................................... 112

    E) Mount a File System on the CIFS Server in VNX .................................................... 112

    F) Test the CIFS File System on your Management Workstation ................................ 113

    G) Mount CIFS on VM ................................................................................................... 113

    LAB 15. Protecting Vblock System Metadata .................................................................... 114

    A) VCE Vision Configuration Backup ............................................................................ 114

    B) VCE Vision Configuration Restoration ..................................................................... 114

    C) VCE Vision Interface to Vblock System Configuration............................................. 115

    D) Backup of UCS Manager ......................................................................................... 115

    E) Backup of the Nexus 5k Switch ................................................................................ 115

    F) Backup of the MDS Switch ....................................................................................... 116

    LAB 16. Protecting Vblock System Production Data ........................................................ 117

    A) Protection in Unisphere ............................................................................................ 117

    Consistency Groups ............................................................................................................ 118

    B) Creating Application LUNs ....................................................................................... 118

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 12

    C) Creating a Consistency Group ................................................................................. 118

    D) Protection in vSphere ............................................................................................... 118

    LAB 17. Vblock System Assurance .................................................................................... 120

    A) Running Compliance Scans ..................................................................................... 120

    B) Installing New Certification Matrixes ........................................................................ 121

    C) Installing Optional components in a Compliance Scan ............................................ 121

    LAB 18. Proactive Monitoring ............................................................................................. 123

    A) Validating SNMP Setting within the UCS ................................................................. 123

    B) Validating SNMP on the MDS switches ................................................................... 124

    C) Validating SNMP on Nexus 5K Switches ................................................................. 124

    D) Validating SNMP on VNX ......................................................................................... 125

    E) Validating SNMP trap forwarding in EMC Unisphere ............................................... 125

    F) Configure UCS Threshold Policies ........................................................................... 126

    G) Syslog Management ................................................................................................ 127

    H) Using VCE Vision SNMP in Network Management Systems .................................. 128

    I) Testing System Library Configuration .......................................................................... 129

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 13

    LAB 1. Connecting to the VDC

    Lab resources for this activity are located remotely and will be accessed using the EMC Virtual Data Center (VDC). In the section of the lab, you will connect into the VDC and log in to the management server where you will launch the component interfaces required for this exercise.

    A) Accessing your assigned Windows Management Host.

    1) Login to a local computer and open Internet Explorer. Point the browser to the following URL: https://vdc.emc.com. Log in to the Virtual Data Center using the credentials supplied by your instructor. VDC User name: < supplied by your instructor > VDC Password:

    2) After successful authentication, a page will be displayed that shows a list of available systems. Double-click on the VBlock Team X Management icon where X is your team number. This will launch a Remote Desktop Connection session to your teams Windows Management Server.

    3) In the Windows Security popup, click on Use another account in order to log in to the using User Name of Administrator, and a Password of emc123%%

    4) If a Remote Desktop Connection dialog indicating certificate errors pops up, Click Yes to connect despite the warning.

    5) When it comes time to disconnect from the VDC at the end of each day, there are two ways to exit from your Remote Desktop Connection to the Windows Management Host. One will leave your programs running, allowing for later reconnection. The other will cleanly close all programs.

    a) Closing the Remote Desktop Connection window will pop up the following message:

    i) This will disconnect your Remote Desktop Services session. Your programs will continue to run while you are disconnected. You can reconnect to this session later by logging on again.

    ii) Click OK to disconnect in this way

    b) Click on the Start menu and click Logoff to close all programs and logoff

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 14

    Pre-Lab Notes

    Please use IE (Internet Explorer) whenever a browser is needed. In your own environment other browser like Firefox can be used, but in our simulated lab environment conflicts result from multiple students sharing resources. For example, multiple instances of Firefox by the same user ID is not supported on a single shared Windows Management Host. Please do not change any of the configuration parameters, setting or options unless explicitly asked to do so. These systems are in a shared configuration and unsolicited changes could adversely affect both your lab as well as others.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 15

    Pre-Lab Considerations

    Assumptions: As a prerequisite to the steps outlined in this guide, you may assume that basic power and cabling requirements have been met (as per the VCE Vblock System Installation Guide), and that all components of the Vblock System have successfully powered on without error by a VCE engineer or consultant.

    About this Lab Guide:

    This Lab Guide is prepared in a Run Book format as a reference guide to compliment formal documentation. It is not an all-inclusive Vblock Systems procedure guide but does include many of the basic tasks required administer and manage the Vblock System.

    Any Lab Parts prefixed with (OST) in their description should done by

    One Student per Team in order to avoid causing conflicts.

    Any Lab Parts prefixed with (TST) in their description can be done by

    either one or Two Students per Team concurrently.

    Disclaimer: This Lab Guide is current at the time of its creation and may not include updates that supersede tasks outline in this guide. This document provides procedures that may not conform to your installed Vblock environment due to either differences in the Vblock System model or other special configurations for our education setup. These documented procedures should be considered reference only and are only fully qualified for this education lab environment.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 16

    The following illustration shows the components of the Vblock 340 System that will be used for student labs

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 17

    LAB 2. Capturing the Vblock System Configuration Baseline

    Scenario: The Vblock System has just been deployed in the Counterfake Inc. environment. You were exposed to the environment from the test plan execution. As you prepare to take over the administration and management you need to inventory the system to establish a baseline of the initial configuration. Because of its size and number of components, the first thing would be to establish a baseline of how the system was delivered. This provides the ability to compare changes to the environment in the event something stops working.

    Establish a Vblock System Configuration Baseline

    Simulating a new Vblock System arrival, use the individual component element managers to capture the current configuration for each component in the Vblock System. Each step of this lab will familiarize you with how to access each of the component management systems and to gather information particular to that component. No attempt will be made to collect what would constitute a full baseline of a production system. Note: the procedure to access each element manager in this lab can be referred back to from later labs that will not include the full details of the login procedure.

    A) UCS Manager GUI (TST): Capture Compute Resource Configuration

    1) Log into the UCS Manager GUI

    a) On non-lab systems, you will usually launch the UCS Manager GUI from the Cisco Systems UCS Manager Icon generated on the desktop when it is installed. However, for our lab environment it is necessary to always use the Internet Explorer browser icon on the desktop. In the browser address bar enter the UCS Fabric Interconnect Cluster IP of 192.168.1.1

    b) If a Certificate Error warning comes up, choose Continue to this website

    c) Select the Launch UCS Manager button to launch the GUI. Be patient as it may take some time to download the GUI the first time it is launched

    d) If a Security Warning about the certificate pops up, click Continue. Click Continue again, if it pops up again.

    e) Note: UCS Manager GUI requires Java 1.6 or later. The lab systems have Java 1.7.25 installed. DO NOT UPGRADE the Java release if prompted; select the Later option to defer the upgrade. Upgrading may cause other components you will be using as part of the lab to break. As with any multi-vendor solution, you only want to upgrade Java if all of the involved vendors have certified the new level.

    f) Log in using the User Name of admin and Password of emc123%%

    g) If an Unknown Certificate warning pops up, click Accept to continue

    2) Navigate through the GUI to validate the UCS Configuration. This is basic topology information for the Vblock System Compute resources. The topology for the Vblock UCS starts with the Chassis and blade Servers and then transitions to rack mount servers and Fabric Interconnects.

    a) UCS Configuration - Select the Equipment tab on the GUI Navigation pane (left pane)

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 18

    3) View chassis details.

    a) Expand Chassis in the Navigation pane

    b) Expand Chassis 1 in the Navigation pane

    c) Expand Servers tab in the Navigation pane

    d) Select your team server (Team 1, Server 1, etc) in the Navigation pane

    i) With the General tab selected in the Work pane (right-side) notice if the Slot ID matches the Server/Team number?

    ii) Notice the physical position of the server in the graphical picture of the chassis

    iii) Notice the Product Identifier (PID) of your server

    iv) Notice in the Summary section the number of Cores and Threads

    e) Select the Inventory tab then the Storage sub-tab. Identify the PID of the installed Storage Controller

    4) View the blade servers in the chassis

    a) Select Chassis 1 in the Navigation pane

    b) Select Servers tab in the Work pane

    c) Notice the pie charts in the Work pane

    i) Identify if there any Servers that are inoperable

    ii) Identify if there any Servers currently associated with a Service Profile

    iii) Hover the mouse over the pie chart to get a count of associated servers

    5) View the IO Modules in the chassis

    a) In the Navigation pane for Chassis 1 expand IO Modules

    b) Identify how many IO Modules are present

    6) Get details about the IO Modules.

    a) In the Navigation pane select IO Module 1

    b) Select the Fabric Ports tab in the Work pane

    c) Notice the Fabric ID of IO Module 1

    d) In the Navigation pane select IO Module 2, notice if the Fabric ID of IO Module 2 is different than for IO Module 1?

    7) View the Server ports of Fabric Interconnect A

    a) In the Navigation pane, expand Fabric Interconnects

    i) Expand Fabric Interconnect A

    ii) Expand Fixed Module

    iii) Select Ethernet Ports

    b) In the Work pane, click on the If Role title bar to sort the list by role

    i) Identify ports that are configured as Server ports

    ii) Identify ports that are configured as Network ports

    8) View the Server ports of Fabric Interconnect B

    a) In the Navigation pane, expand Fabric Interconnect B

    i) Expand Fixed Module

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 19

    ii) Select Ethernet Ports

    b) In the Work pane, click on the If Role title bar to sort the list by role

    i) Identify ports that are configured as Server ports

    ii) Identify ports that are configured as Network ports

    9) Determine the Fabric Interconnect model number

    a) In the Navigation pane, select Fabric Interconnect A

    b) In the Work Pane select the General tab

    i) Note the Product Name field, it should be either Cisco UCS 6120XP or Cisco UCS 6248UP

    10) View the mode the FC Ports are running in for Fabric Interconnect A

    a) In the Navigation pane, select Fabric Interconnect A

    b) For Fabric Interconnect model number Cisco UCS 6248UP only:

    i) Under Fixed Module select FC Ports

    c) For Fabric Interconnect model number Cisco UCS 6120XP only:

    i) Under Expansion Module 2 select FC Ports

    d) Sort the ports by Role by selecting the If Role column header in the Work pane

    i) Notice the Enabled versus Disabled ports

    ii) In the Navigation pane, select the first FC Port

    iii) Review the Properties displayed on the Work pane.

    (1) Note: Node proxy (N Proxy) port mode is a function of the Fabric Interconnect running in Node Port Virtualization mode (NPV). This is what allows the Fabric Interconnect to log into the upstream FC Switch as Node as opposed to a FC Switch.

    11) View the mode the FC Ports are running in for Fabric Interconnect B

    a) In the Navigation pane, select Fabric Interconnect B

    b) For Fabric Interconnect model number Cisco UCS 6248UP only:

    i) Under Fixed Module select FC Ports

    c) For Fabric Interconnect model number Cisco UCS 6120XP only:

    i) Under Expansion Module 2 select FC Ports

    d) Sort the ports by Role by selecting the If Role column header in the Work pane

    i) Notice the Enabled versus Disabled ports

    ii) In the Navigation pane, select the first FC Port

    iii) Review the Properties displayed on the Work pane.

    12) View the status of FC Uplink ports of Fabric Interconnect A

    a) Select the SAN tab in the Navigation pane

    b) Expand SAN Cloud

    c) Expand Fabric A

    d) Expand FC Port Channels

    e) Select FC Port-Channel 10

    i) In the Work pane notice the VSAN that the Port-Channel is configured in

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 20

    ii) Notice the Port-Channel Admin Speed setting, click the dropdown to see other available settings

    f) In the Work pane, click the Ports tab

    g) Notice there may be no Ports that are members of the Port-Channel, which in this case is expected. The data paths to the Vblock in the lab environment are through the FC-Uplinks ports

    h) In the Navigation pane, expand FC Port-Channel 10, are the same FC Interfaces displayed as in the previous question?

    13) View the defined VSANs

    a) In the Navigation pane, expand VSANs within Fabric A

    b) Select UIM_VSAN_A_10

    i) In the Work pane verify that VSAN ID is set to 10

    ii) Notice the FCoE VLAN ID

    14) View the status of FC Uplink ports of Fabric Interconnect B

    a) In the Navigation pane, select Fabric B

    b) In the Work pane, click the VSANs tab, and identify the VSAN for the Fabric

    c) In the Navigation pane, expand Fabric B

    d) Expand FC Port Channels

    e) Select FC Port-Channel 11

    i) In the Work pane notice the VSAN that the Port-Channel is configured in

    ii) Notice the Port-Channel Admin Speed

    iii) In the Work pane, click the Ports tab, notice no Ports are members of the Port-Channel which in this case is expected.

    15) View the defined VSANs

    a) In the Navigation pane, expand VSANs within Fabric B

    b) Select UIM_VSAN_B_11

    i) Verify that the VSAN ID is 11

    ii) Notice the FCoE VLAN ID

    16) View the Uplink Ethernet Port-Channel in Fabric A

    a) Select the LAN tab in the Navigation pane

    b) Expand LAN Cloud

    c) Expand Fabric A, then expand Port Channels

    d) Expand Port-Channel 101

    e) Notice if interfaces are part of the Port-Channel

    17) View the Uplink Ethernet Port-Channel in Fabric B

    a) Under LAN Cloud, expand Fabric B then Port Channels

    b) Expand Port-Channel 102

    c) Notice which interfaces are part of the Port-Channel, does this look familiar (hint step 8)?

    18) View configured VLANs

    a) Select the LAN tab in the Navigation pane

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 21

    b) Expand LAN Cloud

    c) Expand VLANs

    d) Review the VLANs that are defined for this Vblock

    19) Close the UCS Manager Browser

    B) UCS Manager CLI (TST): Capture Compute Resource Configuration

    1) Log into the UCS Manager CLI

    a) Double-click the putty Icon on the desktop

    b) In the Host Name (or IP address) field, enter the UCS Fabric Interconnect Cluster IP of 192.168.1.1

    c) Click Open

    d) If a PuTTY Security Alert appears, click Yes to add this host to PuTTYs cache and connect

    e) After the login as: prompt, enter the User Name of admin, enter

    f) After the Password: prompt, enter the Password of emc123%%, enter

    2) Display the UCS configuration. In VCE Vblock Systems, UCS Fabric Interconnects are installed in pairs. The Primary Fabric Interconnect automatically appends an -A, while the subordinate Fabric Interconnect appends a -B to the system name for the display at the command prompt. In the example below, the Unified Computing System is named UCS and we are logged into Fabric Interconnect A.

    show configuration

    This command returns a summary of the UCS configuration in XML format. By pressing the spacebar you can navigate through the configuration in its entirety. Entering question mark ? will give you a complete help list for the more command.

    3) Display the UCS cluster information. This command returns the system name, mode and cluster IP address.

    show system

    4) Display a list of fabric interconnects. Note the CLI has built in help available by entering a question mark ? to list options of what can be typed. Additionally, the tab key can be used to autocomplete options on the command line that have only been partially entered. If the entered letters are not sufficient to make a unique completion then the options available are listed. For example try show ?

    show fa

    show fab

    show fabric-interconnect ?

    show fabric-interconnect d

    show fabric-interconnect detail

    This command returns the detailed characteristics about the pair of fabric interconnect switches. It includes Serial Number, installed memory and connectivity information.

    5) Display cluster state

    show cluster extended-state

    This command returns the state of the fabric interconnect cluster. By using the extended state option you also get to see member and heartbeat state information.

    6) Display chassis information:

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 22

    show chassis detail

    This command returns summary information for each of the chassis that are part of the UCS configuration.

    7) Display the IO Module

    scope chassis 1

    scope iom 1

    show detail

    This command returns detailed information about IO Module 1 in chassis 1. The scope command is used to select specific components when you are trying to view information about a device within said component.

    8) Display the configuration

    exit

    exit

    show server inventory

    The two exit commands exit the previous scope commands and change the context back to the top level. The show server inventory command returns a list of the servers installed within the chassis(s). It includes Serial Number, memory and CPU core information.

    9) Display inventory information about network adapters in each server

    show server adapter inventory

    This command returns a list of the adapters within each server in the UCS. These adapters provide both network and storage connectivity.

    10) Display Layer 2 information about the network adapters for a specific server

    scope server 1/5

    show server adapter layer2

    This command returns the media access control address (MAC address) used by the server to communicate at the layer 2 physical network segment. With UCS these are dynamic and assigned via service profiles.

    11) Display blade status

    scope org

    scope service-profile server 1/1

    show status

    This command allows you to view the Service Profile assigned to this blade. The output also includes its association as well as the power and operational state.

    12) Display a list of policies, pools and templates

    scope org

    show boot-policy

    show server-pool

    show vhba-templ

    UCS simplifies administration through the introduction of policies, pools and templates for server management. The commands above provide a simple view of a single policy, pool and template. Run the command show ? to view additional options.

    13) Display any faults in the chassis.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 23

    scope chassis 1

    show fault

    This command provides a list of UCS Chassis errors in a chronological order with a severity, ID and description of each fault.

    14) Display the audit log

    scope security

    show audit-logs

    The audit log allows you to view the changes made to the UCS systems. It provides the time the action took place as well as the user, action type and a description of the action.

    15) Display backup information

    scope system

    show backup

    This command returns the details of the UCS metadata configuration backup.

    To get details about the host and remote location append the detail option to your command. Note, the CLI also supports command history using the up and down arrows. An up arrow would present the previous command as the base for appending the option.

    16) Exit from the CLI and close the window

    exit

    exit

    The first exit command exits from the scope, and the last exit command from the top context exits the CLI and closes the ssh session.

    C) EMC Unisphere for VNX (TST): Capture VNX Storage Configuration Information

    1) Log into the VNX Unisphere GUI

    a) Double-click the Unisphere VNX Client icon on the desktop

    b) In the Connect Host name or IP address field, enter the VNX Control Station IP address of 192.168.1.15.

    c) Click the Connect button

    d) Click either the Accept for Session or Accept Always button in response to the non-trusted certificate warning

    e) Click Accept in response to the GNU General Public License query

    f) Log in using the VNX Control Station User Name of admin and Password of emc123%%

    2) View the available storage for block and file.

    a) From the Dashboard, examine the Overall Capacity graph.

    i) Notice how much total capacity is available in the VNX

    ii) Hover the mouse over the two section of the horizontal bar chart to see them free space available in unused disks and pools

    iii) Examine the Capacity for File graph and notice how much capacity is available for File storage

    3) View the installed disks

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 24

    a) From the Dashboard, click the link to your VNX system, or select the VNX from the Systems list on the Navigation bar at the top of the screen.

    b) Hover your mouse over the System button on the Navigation bar and wait for the system options to display

    c) Click on Disks from the hardware section to display the installed disks

    d) Are there more than one disk Drive Type(s) installed in this system (hint: you may need to scroll)

    e) Look at the LUN IDs column and notice disks with no LUNs, one LUN and multiple LUNs

    4) View hot spare disks.

    a) Hover your mouse over the System button on the Navigation bar waiting for the system options to display

    b) In the Hardware section click on Hot Spare Policy, view the drives set aside based on the policy to be used as hot spares

    c) Notice how many hot spares are configured in this system

    5) Examine Storage Pools

    a) Hover your mouse over the Storage button on the Navigation bar. waiting for the storage options to display

    b) Click to select Storage Pools from the Storage Configuration section

    c) Notice how many storage pools are configured

    d) Notice the different RAID Type(s) in each Storage Pool

    e) Double-click to open Properties for the first Pool in the list.

    f) Select the Disks tab and notice how many LUNs are configured for this pool

    g) Close (or Cancel) the Storage Pool Properties display

    6) Examine RAID Groups.

    a) Click the RAID Groups tab in the Storage Pools display

    b) Notice how many RAID Groups are configured

    c) Are there a variety of RAID Type(s)?

    d) Click to select the first RAID Group in the list and look at Details at the bottom of the screen

    i) Notice how many LUNs are configured in this group

    7) View the connected hosts that are allowed to utilize storage on the VNX

    a) Hover your mouse over the Hosts button on the Navigation bar.

    b) Select Host List from the menu

    c) Click on your teams assigned host from the list and look at Details at the bottom of the screen

    i) Click the Storage Group the host is part of to display the Storage Group Properties

    ii) Close (or Cancel) the Storage Pool Properties display

    8) Leave Unisphere open for later use

    D) Navisphere CLI (TST): Capture VNX Storage Configuration using

    1) Open a command prompt window to access the Navisphere CLI

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 25

    2) Each naviseccli command must specify the VNX Block side user name, password, scope, and VNX Storage Processor IP address where the command will be executed. Alternatively a Navi Security File can be created so this information does not have to be specified for each command.

    3) Review the Navisphere CLI command syntax:

    -address -user -password -scope

    4) Verify the VNX storage array is functioning properly. Use the VNX Storage Processor IP address of 192.168.1.16 a User name of admin and Password of emc123%%

    naviseccli -address -user -password -scope 0 faults

    -list

    This checks the status information for faulted components on the system and should return as operating normally

    5) Create a security file. The VNX user name, password, and scope can be stored in an encrypted security file located in the home directory of your Windows user account. This security file negates the need for specifying a VNX user name, password, and scope for subsequent Navisphere Secure CLI command.

    naviseccli -addusersecurity -user admin -password emc123%% -scope 0

    6) Display VNX system information

    naviseccli -address 192.168.1.16 getall | more

    Be sure to pipe the output to more (|more) as there is a significant amount of information displayed. The command displays SP, Cache, LUN, RAID group, and drive type to name a few. Add an entry to the user security file to simplify command entry and avoid explicitly showing the password

    7) Display SP information.

    naviseccli -address 192.168.1.16 getsp

    Command returns the SP signature, version, serial number and amount of memory each SP has; both SP should match as memory is mirrored

    8) Displays the back-end bus configuration including the devices residing on the back-end bus (be patient, this command may take a while to display)

    naviseccli -address 192.168.1.16 backendbus -analyze | more

    This command returns the current and maximum back-end bus speeds for each back-end bus on the system and the devices on the back-end bus

    9) Display disk status for all disks.

    naviseccli -address 192.168.1.16 getdisk -all | more

    The command provides detailed output for all the disk drives in the array, information displayed includes type, speed, capacity, RAID group and IO profile for the disk

    10) Display disk status for a specific disk.

    naviseccli -address 192.168.1.16 getdisk 0_0_0

    Similar to the display for all devices, this command provides the information for a single disk 0_0_0 (Bus 0, Enclosure 0 and Disk 0)

    11) Display LUN information

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 26

    naviseccli -address 192.168.1.16 getlun -capacity -disk | more

    There are many options available for displaying information at the LUN level; this command returns, in MB, the LUN capacity and the associated disk drive

    12) Display RAID group information - retrieves information about RAID group 1

    naviseccli -address 192.168.1.16 getrg -all | more

    The output varies depending on the switches used but the output of the above command includes RAID group ID, type, list of disks and list of LUNS

    13) Display network name and address information

    naviseccli -address 192.168.1.16 networkadmin -get -all

    This command lists the network information for the specified SP, including port ID, speed and network identification information for the SP

    14) Navisphere CLI is closed after each command line, so there is nothing to close

    a) The command window you ran in can be closed by entering exit on the command line

    exit

    E) Solutions Enabler CLI (TST): Capture VMAX Storage Configuration (Optional)

    1) The Solutions Enabler CLI by default connects to the VMAX storage array through a Fibre Channel inline connection. Your lab Windows Management host does not have this configured. Therefore, you will need to first configure Solutions Enabler to send each command to a remote host, similarly to the way naviseccli worked.

    a) Using Windows Explorer navigate to the folder C:\Program Files\EMC\SYMAPI\config

    b) Open the file netcnfg with WordPad

    c) Add the following line at the bottom of the file:

    VMAX_SOL_ENABLER - TCPIP - 10.126.96.180 2707 NONSECURE

    This line must be entered on a single line in the file

    d) Save the changes to the file and exit WordPad

    2) Open a command prompt window

    3) Check Solutions Enabler version

    symcli

    What is the SYMCLI version number?

    4) Get help on the syntax of a command

    symcli -h

    What does the -v option of this command do?

    What does the -def option of this command do?

    5) List the full list of Solutions Enabler commands

    symcli -v | more

    Read the description of the symcfg command

    6) Create/update the symapi database

    symcfg discover

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 27

    Is the error No devices were found displayed?

    This error is expected because there are no Symmetrix devices configured as visible to this host

    7) Redirect Solutions Enabler commands to run remotely. Please note; in Windows, setting a variable in a command session is only valid for the duration of the session. Therefore, if the command window is closed and reopened, the variable will no longer exist.

    set SYMCLI_CONNECT=VMAX_SOL_ENABLER

    symcli -def

    Set the SYMCLI environmental variable SYMCLI_CONNECT to match the Service Name you set in the netcnfg file earlier.

    Does the output of symcli -def confirm that this is set correctly?

    8) Display the systems discovered previously by this host

    symcfg list

    The command will return all Symmetrix systems the remote management host has access to.

    What are the last 2 digits of the SymmID(s) ?

    9) Display a summary of the VMAX configuration

    symcfg -sid list -v | more

    The output provides summary information for a Symmetrix system. It will provide code levels and resource capacities to name a few.

    10) Restrict future output to only the specified SymmID

    set SYMCLI_SID=

    symcli -def

    Set the SYMCLI environmental variable SYMCLI_SID to match the last 2 digits of a SymmID you found. This provides an alternative to specifying the -sid option on every command line.

    Does the output of symcli -def confirm that this is set correctly?

    Repeat the command symcfg list. This is helpful when there are multiple VMAX systems, but you only need to work with one.

    11) Display a list of directors configured in a VMAX system

    symcfg -dir ALL list

    symcfg -dir all list -v | more

    Hosts connect to front-end directors (FA) and backend directors (DA) provide access to logical devices through cache.

    12) Display information about installed memory

    symcfg list -memory

    The total amount of usable memory is slightly less than half as the Symmetrix mirrors memory for availability and each director uses a small amount for local memory.

    13) Display physical disk configuration

    symdisk list | more

    symdisk list -v | more

    Information is made persistent on the Physical disks. Each is carved up into Hyper Volumes and formed into LUNs for host presentation as thick devices or for data devices for thin provisioning.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 28

    14) Display information about Symmetrix Logical Volumes (LUNs)

    symdev list | more

    symdev list -v | more

    A Symmetrix Logical Volumes is the EMC term for a LUN. It is typically the device that is mapped to a host; thick device maps directly to physical device(s) thin devices bind to a pool of data devices that map to physical devices.

    15) Exit from the Command window

    exit

    Exit will close the Command window and all environmental variable settings will be forgotten.

    F) CLI for MDS Switch (TST): Capture Storage Area Network (SAN) Configuration

    The purpose of this task is to provide the student with a working knowledge of the tools needed to explore the MDS-Series SAN environment.

    1) View Configuration. From the Windows Management host open a putty ssh session to the MDS-Series switch

    a) Double-click the putty Icon on the desktop

    b) In the Host Name (or IP address) field, enter the A-Side MDS Switch IP Address of192.168.1.6

    c) Click Open

    d) If a PuTTY Security Alert appears, click Yes to add this host to PuTTYs cache and connect

    e) After the login as: prompt, enter the User Name of admin, enter

    f) After the Password: prompt, enter the Password of emc123%%, enter

    NOTE: Please DO NOT make any changes to the configuration of the equipment in this procedure. This switch is shared among all students in the class.

    2) Show the available exec commands. Execute the following command to show a list of commands

    ? (Use the space bar to scroll down the list of commands)

    3) Change to configuration mode and display the available configuration options

    config

    4) Display a list of configuration commands

    ?

    5) You will not be making configuration changes in this exercise so just exit the configuration mode

    exit

    6) Display BIOS, loader, kick start, and system firmware versions

    show version

    7) Display the installed licenses for the switch and their usage

    show license usage

    Notice the PORT_ACTIVATION_PKG license count

    8) Display the current startup configuration

    show startup-config

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 29

    Enter space bar to scroll to end of the output of this command

    Does the interface mgmt0 value match what you used to start this putty session?

    9) The above command showed the complete current startup configuration. Use the ? and command line help to show only the last item displayed above

    show startup-config ?

    show startup-config i

    show startup-config interface ?

    show startup-config interace m

    show startup-config interface mgmt ?

    show startup-config interface mgmt 0

    Scroll up the putty display and compare this output to the end of the previous command. Are they the same?

    10) Display the management port configuration

    show interface mgmt0

    Confirm there are not errors on the management interface, notice the error counts

    11) Display a brief description of the port status where your hosts are connected

    show interface brief

    Notice which ports have a Status of up

    12) Display the configured VSANs and their membership

    show vsan membership

    Notice which vsan has all of the interfaces

    13) Display the configured user accounts

    show user-account

    Notice how the admin and monitor accounts differ

    Do any of the roles have an expiry date?

    14) Display the switch status

    show system health

    Validate the current health information and confirm no errors or issues.

    15) Terminate the telnet session and close the Command Prompt.

    exit

    G) CLI for Nexus 5548 (TST): Capture Network Configuration

    The purpose of this task is to provide the student with a working knowledge of the tools needed to explore the Network environment of the Vblock System through the Nexus-Series switch.

    1) View Configuration. From the Windows Management host open a putty ssh session to the Nexus-5548 switch

    a) Double-click the putty icon on the desktop

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 30

    b) In the Host Name (or IP address) field, enter the A-Side Nexus 5548 IP Address of 192.168.1.4 Click Open.

    c) If a PuTTY Security Alert appears, click Yes to add this host to PuTTYs cache and connect

    d) After the login as: prompt, enter the User Name of monitor, enter

    e) After the Password: prompt, enter the Password of emc123%%., enter

    NOTE: Please DO NOT make any changes to the configuration of the equipment in this procedure. This switch is shared among all students in the class.

    2) Show the available exec commands. Notice that the interface for the MDS and Nexus a very similar. Both are built on NX-OS standards

    a) Execute the following command to show a list of commands

    ? (Use the space bar to move down the list of commands)

    3) Display BIOS, loader, kick start, and system firmware versions

    show version

    4) Display the current startup configuration.

    show startup-config

    Enter space bar to scroll to end of the output of this command

    Does the interface mgmt0 value match what you used to start this putty session?

    5) The above command showed the complete current startup configuration. Use the ? and command line help to show only the last item displayed above

    show startup-config ?

    show startup-config i

    show startup-config int

    show startup-config interface ?

    show startup-config interace m

    show startup-config interface mgmt ?

    show startup-config interface mgmt 0

    Scroll up the putty display and compare this output to the end of the previous command. Are they the same?

    6) Display the management port configuration

    show interface mgmt0

    Confirm there is transmit (TX) and Receive (RX) traffic on the management interface

    7) Display a brief description of the port status where your hosts are connected.

    show interface brief

    Notice which ports have a Status of up

    8) View the number of VLANs currently configured on the Nexus switch.

    show vlan summary

    What is the number of user and extended VLANs?

    9) Display the configured user accounts

    show user-account

    Notice how the admin and monitor accounts differ

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 31

    Do any of the roles have an expiry date?

    10) Display the switch status

    show system resources

    show system uptime

    Notice the idle CPU %

    Notice the free memory size and approximate percentage

    Notice the System uptime

    11) Terminate the telnet session and close the Command Prompt

    exit

    H) vSphere Web Client (TST): Explore vCenter Configuration

    VMware vCenter allows simplified ESXi hypervisor management and monitoring. This step will perform basic vCenter Server inventory operations

    1) Verify vSphere license keys to confirm access to advanced features of VMware vSphere 5.x.

    a) Double-click on the vSphere Web Client desktop icon. Use it to log in to your vCenter Appliance system with the User Name of root and Password of vmware

    b) If a Certificate Error warning comes up, choose Continue to this website

    c) In the Navigator pane, select Home > Administration > Licenses

    i) The Licenses pane is displayed. Notice the Usage and Capacity of the vCenter Server license(s) and the vSphere 5 Enterprise CPU license(s)

    2) View vCenter Server status and configuration

    a) Select the home icon in the top bar to quickly get back to the top level

    b) Select Home > vCenter > vCenter Servers >

    c) Select team-X-vcsa where X is your team number

    d) In the pane to the right select the Monitor tab then the Service Health sub tab

    e) There are no ESXi hosts or Virtual Machines to inventory at this point in the lab. They will be added and validated in later sections.

    f) View all Alerts and Warnings.

    g) View the various options and be sure not to change any settings at this point in the lab.

    3) Select the Home icon at the top of the screen

    4) In the pane to the right, select the Home tab, then Event Console

    5) Review the events for your teams vCenter

    a) Click on the first (most recent event)

    b) Can you describe the behavior that caused this event?

    6) Leave the vSphere Web Client open for the next lab

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 32

    I) Collection Support Information (TST): VCE Vision and vSphere

    When dealing with a support call, you will often need to supply system logs, vSphere provides an easy way to collect those logs. Additionally, you will likely want to provide configuration information, and Vision can provide those.

    1) First, collect the pertinent logs with vSphere, continuing to use the vSphere Web Client from the previous lab

    a) From Home, Click on vCenter

    i) select vCenter Servers under Inventory Lists

    ii) Select team-X-vcsa where X is your team number

    iii) In the middle pane click on the Monitor tab

    iv) Click on the System Logs sub-tab

    v) Download the System Log Bundle by clicking the Export System Logs button

    b) Click on the checkbox for your team and click Next

    c) Review the summary and click Generate Log Bundle (you may need to scroll down to see it)

    d) When that finishes, click the same button again, which will now be labeled Download Log Bundle

    e) Set a location (i.e. Desktop) and click Save. This may take a couple of minutes to complete.

    f) Click Finish.

    g) Close the browser window to exit the vSphere client

    2) Now, collect the configuration data this is a collection

    a) Open up Internet Explorer

    b) Go to the address: https://vision.take.emc.edu:8443/fm/configcollector

    c) This will present you with a login request. Log in with the User Name of admin and Password of dangerous for the VCE Vision CAS Authentication on System Library.

    d) A file download message box will appear at the bottom of your browser window asking whether to save or open the zip file that is the collection of configurations. Click Save As from the drop down menu

    e) Save the file to the Desktop as it defaults it will be in the format backup_configCollector_DATETIME.zip

    f) Find the file on your desktop and double click on it

    g) In this zip file, there will be a parent directory, backup, with three subdirectories: compute, network and storage. Each contains the configuration files for each element.

    h) Close both the Internet Explorer and Window Explorer windows.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 33

    LAB 3. VCE Vision: Administration

    VCE Vision Utilization

    VCE Vision allows for the management and monitoring of the various Vblock system components. With VCE Vision, Autonomic Discovery, Identification, Validation, Logging and Health Monitoring can be accomplished, all with one intelligent platform. It has an open API that allows for simple and rapid integration with 3rd party management tools. VCE Vision operates from a virtual machine that is deployed within your Vblocks AMP, which is called the VCE Vision System Library.

    A) VCE Vision System Library (TST): Administration

    There are a number of administrative activities that can be accomplished with the System Library. In this section we will explore these activities as well as a tour of the VCE Vision System Library in general. This is done via the command line by logging into the System Library Appliance. The entire class is sharing a single Vblock, and thus, a System Library, so the lab wont make any changes, but will walk the student through some potential administrative tasks, showing you how to interrogate the System Library, and how you would make changes if you needed to at a later date.

    1) Login to the VCE Vision System Library

    a) Access the VCE Vision System Library using the putty icon on the desktop. Use the VCE Vision OS Appliance Console: IP Address of 192.168.1.10

    b) Enter the User Name of root and Password of V1rtu@1c3!

    2) Validate that the Vision services are running and their associated Process Identifiers (PIDs). These services include:

    3) Check the status of jboss

    service jboss status

    JBOSS PID?

    4) Check the status of postgresql

    service postgresql-9.1 status

    PostgreSQL PID?

    5) Check the status of rabbitmq

    service rabbitmq-server status

    RabbitMQ PID?

    6) Check the status of rsyslog

    service rsyslog status

    Rsyslog PID?

    7) Check the status of all foundation manager services

    service vce-fm-all-services status

    VCE FM Master PID?

    VCE FM Adapter PID?

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 34

    VCE FM Agent PID?

    VCE FM SMNPd PID?

    VCE FM NA Agent PID?

    8) View the master VCE Vision Configuration file

    more /opt/vce/fm/conf/vblock.xml

    9) This will allow you to view the IP address and configuration information for the System Library. Search for the first IP address that start with 192

    /192

    10) Search for the next IP address that start with a 192

    n

    11) Quit viewing the output of the more command

    q

    12) To edit the master VCE Vision Configuration file the sedit command is used. This will allow you to change the IP address/credentials for the System Library. This command will also provide locking/validation around the editing session. The editor used is vim, a Unix vi clone. For help on using vim, one can execute the command vimtutor on the Vision appliance from the command line. While the vblock.xml file will not be edited as part of class, an example of the sedit syntax is below:

    sedit

    13) View the help for the sedit command

    sedit -help

    14) Check the VCE Vblock Systems discovery information

    discoveryDump.sh

    Nexus 5K A Firmware Level?

    Nexus 5K B Firmware Level?

    Nexus 1K Firmware Level?

    MDS Switch A Firmware Level?

    MDS Switch B Firmware Level?

    VNX Array Software Version?

    15) To check the state of the System Library:

    getFMagentInfo

    FMagent Version and Release?

    16) To get the SNMP status of the VCE Vision system

    dumpFMagentState -a 192.168.1.10 -c csnpub

    This many take a few minutes to complete. Remain calm, and then carry on.

    17) For a list of Syslog forwarding options

    configureSyslogForward -h

    We will configure syslog forwarding in the Proactive Monitoring: Syslog Management section later in the lab

    18) To configure/reconfigure SNMP:

    configureSNMP

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 35

    a) Use option 8 to inspect the current configuration. DO NOT MAKE CHANGES now, but observe other options available to change the information. For instance, to change the community that the System Library publishes to, delete the current community with option 10, and then create a new community with option 2.

    b) Use option 12 (done) to exit configuring SNMP

    19) To display current Vblock settings: name, location and main system contact

    getmany -v2c localhost csnpub sysContact sysName sysLocation

    Note: the csnpub in the above command is your community string. The value csnpub is the one used in the lab environment, but should be replaced with whatever the community string is in your environment.

    DO NOT MAKE CHANGES now, but the command setSNMPParams can be used to change these values

    20) To manually backup the configuration files:

    collectConfig.sh

    This will collect the configuration files for all the systems. Later in the lab we will explore how to download the most recent collection of configuration files to your workstation. If you are working on the system library (as you are now in the lab), you can review these configuration files in the directory /opt/vce/fm/backup. Here you will find a log of the collector, and the configuration files the collector has retrieved (not just the most recent time) under the compute, network, and storage directories.

    21) List all files recursively in the backup directory, noting their classification and size.

    ls -FlasR /opt/vce/fm/backup

    22) There are a series of system log files on the Vision appliance. They can all be found through a single collected directory in /var/log/slib - this is a collection of symbolic links to the actual log directories elsewhere in the system, but makes it easy to get at the logs. There is also an interface to collect all of the logs into a group archive for export called export-fm-logs

    ls FlasR /var/log/slib

    23) Change into the temporary directory:

    cd /tmp

    24) Create a directory

    a) Where X is your team number followed by your last name

    mkdir

    25) Change into your new directory:

    cd /tmp/

    26) Export the Foundation Management Agent log file

    export-fm-logs -f fm_logs.tar.gz

    This is a tar file. You can extract it with the tar command; most Zip utilities can also extract files in the tape archive format (tar files).

    27) Extract the exported Foundation Management Agent log file

    tar xzvf fm_logs.tar.gz

    28) The logs are now extracted, view the contents of the FMAgent.log file

    less opt/vce/fm/logs/FMAgent.log

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 36

    29) Quit the he output of the less command

    a) q

    30) To explore the SNMP data being published by the System Library, you can use the getmany command. Above we retrieved the system name, location and contact, but you can also get any of the SNMP data from the command line.

    a) getmany -v2c localhost csnpub entPhysicalDescr

    31) VCE Vision automatically discovers the physical and logical components of the Vblock System, populating its database repository that feeds the APIs provided. This discovery process, which initially populates the database and, later, updates it as things change, occurs every 15 minutes by default. This interval can be adjusted. The 15-minute initial value is the minimum interval, but it can be set to be anything up to 1440 minutes. Below is an overview on how to change the system discovery cycle:

    a) While the FM Services will not be stopped (stopFMagent) in this example, this would be the first step

    b) Go to the directory where fmagent.xml file is located

    cd /opt/vce/fm/conf

    c) View configuration details in the fmagent.xml file

    more fmagent.xml

    d) Note the Discovery Cycle time between the start tag and end tag

    e) While the FM Services will not be started (startFMagent) in this example, this would be the last step

    32) To make logging into the System Library easier without compromising security, you may choose to place your Pretty Good Privacy (PGP) Public Key on the VCE Vision system. There are a number of tools that allow you to create a public/private key pair such as pgpi.org, gnupg.org, or openpgp.org While beyond the scope of this lab, the user can place their public key in the file /root/.ssh/authorized_keys ensuring that the file is accessible only by the root user when they are finished: chmod 600 /root/.ssh/authorized_keys This will allow tools like putty or ssh to log in without a password, using your key pair to authenticate you.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 37

    LAB 4. VCE Vision Plug-in for vCenter

    While your Vblock comes with a vSphere installed with the Vision extensions, you may find the need to manage the Vblock from a different instance of vCenter, or through an upgrade find you need to install the VCE Vision Intelligent Operations Plug-in for vCenter. This lab walks through that process.

    A) Install VCE Vision Plug-in for vCenter (OST)

    1) The Plug-in can be downloaded from the VCE Customer Portal, for the lab, it has been placed in the share vblock_share.

    a) Double click on the vblock_share shortcut on the desktop of the Windows Management Host

    2) Navigate to the Plug-in directory

    a) Z:\Vision\Plug-in\vce-plugin-2.1.2.0

    b) Copy the vce-plugin folder from the Vblock share to the plugin-packages folder on your Windows Management Host

    c) In the vce-plugin-2.1.2.0 folder, select the vce-plugin sub-folder

    d) Copy the directory vce-plugin, right click, and select Copy.

    e) Select Local Disk (C:) and navigate to the target directory:

    i) C:\Program Files\VMware\Infrastructure\vSphereWebClient\plugin-packages

    f) Right click, and select Paste from the menu to copy the vce-plugin directory into the plugin-packages directory.

    3) Restart the Windows Management Host

    a) Double click on the vblock_share shortcut on the desktop of the Windows Management Host

    b) Navigate to the Vision directory

    Z:\Vision

    c) Double click on the reboot.bat file

    d) If prompted by a popup Open File Security Warning window click the Run button

    i) It will take the Windows Management Host and the associated VMware vSphere Web Client service up to five minutes to become available.

    4) After waiting 5 minutes, log back in to Windows Management Host

    a) Open your local computer open Internet Explorer. Point the browser to the following URL: https://vdc.emc.com. Log in to the Virtual Data Center using the credentials supplied by your instructor.

    i) VDC User name: < supplied by your instructor >

    ii) VDC Password:

    b) After successful authentication, a page will be displayed that shows a list of available systems. Double-click on the VBlock Team X Management icon where X is your team number. This will launch a Remote Desktop Connection session to your teams Windows Management Server.

    c) In the Windows Security popup, click on Use another account in order to log in to the using User Name of Administrator, and a Password of emc123%%

    5) Prepare for Configuring the VCE Vision Plug-in for vCenter

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 38

    a) Security requires that a full hostname is used in the plug-ins authentication, not an IP address, but the name of the host. To do this, the IP address that is assigned to your Vision console must be in your companies DNS records, or, as we will do here in the lab, in your local hosts lookup file. We will add the entry here:

    i) Determine if the VCE Vision OS Appliance Console already has a DNS record. The standard output returned should resolve the FQDN of vision.take.emc.edu to an IP address of 192.168.1.10. Type:

    nslookup vision.take.emc.edu.

    ii) Open a command prompt window

    iii) Double click on the Command Prompt shortcut on the desktop

    b) Test name resolution and connectivity to the VCE Vision OS Appliance, type:

    putty vision.take.emc.edu

    i) Log in to the VCE Vision OS Appliance with a User Name of root and a Password of V1rtu@1c3!

    c) Close the PuTTy session to the VCE Vision OS Appliance command prompt window by exiting, type:

    exit

    d) Close the Command Prompt window by exiting, type:

    exit

    6) Test the REST Interfaces of VCE Vision

    a) Open an Internet Explorer

    b) In the URL bar enter the address

    https://vision.take.emc.edu:8443/fm/vblocks

    c) Select the Continue to this website link

    d) Log in to the VCE Vision CAS Authentication on System Library with a User Name of admin and Password of dangerous

    i) Note the XML displayed. This output details the type of template used when VCE Vision discovered the Vblock.

    e) Close the Internet Explorer CAS VCE Vision tab

    7) Configure the VCE Vision Plug-in for vCenter

    a) Double-click on the vSphere Web Client desktop icon. Select the Continue to this website link. Use it to log in to your vCenter Appliance system with the User Name of root and Password of vmware

    b) Click on Administration in the Navigation pane

    c) Click on Settings under the VCE Vision Plugin for vCenter

    i) Note: If there is no VCE Vision Plugin for vCenter under the Administration menu, close the vSphere Web Client tab, wait 2 minutes, then re-launch the vSphere Web Client via the desktop icon.

    8) Verify/Enter the credentials for the VCE Vision CAS Authentication

    a) Hostname: vision.take.emc.edu

    b) Port: 8443

    c) Username: admin

    d) Password (retype the password if it already exists): dangerous

    e) Confirm Password (retype the password if it already exists): dangerous

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 39

    f) Remember that the vision network address must be the name of the Vision System Library as it resolves in either DNS or the systems hosts file. An IP address will not work here because of how the security mechanisms work within Vision.

    9) Update the settings

    a) Click Update Settings

    b) Click OK to acknowledge restart message

    10) Restart the vSphere Web Service

    a) Start the Services assistant via Start > Administrative Tools > Services

    b) Locate and highlight the service VMWare vSphere Web Client Service

    c) Click on Restart Service

    d) It will take the service up to five minutes to become available note that it takes longer for all of the vSphere services and plugins to become available than just the vSphere web service.

    e) Close the vSphere Web Client browser window

    11) Validate the VCE Vision Plug-in for vCenter

    a) Double-click on the vSphere Web Client desktop icon. Select the Continue to this website link. Use it to log in to your vCenter Appliance system with the User Name of root and Password of vmware

    b) Click on Home in the Navigation pane

    c) Click on Home tab in the Home pane

    d) Locate the Vblock icon in the inventory pane, and select it

    e) In the Navigation pane, expand the Vblock heading prefaced with a capital V icon

    f) In the Navigation pane, expand the Compute resources. Note, there are two UCS Fabric Interconnects, and a single UCS Chassis discovered by VCE Vision. Return to the Home screen of vSphere

    g) Click Home at the top of the Navigation pane

    h) Click on Home tab in the Home pane

    i) Under the Home tab select the VCE Vision System Library Event Monitor icon

    j) Under Monitoring, select the VCE Vision System Library Event Monitor

    k) Validate that vSphere is connected to VCE Vision by ensuring a list of is events populated.

  • 2014 VCE Company LLC. All rights reserved. VCE CONFIDENTIAL 40

    LAB 5. Monitoring for Component Errors or Failures

    There is a wealth of information about the Vblocks current status, and ways to monitor the system for errors or complete failures of your components.

    In this lab we will take a tour of ways to investigate the various health statuses of your Vblock.

    A key part of the ability to monitor and manage these types of issues with the Vblock is the VCE Vision Intelligent Operations product that came installed on your Vblock. Often you will be delving into the individual element managers for detailed information, but VCE Vision groups this information in a Vblock-centric manner then makes it easier to diagnose issues.

    Monitoring Availability with VCE Vision

    While the Vblock arrived at Counterfake Inc. with a full vCenter operational; you may want to integrate using your existing vSphere Web Client to manage the Vblock system. VCE Vision has a vCenter Web Client Plug-in that allows the client to interface directly with the information stream produced by the Vision product.

    The vSphere Web Client that is installed on your management station does not have the VCE Vision Plug-in For vCenter installed; the first section of this lab is to install it, much like you might have to do back at your own facility.

    This plug-in will allow you to view and manage the Vblock in the VMware suite as a single Vblock entity, instead of a collection of components. Additionally it will provide powerful insights into overall Vblock management and maintenance. Before we actually capture the baseline, we are going to install the plug-in for your vSphere Web Client.

    A) Vblock System Events (TST)

    VCE Vision maintains a Vblock-wide event log that can be accessed through the vSphere VCE Vision plugin.

    1) View VMware events

    a) Double-click on the vSphere Web Client desktop icon. Select the Continue to this website link. Use it to log in to your vCenter Appliance system with the User Name of root and Password of vmware

    b) Click Home at the top of the Navigation pane

    c) Select Events.