From: Copeland, Daniel (Daniel.Copeland@alcoa.com)
Date: Wed Feb 26 2003 - 08:15:22 EST
Thanks to:
Randy Ketner
Tom Harrison
Vinod Kumar
Robin Marquis
In addition to my thoughts on monitoring this, the following was suggested:
This is not terribly graceful but it is simple and it works. I put the
following in a script and execute it via cron every 15 minutes. It sends a
message to my pager displaying which component of the cluster is "down"
including lan interfaces.
if [ "`/usr/sbin/cmviewcl -v | grep down`" != "" ]; then
/usr/telalert/telalertc -i Pager -m "`/usr/sbin/cmviewcl -v -p OpC | grep
disabled`" 2>&1 >> /log/testpage.log
fi
Why don't you try Open NMS is a free Network Monitoring Tool on Linux
and then setup is also not that difficult, i have tried this earlier, in
my setup and my management accepted it without any problem since it is a
free, It works on polling, which i guess will fit your requirement
Thanks again,
Dan
> -----Original Message-----
> From: Copeland, Daniel
> Sent: Monday, February 24, 2003 2:39 PM
> To: 'hpux-admin@DutchWorks.nl'
> Subject: monitoring failover lan interface in MC/SG environment
>
> Admins,
>
> We are trying to setup some sort of monitoring of nodes in a MC/SG
> cluster. Particularly, we want to know when the failover interface loses
> connection to the network it needs to be connected to. For example, the
> primary interface (lan0) and the failover interface (lan1) are connected
> to the same network through different switches--they can linkloop to each
> other---they are in the same VLAN. This allows them to be setup in a lan
> card failover situation in MC/SG.
>
> The package ip address is brought up on lan0, but if lan0 were to fail,
> the ip could be switched to lan1. But if lan1 happens to have lost
> connection to it's VLAN some time between when the node joined the cluster
> and when the failure to lan0 happens, the ip won't failover and the
> package will halt.
>
> lan1 may have had it's cable pulled inadvertently or someone switched it's
> VLAN by mistake. So we won't to know when this disconnect (physical or
> virtual) occurs.
>
> One possible solution we thought of was having a script run linkloops to
> each and every interface a couple times a day. This will work but it's
> tedious to setup and maintain. HP gave us nothing. They can only monitor
> whether the card is UP or not (output of lanscan). This doesn't tell us
> if the network is reachable. Their other suggestion was to monitor the
> nettl log file for disconnects. This requires running the nettl format
> command and dumping it to ascii every hour or so--again, not so clean.
> Monitoring the syslog.log file is also an option since the standby
> interface disconnect is logged there but it's a bit vague. Best case
> scenario would be an OVO trap for the situation---HP said it doesn't
> exist.
>
> How are you monitoring this (if you are)?
>
> tia,
> Dan
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:26 EDT