8-5z The entry-number must be globally unique and cannot be used on another interface;otherwise, the operation fails.z You can configure multiple history entries on one interface, but the values of theentry-number arguments must be different, and the values of the sampling-intervalarguments must be different either; otherwise, the operation fails.z You can create up to 100 history entries for the device. When the total number of historyentries exceeds 100, no entry can be created.z When you create an entry in the history table, if the specified buckets number argumentexceeds the history table size supported by the device, the entry can be created. However,the validated value of the buckets number argument that corresponds to the entry is thehistory table size supported by the device.Configuring the RMON Alarm FunctionConfiguration Prerequisitesz To configure the managed devices to send traps to the NMS when an alarm event istriggered, configure the SNMP agent as described in SNMP Configuration in the NetworkManagement and Monitoring Configuration Guide before configuring the RMON alarmfunction.z If the alarm variable is the MIB variable defined in the history group or the Ethernetstatistics group, you must make sure that RMON Ethernet statistics collection or RMONhistory statistics collection is configured on the monitored Ethernet interface; otherwise, thecreation of the alarm entry fails, and no alarm event is triggered.Configuration ProcedureFollow these steps to configure the RMON alarm function:To do… Use the command… RemarksEnter system view system-view —Create an event entry in theevent tablermon event entry-number[ description string ] { log | log-traplog-trapcommunity | none | traptrap-community } [ owner text ]Required
