You have alarms in a production Smarts Service Assurance Manager (SAM) environment under a specific class (e.g., ####) and need to export or copy these alarms to a test Smarts environment.
All supported Smarts releases
If the required alarm class is already defined in your destination Smarts environment, you can use the following methods to transfer alarms:
If your alarm source is an SNMP trap, you can replay the traps to the destination environment. This process triggers the destination Smarts environment to process the traps and generate the corresponding alarms as if they were live events.
You can create a snapshot of the live environment's repository using the .rps file format. By loading this snapshot into your test environment, you replicate the entire state of the production repository, including all current alarms and their associated metadata.
You can use the dmctl command-line utility to query the alarms from the source environment and then inject them into the destination environment. This method involves:
dmctl to extract the specific attributes and instances of the alarms from the production server.dmctl to create the alarm instances manually.Note: Ensure that you verify the consistency of the underlying topology in the destination environment before replaying traps or injecting scripts to avoid orphaned alarms.