Configuration file for SNMPv2 party definitions
The party.conf is used to define the different parties you'll be using for your SNMPv2 communication.
Here's the search order that's used to find this file:
The file uses this format:
FriendlyName PartyID TDomain IP-address UDP-port authProtocol privProtocol lifetime maxmessagesize clock authPrivate authPublic-length authPublic privPrivate privPublic-length privPublic
agent_party .220.127.116.11.18.104.22.168.22.214.171.124.59.5 snmpUDPDomain 10.0.0.59 161 noAuth noPriv 300 484 29F660EA 00000000000000000000000000000000 Null 00000000000000000000000000000000 Null
The agent_party using an object identifier of .126.96.36.199.188.8.131.52.184.108.40.206.59.5 on host 10.0.0.59 is listening to port 161. It's using no authentication for communication and no encryption.
If TDomain (Transport domain) doesn't list an IP address that matches the IP address of an interface on the host running snmpd, there'll be no ports listed in the snmpd output when snmpd is started.
|If you see the following line with no ports listed:
the IP address listed in TDomain (the agent definition entry in /etc/party.conf) doesn't match the IP address of an interface on the host. You must change the agent definition to include the IP address of the interface where you wish to listen for SNMP requests.
snmpget, snmpgetnext, snmptest, snmptrapd, snmpwalk
Based on ISO IS 8824 (ASN.1), RFC 1065, RFC 1066, RFC 1067, RFC 1446