Alert

[GSC]

Hi,

What are the requirements for sending SNMP Alerts for different events?

ARCserve 2000 Build 1086 Installed
Chyenne Alert Notification Server Service running.
Events defined in the Alert tab in the Options Menu.
SNMP configured to send to manager name via IP.

Still not working, I don't receive any messages on my monitor manager.
Thanks in advance.
GSC

 

[databasebaba]

I found out these lines in the release notes...

Try out and let us know ....

5. Configuring Alert v4.0 for Windows NT for your SNMP Manager

Alert for Windows NT can send SNMP alerts to SNMP Managers such as Novell NetWare Management System (NMS) v2.0 and HP OpenView for Windows v7.2. The following six files should be in the ALERT Home Directory:

a. INO.CNF - InocuLAN Trap definition file for UNIX based SNMP Managers such as HP OpenView UNIX and IBM NetView

b. INOMIB.MIB - InocuLAN MIB file for all SNMP Managers

c. INOMIB.TDF - InocuLAN Trap Definition file for HP OpenView for Windows

d. ARC.CNF - Trap definition file for UNIX based SNMP Managers such as HP OpenView UNIX and IBM NetView

e. ASMIB.MIB - ARCserve MIB file for all SNMP Managers

f. ASMIB.TDF - ARCserve Trap Definition file for HP OpenView for Windows

5.1 Configuring Alert for NMS v2.0 (or higher)

1. Copy the file called INOMIB.MIB from the directory where you installed the Alert for Windows NT software to a floppy diskette.

2. Insert the diskette in the workstation where your NMS manager is installed and copy INOMIB.MIB to your NMS\SNMPMIBS\CURRENT directory.

3. Load NMS on your workstation and compile the ARCserve MIB file using the SNMP MIB COMPILER option from the Tools Menu within NMS.

5.2 Configuring Alert for HP's OpenView v7.2 (or higher)

5.2.1 Follow these steps if the NetServer Assistant software is NOT installed:

1. Copy the ARCserve Trap Definition File called ASMIB.TDF from the Alert for Windows NT directory on your Windows 2000 workstation to a floppy diskette.

2. Insert the diskette in the workstation where your HP OpenView software is installed and copy the ASMIB.TDF file to your OV \TRAPMGR directory.

3. Load the HP OpenView software on your workstation and add the
ARCserve trap file using the Customize Traps option in the Monitor Menu.

5.2.2 Follow these steps if the NetServer Assistant software is installed:

1. Copy the ARCserve MIB file called ASMIB.MIB from the Alert directory on your Windows 2000 workstation to a floppy diskette.

2. Insert the diskette in the workstation where your HP OpenView software is installed and copy the ASMIB.MIB file to your OV\MIB directory.

3. Load the HP OpenView software on your workstation and compile the ARCserve MIB file using the Manage Database option from the Control SNMP Manager Menu.

5.3 Configuring Alert for UNIX based SNMP Managers such as HP OpenView and IBM NetView

In order to receive Alert Notification traps from InocuLAN or ARCserve, the appropriate MIB and TRAP definition files must be loaded by the SNMP Manager (HP OpenView UNIX and/or IBM NetView).

The following steps are required to compile/load these files:

1. Convert INOMIB.MIB and ARCMIB.MIB from DOS format to UNIX format. The *.MIB files contain SNMP definitions. They come in DOS format. In order to compile them, they must be converted to UNIX format.

ex. dos2unix < inomib.mib > inomib_u.mib
ex. dos2unix < asmib.mib > asmib_u.mib

2. Compile/load the MIB files inomib_u.mib and arcmib_u.mib into the SNMP
Managers.

3. Convert INO.CNF and ARC.CNF from DOS format to UNIX format.

ex. dos2unix < ino.cnf > ino_u.cnf
ex. dos2unix < arc.cnf > arc_u.cnf

4. Load the trap definition files into the SNMP Manager's trap database. The following is the syntax:

xnmevents -load ino_u.cnf
xnmevents -load arc_u.cnf


