Configuring SNMPv3

If you want to send notifications to SNMPv3 servers, additional setup is required. Configuring SNMPv3 is done using Graphiql APIs.

The console for SNMP queries and mutations is located at https://<TOS URL>/v2/monitor-tower/graphiql and not at https://<TOS URL>/v2/api/sync/graphiql, which is used for most GraphQL queries.

Configure SNMPv3

Run editNotificationProtocolConfiguration

Example:

mutation {
                    editNotificationProtocolConfiguration(input: {
                    editSnmpV3ConfigInput: {
                    authPassword: "12345678"
                    authType: SHA256  
                    privSecret: "134531ss"
                    privType: AES192  
                    securityName: "securityName1"
                    }notificationProtocol: SNMPv3
                    }){
                    resultStatus{
                    successful
                    }
                    }
                }

Enable port listening.

SNMP get/walk requests must be sent to the Primary VIP via port 161. If you use an external IP/host, configure the SNMP to that IP/host. For security purposes, listening at port 161 is disabled by default.
```
[<ADMIN> ~]$ sudo tos config set -p snmp.inboundMonitoringEnabled=true -s monitor-tower
```
sudo tos config set -p snmp.inboundMonitoringEnabled=true -s monitor-tower
Add the TOS Aurora MIB file to your SNMP server.

View Current SNMPv3 Properties

Run notificationProtocolConfiguration

Example:

{
notificationProtocolConfiguration {
  snmpV3Config {
    authType
    context
    engineId
    privType
    securityName    
  }
}
}

Delete SNMPv3 Properties

Run deleteNotificationProtocolConfiguration

Example:

mutation {
  deleteNotificationProtocolConfiguration(input: 

  {
    notificationProtocol: SNMPv3
  }) {
    resultStatus {
      successful
    }
}
}