Next: , Previous: , Up: SNMP Support   [Contents][Index]

18.3 SMUX configuration

To enable SMUX protocol support, Quagga must have been build with the --enable-snmp=smux option.

A separate connection has then to be established between the SNMP agent (snmpd) and each of the Quagga daemons. This connections each use different OID numbers and passwords. Be aware that this OID number is not the one that is used in queries by clients, it is solely used for the intercommunication of the daemons.

In the following example the ospfd daemon will be connected to the snmpd daemon using the password "quagga_ospfd". For testing it is recommending to take exactly the below snmpd.conf as wrong access restrictions can be hard to debug.

	# example access restrictions setup
	com2sec readonly default public
	group MyROGroup v1 readonly
	view all included .1 80
	access MyROGroup "" any noauth exact all none none
	# the following line is relevant for Quagga
	smuxpeer . quagga_ospfd

	! ... the rest of ospfd.conf has been omitted for clarity ...
	smux peer . quagga_ospfd

After restarting snmpd and quagga, a successful connection can be verified in the syslog and by querying the SNMP daemon:

snmpd[12300]: [smux_accept] accepted fd 12 from 
snmpd[12300]: accepted smux peer: \
	oid GNOME-PRODUCT-ZEBRA-MIB::ospfd, quagga-0.96.5

# snmpwalk -c public -v1 localhost .
OSPF-MIB::ospfRouterId.0 = IpAddress:

Be warned that the current version (5.1.1) of the Net-SNMP daemon writes a line for every SNMP connect to the syslog which can lead to enormous log file sizes. If that is a problem you should consider to patch snmpd and comment out the troublesome snmp_log() line in the function netsnmp_agent_check_packet() in agent/snmp_agent.c.

Next: , Previous: , Up: SNMP Support   [Contents][Index]