Hope this helps,
DatabaseBaba

 

[Lalabrigaboris]

Does anyone know the steps involved to send the SNMP traps to MOM (Microsoft Operations Manager)? I've followed the steps provided in the MOM manual on how to recieve traps from 3rd party software (translate asmib.mib from WMI tool smi2smir), ensure the community name is correct and configure MOM appropriately. I haven't used SNMP before so I'm in the midst of learning it. My questions are:
1) is asmib.mib a V1 or V2 file?
2) does anyone know if there is a special config you have to do for MOM to process the traps?

Thanks in advance for your help.

 

[davidmichel]

The mib file is in the Alert directory.

 

[kendas]

any help on how to configure snmp for HP insight manager??

 

[pluscarden]

I have configured Arcserve to send SNMP traps to a Linux server when my back-up job succeeds or fails. This seem to work fine. The snmptrapd daemon running on my Linux server successfully intercepts the trap and places it in my /var/log/messages file (via syslog).

However, I am a little confused since the trap sent back only seems to include the general description OID. So, for example, if my backup operation was successful then I just get something like this :

.1.3.6.1.4.1.46.877.5 = MyServer (JobID:200) Backup Operation Successful..Number of Error(s)/Warnings: 0/1

But I was kinda expecting a specific trap (arcServetrap13 to be precise) to be sent back. Does anyone have any ideas how I can get Arcserve to send back the specicic trap (arcservetrap4, arcservertrap5,arcservetrap6, etc.) rather than the general description trap I am currently getting?

I have included the actual Arcserve alarm MIB below to try and illustrate what I am talking about!


ARCserve-Alarm-MIB DEFINITIONS ::= BEGIN

IMPORTS
enterprises FROM RFC1065-SMI
OBJECT-TYPE FROM RFC-1212
TRAP-TYPE FROM RFC-1215;

cheyenne OBJECT IDENTIFIER ::= { enterprises 46 }
arcServe OBJECT IDENTIFIER ::= { cheyenne 877 }
arcServeRev OBJECT IDENTIFIER ::= { arcServe 1 }

-- *************************************************************************
-- ARCserve (1.3.6.1.4.1.46.877)
-- **************************************************************************
arcServeevMajor OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The major revision level of ARCserve (left of the decimal).
Used for presence checking."
::= { arcServeRev 1 }

arcServeRevMinor OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The minor revision level of ARCserve (right of the decimal)."
::= { arcServeRev 2 }

arcServeParmsTrapEnable OBJECT-TYPE
SYNTAX INTEGER (0..1)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates whether agent should or should not send traps."
::= { arcServe 2 }

arcServeParmsPollTime OBJECT-TYPE
SYNTAX INTEGER (60..2592000)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Seconds between checking for traps."
::= { arcServe 3 }

arcServeServerName OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"ARCserve server which generated trap."
::= {arcServe 4}

arcServetrapdesc OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS optional
DESCRIPTION
"A description of a specific Cheyenne trap"
::= {arcServe 5}

-- *************************************************************************
-- traps
-- **************************************************************************
arcServetrapHigh TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"ARCserve Critical Trap

A Critical trap has been generated by ARCserve.
Refer to the trap summary information for a detailed
description of this trap. A critical trap normally
indicates a serious error has occurred."
--#TYPE "ARCserve Critical"
--#SUMMARY "%s %s "
--#ARGUMENTS {0,1}
--#SEVERITY CRITICAL
--#STATE DEGRADED
::= 1
arcServetrapMed TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"ARCserve Minor Trap

A minor trap has been generated by ARCserve. Minor
traps are used by ARCserve to warn the user of unusual,
but not fatal incidents. Review the message summary to
determine if this trap should concern you."
--#TYPE "ARCserve Warning"
--#SUMMARY "%s %s "
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 2
arcServetrapLow TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"ARCserve Informational Trap

