This section describes how to configure the SonicWall appliance for SNMP access.
SNMP (Simple Network Management Protocol) is a network protocol used over User Datagram Protocol (UDP) that allows you to monitor the status of the SonicWall security appliance and receive notification of critical events as they occur on the network. The SonicWall security appliance supports SNMP v1/v2c/v3 and all relevant Management Information Base II (MIBII) groups except egp and at.
SNMPv3 expands on earlier versions of SNMP and provides secure access to network devices by means of a combination of authenticating and encrypting packets.
Packet security is provided through:
Message Integrity: ensures a packet has not been tampered with in transit
Authentication: verifies a message comes from a valid source
Encryption: encodes packet contents to prevent its being viewed by an unauthorized source.
SNMPv3 provides for both security models and security levels. A security model is an authentication strategy set up between a user and the group in which the user resides. The security level is the permitted level of security within a given security model. The security model and associated security level determine how an SNMP packet will be handled. SNMPv3 provides extra levels of authentication and privacy, as well as additional authorization and access control.
The following table shows how security levels, authentication, and encryption are handled by the different versions of SNMP.
The SonicWall security appliance replies to SNMP Get commands for MIBII, using any interface, and supports a custom SonicWall MIB for generating trap messages. The custom SonicWall MIB is available for download from the SonicWall Web site and can be loaded into third-party SNMP management software such as HP Openview, Tivoli, or SNMPC.
SNMP settings can be viewed and configured by you. Settings cannot be viewed or modified by the user. SNMPv3 can be modified at the User or Group level. Access Views can be read, write, or both, and can be assigned to users or groups. A single View can have multiple Object IDs (OIDs) associated with it.
The SNMPv3 Asset Number is specified when configuring SNMP. The Engine ID is used to authorize a received SNMP packet. Only matching packet EngineIDs will be processed.