The answer depends.
There are certain configuration items that are adapter-specific such as Option ROM, firmware bundles, max # of vNIC/vHBA etc. If you have a service profile configured with one or two vNICs and/or vHBA, you can safely migrate the service profile from any blade with a Menlo adapter (Emulex or Qlogic) to a blade with a Palo (M81KR VIC) adapter.
Conversly, if you try to migrate from a Palo to a Menlo adapter based blade, and you've exceeded the target adapter's capabilities, then the association will fail with an error such as "Insufficient resources" or similar. Palo can support up to 128 virtual adapters, where Menlo has a hard limit of 2 vNICs and 2 vHBAs.
Another item to note, is that for Menlo based adapters, you must include the Option ROM Host firmware bundle if you plan on having your Service Profile SAN boot. With Palo, the firmware is "built in" and does not require a separate option rom Host firmware bundle to be part of the Service Profile. Palo will automatically load it's own option ROM when the profile has been configured with a SAN boot target.
Regards,
Robert
