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.

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.

Step 1: 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.

Please follow the below steps to install the SNMP agent on OSS.
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

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)
a. Change the below highlighted CPU value if necessary
b. Change the DEAFULTVOL location. This could be the default volume of the user who is logged on to NonStop
c. 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.out2>>/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

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.