Re: Inform Destination

Hello,

thank you Wes for your answers that are always usefull !

I'm progressing but I still have some questions...
So I have created rows for the tables snmpNotifyTable, snmpTargetAddrTable 
and smpTargetParamsTable, using the 'createAndGo' (4) value.
First question: for the three tables, I wanted to set the "storageType" to 
ReadOnly(5), but I had the answer :
Error in packet.
Reason: wrongValue (The set value is illegal or unsupported in some way)
Failed object: SNMP-NOTIFICATION-MIB::snmpNotifyType.'tdrs0'
Could you explain me why I've got this answer ? (Actually, I wanted to set 
ReadOnly because I noticed that when I specify an informsink in the 
snmpd.conf file, a row is created in these tables and the StorageType is 
always ReadOnly)

Second question: as you can see below, for the snmpNotifyTable, the 
rowStatus is 'active'. But for snmpTargetAddrTable and 
snmpTargetParamsTable, the rowStatus is 'notInService'.

snmpwalk -v2c -c public xxx.xx.xx.xx:2045 .1.3.6.1.6.3.13
SNMP-NOTIFICATION-MIB::snmpNotifyTag.'tdrs0' = STRING: tdrs0
SNMP-NOTIFICATION-MIB::snmpNotifyType.'tdrs0' = INTEGER: inform(2)
SNMP-NOTIFICATION-MIB::snmpNotifyStorageType.'tdrs0' = INTEGER: 
nonVolatile(3)
SNMP-NOTIFICATION-MIB::snmpNotifyRowStatus.'tdrs0' = INTEGER: active(1)

snmpwalk -v2c  -c public xxx.xx.xx.xx:2045 .1.3.6.1.6.3.12
SNMP-TARGET-MIB::snmpTargetSpinLock.0 = INTEGER: 0
SNMP-TARGET-MIB::snmpTargetAddrTDomain.'tdrs0' = OID: 
SNMPv2-TM::snmpUDPDomain
SNMP-TARGET-MIB::snmpTargetAddrTAddress.'tdrs0' = Hex-STRING: 7F 00 00 01 
00 A2
SNMP-TARGET-MIB::snmpTargetAddrTimeout.'tdrs0' = INTEGER: 1000
SNMP-TARGET-MIB::snmpTargetAddrRetryCount.'tdrs0' = INTEGER: 5
SNMP-TARGET-MIB::snmpTargetAddrTagList.'tdrs0' = STRING: tdrs0
SNMP-TARGET-MIB::snmpTargetAddrParams.'tdrs0' = STRING: tdrs0
SNMP-TARGET-MIB::snmpTargetAddrStorageType.'tdrs0' = INTEGER: 
nonVolatile(3)
SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'tdrs0' = INTEGER: 
notInService(2)
SNMP-TARGET-MIB::snmpTargetParamsMPModel.'tdrs0' = INTEGER: 1
SNMP-TARGET-MIB::snmpTargetParamsSecurityModel.'tdrs0' = INTEGER: 2
SNMP-TARGET-MIB::snmpTargetParamsSecurityName.'tdrs0' = STRING: public
SNMP-TARGET-MIB::snmpTargetParamsSecurityLevel.'tdrs0' = INTEGER: 
noAuthNoPriv(1)
SNMP-TARGET-MIB::snmpTargetParamsStorageType.'tdrs0' = INTEGER: 
nonVolatile(3)
SNMP-TARGET-MIB::snmpTargetParamsRowStatus.'tdrs0' = INTEGER: 
notInService(2)
SNMP-TARGET-MIB::snmpUnavailableContexts.0 = Counter32: 0
SNMP-TARGET-MIB::snmpUnknownContexts.0 = Counter32: 0

Do I miss to set some usefull information for the agent here ?
or maybe, I have to set all the informations in a specific order ?

Thank you for any answer !
Best Regards
Celine



Wes Hardaker <[email protected]> wrote on 04/05/2006 12:57:18 
PM:

> >>>>> On Tue, 4 Apr 2006 11:24:31 -0500, <[email protected]> 
said:

> cherrero> 1. I've defined my own traps in one private MIB but I don't
> cherrero> understand how to use the SNMP-NOTIFICATION-MIB.  Should I
> cherrero> register my traps in this MIB ?

> no, that mib actually registers destinations to which all
> notifications can be sent (though the MIB also provides filtering if
> needed).  When your code sends a notification of any kind, it'll be
> sent to anything registered in that table.

> cherrero> 2. In my snmpd.conf, I use the option 'informsink' to
> cherrero> specify to the agent where to send the informs. Should I see
> cherrero> this target address in the SNMP-TARGET-MIB ?  if not, if I
> cherrero> add (via snmpset) the same address in this MIB, does the
> cherrero> inform sent twice ?  If I add a target in the
> cherrero> SNMP-TARGET-MIB, is it persistent ? ie is this information
> cherrero> will be still there after an agent reset ?

> 1) informsinks *should* register itself in the mib, although there are
> exceptions where this doesn't happen.
> 2) If you do register something twice, then you'll get 2 notifications
> sent to it.
> 3) the mib tables should be persistent, yes.
> --
> Wes Hardaker
> Sparta, Inc.