From: patrik.koch@philips.com
Date: Fri Mar 07 2003 - 12:29:23 EST
Two T3+ in production show the same strange behaviour:
Every night at around 00:50 each T3+ sends two SNMP traps to the
addresses 192.103.54.1 and 192.103.54.5
SNMP configuration is done as described in the manuals,
also checked by the Sun engineer who has installed the system,
the addresses above are unknown and nowhere mentioned.
Perhaps firmware debug traps? Any hints?
Regards,
Patrik
Some T3 output:
ver>
T3B Release 2.01.00 2002/03/22 18:35:03 (192.168.1.242)
Copyright (C) 1997-2001 Sun Microsystems, Inc.
All Rights Reserved.
sys list>
blocksize : 64k
cache : auto
mirror : auto
mp_support : none
naca : off
rd_ahead : on
recon_rate : med
sys memsize : 128 MBytes
cache memsize : 1024 MBytes
enable_volslice : on
fc_topology : auto
cat /etc/syslog.conf>
# syslog.conf
# facility.level action
# messages to local syslog file
*.notice /syslog
# messages to syslogd on another host
# *.warn @saturn
# messages sent as SNMP traps
*.warn |snmp_trap 130.xxx.yyy.zzz <- wiped out
# messages to syslogd on another host
*.notice @130.xxx.yyy.vvv <- wiped out
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:57 EDT