An ARCserve informational trap has been generated by
ARCserve."
--#TYPE "ARCserve Informational"
--#SUMMARY "%s %s "
--#ARGUMENTS {0,1}
--#SEVERITY INFORMATIONAL
--#STATE OPERATIONAL
::= 3
arcServetrap4 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to locate job list service.

This trap signifies that ARCserve was unable to locate
it's NetWare queue or Windows NT/UNIX Job list. This problem
can be caused in NetWare by Bindery or Directory Services
corruption or by the deletion of the ARCserve queue."
--#TYPE "Failed to locate job list service."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 4
arcServetrap5 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to retrieve job from Job List Service.

This trap signifies that ARCserve cannot process jobs.
Under NetWare, this is normally due to a Bindery or
Directory Services corruption. Please verify that ARCserve
was completely installed and that your Bindery/Directory is
not corrupted."
--#TYPE "Failed to retrieve job from Job List Service."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 5
arcServetrap6 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to allocate memory.

This trap signifies that ARCserve was unable to allocate
memory. More server memory may be required if this message
occurs on a regular basis. This message is not normally
fatal, unless repeated attempts for memory fail."
--#TYPE "Failed to allocate memory."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 7
arcServetrap7 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Server is low on memory, cannot start jobs.

This trap signifies that server is so low on memory
that jobs cannot be processed. Shutdown any unnecessary
modules to obtain additional memory so that jobs can be
processed. Jobs will be processed when sufficeint memory
has been restored on the server."

--#TYPE "Server is low on memory, cannot start jobs."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 8
arcServetrap8 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Same license found on another server.

This trap signifies that another server has the same
license as the server which generated the server. You
must install different licenses on each ARCserve server."
--#TYPE "Same license found on another server."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 9
arcServetrap9 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to format tape.

This trap signifies that ARCserve was unable to format
a tape. This could be caused by hardware or media failure.
Verify tape drive has been cleaned and all cable connections.
This message can also occur when an invalid board driver has
been loaded."
--#TYPE "Failed to format tape."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 9
arcServetrap10 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to read tape header.

This trap signifies a hardware or device failure when trying
to read the tape header. Verify that the tape is an ARCserve
formatted tape. Also verify that the tape drive has been
cleaned and all cables are properly connected. This message
can also be displayed when an invalid board driver has been
loaded."
--#TYPE "Failed to read tape header."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 10
arcServetrap11 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Failed to access tape.

This trap signifies that ARCserve was unable to access the
the tape. Also verify that the tape drive has been
cleaned and all cables are properly connected. This message
can also be displayed when an invalid board driver has been
loaded."
--#TYPE "Failed to access tape."
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 11
arcServetrap12 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Backup Operation Cancelled.

This trap indicates that the backup job has been cancelled.
This is normally due to an operator cancelling/deleting a job
from the ARCserve job list."
--#TYPE "Backup Operation Cancelled"
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 12
arcServetrap13 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Backup Operation Successful

This trap signifies that the backup operation completed
successfully."
--#TYPE "Backup Operation Successful"
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY INFORMATIONAL
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 13
arcServetrap14 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Backup Operation Incomplete

This trap signifies that the backup operation completed with
warnings. Refer to the activity log to determine if important
nodes selected for backup have been missed."
--#TYPE "Backup Operation Incomplete"
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY MINOR
--#TIMEINDEX 1
--#STATE OPERATIONAL
::= 14
arcServetrap15 TRAP-TYPE
ENTERPRISE arcServe
VARIABLES {
arcServeServerName,
arcServetrapdesc
}
DESCRIPTION
"Backup Operation Failed

This trap signifies that backup operation failed. This message
indicates that the backup encountered serious processing errors.
Refer to the activity log for a description of the problems en-
countered which caused the backup failed."
--#TYPE "Backup Operation Failed"
--#SUMMARY "%s %s"
--#ARGUMENTS {0,1}
--#SEVERITY CRITICAL
--#TIMEINDEX 1
--#STATE DEGRADED
::= 15
END

 

[davidmichel]

Have you configured the backup job to send the alert for Job Incomplete?