topic Re: Why SIM got snmp trap from eth2, not eth0 in Server Management - Systems Insight Manager

Why SIM got snmp trap from eth2, not eth0

Vandee Chimcherd — Wed, 09 Sep 2009 09:21:22 GMT

Dear expert

We have Redhat version 5 installed on HP Blade. Connected to SIM server as diagram in attach file.

After sent snmptrap from bay 1,5,7,9 found that
Bay5,7 sent IP from eth2 while bay 1,9 can sent eth0 to SIM.

Why SIM not see IP from eth0 of bay 5,7? Are there any solution to make SIM can commucate from eth0 only?

Thank you

Re: Why SIM got snmp trap from eth2, not eth0

Dzmitryj Jakavuk — Fri, 11 Sep 2009 09:44:21 GMT

Yesterday had the same with DL380 G4 with Open Suse 10 on it.

SNMP agent was listening eth1, but not the eth0

Eth1 was created as avirtual interface on eth0. After disabling virtual interface I was able to make quieries to snmp agent

Re: Why SIM got snmp trap from eth2, not eth0

Patrick Schoo — Fri, 11 Sep 2009 13:30:23 GMT

You can try binding the snmp daemon to the address which is configured on eth0.

Add this line to the snmpd.conf file:

agentaddress