Depends if you intend on using FC Trunking. If yes, then you would need to enable FC trunking on the FI and on the MDS By default ports are not trunking and will be configured for a single VSAN only.
On the FI, the FC Uplink port will not come up unless the VSANs match on both sides, or trunking has been correctly configured. You can assign a port to a particular VSAN by selecting it from the Hardware Tab and highlighting the port, and assigning it to a configured VSAN on the right pane. Ensure your required VSANs have been configured on the FI first under the VSAN tab. You should consult your Storage Admin for which VSANs are in use on the upstream MDS.
As I said, if you're not using Trunking you just have to make sure the interface is configured for the appropriate VSAN - on both the FI and MDS sides.
From your MDS - first know exactly which port(s) go to your Fabric Interconnect. Normally a topology would be for a single FI to connect to one MDS, and the other FI to connect to the 2nd MDS. Most SAN admins design split fabrics - even if they happen to use the same single VSAN ID.
1. From the MDS find out which VSAN your interface is assigned to:
MDS# show vsan membership
(VSANs and assigned interfaces will be displayed.)
2. Confirm your interface is configured as a Fabric port
show run int x/y
switchport mode F
3. Next go to UCS, find the corresponding interface on the Fabric Interconnect, ensure the same VSAN above has already been created as a Global VSAN, and then highlight the port in the Equipment Tab, and use the drop down box to assign the appropriate VSAN.
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...