GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- cmanicd and VLANs
Server Management - Systems Insight Manager
1848990
Members
7511
Online
104040
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
Forums
Discussions
Discussions
Forums
Discussions
back
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
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
10-21-2008 04:32 PM
10-21-2008 04:32 PM
cmanicd and VLANs
We have a number of systems running RedHat RHEL5.2 and loaded with PSP 8.10. We have implemented a large VLAN structure with about 120 VLANs all attached to one physical interface.
But what we have seen is cmanicd launch off and consume 100% CPU time. I can't be sure but it seems that it is treating the VLAN virtual interfaces as physical interfaces and is just running around in a loop monitoring them all.
Is this a known problem?
Is there any way to tell cmanicd not to look at the eth1.??? devices any only the eth1 physical device?
The only way to prevent this currently is to add cmanicd to the exclude line in cma.conf but this stops monitoring of every NIC.
But what we have seen is cmanicd launch off and consume 100% CPU time. I can't be sure but it seems that it is treating the VLAN virtual interfaces as physical interfaces and is just running around in a loop monitoring them all.
Is this a known problem?
Is there any way to tell cmanicd not to look at the eth1.??? devices any only the eth1 physical device?
The only way to prevent this currently is to add cmanicd to the exclude line in cma.conf but this stops monitoring of every NIC.
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP