I have often wondered exactly what you can do with SAN Device Virtualisation (SDV). I have not got around to playing with it but you can virtualise an initiator to give it a virtual pWWN. I wonder can you have multiple pWWNs with SDV?
The design of SDV was around target virtualization. If an array has 2 ports, and one is the primary, and it fails, all the hosts must be re-zoned with the back up port. Host like HP-UX and AIX would see a change in FCID which can cause time to resolve. With SDV we virtualize the primary pwwn and back up pwwn to a v-pwwn. We then zone the hosts with the v-pwwn. In the config we link the v-pwwn to the primary. If that fails, we change the link to map the p-wwn to the back up port. The hosts see no change in their target pwwn or FCID...no re-zoning is needed. You can map the v-pwwn to multiple real pwwns, but the link can only be active to one at a time. We do support SDV for initiators as well. The enhancement on that end is that if an HBA is replaced, we do not need to update the fabric zoning or the array security software. We change the link on the v-pwwn to map from the new HBA pwwn to the v-pwwn. The array sees no change in the host pwwn or FCID. Again, no zoning changes are needed.
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...