Just getting wet around the ears on the Nexus line and have two small labs with a couple simple questions:
1. Single N5K.
2. Cisco UCS C-Series C220 M3 w/VIC1225.
3. VNX SAN
As a test, I would like to leverage the NIC virtualization technology to "unify" both normal LAN and iSCSI traffic. Obviously wouldn't be using vPC as I only have a single switch in this lab. Should this be possible is my only question? Just looking for reassurance.
1. Two N5K w/L3
3. Two B22 FEX Modules
4. Dell M620 w/QLogic 10GB CNA
5. VNX SAN
As a test, I would like to leverage the NIC virtualization technology to "unify" both normal LAN and iSCSI traffic as well as vPC. Has anyone successfully connected QLogic vNICs to N5K with vntag on the switchport?
Sorry for the noob questions but really want to ensure I don't start this by banging my head early.
Thanks for the reply. Truly appreciated. In regards to question #2, is there any way to "virtualize" the two types of traffic on a single wire without vntag? It would be ideal to run both LAN and iSCSI traffic this way utilizing the CNA HBA functions for SAN traffic while using the same pipe for data. If not, that is too bad and I'll have to utilize two wires, I suppose.
Padma, again thanks for the feedback but I think I must still be missing something. Here is what I have:
1. Dell M620 Blade server
2. QLogic CNA with iSCSI HBA offloading capabilities (Dual 10GB ports) - 8200 series I believe
3. Pair of Cisco Nexus B22 FEX in Dell chassis
4. Pair of Cisco N5Ks
I want to utilize the dual 10GB ports for both LAN and iSCSI rather than using an completely separate NIC in another fabric slot of my chassis. This would reduce my cabling, power, etc. With that said, are you saying all I need to do is create a separate VLAN for iSCSI, have the CNA iSCSI HBA offload the processing and have the N5Ks provide QoS to that specific iSCSI VLAN? Is it that simple?
Does the above layout and questions sound reasonable or am I missing something in this proposed configuration? I'm about ready to embark on this solution and was hoping for some reassurance. Thanks in advance!
>> With that said, are you saying all I need to do is create a separate VLAN for iSCSI, have the CNA iSCSI HBA offload >> the processing and have the N5Ks provide QoS to that specific iSCSI VLAN? Is it that simple?
Yes, you don't need seperate physical NIC card for iSCSI traffic.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...