- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Why SIM got snmp trap from eth2, not eth0
Server Management - Systems Insight Manager
1748185
Members
4055
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2009 02:21 AM
тАО09-09-2009 02:21 AM
Why SIM got snmp trap from eth2, not eth0
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
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
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 02:44 AM
тАО09-11-2009 02:44 AM
Re: Why SIM got snmp trap from eth2, not eth0
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2009 06:30 AM
тАО09-11-2009 06:30 AM
Re: Why SIM got snmp trap from eth2, not eth0
You can try binding the snmp daemon to the address which is configured on eth0.
Add this line to the snmpd.conf file:
agentaddress
Add this line to the snmpd.conf file:
agentaddress
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP