- Server Policies
- BIOS Policy
- Server BIOS Settings
- Creating a BIOS Policy
- Deleting a BIOS Policy
- Default BIOS Settings
- Basic BIOS Settings
- Processor BIOS Settings
- I/O BIOS Settings
- RAS Memory BIOS Settings
- USB BIOS Settings
- PCI BIOS Settings
- Graphics Configuration BIOS Settings
- Boot Options BIOS Settings
- Server Manager BIOS Settings
- Console BIOS Settings
- IPMI Access Profile
- Serial over LAN Policy
- iSCSI Adapter Policy
- Local Disk Policy
- Scrub Policy
- vMedia Policy
Server
Policies
- Server Policies
- BIOS Policy
- IPMI Access Profile
- Serial over LAN Policy
- iSCSI Adapter Policy
- Local Disk Policy
- Scrub Policy
- vMedia Policy
Server Policies
Server policies allow you to apply changes globally to your Cisco UCS servers.
Note | You must include policies in a service profile and associate them with a server before Cisco UCS Central can apply them. |
BIOS Policy
The BIOS policy automates the configuration of BIOS settings for a server or group of servers. You can create global BIOS policies available to all servers in the root organization, or you can create BIOS policies in sub-organizations that are only available to that hierarchy.
To use a BIOS policy:
-
Create the BIOS policy in Cisco UCS Central.
-
Assign the BIOS policy to one or more service profiles.
-
Associate the service profile with a server.
During service profile association, Cisco UCS Central modifies the BIOS settings on the server to match the configuration in the BIOS policy. If you do not create and assign a BIOS policy to a service profile, the server uses the default BIOS settings for that server platform.
- Server BIOS Settings
- Creating a BIOS Policy
- Deleting a BIOS Policy
- Default BIOS Settings
- Basic BIOS Settings
- Processor BIOS Settings
- I/O BIOS Settings
- RAS Memory BIOS Settings
- USB BIOS Settings
- PCI BIOS Settings
- Graphics Configuration BIOS Settings
- Boot Options BIOS Settings
- Server Manager BIOS Settings
- Console BIOS Settings
Server BIOS Settings
Cisco UCS provides two methods for making global modifications to the BIOS settings on servers in a Cisco UCS domain. You can create one or more BIOS policies, that include a specific grouping of BIOS settings, that match the needs of a server or set of servers. Alternatively, you can use the default BIOS settings for a specific server platform.
Both the BIOS policy and the default BIOS settings for a server platform enable you to fine tune the BIOS settings for a server managed by Cisco UCS Central.
Depending on the needs of the data center, you can configure BIOS policies for some service profiles ,and use the BIOS defaults in other service profiles, in the same Cisco UCS domain, or you can use only one of them. You can also use Cisco UCS Central to view the actual BIOS settings on a server and determine whether they are meeting current needs.
Creating a BIOS Policy
The following example shows how to create a BIOS policy under the root organization, and set the NUMA configuration:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr)/ org #create bios-policy biosPolicy3 UCSC(policy-mgr) /org/bios-policy* # set numa-config numa-optimization enabled UCSC(policy-mgr) /org/bios-policy* # commit-buffer UCSC(policy-mgr) /org/bios-policy #
Deleting a BIOS Policy
The following example shows how to delete a BIOS policy in the root organization:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr)/ org #delete bios-policy biosPolicy3 UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Default BIOS Settings
Cisco UCS Central includes a set of default BIOS settings for each type of server supported by Cisco UCS. The default BIOS settings are available only in the root organization and are global. Only one set of default BIOS settings can exist for each server platform supported by Cisco UCS. You can modify the default BIOS settings, but you cannot create an additional set of default BIOS settings.
Each set of default BIOS settings are designed for a particular type of supported server and are applied to all servers of that specific type which do not have a BIOS policy included in their service profiles.
Unless a Cisco UCS implementation has specific needs that are not met by the server-specific settings, we recommend that you use the default BIOS settings that are designed for each type of server in the Cisco UCS domain.
Cisco UCS Central applies these server platform-specific BIOS settings as follows:
-
The service profile associated with a server does not include a BIOS policy.
-
The BIOS policy is configured with the platform-default option for a specific setting.
You can modify the default BIOS settings provided by Cisco UCS Central. However, any changes to the default BIOS settings apply to all servers of that particular type or platform. If you want to modify the BIOS settings for only certain servers, we recommend that you use a BIOS policy.
Basic BIOS Settings
The following table lists the main server BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Processor BIOS Settings
The following tables list the processor BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description | ||
---|---|---|---|
Hardware Prefetcher |
Whether the processor allows the Intel hardware prefetcher to fetch streams of data and instruction from memory into the unified second-level cache when necessary. This can be one of the following:
|
||
Adjacent Cache Line Prefetcher |
Whether the processor fetches cache lines in even/odd pairs instead of fetching just the required line. This can be one of the following:
|
||
Data Cache Unit (DCU) Streamer Prefetcher |
Whether the processor uses the DCU IP Prefetch mechanism to analyze historical cache access patterns and preload the most relevant lines in the L1 cache. This can be one of the following:
|
||
Data Cache Unit (DCU) IP Prefetcher |
Whether the processor uses the DCU IP Prefetch mechanism to analyze historical cache access patterns and preload the most relevant lines in the L1 cache. This can be one of the following: |
Name | Description | ||
---|---|---|---|
Turbo Boost |
Whether the processor uses Intel Turbo Boost Technology, which allows the processor to automatically increase its frequency if it is running below power, temperature, or voltage specifications. This can be one of the following: |
||
Enhanced Intel Speed Step |
Whether the processor uses Enhanced Intel SpeedStep Technology, which allows the system to dynamically adjust processor voltage and core frequency. This technology can result in decreased average power consumption and decreased average heat production. This can be one of the following:
We recommend that you contact your operating system vendor to make sure your operating system supports this feature. |
||
Hyper Threading |
Whether the processor uses Intel Hyper-Threading Technology, which allows multithreaded software applications to execute threads in parallel within each processor. This can be one of the following:
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
||
Core Multi-Processing |
Sets the state of logical processor cores per CPU in a package. If you disable this setting, Intel Hyper Threading technology is also disabled. This can be one of the following:
We recommend that you contact your operating system vendor to make sure your operating system supports this feature. |
||
Virtualization Technology (VT) |
Whether the processor uses Intel Virtualization Technology, which allows a platform to run multiple operating systems and applications in independent partitions. This can be one of the following:
|
Name | Description | ||
---|---|---|---|
Power Management |
Enables you to configure the CPU power management settings for the following options: Power Technology can be one of the following:
|
||
Energy Performance |
Allows you to determine whether system performance or energy efficiency is more important on this server. This can be one of the following:
|
||
Processor C State |
Whether the system can enter a power savings mode during idle periods. This can be one of the following:
We recommend that you contact your operating system vendor to make sure your operating system supports this feature. |
||
Processor C1E |
Allows the processor to transition to its minimum frequency upon entering C1. This setting does not take effect until after you have rebooted the server. This can be one of the following: |
||
CPU Performance |
Sets the CPU performance profile for the server. This can be one of the following:
|
||
The amount of power available to the server components when they are idle. This can be one of the following:
|
Name | Description | ||
---|---|---|---|
Processor C3 Report |
Whether the processor sends the C3 report to the operating system. This can be one of the following:
On the Cisco UCS B440 Server, the BIOS Setup menu uses enabled and disabled for these options. If you specify acpi-c2 or acpi-c3, the server sets the BIOS value for that option to enabled. |
||
Processor C6 Report |
Whether the processor sends the C6 report to the operating system. This can be one of the following: |
||
Processor C7 Report |
Whether the processor sends the C7 report to the operating system. This can be one of the following:
|
||
Max Variable MTRR Setting |
Allows you to select the number of mean time to repair (MTRR) variables. This can be one of the following: |
||
Demand Scrub |
Whether the system corrects single bit memory errors encountered when the CPU or I/O makes a demand read. This can be one of the following: |
||
Patrol Scrub |
Whether the system actively searches for, and corrects, single bit memory errors even in unused portions of the memory on the server. This can be one of the following:
|
||
CPU Hardware Power Management |
Enables processor Hardware Power Management (HWPM). This can be one of the following: |
I/O BIOS Settings
The following table lists the I/O BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description | ||
---|---|---|---|
Virtualization Technology (VT) for Directed IO |
Whether the processor uses Intel Virtualization Technology for Directed I/O (VT-d). You can select one of the following options:
|
||
Interrupt Re-map |
Whether the processor supports Intel VT-d Interrupt Remapping. You can select one of the following options: |
||
Coherency Support |
Whether the processor supports Intel VT-d Coherency. You can select one of the following options: |
||
Address Translation Services (ATS) Support |
Whether the processor supports Intel VT-d Address Translation Services (ATS). You can select one of the following options: |
||
Pass Through DMA Support |
Whether the processor supports Intel VT-d Pass-through DMA. You can select one of the following options: |
RAS Memory BIOS Settings
The following table lists the RAS memory BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description |
---|---|
NUMA |
Whether the BIOS supports NUMA. This can be one of the following:
|
LV DDR Mode |
Whether the system prioritizes low voltage or high frequency memory operations. This can be one of the following:
|
DRAM Refresh Rate |
The refresh interval rate for internal memory. This can be one of the following: |
Memory RAS Configuration Mode |
How the memory reliability, availability, and serviceability (RAS) is configured for the server. This can be one of the following:
|
Sparing Mode |
Sparing optimizes reliability by holding memory in reserve so that it can be used in case other DIMMs fail. This option provides some memory redundancy, but does not provide as much redundancy as mirroring. The available sparing modes depend on the current memory population. This option is only available if you choose the sparing option for the Memory RAS Config parameter. It can be one of the following:
|
DDR3 Voltage Selection |
The voltage to be used by the dual-voltage RAM. This can be one of the following: |
USB BIOS Settings
The following tables list the USB BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Basic Tab
Name | Description |
---|---|
Make Device Non Bootable |
Whether the server can boot from a USB device. This can be one of the following: |
USB Front Panel Access Lock |
USB front panel lock is configured to enable or disable the front panel access to USB ports. This can be one of the following: |
Legacy USB Support |
Whether the system supports legacy USB devices. This can be one of the following: |
USB Idle Power Optimizing Setting |
Whether the USB System Idle Power Optimizing setting is used to reduce USB EHCI idle power consumption. Depending upon the value you choose, this setting can have an impact on performance. This can be one of the following:
|
Port 60h/64h Emulation Support |
Whether the system supports 60h/64h emulation for complete USB keyboard legacy support. This can be one of the following: |
xHCI Mode Support |
How onboard USB 3.0 ports behave. This can be one of the following: |
Device Management Tab
Name | Description |
---|---|
Front Panel USB Ports |
Whether the front panel USB devices are enabled or disabled. This can be one of the following:
|
Rear Panel USB Ports |
Whether the rear panel USB devices are enabled or disabled. This can be one of the following:
|
Internal USB Ports |
Whether the internal USB devices are enabled or disabled. This can be one of the following:
|
KVM I/O |
Whether the KVM ports are enabled or disabled. This can be one of the following: |
SD Card Drives |
Whether the SD card drives are enabled or disabled. This can be one of the following: |
vMedia Devices |
Whether the virtual media devices are enabled or disabled. This can be one of the following: |
All USB Devices |
Whether all physical and virtual USB devices are enabled or disabled. This can be one of the following: |
PCI BIOS Settings
The following tables list the PCI configuration BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description | ||||
---|---|---|---|---|---|
Max Memory Below 4G |
Whether the BIOS maximizes memory usage below 4GB for an operating system without PAE support, depending on the system configuration. This can be one of the following: |
||||
Memory Mapped IO Above 4Gb Configuration |
Whether to enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space. Legacy option ROMs are not able to access addresses above 4GB. PCI devices that are 64-bit compliant but use a legacy option ROM may not function correctly with this setting enabled. This can be one of the following: |
||||
VGA Priority |
Allows you to set the priority for VGA graphics devices if multiple VGA devices are found in the system. This can be one of the following:
|
||||
PCIe OptionROMs |
Whether Option ROM is available on all expansion ports. This can be one of the following: |
||||
PCIe Mezz OptionRom |
Whether all mezzanine PCIe ports are enabled or disabled. This can be one of the following: |
||||
PCIe 10G LOM 2 Link |
Whether Option ROM is available on the 10G LOM port. This can be one of the following: |
||||
ASPM Support |
Allows you to set the level of ASPM (Active Power State Management) support in the BIOS. This can be one of the following: |
Name | Description |
---|---|
Slot n Link Speed |
This option allows you to restrict the maximum speed of an adapter card installed in PCIe slot n. This can be one of the following:
|
Name | Description |
---|---|
Slot n OptionROM |
Whether Option ROM is available on the specified port. This can be one of the following: |
Slot SAS |
Whether is available on the specified port. This can be one of the following: |
Slot HBA |
Whether is available on the specified port. This can be one of the following: |
Slot MLOM |
Whether Option ROM is available on the PCIe slot connected to the MLOM available on the specified port. This can be one of the following: |
Slot N1 |
Whether is available on the specified port. This can be one of the following: |
Slot N2 |
Whether is available on the specified port. This can be one of the following: |
Graphics Configuration BIOS Settings
The following tables list the graphics configuration BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description |
---|---|
Integrated Graphics |
Enables integrated graphics. This can be one of the following: |
Integrated Graphics Aperture Size |
Allows you to set the size of mapped memory for the integrated graphics controller. This can be one of the following: |
Onboard Graphics |
Enables onboard graphics (KVM). This can be one of the following: |
Boot Options BIOS Settings
The following table lists the boot options BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description |
---|---|
Boot Option Retry |
Whether the BIOS retries NON-EFI based boot options without waiting for user input. This can be one of the following: |
Onboard SCU Storage Support |
Whether the onboard software RAID controller is available to the server. This can be one of the following: |
Intel Entry SAS RAID |
Whether the Intel SAS Entry RAID Module is enabled. This can be one of the following: |
Intel Entry SAS RAID Module |
How the Intel SAS Entry RAID Module is configured. This can be one of the following: |
Server Manager BIOS Settings
The following tables list the server management BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description |
---|---|
Assert NMI on SERR |
Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a system error (SERR) occurs. This can be one of the following:
|
Assert NMI on PERR |
Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a processor bus parity error (PERR) occurs. This can be one of the following: |
OS Boot Watchdog Timer |
Whether the BIOS programs the watchdog timer with a predefined timeout value. If the operating system does not complete booting before the timer expires, the CIMC resets the system and an error is logged. This can be one of the following:
This feature requires either operating system support or Intel Management software. |
OS Boot Watchdog Timer Timeout Policy |
What action the system takes if the watchdog timer expires. This can be one of the following:
This option is only available if you enable the OS Boot Watchdog Timer. |
OS Boot Watchdog Timer Timeout |
What timeout value the BIOS uses to configure the watchdog timer. This can be one of the following:
This option is only available if you enable the OS Boot Watchdog Timer. |
Console BIOS Settings
The following table lists the Console BIOS settings that you can configure through a BIOS policy or the default BIOS settings:
Name | Description | ||
---|---|---|---|
Legacy OS Redirect |
Whether redirection from a legacy operating system, such as DOS, is enabled on the serial port. This can be one of the following: |
||
Console Redirection |
Allows a serial port to be used for console redirection during POST and BIOS booting. After the BIOS has booted and the operating system is responsible for the server, console redirection is irrelevant and has no effect. This can be one of the following:
|
||
BAUD Rate |
What BAUD rate is used for the serial port transmission speed. If you disable Console Redirection, this option is not available. This can be one of the following:
|
||
Terminal Type |
What type of character formatting is used for console redirection. This can be one of the following:
|
||
Flow Control |
Whether a handshake protocol is used for flow control. Request to Send / Clear to Send (RTS/CTS) helps to reduce frame collisions that can be introduced by a hidden terminal problem. This can be one of the following:
|
||
Allows you to change the action of the PuTTY function keys and the top row of the numeric keypad. This can be one of the following:
|
IPMI Access Profile
The IPMI access profile policy allows you to determine whether you can send the IPMI commands directly to the server, using the IP address. For example, you can send commands to retrieve sensor data from the Cisco IMC. This policy defines the IPMI access, including a username and password, that can be authenticated locally on the server, and whether the access is read-only or read-write.
You must include this policy in a service profile and that service profile must be associated with a server for it to take effect.
- Configuring an IPMI Access Profile
- Deleting an IPMI Access Profile
- Adding an Endpoint User to an IPMI Access Profile
- Deleting an Endpoint User from an IPMI Access Profile
Configuring an IPMI Access Profile
Obtain the following:
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . | ||
Step 3 | UCSC(policy-mgr) /org # create ipmi-access-profile profile-name |
Creates the specified IPMI access profile and enters organization IPMI access profile mode. | ||
Step 4 | UCSC(policy-mgr) /org/ipmi-access-profile # create ipmi-user ipmi-user-name |
Creates the specified endpoint user and enters organization IPMI access profile endpoint user mode.
| ||
Step 5 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # set password |
Sets the password for the endpoint user. After entering the set password command, you are prompted to enter and confirm the password. For security purposes, the password that you type does not appear in the CLI. | ||
Step 6 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # set privilege {admin | readonly} |
Specifies whether the endpoint user has administrative or read-only privileges. | ||
Step 7 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # commit-buffer |
Commits the transaction to the system configuration. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create ipmi-access-profile ReadOnly UCSC(policy-mgr) /org/ipmi-access-profile* # create ipmi-user bob UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # set password Enter a password: Confirm the password: UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # set privilege readonly UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # commit-buffer UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user #
Include the IPMI profile in a service profile and/or template.
Deleting an IPMI Access Profile
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete ipmi-access-profile profile-name |
Deletes the specified IPMI access profile. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example deletes the IPMI access profile named ReadOnly:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # delete ipmi-access-profile ReadOnly UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Adding an Endpoint User to an IPMI Access Profile
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . | ||
Step 3 | UCSC(policy-mgr) /org # scope ipmi-access-profile profile-name |
Enters organization IPMI access profile mode for the specified IPMI access profile. | ||
Step 4 | UCSC(policy-mgr) /org/ipmi-access-profile # create ipmi-user ipmi-user-name |
Creates the specified endpoint user and enters organization IPMI access profile endpoint user mode.
| ||
Step 5 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # set password |
Sets the password for the endpoint user. After entering the set password command, you are prompted to enter and confirm the password. For security purposes, the password that you type does not appear in the CLI. | ||
Step 6 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # set privilege {admin | readonly} |
Specifies whether the endpoint user has administrative or read-only privileges. | ||
Step 7 | UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user # commit-buffer |
Commits the transaction to the system configuration. |
The following example adds an endpoint user named alice to the IPMI access profile named ReadOnly:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org* # scope ipmi-access-profile ReadOnly UCSC(policy-mgr) /org/ipmi-access-profile* # create ipmi-user alice UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # set password Enter a password: Confirm the password: UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # set privilege readonly UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user* # commit-buffer UCSC(policy-mgr) /org/ipmi-access-profile/ipmi-user #
Deleting an Endpoint User from an IPMI Access Profile
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # scope ipmi-access-profile profile-name |
Enters organization IPMI access profile mode for the specified IPMI access profile. |
Step 4 | UCSC(policy-mgr) /org/ipmi-access-profile # delete ipmi-user epuser-name |
Deletes the specified endpoint user from the IPMI access profile. |
Step 5 | UCSC(policy-mgr) /org/ipmi-access-profile # commit-buffer |
Commits the transaction to the system configuration. |
The following example deletes the endpoint user named alice from the IPMI access profile named ReadOnly:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # scope ipmi-access-profile ReadOnly UCSC(policy-mgr) /org/ipmi-access-profile # delete ipmi-user alice UCSC(policy-mgr) /org/ipmi-access-profile* # commit-buffer UCSC(policy-mgr) /org/ipmi-access-profile #
Serial over LAN Policy
The serial over LAN policy (SOL) configures a serial over LAN connection for all servers associated with service profiles that use the policy. By default, the serial over LAN connection is disabled.
If you implement a serial over LAN policy, we recommend that you also create an IPMI profile.
You must include this policy in a service profile and that service profile must be associated with a server for it to take effect.
Configuring a Serial over LAN Policy
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr) # scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. | ||
Step 3 | UCSC(policy-mgr) /org # create sol-policy policy-name |
Creates a serial over LAN policy and enters organization serial over LAN policy mode. | ||
Step 4 | UCSC(policy-mgr) /org/sol-policy # set descr description | (Optional)
Provides a description for the policy.
| ||
Step 5 | UCSC(policy-mgr) /org/sol-policy # set speed {115200 | 19200 | 38400 | 57600 | 9600} |
Specifies the serial baud rate. | ||
Step 6 | UCSC(policy-mgr) /org/sol-policy # {disable | enable} |
Disables or enables the serial over LAN policy. By default, the serial over LAN policy is disabled; you must enable it before it can be applied. | ||
Step 7 | UCSC(policy-mgr) /org/sol-policy # commit-buffer |
Commits the transaction to the system configuration. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create sol-policy Sol9600 UCSC(policy-mgr) /org/sol-policy* # set descr "Sets serial over LAN policy to 9600 baud." UCSC(policy-mgr) /org/sol-policy* # set speed 9600 UCSC(policy-mgr) /org/sol-policy* # enable UCSC(policy-mgr) /org/sol-policy* # commit-buffer UCSC(policy-mgr) /org/sol-policy #
Viewing a Serial over LAN Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
Step 3 | UCSC(policy-mgr) /org # show sol-policy policy-name |
Displays the serial over LAN definition (set by the create sol-config command). If the serial over LAN definition is not set, and if a policy is set (using the set sol-policy command), then the policy will be displayed. |
The following example shows how to display serial over LAN information for a serial over LAN policy called Sol9600:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # show sol-policy Sol9600 SOL Policy: Full Name: Sol9600 SOL State: Enable Speed: 9600 Description:
iSCSI Adapter Policy
- Creating an iSCSI Adapter Policy
- Deleting an iSCSI Adapter Policy
- Creating an iSCSI Authentication Profile
- Deleting an iSCSI Authentication Profile
Creating an iSCSI Adapter Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # create iscsi-policy policy-name |
Creates the iSCSI adapter policy. |
Step 4 | UCSC(policy-mgr) /org/iscsi-policy # set descr "description" | (Optional)
Provides a description for the iSCSI adapter policy. |
Step 5 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item connection-timeout timeout-secs |
The number of seconds until Cisco UCS Central assumes that the initial login has failed and the iSCSI adapter is unavailable. Enter an integer between 0 and 255. If you enter 0, Cisco UCS Central uses the value set in the adapter firmware (default: 15 seconds). |
Step 6 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item dhcp-timeout timeout-secs |
The number of seconds to wait before the initiator assumes that the DHCP server in unavailable. Enter an integer between 60 and 300 (default: 60 seconds). |
Step 7 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item lun-busy-retry-count num |
The number of times to retry the connection in case of a failure during iSCSI LUN discovery. Enter an integer between 0 and 60. If you enter 0, Cisco UCS Central uses the value set in the adapter firmware (default: 15 seconds). |
Step 8 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item tcp-time-stamp {no | yes} |
Specifies whether to apply a TCP timestamp. With this setting, transmitted packets are given a time stamp of when the packet was sent so that the packet's round-trip time can be calculated, when needed. This setting applies only to Cisco UCS M51KR-B Broadcom BCM57711 adapters. |
Step 9 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item hbamode {no | yes} |
Specifies whether to enable HBA mode. This option should only be enabled for servers with the Cisco UCS NIC M51KR-B adapter running the Windows operating system. |
Step 10 | UCSC(policy-mgr) /org/iscsi-policy # set iscsi-protocol-item boottotarget {no | yes} |
Specifies whether to boot from the iSCSI target. This option only applies to servers with the Cisco UCS NIC M51KR-B adapter. It should be disabled until you have installed an operating system on the server. |
Step 11 | UCSC(policy-mgr) /org/iscsi-policy # commit-buffer |
Commits the transaction to the system configuration. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCS-AUCSC(policy-mgr)UCS-A /org # create iscsi-policy iscsiboot UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item connection-timeout 60 UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item dhcp-timeout 200 UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item lun-busy-retry-count 5 UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item tcp-time-stamp yes UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item hbamode yes UCSC(policy-mgr) /org/iscsi-policy* # set iscsi-protocol-item boottotarget yes UCSC(policy-mgr) /org/iscsi-policy* # commit-buffer UCSC(policy-mgr) /org/iscsi-policy #
Include the adapter policy in a service profile and/or template.
Deleting an iSCSI Adapter Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete iscsi-policy policy-name |
Deletes the iSCSI adapter policy. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete an iSCSI adapter policy named iscsi-adapter-pol:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # delete iscsi-policy iscsi-adapter-pol UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Creating an iSCSI Authentication Profile
If you use authentication for iSCSI boot, you need to create an authentication profile for both the initiator and target.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # create auth-profile profile-name |
Creates an authentication profile with the specified name. The name can be up to 16 alphanumeric characters. |
Step 4 | UCSC(policy-mgr) /org/auth-profile # set user-id id-name |
Creates a log in for authentication. |
Step 5 | UCSC(policy-mgr) /org/auth-profile # set password |
Creates a password for authentication. |
Step 6 | UCSC(policy-mgr) /org/auth-profile # commit-buffer |
Commits the transaction to the system configuration. |
Step 7 | UCSC(policy-mgr) /org/auth-profile # exit |
Exits the current mode. |
Step 8 | Repeat steps 3 through 7 to create an authentication profile for the target. | |
Step 9 | UCSC(policy-mgr) /org/auth-profile # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to create an authentication profile for an initiator and a target:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org UCSC(policy-mgr) /org # create auth-profile InitAuth UCSC(policy-mgr) /org/auth-profile* # set user-id init UCSC(policy-mgr) /org/auth-profile* # set password Enter a password: Confirm the password: UCSC(policy-mgr) /org/auth-profile* # commit-buffer UCSC(policy-mgr) /org/auth-profile # exit UCSC(policy-mgr) /org # create auth-profile TargetAuth UCSC(policy-mgr) /org/auth-profile* # set user-id target UCSC(policy-mgr) /org/auth-profile* # set password Enter a password: Confirm the password: UCSC(policy-mgr) /org/auth-profile* # commit-buffer UCSC(policy-mgr) /org/auth-profile # exit
Create an Ethernet vNIC for use as the overlay vNIC for the iSCSI device. Then create an iSCSI vNIC.
Deleting an iSCSI Authentication Profile
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr) # scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete auth-profile profile-name |
Deletes the specified iSCSI authentication profile. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example shows how to delete an iSCSI authentication profile and commit the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org UCSC(policy-mgr) /org # delete auth-profile InitAuth UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Local Disk Policy
This policy configures any optional SAS local drives that have been installed on a server through the onboard RAID controller of the local drive. This policy enables you to set a local disk mode for all servers that are associated with a service profile that includes the local disk configuration policy.
The local disk modes include the following:
- Guidelines for all Local Disk Configuration Policies
- Guidelines for Local Disk Configuration Policies Configured for RAID
- Creating a Local Disk Configuration Policy
- Viewing a Local Disk Configuration Policy
- Deleting a Local Disk Configuration Policy
Guidelines for all Local Disk Configuration Policies
Before you create a local disk configuration policy, consider the following guidelines:
No Mixed HDDs and SSDs
Do not include HDDs and SSDs in a single server or RAID configuration.
Do Not Assign a Service Profile with the Default Local Disk Configuration Policy from a B200 M1 or M2 to a B200 M3
Due to the differences in the RAID/JBOD support provided by the storage controllers of B200 M1 and M2 servers and those of the B200 M3 server, you cannot assign or re-assign a service profile that includes the default local disk configuration policy from a B200M1 or M2 server to a B200 M3 server. The default local disk configuration policy includes those with Any Configuration or JBOD configuration.
JBOD Mode Support
The B200 M3 server supports JBOD mode for local disks.
Note | Only B200 M1, B200 M2, B200 M3, B250 M1, B250 M2 and B22 M3 blade servers support the JBOD mode for local disks. |
Guidelines for Local Disk Configuration Policies Configured for RAID
Configure RAID Settings in Local Disk Configuration Policy for Servers with MegaRAID Storage Controllers
If a blade server or integrated rack-mount server has a MegaRAID controller, you must configure RAID settings for the drives in the Local Disk Configuration policy included in the service profile for that server. You can do this either by configuring the local disk configuration policy in the service profile using one of the defined RAID modes for that server, or you can use the Any Configuration mode with the LSI Utilities toolset to create the RAID volumes.
If you do not configure your RAID LUNs before installing the OS, disk discovery failures might occur during the installation and you might see error messages such as “No Device Found.”
Server May Not Boot After RAID1 Cluster Migration if Any Configuration Mode Specified in Service Profile
After RAID1 clusters are migrated, you need to associate a service profile with the server. If the local disk configuration policy in the service profile is configured with Any Configuration mode rather than RAID1, the RAID LUN remains in "inactive" state during and after association. As a result, the server cannot boot.
To avoid this issue, ensure that the service profile you associate with the server contains the identical local disk configuration policy as the original service profile before the migration and does not include the Any Configuration mode.
Do Not Use JBOD Mode on Servers with MegaRAID Storage Controllers
Do not configure or use JBOD mode or JBOD operations on any blade server or integrated rack-mount server with a MegaRAID storage controllers. JBOD mode and operations are not intended for nor are they fully functional on these servers.
Maximum of One RAID Volume and One RAID Controller in Integrated Rack-Mount Servers
A rack-mount server that has been integrated with Cisco UCS Manager can have a maximum of one RAID volume irrespective of how many hard drives are present on the server.
All the local hard drives in an integrated rack-mount server must be connected to only one RAID Controller. Integration with Cisco UCS Manager does not support the connection of local hard drives to multiple RAID Controllers in a single rack-mount server. We therefore recommend that you request a single RAID Controller configuration when you order rack-mount servers to be integrated with Cisco UCS Manager.
In addition, do not use third party tools to create multiple RAID LUNs on rack-mount servers. Cisco UCS Manager does not support that configuration.
Maximum of One RAID Volume and One RAID Controller in Blade Servers
A blade server can have a maximum of one RAID volume irrespective of how many drives are present in the server. All the local hard drives must be connected to only one RAID controller. For example, a B200 M3 server has an LSI controller and an Intel Patsburg controller, but only the LSI controller can be used as a RAID controller.
In addition, do not use third party tools to create multiple RAID LUNs on blade servers. does not support that configuration.
Number of Disks Selected in Mirrored RAID Should Not Exceed Two
If the number of disks selected in the Mirrored RAID exceed two, RAID 1 is created as a RAID 10 LUN. This issue can occur with the Cisco UCS B440 M1 and B440 M2 servers.
License Required for Certain RAID Configuration Options on Some Servers
Some Cisco UCS servers require a license for certain RAID configuration options. When associates a service profile containing this local disk policy with a server, verifies that the selected RAID option is properly licensed. If there are issues, displays a configuration error during the service profile association.
For RAID license information for a specific Cisco UCS server, see the Hardware Installation Guide for that server.
B420 M3 Server Does Not Support All Configuration Modes
The B420 M3 server does not support the following configuration modes in a local disk configuration policy:
In addition, the B420 M3 does not support JBOD modes or operations.
Single-Disk RAID 0 Configurations Not Supported on Some Blade Servers
A single-disk RAID 0 configuration is not supported in the following blade servers:
Creating a Local Disk Configuration Policy
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . | ||
Step 3 | UCSC(policy-mgr) /org # create local-disk-config-policy policy-name |
Creates a local disk configuration policy and enters local disk configuration policy mode. | ||
Step 4 | UCSC(policy-mgr) /org/local-disk-config-policy # set descr description | (Optional)
Provides a description for the local disk configuration policy. | ||
Step 5 | UCSC(policy-mgr) /org/local-disk-config-policy # set mode {any-configuration | no-local-storage | no-raid | raid-0-striped | raid-1-mirrored | raid-5-striped-parity | raid-50-striped-parity-and-striped | raid-6-striped-dual-parity | raid-60-striped-parity-and-striped | raid-10-mirrored-and-striped} |
Specifies the mode for the local disk configuration policy. | ||
Step 6 | UCSC(policy-mgr) /org/local-disk-config-policy # set protect {yes | no} |
Set configuration protection to yes in order to prevent a service profile using this local disk policy from being associated to a server with a different physical disk configuration. If the service profile includes a local disk policy with configuration protection enabled, and there is an attempt to associate that service profile to a server that includes disks with a different local disk configuration, the association immediately fails and produces a configuration mismatch error.
| ||
Step 7 | UCSC(policy-mgr) /org/local-disk-config-policy # commit-buffer |
Commits the transaction to the system configuration. |
The following example configures a local disk configuration policy:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create local-disk-config-policy DiskPolicy7 UCSC(policy-mgr) /org/local-disk-config-policy* # set mode raid-1-mirrored UCSC(policy-mgr) /org/local-disk-config-policy* # set protect yes UCSC(policy-mgr) /org/local-disk-config-policy* # commit-buffer UCSC(policy-mgr) /org/local-disk-config-policy #
Viewing a Local Disk Configuration Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
Step 3 | UCSC(policy-mgr) /org # show local-disk-config-policy policy-name |
Displays the local disk policy. If you have not configured a local disk policy, the local disk configuration (created by the create local-disk-config command) displays. Displays the local disk definition (set by the create local-disk-config command). If the serial over LAN definition is not set, and if a policy is set (using the set local-disk-config-policy command), then the policy will be displayed. |
The following example shows how to display local disk policy information for a local disk configuration policy called DiskPolicy7:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # show local-disk-config-policy DiskPolicy7 Local Disk Config Policy: Name: DiskPolicy7 Mode: Raid 1 Mirrored Description: Protect Configuration: Yes
Deleting a Local Disk Configuration Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete local-disk-config-policy policy-name |
Deletes the specified local disk configuration policy. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example deletes the local disk configuration policy named DiskPolicy7 and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # delete local-disk-config-policy DiskPolicy7 UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
Scrub Policy
From Cisco UCS Central you can create scrub policy to determine what happens to local data and to the BIOS settings on a server during the discovery process, when the server is reacknowledged, or when the server is disassociated from a service profile.
Note | Local disk scrub policies only apply to hard drives that are managed by Cisco UCS Manager and do not apply to other devices such as USB drives. |
Depending upon how you configure a scrub policy, the following can occur at those times:
Disk scrub
One of the following occurs to the data on any local drives on disassociation:
BIOS Settings Scrub
One of the following occurs to the BIOS settings when a service profile containing the scrub policy is disassociated from a server:
FlexFlash Scrub
FlexFlash Scrub enables you to pair new or degraded SD cards, resolve FlexFlash metadata configuration failures, and migrate older SD cards with 4 partitions to single partition SD cards. One of the following occurs to the SD card when a service profile containing the scrub policy is disassociated from a server, or when the server is reacknowledged:
-
If enabled, the HV partition on the SD card is formatted using the PNUOS formatting utility. If two SD cards are present, the cards are RAID-1 paired, and the HV partitions in both cards are marked as valid. The card in slot 1 is marked as primary, and the card in slot 2 is marked as secondary.
-
If disabled, preserves the existing SD card settings.
Note |
|
Creating a Scrub Policy
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. | ||
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . | ||
Step 3 | UCSC(policy-mgr) /org # create scrub-policy policy-name |
Creates a scrub policy with the specified policy name, and enters organization scrub policy mode. | ||
Step 4 | UCSC(policy-mgr) /org/scrub-policy # set descr description | (Optional)
Provides a description for the scrub policy.
| ||
Step 5 | UCSC(policy-mgr) /org/scrub-policy # set disk-scrub {no | yes} |
| ||
Step 6 | UCSC(policy-mgr) /org/scrub-policy # set bios-settings-scrub {no | yes} |
| ||
Step 7 | UCSC(policy-mgr) /org/scrub-policy # commit-buffer |
Commits the transaction to the system configuration. |
The following example creates and enables a scrub policy named ScrubPolicy2 on servers using the scrub policy:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create scrub-policy ScrubPolicy2 UCSC(policy-mgr) /org/scrub-policy* # set descr "Scrub disk but not BIOS." UCSC(policy-mgr) /org/scrub-policy* # set disk-scrub yes UCSC(policy-mgr) /org/scrub-policy* # set bios-settings-scrub no UCSC(policy-mgr) /org/scrub-policy* # commit-buffer UCSC(policy-mgr) /org/scrub-policy #
Deleting a Scrub Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name. |
Step 3 | UCSC(policy-mgr) /org # delete scrub-policy policy-name |
Deletes the specified scrub policy. |
Step 4 | UCSC(policy-mgr) /org # commit-buffer |
Commits the transaction to the system configuration. |
The following example deletes the scrub policy named ScrubPolicy2 and commits the transaction:
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # delete scrub-policy ScrubPolicy2 UCSC(policy-mgr) /org* # commit-buffer UCSC(policy-mgr) /org #
vMedia Policy
A vMedia policy is used to configure the mapping information for remote vMedia devices. Two vMedia devices and mappings for CD and HDD are allowed in a vMedia policy. You can configure one ISO and one IMG at a time. ISO configurations map to a CD drive. IMG configurations map to a HDD device.
Note | If you want to map a device to a remote folder, you must create an IMG and map it as a HDD device. |
From Cisco UCS Central you can provision vMedia devices ISO images for remote UCS servers. Using Scriptable vMedia, you can programmatically mount IMG and ISO images on a remote server. CIMC mounted vMedia provides communications between other mounted media inside your datacenter with no additional requirements for media connection. Scriptable vMedia allows you to control virtual media devices without using a browser to manually map each Cisco UCS server individually.
Scriptable vMedia supports multiple share types including NFS, CIFS, HTTP, and HTTPS shares. Scriptable vMedia is enabled through BIOS configuration and configured through a Web GUI and CLI interface. You can do the following in the registered Cisco UCS domains using scriptable vMedia:
-
Boot from a specific vMedia device
-
Copy files from a mounted share to local disk
-
Install and update OS drivers
Note | Support for Scriptable vMedia is applicable for CIMC mapped devices only. Existing-KVM based vMedia devices are not supported. |
Creating a vMedia Policy
Command or Action | Purpose | |
---|---|---|
Step 1 | UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 | UCSC(policy-mgr)# scope org org-name |
Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
Step 3 | UCSC(policy-mgr) /org # create vmedia-policy policy-name |
Creates the specified vMedia policy and enters organization vMedia policy mode. |
Step 4 | UCSC(policy-mgr) /org/vmedia-policy # set retry-on-mount-fail {yes | no} |
Select whether the vMedia will continue mounting when a mount failure occurs. |
Step 5 | UCSC(policy-mgr) /org/vmedia-policy # create vmedia-mapping name |
Creates a vMedia policy sub-directory with the specified mapping name. |
Step 6 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set device-type {cdd | hdd} |
Specifies the remote vMedia image type that you wish to mount. |
Step 7 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set image-file-name filename |
Specifies the image file name. |
Step 8 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set image-path path |
Specifies the image path. |
Step 9 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set image-variable-name {none | service-profile-name} |
Specifies the name to be used for the image. This can be one of the following: |
Step 10 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set mount-protocol {cifs | http | https | nfs} |
Specifies the remote vMedia protocol. |
Step 11 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set auth-option {default | none | ntlm | ntlmi | ntlmssp | ntlmsspi | ntlmv2 | ntlmv2i} |
Specifies the remote authentication options. |
Step 12 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set password password |
Specifies the password. |
Step 13 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set remote-ip ip-address |
Specifies the remote IP address. |
Step 14 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # set user-id name |
Specifies the user ID for mounting the vMedia device. |
Step 15 | UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping # commit-buffer |
Commits the transaction to the system configuration. |
UCSC# connect policy-mgr UCSC(policy-mgr)# scope org / UCSC(policy-mgr) /org # create vmedia-policy vmediaPol2 UCSC(policy-mgr) /org/vmedia-policy* # create vmedia-mapping MapDir UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set device-type hdd UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set image-file-name win2011.iso UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set image-path /home/vMedia UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set password MyPass UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set remote-ip 10.0.0.0 UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # set user-id VMediaAdmin UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping* # commit-buffer UCSC(policy-mgr) /org/vmedia-policy/vmedia-mapping #