How Can We Help?

Search for answers or browse our knowledge base.

Documentation | Demos | Support

< All Topics
Print

What delivery options do I have?

Quickstart

Alert Delivery Protocols

  • Get Alert notifications: You can set up alerts for all the metrics you want Web ViewPoint Enterprise to watch for. You may set as many alert conditions as needed.
Alerts via SNMP

Before you begin: To modify alert notification settings, you must be assigned the Administrator role.

You must be running an SNMP management application in your system environment. Management Information Base (MIB) files are provided via WVPMIB file which will be part of your installation files (within WVP E subvolume). You must set up the SNMP trap receiver with the MIB files to receive SNMP traps from WVP Enterprise.

WVP E software supports the following versions of SNMP:

Model Level Authentication Encryption
v1 noAuthNoPriv Community String No
v2c noAuthNoPriv Community String No
v3 noAuthNoPriv Username No
v3 authNoPriv Message Digest 5 (MD5) or Secure Hash Algorithm (SHA) No
v3 authPriv MD5 or SHA Data Encryption Standard (DES)
SNMP v1:

In order to send SNMP traps using v1, you will need to configure the below in STRTWVPE file and restart the instance.

  1. Edit the STRTWPE file and add the below. 
    • PARAM in STRTWVPE file: PARAM SNMP-VERSION v1

Note: v is case sensitive and should be specified in lower case.

    • By default, the run command to start the UMPSNMP program (i.e. SNMP Program used to trigger alerts using SNMP v1) is not added. Add the below line if you are using the v1 version. RUN UMPSNMP /NAME $USMP, NOWAIT, TERM $ZHOME, PRI 120, CPU 0/
  1. Restart WVPE by running the below command.

OBEY STOPWVPE > STATUS *, PROG *, STOP > OBEY STRTWVPE

Follow the instructions specified in Step 2 (Needs to be updated) to configure the Trap receiver settings and add alerts.

SNMP v2:

In order to send SNMP traps using v2, you will need to configure the below.

  1. Edit the STRTWPE file and add the below.

         PARAM in STRTWVPE file: PARAM SNMP-VERSION v2  

Note: v is case sensitive and should be specified in lower case.

  1. Follow the steps to configure SNMP persistent process on OSS.
  2. Follow the steps to configure the Trap receiver settings and add alerts.
SNMP V3:

Depending on the type of security levels, SNMPv3 configuration and setup varies.

A. For no authentication protocol, you will need to set the below param(s) in STRTWVPE file and follow the standard steps to configure the persistent process in OSS.

  1. Edit the STRTWPE file and add the below.

PARAM in STRTWVPE file: PARAM SNMP-VERSION v3

Note: v is case sensitive and should be specified in lower case.

PARAM OSSPPD-PROCESS $RSNMP   —- > This param needs to be added only if you change the default SNMP process from $USNMP to a different process name.

      2. Follow the steps to configure SNMP persistent process on OSS.

      3. Follow the steps to configure the Trap receiver settings and add alerts.  

B. For SNMP v3 with authentication, in addition to the steps mentioned above, you must have a specific set of properties configured (within the wvpe_snmp_configuration.properties) in order for Web ViewPoint Enterprise to successfully communicate with them.

Fields in wvpe_snmp_configuration.properties file which is a part of snmp.tar file

Example:

security_name=traptest

authentication_paraphase=mypassword

privacy_paraphase=mypassword

engine_id=80:00:00:00:01:02:03:04

  • In the authentication_passphrase line, type the string to use as a secret key for authentication between SNMPv3 standard hosts, when calculating a message digest. The passphrase can be 16 octets long for MD5 and 20 octets long for SHA-1.
  • In the privacy_passphrase line, type the string to use in the encryption algorithm as a secret key for encryption between SNMPv3 standard hosts.The length of this key must be 16 octets for DES and longer for the AES protocols.
  • In the engineID line, type the string value to identify the device on which the management information is hosted. 

Step 1: Steps configure to SNMP persistent process on OSS

In order to send alerts from WVP to the SNMP receiver, the WVP SNMP component needs to be installed in the OSS space. This component receives messages from notification component of WVP and sends out corresponding SNMP traps to the SNMP receiver.

1) Go to OSS space, create a directory named usnmp in the following location /usr/tandem

Commands:

