We are configurating one Flexpod solution.
UCS 6296UP with Fas8020 Ontap 8.3 Direct Attached Storage for NFS
This is the information found
We are create the "appliance ports" but this are in error.
Error: ENM source pinning failed
Solved! See The Solution
It's going to be hard to troubleshoot with out many details on the configuration. To start with, make sure that the VLAN you have configured on the Appliance port exsits in both the LAN Cloud and Appliance sections.
This blog post describes nicely solving the issue, which quite likely is due to VLAN discrepancies:
I am test with this configuration but the ports are in fail.
is it necesary some special parameters in NetApp (Ontap:8.3)?
I detec what when I configure with "Set Ethernet Swiching Mode" the port are up but in normal mode "End-Host Mode"they are in fail.
There shouldn't be any special configuration you'll need on the NetApp side.
Did you test the VLAN issue mentioned?
Yes I configure same VLAN in two level and It's not sufficient.
Only changing mode, system reboot but I think this is not good solution.
This is how it is configured.
UCSM is in 2.1(3e) version and NetApp in 8.3
Same issue here. Configured the vlans in both (lan cloud and appliances).
Port is in failed mode:
|Additional Info||:||ENM source pinning failed|
My error was I not had any server created. When I create a server with vNic in this Vlan the port are turn up in "storage port" mode.
Other question, If Netapp port are in ifgroup in Fabric Interconet with port channel?
Im having the same problem.
Can i confirm that you resolved this by deploying a service profile on a blade that made use of the storage appliance vlan via a vNic Template and that fixed the error ?
Yes this is the solution. The system need link.
I know that this is a mildly dated thread, however, I've just ran into this issue at a client site where we were making a number of modifications to SnapMirror configurations with a direct-attached to UCS setup and the fix was not to add the new NetApp VLAN to a Service Profile vNIC. The fix was to navigate to each of the appliance ports (in our case just one per fabric) and verify that the newly-created Appliance VLAN was actually checkmarked to enable it on the Applianct Ports. It did also have to be in both the Appliance Cloud and the LAN Cloud as a Global VLAN.
Thanks Chris. In my case the issue was that I didn't create the same VLAN in the LAN cloud but only created in appliance cloud. Hence it failed. Issue got resolved after creating the same VLAN in LAN cloud after referring your solution.
We view the NetApp interfaces are CNA so we are testing with Fcoe Sotorage port. Is it right this option?
How confirure the vlans?