Difference between revisions of "SNMPD in container"
m (add ref. to rhel/centos 5 solution) |
(added to Category: Networking) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | If you are trying to get snmpd working on a | + | If you are trying to get snmpd working on a container (for whatever reason, note you should strongly consider if you can accomplish what you are trying to do on the host) you will need to do a couple things. |
Do this if you are seeing an error like this one: | Do this if you are seeing an error like this one: | ||
| − | error scanning interface data (expected 10, got 0) | + | error scanning interface data (expected 10, got 0) |
First you need to run net-snmp 5.4.1 or later and second you will need to start it with the following option: | First you need to run net-snmp 5.4.1 or later and second you will need to start it with the following option: | ||
| Line 17: | Line 17: | ||
<code>-I -ifTable</code> | <code>-I -ifTable</code> | ||
| − | From what I understand they are in the process of patching things on net-snmp to work with | + | From what I understand they are in the process of patching things on net-snmp to work with OpenVZ a little better, but because of the duplicate IPs on the containers (127.0.0.1) things aren't exactly standard. |
| + | |||
| + | [[Category: Troubleshooting]] | ||
| + | [[Category: Networking]] | ||
Latest revision as of 11:22, 9 April 2008
If you are trying to get snmpd working on a container (for whatever reason, note you should strongly consider if you can accomplish what you are trying to do on the host) you will need to do a couple things.
Do this if you are seeing an error like this one:
error scanning interface data (expected 10, got 0)
First you need to run net-snmp 5.4.1 or later and second you will need to start it with the following option:
-I -ipAddressTable
So
/sbin/snmpd -I -ipAddressTable
The same basic idea applies to net-snmp 5.3.1 (at least in RHEL/Centos 5) with a slightly different flag:
-I -ifTable
From what I understand they are in the process of patching things on net-snmp to work with OpenVZ a little better, but because of the duplicate IPs on the containers (127.0.0.1) things aren't exactly standard.
