All cross connected for redundancy. However, I am not seeing any logins to the second SAN switch when I boot a blade. I looked at all the vSAN config's etc., and it looks good and was wondering if anoyne had any other ideas?
My first suggestion would be is to make things one for one from the FI's to the Brocades. Makes things easier to troubleshoot and brings less complexity.
In my opinion it is overkill for redundancy, you have that at the array level. Unless you have a special reason for the bow-tie connection, go FI A to switch A and the same on the B side. Ensure your switches are in NPIV mode so wwpn can be passed through FI's and FC switches.
When you are talking SAN and say "Cross Connected" for redundancy it kind of freaks me out.
Topology should be
FIA => BrocadeA
FIB => BrocadeB
BrocadeA and BrocadeB should Never cross paths.
You would have two vHBA's per Service Profile.
Would look like this:
vHBA_A => FIA => BrocadeA
vHBA_B => FIB => BrocadeB
The nameservers on each Brocade should only see the WWPN's for the vHBA's on their fabric.
BUT to maybe answer the question you actually asked, the vHBA template will assign either fabric A or B. That is why you need two vHBA's for a dual fabric. If you want to see logins on both switches make sure you create a vHBA_A and vHBA_B set to corresponding Fabric/FI.
Read again, I said what you said. DO NOT CROSS THE CABLES when going from fi to fabric switch, so you must have mis-read my comment. It is a one for one , fi a to San switch a and the same on the b side.
Was trying to get neworking to work on a new Ubuntu install on a UCS server. I did a "shutdown -r" and rebooted the server. Now it seems to be stuck in the Aptio setup utility. I either choose "save and exit" or exit without saving changes and I am brough...
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 ...