Converting UCS Manager/Central Configuration
When you add a UCS device in the IMM Transition Tool and click Next, a utility runs in the backend that validates the hardware inventory and the configuration to check if the device is compatible with IMM.
It connects to the device and replicates the existing logical attributes. These include profiles, policies, pools, and templates.
After the successful completion of the Push to Intersight task, the Intersight application reflects the converted objects on refresh.
Assumptions for Conversion
Following are the assumptions for the conversion process in IMM Transition Tool:
-
Ethernet Network Control Policy - Ethernet Network Control Policy of Intersight can be created using two different sources of information of UCS Manager/Central.
-
Server vNICs - Maps to Network Control Policy of UCS Manager/Central
-
Appliance Ports - Maps to Appliance Network Control Policy of UCS Manager
While creating Ethernet Network Control Policy of Intersight using Network Control Policy of UCS Manager/Central, name of the Ethernet Network Control Policy of Intersight will be same as Network Control Policy of UCS Manager/Central.
While creating Ethernet Network Control Policy of Intersight using Appliance Network Control Policy of UCS Manager, name of the Ethernet Network Control Policy of Intersight will be suffixed with _appliance to the name of Network Control Policy of UCS Manager.
-
-
Ethernet Network Group Policy - There is no Ethernet Network Group Policy equivalent in UCS Manager/Central. Ethernet Network Group Policy details can be retrieved from VLAN Groups. Each VLAN Group will have VLAN details and those details will be used to create Ethernet Network Group Policy. Name of Ethernet Network Group Policy will be same as the name of VLAN Group.
-
Ethernet QoS Policy - QoS Policy of UCS Manager/Central is split into Ethernet and FC QoS Policies in Intersight.
-
Fibre Channel Network Policy - There is no Fibre Channel Network Policy equivalent in UCS Manager/Central. Fibre Channel Network Policy details can be retrieved while creating Server Profile (Intersight). The name of Fibre Channel Network Policy is derived from the names of SAN Connectivity Policy and vHBA.
-
Fibre Channel QoS Policy - QoS Policy of UCS Manager/Central is split into Ethernet and FC QoS Policies in Intersight.
-
IMC Access Policy - Creation of IMC Access Policy for a Service Profile in UCS Manager/Central which has different IP Pools for IPv4 and IPv6 Address in Inband Network Configuration is not supported currently. There is no IMC Access Policy equivalent in UCS Manager/Central. IMC Policy details can be retrieved from Service Profile. Each Service Profile will have Inband Network, IPv4 and IPv6 pool. Using this information IMC Access Policy will be created.
-
Name of the IMC Access Policy is derived using the names of Inband Network VLAN and Inband Pool. The name can be maximum of 64 Characters.
-
In UCS Manager/Central, there are separate options to pick IPv4 and IPv6 pools in Service Profile, but in Intersight there is only one option to pick the IP Pool in IMC Access Policy. Recommendation is to merge IPv4 and IPv6 Pools of UCS Manager/Central into a single Pool, before creating IMC Access Policy in Intersight. But this is not very straight forward to implement. During conversion, if there is a Service Profile with Inband IPv4 and IPv6 addresses belonging to two different IP Pools, then only IPv4 specific Pool will be considered for IMC Access Policy creation.
-
-
IPMI Over LAN Policy - IPMI Over LAN Policy of Intersight is mapped to IPMI Access Profiles in UCS Manager/Central. IPMI User-related information in IPMI Access Profile is moved to Local User Policy in Intersight.
-
iSCSI Boot Policy - There is no iSCSI Boot Policy equivalent in UCS Manager/Central. iSCSI Boot Policy details can be retrieved from Service Profile. Each Service Profile will have its own iSCSI vNICs section. Details of iSCSI vNIC will be available inside iSCSI Boot Parameters section of Service Profile. Using this information iSCSI Boot Policy will be created.
-
Name of the iSCSI Boot Policy is derived using the names of Service Profile and iSCSI vNIC.
-
In UCS Manager/Central, there is an option to provide the IQN Pool/Initiator Name for iSCSI vNICs Node as well as individual iSCSI vNICs. There is no such option in Intersight for individual iSCSI vNICs. In case of Intersight, IQN is at the LCP level (and not in vNICs).
-
Usually in UCS Manager/Central, there will be an option to create two iSCSI Boot Targets for a vNIC and each Target has its own CHAP details. But in Intersight, there is only one option to provide CHAP details for iSCSI Target.
-
For CHAP authentication, a default password will be considered during policy creation.
-
-
iSCSI Static Target Policy - There is no iSCSI Static Target Policy equivalent in UCS Manager/Central. iSCSI Static Target Policy details can be retrieved from Service Profile. Each Service Profile will have its own iSCSI Boot Parameters section. Using these iSCSI Boot Parameters, iSCSI Static Target Policy will be created in Intersight. For a single iSCSI interface, there can be multiple targets based on priority. Hence iSCSI target name is designed as a combination of Service Profile name, iSCSI interface name, and iSCSI target priority.
-
LAN Connectivity Policy - In UCS Manager/Central, vNIC can be configured in multiple ways:
-
Inline vNIC
-
Using Standalone vNIC
-
Using vNIC Templates
-
-
LAN Connectivity Policy
-
Using Standalone vNIC
-
Using vNIC Templates
-
In UCS Manager/Central, it can be either a LAN/SAN Connectivity Policy, or inline vNIC/vHBA that can be using vNIC/vHBA Templates or not. All possible combinations are considered and accordingly converted into LAN/SAN Connectivity Policies in Intersight, as it is the only way to configure connectivity.
-
-
Power Policy - In UCS Manager, the Power-related section of Global Policies are translated as a Power Policy to be used in Chassis Profiles in Intersight.
-
SD Card Policy - There is no SD Card Policy equivalent in UCS Manager/Central. This policy can be created by reading the information from Local Disk Configuration Policy of UCS Manager/Central. If there is Flexflash configured in Local Disk Configuration Policy of UCS Manager/Central, then an equivalent SD Card Policy will be created in Intersight.
-
Storage Policy-
-
Auto Deploy in Local LUN of Storage Profile
All Virtual Drives are Auto Deploy by default. If the option is set to no-auto-deploy, then the mapped VD in Service Profile and the Storage policy VD should have the same name. If the name is different, then it is an invalid configuration.
-
LUN Set in UCS Manager/Central is equivalent to Single Drive RAID Configuration in Intersight.
-
Merge all the disk slots in LUN Set into a single number array.
-
VD Configuration of all drives should be identical. If each LUN set has different VD Configuration, then flag it as invalid configuration.
-
-
M.2 Drive Configuration
-
LUN Size set to Unspecified in UCS Manager/Central should be only for Virtual Drives which has ExpandToAvail Flag set to True. If the Flag is set to False, it is an invalid Configuration.
-
Service Profiles in UCS Manager/Central which has Specific Storage Profile and Generic Storage Profile are merged to form a Single Storage Profile in Intersight.
-
-
VLAN Policy -
VLAN Policy of Intersight maps to VLAN Section in UCS Manager. In UCS Manager, there is an option to select the Fabric ID (A or B or Both) while creating the VLAN but same is not available in Intersight. As part of conversion, two different VLAN Policies get created if the Fabric ID value is set to A or B by suffixing Fabric ID to the name of VLAN Policy and single VLAN Policy gets created if the Fabric ID value is set to Both. You can also create a Private VLAN by choosing the sharing type as primary/isolated/community. Primary VLAN is a mandatory option. If it is not provided, Private VLAN configurations will be skipped. Thus, converting it to normal VLAN assigned with default Multicast Policy.
-
VSAN Policy -
VSAN Policy of Intersight maps to VSAN Section in UCS Manager. In UCS Manager, there is an option to select the Fabric ID (A or B or Both) while creating the VSAN but same is not available in Intersight. As part of conversion, two different VSAN Policies get created if the Fabric ID value is set to A or B by suffixing Fabric ID to the name of VSAN Policy and single VSAN Policy gets created if the Fabric ID value is set to Both.