Unsolved
This post is more than 5 years old
2 Intern
•
388 Posts
0
1914
May 24th, 2015 21:00
Minimum number of VMs required for ESRS VE ?
Hi,
We would like to implement ESRS VE.
From the Pre-install Checklist, my understanding is that we need at least 2 Servers (Vittual Machines)
1 x VE Gateway Server
1 x Monitoring Workstation for VNX Block and Clariion monitoring
Is it correct ?
Besides, if we would like to monitor Brocade Switch, does it mean that we need another Server (Virtual Machine) ?
No Events found!
gaharley
119 Posts
1
May 25th, 2015 06:00
If you have to have centralized monitoring, you would need to keep your ESRS IP Client for VNX for that purpose. To implement ESRSVE, you would need one VM for the ESRSVE. If you wanted to go to distributed monitoring, you could remove the ESRS IP Client for VNX and put manage the VNX and legacy CLARiiON arrays on the ESRSVE. If you wanted to use Policy Manager, you would need another VM or physical server for the Policy Manager. The Policy Manager is not available as a vApp. The Policy Manager cannot be collocated on the same VM as ESRSVE. The Brocade switches and any other EMC arrays would be managed by the ESRSVE. If you wanted high availability (EMC best practices), you would need an additional VM for the other ESRSVE.
TonyJK2
2 Intern
•
388 Posts
0
May 25th, 2015 16:00
Dear James,
Many thanks for your advice.
Currently we have already set up centralized monitoring with ESRS IP Client for both VNX5100 and CX4-120 SAN. Is there any advantage for us to change over to distributed management ?
If not, does it mean that we may consider updating the version of IP Client we are using (2.08.10.00) ?
Regards
ryanbrancel1
53 Posts
0
May 26th, 2015 09:00
The ESRS IP Client can be updated, often times over the top of the existing install without issue. For CX4 systems it is still recommended to use IP Client to take advantage of the additional alerting functionality (centralized monitoring). For VNX arrays, that improved alerting functionality has been integrated in to existing code base, so IP Client is not as necessary. As always it is recommended to update to target system code on both arrays twice per year.