Highlighted
2 Bronze

vipr 2.3 controller 1 VM Restrictions

Hallo, I installed the vipr controller 1 VM in our vCenter.

Now I have problems getting the Fabric Controller (Brocade) included.

Error message: Failed to get version: Unable to connect to device Brocade SMI-S: Unable to connect to ip 10.10.66.56 on port 5988.

the SMI-S Agent ist started and is on a different VM as the VNX Block provider.

In former vipr version I installed the 2+1 VM and there where no problems at all.

Are there any restrictions related to the 1 VM installation of vipr 2.3?

Labels (1)
0 Kudos
7 Replies
Highlighted
2 Iron

Re: vipr 2.3 controller 1 VM Restrictions

I haven't had experience with that specific installation, but I do see that error message regularly when I try to discover Brocades when I forget to enable SSL in ViPR Provider discovery panel (port 5988 IIRC is no-ssl). Can you please retry with SSL enabled?

0 Kudos
Highlighted

Re: vipr 2.3 controller 1 VM Restrictions

As mentioned..  Be sure you are using either SSL and 5989 or no-SSL and 5988.  Are you sure that the CMCNE version you are using is supported with ViPR 2.3?  Check the support matrix which currently shows..

CMCNE version 11.2.1, 12.0.3, 12.1.2, 12.1.5

Are you able to telnet to the SMI-S port 5988 from a command line?

0 Kudos
Highlighted
2 Bronze

Re: vipr 2.3 controller 1 VM Restrictions

Hallo,

I solved the problem.

I had to disable the Windows Domain Firewall on the provider host.

Now the fabric Manager is detected.

The next Problem arises:

When I want to add the VNX for File I get the following error message:

Discovery Status
Discovery failed for Storage System: urn:storageos:StorageSystem:7591933c-c336-4784-bb7e-705fc0a6c9d9:vdc1 because Failed to connect to 10.10.66.30
I used the IP Adress of the control station and the nasadmin account. for the storage host and and the provider.
I also used SSL for the provider.
0 Kudos
Highlighted
3 Zinc

Re: vipr 2.3 controller 1 VM Restrictions

For VNX file with SSL enabled you need access on port 443 and port 5989. Have you confirmed that you can communicate to the CS on these ports?

Maybe ECOM is not enabled? Use EMC KB 15461 on how to check.

0 Kudos
Highlighted
3 Argentum

Re: vipr 2.3 controller 1 VM Restrictions

Did you figure this out for VNX file discovery?

0 Kudos
Highlighted
2 Bronze

Re: vipr 2.3 controller 1 VM Restrictions

Rich is on point. I would suspect that the either the SSL or CMCNE version is incorrect or a port number was fat fingered. I do it all the time.

0 Kudos
Highlighted
Not applicable

Re: vipr 2.3 controller 1 VM Restrictions

test

0 Kudos