The 350-601 exam objective 'Configure and manage Cisco UCS server profiles, pools, and policies' solves a massive problem: manually configuring hundreds of data centre servers one by one is slow and error-prone. UCS (Unified Computing System) automates this by treating server hardware like Lego bricks that can be snapped together using pre-defined templates. For someone studying for 350-601, understanding server profiles, pools, and policies is the difference between guessing exam answers and confidently knowing how Cisco automates data centre operations.
Jump to a section
A simple way to picture UCS Server Configuration and Management
The Hotel Booking Manager is the person who makes sure every guest room is ready before guests arrive. They do not build the hotel or clean the rooms themselves. Instead, they define the rules for how rooms get prepared and assigned.
First, the manager creates a 'policy' - a rule book that says each room must have a fresh towel, a working TV, and a king-size bed. Then they create 'pools' - a list of available rooms, like 'Ocean View Rooms' or 'Standard Rooms'. When a guest books, the manager pulls a room from the correct pool and assigns it to that guest.
Next, the manager creates a 'profile' - a template for a perfect room setup. It says: 'For a corporate guest, use the Ocean View pool, add a desk, and set the TV to channel 5.' When a new corporate booking comes in, the manager uses that profile to instantaneously set up the room without rethinking every detail.
But here is the clever part: if a guest cancels, the room returns to the pool. If a room needs maintenance, the manager moves it to a different pool. The hotel keeps running smoothly because the manager never handles the actual pillows - they just design the system that makes sure the right pillows appear in the right room at the right time. This is exactly how UCS Server Configuration and Management works for data centre servers.
Cisco UCS (Unified Computing System) is a set of hardware and software that brings together computing, networking, and storage into one managed system. Think of it as a single brain that controls many server blades (thin, modular servers that slide into a chassis) and rack servers (standalone tower-style servers).
Before UCS, data centre engineers had to configure each server individually. They would plug in cables, set network addresses, install an operating system, and tweak settings by hand. If you had 200 servers, that meant 200 identical, boring, error-prone jobs. UCS automates this by introducing three key concepts: policies, pools, and profiles.
A policy is a set of rules. For example, a 'power policy' says 'never turn off the server'. A 'boot policy' tells the server 'first try to boot from the network, then from the local hard drive'. A 'MAC address policy' might say 'use a range of MAC addresses from pool X'. Every policy is a reusable rule that you write once and apply to many servers.
A pool is a bucket of unused resources. For example, you might have a pool of MAC addresses (unique hardware identifiers for network interfaces), a pool of WWPNs (World Wide Port Names, which are unique identifiers for Fibre Channel storage connections), and a pool of UUIDs (Universally Unique Identifiers, which are serial numbers that identify a server uniquely on the network). Instead of giving each server a hard-coded MAC address, you tell UCS to 'grab the next available MAC from the pool'. When the server is decommissioned, the MAC returns to the pool and can be reused.
A service profile is the superstar of UCS. It is a complete blueprint that bundles together all the settings a server needs to operate. A service profile includes:
Which pool to use for MAC addresses
Which boot policy to follow
Which power policy to apply
Which firmware version to run
Which storage configuration to use
When you create a service profile and associate it with a physical server, that server instantly configures itself to match the profile. It is like handing a hotel guest a pre-programmed key card that already unlocks their room, sets the temperature, and charges the minibar to their credit card.
The magic happens when you combine these. Say you have 100 servers. Create one 'Gold Service Profile' that uses a specific boot policy, power policy, and MAC pool. Then apply that profile to all 100 servers. Every server comes up identical. If you need to change the boot order for all 100, you edit the boot policy once, and every server attached to that profile picks up the change automatically.
Why does this matter for the exam? The 350-601 loves to test whether you know the difference between a policy and a profile. A policy is a building block - it defines ONE thing (like power behaviour). A profile is the assembled product - it bundles many policies together into a complete server definition.
Another critical distinction: there are 'global' policies that apply to the entire UCS domain, and 'local' policies that only apply to a specific server or chassis. The exam will expect you to know when to use each.
UCS Manager is the central management interface where you create and assign profiles, pools, and policies. It runs on the Fabric Interconnects (the networking switches that connect all UCS components). Everything is configured through UCS Manager, either via a graphical interface, command line, or API.
In older data centres, adding a new server involved cabling, configuration, and testing - often taking hours. With UCS, you create a profile in seconds, associate it with a physical server, and the server configures itself. This is called 'stateless computing' - the server's identity and settings are not stored on the server itself but in the profile, which lives in UCS Manager.
Create Pools
First, create UUID, MAC, and WWPN pools to define ranges of available resources. These are the buckets from which servers will grab their identities.
Define Policies
Create individual policies for boot behaviour, power management, and firmware. Each policy is a single rule that can be reused across many profiles.
Create a Service Profile Template
Build a reusable blueprint that bundles together the pools and policies created in steps 1 and 2. This template saves time when deploying many identical servers.
Create Service Profiles from Template
Use the template to generate individual service profiles. Each profile is a unique instance that inherits all settings from the template but can be customised later if needed.
Associate Profiles with Physical Servers
Link each service profile to a specific server blade or rack server. Upon association, the server automatically configures itself to match the profile.
Verify Configuration
Check UCS Manager to confirm each server reports the correct boot policy, power policy, and pool-assigned identifiers. This step ensures the deployment was successful.
An IT professional at a mid-sized company needs to deploy 50 new server blades for a customer-facing web application. Here is what they actually do.
First, they log into UCS Manager and create a 'Boot Policy' called 'WebAppBoot'. This policy specifies: 'Attempt to boot from the local hard drive first. If that fails, boot from the network using PXE (Preboot eXecution Environment, which allows a server to load an operating system from the network).' This policy is saved once and can be reused by hundreds of servers.
Next, they create a 'Power Policy' called 'WebAppPower'. It says: 'If the server loses power and comes back, power on automatically.' They also create a 'Server Pool' called 'WebAppPool' that contains all 50 physical server blades, grouped by their location in the chassis.
Now comes the profile creation. They create a 'Service Profile Template' called 'WebAppTemplate'. This template bundles:
The 'WebAppBoot' boot policy
The 'WebAppPower' power policy
A MAC pool (which automatically assigns unique Ethernet addresses)
A WWPN pool (which assigns storage network identifiers)
Firmware management settings (which version of the BIOS and UCS software to run)
Once the template is saved, they create 50 service profiles from it - one for each server. In UCS Manager, this takes about 30 seconds. They then associate each profile with a physical server in the WebAppPool.
After association, each server automatically:
Pulls its MAC address from the pool
Configures its network interfaces
Sets the correct BIOS version
Prepares to boot from the local disk
The servers are now ready for the operating system installation. If the company later decides to change the boot order for all 50 servers, the engineer edits the 'WebAppBoot' policy once. The change propagates to all 50 profiles automatically.
If a server fails, the engineer can:
Disassociate the service profile from the broken server
Associate it with a spare server in the pool
The spare server instantly adopts the exact configuration of the failed one, without any manual reconfiguration
This demonstrates the real power: disaster recovery becomes trivial. The profile is the server's identity, not the physical hardware. You can literally swap the underlying metal and the profile makes the new server behave exactly like the old one.
The 350-601 exam tests 'UCS Server Configuration and Management' with specific, predictable patterns. Here is exactly what to expect.
First, expect scenario-based questions that describe a business requirement and ask you to choose the correct pool or policy. For example: 'A company needs all servers to boot from the SAN (Storage Area Network) first. Which policy should be configured?' The correct answer is the 'Boot Policy'. The trap is that they might list 'Power Policy' or 'Server Pool' as distractors.
Second, the exam loves to test the difference between 'Service Profile' and 'Service Profile Template'. A service profile is an individual server's configuration. A template is a reusable blueprint used to create many identical profiles. The exam question might say: 'An engineer needs to deploy 100 identical servers. What should be created first?' The answer is a 'Service Profile Template', not individual profiles.
Third, know the types of pools. The exam expects you to distinguish between:
UUID Pool (server identification)
MAC Pool (network interface addresses)
WWPN Pool (Fibre Channel storage identifiers)
WWNN Pool (World Wide Node Name, the overall storage node identifier)
Server Pool (grouping of physical servers)
A common trap: the exam might describe a scenario where you need to assign storage identifiers and ask which pool to configure. If the question mentions 'Fibre Channel storage', the answer is WWPN Pool. If it mentions 'Ethernet networking', the answer is MAC Pool.
Fourth, understand the difference between 'initial' and 'updating' policies. Some policies (like boot policy) are read when the server boots. If you change them, the server must reboot to apply the change. Other policies (like power policy) are applied immediately. The exam will test whether you know which policies require a reboot.
Fifth, the exam asks about 'stateless computing'. Be ready for a question like: 'What advantage do service profiles provide over traditional server configuration?' The answer is that the server's identity and settings are stored in the profile, not the hardware, allowing quick hardware replacement without reconfiguration.
Finally, there will be questions about 'association'. Associating a profile with a server makes that server assume the profile's configuration. Disassociating frees the server. A trap question might ask: 'What happens to a server's data when the service profile is disassociated?' The correct answer is that the data on the local disks remains intact. The profile only controls configuration, not disk contents.
Memorise these definitions precisely for the exam:
Policy: a single rule or set of rules for a specific behaviour
Pool: a collection of unassigned resources
Service Profile: a complete server configuration template
Service Profile Template: a reusable blueprint for creating multiple service profiles
Association: the action of linking a profile to a physical server
A service profile is a complete server blueprint that bundles multiple policies and pools into one reusable configuration.
Pools hold unassigned resources like MAC addresses and UUIDs that servers can borrow and return dynamically.
Policies define individual behaviours such as boot order, power settings, and firmware versions.
Stateless computing means the server's identity is in the profile, not the hardware, enabling instant hardware replacement.
Service profile templates allow you to create hundreds of identical servers from a single master blueprint.
Association links a service profile to a physical server, immediately applying the profile's configuration.
These come up on the exam all the time. Here's how to tell them apart.
Service Profile
Represents a single server's configuration
Created individually or from a template
Can be customised after creation
Service Profile Template
A reusable blueprint for many servers
Cannot be associated with a server directly
Changes to the template propagate to profiles derived from it
MAC Pool
Provides Ethernet MAC addresses
Used for network interface cards
Each address is 12 hexadecimal characters
WWPN Pool
Provides World Wide Port Names
Used for Fibre Channel storage connections
Each name is 16 hexadecimal characters
Boot Policy
Controls the order of boot devices
Only takes effect on reboot
Can include network, local disk, and SAN boot
Power Policy
Controls what happens on power loss
Takes effect immediately
Options like 'always on' or 'last state'
Local Policy
Applies to a specific server or chassis
Overrides global policies for that device
Configured at the service profile level
Global Policy
Applies to all servers in the UCS domain
Acts as default if no local policy exists
Configured at the UCS Manager system level
Mistake
A service profile is the same as a physical server.
Correct
A service profile is a software definition of a server's configuration, not the physical hardware. The profile can be moved between physical servers without changing the server's behaviour.
Beginners think 'profile' means the server itself because the term sounds physical, but in UCS, the profile is abstract and separate from the metal.
Mistake
Pools allocate resources permanently to a server.
Correct
Pools assign resources (like MAC addresses) temporarily. When a server is decommissioned, the resource goes back to the pool and can be reused by another server.
People think of 'pool' like a swimming pool where once you take water out it's gone. In UCS, resources return to the pool, like borrowing a library book and returning it.
Mistake
Changing a policy immediately changes all servers using it.
Correct
Some policies (like boot policy) only take effect on the next server reboot. Changes to other policies (like power policy) apply immediately.
Beginners assume all changes are instant because UCS feels magical. In reality, certain settings require a reboot because they affect low-level hardware behaviour.
Mistake
UCS Manager is a separate physical appliance you install in the rack.
Correct
UCS Manager is software that runs on the Fabric Interconnects (the network switches in the UCS system), not a separate hardware device.
Many beginners visualise a management server like a traditional management console, but Cisco embedded UCS Manager into the existing network hardware.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A service profile is an individual server's configuration. A service profile template is a reusable base that you use to create many identical service profiles quickly.
Yes. Disassociate the profile from the old server, then associate it with a new server. The new server immediately adopts the exact same configuration.
The data on local disks remains unchanged. Service profiles only configure network, storage, and boot settings - they do not erase or migrate data.
It depends. Changes to boot policy and firmware policy require a reboot. Changes to power policy take effect immediately without a reboot.
A UUID pool provides unique serial numbers (Universally Unique Identifiers) that identify each server on the network. Every server needs a distinct UUID.
Use a WWPN (World Wide Port Name) pool. MAC pools are for Ethernet networking, and WWPN pools are specifically for Fibre Channel storage connections.
You've finished UCS Server Configuration and Management. Continue through the 350-601 study guide to build a complete picture of the exam.
Done with this chapter?