White Papers

Profile Management and Deployment Enhancements in OpenManage Enterprise 3.4 |438
An additional performance improvement include the ability to affect changes to VLAN assignment without
server reboots. With OME 3.4, if changes to VLAN assignments to NIC ports in a template are made, the
changes can be propagated to modular servers that the template had been previously deployed to without
requiring a server reboot.
Easier OME-M workflows: VLAN assignment changes can be propagated to modular sleds in the
NGM chassis, w/o a reboot of the sleds (Propagate checkbox).
The user can also specify if all parameters of VLANs should be matched (use strict checking) or simply best
match (name and QoS only) should be used during propagation.
2.5 Troubleshooting issues
Symptom
What to check
Not all devices in the
device picker can be
targeted for profile
deployment.
• Check if another profile is already deployed to the target that cannot be
selected. For example, if a profile P1 is assigned to a device D1, another
profile P2 cannot be assigned to D1, without unassigning P1 from D1.
• Check task execution service logs.
Deployment cannot be
configured successfully (no
deployment job created).
• Check the application log for basic payload validation and task creation
errors.
Deployment job is created
but the deployment fails.
• Check the task execution service log for causes (specifically if there are
attribute processing failures, connection errors, errors with identity
assignment, and so on).