Removal of SNMP Default Users and Community String

Previous versions of ExtremeXOS came with default SNMP behavior that when not configured prudently could be potentially exploited. In ExtremeXOS 22.1, this default behavior is removed or the user is guided to manage SNMP access more carefully:
  • SNMP v1/v2c: As with most of the vendors, Extreme switches previously had default community strings for read-only and read-write access (“public” and “private,” respectively). Many network administrators change community string to keep intruders from getting their network information. ExtremeXOS 22.1 removes SNMP default community names “private” and “public”.
  • SNMP v3: SNMP request authentication can be done using User-based Security Model (USM). In USM, there are users that can have associated password for authentication and privacy. ExtremeXOS 22.1 removes default values for USM.

During initial switch setup, you are prompted to configure SNMP community string and SNMPv3 user as desired.

These changes in ExtremeXOS 22.1 SNMP behavior do not affect switch upgrades. Switches that already have saved SNMP configurations continue to use their existing configurations.

Supported Platforms

Summit X450-G2, X460-G2, X670-G2, X770, and ExtremeSwitching X620, X440-G2 series switches.

Changed CLI Commands

Changes are underlined.

configure snmpv3 delete user [all | [[hex hex_user_name] | user_name] {engine-id engine_id}]

configure snmpv3 delete community [all | {[[hex hex_community_index] | community_index} | {name [[hex hex_community_name] | community_name}]

The following commands no longer have the default-user option:

enable snmpv3 default-group

disable snmpv3 default-group