Amit,
We ran through a series of stress tests on our environment to ensure the level of scale we were trying to reach.
Probably the best way to generate alarms would be to use the SYSLOGGTW probe. Simply use a syslog generator and point it to the server with SYSLOGGTW probe deployed.
Here is what we did:
1. Deploy SYSLOGGTW probe to the hub or robot you wish to stress test
2. Open the SYSLOGGTW probe and verify the following boxes are checked:
"Activate syslogd"
"Generate NimBUS Alarm"
"Generate SYSLOG-IN message"
3. Open up the hub probe on the hub the robot is pointed to
4. Create a new queue called SYSLOG-IN
"Name: SYSLOG-IN"
"Type: Attach"
"Subject: SYSLOG-IN"
5. At this point we have the probe configured to look for any syslog data and generate an alarm for any and all syslog data. Now we just have to generate a ton of syslog data!
6. Download kiwi syslog generator: http://www.kiwisyslog.com/kiwi-sysloggen-download/
7. Install it on the server with the SYSLOGGTW probe deployed
8. Run the kiwi syslog generator
9. Configure it to generate continuous syslog messages and point it to localhost or 127.0.0.1
10. After this point you should see alarms start generating
To further stress test the machine, install the genorator on multiple machines and point it to the server with the SYSLOGGTW probe deployed.
Please let me know if you need me to be more clear on any of the steps.
Jeff Young
IntelliNet Corporation