configure snmp delete community

configure snmp delete community [readonly | readwrite] [all | community_name |alphanumeric_string | hex hex_community_name | encrypted enc_community_name ]

Description

Deletes a SNMP (Simple Network Management Protocol) read or read/write community string.

Syntax Description

readonly Specifies read-only access to the system.
readwrite Specifies read and write access to the system.
all Specifies all of the SNMP community stings.
alphanumeric_string Specifies an SNMP community string name. See “Usage Guidelines” for more information.
hex Provide value in hexadecimal.
hex_community_name Community name in hexadecimal.

Default

The default read-only community string is public. The default read/write community string is private.

Usage Guidelines

You must have at least one community string for SNMP access. If you delete all of the community strings on your system, you will no longer have SNMP access, even if you have SNMP enabled.

The community strings allow a simple method of authentication between the switch and the remote network manager. There are two types of community strings on the switch. Read community strings provide read-only access to the switch. The default read-only community string is public. read/write community strings provide read and write access to the switch. The default read/write community string is private. Sixteen read-only and sixteen read-write community strings can be configured on the switch, including the defaults. The community string for all authorized trap receivers must be configured on the switch for the trap receiver to receive switch-generated traps. SNMP community strings can contain up to 32 characters.

For increased security, we recommend that you change the defaults of the read/write and read-only community strings.

Use the configure snmp add commands to configure an authorized SNMP management station.

Example

The following command deletes a read/write community string named extreme:

configure snmp delete community readonly hex 65:01

History

This command was first available in ExtremeXOS 10.1.

The hex keyword and hex_community_name variable were added in ExtremeXOS 15.6.

Platform Availability