HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: EMS snmp traps
Operating System - HP-UX
1833875
Members
1900
Online
110063
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
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
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
12-05-2002 03:12 AM
12-05-2002 03:12 AM
EMS snmp traps
Hello,
I have a HP-UX lclass B.11.00 U 9000/800 L2000-44 system running EMS and I think I have some problems sending snmp traps when an event is generated. I configured monitor requests with the monconfig tool. I've added a request for all monitors with criteria threshold
"INFORMATION", criteria operator ">=" and
notification method "SNMP". I did this again for notification method "TEXTLOG" (/var/opt/resmon/log/event.log).
The snmpd is running. The snmpd.conf file has a dest-trap entry which is set to my desktop system and a communitystring which is set to public. The registrar is running, emsagent and several monitors (dm_memory, disk_em, dm_core_hw, etc), diagmond, diaglogd are also running.
When I use the tool send_test_event -va disk_em I see information in the eventlog file and my snmp-trap-test-application on my desktop receives the trap, which looks something like this:
------------ TRAP INFORMATION ------------
Community : sendtrap
Enterprise : 1.3.6.1.4.1.11.2.3.1.7
Agent address : 193.67.87.41
Generic type : 6
Source adr : 193.67.87.41
Specific type : 5
Time stamp : 7457033
Source port : 49339
So it seems to work. When I remove one of my disks, event information appears in the tail on eventlog and the testapp receives the trap. But when I remove one of the three fans I receive nothing in the eventlog. The same if I remove two fans, block the rotating blades with a plastic spoon and put them back. Also when I remove two of the three powercables I still wont see event information in the eventlog or traps in the testapp. Is this normal or did I configure something wrong.
EMS version info:
EMS-Config A.03.20 EMS Config
EMS-Core A.03.10 EMS Core Product
EMS-Core A.03.20 EMS Core Product
EMS-KRMonitor A.11.00.04 EMS Kernel
Resource Monitor
EMS-MIBMonitor A.03.10 EMS MIB Resource
Monitor Product
STM version info:
-- Information --
Support Tools Manager
Version A.31.00
Product Number B4708AA
(C) Copyright Hewlett Packard Co. 1995-2001
All Rights Reserved
Regards,
JeanPaul van der Voort
I have a HP-UX lclass B.11.00 U 9000/800 L2000-44 system running EMS and I think I have some problems sending snmp traps when an event is generated. I configured monitor requests with the monconfig tool. I've added a request for all monitors with criteria threshold
"INFORMATION", criteria operator ">=" and
notification method "SNMP". I did this again for notification method "TEXTLOG" (/var/opt/resmon/log/event.log).
The snmpd is running. The snmpd.conf file has a dest-trap entry which is set to my desktop system and a communitystring which is set to public. The registrar is running, emsagent and several monitors (dm_memory, disk_em, dm_core_hw, etc), diagmond, diaglogd are also running.
When I use the tool send_test_event -va disk_em I see information in the eventlog file and my snmp-trap-test-application on my desktop receives the trap, which looks something like this:
------------ TRAP INFORMATION ------------
Community : sendtrap
Enterprise : 1.3.6.1.4.1.11.2.3.1.7
Agent address : 193.67.87.41
Generic type : 6
Source adr : 193.67.87.41
Specific type : 5
Time stamp : 7457033
Source port : 49339
So it seems to work. When I remove one of my disks, event information appears in the tail on eventlog and the testapp receives the trap. But when I remove one of the three fans I receive nothing in the eventlog. The same if I remove two fans, block the rotating blades with a plastic spoon and put them back. Also when I remove two of the three powercables I still wont see event information in the eventlog or traps in the testapp. Is this normal or did I configure something wrong.
EMS version info:
EMS-Config A.03.20 EMS Config
EMS-Core A.03.10 EMS Core Product
EMS-Core A.03.20 EMS Core Product
EMS-KRMonitor A.11.00.04 EMS Kernel
Resource Monitor
EMS-MIBMonitor A.03.10 EMS MIB Resource
Monitor Product
STM version info:
-- Information --
Support Tools Manager
Version A.31.00
Product Number B4708AA
(C) Copyright Hewlett Packard Co. 1995-2001
All Rights Reserved
Regards,
JeanPaul van der Voort
VtM rules
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2002 05:35 AM
12-10-2002 05:35 AM
Re: EMS snmp traps
JeanPaul,
You should examine the monitor specific configuration file to see on what kind of condition a notifications is generated by ems. In case of the fans it should be the dm_core monitor.
you will see the setting name REQUIRE_REDUNDANCY eq. 1 read the explanation within the file to solve you problem or the docs on:
http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_core.htm
Your friend
You should examine the monitor specific configuration file to see on what kind of condition a notifications is generated by ems. In case of the fans it should be the dm_core monitor.
you will see the setting name REQUIRE_REDUNDANCY eq. 1 read the explanation within the file to solve you problem or the docs on:
http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_core.htm
Your friend
E Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 11:46 AM
02-13-2003 11:46 AM
Re: EMS snmp traps
JeanPaul:
I am having similar EMS issues. Did you ever manage to fix this problem?
Rgds
I am having similar EMS issues. Did you ever manage to fix this problem?
Rgds
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 2025 Hewlett Packard Enterprise Development LP