cd /usr/tandem

mkdir usnmp

Example: /usr/tandem/usnmp

2) Transfer the snmp.tar file to the newly created directory

NOTE: snmp.tar file is present within UMPPAK pak file (which is present within your WVP E install subvolume)

You can transfer the snmp.tar file in 2 ways.

Method 1: You can download it from your WVP E subvolume and transfer it to OSS directory via any FTP client

or

Method 2: You can transfer it to OSS side from Guardian via OSH commands by following the below instructions

a. Logon to OSS space, navigate to location where you have WVP E installed (replace VOLUME/SUBVOLUME with your WVP E install volume subvolume on guardian side)

    cd /G/VOLUME/SUBVOLUME

b. Check to make sure that snmp file is present within that location

    cd /G/VOLUME/SUBVOLUME

    ls

c. Now, copy over the snmp file from this location to your OSS location (i.e. to directory you created in step 1)

    cp snmp /usr/tandem/usnmp

d. Navigate to /usr/tandem/usnmp location and verify if the file has been copied over by using below commands

   cd /usr/tandem/usnmp

   ls   

e. Rename snmp to snmp.tar by running the below command

   mv snmp snmp.tar

3) Extract the contents from the tar file by running the below command.

tar -o -xvf snmp.tar

/usr/tandem/snmp: tar -o -xvf snmp.tar

x snmp4j.jar, 473413 bytes, 925 tape blocks

x umpSNMP.class, 11590 bytes, 23 tape blocks

x umpSNMPStart.sh, 505 bytes, 1 tape blocks

wvpe_snmp_configuration.properties,

4) Edit umpSNMPStart.sh file

a. Modify the java related parameters

b. If needed, change the directory name from /usr/tandem/dir/ to corresponding one (i.e. added in Step 1).

cd /usr/tandem/dir

to

cd /usr/tandem/usnmp

export CLASSPATH=$CLASSPATH:/usr/tandem/dir/snmp4j.jar:.

to

export CLASSPATH=$CLASSPATH:/usr/tandem/usnmp/snmp4j.jar:.

Note: usnmp is an example directory. You can change that to your desired directory.

5) If the TCP Process is a different from $ZTC0, define the specific process name

(add_define =tcpip^process^name file=\$NAME) in the umpSNMPStart.sh file.

#!/bin/sh
cd /usr/tandem/usnmp
export _RLD_LIB_PATH=$_RLD_LIB_PATH:/usr/tandem/javaexth11/lib
export JAVA_HOME=/usr/tandem/nssjava/jdk180_h80/
export JREHOME=$JAVA_HOME/jre
export CLASSPATH=$CLASSPATH:/usr/tandem/javaexth11/lib/tdmext.jar
export PATH=/usr/tandem/javaexth11/bin:$PATH

export APP=umpSNMP

export CLASSPATH=$CLASSPATH:/usr/tandem/usnmp/snmp4j.jar:.

add_define =tcpip^process^name file=\$NAME
run -name=/G/usnmp /usr/tandem/nssjava/jdk180_h80/bin/java $APP

6) Give execute permission to the script file using the below command

chmod 755 ./umpSNMPStart.sh

7) On guardian, add the persistent process information via SCF. To do so, go to SCF prompt, modify the required fields as mentioned below and run the lines (as shown below)

  1. Change the below highlighted CPU value if necessary
  2. Change the DEAFULTVOL location. This could be the default volume of the user who is logged on to NonStop
  3. Make sure the OSS path /usr/tandem/usnmp/umpSNMPStart.sh is the same one you created in Step 1.

ADD PROCESS $ZZKRN.SNMP, &

AUTORESTART 2 , &

CPU 03 , &

DEFAULTVOL $IDEL00.QABKCOL , &

HIGHPIN ON , &

HOMETERM $ZHOME , &

INFILE $ZHOME , &

NAME $USVM0 , &

ASSOCPROC $USNMP , &

OUTFILE $ZHOME , &

PRIORITY 146 , &

PROGRAM $SYSTEM.SYSTEM.OSH , &

SAVEABEND OFF , &

STARTMODE MANUAL , &

STARTUPMSG “-osstty -p /usr/tandem/usnmp/umpSNMPStart.sh <- >>/tmp/umpSNMP.out 2>>/tmp/umpSNMP.err” , &

