06-26-2019
HPOV like most centralized network management systems (NMS) rely primarily on polling to update their management system.
This means you cannot get information by polling an unresponsive server.
However, most of these same systems also can be configured to send traps.
This means, your HPOV team needs to set up your system to send traps back to the management system before the system being monitored slows to a crawl (soft failure) and cannot respond to polling,
In other words, most novices set up network management systems like HPOV to use only polling; but experienced network management people will also set up traps to be sent back to the NMS for certain critical processes which need to alert the NMS prior to overall system "failure" (also meaning a soft failure, not only a hard failure).
I have extensive hands-on experience in NMS including debugging HPOV when it was a black and white versus decades ago. All well configured NMS will be configured to poll (95% +) and to trap (< 5%) alerts.
Bottom Line: Set up traps for the critical processes to alert the NMS before the system soft-fails (slows to a crawl).
Hope this helps.
Cheers.
10 More Discussions You Might Find Interesting
1. HP-UX
So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced... (6 Replies)
Discussion started by: biznatch
6 Replies
2. UNIX for Advanced & Expert Users
Hi Guys,
Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies
3. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
4. Solaris
Can any one of you suggest me the method to get apache server in online from maintenance mode. I tried in the following way, but couldn't get that service to online.
bash-3.00# svcs -a | grep apache
legacy_run 9:51:55 lrc:/etc/rc3_d/S50apache
offline 9:51:22... (3 Replies)
Discussion started by: Sesha
3 Replies
5. Solaris
Good Day all
i have a solaris 8 server and i want the procedure for how to install HPOV
becuse dont have any small info about solaris . (1 Reply)
Discussion started by: thecobra151
1 Replies
6. Shell Programming and Scripting
Hi, all
Now i want write a shell to get the state of weblogic server,and when the Managed Server's state is not ok, after 3 times checking, i will send msg to the system administrator by sms.
BTW, my environment is :
Linux ,Redhat 5.4 64bit
weblogic version: 10.3.3
the count number... (1 Reply)
Discussion started by: wangsk
1 Replies
7. SuSE
Hi all
We've had an issue over the weekend when one of the SUSE Linux Enterprise Server 11 hung and had to be rebooted. The thing is that I got the ticket alert for a FS exceeding its usage at about 22:41:49 PM on 23 March. I checked the dmesg, the messages log and the boot.msg but all I found... (1 Reply)
Discussion started by: hedkandi
1 Replies
8. Red Hat
when system is hung state due to swap, we will reboot it through ILO.
i want to know which process caused system hung. (1 Reply)
Discussion started by: Naveen.6025
1 Replies
9. Linux
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies
10. UNIX for Dummies Questions & Answers
Hi,
We observe below logs from switch - the database servers rebooted becaause they couldn't do I/O on vfiler -Any pointers looking at below logs please?
Switch logs:
2016 Apr 30 07:41:16.729 EAG-ECOM-POD111GPU-SWF1 %ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface Ethernet152/1/8 is down (Link... (0 Replies)
Discussion started by: admin_db
0 Replies
LEARN ABOUT CENTOS
monitor
MONITOR(8) System Manager's Manual MONITOR(8)
NAME
monitor - Directory Server script for monitoring database performance
SYNOPSIS
monitor [ -Z serverID ] [ -D rootdn ] [ -w password ] [ -b basedn ] [-P protocol] [-h]
DESCRIPTION
Retrieves performance monitoring information. To run this script, the server must be running.
OPTIONS
A summary of options is included below:
-Z Server Identifier
The server ID of the Directory Server instance. If there is only one instance on the system, this option can be skipped.
-D Root DN
The Directory Manager DN, or root DN. If not specified, the script will search the server instance configuration for the value.
-w password
The rootdn password.
-b basedn
The DN of a backend from cn=config.
-P Protocol
The connection protocol to connect to the Directory Server. Protocols are STARTTLS, LDAPS, LDAPI, and LDAP. If this option is
skipped, the most secure protocol that is available is used. For LDAPI, AUTOBIND is also available for the root user.
-h
Display the usage.
EXAMPLE
monitor -P STARTTLS
Note: security must be enabled to use protocol STARTTLS. If STARTTLS is not available it will default to next strongest/available
protocol automatically.
monitor -Z instance2 -D 'cn=directory manager' -w password -b 'cn=monitor,cn=userRoot,cn=ldbm database,cn=plugins,cn=config'
Note: You only need to bind as the root DN if you want to look at a backend monitor.
DIAGNOSTICS
Exit status is zero if no errors occur. Errors result in a non-zero exit status and a diagnostic message being written to standard error.
AUTHOR
monitor was written by the 389 Project.
REPORTING BUGS
Report bugs to http://bugzilla.redhat.com.
COPYRIGHT
Copyright (C) 2013 Red Hat, Inc.
Mar 5, 2013 MONITOR(8)