VMware vCenter Server 8.0.x
This issue occurs due to 2 separate agents on the vCenter Appliance - one for vpxd and one for snmp. Alarms use the vpxd agent to send traps whereas the snmp agent allows for traps to be sent to servers outside of the VCSA.
This failure in the installation of vmwspp RPM on 8.0u2 is because of we have moved to FIPS compliant RPM version in this release, which enforces stricter rules for RPM header digest and file digest. Which means, any usage of SHA1 and MD5 is dis-allowed. Hence same package works on 7.0 which is having older RPM version (non FIPS compliant) but fails on 8.0 because of FIPS compliant RPM version.
VMware Engineering is aware of this issue.
To work around this limitation, follow the steps below:
# rpm -qi vmware-spp-1.1.0-Linux.rpm# rpm -Uvh vmware-spp-1.1.0-Linux.rpm# systemctl status vmwspp# systemctl start vmwspp# systemctl status vmwsppsnmp.get
NOTE : The vmwspp service currently requires a manual restart after every vCenter reboot. To fix this, verify its startup configuration by running 'systemctl is-enabled vmwspp'. If the service is disabled, run 'systemctl enable vmwspp' so it starts automatically on boot.
MD5SUM of the RPM file
d0d632dec78914fdb12048c44ea815de *vmware-spp-1.1.0-Linux.rpm