snmpd problems occur when running portsentry

The problems is when installing portsentry, then running the snmpd. Because the snmp was block by portsentry. The solutions is start snmpd first, then portsentry.

Here is the sockstat from our gateway.
First, we check using sockstat to list open ports. From first line, seems port 161 "used" by portsentry. My college down the portsentry and run the snmpd. You can see in the 3rd command.

gw1# sockstat | grep 161
root portsentry 1066 4 udp4 *:161 *:*
squid squid 1016 161tcp4 127.0.0.1:3128 10.0.16.174:2642
squid squid 1016 174tcp4 117.102.83.187:53898 195.161.119.84:80
squid squid 1016 213tcp4 10.0.17.247:3128 10.0.16.161:2137
squid squid 1016 697tcp4 117.102.83.187:* 212.96.161.229:80
gw1#
gw1# netstat -a |grep snmp
udp4 0 0 *.snmptrap *.*
udp4 0 0 *.snmp *.*
gw1# sockstat | grep 161
root snmpd 60836 10 udp4 *:161 *:*
squid squid 1016 95 tcp4 10.0.17.247:3128 10.0.16.161:2242
squid squid 1016 161tcp4 127.0.0.1:3128 10.0.16.174:2642
squid squid 1016 174tcp4 117.102.83.187:53898 195.161.119.84:80
squid squid 1016 209tcp4 10.0.17.247:3128 10.0.16.49:2161
gw1#