PDF(539.3 KB) View with Adobe Reader on a variety of devices
ePub(672.1 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(239.0 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 10, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
RMON Alarms Configuration on 300 Series Managed Switches
The objective of this document is to configure the alarms on the switch for an event which needs to be monitored and alarmed to the network administrators. A rising event is triggered when the rising threshold is crossed . Similarly a falling event is triggered when the falling threshold is crossed.
Note: Alarms can be configured only if there is a RMON event configured on the switch. For more information on how to configure a RMON event, refer to the article RMON Events on 200/300 Series Managed Switches.
• SF/SG 300 Series Managed Switches
RMON Alarm Configuration
Step 1. Log in to the web configuration utility and choose choose Status and Statistics > RMON > Alarms. The Alarms page opens:
Step 2. Click Add. The Add Alarm Entry window appears.
Note: The Alarm Entry field displays the number of the alarm that is currently being configured.
Step 3. Click a type of interface in the interface field to define to which interface the alarm is applied. The available options are:
• Port — This option lets you choose from the Port drop-down list the port you wish to assign an event alarm.
• LAG — This option lets you choose from the Link Aggregation Group (LAG) drop-down list the LAG port you wish to assign an event alarm. A LAG port combine individual interfaces into a single logical link with higher bandwidth.
Step 4. Choose from the Counter Name drop-down list the counter name which indicates the Management Information Base (MIB) to be measured by the alarm.
Note: For information about MIB, refer to the article Simple Network Management Protocol (SNMP) Views Configuration on the 300 Series Managed Switches.
Step 5. Click a sample method to generated an alarm. The available options are:
• Absolute — This option uses the information measured of the current sample to generate the alarm.
• Delta — This option uses the difference between two consecutive samples to generate the alarm.
Step 6. Enter the rising treshold in the Rising Treshold field to trigger the rising treshold alarm.
Step 7. Choose from the Rising Event drop-down list the event you wish to be performed when a rising event is triggered.
Step 8. Enter the falling treshold in the Falling threshold field to trigger the falling ttreshold alarm.
Note: Falling threshold must be less than rising threshold.
Step 9. Choose from the Falling Event drop-down list the event you wish to be performed when a falling event is triggered.
Step 10. Click the startup alarm from which you prefer to start. The available options are:
• Rising Alarm — This option triggers as startup alarm the rising event.
• Falling Alarm — This option triggers as startup alarm the falling event.
• Rising and Falling Alarm — This option triggers both rising and falling events.
Step 11. Enter the interval time between each alarm in the Interval field.
Step 12. (Optional) Enter the name of the user or system that receives the alarm.
Step 13. Click Apply to save your configuration.
Step 14. (Optional) To edit a current alarm, check the check box of the alarm you wish to edit and click Edit.
Step 15. (Optional) T delete a current alarm, check the check box of the alarm you wish to delete and click Delete.