|
Hi, Patrick.
I don't know about DECswitch900/Enterprise RMON.
But in case of using DECpacketprobe90,
you can setup another trap destinations to probe.
Most simple way is create new instance(for example .2) entry,
and if you want PC dosen't receive traps from probe any more,
set Status to invalid. (perhaps, instance is .1)
Below is a sample script for NetView machine.
Of course, you can set each of values manually by using MIB browser.
------ begin of script -------
instance=2 # new instance number not in use
probe=myprobe
write_community=public
trap_target=10.1.1.2 #second trap target you want
trap_community=public
NETscout_objID=.1.3.6.1.4.1.141.1.1.1.1.1
/usr/OV/bin/snmpset -c $write_community $probe \
$NETscout_objID.7.$instance Integer 2 #Status to createRequest
# you may modify IfIndex(.2.) parameter appropriately
/usr/OV/bin/snmpset -c $write_community $probe \
$NETscout_objID.2.$instance Integer 1 \
$NETscout_objID.3.$instance IPAddress $trap_target \
$NETscout_objID.4.$instance OctetString $trap_community \
$NETscout_objID.5.$instance Integer 7 \
$NETscout_objID.6.$instance OctetString "myname" \
$NETscout_objID.7.$instance Integer 1 #Status to valid
------ end of script -------
> That will be useful because, if i want to set the right Trap Address, i
> have to be loggin on the Netwiew system. But we'are using PC with
> CLearvisn too and in this case, if we set information, the traps will
> be sent on the PC.
>
> I need to send all the traps on a single system (Netview).
I understand well that you said, and this is a freqent situation,
so RMON Manager/PROBEwatch provides a command called "dvadmin"
for just only that purpose.
In UNIX version,
"dvadmin" is a simply command "$NSHOME/bin/dvadmin"
that is able to launch from any shell prompt.
(but it's really symbolic-linked to "nsshell".)
In Windows version,
"dvadmin" will be executed from "NETscout Shell" or "clearVISN Shell"
command line that launched at right side down button in main manager window.
Of course, you can launch $NSHOME\bin\nsshell.exe directly.
At command line, you should enter like this.
--> dvadmin add <agent-name> <ip-addr-for-trap-sending> <community-name>
Usually, we use "startup" scripts for those setting.
Because probe's power down/up cause probe to forget installed domains,
threshold settings and trap destinations.
------ begin of startup script -------
## Note: "%1" is a macro replaced by the agent name.
# In UNIX version, change %1 to $1
dvinst dvinst.cfg %1
#
echo "Setting Threshold for agent" %1
dvwatch add %1 ALL dvwatch.cfg
echo "Setting Trap Destinatios for agent" %1
dvadmin add %1 10.1.1.1 public
dvadmin add %1 10.1.1.2 public
:
#repeat all nodes that receive traps
:
:
------ end of startup script -------
And execute from DOS prompt like this,
C:\> C:\clearVIS\PROBEW\bin\nsshell.exe agent-name "<" C:\clearVIS\PROBEW\usr\startup
I don't know mib value setting or "dvadmin" work fine
with DECswitch900/Enterprise RMON. Please try to test it.
Lastly, your question is probably related to
a SNMP agent side(in your case, DECswitch900).
So if you want to ask any more questions about this,
you should ask at HUB_MGNT conference watched by
people familiar with hub products.
(however, thers is no guarantee for usefull replies although at HUB_MGNT,
especially about RMON. :-)
--
Yoshiharu Enya
|