Home >Documents >VERITAS Cluster Server for Solaris Event Notification.

VERITAS Cluster Server for Solaris Event Notification.

Date post:13-Jan-2016
Category:
View:269 times
Download:4 times
Share this document with a friend
Transcript:
  • VERITAS Cluster Serverfor SolarisEvent Notification

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    ObjectivesAfter completing this lesson, you will be able to:Describe the VCS notifier component.Configure the notifier to signal changes in cluster status. Describe SNMP configuration.Describe event triggers.Configure triggers to provide notification.

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    NotificationHow VCS performs notification:The had daemon sends a message to the notifier daemon when an event occurs.The notifier daemon formats the event message and sends an SNMP trap or e-mail message (or both) to designated recipients.

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Message Severity LevelsErrorSevereErrorWarningInformationConcurrency violationService group is online.Resource has faulted.Agent has faulted

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Message QueuesThe had daemon stores a message in a queue when an event is detected.The message is sent over the private cluster network to all other had daemons to replicate the message queue.The notifier daemon can be started on another system in case of failure without loss of messages.

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Configuring NotifierThe notifier daemon can be started and monitored by the NotifierMngr resource.Attributes define recipients and severity levels. For example:SmtpServer = "smtp.acme.com"SmtpRecipients = { "[email protected]" = Warning }

    NICNotifierMngr NICNotifierMngr

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    The NotifierMngr AgentFunctions:Starts, stops, and monitors the notifier daemonRequired attribute:PathName Full path of the notifier daemonRequired attributes for SMTP e-mail notification:SmtpServer Host name of the SMTP e-mail serverSmtpRecipients E-mail address and message severity level for each recipientRequired attribute for SNMP notification:SnmpConsoleName of the SNMP manager and message severity level

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    The NotifierMngr ResourceOptional attributes:MessagesQueue Number of messages in queue; default = 30NotifierListeningPort TCP/IP port number; default =14144SnmpdTrapPort TCP/IP port to which SNMP traps are sent; default=162SnmpCommunity Community ID for the SNMP manager; default = "publicExample resource configuration:NotifierMngr Notify_Ntfr (PathName = "/opt/VRTSvcs/bin/notifier"SnmpConsoles = { snmpserv = Information }SmtpServer = "smtp.your_company.com"SmtpRecipients = { "[email protected]_company.com" = SevereError })

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    SNMP ConfigurationLoad MIB for VCS traps into SNMP console.For HP OpenView Network Node Manager, merge events:xnmevents -merge vcs_trapdVCS SNMP configuration files:/etc/VRTSvcs/snmp/vcs.mib/etc/VRTSvcs/snmp/vcs_trapd

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    The ResourceOwner AttributeVCS sends an e-mail message to the account specified in the ResourceOwner attribute when notification is configured and the attribute is defined for a resource.An entry is also created in the log file:TAG_E 2001/12/03 11:23:48 VCS:10304:Resource file1 (Owner=daniel, Group testgroup) is offline on machine1These events cause VCS to send notification:ResourceStateUnknown, ResourceMonitorTimeout, ResourceNotGoingOffline, ResourceRestartingByAgent, ResourceWentOnlineByItself, ResourceFaultedTo set the ResourceOwner attribute:hares modify res_name ResourceOwner daniel

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Event TriggersHow VCS performs notification:VCS determines if notification is enabled.If disabled, no action is taken.If enabled, VCS runs hatrigger with event-specific parameters.The hatrigger script invokes the event-specific trigger script with parameters passed by VCS.The event trigger script performs the notification tasks.

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Types of Triggers

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Configuring TriggersTriggers enabled by presence of script file:ResFaultResNotOffSysOfflineInJeopardyViolationNoFailoverPostOfflinePostOnlineLoadWarningUnableToRestartHAD

    Triggers configured by service group attributes:PreOnlineResStateChangeTriggers configured by default:Violation

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Sample TriggersSample trigger scripts include example code to send an e-mail message.Mail must be configured on the system invoking trigger to use sample e-mail code.# Here is a sample code to notify a bunch of users.# @recipients=("[email protected]");# $msgfile="/tmp/resnotoff$2";# `echo system = $ARGV[0], resource = $ARGV[1] > $msgfile`;## foreach $recipient (@recipients) {# # Must have elm setup to run this.# `elm -s resnotoff $recipient < $msgfile`;# }#`rm $msgfile`;

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    ResFault TriggerProvides notification that a resource has faultedArguments to resfault:system: Name of the system where the resource faultedresource: Name of the faulted resource

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    ResNotOff TriggerProvides notification that a resource has not been taken offline If a resource is not offline on one system, the service group cannot be brought online on another. VCS cannot fail over the service group in the event of a fault, because the resource will not come offline.Arguments to resnotoff:system: Name of the system where the resource is not offlineresource: Name of the resource that is not offline

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    ResStateChange TriggerProvides notification that a resource has changed stateSet at the service group level by the ResStateChange attribute:hagrp serv_grp -modify TriggerResStateChangeArguments to resstatechange:system: Name of the system where the resource faultedresource: Name of the faulted resourceprevious_state: State of the resource before changenew_state: State of the resource after change

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    SysOffline TriggerProvides notification that a system has gone offlineExecuted on another system when no heartbeat is detectedArguments to sysoffline:system: Name of the system that went offlinesystemstate: Value of the SysState attribute for the offline system

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    NoFailover TriggerRun when VCS determines that a service group cannot fail overExecuted on the lowest numbered system in a running state when the condition is detectedArguments to nofailover:systemlastonline: Name of the last system where the service group is online or partially onlineservice_group: Name of the service group that cannot fail over

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    SummaryYou should now be able to:Describe the VCS notifier component.Configure the notifier to signal changes in cluster status. Describe SNMP configuration.Describe event triggers.Configure triggers to provide notification.

    VCS_3.5_Solaris_R3.5_20020915

    9-*

    Lab 8: Event NotificationTriggersresfaultnofailoversysofflineStudent RedStudent BlueresfaultnofailoversysofflineRedNFSSGClusterServiceBlueNFSSGwebipwebnicnotifier

Click here to load reader

Reader Image
Embed Size (px)
Recommended