To enable SNMP version 2c (SNMPv2c) on a managed FortiSwitch, you must first enable the SNMP agent on the device. For SNMPv2c, access control and authentication are managed through community strings. Therefore, you must create and configure at least one SNMP community. This community defines the password (community string), the IP addresses of the SNMP managers allowed to query the agent, and the type of access (read-only or read-write). This configuration is performed on the managing FortiGate controller.

A. SNMP users, which involve authentication and encryption settings, are a requirement for the SNMPv3 protocol, not for the simpler community-based SNMPv2c.

B. Specifying an SNMP host to send traps to is an optional configuration for sending asynchronous alerts; it is not a requirement to enable the SNMP agent for polling.

C. SNMPv3 is a distinct and more secure version of the protocol. It is not required, nor is it used, to handle SNMPv2c messages or traps.

1. FortiSwitch Manager 7.6.0 Administration Guide:

Page 100, "Configuring SNMP for a managed FortiSwitch": This section details the process. It explicitly shows that for SNMPv1/v2c, you must create an "SNMP Community," which involves setting the community name and hosts. This directly supports the requirement to configure communities.

2. FortiOS 7.6.0 Administration Guide:

Page 111, "SNMP": This section describes the SNMP configuration within FortiOS, which is used to manage the FortiSwitch. It clearly distinguishes between creating "Communities" for SNMPv1/v2c and creating "Users" for SNMPv3. It states, "To add an SNMP community, select Create New in the SNMP v1/v2c section." This confirms that configuring communities is the correct procedure for SNMPv2c.