Home > Veritas Cluster Server Manual Pages
HANOTIFY (1M) |
Maintenance Commands |
hanotify [-N VCS engine port] -i trapId -l severity -n entity_name -T entity_type -t entity_subtype -o trap's_origin -S system_name -L system_location -p peer_system_name -P peer_system_location -c entity_container's_name -C entity_container's_type -O entity_owner -m message
VRTSvcs, GCM
The hanotify command can be used to define how user-defined event messages are transmitted by VCS to the notifier command and from there to the SNMP console and/or SMTP server. With hanotify, users can specify events by SNMP Object Identifier (OID), severity, and type, the name and location of the systems originating the event, the peer systems and their locations, and free-form messages. If you are developing custom agents or want VCS to provide highly available event notification for your custom events, then you can use hanotify. Please note that VCS and notifier act as forwarding entities only. Neither entity recognizes external messages sent through hanotify. Recipients of traps or emails generated because of messages sent through hanotify are determined by the configuration of notifier.
- 0
- -- Resource:
- 1
- -- Group
- 2
- -- System
- 3
- -- VCS Heartbeat
- 4
- -- GCM Heartbeat
- 5
- -- VCS
- 6
- -- GCM
- 7
- -- Agent
- 0
- -- VCS
- 1
- -- GCM
- 2
- -- GAB
- 3
- -- LLT
- 4
- -- Agent
- 5
- -- Heartbeat
- 6
- -- Any other origin
- 1
- -- Group
- 2
- -- System
- 3
- -- VCS Heartbeat
- 4
- -- GCM Heartbeat
- 5
- -- VCS
- 6
- -- Site
- 7
- -- Agent
# hanotify -i "1.3.6.1.4.1.1302.3.8.10.27.2" -l Error -n gcm -T 6 -t 1.1 -o 1 -S sys1 -L London -p sys2 -P Paris -c site1 -C 6 -O admin -m "site1 is down"
notifier(1m)
Copyright (c) 2008 Symantec.
All rights reserved.
Last updated: 07/03/2008
Copyright ©2009 Symantec Corporation
All rights reserved.