Just a quick post to share one problem resolution on the VNXe 3100. While creating a shared folder on a test VNXe I encountered an error – One or more specified parameters are invalid. (Error Code:0x5). The problem was related to the array not being able to communicate on the network but since the error is not clear the resolution is not obvious. It wasn’t a problem with the array itself.
Steps –> to create a shared folder first you have to create its settings. When you create the shared server name and IP address at that time you pick whether the share will be presented to a Linux Host or Windows Host. At that time if you continuously get an error don’t call EMC first. Try this —
VNXe 3100 does not offer an option to add the gateway IP right in the window where you enter the IP for the iSCSI server. For that you need to go to Settings –> More Settings –> Manual Routing –> add the gateway ip (under routing). Then add a host that should be ideally on the same subnet (you have to pick the host option and not routing) and try to ping it. All these options are available right in the manual routing area.
If the ping does not work then go back to iSCSI server setting and make sure that you remove the VLAN ID (depending on your environment things may even work with the VLAN ID in place). Perform a ping test – if that works then go ahead.
In the shared folder system settings pick Windows as the option –> enter domain –> enter DNS –> enter user id and password (leave the OU area blank).
After you remove/add the VLAN id (depending on your environment) you will observe that communication is now working and the array is able to register the share in AD (treats it like a virtual server).
You can then create the shared folder and present it. It works flawlessly for both linux and windows OS. In fact, it’s a great feature to share out a disk to both linux and windows hosts – (wink wink..) consolidate your physical file server and map out straight from the array.
The shared folder can also be replicated using EMC remote protection suite license without the need for replication manager license. With any other presentation (e.g. VMFS) you need to involve replication manager alongwith remote protection suite.
Hope this helps anyone looking for this resolution. If it does help please do drop a comment. I would be interested to hear from you.