STOPMODE STANDARD , &

TYPE OTHER, &

USERID SUPER.SUPER

8) To start the process (in SCF): START PROCESS $ZZKRN.SNMP

9) Verify that the process is running by running the below command in SCF.

-> Status PROCESS $ZZKRN.SNMP

NONSTOP KERNEL – Status PROCESS \NSCLOUD.$ZZKRN.#SNMP

Symbolic Name                    Name   State    Sub Primary  Backup   Owner

                                                     PID      PID      ID

SNMP                            $USVM0 STARTED      3 ,1026  None     255,255

SNMP                            $USNMP STARTED      3 ,1097  None     255,255

10) To stop the process (in SCF): ABORT PROCESS $ZZKRN.SNMP

Now, you can set up the alert to go to SNMP.

Step 2: To configure SNMP alert notifications, complete the following steps:

  1. In the menu bar in the web-based GUI, go to Admin > Delivery.
  2. Under the SNMP tab, specify new settings or remove existing settings.

To specify new settings, input the below fields and click on Submit.

Name:

Specify any name of the SNMP for sending SNMP traps.

IP address:

Specify the host that is configured to receive SNMP traps. You can specify a host name, an IPv4 address, or an IPv6 address depending on what is supported within your environment.

Port:

Specify the port number for receiving SNMP traps. SNMP trap messages are sent to this port when an alert condition is detected. By default, the port is set to 162. 

Alerts via Email or SMS

To send alerts via email or text, Web ViewPoint Enterprise must connect to a mail server, also known as a Simple Mail Transfer Protocol (SMTP) server. An SMTP server is a service that you can send outbound email messages to. It then relays the messages to whoever they’re addressed to. (It doesn’t handle incoming email.) To set up alerts, you must configure Web ViewPoint Enterprise to communicate with your SMTP mail server.

SMTP information you’ll need:

Many organizations already have an SMTP server in-house. Before you continue, ask your IT department if there is an SMTP server that you can use.

Here’s the SMTP server information that you need from your IT department:

  • The server address. This is often something like smtp.example.com or mail.example.com, but other addresses are also possible.
  • A user name.
  • A password.

Some servers don’t require a user name or password because they are only meant for internal use.

You’ll also need to decide on a from address for the alerts that the server sends. When people receive an alert email from Web ViewPoint Enterprise , this is the name that’s on the from line of the message. Because alerts are simply informational, you generally don’t need to worry about who’s on the from line, so people use addresses like no-reply@example.com

After you get the SMTP server information from your IT department, you can follow the below steps to configure and setup alerts.

Step 1: Configure SMTP Server information

  1. Logon to Web ViewPoint Enterprise, navigate to Admin – Delivery section
  2. Enter the information that you received from your IT department.
  3. In the Mail from account box, enter the email address that you want all server emails to be sent from. For example, you might enter or no-reply@example.com.
  4. Click Submit.

Step 2: Add Users and Phone Carriers

Users and Phone carriers need to be added prior to setting up the alerts. This will help specify which user you want to send the email or sms alerts to. Phone carrier is required only if you want to setup text/sms alerts (if you do not want to receive any text alerts you can skip the phone carriers section and go to Add Users section)

a) Add Phone Carriers

In the Admin – Phone Carriers section, there is a list of pre-defined phone carriers present. If your phone carrier is not one of them you will need to add your carrier.

    1. Logon to Web ViewPoint, navigate to Admin – Phone Carriers section
    2. Click on Add button present on the top right corner
    3. Enter the information that you received from your IT department.
    4. Click Add.

b) Add Users

    1. Logon to Web ViewPoint Enterprise, navigate to Admin – Users section
    2. Click on Add button present on the top right corner
    3. Enter all the required information in the fields
    4. Click Save

Note: Phone number and phone carrier fields are optional if you do not want to setup a text alert. However, if you do want to setup a text alert, you will need to enter the phone number and the carrier information.

Step 3: Set up alerts

Go to the Admin – Alerts menu and click Add

Configure the alerts based on your requirements and click Save.

Read more about setting up alerts

Alerts via syslog

Before you begin: To modify alert notification settings, you must be assigned the Administrator role.

In order to send alerts from WVP via SYSLOG, the WVP SYSLOG component needs to be installed in the OSS space. This component receives messages from notification component of WVP and sends out corresponding traps to the SYSLOG receiver.

Please follow the below steps to install the SYSLOG agent on OSS:

1) Go to OSS space, create a directory named umpsl in the following location /usr/tandem

Commands:

cd /usr/tandem

mkdir umpsl

Example: /usr/tandem/umpsl

2) Transfer the umpslog.tar file to the newly created directory

Example: /usr/tandem/umpsl/umpslog.tar

3) Extract the contents from the tar file by running the below command.

tar -o -xvf umpslog.tar

/usr/tandem/umpsl: tar -o -xvf umpslog.tar

4) Edit umpSysLogStart.sh file

Modify the java related parameters

Change the directory name from /usr/tandem/dir/ to corresponding one

export CLASSPATH=$CLASSPATH:/usr/tandem/dir/cloudbees.jar:.

                                           to

export CLASSPATH=$CLASSPATH:/usr/tandem/umpsl/cloudbees.jar:.

 cd /usr/tandem/dir

               to

cd /usr/tandem/umpsl

Note: umpsl is an example directory. You can change that to your desired directory.

5) If the TCP Process is a different from $ZTC0, define the specific process name

   (add_define =tcpip^process^name file=\$NAME) in the umpSysLogStart.sh file.

        #!/bin/sh

        cd /usr/tandem/umpsl

        export _RLD_LIB_PATH=$_RLD_LIB_PATH:/usr/tandem/javaexth11/lib

        export JAVA_HOME=/usr/tandem/nssjava/jdk180_h80/

        export JREHOME=$JAVA_HOME/jre

        export CLASSPATH=$CLASSPATH:/usr/tandem/javaexth11/lib/tdmext.jar

        export PATH=/usr/tandem/javaexth11/bin:$PATH

export APP=SLWrapr

export CLASSPATH=$CLASSPATH:/usr/tandem/umpsl/cloudbees.jar:.

        add_define =tcpip^process^name file=\$NAME

        export DEBUG_PROG=’run -name=/G/umpsl’

        run -name=/G/umpsl /usr/tandem/nssjava/jdk180_h80/bin/java $APP

6) Give execute permission to the script file chmod 755 ./umpSysLogStart.sh

7) On guardian, add the persistent process information via SCF using the below commands

Note: Modify the required fields in the below commands and run it in SCF.

Change the CPU values if necessary

Change the DEAFULTVOL location. This could be the default volume of the user who is logged on to NonStop

Make sure the OSS path /usr/tandem/umpsl/umpSysLogStart.sh is the same one you created in Step 1.

Make sure the ASSOCPROC process i.e. $UMPSL matches the directory name created in Step 1.

ADD PROCESS $ZZKRN.umpsl , &

AUTORESTART 2 , &

CPU FIRST , &

DEFAULTVOL $IDEL00.QABKCOL , &

HIGHPIN ON , &

HOMETERM $ZHOME , &

INFILE $ZHOME , &

NAME $USVM0 , &

ASSOCPROC $UMPSL , &

OUTFILE $ZHOME , &

PRIORITY 146 , &

PROGRAM $SYSTEM.SYSTEM.OSH , &

SAVEABEND OFF , &

STARTMODE MANUAL , &

STARTUPMSG “-osstty /usr/tandem/umpsl/umpSysLogStart.sh <- >>/tmp/umpSysLog.out 2>>/tmp/umpSysLog.err” , &

STOPMODE STANDARD , &

TYPE OTHER, &

USERID SUPER.SUPER

8) To start the process (in SCF):

-> START PROCESS $ZZKRN.UMPSL

9) Verify that the process is running by running the below command.

 -> Status PROCESS $ZZKRN.UMPSL

NONSTOP KERNEL – Status PROCESS \NSCLOUD.$ZZKRN.#UMPSL

Symbolic Name                    Name   State    Sub Primary  Backup   Owner

                                                     PID      PID      ID

UMPSL                           $USVM0 STARTED      3 ,1026  None     255,255

UMPSL                            $UMPSL STARTED      3 ,1097  None     255,255

10) To stop the process (in SCF): ABORT PROCESS $ZZKRN.UMPSL

 

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Previous Overview – Delivery
Next How can I configure/update SMTP information?
Table of Contents
WordPress Image Lightbox Plugin
Skip to content