- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: Unwanted source ip address in CMA traps.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
07-15-2010 06:25 AM
07-15-2010 06:25 AM
Unwanted source ip address in CMA traps.
We followed this advisory : http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01094386〈=en&cc=us&taskId=101&prodSeriesId=428936&prodTypeId=15351
Adding a 'v1trapaddress' parameter in snmpd.conf, makes that the traps sent by the snmpd daemon (like 'Cold Start/Stop') are well-formatted. Not yet, traps sent by hp agents.
Then after uncommenting 'trapIf ...' in cma.conf, the traps from hp agents take the choosen ip address, except in some cases.
The trapif parameter seems ignored when on host, there are a simple ethernet interface with a ip address and cabled, and bonded interfaces, it's always the ip address of this non-bonded interface (eth8 in our cases) which is used.
When there are only bonded interfaces, agents choose the wished one.
When we brought down this non-bonded interface, without restarting the agents, traps take the appropiate source ip address.
No particular logs on system or in cma.log ...
Does anyone know a solution of this issue?
Thanks you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2011 03:41 PM
12-08-2011 03:41 PM
Re: Unwanted source ip address in CMA traps.
I know that this is an old thread, but I also got this particular issue even with newer hardware, RHEL 5.6, and psp8.7.
It's only happening when you're configuring more than one IP address on a host and one of the interface on that IP address is a bonded interface. What happen is that the agent-addr field always contains the IP address of the non-bonded interface when performing snmp test alert via the SMH page -- and I need to send the SNMP package from the bonded interface ;(
There's no problem with the SNMP cold start package though.. that lead me to believe that the problem most likely lies on the HP SNMP agent package.
No problem as well when I'm using 2 non bonded interface or 2 bonded interface. So it's only happening when you have a mix of both.
I've also updated the trapIF on the cma.conf file with bond0, bond0:1, and bond0:2 and still doesn't fix the problem.
Really appreciate if somebody can shed some light here.
Cheers.