Table of Contents
Advertisement
Quick Links
LAN and SAN Connectivity for a Cisco UCS Blade
Document ID: 110202
Contents
Introduction
Verify
Introduction
In order to understand blade management in the Cisco Unified Computing System (UCS), it is key to
understand the Service Profile or logical server. The Service Profile represents a logical view of a single blade
server, without the need to know exactly which blade you discuss. The profile object contains the server
personality, for example, identity and network information and so forth. The profile can then be associated
with a single blade at a time.
The concept of profiles was invented to support the notion of logical server mobility or the transfer of identity
transparently from one blade to another, as well as pooling concept. Even if you intend to manage the blade
server as a traditional individual server, and do not take advantage of mobility or pooling, you still have to
create and manage a service profile for the blade. While you can boot a blade without a service profile, it does
not have a network or SAN connectivity.
This is a summary of contents of a service profile in Cisco UCS:
•
Identity information for Server (UUID)
•
World−Wide Node Name (Server−wide)
•
LAN/SAN configuration (through vNIC/vHBA configuration)
♦
Identity of NIC/HBA (MAC/WWN)
♦
Ethernet NIC Profile
♦
VLAN/ VSAN configuration information
•
Boot Order
•
Various Policies
This document assumes Cisco UCS Manager connectivity works and all hardware was discovered correctly.
Advertisement
Table of Contents
Related Manuals for Cisco UCS 82598KR
Summary of Contents for Cisco UCS 82598KR
-
Page 1: Table Of Contents
Related Information Introduction In order to understand blade management in the Cisco Unified Computing System (UCS), it is key to understand the Service Profile or logical server. The Service Profile represents a logical view of a single blade server, without the need to know exactly which blade you discuss. The profile object contains the server personality, for example, identity and network information and so forth. -
Page 2: Prerequisites
For adapters with only physical NICs, for example, Cisco UCS CNA M71KR and Cisco UCS 82598KR, you must create a vNIC for each NIC you want to make usable on the network within Cisco UCS. Then vNIC has a switch setting and a failover flag. For Cisco UCS 82598KR, you must match the physical setting so that the first adapter goes to Fabric Interconnect A and the second to Fabric Interconnect B, and you cannot choose failover. -
Page 3: Main Task
Physical Adapter For adapters with only physical NICs (Cisco UCS M71KR, Cisco UCS 82598KR), you must create a vNIC for each NIC you want to make usable on the network within Cisco UCS. Then, vNIC has a switch setting and a failover flag. For the Cisco UCS 82598KR, you must match the physical setting so that the first adapter goes to switch A and the second to switch B, and you cannot choose failover. - Page 4 Enter this information in the Create VLAN dialog box and then click OK: In the Name field, enter a unique name for the VLAN. In the ID field, enter the network ID assigned to the VLAN. Cisco UCS Manager GUI adds the VLAN to the VLANs node under LAN Cloud.
- Page 5 VLANs that are accessible to both Fabric Interconnects are visible only in LAN Cloud > VLANs node. You cannot see them under the Fabric Interconnect > VLANs node, which displays only the VLANs accessible to just that Fabric Interconnect. Verify that you have successfully created a global VLAN.
-
Page 6: Create Global Vsan
The VSAN/vHBA logic is mostly analogous to the VLAN/vNIC logic. If you want to support any VSAN, it needs to be configured globally into Cisco UCS Manager, and then it can be associated with a particular vHBA. The default VSAN is preconfigured into Cisco UCS Manager, and is automatically chosen as the default connectivity for each vHBA. - Page 7 Choose the VSANs tab in Work Pane, choose VSANs, then choose + in order to begin the VSAN creation . Cisco UCS Manager GUI adds the VSAN to the VSANs node under SAN Cloud.
- Page 8 In the ID field, enter a valid VSAN ID. This needs to match an ID in your Core SAN. Add a VLAN ID that is used internally in order to carry FCoE. Cisco UCS Manager GUI adds the VSAN to the VSANs node under SAN Cloud.
-
Page 9: Create Vhbas
Add the Virtual HBAs to your Profile if you are required to do FCoE for Fiber Channel access to storage. The vHBA is configured into each Service Profile in a manner analogous to vNIC. Log into Cisco UCS Manager GUI. In the Navigation pane, choose the Servers tab. - Page 10 Select the method to assign WWN names to the vHBAs. Select the vSAN that was created in steps above and assign it to vHBAs.
-
Page 11: Create Vnics
Create vNICs Add vNICs to the profile as explained in the next steps as a continuation of the Service Profile creation process: Complete these steps: Choose the VLAN that was created in the previous step and assign it to the vNICs. -
Page 12: Associate Server To Service Profile
Cisco UCS Manager. When you associate a blade to a Service Profile, the Cisco UCS Manager first tries to assign the blade to the configuration. This does nothing to modify the blade itself, but the assignment still checks that a blade is compatible with a profile. -
Page 13: Troubleshoot
Technical Support & Documentation − Cisco Systems Contacts & Feedback | Help | Site Map © 2013 − 2014 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of Cisco Systems, Inc. - Page 14 Updated: Sep 02, 2009 Document ID: 110202...