Flood Rate Limitation

Flood rate limitation, or storm control, is used to minimize the network impact of ingress flooding traffic. You can configure ports to accept a specified rate of packets per second. When that rate is exceeded, the port blocks traffic and drops subsequent packets until the traffic again drops below the configured rate.

Configure the rate limit.
configure ports port_list rate-limit flood [broadcast | multicast | unknown-destmac] [no-limit | pps]
Display rate limiting statistics.

show ports {port_list} rate-limit flood {no-refresh}

Note
ExtremeXOS switches implement rate limiting granularity at millisecond intervals. The traffic bursts are monitored at millisecond intervals and the actions are performed within sub-seconds (when applicable). When the switch evaluates the traffic pattern for bursts against the configured value in pps, the value is calibrated on a per-millisecond interval. For example, using the configure port 1 rate-limit flood broadcast1000 command would be equivalent to 1 packet per millisecond.
Configure ExtremeCloud IQ Agent logging behavior.

The ExtremeCloud IQ Agent logging feature uses in-memory, buffer-based logging as the default mechanism instead of continuous on-disk file logging. This reduces storage consumption while maintaining diagnostic capabilities.

In-memory buffer logs for both the Python ExtremeCloud IQ Agent application and the HiveAgent process are stored in EMS trace buffers and are included in show tech-support output for support escalations and diagnostics.

File-based, on-disk logging is disabled by default and available only as an on-demand facility for extended troubleshooting sessions when detailed logging is required.
1. View ExtremeCloud IQ Agent buffer logs.
  ExtremeCloud IQ Agent buffer logs are captured in real-time and included in system diagnostics:
```
show tech-support
```
  The output includes recent activity from both the Python application and HiveAgent process buffers, eliminating the need for persistent on-disk logging during normal operations.
2. Enable file-based logging on demand for troubleshooting.
  
  For targeted troubleshooting sessions, file-based logging can be enabled using debug CLI. This is configured using debug commands at critical, error, warning, info, and debug severity levels.
  
  For detailed configuration procedures and complete CLI command syntax for enabling file-based logging, refer to the user guide.
3. Note behavior change after upgrade.
  
  Upgrade Note: After upgrading to version 33.7.1, ExtremeCloud IQ Agent file-based, on-disk logging is off by default. The switch does not write new entries to on-disk log files. Any existing log files present on the switch at the time of upgrade are preserved and are not deleted or truncated. Recent activity remains available through the in-memory buffer-based trace feature.
  
  To resume or extend on-disk file-based logging during a troubleshooting session, enable file-based logging using the debug CLI. Disabling file-based logging stops new writes but preserves previously captured on-disk log files.