When using JBOD, each physical disk had its own WWPN and FCID. The zoning configuration is for a server WWPN against disk WWPN so basically each server has its own disk.
Now for more advance storage systems (such as EMC) instead of physical disks to be mapped to servers we are mapping LUNs per server. I thought that for each LUN a WWPN and FCID are created and then you map the server to that LUN’s WWPN. Now I see that it does not work this way.
I have a UCS system with direct attached storage (EMC VNX5100). The active zoneset shows that all servers WWPNs are mapped to the same target WWPN (which is the EMC). There is a zone entry for each server.
So basically the result of that is that all servers can access the same target and the EMC controls the isolation of the LUNs from other servers.
If this is correct, then my question is why do I need the zoning configuration in this scenario ? why not set the default zone to permit and let EMC control LUN access?
BTW, this scenario of one storage system attached to the SAN is the same if we use Nexus 5k, so why bother and set zoning if the EMC can control the access to LUNs?
Zoning is used to isolate different environments. If there were no zones other than the default one, every server would "see" the rest and that could generate problems (for example, if one HBA started failing and resetting the link, a storm of RSCNs would be be spreaded throughout the Fabric in order to update all the devices of that failure. No multiply this behavior by number of Link resets a host can generate in a minute, and then we could have a nice issue in the SAN.
Most of the storage vendors (if not all) require single-initiator zoning, because it is the best way to prevent a misbehaving device from affecting the rest of the elements in the SAN.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...