Техническая Инструкция для Cisco Cisco UCS B200 M1 Blade Server
LAN and SAN Connectivity for a Cisco UCS Blade
Document ID: 110202
Contents
Introduction
Prerequisites
Requirements
Components Used
Network Diagram
Conventions
Background Information
Main Task
Task
Create Global VLAN
Create Global VSAN
Create vHBAs
Create vNICs
Associate Server to Service Profile
Verify
Troubleshoot
Related Information
Prerequisites
Requirements
Components Used
Network Diagram
Conventions
Background Information
Main Task
Task
Create Global VLAN
Create Global VSAN
Create vHBAs
Create vNICs
Associate Server to Service Profile
Verify
Troubleshoot
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. The profile can then be associated
with a single blade at a time.
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.
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.