In the document I share the real experience of working with ViPR Controller in VNX + VPLEX environment.
In the short post I documented how to install ViPR Controller CLI if your Linux server doesn’t have direct access to Internet.
In the very extensive document I share the real experience of working with ViPR Controller in MetroPoint environment.
Here I posted the doc created to demonstrate how ViPR Controller works with MetroPoint.
Simple procedures to Deregister, delete and add HBA/WWN in ViPR Controller 2.2
All ViPR Controller 2.2 Services are described in the single Excel table.
By default, ViPR creates resources (such as zones and masking views) using global hard-coded naming convention. From ViPR C v2.2 we can override the default and provide our own naming convention for some types of resources.
Now subj is the one of my formal roles.
ViPR administration tasks are controlled by assigning Active Directory (AD) Users / Groups into Roles. Also, access to the ViPR resources can be controlled by assigning AD Users / Groups to the appropriate Access Control List (ACL).
Diagram that describes all network ports used by ViPR Controller.
Let’s check how ViPR Controller takes care about capacity consumed by log files.
I decided to check what ViPR admins will see in the case of one or two nodes fail.
ViPR CController configuration consists of dozens different entities. They are connected and interdependent very complicated ways. I decided to check if it is possible to draw the whole picture in one diagram. After several tries, I found that graph diagrams best suited for that purposes.