registering VMAX3 as storage failed after RP deployment

[DavidQY]

My customer currently has existing Vplex and VMAX3 environtment, and wanted to deploy RP.

Because of Networker requirements, they can only run RP 5.0.1. As a result, Vmax3 splitter is not supported. we need to use VPlex splitter instead.

During the configuration, customer requested to put RP repository on VMAX3 directly. so we created a masking view manually for the repository. We didn't use symrpi command , nor did we assign GK to the RPAs.

RP was built successfully. However in the RP GUI, when we tried to register VMAX3 as storage, it failed. Any idea why it failed? What's the purpose of registering storage?

The versions in the environtment are listed below. Thanks.

- RP Gen6 running 5.0.1

- Vplex VS6 running 6.0.1.04.00.09

- VMAX3 running 5977.1125.1125

[Idan]

Hi there,

First, the VMAX3 shouldn't be registered in this case. Second, why not to expose the repository through VPLEX ?

Regards,

Idan

[DavidQY]

Thanks Idan.

The reason the repository wasn't put behind vplex is that  it's a loaner Vplex and will eventually go away once Networker module supports RP 5.1 and Vmax3 splitter. 

We thought it would be relatively easier if we don't need to move RP repository back to VMAX3 when Vplex is removed. Do you see any issue configured this way?