Cisco Cisco UCS C22 M3 Rack Server 白皮書

 

 

White Paper 

© 2009-2012 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. 

Page 12 of 44 

Note:   It is very important that you create a VLAN that is global across both fabric interconnects. This way, VLAN 
 

identity is maintained across the fabric interconnects in case of failover. 

The following screenshot shows two VLANs. 

 

After these preparatory steps have been completed, you can generate a service profile template for the required 

hardware configuration. You can then create the service profiles for all eight nodes from the template.  

Service profiles are the central concept of the Cisco Unified Computing System. Each service profile serves a specific 

purpose: to help ensure that the associated server hardware has the configuration required to support the 

applications it will host. 

The service profile maintains configuration information about: 

● 

Server hardware 

● 

Interfaces 

● 

Fabric connectivity 

● 

Server and network identity  

This information is stored in a format that can be managed through Cisco UCS Manager. All service profiles are 

centrally managed and stored in a database on the fabric interconnect.  

The service profile consists of the following information: 

● 

Identity and personality information for the server 

◦ 

Universally unique ID (UUID) 

◦ 

World wide node name (WWNN) 

◦ 

Boot order 

● 

LAN and SAN configuration (through the vNIC and vHBA configuration) 

◦ 

NIC and HBA identity (MAC addresses and WWN and WWPN information) 

◦ 

Ethernet NIC profile (flags, maximum transmission unit [MTU], etc.) 

◦ 

VLAN and VSAN connectivity information 

● 

Various policies (disk scrub policy, quality of service [QoS], etc.). For Oracle certification testing, no policies 

were used.