Management of solution packs (SP) on distributed collectors in the internal zone, and SRM Gate collectors in the DMZ, is performed from the frontend’s admin UI. A frontend server located in the external zone can access servers in the internal zone thanks to firewall rules implemented on SRM Gate servers. Servers in the DMZ are directly reachable by the servers in the external zone.
Install any relevant solution packs on distributed collectors if they are not already deployed.
Time-series data generated by solution packs on distributed collectors in the internal zone must be pushed towards SRM Gate’s LBC, which further pushes data to Load-Balancer-Arbiter (LBA), backend instances on PBE, and Additional Backends (ABE).
The LBC collector-manager on a Gate server must have its max-heap-size increased from the default 2048 MB to an initial value of 4096 MB. This can be done either in the unix-service.properties file, or by means of the admin UI Configure service button of the collector-manager Load-Balancer service.
Increase or decrease memory accordingly in case the number of underlying collector servers increases or decreases and based on cpu/memory utilization in health reports (Report Library/System Health/Workload/JVMs Sizing Recommendation, Collector Managers).
Gate’s LBC is configured as per default settings:
Figure 4. SRM Gate LBC configuration
Reconfigure the data collection block of all SPs hosted by distributed collectors as follows:
- Time-series data from collectors is sent to Gate’s LBC. Set Hostname or IP address to send data to to the respective Gate’s hostname/IP.
Figure 5. SP data collection configuration
- Frontend Web service: PropertyAccessor traffic for data enrichment from collectors is sent to the frontend via Gate’s listening tcp port 58443. Set Tomcat hostname or IP address to the respective Gate’s hostname/IP.
Figure 6. SP frontend web service configuration
- Topology Service: SparqlAccessor traffic for data enrichment from collectors is sent to the PBE Topology-Service via Gate’s listening tcp port 48443. Set Web-Service Gateway hostname or IP address to the respective Gate’s hostname/IP. The Topology-Mapping-Service (TMS) on collector servers communicates with PBE Topology-Service via Gate’s listening port 48443. Set Topology Service hostname or IP address to the respective Gate’s hostname/IP.
Figure 7. SP topology service configuration
- Events data (Dell Unity/VNX/VNXe, DPA, ECS, PowerScale, PowerFlex, XtremIO) collected by the respective solution packs’ collectors is sent to PBE alert consolidation via Gate’s listening tcp port 2040. Reconfigure the SP data collection block for relevant collectors and SPs (for Alert consolidation) and set Alert consolidation server hostname or IP address to the respective Gate’s hostname/IP.
Figure 8. SP events configuration
- SNMP trap data from storage arrays and fabric switches is sent to a PBE snmp trap receiver via Gate’s listening udp ports 162 or 2041. Configure managed devices to send snmp traps to Gate’s hostname/IP, udp port 162 or 2041. Packets with target udp port 162 are redirected to udp port 2041 when they reach the PBE server.
- Events data for the Cisco UCS solution pack is sent from the collector to the PBE event listener via Gate’s listening tcp port 52007. Reconfigure the SP data collection block for Cisco UCS and set Event server hostname or IP address to Gate’s hostname/IP and Event server port number to 52007.
Figure 9. Cisco UCS SP events configuration
- Events data for the Dell Unity/VNX/VNXe solution pack is sent from the collector to the PBE event listener via Gate’s listening tcp port 52001. Reconfigure the SP data collection block for Dell Unity/VNX/VNXe and set Event server hostname or IP address to Gate’s hostname/IP and Event server port number to 52001.
Figure 10. Dell Unity/VNX SP events configuration
- Events data for the Dell Data Protection Advisor (DPA) solution pack is sent from the collector to the PBE event listener via Gate’s listening tcp port 22020. Reconfigure the SP data collection block for DPA and set Event server hostname or IP address to Gate’s hostname/IP and Event server port number to 22020.
Figure 11. Dell DPA SP events configuration
- Alerting data flow for time-series data is initiated from the Gate LBC towards PBE, so there is nothing to be modified on SPs’ data collection blocks of distributed collectors. The only change needed is for the System Health solution pack’s Events block, which sends alerting data to PBE alerting backend via Gate’s listening tcp port 2010. Set Alerting Backend hostname or IP address to Gate’s hostname/IP.
Figure 12. System Health SP alerting configuration