Quick question regarding VSAN trunking. I have 2 6120 Fabric Interconnects and 2 MDS 9148's. Fabric-A is connected to MDS-1 and Fabric-B is connected to MDS-2 (4 4Gb links).
I have created 3 VSAN's on the MDS's and have configured the ports connected to the Fabric interconnects to trunk mode (VSAN trunking). I want to create a fiber channel on the UCS for the 6120 connections down to the MDS. (I know I need UCS version 1.4 to do this).
I'm wondering if I need to add the fc ports on the 6120 (4 each) to any particular VSAN (or create a new VSAN), or once I create a fiber channel and bundle them then they will trunk with the MDS's without a problem?
The functionality you describe is exactly what is provided in the 1.4.1 release.
The only caveat is a issue with any existing VSANs DomainIDs on your UCS system that fall into the range of 3840 to 4078. If you attempt to enable trunking and have VSANs in that DomainID range you will receive a warning that those VSANs will become disabled. If you proceed, they will go disabled and no longer pass traffic. All other allowed VSAN DomainIDs will continue to function properly.
This is a recent changed that was introduced with the MDS NX-OS 4.1 code. Which the UCS shares with at 1.4.1 for fc trunk
Regarding your question regarding what VSAN to put the end ports into. As you'll be starting in NPV mode, it's best to ensure proper connectivity by having the UCS and MDS end ports in the same VSAN. This will establish the link up properly and eliminate later physical level troubleshooting.
In UCS, trunk is disabled by default, see above for reason. Enabling UCS trunk mode is at the switch level, all uplink ports will be trunk enabled. In the MDS trunk mode is enabled at the interface level (individual link or port-channel). Once trunking is enabled on both sides, all VSAN from the UCS side are allowed. The MDS side can be trimmed to allow specific or a range of VSANs. Default on MDS is all VSANs.
As to what is best practice for what VSAN to put those end ports into, is a subject to debate. My best practice is to use VSAN 1, as VSAN 1 can never be deleted, which means the SAN port-channel will never lose it's native port.
Just wonder we recently try to add 2 M200 with firmware 4.1.1b, our UCS manager version is 4.0.2d, we got error said cannot donwgrade. I know we can update ucs manager from 4.0 to 4.1, bur wonder we can downgrade
OpenStack Neutron project offers pluggable framework means you can extend the capability of Neutron by orchestrating the Neutron functions to your upstream networking gears. For example, if you have provisioned a VLAN tagged Neutron network in Op...
https://soundcloud.com/user-327105904/s7e25-from-the-office-to-anywhere-empowering-secure-remote-work-with-cisco-vdi-solutions As organizations have had to rapidly respond and transition in the face of swift change, Cisco VDI solutions have enabled ...
In today’s fast paced digitization, Kubernetes enables enterprises to rapidly deploy new updates and features at scale while maintaining environmental consistency across test/dev/prod. Kubernetes lays the foundation for cloud-native apps which ca...
What can we collect before opening a case for Unified Computing System(UCS) ?
Serial Number and Part Details
UCS Server Serial Number : e.g. XXXXXXX in Serial number field. Check UCSM or CIMC
Product ID(PID) o...