[Top] [All Lists]

Re: [nv-l] ibm server raid manager traps

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] ibm server raid manager traps
From: James Shanks <jshanks@us.ibm.com>
Date: Tue, 18 Apr 2006 14:07:38 -0400
Delivery-date: Tue, 18 Apr 2006 19:08:12 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <001e01c6630d$30d5f210$240a8081@maipu>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
What's in $NVA?
When you say the Agent address is in  $NVATTR_1 is that as a string or an
IP address?   In other words, who did the name resolution for that varbind,
the RAID server or  your Solaris box?    If the RAID server, then perhaps
when your Solaris machine, which presumably has a good DNS, will  resolve
the agent address of the trap ($NVA) as a FQDN.

If not, then you'd need to resolve it again yourself in a script.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

             "Jorge Jiles"                                                 
             erta.ca>                                                   To 
             Sent by:                  <nv-l@lists.us.ibm.com>             
             owner-nv-l@lists.                                          cc 
                                       [nv-l] ibm server raid manager      
             04/18/2006 01:26          traps                               
             Please respond to                                             

Netview 7.1.4 Solaris 9

I’m setting up traps correlation from Windows servers (windows 2000 and
2003) running IBM Raid Manager Version 6.11.07 (2224)

The correlation passes the following variables:

$NVE              Event OID

$NVG              Generic Trap Number (6)

$NVS              Specific Trap Number

$NVATTR_1   Agent Address

$NVATTR_2   Some variable




$NVATTR_6 some variable

The problem I’m having is that $NVATTR_1 (Agent Address) only displays the
agent windows name (local system) and not the fully qualified DNS name. Of
course this is causing problems to identify servers with the same windows
name, but registered on different DNS domains. I asked one of the Window’s
administrators to check if there is any way that the raid manager passes
the servers’ DNS name, but he has been unable to make any progress.

Has any one out there encountered this same issue???

For our trap processing to work, the offending device must be able to pass
its fully qualified DNS name.

Thanks for any help.

Jorge A. Jiles

Network Analyst

Academic Information and Communication Technologies (AICT)

Phone: (780) 492-9168

University of Alberta

Edmonton, Alberta


"This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal, and/or privileged
information.  Please contact us immediately if you are not the intended
recipient of this communication.  If you are not the intended recipient of
this communication, do not copy, distribute, or take action on it. Any
communication received in error, or subsequent reply, should be deleted or

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web