- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: MC SG 11.15 and net-snmp 5.10 on RH ES 3.0
Operating System - Linux
1753797
Members
7302
Online
108805
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
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
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
04-08-2005 01:19 AM
04-08-2005 01:19 AM
MC SG 11.15 and net-snmp 5.10 on RH ES 3.0
We were using MC Service Guard for Linux 11.15 and created packages for an application.
The application for which SG package was created internally communicates with net-snmp(agent x) to publish its statistics through MIBs.
The net-snmp daemon is also running on the same machine as where the package runs.
The problem we were facing is when the application is run independently without SG it is able to communicated with agent X(named pipe)opened by net-snmp daemon, but when running as SG package it couldn't communicate.
The ports are not blocked by any iptables settings or so.
We couldn't really make out what is the problem. The application logs also doesn't show any problems as well in syslog.
Any clues/pointers would be really appreciated.
Hope somebody could help us.
Thanks & Regards,
Karthik
The application for which SG package was created internally communicates with net-snmp(agent x) to publish its statistics through MIBs.
The net-snmp daemon is also running on the same machine as where the package runs.
The problem we were facing is when the application is run independently without SG it is able to communicated with agent X(named pipe)opened by net-snmp daemon, but when running as SG package it couldn't communicate.
The ports are not blocked by any iptables settings or so.
We couldn't really make out what is the problem. The application logs also doesn't show any problems as well in syslog.
Any clues/pointers would be really appreciated.
Hope somebody could help us.
Thanks & Regards,
Karthik
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2005 08:56 AM
04-08-2005 08:56 AM
Re: MC SG 11.15 and net-snmp 5.10 on RH ES 3.0
If you are trying to use an IP address that SG fails over this can be an issue.
The SNMP protocol needs to communicate with the network. On node 1, the primary IP address is not the same as on Node 2. You can use a failover IP address and see if this helps the situation.
Check the snmp configuration and see if there is anything specific to IP address that would interfere with this.
You might find that tying snmp configuration to the hardware and not SG is the right way to go.
SEP
The SNMP protocol needs to communicate with the network. On node 1, the primary IP address is not the same as on Node 2. You can use a failover IP address and see if this helps the situation.
Check the snmp configuration and see if there is anything specific to IP address that would interfere with this.
You might find that tying snmp configuration to the hardware and not SG is the right way to go.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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