- I wish sent the snmp alerts for the port 161 instead port 162 Firepower

[ricardo_puga]

- I wish sent the snmp alerts for the port 161 instead port 162

was configured alerts of the system health for snmp, but when the system sends the alerts those alerts go to port 162 snmptrap udp, but the server is waiting the alerts for the port 161 snmppolling, i can 't configure the alerts for than it send for the port 161 snmppolling.

the question is: 
the firepower can it send alerts for snmppolling for port 161 udp ?

i attach the image the connection you can see the destination port is 162 snmptrap and not snmppolling 161

[mikael.lahtela]

Hi,

I don't think you can change the destination port in Firepower.
This is an health alert (notification) and it is recommended to be sent to snmptrap 162, if you are going to follow the rfc for snmp traffic.
I would try to see why your snmp server is listening for traps on 161 instead of 162.

br, Mikael