DCUCT Data Center Unified Computing Troubleshooting Version 5.0 Fast Lane LAB Guide Version 5.1.2 (UCS Software 2.1) ATTENTION The Information contained in this guide is intended for training purposes only. This guide contains information and activities that, while beneficial for purposes of training in a close, non-production environment, can result in downtime or other severe consequences and therefore are not intended as a reference guide. This guide is not a technical reference and should not, under any circumstances be used in a production environment. Customers should refer to the published specifications applicable to specific products for technical information. The information in this guide is distributed AS IS, and the use of this information or implementation of any recommendations or techniques herein is a customer’s responsibility. COPYRIGHT © 2013 Fast Lane GmbH. All rights reserved. All other brands and product names are trademarks of their respective owners. No part of this book covered by copyright may be reproduced in any form or by any means (graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system) without prior written permission of the copyright owner. Fast Lane reserves the right to change any products described herein at any time and without notice. Fast Lane assumes no responsibility or liability arising from the use of products or materials described herein, except as expressly agreed to in writing by Fast Lane. The use or purchase of this product or materials does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of Fast Lanehe product described in this manual may be protected by one or more patents, foreign patents, or pending applications. 2 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Overview This guide presents the instructions and other information concerning the lab activities for this course. You can find the solutions in the lab activity Answer Key. Outline This guide includes these activities: n Lab 1-1: Cisco UCS Network Baseline Documentation n Lab 1-2: Cisco UCS Management and Service Profile Deployment n Lab 1-3: Troubleshoot Cisco UCS B-Series Server Boot from SAN n Lab 1-4: Troubleshoot LAN Connectivity: Part 1 n Lab 1-5: Troubleshoot LAN Connectivity: Part 2 n Lab 1-6: Troubleshoot Failover Connectivity: Part 1 n Lab 1-7: Troubleshoot Failover Connectivity: Part 2 n Lab 3-1: Troubleshoot Cisco UCS C-Series © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 3 FastLane UCS Lab Layout FastLane UCS Lab v1.5 FTP/WWW/mail NetApp 172.17.1.x/24 Data Network MDS A MDS B Student Desktop 172.16.1.x/24 Management Network FI A GE FI B 2232PP FEX 2232PP FEX FC Port 0 10GE Port 1 eth2 eth1 8x C200 with VIC 4 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Remote Lab login Note the remote lab access data you received from your instructor in this table: LAB IDs: Rack 183 is Lab ID 1, Rack 184 is Lab ID 2, Rack 191 is Lab ID 3, Rack 192 is Lab ID 4, Rack 109 is Lab ID 5, Rack 110 is Lab ID 6, Rack 108 is Lab ID 7. Ask your instructor for your lab id! The URL is always: http://remotelabs.flane.de LAB ID POD# © 2013 Fast Lane and Cisco Systems, Inc. Username Password Fast Lane Lab Guide V5.1.2 5 FastLane UCS Lab Topology – Lab Aids Management IP Addresses (P is always your Pod #) Device IP Address Default Gateway MDS-A 172.16.1.31 172.16.1.254 MDS-B 172.16.1.32 172.16.1.254 UCS Fabric A 172.16.1.101 172.16.1.254 UCS Fabric B 172.16.1.102 172.16.1.254 UCS Cluster IP 172.16.1.200 172.16.1.254 Domain Controller/DNS 172.16.1.20 172.16.1.254 Student Desktop 172.16.1.2P 172.17.1.2P 172.16.1.254 n/a Mail Server 172.16.1.250 172.17.1.250 172.17.1.254 Linux Server 1 172.17.11.1 172.17.11.254 Linux Server 2 172.17.P1.2 172.17.P1.254 UCS Central Server 172.16.1.100 172.16.1.254 Device Username Password Student PC administrator 1234QWer Linux student 1234QWer (with sudo 1234QWer) UCS Manager admin 1234QWer MDS student 1234QWer UCS Central admin 1245QWer / key 1245QWer Device Login Credentials 6 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. DCUCT ................................................................................................................................. 1 Overview ..................................................................................................................................... 3 Outline .................................................................................................................................................. 3 FastLane UCS Lab Layout ........................................................................................................ 4 Remote Lab login ....................................................................................................................... 5 FastLane UCS Lab Topology – Lab Aids ................................................................................. 6 Lab 1-1: Cisco UCS Network Baseline Documentation ......................................................... 9 Activity Objective .................................................................................................................................. 9 Visual Objective .................................................................................................................................... 9 Required Resources ........................................................................................................................... 10 Command List .................................................................................................................................... 10 Task 1: Verify Cisco UCS Equipment Using Cisco UCSM GUI .......................................................... 11 Task 2: Verify Cisco UCS B-Series Equipment .................................................................................. 13 Task 3: Verify Cisco UCS C-Series Equipment .................................................................................. 14 Task 4: Examine LAN and SAN Network Topology ........................................................................... 15 Lab 1-2: Cisco UCS Management and Service Profile Deployment .................................... 17 Activity Objective ................................................................................................................................ 17 Required Resources ........................................................................................................................... 17 Task 1: Lab setup ............................................................................................................................... 18 Task 2: Trouble Ticket ........................................................................................................................ 21 Task 3: Clean Up ................................................................................................................................ 22 Lab 1-3: Troubleshoot Cisco UCS B-Series Server Boot from SAN ................................... 23 Activity Objective ................................................................................................................................ 23 Required Resources ........................................................................................................................... 23 Job Aids .............................................................................................................................................. 23 Command List .................................................................................................................................... 24 Task 1: Lab setup ............................................................................................................................... 25 Task 2: Trouble Ticket ........................................................................................................................ 28 Task 3: Clean Up ................................................................................................................................ 29 Lab 1-4: Troubleshoot LAN Connectivity: Part 1 .................................................................. 30 Activity Objective ................................................................................................................................ 30 Required Resources ........................................................................................................................... 30 Job Aids .............................................................................................................................................. 30 Task 1: Lab setup ............................................................................................................................... 31 Task 2: Trouble Ticket ........................................................................................................................ 34 Task 3: Clean Up ................................................................................................................................ 35 Lab 1-5: Troubleshoot LAN Connectivity: Part 2 .................................................................. 36 Activity Objective ................................................................................................................................ 36 Required Resources ........................................................................................................................... 36 Job Aids .............................................................................................................................................. 36 Task 1: Lab setup ............................................................................................................................... 37 Task 2: Trouble Ticket ........................................................................................................................ 40 Task 3: Clean Up ................................................................................................................................ 41 Lab 1-6: Troubleshoot Failover Connectivity: Part 1 ........................................................... 42 Activity Objective ................................................................................................................................ 42 Required Resources ........................................................................................................................... 42 Job Aids .............................................................................................................................................. 42 Task 1: Lab setup ............................................................................................................................... 43 Task 2: Trouble Ticket ........................................................................................................................ 46 Task 3: Clean Up ................................................................................................................................ 47 © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 7 Lab 1-7: Troubleshoot Failover Connectivity: Part 2............................................................ 48 Activity Objective ................................................................................................................................ 48 Required Resources ........................................................................................................................... 48 Job Aids .............................................................................................................................................. 48 Task 1: Lab setup ............................................................................................................................... 49 Task 2: Trouble Ticket ........................................................................................................................ 52 Task 3: Clean Up ................................................................................................................................ 53 Lab 3-1: Troubleshoot Cisco UCS C-Series .......................................................................... 54 Activity Objective ................................................................................................................................ 54 Required Resources ........................................................................................................................... 54 Job Aids .............................................................................................................................................. 54 Task 1: Lab setup ............................................................................................................................... 55 Task 2: Trouble Ticket ........................................................................................................................ 58 Task 3: Clean Up ................................................................................................................................ 60 Answer Key .............................................................................................................................. 61 Lab 1-1 Answer Key: Cisco UCS Network Baseline Documentation ................................................. 61 Lab 1-2 Answer Key: Cisco UCS Management and Service Profile Deployment .............................. 85 Lab 1-3 Answer Key: Troubleshoot Cisco UCS B-Series Server Boot from SAN .............................. 92 Lab 1-4 Answer Key: Troubleshoot LAN Connectivity: Part 1 ............................................................ 97 Lab 1-5 Answer Key: Troubleshoot LAN Connectivity: Part 2 ............................................................ 99 Lab 1-6 Answer Key: Troubleshoot Failover Connectivity: Part 1 .................................................... 103 Lab 1-7 Answer Key: Troubleshoot Failover Connectivity: Part 2 .................................................... 106 Lab 3-1 Answer Key: Troubleshoot Cisco UCS C-Series Server ..................................................... 108 8 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-1: Cisco UCS Network Baseline Documentation Complete this lab activity to practice using support tools that are available for Cisco UCS systems and to determine equipment available in the lab. Activity Objective In this activity, you will use the CLI or GUI to log in to the equipment in your pod. After completing this activity, you will be able to meet these objectives: n Check that you can access the lab environment n Examine Cisco UCS B-Series and C-Series server equipment using the Cisco UCSM GUI n Examine LAN and SAN network topology Caution Do not reload the equipment or erase configurations because it can take more than 20 minutes to complete the reload. Visual Objective The figure illustrates your lab topology. FastLane UCS Lab v1.5 FTP/WWW/mail NetApp 172.17.1.x/24 Data Network MDS A MDS B Student Desktop 172.16.1.x/24 Management Network FI A GE FI B 2232PP FEX 2232PP FEX FC Port 0 10GE Port 1 eth2 eth1 8x C200 with VIC © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 9 Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Instructor to provide the access details for lab equipment n A computer and network access n Preconfigured Core Switch n Eight Cisco UCS C-Series servers n Two Cisco MDS switches n JBOD Disk array n Two Cisco UCS I/O Modules n One Cisco UCS Chassis n Eight Cisco UCS B-Series servers Command List The table describes the commands that are used in this activity. Cisco UCSM and NX-OS Commands 10 Command Description connect local-mgmt Connects to the local management port connect nxos Connects to NX-OS CLI scope license Enters the license mode show cdp neighbor Displays neighbor information obtained by Cisco Discovery Protocol show cluster state Displays cluster information show interface brief Displays brief overview of interfaces show interface status Displays interface status show usage detail Displays license usage for a Fabric Interconnect show version Displays Cisco NX-OS version Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Verify Cisco UCS Equipment Using Cisco UCSM GUI In this task, you will examine Cisco UCS B-Series server equipment using Cisco UCS Manager (UCSM) GUI. Activity Procedure Complete these steps: Step 1 Log into the FastLane remote lab by starting internet explorer (or any other browser) and navigating to http://remotelabs.flane.de Step 2 Click the “login” button on the top right (or the “student login” link on the bottom of the page) Step 3 Login with the credentials of your workgroup (supplied by the instructor) Step 4 Click on the BLUE PC icon to start your remote access session to the remote lab. ALL lab exercises will be done on this PC, your local PC will only be used for accessing the remote lab GUI. (the GREY components are not manageable by you for now). Use username “Administrator” und passwort “1234QWer” Step 5 Click on the “UCS Manager” icon on the remote desktop to connect to the UCS manager (this icon is just a shortcut to http://172.16.1.200, you can also start IE manually and type the url.) Step 6 Wait for the page to load and click the LAUNCH UCS Manager link to start the Cisco UCS Manager application. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 11 Step 7 Confirm all security warnings and log in by using the admin account and the password that was entered in the configuration wizard (1234QWer) (NOTE: everybody in the lab is using the admin account, please be cautious not to step on anybody else, configure ONLY your designated ports, servers etc. If you want to perform some additional tasks or play around, ask your instructor first.) Step 8 Select the Equipment tab in the left pane. Step 9 Select Chassis, and in the right pane, select the server assigned to your pod. Your Server number is your Pod# (e.G. Pod 9 would use Server 9) Step 10 Right-click on your server and select Show Navigator. Step 11 In the right pane, select the Inventory tab. Step 12 In the left pane, select Chassis 1 and then IO Modules. Expand the view in the right pane by clicking on the + sign. Write down the IO modules model in your chassis, the port types, and the number of ports. ___________________________________ Step 13 Determine and write down the type of FEX used for rack-mount connectivity __________________________________ Activity Verification You have completed this task when you attain this result: 12 n You successfully logged into UCS Manager n Requested information is written down. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 2: Verify Cisco UCS B-Series Equipment In this task, you will examine the Cisco UCS B-Series server equipment using Cisco IMC. Activity Procedure Complete these steps: Step 1 The instructor will assign a B-Series Blade server to your pod. (most likely your server slot is your Pod#, Pod1=Slot1/Server1, Pod2=Slot2/Server2 etc.) Step 2 Use UCS Manager to navigate to “Equipment” – “Chassis 1” and click on your assigned server Step 3 Determine and write down the status and status details of your assigned server ___________________________________________________________________ Step 4 Note Select Inventory and, by navigating through different tabs, determine and write down the following information in the right pane: n Cisco IMC firmware version ______________________ n Number of CPUs, speed, and number of cores ______________________ n Number of DIMMs and total amount of memory ______________________ n Number and type of adapters ______________________ n Local storage information ______________________ Different Pods may have different hardware. Step 5 Examine and write down the server BIOS version. ______________________ Step 6 Is Intel VT enabled in the BIOS? ______________________ Step 7 Examine and write down the server fault status. ______________________ Step 8 How much Power is used by your server? ______________________ Step 9 What is the CPU temperature? ______________________ Step 10 Turn ON the locator LED (Hint: use the General tab) Student Notes __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 13 Task 3: Verify Cisco UCS C-Series Equipment In this task, you will examine the Cisco UCS C-Series server equipment using Cisco IMC. Activity Procedure Complete these steps: Step 1 The instructor will assign a C-Series Rack server to your pod. (most likely your server slot is your Pod#, Pod1=Server1, Pod2=Server2 etc.) Step 2 Use UCS Manager to navigate to “Equipment” – “Rack-Mounts” and click on your assigned server Step 3 Determine and write down the status and status details of your assigned server ___________________________________________________________________ Step 4 Note Select Inventory and, by navigating through different tabs, determine and write down the following information in the right pane: n Cisco IMC firmware version ______________________ n Number of CPUs, speed, and number of cores ______________________ n Number of DIMMs and total amount of memory ______________________ n Number and type of adapters ______________________ n Local storage information ______________________ Different Pods may have different hardware. Step 5 Examine and write down the server BIOS version. ______________________ Step 6 Examine and write down the server fault status. ______________________ Step 7 What is the reported fault? ______________________ Step 8 How much Power is used by your server? ______________________ Step 9 What is the CPU temperature? ______________________ Step 10 Turn ON the locator LED (Hint: use the General tab) Student Notes __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ 14 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 4: Examine LAN and SAN Network Topology In this task, you will examine LAN and SAN network topology. Activity Procedure Complete these steps: Step 1 On your assigned management PC, open Cisco UCSM. Step 2 On the web page, select Cisco UCSM and log in using username admin with password 1234QWer. The Equipment topology page appears. Step 3 Select the Equipment tab in the left pane. Step 4 Select Fabric Interconnect and then, in the right pane, select the Fabric Interconnects tab. Step 5 Expand the view by clicking on the + sign. Step 6 Write down number of uplink ports A:________ B:_______ Step 7 Write down the number of server ports A:________ B:_______ Step 8 Write down the number of Fibre Channel ports A:________ B:_______ Step 9 Write down the number of unconfigured Ethernet ports. A:________ B:_______ Step 10 Connect to Cisco UCSM using SSH protocol. Connect by using PuTTY or a similar terminal client. Use IP address 172.16.1.200. Log in using username admin with password 1234QWer. (Hint: you may have to change the CLI mode) Step 11 By using Cisco Discovery Protocol, determine neighboring devices and ports used for connection. Device ID Step 12 Local Interface Remote Interface Determine and write down the Cisco NX-OS version running on the Fabric Interconnect. (not the UCS version) Fabric Interconnect A: Kickstart: ____________________________ System: ____________________________ Fabric Interconnect B: Kickstart: ____________________________ System: ____________________________ © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 15 Step 13 Determine and write down the module types installed on the Fabric Interconnect. Fabric Interconnect A: Module 1: ____________________________ Module 2: ____________________________ Fabric Interconnect B: Step 14 Module 1: ____________________________ Module 2: ____________________________ Determine and write down the number and type of FEXs attached to the Fabric Interconnect. Fabric Interconnect FEX number FEX model A A B B Step 15 Determine and write down the cluster status. ________________________ Step 16 Which FI is the Primary? ________________________ Step 17 Which chassis&servers is/are used for HA ________________________ Step 18 Determine and write down the license usage on the Fabric Interconnect. Fabric Interconnect Number of licenses installed Number of licenses used A B Activity Verification You have completed this task when you attain this result: n 16 Requested info is written down in the Student Notes section. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-2: Cisco UCS Management and Service Profile Deployment Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot service profiles. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Successfully associate the service profile created from the service profile template Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnect n One Cisco UCS Chassis n Eight Cisco UCS B-Series servers © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 17 Task 1: Lab setup In this task, you will create a (nonworking) service profile to prepare for Troubleshooting Activity Procedure Complete these steps: 18 Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-2” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Step 8 Select “Change Service Profile Association” in the Actions panel © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 19 Step 9 Note Step 10 20 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Note the Status of your Service Profile is “Config Error”. This is the intended result! (keep in mind, this is a troubleshooting class ;) ) Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 2: Trouble Ticket The customer has deployed a new Cisco UCS and is in the process of deploying new Linux hosts. The customer would like to use a service profile template to create their service profile. They have already configured a service profile template. When they create a service profile template from the service profile, they receive an error and they do not know how to solve the problems. The customer also has problems with accessing the KVM console. It works only when accessed from the physical server but KVM manager and access from the Service Profile do not work as expected. The customer also wants to fix the problems that they had with previous service profiles in the testing deployments. When they applied some changes to the service profile, the system would reboot the servers without warning, leading to downtime. They want to fix this issue. Activity Procedure Complete these steps: Step 1 Read the trouble ticket. Document what the problems are: Problems description: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ Step 2 Start troubleshooting. When you are done you are supposed to see a Linux login prompt. Document your findings and actions. Caution DO NOT change the service profile template or any global setting. If in doubt ask your instructor. Findings and Actions: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ Activity Verification You have completed this task when you attain these results: n Service profile does not have any errors and the association of your service profile to the blade and boot is successful. n Your server does not automatically reboot when you make some changes on the service profile templates. n You can access your blade KVM console through KVM manager or service profile. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 21 Task 3: Clean Up In this task, you will delete your fixed service profile to prepare for the next lab. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 3 In Cisco UCS Manager, select the Server tab. Step 4 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 5 Expand the Sub-Organizations and select YOUR POD Step 6 Right-click YOUR service profile and select delete Note 22 Keep in mind the de-association process takes some time on the physical server. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-3: Troubleshoot Cisco UCS B-Series Server Boot from SAN Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot a bootup from the SAN. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Boot the Linux server from the SAN Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnects n One Cisco UCS Chassis n Eight UCS B-Series servers n Two MDS switches n Storage connected to the MDS switches. Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) Pod Blade PODX Server 1/X Fibre Channel Switches Fabric Telnet IP Username Password A 172.16.1.31 student 1234QWer B 172.16.1.32 student 1234QWer Cisco UCS Fabric Interconnect Fabric IP Username Password A 172.16.1.101 admin 1234QWer B 172.16.1.102 admin 1234QWer Cluster 172.16.1.200 admin 1234QWer © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 23 Command List The table describes the commands used in this activity. 24 Command Description connect nx-os Connects to Cisco NX-OS CLI fcping Performs Fibre Channel Ping to connected neighbor feature npiv Enables feature NPIV show features Displays enabled features on MDS switch show flogi database Displays the FLOGI table show npv flogi-table Shows FLOGI table on the Cisco UCS NX-OS show vsan Displays the VSANs show zone active Displays active zones show zoneset active Displays active zonesets Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 25 26 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-3” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK Note If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Step 10 Note the Status of your Service Profile is “Config”. Step 11 Wait for the Status to be “OK” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 27 Task 2: Trouble Ticket The customer is having a problem with booting the Server from the SAN. The storage engineer has already configured the zoning and LUN masking and they are pretty sure everything is correct on their side. They have given you read-only access to their fibre switches to verify. On the boot LUN, the customer has already installed the operating system, which was achieved with LUN copy functionality provided by the storage array. They want to fix the issue and they need your help. You received this screenshot: Activity Procedure Complete these steps: Step 1 Read the trouble ticket. Document what the problems are: Problems description: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ Step 2 Start troubleshooting. When you are done you are supposed to see a Linux login prompt. Document your findings and actions. Caution DO NOT change the service profile template or any global setting. If in doubt ask your instructor. Findings and Actions: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ Note Zoning on the MDS switches and LUN masking on the storage array is already preconfigured. You do not need to configure anything there. The zone used for this class is named DCUCT-LNX and there are additional zones configured for other courses. Activity Verification You have completed this task when you attain these results: 28 n You successfully booted the ESXi server. n You see on both MDS switches your service profile HBA. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 3: Clean Up In this task, you will delete your fixed service profile to prepare for the next lab. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note Keep in mind the de-association process takes some time on the physical server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 29 Lab 1-4: Troubleshoot LAN Connectivity: Part 1 Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot network connectivity. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Ping or access the management interface of the host Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnects n One Cisco UCS 5108 Chassis n Eight Cisco UCS B-Series servers Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) POD Blade PODX Server 1/X Core Switch telnet IPs 172.16.1.254 172.17.12.254 172.17.P2.254 30 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 31 32 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-4” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK Note If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Step 10 Note the Status of your Service Profile is “Config”. Step 11 Wait for the Status to be “OK” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 33 Task 2: Trouble Ticket The customer is having problems with the network connectivity of the newly configured Linux servers. The interface of the server is not reachable. The customer also noticed that PCI cards are not presented to the server in the correct order. The Application vendor requires the FC HBAs in the first two slots. Activity Procedure Complete these steps: Step 1 Open KVM to the Linux server and log in with “student” and “1234QWer” Step 2 Determine the Ethernet interface number of your Linux server (it should be 0 or 1, the example shows eth0) student@DCUCT:~$ sudo ifconfig –a [sudo] password for student: 1234QWer … interface eth0 … Step 3 Bring up the Ethernet interface student@DCUCT:~$ sudo ifconfig eth# up Step 4 Assign IP address 172.17.12.P / 24 (P is your Pod#) student@DCUCT:~$ sudo ifconfig eth# 172.17.12.P/24 Step 5 Check the Ethernet interface configuration and status student@DCUCT:~$ sudo ifconfig eth# eth# Link enacp:Ethernet HWaddr: 00:25:b5:00:00:0P inet addr:172.17.12.9 Bcast:172.17.12.255 Mask:255.255.255.0 inet6 addr: fe80::225:b5ff:fe00:9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 … Step 6 Try pinging the default gateway (172.17.12.254) or other Pods (172.17.12.Q) student@DCUCT:~$ ping 172.17.12.254 ... Destination Host Unreachable ... student@DCUCT:~$ ping 172.17.12.Q ... Destination Host Unreachable ... Step 7 Start troubleshooting. Activity Verification You have completed this task when Network connectivity works and the PCI cards are presented in the correct order. 34 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 3: Clean Up In this task, you will delete your fixed service profile to prepare for the next lab. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note Keep in mind the de-association process takes some time on the physical server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 35 Lab 1-5: Troubleshoot LAN Connectivity: Part 2 Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot network connectivity. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Ping or access the management interface of the ESXi host Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnects n One Cisco UCS 5108 Chassis n Eight Cisco UCS B-Series servers Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) POD Blade PODX Server 1/X Core Switch telnet IPs 172.16.1.254 172.17.12.254 172.17.P2.254 36 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 37 38 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-5” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK Note If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Step 10 Note the Status of your Service Profile is “Config”. Step 11 Wait for the Status to be “OK” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 39 Task 2: Trouble Ticket The customer is having problems with the network connectivity of the newly configured Servers. They are supposed to be in VLAN LP1 (L is your Lab ID (see page 5), P is your Pod#) using IP 172.17.P2.P/24(P is your Pod#) The customers networking team has verified VLANs and SVIs on their core switch(es) and they are quite sure everything is correct. They have given you read-only access to their core switch to verify. Activity Procedure Complete these steps: Step 1 Open KVM to the Linux server and log in with “student” and “1234QWer” Step 2 Determine the Ethernet interface number of your Linux server (it should be 0 or 1, the example shows eth0) student@DCUCT:~$ sudo ifconfig –a [sudo] password for student: 1234QWer … interface eth0 … Step 3 Bring up the Ethernet interface student@DCUCT:~$ sudo ifconfig eth# up Step 4 Assign IP address 172.17.P2.P / 24 (P is your Pod#) student@DCUCT:~$ sudo ifconfig eth# 172.17.P2.P/24 Step 5 Check the Ethernet interface configuration and status student@DCUCT:~$ sudo ifconfig eth# eth# Link enacp:Ethernet HWaddr: 00:25:b5:00:00:0P inet addr:172.17.P2.P Bcast:172.17.P2.255 Mask:255.255.255.0 inet6 addr: fe80::225:b5ff:fe00:9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 … Step 6 Try pinging the default gateway (172.17.P2.254) (P is your Pod#) student@DCUCT:~$ ping 172.17.P2.254 ... Destination Host Unreachable ... Step 7 Start troubleshooting. Activity Verification You have completed this task when you are able to ping from the server shell to the default gateway 172.17.P2.254 (where P is your pod number) or ping the management IP from your student PC. 40 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 3: Clean Up In this task, you will delete your fixed service profile to prepare for the next lab. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note Keep in mind the de-association process takes some time on the physical server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 41 Lab 1-6: Troubleshoot Failover Connectivity: Part 1 Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot network connectivity in a failover scenario. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Ping or access the management interface of the ESXi host Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnects n One Cisco UCS 5108 Chassis n Eight Cisco UCS B-Series servers Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) POD Blade PODX Server 1/X Core Switch telnet IPs 172.16.1.254 172.17.12.254 172.17.P2.254 42 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 43 44 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-6” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK Note If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Step 10 Note the Status of your Service Profile is “Config”. Step 11 Wait for the Status to be “OK” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 45 Task 2: Trouble Ticket Now you are assigned a case where you need to resolve the LAN connectivity problems that the customer wass experiencing with their UCS deployment. The customer had issues with accessing the hosts from the core LAN in the event of failover. They are also concerned that a mismatch of native VLANs may exist between the UCS system and the network infrastructure and want you to check the native VLAN on the UCS uplinks. The UCS system is already in production and you cannot disable the uplinks since other servers would be affected. (The instructor can decide to disable the uplinks on Fabric Interconnect A, do NOT disable them yourselves) Activity Procedure Complete these steps: Step 1 Open KVM to the Linux server and log in with “student” and “1234QWer” Step 2 Determine the Ethernet interface number of your Linux server (it should be 0 or 1, the example shows eth0) student@DCUCT:~$ sudo ifconfig –a [sudo] password for student: 1234QWer … interface eth0 … Step 3 Bring up the Ethernet interface student@DCUCT:~$ sudo ifconfig eth# up Step 4 Assign IP address 172.17.12.P / 24 (P is your Pod#) student@DCUCT:~$ sudo ifconfig eth# 172.17.12.P/24 Step 5 Check the Ethernet interface configuration and status student@DCUCT:~$ sudo ifconfig eth# eth# Link enacp:Ethernet HWaddr: 00:25:b5:00:00:0P inet addr:172.17.12.9 Bcast:172.17.12.255 Mask:255.255.255.0 inet6 addr: fe80::225:b5ff:fe00:9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 … Step 6 Start troubleshooting. Activity Verification You have completed this task when you are able to ping from the Linux shell to the default gateway 172.17.12.254 with all Uplinks on FI A failed. Note 46 It is up to the instructor if the uplinks are disabled during this lab. DO NOT disable them yourself! Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 3: Clean Up In this task, you will delete your fixed service profile to prepare for the next lab. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note Keep in mind the de-association process takes some time on the physical server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 47 Lab 1-7: Troubleshoot Failover Connectivity: Part 2 Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot network connectivity. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue n Ping or access the management interface of the ESXi host Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n Two Cisco UCS Fabric Interconnects n One Cisco UCS 5108 Chassis n Eight Cisco UCS B-Series servers Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) 48 POD Blade PODX Server 1/X Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 49 50 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab1-7” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED Blade Server and click OK Note If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Step 10 Note the Status of your Service Profile is “Config”. Step 11 Wait for the Status to be “OK” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 51 Task 2: Trouble Ticket The Customer has deployed a number of servers with hardware failover. During a reboot of the Fabric Interconnect during a software update failover occurred and the servers lost network connectivity. Server admins report the interface never went down but there was no connectivity. The UCS system is already in production and you cannot disable the uplinks since other servers would be affected. (The instructor can decide to disable the uplinks on Fabric Interconnect A, do NOT disable them yourselves) Activity Procedure Complete these steps: Step 1 Open KVM to the Linux server and log in with “student” and “1234QWer” Step 2 Determine the Ethernet interface number of your Linux server (it should be 0 or 1, the example shows eth0) student@DCUCT:~$ sudo ifconfig –a [sudo] password for student: 1234QWer … interface eth0 … Step 3 Bring up the Ethernet interface student@DCUCT:~$ sudo ifconfig eth# up Step 4 Assign IP address 172.17.12.P / 24 (P is your Pod#) student@DCUCT:~$ sudo ifconfig eth# 172.17.12.P/24 Step 5 Check the Ethernet interface configuration and status student@DCUCT:~$ sudo ifconfig eth# eth# Link enacp:Ethernet HWaddr: 00:25:b5:00:00:0P inet addr:172.17.12.9 Bcast:172.17.12.255 Mask:255.255.255.0 inet6 addr: fe80::225:b5ff:fe00:9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 … Step 6 Start troubleshooting. Activity Verification You have completed this task when you are able to ping from the Linux shell to the default gateway 172.17.12.254 with all Uplinks on FI A disabled. Note 52 It is up to the instructor if the uplinks are disabled during this lab. DO NOT disable them yourself! Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 3: Clean Up In this task, you will delete your fixed service profile. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note Keep in mind the de-association process takes some time on the physical server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 53 Lab 3-1: Troubleshoot Cisco UCS C-Series Complete this lab activity to practice what you learned in the related module. Activity Objective In this activity, you will troubleshoot C-Series Servers. After completing this activity, you will be able to meet these objectives: n Perform trouble analysis and identify the cause of the problem n Resolve the issue Required Resources These are the resources and equipment for all PODs that are required to complete this activity: n One Cisco UCS C-Series servers per Pod n Two Cisco UCS Fabric Interconnects n One Cisco UCS Chassis Job Aids These job aids are available to help you complete the lab activity. Server per Pod Assignment (where X is your pod number) 54 POD Rack Server PODX Server X Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 1: Lab setup In this task, you will create a (nonworking) service profile to prepare for Troubleshooting Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Click “Create Service Profile From Template” on the Actions panel. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 55 56 Step 5 Use naming Prefix “Pod#-“and create 1 Service Profile from Template “Lab3-1” Step 6 Verify the Service Profile has been created INSIDE your Pod organization Step 7 Select your Service Profile and click “Unbind from the Template” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 8 Select “Change Service Profile Association” in the Actions panel Step 9 Select “Select existing Server”, select YOUR ASSIGNED RACK! Server and click OK Note Step 10 If your server does NOT show up, select the “All Servers” Radio Button, select your server and click OK. Then make sure no other service profile is associated with your server – also keep in mind de-association takes some time! Note the Status of your Service Profile is “Config Error”. This is the intended result! (keep in mind, this is a troubleshooting class ;) ) © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 57 Task 2: Trouble Ticket The customer has previously owned Cisco UCS C-Series servers and used them as stand-alone rack servers. The customer has decided to integrate these servers into UCS manager. A server admin has recreated the previous server setup but the server fails to boot because the service profile has an error. Also the rack servers seem to be numbered in a strange way. The cabling is from port X and 1X from the FEX to the Server X but UCS manager does not agree. The customer unplugged physical server 1 and another server was affected. The Customer demands some documentation and possibly some meaningful numbering scheme. The customer has this cabling documentation and they have checked it many times. Physical Server # FEX A mgmt. FEX A Data FEX B mgmt FEX B Data 1 Port 1 Port 11 Port 1 Port 11 2 Port 2 Port 12 Port 2 Port 12 3 Port 3 Port 13 Port 3 Port 13 4 Port 4 Port 14 Port 4 Port 14 5 Port 5 Port 15 Port 5 Port 15 6 Port 6 Port 16 Port 6 Port 16 7 Port 7 Port 17 Port 7 Port 17 8 Port 8 Port 18 Port 8 Port 18 Activity Procedure Complete these steps: Step 1 Start troubleshooting and make the server boot. Step 2 For the customers documentation fill this table Server Number in UCS Physical Server Number 1 2 3 4 5 6 7 8 Step 3 58 (Optional Task) To make life easier for the customer you have decided to renumber your server to 1P (where P is both the physical server number and your Pod#) Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Activity Verification You have completed this task when you attain these results: n The server boots successfully n You filled the table. n (Optional) You assigned 1P (P is your Pod#) to your Server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 59 Task 3: Clean Up In this task, you will delete your fixed service profile. Activity Procedure Complete these steps: Caution Make sure to ALWAYS use YOUR Pod organization! Caution NEVER change service profile TEMPLATES or ANY setting outside your Pod Organization! Step 1 In Cisco UCS Manager, select the Server tab. Step 2 From the Filter drop-down menu, choose Service Profiles to filter other categories. Step 3 Expand the Sub-Organizations and select YOUR POD Step 4 Right-click YOUR service profile and select delete Note 60 Keep in mind the de-association process takes some time on the physical server. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Answer Key The steps needed for requested activities that are described in this guide appear here. Note Depending on your lab configuration, screenshots and printouts presented here might be different from the actual screenshots and printouts that you have in your lab. Lab 1-1 Answer Key: Cisco UCS Network Baseline Documentation Task 1: Verify Cisco UCS Equipment Using Cisco UCSM GUI © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 61 62 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Task 2: Verify Cisco UCS B-Series Equipment © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 63 64 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 65 66 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 67 Task 3: Verify UCS C-Series Equipment 68 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 69 70 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 71 Task 4: Examine LAN and SAN Network Topology 72 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. FastLane-UCS-A# connect nxos Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-A(nxos)# FastLane-UCS-A(nxos)# Capability Codes: R S V s - sho cdp neighbors Router, T - Trans-Bridge, B - Source-Route-Bridge Switch, H - Host, I - IGMP, r - Repeater, VoIP-Phone, D - Remotely-Managed-Device, Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability F110-UCS-Backbone mgmt0 F110-UCS-Backbone Eth1/11 F110-UCS-Backbone Eth1/12 FastLane-UCS-A(nxos)# 170 170 164 R S I R S I R S I Platform WS-C4900M WS-C4900M WS-C4900M Port ID Gig2/1 Ten1/1 Ten1/2 FastLane-UCS-A(nxos)# exit FastLane-UCS-A# connect nxos b Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 73 Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-B(nxos)# FastLane-UCS-B(nxos)# Capability Codes: R S V s - sho cdp neighbors Router, T - Trans-Bridge, B - Source-Route-Bridge Switch, H - Host, I - IGMP, r - Repeater, VoIP-Phone, D - Remotely-Managed-Device, Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability F110-UCS-Backbone mgmt0 F110-UCS-Backbone Eth1/11 FastLane-UCS-B(nxos)# 174 174 R S I R S I Platform WS-C4900M WS-C4900M Port ID Gig2/2 Ten1/3 FastLane-UCS-A(nxos)# sho ver Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software are covered under the GNU Public License. A copy of the license is available at http://www.gnu.org/licenses/gpl.html. Software BIOS: version 1.5.0 loader: version N/A kickstart: version 5.0(3)N2(2.11a) system: version 5.0(3)N2(2.11a) power-seq: Module 1: version v1.2 BIOS compile time: 11/30/10 kickstart image file is: bootflash:/installables/switch/ucs-6100-k9kickstart. 5.0.3.N2.2.11a.bin kickstart compile time: 11/15/2012 2:00:00 [11/15/2012 10:10:53] system image file is: bootflash:/installables/switch/ucs-6100-k9system.5.0 .3.N2.2.11a.bin system compile time: 11/15/2012 2:00:00 [11/15/2012 12:22:31] Hardware cisco UCS 6100 Series Fabric Interconnect ("20x10GE/Supervisor") Intel(R) Celeron(R) M CPU with 3633996 kB of memory. Processor Board ID FOC15321R9Z Device name: FastLane-UCS-A bootflash: 15728640 kB Kernel uptime is 6 day(s), 6 hour(s), 5 minute(s), 32 second(s) Last reset at 525719 usecs after Wed Feb 6 12:02:56 2013 Reason: Reset Requested by CLI command reload System version: 5.0(3)N2(2.11a) Service: plugin Core Plugin, Ethernet Plugin, Fc Plugin, Virtualization Plugin FastLane-UCS-A(nxos)# 74 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. FastLane-UCS-B(nxos)# sho ver Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Some parts of this software are covered under the GNU Public License. A copy of the license is available at http://www.gnu.org/licenses/gpl.html. Software BIOS: version 1.5.0 loader: version N/A kickstart: version 5.0(3)N2(2.11a) system: version 5.0(3)N2(2.11a) power-seq: Module 1: version v1.2 BIOS compile time: 11/30/10 kickstart image file is: bootflash:/installables/switch/ucs-6100-k9kickstart. 5.0.3.N2.2.11a.bin kickstart compile time: 11/15/2012 2:00:00 [11/15/2012 10:10:53] system image file is: bootflash:/installables/switch/ucs-6100-k9system.5.0 .3.N2.2.11a.bin system compile time: 11/15/2012 2:00:00 [11/15/2012 12:22:31] Hardware cisco UCS 6100 Series Fabric Interconnect ("20x10GE/Supervisor") Intel(R) Celeron(R) M CPU with 3633996 kB of memory. Processor Board ID FOC15315V9P Device name: FastLane-UCS-B bootflash: 15728640 kB Kernel uptime is 6 day(s), 6 hour(s), 4 minute(s), 9 second(s) Last reset at 425224 usecs after Wed Feb 6 12:02:41 2013 Reason: Reset Requested by CLI command reload System version: 5.0(3)N2(2.11a) Service: plugin Core Plugin, Ethernet Plugin, Fc Plugin, Virtualization Plugin FastLane-UCS-B(nxos)# Display installed modules in the Fabric Interconnect. FastLane-UCS-A(nxos)# sho module Mod Ports Module-Type Model Status --- ----- -------------------------------- ---------------------- ----------1 20 20x10GE/Supervisor N10-S6100-SUP active * 2 6 6x1/2/4/8G FC Module N10-E0060 ok Mod Sw Hw --- -------------- -----1 5.0(3)N2(2.11a 1.2 2 5.0(3)N2(2.11a 1.0 20:46:54:7f:ee:17:87:40 World-Wide-Name(s) (WWN) -------------------------------------------------20:41:54:7f:ee:17:87:40 to Mod MAC-Address(es) --- -------------------------------------1 547f.ee17.8748 to 547f.ee17.876f 2 547f.ee17.8770 to 547f.ee17.8777 FastLane-UCS-A(nxos)# Serial-Num ---------FOC15321R9Z FOC153343HD FastLane-UCS-B(nxos)# sho module © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 75 Mod Ports --- ----1 20 2 6 Module-Type Model Status -------------------------------- ---------------------- ----------20x10GE/Supervisor 6x1/2/4/8G FC Module Mod Sw Hw --- -------------- -----1 5.0(3)N2(2.11a 1.2 2 5.0(3)N2(2.11a 1.0 20:46:54:7f:ee:17:87:80 N10-S6100-SUP N10-E0060 active * ok World-Wide-Name(s) (WWN) -------------------------------------------------20:41:54:7f:ee:17:87:80 to Mod MAC-Address(es) --- -------------------------------------1 547f.ee17.8788 to 547f.ee17.87af 2 547f.ee17.87b0 to 547f.ee17.87b7 FastLane-UCS-B(nxos)# Serial-Num ---------FOC15315V9P FOC153343DG Display FEX details. FastLane-UCS-A# sho fex FEX: ID Fabric ID Overall Status ---------- --------- -------------2 A Power Problem 3 B Power Problem FastLane-UCS-A# FastLane-UCS-A# sho fex detail FEX: ID: 2 Fabric ID: A User Label: Overall Status: Power Problem Oper qualifier: Fan Power,Psu Power,Fan Inoperable,Psu Inoperable Thermal Status: N/A Product Name: Cisco Nexus 2232PP PID: N2K-C2232PP-10GE VID: V01 Vendor: Cisco Systems Serial (SN): SSI160701EV HW Revision: 0 Controller Subject: Current Task 1: Current Task 2: ID: 3 Fabric ID: B User Label: Overall Status: Power Problem Oper qualifier: Fan Power,Psu Power,Fan Inoperable,Psu Inoperable Thermal Status: N/A Product Name: Cisco Nexus 2232PP PID: N2K-C2232PP-10GE VID: V01 Vendor: Cisco Systems Serial (SN): SSI16270DK2 HW Revision: 0 Controller Subject: Current Task 1: Current Task 2: FastLane-UCS-A# FastLane-UCS-A# connect nxos Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. 76 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-A(nxos)# sho fex FEX FEX FEX FEX Number Description State Model Serial -----------------------------------------------------------------------1 FEX0001 Online N20-C6508 QCI1525A880 2 FEX0002 Online N2K-C2232PP-10GE FOC1634EQZM FastLane-UCS-A(nxos)# sho fex detail FEX: 1 Description: FEX0001 state: Online FEX version: 5.0(3)N2(2.11a) [Switch version: 5.0(3)N2(2.11a)] FEX Interim version: 5.0(3)N2(2.11a) Switch Interim version: 5.0(3)N2(2.11a) Chassis Model: N20-C6508, Chassis Serial: FOX1519G0EC Extender Model: N20-I6584, Extender Serial: QCI1525A880 Part No: 73-11623-07 Card Id: 67, Mac Addr: 30:e4:db:90:94:5c, Num Macs: 10 Module Sw Gen: 12594 [Switch Sw Gen: 21] post level: complete pinning-mode: static Max-links: 1 Fabric port for control traffic: Eth1/1 Fabric interface state: Eth1/1 - Interface Up. State: Active Fex Port State Fabric Port Eth1/1/1 Down Eth1/1 Eth1/1/2 Down Eth1/1 Eth1/1/3 Down None Eth1/1/4 Down Eth1/1 Eth1/1/5 Down Eth1/1 Eth1/1/6 Down None Eth1/1/7 Down None Eth1/1/8 Down None Eth1/1/9 Up Eth1/1 Logs: 02/06/2013 12:27:44.917213: Module register received 02/06/2013 12:27:44.919047: Registration response sent 02/06/2013 12:27:45.159486: Module Online Sequence 02/06/2013 12:27:49.13594: Module Online FEX: 2 Description: FEX0002 state: Online FEX version: 5.0(3)N2(2.11a) [Switch version: 5.0(3)N2(2.11a)] FEX Interim version: 5.0(3)N2(2.11a) Switch Interim version: 5.0(3)N2(2.11a) Extender Model: N2K-C2232PP-10GE, Extender Serial: FOC1634EQZM Part No: 73-12533-05 Card Id: 82, Mac Addr: 30:f7:0d:70:d6:82, Num Macs: 64 Module Sw Gen: 12594 [Switch Sw Gen: 21] post level: complete pinning-mode: static Max-links: 1 Fabric port for control traffic: Eth1/5 Fabric interface state: Eth1/5 - Interface Up. State: Active Eth1/6 - Interface Up. State: Active Fex Port State Fabric Port Eth2/1/1 Down Eth1/5 Eth2/1/2 Up Eth1/6 Eth2/1/3 Up Eth1/5 Eth2/1/4 Up Eth1/6 Eth2/1/5 Down None Eth2/1/6 Down None Eth2/1/7 Down None Eth2/1/8 Down None © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 77 Eth2/1/9 Eth2/1/10 Eth2/1/11 Eth2/1/12 Eth2/1/13 Eth2/1/14 Eth2/1/15 Eth2/1/16 Eth2/1/17 Eth2/1/18 Eth2/1/19 Eth2/1/20 Eth2/1/21 Eth2/1/22 Eth2/1/23 Eth2/1/24 Eth2/1/25 Eth2/1/26 Eth2/1/27 Eth2/1/28 Eth2/1/29 Eth2/1/30 Eth2/1/31 Eth2/1/32 Logs: 02/06/2013 02/06/2013 02/06/2013 02/06/2013 Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down Down 15:32:36.109957: 15:32:36.111457: 15:32:36.298590: 15:32:38.411258: None None Eth1/5 Eth1/6 Eth1/5 Eth1/6 None None None None None None None None None None None None None None None None None None Module register received Registration response sent Module Online Sequence Module Online FastLane-UCS-A(nxos)# FastLane-UCS-A(nxos)# exit FastLane-UCS-A# connect nxos b Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-B(nxos)# sho fex FEX FEX FEX FEX Number Description State Model Serial -----------------------------------------------------------------------1 FEX0001 Online N20-C6508 QCI1528A36U 3 FEX0003 Online N2K-C2232PP-10GE FOC1634ER2P FastLane-UCS-B(nxos)# sho fex detail FEX: 1 Description: FEX0001 state: Online FEX version: 5.0(3)N2(2.11a) [Switch version: 5.0(3)N2(2.11a)] FEX Interim version: 5.0(3)N2(2.11a) Switch Interim version: 5.0(3)N2(2.11a) Chassis Model: N20-C6508, Chassis Serial: FOX1519G0EC Extender Model: N20-I6584, Extender Serial: QCI1528A36U Part No: 73-11623-07 Card Id: 67, Mac Addr: 44:d3:ca:2a:56:54, Num Macs: 10 Module Sw Gen: 12594 [Switch Sw Gen: 21] post level: complete pinning-mode: static Max-links: 1 Fabric port for control traffic: Eth1/1 Fabric interface state: Eth1/1 - Interface Up. State: Active Fex Port State Fabric Port 78 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Eth1/1/1 Eth1/1/2 Eth1/1/3 Eth1/1/4 Eth1/1/5 Eth1/1/6 Eth1/1/7 Eth1/1/8 Eth1/1/9 Logs: 02/06/2013 02/06/2013 02/06/2013 02/06/2013 Down Down Down Down Down Down Down Down Up 12:28:01.488113: 12:28:01.489950: 12:28:01.726304: 12:28:05.728227: Eth1/1 Eth1/1 None Eth1/1 Eth1/1 None None None Eth1/1 Module register received Registration response sent Module Online Sequence Module Online FEX: 3 Description: FEX0003 state: Online FEX version: 5.0(3)N2(2.11a) [Switch version: 5.0(3)N2(2.11a)] FEX Interim version: 5.0(3)N2(2.11a) Switch Interim version: 5.0(3)N2(2.11a) Extender Model: N2K-C2232PP-10GE, Extender Serial: FOC1634ER2P Part No: 73-12533-05 Card Id: 82, Mac Addr: 30:f7:0d:70:d5:c2, Num Macs: 64 Module Sw Gen: 12594 [Switch Sw Gen: 21] post level: complete pinning-mode: static Max-links: 1 Fabric port for control traffic: Eth1/5 Fabric interface state: Eth1/5 - Interface Up. State: Active Eth1/6 - Interface Up. State: Active Fex Port State Fabric Port Eth3/1/1 Up Eth1/5 Eth3/1/2 Down Eth1/6 Eth3/1/3 Up Eth1/5 Eth3/1/4 Up Eth1/6 Eth3/1/5 Down None Eth3/1/6 Down None Eth3/1/7 Down None Eth3/1/8 Down None Eth3/1/9 Down None Eth3/1/10 Down None Eth3/1/11 Down Eth1/5 Eth3/1/12 Down Eth1/6 Eth3/1/13 Down Eth1/5 Eth3/1/14 Down Eth1/6 Eth3/1/15 Down None Eth3/1/16 Down None Eth3/1/17 Down None Eth3/1/18 Down None Eth3/1/19 Down None Eth3/1/20 Down None Eth3/1/21 Down None Eth3/1/22 Down None Eth3/1/23 Down None Eth3/1/24 Down None Eth3/1/25 Down None Eth3/1/26 Down None Eth3/1/27 Down None Eth3/1/28 Down None Eth3/1/29 Down None Eth3/1/30 Down None Eth3/1/31 Down None Eth3/1/32 Down None Logs: 02/06/2013 15:32:44.934807: Module register received 02/06/2013 15:32:44.936351: Registration response sent 02/06/2013 15:32:45.79096: Module Online Sequence 02/06/2013 15:32:47.301511: Module Online © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 79 FastLane-UCS-B(nxos)# Display interface brief. FastLane-UCS-A# connect nxos Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-A(nxos)# sho int brief -----------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper Port Mode Trunk Mode Speed Channel Mode (Gbps) -----------------------------------------------------------------------------fc2/1 11 NP off up swl NP 4 -fc2/2 11 NP off down swl --fc2/3 11 NP off up swl NP 4 -fc2/4 11 NP off up swl NP 4 -fc2/5 11 NP off sfpAbsent ---fc2/6 1 NP off sfpAbsent --------------------------------------------------------------------------------Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -----------------------------------------------------------------------------Eth1/1 1 eth fabric up none 10G(D) -Eth1/2 4044 eth trunk up none 10G(D) -Eth1/3 4044 eth trunk up none 10G(D) -Eth1/4 4044 eth trunk up none 10G(D) -Eth1/5 1 eth fabric up none 10G(D) -Eth1/6 1 eth fabric up none 10G(D) -Eth1/7 1 eth access down Administratively down 10G(D) -Eth1/8 1 eth access down Administratively down 10G(D) -Eth1/9 1 eth access down SFP not inserted 10G(D) -Eth1/10 1 eth access down SFP not inserted 10G(D) -Eth1/11 1 eth trunk up none 10G(D) -Eth1/12 1 eth trunk up none 10G(D) -Eth1/13 1 eth trunk down SFP not inserted 10G(D) -Eth1/14 1 eth trunk down SFP not inserted 10G(D) -Eth1/15 1 eth access down SFP not inserted 10G(D) -Eth1/16 1 eth access down SFP not inserted 10G(D) -Eth1/17 1 eth access down SFP not inserted 10G(D) -Eth1/18 1 eth access down SFP not inserted 10G(D) -Eth1/19 1 eth access down SFP not inserted 10G(D) -Eth1/20 1 eth access down SFP not inserted 10G(D) ------------------------------------------------------------------------------Port VRF Status IP Address Speed MTU -----------------------------------------------------------------------------mgmt0 -down 172.16.1.101 1000 1500 -----------------------------------------------------------------------------Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -----------------------------------------------------------------------------Eth1/1/1 1 eth vntag down Link not connected 10G(D) -80 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Eth1/1/2 1 eth Eth1/1/3 1 eth Eth1/1/4 1 eth Eth1/1/5 1 eth Eth1/1/6 1 eth Eth1/1/7 1 eth Eth1/1/8 1 eth Eth1/1/9 4044 eth Eth2/1/1 4044 eth Eth2/1/2 1 eth Eth2/1/3 1 eth Eth2/1/4 1 eth Eth2/1/5 4044 eth Eth2/1/6 4044 eth Eth2/1/7 4044 eth Eth2/1/8 4044 eth Eth2/1/9 4044 eth Eth2/1/10 4044 eth Eth2/1/11 1 eth Eth2/1/12 1 eth Eth2/1/13 1 eth Eth2/1/14 1 eth Eth2/1/15 4044 eth Eth2/1/16 4044 eth Eth2/1/17 4044 eth Eth2/1/18 4044 eth Eth2/1/19 4044 eth Eth2/1/20 4044 eth Eth2/1/21 4044 eth Eth2/1/22 4044 eth Eth2/1/23 4044 eth Eth2/1/24 4044 eth Eth2/1/25 4044 eth Eth2/1/26 4044 eth Eth2/1/27 4044 eth Eth2/1/28 4044 eth Eth2/1/29 4044 eth Eth2/1/30 4044 eth Eth2/1/31 4044 eth Eth2/1/32 4044 eth FastLane-UCS-A(nxos)# vntag access vntag vntag access access access trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk vntag vntag vntag vntag trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk trunk down down down down down down down up down up up up down down down down down down down down down down down down down down down down down down down down down down down down down down down down Link not connected Administratively down Link not connected Link not connected Administratively down Administratively down Administratively down none Link not connected none none none SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted Link not connected Link not connected Link not connected Link not connected SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 1000(D) 1000(D) 1000(D) 1000(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) ----------------------------------------- FastLane-UCS-B(nxos)# sho int brief -----------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper Port Mode Trunk Mode Speed Channel Mode (Gbps) -----------------------------------------------------------------------------fc2/1 12 NP off up swl NP 4 -fc2/2 12 NP off up swl NP 4 -fc2/3 12 NP off up swl NP 4 -fc2/4 12 NP off up swl NP 4 -fc2/5 12 NP off sfpAbsent ---fc2/6 1 NP off sfpAbsent --------------------------------------------------------------------------------Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -----------------------------------------------------------------------------Eth1/1 1 eth fabric up none 10G(D) -Eth1/2 4044 eth trunk up none 10G(D) -Eth1/3 4044 eth trunk up none 10G(D) -Eth1/4 4044 eth trunk up none 10G(D) -Eth1/5 1 eth fabric up none 10G(D) -Eth1/6 1 eth fabric up none 10G(D) -Eth1/7 1 eth access down Administratively down 10G(D) -Eth1/8 1 eth access down Administratively down 10G(D) -© 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 81 Eth1/9 Eth1/10 Eth1/11 Eth1/12 Eth1/13 Eth1/14 Eth1/15 Eth1/16 Eth1/17 Eth1/18 Eth1/19 Eth1/20 1 1 1 1 1 1 1 1 1 1 1 1 eth eth eth eth eth eth eth eth eth eth eth eth access access trunk access trunk trunk access access access access access access down down up down down down down down down down down down SFP not inserted SFP not inserted none Administratively down SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted SFP not inserted 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) 10G(D) ------------- -----------------------------------------------------------------------------Port VRF Status IP Address Speed MTU -----------------------------------------------------------------------------mgmt0 -down 172.16.1.102 1000 1500 -----------------------------------------------------------------------------Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -----------------------------------------------------------------------------Eth1/1/1 1 eth vntag down Link not connected 10G(D) -Eth1/1/2 1 eth vntag down Link not connected 10G(D) -Eth1/1/3 1 eth access down Administratively down 10G(D) -Eth1/1/4 1 eth vntag down Link not connected 10G(D) -Eth1/1/5 1 eth vntag down Link not connected 10G(D) -Eth1/1/6 1 eth access down Administratively down 10G(D) -Eth1/1/7 1 eth access down Administratively down 10G(D) -Eth1/1/8 1 eth access down Administratively down 10G(D) -Eth1/1/9 4044 eth trunk up none 10G(D) -Eth3/1/1 1 eth trunk up none 1000(D) -Eth3/1/2 4044 eth trunk down Link not connected 1000(D) -Eth3/1/3 1 eth trunk up none 1000(D) -Eth3/1/4 1 eth trunk up none 1000(D) -Eth3/1/5 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/6 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/7 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/8 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/9 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/10 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/11 1 eth vntag down Link not connected 10G(D) -Eth3/1/12 1 eth vntag down Link not connected 10G(D) -Eth3/1/13 1 eth vntag down Link not connected 10G(D) -Eth3/1/14 1 eth vntag down Link not connected 10G(D) -Eth3/1/15 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/16 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/17 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/18 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/19 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/20 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/21 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/22 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/23 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/24 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/25 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/26 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/27 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/28 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/29 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/30 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/31 4044 eth trunk down SFP not inserted 10G(D) -Eth3/1/32 4044 eth trunk down SFP not inserted 10G(D) -FastLane-UCS-B(nxos)# 82 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Connect to local-mgmt. FastLane-UCS-A# connect local-mgmt Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-A(local-mgmt)# FastLane-UCS-A(local-mgmt)# sho cluster extended-state Cluster Id: 0xfa38bef0705511e2-0xac58547fee178744 Start time: Wed Feb 6 12:14:33 2013 Last election time: Wed Feb 6 12:23:23 2013 A: UP, PRIMARY B: UP, SUBORDINATE A: memb state UP, lead state PRIMARY, mgmt services state: UP B: memb state UP, lead state SUBORDINATE, mgmt services state: UP heartbeat state PRIMARY_OK INTERNAL NETWORK INTERFACES: eth1, UP eth2, UP HA READY Detailed state of the device selected for HA storage: Chassis 1, serial: FOX1519G0EC, state: active Server 1, serial: QCI1533A7RR, state: active Server 3, serial: QCI1537A6EL, state: active FastLane-UCS-A(local-mgmt)# FastLane-UCS-A(local-mgmt)# exit FastLane-UCS-A# connect local-mgmt b Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2009, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php FastLane-UCS-B(local-mgmt)# FastLane-UCS-B(local-mgmt)# sho cluster extended-state Cluster Id: 0xfa38bef0705511e2-0xac58547fee178744 Start time: Wed Feb 6 12:23:14 2013 Last election time: Wed Feb 6 12:23:22 2013 B: UP, SUBORDINATE A: UP, PRIMARY B: memb state UP, lead state SUBORDINATE, mgmt services state: UP A: memb state UP, lead state PRIMARY, mgmt services state: UP heartbeat state PRIMARY_OK © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 83 INTERNAL NETWORK INTERFACES: eth1, UP eth2, UP HA READY Detailed state of the device selected for HA storage: Chassis 1, serial: FOX1519G0EC, state: active Server 1, serial: QCI1533A7RR, state: active Server 3, serial: QCI1537A6EL, state: active FastLane-UCS-B(local-mgmt)# Display the license. FastLane-UCS-A# sho license usage This command is deprecated. Please use UCSM shell for license operations. For looking into the licenses, please go to the 'license' scope and issue 'show usage <detail>' FastLane-UCS-A# FastLane-UCS-A# scope license FastLane-UCS-A /license # sho usage Feat Name Scope Default Total Quant Used Quant State Peer Count Comparison Grace Used ------------------------------ ----- ------- ----------- ---------- ------------------ ----------------------- ---------ETH_PORT_ACTIVATION_PKG A 8 8 10 License Graceperi od Matching 540000 ETH_PORT_ACTIVATION_PKG B 8 8 9 License Graceperi od Matching 540000 FastLane-UCS-A /license # FastLane-UCS-A /license # sho usage detail License instance: ETH_PORT_ACTIVATION_PKG Scope: A Default: 8 Total Quant: 8 Used Quant: 10 State: License Graceperiod Peer Count Comparison: Matching Grace Used: 540000 License instance: ETH_PORT_ACTIVATION_PKG Scope: B Default: 8 Total Quant: 8 Used Quant: 9 State: License Graceperiod Peer Count Comparison: Matching Grace Used: 540000 FastLane-UCS-A /license # 84 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-2 Answer Key: Cisco UCS Management and Service Profile Deployment When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: Step 1 When the service profile is created, you receive the following error. Step 2 To resolve the issue with the UUID, go to the service profile template, sptPODX, by navigating to Service profile templates > Sub-organizations > PodX, and choose Change UUID. The example is for Pod 8. Note Step 3 If the button is disabled (greyed out) you forgot to unbind your service profile from the template A Change UUID window will pop up. In the UUID Assignment, choose the ValidUUIDs Pool. The example is for POD1. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 85 Step 4 86 The service still has an error. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 5 The service profile cannot derive the WWNN. Step 6 Click “change World Wide Node Name” Step 7 Select the “WWNN-Pool” and click OK Note Step 8 If the pool is not visible you have probably created the service profile in the root organization. Since moving a service profile is not possible you need to delete it, create it in the correct organization and start over. Check the status. The association is successful. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 87 88 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 9 To resolve the issue with automatic reboot of the server when some changes are made in the service profile check the maintenance policy of your service profile. Step 10 Click “Change Maintenance Policy” and select the “user-ack” policy. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 89 90 Step 11 To resolve the issue with accessing the KVM console, you will have to check and change management IP addresses. Check the management IP address assigned to your service profile… Step 12 Click “Change Management IP Address” Step 13 Choose the correct Pool “ext-mgmt” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 91 Lab 1-3 Answer Key: Troubleshoot Cisco UCS B-Series Server Boot from SAN When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: Step 1 Check the storage configuration. Step 2 Log in to both MDS switches and check for your server and the storage system (WWPN starts with 50:…). Note your server is not logged into the fabric! If the server is not even logged in there is no point in checking zoning, storage array settings etc. Lab6-MDS-A# sho flogi database -------------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------fc1/1 11 0x8e0000 20:41:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/2 11 0x8e0200 20:42:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/3 11 0x8e0200 20:43:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/4 11 0x8e0300 20:44:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/10 11 0x8e0700 50:0a:09:83:83:e1:00:86 50:0a:09:80:83:e1:00:86 Total number of flogi = 5. Lab6-MDS-A# 92 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab6-MDS-B# sho flogi database -------------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------fc1/1 12 0x8c0000 20:41:54:7f:ee:17:87:80 20:0c:54:7f:ee:17:87:81 fc1/2 12 0x8c0100 20:42:54:7f:ee:17:87:80 20:0c:54:7f:ee:17:87:81 fc1/3 12 0x8c0200 20:43:54:7f:ee:17:87:80 20:0c:54:7f:ee:17:87:81 fc1/4 12 0x8c0300 20:44:54:7f:ee:17:87:80 20:0c:54:7f:ee:17:87:81 fc1/10 12 0x8c0800 50:0a:09:84:83:e1:00:86 50:0a:09:80:83:e1:00:86 Total number of flogi = 5. Step 3 Check the Boot Order in the service profile Step 4 Click “modify Boot Policy” Step 5 Set it to “NetApp-SAN” and check the storage WWPNs against the FLOGI database you checked earlier. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 93 Step 6 Since “reboot on boot order change” is disabled you need to reset the server. (Note UUOS is NOT needed to change boot policies) The server still does not boot from the SAN. Verify the HBA settings. First, you must fix the problem for the first HBA. The VSAN is set to default, which is wrong. Select SAN, which is in VSAN11. (Don’t forget to save the changes ;) ) 94 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 7 Check the FLOGI table on the MDS1 and verify that you can see your server. The example is for POD1. Lab6-MDS-A# sho flogi database -------------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------fc1/1 11 0x8e0000 20:41:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/1 11 0x8e004b 20:00:00:25:b5:06:08:21 20:00:00:25:b5:06:08:20 fc1/2 11 0x8e0200 20:42:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/3 11 0x8e0200 20:43:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/4 11 0x8e0300 20:44:54:7f:ee:17:87:40 20:0b:54:7f:ee:17:87:41 fc1/10 11 0x8e0700 50:0a:09:83:83:e1:00:86 50:0a:09:80:83:e1:00:86 Total number of flogi = 5. Lab6-MDS-A# Step 8 On the second MDS switch, you still do not see the second HBA. Under the SAN tab, check the second HBA. The VSAN settings are correct. The problem is with SAN pinning. Check the SAN pin group and remove it. (Don’t forget to save the changes ;) ) © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 95 Step 9 Reboot your server. Step 10 Note the FC card BIOS finds the Storage array. Step 11 The server booted successfully. Note 96 If you cannot make the server boot from SAN, disassociate and reassociate the service profile. This forces a run of UUOS and server reconfiguration. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-4 Answer Key: Troubleshoot LAN Connectivity: Part 1 When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: Step 1 Open the service profile network settings. Step 2 Double-click the NIC to determine the settings. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 97 Step 3 Select the “native VLAN” radio Button next to the DATA VLAN. Step 4 Try to ping 172.17.12.254, it should work now. Step 5 Reorder the vNICS by going to your service profile, select the Network tab in the right window and choose Modify vNIC/vHBA Placement. Step 6 In the Modify vNIC/vHBA Placement window, move the eth0 NIC to the last position by using the “Move Down”-Button. Note 98 UUOS will reassign the PCI slots when it runs the next time (like moving the service profile) Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-5 Answer Key: Troubleshoot LAN Connectivity: Part 2 When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: Step 1 Log in to your Linux server with the using the username student and password 1234QWer. Step 2 Open the NIC settings. Step 3 The vlan is obviously wrong and you cannot select the correct one, so it has not been created in UCS. Click “Create VLAN” Step 4 Name your VLAN “Pod#-Data” (# is your Pod# !!), use VLAN identifier LP1 (L=Lab ID (refer to page 6 or ask your instructor), P= your Pod#). Also make sure “Common/Global” is selected. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 99 100 Step 5 Select your newly created VLAN, do NOT forget to unselect the “DATA” VLAN and make sure “native” is selected. Step 6 Click OK and “Save Changes” and retry the ping. It still does NOT work. Step 7 Check the interface state in UCSM by going to VIF Path for your service profile. Step 8 The pin group is configured to the uplink ports which are not working. Create a new PIN group for a working Uplink interface e1/11. Name your Pin Group “Pod#PinGroup” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 9 Don’t forget to change the Pin Group in your NIC settings and press OK and “save Changes” to activate. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 101 102 Step 10 The status of the interface on the host should become active. Check the VIF status again. Step 11 Next, try to ping the IP address 172.17.P2.254. The ping is now working. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Lab 1-6 Answer Key: Troubleshoot Failover Connectivity: Part 1 When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: Step 1 Check the network settings for your NIC. Step 2 After the failover, the ping is not working and Hardware Failover is not enabled. Enable hardware failover. Step 3 Note a run of UUOS is required. Confirm the pending activity (for YOUR POD ONLY!!!) and reboot. Step 4 Open the LAN Tab in UCSM and check the native VLAN on both fabrics. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 103 Step 5 To confirm open a ssh session to UCSM using IP 172.16.1.200 FastLane-UCS-A# connect nxos a … FastLane-UCS-A(nxos)# sho int e1/11-12 trunk -------------------------------------------------------------Port Native Status Port Vlan Channel -------------------------------------------------------------Eth1/11 1 trunking -Eth1/12 1 trunking --------------------------------------------------------------Port Vlans Allowed on Trunk -------------------------------------------------------------Eth1/11 1,610-611 Eth1/12 1,610-611 -------------------------------------------------------------Port Vlans Err-disabled on Trunk -------------------------------------------------------------Eth1/11 none Eth1/12 none -------------------------------------------------------------Port STP Forwarding -------------------------------------------------------------Eth1/11 1,610-611 Eth1/12 1,610-611 -------------------------------------------------------------Port Vlans in spanning tree forwarding state and not pruned -------------------------------------------------------------Eth1/11 -Eth1/12 -FastLane-UCS-A(nxos)# 104 Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. FastLane-UCS-A(nxos)# exit FastLane-UCS-A# connect nxos b … FastLane-UCS-B(nxos)# sho interface e1/11-12 trunk -------------------------------------------------------------Port Native Status Port Vlan Channel -------------------------------------------------------------Eth1/11 1 trunking --------------------------------------------------------------Port Vlans Allowed on Trunk -------------------------------------------------------------Eth1/11 1,610-611 -------------------------------------------------------------Port Vlans Err-disabled on Trunk -------------------------------------------------------------Eth1/11 none -------------------------------------------------------------Port STP Forwarding -------------------------------------------------------------Eth1/11 1,610-611 -------------------------------------------------------------Port Vlans in spanning tree forwarding state and not pruned -------------------------------------------------------------Eth1/11 -FastLane-UCS-B(nxos)# © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 105 Lab 1-7 Answer Key: Troubleshoot Failover Connectivity: Part 2 When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup 106 Step 1 Check NIC settings. Hardware failover is enabled. Step 2 The uplink interface goes DOWN and vNIC stays UP with no failover, which means that there is something strange configured on the vNIC. Check for more settings on the vNIC. Step 3 You will notice that the Network Control Policy is configured as NCP. Step 4 Navigate to the policy configuration. Step 5 The network control policy Action on uplink Fail is set to Warning, which means that if the uplink fails, only the warning will be seen in the UCSM. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 107 Lab 3-1 Answer Key: Troubleshoot Cisco UCS C-Series Server When you complete this activity, your solution will be similar to the results here, with differences that are specific to your device or workgroup: 108 Step 1 The first thing to look for is the config error message Step 2 You notice the server admin is used to local disks and has created a local disk policy. Step 3 Go to the Equipment Tab and check your servers inventory for local disks. Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 4 There are no disks in the assigned server, therefore the service profile config fails. there are two possible solutions: - the wrong server has been selected (the customers other problem) - there are no disks in any server and the local disk configuration needs to be removed. In this lab there are NO disks in any server (you can check all of them) so Option 2 is the one we are looking for. Step 5 Go to your service profile and click the “Storage” tab, then “Change Local Disk Configuration Policy” Step 6 Select “No Disk Policy” and click “OK” and “Save Changes” © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 109 Caution 110 Changing the Disk Policy may cause DATA LOSS if data is stored on local disks. Step 7 The Service Profile Status changes to “Config” and the rack server is successfully assiociated. Step 8 To solve the numbering problem go to “Equipment” – “Rack-Mounts” and expand one of the FEX and select “Backplane Ports” Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 9 Note On the pane on the right notice Ports and server IDs, this enables you to fill in the table from step 2 The server are labeled identical on both FEX. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 111 Optional Task: renumber your server to 1P 112 Step 1 Remove the service profile from your server. Step 2 Select your PHYSICAL server, right-click and select “Server Maintenance” Step 3 Select “Decommission” and click OK Step 4 Wait for the server to disappear from the equipment tab Step 5 Select “Equipment” in the Equipment tab Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc. Step 6 Select the “Decommissioned” Tab in the right hand workpane Step 7 Expand “Rack-Mounts” and select your server. Step 8 Double-Click the ID field and enter ID 1P (P is your Pod number) Step 9 Select the “Recommission” radio Button on your server. © 2013 Fast Lane and Cisco Systems, Inc. Fast Lane Lab Guide V5.1.2 113 Step 10 Click “Save Changes” Step 11 Note your Server has disappeared from the “Decommissioned“ tab. Step 12 Your server appears in the equipment tab with the new ID. Note 114 Chassis can also be renumbered this way but keep in mind you need to decommission equipment you want to renumber and decommissioned equipment cannot be used (no service profile running etc.) Troubleshooting Cisco Data Center Unified Computing (DCUCT) v5.0 © 2013 Fast Lane and Cisco Systems, Inc.
