No problem notifications generated by Smarts server until console is attached.

Products

• VMware

Issue/Introduction

Symptoms:




No problem alarms generated until a notification console is started and attached to the Smarts server

sm_server process uses little CPU then spikes and remains high to a long period of time

 

problem notifications may not appear for long period of time after starting and connects to Smarts server

Environment

VMware Smart Assurance - SMARTS

Cause

The --subscribe=default option is not used when starting up the Smarts server thus the Smarts server will begin polling to generate problem notifications once the first client, a console, attaches and thus subscribes for problem events.

Resolution

Restart the Smarts server and include parameter --subscribe=default in the sm_server command.  This will ensure the sm_server always has a client subscribing to problem notifications and remains polling at all times.