Hi,

Can any one tell me is there any difference between SNMP / SNMPD configuration in RHAS 2.1 and RHAS 3.0 (upgrade 2) because my application which works fine with RHAS 2.1 is giving me problematic results with RHAS 3.0 upgrade 2.

My SNMP agent structure is as follows:
1) Main SNMP Agent running on port 161 (default)
2) Our Sub Agent running on port 8001, which is our product and monitores our MIB subtree.


Now both of the agents monitor MIB. Our application also has its entries in the MIB. A query for our application's MIB entries could either come through port 161 or through 8001. When it has come through 8001 the sub agent responds to the query (which is working perfectly) and when it is through 161 the default SNMP agent responds to it, by inturn calling the sub agent running at 8001. This redirection is achieved through an entry in "snmpd.conf":

proxy -c public -v 1 -p 8001 localhost .1.2.3.4

*say our application's MIB entries starts at .1.2.3.4

Now first of all this redirection works well in 2.1 but doesnt work at all in 3.0. In 3.0, I am able to "contact" the entries but snmpwalk command fails.

So just to provide a work around, we changed the entry to

proxy -c public -v 1 localhost:8001 .1.2.3.4

Now I am able to contact as well as "walk" the MIB entries but during snmpwalk when it reaches the last entry of our application's MIB subtree, it keeps on prints its value indefinitly.


Please let me know:
1) Is there some other specifc setting that needs to be done for RHAS3.0 since the application works fine with RHAS2.1
2) Is it is a bug with RHAS3.0 upgrade2 (just in case )

Thanks and Regards,
Nitin