A service profile represents a logical server and stores the server personality and server connectivity requirements. The main purpose of a service profile is to support server mobility. Once a service profile is associated with a server, the server is ready to have an operating system and applications installed. Remember that when a service profile is disassociated from a server, the identity and connectivity information for the server is reset to factory defaults. A service profile can be associated with only one blade at a time, but the association can be changed if there is a problem with the particular blade. The “replacement blade” for the profile will inherit the WWN/VSAN information and boot specifications from the profile just like the original blade.
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.
Service Profile Templates
With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.
Move a service profile
To move a service profile which is associated to a particular blade to a different blade; the service profile needs to be first disassociated with the blade to which it is assigned and then it can be associated to the other blade. However to quickly do this, login to UCS manager and navigate to Server tab > Service Profiles and select the service profile that you want to move. Click Change Service Profile Association from the work pane.
In the Associate Service Profile window select the Server Assignment as Select Existing Server and then select the blade server from the available servers.
Hello, I'm trying to start VNC console using REST API on NFVIS.According to NFVIS API reference you have to do POST request to /api/operations/vncconsole/start without payload, which obviously doesn't make sense as host might ha...
Hi folks,Does changing the Port Tracking setting on ACI (namely, enabling it, or modifying the number of active uplinks) cause any disruption?A customer does not have that enabled, and is requiring it to be enabled with 0 active uplinks, in order for Leaf...
We're running DCNM 11.5(3) and are not able to create and deploy switch local SNMPv3 user on the Nexus switches in the fabric.I've already tried two approaches:I entered the CLI configuration in the fabric settings > Manageability > AAA Freefor...