Every server that is provisioned in the Cisco Unified Computing System is specified by a service profile. A service profile is a software definition of a server and its LAN and SAN network connectivity, in other words, a service profile defines a single server and its storage and networking characteristics. Service profiles are stored in the Cisco UCS 6100 Series Fabric Interconnects. When a service profile is deployed to a server, UCS Manager automatically configures the server, adapters, fabric extenders, and fabric interconnects to match the configuration specified in the service profile. This automation of device configuration reduces the number of manual steps required to configure servers, network interface cards (NICs), host bus adapters (HBAs), and LAN and SAN switches.
Service profile Overview
A service profile typically includes four types of information:
a) Server definition: It defines the resources (e.g. a specific server or a blade inserted to a specific chassis) that are required to apply to the profile.
b) Identity information: Identity information includes the UUID, MAC address for each virtual NIC (vNIC), and WWN specifications for each HBA.
c) Firmware revision specifications: These are used when a certain tested firmware revision is required to be installed or for some other reason a specific firmware is used.
d) Connectivity definition: It is used to configure network adapters, fabric extenders, and parent interconnects, however this information is abstract as it does not include the details of how each network component is configured.
A service profile is created by the UCS server administrator. This service profile leverages configuration policies that were created by the server, network, and storage administrators. Server administrators can also create a Service profile template which can be later used to create Service profiles in an easier way. A service template can be derived from a service profile, with server and I/O interface identity information abstracted. Instead of specifying exact UUID, MAC address, and WWN values, a service template specifies where to get these values. For example, a service profile template might specify the standard network connectivity for a web server and the pool from which its interface's MAC addresses can be obtained. Service profile templates can be used to provision many servers with the same simplicity as creating a single one.
Service profile types
There are two types of service profiles in a UCS system:
a) Service profiles that inherit server identity: These service profiles are similar in concept to a rack mounted server. These service profiles use the burned-in values (like MAC addresses, WWN addresses, BIOS version and settings, etc.) of the hardware. Due to the nature of using these burned-in values these profiles are not easily portable and can’t be used from moving one server to the other. In other words these profiles exhibit the nature of 1:1 mapping and thus require changes to be made to them when moving from one server to another.
b) Service profiles that override server identity: These service policies exhibit the nature of stateless computing in UCS system. These service profiles take the resources (like MAC addresses, WWN addresses, BIOS version, etc.) from a resource pool already created in the UCS manager. The settings or values from these resource pools override the burned-in values of the hardware. Hence these profiles are very flexible and can be moved from one server to the other easily and this movement is transparent to the network. In other words these profiles provide a 1: many mapping and require no change to be made to them when moving from one server to another.
To create a Service profile navigate to the Servers tab, right click on Service Profiles and choose Create Service Profile.
Watch this video to learn more about Service Profiles on UCS.
Design: ACI to physical Alteon LB connected over VPC VPC -Port-channel feature: PCP-ON Control : Fast select hot standby port, Graceful convergence, Suspend individual port Could you please let me know how we can avoid causing a MAC t...
Hi community,1. When using the topology with Cloud ACI using TGW to connect between infra and user VPC, does it mean the version of Cloud ACI has to be 5.x or later? Or does it mean the ACI On-premises it self has to be at version 5.x or later?My guess is...
greetings!im in a spot of bother where i need to make additional storage available on a new brocade coreIs it possible to have 2 x upstream core brocades available to a server interface using a Nexus 5672UP as edgei.e flogi-tableserver int ...
I have a case logged with TAC that is not progressing very fast and am wondering if anyone has seen this before.We have a pair of N93180 switches running in NXOS mode as peer partners, vpc etc. While doing some testing on QoS settings for a teams im...