I am experiencing similar problems with Altiga traps as you did with the
8272 system noted in your email below. The addtrap script generated by
mib2trap also lacks the -i option specifying the enterprise ID. Looking at
the MIB file, tho, I am at a loss how to proceed tracking it back to it's
root. Could you please pass on how you tracked down the e-ID for the 8272?
Thank You & Regards,
Sr. Network Mgmt. Engineer
From: Ray Westphal [mailto:firstname.lastname@example.org]
Sent: Monday, October 09, 2000 7:15 AM
To: NV List (E-mail)
Subject: [NV-L] Re: Addtrap problem.
Thanks James & Mythili .....
You were both correct. Here's the format that finally worked.
/usr/OV/bin/addtrap -n ibm8272TsSys -l ibm8272TsTempThreshold \
-i 220.127.116.11.18.104.22.168.66 -g 6 -s 1 \
-o A -c "LOGONLY" -t 0 \
-S 1 \
-D "This trap is generated when the system temperature
either exceeds 50 C or when it returns to normal(45 C)
after exceeding the temperature. The variable
ibm8272Ts2SysTemperature indicates the temperature
condition at the time of the event." \
-e ibm8272TsTempThreshold \
-F '$E $G $S $# args: $*'
Archive operated by Skills 1st Ltd
See also: The NetView Web