Configure SNMP 

Enable SNMP on the appliance to monitor the appliance from your existing Network Management System. You can configure an SNMP agent on the appliance so that the SNMP manager can poll the appliance to get the status of the supported OIDs using v2c or v3 queries. For more information on the supported OIDs, see Standard OIDs and Custom OIDs.

The appliance can also send trap notifications to the trap receiver in your network when SNMP traps are configured on the appliance.

The following settings need to be configured before an appliance can start responding to SNMP queries.

Configure the SNMP agent so that the appliance responds to SNMP queries from the SNMP manager. Run these commands:

set snmp agent enable true
set snmp agent syscontact <email address>
set snmp agent syslocation <location>

To poll the appliance using v2c queries, run:

set snmp agent v2c rocommunity-string <string value>
add snmp agent v2c allowed-network-list
set snmp agent v2c allowed-network-list 0 network <IP address of the SNMP agent>
save

To poll the appliance using v3 queries, run:

set snmp agent v3 engine-id <engine-id>
set snmp agent v3 usm auth username <username> key <passphrase> protocol [MD5|SHA]
set snmp agent v3 usm privacy protocol [AES|DES] key <passphrase>
save

The command descriptions are: 

CLI Command		Description
set snmp agent	enable	Enable/Disable SNMP agent on the appliance. When set to true, the appliance must be configured as v2c or v3 agent.
	syscontact	Set the system contact information (admin email etc). For example, admin@localskope.local.
	syslocation	Set the system location. For example, "Los Altos HQ".
	v2c rocommunity-string	Provide a string value. The string configured here will be used in snmpwalk/snmpget commands from the SNMP manager to access the information exposed. If the value does not match the one configured, the relevant information will not be returned. It is used as access control in SNMPv2.
	v2c allowed-network-list	(Optional) Provide the list of hosts/subnets.
	v3 engine-id	(Optional) Set the engine identifier of the SNMP agent in hex format. For example, 0x0102030405.
	v3 usm auth	username	Set the username to authenticate a user with the SNMP agent.
		key	Set the password required to connect with the SNMP agent.
		protocol	Choose a hash function, "MD5" or "SHA" to store the data exchanged between the SNMP agent on the appliance and the SNMP manager.
	v3 usm privacy	protocol	(Optional) Choose an encryption type, "AES" or "DES" to encrypt the traffic between the SNMP agent on the appliance and the SNMP manager.
		key	(Optional) Set the password required to access the encrypted data on the SNMP agent.

Configure SNMP traps on the appliance to send trap notifications to the SNMP trap receiver. Run these commands:

set snmp traps server <hostname or IP address>

To send SNMP v2c traps to the trap receiver, run:

set snmp traps v2c enable true
save

To send SNMP v3 traps to the trap receiver, run:

set snmp traps v3 enable true 
set snmp traps v3 use-agent-settings [true|false]
set snmp traps v3 engine-id <engine-id>
set snmp traps v3 usm auth username <username> key <passphrase> protocol [MD5|SHA]
set snmp traps v3 usm privacy protocol [AES|DES] key <passphrase>
save

The command descriptions are:

These are the standard OIDs.

The official Private Enterprise Number (PEN) assigned to Netskope from IANA (http://www.iana.org/ assignments/enterprise-numbers) is 48007.

Setup an SNMP traps receiver on your SNMP server to receive SNMP traps notifications from the appliance. The appliance uses the following SNMP traps notification OIDs.

Make sure the daemon that receives the SNMP traps (snmptrapd) is running.

To set up the traps receiver,