Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Alerting feature in ApplicationHA

Created: 14 Dec 2011 • Updated: 16 Feb 2012 | 5 comments
This issue has been solved. See solution.

We have the product deployed in vSphere 4.1 but could't see anything related to alerting. When something needs attention as per ApplicationHA for a configured service (in a fault state), how do you get notified ? Didn't see anything except the status info from the ApplicationHA tab.

Comments 5 CommentsJump to latest comment

Soumya Sakha Tripathy's picture

You can use the notifier agent to capture and send snmp/smtp alerts.

They behave the same as classic VCS (WxRT).

 

And JFYI, in the next release of ApplicationHA, we are targetting for a notification mechanism (SNMP, SMTP etc), where the notifications will be more ApplicationHA specific and will have more ease of use in terms of configuring notification settings etc.

srikanthnxt's picture

Does this mean VOM needs to be in place ? Currently this is not.

Virtually_LG's picture

We are in the process of writing a technote on how to do this. but in the mean time the steps below should help.

ApplicationHA can provide a method for notifying important events such as resource or system faults to administrators or designated recipients.This notification is configured via the command line from within the virtual machine or through the Veritas Operations Manager web interface.

ApplicationHA includes a notifier component, which consists of the notifier process. ApplicationHA support SNMP consoles that can use an SNMP V2 MIB. The notifier process performs the following task

  • Receives notifications from High Availability engine (HAD)
  • Formats the notification
  • Generates an SNMP (V2) trap or sends an email to the designated recipient, or does both.

There four severity levels: SevereError, Error, Warning, and Information. SevereError indicates the highest severity level, Information the lowest. Note that these severity levels are case-sensitive. SNMP traps are forwarded to the SNMP console. Typically, traps are predefined for events such as service group or resource faults.

For configuration via command line connect to the virtual machine via RDP, putty or similar remote management tool or via VMware Console from with vSphere Client.

Launch a command prompt or terminal session depending on which operating system the virtual machine is running.

Procedure

Step 1.  Enable writing to the virtual machine ApplicationHA configuration.

haconf –makerw

Step 2. Add the Notifier resource to Heartbeat service group.

hares –add <notifier resource> NotifierMngr <Heartbeat Service Group>

Example:- hares -add AppMonNtfr NotifierMngr VCSAppMonHBSG

Step 3.  Configure for SNMP notifications type

hares -modify <notifier resource> SnmpConsoles  <snmpserv>  <security level>

example:- hares -modify AppMonNtfr SnmpConsoles  10.10.1.6  Information

Step 4.  Enable the new resource type

hares -modify AppMonNtfr Enabled 1

Step 5. Configure for SMTP notifications type

hares -modify <notifier resource> <SmtpServer> <SMTP server admin email address>

Example:-hares -modify AppMonNtfr EXCHSVR1 infra_admin@company.com

Step 6.  Set the type of notifications for SNMP type

hares -modify <notifier resource> SmtpRecipients  <admin email> <security level>

Example:- hares -modify AppMonNtfr SmtpRecipients "infra_admin@company.com" SevereError

Step 7. Save the changes to the virtual machine ApplicationHA configuration.

haconf -dump -makero

Step 8.  Online the resource.

hares -online AppMonNtfr -sys <virtual machine name>

Example:- hares -online AppMonNtfr -sys SQL2008SRV1

 

To speed up the process a batch file can be created and run on each VM.

srikanthnxt's picture

Well, I got the same document from our symantec tech contacts but when I used the above commands, tha last gave me an error:

C:\Users\admin>hares -online AppMonNtfr -sys SQLSVR2008VM

VCS WARNING V-16-1-10200 System SQLSVR2008VM is not available

SQLSVR2008VM is the name of virtual machine.

Your document text says 

"ApplicationHA can provide a method for notifying important events such as resource or system faults to administrators or designated recipients.This notification is configured via the command line from within the virtual machine or through the Veritas Operations Manager web interface."

So what I understand is if you have Veritas Operations Manager configured, you can do it from its web interface or from a VM's command line. So what I want to know is, will this need a VOM in place before I excute those commands ?

Soumya Sakha Tripathy's picture

Hi,

You have to use the host name (of the guest OS), not the VM name.

 

On the other query:

No. VOM is not needed to execute the above commands.

Configuring through VOM (if VOM is in place) is an alternative to the above commands.

SOLUTION