|To:||"Hill, Channing" <CHill@BBandT.com>, <firstname.lastname@example.org>|
|Subject:||RE: [nv-l] Efficiency of snmpd.conf|
|From:||"Barr, Scott" <Scott_Barr@csgsystems.com>|
|Date:||Fri, 25 Jul 2003 12:54:01 -0500|
|Delivered-to:||mailing list email@example.com|
|Delivery-date:||Fri, 25 Jul 2003 18:57:45 +0100|
|Mailing-list:||contact firstname.lastname@example.org; run by ezmlm|
|Thread-topic:||[nv-l] Efficiency of snmpd.conf|
You don't have much choice.
The smarset entries in ovsnmp.conf cannot be used during discovery. So if you DON'T use the communityNames.conf file, you will never get an SNMP request to work on them in the first place and thus you won't be able to have the smartset entry picked up in ovsnmp.conf. (Unless your smartset is based SOLEY on the name of the box. It's a chicken vs. egg problem. You have to have an entry in ovsnmp.conf first before the smarset criteria applies.
Someone chime in if this is wrong. Our smarset criteria is often based on SysContact and SysLocation which of course, can't be interrogated until after the box has been discovered which requires SNMP in the first place.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||[nv-l] Deletion of objects from normal topology DB, Liew, Wen|
|Next by Date:||RE: [nv-l] Efficiency of snmpd.conf, Hill, Channing|
|Previous by Thread:||[nv-l] Efficiency of snmpd.conf, Hill, Channing|
|Next by Thread:||RE: [nv-l] Efficiency of snmpd.conf, Hill, Channing|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web