When creating the a vPC on a pair of N5548UP’s how should the channel group mode be set when connecting to a Emulex CNA with the ports attached to a the N1K?
I have configured the mode as “active”, however, when the server is booted and the physical ports come up the channel group is operationally down stating no operational members. I am sure this is due to no lacp negotiation on the trunk. Please note the server does not have ESXi or the N1KV installed as yet, I am in the process of configuring boot from SAN. I am wondering if the trunk would come up once the N1KV was installed with “channel-group x mode active”, however, where does this put me while the system is booting and attempting to access the FC storage.?
Since you do not have any OS on the server yet, it cannot send LACP frames and hence your port-channel will not come up and vFC associated with the port-channel will not come up either. You have couple options
1)Do not use LACP channel. Use individual interfaces or ON mode channel
2)If you are running 5.1(3)N1(1) and later on your Nexus 5548, you have an option of binding vFC to physical ethernet. In older NX-OS you did not have this option once the physical ethernet is in a port-channel.
Great, thanks for the response. I thought this would be the case, however, I thought that if using a port channel with the N1Kv the mode NEEDED to be “active”.... Obviously I was incorrect here. I will use mode “on” as I require the use of a port channel.
In an environment in which you boot from san via a CNA then the vPC must always be a configured as a static port channel (mode on)?? If using LACP and no LACP PDUs are received by the N5Ks is it not the case that the port channel is disabled and the member ports act as individual ports? If this was the case could the fcoe would still boot from SAN then the vPC would come up once the N1K was loaded on the hosts??????
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...