I am trying to understand read only zoning - particularly this statement in the MDS 9000 Guide:
"If two members belong to a read-only zone and to a read-write zone, the read-only zone takes priority and write access is denied."
What I am wanting to do is this - I have ESXi servers that are zoned to see my storage ports on my SAN, now I want to zone a Windows server to see those same storage ports on the SAN so that it can read those LUN's and perform backups of them. I want the Windows server to see them as read-only though. I am not sure how to interpret the statement above - does it mean that since my storage ports are in multiple zones where they are normally read-write but now they are also in a zone where they are read-only that they will only by read-only in all zones? That doesn't seem like it should work that way but I have never configured a read-only zone so I don't really understand.
So that I am clear my two zones are below - the only difference in them is the first member (which is my ESX host) all the other members are the same storage ports on the same SAN. So in this case if Zone 1 is read-only and Zone 2 is default read-write does that mean that the storage ports would be read only in both zones?
Other than what was posted here no. I am assuming from the answer that was supplied that I could not accomplish what I needed. We were trying to implement Symantec Netbackup to backup our vm's and we have not moved forward yet. We are planning on doing it second half of this year and based on above we have two options - one, let the Symantec server (Windows) have read/write to the volumes and hope the backup administrator doesn't do something damaging or two, don't backup over the SAN and configure it for network based backups which doesn't require us to do the zoning.
I recently needed to implement something similar. My take on it is that if you have 2 conflicting zones, with the same initiator and targets in them... the some conflict resolution needs to happen... in this case the most restrictive (read-only) wins. I wanted to test this, but activating the zoneset failed.
The error was Activation Failed on VSAN:x Reason: Unkown: 25, domain id:#
Long story short, MDS 5.0 and above have removed the read-only zoning feature.
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...